Vladimir Micovic
2012-Jan-02 05:14 UTC
[Nut-upsdev] Problem with detecting "Mustek PowerMust 2000VA"
Hello,
i try to setup NUT service to read/control my UPS but without success.
Problem is when i try to start "/usr/local/ups/bin/upsdrvctl -DDDD -u
root start" i got:
/Network UPS Tools - UPS driver controller 2.6.2/
/ 0.000000/
/If you're not a NUT core developer, chances are that you're
told to enable debugging/
/to see why a driver isn't working for you. We're sorry for the
confusion, but this is/
/the 'upsdrvctl' wrapper, not the driver you're interested
in./
/Below you'll find one or more lines starting with 'exec:'
followed by an absolute/
/path to the driver binary and some command line option. This is
what the driver/
/starts and you need to copy and paste that line and append the
debug flags to that/
/line (less the 'exec:' prefix)./
/ 0.000348 Starting UPS: mustek/
/ 0.000489 exec: /usr/local/ups/bin/blazer_ser -a mustek
-u root/
/Network UPS Tools - Megatec/Q1 protocol serial driver 1.51 (2.6.2)/
/Unable to open auto: No such file or directory/
/Things to try:/
/ - Check 'port=' in ups.conf/
/ - Check owner/permissions of all parts of path/
/Fatal error: unusable configuration/
/ 0.003411 Driver failed to start (exit status=1)
/
//My "/usr/local/ups/etc/ups.conf" contain:
user = root
[mustek]
driver = blazer_ser
port = auto
UPS is connected over USB and log from "message" show next on connect:
hiddev97: USB HID v1.00 Device [Cypress Semiconductor USB to
Serial] on usb-0000:00:1a.0-1
Can i get some help please? :)
thank you.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.alioth.debian.org/pipermail/nut-upsdev/attachments/20120102/f206e506/attachment.html>
Charles Lepple
2012-Jan-02 14:22 UTC
[Nut-upsdev] Problem with detecting "Mustek PowerMust 2000VA"
On Jan 2, 2012, at 12:14 AM, Vladimir Micovic wrote:> Hello, > > i try to setup NUT service to read/control my UPS but without success. > Problem is when i try to start "/usr/local/ups/bin/upsdrvctl -DDDD -u root start" i got: > > Network UPS Tools - UPS driver controller 2.6.2 > 0.000000 > If you're not a NUT core developer, chances are that you're told to enable debugging > to see why a driver isn't working for you. We're sorry for the confusion, but this is > the 'upsdrvctl' wrapper, not the driver you're interested in. > Below you'll find one or more lines starting with 'exec:' followed by an absolute > path to the driver binary and some command line option. This is what the driver > starts and you need to copy and paste that line and append the debug flags to that > line (less the 'exec:' prefix). > 0.000348 Starting UPS: mustek > 0.000489 exec: /usr/local/ups/bin/blazer_ser -a mustek -u root > Network UPS Tools - Megatec/Q1 protocol serial driver 1.51 (2.6.2) > Unable to open auto: No such file or directory[...]> hiddev97: USB HID v1.00 Device [Cypress Semiconductor USB to Serial] on usb-0000:00:1a.0-1Using "port = auto" is for drivers which connect using USB APIs, such as blazer_usb. If the UPS had been recognized by the kernel as a true USB-to-serial device, you would have something like "/dev/ttyUSB*" created when the UPS is plugged in. In that case, you would use a serial-based driver like blazer_ser. Without seeing more specific information (such as the output of lsusb) it is not possible to tell for certain whether blazer_usb is the correct driver. Also, please subscribe to the list before posting (even if in digest mode):> _______________________________________________ > Nut-upsdev mailing list > Nut-upsdev at lists.alioth.debian.org > http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsdev-- Charles Lepple clepple at gmail
Vladimir Micovic
2012-Jan-02 15:51 UTC
[Nut-upsdev] Problem with detecting "Mustek PowerMust 2000VA"
Hello, i am subscribe to list :S How can i see which port can be setup? I need just to try to read data from him, after that i will setup nut by myself i guess :) lsusb show this: Bus 003 Device 004: ID 0665:5161 Cypress Semiconductor USB to Serial best regards and thank you. p.s: HNY! :)
Petr Kubánek
2012-Jan-02 15:57 UTC
[Nut-upsdev] Problem with detecting "Mustek PowerMust 2000VA"
run: dmesg and look for ttyUSB (dmesg | less should be more usefull) Petr Vladimir Micovic p??e v Po 02. 01. 2012 v 16:51 +0100:> Hello, > > i am subscribe to list :S > How can i see which port can be setup? I need just to try to read data > from him, after that i will setup nut by myself i guess :) > > lsusb show this: > > Bus 003 Device 004: ID 0665:5161 Cypress Semiconductor USB to Serial > > > best regards and thank you. > > > p.s: HNY! :) > > _______________________________________________ > Nut-upsdev mailing list > Nut-upsdev at lists.alioth.debian.org > http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsdev
Charles Lepple
2012-Jan-02 16:00 UTC
[Nut-upsdev] Problem with detecting "Mustek PowerMust 2000VA"
On Jan 2, 2012, at 10:51 AM, Vladimir Micovic wrote:> Bus 003 Device 004: ID 0665:5161 Cypress Semiconductor USB to SerialUnfortunately, this device ID is used by several different vendors. What does "lsusb -vvv -d 0665:5161" show? Also, what OS and kernel are you using? (I thought certain kernels had USB-to-serial drivers for that chip.) -- Charles Lepple clepple at gmail
Vladimir Micovic
2012-Jan-02 16:05 UTC
[Nut-upsdev] Problem with detecting "Mustek PowerMust 2000VA"
# dmesg | grep ttyUSB
show nothing.
if you need to check something, here is whole dmesg:
http://pastebin.com/mNdUmGKH (there is kernel ver.)
and here lsub with verobse:
# /sbin/lsusb -vvv -d 0665:5161
Bus 003 Device 004: ID 0665:5161 Cypress Semiconductor USB to Serial
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 1.10
bDeviceClass 0 (Defined at Interface level)
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 8
idVendor 0x0665 Cypress Semiconductor
idProduct 0x5161 USB to Serial
bcdDevice 0.02
iManufacturer 1 Cypress Semiconductor
iProduct 2 USB to Serial
iSerial 0
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 34
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 3
bmAttributes 0x80
MaxPower 100mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 1
bInterfaceClass 3 Human Interface Device
bInterfaceSubClass 0 No Subclass
bInterfaceProtocol 0 None
iInterface 4 Sample HID
HID Device Descriptor:
bLength 9
bDescriptorType 33
bcdHID 1.00
bCountryCode 0 Not supported
bNumDescriptors 1
bDescriptorType 34 Report
wDescriptorLength 27
Report Descriptors:
** UNAVAILABLE **
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0008 1x 8 bytes
bInterval 32
On 02-Jan-12 4:57 PM, Petr Kub?nek wrote:> run:
>
> dmesg
>
> and look for ttyUSB (dmesg | less should be more usefull)
>
> Petr
>
> Vladimir Micovic p??e v Po 02. 01. 2012 v 16:51 +0100:
>> Hello,
>>
>> i am subscribe to list :S
>> How can i see which port can be setup? I need just to try to read data
>> from him, after that i will setup nut by myself i guess :)
>>
>> lsusb show this:
>>
>> Bus 003 Device 004: ID 0665:5161 Cypress Semiconductor USB to Serial
>>
>>
>> best regards and thank you.
>>
>>
>> p.s: HNY! :)
>>
>> _______________________________________________
>> Nut-upsdev mailing list
>> Nut-upsdev at lists.alioth.debian.org
>> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsdev
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.alioth.debian.org/pipermail/nut-upsdev/attachments/20120102/561afcf7/attachment-0001.html>
Petr Kubánek
2012-Jan-02 16:32 UTC
[Nut-upsdev] Problem with detecting "Mustek PowerMust 2000VA"
Hi, https://usb-ids.gowdy.us/read/UD suggest there are two Cypress product ID - 0x04b4 and 0x0665. It looks as 0x0665 is not claimed by cypress_m8: http://lxr.free-electrons.com/source/drivers/usb/serial/cypress_m8.h http://lxr.free-electrons.com/source/drivers/usb/serial/cypress_m8.c I believe that adding 0x0665 ID to cypress_m8, recompiling it, should fix the problem. Will you try, or do you prefer to let me do it, send patched version and let you try? If you never compile kernel from source code, this might be painful experience - so if you are running something Ubuntu based, I can try to just ship binary version of the module.. Petr Kubanek http://rts2.org Vladimir Micovic p??e v Po 02. 01. 2012 v 17:05 +0100:> # dmesg | grep ttyUSB > show nothing. > if you need to check something, here is whole dmesg: > http://pastebin.com/mNdUmGKH (there is kernel ver.) > > and here lsub with verobse: > # /sbin/lsusb -vvv -d 0665:5161 > Bus 003 Device 004: ID 0665:5161 Cypress Semiconductor > USB to Serial > Device Descriptor: > bLength 18 > bDescriptorType 1 > bcdUSB 1.10 > bDeviceClass 0 (Defined at Interface > level) > bDeviceSubClass 0 > bDeviceProtocol 0 > bMaxPacketSize0 8 > idVendor 0x0665 Cypress Semiconductor > idProduct 0x5161 USB to Serial > bcdDevice 0.02 > iManufacturer 1 Cypress Semiconductor > iProduct 2 USB to Serial > iSerial 0 > bNumConfigurations 1 > Configuration Descriptor: > bLength 9 > bDescriptorType 2 > wTotalLength 34 > bNumInterfaces 1 > bConfigurationValue 1 > iConfiguration 3 > bmAttributes 0x80 > MaxPower 100mA > Interface Descriptor: > bLength 9 > bDescriptorType 4 > bInterfaceNumber 0 > bAlternateSetting 0 > bNumEndpoints 1 > bInterfaceClass 3 Human Interface Device > bInterfaceSubClass 0 No Subclass > bInterfaceProtocol 0 None > iInterface 4 Sample HID > HID Device Descriptor: > bLength 9 > bDescriptorType 33 > bcdHID 1.00 > bCountryCode 0 Not supported > bNumDescriptors 1 > bDescriptorType 34 Report > wDescriptorLength 27 > Report Descriptors: > ** UNAVAILABLE ** > Endpoint Descriptor: > bLength 7 > bDescriptorType 5 > bEndpointAddress 0x81 EP 1 IN > bmAttributes 3 > Transfer Type Interrupt > Synch Type None > Usage Type Data > wMaxPacketSize 0x0008 1x 8 bytes > bInterval 32 > > > On 02-Jan-12 4:57 PM, Petr Kub?nek wrote: > > run: > > > > dmesg > > > > and look for ttyUSB (dmesg | less should be more usefull) > > > > Petr > > > > Vladimir Micovic p??e v Po 02. 01. 2012 v 16:51 +0100: > > > Hello, > > > > > > i am subscribe to list :S > > > How can i see which port can be setup? I need just to try to read data > > > from him, after that i will setup nut by myself i guess :) > > > > > > lsusb show this: > > > > > > Bus 003 Device 004: ID 0665:5161 Cypress Semiconductor USB to Serial > > > > > > > > > best regards and thank you. > > > > > > > > > p.s: HNY! :) > > > > > > _______________________________________________ > > > Nut-upsdev mailing list > > > Nut-upsdev at lists.alioth.debian.org > > > http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsdev > > > >
Vladimir Micovic
2012-Jan-02 19:36 UTC
[Nut-upsdev] Problem with detecting "Mustek PowerMust 2000VA"
Huh, thank you for your help but i think that alone cannot recompile kernel, if you give me some tips i will try. I was recompile but only for adding NIC driver and that was on slackware, this srv. is on centos. Because i don`t have nothing on that box except samba and 4 disk in raid i think that i can handle my self with little help from you. Do you want to help me via some messenger or join.me or to continue here via email? tnx. On 02-Jan-12 5:32 PM, Petr Kub?nek wrote:> Hi, > > https://usb-ids.gowdy.us/read/UD > > suggest there are two Cypress product ID - 0x04b4 and 0x0665. It looks > as 0x0665 is not claimed by cypress_m8: > > http://lxr.free-electrons.com/source/drivers/usb/serial/cypress_m8.h > http://lxr.free-electrons.com/source/drivers/usb/serial/cypress_m8.c > > I believe that adding 0x0665 ID to cypress_m8, recompiling it, should > fix the problem. Will you try, or do you prefer to let me do it, send > patched version and let you try? If you never compile kernel from source > code, this might be painful experience - so if you are running something > Ubuntu based, I can try to just ship binary version of the module.. > > Petr Kubanek > http://rts2.org > > Vladimir Micovic p??e v Po 02. 01. 2012 v 17:05 +0100: >> # dmesg | grep ttyUSB >> show nothing. >> if you need to check something, here is whole dmesg: >> http://pastebin.com/mNdUmGKH (there is kernel ver.) >> >> and here lsub with verobse: >> # /sbin/lsusb -vvv -d 0665:5161 >> Bus 003 Device 004: ID 0665:5161 Cypress Semiconductor >> USB to Serial >> Device Descriptor: >> bLength 18 >> bDescriptorType 1 >> bcdUSB 1.10 >> bDeviceClass 0 (Defined at Interface >> level) >> bDeviceSubClass 0 >> bDeviceProtocol 0 >> bMaxPacketSize0 8 >> idVendor 0x0665 Cypress Semiconductor >> idProduct 0x5161 USB to Serial >> bcdDevice 0.02 >> iManufacturer 1 Cypress Semiconductor >> iProduct 2 USB to Serial >> iSerial 0 >> bNumConfigurations 1 >> Configuration Descriptor: >> bLength 9 >> bDescriptorType 2 >> wTotalLength 34 >> bNumInterfaces 1 >> bConfigurationValue 1 >> iConfiguration 3 >> bmAttributes 0x80 >> MaxPower 100mA >> Interface Descriptor: >> bLength 9 >> bDescriptorType 4 >> bInterfaceNumber 0 >> bAlternateSetting 0 >> bNumEndpoints 1 >> bInterfaceClass 3 Human Interface Device >> bInterfaceSubClass 0 No Subclass >> bInterfaceProtocol 0 None >> iInterface 4 Sample HID >> HID Device Descriptor: >> bLength 9 >> bDescriptorType 33 >> bcdHID 1.00 >> bCountryCode 0 Not supported >> bNumDescriptors 1 >> bDescriptorType 34 Report >> wDescriptorLength 27 >> Report Descriptors: >> ** UNAVAILABLE ** >> Endpoint Descriptor: >> bLength 7 >> bDescriptorType 5 >> bEndpointAddress 0x81 EP 1 IN >> bmAttributes 3 >> Transfer Type Interrupt >> Synch Type None >> Usage Type Data >> wMaxPacketSize 0x0008 1x 8 bytes >> bInterval 32 >> >> >> On 02-Jan-12 4:57 PM, Petr Kub?nek wrote: >>> run: >>> >>> dmesg >>> >>> and look for ttyUSB (dmesg | less should be more usefull) >>> >>> Petr >>> >>> Vladimir Micovic p??e v Po 02. 01. 2012 v 16:51 +0100: >>>> Hello, >>>> >>>> i am subscribe to list :S >>>> How can i see which port can be setup? I need just to try to read data >>>> from him, after that i will setup nut by myself i guess :) >>>> >>>> lsusb show this: >>>> >>>> Bus 003 Device 004: ID 0665:5161 Cypress Semiconductor USB to Serial >>>> >>>> >>>> best regards and thank you. >>>> >>>> >>>> p.s: HNY! :) >>>> >>>> _______________________________________________ >>>> Nut-upsdev mailing list >>>> Nut-upsdev at lists.alioth.debian.org >>>> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsdev >>> > >