Doing a textinstall on my laptop (chaplett 5032 / p133) seems to skip the
After creating the bootdisk the HD rattles a bit and then the setup is
This is very likely related to Xconfigurator crashing also when run after
the install as root.
I'll add a comment with the bugzilla id of that bug once entered.
Also kudzu has serious trouble on this machine see bug 14455 and bug 14456
Also see Xconfigurator segfaults: bug 14458
The Xconfigurator segfaults bug (bug 14458) has been fixed, by adding the option
-noddcprobe, if the installer now would be updated to pass this to Xconfigurator
when it is run with the noprobe option, then I concider this fixed.
Is this fixed in beta 5?
I'm currently checking, the laptop only does nfs install, and this takes about 3
hours so I'll lett you know then.
Nope, I've started the installer with:
On the syslinux prompt, I guess this still work or has this option been removed
from the later beta's?
Anyways with this option the Xconfiguration is still skipped.
This defect is considered MUST-FIX for Winston Release-Candidate #1
This cannot be fixed at this time - the installer should allow you to skip X
configuration at install time and
then you can run Xconfigurator with the special command line option once your
system is installed.
First of all, the screen goes completly black, so this is a cannot complete
install bug, not everyone has a spare monitor handy to plug in, and other
systems are bound to be bitten by this too.
The help screens on the bootdisks clearly state that you can use expert mode to
install on buggy hardware, and that in this case no autoprobing will be done.
I would expect noprobe todo a normal install, without any probing as in expert
mode. That is what I plea for, and what afaik 6.1 used todo.
But letts say I use expert mode, then I presume kudzu won't do dcc probing and
Xconfigurator will be run with --nodccprobe? If not I concider that a bug, and I
strongly urge for a noprobe option doing the noprobing effect of expert without
all the other questions I don't want to answer and have no need for. If this is
not feasible for this release, then fix this in expert mode, and defer the
I believe we have corrected the display going blank problem in your other bug
report, so this one should be
fixed as well.