7th September 18:17
I'm (still) running a 2.4 kernel on my primary computer (trying to figure
how to safely upgrade to 2.6) and all of a sudden now NO USB devices work.
My Asus A7V8X-X motherboard has usb 2.0 on it (don't know if it is a 'high
power' connection though). I was able to talk to my Epson USB inkjet
printer and plug my digital camera and usb flash drive in as well to
download files. Now nothing works. Nothing shows up
in /proc/bus/usb/devices either (or is this only a 2.6/udev thing?).
I think it all started when I tried plugging my new iPod into the usb on the
computer. Is it possible that plugging in a high power usb device could
blow up the interface?
The iPod works fine on a windows XP machine, and on
another linux box with a high power usb pci card under kernel 2.6.11 (with
some weirdness though). (The other machine is not my primary computer, I
built it to record and rip cd's, and run mythtv.) I could go to the
ratshack and get another pci usb2.0 card to 'replace' the motherboard usb
controller, but first maybe I'll upgrade the kernel and use udev (which
works on the other linux box). Sure wish I knew for sure if I have a hw or
The linux box that works with the ipod has some weirdness. I set up a udev
rule to create an /dev/ipod simlink to /dev/sdaN. It mostly shows up
as /dev/sda1, but sometimes as /dev/sda2! (fat formated ipod). Also if
after syncing the ipod with gtkpod I umount /dev/ipod and then
eject /dev/ipod, the eject command issues an error, but the ipod DOES
disconnect and the 'NO' glyph disapears to be replaced with the main menu
screen. (ipod mini). I can't reconnect the ipod to the commputer from the
same usb socket, but a DIFFERENT one works! Also even though my /etc/fstab
line for the ipod has the 'noauto' modifier, most of the time (first time
mouting after booting the computer) it WILL automount on plugin.
enough rant. Anybody been there before with any of this?
7th September 18:17
Did you compile the usb support into or as modules?
Did you disable the usage of tarball in /etc/conf.d/rc ?
If the interface is already broken, I guess it could be possible.
Compare the kernel .config with the two kernels and see what you missed to enable.
This is usually the case when you already have mounted another usb mass
storage device or have a SCSI interface.
Don't think the eject was made to unmount devices that can't be ejected, I
would try to just unmount the device (from the desktop icon or from an terminal).
The unmount didn't go well and the device is still in the mtab, you need to
force an unmount on the device. Disable the automount feature in the kernel.