Red Hat Bugzilla – Bug 74256
keyspan.o kernel module is missing firmware for Keyspan USA-49W
Last modified: 2007-04-18 12:46:47 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (compatible; Konqueror/3.0.0-10; Linux)
Description of problem:
The keyspan.o module seemingly wasn't compiled with support for the Keyspan USA-49W USB to 4-port serial adapter.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Plug in Keyspan USA-49W on USB bus.
2. Watch the red LED *not* light, as the unit isn't downloaded the necessary firmware from the keyspan.o module.
3. Be disappointed.
Actual Results: The Keyspan USA-49W isn't loaded with its firmware, and so it sits idle.
Expected Results: The red LED indicating downloading of firmware and its IPO should have lit, and it should be operational as /dev/ttyUSB[0-3]
I will attach a portion of /var/log/messages that occurs immediately after plugging in the Keyspan USA-49W. The major downside of this is that the computer has to be rebooted to clear the "keyspan" from lsmod. "rmmod keyspan" locks the shell - control-C will now break out.
I have attempted to recompile keyspan.o with the USA-49W firmware, with the same lack of success.
Created attachment 76548 [details]
Portion of /var/log/messages
Created attachment 76549 [details]
ksymoops from the previously attached /var/log/messages segment
Note that by building a kernel from the standard i686 config
file from the configs directory from the
kernel-source-2.4.18-10.rpm, modified to include the firmware,
keyspan.o fails to load firmware, can't be removed with rmmod
(shell hangs), and unplugging the Keyspan from the USB port
oopses khubd (see attachments).
Using the same kernel .config file as above, both the stock
2.4.18 and 2.4.19 kernels behave properly. Firmware is
downloaded, rmmod functions properly, and there is no oops when
unplugging the Keyspan from the USB bus. Somehow, one or more
of the -10 Red Hat kernel's tweaks/patches cause the above
Please attach the result of dmesg after the failure,
but do not edit it. The messages file is too confusing.
Created attachment 76725 [details]
dmesg from boot with Keyspan USA-49W attached
Created attachment 76726 [details]
dmesg generated from plugging Keyspan USA-49W into a freshly booted machine
Attachment id=76725 is the dmesg from the boot of this machine with the Keyspan
attached before booting. Attachment id=76726 is from the same machine, after
rebooting without having the Keyspan attached, logging in as root, and plugging
in the Keyspan to the USB port.
keyspan works properly with stock 2.4.19 and 2.4.20-pre8 kernels running on Psyche.
2.4.18-17.7.x on 7.3 oopses as well. I will attach a ksymoops trace from a
custom kernel built with the USA49W firmware included, using
/usr/src/linux-2.4.18-17.7.x/configs/kernel-2.4.18-athlon.config as the base,
changing only the USA49W firmware line.
At a cold boot, with the Keyspan also cold booted (no firmware loaded into the
Keyspan at this point), the kernel oopses at boot. But if I now reboot the
linux box, the Keyspan will be fed its firmware and will work until it is
unplugged. Upon replugging the Keyspan, the kernel will oops again.
Created attachment 84645 [details]
oops of Keyspan USA49W with 2.4.18-17-7.x kernel
2.4.18-18.8.0 doesn't work either. Same problems.
*** This bug has been marked as a duplicate of 76473 ***