Arch Linux

KoS

Member

Registered: 2006-02-02

Posts: 35

AMD64 with arch32 - symbol lookup error, segfault [solved]

I have upgraded my PC from an older motherboard (VIA KT600 chipset) with Sempron CPU and AGP bus GPU to Abit KN9 Ultra motherboard (MCP55-Ultra aka. nForce 570 Ultra chipset) with Athlon 64 3500+ CPU and PCI-e GPU (nVidia 7600GS). I still use an ATA HDD (Samsung 80 GB).
Naturally I was not able to boot with the previous ramdisk, but with the fallback one.
I also needed to add "noapic" option to the kernel command line (the full command line is: root=/dev/hda2 ro noapic).

The problem is that many times during bootup I face "symbol lookup error: ..." for various libraries. Then after several restarts when I am able to boot in, still many applications (e.g. Firefox, konqueror, etc.) give symbol lookup errors for various libraries, or segmentation fault.
So practically I can't use my system.

Am I missing a kernel parameter on the command line? Or some other thing that I should set up for this system to work?

If somebody is using AMD64 CPU (and possibly nForce chipset) with Arch32, please can you inform me about your kernel command line parameters or what else is needed?

I ran Memetest for 6 hours (12x full run) without any error, and I have also fully checked my HDD and no errors.

So once again here comes the specifications of my system (hoping it might be usefull):
ArchLinux 32bit version with latest updates
Kernel: 2.6.19.1
Kernel command line: root=/dev/hda2 ro noapic
Initrd: kernel26-fallback.img
Motherboard: Abit KN9 Ultra
CPU: Athlon 64 3500+
RAM: 2x512 DDR2 677 MHz
GPU: PCI-e Gainward GeForce 7600GS
PCI Soundcard: Audigy 2 ZS
HDD: ATA Samsung 80GB
DVD: ATA DVD ROM

If any other information is needed, just tell me.

Any help is wellcome.
Thanks in advance.

Edit: title changed to be more concrete
Edit: title changed to [solved] see below why

KoS

Member

Registered: 2006-02-02

Posts: 35

Re: AMD64 with arch32 - symbol lookup error, segfault [solved]

Update to this issue:
It looks like I have faced an nForce chipset problem, which handles HDDs badly (it is mentioned in a few forums). I hope that a motherboard change will fix my problem.
I will try to change the title to [fixed] when I check the system with a new mobo.

JGC

Developer

Registered: 2003-12-03

Posts: 1,664

Re: AMD64 with arch32 - symbol lookup error, segfault [solved]

Try turning off ACPI. Nowadays you're fucked if manufacturers don't deliver a BIOS with correct ACPI support. Asus is known to have the worst ACPI support of all, don't know about Abit.

byte

Member

From: Düsseldorf (DE)

Registered: 2006-05-01

Posts: 2,046

Re: AMD64 with arch32 - symbol lookup error, segfault [solved]

Yep, ACPI can be a mess. Since 2.6.12 kernel (with slackware) I needed acpi=off in order to boot normally or make my cdrom work (lost interrupt stuff).
Last week I tried again and finally found a working kernel commandline (after finding even more issues inbetween): ... pci=noacpi clocksource=pit

I spent a lot of time reading kernel-parameters.txt (kernel sources), maybe just try searching for nforce in there, I'm sure there are some options for it.

---

1000

KoS

Member

Registered: 2006-02-02

Posts: 35

Re: AMD64 with arch32 - symbol lookup error, segfault [solved]

Thank you guys for your response!
For now it looks like this is a real harware problem, as the problems are present not only under Linux. To check this I pushed up a windoze, and it was doing really strange things (stranger than usually - dll problems, system check even after normal shut down, etc.), so for now I'm pretty much concerned that it is a hw bug.
The other thing is when I boot from a Live CD Linux (Puppy Linux with 2.6.18.X kernel which supports MCP 55 chipset) no problem arises.

But then again I will definitely try acpi=off and the other options you guys suggested on the new mobo to get rid of any possible software problems.

KoS

Member

Registered: 2006-02-02

Posts: 35

Re: AMD64 with arch32 - symbol lookup error, segfault [solved]

Hi!

It looks like the problem was caused by one of the two 512 MB DDR2 RAMs (667 MHz), even if memtest didn't show any errors after running twice for 8 hours.
For now the RAMs are changed for two 512 MB 533 MHz DDR2 RAMs and for the first tests it looks ok... I will be cautious for a few days anyway....

KoS

Member

Registered: 2006-02-02

Posts: 35

Re: AMD64 with arch32 - symbol lookup error, segfault [solved]

The system is working correctly now for more than 10 days, so the problem was definitely the RAM (although the up to date memtest showed nothing).
From now I will not believe blindly in memtests....