[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

install report: Debian-Installer fails on old IBM PC

Package: installation-reports

Of course, I do realize that this isn't exactly current hardware, but I
don't see why it shouldn't work anyway.

    boot floppy daily build of March 18th, from

    boot from floppy, install packages from network

    IBM Personal Computer 750 (PCI/ISA, not MicroChannel)
    chipset: INTEL PCIset SB82437JX + SB82371FB

    Pentium-1 133MHz


Root Device:
    Quantum 540MB IDE hard disk

Partition table:
    Disk /dev/hda: 541 MB, 541384704 bytes
    255 heads, 63 sectors/track, 65 cylinders
    Units = cylinders of 16065 * 512 = 8225280 bytes

       Device Boot      Start         End      Blocks   Id  System
    /dev/hda1   *           1          65      522081   83  Linux

    note: swap space is on separate drive, on secondary IDE bus

PCI devices:
    0000:00:00.0 Host bridge: Intel Corp. 82437FX [Triton FX] (rev 01)
    0000:00:01.0 ISA bridge: Intel Corp. 82371FB PIIX ISA [Triton I] (rev 02)
    0000:00:01.1 IDE interface: Intel Corp. 82371FB PIIX IDE [Triton I] (rev 02)
    0000:00:06.0 Ethernet controller: 3Com Corporation 3c905 100BaseTX [Boomerang]
    0000:00:08.0 VGA compatible controller: S3 Inc. 86c764/765 [Trio32/64/64V+] (rev 53)

Problems: reboot from hard disk fails

The installation was carried out with the current daily-build floppy
disks (boot, root, drivers), with everything else obtained through the
network. Everything proceeds smoothly until the reboot from hard disk.
GRUB loads the kernel and initrd image, apparently successfully. The
kernel runs through the bootup sequence without issue until it tries to
"Partition check" the hard drive. After making some comment about using
the PIIX module, and correctly recognizing the Quantum hard drive, it
then fails with a bunch of DMA timeout errors.

Since neither the install floppies, nor GRUB, nor "tomsrtbt" have any
problem at all with this hardware, I infer that it's a software problem.
Probably something about the right module not being loaded, or loaded in
the wrong order, or a conflict with another module. The installer chose
the "kernel-image-2.4.27-2-586tsc_2.4.27-8_i386.deb" kernel package; I
also tried the "kernel-image-2.4.27-2-386_2.4.27-8_i386.deb" kernel
package, but the result was the same.

Attached are the files "/linuxrc.conf", "/script", and "/loadmodules"
extracted from the initrd image "/boot/initrd.img-2.4.27-2-586tsc" found
on the hard disk after the failed reboot. The initrd package is

Any suggestions?

-- Ian Bruce
unload_unused_ide 'yes' pdc202xx_new adma100 aec62xx alim15x3 amd74xx atiixp cmd640 cmd64x cs5530 cy82c693 generic hpt34x hpt366 ns87415 opti621 pdc202xx_old piix rz1000 sc1200 serverworks siimage sis5513 slc90e66 triflex trm290 via82cxxx
modprobe -k  vesafb > /dev/null 2>&1
modprobe -k  fbcon 2> /dev/null
modprobe -k  unix 2> /dev/null
modprobe -k  pdc202xx_new > /dev/null 2>&1
modprobe -k  adma100 > /dev/null 2>&1
modprobe -k  aec62xx > /dev/null 2>&1
modprobe -k  alim15x3 > /dev/null 2>&1
modprobe -k  amd74xx > /dev/null 2>&1
modprobe -k  atiixp > /dev/null 2>&1
modprobe -k  cmd640 > /dev/null 2>&1
modprobe -k  cmd64x > /dev/null 2>&1
modprobe -k  cs5530 > /dev/null 2>&1
modprobe -k  cy82c693 > /dev/null 2>&1
modprobe -k  generic > /dev/null 2>&1
modprobe -k  hpt34x > /dev/null 2>&1
modprobe -k  hpt366 > /dev/null 2>&1
modprobe -k  ns87415 > /dev/null 2>&1
modprobe -k  opti621 > /dev/null 2>&1
modprobe -k  pdc202xx_old > /dev/null 2>&1
modprobe -k  piix > /dev/null 2>&1
modprobe -k  rz1000 > /dev/null 2>&1
modprobe -k  sc1200 > /dev/null 2>&1
modprobe -k  serverworks > /dev/null 2>&1
modprobe -k  siimage > /dev/null 2>&1
modprobe -k  sis5513 > /dev/null 2>&1
modprobe -k  slc90e66 > /dev/null 2>&1
modprobe -k  triflex > /dev/null 2>&1
modprobe -k  trm290 > /dev/null 2>&1
modprobe -k  via82cxxx > /dev/null 2>&1
modprobe -k  ide-detect
modprobe -k  ide-disk

Reply to: