After a second reading of the instructions for configuring the kernel module and wlan-ng drivers for the MA111 USB Wireless Adapter on Fedora Core 1 Linux, I've discovered that I have an athlon kernel, whereas I assumed that I had a i686 kernel and CPU. Choosing the appropriate RPMs for the athlon kernel permitted the packages to install cleanly without any warnings.

However, after booting, when I plug in the USB device, the system freezes and the lights on the keyboard start flashing. I can't get to a virtual console with CTRL-ALT-F2, and all I can do is push the big red button to restart. If I leave the USB device plugged in during a boot, the system freezes again just after printing this during the startup sequence:

Stack: {lots of memory addresses}
Call Trace: usb_free_devR8bf51c4a
process_urb [usbcore]
Code: {lots of digit pairs here}
Kernel panic: Aiee, killing interrupt handler!
In interrupt handler not synching

The instructions state that if you want to request help from the author of the RPM packages you should email the answers to a couple of questions. While I'm not ready to bug him quite yet, here is what I have:

Microtel SYSMAR417 PC with AMD Duron processor
Netgear MA111 802.11b Wireless USB Adapter
Fedora Core 1

1. The output of 'uname -a'.
Linux Walden 2.4.22-1.2115.nptl # Wed Oct 29 15:31:21 EST 2003 i686 athlon i386 GNU/Linux

2. The contents of /boot/kernel.h.
/* Kernel type athlon */
#ifndef __MODULE_KERNEL_athlon
#define __MODULE_KERNEL_athon 1

3. Your kernel version (or, output of 'rpm -qa | grep kernel-2')

4. An excerpt from /var/log/messages at the time you insert your USB device.
Feb 29 18:29:39 Walden kernel: hub.c: new USB device 00:07.3-1, assigned address 3
Feb 29 18:29:39 usb.c: USB device 3 (vend/prod 0x846/0x4110) is not claimed by any active driver.
Feb 29 18:29:39 prism2_init: prism2_usb.o: 0.2.1-pre14 Loaded
Feb 29 18:29:39 prism2_init: dev_info is: prism2_usb
Feb 29 18:29:39 usb.c: registered new driver prism2_usb
Feb 29 18:29:39 usb.c: USB disconnect on device 00:07.3-1 address 3
Feb 29 18:31:25 sysylogd 1.4.1: restart.

See my earlier report from when I tried installing the RPMs for the wrong kernel type.