Linux - Wireless NetworkingThis forum is for the discussion of wireless networking in Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
hello any 1 who wants to listen i can get myself on the net with linux no problem the problem is every time i log off go on to windows then go back on to linux i get error message device eth0 not present now unless i reinstall it im buggerd i just need to know why its is not saving every time i reinstall my device driver imasked if i want to save my new settings i choose yes so pleasse pleeese help me
hello im back it would seem if i type" insmod bcm4400.o" it gets me back on the net every time but thats a pain in the *** i must be missing something realy simple but what.
Saw this issue on here somewhere - turned out that in Windows the power management settings in Control Panel were set to also be able to put the network card to sleep. This worked fine in Windows but stopped linux recognising the card on boot up. Solution was to turn off in Windows power management of the network card. Worth a try.
Had another look at your posts and it seems that you now have success with insmod bcm4400.o whereas previously you had tried insmod bcm4400 and modprobe bcm4400 and got module not found. If so does that mean the /etc/modules.conf line should be 'alias eth0 bcm4400.o' ?
Hello master!
I had a problem with a broadcom440 too, and I went to broadcom.com. THey have a driver there which will definitely help. I'm using redhat9.0, and it's worked perfect...
I'm a newbie in linux, but someone helped me install it. It's perfect.
Just go ahead and download it... it's so straight forward.
God bless you!
hello andrew just to let u know i tried putting "bcm4400.o" in my etc/modules.conf instead of my previous bcm4400
but it still did not work so i am still having to log on as root open terminal and type "insmod bcm4400.o" then log out of root then log in as normal user some times it can be a bit of a drag
cya nige
hello mungujakisa not sure if u have got the wrong end of the stick but i have allready got the driver and i am on the net my only problem is as above thanks 4 ur reply
Glad you had the driver. I was just trying to help... and as I said, I"m a newbie at this.
God bless you master...
and o, my pc starts up well with all the drivers and pci device, so I don't have to activate or do whatever else... maybe if you could re-install the drivers, it'd work fine.
my words end here
Just had another thought - i've been wrestling with a similar problem on my laptop with a Cardbus/pcmcia wireless card - managed to get it up and running with ndiswrapper but on reboot although the ndiswrapper module had loaded the card was not recognisable. Had to rmmod ndiswrapper and then insmod ndiswrapper and then iwconfig,ifconfig dhcpcd etc to get up and running.
Found out the reason was that order of the init scripts was network, hotplug and pcmcia (on SuSE 9.0 with kernel 2.4.21). Changed the order to put network after hotplug and pcmcia, rebooted and it starts like a dream!
Not the same issue as you (unless your card is pcmcia) but worth checking the order of the scripts in case it's trying to load the driver before the card is recognised.
I don't know how the init process is managed in RH9 but I think if you look in /etc/init.d you should find links to scripts - in SuSE there are folders called rcX.d where X is the init level and within those folders are links to start scripts and kill scripts (in fact they are the same script called with different parameters) which are numbered in the order they are executed. All I did was change the numbering on the network script to start it after hotplug and pcmcia.
Don't know whether this will help - but I'm learning a lot exploring this stuff !
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.