Why spend money on hardware i dont need if there is a simple straightforward solution that involves no money and little time? And it isnt jsut intel, i have used video hardware on other machines, mostly older ones, that didnt display the framebuffer console correctly. Even on a machine with hardware resources to spare, framebuffer consoles are sometimes visibly slower, it would be much better to be offered the choice. I realize tho that framebuffer support is compiled in (iirc) and not a module, so it would add the over head of another kernel to the install media, and that its about how it looks and not functionality.

So I may try that instead If I get brave enough to attempt a kernel rebuild, which I haven't yet in over 5 years of using Linux!).

Go for it dude

As long as you remember to append a version string to the kernel so that the module installer doesnt put the modules in the same dir in /lib/modules that was installed by the distro and remember to edit your lilo config appropriately to add the new kernel you just built, its pretty safe. The worst that can happen is that you build a kernel that wont boot and you still have the original as a fallback.

Notice the difference in names, that way there is no confusion. Append the version of the kernel you just built to the System.map and config files as well, ie System.map-2.6.27.12bo and config-2.6.27.12bo and you will be good to go and still have the original vanilla kernel as a back up. Dont forget to back up your lilo.conf just in case.

EDIT: I guess i should check out the docs before shooting my mouth off I wish i could say it will be the last time i do it Anyway, i just checked and i dont have a kernel running on my machine that has an fbcon module compiled for it. If anybody tries this could you post the results here?my guess is that the way you would use it would be to put a file in /etc/modprobe.d named "fbcon" and containing the single line "options fbcon=map:1" .

If I get brave enough to attempt a kernel rebuild, which I haven't yet in over 5 years of using Linux!)To date, COLONEL - we have not been informed of VL version (does kernel sources exist)~ Have not seen error logs, xorg.conf content

A frame buffer device is a memory device like /dev/mem andit has the same features. You can read it, write it, seek to some location init and mmap() it (the main usage). The difference is just that the memory thatappears in the special file is not the whole memory, but the frame buffer of some video hardwarePlease see (/dev/fb_nx) ~ /usr/src/linux_nx/documentation

NOTE: ~ Reserved vs re-mapable - SIZE (very small - only use is for text display/colours)If/when reserved - unavailable for total GPU Mem

I couldnt get the fbcon thing to work because the only kernel i have with framebuffer support enabled is the new VL beta and according to /proc/config.gz framebuffer support is compiled into the kernel. I took a look at man fbset and couldnt get that to work, but i did find this:http://bkhome.org/blog/?viewDetailed=01706Apparently framebuffer console problems are common enough and i am about to reboot and try the solution in the above url.

EDIT: SUCCESS! passing the kernel "video=640x480" gives a readable console that looks just like the default vga, and the screen and monitor edges match. YAY!

You really should learn how VESA standards apply to chipset-firmware &/or OEM non-conformity to stipulations ----------------------------------------------------------------------------------------------------------------------------------------------------------His Tmp solution (which he is not happy with) relates to use of fbcon module

NOTE ~ That addressed only PUPPY community, reports of "small text displayed" ~ NOT weird behaviour @ bootup, or text out of view

Further, since when is Nouveau (Xorg driver) a VID hardware device ?

Did you fail to read bug reports - it is an OEM firmware policy now NOT kernel or Xorg

« Last Edit: March 13, 2011, 01:46:21 am by rm-r »

Logged

"Problems are seldom resolved by thinking in the same manner they were created"

A quick update; I solved this for the time being by installing Vector 5.8 Standard. For some reason it doesn't have the framebuffer console display problem I've described here, and it runs Softmaker Office 2008 so is useful as a home / office distro.

It might not be as secure for most people as a later Vector release would be so I couldn't recommend it for others, but I don't have a home internet connection at the moment so this doesn't matter much in my case.