> On 12 Jun 1999, Paul Flinders wrote:
>
> > I get exacly the same thing in 2.3.6 on a machine with an asus P55T2P4
> > M/B except that it isn't "harmless" as linux won't boot.
> >
> > > Since you have a good bios/mainboard combination, skip the inclusion of
> > > the "piix.c" chipset code.
> >
> > Fortunately this works for me.
>
> Okay this is good to know............but you have a 430FX/HX PIIX3
> adapter correct?
Yes, the P55T2P4 is a 430HX.
If it's any use to you I've copied down the boot messages that I get
with CONFIG_BLK_DEV_PIIX=y in 2.3.6
Configuring the kernel without CONFIG_BLK_DEV_PIIX is fine as are
kernels <= 2.3.3 (I haven't used 2.3.[45]). It takes a power cycle
before the TM3200A(hdd) is even recognised by the BIOS after trying to
boot.
Any minor errors are the result of copying this by hand.
Uniform Multi-Platform E-IDE driver Revision: 6.19
PIIX3: IDE controller on PCI bus 00 dev 39
PIIX3: not 100% native mode: will probe irqs later
ide0: BM-DMA at 0xe800-0xe807, BIOS settings: hda:DMA, hdb:DMA
ide1: BM-DMA at 0xe808-0xe80f, BIOS settings: hdc:DMA, hdd:DMA
hda: QUANTUM FIREBALL ST6.4A, ATA DISK drive
hdb: LS-120 VER4 06 UHD Floppy, ATAPI FLOPPY drive
hdc: Maxtor 90680D4, ATA DISK drive
hdd: QUANTUM FIREBALL_TM3200A, ATA DISK drive
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
ide1 at 0x170-0x177,0x376 on irq 15
hda: set_geometry_intr: status=0x51 { DriveReady SeekComplete Error }
hda: set_geometry_intr: error=0x04 { DriveStatusError }
hda: QUANTUM FIREBALL ST6.4A, 6149MB w/81kB Cache, CHS=784/255/63, (U)DMA
hdc: irq timeout status = 0xd0 {Busy}
hdc: Maxtor 90680D4, 6485MB w/256kB Cache, CHS=13176/16/63, (U)DMA
hdd: status timeout: status = 0xd0 {Busy}
hdd: drive not ready for command
hdd: QUANTUM FIREBALL_TM3200A, 3067MB w/76kB Cache, CHS=6232/16/63, DMA
Partition check:
hda: hda1 hda2 hda3 hda4 < hda5 >
hdc: hdc: status timeout: status = 0xd0 {Busy}
hdc: DMA disable
hdd: DMA disable
hdc: drive not ready for command
ide1: reset timed-out, status = 0x80
hdc: status timeout: status = 0x80 {Busy}
hdc: drive not ready for command
ide1: reset timed-out, status = 0x80
hdc: status timeout: status = 0x80 {Busy}
end_request: I/O error, dev 16:00(hdc), sector 0
hdc: drive not ready for command
unable to read partition table
hdd: hdd: status timeout: status = 0xd0 {Busy}
hdd: DMA disable
hdd: DMA disable
hdd: drive not ready for command
ide1: reset timed-out, status = 0x80
hdd: status timeout: status = 0x80 {Busy}
hdd: drive not ready for command
ide1: reset timed-out, status = 0x80
hdd: status timeout: status = 0x80 {Busy}
end_request: I/O error, dev 16:40(hdd), sector 0
hdd: drive not ready for command
unable to read partition table
attempt to access beyond end of device
16:41: rw=0, want=2, limit=0
EXT2-fs: unable to read superblock
16:41: rw=0, want=1, limit=0
FAT bread failed
attempt to access beyond end of device
16:41: rw=0, want=1, limit=0
FAT bread failed
Kernel panic: VFS: Unable to mount root FS on 16:41
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/