On Sun, 8 Aug 2004, Dominik Karall wrote: > > It's possible that when your EHCI driver was loaded, it interfered with > > other devices already being managed by the OHCI driver. There are other > > possibilities too, however. It would be easier to tell what happened if > > you turned on usb-storage verbose debugging in your kernel configuration.
> @Alan > here is the full syslog output with 2.6.8-rc3-mm1 (usb debug enabled). > i'm using /dev/sda1 for the cf reader, but it tells me, that it isn't a block > orientated device. You didn't have usb-storage debugging turned on, so I can't be sure about this. It still looks as though everything worked okay. The reader was detected, then the EHCI driver took over the port from the OHCI driver, then it gave the port back and the reader was detected again, all as it should be. If the reader isn't showing up as /dev/sda maybe it's because you don't have the sd_mod driver loaded. Or maybe you're trying to use /dev/sda1 when you should be using /dev/sda. Alan Stern ------------------------------------------------------- This SF.Net email is sponsored by OSTG. Have you noticed the changes on Linux.com, ITManagersJournal and NewsForge in the past few weeks? Now, one more big change to announce. We are now OSTG- Open Source Technology Group. Come see the changes on the new OSTG site. www.ostg.com _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
