Arch Linux

cyberpatrol

Member

From: Germany

Registered: 2006-11-22

Posts: 68

Problems with kernel26beyond and vesafb

Hi!

I've noticed that iphitus unfortunately removed vesafb-tng from kernel26beyond 2.6.19.

The problem is that vga=795 which shall invoke the 1280x1024-24 mode doesn't work for me with my NVIDIA GeForce 2 MX 400. I'm getting the message "You passed an undefined mode number." And vga=794, the 16 bit mode, is just ugly. With vesafb-tng I didn't have any problems.

Another disadvantage of vesafb is that it only works in a - even on TFT monitors - flickering 60Hz mode while vesafb-tng works with 75 Hz and is not really slower.

So it would be great if vesafb-tng would get back again into the kernel26beyond. Or does someone know how to get the 1280x1024-24@75 mode or even better the 1280x1024-32@75 mode working with vesafb?

cromo

Member

From: Czestochowa, Poland

Registered: 2006-09-20

Posts: 87

Re: Problems with kernel26beyond and vesafb

Since vesafb-tng is removed from beyond, are there any chances for radeonfb to be available as module again?

Avenger

Member

Registered: 2005-11-11

Posts: 65

Re: Problems with kernel26beyond and vesafb

I've also got a problem with 2.6.19 beyond and vesafb, I get the same undefined mode message for every mode except vga=normal

I have a radeon mobility x700, and it worked perfectly in 1024x768-32 with vesafb-tng.

I was using gensplash before the upgrade, and here is my kernel-line:

kernel /boot/vmlinuz26beyond root=/dev/hda2 vga=792 video=vesafb:mtrr:3,ywrap splash=silent,kdgraphics,fadein,theme:darch console=tty1 quiet

cyberpatrol

Member

From: Germany

Registered: 2006-11-22

Posts: 68

Re: Problems with kernel26beyond and vesafb

Thanks for the hint, gpfault. Your method works but doesn't bring the solution to the problem.
The highest mode the vesa driver shows me is 0x11a (794) which is the mode 1280x1024-16 while, as I wrote in my original post, vesafb-tng offers additionally the mode 1280x1024-24.
And the problem that vesafb only works with 60 Hz instead of 75 Hz which is used by vesafb-tng still exists.

And there's another unaesthetic problem. When booting with the silent splash the monitor is getting black for a short time after the kernel is initialized.

So I still can only ask to bring vesafb-tng back to kernel26beyond because it's much more advanced compared to vesafb. I'm using vesafb-tng since 3 years on Gentoo now and hadn't had any problems with it. But always when I try vesafb I've got many problems, not only eyecandy problems. I also have the impression that vesafb is a bit slower than vesafb-tng.

From experience vesafb is much less stable than vesafb-tng.