I was so happy last night when I finally got WiFi working on my HP laptop with AntiX.. This morning I planned on setting it up for my kids to use.

But it wouldn't connect. It's now doing the same thing it did before. Simply not connecting. I can see the APs but when connecting with WPA it times out with"bad password". If I turn off WPA to test it times out with"could not retrieve IP address".

I'm frustrated, and ready to just go buy them a new laptop at Best Buy with windows 7... I fought for days with Mint, Ubunutu, SUse, etc.. all with the same wifi issues (well, they would never connect). I just don't get how it worked one day, then stops working the next morning. __{{emoticon}}__

I'm open to suggestions.

legbuh,

Would you run
inxi -F in terminal as a user so we can see your wireless card?

cheers,
ohh

I guess it is a bcm 4306.

Have a look here, especially the last post.

post15388.html?hilit=bcm 4306#p15388

anticapitalista wrote:I guess it is a bcm 4306.

Have a look here, especially the last post.

post15388.html?hilit=bcm 4306#p15388

Yep, the last post is what I used to get everything going. I shut it off last night, turned it on this morning, and it won't connect again.

Try using ceni if you haven't done so already.

Yep, already tried ceni. it keeps mentioning no DHCP discoveries

maybe you need to modprobe your chip?

If you mean modprobe ssb && modprobe b43, I tried that.. no go.

When I got it working last night I purposely rebooted a few times to make sure it would find the AP I set up as the default and always to connect too. During the boot I could see it making the connection right away. So happy that I had finally defeated this ugly moster, I went to sleep after shutting down the laptop.

Only to find this morning, it not working.. lol..

Did you go into
/etc/modprobe.d/b43.conf and as root and comment the following (# sign )


#ssb true
#b43 true
b44 true

then as root run

modprobe ssb && modprobe b43


In antiX 8.5 Wicd's default is for wired, if you have wireless this is one way to get connected.

Control Center--> Network--> Connect Wirelessly (wicd) The first time it is run The Wicd Network Manager pops up with wired network as default, click on +Add, a pop up box with Enter Profile name comes up, in Profile Name enter wireless--> Click OK--> Click Preferences--> Enter your wireless interface (eth0,ath0,wlan0,etc), if you only connect wirelessly, remove the interface from the wired. Note:(If the pop up box does not come up, then go to preferences and enter your wireless interface (eth0,ath0,wlan0,etc)

Note: Under External Programs tab, the DHCP client default is set to Automatic, if you get an ip address, but cannot connect to the www, then return here and try dhclient.

cheers,
ohh

Yep, I did all that. Like I said, worked great last night. Today, no go. So, I went to best buy and while I was picking up a kindle for my wife, I got a netbook for the kids. __{{emoticon}}__

I'll still play around with AntiX but I still wait for the day when I can just install a distro and have it work and not have to edit, run root commands, etc. I know it's not Linux's fault, but my time is too valuable these days. __{{emoticon}}__

have you tried rebooting the wap itself, sometimes this does the trick for me. Not sure why but I have one netgear wn2000 wireless n router and it needs a reboot for wireless to work from time to time.

have you tried rebooting the wap itself, sometimes this does the trick for me. Not sure why but I have one netgear wn2000 wireless n router and it needs a reboot for wireless to work from time to time.