Wifi fails after 14.1 update [SOLVED]

[Sasquatch]

My wi-fi worked fine when I installed 14.1. But I find myself without connection this morning after updating last night. I don't understand what changed. My phone has a connection, so I know the router is working.

[mimosa]

I've created a new topic for this post, which you should do for a separate problem - if you think there is an important connection to an old thread on the forum, link to it.

Also the 'solved' in the tile is rather misleading

This is unlikely to have been caused by the update. In any case, the solution needs to be found by investigation and elimination. First off, though, are you sure you didn't do anything apart from teh update and upgrade that might have affected the wireless connection? Open wicd and make sure all the serttings look ok. Can it see your wireless signal at all? Try 'Refresh'. Is the box 'always automatically connect to this network' ticked?

[Sasquatch]

Couldn't type a full response on my phone so I reinstalled to get the wi-fi back. I haven't done any updates yet to see if the problem repeats.

Ok, to answer all the questions;

No, I didn't do anything other than "refresh", "mark updates", "execute" in gslapt. And it was the second time I updated since installing.

Just before this current reinstall I tried running wicd from a terminal and got nothing. It told me "the daemon appears to be running already. If it is not, remove /var/run/wicd/wicd.pid and try again. So I did;

Code: Select all

sudo rm /var/run/wicd/wicd.pid

and tried again, but still nothing.

The connections GUI tells me "no connections available". I refreshed it several times.

It can't be a hardware issue since I'm connected right now with all the same hardware. But I don't see how a simple update could have broken the wi-fi. Especially since it would have broken more systems than just mine. So it has to be something unique to my system. Which is where I'm confused.

I'm going to do an update again and see if it happens again.

[mimosa]

To open wicd, click on the icon in the taskbar, or, from the command line, not as root, do:

Code: Select all

wicd-gtk

[Sasquatch]

Ah, I didn't realize wicd was the same program as in the taskbar. That's what I was using.

I forgot to mention that, yes, I do have it marked to autoconnect.

Okay, just finished the update and everything still works. I am going to reboot and see what happens now.

[Sasquatch]

No wi-fi again after the reboot.

[mimosa]

Try running (as root)

Code: Select all

ifconfig -a

You should see either wlan0 or wlan1 in the output. Go back to wicd and check the settings are looking at the right one. I think this problem is more common with the ethernet (eth0 versus eth1) but it's worth checking.

If that doesn't work, for starters, try

Code: Select all

sudo iwlist scan
sudo iwconfig

and post the output.

[Sasquatch]

Thanks, I'll try that as soon as I get home this evening.

[marcxjo]

On both 14.0 and 14.1 (not 13.37, at least that I can recall), I've always had to run dhcpcd manually after boot to get my connection going. It's probably just a matter of creating or modifying an init file, but so far it hasn't bothered me enough to jump on that yet. I wonder if the same issue is preventing your connection.

You might try:

Code: Select all

sudo dhcpcd

But if your setup is like mine, you'll likely have more success with

Code: Select all

sudo su
dhcpcd

(For some reason I've had issues simply passing "sudo <command>" with almost any command, but that's an entirely different problem.)

[laprjns]

(For some reason I've had issues simply passing "sudo <command>" with almost any command, but that's an entirely different problem.)

That is because most of the commands that you use as root are not in the normal users PATH. Commands like reboot and spkg are in /sbin and when called with sudo need to have the full path. For example :

sudo /sbin/reboot