[i915gm] [i915] 'xrandr' with no arguments garbles screen

This is the output of the triggering 'xrandr' command.

And here is a bad, but hopefully better than nothing, photo of the garbled screen.

Hi Dag,

I've forwarded this bug upstream to http://bugs.freedesktop.org/show_bug.cgi?id=23112 - please subscribe to this bug in case upstream needs further information or wishes you to test something. Thanks ahead of time.

I am now on the Cc-list for the upstream bug (which was the closest I could find to be subscribed).

Hi, Dag
     Does this issue still exist when using another external monitor?
    Will you please add the modedebug option in xorg.conf and attach the xorg.log? Will you please also attach the xorg.log in UMS mode?
    Will you please also attach the vbios.dump? You can use the following command to get the vbios.dump
    echo 1 > /sys/devices/pci0000:00/0000:00:02.0/rom
    cat /sys/devices/pci0000:00/0000:00:02.0/rom >vbios.dump
    echo 0 > /sys/devices/pci0000:00/0000:00:02.0/rom

Thanks.

I will try this with another external monitor later, but I'll provide what I can. I booted in UMS mode by giving the option i915.modeset=0 on the kernel command line - this gives an errror message about an unknown option, but seems to work. I can't reproduce the bug under UMS, so this is a functioning work-around. The xorg.log-file is attached (also with Option "ModeDebug" "yes" set in the xorg.conf).

I don't know if this is related, but I get the following:

$ xrandr --output LVDS --auto --output VGA --auto --right-of LVDS
xrandr: screen cannot be larger than 2048x2048 (desired size 2880x1200)

even though I have the following in my xorg.conf:

Section "Screen"
        ...
        SubSection "Display"
                Virtual 2880 1600
        EndSubSection
EndSection

I cannot believe this is low priority. The intel chipset is fairly common and a lot of people are having issues with Xrandr and the intel driver. Please look at bug 465318: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/465318. It is marked as a duplicate of this bug. I am not sure it is, but it is related and there are tons of comments on it.

fiacobelli, the main reason that this bug has not been resolved is not low priority, but that the original reporter (Dag Asheim) has stopped responding to the intel developers who try to fix this bug. If this is going to be resolved, someone who has this problem needs to follow up in the upstream bug report.

PS: I subscribed you to this bug report so that you get updates. I assume this is what you want, but you can unsubscribe again if you would like. I see you have a new Launchpad account, so that you may not have learned this yet.

Thanks!
PS: I'd be gald to respond to the intel developers trying to fix this if
they tell me what to look for.

Francisco.

Geir Ove Myhr wrote:
> fiacobelli, the main reason that this bug has not been resolved is not
> low priority, but that the original reporter (Dag Asheim) has stopped
> responding to the intel developers who try to fix this bug. If this is
> going to be resolved, someone who has this problem needs to follow up in
> the upstream bug report.
>
> PS: I subscribed you to this bug report so that you get updates. I
> assume this is what you want, but you can unsubscribe again if you would
> like. I see you have a new Launchpad account, so that you may not have
> learned this yet.
>
> --
> [i915] 'xrandr' with no arguments garbles screen
> https://bugs.launchpad.net/bugs/408432
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in X.org xf86-video-intel: In Progress
> Status in “xserver-xorg-video-intel” package in Ubuntu: Triaged
>
> Bug description:
> Binary package hint: xserver-xorg-video-intel
>
> This is on a Dell Latitide X1 laptop, and only occurs under the following
> circumstances:
>
> 1. xorg is started
> 2. The external monitor (a Dell 2001 FP) is plugged into the VGA port
> 3. 'xrandr' is called without arguments, and instantly the screen is
> garbled - mostly black, except for a few pixels at the top of the screen
> that appears relatively normal.
>
> If step 2 is done before step 1, the screen stays normal.
>
> The bug is a regression, as earlier (Jaunty and earlier) didn't display
> this behavior.
>
> ProblemType: Bug
> Architecture: i386
> Date: Mon Aug 3 16:41:26 2009
> DistroRelease: Ubuntu 9.10
> MachineType: Dell Inc. Latitude X1
> Package: xserver-xorg-video-intel 2:2.8.0-0ubuntu1
> ProcCmdLine: root=UUID=513087c1-ebbd-4d02-bc2e-0dbc1cc68719 ro quiet
> splash
> ProcEnviron:
> LANGUAGE=nb_NO.UTF-8
> LANG=nb_NO.UTF-8
> SHELL=/bin/bash
> ProcVersionSignature: Ubuntu 2.6.31-4.23-generic
> RelatedPackageVersions:
> xserver-xorg 1:7.4+3ubuntu5
> libgl1-mesa-glx 7.5-1ubuntu1
> libdrm2 2.4.12-1ubuntu1
> xserver-xorg-video-intel 2:2.8.0-0ubuntu1
> xserver-xorg-video-ati 1:6.12.99+git20090629.f39cafc5-0ubuntu4
> SourcePackage: xserver-xorg-video-intel
> Uname: Linux 2.6.31-4-generic i686
> dmi.bios.date: 06/21/2005
> dmi.bios.vendor: Dell Inc.
> dmi.bios.version: A03
> dmi.board.name: 0G6951
> dmi.board.vendor: Dell Inc.
> dmi.chassis.type: 8
> dmi.chassis.vendor: Dell Inc.
> dmi.modalias:
> dmi:bvnDellInc.:bvrA03:bd06/21/2005:svnDellInc.:pnLatitudeX1:pvr:rvnDellInc.:rn0G6951:rvr:cvnDellInc.:ct8:cvr:
> dmi.product.name: Latitude X1
> dmi.sys.vendor: Dell Inc.
> fglrx: Not loaded
> system:
> distro: Ubuntu
> architecture: i686kernel: 2.6.31-4-generic
>
> [lspci]
> 00:02.0 VGA compatible controller [0300]: Intel Corporation Mobile
> 915GM/GMS/910GML Express Graphics Controller [8086:2592] (rev 03)
> Subsystem: Dell Device [1028:01a3]
>
>
> To unsubscribe from this bug, go to:
> https://bugs.launchpad.net/xserver-xorg-video-intel/+bug/408432/+subscribe
>

There are some patches that they would like to have tested upstream: https://bugs.freedesktop.org/show_bug.cgi?id=23112 . I can see if I can build some kernels with and without the patches for you to test. If you know how to build and patch a kernel yourself, it is even better. I'm moving to another city tomorrow, so I'm a little busy.

I have built kernel packages with linux 2.6.31-rc7 (which was the newest kernel when the tests were requested) without patches and the two patches that they requested. They can be tested in the same way as the mainline builds (see https://wiki.ubuntu.com/KernelTeam/MainlineBuilds). Please subscribe to the upstream bug report (by registering and adding yourself in the CC field) and report you findings. They may ask for other tests to be performed, possibly with newer kernels (I can help with building).
The kernel packages can be found at http://www.kvante.info/LP408432/ .

Since the original reporter of this bug isn't active anymore it may also be a good idea to file your own bug report (with ubuntu-bug xserver-xorg-video-intel`) instead of commenting on this. That way we will get your log files on your updated system instead of the original reporter's. In this case you can probably mark this bug as a duplicate of your own. It may be that the upstream developers will ask you to file your own bug report upstream.

Hi, I hope the move went well.
I tried all three kernels you built.
I am not sure which logs to look at, but here's what I did:
1. boot up with one of the kernels
2. log in (in gnome)
3. Go to System->Preferences->Display
and then all I see is a black screen with half of the cursor to the far
right. Everything freezes (keyboard and mouse) and I have to shutdown the
computer by cutting the power.

Please let me know which logs to look at. Also, I didn't understand the
steps to subscribe to the upsteram bug report (I thought I was)

Any suggestions?

Thanks!

Geir Ove Myhr wrote:
> I have built kernel packages with linux 2.6.31-rc7 (which was the newest
> kernel when the tests were requested) without patches and the two patches
> that they requested. They can be tested in the same way as the mainline
> builds (see https://wiki.ubuntu.com/KernelTeam/MainlineBuilds). Please
> subscribe to the upstream bug report (by registering and adding yourself
> in the CC field) and report you findings. They may ask for other tests to
> be performed, possibly with newer kernels (I can help with building).
> The kernel packages can be found at http://www.kvante.info/LP408432/ .
>
> Since the original reporter of this bug isn't active anymore it may also
> be a good idea to file your own bug report (with ubuntu-bug xserver-
> xorg-video-intel`) instead of commenting on this. That way we will get
> your log files on your updated system instead of the original
> reporter's. In this case you can probably mark this bug as a duplicate
> of your own. It may be that the upstream developers will ask you to file
> your own bug report upstream.
>
> --
> [i915] 'xrandr' with no arguments garbles screen
> https://bugs.launchpad.net/bugs/408432
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in X.org xf86-video-intel: In Progress
> Status in “xserver-xorg-video-intel” package in Ubuntu: Triaged
>
> Bug description:
> Binary package hint: xserver-xorg-video-intel
>
> This is on a Dell Latitide X1 laptop, and only occurs under the following
> circumstances:
>
> 1. xorg is started
> 2. The external monitor (a Dell 2001 FP) is plugged into the VGA port
> 3. 'xrandr' is called without arguments, and instantly the screen is
> garbled - mostly black, except for a few pixels at the top of the screen
> that appears relatively normal.
>
> If step 2 is done before step 1, the screen stays normal.
>
> The bug is a regression, as earlier (Jaunty and earlier) didn't display
> this behavior.
>
> ProblemType: Bug
> Architecture: i386
> Date: Mon Aug 3 16:41:26 2009
> DistroRelease: Ubuntu 9.10
> MachineType: Dell Inc. Latitude X1
> Package: xserver-xorg-video-intel 2:2.8.0-0ubuntu1
> ProcCmdLine: root=UUID=513087c1-ebbd-4d02-bc2e-0dbc1cc68719 ro quiet
> splash
> ProcEnviron:
> LANGUAGE=nb_NO.UTF-8
> LANG=nb_NO.UTF-8
> SHELL=/bin/bash
> ProcVersionSignature: Ubuntu 2.6.31-4.23-generic
> RelatedPackageVersions:
> xserver-xorg 1:7.4+3ubuntu5
> libgl1-mesa-glx 7.5-1ubuntu1
> libdrm2 2.4.12-1ubuntu1
> xserver-xorg-video-intel 2:2.8.0-0ubuntu1
> xserver-xorg-video-ati 1:6.12.99+git20090629.f39cafc5-0ubuntu4
> SourcePackage: xserver-...

In order to subscribe to the bug report at bugs.freedesktop.org you first need an account. Go to https://bugs.freedesktop.org/ and click "Open a new FreeDesktop Bugzilla account". Only then can you add your email address to the CC field of the bug report.

The logs that I think are useful with all the three kernels are:
- the file generated from `dmesg >Dmesg.txt`
- the file /var/log/Xorg.0.log
- the file generated from `lspci -vvnn >Lscpi.txt`
- the file generated from `sudo intel_reg_dumper > Regdump.txt` (You will need one of the packages xserver-xorg-video-intel-dbg or intel-gpu-tools for this, depending on the ubuntu version.)

I think the best option is if you file a new bug report with the `ubuntu-bug` command, describe exactly what your setup, what you do and what you observe, mention this bug report and upload the files I described above. It is best if you do this with Lucid, which is the current development version of Ubuntu, since there has been a lot of changes since the software that is currently in Karmic was written.

And when you test, could you use the command `xrandr` instead of going to System->Preferences->Display. It should do the same, but removes a possible source of errors. The log files should be taken _after_ the screen has gone black if possible. To do that you need to have openssh-server installed and ssh in from another computer, since it is obviously hard to do anything with a garbled screen.

Dag, upstream closed your bug report due to lack of response to their questions. If you're still having this bug, and can reproduce it on lucid, please re-open the upstream bug report at https://bugs.freedesktop.org/show_bug.cgi?id=23112 and provide further comment there.