Martin G. McCormick <martin at server1.shellworld.net> wrote: > What you get when the system boots precludes much > control other than through an X console. You hear the speakup > kernel starting up and complaining about many things such as the > state of the alsa configuration. Apparently, this is okay as > sound and sound effects do run. Eventually, X starts on its own > and you loose the ability to stop speakup. > > Speakup continues to complain about many things and then > describes everything starting up until about where bluetooth > starts at which point it stops talking. > > What should happen after that based on a few tantalizing > events is that you get the orca login window but nothing has > worked after that. My suggestion was to turn off gdm so that X doesn't start during the boot process. You'll need to modify the init scripts with, for example, chkconfig gdm3 off and if it's already started, service gdm3 stop
