console:switching to colour frame buffer device 128x48 while kernel boot 2.6.33-smp
 

hi!

in lilo.conf i do have specified vga normal

but while booting the system screen resolution changes and it says
what is causing this? how can i prevent this from happening again?

this only happens when i do have 2.6.33 predefined kernels installed.

Thanks alot!

hi,
Are you running slackware-current?
Blacklisting the nouveau driver (and using the nvidia driver) solved the problem for me.

As I understand it, something was changed in the KBM (kernel based mode setting), that thingy which prevents flickering of the display during boot and changes of resolution. Maybe it is just a side effect...

yes slackware-current.im using intel 865g onboard chipset i tried blacklisting by specifying blacklist nouveau anyway to see no matter because its nvidia and no joy for me.

If it is related to KMS (not KBM), you can disable it at boot by passing the 'nomodeset' option to the kernel. Mind you, I doubt X will start on intel GPUs without KMS enabled :-)

EDIT: Alright, so X will still work if you disable KMS on Slackware 13.0. What I've heard, though, is that it will not work on -current. I can't confirm this personally, though:

http://www.linuxquestions.org/questi...normal-792873/

Darned acronyms ;) :p

Thanks for the correction.

@JZL240I-U and adam yes that fixes the problem.

jzl where did you get the info from that its about kms ?

when i disable kms while in X windows i can change console with ctrl+alt+f1-f6 no problem but if kms is enabled then when i try to switch back to consoles with ctrl+alt+f1-f6 it gives black screen and i cant use ctrl+alt+backspace no more.

also xorgsetup when trying to detect hardware gives black screen no matter if kms is enabled or disabled. im wondering what cause that it gives black screen?, im wondering how xorgsetup operate? does it operate in a way that its trying to start a xorg server when detecting hardware?

i saved xorg.conf from previous xorg server from slack13

and tried to start x to see what happens.
i get this:

/usr/lib/xorg/modules/intel_drv.so: undefined symbol: resVgaShared

because at the moment im unable to get proper resolution in X windows. i see that many ppls say that driver that i have installed is conflict with x-org server or does not support xorg server that im running, so i will see about it.

thats why i would like to know how xorgsetup operate when detecting hardware through hal?

thanks guys

That was a guess founded on your description of the problem.

For a controlled reboot use <Alt> + <SysReq> + REISUB (typing the (small) characters in this sequence)

http://kember.net/articles/231/reisu...-linux-restart
http://www.definition-of.com/REISUB

For this the SysRq feature must be turned on, i.e. "cat /proc/sys/kernel/sysrq" issues "1".

I have no answer for this, sorry.

If I wouldn't want frame buffer I'd just blacklist the relevant module; lsmod|grep fb would tell me which one.

@jzl sysrq codes works perfecly. thanks for info!

lets wait and see that someone reply whys that happening when kms is enabled and while in X windows when switching to consoles ctrl+alt+f1-f6 gives black screen? what causes that?

and no matter if kms is enabled or disabled in lilo xorgsetup gives black screen while trying to detect hardware ? what causes this?


wondering how xorgsetup operate when trying to detect hardware?

another thing about inteldrmfb would like to know how its related to kms?

And I have that problem, but I am not using any drivers for the video card. So, before slackware start on the lilo prompt to type nomodeset, and I should turn off kms from lilo.conf? But after that X may not work?

im speaking in the name of intel chipset 865g, if you have slackware-current installed libdrm and xf86-video-intel-2.10 installed you can start X windows no matter if kms is enabled or disabled, but resolution wont be properly displayed, as i described earlier. however im still waiting for peoples to answer on my questions that i posted,

thanks guys

I have installed only libdrm, but as I said I don't use any drivers, but if I remove libdrm? This will break anything...

What do you mean by "I am not using any drivers for the video card." ? Are you saying that you're not using Xorg? Because if you are using Xorg, then you're using drivers for your video card.

Adam

to turn off kms in /etc/lilo.conf add the line
save /etc/lilo.conf,

then do :
and reboot.thats how resolution came back to normal for me on 865g chipset.

if u want to turn on kms back just comment the line to be like this: save lilo.conf and start lilo with and reboot.


im wondering when i will get the answer on my questions :)

I have been bitten by the same irritating bug:

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...

My graphics are:

and I would love a bit of advice on how to get around this problem. Running Slackware 13.1 and 2.6.33.4-smp.

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,

Hmmm... perhaps I have done this incorrectly? I simply added:

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? ??

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:
and then executed : and rebooted but it dosent work for me either. Is there anything we missed?

What happens when you booted up with that append line? Can you show us the output of 'dmesg | grep drm'?

Adam

shows nothing, and with that append line i still have microcospic fonts

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:
If you still see the hight of characters changing on the console during startup, then another frame-buffer driver is involved. To know which one type:
and post the output here.

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 : and heres

Then append following line at the end of /etc/modprobe.d/blacklist.conf:
reboot and see what happens.

blacklisting didnt help
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 :
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

Theoretically when KMS kicks in the vga/vesa console will hand control over to inteldrmfb, so you probably don't need vga=normal, but it can't hurt anything.

But your fbset output basically shows that it's working as expected. If you want a different resolution on the console (such as 800x600 or 640x480) just specify that with video= instead of 1024x768.

Adam

It worked and really vga=normal its not necessary, when i changed to 640x480 it gave big change, in opposite to 800x600.

can you tell me also where i can look for full list of switches for kernel options for append ?

You'd have to check the documentation that comes with the kernel. There are probably thousands of options for the various kernel subsystems and drivers. The framebuffer documentation, unfortunately, is pretty out-of-date, actually. The only reason I know these options is from hanging on in various related channels on IRC.

Adam

See /usr/src/linux/Documentation/kernel-parameters.txt, provided a kernel-source package be installed, of course.

Be aware though that as stated in it "This document may not be entirely up to date and comprehensive".

You can "grep -r __setup /usr/src/linux/*" to find more parameters but it will take _some_time_ to complete ;)

thanks to all.

adam: what are those channels if you dont mind sharing?

#radeon, #dri-devel

There's an intel specific one that I don't spend much time in, though, called #intel-gfx

All three are on freenode.

Adam

I have just been playing with this.
The 'vga=normal/ext/ask/n' is used by the kernel until the inteldrmfb is setup. Have a look at 'dmesg | less'.
The 'append = "intelfb:video=1024x768"' is used by the kernel to configure the framebuffer.

Apart from /usr/src/linux/Documentation/kernel-parameters.txt you can also take a look at /usr/src/linux/Documentation/fb/intelfb.txt

The intelfb.txt document is largely not applicable to this situation since the OP isn't using intelfb. He's using inteldrmfb, a completely separate beast.

Adam

It does give detail about the options though.

hey allend both you and adam were right and its pleasure to learn from you :) i hope you upgraded intel driver since i had problems up untill several days ago :) thank you all