Recently in Alps Touchpad Category

Things have gone very smoothly on my third day of using the Xubuntu flavor of Ubuntu 8.04 LTS. While in Xfce (Xubuntu's desktop environment), I haven't had the screen, keyboard and mouse freeze at all.

Wondering whether all this good fortune was really due to starting with the Xfce window manager instead of GNOME, I logged out, changed my WM to GNOME and logged back in.

Everything seemed to be going well. But in the mid-afternoon, I had a couple browser windows open and was writing in Gedit when the thing froze up on me. (Had I saved my document in Gedit? Nope.)

So regular old Ubuntu 8.04 hasn't improved at all. My ability to keep this distro running is somehow due to whatever Xubuntu packages take precedence over those in Ubuntu when logged in with Xfce.

By the way, the Trackpad utility in Ubuntu doesn't show up in Xubuntu, so I modified the xorg.conf in Ubuntu/Xubuntu to turn off tapping in my Alps touchpad by adding the line setting "MaxTapTime" to 0:

Section "InputDevice"
Identifier "Synaptics Touchpad"
Driver "synaptics"
Option "SendCoreEvents" "true"
Option "Device" "/dev/psaux"
Option "Protocol" "auto-dev"
Option "HorizEdgeScroll" "0"
# adding next line in attempt to turn off tapping
Option "MaxTapTime" "0"
EndSection

I've always been pretty happy with Xfce. I used it more often than not in Slackware and always in Wolvix. And with all the tools that Ubuntu keeps across all of its companion distros (including Kubuntu and Xubuntu), running Xfce isn't all that different than running GNOME.

The strengths of Xfce are that the Thunar file manager and Mousepad text editor are lightning fast and quite functional. I'm also OK managing the desktop with the Xfce tools. I discovered that Xorg.conf line to turn off touchpad tapping when I was setting up CentOS 5.2, and I think this is a much better way to deal with the issue than using the Q/G/Ksynaptics package. I believe that in "regular" Ubuntu each user can set up the touchpad according to their individual preferences, but since I don't have any users, potential or real, who like touchpad tapping, turning it off globally in xorg.conf is definitely the way to go.

Now that I'm sure that Ubuntu with GNOME is still screwing up on this hardware, I'll continue using Xubuntu/Xfce for the next few days to make sure everything continues working.

And while I'm reluctant to move off of the LTS to Ubuntu 8.10, that does remain an option. While the LTS' 3-year support timeframe is something I'd like to have, with the "regular" Ubuntu release, there's still 18 months of support, which means I could keep the same system for quite awhile nonetheless. The quality of support (i.e. bug fixes and security patches) for Ubuntu is not something I feel qualified to judge, but the 18-month life of non-LTS releases is something I'm very much in favor of.

Fedora's releases have a 13-month life, and OpenSUSE's are two years, I believe. I think Ubuntu is right where they should be, given that there's also the LTS release with 3 years on the desktop and 5 years on the server. I initially hoped that Ubuntu 8.04 LTS would run well enough that I could ride it out for at least a year, maybe two, without running into problems, and while I've "solved" the problem that has cropped up, not being able to use GNOME isn't exactly the solution I was looking for.

In conclusion: It would be a strange thing indeed if Xubuntu ended up running better on my Gateway Solo 1450 than the flagship Ubuntu distro. While I've had luck with Xubuntu in the past (I think my favorite version was 7.04), regular Ubuntu always seemed to be more polished and stable than Xubuntu or Kubuntu. Until now.

I feel like I'm booting children off a train.

Sure I've had my times when I installed a GNU/Linux distribution, used it for a couple of hours and then pulled it.

But for the past year or so, I've stuck with Debian, first with Etch and then Lenny since Etch went stable in April 2007. And when Ubuntu rolled out its new LTS distro in April of this year, I installed it and have been using it since. My older Compaq laptop has been running OpenBSD 4.2 for over a year, and I've done two very satisfactory Etch installs in the past month or so.

But on my main machine, a 2002-era Gateway Solo 1450 laptop, there's been trouble in GNU/Linux paradise.

After fighting with Debian Lenny for months over the Gateway's screen-refresh problems (which basically render much of that screen unreadable after a half-hour or so of use), I finally decided that I couldn't stick with the Testing branch of my favorite Linux distro on its road to becoming Stable. While many other problems cropped up and were mowed down either by me or the Debian Project itself, this last issue just wouldn't go away. And since I see not even one other person with this same problem, I fear the issue will never be resolved. I don't even know which package to file a bug against.

Remember when I thought I fixed my random-screen-freeze problem on this same laptop in Ubuntu 8.04 LTS? I thought that turning off automatic suspend in GNOME fixed the problem.

That didn't work. I still have random freezes. And I can't really blame it on the power plug because I've been in conditions where that plug does not move, and moreover these freezes never happened in Debian (when my screen image was not totally disintegrating, that is).

I was trying to get some pre-election work done on http://www.dailynews.com, and when I found that I didn't have the Java runtime installed (and needed it), I moved over to Ubuntu 8.04. In a half-hour, I had three unrecoverable crashes.

Again, I haven't heard of this happening to anybody but me.

I have TWO surplus laptops waiting in the wings. I'll see if any of them perform as well as or better than this Gateway. But whatever happens with those two machines, the Gateway will remain in service.

Once I decided to let go of Debian Lenny, I thought I would try Fedora 9, but when the live CD wouldn't let me install it, I turned to CentOS 5.2 — the free version of Red Hat Enterprise Linux — instead.

I first booted the live CD, then used the live CD to do a network install (NOT from the live environment but as a boot option). Once I determined that an http install wouldn't work but an ftp install would, I was off and running.

I've been testing CentOS 5.2 for about a week now. I've been slowly solving problems (adding things like Pidgin and Flash), and at this point I can say that CentOS 5.2 boots quickly, seems as snappy on this hardware as Ubuntu or Debian and runs extremely well.

I have yet to see a bug, and it has never crashed.

I have a full review and how-to for CentOS 5.2 in the works.

I hadn't anticipated replacing Ubuntu 8.04 LTS. I've had trouble with Ubuntu on this laptop since 7.04, and I've gone back and forth with it. Until I pulled it last week, I always had either Debian Etch or Lenny running on it. I've run Puppy 3.01 from live CD and the Slackware-based Wolvix Hunter — both with few problems.

The 2.6.18 kernel in CentOS 5 has always run better than any other on the Gateway. Other distros that share this kernel (albeit in slightly different versions) include PCLinuxOS 2007 and Debian Lenny.

And with support for RHEL/CentOS 5 slated to last a very, very long time, the fact that it runs so exceedingly well on this hardware gives me a true long-term solution.

I suspect that if I rolled the older Ubuntu 6.06 LTS — which has a little over seven months of support left before it EOLs — onto this laptop, it would run flawlessly. But it's packages are even older than Debian Etch's ...

As it stands right now, I'm going to stick with CentOS 5.2, and as much as I don't want to do it, I need to drop Ubuntu 8.04. I love Ubuntu — its philosophy and package mix, if not its brown color scheme. But I can't deal with the random freezes (after which ctrl-alt-backspace and ctrl-alt-delete are useless and only a hard reboot will work).

Aside from the screen-refresh problem, Debian Lenny was doing great. It improves on Etch in many, many ways.

I could see myself returning to Etch, which will have a full year of support as Debian's Old Stable distribution once Lenny is declared stable.

Whether I continue using this laptop or not, it has to run my daughter's educational games (GCompris, TuxPaint and Childsplay), and it has to be as stable as possible.

With Etch on the Gateway, I had trouble with the Alps touchpad, but since those problems were so easily solved in CentOS 5.2, perhaps I've learned enough to figure them out in Etch, where in addition to the touchpad-tapping issue the speed differences between the touchpad and a plugged-in USB mouse were more than a little incovenient.

I remember PCLinuxOS running as well as anything during the week or so I used it. I wonder how much support is left for the 2007 edition of that distro. The hype over PCLinuxOS has really slowed down over the past year, but I still think it's a very solid distro (based on Mandriva but with Debian-style apt and Synaptic package tools).

I've had trouble with X in Slackware on this platform, never seeming to get xorg.conf right, although Slack-based Wolvix runs perfectly for some reason. Slackware-based ZenWalk has all the packages I need and during the brief times I've run it has show itself to be extremely fast.

And since I'm running with separate /home partitions for both distros on this PC, switching those distros in and out should be less traumatic than in the past.

Even though I've taken great pains, after the fact (when it's harder to reconcile), to keep my user accounts' UID and GID numbers in Debian- and Red Hat- based distros compatible, I will probably dual-boot Fedora and CentOS for a while just to see how they match up on this hardware.

Depending on how things go with CentOS 5.2, I could eventually simplify things and do the unthinkable: not dual-boot anything.

CentOS seems terribly boring. But ever since Red Hat rolled a bunch of newer apps into its RHEL 5.2 (the base for CentOS), including Firefox 3 and OpenOffice 2.3, I've seen it as a very real alternative for the desktop.

And I neither expected it to run so well or for Debian and Ubuntu to run so comparatively poorly on this specific hunk of hardware.

If I had 10 test machines and Debian or Ubuntu ran flawlessly on them, I would be telling a different story, but from the perspective of this 6-year-old Gateway, RHEL/CentOS is pulling way out in front.

This wasn't the first time I tried Fedora — or Fedora 9 for that matter — via live CD. I must have burned my first CD of the distro soon after it was released.

Now that I was resolved to replace Debian Lenny on The $0 Laptop (Gateway Solo 1450) with ... something that didn't have Lenny's seemingly unsolvable screen-refresh issues, I decided to give Fedora 9 a try. I knew that it was a little less than three weeks until the release of Fedora 10, but since I was ready now, Fedora 9 it was.

I first tried the live CD on my Dell desktop. It booted, but not after the usual Fedora disc access errors, which take up a minute of time before the disc boots and then seem to have no effect whatsoever on subsequent loading and performance of the OS and applications.

Fedora 9 loaded, I configured the network and then ran the system for awhile on the Dell.

Then I needed to prepare the Gateway. I plan to keep Ubuntu 8.04 LTS as the main distro on the laptop, so that part of the installation was going to stay exactly as is.

Before wiping Debian off the drive, I rsynced the Lenny /home files to Ubuntu's /home partition. (I did forget to archive my Puppy 3.01 configuration, which I'm not happy about losing.)

Previously I had Ubuntu set up to have its own separate /home partition on the extended partition. Debian, however, had the root and /home directories on the same partition.

This time I wanted each GNU/Linux distribution to have their own separate /home partitions.

Here's how I divided up the 30 GB hard drive:

I started with a 1 GB swap partition on hda1. Then came Ubuntu's root partition on hda2 and space for a Fedora root partition on hda3, about 10 GB each.

The rest of the drive was configured as extended partition hda4. On that extended partition, Ubuntu's /home directory was living on hda6, and that left hda5 for Fedora's /home directory.

This way, if any of these two distros needs to be replaced, the /home partitions should remain intact and can be used as /home for any other Linux distros that could potentially take their place.

I also planned to keep Ubuntu's GRUB bootloader on the master boot record with a stanza in its menu.lst chainloading to a second GRUB (or LILO or ...) located on the secondary distro's root partition. I've found that setting the bootloaders up this way solves all problems with menu.lst updating when new kernels roll through the two distros on the drive.

Before I began, I downloaded a new Fedora 9 ISO and burned a new disc. I booted the new disc on the Gateway, and while I got the same errors early in the boot sequence on the Gateway as I did on the Dell, the disc did load, and I was in the GNOME desktop in fairly good time.

After checking out Fedora for awhile in the live environment, I was ready to install.

I always like live CDs that allow you to install while in the live environment. It's one of the things that makes distros like Ubuntu and PCLinuxOS so successful. You can try the distro with a live CD and if the hardware responds even halfway well, install right then and there.

I clicked Fedora 9's "Install Fedora to disc" icon.

Nothing happened. I clicked again. And again. Still nothing.

I rebooted the live CD and tried to install again. It wasn't working.

At this point I could've begun downloading the install images and burning them to disc, but I didn't.

I liked the fact that Fedora has a fairly deep repository that included most of the applications I wanted. I wasn't crazy about needing to upgrade every six months — especially upon seeing the Fedora Project's recommendation that you do a full install instead of the kinds of upgrades you're encouraged to do in Debian and Ubuntu (as in changing your sources.list and update/dist-upgrade).

And I don't know whether it was my hardware that refused to install Fedora from the live CD, or a glitch that affected every user of the live image, but I was ready to move on.

Wiping Debian Lenny from the drive was a big step, since I'd been running the distro for well over six months on the laptop and had grown quite fond of its many improvements over Etch. But my X configuration's refusal to cease slowly degrading during every computing session made it easy to run Ubuntu more as well as consider jumping back into distro-hopping mode for a secondary system.

At this point, it's all about having a reliable pair of distros on the laptop that each allow me to get work done without causing problems.

Coming up next: Now that Debian Lenny was gone and Fedora wouldn't install, I turned my attentions to CentOS 5. I had done a couple of successful CentOS 3 installs on a different system, and ever since Red Hat shook up its Enterprise Linux with newer packages and a greater emphasis on the desktop experience with version 5.2, I had been eager to see how it played out in CentOS's 5.2 clone of RHEL.

Here's the deal: I've been fighting with Debian Lenny for months on The $0 Laptop (Gateway Solo 1450), where I have everything running great except for my persistent problem with screen refresh in X. I've replaced the Intel i810 driver with the plain Intel driver, I've tweaked everything that can be tweaked in xorg.conf.

I can't really get work done while my display is slowly disintegrating during the course of a computing session.

I'm already running Ubuntu 8.04 LTS as the main distro on this system, and I've been thinking about what to do for the second distro. I'd go back to Debian Etch, but I had problems with the speed of the USB-connected mouse vs. the Alps touchpad, plus problems controlling the touchpad on its own.

In Lenny, the problems I've dealt with (and mostly solved) over the past six or more months have included suddenly disappearing sound (fixed with manually installed ESS Allegro modules), and an Epiphany browser that would always start in offline mode (fixed with a modification to Gconf2, if I have the name of the app right).

Nothing major — and nothing that couldn't be fixed with some help from either the bug reports themselves or other helpful people on the Web.

But this screen-refresh problem persists. I keep hoping that a routine software upgrade will take care of it, but that hasn't happened in countless xorg, driver and kernel updates. I don't think it's going to happen, either.

If you're running something that's very popular that catches the attention of developers (like the Asus Eee PC), chances are good that issues will be resolved. But I can't imagine any developers anywhere are paying any attention whatsoever to my 2002-era Gateway laptop. I'm no C hacker, so there's nothing much I can do, either.

I love Debian. I'm running two newish Etch installs right now (one PowerPC, one i386), and I could very well add a third with my $15 Laptop (Compaq Armada 7770dmt), or even more to a couple of testing desktops I have waiting in the wings. Whenever Lenny goes Stable, Etch will have another year's worth of patches as Old Stable before it reaches its end of life.

Etch has been great, and Lenny has made dozens of improvements. But this one regression has made it very hard to keep my favorite distro on my main laptop.

So I have been thinking for months about what to do, all the while hoping that I could fix the X problem in Lenny.

First of all, I need to rewire the power supply plug. I think that is what is responsible for my intermittent freezes in Ubuntu (which don't seem to happen in Lenny, for reasons unknown). When I have the laptop on a desk, it never freezes, but when it's on my actual lap, as it was when I was trying to work on last-minute election programming yesterday morning, those freezes can really throw me off. I moved over to Debian, but I needed the Java runtime, didn't have it installed and didn't have the time to do that.

And then there's the video issue.

So I've been thinking, what should I install in place of Debian Lenny? I'm a big fan of long-term support releases, especially for older hardware, so I strongly considered CentOS 5, a clone of Red Hat Enterprise Linux 5. But the relative lack of consumer-oriented software had me worried. I could add the Dag Wieers repositories to deal with that issue, but even that repository doesn't cover everything I need.

Mandriva is also on the table, as is one of my favorite distros, Wolvix. The Slackware 11-based Wolvix is due for a new version soon. While its package mix addresses most of my issues, there are a few things that I can't easily find for it. And I worry in Wolvix's case (as well as Slackware's in general) about how long the kernel goes without getting patched.

I almost never see new kernels for older Slackware releases. I don't know if that's because they are unnecessary, but with patched kernels rolling into Debian and Ubuntu fairly regularly, I wonder why Slackware does things differently.

I'd run "regular" Slackware, but I had quite a bit of trouble getting X configured, and I'd rather use GNOME than KDE. I know there are GNOME projects for Slackware, but what I'm trying to do is install something that works well, comes together easily and has lots of available packages.

Given all the Mandriva fans on LXer, I considered it. I've used the Mandriva-derived PCLinuxOS and thought highly of it — and I may in fact go that way. The 2.6.18 kernel in PCLinuxOS 2007 (Debian Etch is also built on that kernel) is perhaps the best ever for the Gateway in that it controls the CPU fan with no intervention. The intervention needed in other kernels is slight (a single line in /etc/rc.local usually does it), but it's nice to have it done automatically.

Again, I'm not a huge fan of KDE, and I find that distros that are either KDE- or GNOME-centric tend to treat the other desktop environment as something of a second-class citizen.

I've had Fedora in the back of my mind for a while. Seeing all the packages available is very encouraging. And the Fedora community looks like a very good resource in terms of getting things working. I imagine that quite a bit of RHEL information would apply to Fedora as well, giving the distro an even deeper bench.

I'm not crazy about the length of support for a given Fedora release, which looks to be 12 to 13 months. I'd feel better with the 18 months that Ubuntu's non-LTS releases get, or even a full 2 years. Compromising on length of support is something I'm willing to do at this time for something that potentially gives me all the packages I want and that runs well besides.

As far as the availability of packages goes, Fedora acquits itself well. I have run it from the live CD before, and it seemed to do well on the Gateway.

In a slightly related matter, my install of Fedora 9 on my Power Mac G4/466 didn't go so well. The X configuration was horrible, and the distro ran much slower than Debian Etch on the same hardware. And Debian did a perfect X configuration for the internal graphics card and huge LaCie electron22blue monitor. Sure I could've used the information from the xorg.conf in Debian to properly modify the same config file in Fedora, but with such a performance hit, it didn't seem worth it.

Since the 1.3 GHz CPU and 1 GB of RAM in the Gateway offers much more power than the 466 MHz and 384 MB in the G4, Fedora seems to run fine on the faster machine.

And now that I have the Ubuntu LTS as my main distro (and hopefully a trouble-free one once I replace that shaky power plug), it's time to try something else.

First I need to keep copies of the xorg.conf, my CPU-fan script and rc.local from Debian Lenny in case I do a reinstall. Then I need to back up the /home files and consider adding a separate /home partition for the secondary distro (Ubuntu already has a separate /home partition).

Again, I'm not happy about the 13-month life cycle of any given Fedora release, and I really don't need a cutting-edge kernel for my not-cutting-edge hardware (unless, of course, it makes a cheap wireless adapter work), but with /home on its own partition, and Fedora installing GRUB on the root partition instead of the master boot record, with the GRUB on the MBR chainloading to the Fedora partition, it shouldn't be hard to roll Fedora out and something else in.

I could change my mind ... or not.

Update: OpenSUSE offers about two years of support per release, and that is enough to get me interested.

I'm downloading new OpenSUSE 11 and Fedora 9 ISOs now, and I'll burn them in the morning.

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.

I booted into Debian Lenny for the first time in a while on the $0 Laptop (Gateway Solo 1450), and after doing about 150 updates, I logged out of the GNOME desktop and switched over to Fluxbox.

Now this PC, for me, anyway, is quite powerful — 1.3 GHz Celeron, 1 GB RAM — so GNOME runs quite well on it.

But with Fluxbox (and even with Xfce, I suspect) it really flies. Apps load way quicker than they do in GNOME, and if you can deal with a more minimalist window manager, you get a lot more in terms of performance.

I had my Alps Touchpad's tap-to-click function turned off in GNOME, but in Fluxbox I had to use GSynaptics to turn it off. I wonder if things will be screwed up in GNOME as a result. The first thing I'll do is see if I can easily turn off the touchpad's tapping for my other users. That doesn't work so well in GNOME, where the "primary" user has control over the touchpad but the others do not.

I logged into one of my other user accounts, turned off tapping in GSynaptics, and everything worked. That's the way it's supposed to be in GNOME.

One thing I'd like to do is modify the Fluxbox menu to make things quicker, with my most-used apps higher up so I don't have to mouse through so many menus to get to them.