On Thu, Jul 11, 2002 at 06:11:17PM -0500, Nick Traxler wrote: | On Thu, Jul 11, 2002 at 07:10:04AM -0500, Derrick 'dman' Hudson wrote: | > On Thu, Jul 11, 2002 at 01:44:44AM -0500, Nick Traxler wrote: | > | I recently decided to play with a framebuffer device for my console, to | > | have a really l33t-looking shell, and to get the cool Tux logo when I | > | boot. | > | | > | Well, I got the framebuffer device working with my card (Geforce 2 MX) | > | and found the mode that I like best. (0x315, 800x600, 24-bit) | > | The problem is, when I tried putting '0x315' in my kernel options | > | > For vesafb, use | > vga=0x315 | | I guess I should have been clearer. That's what I tried. This was the | block from menu.lst: | | title Debian GNU/Linux, kernel 2.4.18 | root (hd0,0) | kernel /vmlinuz root=/dev/hda2 ro vga=0x315 | savedefault Do you have the vesafb driver compiled in your kernel? The line I have is this : kernel /boot/vmlinuz-2.4.18-custom.3 root=/dev/hda1 read-only video=vesa vga=0x31A however I didn't have the "video=" line when I first started using vesafb and it still worked. HTH, -D -- If we claim to be without sin, we deceive ourselves and the truth is not in us. I John 1:8 http://dman.ddts.net/~dman/
Attachment:
pgpryJULI8svz.pgp
Description: PGP signature