Hi!
dman <[EMAIL PROTECTED]> writes:
> What about bootloader config? Add "vga=0x31A" to your kernel command
> line.
Thanks for that hint. After reading the Kernel-Documentation about
vesafb I finally inserted vga=0x314 for better reading.
Ciao!
juh
--
Für eine Hand voll Bimbes
http://www.sud
On Mon, Oct 29, 2001 at 05:55:02PM +0100, Jan Ulrich Hasecke wrote:
| "Daniel T. Chen" <[EMAIL PROTECTED]> writes:
|
| > Rumours are that vesafb works just fine, though.
|
| Ok, I compiled a new kernel 2.4.12, disable rivafb and enable
| vesafb. All problems with the new nvidia-drivers seems to b
"Daniel T. Chen" <[EMAIL PROTECTED]> writes:
> Rumours are that vesafb works just fine, though.
Ok, I compiled a new kernel 2.4.12, disable rivafb and enable
vesafb. All problems with the new nvidia-drivers seems to be gone.
But I cannot get the vesafb to work.
After booting there is no Tux-Log
3 matches
Mail list logo