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”.
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).
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.
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:
Error 15: File not found Press any key to continue
kernel /vmlinuz-2.6.5-1.358 ro root=LABEL=/ rhgb quiet
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”.
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
to the atrpms-users mailing list.
I’ll let you know how it works out!