Find the answer to your Linux question:
Results 1 to 3 of 3
I have onboard wireless on my motherboard and a pci card. I had no trouble getting ndiswrapper to work for the onboard wireless; however, it has range issues. I dual ...
  1. #1
    Just Joined!
    Join Date
    Dec 2004
    Posts
    3

    [SOLVED] ndiswrapper is not working

    I have onboard wireless on my motherboard and a pci card. I had no trouble getting ndiswrapper to work for the onboard wireless; however, it has range issues. I dual boot winXP so I know the pci card works better in terms of getting a signal.

    After restarting the computer it hung on the kde startup screen so I
    • used the live cd
    • mounted my filesystem:
      sudo mkdir /oldsys/
      sudo mount -t ext3 /dev/hda3 /oldsys/
    • used a chroot:
      sudo chroot /oldsys
    • tried modprobe -r ndiswrapper but it couldn't find a file
    • successfully removed the windows drivers from ndiswrapper and rewrote the kernel module: (note you need to remove each driver that is listed by the first command)
      ndiswrapper -l
      ndiswrapper -r
      <name of driver>
      sudo ndiswrapper -m
    • rebooted the computer and kde loaded successfully


    I get weird junk on screen when I run ndiswrapper -m.:
    module configuration contains directive install pci:v000010ECd00008185sv000013F2sd000010BDbc*sc*i* /sbin/modprobe ndiswrapper
    ;you should delete that at /usr/sbin/ndiswrapper-1.9 line 790, <MODPROBE> line 194.
    module configuration contains directive install pci:v000010ECd00008185sv000014F2sd000010BDbc*sc*i* /sbin/modprobe ndiswrapper
    ;you should delete that at /usr/sbin/ndiswrapper-1.9 line 790, <MODPROBE> line 195.
    module configuration contains directive install pci:v000010ECd00008185sv00006165sd000018E8bc*sc*i* /sbin/modprobe ndiswrapper
    ;you should delete that at /usr/sbin/ndiswrapper-1.9 line 790, <MODPROBE> line 196.
    module configuration contains directive install pci:v000010ECd00008185sv00008185sd000010ECbc*sc*i* /sbin/modprobe ndiswrapper
    ;you should delete that at /usr/sbin/ndiswrapper-1.9 line 790, <MODPROBE> line 197.
    module configuration contains directive install pci:v000010ECd00008185sv*sd*bc*sc*i* /sbin/modprobe ndiswrapper
    ;you should delete that at /usr/sbin/ndiswrapper-1.9 line 790, <MODPROBE> line 198.
    module configuration contains directive install pci:v000011ABd00001FA4sv*sd*bc*sc*i* /sbin/modprobe ndiswrapper
    ;you should delete that at /usr/sbin/ndiswrapper-1.9 line 790, <MODPROBE> line 199.
    module configuration contains directive install pci:v000011ABd00001FA6sv0000108Fsd00001043bc*sc*i* /sbin/modprobe ndiswrapper
    ;you should delete that at /usr/sbin/ndiswrapper-1.9 line 790, <MODPROBE> line 200.
    module configuration contains directive install pci:v000011ABd00001FA6sv0000128Fsd00001043bc*sc*i* /sbin/modprobe ndiswrapper
    ;you should delete that at /usr/sbin/ndiswrapper-1.9 line 790, <MODPROBE> line 201.
    module configuration contains directive install pci:v000011ABd00001FA6sv0000138Fsd00001043bc*sc*i* /sbin/modprobe ndiswrapper
    ;you should delete that at /usr/sbin/ndiswrapper-1.9 line 790, <MODPROBE> line 202.
    module configuration contains directive install pci:v000011ABd00001FA6sv*sd*bc*sc*i* /sbin/modprobe ndiswrapper
    ;you should delete that at /usr/sbin/ndiswrapper-1.9 line 790, <MODPROBE> line 203.
    module configuration contains directive install pci:v000011ABd00001FA7sv*sd*bc*sc*i* /sbin/modprobe ndiswrapper
    ;you should delete that at /usr/sbin/ndiswrapper-1.9 line 790, <MODPROBE> line 204.
    module configuration already contains alias directive


    When I added the ndiswrapper module to the kernel with:
    sudo modprobe ndiswrapper

    The first time it said Killed and i checked dmesg to get this dump:
    [ 2997.955516] Pid: 7635, comm: modprobe Tainted: P 2.6.22-14-generic #1
    [ 2997.955518] RIP: 0010:[<ffffc2000501457a>] [<ffffc2000501457a>]
    [ 2997.955523] RSP: 0018:ffff81003cf31850 EFLAGS: 00010286
    [ 2997.955526] RAX: ffffc200050738bc RBX: ffffc20005072000 RCX: 00000037a2451bf0
    [ 2997.955528] RDX: 0000000000000000 RSI: 0000000000000000 RDI: 00000000fe538512
    [ 2997.955531] RBP: 0000000000000000 R08: 0000000000000000 R09: 0000000000000000
    [ 2997.955533] R10: ffffffff881c30b0 R11: 0000000000000000 R12: 0000000000000005
    [ 2997.955536] R13: ffffc2000506a070 R14: 0000000000000000 R15: 000000000000001b
    [ 2997.955539] FS: 00002b0e0e44a6e0(0000) GS:ffffffff80560000(0000) knlGS:0000000000000000
    [ 2997.955542] CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003b
    [ 2997.955545] CR2: ffffc237a74bbc60 CR3: 000000003ceb3000 CR4: 00000000000006e0
    [ 2997.955548] Process modprobe (pid: 7635, threadinfo ffff81003cf30000, task ffff81003d0aa000)
    [ 2997.955550] Stack: ffff81007b345230 ffffc20005021ded 0000000000000000 000000000000001b
    [ 2997.955555] ffffffff881d4500 0000000000000000 ffffc20005072000 ffff810049f6ee00
    [ 2997.955560] ffff81007b345230 0000000000000000 ffffc2000506d010 ffff8100638e5780
    [ 2997.955563] Call Trace:
    [ 2997.955603] [<ffffffff881d4500>] :ndiswrapper:_win_towupper+0x10/0x20
    [ 2997.955631] [<ffffffff881ca42f>] :ndiswrapper:IofCallDriver+0x5f/0xc0
    [ 2997.955649] [<ffffffff881ca404>] :ndiswrapper:IofCallDriver+0x34/0xc0
    [ 2997.955668] [<ffffffff881d0dd5>] :ndiswrapper:mp_init+0xa5/0x190
    [ 2997.955685] [<ffffffff881cb8c0>] :ndiswrapper:IoSyncForwardIrp+0x90/0xd0
    [ 2997.955707] [<ffffffff881d152b>] :ndiswrapper:NdisDispatchPnp+0xdb/0xd40
    [ 2997.955713] [<ffffffff8022cacc>] task_rq_lock+0x4c/0x90
    [ 2997.955721] [<ffffffff80435be8>] kprobe_flush_task+0x58/0xb0
    [ 2997.955730] [<ffffffff804303ec>] thread_return+0x445/0x6c9
    [ 2997.955737] [<ffffffff8029180c>] get_partial_node+0x1c/0xa0
    [ 2997.955741] [<ffffffff8029333b>] __slab_alloc+0x17b/0x400
    [ 2997.955757] [<ffffffff881cab4d>] :ndiswrapper:IoAllocateIrp+0x4d/0x80
    [ 2997.955776] [<ffffffff881caacb>] :ndiswrapper:IoInitializeIrp+0x3b/0x70
    [ 2997.955800] [<ffffffff881d4537>] :ndiswrapper:win2lin2+0xe/0x11
    [ 2997.955817] [<ffffffff881ca42f>] :ndiswrapper:IofCallDriver+0x5f/0xc0
    [ 2997.955835] [<ffffffff881ca404>] :ndiswrapper:IofCallDriver+0x34/0xc0
    [ 2997.955852] [<ffffffff881cb2ff>] :ndiswrapper:IoBuildSynchronousFsdRequest+0x2f/0x50
    [ 2997.955871] [<ffffffff881cf61c>] :ndiswrapper:IoSendIrpTopDev+0xac/0x100
    [ 2997.955898] [<ffffffff881cf91f>] :ndiswrappernp_start_device+0x4f/0xa0
    [ 2997.955923] [<ffffffff881cfb54>] :ndiswrapper:wrap_pnp_start_device+0x1e4/0x280
    [ 2997.955949] [<ffffffff881cfc40>] :ndiswrapper:wrap_pnp_start_pci_device+0x50/0x60
    [ 2997.955958] [<ffffffff802e8530>] sysfs_make_dirent+0x30/0x50
    [ 2997.955968] [<ffffffff803352d1>] pci_device_probe+0xf1/0x170
    [ 2997.955978] [<ffffffff80391063>] driver_probe_device+0xa3/0x1b0
    [ 2997.955985] [<ffffffff80391329>] __driver_attach+0xc9/0xd0
    [ 2997.955991] [<ffffffff80391260>] __driver_attach+0x0/0xd0
    [ 2997.955995] [<ffffffff8039023d>] bus_for_each_dev+0x4d/0x80
    [ 2997.956004] [<ffffffff8039069f>] bus_add_driver+0xaf/0x1f0
    [ 2997.956011] [<ffffffff80335556>] __pci_register_driver+0x66/0xb0
    [ 2997.956025] [<ffffffff881bfd5c>] :ndiswrapper:loader_init+0x13c/0x260
    [ 2997.956037] [<ffffffff880b50b5>] :ndiswrapper:wrapper_init+0xb5/0xc2
    [ 2997.956043] [<ffffffff80256edb>] sys_init_module+0x19b/0x19b0
    [ 2997.956063] [<ffffffff80326a21>] __up_write+0x21/0x130
    [ 2997.956077] [<ffffffff80209e8e>] system_call+0x7e/0x83
    [ 2997.956089]
    [ 2997.956090]
    [ 2997.956090] Code: 4a 83 3c 29 00 0f 84 98 00 00 00 4a 8b 4c 29 20 48 85 c9 0f
    [ 2997.956097] RIP [<ffffc2000501457a>]
    [ 2997.956101] RSP <ffff81003cf31850>
    [ 2997.956103] CR2: ffffc237a74bbc60


    When I ran modeprobe ndiswrapper the second time it just sat there indefinately. I have tried both x64 and normal XP drivers and haven't seen any difference. Any advice would be appreciated as to getting ndiswrapper to function properly with both wireless devices.

  2. #2
    Just Joined!
    Join Date
    Dec 2004
    Posts
    3

    Solution

    I tracked the issue down to the fact that I had two wireless devices. Since I am no longer using the wireless on my motherboard I disabled it from the bios settings. This eliminated half the error messages I get when running ndiswrapper -m and I was able to successfully
    -run: modprobe ndiswrapper
    -connect to a WPA enterprise network using PEAP security (with the Gnome network manager applet to simplify the wpa supplicant config proccess)

  3. #3
    Trusted Penguin Dapper Dan's Avatar
    Join Date
    Oct 2004
    Location
    The Sovereign State of South Carolina
    Posts
    4,562
    vertago1, you've had a long journey with this and many people have watched this thread. Linuxforums thanks you for being considerate enough to share your solution with future members who might run into the same problem. Glad you got it all sorted!
    Linux Mint + IceWM Registered:#371367 New Members: click here

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •