On Tue, Jan 16, 2007 at 14:13:15 +0100, Daniel Haude wrote:
> Florian Kulzer wrote:
>
> > I use vga=0x303 and that looks exactly like Knoppix's fonts on my
> > terminals. However, I think this also depends on the kernel
> > configuration options related to the console fonts. Here is what I have:
> >
> > $ grep -i font /boot/config-$(uname -r)
> > # CONFIG_FONTS is not set
> > CONFIG_FONT_8x8=y
> > CONFIG_FONT_8x16=y
> >
> > (I use a self-compiled kernel, therefore I do not know how the stock
> > Debian kernels are set up in that respect.)
>
> My stock kernel (2.4.27-3-k7) gives the same settings, but doesn't let
> me change anything. In fact it seems to ignore any of the vga= options,
> including "vga=ask". Here's what I see in dmesg's output:
>
> Kernel command line: root=/dev/hda5 ro vga=4 hdc=ide-scsi hdd=ide-scsi
> vga=791
> Initializing CPU#0
> Detected 2104.783 MHz processor.
> Console: colour VGA+ 80x30
>
> This is sad because it's a non-X system and I'd like to see some more
> info on the console screen.
One thing I forgot to mention: I use the generic vesa framebuffer
compiled statically into the kernel. (I have an nvidia GeForce2 graphics
card, but I never found a reason to bother with the nvidia framebuffer
module.)
I would check with dmesg and lsmod which framebuffer module you are
using. Compiling the framebuffer code into the kernel might make a
difference for the availability of video modes at boot time. (I vaguely
remember that I had problems with the vga modes when I started to play
around with Linux, and I think that was the reason for me to compile
vesafb into the kernel. Unfortunately, however, I am not 100% sure of
this.)
--
Regards,
Florian
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
