Bug#561021: KMS retaining information that it shouldn't have
On Sat, 19 Dec 2009, Wouter Verhelst wrote: When I run 'xrandr' without arguments, it still only shows the supported resolutions of the original monitor, rather than those of the monitor that I'm connected to at that point. is this reproducible with 2.6.32-8 latest sid and how about that xorg log? thanks for feedback. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#561021: KMS retaining information that it shouldn't have
On Sat, Dec 19, 2009 at 03:32:58PM +0100, Wouter Verhelst wrote: Hi, On Sun, Dec 13, 2009 at 09:28:09PM +0100, Bastian Blank wrote: On Sun, Dec 13, 2009 at 08:12:41PM +0100, Wouter Verhelst wrote: Package: linux-2.6 Version: 2.6.31-2 This is not the latest version, please update. That's today, after an 'apt-get update'. I don't think so. Yes, there is, I uploaded it myself. | $ apt-cache policy linux-image-2.6.32-trunk-amd64 | linux-image-2.6.32-trunk-amd64: | Installed: (none) | Candidate: 2.6.32-2 | Version table: | 2.6.32-2 0 | 500 http://debian.waldi.eu.org sid/main Packages | 500 http://ftp.de.debian.org sid/main Packages When I run 'xrandr' without arguments, it still only shows the supported resolutions of the original monitor, rather than those of the monitor that I'm connected to at that point. xorg log? Bastian -- If I can have honesty, it's easier to overlook mistakes. -- Kirk, Space Seed, stardate 3141.9 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#561021: KMS retaining information that it shouldn't have
Hi, On Sun, Dec 13, 2009 at 09:28:09PM +0100, Bastian Blank wrote: On Sun, Dec 13, 2009 at 08:12:41PM +0100, Wouter Verhelst wrote: Package: linux-2.6 Version: 2.6.31-2 This is not the latest version, please update. wou...@celtic:~$ LC_ALL=C apt-cache policy linux-image-$(uname -r) linux-image-2.6.31-1-amd64: Installed: 2.6.31-2 Candidate: 2.6.31-2 Version table: *** 2.6.31-2 0 500 http://apt-cacher.grep.be unstable/main Packages 500 http://ftp.be.debian.org unstable/main Packages 100 /var/lib/dpkg/status That's today, after an 'apt-get update'. I don't think so. However, when trying to use xrandr to move the resolution to the native output resolution of that second monitor, I found that I could not do so; instead, the system refused to go beyond the resolution which the TV had in its EDID data. Additionally, the 1330xsomething resolution supported by the TV, while supported by the monitor, is not actually shown in its EDID data (at least not after a reboot). What is the output of xrandr? How does it refuse to move the resolution? When I run 'xrandr' without arguments, it still only shows the supported resolutions of the original monitor, rather than those of the monitor that I'm connected to at that point. -- The biometric identification system at the gates of the CIA headquarters works because there's a guard with a large gun making sure no one is trying to fool the system. http://www.schneier.com/blog/archives/2009/01/biometrics.html -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#561021: KMS retaining information that it shouldn't have
Package: linux-2.6 Version: 2.6.31-2 Severity: normal Hi, I'm using kernel mode setting on my system. Yesterday, I had connected my laptop to my TV (an LCD TV with VGA input) to watch a movie. The resolution on that TV is not exactly huge, though good enough; it's a 1330xsomething IIRC (a 16:9 aspect ratio). Today, I needed to do some work, so took the laptop downstairs to the office, where I connected it to my monitor there (which has a 16:10 aspect ratio and can do up to 1920x1200). However, when trying to use xrandr to move the resolution to the native output resolution of that second monitor, I found that I could not do so; instead, the system refused to go beyond the resolution which the TV had in its EDID data. Additionally, the 1330xsomething resolution supported by the TV, while supported by the monitor, is not actually shown in its EDID data (at least not after a reboot). I suspect this is a bug in the kernel, because: - I have done this successfully in the past, before I enabled KMS - Rebooting fixed the problem, while restarting the X server did not however, if you have evidence to the contrary, feel free to reassign. -- Package-specific info: ** Version: Linux version 2.6.31-1-amd64 (Debian 2.6.31-2) (b...@decadent.org.uk) (gcc version 4.3.4 (Debian 4.3.4-6) ) #1 SMP Mon Nov 16 04:44:38 UTC 2009 ** Command line: BOOT_IMAGE=/boot/vmlinuz-2.6.31-1-amd64 root=UUID=acdf54ed-d8be-4533-a9c6-5a66d77fb0e3 ro quiet ** Tainted: W (512) * Taint on warning. ** Kernel log: [ 125.803075] i915 :00:02.0: DVI-D-1: no EDID data [ 125.807563] i2c-adapter i2c-2: unable to read EDID block. [ 125.807565] i915 :00:02.0: DVI-D-1: no EDID data [ 126.385308] i2c-adapter i2c-2: unable to read EDID block. [ 126.385313] i915 :00:02.0: DVI-D-1: no EDID data [ 126.389853] i2c-adapter i2c-2: unable to read EDID block. [ 126.389855] i915 :00:02.0: DVI-D-1: no EDID data [ 126.626565] i2c-adapter i2c-2: unable to read EDID block. [ 126.626571] i915 :00:02.0: DVI-D-1: no EDID data [ 126.631092] i2c-adapter i2c-2: unable to read EDID block. [ 126.631095] i915 :00:02.0: DVI-D-1: no EDID data [ 126.856349] i2c-adapter i2c-2: unable to read EDID block. [ 126.856352] i915 :00:02.0: DVI-D-1: no EDID data [ 126.860774] i2c-adapter i2c-2: unable to read EDID block. [ 126.860777] i915 :00:02.0: DVI-D-1: no EDID data [ 173.705358] sky2 eth0: enabling interface [ 173.706209] ADDRCONF(NETDEV_UP): eth0: link is not ready [ 175.516299] sky2 eth0: Link is up at 100 Mbps, full duplex, flow control both [ 175.517147] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready [ 177.397899] i2c-adapter i2c-2: unable to read EDID block. [ 177.397903] i915 :00:02.0: DVI-D-1: no EDID data [ 177.402513] i2c-adapter i2c-2: unable to read EDID block. [ 177.402517] i915 :00:02.0: DVI-D-1: no EDID data [ 177.639278] i2c-adapter i2c-2: unable to read EDID block. [ 177.639282] i915 :00:02.0: DVI-D-1: no EDID data [ 177.643721] i2c-adapter i2c-2: unable to read EDID block. [ 177.643724] i915 :00:02.0: DVI-D-1: no EDID data [ 177.876590] i2c-adapter i2c-2: unable to read EDID block. [ 177.876595] i915 :00:02.0: DVI-D-1: no EDID data [ 177.881036] i2c-adapter i2c-2: unable to read EDID block. [ 177.881039] i915 :00:02.0: DVI-D-1: no EDID data [ 178.108279] i2c-adapter i2c-2: unable to read EDID block. [ 178.108285] i915 :00:02.0: DVI-D-1: no EDID data [ 178.112714] i2c-adapter i2c-2: unable to read EDID block. [ 178.112718] i915 :00:02.0: DVI-D-1: no EDID data [ 178.338099] i2c-adapter i2c-2: unable to read EDID block. [ 178.338104] i915 :00:02.0: DVI-D-1: no EDID data [ 178.342542] i2c-adapter i2c-2: unable to read EDID block. [ 178.342545] i915 :00:02.0: DVI-D-1: no EDID data [ 178.574927] i2c-adapter i2c-2: unable to read EDID block. [ 178.574931] i915 :00:02.0: DVI-D-1: no EDID data [ 178.579379] i2c-adapter i2c-2: unable to read EDID block. [ 178.579382] i915 :00:02.0: DVI-D-1: no EDID data [ 178.807658] i2c-adapter i2c-2: unable to read EDID block. [ 178.807662] i915 :00:02.0: DVI-D-1: no EDID data [ 178.812200] i2c-adapter i2c-2: unable to read EDID block. [ 178.812203] i915 :00:02.0: DVI-D-1: no EDID data [ 179.036723] i2c-adapter i2c-2: unable to read EDID block. [ 179.036727] i915 :00:02.0: DVI-D-1: no EDID data [ 179.041310] i2c-adapter i2c-2: unable to read EDID block. [ 179.041313] i915 :00:02.0: DVI-D-1: no EDID data [ 179.281522] i2c-adapter i2c-2: unable to read EDID block. [ 179.281526] i915 :00:02.0: DVI-D-1: no EDID data [ 179.286009] i2c-adapter i2c-2: unable to read EDID block. [ 179.286012] i915 :00:02.0: DVI-D-1: no EDID data [ 179.527018] i2c-adapter i2c-2: unable to read EDID block. [ 179.527022] i915 :00:02.0: DVI-D-1: no EDID data [ 179.531505] i2c-adapter i2c-2: unable to read EDID block. [ 179.531507] i915 :00:02.0: DVI-D-1: no EDID data [ 179.879092]
Bug#561021: KMS retaining information that it shouldn't have
On Sun, Dec 13, 2009 at 08:12:41PM +0100, Wouter Verhelst wrote: Package: linux-2.6 Version: 2.6.31-2 This is not the latest version, please update. However, when trying to use xrandr to move the resolution to the native output resolution of that second monitor, I found that I could not do so; instead, the system refused to go beyond the resolution which the TV had in its EDID data. Additionally, the 1330xsomething resolution supported by the TV, while supported by the monitor, is not actually shown in its EDID data (at least not after a reboot). What is the output of xrandr? How does it refuse to move the resolution? Bastian -- Worlds are conquered, galaxies destroyed -- but a woman is always a woman. -- Kirk, The Conscience of the King, stardate 2818.9 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
