From: James Wright <james@jigsawdezign.com>
To: "Nakajima, Jun" <jun.nakajima@intel.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: P4 3.06Ghz Hyperthreading with 2.4.20?
Date: Thu, 20 Mar 2003 13:37:12 +0000 [thread overview]
Message-ID: <20030320133712.468930bd.james@jigsawdezign.com> (raw)
In-Reply-To: <3014AAAC8E0930438FD38EBF6DCEB564013393B6@fmsmsx407.fm.intel.com>
So i can apply the ACPI patch to 2.4.20, and it will work, even though my motherboard BIOS
doesn't provide the MPS table? Do i still need to use "acpismp=force" option? What do you mean
by *configuring* acpi, do i need the "acpid" or other resources, than just enabling it?
Thanks,
James
On Wed, 19 Mar 2003 18:50:59 -0800
"Nakajima, Jun" <jun.nakajima@intel.com> wrote:
> You need to apply the ACPI patch: http://sourceforge.net/projects/acpi and *configure* APIC.
>
> The 2.4 kernel depends on the MPS table for all but logical processors. If MPS table is not present, it will fall back to UP.
>
> Thanks,
> Jun
>
> > -----Original Message-----
> > From: James Wright [mailto:james@jigsawdezign.com]
> > Sent: Wednesday, March 19, 2003 5:34 PM
> > To: linux-kernel@vger.kernel.org
> > Subject: P4 3.06Ghz Hyperthreading with 2.4.20?
> >
> > Hello,
> >
> > I have kernel 2.4.20 with a single P4 3.06Ghz CPU and Asus P4G8X
> > motherboard
> > (with the Intel E7205) Chipset. I have enabled Hyperthreading in the BIOS
> > options,
> > compiled in SMP & ACPI support, and also tried adding "acpismp=force" to
> > my lilo
> > kernel cmdline, but it just doesn't seem to detect the second Logical CPU.
> > My
> > current theory is that this is bcos Linux expects the motherboard to be an
> > SMP
> > item (as with the Xeon boards) but this board is a Single processor board,
> > ansd
> > doesn't have an MP table, but the cpu info is held in the ACPI tables.?!?
> >
> > I have tried installing 2.5.65 but can't get past the compile due to
> > compile-time
> > errors... Is this a known problem? SHall i just disable Hyperthreading
> > until a new
> > kernel release?
> >
> >
> > Thanks,
> > James
> >
> >
> >
> > -
> > To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> > the body of a message to majordomo@vger.kernel.org
> > More majordomo info at http://vger.kernel.org/majordomo-info.html
> > Please read the FAQ at http://www.tux.org/lkml/
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
next prev parent reply other threads:[~2003-03-20 13:26 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-20 2:50 P4 3.06Ghz Hyperthreading with 2.4.20? Nakajima, Jun
2003-03-20 13:37 ` James Wright [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-03-20 22:32 Grover, Andrew
2003-03-20 23:45 ` James Wright
2003-03-20 17:11 Grover, Andrew
2003-03-20 21:29 ` James Wright
2003-03-20 22:27 ` J.A. Magallon
2003-03-20 2:53 Nakajima, Jun
2003-03-20 1:34 James Wright
2003-03-20 1:32 James Wright
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=20030320133712.468930bd.james@jigsawdezign.com \
--to=james@jigsawdezign.com \
--cc=jun.nakajima@intel.com \
--cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox