Installation type: expert install from hd.img
********************************************************************************
System: Gigabyte GA-6BXE ATX motherboard
        Intel 440BX chipset
        PIIX4 onboard IDE controller: no drives - disabled in BIOS
        Intel PII-400
        384MB 100 MHz SDRAM
        PDC20267 Promise UDMA100 PCI IDE controller: 4 Maxtor drives
        PDC20262 Promise UDMA66  PCI IDE controller: no drives yet
        Adaptec AHA-2940AU with 1 IBM drive, DVD-ROM, writer, Umax 2400S scanner
        Matrox G400 32MB
        Microsoft IntelliMouse Optical - PS/2 connection (USB possible)
        CTX-1792UA 17-inch monitor
        SB AWE64 (isapnp)
        HP-Colorado Travan T1000 floppy tape drive
        USR 56K external Message Modem on ttyS01
        3 1/2 inch floppy drive
        HP DeskJet 720C
********************************************************************************
1.  Installation trouble-free, except:
        Mouse detection still difficult to capture mouse in dialog.
        Have to select network config twice - LAN and modem (after completing 
        one the damn thing *still* thinks you've finished - how about a
        "done" button?).

2.  Throughout install, drives recognised as hd{e,f,g,h}.  hde goes up to
    hde21.  However, on first boot, kernel panic!  Can't find hdf5 to boot
    from.  Of course, with this accursed "CONFIG_BLK_DEV_OFFBOARD=y"
    kernel config, the drives are now hd{a,b,c,d}.  OK, I passed boot
    param "root=/dev/hdb5" to get in, but then I had to do file system
    repair to correct fstab hd values.  First I had to remount / rw.  Then
    after `vim /etc/fstab`, exit and reboot, I had to do file system
    repair *again* to do `mknod /dev/hda{17-21} b 3 {17-21}`.  The
    installer had already created /dev/hde{17-21}, which are now not
    needed.

    This should not be necessary.  I don't mind your crackpot idea of
    using the "CONFIG_BLK_DEV_OFFBOARD=y" kernel config, as long as you
    clean up afterwards.

3.  For the first time I see anti-aliased fonts - but they're *horrible* -
    I'll have to do some work on those.  That terrible A D MONO font (all
    caps) must have been at the top of the list somewhere, because until I 
    rebooted again, that was the KDE task bar font! - imagine!

Overall, there is pleasing evidence of a lot of good work done, but, as 
with 7.2, it is spoilt by the lack of attention to "first impressions".  I 
think the freeze/fix/release period should be doubled in future to try to 
avoid the half-finished appearance of what gets to market.
-- 
              ----------------------------------------------------
                 Linux Mandrake release 7.2 (Odyssey) for i586
                                    KDE 2.1
              Linux 2.2.17-27mdkWin4Lin, Uptime 4 hours 41 minutes
              ----------------------------------------------------

Reply via email to