1 |
On Fri, Nov 28, 2008 at 12:36 PM, R C Mitchell <rcm@×××××××××××××.uk> wrote: |
2 |
> |
3 |
> I use Ubuntu for every day but as my box has a spare 40GB hard disk I decided |
4 |
> to have a go at installing Gentoo on it for evaluation |
5 |
> |
6 |
> Using the handbook documentation for AMD64 I burned a basic installation CD, |
7 |
> booted it up, and followed the instructions for installation on the spare |
8 |
> drive. Everything went fine; I partitioned the disk with a 32MB ext2 sector |
9 |
> for /boot, a 512MB swap sector, 10GB for root and the rest for /home. I had |
10 |
> no trouble with the network, successfully downloaded everything that needed |
11 |
> to be downloaded and unpacked it, successfully chrooted to the new system, |
12 |
> and reached the compiling the kernel section without a glitch. |
13 |
> |
14 |
> And the then the trouble began. I emerged gentoo-sources, and it ran fine for |
15 |
> about five minutes, and then (choosing the moment when I decided all was well |
16 |
> to go and make a pot of tea, the system rebooted itself. I booted up the |
17 |
> disk again and went through the chrooting process. When I went to emerge |
18 |
> gentoo-sources again, emerge looked for the dependencies and then the whole |
19 |
> system froze solid with one of those "this is NOT our fault" kernel panic |
20 |
> messages. |
21 |
> |
22 |
> Not to worry. I can be very patient on occasions. I cold booted the box and |
23 |
> started all over again, deleting the new partitions and going through the |
24 |
> instructions from the beginning incase I'd missed anything. Again I got to |
25 |
> emerging gentoo-sources. Again it ran for about five minutes before the |
26 |
> system rebooted itself. Again I went through the chrooting process and went |
27 |
> to emerge gentoo-sources. Again the system froze. I rebooted and rechrooted |
28 |
> and tried it again. Same result. |
29 |
> |
30 |
> I'm reluctant to believe that this is down to an arbitrary hardware fault, |
31 |
> since everything else works fine. It does seem to have something to do with |
32 |
> emerging gentoo-sources. |
33 |
> |
34 |
> Is anybody able to rescue this maiden in distress and throw some light on my |
35 |
> problem? |
36 |
> |
37 |
> Rosie |
38 |
|
39 |
An easy way to find out if this is a gentoo related problem is to |
40 |
avoid using the livecd. |
41 |
You can easily chroot into the gentoo drive from your ubuntu |
42 |
installation and try to emerge |
43 |
gentoo-sources from there. |
44 |
|
45 |
If you still get a failure you can be almost sure this is an hardware problem. |
46 |
|
47 |
If you don't get any failure, than this does NOT mean gentoo is not |
48 |
for your hardware, |
49 |
but only that the livecd configured kernel may have issues with your hardware. |
50 |
|
51 |
Of course be careful compiling your own :P |
52 |
|
53 |
-- |
54 |
Momesso (TopperH) Andrea |
55 |
http://topperh.blogspot.com |
56 |
Jabber: topper_harley@××××××.org |
57 |
ICQ: 224179391 |