-   Linux - Wireless Networking (
-   -   Problem getting ndiswrapper to work FC6 (

woodpecka_04 05-16-2007 07:18 AM

Problem getting ndiswrapper to work FC6
Hey, I have recently installed ndiswrapper, from what I can tell successfully:

ndiswrapper -l gives me:
bcmwl5 : driver installed
device (14E4:4312) present (alternate driver: bcm43xx)

However, the light for my Wireless fails to come on

I then try and activate the wireless network eth1 and dmesg gives output that contains alot about the bcm43xx driver and I have read this one is not as good as the bcmwl5 that I need to use.

I checked ./iwconfig and the eth1 network comes up with an entry like:

eth1 IEEE 802.11 b/g ESSID "" blah blah blah

However, the wireless still doesnt work.

I decided to blacklist the bcm43xx driver in the hope it would stop using it. Interestingly enough when I restarted the wireless light came on!? But then when I checked iwconfig eth1 did not appear anymore - just lo and eth0.

Help me please!!!

Lenard 05-16-2007 08:56 AM

Did you perhaps forget to also edit the /etc/modprobe.conf file eth1 line entry??

Recreate the missing /etc/sysconfig/network-scripts/ifcfg-eth1 file, sample below;

CHANNEL= <<--adjust to the channel shown by the command:iwlist eth1 scan

FYI: with the freshrpms-release rpm package installed:

yum install dkms dkms-ndiswrapper

And you will not need to rebuild the ndiswrapper module again after a kernel update. Extra points for rebuilding and installing the dkms-ndisswrapper for the latest release version of ndiswrapper. Just grab the source rpm file and the latest ndiswrapper source. Edit the spec file from the source rpm package to reflect the latest released version and build;

rpmbuild -ba --define 'dist .fc6' <the spec file name here>

If you have a problem then; yum install rpm-build

woodpecka_04 05-16-2007 09:27 AM

Right well I have just changed the modprobe.conf
I presume you mean the line that read:
alias eth1 bcm43xx

So I have changed the bcm43xx to bcmwl5

Restarted but nothing changed, by dmesg says the following when I try and connect:
bcm43xx: set security called .level = 0, .enabled = 0, .encrypt = 0
SoftMAC: Associate: Scanning for networks first
SoftMAC: Associate: Failed to initiate scan. Is device up?
bcm43xx: PHY connected
bcm43xx: Error: Microcode "bcm43xx_microcode5.fw" not available or load failed
bcm43xx: core_up for active 802.11 core failed (-2)

I will try adding the script you mentioned now

Thanks for getting back to me

Lenard 05-16-2007 09:41 AM

Nope change the line to: alias eth1 ndiswrapper

Then restart the network after creating the ifcfg-eth1 file;

service network restart

intricatic 05-16-2007 09:42 AM

Are you sure you're using the correct firmware for your chipset?

woodpecka_04 05-16-2007 10:06 AM

Yes I am sure the firmware is right

Okay let me update where I am up to:

- I have re-blacklisted the bcm43xx drivers
- I have modified the modprobe.conf as above
- I have also changed the line in /etc/modprobe.d/ndiswrapper
alias wlan0 ndiswrapper to alias eth1 ndiswrapper
(not sure if that was the right thing to do or not - wlan0 seemed quite useless though)
- I then restarted and thankfully the wireless light is now on
- iwconfig shows the expected eth1 interface as before (so this is an improvement :D)
- The eth1 script is still there, but when I scan with iwlist is says no scan results so I don't think I can set the channel properly
- When I now try and enable the network through system-network-config I get the following output:
Error for wireless request "Set Mode" (8B06) SET failed on device eth1; Invalid argument
- Then when I look at my dmesg I have the following output:
ADDRCONF(NETDEV_UP): eth1: link is not ready

Now then, reading what Lenard just posted:
"Nope change the line to: alias eth1 ndiswrapper"
Do I have to change it to that line as I stated above (where previously it was alias wlan0 ndiswrapper) in /etc/modprobe.d/ndiswrapper?

Okay I will see what happens when I use Lenard's suggestion. Please bear with me - i've been trying to get this thing working for a while now. If any of the steps I have taken above are wrong then please tell me lol.

intricatic 05-16-2007 10:26 AM

Press the wireless button. ;)

I had the same problem when I upgraded Ubuntu, from the sounds of it. Took me about a week to figure it out, too.

woodpecka_04 05-16-2007 10:39 AM

Right I just made that change that Lenard metioned

Unfortunately there seems to be no change in results, the light still comes on but I am receiving the same messages from dmesg and system-config-network.

I noticed that the encryption on the wireless network I am trying to connect to is WPA-PSK encrypted, is ndiswrapper only good for WEP encryption or will it not matter?

I wish it was as easy as pressing the wireless button! Maybe one day it will be...

Lenard 05-16-2007 10:54 AM

Why not show use which Broadcom chipset you have, some work just fine with the bcm43xx driver and others do not.

/sbin/lscpi -v

If your chipset is OK then you need to install the firmware from he same file you used with ndiswrapper using the firmware cutter package;

The good/bad bcm43xx list:
The bcm43xx-fwcutter can be installed by: yum install bcm43xx-fwcutter
The firmware is installed by typing: bcm43xx-fwcutter -w /lib/firmware <the file name here>

intricatic 05-16-2007 11:10 AM

That's about how much of a problem it was for me... lol

WPA, I think you need wpa_supplicant, but if you have the ability, set it to WEP and it should work OK. I've personally never played around with WPA on ndiswrapper, but it is do-able.

You're saying that "iwlist ifname scan" gives you no results, though? It should find the network regardless of encryption.

intricatic 05-16-2007 11:14 AM

Like I said, when I upgraded Ubuntu recently I had a problem that sounds exactly like this -- the wireless looked like it should be working, the firmware loaded properly, etc... and the interface was showing up on iwconfig, but it wouldn't do anything on an iwlist.

Pressing FN + F2 (wireless button) got it working like a charm instantly.

woodpecka_04 05-16-2007 11:29 AM

Okay good news is some progress has been made!

I messed around with the modprobe.conf file as Lenard suggested, eventually I am now up to the stage where iwlist eth1 scan is giving me some results! Horaahhh!

However, at the moment it is only picking up my neighbours WLAN's and not mine, and yes they are encrypted so I can't even "borrow" them.

I am hoping that after a few tries my network will eventually come up.

What commands should I be using though if (and hopefully when) it comes up? The essid of the network is "woody"

Thanks alot for all of your help so far

P.S I would love to be using yum but I have no internet on FC6 - thats why I'm trying to sort things out. I keep having to reboot into Windoze to post these messages lol.

Lenard 05-16-2007 12:16 PM

Remember this;

CHANNEL= <<--adjust to the channel shown by the command:iwlist eth1 scan

Change the ESSID to ESSID=woody

FYI: disable encryption on your wireless router until you see if you get a connection.
FYI: both the wireless router and the Linux wireless device must use the same encryption level 64-bit or 128-bit. The default is 128-bit in Linux.

FYI: it does not matter the alias name for the device as long as ever file uses the same name.

woodpecka_04 05-16-2007 02:02 PM

Hey, I've managed to get my home network to show up and I turned the encryption off but it still doesnt seem to connect.

The commands I am using are:
./iwconfig eth1 essid woody channel 11
./dhclient eth1

I don't know what is meant to happen i.e. does it tell me I am connected or what?

What am I doing wrong?

EDIT: Okay I have found it works with no encryption when I restart - wow internet on linux! Im just going to try turning encryption back on

intricatic 05-16-2007 03:32 PM

Awesome! :D

Like I said, you'll probably need wpa_supplicant to get the WPA encryption to work.

All times are GMT -5. The time now is 01:47 PM.