As Gutsy dies, Feisty rises from the ashes

By Steven Rosenberg on December 12, 2007 6:00 PM | Permalink | Comments (0) |

The Ubuntu 7.10 Gutsy install on the $0 Laptop (Gateway Solo 1450) performed admirably for its first few months, but after a couple weeks of inactivity I had trouble during a software update. Everything slowed to a crawl. Apt and Aptitude worked, but any other kind of package management (Add/Del Programs, Synaptic) slowed the system to point that the only way to regain control was a hard reset.

So I reinstalled Gutsy from scratch. Gone was the Feisty-era kernel that expertly managed the $0 Laptop's CPU fan, and this install started exhibiting the same sludgy symptoms almost immediately.

Did a recent update break Gutsy?

I found no evidence to support this from the Ubuntu forums, nor anywhere else.

But I wanted to install wine and Internet Explorer the easy way, and even that wasn't working in Gutsy.

Then I broke my vow to stop dual- and triple-booting and put Slackware 12 in my last available partition. I purposefully installed LILO, and could boot Slackware from the $0 Laptop for the first time. And while I got X working with the frame-buffer version of xorg.conf, resolution was way less than optimal. It was probably running at 16 colors. Still, Slackware -- even in KDE -- was very, very fast. Had I been able to get X right, I would've been tempted to turn the entire laptop over to Slackware.

I tried every xorg.conf that Slackware had in /etc/X11. I tried both the whole file plus the monitor portions of xorg.conf files from Ubuntu 7.10, Debian 4.0 and Puppy 3.00. Nope.

Then it was time to reinstall Ubuntu. I did the only reasonable thing. I put Ubuntu 7.04 Feisty in the No. 1 slot. That brought back GRUB, and I was able to boot Ubuntu -- running fine now -- and Debian. But the GRUB entries for Slackware? None of them work. Kernel panic on all. Then I replaced references to sda with hda. Two got farther than that, but I was left with blank screens and no login prompt. I couldn't for the life of me figure out how to set GRUB to successfully boot Slackware 12.

Here's what I had:

# This entry automatically added by the Debian installer for an existing
# linux installation on /dev/sda5.
title Slackware Linux (Slackware 12.0.0) (on /dev/sda5)
root (hd0,4)
kernel /boot/vmlinuz-generic-2.6.21.5 root=/dev/hda5
savedefault
boot

Next thing I'll try: adding initrd lines to see if that gets it going.

I'm not ready to give up on Slackware via GRUB yet, but does it have to be so damn hard?

New ways to sign in to comment: I just added the ability for prospective commenters on this blog to sign in using their AOL, Yahoo! and Wordpress.com accounts (for the past 200 posts anyway ... more than that will take an extensive, middle-of-the-night rebuild). That's in addition to the other sign-in choices, which include starting a Movable Type account on this blog, Typekey, OpenID, Live Journal and Vox. If you have trouble getting your Movable Type account verified, or any of the other sign-in options are not working properly, please e-mail me. With these added ways of signing in, there's more reason than ever for you to make a comment (or several!).