[Jaunty] USB Devices wont recognised on startup

Bug #348049 reported by Sven K.
46
This bug affects 6 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Won't Fix
Undecided
Unassigned

Bug Description

I figure out that some USB external storage devices (and my printer so far), not always recognised via usb.
My WD MyBook only be discovered and mounted successfully, if the system is fully loaded and running. But if i restart the system with device plugged in, the external Harddisk wouldnt discovered and mounted after boot.

Only if i unplug the device and plug it in again, the devices works fine so far.

Same bug belongs to my printer (Canon IP3600), which work fine under Intrepid.

uname -a: Linux Linux-x64 2.6.28-11-generic #37-Ubuntu SMP Mon Mar 23 16:40:00 UTC 2009 x86_64 GNU/Linux
Jaunty (newest updates so far)
Hardware: MSI DKA-790GX (SB750)
AMD X2 6000+
4GB Ram
ATi 3870 - fglrx

For lspci and dmesg log reports, look a few posts below...

Sven K. (sven.k)
description: updated
Revision history for this message
Brian Murray (brian-murray) wrote : Package assigned

Thank you for taking the time to report this bug and helping to make Ubuntu better. This bug did not have a package associated with it, which is important for ensuring that it gets looked at by the proper developers. You can learn more about finding the right package at https://wiki.ubuntu.com/Bugs/FindRightPackage. I have classified this bug as a bug in linux.

Revision history for this message
Brian Murray (brian-murray) wrote : Need more information

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' 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!

Revision history for this message
Duckie (duckielucky) wrote :

I can only confirm the bug.
I am using a usb Western Digital 1GB MyBook and the first boot after a fresh install it was perfectly recognized en mounted. After a reboot I can only get it working by unplug and again plug it in.

uname -a:
Linux athlon 2.6.28-11-generic #37-Ubuntu SMP Mon Mar 23 16:40:00 UTC 2009 x86_64 GNU/Linux

Revision history for this message
Duckie (duckielucky) wrote :

And here is the dmesg.log.
Sorry for the two posts, I couldn't find out how to add two attachments.

Revision history for this message
Sven K. (sven.k) wrote :

Thanks Brian

and sorry for the rarely informations - its my first bugreport.

uname -a gives:
Linux Linux-x64 2.6.28-11-generic #37-Ubuntu SMP Mon Mar 23 16:40:00 UTC 2009 x86_64 GNU/Linux

The dmesg.log is in the attachement of this post.

Revision history for this message
Sven K. (sven.k) wrote :

and the lspci-vnn.log :)

Couldnt find to add two attachements in one post too, sorry

Revision history for this message
Duckie (duckielucky) wrote :

And sorry again. I'm sure it would be possible to change a post, but I really can't find it.
In my first post I said I have a 1 GB MyBook, that must be 1000 GB.

Sven K. (sven.k)
description: updated
Revision history for this message
Duckie (duckielucky) wrote :

I don't know if this helps but I just found out that when I switch on te printer (Epson DX5000) Jaunty mounts the MyBook.
When I switch the printer off the MyBook stays mounted. Til a reboot, that is.

Revision history for this message
Sven K. (sven.k) wrote :

Hehe, funny... Ducky, youre right - here too...
Dont noticed that till now :-)

Sven K. (sven.k)
description: updated
Sven K. (sven.k)
Changed in linux:
status: Incomplete → Confirmed
Revision history for this message
bj mccormick (bjmccormick) wrote :

Would also like to confirm. Plugging in USB stick initializes all my usb devices.

uname -a
Linux bj-desktop 2.6.28-11-generic #41-Ubuntu SMP Wed Apr 8 04:39:23 UTC 2009 x86_64 GNU/Linux

Revision history for this message
ebi (33454-web) wrote :

I can confirm the same problem here.

uname -a:
Linux 2.6.28-11-generic #42-Ubuntu SMP Fri Apr 17 01:57:59 UTC 2009 i686 GNU/Linux

lshw:
...
*-usb:0
             description: USB Controller
             product: SB700/SB800 USB OHCI0 Controller
             vendor: ATI Technologies Inc
             physical id: 12
             bus info: pci@0000:00:12.0
             version: 00
             width: 32 bits
             clock: 66MHz
             capabilities: bus_master
             configuration: driver=ohci_hcd latency=32
...

Devices appear in lspci but no /dev/sd* is created. Plugging one device brings up the others too.

Had hardy and intrepid on the same configuration without the problem.

Is there any way to restart/rescan the usb with a shell command or script?

Revision history for this message
ebi (33454-web) wrote :

# modprobe usb_storage
brings up the devices.

Revision history for this message
Sven K. (sven.k) wrote :

Till now, no changes so far :(
The bug still exists here too. But, thanks for the "modprobe..." way, i dont have try'd this till now, my devices comes up too...

Revision history for this message
Steve Krekeler (skrekeler) wrote :

Similar problem here. Had 8.10 installed and working on ext USB HD, and now, after upgrade to 9.04 / 2.6.28-11-generic, it will no longer boot from ext USB drive unless I drop back to the 2.6.27-11-generic kernel.

Tried a fresh install to ext drive from 9.04 live CD, but external USB drive not seen after boot from CD. If I unplug/replug the ext USB drive, it sees it and installs to it, but then crashes at first boot:

[ 2.340041] ata1: softreset failed (device not ready)
modprobe: FATAL: Could not load /lib/modules/2.6.28-11-generic/modules.dep: No such file or directory.
Gave up waiting for root device.
...

Revision history for this message
maccus (maccus) wrote :

Same issue here. USB stick is invisible except after replugging the stick of turning on a USB-printer or plugging in any other USB-device. Annoying. Fixed it by putting a line "usb_storage" in "/etc/modules" and reboot.

Revision history for this message
Neil Hollow (hollowfamily) wrote :

I have the opposite problem. I have to plug usb devices in before boot otherwise they are not recognised for example mouse and Ipod

sudo modprobe usb_storage

got the ipod recognised and allowed me to put U2 on it.

If I do lsusb

x:~$ lsusb
Bus 001 Device 003: ID 05ac:1262 Apple, Inc.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 002: ID 1241:1111 Belkin Mouse
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub

it sees it same with the mouse but it isn't usable.

uname -r

2.6.28-13-generic

Neil

Revision history for this message
Mediaklan (didli) wrote :

"My WD MyBook only be discovered and mounted successfully, if the system is fully loaded and running. But if i restart the system with device plugged in, the external Harddisk wouldnt discovered and mounted after boot."
Same problem here with same hdd, getting worse since last gvfs update (but I don't know if it is currently related). Doesn't try yet to switch my printer off or modprobe usb_storage.

Revision history for this message
Andre LeBlanc (andrepleblanc) wrote :

I have the same issue, but its not related to storage at all, my usb wireless keyboard reciever and IR Remote Reciever both stop working after rebooting, making the task of turning off my media center completely not worth it. this is right up there among the most annoying bugs I've ever been stricken with.

Revision history for this message
corevalue (corevalue-uk) wrote :

Worst bug I've ever had. Got to wipe system and go back to 8.04.

(1) Couldn't boot from live CD unless USB cd-rom unplugged and plugged back during Kubuntu splash screen.

(2) Pinnacle72e USB DVB stick always found (in dmesg as "found in a warm state"...) but application (Kaffeine) only uses it correctly if plugged in AFTER boot. If plugged in before boot, Kaffeine "sees" the device and it is identified correctly, but control is incorrect and no channels found.

(3) No memory sticks found in Dolphin (but reported in dmesg) if plugged in before boot, but correctly mounted if plugged in AFTER boot.

(4) USB speakers promptly stop working in the application (VLC) if a memory stick plugged in, but still work OK if run from the system settings test panel. Unplugging and replugging brings a second USB speaker device up on the system settings, but still won't work with an application.

(5) USB cd-rom not mounted in Dolphin if plugged in before boot, but mounted correctly if plugged in later - except that stops the speakers so you can't play a CD!

The other USB device is a wireless trust keyboard, which works flawlessly.

Revision history for this message
Alejandro Vidal (mancvso) wrote :

Is this update still being offered??

can I upgrade my fresh jaunty install without beign affecyed by this bug??

Revision history for this message
Sven K. (sven.k) wrote :

Dont know... Id make an fresh Karmic install in the last days. There everything works fine so far.

Revision history for this message
Duckie (duckielucky) wrote :

I did a reïnstall of Jaunty a few weeks ago and it looks like this bug is solved.

Revision history for this message
Brad Figg (brad-figg) wrote : Unsupported series, setting status to "Won't Fix".

This bug was filed against a series that is no longer supported and so is being marked as Won't Fix. If this issue still exists in a supported series, please file a new bug.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

Changed in linux (Ubuntu):
status: Confirmed → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.