From: cerise@armory.com
To: linux-smp@vger.kernel.org
Subject: Re: Dual Core CPU on Abit NI8-Board
Date: Tue, 4 Apr 2006 23:39:41 -0700 [thread overview]
Message-ID: <20060405063941.GA16737@boogeyman> (raw)
In-Reply-To: <200604050828.02444.f.vondaak@kpage.de>
Hi Frank:
This sounds suspiciously to me like those kernels don't have SMP support
built in. Are those kernels you built yourself or obtained from your distro?
-Phil/CERisE
On Wed, Apr 05, 2006 at 08:28:02AM +0200, Frank von Daak wrote:
> Hello to all!
>
> I hope that this is the right place for me to report my problem - if not,
> please tell me!
>
> Some days ago I've purchased a new motherboard, cpu and graphics-adapters.
> The board is called "Abit NI8 SLI" which has a nForce4-Chipset and a socket
> 775.
>
> http://www.abit-usa.com/products/mb/products.php?categories=1&model=280
>
> The CPU is a Pentium-D 2,8 GHz. And the graphics-adapters are two
> GeForce7800GTX-Cards...
>
> My problem is, that a "cat /proc/cpuinfo" shows me just one cpu with one core.
> I've tested this with kernels 2.6.16.1 and 2.6.17-rc1 (x86 and x86_64)
>
> If I add the following line in my lilo.conf to the kernel, I can see both
> cpu's:
> append="pci=noacpi pci=routeirq noapic acpi=off"
>
> After this my cpuinfo looks like this:
> http://www.kpage.de/cpuinfo.txt
>
> and dmesg say's this:
> http://www.kpage.de/dmesg.txt
>
> But if I do so, the machine is running very unstable and is hanging after a
> while. The crashes will happen espacialy if I run OpenGL-Applications like
> "glxgears".
>
> Can someone of you tell me, what I can do to fix this problem?
> If you need further information, please tell me!
>
> Thank you very much and greetings!
> Frank
>
> --
> Name: Frank von Daak
> eMail: f.vondaak@kpage.de Homepage: http://www.kpage.de
> "It takes a revolution, to make a solution!
> Bob Marley"
> -
> To unsubscribe from this list: send the line "unsubscribe linux-smp" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2006-04-05 6:39 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-05 6:28 Dual Core CPU on Abit NI8-Board Frank von Daak
2006-04-05 6:39 ` cerise [this message]
2006-04-05 7:13 ` Frank von Daak
2006-04-05 16:57 ` cerise
[not found] ` <cbe23c50604050011i3bcd433dxbf0bf826ba679324@mail.gmail.com>
2006-04-05 8:39 ` Frank von Daak
2006-04-05 9:43 ` Frank von Daak
[not found] ` <cbe23c50604050315u3daad82x14beed5ed16c43fd@mail.gmail.com>
2006-04-05 12:05 ` Frank von Daak
2006-04-06 6:27 ` Frank von Daak
2006-04-06 20:39 ` Frank von Daak
2006-04-06 20:58 ` Randy.Dunlap
-- strict thread matches above, loose matches on Subject: below --
2006-04-07 5:07 Frank von Daak
2006-04-07 9:19 ` Frank von Daak
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20060405063941.GA16737@boogeyman \
--to=cerise@armory.com \
--cc=linux-smp@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.