Hi John, Silly me !!!! :) After correcting myself, I took out the ndiswrapper module, and checked my modprobe.conf file, which now looks like: [root@home ~]# cat /etc/modprobe.conf alias eth0 forcedeth alias scsi_hostadapter libata alias scsi_hostadapter1 pata_amd alias snd-card-0 snd-intel8x0 options snd-card-0 index=0 options snd-intel8x0 index=0 I thenn went to System --> Administration --> Network to see if the device had popped up in there, but sadly I only saw the ethernet connection. I thought about trying to create a new network connection, but the only broadcom device listed is "Broadcom Tigon3", which isn't mine. Your next step is rfkill button, what is that? I tried it on the command line but couldn't find a command, any pointers here would be good? The only reference I can find is with a module, lsmod shows: rfkill 9297 1 b43 Thanks again Dan On Nov 18, 2007 3:19 AM, John W. Linville <linville@xxxxxxxxxx> wrote: > On Fri, Nov 16, 2007 at 11:16:52PM +0000, Dan Track wrote: > > > Many thanks for your script. I ran it but the downloads failed, since > > I don't have connectivity on the pc. Instead I downloaded your script > > requirements on to my laptop then transferred via a usb memory stick > > to the pc. I then ran the script you attached from the same directory > > as the downloads and then the script ran fine as I didn't get any > > errors reported. I then did a "modprobe ndiswrapper", but still dmesg > > didn't show the wireless card. Any ideas? I've attached the dmesg > > output after running the "modprobe ndiswrapper" command. > > Clearly you missed the point of the exercise. :-) If you insist on > using ndiswrapper, then you don't need to load the firmware... > > Please forget all about ndiswrapper. Remove any references to > ndiswrapper from modprobe.conf, and type the following command: > > modprobe -r ndiswrapper > > Then observe this part of my former message: > > > On Nov 16, 2007 4:23 PM, John W. Linville <linville@xxxxxxxxxx> wrote: > > > You may need to reboot or 'modprobe -r b43 ; modprobe b43' afterwards. > > Afterwords, you probably want to run NetworkManager: > > service NetworkManager start > > With any luck, your wireless device should now be working. If not, > please check the state of your rfkill button. > > Thanks, > > > John > -- > John W. Linville > linville@xxxxxxxxxx > > -- > fedora-list mailing list > fedora-list@xxxxxxxxxx > To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list >
