Skip to contentSkip to conversation

enabling kms for i915 disables brightness control and xrandr

DISCUSSION Soeren Sonnenburg 4 participants 10 messages Mar 29, 2009 – Mar 31, 2009

lore
Share & tools
lore
#0 lore raw

Dear all,

I am not sure if this is just a user error/ too old userspace problem, but I recognized that when I enable kernel based modesetting on a intel 945 based samsung nc 10 netbook, I loose brightness control from within X and X resolutions are wrong (instead of 1024x600 it is 1024x1024) and xrandr does no longer have the all the modelines ranging from 1024x600 to 640x350... Trying to change resolutions / setting the brightness via xrandr results in error messages being printed.

Furthermore, this same flag disables Xv support..

However, screen switches between terminal and X are quite fast now (without any flicker) and suspend and everything works stably.

I recognized that I can set the brightness via

setpci -s 00:02.1 F4.B=XX

(XX ranging from 00 to FF) just fine...

I am attaching the .config .

Any ideas?
Soeren

Signature · 2 lines
For the one fact about the future of which we can be certain is that it
will be utterly fantastic. -- Arthur C. Clarke, 1962
#1 lore raw
Quoted 2 lines · Soeren Sonnenburg

I am not sure if this is just a user error/ too old userspace problem,

Which version of X intel driver are you running?
http://lkml.org/lkml/2009/2/27/363 suggests you will have unsupported problems unless it is 2.6.2 or higher...

Signature · 1 line
Sitsofe | http://sucs.org/~sits/
#2 lore raw
Quoted 7 lines · Sitsofe Wheeler
Quoted 2 lines · Soeren Sonnenburg

I am not sure if this is just a user error/ too old userspace problem,

Which version of X intel driver are you running?
http://lkml.org/lkml/2009/2/27/363 suggests you will have unsupported problems unless it is 2.6.2 or higher...

Using 2.6.3 things became a lot faster with UXA, but the brightness (only possible to set via setpci) and xrandr problems (modes missing) are still there...

Soeren

Signature · 2 lines
For the one fact about the future of which we can be certain is that it
will be utterly fantastic. -- Arthur C. Clarke, 1962
#4 lore raw
In reply to Soeren Sonnenburg

(CC'ing dri-devel, Eric Anholt and Jesse Barnes)

Quoted 3 lines · Soeren Sonnenburg

Dear all,

I am not sure if this is just a user error/ too old userspace problem,

[User stated that 2.6.3 intel driver is being used in another email]

Quoted 22 lines

but I recognized that when I enable kernel based modesetting on a intel 945 based samsung nc 10 netbook, I loose brightness control from within X and X resolutions are wrong (instead of 1024x600 it is 1024x1024) and xrandr does no longer have the all the modelines ranging from 1024x600 to 640x350... Trying to change resolutions / setting the brightness via xrandr results in error messages being printed.

Furthermore, this same flag disables Xv support..

However, screen switches between terminal and X are quite fast now (without any flicker) and suspend and everything works stably.

I recognized that I can set the brightness via

setpci -s 00:02.1 F4.B=XX

(XX ranging from 00 to FF) just fine...

I am attaching the .config .

Any ideas?
Soeren

Signature · 1 line
Sitsofe | http://sucs.org/~sits/
#5 lore raw
Quoted 8 lines · Sitsofe Wheeler

(CC'ing dri-devel, Eric Anholt and Jesse Barnes)

Quoted 3 lines · Soeren Sonnenburg

Dear all,

I am not sure if this is just a user error/ too old userspace problem,

[User stated that 2.6.3 intel driver is being used in another email]

Just to not cause any (further?) confusion, I was using 2.6.1 when I wrote that email and after compiling/upgrading to 2.6.3 a number of problems vanished (like Xv works, screen resolution is correct, things are *a lot* faster with UXA). However, brightness still only works via setpci and xrandr only shows the 1024x600 modeline.

Quoted 9 lines
Quoted 9 lines

but I recognized that when I enable kernel based modesetting on a intel 945 based samsung nc 10 netbook, I loose brightness control from within X and X resolutions are wrong (instead of 1024x600 it is 1024x1024) and xrandr does no longer have the all the modelines ranging from 1024x600 to 640x350... Trying to change resolutions / setting the brightness via xrandr results in error messages being printed.

Furthermore, this same flag disables Xv support..

Quoted 8 lines
Quoted 8 lines

However, screen switches between terminal and X are quite fast now (without any flicker) and suspend and everything works stably.

I recognized that I can set the brightness via

setpci -s 00:02.1 F4.B=XX

(XX ranging from 00 to FF) just fine...

Soeren.

Signature · 2 lines
For the one fact about the future of which we can be certain is that it
will be utterly fantastic. -- Arthur C. Clarke, 1962
#6 lore raw
Quoted 8 lines · Soeren Sonnenburg
Quoted 7 lines · Sitsofe Wheeler

(CC'ing dri-devel, Eric Anholt and Jesse Barnes)

Quoted 3 lines · Soeren Sonnenburg

Dear all,

I am not sure if this is just a user error/ too old userspace problem,

Quoted 25 lines
Quoted 1 line

[User stated that 2.6.3 intel driver is being used in another email]

Just to not cause any (further?) confusion, I was using 2.6.1 when I wrote that email and after compiling/upgrading to 2.6.3 a number of problems vanished (like Xv works, screen resolution is correct, things are *a lot* faster with UXA). However, brightness still only works via setpci and xrandr only shows the 1024x600 modeline.

Quoted 17 lines
Quoted 17 lines

but I recognized that when I enable kernel based modesetting on a intel 945 based samsung nc 10 netbook, I loose brightness control from within X and X resolutions are wrong (instead of 1024x600 it is 1024x1024) and xrandr does no longer have the all the modelines ranging from 1024x600 to 640x350... Trying to change resolutions / setting the brightness via xrandr results in error messages being printed.

Furthermore, this same flag disables Xv support..

However, screen switches between terminal and X are quite fast now (without any flicker) and suspend and everything works stably.

I recognized that I can set the brightness via

setpci -s 00:02.1 F4.B=XX

(XX ranging from 00 to FF) just fine...

One more thing: Connecting an external display I could turn it on via xrandr --auto successfully. However, it was not possible to turn the internal display off (xrandr --output LVDS1 --off) and switching to the console with the external display connected I managed to freeze the machine. Turning the external display off worked somehow (the display then showed vertical stripes) but I could switch to console.

Soeren.

Signature · 2 lines
For the one fact about the future of which we can be certain is that it
will be utterly fantastic. -- Arthur C. Clarke, 1962
#7 lore raw
Quoted 37 lines · On Mon, 30 Mar 2009 15:37:19 +0200 Soeren Sonnenburg <[email protected]> wrote:
Quoted 36 lines · Soeren Sonnenburg
Quoted 10 lines · Sitsofe Wheeler

(CC'ing dri-devel, Eric Anholt and Jesse Barnes)

Quoted 4 lines · Soeren Sonnenburg

Dear all,

I am not sure if this is just a user error/ too old userspace problem,

[User stated that 2.6.3 intel driver is being used in another email]

Just to not cause any (further?) confusion, I was using 2.6.1 when I wrote that email and after compiling/upgrading to 2.6.3 a number of problems vanished (like Xv works, screen resolution is correct, things are *a lot* faster with UXA). However, brightness still only works via setpci and xrandr only shows the 1024x600 modeline.

Quoted 18 lines
Quoted 18 lines

but I recognized that when I enable kernel based modesetting on a intel 945 based samsung nc 10 netbook, I loose brightness control from within X and X resolutions are wrong (instead of 1024x600 it is 1024x1024) and xrandr does no longer have the all the modelines ranging from 1024x600 to 640x350... Trying to change resolutions / setting the brightness via xrandr results in error messages being printed.

Furthermore, this same flag disables Xv support..

However, screen switches between terminal and X are quite fast now (without any flicker) and suspend and everything works stably.

I recognized that I can set the brightness via

setpci -s 00:02.1 F4.B=XX

Quoted 8 lines
Quoted 1 line
Quoted 1 line
Quoted 1 line

(XX ranging from 00 to FF) just fine...

One more thing: Connecting an external display I could turn it on via xrandr --auto successfully. However, it was not possible to turn the internal display off (xrandr --output LVDS1 --off) and switching to the console with the external display connected I managed to freeze the machine. Turning the external display off worked somehow (the display then showed vertical stripes) but I could switch to console.

Have you filed bugs for these problems? I think the brightness control issue is due to some missing bits on the 2D side (we don't enable backlight property control when KMS is active, but should), the other issues sound like bugs.

Signature · 1 line
Jesse Barnes, Intel Open Source Technology Center
#8 lore raw
Quoted 49 lines · Jesse Barnes
Quoted 37 lines · On Mon, 30 Mar 2009 15:37:19 +0200 Soeren Sonnenburg <[email protected]> wrote:
Quoted 36 lines · Soeren Sonnenburg
Quoted 10 lines · Sitsofe Wheeler

(CC'ing dri-devel, Eric Anholt and Jesse Barnes)

Quoted 4 lines · Soeren Sonnenburg

Dear all,

I am not sure if this is just a user error/ too old userspace problem,

[User stated that 2.6.3 intel driver is being used in another email]

Just to not cause any (further?) confusion, I was using 2.6.1 when I wrote that email and after compiling/upgrading to 2.6.3 a number of problems vanished (like Xv works, screen resolution is correct, things are *a lot* faster with UXA). However, brightness still only works via setpci and xrandr only shows the 1024x600 modeline.

Quoted 18 lines
Quoted 18 lines

but I recognized that when I enable kernel based modesetting on a intel 945 based samsung nc 10 netbook, I loose brightness control from within X and X resolutions are wrong (instead of 1024x600 it is 1024x1024) and xrandr does no longer have the all the modelines ranging from 1024x600 to 640x350... Trying to change resolutions / setting the brightness via xrandr results in error messages being printed.

Furthermore, this same flag disables Xv support..

However, screen switches between terminal and X are quite fast now (without any flicker) and suspend and everything works stably.

I recognized that I can set the brightness via

setpci -s 00:02.1 F4.B=XX

Quoted 8 lines
Quoted 1 line
Quoted 1 line
Quoted 1 line

(XX ranging from 00 to FF) just fine...

One more thing: Connecting an external display I could turn it on via xrandr --auto successfully. However, it was not possible to turn the internal display off (xrandr --output LVDS1 --off) and switching to the console with the external display connected I managed to freeze the machine. Turning the external display off worked somehow (the display then showed vertical stripes) but I could switch to console.

Quoted 4 lines

Have you filed bugs for these problems? I think the brightness control issue is due to some missing bits on the 2D side (we don't enable backlight property control when KMS is active, but should), the other issues sound like bugs.

I did nothing besides asking here on lkml. Where should I report what?

Soeren

Signature · 2 lines
For the one fact about the future of which we can be certain is that it
will be utterly fantastic. -- Arthur C. Clarke, 1962
#9 lore raw
Quoted 54 lines · On Tue, 31 Mar 2009 00:57:50 +0200 Soeren Sonnenburg <[email protected]> wrote:
Quoted 53 lines · Jesse Barnes
Quoted 49 lines · On Mon, 30 Mar 2009 15:37:19 +0200 Soeren Sonnenburg <[email protected]> wrote:
Quoted 13 lines · Soeren Sonnenburg
Quoted 11 lines · Sitsofe Wheeler

(CC'ing dri-devel, Eric Anholt and Jesse Barnes)

Quoted 4 lines · Soeren Sonnenburg

Dear all,

I am not sure if this is just a user error/ too old userspace problem,

[User stated that 2.6.3 intel driver is being used in another email]

Quoted 27 lines

Just to not cause any (further?) confusion, I was using 2.6.1 when I wrote that email and after compiling/upgrading to 2.6.3 a number of problems vanished (like Xv works, screen resolution is correct, things are *a lot* faster with UXA). However, brightness still only works via setpci and xrandr only shows the 1024x600 modeline.

Quoted 20 lines
Quoted 20 lines

but I recognized that when I enable kernel based modesetting on a intel 945 based samsung nc 10 netbook, I loose brightness control from within X and X resolutions are wrong (instead of 1024x600 it is 1024x1024) and xrandr does no longer have the all the modelines ranging from 1024x600 to 640x350... Trying to change resolutions / setting the brightness via xrandr results in error messages being printed.

Furthermore, this same flag disables Xv support..

However, screen switches between terminal and X are quite fast now (without any flicker) and suspend and everything works stably.

I recognized that I can set the brightness via

setpci -s 00:02.1 F4.B=XX

(XX ranging from 00 to FF) just fine...

One more thing: Connecting an external display I could turn it on via xrandr --auto successfully. However, it was not possible to turn the internal display off (xrandr --output LVDS1 --off) and switching to the console with the external display connected I managed to freeze the machine. Turning the external display off worked somehow (the display then showed vertical stripes) but I could switch to console.

Quoted 6 lines
Quoted 4 lines

Have you filed bugs for these problems? I think the brightness control issue is due to some missing bits on the 2D side (we don't enable backlight property control when KMS is active, but should), the other issues sound like bugs.

I did nothing besides asking here on lkml. Where should I report what?

Your xrandr problems should be reported at bugs.freedesktop.org against the xf86-video-intel driver (in the xorg component). A separate bug report should be filed for the missing backlight property.

Thanks,

Signature · 1 line
Jesse Barnes, Intel Open Source Technology Center
#3 lore raw
In reply to Soeren Sonnenburg
Quoted 5 lines · Soeren Sonnenburg
Quoted 4 lines · Sitsofe Wheeler
Quoted 2 lines · Soeren Sonnenburg

I am not sure if this is just a user error/ too old userspace problem,

Quoted 7 lines
Quoted 3 lines

Which version of X intel driver are you running?
http://lkml.org/lkml/2009/2/27/363 suggests you will have unsupported problems unless it is 2.6.2 or higher...

Using 2.6.3 things became a lot faster with UXA, but the brightness (only possible to set via setpci) and xrandr problems (modes missing) are still there...

KMS property control in the 2D driver was introduced recently, and should be in 2.7, think.

Signature · 2 lines
Eric Anholt
[email protected]                         [email protected]