Fedora Core 2


Last night I downloaded the ISO DVD image for
Fedora Core 2,
which was really nice, since it meant I didn’t have to burn like 5 CDs or something.
It was nice to use BitTorrent to download the 4 Gig image all in one night (I have no bandwidth cap from 2am-10am).

I burned the image to DVD on my Mac, and then slapped the DVD into the Media Box (which I named “Media” during all installs) and did an install.

It was the first of three I did tonight.

The first install seemed to go swimmingly, but when it was all done and the machine rebooted, it hung after spitting out the text “GRUB”.
Now, “grub” is the default boot loader for Fedora Core 2, so I realized that I had a problem, possibly because i was trying to be fancy and include my already-existing old disk as an optional boot.

Now at this point I should mention that I have two hard disks in Media, each of which is 160 Gig.
One is Serial ATA (SATA, new-fangled, fast tech), while the other is old-school parallel ATA (PATA).
They are from the same manufacturer, and in fact their model numbers only differ by an “S” at the end for the SATA drive.
The model #, for the morbidly curious, is “ST3160023A” (and “ST3160023AS” for the SATA, obviously).

I’ve been having problems with the SATA drive because the 2.4 Linux kernel didn’t support my SATA chipset — “Silicon Image 3112” — which meant performance on my SATA drive was ultra-crappy.
I went and got the second drive because of this, in fact.
Now, when Fedora Core 2 was announced, it was not only going to have the new, fast, cool and in other ways spiffy 2.6 kernel, but it was also going to have the SiI3112 SATA driver built-in.
W00t!
So you can imagine that I was really looking forward to the upgrade.

I was surprised to learn that in fact, Fedora Core 2 was released back on May 18th!
Ah well, I guess I waited a few extra weeks.

Well, back to the install.
So when I couldn’t boot, I thought that maybe the problem was that the BIOS was set to boot off the PATA drive, and not the SATA drive.
Well, changing that BIOS setting could really confuse the boot setup for Fedora, so I thought a re-install was in order.
Especially since it was so easy to install!

Now, about some shortcomings in the installer…
When the installer starts up, it asks to test the disc media from which you are installing.
This is a good idea, and is also used in Apple’s recent installers.
So I let it check out my DVD and make sure all is good.
After about 10 minutes, it spits out my DVD and says “put in the next CD”.
Well, I would think that: (a) it should notice that I am using the DVD, and (b) most people will only have the one disc, and (c) it should only spit out the disc when you click on “Test another disc”!

Shortcoming number two has to do with package selection.
Following the advice of someone who wrote up their Fedora install (sorry, no link), I selected my packages manually rather than just saying “Everything”.
The defaults for the package groups were not all that great.
I would say that about half the groups needed no change, but the other half definitely were missing key components.
I had to manually add things like postfix, mailman, squirrelmail, mysql, and ruby.

Well, after the second install I got an error that ended with:


kernel /vmlinuz-2.6.5-1.358 ro root=LABEL=/ rhgb quiet

Error 15: File not found

Press any key to continue

Now, as it turned out, the key bit there was “root=LABEL=/”, because it was supposed to say something like “root=/some/path LABEL=/”.
Well, the long and short of it was that I had to manually edit my grub.conf file to have a fixed “root”, and also have the root defained as “root (hd0,0)” instead of using “hd1”.

Now that I had a successfully booting Fedora Core 2 system, I had to get MythTV installed.
The easiest way to do this is to follow
the instructions about using atrpms.
I did that, but got more errors concerning a conflict between qt and redhat-artwork, of all things.
So I have
posted
about it

to the atrpms-users mailing list.
I’ll let you know how it works out!

Published by

rae

Mac developer

3 thoughts on “Fedora Core 2”

  1. Well as it turns out, I just needed to do an “apt-get dist-upgrade”, which upgraded my version of qt among other things such that my later call to “apt-get install mythtv-suite” worked without a hitch.

    Now I just have to configure Myth and then… get the damned ethernet to the living room!

  2. We just got a new light installed in the kitchen. It’s hard to describe, but you can run wires through the ceiling by cutting 6″ holes centered on the beams and saving the cut-outs [it looks like a large doorknob hole cutter]. Then you chop small bits out of the beam just large enough to accomodate the wires (say, 1/4″). Replace the cutouts by using two 1.5″ screws, then sand, add drywall compound, tape and repeat (2nd day). Then prime & paint (3rd day, 4th day).

    I called a pro.

  3. I start install Fedora core 2 with SiI3112A but even i have added the driver when it asked me to select sata driver (sil_sata is my selection), but it keep asking to insert disk drivers into /dev/fd0. Could you teach me the installation process in details?

Leave a Reply

Your email address will not be published. Required fields are marked *

To create code blocks or other preformatted text, indent by four spaces:

    This will be displayed in a monospaced font. The first four 
    spaces will be stripped off, but all other whitespace
    will be preserved.
    
    Markdown is turned off in code blocks:
     [This is not a link](http://example.com)

To create not a block, but an inline code span, use backticks:

Here is some inline `code`.

For more help see http://daringfireball.net/projects/markdown/syntax

This site uses Akismet to reduce spam. Learn how your comment data is processed.