[SOLVED] console:switching to colour frame buffer device 128x48 while kernel boot 2.6.33-smp
SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Console: switching to colour frame buffer device 100x37
and the various attempts I have made to get around it have failed. Adding append = "nomodeset" to lilo.conf certainly stopped the microscopic frame buffer output but X would not start. Selecting a better size frame buffer option in lilo.conf worked for the first few screens and then back to microfont. Repeatedly crashing my head into the keyboard also did not work...
How did you set "a better frame buffer option" ? Simply using 'video=1024x768' (or whatever resolution you want) appended to the kernel boot line should force the framebuffer to use that resolution always.
How did you set "a better frame buffer option" ? Simply using 'video=1024x768' (or whatever resolution you want) appended to the kernel boot line should force the framebuffer to use that resolution always.
Hmmm... perhaps I have done this incorrectly? I simply added:
Code:
vga=771
and this is what I received for a few screens before being resized. Should this be added as append video=1024x768 in the top section? ??
I'm not in front of a slackware box at the moment, but as I recall there's already an append line, right? Just add video=1024x768 to it (make sure it's in the quotes already in that line).
vga=771 only works with the vesa/vga framebuffer, iirc. KMS uses the video option.
guys you are fast either with append = "video=1024x768" and vga=normal same problem as with when i disable vga=normal and leave append = "video=1024x768"
drm in dmesg shows this :
Code:
drm] Initialized drm 1.1.0 20060810
[drm] set up 7M of stolen space
[drm] initialized overlay support
fb0: inteldrmfb frame buffer device
[drm] Initialized i915 1.6.0 20080730 for 0000:00:02.0 on minor 0
Well, first, inteldrmfb is not a module. It's part of the intel drm. Simply using "nomodeset" on the kernel boot line will disable KMS (including inteldrmfb). But, as I believe we've already confirmed earlier in the thread, X will then not work with the intel driver.
I'm sorry, but if adding video="1024x768" doesn't force the framebuffer resolution to 1024x768, I'm not sure what to try next. Can you boot up with that option, run 'fbset' in the console, and show us the output?
one quick question what is relation between append = "video=1024x768" and vga=normal?
does both have to be enabled in lilo.conf?
im asking just to clarify
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.