All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ@public.gmane.org
To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: [Bug 73267] Nouveau: corrupted laptop screen's EDID info
Date: Tue, 23 Sep 2014 17:29:43 +0000	[thread overview]
Message-ID: <bug-73267-8800-6prQAXC9Vy@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-73267-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>


[-- Attachment #1.1: Type: text/plain, Size: 2046 bytes --]

https://bugs.freedesktop.org/show_bug.cgi?id=73267

chr[] <chris-4cZEHNAa5IdBDgjK7y7TUQ@public.gmane.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |chris-4cZEHNAa5IdBDgjK7y7TUQ@public.gmane.org

--- Comment #5 from chr[] <chris-4cZEHNAa5IdBDgjK7y7TUQ@public.gmane.org> ---
Hello pjv!

I'm back. Dat Bug #34554 happened again after 2 years. Same machine, running
kernel 3.15.10 meanwhile.

I plugged in an external Monitor just as I did that dozend times before since
then. It went on, and the Laptop-Display just went off and disappeared. Xrandr
says it's disconnected and kernel says:

kernel: [66875.422770] nouveau E[     DRM] DDC responded, but no EDID for
LVDS-1

Well, I also got the problem with the edid-tool:

edid-tool /dev/i2c-0 write < edid-fixed
ERROR at 91: i2c_smbus_write_byte_data() failed: No such device or address

and I somehow fixed it by dropping "usleep(10000);" into the write loop.

I feel like putting my finger in that wound ....

If it's a timing issue, how likely is it to turn a i2c-read operation into a
write?
I mean, by hot-plugging in an external display I also hot-plug an i2c-bus.
I know, I can confuse my adourinous i2c-attached gadget this way.

For the record, here are the flipped bits:

--- edid.broken.hex
+++ edid.ok.hex
@@ -1,9 +1,9 @@
-00000000  00 03 00 00 00 07 4f 00  06 10 bb 9c 00 00 00 00
+00000000  00 ff ff ff ff ff ff 00  06 10 bb 9c 00 00 00 00
 00000010  00 13 01 03 80 21 15 78  0a 50 c5 98 58 52 8e 27
 00000020  25 50 54 00 00 00 01 01  01 01 01 01 01 01 01 01
 00000030  01 01 01 01 01 01 7c 2e  90 a0 60 1a 1e 40 30 20
 00000040  36 00 4b cf 10 00 00 18  00 00 00 01 00 06 10 30
 00000050  00 00 00 00 00 00 00 00  0a 20 00 00 00 fe 00 4c
 00000060  50 31 35 34 57 45 33 2d  54 4c 42 31 00 00 00 fe
 00000070  00 43 6f 6c 6f 72 20 4c  43 44 0a 20 20 20 00 dd

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 3457 bytes --]

[-- Attachment #2: Type: text/plain, Size: 181 bytes --]

_______________________________________________
Nouveau mailing list
Nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
http://lists.freedesktop.org/mailman/listinfo/nouveau

  parent reply	other threads:[~2014-09-23 17:29 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-03 21:11 [Bug 73267] New: Nouveau: corrupted laptop screen's EDID info bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
     [not found] ` <bug-73267-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2014-01-03 21:23   ` [Bug 73267] " bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-01-03 22:47   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-01-03 22:50   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-01-03 23:51   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-09-23 17:29   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
2014-09-27 12:34   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-12-04  8:41   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-73267-8800-6prQAXC9Vy@http.bugs.freedesktop.org/ \
    --to=bugzilla-daemon-cc+yj3umiyqdupfqwhejaq@public.gmane.org \
    --cc=nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.