Upgraded to 8.04 using the Ubuntu Update Manager and now I have no wireless!

It's intel wireless.

Which intel wireless?
Was it auto-configured in Gutsy?

Intel 3945

Worked fine in 7.10, auto configured.

Check what wireless chipset you have by running gnome-terminal and entering the commands below
Post back the output.

Have you installed linux-ubuntu-modules-2.6.24
https://bugs.launchpad.net/ubuntu/+s...24/+bug/195136

Have you enabled essid broadcast on AP?
https://bugs.launchpad.net/ubuntu/+bug/200952

There are quite a few issues with intel 3945 and Hardy.
http://ubuntuforums.org/showthread.php?t=672332
(Long thread)

Seems related to a driver change.

The problem arises from the change from the old driver with proprietary userspace microcode to the new iwlwifi 3945 driver which I belive is open source. This problem is common across all distros using kernels 2.6.24 onwards in my experience (some 3945 cards work across the board and some like mine don't without the following workaround). It can probably be fixed for you very easily. I had the problem that the card was recognised, driver and microcode loaded but it was unable to scan. A fix based on that outlined in the following thead http://ubuntuforums.org/showthread.php?p=4611920 fixed this issue for me.

Here's a brief summary of what I did (which is slightly different to the fix in the thread and makes more sense to me):

unload the driver create a file name iwl3945 in /etc/modprobe.d/ and
in the file type the following and save:

reload the driver

restart the network interfaces:

The 3945abg wireless card/chip should now work fine with network manager. There should be no need to reboot or substitute wicd for nm.

I did an upgrade from 7.10 to 8.04 two nights ago. Everything seemed to be fine, until I opened Network Manager...then all hell broke loose. It gave me a hard time setting up my network, because sudo commands don't work. For some reason, the upgrade renamed me to some dotster.com nonsense, and using gedit is not an option to fix the problem. I've also tried to Hotwire it, but it ignores me in the booting sequence, so that's out. I was pretty excited about this upgrade, and it fixed a lot of issues I had with 7.10 but in end, not being able to root in, is kicking my ass. I'm locked out as a normal user, and root is now in the hands of the laptop and the Ubuntu program. Any ideas on how I can circumvent this problem? I'd appreciate any help anyone could offer.

In what way? I can sudo fine.

What? Actually edited your actual birth certificate? Took out a deed-poll in your name? Changed your hostname? Be clear! What sort of network? How would you normally set it up?

Why not? The config files are still there!

What does this mean?

Yes - that's how it's supposed to work. There has been no root login on ubuntu for a while now. You can enable it though, and there's a root terminal.

You have not actually told us the nature of your problem. You have, instead, waxed lyrical about your frustration. Metaphors are all very well, but hardly useful for troubleshooting.

Start a new thread and link to it from here. Revise the LQ tutorial an how to post a question or just take the "advice" in my sig.

The sudo problem is widespread for upgraders and is because the hosts file has been modified adversely during the upgrade. I belive you just need to add your host name to the file /etc/hosts i.e.

I believe that while sudo is broken you can still use gksudo so you can Alt+F2 and use gksudo gedit to access and write to /etc/hosts

Another workaround for people using iwl3945 and firestarter. On a default install Firestarter seems to prevent the iwl3945 driver from loading the microcode, or perhaps the driver loads the microcode rather slowly and fails to start promptly but anyway the result is that both firestarter and the driver fail, resulting in no wireless networking.

The workaround is actually simple and works. Blacklist the iwl3945 driver in /etc/modprobe.d/blacklist and add it to /etc/modules instead. Reboot and now everything is normal, both the wireless driver and firestarter start normally and boot time is back to normal.

Simon, your claim to be a guru baffles me. Do you need me to hold your hand through the problem I've stated?

sudo doesn't work, I can't gedit, gksudo or Alt F2 any files to fix this problem.

If you don't have an answer that isn't smug, then please spare me. I'm trying to deal with a situation with an upgrade, and you want to do your comedy act. Don't quit your day job. You're obviously a help desk employee...no answer, be an ass. It works for you.

Takla:

I've tried changing the localhost info, but still can't save it. Regardless what I try, it refuses me access or edit. But accepting upgrades asks me for root password, and it accepts it. This is really starting to baffle me. I have root access if I do the upgrades via Upgrade Manager, but none any other way.

So edit it from the livecd.

I've tried that as well. Edit isn't possible from any point. I've even tried to reinstall. I'm about to head to Mandriva if I can't open this up.

I am rather puzzled that the livecd didn't cut it. It has been a while since I last used it but still, you are operating in a different environment so I don't see what could be keeping the file locked. You did use sudo gedit? And you didn't accidentally edit the file on the livecd rather than the one on your hard drive?