Bug 997

Summary:	DRM failures when setting up graphics before password screen
Product:	Mageia	Reporter:	DariuszSki <linuxstuff>
Component:	RPM Packages	Assignee:	Mageia Bug Squad <bugsquad>
Status:	RESOLVED OLD	QA Contact:
Severity:	major
Priority:	High	CC:	anssi.hannula, thierry.vignaud, tmb
Version:	Cauldron	Keywords:	NEEDINFO
Target Milestone:	---
Hardware:	i586
OS:	Linux
Whiteboard:	check
Source RPM:	kernel	CVE:
Status comment:
Attachments:	DRM graphics errors during boot sequence on eee-pc

Description DariuszSki 2011-04-26 17:03:07 CEST

Description of problem:
There are errors in DRM graphics card initialisation which slow the boot a little bit while they are sorted out.

[drm:drm_edid_block_valid] *ERROR* EDID checksum is invalid, remainder is 128
[drm:drm_edid_block_valid] *ERROR* Raw EDID:

(Fuller readout in attached text file).

Tested on EEE-PC, mobile 945GME Express integrated graphics controller (Intel)

I left it as a bug needs fixing as it does boot into the password screen, then to KDE, doesn't appear to crash anything, unless it cases other problems that I haven't found yet. Although GUI loading is a bit slower than Mandriva 2010.1

Version-Release number of selected component (if applicable):
Mageia Beta1

How reproducible:
Watch verbose readout of boot in EEE-PC

Comment 1 DariuszSki 2011-04-26 17:05:02 CEST

Created attachment 293 [details]
DRM graphics errors during boot sequence on eee-pc

Comment 2 Ahmad Samir 2011-04-27 04:57:15 CEST

Looks like https://bugzilla.redhat.com/show_bug.cgi?id=649949

What's the output of:
su
monitor-edid

Are you using a KVM switch?

CC: (none) => anssi.hannula, thierry.vignaud, tmb
Component: Installation => RPM Packages
Source RPM: (none) => kernel

Ahmad Samir 2011-04-27 04:57:28 CEST

Priority: Normal => High
Severity: normal => major

Comment 3 Manuel Hiebel 2011-10-02 00:13:23 CEST

ping ?

Keywords: (none) => NEEDINFO
Whiteboard: (none) => check

Comment 4 Manuel Hiebel 2011-11-20 00:46:58 CET

Since there are insufficient details provided in this report for us to investigate the issue further, and we have not received feedback to the information we have requested above, we will assume the problem was not reproducible, or has been fixed in one of the updates we have released for the reporter's distribution.

Users who have experienced this problem are encouraged to upgrade to the latest update of their distribution, and if this issue turns out to still be reproducible in the latest update, please reopen this bug with additional information.

Closing as OLD.

Status: NEW => RESOLVED
Resolution: (none) => OLD