toofishes.net

New Eee kernel has KMS enabled by default

Posted June 23, 2009 at 9:17 p.m.

With the release of kernel-eee-2.6.30-2 tonight, I've made the switch to KMS (kernel mode-setting) being enabled by default. Hopefully this will be a seemless transition for all as I've pulled in three patches to the build to ensure things are working well. This is the first time I've patched the vanilla kernel in some time, so you know I'm serious about this.

The biggest things to keep in mind when upgrading:

Any vga= or video= lines you may have in your grub command line should be removed with the change to KMS.
Ensure your userspace has been upgraded- you need a relatively new version of Xorg for this to work.

I didn't need to make any xorg.conf configuration changes once I pulled in the relevant patches, so hopefully the same applies for everyone else. Please let me know if you have any trouble with the upgrade (by leaving a comment) and I'll try to follow up here. If everything works great, feel free to speak up too. :)

Comments (12)

Chicha on June 24, 2009 at 2:19 a.m.:

Hello !

I have a quick question: what is the issue keeping vga= or video= kernel options while using KMS ? Will those options disable KMS or are they just simply not necessary anymore ?

I any case, thanks a lot for all your work on the kernel !

Cheers,
Chicha

Svein on June 24, 2009 at 4:15 a.m.:

I could still have vga= on grub without that causing any trouble? I don't use an xorg.conf, i run xorg without a conf file and that works.

Thank you very much for an updated custom kernel!!!

Faelar on June 24, 2009 at 5:42 a.m.:

The only "problem" I have is that my cursor blink when I load a website or launch an application.

Everything else is smooth, and fast ! Even my external monitor can be used without a glitch.

I would like to thank you again for your work on the eee kernel toofishes :)

Dan McGee on June 24, 2009 at 6:57 a.m.:

There is no real need for a vga= or video= line in grub because the native resolution of your flatpanel will be used by the framebuffer, so specifying it doesn't make a whole lot of sense. I'm not sure what happens if you leave it there, so I'll let you guys find that out.

vinvin on June 24, 2009 at 9:16 a.m.:

I'm sorry to report that's a bad idea, since KMS is not working fine on EeePC 900 models. The wakeup from sleep leads to a black screen, and VGA output is not working at all.
See: http://bugzilla.kernel.org/show_bug.c... for more information.

David Coppa on June 29, 2009 at 2:28 a.m.:

Hi,
to have working suspend/resume with 2.6.30 and KMS, try this patch:
http://bugs.freedesktop.org/show_bug....

Cheers,
David

vinvin on July 7, 2009 at 1:24 p.m.:

David, this is not the same problem. The patch you point has been included in 2.6.30.1 and i still can't get the i915 out from sleep with KMS.

Cagnulein on Aug. 8, 2009 at 2:14 a.m.:

Hi, i follow your work from many month and i would like to thank you for all :)
Anyway i have a tip to grow your stuff: why don't you upload on your git the eeepc kernel module (compiled with your kernel :) )?
Thanks
Cagnulein

mxairman on Aug. 15, 2009 at 2:38 p.m.:

Hi.

When I updated to 2.6.30-2 Ilost my splash screen (splashy). I have no vga or video on my grub menu, and I don't use an xorg.conf. No big deal, though

Now I upgraded to 2.6.30-4 and I have a strange problem. Filesystem check fails and sends me to a maintenance shell... fsck tells me drives are clean. That problem doesn't appear when I boot the Arch stock kernel (filesystems clean), but now I cannot use the stock kernel because some modules are blacklisted by framebuffer and it doesn't start x.

I reinstalled the whole thing and the same problem persists. Only walk through is to boot eee kernel on battery, so file system checks are skipped. I really have no idea.

By the way thanks for the great job, and I hope my info is helpful

vinvin on Aug. 26, 2009 at 3:57 a.m.:

mxairman: I had the same problem, only sometimes, i couldn't figure why. With stock kernel the fs was clean, but with kernel-eee it was not. I finally ran the fsck on an alternate block, as suggested, and it found several errors. Maybe a ext2 corruption bug was announced in the kernel, i don't know, but it seems that there is a problem at some point. It did not reappear for me since I made the fsck on alternate superblock, but it does not mean it solved it.

mxairman on Aug. 26, 2009 at 11:25 a.m.:

Thanks for the reply vinvin. After a reinstall, with ext4, I'm having the same problem, so I don't think it's any ext2 corruption.I will try the fsck on alternate superblock and I will post the result. Thanks

mxairman on Sept. 2, 2009 at 7:15 a.m.:

Filesystem problem got fixed after kernel 2.26.30-5. Splash image still not working, not a big deal, but i'd still like to use splashy

New Eee kernel has KMS enabled by default

Posted June 23, 2009 at 9:17 p.m.

Similar Posts

Comments (12)