problem setting up wireless

[pwatk]

Well I never did care much for positive rants :^{

Lol, fair enough

You could install the kernel-source with your wired connection, install the b43-fwcutter and b43-firmware you require and start again form there. The instructions at http://linuxwireless.org are pretty straight forward.

You can probably download SlackBuilds from http://slackbuilds.org for the b43 stuff or if I get time in the next few days I'll dig out my old scripts and make slkbuilds for them.

At least then you might be able to do away with the dongle and use the inbuilt wireless.

[pwatk]

I've posted my slkbuilds here [link], hope this helps.

[laprjns]

I have loaded the broadcom driver, bcmwl5.inf, into ndiswrapper using the gtk tool that came with salix and the command ndiswapper -l tells me it has been installed.

However, modprobe ndiswrapper tells me that ndiswrapper is not found.

It is in /lib/modules/misc so when I do an insmod -f /lib/modules/misc ndiswrapper I am given an Invalid format message.

The problem is that /lib/modules/misc is the wrong directory; modprobe can't find it there. ndiswrapper.ko needs to be in /lib/modules/uname -r/misc. uname -r is 2.6.33.4-smp in SalixLive 13.1 Do the following as root:

Code: Select all

oot[one]# mv /lib/modules/misc/ /lib/modules/2.6.33.4-smp/
root[one]# depmod -a
root[one]# rmmod b43
root[one]# rmmod ssb
root[one]# modprobe ndiswrapper

This worked for me on my laptop with a Broadcom bcm4312 802.11b/g (rev 01

[laprjns]

The problem is that /lib/modules/misc is the wrong directory; modprobe can't find it there. ndiswrapper.ko needs to be in /lib/modules/uname -r/misc.

There is now an update to the ndiswrapper package that fixes this.

[caitlyn]

It is a very recent broadcom chipset which I had to blacklist in order to boot either salix or slack, I have to do the install using noudev.

I have an HP Mini 110 with the Broadcom 4312 wireless chipset. I think your chipset is the same as mine.

First, you don't need or want noudev. udev is decidedly useful. What you want to do is disable the conflicting drivers, ssb and b43. I actually wrote a how-to article about this: http://broadcast.oreilly.com/2010/06/av ... books.html

Build the correct Broadcom driver (yes, the proprietary one) with the SlackBuild located at: http://slackbuilds.org/repository/13.1/ ... adcom-sta/

The Broadcom chipset works flawlessly with SalixOS 13.1 once you have the proper driver installed. It actually seems to have the best range of any wireless chipset in any netbook or notebook I've tried. I do NOT recommend ndiswrapper and Windows drivers when there is a perfectly good native Linux driver.

[laprjns]

I do NOT recommend ndiswrapper and Windows drivers when there is a perfectly good native Linux driver.

Yes, I would agree, but when using a Live CD, compiling a driver every time you boot is not a good option. In a pinch, as I was, traveling with only a corporate issued laptop that had Windows Xp so locked-down that I really couldn't surf the web, using SalixLive Cd with ndiswrapper worked well.
Rich

[gapan]

I do NOT recommend ndiswrapper and Windows drivers when there is a perfectly good native Linux driver.

Yes, I would agree, but when using a Live CD, compiling a driver every time you boot is not a good option. In a pinch, as I was, traveling with only a corporate issued laptop that had Windows Xp so locked-down that I really couldn't surf the web, using SalixLive Cd with ndiswrapper worked well.
Rich

You could have used the persistency option with a usb flash drive and compiled it only once.

[laprjns]

You could have used the persistency option with a usb flash drive and compiled it only once.

Yes, if only i had one with me.

[gapan]

You could have used the persistency option with a usb flash drive and compiled it only once.

Yes, if only i had one with me.

Ah, that bad then.

[justwantin]

After putting this netbook aside for awhile I got it out tonight and finally conjured up a wireless connection using the Ralink usb doodah and wicd. I'm still thick as a brick though having spent too long on Alien Bob's wike trying to set up wpa_supplicant to no avail. I finally reset the wireless modem to no wpa anything. I had also set it up to allow/deny with mac addresses so while probably not as good as wpa-psk. It will have to do until I sort out the rest and maybe even get that broadcom device working.