Wireless Issues

Steedie · 19 Jan 2008 at 16:26

Hey guys

Sorry for another thread

I just can't connect using my wireless card at all, it's driving me mad.

I've downloaded ndiswrapper, installed it using a tutorial and ran everything correctly, ndiswrapper shows that both the driver and hardware is present

So I went into Network Config and it found my wireless card in there to which I installed. But now, it comes up with the error message

"SIOCSIFFLAGS: file or directory not found"

I looked into this problem and found it is due to missing firmware, which I downloaded from the prism54 site which was recommended. Got the firmware, put it in the folder /etc/firmware first, same problem, then /lib/firmware and again same problem

This is really getting to me now as I really wanna get my Linux PC online but

Just no joy

ifconfig wlan0 up is the command that gives the SIOCSIFFLAGS error by the way

Also, it's not conflicting IRQ address's either which is the other problem associated with that error as I ran a command to check IRQ addresses and thats all ok

If anyone can help you will be considered Linux gods lol

Steedie · 19 Jan 2008 at 17:50

Ok I've installed the drivers and firmware using b43xx-fwcutter

But now in network config, it's recognised as the correct device and exact model but is recognised as eth2 rather than a wireless device, any ideas how to correct that?

|Thomas| · 19 Jan 2008 at 18:14

Which distro is this?

You don't need to, eth2 is just what linux has labeled your connection as, it will still work fine as a wireless network. My laptop has a wireless connection called eth1 and it's absolutely fine.

Steedie · 19 Jan 2008 at 19:10

Sorry its Fedora 8

And I cant use it as it is using the same config setup screen as an ethernet connection so I have no way of entering any wireless details like my SSID or WEP Key

AndrewP · 20 Jan 2008 at 20:13

Which wireless chipset is it? I got my Dad's laptop working from the LiveCD of Fedora 8 without messing around with ndiswrapper, it's a Dell and Broadcom 4318 chipset.

The only real problem I had was it trying to load both the bcm43xx and bcm43xx_mac80211 modules, but removing/reloading those sorted it out and then the interface shows up as normal.

I wrote a script so my dad could do it from a USB drive when running the live OS, but you'd only need to do it once I think:

Code:

su root
cp /media/USB\ 128\ MB/*.fw /lib/firmware/
echo 'blacklist bcm43xx' >> /etc/modprobe.d/blacklist
modprobe -r bcm43xx
modprobe -r ieee80211_crypt
modprobe -r bcm43xx_mac80211
modprobe -r ieee80211
modprobe -r ieee80211softmac
modprobe bcm43xx_mac80211