Re: [arch-general] Did new kernel version removed vesa FB?
On 5/12/09, Damjan Georgievski gdam...@gmail.com wrote: Well, I tried it, and I got uvesafb working (that's way better than no FB at all), but I can't get it to work properly. It seems uvesafb is not paying attention to: % grep '^options' /etc/modprobe.d/uvesafb options uvesafb mode_option=1920x1200...@75 scroll=ywrap I've tried other resolutions, no frequency specification, and several other combinations, and I always get: You could try some of the options documented here: http://www.mjmwired.net/kernel/Documentation/fb/uvesafb.txt Maybe vbemode:x Force the use of VBE mode x. The mode will only be set if it's found in the VBE-provided list of supported modes. NOTE: The mode number 'x' should be specified in VESA mode number notation, not the Linux kernel one (eg. 257 instead of 769). HINT: If you use this option because normal mode parameter does not work for you and you use a X server, you'll probably want to set the 'nocrtc' option to ensure that the video mode is properly restored after console - X switches. -- damjan I tried that, with no luck at all... By doing: cat /sys/bus/platform/drivers/uvesafb/uvesafb.0/vbe_modes I see that 1920x1200-32 corresponds to 0x017d. I tried to specify that with vbemode option, several ways, like keeping the 1920x1200-32 option, removing everything but the vbemode option, etc... And the result is always the same128x48... Thanks, -- Javier
Re: [arch-general] Did new kernel version removed vesa FB?
On 5/12/09, Damjan Georgievski gdam...@gmail.com wrote: I few minutes ago I upgraded a arch box (x86_64), and to my surprise, something that was working before, loading the kernel with parameter vga=0x37D is no longer working (nothing happens). The new version is 2.6.29.3-1. The resolution for nvidia quadro fx 570m is 1920x1200, but the nvidiafb module has never worked, so I need to use the vesa FB... You can try uvesafb which should offer more features and maybe is even more stable. It's a module in the Ach kernel, so you'll need to include it in the initramfs ... Actually here's a description http://wiki.archlinux.org/index.php/Uvesafb -- damjan Well, I tried it, and I got uvesafb working (that's way better than no FB at all), but I can't get it to work properly. It seems uvesafb is not paying attention to: % grep '^options' /etc/modprobe.d/uvesafb options uvesafb mode_option=1920x1200...@75 scroll=ywrap I've tried other resolutions, no frequency specification, and several other combinations, and I always get: uvesafb: NVIDIA Corporation, G84 Board - vb_040CE, Chip Rev , OEM: NVIDIA, VBE v3.0 uvesafb: VBIOS/hardware doesn't support DDC transfers uvesafb: no monitor limits have been set, default refresh rate will be used uvesafb: scrolling: redraw Console: switching to colour frame buffer device 128x48 uvesafb: framebuffer at 0xe700, mapped to 0xc2000410, using 14336k, total 14336k fb0: VESA VGA frame buffer device It doesn't sound completely right to me. I also tried the default 1280x800, and nothing... Well, with this I can set a terminus font, which can't happen without FB... Thanks, -- Javier
Re: [arch-general] Did new kernel version removed vesa FB?
Well, I tried it, and I got uvesafb working (that's way better than no FB at all), but I can't get it to work properly. It seems uvesafb is not paying attention to: % grep '^options' /etc/modprobe.d/uvesafb options uvesafb mode_option=1920x1200...@75 scroll=ywrap I've tried other resolutions, no frequency specification, and several other combinations, and I always get: You could try some of the options documented here: http://www.mjmwired.net/kernel/Documentation/fb/uvesafb.txt Maybe vbemode:x Force the use of VBE mode x. The mode will only be set if it's found in the VBE-provided list of supported modes. NOTE: The mode number 'x' should be specified in VESA mode number notation, not the Linux kernel one (eg. 257 instead of 769). HINT: If you use this option because normal mode parameter does not work for you and you use a X server, you'll probably want to set the 'nocrtc' option to ensure that the video mode is properly restored after console - X switches. -- damjan
