[Ndiswrapper-general] problem with 2.6.0 Kernel
Status: Beta
Brought to you by:
pgiri
From: Ashutosh J. <ash...@cs...> - 2004-01-21 23:29:09
|
Hi, I'm trying to get ndiswrapper working on a Dell Inspiron 4150 with a TrueMobile 1180 (broadcom 4301), Gentoo-Linux system running 2.6.0 kernel. After running install.sh I did a modprobe ndiswrapper and got the following message: Calling putdriver ioctl Parsing the inf file. Driver version: 07/09/2002, 3.08.27.0 Adding setting: RadioState = 0 Adding setting: Channel = 11 Adding setting: PowerSaveMode = 0 Adding setting: Rate = 0 Adding setting: PLCPHeader = 0 Adding setting: antdiv = -1 Adding setting: frag = 2346 Adding setting: rts = 2347 Calling startdriver ioctl FATAL: Error running install command for ndiswrapper On checking the dmesg output I found the following: ndiswrapper version 0.4 loaded Unable to handle kernel paging request at virtual address e1a21000 printing eip: e1a21000 *pde = 1fe08067 *pte = 00000000 Oops: 0000 [#1] CPU: 0 EIP: 0060:[<e1a21000>] Tainted: P EFLAGS: 00010286 EIP is at 0xe1a21000 eax: dcbdbac0 ebx: dcbdba28 ecx: dcbdbac0 edx: dcbdbac0 esi: ffffffed edi: dff2dc00 ebp: dcbdba4c esp: dd3dde68 ds: 007b es: 007b ss: 0068 Process loadndisdriver (pid: 18337, threadinfo=dd3dc000 task=dd1146a0) Stack: c01d7150 dff2dc00 dcbdbac0 dcbdba28 dff2dc00 ffffffed c01d718a dcbdba28 dff2dc00 c01d71b8 dcbdba28 dff2dc00 dcbdba4c dff2dc54 c021b2fe dff2dc54 dcbdba4c dff2dc5c c035c008 dcbdba4c c021b410 dff2dc54 dcbdba4c dcbdba64 Call Trace: [<c01d7150>] pci_device_probe_static+0x52/0x63 [<c01d718a>] __pci_device_probe+0x29/0x2b [<c01d71b8>] pci_device_probe+0x2c/0x4a [<c021b2fe>] bus_match+0x3f/0x6a [<c021b410>] driver_attach+0x56/0x80 [<c021b68e>] bus_add_driver+0x8b/0x9d [<c021ba71>] driver_register+0x2f/0x33 [<c01d734a>] pci_register_driver+0x34/0x44 [<e2df536c>] start_driver+0x68/0x96 [ndiswrapper] [<e2df5991>] misc_ioctl+0x111/0x1a3 [ndiswrapper] [<c01fce06>] tty_write+0x1a3/0x207 [<c0115b30>] recalc_task_prio+0x92/0x19d [<c011679e>] schedule+0x2eb/0x4f5 [<c0157004>] sys_ioctl+0xb2/0x22a [<c0108e9b>] syscall_call+0x7/0xb Code: Bad EIP value. Is this problem with the kernel or am I doing something wrong? thanks, Ashu |