Thread: [Ndiswrapper-general] Kernel OOPS trying to load w70n51.sys on a T40p
Status: Beta
Brought to you by:
pgiri
From: Tomas S. <sz...@pi...> - 2003-12-20 09:54:22
Attachments:
config.gz
|
Hi, Box: IBM ThinkPad T40p (part no. 2373-G5G) Device: Intel PRO/Wireless 2100B (Class 0280: 8086:1043, rev 04) Kernel: 2.6.0 vanilla Kernel config: (attached) GCC: 3.3.2 ndiswrapper: CVS as of 2003-12-20 Drivers tested (w/ almost identical results): 6e46b79642d2901a41c239d5043292f5 w70n51.sys 0454ef07fecea4141531cfce0f7e4ceb w70n51.sys a7412fbf0d838dc42a12d5e6cacb1788 w70n51.sys Results: # insmod ./driver/ndiswrapper.ko # ./utils/loadndisdriver 8086 1043 ../w70n51.sys ../w70n51.inf Calling putdriver ioctl Parsing the inf file. Driver version: 07/31/2003,1.2.0.58 Calling startdriver ioctl kernel: Unable to handle kernel paging request at virtual address e1988000 kernel: *pde = 1fd5a067 kernel: *pte = 00000000 Segmentation fault ... ndiswrapper version 0.3+CVS loaded kernel: Putting driver size 2370688 kernel: Image is at e19d0000 Calling entry at e19d0300 rva(00010300) NdisInitializeWrapper handle=de00fe0c, SS1=dfb87000, SS2=de00fef4 NdisMRegisterMiniport driver: dfb87000 NdisMRegisterMiniport Version 5.1 NdisMRegisterMiniport Len: 0000007c:00000044 Past entry: Version: 5.1 e19d0ae0 (rva 00010ae0):CheckForHangTimer e19ed210 (rva 0002d210):DisableInterruptHandler e19ed230 (rva 0002d230):EnableInterruptHandler e19d0910 (rva 00010910):halt e19ed250 (rva 0002d250):HandleInterruptHandler e19d0440 (rva 00010440):init e19ed4c0 (rva 0002d4c0):ISRHandler e19d5d40 (rva 00015d40):query 00000000 (rva 00000000):ReconfigureHandler e19d0d70 (rva 00010d70):ResetHandler e19dd090 (rva 0001d090):SendHandler e19d9a80 (rva 00019a80):SetInformationHandler 00000000 (rva 00000000):TransferDataHandler e19ec0b0 (rva 0002c0b0):ReturnPacketHandler e19dd0b0 (rva 0001d0b0):SendPacketsHandler dfdfdfdf (rva fe43dfdf):AllocateCompleteHandler Unable to handle kernel paging request at virtual address e1988000 printing eip: e1988000 *pde = 1fd5a067 *pte = 00000000 Oops: 0000 [#1] CPU: 0 EIP: 0060:[<e1988000>] Tainted: P EFLAGS: 00010286 EIP is at 0xe1988000 eax: dfb870c0 ebx: dfb87028 ecx: dfb870c0 edx: dfb870c0 esi: ffffffed edi: dfde0c00 ebp: dfb8704c esp: de00fe64 ds: 007b es: 007b ss: 0068 Process loadndisdriver (pid: 141, threadinfo=de00e000 task=dde40080) Stack: c01a4ef4 dfde0c00 dfb870c0 dfb87028 dfde0c00 ffffffed c01a4f2e dfb87028 dfde0c00 c01a4f5c dfb87028 dfde0c00 dfb8704c dfde0c54 c01fd8ee dfde0c54 dfb8704c dfde0c5c c02deb48 dfb8704c c01fda00 dfde0c54 dfb8704c dfb87064 Call Trace: [<c01a4ef4>] pci_device_probe_static+0x52/0x63 [<c01a4f2e>] __pci_device_probe+0x29/0x2b [<c01a4f5c>] pci_device_probe+0x2c/0x4a [<c01fd8ee>] bus_match+0x3f/0x6a [<c01fda00>] driver_attach+0x56/0x80 [<c01fdc7e>] bus_add_driver+0x8b/0x9d [<e19c258e>] misc_ioctl+0x0/0x1ab [ndiswrapper] [<c01fe05d>] driver_register+0x2f/0x33 [<c01a50ee>] pci_register_driver+0x34/0x44 [<e19c2068>] start_driver+0x47/0x96 [ndiswrapper] [<e19c26a3>] misc_ioctl+0x115/0x1ab [ndiswrapper] [<c01cd5aa>] tty_write+0x186/0x1d3 [<c0116a82>] recalc_task_prio+0x90/0x1aa [<c01176a4>] schedule+0x2e6/0x4f1 [<e19c258e>] misc_ioctl+0x0/0x1ab [ndiswrapper] [<c0156e1d>] sys_ioctl+0xbd/0x224 [<c0108d23>] syscall_call+0x7/0xb Code: Bad EIP value. Any pointers appreciated, -- Tomas Szepe <sz...@pi...> |
From: Bill N. <bi...@bi...> - 2003-12-20 11:15:44
|
Hello, I have almost the same problem with Toshiba Pro M10. Same network card. Same driver. Running debian unstable. The problem was the gcc-3.x. Switching back to the 2.95 solve some problems. I am working on that now. I was playing with driverloader and the driver they propose. The card was working just great. Now i am trying to do the same with ndiswrapper. Hope i will have got news in the weekend. Regards, Billy |
From: Tomas S. <sz...@pi...> - 2003-12-20 12:08:15
|
On Dec-20 2003, Sat, 13:15 +0200 Bill Nikolopoulos <bi...@bi...> wrote: > I have almost the same problem with Toshiba Pro M10. Same network card. > Same driver. Running debian unstable. slackware-current (post 9.1) here. > The problem was the gcc-3.x. Switching back to the 2.95 solve some > problems. I am working on that now. Ok, let's retry w/ 2.95.3. [time passes] # cat /proc/version Linux version 2.6.0 (kala@ns) (gcc version 2.95.3 20010315 (release)) #1 Sat Dec 20 12:29:17 CET 2003 # gcc -v Reading specs from /usr/lib/gcc-lib/i386-slackware-linux/2.95.3/specs gcc version 2.95.3 20010315 (release) # pwd /tmp/ndiswrapper.cvs # make ... # insmod ./driver/ndiswrapper.ko # ./utils/loadndisdriver 8086 1043 ../w70n51.sys ../w70n51.inf Calling putdriver ioctl Parsing the inf file. Driver version: 07/31/2003,1.2.0.58 Calling startdriver ioctl kernel: Unable to handle kernel paging request at virtual address e194f000 kernel: *pte = 00000000 kernel: *pde = 1fd59067 Segmentation fault I guess I must be out of luck. > I was playing with driverloader and the driver they propose. > The card was working just great. Thanks for the info, I'll see if I've got the time to fix up their broken bash scripts and retry. > Now i am trying to do the same with ndiswrapper. Hope i will have got news > in the weekend. Good luck! -- Tomas Szepe <sz...@pi...> |
From: Stefan <ste...@gm...> - 2003-12-20 13:07:58
|
Hello, > ndiswrapper: CVS as of 2003-12-20 > > Drivers tested (w/ almost identical results): > 6e46b79642d2901a41c239d5043292f5 w70n51.sys > 0454ef07fecea4141531cfce0f7e4ceb w70n51.sys > a7412fbf0d838dc42a12d5e6cacb1788 w70n51.sys > > Any pointers appreciated, Did you get the latest driver from your vendor? The drivers in your Windows directory are to old. If the newest drivers don't work try the driver for the Acer Travelmate 803. They work for me. /Stefan |
From: Tomas S. <sz...@pi...> - 2003-12-20 13:33:50
|
On Dec-20 2003, Sat, 14:14 +0100 Stefan D=F6singer <ste...@gm...> wrote: > > Drivers tested (w/ almost identical results): > > 6e46b79642d2901a41c239d5043292f5 w70n51.sys > > 0454ef07fecea4141531cfce0f7e4ceb w70n51.sys > > a7412fbf0d838dc42a12d5e6cacb1788 w70n51.sys > > > > Any pointers appreciated, >=20 > Did you get the latest driver from your vendor? The drivers in your Win= dows=20 > directory are to old. If the newest drivers don't work try the driver f= or the=20 > Acer Travelmate 803. They work for me. The three drivers I've tried are - IBM's latest iprowiir.exe (identical to Intel's intel2100b.zip) - the M$ one (from windowsupdate) - the one from v12056logo_xp.zip The Acer Travelmate 800 series driver (from tm800wir.exe) is bit-to-bit identical to the beast from windowsupdate. --=20 Tomas Szepe <sz...@pi...> |
From: Tomas S. <sz...@pi...> - 2003-12-20 14:26:44
|
On Dec-20 2003, Sat, 10:54 +0100 Tomas Szepe <sz...@pi...> wrote: > Box: IBM ThinkPad T40p (part no. 2373-G5G) > Device: Intel PRO/Wireless 2100B (Class 0280: 8086:1043) > Kernel: 2.6.0 vanilla > Kernel config: (attached) > GCC: 3.3.2 > ndiswrapper: CVS as of 2003-12-20 > > Drivers tested (w/ almost identical results): > 6e46b79642d2901a41c239d5043292f5 w70n51.sys > 0454ef07fecea4141531cfce0f7e4ceb w70n51.sys > a7412fbf0d838dc42a12d5e6cacb1788 w70n51.sys > > Results: ... > kernel: Unable to handle kernel paging request at virtual address e1988000 > kernel: *pde = 1fd5a067 > kernel: *pte = 00000000 > Segmentation fault ... I think I can confirm this as an ndiswrapper bug; linuxant driverloader appears to work just fine w/ the very same setup. -- Tomas Szepe <sz...@pi...> |
From: Tomas S. <sz...@pi...> - 2003-12-25 17:05:46
|
On Dec-20 2003, Sat, 15:26 +0100 Tomas Szepe <sz...@pi...> wrote: > > Box: IBM ThinkPad T40p (part no. 2373-G5G) > > Device: Intel PRO/Wireless 2100B (Class 0280: 8086:1043) > > Kernel: 2.6.0 vanilla > > Kernel config: (attached) > > GCC: 3.3.2 > > ndiswrapper: CVS as of 2003-12-20 > > > > Drivers tested (w/ almost identical results): > > 6e46b79642d2901a41c239d5043292f5 w70n51.sys > > 0454ef07fecea4141531cfce0f7e4ceb w70n51.sys > > a7412fbf0d838dc42a12d5e6cacb1788 w70n51.sys > > > > Results: > > ... > > > kernel: Unable to handle kernel paging request at virtual address e1988000 > > kernel: *pde = 1fd5a067 > > kernel: *pte = 00000000 > > Segmentation fault > > ... > > I think I can confirm this as an ndiswrapper bug; linuxant driverloader > appears to work just fine w/ the very same setup. And with ndiswrapper cvs as of 2003-12-25 18:00 CET the oops is gone and the driver loads and appears to work. Great work! -- Tomas Szepe <sz...@pi...> |