SUSE / openSUSEThis Forum is for the discussion of Suse Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I am still trying to find a way to make my AMD dual core 64 bit processor work in smp mode in 64 bits. It works in 32 bits. But on generic install, 64 bits, smp, it crashes on boot with an APIC kernel panic.
If I add the noapic line to the boot options, it will boot, but only one CPU registers in the ksysguard.
Can someone tell me:
1) Why the dual core 32 bit APIC works but not the dual core 64 bits
2) Is this something that can be resolved through a kernel patch or is this a BIOS problem (no guesses, please, I need to know who to pay for support).
3) Are their any other boot options that will make this work in dual core 64 bits?
Thanks. For the record:
Shuttle SN95G5V3
nForce3-250 chipset
2GB ram
nVidia 9800 PCI
2 SATA drives
Well I don't know if this will solve your problem, but I had a different, but related, problem with my dual core and this solved it. There's an official Athlon64 Powernow driver from AMD through their website, but it's also included in the kernel starting with 2.6.13. If you do make menuconfig, it's Power management options > CPU frequency scaling > AMD Opteron/Athlon64 PowerNow!. Try compiling 2.6.13 with this driver included, and see what happens.
Last edited by walmartshopper; 09-04-2005 at 04:12 PM.
That driver is included as a Module in the kernel that ships with Suse. which is 2.6.11
Is it good enough to leave as a module or should I recompile with it added into the kernel?
Also, do you think the 2.6.11 is good enough or should I get the latest? I tried the latest kernel a while ago, but I don't remember checking the power now setting.
Thanks for the suggest, but it still doesn't work. Please give me your opinion on the above questions.
Version 1.50.xx of the driver can use either the
PSB table of the ACPI objects. It supports Opteron,
Athlon 64 processors, in both single and dual core
versions, for all of the 754, 939, 940, and 1207
pin packages. This driver supports SMP frequency
management but will not work on SMP or dual core
systems unless the ACPI powerstate objects are
available. It will only work on 2.6.10 and later
kernels. This driver is distributed with the
2.6.13 and later kernels.
The one that shipped with Suse might be an older version. I'm not sure if it makes any difference whether it's a module or built in. I'd suggest trying the 2.6.13 kernel and building the driver into it. If that doesn't work, I don't know what else to tell you. But it's definitely worth a try in my opinion.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.