Recently in The $15 Laptop Category

You can run 233 MHz of CPU with 144 MB of RAM, but you can't hide

| | Comments (1) |

I cleared the enormous 22-inch CRT monitor, then the smaller 15-inch LCD monitor and the accompanying keyboards and mice off the desk and plopped the $15 Laptop — the 1999-era Compaq Armada 7770dmt down, booted into my built-from-standard Debian Lenny install with minimal Xfce (with / under 1 GB), updated for the first time in a long time and opened the Opera Web browser (about the only one that will run acceptably well on this aged 233 MHz CPU).

I turned on Opera Turbo browsing — I'm using Netgear power-line networking to my converted-garage office — and aside from some fuzzy graphics, all is looking and working fine.

In contrast with my converted thin client and its somewhat botched Xfce/GNOME hybrid, here I only have a 3 GB hard drive (yep, the original from 11 years ago), so I've kept it Debian and minimal to save space.

I noticed that I didn't have an image editor. My go-to app gThumb was going to bring in a boatload of dependencies, so I opted for MtPaint instead.

Did I mention how great Opera is on these ancient computers? I just got an e-mail from the company that version 10.50 is out. I'll give it a run on my Toshiba before I upgrade here from 10.10. Opera isn't open source, but it's the best graphical browser I've ever found for old hardware that usually chokes the life out of Firefox. Or is it the other way around?

Ubuntu Karmic fail report: Xorg update breaks screensaver on Intel 830m video

| | Comments (1) |

I don't know whether or not this is just me that Ubuntu and/or Xorg is trying to kill, but my latest Intel-graphics honeymoon is most definitely over.

Yesterday I used Aptitude to pull in the latest Ubuntu Karmic updates for the Toshiba Satellite 1100-S101 (with the Intel 82830 CGC, aka 830M). If you'll recall, the last series of updates I installed for Karmic allowed me to use kernel mode setting for the X server, and I was once again able to run Ubuntu (with no xorg.conf, by the way) and have the onboard Intel graphics run as well as they ever have.

But after yesterday's bag full of updates, which were mostly Xorg-related, everything worked OK until the screensaver blanked the screen, after which the screen could not be restored either with the keyboard or mouse.

I haven't yet bothered to return ctrl-alt-backspace functionality to kill the X server in Ubuntu, so I don't know whether or not that would bring X back.

As it stands now, if the screensaver is invoked, I need to do a hard reset with the power button to bring the machine back.

The closest bug I could find is this one specific to the Ubuntu Netbook Remix, Bug #491302 in Launchpad. I do have a Launchpad account, and I did add a comment to the bug. Right now I'm not running the Ubuntu laptop, so I can't attach dmesg, lspci, etc.

Before setting up the Ubuntu Toshiba laptop, I pulled out the 1999-era Compaq Armada 7770dmt (Pentium II MMX 233 MHz, 144 MB RAM) and updated its Debian Lenny system ("customized" with a minimal Xfce desktop), writing this entry via the just-updated Opera 10 browser.

My next course of action with Ubuntu Karmic will be to try the xorg.conf I used in Ubuntu 9.04 (Jaunty). Hopes remain low.

Debian Lenny on the $15 Laptop and its big 233 MHz and 144 MB of raw power

| | Comments (0) |

I broke out the Compaq Armada 7770dmt, a 1999-era laptop with a 233 MHz Pentium II MMX processor and 144 MB of RAM.

This unusual laptop (the power brick is inside the case, it has that little "eraser-like" pointer — which still works — on the keyboard, which is very nice as far as laptop keyboards go) has run more than a few OSes since I've owned it.

I had OpenBSD 4.2 on it for a long time and recently wiped the drive and installed Debian Lenny.

Lenny is running as well or better than Etch did on the Compaq. I have a very minimal Xfce setup — no office suite, the Geany editor in the GUI and two Web browsers: Iceweasel/Firefox for when I absolutely need it and Opera 10.01 for when I want to browse on this 10-year-old laptop with only a little frustration.

I can't recommend a 10-year-old computer for intensive work on today's Web, but you can still squeeze a bit out of it.

Tips on running netbooks with Ubuntu Netbook Remix from Ladislav Bodner ... plus a look at flash-memory life span

| | Comments (3) |

ubuntu-eee.jpg

Distrowatch guru Ladislav Bodner has been rolling more than a few operating systems onto his ASUS Eee PC 900 netbook — probably the most popular netbook out there at this point (they even sell them at Target now).

In this week's Distrowatch (which I recommend as a must-read for anybody who wants to follow what's happening in Linux and the BSDs), Ladislav writes about how a mouse-over problem that tends to freeze the screen in Ubuntu Netbook Remix on the ASUS Eee was solved in the Linux kernel but almost immediately returned due to the relevant patch being pulled from the kernel because it began causing other problems.

Ladislav goes over how you can go backward from Linux kernel 2.6.28-11.41 to 2.6.28-11.40 and get your ASUS working again under Ubuntu Netbook Remix.

He also provides a tip for those using SSD (solid-state drive) disks on how not to wear them out:

Finally, a quick reminder for those who are about to install Ubuntu Netbook Remix (or any other Linux distribution) on a netbook with solid state drives. Since these drives have a limited life span that depends on the frequency of write access to the drives, you can greatly prolong their life span if you follow these two rules while installing your preferred distribution (here is the source of this information, although there are those who dispute this):

* choose a non-journalling file system (e.g. ext2)

* don't create a swap partition

As Ladislav says, there is some dispute about the life of flash media in everything from those mini USB drives and SD camera memory cards to devices designed to replace traditional IDE and (mostly these days) SATA .

samsung_flash_drive.jpgSome people have said that the MTBF (mean time between failures) for SSDs is so low when compared to spinning hard drives that the devices will last much longer than traditional spinning hard drives due to the lack of moving parts in an SSD. They say that worry about killing the flash memory with repeated write cycles is overblown.

But others are worried about killing their flash memory too quickly and take precautions such as the recommendation above not to have swap space on the drive.

For those who might not know, most operating systems do use swap space on the hard drive in the event that your computer's RAM (memory) fills up. I won't go into just how much space you need for swap because that's a whole new topic that's been discussed countless times in countless places. (I generally set aside 300 MB for swap on my systems).

Even Windows uses swap (that's one of the reasons your box tends to slow down after it's been running all day [or week/month/year]) — you've got a lot of critical stuff that the OS has written to the swap area of the drive.

Back to flash/SSD memory: As I say, some people think that worrying about excessive writes to flash is unwarranted. While I'm tempted to say that you shouldn't use an SSD on a server, Sun Microsystems (yep, the company bought recently by Oracle) is offering SSD-equipped servers and storage arrays. Sun thinks SSDs are the (near) future in servers since performance gains are too large to be ignored.

Sun is using single-level cell (SLC) flash memory, which has a much longer life than the cheaper multilevel cell (MLC) devices that pack more memory into the same space but have shorter write/erase lives.

We're a bit far away from the ASUS Eee PC and Ubuntu at this point in the post, aren't we?

Maybe. But here's what I want to say about flash-based storage: I'm all for it. I'd like to start moving everything I have to SSDs as soon as fiscally possible.

One thing I really like is a silent PC: no fans, and no spinning hard drives. If you've ever worked on a system with drives snaking out of the back of the case and sitting on a table (I did it for years), you know how much noise traditional hard drives make and how much heat they throw off.

For the energy and noise considerations alone, I'd like to dump spinning hard drives.

To that end, I'm doing one test and hope to do another soon. I've been running my Self-Reliant Thin Client (converted Maxspeed Maxterm) with an 8 GB CF card in the box's built-in CF-to-IDE adapter as the unit's main drive. I am still running Debian Etch on it (and will continue with it until I manage to get networking into the room). The box isn't in heavy use at present, but it is running (and has been this time for more than a week). I do have swap set up on the flash, and with only 256 MB of RAM, it'll probably get used a bit.

I'm running regular backups of the /home files to a 1 GB USB flash drive with rsync, so I have an all-flash system.

It's not fast. A low-end CF card (mine is a Transcend) doesn't have the performance of a top-of-the-line SSD. For one thing, the Transcend uses MLC instead of SLC and for that reason alone should have a shorter life.

I'll keep the box running for quite some time to monitor its progress with the flash memory and see if it can withstand repeated use. An upgrade from Etch to Lenny would definitely tax the CF card.

Another thing I'd like to try is an SSD in one of my laptops — maybe the $15 Laptop (Compaq Armada 7770dmt), which I've recently put back into service. At least the drive is easy to get to.

No distro-hopping for me these days

| | Comments (2) |

I've been writing updates in my print column of the things I've bought/used/discarded/loved/hated over the past year, and that got me thinking: I got started with Linux in early 2007 and used many a distro on the machines available to me.

But for the last six months, I've pretty much stuck with the same OSes on the same machines. There are two reasons for this:

1) I've found stuff that works

2) see 1)

OK, that's one reason, but it sure feels better as two.

Anyhow, the other reason I've kept the same operating systems on my half-dozen or so active computers is that I need them to run — and run well. And they do.

Here's the rundown:

On my main laptop, the Toshiba Satellite 1100-S101, I've been running OpenBSD 4.4 for nearly six months. The only "sticking" point is not having Flash 9 or 10. Flash 7 works for YouTube but not much else. I have a few things that I do that need more up-to-date Flash, but otherwise the OS and applications in packages and ports have been extremely stable. I just upgraded it from Firefox 2 to 3, and tonight I added Mplayer and successfully played a Quicktime video. (Too bad the sound chip on the Toshiba is broken; the video itself looked great.)

If OpenBSD weren't so good, I'd use the Flash situation as a excuse to run back to Linux. But I've enjoyed using OpenBSD and learned so much over these months that for now I'm going to stick with it.

I have an identical Toshiba Satellite laptop running Ubuntu 8.04 LTS. It, too, is performing very well, although I seldom use it since I have all of my data on the OpenBSD laptop. I have few complaints about Ubuntu 8.04, and before it came out I vowed to stick with the LTS for at least a year, maybe longer. I could be persuaded to upgrade if I needed to get a newer wireless adapter to work, but so far I haven't needed to do that. Ubuntu remains very solid, and with better Flash support than OpenBSD it's nice to have it as a backup.

Our daughter has what used to be known as the $0 Laptop, a Gateway Solo 1450. The Gateway could never comfortably run OpenBSD because of its noisy CPU fan, which Linux can manage most of the time (with a simple shell script). FreeBSD managed the fan even better, but only during the first boot after the install. After that, it all went to hell.

Our girl has all her educational games on the Gateway, which is also running Ubuntu 8.04. I still think that the Debian Project packages Gcompris, Childsplay and TuxPaint just that much better than Ubuntu, but all the problems I had with Debian Lenny and X on both the Gateway and later the Toshiba had me running back to Ubuntu and OpenBSD — both of which run X perfectly on both laptops with no xorg.conf file needed.

I'll concede that installing, customizing and maintaining just about any Linux distro is easier than doing the same in OpenBSD, but as I say above, I'm grateful for the learning experience and most of the time can figure out how to do what needs to be done in OpenBSD.

My Self-Reliant Thin Client, the first test machine that I began running Ubuntu, Slackware, Debian, ZenWalk, Puppy, DSL and other distros on in 2007 has been running Debian Etch on a bootable 8 GB CF card for quite a few months now. I don't have it networked at the moment, so I can't upgrade to Lenny. I'm keeping the converted thin client powered on these days in another informal long-term test, and I hope to have networking hooked up to it soon. With 128 MB of RAM and less-than-great video and sound hardware, it's not the greatest machine, but I love having something with no moving parts and minimal power consumption.

I have the Mac G4/466, aka the Debian Mac, running Debian Etch, which I continue to think is the best non-OS X operating system for this particular hunk of hardware. I managed to get 640 MB of RAM into it, and it's a great machine. Since it's a PowerPC box, there's no Flash Player in any OS that isn't OS X. I'm considering an OS X 10.4 install to see how that runs. We have dual-500 MHz G4s in the office that run OS X really, really well. I wonder how this single-CPU 466 MHz box will measure up. We could use a Mac OS backup machine in the house.

Earlier this week, I pulled out the $15 Laptop, a 1999-era Compaq Armada 7770dmt with 233 MHz CPU and 144 MB RAM and fixed what was ailing it: It wouldn't run X in OpenBSD 4.2 in my user account, but would in root. That's because when it comes to screwing around with X, I don't know what I'm doing some of the time. I had created an .xinitrc file with a single line reading "xset b off" to silence the system bell in X, and that was enough to keep the Fvwm window manager from loading. I killed .xinitrc and all was well with the Compaq. I'll probably do a reinstall of OpenBSD, since upgrading from 4.2 to 4.3 to 4.4 to ... is just too much work. Yep, after a long search for the right OS, the Compaq has run OpenBSD for a long, long time.

The real workhorse of our stable is the iBook G4 1 GHz laptop. In the past year I've replaced the hard drive, pumped 1 GB of memory into it and upgraded from OS X 10.3 to 10.4. We needed 10.4 in order to run Firefox 3 and Flash 10. Yep, that's when I upgrade — only when absolutely necessary.

To make a long story short, until I have a burning desire to watch Web video all the time, or until I need to edit and process video into Flash, I just might stick with OpenBSD on my i386 hardware. Otherwise I'll probably move back to Ubuntu or Debian, the latter only if those nagging video problems somehow go away. (I've had similar issues with Slackware ...).

My next "challenge" will be to run OpenBSD -current instead of -release. Since I already hate waiting for things to compile, I don't know how I'll react to keeping a -current installation up to date. There's only one way to find out.

Dark side of the laptop

| | Comments (2) |

disassembled_powerbook.jpg

(Image above from http://mike.kruckenberg.com)


We've pretty much reached the point at which it's probably cheaper to buy a laptop computer than it is to purchase a comparable desktop PC with the keyboard, mouse and monitor needed to make it all work.

Of course if you have all of those things — especially the monitor — you will still save money by buying just the desktop box and keeping as many of your old peripherals as will work.

But it seems like the graphs of "laptop cost" and "desktop cost" have finally intersected.

Laptops are convenient. You can carry them almost anywhere, use them almost anywhere ... you always have a keyboard, mouse (in the form of a touchpad) and monitor attached ...

Can you see where I'm headed?

Laptops break. And they're hard to fix. Often really hard.

And instructions on how to fix them are either really detailed (like those for Macs from ifixit.com) or, shall we say, "nonexistent."

I couldn't have replaced our 2003 Macintosh iBook G4's hard drive without the lengthy instructions from ifixit.com, and even with them, the procedure took three hours and had me cursing more than twice.

I thought that PC-based laptops put their hard drives in "civilized" places. On both my 1999 Compaq Armada 7770dmt and 2002 Gateway Solo 1450, I could swap out a hard drive by removing five screws, switching the drive and reversing the procedure. Five minutes from start to finish.

Now that I'm using this 2002 Toshiba 1100-S101 — hell, I've got TWO IDENTICAL MODELS — I find out little about how to replace their hard drives other than that "it's not easy."

There's no easily-accessible bay like in the Compaq and Gateway. The one forum post I found said that just about everything needs to be torn apart to get at the hard drive.

And now that the Toshiba on which I'm running OpenBSD seems to be slowly dying, the prospect of getting the drive out and trying it in the other Toshiba is looking to be way harder than I'd like it to be.

Clearly I should've spent more time with the other Toshiba before I decided which one I'd be using.

Here are the major parts of each laptop and their problems:

Case:

Toshiba 1 looked better from the outside
Toshiba 2 had a prominent crack that was somehow repaired

Keyboard:

Toshiba 1 has fairly worn keys. The space bar is a bit unresponsive toward the ends
Toshiba 2 seems fine

Touchpad:

Toshiba 1's has a tendency to stop working at all for short periods of time. After a certain length of time it also starts to become very erratic (a USB mouse always works fine).
Toshiba 2's touchpad seems fine, but I haven't used it enough to know for sure.

CD/DVD drive:

Both Toshiba 1 and 2 have very picky optical drives when it comes to reading CD-R discs. Each will only read/boot a few of my many CD-Rs. And each boots different ones.

Screen:

Toshiba 1 came to me with a sticker on it that said "bad screen." But since it seemed to work, I just went forward with my floppy/network install of OpenBSD 4.4. Today, though, the screen began blanking out intermittently. Squeezing the bottom plastic portion of the screen will often (but not always) fix it.
Toshiba 2's screen seems fine.

Sound:

Toshiba 1's sound is intermittent in both Windows and OpenBSD.
Toshiba 2's sound seems fine.

Hard drive:
Toshiba 1's hard drive runs fine.
Toshiba 2's drive seems a bit noisy

Floppy drive:
Both seem fine.

Battery:
I've learned to expect nothing from old laptop batteries. I haven't even tried using them.

CMOS battery:
Toshiba 1 powered up with the correct time and date. No problems since.
Toshiba 2 powered up with a 1999 time and date. I suspect that the CMOS battery is dead.

Ever try replacing a CMOS battery in a laptop? Some are easy to replace but super-expensive to buy (my Compaq), others are commonly found and inexpensive but seem impossible to extract (my Gateway).


The bottom line is that laptops are extremely convenient. But they are still quite expensive, and for the most part disposable. In the past few months, I've heard about plenty of bricked laptops — Macintosh and PC.

At my office, I have a Dell Optiplex GX520 that's now probably three or four years old. Actually, we've got quite a few dozen of them. I beat the hell out of the thing, and it just keeps working. I've spilled plenty of things into the keyboard. It still works.

Since it's a Dell and not a generic box assembled from off-the-shelf parts, it wouldn't be as easy to fix as something I put together from TigerDirect or Newegg-purchased components, but if the hard drive, optical drive, mouse, keyboard or monitor died, I'd have it fixed in a few minutes.

I'm as guilty as anybody of spending a lot of time (but in my case almost no money; all these dead and dying machines have been free or nearly so) using laptops. I don't have a "home office" that I actually work in (it's a sordid tale that I won't even begin to relate), so when I do work at home, it's pretty much on a laptop.

When, after suffering for over a year with the Gateway Solo 1450's not-to-be-tamed-by-any-BSD CPU fan, I found in the Toshiba 1100 a laptop with no CPU fan problem in OpenBSD.

Never mind that its optical drive, touchpad, keyboard, sound and display are not exactly ship-shape.

But I can run OpenBSD in peace. And for the past hour, the screen hasn't gone blank. The touchpad has even continued to work.

While the first Toshiba booted Debian Etch and a Half's netinstall CD (and nothing else, leaving me to install OpenBSD from a floppy — and damned glad that's an option), the second Toshiba booted Debian Lenny's business-card CD and Knoppix.

And I'm wondering how useful Windows XP is to me on either of these laptops. Even if I do manage to figure out the admin password and can bring them from Service Pack 1 to whatever it is XP is up to now. (Is it the SP3 that my Dell desktop for some reason refuses to install?)

If I get the time (and if Toshiba No. 1's screen doesn't continue to cooperate), I'll probably be running Debian Lenny from Toshiba No. 2 before the end of this week.

I did pull the memory door on one of the Toshiba's, and I was pleased to learn that the 256 MB is on a single SODIMM, meaning I could pull the module from one and have 512 MB in the other.

I'd probably be better off loading up the other Dell desktop I have waiting in the proverbial wings. It's not a server, but it uses this expensive PC800 Rambus ECC server memory. (What was Dell thinking, other than "mmmm ... expensive memory"?) Maybe it'll do OK with the 256 MB loaded in there now. And there's always my Power Mac G4/466, which runs Debian Etch fairly well in 384 MB of RAM (but without Flash video, since there's no Flash in the world of non-Mac-OS PowerPC). ...

I'll give Toshiba 1's hinky screen another week. Because I'm weak.

Now that I dumped Debian Lenny from this laptop, Ubuntu has got to go, too

| | Comments (4) |

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.

My next project: Goodbye Debian, hello ... Fedora or OpenSUSE?

| | Comments (3) |

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.


What I'm running right now

| | Comments (3) |

As of today, here are all the machines I use and what they run:

At the office:

Work box:
Dell Optiplex GX520
Pentium 4 (3 GHz)
512 MB RAM
Windows XP SP2

The Debian Mac:
Power Macintosh G4
466MHz single PowerPC processor
384 MB RAM
Debian Etch

The Self-Reliant Thin Client:
Maxspeed Maxterm 5300(??) thin client
VIA C3 Samuel (1 GHz, running at 500 MHz for some reason)
256 MB RAM
8 GB Transcend Compact Flash module as boot drive
1 GB USB flash drive for backup
Debian Etch

At home:

iBook G4
1 GHz CPU
384 MB RAM
120 GB Fujitsu hard drive (replaced by me in a 3-hour odyssey)
OS X 10.3

This Old PC:
Pentium II MMX (333 MHz)
256 MB RAM
10 GB hard drive
Windows 2000 (I haven't booted this or connected it to the Internet in over a year)

The $0 Laptop:
Gateway Solo 1450
Mobile Celeron (1.3 GHz)
1 GB RAM
30 GB Toshiba hard drive
Ubuntu 8.04 LTS, Debian Lenny, Puppy 3.01

The $15 Laptop:
Compaq Armada 7770dmt
Pentium II MMX (233 MHz)
144 MB RAM
3 GB IBM hard drive
OpenBSD 4.2

I have quite a few machines in various states of repair that I might resurrect over the next year if and when I get the time, but this is what I have right now. With the exception of the white-box This Old PC, all of these get fairly regular use.

I think I've fixed my Ubuntu 8.04 screen/keyboard/mouse-freeze issue ... but should I upgrade to 8.10?

| | Comments (0) |

Every time I write about Ubuntu 8.04 LTS, which I've been running on my Gateway Solo 1450 laptop since its release in April, I mention that it's the only GNU/Linux distribution I've used that successfully suspends and resume the computer.

And I've made that feature — suspend and resume — the bar over which other distros must jump to "beat" 8.04 on this platform.

Make no mistake, I've "enjoyed" a working suspend/resume capability. But I haven't enjoyed returning to the laptop after a while to find the screen looking normal but the keyboard and mouse completely dead. CTRL-ALT-backspace won't kill X. CTRL-ALT-delete won't reboot the machine. I need to do a hard boot with the power button to get things working again.

I've had X issues in many distros, most severely with Debian Lenny, my preferred distro for this PC, which has serious problems with refreshing the screen, leaving the upper panel in GNOME and many graphical elements of various applications virtually unrecognizable after about a half-hour of use.

I appeared to have a similar X issue in Slackware 12, which I installed only briefly (and too briefly to make a determination, especially since I never got a "perfect" X configuration), but other systems, including CentOS 5, Fedora 9, and Puppy 3.00 had none of these issues.

Nor did Ubuntu 8.04, which automatically wrote an xorg.conf that was much different — being way more spares — than any other I'd seen before. But X performs flawlessly.

Even though suspend/resume works in Ubuntu, I'm now about 80 percent sure my intermittent keyboard/mouse freezesare caused by whatever daemon is responsible for automatically checking whether or not to suspend the system.

I pretty much arrived at this point through the process of elimination with the addition of a little bit of logic. Since no other distro appeared to be freezing like this, and since I only have automatic suspend/resume set on Ubuntu, that seemed to be the most likely cause.

So I went into the GNOME Power Manager utility and turned off the "put the computer to sleep after XX minutes" feature.

Since then, I've had no freezing whatsoever in Ubuntu 8.04. A month from now, I'll be sure.

Unfortunately, I haven't been able to figure out the problem with screen refresh in Debian Lenny. I'm considering wiping it from the laptop and trying another secondary distro, maybe CentOS or Fedora. Even Sidux — a more "tame" version Debian Sid — is something to try just to see if I continue to have the screen issues.

Or I could just stick with Ubuntu 8.04. I'm not thinking about upgrading to 8.10, which not coincidentally is available for download today.

Click that last link to see the major new features in Ubuntu 8.10. I'm very unlikely to need 3G wireless, but if I find that 8.10 supports my Airlink 101 AWLL 3028 USB wireless adapter, I would strongly consider doing the upgrade.

I'm sure all of the Ubuntu mirrors are straining mightily with everybody trying to download the whole 8.10 image or upgrading their current installations. I'll be waiting at least a couple of weeks before I try to download the ISO and burn a live CD. If that loads and then the wireless works out of the box (I won't be holding my breath), I'll go forward.

Otherwise, I'll stick with 8.04 LTS — the long-term-support edition of Ubuntu that will be supported until 2011 on the desktop.

But with suspend/resume off the table, Ubuntu has lost its edge over every other GNU/Linux distribution (and even FreeBSD/PC-BSD) on this laptop.

I've been sticking with my installs much longer than usual — I'm still using a now-year-old installation of OpenBSD 4.2 on my $15 Laptop (and OpenBSD 4.4 will be released on Nov. 1).

See tomorrow's post for a breakdown on what I'm running on every machine.

Tech Talk column

Steven Rosenberg's weekly Tech Talk column, which appeared Saturdays in the Los Angeles Daily News through about October 2009, is available on the Daily News Technology page.

About this blog






Steven Rosenberg aims to learn what he does not know. He writes about it here.



About this Archive

This page is a archive of recent entries in the The $15 Laptop category.

The $0 Laptop is the previous category.

The Self-Reliant Thin Client is the next category.

Find recent content on the main index or look in the archives to find all content.

Recent Comments

Steven Rosenberg on Running OpenBSD in a live environment with MarBSD-X : Jggimi has images for OpenBSD 5.0: http://jggimi.homeip.net/ ...

Monstra on CMS and blog software without databases: Monstra CMS is the best flatfile CMS ever! (!) Easy to install, upgr ...

Chris on Running OpenBSD in a live environment with MarBSD-X : Jggimi isn't developing his images anymore. If you want an updated Ope ...

Peter Ljung on Review: DragonFlyBSD 3.0.1 -- the longest DragonFlyBSD review ever -- Part 5: Comparison to OpenBSD 5.0 and closing comments: I have also been fascinated by the Hammer file system and think it wou ...

Anonymous on Review: DragonFlyBSD 3.0.1 -- the longest DragonFlyBSD review ever -- Part 2: My BSDistory: Can you just get to the actual review? ...

Bill Callahan on SugarSync is working on a Linux client, but I'm not unhappy at all with Dropbox: I've been very happy with SpiderOak. It has a native Linux client as w ...

AJ on Debian Stable -- set it and forget it -- spoils me for fresh Linux Mint 12 on some very nice ZaReason hardware: Gnome 2 is still standard in the upcoming SolusOS (Currently at RC 2). ...

Niki Kovacs on Debian Stable -- set it and forget it -- spoils me for fresh Linux Mint 12 on some very nice ZaReason hardware: Since I've moved to Debian stable - with a few tweaks - I've not only ...

Earl on Debian Stable -- set it and forget it -- spoils me for fresh Linux Mint 12 on some very nice ZaReason hardware: I use Mint 12 and LMDE based on Debian testing. Both are plagued by G ...

Alan Rochester on Debian Stable -- set it and forget it -- spoils me for fresh Linux Mint 12 on some very nice ZaReason hardware: "mint does have a separate xfce edition afaik.." The Debian version o ...

Powered by Movable Type 4.25

Search this blog

Loading

LXer

Links

Life, the Universe and Debian
Simplify
Daily News technology
LXer
Distrowatch
Linus' Blog
David Pogue
BoingBoing
Linux Today
TuxRadar
Linux.com
Linux Planet
The Open Road
Linux Outlaws podcast
Dan Lynch
Fabian Scherschel
The VAR Guy
Larry the Free Software Guy
Chess Griffin
Linux Reality podcast
Desktop Linux
Practical Technology
Linux Devices
ZDNet
ZDNet's Storage Bits
ZDNet U.K.
iTWire
CNet News
Webware
Beyond Binary
TechCrunch
The Register
Ars Technica
Reg Developer
Computerworld
Computerworld blogs
Steven J. Vaughan-Nichols at Computerworld
Debian
Planet Debian
Debian Forums
Debian News
debianHELP
debiantutorials.org
The Debian User
Wolfgang Lonien
Debian-News.net
Debian Administration
Debian Admin
Debian Weather
Aaron Toponce
Ubuntu
Xubuntu
Kubuntu
Edubuntu
Planet Ubuntu
Ubuntu Forums
Ubuntu Geek
Works With U
OMG! Ubuntu!
I' Been to Ubuntu
Tanner Helland
Dustin Kirkland
Ubuntu UK Podcast
Ubuntu Linux Help
Popey
Linux Mint
CrunchBang Linux
OpenBSD
OpenBSD Journal
OpenBSD Ports
OpenBSD 101
Planet.OpenBSD.nu
jggimi's OpenBSD live CD
DaemonForums
BSDanywhere
Marc Balmer
Denny's OpenBSD blog
Polarwave's OpenBSD Tips and Tricks
Binary Updates for OpenBSD
Puppy Linux
Damn Small Linux
Tiny Core Linux
Lucky 13's Linux blog (lots of Tiny Core)
Lucky 13's BSD blog
PCLinuxOS
Mandriva
Red Hat
Red Hat News
Red Hat Blogs
Red Hat: Truth Happens
Red Hat Magazine
CentOS
Planet CentOS
Fedora
Planet Fedora
Fedora Forums
Fedora Docs
Join Fedora
Paul Frields
Slackware
Slackbuilds
Robby's Slackware Packages
Slackblogs
dropline GNOME for Slackware
GNOME Slackbuild
GWARE - GNOME for Slackware
Wolvix
Zenwalk Linux
Vector Linux
Slax
Splack Linux — Slackware for Sparc
Nonux
How to Forge
marc.info BSD and Linux mailing list archive
FreeBSD
FreeBSD, the Unknown Giant
A Year in the Life of a BSD Guru
NetBSD
hubertf's NetBSD Blog
PC-BSD
Daemon Forums
FreeBSD Forums
Planet FreeBSD
Evilcoder.org
miwi's Privat Blog
DragonFlyBSD
DragonFlyBSD Digest
DesktopBSD
BSD Talk podcast
BSD Magazine
Rhyous
OpenSolaris
MilaX
BeleniX
DeLi Linux
Linux Loop
Electronista
The Tech Report
Engadget
Gizmodo
Phoronix
xkcd – A webcomic of romance, sarcasm, math and language
Nixie Pixel
Technology for Mortals
Thoughts on Technology
ZaReason
System 76
Tiger Direct
NewEgg
DealExtreme

Advertisement