Cannot get Linksys WPC11 v4 to work on SuSE 9.1
 

First and foremost, I am fairly new to Linux. Played with it a few times. This time I am sick of Windoze and all of the security holes that go along with it.

Now the problem......
I am frustrated. I have read all of the various postings on this card and have tried and tried to get this da*n thing working - and nothing is helping

OS is SuSE 9.1
Wireless card: Linksys WPC11 v4
Trying to use: ndiswrapper

I have tried different versions of ndiswrapper. System keeps locking up when 'modprobe ndiswrapper' is invoked. I have downloaded the WinXP drivers for this card (net8180).

Please HELP before I shoot the computer.

Thanks

Here is a copy of my /var/log/messages file after the 'modprobe ndiswrapper' is invoked:

Aug 18 18:35:04 linux kernel: ndiswrapper version 0.6+CVS loaded
Aug 18 18:35:04 linux kernel: ndiswrapper adding rtl8180.sys
Aug 18 18:35:04 linux kernel: PCI: Enabling device 0000:02:00.0 (0000 -> 0003)
Aug 18 18:35:04 linux kernel: PCI: Setting latency timer of device 0000:02:00.0 to 64
Aug 18 18:35:04 linux kernel: wlan0: ndiswrapper ethernet device 00:0c:41:c7:18:5e using driver rtl8180.sys
Aug 18 18:35:08 linux kernel: Unable to handle kernel paging request at virtual address efd2eb54
Aug 18 18:35:08 linux kernel: printing eip:
Aug 18 18:35:08 linux kernel: d1051553
Aug 18 18:35:08 linux kernel: *pde = 00000000
Aug 18 18:35:08 linux kernel: Oops: 0000 [#1]
Aug 18 18:35:08 linux kernel: CPU: 0
Aug 18 18:35:08 linux kernel: EIP: 0060:[__crc_kernel_read+3385496/5020298] Tainted: P
Aug 18 18:35:08 linux kernel: EIP: 0060:[<d1051553>] Tainted: P
Aug 18 18:35:08 linux kernel: EFLAGS: 00010046 (2.6.4-52-default)
Aug 18 18:35:08 linux kernel: EIP is at 0xd1051553
Aug 18 18:35:08 linux kernel: eax: 00000006 ebx: 00000006 ecx: efd2eb54 edx: c39adac0
Aug 18 18:35:08 linux kernel: esi: cde91cd4 edi: 00000006 ebp: cde91f3c esp: cde91cbc
Aug 18 18:35:08 linux kernel: ds: 007b es: 007b ss: 0068
Aug 18 18:35:08 linux kernel: Process events/0 (pid: 3, threadinfo=cde90000 task=cdedebf0)
Aug 18 18:35:08 linux kernel: Stack: d10526b9 cde91cd4 00000006 c39adaec cde91cd4 d1047382 cde91cd4 00000006
Aug 18 18:35:08 linux kernel: 00000001 d1070000 00000000 00000000 00000000 00000000 00000028 00000000
Aug 18 18:35:08 linux kernel: cde8e2c0 00000000 c01ed9f5 00000028 00000000 00000008 cde91d84 cde91d84
Aug 18 18:35:08 linux kernel: Call Trace:
Aug 18 18:35:08 linux kernel: [acpi_ex_access_region+63/72] acpi_ex_access_region+0x3f/0x48
Aug 18 18:35:08 linux kernel: [<c01ed9f5>] acpi_ex_access_region+0x3f/0x48
Aug 18 18:35:08 linux kernel: [scheduler_tick+27/1872] scheduler_tick+0x1b/0x750
Aug 18 18:35:08 linux kernel: [<c011cf2b>] scheduler_tick+0x1b/0x750
Aug 18 18:35:08 linux kernel: [do_timer+47/1200] do_timer+0x2f/0x4b0
Aug 18 18:35:08 linux kernel: [<c012618f>] do_timer+0x2f/0x4b0
Aug 18 18:35:08 linux kernel: [smp_local_timer_interrupt+8/160] smp_local_timer_interrupt+0x8/0xa0
Aug 18 18:35:08 linux kernel: [<c0116db8>] smp_local_timer_interrupt+0x8/0xa0
Aug 18 18:35:08 linux kernel: [timer_interrupt+551/640] timer_interrupt+0x227/0x280
Aug 18 18:35:08 linux kernel: [<c010dc97>] timer_interrupt+0x227/0x280
Aug 18 18:35:08 linux kernel: [acpi_ut_acquire_from_cache+71/161] acpi_ut_acquire_from_cache+0x47/0xa1
Aug 18 18:35:08 linux kernel: [<c01f99ae>] acpi_ut_acquire_from_cache+0x47/0xa1
Aug 18 18:35:08 linux kernel: [acpi_ec_wait+61/133] acpi_ec_wait+0x3d/0x85
Aug 18 18:35:08 linux kernel: [<c01fce00>] acpi_ec_wait+0x3d/0x85
Aug 18 18:35:08 linux kernel: [acpi_hw_low_level_read+89/152] acpi_hw_low_level_read+0x59/0x98
Aug 18 18:35:08 linux kernel: [<c01f1483>] acpi_hw_low_level_read+0x59/0x98
Aug 18 18:35:08 linux kernel: [scheduler_tick+95/1872] scheduler_tick+0x5f/0x750
Aug 18 18:35:08 linux kernel: [<c011cf6f>] scheduler_tick+0x5f/0x750
Aug 18 18:35:08 linux kernel: [__crc_kernel_read+3249778/5020298] doquery+0x4d/0xe0 [ndiswrapper]
Aug 18 18:35:08 linux kernel: [<d103032d>] doquery+0x4d/0xe0 [ndiswrapper]
Aug 18 18:35:08 linux kernel: [__crc_kernel_read+3265688/5020298] NdisMSendComplete+0x23/0x30 [ndiswrapper]
Aug 18 18:35:08 linux kernel: [<d1034153>] NdisMSendComplete+0x23/0x30 [ndiswrapper]
Aug 18 18:35:08 linux kernel: [schedule+563/1920] schedule+0x233/0x780
Aug 18 18:35:08 linux kernel: [<c011c613>] schedule+0x233/0x780
Aug 18 18:35:08 linux kernel: [__crc_kernel_read+3262610/5020298] ndis_irq_bh+0x5d/0x80 [ndiswrapper]
Aug 18 18:35:08 linux kernel: [<d103354d>] ndis_irq_bh+0x5d/0x80 [ndiswrapper]
Aug 18 18:35:08 linux kernel: [worker_thread+358/496] worker_thread+0x166/0x1f0
Aug 18 18:35:08 linux kernel: [<c012c6c6>] worker_thread+0x166/0x1f0
Aug 18 18:35:08 linux kernel: [__crc_kernel_read+3262517/5020298] ndis_irq_bh+0x0/0x80 [ndiswrapper]
Aug 18 18:35:08 linux kernel: [<d10334f0>] ndis_irq_bh+0x0/0x80 [ndiswrapper]
Aug 18 18:35:08 linux kernel: [default_wake_function+0/16] default_wake_function+0x0/0x10
Aug 18 18:35:08 linux kernel: [<c011bdc0>] default_wake_function+0x0/0x10
Aug 18 18:35:08 linux kernel: [schedule+649/1920] schedule+0x289/0x780
Aug 18 18:35:08 linux kernel: [<c011c669>] schedule+0x289/0x780
Aug 18 18:35:08 linux kernel: [default_wake_function+0/16] default_wake_function+0x0/0x10
Aug 18 18:35:08 linux kernel: [<c011bdc0>] default_wake_function+0x0/0x10
Aug 18 18:35:08 linux kernel: [worker_thread+0/496] worker_thread+0x0/0x1f0
Aug 18 18:35:08 linux kernel: [<c012c560>] worker_thread+0x0/0x1f0
Aug 18 18:35:08 linux kernel: [kthread+169/209] kthread+0xa9/0xd1
Aug 18 18:35:08 linux kernel: [<c012f4d9>] kthread+0xa9/0xd1
Aug 18 18:35:08 linux kernel: [kthread+0/209] kthread+0x0/0xd1
Aug 18 18:35:08 linux kernel: [<c012f430>] kthread+0x0/0xd1
Aug 18 18:35:08 linux kernel: [kernel_thread_helper+5/16] kernel_thread_helper+0x5/0x10
Aug 18 18:35:08 linux kernel: [<c0106005>] kernel_thread_helper+0x5/0x10
Aug 18 18:35:08 linux kernel:
Aug 18 18:35:08 linux kernel: Code: f6 01 03 74 0e 50 ff 74 24 08 e8 76 14 00 00 32 c0 eb 02 b0
Aug 18 18:35:17 linux kernel: <7>wlan0: no IPv6 routers present

I may have confused this card with another one, but I didn't think this used a realtek chipset. Could you have a look at the output of lspci and check that your using the proper windows driver?