Setting up general console font ... / framebuffer

[hnzi]

hi@forum,

ich hab schon ziemlich viele postings ueber dieses thema gelesen, aber mein problem wurde darin noch nicht behandelt, oder ich habe es noch nicht gefunden.

beim booten habe ich einen framebuffer aktiviert ( riva tnt mit vesa ), der tut auch, bis ich von stable auf testing gewechselt habe. jetzt sieht mein booting so aus, dass der framebuffer bis zum setzen der konsolenschrift aktiviert ist, und dann wieder in den normalen vga-modus (80x25 ?) zurueckspringt. schriften sind unveraendert, ich kann normal weiter arbeiten.

als kernel hab ich einen manuell compilierten 2.4.20, mit vesa-framebuffer, der riva-framebuffer ging damals (zur zeit des kernelcompilierens) nicht.

ich hab keine ahnung, wo ich suchen soll, hat jemand tipps fuer mich?

mfg, hnzi

[Six]

Hi hnzi und willkommen an Bord.

Ich habe keine Lösung parat, aber vielleicht kannst du uns ja noch ein paar weitere Informationen liefern.

Z. B. gibt es /dev/fb0?
Wie aktivierst du den FB in lilo?

[hnzi]

ok, mein lilo.conf:

Code: Alles auswählen

# /etc/lilo.conf - See: `lilo(8)' and `lilo.conf(5)',
# ---------------       `install-mbr(8)', `/usr/share/doc/lilo/',
#                       and `/usr/share/doc/mbr/'.

# +---------------------------------------------------------------+
# |                        !! Reminder !!                         |
# |                                                               |
# | Don't forget to run `lilo' after you make changes to this     |
# | conffile, `/boot/bootmess.txt', or install a new kernel.  The |
# | computer will most likely fail to boot if a kernel-image      |
# | post-install script or you don't remember to run `lilo'.      |
# |                                                               |
# +---------------------------------------------------------------+

# Support LBA for large hard disks.
#
lba32

# Overrides the default mapping between harddisk names and the BIOS'
# harddisk order. Use with caution.
#disk=/dev/hde
#    bios=0x81

#disk=/dev/sda
#    bios=0x80

# Specifies the boot device.  This is where Lilo installs its boot
# block.  It can be either a partition, or the raw device, in which
# case it installs in the MBR, and will overwrite the current MBR.
#
boot=/dev/hda

# Specifies the device that should be mounted as root. (`/')
#
root=/dev/hda3

# Enable map compaction:
# Tries to merge read requests for adjacent sectors into a single
# read request. This drastically reduces load time and keeps the
# map smaller.  Using `compact' is especially recommended when
# booting from a floppy disk.  It is disabled here by default
# because it doesn't always work.
#
# compact

# Installs the specified file as the new boot sector
# You have the choice between: bmp, compat, menu and text
# Look in /boot/ and in lilo.conf(5) manpage for details
#
install=/boot/boot-menu.b

# Specifies the location of the map file
#
map=/boot/map

# You can set a password here, and uncomment the `restricted' lines
# in the image definitions below to make it so that a password must
# be typed to boot anything but a default configuration.  If a
# command line is given, other than one specified by an `append'
# statement in `lilo.conf', the password will be required, but a
# standard default boot will not require one.
#
# This will, for instance, prevent anyone with access to the
# console from booting with something like `Linux init=/bin/sh',
# and thus becoming `root' without proper authorization.
#
# Note that if you really need this type of security, you will
# likely also want to use `install-mbr' to reconfigure the MBR
# program, as well as set up your BIOS to disallow booting from
# removable disk or CD-ROM, then put a password on getting into the
# BIOS configuration as well.  Please RTFM `install-mbr(8)'.
#
password=**************
restricted

# Specifies the number of deciseconds (0.1 seconds) LILO should
# wait before booting the first image.
#
delay=20

# You can put a customized boot message up if you like.  If you use
# `prompt', and this computer may need to reboot unattended, you
# must specify a `timeout', or it will sit there forever waiting
# for a keypress.  `single-key' goes with the `alias' lines in the
# `image' configurations below.  eg: You can press `1' to boot
# `Linux', `2' to boot `LinuxOLD', if you uncomment the `alias'.
#
# message=/boot/bootmess.txt
prompt
timeout=50
#	prompt
#	single-key
#	delay=100
#	timeout=100

# Specifies the VGA text mode at boot time. (normal, extended, ask, <mode>)
#
vga=6
# vga=9
#
# vga=normal

# Kernel command line options that apply to all installed images go
# here.  See: The `boot-prompt-HOWO' and `kernel-parameters.txt' in
# the Linux kernel `Documentation' directory.
#
# append=""

# Boot up Linux by default.
#
default=Linux

image=/vmlinuz
	label=Linux
	read-only
#	restricted
#	alias=1

image=/vmlinuz.old
	label=LinuxOLD
	read-only
	optional
#	restricted
#	alias=2

# If you have another OS on this machine to boot, you can uncomment the
# following lines, changing the device name on the `other' line to
# where your other OS' partition is.
#
# other=/dev/hda4
#	label=HURD
#	restricted
#	alias=3
other=/dev/hdb1
  label="WindowsXP"
  map-drive=0x80
  to=0x81
  map-drive=0x81
  to=0x80

Code: Alles auswählen

crw--w----    1 root     video     29,   0 2002-03-14 22:51 /dev/fb0

fb0 gibts es auch, am anfang funktioniert es ja auch (der framebuffer)

???

mfg, hnzi

[Plat0n]

http://www.debianforum.de/wiki/?page=Ei ... er+Konsole

schau mal hier. Du musst Auflösung, ... in der lilo.conf eintragen.

[hnzi]

also an lilo.conf liegst nicht. ich hab einige einstellungen ausprobiert, auch die ask-option. bis zu 'Setting up general console font...' ist der framebuffer eingeschaltet, ab da wieder die normale vga-aufloesung.

braucht das setzen der consolenschrift bestimmte schriftsaetze die ich nicht habe?

ich werde das setzen mal deaktivieren , wozu ist das eigentlich gut?

mfg, hnzi