From owner-acpi-jp@jp.FreeBSD.org Tue Oct  1 20:38:15 2002
Received: (from daemon@localhost)
	by castle.jp.FreeBSD.org (8.11.6+3.4W/8.11.3) id g91BcFM50196;
	Tue, 1 Oct 2002 20:38:15 +0900 (JST)
	(envelope-from owner-acpi-jp@jp.FreeBSD.org)
Received: from tasogare.imasy.or.jp (root@tasogare.imasy.or.jp [202.227.24.5])
	by castle.jp.FreeBSD.org (8.11.6+3.4W/8.11.3) with ESMTP/inet id g91BcD350191
	for <acpi-jp@jp.FreeBSD.org>; Tue, 1 Oct 2002 20:38:13 +0900 (JST)
	(envelope-from iwasaki@jp.FreeBSD.org)
Received: from localhost (iwa@tasogare.imasy.or.jp [202.227.24.5])
	by tasogare.imasy.or.jp (8.11.6+3.4W/8.11.6/tasogare) with ESMTP/inet id g91BbwY54960;
	Tue, 1 Oct 2002 20:37:58 +0900 (JST)
	(envelope-from iwasaki@jp.FreeBSD.org)
Message-Id: <20021001.203749.98096231.iwasaki@jp.FreeBSD.org>
To: obrien@freebsd.org
Cc: acpi-jp@jp.FreeBSD.org
From: Mitsuru IWASAKI <iwasaki@jp.FreeBSD.org>
In-Reply-To: <20020930221555.GA49168@dragon.nuxi.com>
References: <20020928011422.GA53408@dragon.nuxi.com>
	<20020930221555.GA49168@dragon.nuxi.com>
X-Mailer: Mew version 2.2 on Emacs 20.7 / Mule 4.0 (HANANOEN)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Reply-To: acpi-jp@jp.FreeBSD.org
Precedence: list
Date: Tue, 01 Oct 2002 20:37:49 +0900
X-Sequence: acpi-jp 1856
Subject: [acpi-jp 1856] Re: (FWD) no floppy drive with acpi.ko loaded
Errors-To: owner-acpi-jp@jp.FreeBSD.org
Sender: owner-acpi-jp@jp.FreeBSD.org
X-Originator: iwasaki@jp.FreeBSD.org
X-Distribute: distribute version 2.1 (Alpha) patchlevel 24e+020902

I'm not interested in this at all, because it seems to be your BIOS
specific issue for me.  So this will be my last mail to this thread.
Maybe somebody will help you if one is interested in this.

> On Fri, Sep 27, 2002 at 06:14:22PM -0700, David O'Brien wrote:
> > ----- Forwarded message from David O'Brien <obrien@FreeBSD.org> -----
> > Date: Fri, 13 Sep 2002 16:14:10 -0700
> > To: current@freebsd.org
> > 
> > If I load ACPI on my Gigabyte GA-7VTXE+ rev 1.0 motherboard I have no
> > floppy drive support (ie. no fdc or fd0 devices).  Below is the verbose
> > dmesg.boot both with and followed by w/o ACPI:
> 
> Here is the ACPI DSDT dump (w/o acpi.ko loaded) for this machine.

BTW, it's not a raw DSDT data.  Please specify `-o' option to
get it as mentioned in acpidump(8).

> Scope(\_SB_) {
[snip]
>     Device(PCI0) {
[snip]
>         Device(FDC0) {
>             Name(_HID, 0x0007d041)
>             Method(_STA) {

This means that the fdc is connected to pci directly (path is
_SB_.PCI0.FDC0), but I think our fdc(4) doesn't have PCI attachment as
you know.
If fdc is connected to isa actually, normally there should be a
PCI-ISA bridge definition between PCI0 and FDC0.
pciconf -lv output will be helpful.

And this is the diff of dmesg output between w/o acpi.ko case and w/ acpi.ko.
Host-PCI bridge number is different.
John, does this cause any problems?

@@ -73,8 +74,24 @@
 embedded    0   18    D   0x05  3 4 5 6 7 10 11 12 14 15
 npx0: <math processor> on motherboard
 npx0: INT 16 interface
-pcib0: <Host to PCI bridge> at pcibus 0 on motherboard
-pci0: <PCI bus> on pcib0
+acpi0: <AMIINT VIA_K7  > on motherboard
+acpi0: power button is handled as a fixed feature programming model.
+ACPI timer looks GOOD min = 2, max = 3, width = 2
[snip]
+ACPI timer looks GOOD min = 2, max = 3, width = 2
+Timecounter "ACPI-fast"  frequency 3579545 Hz
+acpi_timer0: <24-bit timer at 3.579545MHz> port 0x808-0x80b on acpi0
+acpi_cpu0: <CPU> on acpi0
+acpi_button0: <Power Button> on acpi0
+pcib1: <ACPI Host-PCI bridge> port 0xcf8-0xcff on acpi0
+pci0: <ACPI PCI bus> on pcib1
 pci0: physical bus=0
        map[10]: type 3, range 32, base e0000000, size 26, enabled
 found->        vendor=0x1106, dev=0x3099, revid=0x00

Off-topic:
>         Method(_INI) {
>             \_SB_.PCI0.IODT()
>             If(MCTH(\_OS_, "Microsoft Windows NT")) {
>                 Store(0x0, OSFL)
>             }
>             Else {
>                 If(MCTH(\_OS_, "Microsoft Windows")) {
>                     Store(0x1, OSFL)
>                 }
>                 Else {
>                     If(MCTH(\_OS_, "Microsoft WindowsME: Millennium Edition")) {
>                         Store(0x2, OSFL)
>                     }
>                     Else {
>                         Store(0x3, OSFL)
>                     }

What do you think about this?
This means that only MS Windows family OS is officially supported by
BIOS vendor.  You should not surprise if there are any problems on
unsupported OS.  If you have some problems and want to run unsupported
OS like FreeBSD, you have to add support code by yourself and
overrive DSDT at your own risk.  Or report the problem to BIOS vendor
and get fixed version of BIOS.

Thanks
