public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Adrian Bunk <bunk@stusta.de>
To: Thomas Voegtle <tv@lio96.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.16.52 can't boot on Intel DG965SS
Date: Wed, 6 Jun 2007 18:04:51 +0200	[thread overview]
Message-ID: <20070606160451.GN5500@stusta.de> (raw)
In-Reply-To: <Pine.LNX.4.63.0706061436190.32355@er-systems.de>

On Wed, Jun 06, 2007 at 05:16:00PM +0200, Thomas Voegtle wrote:
> 
> Hi,
> 
> I want to use 2.6.16.y on the Intel DG965SS mainboard, but the kernel 
> stops booting:
> 
> ...
> ACPI: bus type pci registered
> PCI: Using MMCONFIG
> ACPI: Subsystem revision 20060127
> ACPI: Interpreter enabled
> ACPI: Using IOAPIC for interrupt routing
> ACPI: PCI Root Bridge [PCI0] (0000:00)
> ACPI: Assume root bridge [\_SB_.PCIO] bus is 0 
> 
> 
> 
> A Kernel 2.6.16.52 boots with pci=nommconf.
> A SuSE 10.1 installation cd boots with no special bootparams.
> A Kernel 2.6.17 vanilla boots with no special bootparams.
> 
> 
> So something is missing in 2.6.16.y, can anyone point me to a patch or 
> something else which enables this?
>...

Set in the kernel configuration:
  Bus options (PCI, PCMCIA, EISA, MCA, ISA)
    PCI access mode
to "Direct".

There are fixes in this area in 2.6.17, but that's something I'll not 
fiddle with in 2.6.16.

>       Thomas

cu
Adrian

-- 

       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed


      reply	other threads:[~2007-06-06 16:04 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-06 15:16 2.6.16.52 can't boot on Intel DG965SS Thomas Voegtle
2007-06-06 16:04 ` Adrian Bunk [this message]

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=20070606160451.GN5500@stusta.de \
    --to=bunk@stusta.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tv@lio96.de \
    /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