kernel: [...] i915 0000:00:02.0: LVDS-1: EDID invalid.

Bug #575985 reported by Jan
124
This bug affects 46 people
Affects Status Importance Assigned to Milestone
xf86-video-intel
Fix Released
Medium
xdiagnose (Ubuntu)
Fix Released
Medium
Unassigned

Bug Description

During boot my screen goes blank. Instead of a normal plymouth screen I see something like this:

[drm:edid_is_valid] *ERROR* Raw EDID
[drm:edid_is_valid] *ERROR* Raw EDID
[drm:edid_is_valid] *ERROR* Raw EDID

this might be a problem with intel's i915 chipset. This bug comes new with 10.04 - it never appeared with ubuntu 9.10.

kern.log (examples):
----------
 May 5 20:30:00 jan-vaio-vgn-tz31-vn kernel: [ 700.891251] [drm:edid_is_valid] *ERROR* Raw EDID:
May 5 20:30:00 jan-vaio-vgn-tz31-vn kernel: [ 700.891261] <3>00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
May 5 20:30:00 jan-vaio-vgn-tz31-vn kernel: [ 700.891264] <3>00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
May 5 20:30:00 jan-vaio-vgn-tz31-vn kernel: [ 700.891268] <3>00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
May 5 20:30:00 jan-vaio-vgn-tz31-vn kernel: [ 700.891271] <3>00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
May 5 20:30:00 jan-vaio-vgn-tz31-vn kernel: [ 700.891274] <3>00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
May 5 20:30:00 jan-vaio-vgn-tz31-vn kernel: [ 700.891277] <3>00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
May 5 20:30:00 jan-vaio-vgn-tz31-vn kernel: [ 700.891280] <3>00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
May 5 20:30:00 jan-vaio-vgn-tz31-vn kernel: [ 700.891283] <3>00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
May 5 20:30:00 jan-vaio-vgn-tz31-vn kernel: [ 700.891286]
May 5 20:30:01 jan-vaio-vgn-tz31-vn kernel: [ 701.261392] [drm:edid_is_valid] *ERROR* Raw EDID:
May 5 20:30:01 jan-vaio-vgn-tz31-vn kernel: [ 701.261400] <3>00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
May 5 20:30:01 jan-vaio-vgn-tz31-vn kernel: [ 701.261404] <3>00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
May 5 20:30:01 jan-vaio-vgn-tz31-vn kernel: [ 701.261407] <3>00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
May 5 20:30:01 jan-vaio-vgn-tz31-vn kernel: [ 701.261410] <3>00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
May 5 20:30:01 jan-vaio-vgn-tz31-vn kernel: [ 701.261414] <3>00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
May 5 20:30:01 jan-vaio-vgn-tz31-vn kernel: [ 701.261417] <3>00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
May 5 20:30:01 jan-vaio-vgn-tz31-vn kernel: [ 701.261420] <3>00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
May 5 20:30:01 jan-vaio-vgn-tz31-vn kernel: [ 701.261423] <3>00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
May 5 20:30:01 jan-vaio-vgn-tz31-vn kernel: [ 701.261426]
May 5 20:30:01 jan-vaio-vgn-tz31-vn kernel: [ 701.629793] [drm:edid_is_valid] *ERROR* Raw EDID:
May 5 20:30:01 jan-vaio-vgn-tz31-vn kernel: [ 701.629802] <3>00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
May 5 20:30:01 jan-vaio-vgn-tz31-vn kernel: [ 701.629805] <3>00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
May 5 20:30:01 jan-vaio-vgn-tz31-vn kernel: [ 701.629809] <3>00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
May 5 20:30:01 jan-vaio-vgn-tz31-vn kernel: [ 701.629812] <3>00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
May 5 20:30:01 jan-vaio-vgn-tz31-vn kernel: [ 701.629815] <3>00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
May 5 20:30:01 jan-vaio-vgn-tz31-vn kernel: [ 701.629818] <3>00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
May 5 20:30:01 jan-vaio-vgn-tz31-vn kernel: [ 701.629821] <3>00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
May 5 20:30:01 jan-vaio-vgn-tz31-vn kernel: [ 701.629824] <3>00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
May 5 20:30:01 jan-vaio-vgn-tz31-vn kernel: [ 701.629827]
May 5 20:30:01 jan-vaio-vgn-tz31-vn kernel: [ 701.996977] [drm:edid_is_valid] *ERROR* Raw EDID:
May 5 20:30:01 jan-vaio-vgn-tz31-vn kernel: [ 701.996984] <3>00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
May 5 20:30:01 jan-vaio-vgn-tz31-vn kernel: [ 701.996987] <3>00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
May 5 20:30:01 jan-vaio-vgn-tz31-vn kernel: [ 701.996991] <3>00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
May 5 20:30:01 jan-vaio-vgn-tz31-vn kernel: [ 701.996994] <3>00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
May 5 20:30:01 jan-vaio-vgn-tz31-vn kernel: [ 701.996997] <3>00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
May 5 20:30:01 jan-vaio-vgn-tz31-vn kernel: [ 701.997000] <3>00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
May 5 20:30:01 jan-vaio-vgn-tz31-vn kernel: [ 701.997003] <3>00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
May 5 20:30:01 jan-vaio-vgn-tz31-vn kernel: [ 701.997006] <3>00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
May 5 20:30:01 jan-vaio-vgn-tz31-vn kernel: [ 701.997009]
May 5 20:30:01 jan-vaio-vgn-tz31-vn kernel: [ 701.997014] i915 0000:00:02.0: LVDS-1: EDID invalid.

ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: linux-image-2.6.32-22-generic 2.6.32-22.33
Regression: Yes
Reproducible: No
ProcVersionSignature: Ubuntu 2.6.32-22.33-generic 2.6.32.11+drm33.2
Uname: Linux 2.6.32-22-generic x86_64
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21.
AplayDevices:
 **** List of PLAYBACK Hardware Devices ****
 card 0: Intel [HDA Intel], device 0: ALC262 Analog [ALC262 Analog]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
Architecture: amd64
ArecordDevices:
 **** List of CAPTURE Hardware Devices ****
 card 0: Intel [HDA Intel], device 0: ALC262 Analog [ALC262 Analog]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: jan 1355 F.... pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'Intel'/'HDA Intel at 0xfc540000 irq 19'
   Mixer name : 'Realtek ALC262'
   Components : 'HDA:10ec0262,104d1f00,00100100 HDA:14f12c06,104d1700,00100000'
   Controls : 18
   Simple ctrls : 11
Date: Wed May 5 21:28:55 2010
Frequency: Once a day.
HibernationDevice: RESUME=UUID=ad91734c-7a91-4f0b-9ce9-00a231f658c5
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429)
MachineType: Sony Corporation VGN-TZ31VN_X
PccardctlIdent:
 Socket 0:
   no product info available
PccardctlStatus:
 Socket 0:
   no card
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-22-generic root=UUID=a161045e-563e-4161-8fd0-0a2ca9bc14cd ro quiet splash
ProcEnviron:
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
RelatedPackageVersions: linux-firmware 1.34
SourcePackage: linux
StagingDrivers: phison
Title: [STAGING]
dmi.bios.date: 02/07/2008
dmi.bios.vendor: Phoenix Technologies LTD
dmi.bios.version: R0091N7
dmi.board.asset.tag: N/A
dmi.board.name: VAIO
dmi.board.vendor: Sony Corporation
dmi.board.version: N/A
dmi.chassis.type: 10
dmi.chassis.vendor: Sony Corporation
dmi.chassis.version: N/A
dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvrR0091N7:bd02/07/2008:svnSonyCorporation:pnVGN-TZ31VN_X:pvrJ003AHVP:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A:
dmi.product.name: VGN-TZ31VN_X
dmi.product.version: J003AHVP
dmi.sys.vendor: Sony Corporation

Revision history for this message
In , Bartosz Fenski (fenio) wrote :

Created an attachment (id=33013)
vbios.dump

Revision history for this message
In , Jesse Barnes (jbarnes-virtuousgeek) wrote :

Not sure what the bug is here, reassigning to Yakui. Invalid EDIDs can be due to bad timing on the kernel side, flakey hardware or cables, or a real bad EDID in the monitor.

Revision history for this message
In , Bartosz Fenski (fenio) wrote :

It's notebook Sony Vaio VGN-C2S_L, so I suppose it's bad EDID, and not cables ;)

Revision history for this message
In , yakuizhao (yakui-zhao) wrote :

(In reply to comment #3)
> It's notebook Sony Vaio VGN-C2S_L, so I suppose it's bad EDID, and not cables
> ;)

Will you please add the boot option of "drm.debug=0x04" and attach the output of dmesg?

Thanks.
   Yakui
>

Revision history for this message
In , Bartosz Fenski (fenio) wrote :

Created an attachment (id=33144)
dmesg with drm.debug=0x04

Here goes dmesg with drm.debug=0x04 option.

Revision history for this message
In , yakuizhao (yakui-zhao) wrote :

Created an attachment (id=33189)
Ignore the LVDS edid when it is unavailable or invalid

Will you please try the attached patch and see whether it frequently reports the following similar message?
     >i915 0000:00:02.0: LVDS-1: EDID invalid.

thanks.

Revision history for this message
In , Bartosz Fenski (fenio) wrote :

Now it only reports:

[ 23.903220] [drm] Initialized drm 1.1.0 20060810
[ 23.908682] i915: no symbol version for module_layout
[ 23.932410] i915: no symbol version for module_layout

(no symbol version probably due to my way of compilation).

Does this ignoring LVDS can make some problems or is it safe?

Revision history for this message
In , Bartosz Fenski (fenio) wrote :

Since that change my X.org eats many CPU, and everything is working extremely slow.

At least I'm finally able to run Enemy-territory game, but it works so slow, that I have to try to select proper option to be able to exit from the game.
Before that patch I wasn't able to even run it (signal 11).

Seems there's something wrong with hardware acceleration after that patch.

Is there something else I can provide you to resolve these issues?

regards
fEnIo

Revision history for this message
In , yakuizhao (yakui-zhao) wrote :

Created an attachment (id=33484)
try the debug patch that the LVDS edid when it is unavailable or invalid

will you please try the updated patch and see whether it can work for you?

thanks.

Revision history for this message
In , yakuizhao (yakui-zhao) wrote :

(In reply to comment #8)
> Since that change my X.org eats many CPU, and everything is working extremely
> slow.
>
> At least I'm finally able to run Enemy-territory game, but it works so slow,
> that I have to try to select proper option to be able to exit from the game.
> Before that patch I wasn't able to even run it (signal 11).

It seems that the slow issue is not related with this bug. And from the log it seems that the xorg will query the status of every possible outputs periodically.

Can you provide the info of "cat /proc/interrupts"?

Thanks.

>
> Seems there's something wrong with hardware acceleration after that patch.
>
> Is there something else I can provide you to resolve these issues?
>
> regards
> fEnIo
>

Revision history for this message
In , yakuizhao (yakui-zhao) wrote :

Now the corresponding patch is already shipped. And after the patch is applied, it can avoid the warning message of "drm:edid_is_valid" perodically.

commit bfac4d6725baacbfc085c38e231b8582a1b8f62b
Author: Zhao Yakui <email address hidden>
Date: Wed Apr 7 17:11:22 2010 +0800

    drm/i915: Ignore LVDS EDID when it is unavailabe or invalid

So this bug will be marked as resolved.

Thanks.

Revision history for this message
Jan (jan-timo-henrich-deactivatedaccount) wrote :
Download full text (7.3 KiB)

During boot my screen goes blank. Instead of a normal plymouth screen I see something like this:

[drm:edid_is_valid] *ERROR* Raw EDID
[drm:edid_is_valid] *ERROR* Raw EDID
[drm:edid_is_valid] *ERROR* Raw EDID

this might be a problem with intel's i915 chipset. This bug comes new with 10.04 - it never appeared with ubuntu 9.10.

kern.log (examples):
----------
 May 5 20:30:00 jan-vaio-vgn-tz31-vn kernel: [ 700.891251] [drm:edid_is_valid] *ERROR* Raw EDID:
May 5 20:30:00 jan-vaio-vgn-tz31-vn kernel: [ 700.891261] <3>00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
May 5 20:30:00 jan-vaio-vgn-tz31-vn kernel: [ 700.891264] <3>00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
May 5 20:30:00 jan-vaio-vgn-tz31-vn kernel: [ 700.891268] <3>00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
May 5 20:30:00 jan-vaio-vgn-tz31-vn kernel: [ 700.891271] <3>00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
May 5 20:30:00 jan-vaio-vgn-tz31-vn kernel: [ 700.891274] <3>00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
May 5 20:30:00 jan-vaio-vgn-tz31-vn kernel: [ 700.891277] <3>00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
May 5 20:30:00 jan-vaio-vgn-tz31-vn kernel: [ 700.891280] <3>00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
May 5 20:30:00 jan-vaio-vgn-tz31-vn kernel: [ 700.891283] <3>00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
May 5 20:30:00 jan-vaio-vgn-tz31-vn kernel: [ 700.891286]
May 5 20:30:01 jan-vaio-vgn-tz31-vn kernel: [ 701.261392] [drm:edid_is_valid] *ERROR* Raw EDID:
May 5 20:30:01 jan-vaio-vgn-tz31-vn kernel: [ 701.261400] <3>00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
May 5 20:30:01 jan-vaio-vgn-tz31-vn kernel: [ 701.261404] <3>00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
May 5 20:30:01 jan-vaio-vgn-tz31-vn kernel: [ 701.261407] <3>00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
May 5 20:30:01 jan-vaio-vgn-tz31-vn kernel: [ 701.261410] <3>00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
May 5 20:30:01 jan-vaio-vgn-tz31-vn kernel: [ 701.261414] <3>00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
May 5 20:30:01 jan-vaio-vgn-tz31-vn kernel: [ 701.261417] <3>00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
May 5 20:30:01 jan-vaio-vgn-tz31-vn kernel: [ 701.261420] <3>00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
May 5 20:30:01 jan-vaio-vgn-tz31-vn kernel: [ 701.261423] <3>00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
May 5 20:30:01 jan-vaio-vgn-tz31-vn kernel: [ 701.261426]
May 5 20:30:01 jan-vaio-vgn-tz31-vn kernel: [ 701.629793] [drm:edid_is_valid] *ERROR* Raw EDID:
May 5 20:30:01 jan-vaio-vgn-tz31-vn kernel: [ 701.629802] <3>00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
May 5 20:30:01 jan-vaio-vgn-tz31-vn kernel: [ 701.629805] <3>00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
May 5 20:30:01 jan-vaio-vgn-tz31-vn kernel: [ 701.629809] <3>00 00 00 00 00 00 00 00 00 00 00 00 ...

Read more...

Revision history for this message
Jan (jan-timo-henrich-deactivatedaccount) wrote :
Revision history for this message
Jeremy Foshee (jeremyfoshee) wrote :

Hi Jan,

If you could also please test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text. Please let us know your results.

Thanks in advance.

    [This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

tags: added: kj-triage
Changed in linux (Ubuntu):
status: New → Incomplete
tags: removed: needs-upstream-testing
Revision history for this message
Jan (jan-timo-henrich-deactivatedaccount) wrote :

Hi Jeremy,

I used linux-image-2.6.34-999-generic_2.6.34-999.201005061008_amd64.deb and hat the same problem.

Revision history for this message
Jan (jan-timo-henrich-deactivatedaccount) wrote :

This bug-file _might_ be a duplicate, see:

http://www.google.de/search?q="[drm:edid_is_valid]+*ERROR*+Raw+EDID"+site:bugs.launchpad.net

http://www.google.de/search?q="LVDS-1:+EDID+invalid"+site:bugs.launchpad.net

Revision history for this message
Jan (jan-timo-henrich-deactivatedaccount) wrote :
Revision history for this message
Jan (jan-timo-henrich-deactivatedaccount) wrote :

Hi Jeremy, are you still with me?

Maybe this is something: "i915 0000:00:02.0: LVDS-1: EDID" - I don't know, but to me it looks like that the kernel expects to handle an i915-Chipset (with a GMA 900 graphics core). In fact I have a Mobile Intel® 945GMS Express Chipset (GMA 950).

http://en.wikipedia.org/wiki/List_of_Intel_chipsets#Core.2FCore_2_Mobile_Chipsets
http://en.wikipedia.org/wiki/Intel_GMA#GMA_900
http://support.vaio.sony.eu/computing/vaio/specifications/index.aspx?m=VGN-TZ31VN_X&l=en_GB

Revision history for this message
Jeremy Foshee (jeremyfoshee) wrote :

Jan,
    I am. It appears that this is in the same direction as some of the other reports I have seen. I've set the bug to triaged for a kernel team member to take a look at, but sue to UDS this coming week, it may be a bit.

Thanks!

~JFo

Changed in linux (Ubuntu):
status: Incomplete → Triaged
importance: Undecided → Medium
Revision history for this message
Jan (jan-timo-henrich-deactivatedaccount) wrote :

Hi Jeremy,

I asked Yakui Zhao from intel to have a look on this thread. He said, from the log it seems that his patch is not shipped in the kernel I used. He will send it to the stable kernel.

thanks to both of you.

Jan

refered link: http://bugs.freedesktop.org/show_bug.cgi?id=26395

Revision history for this message
Radu (radu4us) wrote :

I have this bug also. Error I get on startup on Toshiba Tecra A8-103:

[drm:edid_is_valid] *ERROR* Raw EDID:

i915 0000:00:02.0: LVDS-1: EDID invalid

What to do?

Revision history for this message
Konstantin Lavrov (lacosta) wrote :

I have similar issue early I sent comments to bug 536827 but now it has Fix Released status.

So here is my experience with upstream kernel.

Zhao's patch already is in upstream from 2.6.34-rc5-lucid ( http://kernel.ubuntu.com/~kernel-ppa/mainline/v2.6.34-rc5-lucid/CHANGES )

With this kernel I see no "*ERROR* Raw EDID" when boot or shotdown.
Still there are several [drm:drm_edid_is_valid] messages in dmesg but only ones:
i915 0000:00:02.0: LVDS-1: EDID invalid

I suppose it is what mention patch must do.

Jan, try latest for now kernel http://kernel.ubuntu.com/~kernel-ppa/mainline/v2.6.34-rc7-lucid/

Revision history for this message
Jan (jan-timo-henrich-deactivatedaccount) wrote :

Still have this issue with kernel 2.6.32-24

My workaround:

open a terminal
$ gksu gedit /etc/default/grub
add: GRUB_CMDLINE_LINUX="nomodeset"
$ sudo update-grub

Revision history for this message
cascagrossa (cascagrossa-cascao) wrote :

Asus eeepc 1000h, Bios 2.204, Kubuntu Netbook 10.4.
I tested mainline kernel 2.6.34 and the messages don't show at boot time, but still have a few messages in kernel.log.
Had to go back to stock kernel due to sound intermitent faults and issue with ureadahead terminating with status 5...

Changed in xserver-xorg-video-intel:
importance: Unknown → Medium
status: Unknown → Fix Released
Revision history for this message
totof1169 (bourgeotc) wrote :

still the same on maverick for me

Revision history for this message
Wim Cools (wim-cools) wrote :

Still the same for me on Maverick with an LG flatron e2350v monitor. What do I have to do to install the fix ?

Revision history for this message
totof1169 (bourgeotc) wrote :

i have made this

sudo gedit /etc/default/grub

Add nomodeset into /etc/default/grub --> GRUB_CMDLINE_LINUX="nomodeset"

save and run update-grub then reboot

and i don t have anymore the drm fault message ,

if i m right the probleme come with KMS
is there any probleme to diseable KMS??

Changed in xserver-xorg-video-intel:
importance: Medium → Unknown
Changed in xserver-xorg-video-intel:
importance: Unknown → Medium
Revision history for this message
Aacron (liath-ww) wrote :

The main thing that I'm wondering (I also have this issue), is why is EDID information even needed by the kernel? Especially in Lucid Server? No gui installed, so I don't even see why it should care, as it not running an X server. Which begs me to ask, why is this not in Xorg, instead of kernel?

Revision history for this message
Benji (benjim) wrote :

I have an Jujitsu Siemens external monitor connected to my Samsung laptop. Bevore I upgraded Ubuntu, the monitor worked fine. Now I'm stuck to my laptop monitor and can't use the external monitor. Got the same error:

[drm:drm_edid_block_valid] *ERROR* EDID checksum is invalid, remainder is 254
i915 0000:00:02.0: HDMI-A-1: EDID block 0 invalid.

This is a pretty annoying bug...

Revision history for this message
Bryce Harrington (bryce) wrote :

When the EDID provided by hardware is invalid or unavailable, there really is little the kernel can do to correct it. In some cases where there is a simple monitor-specific flaw, that can be quirked on a case-by-case basis, however the situation described here is outside that scope, since the EDID is just plain blank.

Disabling use of KMS modesetting (as described in the above comments, and as provided by the upstream bug report) works around the problem but doesn't really "fix" it. A proper fix would be to provide a tool for installing a corrected EDID into the kernel's /lib/firmware/edid. The kernel already supports this, but the tool needs to be provided on the userspace side, e.g. xdiagnose.

affects: linux (Ubuntu) → xdiagnose (Ubuntu)
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package xdiagnose - 3.4

---------------
xdiagnose (3.4) raring; urgency=low

  * bin/xrotate: Add new script to manually rotate screen and input.
    Designed for the Nexus 7 tablet; will need extended to support other
    devices.
  * bin/xedid: Add new script for viewing and installing EDID files into
    firmware.
    + Fixes situation where EDID is unavailable, corrupted, or invalid
      (LP: #575985)
    + Fixes situation where KVM corrupts the EDID the monitor provides.
      (LP: #992346)
  * bin/xpci: Fix two string issues so xpci will run.
    (LP: #1098390)
  * apport/source_xorg.py: Gracefully skip Xorg.0.log parsing if the
    parsing fails.
    (LP: #1098395)
  * apport/apport-gpu-error-intel.py: Gracefully skip DMI parsing if
    the parsing fails.
    (LP: #1062042)
  * xdiagnose/applet.py: Fix bug where a stray =1 gets added to
    GRUB_CMDLINE_LINUX_DEFAULT.
    (LP: #954123)
  * tests: Add sample Xorg.*.log files rather than using the on-disk one
 -- Bryce Harrington <email address hidden> Wed, 09 Jan 2013 18:17:24 -0800

Changed in xdiagnose (Ubuntu):
status: Triaged → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Related questions

Remote bug watches

Bug watches keep track of this bug in other bug trackers.