I similarly installed RH 6.1 on my Athlon system at home this weekend. I
experienced the same thing. What I found was that I had to create the /
partition before the 1024 cylinder. On new systems that is before the
first 8.4gb of disk space. Installing after that the Linux kernel can
not boot up. I ended up making my Windows partition about 6.5gb, and
then making a 2gb / partition. The remainder of the space I partitioned
as /home. It booted just fine after that. Note: if anyone is planning on
loading up their Athlon, you should upgrade to kernel 2.2.14. The
2.2.12-20 kernel distributed with RH 6.1 will work but you may notice
strange things like the klogd taking up 100% of the cpu. Also the 2.2.14
kernel adds support for the Via PCI chipset and UDMA66 support.
JDF
Matt Herbert wrote:
>
> Hey everybody,
>
> After an awesome quake 3 LAN party this weekend :), one of my friends
> decided he wanted to try linux on his system. I excitedly agreed to
> help him install Red Hat 6.1. To my surprise and disappointment, I
> couldn't get it installed to save my life. He has a new system with
> a 27 GIG IDE hard drive. When he set the system up, he formatted a
> ~24 GIG Windows partion, and left 3 GIG as unpartioned space. For
> some strange reason, the redhat installer simply wouldn't allow me to
> create a / partion on that space, it kept saying there wasn't enough
> room.
>
> What I was doing, was creating a 128 meg swap partion, which worked
> fine. Then I would create a 1 meg / partion and select the "Grow to
> fill disk" checkbox. That didn't work. So I typed in the the size
> of the partion based on the free space printed in the summary section.
> Nix on that too. So I tried creating a 100 meg / partion ... nope.
> Always the same error. I could create any other partion without a
> problem, e.g. I created a /home and set it to "Grow to fill disk"
> and it worked fine. I just couldn't create the slash partion.
>
> The only thing I can guess at, is that slash needs to be hda1
> (although I'd swear I've had slash as hda5 before) or possibly the
> slash partion needs to be near the beginning of the disk for some
> ancient bios reason.
>
> So does anybody know what the problem might be? and if there is a
> workaround?
>
> -Matt
>
> --
> Matthew W. Herbert x75764
> Spectrum Advanced Applications
> http://www.aprisma.com/
> mailto:[EMAIL PROTECTED]
>
> **********************************************************
> To unsubscribe from this list, send mail to
> [EMAIL PROTECTED] with the following text in the
> *body* (*not* the subject line) of the letter:
> unsubscribe gnhlug
> **********************************************************
**********************************************************
To unsubscribe from this list, send mail to
[EMAIL PROTECTED] with the following text in the
*body* (*not* the subject line) of the letter:
unsubscribe gnhlug
**********************************************************
