I'm now running RC2 on my five year old Toshiba Satellite 1805-S204, 1GHz Celeron processor, 512MB RAM, 20GB HDD. There are still two very significant bugs in the installer that I've run across:
1. Installer: Grub is still a mess. Every Linux partition not assigned a mount point gets an entry whether or not an OS is installed there. Worse, if there is an OS there (my system currently has three installed distros) it gets them wrong too and doesn't correctly detect the initrd file. Even Vector Linux isn't properly labeled! We'd be better off with just lilo than this result for grub, IMHO. Here is the relevant portion of the /boot/grub/menu.lst file generated by the installer:
# Linux bootable partition config begins
title Linux on (/dev/hda1)
root (hd0,0)
kernel /boot/vmlinuz root=/dev/hda1 ro vga=791 splash=silent
initrd /boot/initrd
# Linux bootable partition config ends
# Linux bootable partition config begins
title Linux on (/dev/hda5)
root (hd0,4)
kernel /boot/vmlinuz root=/dev/hda5 ro vga=791 splash=silent
initrd /boot/initrd
# Linux bootable partition config ends
# Linux bootable partition config begins
title Linux on (/dev/hda6)
root (hd0,5)
kernel /boot/vmlinuz root=/dev/hda6 ro vga=791 splash=silent
initrd /boot/initrd
# Linux bootable partition config ends
# Linux bootable partition config begins
title Linux on (/dev/hda7)
root (hd0,6)
kernel /boot/vmlinuz root=/dev/hda7 ro vga=791 splash=silent
initrd /boot/initrd
# Linux bootable partition config ends
Here is what my working menu.lst looks like:
title WolvixHunter-1.1.0
root (hd0,4)
kernel /boot/vmlinuz root=/dev/hda5 ro vga=791 splash=silent
initrd /boot/initrd.splash
savedefault
boot
title AliXe 0.11b
root (hd0,5)
kernel /boot/vmlinuz root=/dev/hda6 ro vga=791
boot
title Vector Linux 5.9
root (hd0,0)
kernel /boot/vmlinuz root=/dev/hda1 ro vga=791 splash=silent
initrd /boot/initrd
boot
I don't expect grub to correctly label other distros besides VL. I do expect the installer to recognize where a valid distro is and isn't installed and to create a proper menu entry. Most other distros do this just fine.
2. X Configuration: Still wrong with my Trident CyberBlade XP chipset on this laptop. I get a mini window with lots of black space all around. Slackware 12 does the same thing, BTW, but some other Slackware based distros (Zenwalk, AliXe, Wolvix) get it right. AliXe uses Zenwalk's vconf utility before starting X. If we could integrate vconf into the installer that would solve the problem. I don't know how Wolvix does it but I could do some digging.
Relevant sections of the xorg.conf file generated by VL:
Section "Monitor"
DisplaySize 269 201 # 96 DPI @ 1024x768
Identifier "Monitor0"
VendorName "Monitor Vendor"
ModelName "Monitor Model"
HorizSync 37-48
VertRefresh 72-75
EndSection
Identifier "Card0"
Driver "trident"
VendorName "Trident Microsystems"
BoardName "CyberBlade XPAi1"
BusID "PCI:1:0:0"
EndSection
A correct xorg.conf file for my system:
Section "Monitor"
Identifier "Monitor1"
VendorName "TOS"
ModelName ""
HorizSync 31.5 - 50.0
VertRefresh 40-90
Option "UseEdidFreqs" "1"
Option "DPMS"
EndSection
# **********************************************************************
# Graphics device section
# **********************************************************************
# Any number of graphics device sections may be present
Section "Device"
Identifier "Videocard1"
VendorName "Trident Microsystems"
BoardName "CyberBlade XPAi1"
Driver "trident"
BusID "PCI:1:0:0"
EndSection
Note that the error is in the monitor section, not the device section.
3. Not a bug, but... the ugly prune has got to go!
The good news: performance is excellent and everything I've tried so far has worked. I need to do more testing, of course.