Recently in The dreaded NetworkManager Category

Jono Bacon goes on at length at his blog on the contrast between the euphoria over the release of Ubuntu 9.10 (Karmic Koala) and the reports of problems by users.

Read the 10 or so entries below this one and you can see the problems I've had.

It's time to put this in perspective. I've had plenty of problems with all manner of Linux and other Unix-like operating systems over the past few years. Given all the hardware that a modern OS must contend with (and I'll include Windows in that number since it runs – or is supposed to, anyway – on a wide variety of hardware), there's bound to be breakage.

Apple has it easy because it controls the hardware and the software and hence has an easier time making all the bits work together.

In my experience, Ubuntu generally performs well, and its developers seem genuinely worried about whether or not hardware will work with the distribution's constant stream of releases.

In both Linux and OpenBSD, for instance, wireless support has only gotten better over time.

I wish I could say the same for sound and video. PulseAudio has been somewhat of a disaster over the past year or more. It just wasn't ready for the average user, and the above-average user is demanding Jack and real-time kernels to do sophisticated audio work.

Now PulseAudio seems to be getting better.

For me, my Intel video hardware on a couple of laptops (Gateway Solo 1450 and Toshiba Satellite 1100-S101) has been causing problems beginning with Debian Lenny's time in testing. Whenever you need xorg.conf hacks just to make video work, and those hacks aren't crystal clear and easy to find, there will be problems. People will try Linux and run away from it as fast as they can if they can't get the basics (sound and video) to work.

And for my particular Toshiba laptop, the use of Kernel Mode Setting killed X in my Ubuntu 9.10 upgrade. Once I figured out how to turn KMS off (with a new line in GRUB), I could run X without an xorg.conf for the first time since Ubuntu 8.04 and OpenBSD 4.4. That's a nice change.

But to get there — to get basic functionality — I had to bring my 2 years of FOSS knowledge to bear in order to solve the problem.

Then just about every ancillary GNOME app (Brasero, Rhythmbox, Empathy and the non-GNOME Pidgin) stopped working after the upgrade. A quick search determined that my previous installation (in 9.04) of KDEnlive brought in a plugin that kept the other four apps from working. I saw lots of chatter on the problem, but none of the solutions worked for me. I had to remove the offending plugin and then reinstall three opencv libraries to clear things up (you can see all the details in the previous entries on this blog).

Many will say that I should've stuck with the Ubuntu 8.04 LTS (with the initials standing for "long-term support"), which performed well for me but wasn't as stable on my particular hardware as 9.10 (for which I had to do some hackery to get NetworkManager to manage my network).

And both Ubuntu 8.04 (I'm still using it on the Gateway laptop, where it's very solid) and Debian Lenny (now stable and running very well for me on two other machines) are viable options, but for my main laptop I want newer packages, especially Firefox 3.5, and I've been more inclined to upgrade the distro itself rather than use backports or PPAs to bring newer apps to older distributions.

Maybe I've got that wrong (or maybe not).

I've been meaning to move all of my user files to a Debian Lenny machine and see how well that performs with my regular abuse of the hardware and software. And there's always Fedora (and Mandriva ... and PCLinuxOS ... Mepis ... and dozens of others).

But despite all my grumbling, I do have a functioning Ubuntu 9.10 system. I even ditched my own "blue" theme and wallpaper and brought in the "human" theme and wallpaper that shipped with the upgrade. I'm back to Ubuntu s**t brown and orange, and I'm liking it. The new GNOME icons are cool. And we all have the next Ubuntu release — and 10.04 will be the next LTS — to look forward to with hope that many bugs will be squashed in the service of a stable desktop that will have the customary 3 years of desktop support.

In a nutshell: Ubuntu's under the hot lights. People expect more from it than they do from any other FOSS operating system. And it generally delivers more than any other, if not as much as people are counting on in their lofty expectations.

I use Ubuntu for many reasons: It seems to have the right balance between total "freedom" and the ability to play most multimedia, its developers are focused more on the desktop and less on the server (although Ubuntu is making a big play there), and its vast user base means that when there are problems, the community (including me in this blog) can often solve problems that benefit all users.

We're all looking for the time when Ubuntu (or some other distro, or some other OS entirely) can be easily handled by the average computer owner. That time really isn't here yet. With a Windows preload, the manufacture of the hardware generally makes sure there are drivers for all the hardware. Linux preloads — a few of which do exist — generally do the same. But in the wild and wooly world of geeks burning ISOs and installing Unix-like operating systems on all manner of hardware, a foolproof experience just isn't in the cards. Yet.

Will we ever get there? I hope so. I also have at least a little bit of hope for more preloads of Ubuntu and other Linux distros and maybe even a BSD.

There has been a whole lot of progress over the past few years on the Linux desktop. It's hard to predict where the state of FOSS will be five years from now.

In the near future I'll settle for Xorg and Intel playing well together, mass adoption of a free and open video standard and a move away from proprietary document formats since we barely need to print anything anyway.

Yep, I used wireless to upgrade from Ubuntu 8.04 to 8.10 and finally 9.04, and NetworkManager lost control of my wired Ethernet interface in the transition from 8.04 to 8.10.

I did manage to find a fix very quickly, and I can confirm that it does indeed work.

Here it is:

If you want to keep your devices configured via /e/n/i but managed by NM, then use managed=true in /etc/NetworkManager/nm-system-settings.conf and don't forget to kill the running nm-system-settings instance./blockquote>

I went into that file:

$ sudo gedit /etc/NetworkManager/nm-system-settings.conf

There I changed managed=false to managed=true, saved the file and then rebooted.

After that, my wired-Ethernet configurations from 8.04 returned to NetworkManager (which works completely differently, by the way), and I was able to select one of my preferred configurations, which work.

I'll say more about the "new" NetworkManager in the near future, but for now, I'm able to connect to wired and wireless networks with it, and it appears less buggy than before.

For a new 9.04 installation (and a 9.10, I suspect, as well), this won't pose a problem, as your favored interface should be configured automatically.

But this problem with NetworkManager in upgrades — and it looks like it breaks in Debian as well as Ubuntu — is really a bad deal for users.

I seldom find fixes for these problems so quickly. And in-place upgrades should go a whole lot better than mine have in recent memory.

Meanwhile, I have a perfectly working Ubuntu 9.04 installation, and I'm ready for 9.10.

I won't be upgrading to 9.10 during the first week of its release because the mirrors will be extremely busy. I tend to wait at least a week, but it's better to wait two or three (though I usually pull the trigger before that time).

I always pull the trigger too soon when declaring success with a new WiFi adapter/software/hardware combination, and I'm hoping that's not the case with the Airlink 101 AWLL3028, Ubuntu 8.04 LTS and my aging Toshiba Satellite 1100-S101.

But today I first had trouble connecting with my WEP encryption key (I know I shouldn't be using WEP ... and I will change to WPA2 once I resolve a few issues and get the rest of the house's computers on board ...).

Then when I finally did connect (had to reboot) I had the typical screen-freezes-and-ctrl-alt-backspace-AND-ctrl-alt-delete-have-no-effect-so-I-have-to-do-a-hard-reset.

That's the beauty of blogging where absolutely no one is making any damn money from the entire enterprise: I can just spin out a fake word with 30 or so hyphens and just move on.

OK ... I was reprimanded once for using the kind of language that flows continuously through my favorite podcast, and I considered just chucking the whole blogging-for-the-man thing and doing this on my own time, on my own site and enjoying the tens of dollars yearly I could earn from Google AdSense.

OK, I pretty much do this entirely on my own time as is ...

Anyhow, I'm ready to return to the raw meat of this blog post, which is my trouble with wireless networking.

So I did the hard reset, booted back into Ubuntu and while things seem a bit slow, networking-wise (that could be anything), it's working OK for the moment.

Here's what I'm thinking:

The problem might not be the specific wireless networking adapter; it could be an issue with USB (1.1 in the case of this old hunk of saved-from-the-garbage hardware). Whether Linux-related or not, perhaps the Toshiba just can't handle using the USB inteface that intensely.

I don't recall having any problems with the PCMCIA adapter I use with every damn PCMCIA-equipped computer known to woman and man, namely the Orinoco WaveLAN Silver (all I'm saying is if you don't have one of these, go to eBay and get one; for me's it's the geek-networking equivalent of the Swiss Army knife or Leatherman.

So a "newer" Cardbus adapter (maybe another $10 Airlink?) might work better for this particular laptop.

Another thing: If whatever problem I'm having is related to software, it's possible that performance will improve and crashes will diminish (or end entirely) with newer versions of everything from the Linux kernel (remember, I'm using Ubuntu 8.04, which is pretty much a year and a half old; ancient in Linux terms) to the dreaded NetworkManager in GNOME or anything else in the stack.

But given my recent experience, I'm extremely gunshy and more worried about regressions than either a lack or abundance of "improvements." That's what screwing up Xorg for probably half the PCs out there will do to you, O Xorg developers who decided that working Intel video is for other people, meaning people who don't have Intel video chips embedded in their PCs.

Can you tell I'm bitter? I thought you could.

Of course with the super-fast USB 3 on the horizon for Linux — yep, first for Linux and then for the other 99 percent of the world, I expect we'll be getting more USB-connected hardware and not less, and that includes add-on network adapters, which I suspect will be with us in various forms for quite awhile as PCs' built-in networking (wired and wireless) are superseded by newer devices and protocols.

I'll continue testing the Airlink 101 AWLL3028 USB adapter and even consider entering the modern era and slapping Ubuntu 9.10 on this laptop. I'll try an in-place upgrade from 8.04-8.10-9.04-9.10, and if that doesn't work I can do a reintall with a fresh 9.10. That'll keep me (and my office's ample bandwidth) busy for awhile, I suspect.

I'm always hopeful; "It's only one crash," I say to myself. But one crash usually begets many more. I say usually hoping for the unusual and simultaneously wondering to myself why things have to be this hard (and remembering that these kind of problems reared themselves very well during my time running Windows 98/2000/XP and Mac OS 7.6/9.x/10.x).

Right now with the built-in wired networking, this hardware/software setup is pretty much problem-free (OK ... suspend/resume is a disaster, but I wasn't expecting anything more with hardware of this now-7-year-old vintage).

It's a good time to put my optimism hat atop my head, leave the friendly confines of the Ubuntu LTS behind and leap into the world of the six-month upgrade cycle and hope that improvements drown out regressions.

After all, I can always initiate my own regression and return to 8.04 (or chuck it all for something safe like Slackware 12.2 ...). I called Slackware "safe." Time for more coffee.