usb storage devices

Steven P. Ulrick ulrick2 at faith4miracle.org
Thu Feb 17 06:10:35 UTC 2005


On Wednesday 16 February 2005 10:10 pm, Ankush Grover wrote:
> hey,
>
> did you update usbutilits and udev rpms also.For the problem you are
> facing i will definitely look for some solution.
>
> Regards
>
> Ankush

Hello, Donald :)
I had EXACTLY the same thing happen to me.  Anksuh advised me to update those 
items just like he suggested to you.  Like you, I had all the stable updates 
installed.  But, I had gotten so tired of rebooting to get rid of zombie 
processes, and get full functionality back on our USB2 devices, that I 
thought I would update those RPM's from Rawhide.  Guess what?  My devices 
have not dissappeared since!  All is now well here :)
I even tried an experiment: I plugged our scanner into one of our six USB2 
ports, and scanned a 600dpi image.  No problem.  I unplugged it and 
IMMEDIATELY replugged it into another USB2 port and scanned the same image at 
the same dpi. Again, success.  I repeated this test four times, four 
different ports, no problems.  Most of the time my devices would dissappear, 
but I also experienced functionality issues with our two devices.  Now I have 
even burned quite a few cd's over a week or so, and all is well!
I would update the RPM's (from Rawhide) that Ankush said to update.  I will 
tell you all of the ones that I updated, but try what he said first, and see 
how things go:
I updated:
	hotplug
	usbutils
	udev
	kernel
	initscripts (I thought I would update that as well, since I would be running 
FC3 with a Rawhide kernel.  Our system booted fine Without updating 
initscripts, but on the other hand, it has been running beautifully ever 
since, With initscripts from Rawhide.  YMMV.)

Our uptime looks like this:
 00:02:40 up 5 days, 16:57,  4 users,  load average: 2.87, 2.40, 1.40
That is a big deal for me, because I had to reboot every time that full 
functionality was not restored after plugging a device in a different port.  
I did reboot everytime that a zombie process got started because of running a 
command related to a device that had dissappeared, but of course, all of that 
is in the past now.
Also, check out my message to this list on this same thread, that I sent after 
everything started working perfectly again:
https://www.redhat.com/archives/fedora-list/2005-February/msg03565.html

Have a Great Day,
Steven P. Ulrick




More information about the fedora-list mailing list