fedora usb devices

[Bill Rees]

Bob Chiodini wrote:
> On Tue, 2005-08-02 at 17:24 -0700, Bill Rees wrote:
>   
>> Hi,
>>     I've upgraded from a fedora core 2 to fc 4 and have discovered that 
>> /dev/usb has apparently gone away.  I have a usb device that reports 
>> real time data from a bunch of sensors that I had working on fc2 and 
>> need to get working on fc4.  Where should my driver be looking for the 
>> usb device?
>>
>> bill rees
>>
>>     
>
> Bill,
>
> Some more info is needed:
>
> In FC2 what was the device file name of your USB device?  In FC4 what
> does dmesg and /var/log/messages tell you about the device?  Is your
> driver a kernel module or a user space application?
>
> Bob...
>
>   
Hi Bob,
    Below is the data for your questions.  I didn't look at messages 
since the files were rotated out of existence before I went back to look 
at them.  Since the dmesg info indicates that the usb device didn't even 
get registered and in fact now creates an ETIMEOUT (-110) where before 
it worked, I'm going to take this discussion over to the linux-usb 
list.  I still would like to know where the device will show up but 
until I get the usb board even registered it's not worrying about.  
Thanks for your help and go ahead and comment on the following data 
since I'll still be listening on this thread.

bill

In FC2 the device file name is /dev/usb/vdmrio
                    crw-r--r--  1 root root 180, 192 Dec 10  2004 
/dev/usb/vdmrio

The dmesgs relevant to this usb device are:

FC2:
        EXT3 FS on hda2, internal journal
        EXT3-fs: mounted filesystem with ordered data mode.
        usb 2-1: string descriptor 0 read error: -71
        usb 2-1: string descriptor 0 read error: -71
        usb 2-1: string descriptor 0 read error: -71
        usb 2-1: string descriptor 0 read error: -71
        usb 2-1: string descriptor 0 read error: -71
        usb 2-1: string descriptor 0 read error: -71
        VP_IDE: IDE controller at PCI slot 0000:00:11.1
        ACPI: PCI interrupt 0000:00:11.1[A] -> GSI 5 (level, low) -> IRQ 5


FC4:
        Bluetooth: L2CAP socket layer initialized
        usb 2-1: string descriptor 0 read error: -110
        usb 2-1: string descriptor 0 read error: -110
        usb 2-1: string descriptor 0 read error: -110
        usb 2-1: can't set config #1, error -110
        usb 2-1: new full speed USB device using ohci_hcd and address 3
        usb 2-1: string descriptor 0 read error: -110
        usb 2-1: string descriptor 0 read error: -110
        usb 2-1: string descriptor 0 read error: -110
        usb 2-1: can't set config #1, error -110
        usb 2-1: new full speed USB device using ohci_hcd and address 4
        usb 2-1: string descriptor 0 read error: -110
        usb 2-1: string descriptor 0 read error: -110
        usb 2-1: string descriptor 0 read error: -110
        usb 2-1: can't set config #1, error -110
        usb 2-1: new full speed USB device using ohci_hcd and address 5
        usb 2-1: string descriptor 0 read error: -110
        usb 2-1: string descriptor 0 read error: -110
        usb 2-1: string descriptor 0 read error: -110
        usb 2-1: can't set config #1, error -110
        Bluetooth: RFCOMM ver 1.5