On Thu, 4 Mar 2004 [EMAIL PROTECTED] wrote: > I have had no problems with the old uhci driver working with my laptop > (From the 2.4 kernel), but the 2.6 uhci (je) driver does not seem to work. > The JE driver which I assume is the same driver from the 2.4 series which > does not work either. I attached the lspci -vvv from the old working > driver (uhci, ehci 2.4.22). I also added the dmesg output from my computer > as well. If you want I can send you an output from the non working one. (I > have to compile 2.6.3 kernel again to get you an output) I noticed the > only difference is the old driver. I noticed that the old uhci driver > seems to automatically assign IRQ 6 when the JE driver will assign IRQ 0. > I don't know if it is hard coded? (I don't have a floppy drive even though > it tries to use IRQ 6 for that) I tried all of the bios setting changes > described on the internet and it does not work. I know VIA chipsets have a > lot of bugs anyhow. Is there somewhere I need to file bug requests? I have > used linux a long time (1997?) and I usually find a fix, so I have never > had to try to contact developers. I have an Averatec 3150h with althlon > mobile and VIA chipset. > > Don't know if that helps
Are you the same as [EMAIL PROTECTED] I tried to reply to your earlier message, but your mail server said that the username ron was not unique and bounced the email. For questions about the UHCI driver, you should post to the USB development mailing list: <[EMAIL PROTECTED]>, not directly to me. That way lots of other people will also be able to see your message and offer suggestions. About all I could get out of your message was that the uhci-hcd driver in 2.6.3 doesn't work on your laptop, whereas the uhci driver from 2.4 does work. You need to say more than that before anyone will be able to help! Dmesg output from the non-working system would be a good start, and you should also include the contents of /proc/bus/usb/devices. In addition, you need to provide a more detailed description of the problem, something more precise than just "does not seem to work". By the way, none of the USB drivers is responsible for assigning IRQ lines to devices. That's handled by an entirely different part of the system. Alan Stern ------------------------------------------------------- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
