I have been bitten by the same irritating bug:
Code:
Console: switching to colour frame buffer device 100x37 My graphics are: Code:
root@skamandros/home/andrew# lspci | grep Graphics Andrew |
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.
Adam |
Hi Adam,
Quote:
Code:
vga=771 Andrew |
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. Adam |
I also have the problem although im using intel 865g
in lilo.conf i have added line exactly like this: Code:
append = "video=1024x768" Code:
/sbin/lilo |
What happens when you booted up with that append line? Can you show us the output of 'dmesg | grep drm'?
Adam |
Code:
dmesg |grep drm |
Can you show the full output of 'dmesg' then? Is KMS even enabled in your kernel?
Adam |
To double-check that vesa be not involved, at boot hit <tab> and type:
Code:
Linux vga=normal Code:
lspci -k | grep -A3 VGA Now if you see a module name including "fb" in the output, then blacklist this module, reboot (still with vga=normal) and please tell us the outcome. |
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 Code:
lspci -k | grep -A3 VGA |
Then append following line at the end of /etc/modprobe.d/blacklist.conf:
Code:
blacklist inteldrmfb |
Quote:
although vga=normal i disabled in lilo.conf, and enabled append = "video=1024x768" im wondering what adam will respond since my conclusion its something about kms related issue |
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? Adam |
I suppose i915 is compiled as a module and KMS is enabled by default for it. At least this is the case for kernels shipped with 13.1
If you want to make sure that kernel modesetting be not used (though may be then X won't start as Adamk75 stated) you could try this as root echo 'options i915 modeset=0' > /etc/modprobe.d/i915 and reboot. |
it gives :
Code:
mode "1024x768" does both have to be enabled in lilo.conf? im asking just to clarify |
All times are GMT -5. The time now is 06:30 PM. |