Strange KMS Glitch

jlacroix · 2009-12-09 02:23:30

Hello everyone, I decided to enable KMS so I can take advantage of it. I followed the Arch "Early Start" instructions:
http://wiki.archlinux.org/index.php/Int … Setting.29

Now there are two small glitches. First of all, the boot messages don't show in the native resolution. I'm fine with that since it's no big deal unless it's an easy fix. The worst problem is that when I switch to a TTY, it's nothing but a blank screen with a blinking cursor closer to the middle of the screen. The good thing is that if I press enter, the TTY will appear the way it should but I have to press enter in order for the TTY to appear correctly.

My system uses an Intel video card stock on the motherboard.

tavianator · 2009-12-09 03:18:16

Look through "dmesg | grep drm" to maybe find why it's not setting the resolution correctly at first. But the second problem is probably a result of the first. That's what happens when the framebuffer console gets resized: it erases the console and sticks your cursor in the middle. When during the boot process does the resolution change?

jlacroix · 2009-12-09 03:48:43

tavianator wrote:

Look through "dmesg | grep drm" to maybe find why it's not setting the resolution correctly at first. But the second problem is probably a result of the first. That's what happens when the framebuffer console gets resized: it erases the console and sticks your cursor in the middle. When during the boot process does the resolution change?

The resolution never changes during the boot process until KDM loads. When I shut down, the resolution is the native resolution.

[jeremy@jeremy-laptop ~]$ dmesg | grep drm
[drm] Initialized drm 1.1.0 20060810
[drm] MTRR allocation failed.  Graphics performance may suffer.
[drm:intel_dp_i2c_init] *ERROR* i2c_init DPDDC-D
[drm] fb0: inteldrmfb frame buffer device
[drm] Initialized i915 1.6.0 20080730 for 0000:00:02.0 on minor 0
[drm] LVDS-8: set mode 1366x768 c

As I can see there is a couple of errors there. I'll Google them, but if you already know the answer feel free to post it.

Thank you.

tavianator · 2009-12-09 03:53:02

I've got no better explanations that google can provide you with at this point. But being that it looks like an in-kernel issue, you might want to upgrade your kernel. I believe 2.6.32 is in [testing].

jlacroix · 2009-12-09 03:56:01

tavianator wrote:

I've got no better explanations that google can provide you with at this point. But being that it looks like an in-kernel issue, you might want to upgrade your kernel. I believe 2.6.32 is in [testing].

Thanks. I don't want to enable testing, but 2.6.32 should be coming soon for stable any time, right?

tavianator · 2009-12-09 04:27:58

Oh yeah right, maybe I should shy away from recommending [testing] in the Newbie Corner . But yeah, it should be in [core] pretty soon.

jlacroix · 2009-12-09 04:29:06

Cool. Whenever it hits I'll use it.

I normally don't mind testing but on my laptop I keep stable stuff because it's my lifeline when I'm traveling.

R00KIE · 2009-12-09 12:26:06

You can always download the packages and install them manually with pacman -U. Just make sure you get all the needed packages.

Arch Linux

#1 2009-12-09 02:23:30

Strange KMS Glitch

#2 2009-12-09 03:18:16

Re: Strange KMS Glitch

#3 2009-12-09 03:48:43

Re: Strange KMS Glitch

#4 2009-12-09 03:53:02

Re: Strange KMS Glitch

#5 2009-12-09 03:56:01

Re: Strange KMS Glitch

#6 2009-12-09 04:27:58

Re: Strange KMS Glitch

#7 2009-12-09 04:29:06

Re: Strange KMS Glitch

#8 2009-12-09 12:26:06

Re: Strange KMS Glitch

Board footer