norman.walsh.name: Comments on /2007/04/01/feistyhttp://norman.walsh.name/2007/04/01/feisty/comments.atom2012-05-23T11:38:56.706162ZComment 1 on /2007/04/01/feistyhttp://norman.walsh.name/2010/09/25/oauth#comment00012007-04-02T19:02:53Z2007-04-02T19:02:53ZShelleyda39a3ee5e6b4b0d3255bfef95601890afd80709

Your feed entry, "Feeling feisty... Moving up to the latest Ubuntu." cracked me up.

A+ in the art of creating feed excerpts.

Comment 2 on /2007/04/01/feistyhttp://norman.walsh.name/2010/09/25/oauth#comment00022007-04-04T09:16:33Z2007-04-04T09:16:33ZSteinar Bangda39a3ee5e6b4b0d3255bfef95601890afd80709
The applet you're talking about, is it the one from network-manager (nm-applet)?

I'm already running network-manager in Dapper, and was wondering if that would conflict with whatever's native, when first upgrading to Edgy, and then to Feisty.

Since my laptop (originally installed with Breezy in February 2006, and upgraded to Dapper sometime during the summer) basically works, I've avoided upgrading. But I guess if I don't upgrade soon, I'll be stuck in Dapper-land.

Comment 3 on /2007/04/01/feistyhttp://norman.walsh.name/2010/09/25/oauth#comment00032007-04-04T11:00:36Z2007-04-04T11:00:36ZNorman Walshda39a3ee5e6b4b0d3255bfef95601890afd80709

Yes, Steinar, it's nm-applet. "About" tells me that it's NetworkManager Applet 0.6.4.

Comment 4 on /2007/04/01/feistyhttp://norman.walsh.name/2010/09/25/oauth#comment00042007-05-05T19:08:10Z2007-05-05T19:08:10ZSteinar Bangda39a3ee5e6b4b0d3255bfef95601890afd80709

Ok. Now I'm feeling Feisty too.

I did the upgrade from Dapper to Edgy, tried out Edgy for half an hour, to see if thing worked. Some did, some (eg. WLAN) didn't.

Then I started the upgrade to Feisty. It went without a hitch. The first thing that struck me was how much smoother everything was. Everything mission critical, including WLAN and VPNC, through nm-applet, worked. For the Broadcom WLAN NIC (traditionally a problem in linux) I got a newer bcm43xx driver, and it downloaded and installed new firmware for the card automatically.

Some things did not work; google earth, and VMWare. The VMWare problem was fixed by commenting out a single line in a header in the VMWare module source. For Google Earth I ended up with throwing out the closed source fglrx driver for the ATI Radeon Mobility card, and using the open aiglx driver insted. This eventually got google earth started but running slooowly. Turns out there is a bug with the driver for the r300 chip wrt. to google earth. But for other things, eg. Beryl, the aiglx driver works a lot better (and the fglrx driver did not work for me at all in this incarnation).

So win some, lose some. Good WLAN is a lot more important for me than google earth. And leaving the fglrx driver behind I may be able to use my laptop for presentations again (I lost external VDU output with fglrx).

So I'm happy with this upgrade. And very impressed at how smooth the two stage upgrade turned out to be.