On Fri, Nov 28, 2008 at 12:36 PM, R C Mitchell <[EMAIL PROTECTED]> wrote:
>
> I use Ubuntu for every day but as my box has a spare 40GB hard disk I decided
> to have a go at installing Gentoo on it for evaluation
>
> Using the handbook documentation for AMD64 I burned a basic installation CD,
> booted it up, and followed the instructions for installation on the spare
> drive.  Everything went fine; I partitioned the disk with a 32MB ext2 sector
> for /boot, a 512MB swap sector, 10GB for root and the rest for /home.  I had
> no trouble with the network, successfully downloaded everything that needed
> to be downloaded and unpacked it, successfully chrooted to the new system,
> and reached the compiling the kernel section without a glitch.
>
> And the then the trouble began.  I emerged gentoo-sources, and it ran fine for
> about five minutes, and then (choosing the moment when I decided all was well
> to go and make a pot of tea, the system rebooted itself.  I booted up the
> disk again and went through the chrooting process.  When I went to emerge
> gentoo-sources again, emerge looked for the dependencies and then the whole
> system froze solid with one of those "this is NOT our fault" kernel panic
> messages.
>
> Not to worry.  I can be very patient on occasions.  I cold booted the box and
> started all over again, deleting the new partitions and going through the
> instructions from the beginning incase I'd missed anything.  Again I got to
> emerging gentoo-sources.  Again it ran for about five minutes before the
> system rebooted itself.  Again I went through the chrooting process and went
> to emerge gentoo-sources.  Again the system froze.  I rebooted and rechrooted
> and tried it again.  Same result.
>
> I'm reluctant to believe that this is down to an arbitrary hardware fault,
> since everything else works fine.  It does seem to have something to do with
> emerging gentoo-sources.
>
> Is anybody able to rescue this maiden in distress and throw some light on my
> problem?
>
> Rosie

An easy way to find out if this is a gentoo related problem is to
avoid using the livecd.
You can easily chroot into the gentoo drive from your ubuntu
installation and try to emerge
gentoo-sources from there.

If you still get a failure you can be almost sure this is an hardware problem.

If you don't get any failure, than this does NOT mean gentoo is not
for your hardware,
but only that the livecd configured kernel may have issues with your hardware.

Of course be careful compiling your own :P

--
Momesso (TopperH) Andrea
http://topperh.blogspot.com
Jabber: [EMAIL PROTECTED]
ICQ: 224179391

Reply via email to