Kernel mode setting on slack-current
Has anyone here tried intel kernel mode setting with slack-current?
I managed to make it work (well, almost), there're still some problems remain. I really appreciate if someone can give me some clue. I have G45 chipset (GMA X4500HD). I've updated xorg.conf to remove all input devices and switch to "UXA" acceleration method. That works nicely with VESA framebuffer before I enable kernel mode setting. Then I recompiled my kernel to enable kernel mode setting by default: Code:
CONFIG_DRM_I915_KMS=y Code:
CONFIG_FB_INTEL=y (... and quite a few of other dependents) Code:
video=intelfb:mode=800x600 Code:
fbcon=map:1 Now I'll list all problems I found, hopefully someone here knows how to solve them:
I really appreciate your help! |
I managed to get it working on my 945GM chip with a custom 2.6.30 kernel, and a UXA intel driver.
I get my native resolution at boot, but X hangs requiring a hard reboot if I attempt to switch to a VT or quit X. |
From what I am seeing in the newer 2.6.31-rc1-git3 kernel is that the Intel 915 chipset is getting a lot of work.
|
Quote:
|
Quote:
|
Quote:
Looks like I'm changing topic :) Anyway, one primary reason I want to try 2.6.30 is fast boot. Have you noticed the difference in boot speed? |
Quote:
Code:
TerminateServer=true It forces X to restart on logout, but that's better than hanging. Apart from this I have UXA/DRI2 working without problems on 2.6.30 kernel and a 965GM chipset. Helo |
1 Attachment(s)
if you are using KMS, you do not want to have any frame buffer drivers in your kernel or you will have problems.
remove all framebuffer devices, but leave framebuffer console support built-in also, you cannot use PAE with KMS without patching your kernel (attached) |
Problem (almost) solved
I removed intel framebuffer driver as suggested by "botnet" (that's a cool ID :) ). That's the only one in my customized kernel so no framebuffer driver is left after the removal. There's no behavior change after that, I think that means intel framebuffer is not necessary at all when KMS has been enabled.
Then I realize I have built DRM driver (i915 driver) as module. After I built i915 into kernel directly, the boot screen looks correctly, and the penguin mascot is now back! I also solve X crash problem follows helo's suggestion, add the following to the [X-:*-Core] section of /etc/kde/kdm/kdmrc: Code:
TerminateServer=true BTW, kernel mode setting is really great, switching between VT is blazingly fast. I know I won't go back to non-KMS kernel. |
I built a new 2.6.31-rc1 kernel and for whatever reason, KMS now works perfectly for me :) No more crashes on vt switch. Native resolution in VTs is very nice.
|
2.6.30 problem solved
Quote:
Now I'm using 2.6.30.1 with KMS, graphic behavior is as good as 2.6.29.5 (all problems solved except the text console resolution). I also tried the same kernel build options (no framebuffer driver, build in AGP and DRM driver, enable KMS by default) on another box (dell vostro 1400 laptop, GMA3100) with the same satisfactory result. |
All times are GMT -5. The time now is 08:12 AM. |