Stage 3 install... emerge --sync segmentation fault

[ishtvan222]

Hi,

This is my second time trying to install gentoo, i gave up the first time. I am doing a stage 3 on a 450 mhz box with 256 ram. I was following the Gentoo Handbook instructions and it was going well until I came upon emerge --sync. When i started it text flew across the screen for about 30 min then it got to




>>>Updating portage cache... /Unable to handle kernel paging request at virtual address 00142454
printing eip:
c014748e
*pde = 00000000
Oops: 0002 [#1]
SMP
Modules linked in: ipv6 evdev tulip crc32 parport_pc parport sbp2 ohci1394 ieeei394 ohci_hcd uhci_hcd usb_storage ehci_hcd
CPU: 0
EIP: 0060:[<c014748e>] Not tainted VLI
EFLAGS 00010246 (2.6.9-gentoo-r1)
eax: c4c7c000 ebx: 00000000 ecx:00000000 edx: 00000003
esi: cd35fd08 edi: c4c7d000 ebp:00001000 esp: cd35fce9
ds: 007b es:007b ss:0068
Process emerge (pid: 4631, threadinfo=cd35e000 task=cf2b8110)
Stack: 7ec4c7c0 e0000009 ______ ______ _____ ______ _______ ________
_______ _____ ______ ______ _____ ______ _______ ________
_______ _____ ______ ______ _____ ______ _______ ________
Call trace:
Code:44 39 4c 24 18 72 06 3b 6c 24 48 76 1a 8d 44 24 1c 50 6a 01 6a 00 e8 da 11 00 00 8b 44 24 28 89 06 83 c4 0c 83 c6 04
83 44 24 10 <01> 83 54 24 14 00 8b 44 24 1c 89 6c 24 18 8b 40 04 3b 44 24 08
Segmentation fault



The blanks I put in are eight digit combinations of letters and numbers. I have a feeling that there may be something wrong with the ram on this machine because when it had windows it always said 252 MB instead of 256 which it has. Also, it has a 512 MB swap space.

After it said segmentation fault i got to a command line and tried to run nano but then it crashed.

This box has run a knoppix install and a debian install, but i got tired of them.

Anything you can tell me will help because i have no idea what to do now.

[slycordinator]

What processor do you have? (we know it's 450 MHZ but we don't know the brand or model).

What stage3 tarball did you use?

It's possible you use the wrong tarball, due to your processor type and the tarball you downloaded not matching.

[ishtvan222]

I have a amd k6-2
when i did the make.conf i put -march=k6-2 in the cflag place
i used the x86 tarball

[thefatdx]

try taking the march flag out

[ishtvan222]

Should i replace the march flag with -mcpu=x86 ?

Originally it had -mcpu=686 but i took that out.

Should i proceed with a fresh install or should i continue with this one?

and how would I continue with this one if i decided to? (i already did the chroot part.)

Thanks

[Sven Vermeulen]

I'm not sure this is due to wrong CFLAGS settings - that would lead to a regular segmentation fault (invalid instruction mostly). The kernel Oops is what's causing troubles, which can be due to faulty memory, but can also be triggered by a kernel bug.

Verify your memory using memtest; if all memory comes out clean, retry and see if you Oops out again during the installation. If you do, you might want to try to install Gentoo using a different kernel...

[ishtvan222]

well, my memory came out clean. Then i started the installation again from freshly burned cdrw. I am using the minimal install for x86. in the make.conf i changed the default -mcpu=686 to -mcpu=k6-2 . I did not use march this time because the make.conf.example warned not to for the k6. Then when I did the emerge --sync I got the same error as before.

Should I try again with a different stage? (I dont mind doing a stage 1 now that i have a week off from school...)
And if a do a stage 1 what cflags should i use?

[Bob P]

i haven't compiled for a K6 yet, but i have one that will be getting gentoo'd soon. i remember reading about a bug wherein architecture specification is rather murky with the K6. IIRC, there are a bunch of different cores that are all classified as K6, and you can run into some real problems if you specify the wrong architecture. IIRC, there should be a reference to the bug in make.conf.example. good luck.
_________________
.
Stage 1/3 | Jackass! | Rockhopper! | Thanks | Google Sucks