Results 11 to 20 of 54
Originally Posted by MikeTbob
Do you have the drivers? If you have Windows on another partition, I think its ok to copy them from there. Is that where you got ...
- 06-12-2007 #11Just Joined!
- Join Date
- Apr 2007
- Posts
- 97
- 06-12-2007 #12
Well, I'm sure the files aren't very big, you might be able to get them on a floppy disk if you have one available for use. Do you have a CD Writer?
From the NDISwrapper web site:
Or you can try downloading one from the NDISwrapper listIf you already have your device working in Windows you can try that driver. Open the device manager and find the name of the .sys driver file listed for the device. You need the .sys file and the .inf file. To find the .inf file search in the \Windows\inf\ directory for a file containing the name of the .sys file. You will need to do an advanced search to search for text within the files.
NDISwrapper
Have you seen this link yet? It might help shed some light on this for you.
http://www.linuxforums.org/forum/lin...-new-post.htmlI do not respond to private messages asking for Linux help, Please keep it on the forums only.
All new users please read this. and the Forum FAQS.
- 06-12-2007 #13
NOOOOOOOO!
There is a native Linux driver for this chipset, it's called bcm43xx, and it comes with 2.6.18 kernels as standard; it was included in FC6 - which I run on my laptop.
You need a line in /etc/modprobe.conf that says 'alias bcm43xx eth1' or summat like that (I'm doing this from memory, as my laptop is at home and I'm at work), and the 'bcm43xx-fwcutter' package. You run the cutter tool over the windows drivers, and put the resulting firmware in /lib/firmware.
All that's needed then is a 'modprobe -r' as root, and you can use 'system-config-network' to set up your wireless - if you add a new interface eth1 will appear in the list.
If the wireless lan needs security, WPA-PSK or whatever, then it needs wpa_supplicant or NetworkManager, either of which are straightforward to configure (but should be the subject of a new thread...)Linux user #126863 - see http://linuxcounter.net/
- 06-12-2007 #14Just Joined!
- Join Date
- Apr 2007
- Posts
- 97
Uh, well I'm gonna try out what Miketbob said and if it doesn't work i'll try out the other way....
- 06-12-2007 #15
If it's not too late, Roxoff has the right idea. Hopefully it will work either way and you'll be done with it.
I wasn't aware that Fedora had the driver available.Last edited by MikeTbob; 06-12-2007 at 01:45 PM. Reason: spelling
I do not respond to private messages asking for Linux help, Please keep it on the forums only.
All new users please read this. and the Forum FAQS.
- 06-12-2007 #16
If it were me, I'd try ndiswrapper as a last resort only. Using native drivers really is much easier. Before the 2.6.18 kernel, I had no native driver and had very mixed experiences with ndiswrapper - sometimes it liked the windows drivers I had, and sometimes it didn't.
Linux user #126863 - see http://linuxcounter.net/
- 06-12-2007 #17Just Joined!
- Join Date
- Apr 2007
- Posts
- 97
- 06-12-2007 #18
Sorry about that. I just googled the chipset with the word "Linux" and posted what I found. I've never personally had to deal with Broadcom chipsets before, only Atheros.
- 06-13-2007 #19Just Joined!
- Join Date
- Apr 2007
- Posts
- 97
Well i still need those instructions when u get a chance!
- 06-13-2007 #20
Try this:
Open a terminal window and log in as root (use 'su -' as the command, and the root password when prompted).
Use 'gedit' or 'kate' to edit the file /etc/modprobe.conf like this:
And add a line at the bottom that looks like this:Code:gedit /etc/modprobe.conf
install the bcmfwcutter with:Code:alias bcm43xx eth1
change to the directory where you have the windows drivers, e.g. if they're in a 'drivers' directory in your home directory, do:Code:yum -y install bcmfwcutter
and do:Code:cd ~/drivers
You can take a look at the man page for bcmfwcutter if you want to do this better - but these are simple instructions...Code:bcmfwcutter <windows_driver_filename>
This will dump a load of files into the same directory as the windows driver. Copy all the firmware files into /lib/firmware, probably with a command like this:
Then do:Code:cp * /lib/firmware
and finally do:Code:modprobe -r
to bring up the graphical network tool - if you add a new device, eth1 should be there. You can now configure IP addresses or DHCP just like any other interface.Code:system-config-network
If you're using a secured wireless lan, and want to use NetworkManager, then make sure the interface is not turned on at boot time, but ensure that NetworkManager and NetworkManagerDispatcher services are started in your runlevel (i.e. tick their boxes and save the settings in the 'system-config-services' tool).Linux user #126863 - see http://linuxcounter.net/



Reply With Quote
