New UPS, can't find its device?

Gene Heskett gene.heskett at verizon.net
Mon Mar 5 22:42:12 UTC 2007


Greetings;

FC6 system, uptodate as of an hour ago.

My old ups has been missing power bumps, causing resets, but its battery 
is fresh and good, so I popped for a new Belkin F6C1500-TW-RK

When I plugged its usb cable into a usb2.0 hub, I got this in dmesg:

usb 3-3.4.4: new low speed USB device using ehci_hcd and address 8
usb 3-3.4.4: configuration #1 chosen from 1 choice
hiddev96: USB HID v1.11 Device [Belkin  Belkin UPS] on 
usb-0000:00:02.2-3.4.4

That last 'device' I assume I'd find in /proc.

However, when I do an lsusb -v|grep  -A56 'Bus 003 Device 008', this falls 
out:

Bus 003 Device 008: ID 050d:0751 Belkin Components
Device Descriptor:
  bLength                18
  bDescriptorType         1
  bcdUSB               1.10
  bDeviceClass            0 (Defined at Interface level)
  bDeviceSubClass         0
  bDeviceProtocol         0
  bMaxPacketSize0         8
  idVendor           0x050d Belkin Components
  idProduct          0x0751
  bcdDevice            0.01
  iManufacturer           4 Belkin
  iProduct               20 Belkin UPS
  iSerial                 0
  bNumConfigurations      1
  Configuration Descriptor:
    bLength                 9
    bDescriptorType         2
    wTotalLength           34
    bNumInterfaces          1
    bConfigurationValue     1
    iConfiguration          0
    bmAttributes         0xc0
      Self Powered
    MaxPower               20mA
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        0
      bAlternateSetting       0
      bNumEndpoints           1
      bInterfaceClass         3 Human Interface Devices
      bInterfaceSubClass      0 No Subclass
      bInterfaceProtocol      0 None
      iInterface              0
        HID Device Descriptor:
          bLength                 9
          bDescriptorType        33
          bcdHID               1.11
          bCountryCode           33 US
          bNumDescriptors         1
          bDescriptorType        34 Report
          wDescriptorLength     543
         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             248

And, apparently udev is at work as I have two new devices in the /dev 
directory that showed up when I plugged the usb cable from it into the 
hub:

crw------- 1 root root   254,  24 Mar  5 16:50 usbdev3.8_ep00
crw------- 1 root root   254,  25 Mar  5 16:50 usbdev3.8_ep81

The ups is powered up, so it seems like I should be able to cat that 
puppy, but:
[root at coyote Bulldog]# cat /dev/usbdev3.8_ep00
cat: /dev/usbdev3.8_ep00: No such device or address
rinse lather repeat for the _ep81 address:

There are not any /dev/ttyUSB* devices beyond the one associated with a 
pl2303 cable that's plugged in also.  The instructions from Belkin to 
install their monitoring software says the device it is going to use must 
be present before running the installer.  Am I not building enough 
modules in my 2.6.20+rds custom kernel or what?

Thanks all.

-- 
Cheers, Gene
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Yahoo.com and AOL/TW attorneys please note, additions to the above
message by Gene Heskett are:
Copyright 2007 by Maurice Eugene Heskett, all rights reserved.




More information about the fedora-list mailing list