no auto-mount for USB-stick through USB-hub

[Rhanh-BKK]

Hi.

I updated my Ubuntu today, from kernel 2.6.24-16-generic to the latest 2.6.24-21-generic. Now i can no longer auto-mount USB-sticks (thumb drives) by connecting them to an external 4-port USB hub.

When i connect the USB-stick directly to a MoBo USB port, it auto-mounts fine.

When plugged into the hub and i do a "lsusb", the stick does NOT show up, however immediately after issuing that command the stick will auto-mount (and show up correctly when i do the "lsusb" a second time)!

Tried with varying amounts of time between inserting the stick and issuing the command to see if it will eventually mount after some time, but up to 14 minutes no reaction at all, and after issuing "lsusb" it immediately mounts.

Another user on Ubuntu-forums experienced the identical problem on a laptop, mine is a desktop.

Machine: Asus K8N4-E SE, AMD Sempron 2800+, 2x1 GB Kingston RAM, Nvidia graphics. USB devices connected: Printer HP all-in-one, mouse Logitech, external memory card reader, IrDA dongle, 4-port hub. All work fine except for any device that will be connected to the hub (tested several USB-sticks) except when doing "lsusb".

Ubuntu-version: 8.04.1 Hardy Heron
Kernel: 2.6.24-21-generic 32 bit

if you need further information, please explain to me how i can obtain it as i am still quite a newbie to Linux.

Kind regards.....

Thanh

[David D Short (chameleondave)]

This bug is being discussed at http://ubuntuforums.org/showthread.php?t=950214

It would be good if someone good ascertain whether the bug is affecting other distros.

[David D Short (chameleondave)]

*could

[Rhanh-BKK (boythanh)]

Hi.

Yeah that's my thread there - i did a typo when signing up here, should be "Thanh-BKK" instead of "Rhanh-BKK".

I just confirmed it's a kernel bug because when i boot into the older kernel, the auto-mount still works for USB-sticks in the hub, it's only the new kernel where it does not work.

Best regards...

Thanh

[Rhanh-BKK (boythanh)]

Hi.

A new finding: This but seems to apply only to USB 2.0 hubs! Because yesterday i purchased a new one, and when at the office and testing it (i got two, one for me and one for the office) i figured out it's a USB 1.1 hub - Windows told me so (Linux doesn't mention tat!)

HOWEVER once at home, connected it instead of the old one to my Linux box - and USB sticks mount fine on it!!

However the speed with which data is transferred is a disgrace. Reading at 900 KILObytes/second, writing at 1 Megabyte/second.

So for now i can narrow this down to a problem that the 2.6.24-21-generic has with USB 2.0 hubs.

Best regards.....

Thanh

[Ezra Morris (ezramorris)]

My bug report <may> be slightly relevant. https://bugs.launchpad.net/ubuntu/+source/linux/+bug/285485

It concerns USB problems with a webcam and printer. They are USB, and the problem occurred after upgrading to the 2.6.24-21-generic kernel.

[bubbalouie (ryan-gossink)]

I have a similar problem, since the update none of my thumb drives work, with or without a hub, I literally need to mount the drives manually (i.e. mount -t vfat /dev/sdc1 /media/bah). I have the problem on both the 64 & 32 bit versions.

[Ian Weisser (ian-weisser)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately we can't fix it without more information.

Please include the following additional information, if you have not already done so (pay attention to lspci's additional options), as required by the Ubuntu Kernel Team:
1. Please include the output of the command "uname -a" in your next response. It should be one, long line of text which includes the exact kernel version you're running, as well as the CPU architecture.
2. Please run the command "dmesg > dmesg.log" after a fresh boot and attach the resulting file "dmesg.log" to this bug report.
3. Please run the command "sudo lspci -vvnn > lspci-vvnn.log" and attach the resulting file "lspci-vvnn.log" to this bug report.

For your reference, the full description of procedures for kernel-related bug reports is available at https://wiki.ubuntu.com/KernelTeamBugPolicies Thanks in advance!

[Rhanh-BKK (boythanh)]

Hi :)

Here's uname -a:

Linux thanh-desktop 2.6.24-21-generic #1 SMP Mon Aug 25 17:32:09 UTC 2008 i686 GNU/Linux

I did the other two as well but where could i find the log files??

Regards....

Thanh

[Rhanh-BKK (boythanh)]

Ok found them, i will attach the two log files here.

Kind regards....

Thanh

[Rhanh-BKK (boythanh)]

and the other one

[Lars Westerhoff (lwhoff)]

Hi,

same problems here. KUbuntu 8.04.1 and a 2-port-hub (part of LCD screen) causing the problems. As soon as an lsusb is issued plugged devices get being detected. This is not limited to USB Mass Storage devices. A PTP Fuji digital camera is also affected.

I have also a mainboard with an NVIDIA chipset, although not the same (lspci to come in next post)

uname -a:
Linux hawking 2.6.24-22-generic #1 SMP Mon Nov 24 18:32:42 UTC 2008 i686 GNU/Linux

[Lars Westerhoff (lwhoff)]

As USB is affected, also the lsusb

[Lars Westerhoff (lwhoff)]

As you see, the camera is not detected, but immediately after this lsusb is issued the camera will be discovered.

[Lars Westerhoff (lwhoff)]

This one is take about 3 seconds after the previous one. As you see, now the camera is there.

Hope that helps.

[rodrigo (rodrigo-natalizi)]

Exactly the same problem to me. After upgrade from kernel 2.6.24-19 to 2.6.24-22, I have no usb device detected in my four ports hub. After "lsusb", the devices start to be detected.
Kubuntu 8.04.1, 32 bits, Intel Pentium IV processor.

Attachmento: dmesg.log
Next I will include the other ones.

[rodrigo (rodrigo-natalizi)]

Attachment: lspci-vvnn.log

[rodrigo (rodrigo-natalizi)]

Attachment: uname-a.log

[rodrigo (rodrigo-natalizi)]

And attachment: version.log

End!

Thanks.

[DaveM (davidmartin-ntlworld)]

I have an identical issue as the op, although I am running Kubuntu 8.04. My setup is quite similar to the op's - Sempron 3200+ on an Asus K7N2 mobo with NVidea graphics.

Since the kernel update to 2.6.24-22-generic in my case, I either have to plug USB devices into the hub before booting, or else "sudo lsusb" to get them automounted. The printer is plugged into the hub, and I use it for thumbdrives etc. Here's the output from lsusb with printer switched on and a thumbdrive plugged in (and mounted, after I did lsusb):

Bus 007 Device 001: ID 0000:0000
Bus 006 Device 001: ID 0000:0000
Bus 005 Device 001: ID 0000:0000
Bus 004 Device 005: ID 04a9:10a2 Canon, Inc.
Bus 004 Device 004: ID 0781:5406 SanDisk Corp. Cruzer Micro 4GB Flash Drive
Bus 004 Device 003: ID 05e3:0606 Genesys Logic, Inc. D-Link DUB-H4 USB 2.0 Hub
Bus 004 Device 001: ID 0000:0000
Bus 003 Device 001: ID 0000:0000
Bus 002 Device 001: ID 0000:0000
Bus 001 Device 003: ID 041e:401e Creative Technology, Ltd WebCam NX Pro
Bus 001 Device 001: ID 0000:0000

The webcam is plugged into a port on the motherboard (it only has 2 ports, hence my use of the hub).

uname -a gives:

Linux ourbox 2.6.24-22-generic #1 SMP Mon Nov 24 18:32:42 UTC 2008 i686 GNU/Linux

I have attached dmesg output and the other outputs requested. Towards the end of dmesg can be seen where I plugged in the thumbdrive and did lsusb. Then I switched on the printer and did lsusb again.

I hope this helps resolve some other people's issues...just received a new Gigabyte GA-MA78GM-S2H mobo with Athlon X2 4850e. Will no longer need the hub since this new kit has plenty of ports on it.

[DaveM (davidmartin-ntlworld)]

And dmesg

[DaveM (davidmartin-ntlworld)]

By the way I have an old USB 1.0 PCI card with 4 ports on it, which I never use (too slow for anything nowadays). Hence it looks like I have a lot more than 2 ports plus the hub.

[pezcurrel (pezcurrel)]

Same behaviour here.
Anyway I noticed that if I connect a second stick while there is a first stick connected and already recognized by doing "lsusb", the second stick won't need lsusb (ie it will be recognized as soon as it is plugged in - normal beahviour).

uname -a
Linux xxxxx 2.6.24-23-generic #1 SMP Mon Jan 26 00:13:11 UTC 2009 i686 GNU/Linux

lsusb
Bus 004 Device 003: ID 05e3:0608 Genesys Logic, Inc. USB-2.0 4-Port HUB
Bus 004 Device 001: ID 0000:0000
Bus 003 Device 001: ID 0000:0000
Bus 002 Device 001: ID 0000:0000
Bus 001 Device 002: ID 13ee:0003
Bus 001 Device 001: ID 0000:0000
(with nothing plugged into the usb hub)

lspci
00:00.0 Host bridge: Intel Corporation 82865G/PE/P DRAM Controller/Host-Hub Interface (rev 02)
00:01.0 PCI bridge: Intel Corporation 82865G/PE/P PCI to AGP Controller (rev 02)
00:1d.0 USB Controller: Intel Corporation 82801EB/ER (ICH5/ICH5R) USB UHCI Controller #1 (rev 02)
00:1d.1 USB Controller: Intel Corporation 82801EB/ER (ICH5/ICH5R) USB UHCI Controller #2 (rev 02)
00:1d.2 USB Controller: Intel Corporation 82801EB/ER (ICH5/ICH5R) USB UHCI Controller #3 (rev 02)
00:1d.7 USB Controller: Intel Corporation 82801EB/ER (ICH5/ICH5R) USB2 EHCI Controller (rev 02)
00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev c2)
00:1f.0 ISA bridge: Intel Corporation 82801EB/ER (ICH5/ICH5R) LPC Interface Bridge (rev 02)
00:1f.1 IDE interface: Intel Corporation 82801EB/ER (ICH5/ICH5R) IDE Controller (rev 02)
00:1f.5 Multimedia audio controller: Intel Corporation 82801EB/ER (ICH5/ICH5R) AC'97 Audio Controller (rev 02)
00:1f.6 Modem: Intel Corporation 82801EB/ER (ICH5/ICH5R) AC'97 Modem Controller (rev 02)
01:00.0 VGA compatible controller: nVidia Corporation NV34M [GeForce FX Go5200 64M] (rev a1)
02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ (rev 10)
02:01.0 CardBus bridge: ENE Technology Inc CB-710/2/4 Cardbus Controller (rev 02)
02:01.1 FLASH memory: ENE Technology Inc CB710 Memory Card Reader Controller
02:02.0 FireWire (IEEE 1394): Texas Instruments TSB43AB21 IEEE-1394a-2000 Controller (PHY/Link)
02:03.0 Network controller: Broadcom Corporation BCM4306 802.11b/g Wireless LAN Controller (rev 03

[Kal Zarius (kalzarius)]

Same behaviour, newer kernel. Apacer 2GB flash drive in a 7-port HUB.

uname -a
Linux xxxx 2.6.24-24-generic #1 SMP Tue Jun 30 20:28:53 UTC 2009 i686 GNU/Linux

lsusb
Bus 005 Device 003: ID 05e3:0608 Genesys Logic, Inc. USB-2.0 4-Port HUB
Bus 005 Device 002: ID 05e3:0608 Genesys Logic, Inc. USB-2.0 4-Port HUB
Bus 005 Device 001: ID 0000:0000
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

lspci
00:00.0 Host bridge: VIA Technologies, Inc. VT8363/8365 [KT133/KM133] (rev 03)
00:01.0 PCI bridge: VIA Technologies, Inc. VT8363/8365 [KT133/KM133 AGP]
00:04.0 ISA bridge: VIA Technologies, Inc. VT82C686 [Apollo Super South] (rev 40)
00:04.1 IDE interface: VIA Technologies, Inc. VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE (rev 06)
00:04.2 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 16)
00:04.3 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 16)
00:04.4 Bridge: VIA Technologies, Inc. VT82C686 [Apollo Super ACPI] (rev 40)
00:0a.0 Multimedia audio controller: Creative Labs SB Live! EMU10k1 (rev 08)
00:0a.1 Input device controller: Creative Labs SB Live! Game Port (rev 08)
00:0b.0 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 62)
00:0b.1 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 62)
00:0b.2 USB Controller: VIA Technologies, Inc. USB 2.0 (rev 65)
00:0d.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8029(AS)
00:11.0 Mass storage controller: Promise Technology, Inc. PDC20265 (FastTrak100 Lite/Ultra100) (rev 02)
01:00.0 VGA compatible controller: nVidia Corporation NV20 [GeForce3 Ti 200] (rev a3)

After plugging USB Drive in:

lsusb
Bus 005 Device 003: ID 05e3:0608 Genesys Logic, Inc. USB-2.0 4-Port HUB
Bus 005 Device 002: ID 05e3:0608 Genesys Logic, Inc. USB-2.0 4-Port HUB
Bus 005 Device 001: ID 0000:0000
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

lsusb
Bus 005 Device 004: ID 1005:b113 Apacer Technology, Inc. Handy Steno 2.0 (256MB)
Bus 005 Device 003: ID 05e3:0608 Genesys Logic, Inc. USB-2.0 4-Port HUB
Bus 005 Device 002: ID 05e3:0608 Genesys Logic, Inc. USB-2.0 4-Port HUB
Bus 005 Device 001: ID 0000:0000
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

[kernel-janitor (kernel-janitor)]

Hi Rhanh-BKK,

Please be sure to confirm this issue exists with the latest development release of Ubuntu. ISO CD images are available from http://cdimage.ubuntu.com/releases/karmic . If the issue remains, please run the following command from a Terminal (Applications->Accessories->Terminal). It will automatically gather and attach updated debug information to this report.

apport-collect -p linux 285006

Also, if you could test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text. Please let us know your results.

Thanks in advance.

[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

[Mathias (mathias-anlander)]

Architecture: i386
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC1: mathias 2623 F.... pulseaudio
 /dev/snd/controlC0: mathias 2623 F.... pulseaudio
CRDA: Error: [Errno 2] Filen eller katalogen finns inte
Card0.Amixer.info:
 Card hw:0 'XFi'/'Creative X-Fi 20K1 Unknown'
   Mixer name : '20K1'
   Components : ''
   Controls : 30
   Simple ctrls : 11
Card1.Amixer.info:
 Card hw:1 'Intel'/'HDA Intel at 0xf2100000 irq 22'
   Mixer name : 'Realtek ALC889A'
   Components : 'HDA:10ec0885,1458a002,00100101'
   Controls : 43
   Simple ctrls : 24
DistroRelease: Ubuntu 9.10
HibernationDevice: RESUME=UUID=3c0782db-a1d9-42ff-9906-19f706eff8bc
MachineType: Gigabyte Technology Co., Ltd. EP35-DS3
NonfreeKernelModules: nvidia
Package: linux (not installed)
ProcCmdLine: root=UUID=9c8c7e60-dbcc-4724-9c0a-913ba59338b3 ro quiet splash
ProcEnviron:
 SHELL=/bin/bash
 PATH=(custom, user)
 LANG=sv_SE.UTF-8
ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
RelatedPackageVersions:
 linux-backports-modules-2.6.31-14-generic N/A
 linux-firmware 1.24
RfKill:
 0: hci0: Bluetooth
  Soft blocked: no
  Hard blocked: no
Uname: Linux 2.6.31-14-generic i686
UserGroups: adm admin audio cdrom dialout dip floppy fuse lpadmin plugdev sambashare users video
WpaSupplicantLog:

dmi.bios.date: 01/04/2008
dmi.bios.vendor: Award Software International, Inc.
dmi.bios.version: F2
dmi.board.name: EP35-DS3
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.type: 3
dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF2:bd01/04/2008:svnGigabyteTechnologyCo.,Ltd.:pnEP35-DS3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnEP35-DS3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
dmi.product.name: EP35-DS3
dmi.sys.vendor: Gigabyte Technology Co., Ltd.

[Mathias (mathias-anlander)]

I have the same problem so I did the apport-collect thing, I hope that was OK!

[penalvch (penalvch)]

Rhanh-BKK, thank you for reporting this and helping make Ubuntu better. Hardy desktop reached EOL on May 12, 2011.
Please see this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases

We were wondering if this is still an issue on a supported release? If so, can you try with the latest development release of Ubuntu? ISO CD images are available from http://cdimage.ubuntu.com/releases/ .

If it remains an issue, could you run the following command in a supported release from a Terminal (Applications->Accessories->Terminal). It will automatically gather and attach updated debug information to this report.

apport-collect -p linux <replace-with-bug-number>

Also, if you could test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text. Please let us know your results.

Thanks in advance.

[Launchpad Janitor (janitor)]

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]