[Ubuntu-x-swat] [Bug 487185] Re: [g45] On Intel G45 unable to read EDID block in Dmesg after move from G35 to G45

2010-04-06 Thread Bryce Harrington
Based on Rusty's last comment that this was fixed in the .32 kernel, which we include in lucid, I assume this will no longer be an issue in lucid. Can anyone confirm that? Meanwhile, since it sounds like this issue needs a kernel fix I'm reassigning to linux. ** Package changed:

[Ubuntu-x-swat] [Bug 487185] Re: [g45] On Intel G45 unable to read EDID block in Dmesg after move from G35 to G45

2010-03-02 Thread Bryce Harrington
** Summary changed: - [g45] [g45] On Intel G45 unable to read EDID block in Dmesg after move from G35 to G45 + [g45] On Intel G45 unable to read EDID block in Dmesg after move from G35 to G45 -- [g45] On Intel G45 unable to read EDID block in Dmesg after move from G35 to G45

[Ubuntu-x-swat] [Bug 487185] Re: [g45] On Intel G45 unable to read EDID block in Dmesg after move from G35 to G45

2010-02-12 Thread Rusty64bit
Yesterday i installed the 2.6.32.8 ubuntu mainline kernel on my system and the problem disappered ! No more messages in dmesg ** Attachment added: dmesg mainline kernel 2.6.32.8 http://launchpadlibrarian.net/39092001/dmesg -- [g45] On Intel G45 unable to read EDID block in Dmesg after move

[Ubuntu-x-swat] [Bug 487185] Re: [g45] On Intel G45 unable to read EDID block in Dmesg after move from G35 to G45

2010-02-09 Thread Bryce Harrington
** Description changed: Binary package hint: xorg i'm getting i915 :00:02.0: HDMI Type A-1: no EDID data [ 1096.497057] i2c-adapter i2c-1: unable to read EDID block. [ 1096.497061] i915 :00:02.0: HDMI Type A-1: no EDID data [ 1096.501452] i2c-adapter i2c-1: unable to

[Ubuntu-x-swat] [Bug 487185] Re: [g45] On Intel G45 unable to read EDID block in Dmesg after move from G35 to G45

2010-02-03 Thread T. S.
I apparently just experienced the same problem, and it crashed my X server. I was writing some e-mails in Thunderbird and suddenly X crashed and restarted. I was running just the laptop screen at the time, but often I use an external screen as well, if that matters. I have a Fujitsu S7020 with

[Ubuntu-x-swat] [Bug 487185] Re: [g45] On Intel G45 unable to read EDID block in Dmesg after move from G35 to G45

2009-12-11 Thread lmp
I have same situation, bu unfortunately I have problems too. I have port replicator with connected external monitor. So this monitor is not detected or just disappears on some random bases. After a while it can be detected again. Display preferences, Detect monitor - nothing happens (i.e.

[Ubuntu-x-swat] [Bug 487185] Re: [g45] On Intel G45 unable to read EDID block in Dmesg after move from G35 to G45

2009-12-09 Thread Maxxer
while not having apparently experience any misbehavior (in 2 days of life), I've seen these messages in my syslog too. fresh install of 9.10 on Amilo 3655. -- [g45] On Intel G45 unable to read EDID block in Dmesg after move from G35 to G45 https://bugs.launchpad.net/bugs/487185 You received

[Ubuntu-x-swat] [Bug 487185] Re: [g45] On Intel G45 unable to read EDID block in Dmesg after move from G35 to G45

2009-12-06 Thread Avuton Olrich
Would like to give something a bit more useful than me too but I'm afraid I don't comre with much more than me being in karmic and having the same problems described by the toppost. Stays stable afterwards for a random amount of time then will occur again. Sometimes occurs again after a

[Ubuntu-x-swat] [Bug 487185] Re: [g45] On Intel G45 unable to read EDID block in Dmesg after move from G35 to G45

2009-12-05 Thread Bryce Harrington
** Changed in: xserver-xorg-video-intel (Ubuntu) Status: New = Confirmed -- [g45] On Intel G45 unable to read EDID block in Dmesg after move from G35 to G45 https://bugs.launchpad.net/bugs/487185 You received this bug notification because you are a member of Ubuntu-X, which is subscribed

[Ubuntu-x-swat] [Bug 487185] Re: [g45] On Intel G45 unable to read EDID block in Dmesg after move from G35 to G45

2009-12-03 Thread Havard Sorli
Not sure if this is the same: The box almost frezze, some about 10-15 sec. after login if I move the mouse. It's possible to login via ssh from another computer. (worked in Ubuntu 8.10 and 9.4 upgraded to 9.10 and it failed # tail -n 100 /var/log/messages Dec 3 19:12:17 hlap kernel: [

[Ubuntu-x-swat] [Bug 487185] Re: [g45] On Intel G45 unable to read EDID block in Dmesg after move from G35 to G45

2009-12-03 Thread Havard Sorli
xrandr --verbose gives: # xrandr --verbose Xlib: extension Generic Event Extension missing on display localhost:10.0. SZ:Pixels Physical Refresh *0 1920 x 1200 ( 554mm x 342mm ) *60 1 1600 x 1200 ( 554mm x 342mm ) 61 2 1280 x 1024 ( 554mm x 342mm ) 76

[Ubuntu-x-swat] [Bug 487185] Re: [g45] On Intel G45 unable to read EDID block in Dmesg after move from G35 to G45

2009-12-03 Thread Havard Sorli
** Bug watch added: Red Hat Bugzilla #524403 https://bugzilla.redhat.com/show_bug.cgi?id=524403 ** Also affects: xserver-xorg-video-intel (Fedora) via https://bugzilla.redhat.com/show_bug.cgi?id=524403 Importance: Unknown Status: Unknown -- [g45] On Intel G45 unable to read EDID

[Ubuntu-x-swat] [Bug 487185] Re: [g45] On Intel G45 unable to read EDID block in Dmesg after move from G35 to G45

2009-12-03 Thread Havard Sorli
Possible to kill -9 (prosee id) X server (this line in #ps aux ) from ssh login from another computer. /usr/bin/X :0 -br -audit 0 -auth /var/lib/gdm/:0.Xauth -nolisten tcp vt7 -- [g45] On Intel G45 unable to read EDID block in Dmesg after move from G35 to G45

[Ubuntu-x-swat] [Bug 487185] Re: [g45] On Intel G45 unable to read EDID block in Dmesg after move from G35 to G45

2009-12-03 Thread Bug Watch Updater
** Changed in: xserver-xorg-video-intel (Fedora) Status: Unknown = Confirmed -- [g45] On Intel G45 unable to read EDID block in Dmesg after move from G35 to G45 https://bugs.launchpad.net/bugs/487185 You received this bug notification because you are a member of Ubuntu-X, which is

Re: [Ubuntu-x-swat] [Bug 487185] Re: [g45] On Intel G45 unable to read EDID block in Dmesg after move from G35 to G45

2009-12-03 Thread Rusty64bit
I did a clean install of 9.10 and mine is stable so far. updated to the latest bios from Intel, but no change since then. I tested it on my old Asus G35 board and havn't got the error at all. Havard Sorli schrieb: Not sure if this is the same: The box almost frezze, some about 10-15 sec.

[Ubuntu-x-swat] [Bug 487185] Re: [g45] On Intel G45 unable to read EDID block in Dmesg after move from G35 to G45

2009-11-24 Thread Bryce Harrington
** Summary changed: - On Intel G45 unable to read EDID block in Dmesg after move from G35 to G45 + [g45] On Intel G45 unable to read EDID block in Dmesg after move from G35 to G45 -- [g45] On Intel G45 unable to read EDID block in Dmesg after move from G35 to G45

[Ubuntu-x-swat] [Bug 487185] Re: [g45] On Intel G45 unable to read EDID block in Dmesg after move from G35 to G45

2009-11-24 Thread Geir Ove Myhr
** Tags added: edid g45 karmic -- [g45] On Intel G45 unable to read EDID block in Dmesg after move from G35 to G45 https://bugs.launchpad.net/bugs/487185 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-intel in ubuntu.

Re: [Ubuntu-x-swat] [Bug 487185] Re: [g45] On Intel G45 unable to read EDID block in Dmesg after move from G35 to G45

2009-11-24 Thread Rusty64bit
I had only about two hours to test yet, but it looked stable, means wasn't crashing within this time. boots fine and fast and goes straigt to the login. I had a HDMI to HDMI cable connected first, this was causing the screen flicker, but with the org. HDMI to DVI cable, that came with the IIyama