mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Michael T" <raselmsh@hotmail.com>
To: linux-kernel@vger.kernel.org
Subject: PROBLEM: PCI: mmconfig does not work with my ASUS K8N4-E board
Date: Sun, 21 May 2006 12:06:47 +0200	[thread overview]
Message-ID: <BAY122-F1005FA13DD8848952B2FDBD0A50@phx.gbl> (raw)

Hello,

I am reporting this to the kernel mailing list on the advice of Greg KH.

I would like to report a problem with my ASUS K8N4-E board/CK804 chipset.
Basically, kernels from 2.6.14 do not boot correctly unless I use the kernel 
option
pci=nommconf.  I have tested this with several kernels, including a vanilla 
2.6.14,
2.6.15, 2.6.16 and 2.6.17-rc4.  Searching on google indicated that several 
people
have similar problems with similar hardware - obviously I can't say for sure 
that it
is exactly the same problem, but in at least two other cases, disabling 
mmconfig
enabled the system to boot.

Note that I can also boot by disabling ACPI, which requires me to specify
in the BIOS that the operating system in use is "non-PnP" in order for the
mouse to work.   If I specify
ide=nodma as a kernel parameter, I can boot, but various other components
including the nVidia ethernet (forcedeth driver) do not work.

I have included the end of the messages printed by
the kernel on bootup when mmconfig is not disabled below.  I can happily 
either
post additional information such as .config, dmesg (when the kernel is 
booted
with mmconfig disabled) or lspci output to the mailing list or send it by 
e-mail to
anyone who is interested, but I have not posted anything initially to avoid
clogging up the list.

Please note that I am not subscribed to the mailing list, so I would request 
you to
CC me any answers you would like me to reply to fast.  This e-mail address 
is not
permanent, but I will monitor it at least as long as this thread is 
relevant.

Regards and thanks,

Michael

End of bootlog when mmconfig is active follows:

NFORCE-CK804: IDE controller at PCI slot 0000:00:06.0
NFORCE-CK804: chipset revision 242
NFORCE-CK804: not 100% native mode: will probe irqs later
     ide0: BM-DMA at 0x1000-0x1007, BIOS settings: hda:DMA, hdb: DMA
NFORCE-CK804 Bus-Master DMA disabled (BIOS)
hda: WDC WD1600JB-00REA0, ATA DISK drive
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
hdc: HL-DT-ST DVDRAM GSA-4167B, ATAPI CD/DVD-ROM drive
ide1 at 0x170-0x177,0x376 ob irq 15
SCSI subsystem initialized
hda: max request size 1024KiB
hda: cache flushes supported
hda:<4>hda: dma_timer_expiry: dma_status == 0xff
hda: dma_timer_expiry: dma_status == 0xff
hda: dma_timer_expiry: dma_status == 0xff
(...)
Done.
Begin: Waiting for root file system... ...
hda: dma_timer_expiry: dma_status == 0xff
(...)
Done.
ALERT! /dev/hda2 does not exist. Dropping to a shell!
(shell...)

_________________________________________________________________
Express yourself instantly with MSN Messenger! Download today it's FREE! 
http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/


             reply	other threads:[~2006-05-21 10:06 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-21 10:06 Michael T [this message]
2006-05-21 14:03 ` Arjan van de Ven
2006-05-22 11:20 ` Andi Kleen

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=BAY122-F1005FA13DD8848952B2FDBD0A50@phx.gbl \
    --to=raselmsh@hotmail.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

all inboxes | Powered by JetHome®