public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Stephen Clark <Stephen.Clark@seclark.us>
To: Arjan van de Ven <arjan@infradead.org>
Cc: Shaun Q <shaun@c-think.com>, Jesper Juhl <jesper.juhl@gmail.com>,
	linux-kernel@vger.kernel.org
Subject: Re: Dual cores on Core2Duo not detected?
Date: Mon, 13 Nov 2006 11:33:24 -0500	[thread overview]
Message-ID: <45589E54.3000603@seclark.us> (raw)
In-Reply-To: <1163435248.15249.179.camel@laptopd505.fenrus.org>

Arjan van de Ven wrote:

>>Processor #0 6:15 APIC version 20
>>Setting APIC routing to physical flat
>>BIOS bug, no explicit IRQ entries, using default mptable. (tell your hw 
>>vendor)
>>    
>>
>
>hmmm smells like a disabled ACPI, since normally this info comes from
>ACPI nowadays, not the mptable
>
>
>
>
>if you want to mail me at work (you don't), use arjan (at) linux.intel.com
>Test the interaction between Linux and your BIOS via http://www.linuxfirmwarekit.org
>
>
>  
>
 From Shaun's previous E-Mail

Bootdata ok (command line is root=/dev/sda2 vga=0x31a acpi=off 

                                                                                                             
^^^^^^

-- 

"They that give up essential liberty to obtain temporary safety, 
deserve neither liberty nor safety."  (Ben Franklin)

"The course of history shows that as a government grows, liberty 
decreases."  (Thomas Jefferson)




  reply	other threads:[~2006-11-13 16:33 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-13  7:24 Dual cores on Core2Duo not detected? Shaun Q
2006-11-13 13:46 ` Stephen Clark
2006-11-13 15:52   ` Shaun Q
2006-11-13 16:03     ` Jesper Juhl
2006-11-13 16:17       ` Shaun Q
2006-11-13 16:27         ` Arjan van de Ven
2006-11-13 16:33           ` Stephen Clark [this message]
2006-11-13 16:57           ` Shaun Q
2006-11-13 14:00 ` Jesper Juhl
2006-11-13 15:54   ` Shaun Q
2006-11-13 14:44 ` Mark Lord
2006-11-13 15:51   ` Shaun Q

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=45589E54.3000603@seclark.us \
    --to=stephen.clark@seclark.us \
    --cc=arjan@infradead.org \
    --cc=jesper.juhl@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=shaun@c-think.com \
    /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