A week ago i wrote to this mail list about my problems in
installing M-6.0.
In a nut shell:
1) Cd burned using iso image downloaded from Mdk's mirrors
don't boots on my system.
2) If I boot from a floppy (on which I copied boot.img),
I'm able to boot but, when I try to install from CD-ROM
the CD spins without results, the keyboard freezes and
I can only to reset the PC.
If i check messages using alt-F3 (before starting
installation), i found:
=======================================================
.........
<4> hdb: ATAPI 40x CD-ROM drive, 120 kB Cache
<6> UNIFORM CDROM driver Revision: 2.54
..... hda's partitions, floppy, are mounted.........
<4> VFS: Mounted root (ext2 filesystem)
<6> VFS: Disk Change detected on device ide0(3,64)
<4> drive-cmd: status=0x51 {Drive Ready SeekCompleteError}
<4> hdb: drive-cmd: error=0x04
<4> hdb: drive-cmd: status=0x51 {Drive Ready SeekCompleteError}
<4> hdb: drive-cmd: error=0x04
<6> install uses obsolete /proc/pci interface
=============================================================
I tried some different way to resolve my problem:
- following suggestions in mail list,
- burning new CDs downloaded by different mirrors
and/or being more careful in procedure.
- burning a my own image built using mkisofs
The only result was that my self-made CD boots
but don't install.
Eventually, i tried using an old (Mdk-5.2) boot.img
to boot and a M-6.0 Cd to install.
It works!
Now i think the M-6.0 boot.img have a bug or, at least,
is not compatible with my system.
As remark, Mdk-5.3 and RH-6.0 installed without problems.
My system was:
- Intel Pentium 233 mmx
- quantum fireball Hb
- Atapi 40x CD-ROM
In this days i added a new Samsung HD
(hda=Quantum, hdb=Samsung and hdc=CD)
the only difference is a new message of this kind:
hdb: irq lost
The message don't changes if i move the new HD to hdc
and the cdrom to hdb: the problem is allways on
hdb's irq.
Also with the new configuration i have no problems
in installing Mdk-5.3 or RH-6.0 or working with
such distributions.
bye, Andrea Celli
