Thread: [Ndiswrapper-general] ndiswrapper failing on Fedora 7
Status: Beta
Brought to you by:
pgiri
From: Huub <huu...@gm...> - 2007-07-23 07:00:13
|
Hi, After reinstalling Fedora 7 and ndiswrapper 1.47 I can't get wlan0 to work. This is my output: > $ /usr/sbin/ndiswrapper -l > net8180 : driver installed > device (10EC:8180) present > $ /usr/sbin/ndiswrapper -m > module configuration already contains alias directive > $ /sbin/iwlist wlan0 scanning > wlan0 Interface doesn't support scanning. > $ /sbin/iwconfig > lo no wireless extensions. > > eth0 no wireless extensions. Rebooting doesn''t change anything. Any advise on next steps? Thanks for helping out. |
From: Pavel R. <pr...@gn...> - 2007-07-23 13:30:47
|
On Mon, 2007-07-23 at 08:32 +0200, Huub wrote: > Hi, > > After reinstalling Fedora 7 and ndiswrapper 1.47 I can't get wlan0 to > work. This is my output: > > > $ /usr/sbin/ndiswrapper -l > > net8180 : driver installed > > device (10EC:8180) present > > > $ /usr/sbin/ndiswrapper -m > > module configuration already contains alias directive > > > $ /sbin/iwlist wlan0 scanning > > wlan0 Interface doesn't support scanning. That's a misleading message. I think you don't have wlan0 at all. > > $ /sbin/iwconfig > > lo no wireless extensions. > > > > eth0 no wireless extensions. Otherwise it would appear here. > Rebooting doesn''t change anything. Any advise on next steps? Make sure that the "ndiswrapper" module is loaded. Check "lsmod" output. Try loading "ndiswrapper" manually first, as the INSTALL file suggests. Then check kernel log for the messages from the driver using the "dmesg" command. -- Regards, Pavel Roskin |
From: Huub <huu...@gm...> - 2007-07-24 06:02:01
|
> > Make sure that the "ndiswrapper" module is loaded. Check "lsmod" > output. Try loading "ndiswrapper" manually first, as the INSTALL file > suggests. > > Then check kernel log for the messages from the driver using the "dmesg" > command. > Ok. "lsmod" didn't show ndiswrapper. According to INSTALL I should "modprobe ndiswrapper", which claims # modprobe ndiswrapper FATAL: Module ndiswrapper not found. Then: # find / -name ndiswrapper.ko /lib/modules/2.6.21-1.3228.fc7/misc/ndiswrapper.ko /home/huub/ndiswrapper-1.47/driver/ndiswrapper.ko # modprobe ndiswrapper FATAL: Module ndiswrapper not found. # modprobe /lib/modules/2.6.21-1.3228.fc7/misc/ndiswrapper.ko FATAL: Module /lib/modules/2.6.21_1.3228.fc7/misc/ndiswrapper.ko not found. # modprobe /home/huub/ndiswrapper-1.47/driver/ndiswrapper FATAL: Module /home/huub/ndiswrapper_1.47/driver/ndiswrapper not found. Any suggestions? |
From: Huub <huu...@gm...> - 2007-07-24 07:47:01
|
> > depmod -a > modprobe ndiswrapper FATAL: Module ndiswrapper not found. > > or > > cd /lib/modules/2.6.21-1.3228.fc7/misc/ > modprobe ndiswrapper > FATAL: Module ndiswrapper not found. > or > > insmod /lib/modules/2.6.21-1.3223.fc7/misc/ndiswrapper.ko insmod: error inserting 'ndiswrapper.ko': -1 Invalid module format I guess I better reinstall ndiswrapper and try from the beginning. |
From: Huub <huu...@gm...> - 2007-07-24 10:38:43
|
> > AFAIK, this generally happens when: > > a) you're not running the kernel that the module was built for. > Turns out this was the case. Now I have this: # iwconfig lo no wireless extensions. eth0 no wireless extensions. wlan0 IEEE 802.11b ESSID:off/any Mode:Auto Frequency:2.412 GHz Access Point: Not-Associated Bit Rate=11 Mb/s Tx-Power:20 dBm Sensitivity=0/3 RTS thr=2432 B Fragment thr=2432 B Encryption key:off Power Management:off Link Quality:0 Signal level:0 Noise level:0 Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 Tx excessive retries:0 Invalid misc:0 Missed beacon:0 Just can't get it configured through NetworkManager (Fedora) yet. |
From: Huub <huu...@gm...> - 2007-07-25 05:32:58
|
> Huub, > > Make sure you've got the latest version of NetworkManager (0.6.5) > because it fixes a lot of really basic issues that shouldn't have arisen > in the first place. If that isn't an issue, try manually configuring the > device using iwconfig commands. man iwconfig should have plenty of > details. :) > Oops, my mistake. The tool I'm using is System-config-network vs. 1.3.96. And I have NetworkManager 0.6.5 installed. I did try manually configuring, but some of the arguments didn't change. As yet, no idea why. |
From: Huub <huu...@gm...> - 2007-07-25 12:39:45
|
> Make sure you have the latest windows driver for your card. And the latest version of ndiswrapper. I've had similar issues in the past which got resolved with upgrades. Some cards aren't fully supported, or otherwise quirky, so check the wiki on it's status. I used to have to set the ESSID before all else, or my card wouldn't let me change it. Just one of my quirks that isn't a quirk anymore after upgrades. And there's that 32 bit driver vs. 64 bit driver thing. > I'm using ndiswrapper-1.47 and the Realtek WindowsXP driver v.1.73. As far as I know these are the latest versions. |
From: Huub <huu...@gm...> - 2007-07-26 10:42:55
|
Another thing that is pretty odd: according to the installationguide, "ndiswrapper -m" loads "alias wlan0 ndiswrapper" into /etc/moprobe.d/ndiswrapper. That it did with mine as well. But, everytime I boot, "ifconfig -a" doesn't show wlan0 until I manually do "modprobe ndiswrapper". This isn't right, right? |
From: James S. <Sha...@ea...> - 2007-07-24 07:36:05
|
> Ok. "lsmod" didn't show ndiswrapper. According to INSTALL I should > "modprobe ndiswrapper", which claims > > # modprobe ndiswrapper > FATAL: Module ndiswrapper not found. > > Then: > > # find / -name ndiswrapper.ko > /lib/modules/2.6.21-1.3228.fc7/misc/ndiswrapper.ko > /home/huub/ndiswrapper-1.47/driver/ndiswrapper.ko > > # modprobe ndiswrapper > FATAL: Module ndiswrapper not found. depmod -a modprobe ndiswrapper or cd /lib/modules/2.6.21-1.3228.fc7/misc/ modprobe ndiswrapper or insmod /lib/modules/2.6.21-1.3223.fc7/misc/ndiswrapper.ko This assumes that 2.6.21-1.3228.fc7 is the current running kernel(`uname -r`). And that the modules was compiled with the same version of gcc. And that you're doing so as root. And all that jazz. |
From: James S. <Sha...@ea...> - 2007-07-24 09:41:20
|
> > insmod /lib/modules/2.6.21-1.3223.fc7/misc/ndiswrapper.ko > > insmod: error inserting 'ndiswrapper.ko': -1 Invalid module format > > I guess I better reinstall ndiswrapper and try from the beginning. AFAIK, this generally happens when: a) you're not running the kernel that the module was built for. $ uname -r or b) the module was compiled by a different compiler version, than the one used for the currently running kernel. Or something else strange along those lines like 32 bit vs. 64 bit. If lilo is your boot loader, it might be as simple as rerunning lilo and rebooting to ensure that you're running the kernel that you think you're running. Or it could be something less benign. There's ways to force it to load(not to imply usability) by disabling version checking in the kernel, but you really shouldn't have to do that. |
From: Andrew D. <lin...@wi...> - 2007-07-25 02:32:55
|
> Just can't get it configured through NetworkManager (Fedora) yet. > > Huub, Make sure you've got the latest version of NetworkManager (0.6.5) because it fixes a lot of really basic issues that shouldn't have arisen in the first place. If that isn't an issue, try manually configuring the device using iwconfig commands. man iwconfig should have plenty of details. :) ~~ Andrew D. |
From: James S. <Sha...@ea...> - 2007-07-25 11:58:02
|
> I did try manually configuring, but some of the > arguments didn't change. As yet, no idea why. Make sure you have the latest windows driver for your card. And the latest version of ndiswrapper. I've had similar issues in the past which got resolved with upgrades. Some cards aren't fully supported, or otherwise quirky, so check the wiki on it's status. I used to have to set the ESSID before all else, or my card wouldn't let me change it. Just one of my quirks that isn't a quirk anymore after upgrades. And there's that 32 bit driver vs. 64 bit driver thing. |
From: James S. <Sha...@ea...> - 2007-07-25 15:10:57
|
> I'm using ndiswrapper-1.47 and the Realtek WindowsXP > driver v.1.73. As far as I know these are the latest > versions. Some laptops have power buttons specific to the wifi card. On mine it's a blue button next to the power button. On others it's an Fn + radio tower button(a graphic on one of the F# keys). When toggled off, it exhibits the behavior you've described. When toggle on, it works normally. If I toggle it on mine, I have to unload and reload ndiswrapper, after toggling to on, to get it working again. This might not be your issue, but it might. Best of Luck. |
From: James S. <Sha...@ea...> - 2007-07-26 14:56:36
|
> everytime I boot, "ifconfig -a" doesn't show wlan0 until I manually do > "modprobe ndiswrapper". This isn't right, right? It is right if you don't have your system configured to load ndiswrapper at boot. Normally you put a single line "ndiswrapper" in /etc/modules. Although it may differ on your system and be /etc/modules.autoload or a variation. You can also add the modprobe to a bootup script, preferably at a point before your distro tries to configure the device. Various ways, if ndiswrapper was part of the kernel, you could compile it into the kernel and not worry about it. Unless you need to unload/reload it like I do. In theory with the /etc/modprobe.d/ and/or /etc/modutils.d/ entry the kernel will autoload the modules when you try to use it, like setting the essid. Although I've only be able to get that to actually happen on a few systems. HTH |
From: Huub <huu...@gm...> - 2008-01-10 11:04:59
|
> It is right if you don't have your system configured to load ndiswrapper at boot. Normally you put a single line "ndiswrapper" in /etc/modules. Although it may differ on your system and be /etc/modules.autoload or a variation. You can also add the modprobe to a bootup script, preferably at a point before your distro tries to configure the device. > > Various ways, if ndiswrapper was part of the kernel, you could compile it into the kernel and not worry about it. Unless you need to unload/reload it like I do. In theory with the /etc/modprobe.d/ and/or /etc/modutils.d/ entry the kernel will autoload the modules when you try to use it, like setting the essid. Although I've only be able to get that to actually happen on a few systems. > > HTH Now, being several months and an upgrade to F8 later, I've tried once again. And for some reason it works...but I have no idea about the cause. |