Fedora Core is a bipolar Linux distribution. There, I’ve said it. I know there are legions of Fedora devotees out there, but they have probably had no such headaches installing the damn distro as I have had in the past week or so.
For all my troubles, it was easier to get FreeBSD up and running (a mere two attempts instead of the several dozen with Fedora) and get a full graphical desktop running. To their credit, the Fedora Project is trying to create a “fully functional” graphical desktop environment right out of the box, which is a bit more of a challenge than FreeBSD’s standard install which drops the user straight into a command-line shell. Thankfully, I am not that much of a computer cripple, and so I was able to find my way into the full GNOME desktop environment in a matter of minutes.
Even so, there are many things left undone in FreeBSD’s standard installation (which are supposed to work almost immediately with a Fedora Linux installation), and which I will end up having to go back and configure myself later. For what its worth, I am at least getting a far more hands-on introduction to a real UNIX than what I would have gotten if Fedora Core worked as advertised. Whether or not that is a good thing only time will tell. In the mean time, I am merely happy to be experiencing a new OS.
Further Fedora Failures
I had tried to install Fedora Core 3 on several PCs of very different hardware makes last week. In each case I was unable to complete the Fedora Core 3 installer and get a working version of Fedora Linux onto the computers. Despite spending the better part of this week researching the topic and attempting to find solutions to the problems, I simply could not get it to work.
Fedora Core 3 Installation Problems
I was constantly confronted, in some point during either the graphical or text-based installation of Fedora with the console message Install exited abnormally followed by lines that read Sending termination signals…done., unmounting filesystems, and finally stating that You may safely reboot your system.
Whether or not it was, indeed, safe to reboot the system is up for debate. In some cases my previous OS had already been rendered unbootable by the installer having written a new partition table to the hard drive before “exitting abnormally.” This is why I had rescue CDs before attempting a Linux migration (and is why you need to have them, too)!
In all the mailing list archives and installation guides I could find, several common motifs echoed in the various “Help me” posts I perused:
-
Using certain kinds of mice, most notably any form of LogiTech® or serial mice can cause crashes of the graphical installer and should not be probed for automatically, or—in the worst cases—should not be used during installation, period. This is not really a problem because the installer provides ample keyboard navigation support, but is a rather annoying bug anyway.
Workarounds that I have tried included:
- Using a generic mouse instead of any major brand mouse. Specifically, I used an InterAct PS/2 (6-pin mini-DIN) mouse instead of a LogiTech, IntelliMouse, or serial mouse.
- Unplugging the mouse for the duration of the automatic hardware probing and then manually configuring the installer to use a generic 3-button mouse.
- Unplugging the mouse for the duration of the installer. Or for the durations that worked, anyway.
- Using the text-based installer (which does not use a mouse at all) instead of the graphical one.
Unfortunately, none of this had any effect other than to drive me crazy when trying to combine these various workarounds with the following workarounds.
-
Hardware probing itself is sometimes, allegedely, to blame for the failed installs. Disabling the hardware probe, or certain parts of it, by passing special options to the Linux kernel at boot time sometimes fixes the problem. Additionally, sometimes certain options regarding the power management features of the hardware and the kernel cause problems, and they should also be disabled during the installation boot-up process via special kernel arguments. The list of special boot options I tried were:
linux noprobe
linux noacpi
linux nofb
linux mem=mem_amount (with the appropriate amount of memory available on whatever system I was trying to install onto in place of mem_amount)
- Various others I can’t remember right now.
- Various combinations of the above options in conjunction with other attempts.
In my case, the automatic hardware probe always managed to correctly guess my video card and monitor type (Intel 810 and ViewSonic EF70, respectively), so I was left to believe that the mouse was the only likely hardware issue. Nevertheless, I did notice that when the X server was starting up, parts of the usually gray screen were corrupted (think horizontal or vertical “snow” on an old TV set) and later, scrolling text and pop-up windows would not display correctly.
Sooner or later, usually sooner and almost always during the Searching for Fedora Core installations… progress dialogue, the X server would exit abnormally (or crash) and I would be told that it was safe to reboot my system. To which I scoffed and went to eat more cake.
I suspect that I may be lacking some kind of knowledge about either
- how the Linux kernel works or how OS kernels in general work, or
- how physical media such as hard disk drives interact with their software counterparts and how they store information (partitions, blocks, clusters, sectors, heads, cylinders, etcetera…)
that I need to understand in order to solve this problem. Unfortunately, despite all that I am reading on that topic these days I just could not get Fedora Core 3 to install successfully.
The really frustrating part in all of this is that there are no explicit error messages that come up to help me diagnose the issue. Even with the most braindead implementation issues on Windows, an error message, cryptic as it usually is, never fails to pop up and let the user know something is wrong. (Of course, the sheer frequency with which that happens is actually a prime motivator to my fondness for Unix-like systems.)
In this case, Fedora Core’s installer never warns me of a problem until its too late. In two cases, during a graphical installation on a machine that had already logged a failed installation attempt an error window did show itself and read something like BUG! Assertion (heads > 0) failed! which I understood to mean that something was either royally screwed with my partition table, BIOS drive geometry, or physical hard disk drive, and thus induced my search for the bugfix at LWN.net. Some common sense tells me it is more likely to be a problem with the partition table than anything else because both Windows and Knoppix work without any problems at all.
Fedora Core 2 Installation Succeses and Woes
It was suggested to me, when I finally gave up and sent a rare and detailed “help me” request to a very nice (and far more skilled) acquaintence of mine, that I should try to install Fedora Core 2 instead of Fedora Core 3 because it was likely to be far more stable.
The good news is that I have actually managed to get FC2 working on one (1!) machine of mine. Surprisingly, the docile computer is the extremely old PeoplePC-branded box with extremely low resources. (PeoplePC was a prevalent ISP in the mid-1990’s who were, I believe, the first to offer cheap computers as a bonus to new subscribers.)
Unfortunately, this machine runs painfully slowly (especially with a huge application like GNOME) and so even opening windows is an exercise in patience. Doing anything actually productive is simply unrealistic, as it took nearly 2 hours to get the latest updates in up2date from the Red Hat Network, and I actually cancelled the update in the middle of that process. So I had been hoping that Fedora Core 2 would install nicely on the other machines I have.
Of course, that’s when the bad news hit. The bad news is that bugs are in FC2 as well and the same thing happened with it as what happened with FC3 on one of the machines I tried to install it on. I was greeted with that very familiar Install exited abnormally message and was told to reboot my system. I spent a few minutes trying a few of the workarounds I talked about above on this version of Fedora on this machine, but gave up after about half an hour.
Interestingly, on the other machine which didn’t take the install the problem was entirely different. Rather than even getting to the graphical installer, when I pressed Enter at the boot:-prompt I was inexplicably dropped into the text-based installer instead. There was not the slightest indication that the computer was even trying to load the graphical installer. Wierd! This didn’t happen with Fedora Core 3 at all.
Optimistic as I was, I thought it still might work; perhaps it was just the graphical installer that wouldn’t function. But alas, this was not to be. When I was asked where the installation media is to be found and responded with “Local CD-ROM,” the text-based installer reported being unable to locate Fedora Core on the CD-ROM, even though the install disk was right there in the CD drive and I had used that very disc to get FC2 working on the first, oldest machine I tried!
Thus, I have decided that Fedora is a bipolar Linux distribution which needs heavy doses of appropriate patience and medications. I am at a total loss to explain this except to say that I am not left with a great taste for Fedora or Red Hat in my mouth. Ew.
FreeBSD is Less Moody, but also Potentially Confusing
To make matters even more confusing, I had tried to install FreeBSD some days ago on the old machine which now holds the only working Fedora Core installation I have. When I tried to install FreeBSD on it the other day I was unable to proceed due to an error that read something like Unable to locate Hard Disk Drive or similar. I can’t remember the exact wording.
After giving up with Fedora tonight, I tried to install FreeBSD on the machine which forced me into the text-based installer for FC2. It has completed without a hitch, and it only took me a few moments to orient myself within the system (man hier was incredibly helpful) in order to find out how to start a GNOME session and get back to the still-comforting GUI desktop.
Final Fumbling Thoughts
It might be of interest that both machines on which Fedora Core 2 failed to install for one reason or the other are HP Pavillion machines of somewhat different makes. One has a Pentium III processor and the other a Celeron, for instance.
Since FreeBSD has worked on one of these Pavillion towers but not on the old PeoplePC-branded tower (where Fedora 2 did work) I am hoping that at the very least some other BSD will take to the other Pavillion. That way, I can get different operating systems on my various computers and finally get to start playing with the many options out there, like I have been wanting to do for months now.
While I hope this is certainly not the end, I am not at all opposed to the idea of giving up on Linux (or at least Red Hat) for the time being. Perhaps all I really need is to go build myself a new system with new and (hopefully) supported hardware. That really shouldn’t be such a big deal, and I need to upgrade that old PeoplePC box anyway. 200-something mhz is just not acceptable these days. (It wasn’t even in the mid 1990’s, but PeoplePC was cheap and we are not rich.)
I am already far more comfortable with FreeBSD than I was even in the graphical environment of Fedora Core 2’s default GNOME themes. Perhaps it is the shell. I spend a lot of time on Mac OS X within Terminal at a tcsh prompt (though I have playing with bash lately) and, after all, FreeBSD is one of Mac OS X’s parents.
Seems only fitting that I should feel more comfortable with the BSD’s than with a Linux. In the end, Linux Is Not UniX. ;)