LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Linux - Laptop and Netbook (https://www.linuxquestions.org/questions/linux-laptop-and-netbook-25/)
-   -   USB stopped working (https://www.linuxquestions.org/questions/linux-laptop-and-netbook-25/usb-stopped-working-552858/)

vieraci 05-10-2007 07:16 AM
USB stopped working
 
I have openSuse 10.2 installed in an IBM T40 laptop.
USB suddenly stopped working and won't recognize anything I plug into it.
I don't know where to look for the problem. I know I installed a kernel update a week or 2 ago that came up on the openSuse updater, and I'm wondering if this broke it ?

Output from lsusb is:
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

Output from mount:
/dev/hda4 on / type ext3 (rw,acl,user_xattr)
proc on /proc type proc (rw)
sysfs on /sys type sysfs (rw)
debugfs on /sys/kernel/debug type debugfs (rw)
udev on /dev type tmpfs (rw)
devpts on /dev/pts type devpts (rw,mode=0620,gid=5)
securityfs on /sys/kernel/security type securityfs (rw)
none on /proc/sys/fs/binfmt_misc type binfmt_misc (rw)

leosgb 05-10-2007 11:15 PM
Try to dmesg before you plug your usb device and after. Compare the differences in the end of dmesg.

If your kernel can see it at all then you shall see it in dmesg. If it doenst display here you probably dont have usb enabled anymore, I suppose.

vieraci 05-11-2007 05:28 AM
hmmmm... is acting strange...
I did as you suggested, ran dmesg and couldn't find any obvious usb errors or problems.
Then plugged in a memory stick, and it came to life !
So I ran dmesg again and compared the output, the following appeared after the second dmesg:

usb 4-4: new high speed USB device using ehci_hcd and address 2
usb 4-4: new device found, idVendor=058f, idProduct=6387
usb 4-4: new device strings: Mfr=1, Product=2, SerialNumber=3
usb 4-4: Product: Mass Storage Device
usb 4-4: Manufacturer: JetFlash
usb 4-4: SerialNumber: YYP72JKK
usb 4-4: configuration #1 chosen from 1 choice
SCSI subsystem initialized
Initializing USB Mass Storage driver...
scsi0 : SCSI emulation for USB Mass Storage devices
usb-storage: device found at 2
usb-storage: waiting for device to settle before scanning
usbcore: registered new driver usb-storage
USB Mass Storage support registered.
Vendor: JetFlash Model: TS2GJF150 Rev: 8.07
Type: Direct-Access ANSI SCSI revision: 02
usb-storage: device scan complete
SCSI device sda: 4014080 512-byte hdwr sectors (2055 MB)
sda: Write Protect is off
sda: Mode Sense: 03 00 00 00
sda: assuming drive cache: write through
SCSI device sda: 4014080 512-byte hdwr sectors (2055 MB)
sda: Write Protect is off
sda: Mode Sense: 03 00 00 00
sda: assuming drive cache: write through
sda: sda1
sd 0:0:0:0: Attached scsi removable disk sda
sd 0:0:0:0: Attached scsi generic sg0 type 0

Then the light on the usb memory stick went out for no reason, and a dialog popped up stating "a new medium detected..." but the device dissapeared from the konqueror files list.

I removed the device, re-inserted it and it came good again !?

I ran dmesg again, and there appears a bunch of lines that seems to be some error message:

SFW2-OUT-ERROR IN= OUT=eth1 SRC=192.168.2.4 DST=72.14.253.93 LEN=52 TOS=0x00 PREC=0x00 TTL=64 ID=176 DF PROTO=TCP SPT=1046 DPT=80 WINDOW=407 RES=0x00 ACK FIN URGP=0 OPT (0101080A00FDE2C25B0BC33A)
SFW2-INext-DROP-DEFLT IN=eth1 OUT= MAC= SRC=192.168.2.4 DST=224.0.0.251 LEN=71 TOS=0x00 PREC=0x00 TTL=255 ID=0 DF PROTO=UDP SPT=5353 DPT=5353 LEN=51
SFW2-INext-DROP-DEFLT IN=eth1 OUT= MAC= SRC=192.168.2.4 DST=224.0.0.251 LEN=71 TOS=0x00 PREC=0x00 TTL=255 ID=0 DF PROTO=UDP SPT=5353 DPT=5353 LEN=51
SFW2-INext-DROP-DEFLT IN=eth1 OUT= MAC= SRC=192.168.2.4 DST=224.0.0.251 LEN=71 TOS=0x00 PREC=0x00 TTL=255 ID=0 DF PROTO=UDP SPT=5353 DPT=5353 LEN=51
SFW2-INext-DROP-DEFLT IN=eth1 OUT= MAC= SRC=192.168.2.4 DST=224.0.0.251 LEN=71 TOS=0x00 PREC=0x00 TTL=255 ID=0 DF PROTO=UDP SPT=5353 DPT=5353 LEN=51
SFW2-INext-DROP-DEFLT IN=eth1 OUT= MAC= SRC=192.168.2.4 DST=224.0.0.251 LEN=71 TOS=0x00 PREC=0x00 TTL=255 ID=0 DF PROTO=UDP SPT=5353 DPT=5353 LEN=51
SFW2-INext-DROP-DEFLT IN=eth1 OUT= MAC= SRC=192.168.2.4 DST=224.0.0.251 LEN=103 TOS=0x00 PREC=0x00 TTL=255 ID=0 DF PROTO=UDP SPT=5353 DPT=5353 LEN=83
SFW2-INext-DROP-DEFLT IN=eth1 OUT= MAC= SRC=192.168.2.4 DST=224.0.0.251 LEN=103 TOS=0x00 PREC=0x00 TTL=255 ID=0 DF PROTO=UDP SPT=5353 DPT=5353 LEN=83
SFW2-INext-DROP-DEFLT IN=eth1 OUT= MAC= SRC=192.168.2.4 DST=224.0.0.251 LEN=71 TOS=0x00 PREC=0x00 TTL=255 ID=0 DF PROTO=UDP SPT=5353 DPT=5353 LEN=51
SFW2-INext-DROP-DEFLT IN=eth1 OUT= MAC= SRC=192.168.2.4 DST=224.0.0.251 LEN=71 TOS=0x00 PREC=0x00 TTL=255 ID=0 DF PROTO=UDP SPT=5353 DPT=5353 LEN=51
SFW2-INext-DROP-DEFLT IN=eth1 OUT= MAC= SRC=192.168.2.4 DST=224.0.0.251 LEN=71 TOS=0x00 PREC=0x00 TTL=255 ID=0 DF PROTO=UDP SPT=5353 DPT=5353 LEN=51
SFW2-INext-DROP-DEFLT IN=eth1 OUT= MAC= SRC=192.168.2.4 DST=224.0.0.251 LEN=71 TOS=0x00 PREC=0x00 TTL=255 ID=0 DF PROTO=UDP SPT=5353 DPT=5353 LEN=51
SFW2-INext-DROP-DEFLT IN=eth1 OUT= MAC= SRC=192.168.2.4 DST=224.0.0.251 LEN=71 TOS=0x00 PREC=0x00 TTL=255 ID=0 DF PROTO=UDP SPT=5353 DPT=5353 LEN=51
SFW2-INext-DROP-DEFLT IN=eth1 OUT= MAC=00:04:23:87:36:c1:00:17:3f:68:3a:54:08:00 SRC=192.168.2.1 DST=192.168.2.4 LEN=78 TOS=0x00 PREC=0x00 TTL=64 ID=10648 PROTO=UDP SPT=44461 DPT=137 LEN=58
SFW2-INext-DROP-DEFLT IN=eth1 OUT= MAC=00:04:23:87:36:c1:00:17:3f:68:3a:54:08:00 SRC=192.168.2.1 DST=192.168.2.4 LEN=78 TOS=0x00 PREC=0x00 TTL=64 ID=10649 PROTO=UDP SPT=44461 DPT=137 LEN=58
SFW2-INext-DROP-DEFLT IN=eth1 OUT= MAC=00:04:23:87:36:c1:00:17:3f:68:3a:54:08:00 SRC=192.168.2.1 DST=192.168.2.4 LEN=78 TOS=0x00 PREC=0x00 TTL=64 ID=10650 PROTO=UDP SPT=44461 DPT=137 LEN=58
SFW2-INext-DROP-DEFLT IN=eth1 OUT= MAC=00:04:23:87:36:c1:00:17:3f:68:3a:54:08:00 SRC=192.168.2.1 DST=192.168.2.4 LEN=78 TOS=0x00 PREC=0x00 TTL=64 ID=10656 PROTO=UDP SPT=44462 DPT=137 LEN=58
SFW2-INext-DROP-DEFLT IN=eth1 OUT= MAC=00:04:23:87:36:c1:00:17:3f:68:3a:54:08:00 SRC=192.168.2.1 DST=192.168.2.4 LEN=78 TOS=0x00 PREC=0x00 TTL=64 ID=10657 PROTO=UDP SPT=44462 DPT=137 LEN=58
SFW2-INext-DROP-DEFLT IN=eth1 OUT= MAC=00:04:23:87:36:c1:00:17:3f:68:3a:54:08:00 SRC=192.168.2.1 DST=192.168.2.4 LEN=78 TOS=0x00 PREC=0x00 TTL=64 ID=10658 PROTO=UDP SPT=44462 DPT=137 LEN=58
SFW2-INext-DROP-DEFLT IN=eth1 OUT= MAC=00:04:23:87:36:c1:00:17:3f:68:3a:54:08:00 SRC=192.168.2.1 DST=192.168.2.4 LEN=78 TOS=0x00 PREC=0x00 TTL=64 ID=10664 PROTO=UDP SPT=44463 DPT=137 LEN=58
SFW2-INext-DROP-DEFLT IN=eth1 OUT= MAC=00:04:23:87:36:c1:00:17:3f:68:3a:54:08:00 SRC=192.168.2.1 DST=192.168.2.4 LEN=78 TOS=0x00 PREC=0x00 TTL=64 ID=10666 PROTO=UDP SPT=44463 DPT=137 LEN=58
SFW2-INext-DROP-DEFLT IN=eth1 OUT= MAC= SRC=192.168.2.4 DST=224.0.0.251 LEN=71 TOS=0x00 PREC=0x00 TTL=255 ID=0 DF PROTO=UDP SPT=5353 DPT=5353 LEN=51
SFW2-INext-DROP-DEFLT IN=eth1 OUT= MAC= SRC=192.168.2.4 DST=224.0.0.251 LEN=71 TOS=0x00 PREC=0x00 TTL=255 ID=0 DF PROTO=UDP SPT=5353 DPT=5353 LEN=51
SFW2-INext-DROP-DEFLT IN=eth1 OUT= MAC= SRC=192.168.2.4 DST=224.0.0.251 LEN=71 TOS=0x00 PREC=0x00 TTL=255 ID=0 DF PROTO=UDP SPT=5353 DPT=5353 LEN=51
SFW2-INext-DROP-DEFLT IN=eth1 OUT= MAC= SRC=192.168.2.4 DST=224.0.0.251 LEN=71 TOS=0x00 PREC=0x00 TTL=255 ID=0 DF PROTO=UDP SPT=5353 DPT=5353 LEN=51
SFW2-INext-DROP-DEFLT IN=eth1 OUT= MAC= SRC=192.168.2.4 DST=224.0.0.251 LEN=71 TOS=0x00 PREC=0x00 TTL=255 ID=0 DF PROTO=UDP SPT=5353 DPT=5353 LEN=51

What does this mean ?

leosgb 05-11-2007 03:31 PM
Ok, lets try to get to the bottom of this.

could you use your usb stick?

what did lsusb return?

well you might have a problem in your usb controller if it ejects the device or you can have a driver problem too. It can even be your automounter that is acting up.

so lets run lsusb again and check the output. Make sure you run it while the light is on and, if the light goes off you run it too so we can compare it.

In any case you can get where it is mounted from dmesg: "sda: sda1"

So you can go ahead and run "mount" and check if /dev/sda1 is presented there.

If not, and the light is OFF, you can try to mount it with:
mount /dev/sda1 /mnt/some_name_here_for_usb_folder -- does it mount?

then you can browse it as a regular folder: cd /mnt/some_name_here_for_usb_folder.

Can you "ls" in it? --if so then we are good to go. You probably have an automounter problem. If not... then we will have to find out what happened.

Post back the lsusb and dmesg with light ON and OFF. Try to mount it if the light is off. And try to read the files from it once the light is on.

vieraci 05-12-2007 03:09 AM
OK, It appears that it's a hardware problem.
I have 2 identical laptops, and another HDD that has suse installed as well.
I changed HDD's and the problem is still there.
Thanks for your help,


All times are GMT -5. The time now is 03:41 PM.