Hello all,

I am using the most recent -current (that fixes the libpng "ratness" described in the ChangeLog 8-) and the Intel Framebuffer setup is annoying me. I specify vga=normal in LILO and to my knowledge I am not asking Intel Framebuffer modules to load at boot (and intelfb is blacklisted).

It's annoying because it makes the text microscopic. However, the machine works great in -Current so I can't complain. Graphics work fine and so does X, it's just annoying.

This is my Sony Vaio VGN-C140G detailed here:
http://www.puresimplicity.net/~delah...sony/sony.html

I had tried previously blacklisting inteldrmfb as well (the -Current release right before the libpng fix) and that made no difference.

I found all binaries with "intel" in their name and read the manual pages but didn't find anything useful for possibly manually setting the mode back to something equivalent to vga=normal.

Thanks!

- Robert

By the way, can someone please change my user name on this forum to "Robert Delahunt" or "radelahunt"? Thanks....

This sounds like kernel mode setting to me. It's the default in the latest kernels. With kms you don't use a vga line at all in lilo.

You should be able to disable kernel modesetting with the 'nomodeset' option on the kernel command line. At least that works for radeon cards, and I *believe* it works for intel GPUs too.

Adam

Tried nomodeset but then X complains that it can't talk to the modesetting driver so X won't start.

Sorry, I'll be back online later. I've been in the air 15 hours, gotta get some sleep. Thanks though!

Yeah, I thought the intel driver might be dependent on KMS these days. I know with radeon you can specify a resolution with 'video=1024x768' on the kernel command line. Perhaps the same is true with intel.

Adam

This blogger has posted many times about video problems with Intel KMS:
http://www.insidesocal.com/click/201...eeling-in.html
Basically, the combination of latest kernel, latest xorg and latest Intel driver results in nomodeset no longer being an option and kms is required. Unfortunately, some equipment simply won't work (currently) with kms.

Hah... They talk about switching to FreeBSD... I guess they are unaware tht FreeBSD is even worse off for Intel GPU users. FreeBSD does not support KMS, so newer versions of the intel driver won't work on FreeBSD at all. In addition, the current version in FreeBSD ports does not work on newer versions of the X server. So when the ports tree finally gets a newer Xserver, there is a good chance that intel users will be forced to use the vesa driver unless one of those two situations is resolved.

Adam