You are not logged in.
Thanks, with that config I can get this "working"...
So, I remove my Xorg config completely, boot with "i915.modeset=1" on the kernel line and things seem to go well. When boot gets to the udev line, the resolution in all my vt/x increases. Go, go, framebuffer. Then X actually works.
From my xorg log, I can see UXA is activated by default so KMS appears to work. glxgears still ~520 FPS, which is slower than with UXA and no KMS. The games I use to test (chromium-bsu and extreme-tux-racer) still run badly.
It's a conspiracy.
Offline
Thanks, with that config I can get this "working"...
So, I remove my Xorg config completely, boot with "i915.modeset=1" on the kernel line and things seem to go well. When boot gets to the udev line, the resolution in all my vt/x increases. Go, go, framebuffer. Then X actually works.
From my xorg log, I can see UXA is activated by default so KMS appears to work. glxgears still ~520 FPS, which is slower than with UXA and no KMS. The games I use to test (chromium-bsu and extreme-tux-racer) still run badly.
Hm. That's too bad. (I don't think the glxgears issue matters though, but the games should run well).
Maybe you could also try updating libgl, intel-dri, and mesa to 7.4-rc1.
I'm gonna install etracer and see where it gets me.
EDIT: Also, there might be something to this: http://jasondclinton.livejournal.com/72910.html
Last edited by nightfrost (2009-03-23 14:46:50)
Offline
When boot gets to the udev line, the resolution in all my vt/x increases.
this is confusing me a bit. when i'm using vesafb, i'm in framebuffer earlier in the boot process. should i include any module in the kernel image to get this working earlier? i'm not using any special kernel command line BTW, i tried what Allan just used and in that case, the resolution will not change.
Offline
When boot gets to the udev line, the resolution in all my vt/x increases.
this is confusing me a bit. when i'm using vesafb, i'm in framebuffer earlier in the boot process. should i include any module in the kernel image to get this working earlier? i'm not using any special kernel command line BTW, i tried what Allan just used and in that case, the resolution will not change.
I put this in /etc/mkinicpio.conf
MODULES="intel_agp drm i915"
Offline
bangkok_manouel wrote:When boot gets to the udev line, the resolution in all my vt/x increases.
this is confusing me a bit. when i'm using vesafb, i'm in framebuffer earlier in the boot process. should i include any module in the kernel image to get this working earlier? i'm not using any special kernel command line BTW, i tried what Allan just used and in that case, the resolution will not change.
I put this in /etc/mkinicpio.conf
MODULES="intel_agp drm i915"
ok it worked, thanks! last thing, not that i care that much but i dont have any logo showing up anymore... any idea?
Offline
Allan, I just tried etracer here and it runs smoothly @ my native resolution. Nothing to complain about.
I get ~20 fps with the ondemand governor (and its bug). With the performance governor, I get ~30 fps. This is on g45.
What are your figures?
Offline
Adding that MODULEs line to /etc/mkinitcpio.conf enables the framebuffer earlier but makes no difference overall.
Where do you get FPS for etracer? I don't see an option to display them. With chromuim-bsu I get ~10FPS with 2.6.29 (with disabled cpufreq governors) but get ~50FPS in 2.6.28 with UXA.
Offline
Where do you get FPS for etracer? I don't see an option to display them.
Configuration -> Graphics -> Display FPS.
Offline
chromium is one seriously cool game! Nice!
I get ~50 fps with performance governor. And about 40 without.
Offline
In the case of tuxracer the choice of governor makes a huge difference for me.
ondemand ~40fps
performance ~120fps
Offline
Anyone knows how am i supposed to enable kms? i read on the dev ml that i had to set option i915 modeset=1 (i supposed he meant options).. anyway, can any one point me to TFM?
Offline
Anyone knows how am i supposed to enable kms? i read on the dev ml that i had to set option i915 modeset=1 (i supposed he meant options).. anyway, can any one point me to TFM?
Look some posts up and you'll have your answer
My blog: blog.marcdeop.com
Jabber ID: damnshock@jabber.org
Offline
Anyone knows how am i supposed to enable kms? i read on the dev ml that i had to set option i915 modeset=1 (i supposed he meant options).. anyway, can any one point me to TFM?
Add i915.modeset=1 on the grub command line. I was kinda confused about this at first myself, because the first you'll see after booting is something to the effect of "i915.modeset=1 unknown option". But it actually does what it's supposed to.
Offline
2.6.29 and UXA freezes the computer, only rebooting through sysrq keys work..........anyone experiencing this? UXA used to work with 2.6.28
Offline
2.6.29 and UXA freezes the computer, only rebooting through sysrq keys work..........anyone experiencing this? UXA used to work with 2.6.28
Are you using the intel driver from [testing]? You could try a git tip to see if that helps? FWIW, I'm not experiencing crashes, but a couple of other weirdnesses.
Offline
2.6.29 and UXA freezes the computer, only rebooting through sysrq keys work..........anyone experiencing this? UXA used to work with 2.6.28
I had a similar problem, adding MODULES="intel_agp drm i915" to mkinitcpio.conf fixed it for me. YMMV
Offline
Hi Arch users,
I achieved to enable KMS using kernel 2.6.29 and xf86-video-intel 2.6.99.902 (both from testing) on a Lenovo 3000 N200 laptop with a 965GM GC with all the tips given above (thanks guys!).
Everything seems to work fine but there's a few things I wanted to know:
- KMS is enabled only after udev is started. Is there a way to enable it right after kernel boot (I've added intel_agp drm & i915 in mkinitcpio.conf)?
- Switching from X to VT is smooth and fast, but switching back to X still makes the screen flicker. Is that normal? I noticed this in Xorg.0.log:
(II) AIGLX: Suspending AIGLX clients for VT switch
(II) Open ACPI successful (/var/run/acpid.socket)
(II) AIGLX: Resuming AIGLX clients after VT switch
Is that behavior related to AIGLX? I don't think so, since removing xorg.conf make X enable it (and UXA and DRI2) anyway, so I think this is the expected behavior from X and/or Intel driver with KMS...
Offline
I have the exact same problem as ianux, also.. X seems slower and doesn't seem to be using the same depth as before now (using UXA).. Anyone else experiencing this?
Offline
I follow your instructions, but it doesn't work for me.
KMS is not enabled, even if I made modifications in boot and /etc/mkinicpio.conf.
In dmesg, i915.modeset=1 is unknown option.
And when I start X, it freezes on black screen.
without i915.modeset=1, I can start X, but in EXA (no UXA with HAL)
What did I missed ? (2.6.29 kenel and all testing packages)
Last edited by mika91 (2009-03-26 12:55:04)
Offline
You have built your own kernel? The kernel in [testing] does not enable CONFIG_DRM_I915_KMS.
Offline
Ok, so I need to compile my own kernel ?
I think it would be enabled in [testing] kernel.
Thanks
Offline
You have built your own kernel? The kernel in [testing] does not enable CONFIG_DRM_I915_KMS.
As far as I understand, modetsetting is now part of the i915 module, period. The CONFIG_DRM_I915 option is merely a question of whether modesetting should be enabled by default or not. If it's not set, as is the case with the arch kernel, you just have to add i915.modeset=1 at the grub boot line (and, possibly, "options i915 modeset=1" to /etc/modprobe.conf).
For what it's worth, I have modesetting working just fine with the official kernel from [testing]. The instructions are all to be found in this thread. Also, I should note that I also see the complaint that "i915.modeset=1 is an unknown option", but still, KMS does work properly on my two laptops.
Last edited by nightfrost (2009-03-26 13:37:26)
Offline
Allan wrote:You have built your own kernel? The kernel in [testing] does not enable CONFIG_DRM_I915_KMS.
As far as I understand, modetsetting is now part of the i915 module, period. The CONFIG_DRM_I915 option is merely a question of whether modesetting should be enabled by default or not. If it's not set, as is the case with the arch kernel, you just have to add i915.modeset=1 at the grub boot line (and, possibly, "options i915 modeset=1" to /etc/modprobe.conf).
I tried with just the "i915.modeset=1" at the grub boot line and it did not work. I guess you now MUST add the modules to /etc/mkinicpio.conf. I will be trying all this out again at the weekend.
Offline
I have KMS working fine here as well, but other than that X is horribly slow! I can't use compiz anymore, as my 3d performance is totally gone. I have tested my 3d performance in 'tuxracer' (the old one as I can't even play 'etracer' with my normal config) and it's unplayable right now. I have gone from ~1450 fps to ~500 fps in 'glxgears' (I know it's not a benchmark, but the performance drop is quite significant I think).
Does anybody know when we will see a brighter future? I'm a little tired of not having proper video overlay with my normal setup (I normally use 'xorg-server 1.4.2' and 'xf86-video-intel 2.3.2').
Offline
For what it's worth, I have modesetting working just fine with the official kernel from [testing]. The instructions are all to be found in this thread. Also, I should note that I also see the complaint that "i915.modeset=1 is an unknown option", but still, KMS does work properly on my two laptops.
How do you see that KMS works ?
I followed all this post instructions, but it doesn't work for me.
The console resolution don't change when I boot, and X freezes my system (only hard reboot possible)
Do you use HAL or have an xorg.conf ?
Please share it thanks
Offline