Unable modprobe ndiswrapper on 2.6.12.5 kernel

Greetings everyone,
As my username implies, long time slackware user. Got bored one day and installed Arch and am very impressed.
One small problem. I have using a 2.6.12.5 kernel with a custom .config file that has reiser4 support patched in.
I have the ndiswrapper 1.2.tar.gz source that I compile and install. Sets up the ndiswrapper.ko module under /lib/modules/2.6.12.5/misc.
When I try to modprobe ndiswrapper I get the error:
FATAL: error inserting ndiswrapper (/lib/modules/2.6.12.5/misc/ndiswrapper.ko): Invalid module format
If I try ndiswrapper -i bcmwl5.inf I get errors pointing to line 17 of /usr/sbin/ndiswrapper which is "use strict"
There are various other errors relating to /usr/perl/5.8.7, etc.
I use the same kernel with the same .config file in slackware with no problems installing the ndiswrapper module or modprobing it. Works fine.
I've been using Arch for a few months now, using 2.6.12.3 on. I know at one point I could modprobe ndiswrapper 1.2 with the previous kernels, so I don't know if there is something specific to 2.6.12.5 that is the problem.
I would use the Arch ndiswrapper, but it installs to the module that 2.6.12-ARCH uses, not my vanilla kernel.
Any suggestions??
Thanks in advance for any assistance and a very well put together distro.
Gary

phrakture,
Just finished recompiling 2.6.12.4 & 2.6.12.5 with and w/o the Arch logo. Am now able to load ndiswrapper module w/o any problems.
Previously, and I apologize if my first post was a little comfusing, was that
1: ndiswrapper.ko module would not load using modprobe without giving the invalid module format error.
2: if i tried ndiswrapper -i bcmwl5.inf, thst's when I got the various perl errors which a reinstall did not fix.
I think maybe my 2.6.12.5 kernel source may have been corrupt.
When I installed Arch with reiser3.6, using the default ARCh 2.6 kernel, I then installed libaal-1.0.4-1 & reiser4progs-1.0.4.1, compiled a 2.6.12.5 kernel patched with the namesys R4 patch. Copied everything to another partition. Booted into slackware setup identically. Formatted hda6 for reiser4 and copied the data back. Use 0.96 Reiser4 patched Grub to boot into either Slackware, Arch or Windows XP.
So maybe the copy somehow corrupted something. Have never had a problem with this before, but live and learn.
I would still like to learn how to use pkgbuild as I am really impressed with the responsiveness of Arch, not that Slackware is a slouch by any means, but I think the 686 optimization works better with my 2.4ghz P4.
So any tips of pkgbuild would be most appreciated.
Gary

Similar Messages

Ndiswrapper and the 2.6.13 kernel

The current ndiswrapper package 1.4-1 (Last Updated: Sat, 08 Oct 2005 00:32:51 -0400) does not work with the new 2.6.13 stock kernel. You should use the 1.4@051015 found here:
http://ndiswrapper.sourceforge.net/snap … per.tar.gz
if you wish ndiswrapper to work with the new 2.6.13 arch stock kernel. I just upgraded everything on my laptop and the current stable version does not work, as it makes the kernel crash. Until the package is updated, just compile this version.
log in as root (su)
first uninstall the one you have
pacman -R ndiswrapper ndiswrapper-bin
the remove the config files
rm -R /ect/ndiswrapper
untar the archive and compile
tar xzvf ndiswrapper.tar.gz
cd ndiswrapper
make distclean
make
make install
reinstall your wireless drivers
ndiswrapper -i driver_file.inf
and check if they're installed
ndiswrapper -l
update the module dependencies
depmod -a
finally modprobe it
modprobe ndiswrapper
if the kernel does not crash, dance around and be merry.

tyler wrote:wow, the package is updated, and its even more bleeding edge than the version I installed. thanks, i'll pacman it.
Yeah the snapshot isn't versioned, so I had no choice. I'm hoping 1.5 (or 1.4.X) is released soon, as I don't like running the snapshot like that.

Ndiswrapper 1.58 - temporary fix for kernel 3.10

As many of you might know, ndiswrapper got removed from the official repos as it's broken by procfs API changes in kernel 3.10.
I couldn't find any patches and upstream seems to be dead, so I migrated it myself.
This is only intended to be a temporary solution! I would welcome it if the old maintainer or someone else took over maintainership again as my time is limited these days.
Upstream source: http://sourceforge.net/projects/ndiswrapper/
Patch: kernel-3.10.patch
AUR: ndiswrapper-1.58-16
Tested and working with linux-3.10.2 and 3.10.3 and a Realtek 8187Se.
Happy NDIS wrapping!

Maybe you might want to send an email to [arch-general] (or even [aur-general] since it was in [community] before).

Unable to open pseudo-tty with 2.6 kernel

I put the 2.6 kernel in on a few boxes for fun. One box at home, with Arch, has no problem, nor does a Slackware install on the same machine have a problem.
However, on a box at work, I cannot open xterms at all--if, for example, I do a start x with twm it won't open period. As root, I can open fluxbox and open an rxvt terminal.
As a user, I can open fluxbox but cannot open an rxvt terminal. Upon leaving X I see the message failed to open pseudo-tty. (The terminal will flash on the screen and disappear in X).
I figured I'd left something out in my .config file, or that something was wrong with permissions. However, checking it against the home boxs' .config and permissions indicates that this isn't the case. I haven't tested another flavor of Linux on this box, to see if the issue is Arch specific or not. I suspect it is not
The box in question is a Dell Dimension, a few years old, which, AFAIK has a standard Intel chipset. I'm guessing it's sometihng to do with the hardware, but not sure what the next step should be. Googling hasn't brought me any joy, the people with the same error messages are in different situations, (also from older kernels.)
Using the 2.4 kernel I don't have this problem. Does anyone have any idea what I'm overlooking here? It doesn't seem to be the obvious in filesystems or ptys in my .config--the only differences in configuration were adding a chipset for the ASUS board on the box at home and and different NICS. Support for the Intel chipset is compiled in (directly, not as module).
Thanks for any help.
Scott

This is embarrassing, but amusing enough to post, I thnk.
I went to add that information to a page I have up. I saw the info was already there. Apparently I researched this a little more thoroughly last time, and not only found the answer but had put it on my page.
Sigh. They say short term memory is the first thing to go--I forget the second, I just heard it recently.
Scott

Ndiswrapper problems.

Hi,
I installed Arch Linux 4 or 5 days ago and I am currently having a problem that is giving me headaches. I have searched the web over and over for a solution and I can't seem to find one.
I have a wireless card which is a DLink DWL-G510. I got this card working using the ndiswrapper and the WL138 Asus 64 bit drivers and everything was fine.
Then my system had a crash. Actually, I was stuck in a situation where 2 problems prevented me from rebooting in a nice way. I tried to shut down KDE and for reasons I have now fixed it would hang with a completely black screen. At the same time I was having a keyboard problem where I couldn't use the shift or control keys. Therefore I couldn't switch to a vc and reboot. I had to use the reset button on the computer.
Ever since that time I have been unable to get my card to work. I tried it with a Knoppix boot disc and it was able to detect and see the card using iwconfig on that, so I know its not the fault of the card. I think I must have corrupted something when I rebooted.
Currently I get one of two problems when I try to install. I go through ndiswrapper -i and it installs and ndiswrapper -l says the card has been detected. When I try to run modprobe ndiswrapper I get one of two situation.
1) I check dmesg and I see
ndiswrapper version 1.52 loaded (smp=yes, preempt=yes)
ndiswrapper (link_pe_images:576): fixing KI_USER_SHARED_DATA address in the driver
ndiswrapper: driver mrv8k64 (Marvell,06/08/2005,2.7.1.19) loaded
ACPI: PCI Interrupt Link [APC2] enabled at IRQ 17
ACPI: PCI Interrupt 0000:03:07.0[A] -> Link [APC2] -> GSI 17 (level, low) -> IRQ 17
ndiswrapper: using IRQ 17
ndiswrapper (mp_init:216): couldn't initialize device: C0000001
ndiswrapper (pnp_start_device:439): Windows driver couldn't initialize the device (C0000001)
ndiswrapper (mp_halt:259): device ffff810119f96700 is not initialized - not halting
ndiswrapper: device eth%d removed
ACPI: PCI interrupt for device 0000:03:07.0 disabled
ndiswrapper: probe of 0000:03:07.0 failed with error -22
usbcore: registered new interface driver ndiswrapper
NET: Registered protocol family 10
lo: Disabled Privacy Extensions
eth0: no IPv6 routers present
vmnet1: no IPv6 routers present
vmnet8: no IPv6 routers present
2) Sometimes immediately and sometimes using dmesg I will see the following message and I will be unable to remove ndiswrapper, so further testing requires a reboot, which is very annoying. The message in the system log is different from what I get, but it is something to do with a
windows driver cannot initialize device.
I have tried reloading the ndiswrapper and ndiswrapper-utils packages but that didn't seem to do much. I'm having trouble remembering some of the other things I've tried with this. Oh yeah, I tried the sources from the ndiswrapper sourceforge site but that didn't seem to do anything either.
Any ideas?
Daniel

Its funny, but in the process of doing this I was playing around with all kinds of things and reinstalling components to see if anything had been corrupted. In the process of doing this I tried the unstable kernel and then for some reason I lost ethernet. I couldn't get it to function in the regular kernel (I think it was still working for the new kernel), the arch install cd 2007.08.2, or the Knoppix 3.5.1 dvd. The cure was to reboot into windows and then reboot back into Linux. I wonder if the same thing would work for my wireless driver. Unfortunately the only windows I have install is 64 bit Vista and I don't have a functioning wireless driver for it so I cannot get it to work anywhere right now. Yes, I am aware that I am using the 64 bit ASUS driver in Linux but it says it is unable to start the device in Windows. This is not new, it has always happened.

Wifi on Surface Pro - installed with ndiswrapper but not working

Hi there guys.
I have installed Arch on a Surface Pro and most things work well.
The biggest problem so far is wifi - it comes with a 88w8797 Marvell Avastar chipset. I managed to find the drivers and used ndiswrapper to install them.
$ ndiswrapper -l
mwlu97w8 : driver installed
device (1286:2043) present (alternate driver: mwifiex_usb)
The ndiswrapper help page says that one should get rid of alternate drivers before enabling ndiswrapper but I have no clue where to start - that seems to be a kernel loaded module (link) but it really doesn't do much apparently.
I did 'modprobe ndiswrapper' but as you can see below, nothing seems to be really happening
# iwconfig
enp0s20u2u3 no wireless extensions.
lo no wireless extensions.
dmesg returns this on ndiswrapper
$ dmesg | grep ndiswrapper
[ 2.996565] ndiswrapper version 1.58 loaded (smp=yes, preempt=yes)
[ 4.230024] usbcore: registered new interface driver ndiswrapper
The gnome network manager, just like iwconfig, shows no able wireless.
I'm at a loss on what to do, any help is greatly appreciatted
Last edited by OttoRobba (2013-02-21 10:26:50)

The blacklisting was a good call as I had completely forgot to do so. Made a /etc/modprobe.d/blacklist.conf with 'install mwifiex_usb /bin/false' - nothing changed though, the wireless network still won't show.
# lsusb
Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 003 Device 003: ID 058f:6254 Alcor Micro Corp. USB Hub
Bus 003 Device 002: ID 1286:2043 Marvell Semiconductor, Inc.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 003: ID 045e:0795 Microsoft Corp.
Bus 002 Device 003: ID 045e:079c Microsoft Corp.
Bus 002 Device 004: ID 03eb:8209 Atmel Corp.
Bus 002 Device 005: ID 045e:0794 Microsoft Corp.
Bus 003 Device 006: ID 04e8:6863 Samsung Electronics Co., Ltd
# lspci
00:00.0 Host bridge: Intel Corporation 3rd Gen Core processor DRAM Controller (rev 09)
00:02.0 VGA compatible controller: Intel Corporation 3rd Gen Core processor Graphics Controller (rev 09)
00:14.0 USB controller: Intel Corporation 7 Series/C210 Series Chipset Family USB xHCI Host Controller (rev 04)
00:16.0 Communication controller: Intel Corporation 7 Series/C210 Series Chipset Family MEI Controller #1 (rev 04)
00:1a.0 USB controller: Intel Corporation 7 Series/C210 Series Chipset Family USB Enhanced Host Controller #2 (rev 04)
00:1b.0 Audio device: Intel Corporation 7 Series/C210 Series Chipset Family High Definition Audio Controller (rev 04)
00:1d.0 USB controller: Intel Corporation 7 Series/C210 Series Chipset Family USB Enhanced Host Controller #1 (rev 04)
00:1f.0 ISA bridge: Intel Corporation HM77 Express Chipset LPC Controller (rev 04)
00:1f.2 SATA controller: Intel Corporation 7 Series Chipset Family 6-port SATA Controller [AHCI mode] (rev 04)
00:1f.3 SMBus: Intel Corporation 7 Series/C210 Series Chipset Family SMBus Controller (rev 04)
It seems ndiswrapper is failing to load - I wonder if there is another module claiming the device?
#dmesg
[ 4.191249] ndiswrapper (import:232): unknown symbol: ntoskrnl.exe:'__chkstk'
[ 4.191274] ndiswrapper (import:232): unknown symbol: ntoskrnl.exe:'MmGetSystemRoutineAddress'
[ 4.191295] ndiswrapper (import:232): unknown symbol: NDIS.SYS:'NdisFreeIoWorkItem'
[ 4.191305] ndiswrapper (import:232): unknown symbol: NDIS.SYS:'NdisQueueIoWorkItem'
[ 4.191326] ndiswrapper (import:232): unknown symbol: NDIS.SYS:'NdisFreeMdl'
[ 4.191336] ndiswrapper (import:232): unknown symbol: NDIS.SYS:'NdisAllocateMdl'
[ 4.191346] ndiswrapper (import:232): unknown symbol: NDIS.SYS:'NdisAllocateNetBufferAndNetBufferList'
[ 4.191356] ndiswrapper (import:232): unknown symbol: NDIS.SYS:'NdisFreeNetBufferList'
[ 4.191366] ndiswrapper (import:232): unknown symbol: NDIS.SYS:'NdisFreeNetBufferListPool'
[ 4.191376] ndiswrapper (import:232): unknown symbol: NDIS.SYS:'NdisAllocateNetBufferListPool'
[ 4.191386] ndiswrapper (import:232): unknown symbol: NDIS.SYS:'NdisMAllocatePort'
[ 4.191403] ndiswrapper (import:232): unknown symbol: NDIS.SYS:'NdisMIdleNotificationComplete'
[ 4.191413] ndiswrapper (import:232): unknown symbol: NDIS.SYS:'NdisMIdleNotificationConfirm'
[ 4.191423] ndiswrapper (import:232): unknown symbol: NDIS.SYS:'NdisMFreePort'
[ 4.191432] ndiswrapper (import:232): unknown symbol: NDIS.SYS:'NdisMNetPnPEvent'
[ 4.191443] ndiswrapper (import:232): unknown symbol: NDIS.SYS:'NdisMIndicateReceiveNetBufferLists'
[ 4.191453] ndiswrapper (import:232): unknown symbol: NDIS.SYS:'NdisMSendNetBufferListsComplete'
[ 4.191463] ndiswrapper (import:232): unknown symbol: NDIS.SYS:'NdisMOidRequestComplete'
[ 4.191473] ndiswrapper (import:232): unknown symbol: NDIS.SYS:'NdisMIndicateStatusEx'
[ 4.191483] ndiswrapper (import:232): unknown symbol: NDIS.SYS:'NdisMSetMiniportAttributes'
[ 4.191493] ndiswrapper (import:232): unknown symbol: NDIS.SYS:'NdisSetOptionalHandlers'
[ 4.191504] ndiswrapper (import:232): unknown symbol: NDIS.SYS:'NdisAllocateMemoryWithTagPriority'
[ 4.191514] ndiswrapper (import:232): unknown symbol: NDIS.SYS:'NdisOpenConfigurationEx'
[ 4.191523] ndiswrapper (import:232): unknown symbol: NDIS.SYS:'NdisFreeTimerObject'
[ 4.191533] ndiswrapper (import:232): unknown symbol: NDIS.SYS:'NdisCancelTimerObject'
[ 4.191543] ndiswrapper (import:232): unknown symbol: NDIS.SYS:'NdisSetTimerObject'
[ 4.191599] ndiswrapper (import:232): unknown symbol: NDIS.SYS:'NdisAllocateIoWorkItem'
[ 4.191613] ndiswrapper (import:232): unknown symbol: NDIS.SYS:'NdisMRegisterMiniportDriver'
[ 4.191623] ndiswrapper (import:232): unknown symbol: NDIS.SYS:'NdisMDeregisterMiniportDriver'
[ 4.191648] ndiswrapper (import:232): unknown symbol: NDIS.SYS:'NdisAllocateTimerObject'
[ 4.191663] ndiswrapper (load_sys_files:199): couldn't prepare driver 'mwlu97w8'
[ 4.191827] ndiswrapper (load_wrap_driver:121): couldn't load driver 'mwlu97w8'
[ 4.191926] usbcore: registered new interface driver ndiswrapper

How to use ndiswrapper for a D-Link DWA-160?

I'm trying to get ndiswrapper working on my D-Link DWA-160 wireless USB dongle. The current driver, carl9170, is horrible - it's slow, unstable, and overheats the adapter. (The old driver, ar9170, worked like a dream - but got discontinued.)
I got ndiswrapper working on this back in Ubuntu, but I can't seem to get it working here. (I'm curretly just using a different adapter, but when using ndiswrapper, this adapter is my most powerful one.)
It seems that ndiswrapper hasn't been updated for the most recent kernel? The AUR looks like it's just been updated for the 3.10 kernel, but I'm on the 3.11 one. However, since I'm conpiling it from source, wouldn't tha take care of all issues?
Anyway, do I need to just give up this battle until ndiswrapper gets updated? Or is there something I can do in the meantime?
Last edited by ThePacman (2013-10-12 16:43:55)

journalctl -xn gives:
-- Logs begin at Fri 2013-10-11 14:17:23 CDT, end at Sun 2013-10-13 12:53:10 CDT. --
Oct 13 12:53:03 james-OptiPlex-GX620 systemd[1]: Starting Networking for netctl profile enp0s29f7u8-Zorakistan...
-- Subject: Unit netctl@enp0s29f7u8\x2dZorakistan.service has begun with start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Unit netctl@enp0s29f7u8\x2dZorakistan.service has begun starting up.
Oct 13 12:53:03 james-OptiPlex-GX620 network[22716]: Starting network profile 'enp0s29f7u8-Zorakistan'...
Oct 13 12:53:03 james-OptiPlex-GX620 network[22716]: The interface of network profile 'enp0s29f7u8-Zorakistan' is already up
Oct 13 12:53:03 james-OptiPlex-GX620 systemd[1]: netctl@enp0s29f7u8\x2dZorakistan.service: main process exited, code=exited, status=1/FAILURE
Oct 13 12:53:03 james-OptiPlex-GX620 systemd[1]: Failed to start Networking for netctl profile enp0s29f7u8-Zorakistan.
-- Subject: Unit netctl@enp0s29f7u8\x2dZorakistan.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Documentation: http://www.freedesktop.org/wiki/Software/systemd/catalog/be02cf6855d2428ba40df7e9d022f03d
-- Unit netctl@enp0s29f7u8\x2dZorakistan.service has failed.
-- The result is failed.
Oct 13 12:53:03 james-OptiPlex-GX620 systemd[1]: Unit netctl@enp0s29f7u8\x2dZorakistan.service entered failed state.
Oct 13 12:53:03 james-OptiPlex-GX620 sudo[22290]: pam_unix(sudo:session): session closed for user root
Oct 13 12:53:10 james-OptiPlex-GX620 sudo[22767]: james : TTY=pts/2 ; PWD=/home/james ; USER=root ; COMMAND=/usr/bin/journalctl -xn
Oct 13 12:53:10 james-OptiPlex-GX620 sudo[22767]: pam_unix(sudo:session): session opened for user root by james(uid=0)
Oct 13 12:53:10 james-OptiPlex-GX620 sudo[22767]: pam_unix(sudo:session): session closed for user root
I've made sure to modprobe -r carl9170, modprobe ndiswrapper, and ndiswrapper -l says everything's fine.
I've even tried ndiswrapper -a 07D1:3A09 dwarusb_xp, but to no avail.
Concerning the part where it sayn the interface is "already up", I've tried ip link set down dev enp0s29f7u8, but that didn't fix it (although the command seemed to succeed.)
Sometimes, when trying to use wifi-mine to start the connection, I get a few errors about "ioctl[SIOCSIWPMKSA]: Invalid argument". What does this mean?
EDIT: just tried unplugging the adapter and I got a kernel panic.
Last edited by ThePacman (2013-10-13 18:08:55)

Why modeprobe ndiswrapper produced and error?

Hello
These are the steps that I took to make OEL connect to the internet:
I downloaded ndiswrappers latest version.
I typed "su -c 'yum install kmod-ndiswrapper'"
the response was:
"setting up install process"
"setting up repositories"
however the error message was:
"cannot find a valid baseurl for repo: update"
Therefore I didn't use yum and proceeded as follows
1)created a directed named "ndiswrapper_drivers"
2)tar -zxvf ndiswrapper-1.47.tar.gz
3)make uninstall
4)make distclean
5)make
6)make install
NOTE: this gave two warnings:
a)'task_nice': (/ndiswrapper_drivers/ndiswrapper-1.47/ndiswrapper.ko) undefined!
b)this kernel seems to use 4k stack size option(CONFIG_4KSTACKS): many Windows dirver will not work with the option enabled . Disable CONFIG_4KSTACKS option recompile and install kernel
NOTE:Windows config file format changed since 1.5 you must reinstall windows driver if they wre installed before
7)ndiswrapper -i bcmwl5.inf
(driver now installed)
8)ndiswrapper -i bcmwl5.sys
(driver already installed)
9)ndiswrapper -l
(driver now present)
10)demod -a
11)modprobe ndiswrapper
FATAL: Error inserting ndiswrapper (/lib/modules/2.6.9-55.0.0.0.2ELsmp/misc/ndiswrapper.ko); unknown symbol in module or unknown parameter.
The error file ndiswrapper.0 file in step 11 seems to be the same error file in ndiswrapper.k0 file after step 6.
How do I correct this problem with ndiswrapper and how can I get "yum" to work?

The Linux kernel and all of its active device drivers are limited to a 4K stack space. The NDISwrapper may allow you to use some device drivers from Windows (tm) but these frequently assume that they may use much more stack space than is available under Linux. As a result, the system may crash or operate unpredictably.
There are valid performance and technical reasons for limiting the kernel to using only a 4K stack; this is why it is the delivered configuration. However, the choice of a 4K or 8K stack is a kernel compile-time option, so if you want to recompile your kernel and try that you can, although I personally do not recommend it.

Kernel26-beyond + ndiswrapper + wpa_supplicant [solved]

Hello!
A few problems with kernel-2.6.16-beyond and my network profile (ndiswrapper plus wpa2-psk).
Here we go:
- Running Arch 0.7.2, uptodate with current and extra repos.
- Installed kernel26beyond package and ndiswrapper-beyond.
kernel26beyond version: 2.6.16.beyond4.1-1
Ndiswrapper-beyond version: 1.16-1
- Edited the grub configuration, adding the new kernel:
title Arch Linux Beyond
root (hd0,1)
kernel /vmlinuz26beyond root=/dev/hda5 ro video=vesafb:ywrap,1280x800-16@60
initrd /initramfs-beyond.img
- Reboot to test the new kernel.
It seems the wifi profile doesn't start. Ok, let's see...
My wifi profile works OK with stock Arch kernel, but after the installation of kernel26 beyond the wpa socket directory (/var/run/wpa_supplicant) has dissapeared.
No problem, created it again and restart the network. Still no luck.
ndiswrapper-beyond seems to work fine:
$ ndiswrapper -l
bcmwl5 driver installed, hardware present
dmesg output:
ndiswrapper version 1.16 loaded (preempt=yes,smp=yes)
ndiswrapper: driver bcmwl5 (Broadcom,05/26/2005, 3.120.27.0) loaded
ACPI: PCI Interrupt 0000:06:02.0[A] -> GSI 21 (level, low) -> IRQ 22
ndiswrapper: using irq 22
wlan0: vendor: ''
wlan0: ndiswrapper ethernet device 00:14:a5:4e:11:27 using driver bcmwl5, 14E4:4319.5.conf
wlan0: encryption modes supported: WEP; TKIP with WPA, WPA2, WPA2PSK; AES/CCMP with WPA, WPA2, WPA2PSK
The wpa_supplicant configuration works fine with stock kernel:
$ cat /etc/wpa_supplicant.conf
ctrl_interface=/var/run/wpa_supplicant
ap_scan=1
network={
ssid="myssid"
proto=RSN
key_mgmt=WPA-PSK
pairwise=TKIP
group=TKIP
#psk="blah"
psk=encrypted blah
I have tried adding ndiswrapper to the modules array in /etc/rc.conf, the network doesn't start.
Later I have changed the file /etc/mkinitramfs.conf and generated a new initramfs-beyond.img, trying to enable ndiswrapper here and/or USB subsystem support, but the result was the same.
The *ONLY* solution I have found is booting the system with the beyond kernel, wait to the network init script to fail (it seems a dhcp timeout), log into the system and execute the following:
# killall wpa_supplicant
# /etc/rc.d/network restart
Any idea about why I have to kill wpa_supplicant to get the wifi working with it? As I said, this problem does't exist with the stock kernel, and I don't see any errors reported by wpa_supplicant.
Thanks in advance!
Regards,
miausX

Thanks for your reply, Phrodo_00.
I think it is using the correct ndiswrapper module (beyond).
Looking at the modinfo output:
$ modinfo ndiswrapper
filename: /lib/modules/2.6.16-beyond/misc/ndiswrapper.ko
license: GPL
version: 1.16
description: NDIS wrapper driver
Maybe this problem is related to the execution order of the commands (modprobe ndiswrapper, wpa_supplicant, dhcpcd) during boot.
Everything works fine after killing wpa_supplicant and restarting the network, the ndiswrapper module is loaded, wpa_suplicant is running as a daemon, etc.
$ ps -ef | grep wpa
root 4262 1 0 10:12 ? 00:00:00 wpa_supplicant -wB -i wlan0 -c /etc/wpa_supplicant.conf -D wext
$ ps -ef | grep dhcp
root 4274 1 0 10:12 ? 00:00:00 dhcpcd -t 30 -h portatil wlan0
$ lsmod | grep ndis
ndiswrapper 145004 0
usbcore 97696 6 ndiswrapper,hci_usb,usbhid,ohci_hcd,ehci_hcd
Regards,
miausX.

Ndiswrapper 1.5

Hello I been using Arch for about 2 months now, and I love it. I think is the only linux distribution that I been excited about.
BUT, I have a problem... remember those October 1 updates, well they make my ndiswrapper stop working in my laptop, my laptop completly stop working as I did a
modprobe ndiswrapper
well i follow what I found here and in other forums, uninstall ndiswrapper and install new version. So, I follow the uninstall procedures from the ndiswrapper page with no luck.
So i need help uninstalling the whole thing (ndiswrapper version 1.4 something) and installing the 1.5 to see if i can fix my problem
Thank you for your time

creatorx wrote:phrakture --- can u detail a little more, because am very much a newbie to linux too.
The package is in the [community] repo. If you don't have this available, edit /etc/pacman.conf and uncomment the community lines near the bottom.
After that, run "pacman -Sy" to refresh your repo db and then run "pacman -Ss ndiswrapper" to search for the ndiswrapper packages (the -bin package is a dependancy of the others, so I can provide multiple modules, when I get a chance)

Wireless w/ ndiswrapper; fails to get ip from dhcp

I've got a DWL-G510 and I recently used ndiswrapper to install the win2k drivers. It confirms 'driver installed, hardware present', iwlist can scan and pick up my access point, put in the WEP key, and associate the access point successfully (It comes up with the MAC Address of the router). However, then I go the old
ifconfig wlan0 up
dhcpcd wlan0
and it fails to receive an IP; it just sits there for a few minutes, does nothing, and downs the interface in ifconfig. And yes, DHCP is set up, as ethernet connections work fine. The wireless also works in windows, so it's not with that either. Is there any step that I've missed? (Yes, I've read the ndiswrapper installation wiki page)

I boot:
[root@archbox tom]# ifconfig
eth0 Link encap:Ethernet HWaddr 00:11:D8:A2:A2:C0
inet addr:10.0.0.38 Bcast:10.255.255.255 Mask:255.0.0.0
UP BROADCAST NOTRAILERS RUNNING MULTICAST MTU:1500 Metric:1
RX packets:7 errors:0 dropped:0 overruns:0 frame:0
TX packets:8 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:1144 (1.1 Kb) TX bytes:1626 (1.5 Kb)
Interrupt:16
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:4 errors:0 dropped:0 overruns:0 frame:0
TX packets:4 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:280 (280.0 b) TX bytes:280 (280.0 b)
I modprobe ndiswrapper and scan the networks:
[root@archbox tom]# iwlist wlan0 scan
wlan0 Scan completed :
Cell 01 - Address: 00:15:E9:03:F7:10
ESSID:"homewlan"
Protocol:IEEE 802.11g
Mode:Managed
Frequency:2.437 GHz (Channel 6)
Quality:0/100 Signal level:-44 dBm Noise level:-256 dBm
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 6 Mb/s
9 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
48 Mb/s; 54 Mb/s
Extra:bcn_int=100
Extra:atim=0
I associate the access point:
[root@archbox tom]# iwconfig wlan0 key ########## essid homewlan
I check to make sure it's configured fine:
[root@archbox tom]# iwconfig
lo no wireless extensions.
wlan0 IEEE 802.11g ESSID:"homewlan"
Mode:Managed Frequency:2.437 GHz Access Point: 00:15:E9:03:F7:10
Bit Rate=54 Mb/s Tx-Power:20 dBm Sensitivity=-121 dBm
RTS thr=2347 B Fragment thr=2346 B
Encryption key:####-####-## Security mode:restricted
Power Management:off
Link Quality:100/100 Signal level:-44 dBm Noise level:-256 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0
eth0 no wireless extensions.
eth1 no wireless extensions.
sit0 no wireless extensions.
I bring it up:
[root@archbox tom]# ifconfig wlan0 up
[root@archbox tom]# ifconfig
eth0 Link encap:Ethernet HWaddr 00:11:D8:A2:A2:C0
inet addr:10.0.0.38 Bcast:10.255.255.255 Mask:255.0.0.0
inet6 addr: fe80::211:d8ff:fea2:a2c0/64 Scope:Link
UP BROADCAST NOTRAILERS RUNNING MULTICAST MTU:1500 Metric:1
RX packets:325 errors:0 dropped:0 overruns:0 frame:0
TX packets:283 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:363403 (354.8 Kb) TX bytes:74604 (72.8 Kb)
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:4 errors:0 dropped:0 overruns:0 frame:0
TX packets:4 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:280 (280.0 b) TX bytes:280 (280.0 b)
wlan0 Link encap:Ethernet HWaddr 00:15:E9:32:48:E6
inet6 addr: fe80::215:e9ff:fe32:48e6/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:1 errors:0 dropped:0 overruns:0 frame:0
TX packets:12 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:60 (60.0 b) TX bytes:2996 (2.9 Kb)
Interrupt:19 Memory:d0000000-d0008000
I dhcp it:
[root@archbox tom]# dhcpcd wlan0
ifconfig then returns to its initial state (ie. without wlan0 as active).

Ndiswrapper, dhcp, internet headaches.

I recently got a nintendo wii (!, woohoo) and it didn't immediately work with my wireless internet. I read up on it and was told to upgrade & reset my router. I did it, and now the wii works, and all my Windows computers work with the net perfectly as well.
Nevertheless, after this router upgrade, Arch's internet just won't work. I use ndiswrapper with the netgear wg121 USB adapter, with the netgear wgr614v4 router.
My network's essid is "mnet", so to load my network, before the upgrade, I would just:
modprobe ndiswrapper
iwconfig wlan0 essid mnet
dhcpcd wlan0
...and that would be the end of it.
Now, however, I can't connect to anything when I do that. It still detects the network -- i.e., when running iwconfig I can see my network, my router's mac address, etc. dhcpcd doesn't give me a lot of helpful information as to what the problem is--It just runs and closes. I've tried numerous variations of it, i.e., dhcpcd -G 192.168.0.1 wlan0, etc., but nothing usually works. Here's the deal: sometimes it does! On occasion, after running dhcpcd numerous times and playing with it for 15+ minutes, I can get it to connect to the internet, but there is no way to tell why! It just "decides" randomly to connect occassionally, and it's not like I issued a different command -- each time it "decides" to connect, it was because I issued a command I must have done at least 10 times before.
dhclient gives a little more info--I found out that I was being set up with 192.168.0.5, every time--whether the net worked or not. This is kind of signifigant because I actually set up my router to have my mac address always get 192.168.0.5, so it seems dhcp is actually working.
So the question is, why would the internet always work on windows, and rarely work on arch? What could be the difference with the upgraded router?
Thanks for any ideas...

Okay then. I just tried multiple ndiswrapper versions -- 1.35, 1.34 (what I've been using forever), 1.33, 1.32, 1.28, and 1.8. None of them worked. (BTW, I've been compiling ndiswrapper from source forever, and not using the pacman versions. I did this before the network stopped working, too, so I didn't think this could possibly be a problem?)
I didn't expect ndiswrapper to work as good as native windows drivers! I just found it weird that the driver would suddenly stop working in linux, and keep working in windows/wii.
I tried "ifconfig wlan0 up" and just about a billion other commands.
Now, I tried a bunch of really interesting tests: First, I connected to a neighbor's network. And it worked. Second, I installed ubuntu and ndiswrapper 1.8 on that. And it worked. Why would it work with ubuntu consistently, and not with arch? That seemed odd.
And now, the logs:
iwconfig - broken, working. (I didn't add in the lo, eth0, sit0 on the second one; they weren't being picked up by iwconfig > file, so I added them in on the first one, but they were showing up when I ran the command).
iwlist wlan0 scan - broken, working.
dmesg - broken, working (I actually unmodprobe'd ndiswrapper and remodprobed it right before it started working. It's weird tricks like that that get it to work, but it's not consistent, like I said).
ping google.com - broken (just in case it might help; I doubt it will, but that pops up after about 30 seconds when the internet's not working).
Notice how the broken/working contents for almost everything is pretty much the same. That's why I figured it would be useless to post it!
Any ideas now, especially about how it would work on ubuntu and not arch (which is a little more fair then comparing arch to windows, I guess)?
Thanks again!
Last edited by tm8992 (2007-01-29 17:37:41)

Ndiswrapper usb support

Is there a way to disable usb support in ndiswrapper ?
Edited:Forget it. I've compile it from the source.
Last edited by mvinnicius (2008-08-10 06:01:52)

Thanks for your reply, Phrodo_00.
I think it is using the correct ndiswrapper module (beyond).
Looking at the modinfo output:
$ modinfo ndiswrapper
filename: /lib/modules/2.6.16-beyond/misc/ndiswrapper.ko
license: GPL
version: 1.16
description: NDIS wrapper driver
Maybe this problem is related to the execution order of the commands (modprobe ndiswrapper, wpa_supplicant, dhcpcd) during boot.
Everything works fine after killing wpa_supplicant and restarting the network, the ndiswrapper module is loaded, wpa_suplicant is running as a daemon, etc.
$ ps -ef | grep wpa
root 4262 1 0 10:12 ? 00:00:00 wpa_supplicant -wB -i wlan0 -c /etc/wpa_supplicant.conf -D wext
$ ps -ef | grep dhcp
root 4274 1 0 10:12 ? 00:00:00 dhcpcd -t 30 -h portatil wlan0
$ lsmod | grep ndis
ndiswrapper 145004 0
usbcore 97696 6 ndiswrapper,hci_usb,usbhid,ohci_hcd,ehci_hcd
Regards,
miausX.

Setting-up Wireless Card (Using Ndiswrapper) [Solved]

I've recently setup Arch-Linux on my laptop and I am now trying to get my wireless card to work. I've got this card to work with Ubuntu Linux using Ndiswrapper, so I know it should be possible. The card is 'Atheros AR5007EG' and my laptop model is a Toshiba p205-s6307.
I have the drivers that I used on Ubuntu and I installed Ndiswrapper from source. I then went through the following steps (I didn't document my original driver installation, so I will just write what the commands now output. The installation had no errors):
[tristan@asuka wdriver]$ pwd
/home/tristan/wdriver
[tristan@asuka wdriver]$ ls
ar5211.sys net5211.inf
[tristan@asuka wdriver]$ sudo ndiswrapper -i net5211.inf
Password:
driver net5211 is already installed
[tristan@asuka wdriver]$ sudo ndiswrapper -m
module configuration already contains alias directive
[tristan@asuka wdriver]$ sudo modprobe ndiswrapper
[tristan@asuka wdriver]$ iwconfig
lo no wireless extensions.
eth0 no wireless extensions.
To my knowledge, this should work. But, unfortunately 'wlan' is not showing. I was hoping someone might have some tips or advice to help me resolve this. Any information will greatly be appreciated. If you need anymore information about my system, please ask!
Thank you very much.
Last edited by azurepancake (2009-01-27 05:43:45)

I've been doing a little experimenting and still haven't been able to get wlan0 up. I uninstalled the driver and reinstalled it using the ArchWiki:
ndiswrapper -i filename.inf
ndiswrapper -l
ndiswrapper -m
depmod -a
(Add 'ndiswrapper' to '/etc/rc.conf' modules section)
modprobe ndiswrapper
Still nothing.
Results of ndiswrapper -l:
net5211 : driver installed
device (168C:001C) present (alternate driver: ath5k)
But, I have found a few things that might be related to the problem.
When I attempt to run 'ndiswrapper -m' - I get the following error:
[tristan@asuka ~]$ ndiswrapper -m
module configuration contains directive install pci:v0000168Cd00000013sv*sd*bc*sc*i* /sbin/modprobe ndiswrapper
;you should delete that at /usr/sbin/ndiswrapper line 868, <MODPROBE> line 4.
module configuration contains directive install pci:v0000168Cd00000013sv00000406sd00001468bc*sc*i* /sbin/modprobe ndiswrapper
;you should delete that at /usr/sbin/ndiswrapper line 868, <MODPROBE> line 5.
module configuration contains directive install pci:v0000168Cd00000013sv00000407sd00001468bc*sc*i* /sbin/modprobe ndiswrapper
;you should delete that at /usr/sbin/ndiswrapper line 868, <MODPROBE> line 6.
module configuration contains directive install pci:v0000168Cd00000013sv00000408sd00001468bc*sc*i* /sbin/modprobe ndiswrapper
;you should delete that at /usr/sbin/ndiswrapper line 868, <MODPROBE> line 7.
module configuration contains directive install pci:v0000168Cd00000013sv00001025sd0000168Cbc*sc*i* /sbin/modprobe ndiswrapper
;you should delete that at /usr/sbin/ndiswrapper line 868, <MODPROBE> line 8.
module configuration contains directive install pci:v0000168Cd00000013sv00001026sd0000168Cbc*sc*i* /sbin/modprobe ndiswrapper
This pretty much repeats its self for quite a bit.
I've noticed that when I boot my system up, it complains about the following:
FATAL: Module ath_pci not found
FATAL: Module ath_hal not found
FATAL: Module wlan not found
I found a post about my particular card saying to blacklist ath_pci and ath_hal. So I added the following to my /etc/modprobe.d/framebuffer_blacklist
blacklist ath_pci
blacklist hal_pci
Still no luck. So I then noticed that these were part of my modules in /etc/rc.conf:
So I then removed them, making my MODULES line look like so:
MODULES=(r8169 ath5k wlan snd-mixer-oss snd-pcm-oss snd-hwdep snd-page-alloc sn$
ndiswrapper)
I'm afraid this hasn't resolved the issue yet. If anyone has any advice at all, please share!
Last edited by azurepancake (2009-01-26 22:10:04)

Cannot modprobe (where are the modules?)

This is driving me crazy, and I don't understand how things work well enough to figure out what's going on. Usually after installing an OS, i just do a serious of "modprobe fan", "modprobe thermal", "modprobe battery", etc. But when I try to run them, I get:
# modprobe thermal
FATAL: Module thermal not found.
# locate thermal
/usr/src/linux-2.6.10-ARCH/include/config/x86/mce/p4thermal.h
/usr/src/linux-2.6.10-ARCH/include/config/acpi/thermal.h
Looking in Google, it seems that I want a thermal.ko file under
/lib/modules/2.6.10-ARCH/..... but it's not there. Same goes for fan, battery, etc.. Why am I missing these modules?

kth5 wrote:
running
modprobe /lib/modules/2.6.10-ARCH/kernel/drivers/cpufreq/cpufreq_ondemand.ko
will most probably not work! in order to probe a arbitary file as a module use insmod.
:oops: You learn something new everyday. That explains hours worth of frustration in the past heh...
kth5 wrote:
but instead you should really do this in a root-shell:
modprobe cpufreq_ondemand
I seem to be using 2.6.10.. out of curiosity, would I be able to roll back to 2.6.9 using pacman? How would I do that? Just to test things
to roll back you simply need the old arch-pkg-tarball and run "pacman -U" on it
Awesome, modprobing all four modules worked! My laptop is now running at full speed again. Just need to add them to the rc.conf file and I'm good to go. Thanks so much kth5! I'm so excited to be using Arch

Unable modprobe ndiswrapper on 2.6.12.5 kernel

Similar Messages

Maybe you are looking for