PIIX, 82371 DMA probs (again?)
Howdy hackers, i'm stuck ...
Searching debian.org, kernel.org, etc. i can not find a solution.
search.debian.org gives just some BUG closed msgs and some people
giving up on the issue ...
Now i already downloaded the intel 82371FB docs, being prepared to
initialize the PCISet myself. But as i've never dealt with (modern) PC
hardware before, i'm looking forward to some hard times.
That doesn't bother me too much, but the machine in question is the server
of a little network with, err, little to no hardware for doing backups
as they should ... and after all it's the IDE controller we're gonna
play with ...
So, i would very much appreciate any help or pointers of yours ...
Thank You!
Computer is IBM 350-P75 with newest BIOS (1996)
lspci
00:00.0 Host bridge: Intel Corporation 430FX - 82437FX TSC [Triton I] (rev 02)
00:07.0 ISA bridge: Intel Corporation 82371FB PIIX ISA [Triton I] (rev 02)
CONFIG_PCI=y, CONFIG_PCI_GOANY=y CONFIG_PCI_BIOS=y, CONFIG_PCI_DIRECT=y
CONFIG_PCI_QUIRKS=y, CONFIG_PCI_OPTIMIZE=y
# CONFIG_PCI_OLD_PROC is not set
kernel-2.2.17 with ide-patch both from potato-proposed-updates
CONFIG_BLK_DEV_IDEPCI=y, CONFIG_BLK_DEV_IDEDMA=y, CONFIG_IDEDMA_AUTO=y
CONFIG_BLK_DEV_PIIX=y, CONFIG_PIIX_TUNING=y
now dmesg can tell better than i:
Linux version 2.2.17 (root@eisbox) (gcc version 2.95.2 20000220 (Debian GNU/Linu
x)) #11 Sat Nov 18 05:09:06 CET 2000
Detected 74540 kHz processor.
ide_setup: hdd=cdrom
ide_setup: ide0=dma
ide_setup: ide1=dma
Console: colour VGA+ 80x34
Calibrating delay loop... 148.68 BogoMIPS
Memory: 63580k/65536k available (668k kernel code, 412k reserved, 836k data, 40k
init)
...
CPU: Intel Pentium 75 - 200 stepping 05
Checking 386/387 coupling... OK, FPU using exception 16 error reporting.
Checking 'hlt' instruction... OK.
Intel Pentium with F0 0F bug - workaround enabled.
PCI: PCI BIOS revision 2.10 entry at 0xfda51
PCI: Using configuration type 1
PCI: Probing PCI hardware
...
apm: BIOS version 1.1 Flags 0x03 (Driver version 1.13)
Real Time Clock Driver v1.09
Uniform Multi-Platform E-IDE driver Revision: 6.30
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
PIIX: IDE controller on PCI bus 00 dev 38
PIIX: chipset revision 2
PIIX: not 100% native mode: will probe irqs later
hda: QUANTUM LPS540A, ATA DISK drive
hdb: QUANTUM FIREBALL EX5.1A, ATA DISK drive
hdc: QUANTUM FIREBALL1280A, ATA DISK drive
hdd: 4X4X32, ATAPI CDROM drive
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
ide1 at 0x170-0x177,0x376 on irq 15
hda: QUANTUM LPS540A, 516MB w/96kB Cache, CHS=560/32/59
hdb: QUANTUM FIREBALL EX5.1A, 4892MB w/418kB Cache, CHS=662/240/63
hdc: QUANTUM FIREBALL1280A, 1222MB w/83kB Cache, CHS=2484/16/63
Clearly, the hdx messages are missing the DMA at the end! And yes, the
EX5.1A even claims UDMA, all do mwdma2 (for instance on a PIIX4).
(What about the PCI Bus speed? Driver docs say for P75 25MHz would be
correct? The ibm hw manual says nothing about any particular board.)
Looking into the kernel/driver/block/ide-* sources indicate that the
test (ide-pci.c::ide_setup_pci_device::565 --- ide-patched version!)
if (e->reg && (pci_read_config_byte(dev, e->reg, &tmp) || (tmp &
e->mask) != e->val)) /*continue*/; /* port not enabled */
is met. So, the driver meets the condition after the loop:
if (!at_least_one_hwif_enabled)
printk("%s: neither IDE port enabled (BIOS)\n", d->name);
This can not be seen in the above dmesg, because this is already from a
version, where i tried to initialize the PIIXa set with the PIIX4
routines. The only outcome is another msg:
PIIX: IO baseregs (BIOS) are reported as MEM, report to <andre@suse.com>.
ok, it was just a try ...
As i said above, after finishing the mail (and compiling qt - what the
heck are libgl-dev and libmng-dev it build-depends on?) i'll start
reading the manuals, but i'ld rather prefer joining some
linux-midi-audio project than to re-invent a solution for a long closed
BUG.
Though this was a long post, that i hope do not annoy too many of you,
i'm still in hope that so. of you might be able to help me out ...
greetings, martin
Reply to: