It shouldn’t be news that Ubuntu worked all day without crashing

I ran the $0 Laptop (Gateway Solo 1450) all day today and didn’t have a single crash, a single problem with X, or any other kind of problem.

Among the things I did today:

• I used rsync to bring the /home file from my previous Ubuntu 8.04 installation into the new one (which now has /home on its own partition). It only took me three tries to get the right rsync command to a) work and b) put everything in its proper place. Rsync is too geeky, but I was able to muddle through.
• I somehow managed to get Google Docs working offline with Gears. While the Docs/Gears offline thing came together immediately for me in Wolvix Hunter a couple of months ago, getting my documents to show up offline with Firefox 3 in Ubuntu 8.04 has been a bit of a challenge. Something happened today — I can’t say what — but it appears to be working fine. We’ll see what happens when I fire up the laptop later. P.S. Google Docs offline is still a bit too slow for comfort.
• Debian Lenny’s X problems (artifacts on screen) persist. I remain unhappy in that respect.
• Three geeky cheers for Ubuntu, eh?

I was about to praise Ubuntu …

I still might be in a position to heap praise upon Ubuntu 8.04 for its performance on the $0 Laptop (Gateway Solo 1450) since I reinstalled it a couple of weeks ago with a separate /home partition and a not-screwed-up UUID scenario.

But I keep getting these freezes in which ctrl-alt-backspace or ctrl-alt-delete won’t save me. I have to do a hard reset with the power button.

Now this could be due to the shaky nature of my power connection (the power jack from the laptop’s brick doesn’t quite meet up with the hacked power plug I installed to make this laptop work after I first acquired it). Having a dead battery doesn’t help.

I need to figure out whether my freezes in Ubuntu are due to the OS itself or due to the flaky power situation.

I finally got a replacement power jack at Fry’s that I could use on the power brick to make a foolproof connection.

It could be chance, but this freezing problem never happens in Debian Lenny, which has problems of its own (related to X refresh, and chronicled in agonizing detail on this very blog).

I will confirm that suspend/resume continues to work, as does everything else. Except for this cursor-freezing.

Again, I’m not ready to blame Ubuntu and am more inclined to blame the power jack/plug situation. I am keeping an eye on the problem.

Another 150 or so updates rolled into Debian Lenny recently, including new Xorg and Intel video driver packages. For the upteenth time, I’m hoping for the miracle of properly refreshing X. It didn’t do so well yesterday just after the updates, but there were some “enhancements” to the Debian login screen, principally the word “Debian” appearing in the upper left portion of the screen.

Again, my hope is that this X problem somehow solves itself and I can continue using Debian on this laptop. Again, no breath being held.

Double-tapping in Debian Lenny

I turned on touchpad tapping today in Debian Lenny on the $0 Laptop (Gateway Solo 1450), and I had forgotten the one thing that makes the tap-to-click function work so well in Lenny:

Double-tapping.

By that I mean it takes two taps to count as a left-click. That way, every time I use the touchpad to move around the screen, I’m not mistakenly left-clicking on things and screwing up everything I’m doing

I also turned on touchpad scrolling, by which sliding a finger down the far right of the touchpad mimics scrolling up and down with the arrow keys.

Note: Double-tapping only seems to work if the settings are just right. I will report later on just what those settings are.

Another Ubuntu install bites the dust

I always seem to have trouble with Ubuntu. On the $0 Laptop — the Gateway Solo 1450 — there comes a time in every Ubuntu install when the thing either won’t boot or runs so slowly that I have to wipe the thing off the drive and start over.

It could be something particular to this laptop, the hard drive in it, or my constant dual- and triple-booting of Linux and BSD operating systems in a constantly shifting array.

When I use recovery mode to boot Ubuntu 8.04 and see the messages scrolling across the screen, I can see the point where it stalls. Something about ATA 2.01 is pausing for 5 seconds to look for devices. This pause used to be only 5 minutes, but today it appeared to stretch forever.

I had (and have) work to do, so I ctrl-alt-deleted out of there and booted Debian Lenny. I’ll take the annoying screen artifacts problem in Lenny any day over not being able to boot at all in Ubuntu.

The Ubuntu problem began after an aborted installation of FreeBSD about a month ago. And even though I wiped that partition right away and have reformatted it a few times, Ubuntu still stalls during the boot sequence.

Now that I sort of, kind of know how to use rsync to backup my /home files, I need to delete the Ubuntu partition and start again. I have a funny feeling that I’ll still have a problem. It could be the hard drive. I have an old 30 GB Toshiba drive in here that I bought on eBay, and it’s probably not the ideal drive for daily use, it being old and all, but it’s what I’ve got, and I’ve never had a problem before. … Except for these Ubuntu problems (7.04 and 7.10 didn’t fare too well in this respect; I thought that 8.04 would be OK, but that hasn’t turned out to be the case).

Anyway, gotta get back to work, so I’ll be auditioning distros soon enough to see what’s going to work for me. I’m almost at the point of throwing CentOS on the box. I’m worried that I’ll be missing packages and codecs that I need, and I’m nowhere near good enough with RPM repositories and packages to figure it all out. That’s what I count on the people from Debian and Ubuntu for …

I’ve really enjoyed using Ubuntu this go ’round. Everything has worked better than ever … except for this not being able to boot. That’s quite an “except,” don’t you think?

Update: The Ubuntu partition does boot; it just takes a long time.

A new Debian Lenny kernel and X packages

Debian Lenny — on this laptop anyway — just got the 2.6.26 kernel, along with X packages that, once again, have a chance of making Debian Lenny’s ghosting problem go away when I run X.

Basically, I’ve concluded that for some reason the screen isn’t properly refreshing during the course of the X session. (The hardware in question is a Gateway Solo 1450 with the Intel i810 video driver).

Lately I’ve been able to run xrefresh in a terminal and clear things up, but since this problem only exhibits itself in Debian Lenny and not in Debian Etch, Ubuntu, or anything else I’ve ever used on this laptop, I’d like to believe that said problem will somehow be miraculously solved, like the other half-dozen or more potential deal-breaking issues I’ve had with Debian Lenny over the course of its use on this PC.

What I’m saying is that after a whole lot of fiddling with xorg.conf, I can’t seem to fix the problem myself, and I hope the fine Debian Developers out there will do it for me.

Once again, everything’s looking good in my preliminary testing, but that optimism seems to fade rather quickly as things turn to their usual crap as the X session wears on.

As always, I’ll report back when I know more.

Later: My X refresh problems continue as before.

My latest warning against dual- and triple-booting Linux and BSDs

My advice is to avoid dual-booting, and especially triple-booting (or even more than that).

If you set up a box to dual-boot with two Linux distros, Linux and Windows, or even a BSD (OpenBSD, NetBSD, FreeBSD) and Linux, and you leave it alone, you’ll probably be OK.

But me, I’m testing things all the time, and lately I’ve been playing around with triple-booting on my Gateway Solo 1450 laptop. I’ve done this a lot, and I generally know how to do it so I don’t hose one partition or another.

But I slightly hosed something on the laptop last night.

I’ve been playing around with FreeBSD, trying to figure out why it sometimes manages my CPU fan extremely well but usually not at all.

I have FOUR primary partitions on the 30 GB hard drive. The first is Linux swap, the second is Ubuntu 8.04, the third Debian Lenny, and for a long time the fourth was just an empty Linux ext3 partition where I could stash files large and small.

I started throwing new OSes on it about a week or so ago. I had PC-BSD on there, FreeBSD, Debian Etch …

And last night I did another FreeBSD install. Now remember, I had FOUR primary partitions. As far as I know, no BSDs will install on a secondary partition. And in Linux, — again, as far as I know — you can only have four primary partitions. If you want more than that, you need to make one an ‘extended’ partition, and then you can fill that with a much larger number of secondary partitions (I’m not sure of the total number in Linux, but it’s a lot).

When I was installing FreeBSD to the fourth primary partition, I veered from my usual practice of installing it in a single FreeBSD partition and instead let the installer auto-partition the portion of the drive set aside for FreeBSD.

Long story short, I think I screwed something up.

I deleted the screwed-up FreeBSD partition and replaced it with another Linux ext3 partition, but that didn’t seem to “fix” whatever problem it is I’m having.

Debian Lenny boots fine. But Ubuntu 8.04 stalls in the middle. It eventually does boot, but there’s a stall of a few minutes in the boot sequence. I booted in recovery mode to see what was going on, and it does appear to be disk-related, but I’m not quite sure what to do about it. I already deleted the “offending” partition, but maybe I shouldn’t have replaced it (or so quickly before testing the other partitions)?

It’s been over six months since I hosed a whole box, so in the grand scheme of things I’m not doing too badly.

But I should really start following my own advice and stop dual-booting on what, for me at least, amount to “production machines,” which I rely on to get work done.

When experimenting, I need to swap whole drives instead, like I do with my VIA C3-based converted-thin client test box, which has three drives that are easily swapped via power and IDE cables that extend well outside the thin client’s small case.

I didn’t hose things so badly that I either lost files or can’t boot either of the two Linux distros on the box, but I really need to be more careful, especially when mixing BSDs and Linux.

When doing just that, incidentally, I’ve had a lot more success by installing the given BSD FIRST, then throwing Linux on the box after that.

What I think I’m going to do, when it comes to Linux anyway, is to have the first partition be swap, the second partition for the distro itself and the third partition for /home. That way I can theoretically swap in new distros and keep the same /home file (backing that up, of course).

Now I’m going to think of what to install on the Gateway Solo 1450 to single-boot it for awhile.

One thing that preload helps run quickly: OpenOffice

OpenOffice Writer starts in about five seconds in Debian Lenny on my Gateway Solo 1450, and I have to think the preload app is responsible.

I’ve written before about how preload doesn’t seem to have any effect on Iceweasel and Epiphany, which I’d sure like to start more quickly, but with OpenOffice, preload seems to be doing its job.

While on the topic of Open Office, I should mention that I’ve been using it quite a bit lately. I like the way the fonts look way better than those in Abiword, and OO just seems to be working well, so I’ve taken to it quite a bit more than in previous months.

Oh, and Google Docs offline under Google Gears has been pretty much a big disappointment.

Since I started using it (with Firefox in Ubuntu), it has lost my database once, and is dog-slow the rest of the time. I hate starting Docs offline in the browser and waiting an age for my files to show up. With this kind of performance — which is in much contrast to Google Docs’ swiftness when connected to the Internet, I’d much rather use a traditional word processor or text editor.

Hence my increasing use of OpenOffice.

Debian Lenny update: so far, much better, and we also have ‘Etch and a half’

Now that Debian’s current testing release, code name Lenny, has been frozen, we’re this much closer to seeing Lenny become a Stable release, a milestone that is projected for September of this year. That would make it a year and four months after the current Stable release, Etch, was so designated in April 2007.

For those using Etch now, keep in mind that once Lenny becomes a Stable release, Etch will receive the designation Old Stable and continue to receive security patches for another year.

While on the subject of Etch, it’s interesting to know that the install images have been updated, and along with that update comes a 2.6.24 kernel as an alternative to the 2.6.18 kernel that shipped with the initial release.

This new Etch, dubbed “Etch and a half” by the Debian team. With the new kernel comes additional hardware support. For details on the new packages and bug fixes, go to the release announcement.

I don’t think that the decision to add hardware support to Etch at this stage has anything to do with Red Hat’s similar move with its Enterprise Linux product, but it’s interesting to see both distros going in this direction.

Back to Lenny: I still have 84 updates to do with Lenny, but I’m holding off for the moment because I’m at home, and when I start a big download, I tend to dominate our home DSL connection. My Netgear router tends to dedicate almost all of the bandwidth to the huge download, and my wife, Ilene, who is using the iBook G4 on this same router, can barely use Firefox.

I don’t know if there’s some kind of setting in the router I can tweak to more equitably share the bandwidth, and if there is, I’d sure like to know about it.

No, really … back to Lenny: One of today’s updates, which I will install later, is a new Abiword, which will go from version 2.4.6 to 2.6.4. I noticed considerable lengthening of the load times for Abiword in Puppy Linux 4, which uses an Abiword from the 2.5 series, over the 2.4.5 version in previous Puppy builds.

The $0 Laptop — a Gateway Solo 1450 with 1.3 GHZ Celeron processor and 1 GB of RAM — loads Abiword almost instantly, and I’ll be anxious to see if that changes with this new version.

Since my last Lenny update, Firefox/Iceweasel 3.01 has been performing well. The “work offline” issue has been fixed, and I don’t have to uncheck the box every time I start the browser.

One thing about Iceweasel 3 that I like is that the fonts have been cleaned up. Debian has been using what appear to be bitmapped fonts, as opposed to smoother varieties, for quite some time. These look better on LCD displays, but I’ve grown so used to them that I just leave them on the lone CRT monitor I still use.

But now that the fonts are looking so much better right out of the box, I’m just happy to see the screen looking better in Firefox.

OpenOffice 2.4 has been running very well, and I’ve been using it quite a bit more in Debian, Ubuntu and Windows, the latter of which needs an update from what I think is version 2.2. Since I don’t get prompted for an upgrade on the Windows box, I get very lazy about doing them at all.

Going to Windows for a moment, my main Windows text editor, Notepad++, just pushed an update to me yesterday, and I did download and install it. I really am not good about checking Web sites for updated applications, and I do appreciate when the program itself tells me about a new version. Filezilla also does this in Windows, and of course Firefox and Thunderbird always notify me about updates.

Back to Lenny, again: When I wanted to test the KDE photo editor Krita and camera-interface digiKam, a ton of KDE apps and libraries came along for the ride. Since then I’ve also added Xfce, and as a result this Debian Lenny installation is quite large. I might want to redo it at some point with just the default GNOME desktop and Xfce added, just to keep it a little more manageable. But to the Debian Project’s credit, things are working quite well, and many issues have been resolved on Lenny’s road to Stable.

I’m still getting the “ghosting” in the upper panel in GNOME, but it does seem to go away at various times in the computing session. The same thing doesn’t happen in Ubuntu, so that makes it a bit of a mystery.

And if I could figure out why and how Ubuntu is able to suspend/resume this Gateway laptop and make Lenny do the same thing, I’d probably use Lenny a whole lot more.

I’m pretty much a “Stable release” kind of person. I would’ve been content to use Etch all the way through up until Lenny goes Stable, but since Lenny ran so much better on this laptop, most importantly supporting the touchpad better, I decided to follow it through on the road to it becoming a stable Debian 5.0.

Since then, I’ve also tried Sidux, which takes the unstable Debian Sid and makes it easier to use as a desktop system. My time with Sidux was brief, but it pretty much flew on this system as a live CD loaded entirely into RAM.

I had planned to write a full Sidux review, and I still might, but since I’m more inclined to run a Stable release over Testing, I can’t see any reason to run Unstable, even with the Sidux team smoothing the way. I just don’t need the latest packages that quickly to get my work done.

Quick Ubuntu note: Being so “Stable,” in my own mind at least, I had planned to continue running Ubuntu 8.04 LTS for at least a year if not two, but the upcoming Ubuntu 8.10 release promises something I really want: encrypted folders. Instead of encrypting whole drives or partitions, which Debian (and Ubuntu with the alternate installer) has done since Etch, the ability to only encrypt what is really “sensitive” is something that I could really use. Such an ability would speed up the system, since there will be much less to unencrypt, and it would also make it easier to choose to use or not use encryption.

So will I upgrade when October arrives? I’m not sure yet. 8.04 runs so well on this laptop that I’m loathe to mess with it.

Related:
Debian mailing list announcement of Lenny freeze
Sidux 2008-2 release notes
“Etch and a half” announcement

Debian Lenny — things are happening

Things are happening in Debian Lenny, and not just in my installation.

OK, mostly in my installation.

For one thing, something — I have no idea what — made the GNOME Network Admin package disappear. I couldn’t change my network settings from the System–Preferences menu or the icon I have in the panel for that very purpose.

I went into Synaptic and reinstalled it. Now it works.

I’m still having the “work offline” problem with Iceweasel (aka Firefox) 3. Whenever I start the browser, I’m automatically in “work offline” mode, regardless of whether I’m actually online or not.

I also still have the “ghosting” on the upper GNOME panel.

Right now I’m doing a software update. Among the new packages is a kernel update. Will this solve my problems? And will I have to reinstall the ALSA sound modules for my ESS Allegro/Maestro3 chip in the $0 Laptop?

After the update: The Debian Lenny updates included a 2.6.25 Linux kernel, but boot code for the new kernel didn’t get written into the menu.lst that controls the Ubuntu-installed GRUB, which controls the master boot record for this dual-boot system.

It turns out that Debian only updated its own /boot/grub/menu.lst, so I copied the new entries over to Ubuntu’s /boot/grub/menu.lst to try the new kernel.

This appears to be the SECOND 2.6.25 kernel in Lenny, but it’s the first I’ve seen of it, and without Ubuntu’s menu.lst being updated automatically, a new Lenny kernel is easy to miss.

I understand that dual-booting can pose a problem, but I thought that Debian pretty much knew to look for multiple GRUB configurations and update them all. I guess not this time.

In Lenny with the 2.6.25-2 kernel: Sound still works in the new kernel. (After manually jump-starting sound in 2.6.24, I didn’t expect it, but thankfully it does.) Either the Debian developers decided to re-support my sound chip, or my manual installation of ALSA drivers stuck.

Iceweasel 3 still defaults to “work offline” status whenever it’s launched. The same problem still (again, thankfully) doesn’t affect Epiphany.

The upper panel in GNOME still suffers from the same “ghosting” problem.

Looking at the bug reports, which I did in a very recent post, tells me that the Iceweasel problem is not so much with Iceweasel as with NetworkManager. I can pretty much confirm this, since mousing over the NetworkManager icon in the upper GNOME panel says that there is “No network connection,” where there indeed there is. I probably should be looking at bug reports for NetworkManager and not Iceweasel.

I couldn’t find anything in Debian’s bug reports, and nothing leaped right out of this large page of GNOME bug reports.

Ubuntu 8.04 LTS update: Almost four months have passed

It’s been a little while since my last report on how Ubuntu 8.04 LTS has been doing on the $0 Laptop.

In short, all continues to go very, very well. At this point I could see ratcheting down my use of Debian on this machine and pretty much devoting it to Ubuntu all the way.

Why? Everything in Ubuntu works with as little effort as possible.

I have made some strides in getting Debian Lenny working better on the Gateway Solo 1450. I got sound to return by installing the ALSA modules myself. I’m having a problem with the upper GNOME panel looking a bit funky at times, with graphical “ghosting” marring its appearance. It’s not a deal-breaker, but it also doesn’t happen in any other distro.

And again, Ubuntu just does what it’s supposed to do.

I still haven’t conquered suspend-resume in any other distro. In Ubuntu, that just worked.

If for some miraculous reason suspend/resume works in CentOS/RHEL 5.2, I’ll re-evaluate things, but a test of 5.1 today confirmed that it does not work out of the box. And I tried to install 5.2 on a free partition with the super-small network installer, which hung up early in the process. I bailed out of it and figured I’d forget about the whole thing until the CentOS 5.2 live CD image is released.