# Ubuntu GNOME 14.04 (updated today) on Samsung N150 PLus (model
NP-N150)
$ sudo lshw -short
H/W path Device Class Description
=
system N150P/N210P/N220P ()
/0bus N150P/N
eol reached https://wiki.ubuntu.com/Releases
** Changed in: linux (Ubuntu Natty)
Status: In Progress => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/712075
Title:
[drm:drm_edid_blo
Have you tried to upgrade the kernel to > 3.5.?
Since 3.5. the bug should not appear anymore.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/712075
Title:
[drm:drm_edid_block_valid] *ERROR* EDID chec
This Bug affects me. I use viewsonic LCD:
Jan 8 21:03:44 DreamDean kernel: [ 72.399008] [drm:drm_edid_block_valid]
*ERROR* EDID checksum is invalid, remainder is 6
Jan 8 21:03:44 DreamDean kernel: [ 72.399010] Raw EDID:
Jan 8 21:03:44 DreamDean kernel: [ 72.399011]00 ff ff ff ff ff f
This bug was filed against a series that is no longer supported and so
is being marked as Won't Fix. If this issue still exists in a supported
series, please file a new bug.
This change has been made by an automated script, maintained by the
Ubuntu Kernel Team.
** Changed in: linux (Ubuntu)
** Tags removed: kernel-key
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/712075
Title:
[drm:drm_edid_block_valid] *ERROR* EDID checksum is invalid
To manage notifications about this bug go to:
htt
Oeniric Precise error appears, very unstable X and DVI1 disappears all
the time, KDE won't rememer saved output etc. but the real kicker is the
weird things happening to X11.
[17328.593013] [drm:drm_edid_block_valid] *ERROR* EDID checksum is invalid,
remainder is 74
[17328.593018] Raw EDID:
[1732
** Tags added: oneiric precise
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/712075
Title:
[drm:drm_edid_block_valid] *ERROR* EDID checksum is invalid
To manage notifications about this bug go to:
I'm having this problem as well. It seems to almost be confined to the
i915 chipset. I began noticing the error when I first installed ubuntu
a few weeks ago. It didn't affect the performance at all, just a
warning I saw on shutdown. This was on 3.0.12-generic (I can give you
more specifics if I
I see this same issue in 11.10 with the Intel GM45 chipset and a docking
station.
Screensaver kicks in and turns off the monitor and it never comes back.
I have to switch to a VT and restart lightdm. I see the
drm:drm_edid_block_valid error in dmesg.
The 'echo 0 > /sys/module/drm_kms_helper/para
The attachment "drm-Never-change-the-connector-status-to-unknown-whilst-
polling.patch" of this bug report has been identified as being a patch.
The ubuntu-reviewers team has been subscribed to the bug report so that
they can review the patch. In the event that this is in fact not a
patch you can
Same issue with a Philips 220WS8FB and a DELL optiplex 755 Intel GMA.
Resolution max is 1024x768.
I tried 2.6.38-8 but no change.
I have launch lubuntu from a usb hard drive and I was able to go up to
1360x768, I will check the kernel version.
My specific setup is a DVI convertor at the back of t
Was 2.6.35-23 on lubuntu that let me go to 1360x768
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/712075
Title:
[drm:drm_edid_block_valid] *ERROR* EDID checksum is invalid
To manage notifications a
Both of my Viewsonic VE710 monitors seem to produce invalid EDIDs
leaving me stuck with 1024x768. The suggestion in #48 (appropriately
modified) allowed me to finally get to 1280x1024, but the 11.04 Unity
desktop is confused as it partly uses the old resolution. It is not
clear to me where to put
I have Samsung Syncmaster 204Ts which worked fine with Ubuntu 10.04
using DVI connection. Since 10.10 the screen is blank with DVI
connection and I get invalid EDID errors constantly.
Combining two solutions below I was able to get DVI working again:
#1: http://lists.freedesktop.org/archives/dri-
I have tried the solution as described by sikkepitje in comment #52 however
unfortunately it did not resolve my issue.
I am still getting the EDID invalid checksum errors.
My hardware is the same as indicated in comment #27 however at the
moment I am running oneiric with the 3.0-1-generic ke
I had exactly the same problem. The solution that worked for me follows.
THE PROBLEM :
The symptoms:
* the screen flashed every 10 seconds.
* X won't run in a resolution higher than 1024x768 , while it used to run at
1280x1024.
* missing virtual terminals under ctrl-F1 t/m ctrl-F6 keys. There is
maybe it could be ignored for now and the display "connected" in the
driver anyway? is there a way to forcibly "connect" it ? (i.e. make it
useable by x)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/7
This Bug affects me. I'm using a Samsung SF510 ("shark design") notebook
with i915 kernel module and am connecting an Acer AL2216W 1680x1050
flat-screen Monitor via HDMI, using a hdmi-to-dvi-d cable, randr output:
"HDMI1".
Today this happened for the second or third time. I think it is
triggered b
An update:
I found a strange thing happening today. The Acer 17" monitor went back
to 1024x768; No xorg.conf. Monitor "Unknown"; Back yo Square 1.
I connected a different Acer 17" and it was detected instantly and got
back the 1440x900. The old Acer 17" would never get detected. The 2
other repla
For my external Dell display I'm also stuck with 1024x768. As a work-
around, the script below forces the 1600x1200 resolution. I have put the
script in ~/.kde/Autostart/xres_fix.sh and done chmod +x
~/.kde/Autostart/xres_fix.sh to make it execute after KDE starts. I
guess it could be executed also
Solved! Solved
After getting frustrated with this big display, I hot-plugged to a Dell
17" 1280x960 monitor and noticed noting changed except Monitor was
correctly detected as "Dell 17". Then, I restarted, still no change in
resolution - stuck in 1024x768.
And I did old the trick - remo
Extremely Sorry abt the delay! I typed this comment and restarted before
posting it!! :(
@Seth:
"dmesg | grep -i NAK"
returns nothing
"dmesg | grep -i bail"
returns nothing as well.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
@gtdaqua: Do you get the "NAK bailout" messages in your dmesg? There may
be more than one root cause to the EDID checksum failures, because I
don't see that in some logs attached here.
@Kees (and others), if gtdaqua isn't seeing those messages it might be
worth testing the build I made if you get
> No one has been able to identify the root cause of this, but adding the
> following line to /etc/rc.local works around it for me:
> # Disable monitor hotplug polling (https://launchpad.net/bugs/712075)
> echo 0 > /sys/module/drm_kms_helper/parameters/poll
No good. No change. Monitor is still "
On Wed, Apr 20, 2011 at 03:31:17AM -, gtdaqua wrote:
> So, is there a status update on this? 8 more days for Final Release and
> the display is broken!
No one has been able to identify the root cause of this, but adding the
following line to /etc/rc.local works around it for me:
# Disable mon
So, is there a status update on this? 8 more days for Final Release and
the display is broken!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/712075
Title:
[drm:drm_edid_block_valid] *ERROR* EDID che
@gtdaqua, thanks for testing!
I guess it was just coincidental then that this patch went in about the
same time this problem showed up on maverick.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/712075
@Seth:
Thanks for your help.
Downloaded the following files and did a dpkg -i:
linux-headers-2.6.38-8-generic_2.6.38-8.42~lp712075v201104151608_i386.deb
linux-headers-2.6.38-8_2.6.38-8.42~lp712075v201104151608_all.deb
linux-image-2.6.38-8-generic_2.6.38-8.42~lp712075v201104151608_
@gtdaqua:
Would you be able to test using the kernel packages I linked to in
comment #37 and report the results back here? Thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/712075
Title:
[drm:d
Apr 18, 2011, 07:40 GMT
Ubuntu 32-bit 11.04 beta 2 with latest updates.
Never experienced flickering since updating to Natty (2 weeks ago), but
the max resolution 1024x768 but the Acer AL1702w monitor can do
1440x900. Video Card is a built-in Intel G915 on a Core2Duo Processor.
Had no problems wi
** Changed in: linux (Ubuntu Natty)
Milestone: ubuntu-11.04-beta-2 => natty-updates
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/712075
Title:
[drm:drm_edid_block_valid] *ERROR* EDID checksum i
I put together kernel builds for natty with that patch reverted so we
can see if it is behind these issues. They are available at:
http://people.canonical.com/~sforshee/lp712075-natty/
Please test and report the results here. Thanks!
--
You received this bug notification because you are a mem
@Ernst: You're saying that you saw the behavior regress in maverick when
you did updates, correct? You don't happen to know the kernel versions
before and after the update, do you?
Suspiciously, there's a patch dealing specifically with EDID handling on
Intel graphics that would have first gone ou
** Changed in: linux (Ubuntu Natty)
Milestone: ubuntu-11.04-beta-1 => ubuntu-11.04-beta-2
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/712075
Title:
[drm:drm_edid_block_valid] *ERROR* EDID chec
I upgrade to the new kernel 2.6.38-7-generic and also for me the issue is still
there.
Attached the dmesg with the new kernel.
** Attachment added: "dmesg (2011.03.18)"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/712075/+attachment/1918752/+files/dmesg_20110318.txt
--
You received
I recently installed natty and upgraded today, and I also have this bug.
The screen flickers from time-to-time and the EDID dumps appear in the
logs.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/71207
@Kees -- can you confirm if this issue is still present with the v2.6.38
final kernel now uploaded to Natty. Please report back here. Thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/712075
Tit
s/2010-03-11/2011-03-11/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/712075
Title:
[drm:drm_edid_block_valid] *ERROR* EDID checksum is invalid
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubunt
confirming the problem for 10.10, starting about 2010-03-11
- screen resolution is 1024x768 instead of formerly autodetected 1280x1024
- dmesg shows these errors: *ERROR* EDID checksum is invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Attachment added: "xorg.conf for 10.10 installation to get 1440x900
resolution"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/712075/+attachment/1889433/+files/xorg.conf_10.10_20110305.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subsc
** Attachment added: "dmesg result on my 11.04 installation"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/712075/+attachment/1889432/+files/dmesg_11.04_20110305.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bu
** Attachment added: "dmesg result on my 10.10 installation"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/712075/+attachment/1889431/+files/dmesg_10.10_20110305.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bu
I am having the same error, both in my Ubuntu 10.10 as well in my Ubuntu 11.04
installation.
However, I do not so much have the "flickering" that is indicated. I am faced
with a screen resolution that is stuck on 1024x768.
On release 10.10 I was able to retrieve my original screen resolution
(1
Too late for alpha-3, and it doesn't block the alpha-3 release.
** Changed in: linux (Ubuntu Natty)
Milestone: natty-alpha-3 => ubuntu-11.04-beta-1
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/71
Ok so this is a partial fix. The fix does what it claims and prevents
the flickering on read failure. We however have a deeper issue in that
we still lose the connector. Thanks for testing.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ub
Urgh, 24 hours later my monitor vanished again. So, no, this patch isn't
sufficient. Note that I think the patch was a bandaid and doesn't really
address what started causing the EDID fetching routine to fail
repeatedly. I've rebooted with the probing disabled again. :(
--
You received this bug n
So far, so good. I'm still seeing the warnings in dmesg, but there has
not been any screen flickers, so the patch seems to be working.
** Changed in: linux (Ubuntu Natty)
Status: Incomplete => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
Ok I have pulled in the upstream fix into the Natty kernel and built
some kernels. Could those of you affected by this issue try the Natty
kernels at the URL below:
http://people.canonical.com/~apw/lp712075-natty/
Please test and report back here. Thanks.
** Changed in: linux (Ubuntu Natty
Correction, work-around to disable hotplug is here:
/sys/module/drm_kms_helper/parameters/poll
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/712075
Title:
[drm:drm_edid_block_valid] *ERROR* EDID ch
** Changed in: linux (Ubuntu Natty)
Assignee: (unassigned) => Andy Whitcroft (apw)
** Tags added: kernel-key
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/712075
Title:
[drm:drm_edid_block_val
https://patchwork.kernel.org/patch/508681/
** Patch added:
"drm-Never-change-the-connector-status-to-unknown-whilst-polling.patch"
https://bugs.launchpad.net/ubuntu/+bug/712075/+attachment/1825798/+files/drm-Never-change-the-connector-status-to-unknown-whilst-polling.patch
** Changed in: lin
on #intel-gfx ickle says that id:1296039205-3193-1-git-send-email-chris
@chris-wilson.co.uk should fix the problem (edid failures no long
discard connections). In the meantime, a work-around is to disable
hotplug detection:
echo 0 > /sys/module/drm_kms_helper/poll
--
You received this bug notifi
53 matches
Mail list logo