Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#14223 - xrandr --off no longer working with xf86-video-intel 2.6.3

Attached to Project: Arch Linux
Opened by Jacob (Jacob_) - Monday, 13 April 2009, 22:30 GMT
Last edited by Allan McRae (Allan) - Saturday, 02 May 2009, 16:20 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To No-one
Architecture x86_64
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

I've been tracking the intel andd xorg packages through testing and since 2.6.3 I can no longer turn my laptop LVDS1 or external VGA1 off with xrandr --output LVDS1 --off etc. This was working fine a on 2.6.2, but I was probably running other versions of xorg-server and kernel.

On VGA1 the monitor stops receiving updates so its just stuck in time.
LVDS1 just keeps on running as normal.
xrandr reports each as connected but not running.

xf86-video-intel 2.6.3-3
xorg-server 1.6.0-3
kernel26 2.6.29.1-3

xorg.conf is empty (now that DVI1 is correctly detected)
I'm running KMS with i915.modeset=1
This task depends upon

Closed by  Allan McRae (Allan)
Saturday, 02 May 2009, 16:20 GMT
Reason for closing:  Fixed
Additional comments about closing:  Reported fixed in 2.7
Comment by Jan de Groot (JGC) - Tuesday, 14 April 2009, 07:04 GMT
This could be a bug with KMS. Remember that KMS is still in early stage and needs lots of improvement before it's actually usable.
Comment by Jacob (Jacob_) - Tuesday, 14 April 2009, 08:46 GMT
Just tested without i915.modeset=-1 and xrandr works correctly.

I'm not really sure how to debug this issue further, but I thought I should log it here first in-case it's arch specific.
Comment by Jan de Groot (JGC) - Tuesday, 14 April 2009, 08:49 GMT
It's a bug in the kernel i915 module. There's a lot of bugfixes going into this one upstream lately.
Comment by Jacob (Jacob_) - Tuesday, 14 April 2009, 10:16 GMT
Ok thanks, just read the queue. I guess I'll test when 2.6.29.2 is out.

Loading...