Re: [BUG?] ata disk running maximum at DMA33 with 2.6.20 and new pata driver, NV CK804 ide controller.
> As an aside to this sort of problem, shouldn't we print some kind of > loud message in dmesg when we force a high-UDMA-capable device down to > UDMA33 due to a 40-wire cable detection? In the case where it truly is a > 40-wire cable the user may want to know that and replace the cable, if > it isn't it gives more of a hint of why the drive isn't running at full > speed.. Send patches. We also probably want to change speed straight from UDMAlots to UDMA33 if the cable is CBL_UNK so that we can rapidly recover in the cases where the controller says "I'm crap I don't really know" (eg ATI and Nvidia without ACPI) - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [BUG?] ata disk running maximum at DMA33 with 2.6.20 and new pata driver, NV CK804 ide controller.
Well, the cable is OK, of course I checked.
On Wed, 7 Feb 2007, Robert Hancock wrote:
Date: Wed, 07 Feb 2007 22:36:58 -0600
From: Robert Hancock <[EMAIL PROTECTED]>
To: Alan <[EMAIL PROTECTED]>,
linux-kernel
Cc: Luigi Genoni <[EMAIL PROTECTED]>
Subject: Re: [BUG?] ata disk running maximum at DMA33 with 2.6.20 and new pata
driver, NV CK804 ide controller.
Resent-Date: Thu, 08 Feb 2007 05:47:22 +0100
Resent-From: <[EMAIL PROTECTED]>
Alan wrote:
On Wed, 7 Feb 2007 01:19:36 +0100
Luigi Genoni <[EMAIL PROTECTED]> wrote:
Hi,
since upgrading to kernel 2.6.20 my pata disk, using new pata driver, is
initialized maximum in DMA33 mode (and obviously performances drop
consequently), as you can see from:
Interesting.
Willing to test any patch.
Firstly can you see if its consistently the case that booting 2.6.20
gives UDMA33 and 2.6.19 UDMA100 over a few reboots. If it is please drop
the 2.6.19 drivers/ata/pamd_amd into 2.6.20 and try that.
As an aside to this sort of problem, shouldn't we print some kind of loud
message in dmesg when we force a high-UDMA-capable device down to UDMA33 due
to a 40-wire cable detection? In the case where it truly is a 40-wire cable
the user may want to know that and replace the cable, if it isn't it gives
more of a hint of why the drive isn't running at full speed..
--
Robert Hancock Saskatoon, SK, Canada
To email, remove "nospam" from [EMAIL PROTECTED]
Home Page: http://www.roberthancock.com/
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
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 [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Re: [BUG?] ata disk running maximum at DMA33 with 2.6.20 and new pata driver, NV CK804 ide controller.
Alan wrote: On Wed, 7 Feb 2007 01:19:36 +0100 Luigi Genoni <[EMAIL PROTECTED]> wrote: Hi, since upgrading to kernel 2.6.20 my pata disk, using new pata driver, is initialized maximum in DMA33 mode (and obviously performances drop consequently), as you can see from: Interesting. Willing to test any patch. Firstly can you see if its consistently the case that booting 2.6.20 gives UDMA33 and 2.6.19 UDMA100 over a few reboots. If it is please drop the 2.6.19 drivers/ata/pamd_amd into 2.6.20 and try that. As an aside to this sort of problem, shouldn't we print some kind of loud message in dmesg when we force a high-UDMA-capable device down to UDMA33 due to a 40-wire cable detection? In the case where it truly is a 40-wire cable the user may want to know that and replace the cable, if it isn't it gives more of a hint of why the drive isn't running at full speed.. -- Robert Hancock Saskatoon, SK, Canada To email, remove "nospam" from [EMAIL PROTECTED] Home Page: http://www.roberthancock.com/ - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [BUG?] ata disk running maximum at DMA33 with 2.6.20 and new pata driver, NV CK804 ide controller.
I did the test you asked and yes, it is consistently booting at DMA33 with
2.6.20 and DMA100 with 2.6.19.3 (20 reboots, 10 2.6.20 and 10 2.6.19 in
sparse order).
I am compiling a 2.6.20 kernel with older pata_amd.c driver and will let
you know. seeing the diff I do exspect it to compile cleanly.
Luigi
On Wed, 7 Feb 2007, Alan wrote:
Date: Wed, 7 Feb 2007 12:20:00 +
From: Alan <[EMAIL PROTECTED]>
To: Luigi Genoni <[EMAIL PROTECTED]>
Cc: linux-ide@vger.kernel.org, [EMAIL PROTECTED], [EMAIL PROTECTED],
[EMAIL PROTECTED], linux-kernel@vger.kernel.org
Subject: Re: [BUG?] ata disk running maximum at DMA33 with 2.6.20 and new pata
driver, NV CK804 ide controller.
Resent-Date: Wed, 07 Feb 2007 13:17:42 +0100
Resent-From: <[EMAIL PROTECTED]>
On Wed, 7 Feb 2007 01:19:36 +0100
Luigi Genoni <[EMAIL PROTECTED]> wrote:
Hi,
since upgrading to kernel 2.6.20 my pata disk, using new pata driver, is
initialized maximum in DMA33 mode (and obviously performances drop
consequently), as you can see from:
Interesting.
Willing to test any patch.
Firstly can you see if its consistently the case that booting 2.6.20
gives UDMA33 and 2.6.19 UDMA100 over a few reboots. If it is please drop
the 2.6.19 drivers/ata/pamd_amd into 2.6.20 and try that.
Thanks
Alan
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
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 [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Re: [BUG?] ata disk running maximum at DMA33 with 2.6.20 and new pata driver, NV CK804 ide controller.
On Wed, 7 Feb 2007 01:19:36 +0100 Luigi Genoni <[EMAIL PROTECTED]> wrote: > Hi, > since upgrading to kernel 2.6.20 my pata disk, using new pata driver, is > initialized maximum in DMA33 mode (and obviously performances drop > consequently), as you can see from: Interesting. > Willing to test any patch. Firstly can you see if its consistently the case that booting 2.6.20 gives UDMA33 and 2.6.19 UDMA100 over a few reboots. If it is please drop the 2.6.19 drivers/ata/pamd_amd into 2.6.20 and try that. Thanks Alan - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [BUG?] ata disk running maximum at DMA33 with 2.6.20 and new pata driver, NV CK804 ide controller.
I boot 2.6.20 also on a pentium4 with intel 82801EB/ER (ICH5/ICH5R) IDE
Controller and the same pata disk.
On this controller the disk runs in DMA100 as it should, so I'm prone to
think it is a pata_amd.c driver trouble. Should try downgrading this
driver from version 0.2.7 to version 0.2.4?
I looked at the diff, but I do not see why the new "static int
amd_reinit_one(struct pci_dev *pdev)" , that has inside a clear
a if (pdev->vendor == PCI_VENDOR_ID_AMD), should have some impact on a
nvidia controller.
suggestions?
regards
Luigi Genoni
On Wed, 7 Feb 2007, Luigi Genoni wrote:
Date: Wed, 7 Feb 2007 01:19:36 +0100
From: Luigi Genoni <[EMAIL PROTECTED]>
To: linux-ide@vger.kernel.org, [EMAIL PROTECTED], [EMAIL PROTECTED],
[EMAIL PROTECTED]
Cc: linux-kernel@vger.kernel.org
Subject: [BUG?] ata disk running maximum at DMA33 with 2.6.20 and new pata
driver, NV CK804 ide controller.
Hi,
since upgrading to kernel 2.6.20 my pata disk, using new pata driver, is
initialized maximum in DMA33 mode (and obviously performances drop
consequently), as you can see from:
pata_amd :00:06.0: version 0.2.7
PCI: Setting latency timer of device :00:06.0 to 64
ata5: PATA max UDMA/133 cmd 0x1F0 ctl 0x3F6 bmdma 0xF000 irq 14
ata6: PATA max UDMA/133 cmd 0x170 ctl 0x376 bmdma 0xF008 irq 15
scsi4 : pata_amd
ata5.00: ATA-7, max UDMA/100, 156368016 sectors: LBA48
ata5.00: ata5: dev 0 multi count 1
ata5.00: configured for UDMA/33
scsi5 : pata_amd
ata6.00: ATAPI, max UDMA/33
ata6.00: configured for UDMA/33
scsi 4:0:0:0: Direct-Access ATA SAMSUNG SP0822N WA10 PQ: 0 ANSI:
5
SCSI device sdc: 156368016 512-byte hdwr sectors (80060 MB)
sdc: Write Protect is off
sdc: Mode Sense: 00 3a 00 00
SCSI device sdc: write cache: enabled, read cache: enabled, doesn't
support DPO
or FUA
SCSI device sdc: 156368016 512-byte hdwr sectors (80060 MB)
sdc: Write Protect is off
sdc: Mode Sense: 00 3a 00 00
SCSI device sdc: write cache: enabled, read cache: enabled, doesn't
support DPO
or FUA
sdc: sdc1 sdc2 sdc3
sd 4:0:0:0: Attached scsi disk sdc
while with kernel 2.6.19.X it was initialized correctly in DMA100 mode:
pata_amd :00:06.0: version 0.2.4
PCI: Setting latency timer of device :00:06.0 to 64
ata5: PATA max UDMA/133 cmd 0x1F0 ctl 0x3F6 bmdma 0xF000 irq 14
ata6: PATA max UDMA/133 cmd 0x170 ctl 0x376 bmdma 0xF008 irq 15
scsi4 : pata_amd
ata5.00: ATA-7, max UDMA/100, 156368016 sectors: LBA48
ata5.00: ata5: dev 0 multi count 1
ata5.00: configured for UDMA/100
scsi5 : pata_amd
ata6.00: ATAPI, max UDMA/33
ata6.00: configured for UDMA/33
scsi 4:0:0:0: Direct-Access ATA SAMSUNG SP0822N WA10 PQ: 0 ANSI: 5
SCSI device sdc: 156368016 512-byte hdwr sectors (80060 MB)
sdc: Write Protect is off
sdc: Mode Sense: 00 3a 00 00
SCSI device sdc: drive cache: write back
SCSI device sdc: 156368016 512-byte hdwr sectors (80060 MB)
sdc: Write Protect is off
sdc: Mode Sense: 00 3a 00 00
SCSI device sdc: drive cache: write back
sdc: sdc1 sdc2 sdc3
sd 4:0:0:0: Attached scsi disk sdc
I have other 2 sata disks on this system, and I have no problems with
them. I Wonder if this is due to some controller/disk problem triggered
just by 2.6.20 kernel (I saw there are a lot of changes into eh code),
while 2.6.19.X and previous sees everything OK.
Also forf the sata disks, in fact, I see this "doesn't support DPO or FUA"
warning, but I have to admit I do not know which features it is referred to.
This system is an Athlon64 X2 3800+ with an nvidia2 IDE controller
here is the lspci -v
00:00.0 Memory controller: nVidia Corporation CK804 Memory Controller (rev
a3)
Subsystem: ASUSTeK Computer Inc. Unknown device 815a
Flags: bus master, 66MHz, fast devsel, latency 0
Capabilities: [44] HyperTransport: Slave or Primary Interface
Capabilities: [e0] HyperTransport: MSI Mapping
00:01.0 ISA bridge: nVidia Corporation CK804 ISA Bridge (rev a3)
Subsystem: ASUSTeK Computer Inc. K8N4-E Mainboard
Flags: bus master, 66MHz, fast devsel, latency 0
00:01.1 SMBus: nVidia Corporation CK804 SMBus (rev a2)
Subsystem: ASUSTeK Computer Inc. K8N4-E Mainboard
Flags: 66MHz, fast devsel, IRQ 10
I/O ports at e400 [size=32]
I/O ports at 4c00 [size=64]
I/O ports at 4c40 [size=64]
Capabilities: [44] Power Management version 2
00:02.0 USB Controller: nVidia Corporation CK804 USB Controller (rev a2)
(prog-if 10 [OHCI])
Subsystem: ASUSTeK Computer Inc. K8N4-E Mainboard
Flags: bus master, 66MHz, fast devsel, latency 0, IRQ 20
Memory at d4004000 (32-bit, non-prefetchable) [size=4K]
Capabilities: [44] Power Management version 2
00:02.1 USB Controller: nVidia Corporation CK804 USB Controller (rev a3)
(prog-if 20 [EHCI])
Subsystem: ASUSTeK Computer Inc. K8N4-E Mainboard
Flags: bus master, 66MHz, fast devsel, latency 0, IRQ 22
Memory at d4005000 (32-bit, non-p
[BUG?] ata disk running maximum at DMA33 with 2.6.20 and new pata driver, NV CK804 ide controller.
Hi, since upgrading to kernel 2.6.20 my pata disk, using new pata driver, is initialized maximum in DMA33 mode (and obviously performances drop consequently), as you can see from: pata_amd :00:06.0: version 0.2.7 PCI: Setting latency timer of device :00:06.0 to 64 ata5: PATA max UDMA/133 cmd 0x1F0 ctl 0x3F6 bmdma 0xF000 irq 14 ata6: PATA max UDMA/133 cmd 0x170 ctl 0x376 bmdma 0xF008 irq 15 scsi4 : pata_amd ata5.00: ATA-7, max UDMA/100, 156368016 sectors: LBA48 ata5.00: ata5: dev 0 multi count 1 ata5.00: configured for UDMA/33 scsi5 : pata_amd ata6.00: ATAPI, max UDMA/33 ata6.00: configured for UDMA/33 scsi 4:0:0:0: Direct-Access ATA SAMSUNG SP0822N WA10 PQ: 0 ANSI: 5 SCSI device sdc: 156368016 512-byte hdwr sectors (80060 MB) sdc: Write Protect is off sdc: Mode Sense: 00 3a 00 00 SCSI device sdc: write cache: enabled, read cache: enabled, doesn't support DPO or FUA SCSI device sdc: 156368016 512-byte hdwr sectors (80060 MB) sdc: Write Protect is off sdc: Mode Sense: 00 3a 00 00 SCSI device sdc: write cache: enabled, read cache: enabled, doesn't support DPO or FUA sdc: sdc1 sdc2 sdc3 sd 4:0:0:0: Attached scsi disk sdc while with kernel 2.6.19.X it was initialized correctly in DMA100 mode: pata_amd :00:06.0: version 0.2.4 PCI: Setting latency timer of device :00:06.0 to 64 ata5: PATA max UDMA/133 cmd 0x1F0 ctl 0x3F6 bmdma 0xF000 irq 14 ata6: PATA max UDMA/133 cmd 0x170 ctl 0x376 bmdma 0xF008 irq 15 scsi4 : pata_amd ata5.00: ATA-7, max UDMA/100, 156368016 sectors: LBA48 ata5.00: ata5: dev 0 multi count 1 ata5.00: configured for UDMA/100 scsi5 : pata_amd ata6.00: ATAPI, max UDMA/33 ata6.00: configured for UDMA/33 scsi 4:0:0:0: Direct-Access ATA SAMSUNG SP0822N WA10 PQ: 0 ANSI: 5 SCSI device sdc: 156368016 512-byte hdwr sectors (80060 MB) sdc: Write Protect is off sdc: Mode Sense: 00 3a 00 00 SCSI device sdc: drive cache: write back SCSI device sdc: 156368016 512-byte hdwr sectors (80060 MB) sdc: Write Protect is off sdc: Mode Sense: 00 3a 00 00 SCSI device sdc: drive cache: write back sdc: sdc1 sdc2 sdc3 sd 4:0:0:0: Attached scsi disk sdc I have other 2 sata disks on this system, and I have no problems with them. I Wonder if this is due to some controller/disk problem triggered just by 2.6.20 kernel (I saw there are a lot of changes into eh code), while 2.6.19.X and previous sees everything OK. Also forf the sata disks, in fact, I see this "doesn't support DPO or FUA" warning, but I have to admit I do not know which features it is referred to. This system is an Athlon64 X2 3800+ with an nvidia2 IDE controller here is the lspci -v 00:00.0 Memory controller: nVidia Corporation CK804 Memory Controller (rev a3) Subsystem: ASUSTeK Computer Inc. Unknown device 815a Flags: bus master, 66MHz, fast devsel, latency 0 Capabilities: [44] HyperTransport: Slave or Primary Interface Capabilities: [e0] HyperTransport: MSI Mapping 00:01.0 ISA bridge: nVidia Corporation CK804 ISA Bridge (rev a3) Subsystem: ASUSTeK Computer Inc. K8N4-E Mainboard Flags: bus master, 66MHz, fast devsel, latency 0 00:01.1 SMBus: nVidia Corporation CK804 SMBus (rev a2) Subsystem: ASUSTeK Computer Inc. K8N4-E Mainboard Flags: 66MHz, fast devsel, IRQ 10 I/O ports at e400 [size=32] I/O ports at 4c00 [size=64] I/O ports at 4c40 [size=64] Capabilities: [44] Power Management version 2 00:02.0 USB Controller: nVidia Corporation CK804 USB Controller (rev a2) (prog-if 10 [OHCI]) Subsystem: ASUSTeK Computer Inc. K8N4-E Mainboard Flags: bus master, 66MHz, fast devsel, latency 0, IRQ 20 Memory at d4004000 (32-bit, non-prefetchable) [size=4K] Capabilities: [44] Power Management version 2 00:02.1 USB Controller: nVidia Corporation CK804 USB Controller (rev a3) (prog-if 20 [EHCI]) Subsystem: ASUSTeK Computer Inc. K8N4-E Mainboard Flags: bus master, 66MHz, fast devsel, latency 0, IRQ 22 Memory at d4005000 (32-bit, non-prefetchable) [size=256] Capabilities: [44] Debug port Capabilities: [80] Power Management version 2 00:04.0 Multimedia audio controller: nVidia Corporation CK804 AC'97 Audio Controller (rev a2) Subsystem: ASUSTeK Computer Inc. Unknown device 8166 Flags: bus master, 66MHz, fast devsel, latency 0, IRQ 23 I/O ports at dc00 [size=256] I/O ports at e000 [size=256] Memory at d4003000 (32-bit, non-prefetchable) [size=4K] Capabilities: [44] Power Management version 2 00:06.0 IDE interface: nVidia Corporation CK804 IDE (rev f2) (prog-if 8a [Master SecP PriP]) Subsystem: Unknown device f043:815a Flags: bus master, 66MHz, fast devsel, latency 0 [virtual] Memory at 01f0 (32-bit, non-prefetchable) [disabled] [size=8] [virtual] Memory at 03f0 (type 3, non-prefetchable) [disabled] [size=1] [virtual] Memory at 0170 (
[BUG?] ata disk running maximum at DMA33 with 2.6.20 and new pata driver, NV CK804 ide controller.
Hi, since upgrading to kernel 2.6.20 my pata disk, using new pata driver, is initialized maximum in DMA33 mode, as you can see from: pata_amd :00:06.0: version 0.2.7 PCI: Setting latency timer of device :00:06.0 to 64 ata5: PATA max UDMA/133 cmd 0x1F0 ctl 0x3F6 bmdma 0xF000 irq 14 ata6: PATA max UDMA/133 cmd 0x170 ctl 0x376 bmdma 0xF008 irq 15 scsi4 : pata_amd ata5.00: ATA-7, max UDMA/100, 156368016 sectors: LBA48 ata5.00: ata5: dev 0 multi count 1 ata5.00: configured for UDMA/33 scsi5 : pata_amd ata6.00: ATAPI, max UDMA/33 ata6.00: configured for UDMA/33 scsi 4:0:0:0: Direct-Access ATA SAMSUNG SP0822N WA10 PQ: 0 ANSI: 5 SCSI device sdc: 156368016 512-byte hdwr sectors (80060 MB) sdc: Write Protect is off sdc: Mode Sense: 00 3a 00 00 SCSI device sdc: write cache: enabled, read cache: enabled, doesn't support DPO or FUA SCSI device sdc: 156368016 512-byte hdwr sectors (80060 MB) sdc: Write Protect is off sdc: Mode Sense: 00 3a 00 00 SCSI device sdc: write cache: enabled, read cache: enabled, doesn't support DPO or FUA sdc: sdc1 sdc2 sdc3 sd 4:0:0:0: Attached scsi disk sdc while with kernel 2.6.19.X it was initialized correctly in DMA100 mode: pata_amd :00:06.0: version 0.2.4 PCI: Setting latency timer of device :00:06.0 to 64 ata5: PATA max UDMA/133 cmd 0x1F0 ctl 0x3F6 bmdma 0xF000 irq 14 ata6: PATA max UDMA/133 cmd 0x170 ctl 0x376 bmdma 0xF008 irq 15 scsi4 : pata_amd ata5.00: ATA-7, max UDMA/100, 156368016 sectors: LBA48 ata5.00: ata5: dev 0 multi count 1 ata5.00: configured for UDMA/100 scsi5 : pata_amd ata6.00: ATAPI, max UDMA/33 ata6.00: configured for UDMA/33 scsi 4:0:0:0: Direct-Access ATA SAMSUNG SP0822N WA10 PQ: 0 ANSI: 5 SCSI device sdc: 156368016 512-byte hdwr sectors (80060 MB) sdc: Write Protect is off sdc: Mode Sense: 00 3a 00 00 SCSI device sdc: drive cache: write back SCSI device sdc: 156368016 512-byte hdwr sectors (80060 MB) sdc: Write Protect is off sdc: Mode Sense: 00 3a 00 00 SCSI device sdc: drive cache: write back sdc: sdc1 sdc2 sdc3 sd 4:0:0:0: Attached scsi disk sdc I have other 2 sata disks on this system, and I have no problems with them. I Wonder if this is due to some controller/disk problem triggered just by 2.6.20 kernel (I saw there are a lot of changes into eh code), while 2.6.19.X and previous sees everything OK. This system is an Athlon64 X2 3800+ with an nvidia2 IDE controller here is the lspci -v 00:00.0 Memory controller: nVidia Corporation CK804 Memory Controller (rev a3) Subsystem: ASUSTeK Computer Inc. Unknown device 815a Flags: bus master, 66MHz, fast devsel, latency 0 Capabilities: [44] HyperTransport: Slave or Primary Interface Capabilities: [e0] HyperTransport: MSI Mapping 00:01.0 ISA bridge: nVidia Corporation CK804 ISA Bridge (rev a3) Subsystem: ASUSTeK Computer Inc. K8N4-E Mainboard Flags: bus master, 66MHz, fast devsel, latency 0 00:01.1 SMBus: nVidia Corporation CK804 SMBus (rev a2) Subsystem: ASUSTeK Computer Inc. K8N4-E Mainboard Flags: 66MHz, fast devsel, IRQ 10 I/O ports at e400 [size=32] I/O ports at 4c00 [size=64] I/O ports at 4c40 [size=64] Capabilities: [44] Power Management version 2 00:02.0 USB Controller: nVidia Corporation CK804 USB Controller (rev a2) (prog-if 10 [OHCI]) Subsystem: ASUSTeK Computer Inc. K8N4-E Mainboard Flags: bus master, 66MHz, fast devsel, latency 0, IRQ 20 Memory at d4004000 (32-bit, non-prefetchable) [size=4K] Capabilities: [44] Power Management version 2 00:02.1 USB Controller: nVidia Corporation CK804 USB Controller (rev a3) (prog-if 20 [EHCI]) Subsystem: ASUSTeK Computer Inc. K8N4-E Mainboard Flags: bus master, 66MHz, fast devsel, latency 0, IRQ 22 Memory at d4005000 (32-bit, non-prefetchable) [size=256] Capabilities: [44] Debug port Capabilities: [80] Power Management version 2 00:04.0 Multimedia audio controller: nVidia Corporation CK804 AC'97 Audio Controller (rev a2) Subsystem: ASUSTeK Computer Inc. Unknown device 8166 Flags: bus master, 66MHz, fast devsel, latency 0, IRQ 23 I/O ports at dc00 [size=256] I/O ports at e000 [size=256] Memory at d4003000 (32-bit, non-prefetchable) [size=4K] Capabilities: [44] Power Management version 2 00:06.0 IDE interface: nVidia Corporation CK804 IDE (rev f2) (prog-if 8a [Master SecP PriP]) Subsystem: Unknown device f043:815a Flags: bus master, 66MHz, fast devsel, latency 0 [virtual] Memory at 01f0 (32-bit, non-prefetchable) [disabled] [size=8] [virtual] Memory at 03f0 (type 3, non-prefetchable) [disabled] [size=1] [virtual] Memory at 0170 (32-bit, non-prefetchable) [disabled] [size=8] [virtual] Memory at 0370 (type 3, non-prefetchable) [disabled] [size=1] I/O ports at f000 [size=16] Capabilities: [44] Power Managemen
