/etc/init.d/kbd
add this line in the very beginning of the file
KBD_TTY="tty0 tty2 tty3 tty4 tty5 tty6 tty7" |
after modifications
#! /bin/sh # Copyright (c) 1995-2001 SuSE GmbH Nuernberg, Germany. # # Author: Burchard Steinbild <bs@suse.de> # Werner Fink <werner@suse.de> # # /etc/init.d/kbd # # and symbolic its link # # /sbin/rckbd # ### BEGIN INIT INFO # Provides: kbd # Required-Start: $remote_fs # Required-Stop: # X-SuSE-Should-Start: fbset serial # X-SuSE-Should-Stop: # Default-Start: 1 2 3 5 S # Default-Stop: # Description: Keyboard settings (don't disable!) ### END INIT INFO . /etc/rc.status . /etc/sysconfig/console . /etc/sysconfig/keyboard MACHINE=`/bin/uname -m 2> /dev/null` if [ "$MACHINE" = "sparc" -o "$MACHINE" = "sparc64" ]; then # Test if we have a serial console. (test -c /dev/tty1 && > /dev/tty1 ) > /dev/null 2>&1 || exit 0 fi # The variable NON_SUSE_KERNEL determines whether we need to chvt # to a console before some console settings apply. # We have no magic to find out about this (at boot time), so we # leave it to the user to read this comment and put NON_SUSE_KERNEL="yes" # into /etc/sysconfig/console KBDBASE="/usr/share/kbd" KBD_TTY="tty0 tty2 tty3 tty4 tty5 tty6 tty7" KTABLE=${KEYTABLE%.map*} KTABLE=${KTABLE##*/} # # first search the wanted keytable. # if [ $MACHINE = ppc -o $MACHINE = ppc64 ]; then test -f /proc/cpuinfo || mount -n -t proc proc /proc 2>/dev/null while read line; do ...... ...... |
replacing sysfont with consolechars
< needs to be written >
actually might not be needed,
modifying /etc/init.d/kbd solves the problem for me
hwscan causes problems some time
recommended disable, if you have to install new hardware and want to use it
boot with standard kernel and start it manually