You are not logged in.
Pages: 1
I've compiled the archck-sources with vesafb-tng support:
[root@gatubarn kernel26archck]# cat config | grep VESA
CONFIG_FB_VESA=y
CONFIG_FB_VESA_STD=y
CONFIG_FB_VESA_TNG=y
The reason I did this was that my console became crap after switching from the X-server to a regular console, or killing the X-server (I am using tv-out). I heard vesafb-tng was the solution and decided to give it a go.
Here's the grub menu.lst part:
[root@gatubarn grub]# cat menu.lst | grep archck
kernel /vmlinuz26archck root=/dev/hda4 video=vesafb:1024x768-32@72 splash=verbose,theme:darch quiet CONSOLE=/dev/tty1
It *boots* fine... like it did without the vesafb-tng support. Which I guess goes to prove that vesafb-tng works. However, when killing X or switching to another console the screen just turns black and everything just freezes! The only way out of this seems to be hard reboot.
Any ideas?
Offline
After checking the fbsplash page I decided to try disabling SMP in the kernel configuration. This morning I rebooted with the new kernel installed and everything seems to work.
Offline
Is there any solution to the "slow scrolling" in vesa-tng? I have nvidia and I'm runing the console at 1024x768x32@85. It's totally unusable for any serious editing job since the redrawing is so laggy. And this is a 2500Mhz machine.
MDK
Open Source Software Operations/Nokia
michael.kostrzewa (at) nokia.com
Offline
I have never been impressed with vesa-tng
Offline
Pages: 1