Description of problem: When a Zaurus USB cradle is attached the kernel loads the CDCEther rather than the usbnet module. Version-Release number of selected component (if applicable): 2.4.20-2.2 and 2.4.20-2.13 How reproducible: Always Steps to Reproduce: 1. 'tail -t /var/log/messages' 2. plug in Zaurus Actual results: CDCEther driver is loaded Expected results: usbdev driver should be loaded Additional info: I'll add the log messages in a bit
Created attachment 89364 [details] log entries with the standard configuration
Created attachment 89365 [details] log entries with CDCEther in /etc/hotplug/blacklist If I add CDCEther to /etc/hotplug/blacklist, then the proper module gets loaded.
http://groups.google.com/groups?hl=en&lr=&ie=UTF-8&oe=UTF-8&safe=off&threadm=20030112045005%243abb%40gated-at.bofh.it&rnum=1&prev=/groups%3Fq%3Dbrad%2Bhards%2Bcdcether%26hl%3Den%26lr%3D%26ie%3DUTF-8%26oe%3DUTF-8%26safe%3Doff%26scoring%3Dd%26selm%3D20030112045005%25243abb%2540gated-at.bofh.it%26rnum%3D1 From: Brad Hards <bhards.au> Newsgroups: linux.kernel Subject: Re: proposed changes for CDCEther module? Date: Sun, 12 Jan 2003 15:30:16 +1100 Message-ID: <200301121530.17044.bhards.au> References: <Pine.LNX.4.44.0301111625260.15841-100000@dell> > i also *think* i remember someone saying that that was > going to be "fixed" in some way with a subsequent release > of the kernel. can anyone refresh my memory as to what > that fix might have involved? was this issue with CDCEther > considered a "bug" that needed fixing? or am i misremembering? It is, but I haven't got around to doing it yet. Please give me a bit of time to get it coded, tested, and pushed to Greg K-H. It is actually a bug in the Zaurus code, since it is claiming to be compliant with the CDC Ethernet class specification, but it isn't. Brad
Latest changes to Zaurus part of usbnet were coming from David-B (larger send length for certain framings, and removal of private crc table).
Is there a way to use /etc/hotplug/usb.handmap rather than /etc/hotplug/blacklist to get the proper device driver to load. I tried that but I couldn't get it to work. I didn't really know what I was doing though.
Is the 2.4.20-18.9 still broken for you?
Created attachment 92207 [details] Log messages produced by plugging in the Zaurus The latest Red Hat kernel still loads the CDCEther module. Attached are the log messages produced.
Is this a problem still? If yes, what kernel version? Also, I'll need a copy of /proc/bus/usb/devices.
There is no longer quite the same problem: now neither module is loaded. I'm currently using kernel-2.6.8-1.521, but this has been the behavior for a while.
Created attachment 102940 [details] /proc/bus/usb/device Here is /proc/bus/usb/device with the Zaurus plugged in and after 'modprobe usbnet'
works for me on fedora core 3 test 1 (amd64) using: kernel-2.6.8-1.541 hotplug-2004_04_01-4 initscripts-7.80-1 udev-030-26 and the following initscript for usb0 (/etc/sysconfig/network-scripts/ifcfg-usb0) : # Zaurus DEVICE=usb0 ONBOOT=no BOOTPROTO=dhcp configures/unconfigures correctly and loads usbnet, as far as zaurus (5500 with ROM 3.10) is configured to use USB - TCP/IP (advanced).
Thanks for the bug report. However, Red Hat no longer maintains this version of the product. Please upgrade to the latest version and open a new bug if the problem persists. The Fedora Legacy project (http://fedoralegacy.org/) maintains some older releases, and if you believe this bug is interesting to them, please report the problem in the bug tracker at: http://bugzilla.fedora.us/