The problem is quite simple; I can't get Fedora to detect the card no matter what I do. If I try the Madwifi drivers, I'm hampered by the following problem:
Quote:
[root@localhost ~]# ifconfig
eth0 Link encap:Ethernet HWaddr 00:16:36:FD 5:6E
inet addr:192.168.2.8 Bcast:192.168.2.255 Mask:255.255.255.0
inet6 addr: fe80::216:36ff:fefd:d56e/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:2554 errors:0 dropped:0 overruns:0 frame:0
TX packets:2858 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:1078528 (1.0 MiB) TX bytes:440708 (430.3 KiB)
Interrupt:16
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:3867 errors:0 dropped:0 overruns:0 frame:0
TX packets:3867 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:21455996 (20.4 MiB) TX bytes:21455996 (20.4 MiB)
|
Yeah, according to Fedora, the wireless card isn't really there, even though I know it is. It shows up in lspci, though.
Quote:
03:00.0 Ethernet controller: Atheros Communications, Inc. AR5006EG 802.11 b/g Wireless PCI Express Adapter (rev 01)
Subsystem: AMBIT Microsystem Corp. Unknown device 0428
Flags: fast devsel, IRQ 11
Memory at 34100000 (64-bit, non-prefetchable) [disabled] [size=64K]
Capabilities: [40] Power Management version 2
Capabilities: [50] Message Signalled Interrupts: Mask- 64bit- Queue=0/0 Enable-
Capabilities: [60] Express Legacy Endpoint IRQ 0
Capabilities: [90] MSI-X: Enable- Mask- TabSize=1
|
Because I can't see it, I can't get it to work with the Madwifi drivers.
I also tried using the Windows driver through Ndiswrapper. It works in Kubuntu and openSUSE, but in Fedora using Ndiswrapper with this particular driver causes a kernel panic:
Quote:
Aug 11 20:55:54 localhost kernel: ndiswrapper version 1.47 loaded (smp=yes)
Aug 11 20:55:54 localhost kernel: ndiswrapper: driver net5211 (,06/21/2007,5.3.0.56) loaded
Aug 11 20:55:54 localhost kernel: PCI: Enabling device 0000:03:00.0 (0000 -> 0002)
Aug 11 20:55:54 localhost kernel: ACPI: PCI Interrupt 0000:03:00.0[A] -> GSI 17 (level, low) -> IRQ 17
Aug 11 20:55:54 localhost kernel: ndiswrapper (ZwClose:2246): closing handle 0xd46958e8 not implemented
Aug 11 20:55:55 localhost kernel: ndiswrapper: using IRQ 17
Aug 11 20:55:55 localhost kernel: BUG: sleeping function called from invalid context at mm/page_alloc.c:1250
Aug 11 20:55:55 localhost kernel: in_atomic():1, irqs_disabled():0
Aug 11 20:55:55 localhost kernel: [<c045dace>] __alloc_pages+0x2e/0x2aa
Aug 11 20:55:55 localhost kernel: [<c045dd76>] __get_free_pages+0x2c/0x3a
Aug 11 20:55:55 localhost kernel: [<c046587e>] __pte_alloc_kernel+0xe/0x48
Aug 11 20:55:55 localhost kernel: [<c046a337>] map_vm_area+0x6e/0x123
Aug 11 20:55:55 localhost kernel: [<c046a76c>] __vmalloc_area_node+0xf3/0x111
Aug 11 20:55:55 localhost kernel: [<c046a80b>] __vmalloc+0xf/0x11
Aug 11 20:55:55 localhost kernel: [<e056af56>] ExAllocatePoolWithTag+0x58/0x65 [ndiswrapper]
Aug 11 20:55:55 localhost kernel: [<e05674f3>] NdisAllocateMemoryWithTag+0x1f/0x3b [ndiswrapper]
Aug 11 20:55:55 localhost kernel: [<e05682e4>] mp_timer_dpc+0x4b/0x64 [ndiswrapper]
Aug 11 20:55:55 localhost kernel: [<e056979a>] kdpc_worker+0x92/0xa9 [ndiswrapper]
Aug 11 20:55:55 localhost kernel: [<c0433e3b>] run_workqueue+0x85/0x125
Aug 11 20:55:55 localhost kernel: [<e0569708>] kdpc_worker+0x0/0xa9 [ndiswrapper]
Aug 11 20:55:55 localhost kernel: [<c04347cd>] worker_thread+0xf9/0x124
Aug 11 20:55:55 localhost kernel: [<c042229f>] default_wake_function+0x0/0xc
Aug 11 20:55:55 localhost kernel: [<c04346d4>] worker_thread+0x0/0x124
Aug 11 20:55:55 localhost kernel: [<c0436da8>] kthread+0xb0/0xd8
Aug 11 20:55:55 localhost kernel: [<c0436cf8>] kthread+0x0/0xd8
Aug 11 20:55:55 localhost kernel: [<c0405b3f>] kernel_thread_helper+0x7/0x10
Aug 11 20:55:55 localhost kernel: =======================
|
Trying different kernels had no effect at all; all of them either crash this way or give me a list of similar errors (only instead of forcing a restart, it simply prints the error over and over again). I'm about out of ideas now...