The End of A Gutsy Experiment

by Caitlyn Martin

In the comments to the article I wrote about running the 64-bit version of Ubuntu Feisty Fawn on a Gateway MX7626, I added that my friend who owns the laptop had "upgraded" to Gutsy Gibbon Tribe 4 to try and fix a problem with intermittent sound under Feisty. The initial upgrade did work and her sound functioned properly. I talked to her again last night and she is giving up on running Ubuntu alpha software and is going back to Feisty.

11 Comments

BobbyC
2007-08-28 14:36:53
Gusty is in the Alpha stage of testing. Which is always risky business. I managed to crash both the Gusty Ubuntu and Kubuntu 32 and 64 releases. On the Ubuntu 32 my shut down stopped working. Kubuntu was a disaster in the Alpha 4 stage.


But I do enjoy playing with alpha toys.


2007-08-28 23:21:40
"It’s just not ready for prime time yet."


It's not supposed to be. That's what Alpha, and then Beta are for.

Daniel Hedblom
2007-08-29 00:18:08
I have a bad habit of using the betas. If you do and report the bugs you find you can really help with the development. That way even us mere mortals can help. The more people that try gutsy out and report any bugs the better the final product will be.


Anyhow, loved the article, keep em coming =)


2007-08-29 01:39:07
Neither the article or user comments below say what got the laptop to freeze. No bug report given, nothing. How can anyone fix the problem. You will propably encounter the same error in the final version.
Geoff
2007-08-29 05:38:15
The Magic SysRq key will probably do the trick when compiz locks up to the point that ctrl+alt+backspace doesn't work. Going as far as "Raising Elephants" (alt+sysrq+r, alt+sysrq+e) consistently dropped me to the VT1 login when I was having similar issues (downgrading from the 100.14.11 nvidia driver to 9755 made my lockups go away).
Caitlyn Martin
2007-08-29 09:45:47
@Anonymous #1: I'm not an idiot. I know it's not supposed to be ready for prime time and I SAID SO. The point is that this blog is read by a wide range of people including newcomers to Linux who may not understand what Ubuntu Tribes are (development code).


@Anonymous #2: I am not the owner or the primary user of the laptop. I can't report details on what I don't experience, can I? It was strictly when running Compiz-Fusion. Disable Compiz and the problem went away. That actually was described in the article and does give a clue to what component of Ubuntu has the problem. It's up to the laptop owner to decide whether to do any further troubleshooting and/or report the bug. She's fairly new to Linux and may not feel up to going further.


Also, I seriously doubt that her failure to report freeze-ups in Compiz means the problem will go unreported and will show up in the final Gutsy. It's too blatant a bug for that.


ALL: Has anyone noticed that the less than clueful commenters tend to not want to sign their names? Of course, the purpose of both comments seemed to be to throw stones...

Caitlyn Martin
2007-08-29 12:16:19
@BobbyC: Traditionally beta testing was public testing and alpha testing was in house developer testing. I may be showing my age here :) I realize that in the Open Source community code is shared much earlies, often in every stage of development. Still, I assumed public iso == beta. I acknowledge I may have been wrong.


Regardless of the correct stage of development the point remains that Gutsy is still a work in progress. One should expect bugs, possibly serious ones.


@Geoff: The laptop in question has an ATI graphics chipset, not NVidia. It's a little late to try your suggestion but I'm still glad you posted as others may benefit.

LaptopOwner
2007-08-29 13:46:56
Yes, I am the owner of the laptop. No, I did not report any bugs because time is simply something I rarely have as I am usually on the move.


I was feeling pretty fearless as the previous upgrades went without a hitch. Tribe 5 brought my wireless to a screeching halt and I am still troubleshooting the issue (by saying still=I have spent 10 minutes on it so far).


Everything is where it should be and after poking it with a stick I ended up with an "Error inserting ndiswrapper (/lib/modules/2.6.22-10 generic/ubuntu/misc/ndiswrapper/ndiswrapper.ko): Operation not permitted.


I expect to be able to get it back up and running without the re-install at this point, I just need the time to d/l some source and do the work. Good thing that I still dual boot (but was rarely using Windows) as I was troubleshooting a wireless internet connection for someone at the time.


I love running development code for software because when things go odd, you really learn about the software and hardware. Job wise it has earned me a title `Doer of impossible things'. Kind of like a femme version of Scotty on Star Trek. ;)


Geoff, I will try out your suggestion soon I expect, the latest compiz-fusion drivers were just installed on my system. :)

LaptopOwner
2007-08-29 14:24:25
Wireless problem is fixed. :)


Just took 5 minutes away from doing work to get it going again. I d/l the libs that did not upgrade (forgot to write down, shoot me) on the first go 'round, installed them, restarted the network, no go so I logged off and logged on, still no love, and so I finally rebooted the laptop. It still was not showing me anything through the network manager in the right hand corner so I went in and did a:
modprobe ndiswrapper


No error message returned. Next I entered in:
lsmod |grep ndis


It returned:
ndiswrapper 233632 0
usbcore 160560 4 ndiswrapper, ehci_hcd,ohci_hcd


doing iwconfig showed that they were showing up on eth01.


I then went into the network settings off of the menu->system->administration->Network


The wireless info showed up but had the info from the connection I had been troubleshooting. I cleared that out, set it to roam, and immediately found someone's motorola phone.


I learned to never, ever upgrade my system on a flaky connection that suddenly seems perfect. ;)


On the downside, when I am actually around the house now I probably will not be able to use my own laptop.

LaptopOwner
2007-08-30 06:36:28
Something else came up and it was an easy fix. I had to add ndiswrapper back into the modules under etc so it would load at boot. Have no idea why it went missing, but it did and was an easy fix.
Caitlyn Martin
2007-08-30 10:01:49
@laptop owner: I'm glad you took the time and made the effort to solve your problems with Gutsy, now at Tribe 5, rather than rolling back to Feisty. A lot of people wouldn't have the patience or the skills to do what you've done. Working with development code is not for the feint of heart.


Oh, and don't give me grief about having borrowed your laptop. For the last couple of weeks I've used my own exclusively.