Find the answer to your Linux question:
Results 1 to 7 of 7
Trying to get them to fully work. I hard tried: 2 external hard drives (both require >5ma power) failed a floppy drive (5ma) worked a thumb drive (<5ma) fail -> ...
Enjoy an ad free experience by logging in. Not a member yet? Register.
  1. #1
    Linux Newbie
    Join Date
    Aug 2004
    Posts
    220

    Front usb semi-work (Suse 10.3)


    Trying to get them to fully work.

    I hard tried:
    2 external hard drives (both require >5ma power) failed
    a floppy drive (5ma) worked
    a thumb drive (<5ma) fail -> tested this in windows and it worked so not a power problem

    when I plug in the thumb drive it blinks slowly
    Code:
    linux:~> dmesg | tail
    SFW2-OUT-ERROR IN= OUT=eth1 SRC=1.17.0.12 DST=6.24.14.9 LEN=2 TOS=0x0 PREC=0x00 TTL=64 ID=5199 DF PROTO=TCP SPT=64 DPT=53 WINDOW=4 RES=0x0 ACK FIN URGP=0 OPT (01010031AE)
    usb 4-3: new high speed USB device using ehci_hcd and address 118
    usb 4-3: new high speed USB device using ehci_hcd and address 2
    usb 4-3: new high speed USB device using ehci_hcd and address 3
    usb 4-3: new high speed USB device using ehci_hcd and address 9
    usb 4-3: new high speed USB device using ehci_hcd and address 12
    usb 4-3: new high speed USB device using ehci_hcd and address 13
    usb 4-3: new high speed USB device using ehci_hcd and address 22
    usb 4-3: new high speed USB device using ehci_hcd and address 26
    usb 4-3: new high speed USB device using ehci_hcd and address 32
    any ideas?
    Thanks

  2. #2
    Linux Newbie dilbert's Avatar
    Join Date
    Sep 2006
    Location
    Yorkshire, GB
    Posts
    237
    Presumably driver is missing. What says "cat /proc/bus/usb/devices"?

    In the older threads should be plenty of examples.
    Bus Error: Passengers dumped. Hech gap yo'q.

  3. #3
    Linux Newbie
    Join Date
    Aug 2004
    Posts
    220
    well there doesn't seem to be a "/proc/bus/usb/devices" but there is a "/proc/devices" don't know if it's the same thing but here it is:
    Code:
    linux:/proc # cat devices
    Character devices:
      1 mem
      2 pty
      3 ttyp
      4 /dev/vc/0
      4 tty
      4 ttyS
      5 /dev/tty
      5 /dev/console
      5 /dev/ptmx
      7 vcs
     10 misc
     13 input
     14 sound
     21 sg
     29 fb
     81 video4linux
    116 alsa
    128 ptm
    136 pts
    171 ieee1394
    180 usb
    189 usb_device
    195 nvidia
    253 rtc
    254 usb_endpoint
    
    Block devices:
      2 fd
      7 loop
      8 sd
      9 md
     11 sr
     65 sd
     66 sd
     67 sd
     68 sd
     69 sd
     70 sd
     71 sd
    128 sd
    129 sd
    130 sd
    131 sd
    132 sd
    133 sd
    134 sd
    135 sd
    253 device-mapper
    254 mdp
    and here is lsusb and lspci as well:
    Code:
    linux:/proc # lsusb
    Bus 004 Device 001: ID 0000:0000
    Bus 003 Device 001: ID 0000:0000
    Bus 002 Device 001: ID 0000:0000
    Bus 001 Device 001: ID 0000:0000
    linux:/proc # lspci
    00:00.0 Host bridge: VIA Technologies, Inc. VT8377 [KT400/KT600 AGP] Host Bridge
    00:01.0 PCI bridge: VIA Technologies, Inc. VT8235 PCI Bridge
    00:05.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ (rev 10)
    00:07.0 Multimedia video controller: Brooktree Corporation Bt878 Video Capture (rev 11)
    00:07.1 Multimedia controller: Brooktree Corporation Bt878 Audio Capture (rev 11)
    00:08.0 FireWire (IEEE 1394): NEC Corporation uPD72874 IEEE1394 OHCI 1.1 3-port PHY-Link Ctrlr (rev 01)
    00:10.0 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 80)
    00:10.1 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 80)
    00:10.2 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 80)
    00:10.3 USB Controller: VIA Technologies, Inc. USB 2.0 (rev 82)
    00:11.0 ISA bridge: VIA Technologies, Inc. VT8235 ISA Bridge
    00:11.1 IDE interface: VIA Technologies, Inc. VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE (rev 06)
    00:11.5 Multimedia audio controller: VIA Technologies, Inc. VT8233/A/8235/8237 AC97 Audio Controller (rev 50)
    01:00.0 VGA compatible controller: nVidia Corporation NV34 [GeForce FX 5200] (rev a1)
    I don't know why it would work from the back usb ports but not the front if it was a driver, but if thats how to fix it i'll be glad to give it a try. uh how do i install a usb driver, which one, and from where?

  4. #4
    Linux Newbie dilbert's Avatar
    Join Date
    Sep 2006
    Location
    Yorkshire, GB
    Posts
    237
    Quote Originally Posted by robotics56a View Post
    I don't know why it would work from the back usb ports but not the front if it was a driver
    This hasn't been mentioned in the first posting. It was only mentioned that it works with Windows.

    Anyway, that are simple questions but that can become tedious if small details are overlooked. Starting with "/proc/bus/usb/devices". It was on all 2.4 and 2.6 kernels I've seen so far. It has to be enabled for sure, but all kernels I know do this by default.

    You need to know if the USB hotplug mechanism has read out the vendor and product ID for your device.

    Comparing lsusb and lspci shows that there are only the four USB hubs of your PC and nothing else.

    Try to insert, detach, and re-insert your device and look what the commands "dmesg" and "lsusb" do output.

    It is really all the same and I answered already here in this forum in a few threads the always same questions.

    The same goes for drivers if you really would need one.
    Bus Error: Passengers dumped. Hech gap yo'q.

  5. #5
    Linux Newbie
    Join Date
    Aug 2004
    Posts
    220
    Quote Originally Posted by dilbert View Post
    This hasn't been mentioned in the first posting.
    <looks at my post> yep. I forgot. I also forgot to say that I have 6 usb ports (4 back, which work, 2 front that do not)

    dmesg when pen drive plugged in back:
    Code:
     dmesg | tail
    sd 2:0:0:0: [sdc] Mode Sense: 23 00 00 00
    sd 2:0:0:0: [sdc] Assuming drive cache: write through
    sd 2:0:0:0: [sdc] 1001472 512-byte hardware sectors (513 MB)
    sd 2:0:0:0: [sdc] Write Protect is off
    sd 2:0:0:0: [sdc] Mode Sense: 23 00 00 00
    sd 2:0:0:0: [sdc] Assuming drive cache: write through
     sdc: sdc1
    sd 2:0:0:0: [sdc] Attached SCSI removable disk
    sd 2:0:0:0: Attached scsi generic sg3 type 0
    usb-storage: device scan complete
    and from the front:
    Code:
    dmesg | tail
    sd 2:0:0:0: [sdc] Attached SCSI removable disk
    sd 2:0:0:0: Attached scsi generic sg3 type 0
    usb-storage: device scan complete
    usb 3-1: USB disconnect, address 2
    usb 3-3: new high speed USB device using ehci_hcd and address 17
    usb 3-3: new high speed USB device using ehci_hcd and address 21
    usb 3-3: new high speed USB device using ehci_hcd and address 30
    usb 3-3: new high speed USB device using ehci_hcd and address 40
    usb 3-3: new high speed USB device using ehci_hcd and address 46
    usb 3-3: new high speed USB device using ehci_hcd and address 51
    it will continue to count up from there if you let it sit.

    I posted lsusb from front , here from the back:
    Code:
     lsusb
    Bus 004 Device 001: ID 0000:0000
    Bus 003 Device 022: ID 0930:6533 Toshiba Corp. 512M USB Stick
    Bus 003 Device 001: ID 0000:0000
    Bus 002 Device 001: ID 0000:0000
    Bus 001 Device 001: ID 0000:0000
    I searched your posts but didn't really know what to look for . Ya I'm that big a noob. Little help?
    Thanks a ton.

  6. #6
    Linux Newbie
    Join Date
    Aug 2004
    Posts
    220
    did some looking and acording to this site:
    https://lists.ubuntu.com/archives/ke...er/021822.html

    they did away with /proc/bus/usb/devices

    Code:
    dev/bus/usb has replaced /proc/bus/usb for the NNN/XXX devices, simply
    because the latter does not allow any kind of permission control other
    than at a filesystem level. ...
    
    ...Obviously this isn't a complete solution, as /dev/bus/usb does not
    contain a "devices" file with summary information...
    
    E.g. to obtain the descriptive name, vendor id and product id of every
    USB device (in shell):
    
      for DEVICE in /sys/bus/usb/devices/*; do
        [ -f $DEVICE/product ] && cat $DEVICE/product
        [ -f $DEVICE/idProduct ] && cat $DEVICE/idProduct
        [ -f $DEVICE/idVendor ] && cat $DEVICE/idVendor
      done
    so here is what I got (back then front):
    Code:
    for DEVICE in /sys/bus/usb/devices/*; do
    >     [ -f $DEVICE/product ] && cat $DEVICE/product
    >     [ -f $DEVICE/idProduct ] && cat $DEVICE/idProduct
    >     [ -f $DEVICE/idVendor ] && cat $DEVICE/idVendor
    >   done
    USB Flash Memory
    6533
    0930
    UHCI Host Controller
    0000
    0000
    UHCI Host Controller
    0000
    0000
    EHCI Host Controller
    0000
    0000
    UHCI Host Controller
    0000
    0000
    linux:/sys/bus/usb/devices> for DEVICE in /sys/bus/usb/devices/*; do     [ -f $DEVICE/product ] && cat $DEVICE/product;     [ -f $DEVICE/idProduct ] && cat $DEVICE/idProduct;     [ -f $DEVICE/idVendor ] && cat $DEVICE/idVendor;   done
    UHCI Host Controller
    0000
    0000
    UHCI Host Controller
    0000
    0000
    EHCI Host Controller
    0000
    0000
    UHCI Host Controller
    0000
    0000

  7. #7
    Linux Newbie dilbert's Avatar
    Join Date
    Sep 2006
    Location
    Yorkshire, GB
    Posts
    237
    Well, this is something I don't know and never have seen before.

    But from the last code block from your second post (i.e. "so here is what I got (back then front):") you see that it simply cannot detect any external device on the front sockets. Those UHCI (for 1.1) and EHCI (for 2.0) are simply the USB hubs behind those sockets that drive them.

    From the second code of the first posting (i.e. "and from the front:") we see that an external device provokes weird things instead.

    At least it has nothing to do with drivers or the like as it works fine on the rear sockets.

    I would say that if you cannot fix this by enabling something in the BIOS settings maybe then it's a hardware issue and the circuitry is broken somehow.
    Bus Error: Passengers dumped. Hech gap yo'q.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •