Jarjar Apprentice
Joined: 21 Jul 2002 Posts: 265 Location: Sweden
|
Posted: Fri Dec 06, 2002 11:51 pm Post subject: Livecd compilation problems (bootstrap) :( |
|
|
--- NOTE: PROBLEM SOLVED USING GENTOO 1.2 ---
00:36:25 (54.80KB/s) - `/usr/portage/distfiles/binutils-2.13.90.0.4.tar.bz2` saved [xxxxx/xxxxx]
>>> md5 binutils-2.13.90.0.4.tar.bz2
Oops: 0002
CPU: 0
EIP: 0010:[<8011681a>] Not tainted
EFLAGS: 00010003
<all registers, eax-edx, esi, edi, ebp, esp, ds, es, ss>
Process ebuild.sh (pid: 405, stackpage=95b39000)
Stack: <lotsa instructions in hex (words)>
Call trace: [<8010e3fd>] [<8012591a>] [<80122334>] [<801221c5>] [<80121f53>] [<8010ab1d>] [<8010d578>]
Code: f0 ff 00 8d 76 00 b8 e0 60 44 80 8b 14 98 4a 85 d2 89 14 98
<0>Kernel panic: Aiee, killing interrupt handler!
In Inderrupt handler - not syncing
_ <-- blink blink
What the hell is wrong here? I'm using the basic livecd. Same thing with or without even touching make.conf.
BTW; It worked as a charm with gentoo a few weeks ago.
BTW2; Happens on differenct files during the bootstrapping. First it happened at once, and I got some assembler error. I rebooted and tried again, worked for like 5 minutes..
Some H/W:
MB: Asus A7V rev1.02
CPU: AMD Duron 700@950 (no, it's _not_ the overclocking, been running for 2 years 1 week _rock_ stable)
Memory: 2x256MB and 1x128MB, I did NOT use the 128MB when this was my workstation computer.
Is it possible the memory is fucking it all up?
Should I try to burn another image on another CD?
Help please!
And, if the information is insufficient, please ask
Edit: It's not the memory; I'm using the once again rock-stable 2x256 again.. I get another fault using emerge in gentoo 1.2 too. I _won't_ surrender to debian damnit.
Edit2: There! I fixed the 1.2 installation instead; by using portage-rescue. Now I'm compiling the bootstrap for 1.2 instead... Maybe I'll switch to 1.4 when it's final |
|