After trying to configure wireless on Slackware 12 my box is unable to boot. The final message on the screen is:
Triggering udev events: sbin/udevtrigger --retry-failed
I can go out and eat my dinner while udevtrigger tries to do it's thing and it is still sitting there quietly like a sick dog when I get back. Reboots after a three finger salute and does the same thing again.
I am using ndiswrapper for wireless (madwifi had its own set of problems ...) and it was connecting fine from the command line, invoking wpa_supplicant. Wanting wireless to come up with boot, I did some tinkering with /etc/rc.d/rc.wireless.conf and /etc/rc.d/rc.inet1.conf but something must have gone awry. It looks as if udev can't make sense of it.
The tail end of /var/log/messages (omitting the reboot messages) is as follows:
Feb 19 21:00:56 beast logger: /etc/rc.d/rc.inet1: /sbin/route add default gw 192.168.1.1 metric 1
Feb 19 21:00:56 beast logger: SIOCADDRT: No such process
Feb 19 21:00:56 beast logger: /etc/rc.d/rc.inet1: /sbin/ifconfig lo 127.0.0.1
Feb 19 21:00:56 beast logger: /etc/rc.d/rc.inet1: /sbin/route add -net 127.0.0.0 netmask 255.0.0.0 lo
Feb 19 21:00:57 beast logger: /etc/rc.d/rc.inet1: /sbin/modprobe wlan0
Feb 19 21:00:57 beast kernel: ndiswrapper version 1.52 loaded (smp=yes, preempt=yes)
Feb 19 21:00:57 beast kernel: ndiswrapper: driver net5211 (TP-LINK,12/21/2005,184.108.40.206) loaded
Feb 19 21:00:57 beast kernel: ACPI: PCI Interrupt 0000:03:0c.0[A] -> GSI 20 (level, low) -> IRQ 21
Feb 19 21:00:57 beast kernel: ndiswrapper: using IRQ 21
Feb 19 21:00:58 beast kernel: wlan0: ethernet device 00:19:e0:11:cf:74 using serialized NDIS driver: net5211, version: 0x40001, NDIS version: 0x501, vendor: 'NDIS Network Adapter', 168C:001A.5.conf
Feb 19 21:00:58 beast kernel: wlan0: encryption modes supported: WEP; TKIP with WPA, WPA2, WPA2PSK; AES/CCMP with WPA, WPA2, WPA2PSK
Feb 19 21:00:58 beast kernel: usbcore: registered new interface driver ndiswrapper
Any suggestions or advice would be appreciated. I am operating from mandriva on a spare partition at the moment and miss my Slackware.
BTW I only called my box 'beast' to flatter its ego, it is not that powerful really