Description of problem: At the end of the installation we see a summary of all settings. When I test the Graphic Card & Monitor Configuration, I get this message: "An error occurred: (EE) [drm] failed to open device (EE) No devices detected Try to change some parameters" In previous installations of Mandriva (I'm using 2010.0 now), my monitor (Samsung SyncMaster 215TW Digital) was always configured automatically in the installation. Mageia detected a "SyncMaster" (not the full model name) with resolution "Ãutomatic" (not the native resolution). Reproducible: Steps to Reproduce:
Is this still valid with Beta2?
(In reply to comment #1) > Is this still valid with Beta2? Yes, I get the same result in Beta2.
Does the display work in the installed system?
Also please attach /root/drakx/report.bug.gz from the installed system. And the output of: lspcidrake -v
Keywords: (none) => NEEDINFO
Created attachment 399 [details] File /root/drakx/report.bug.gz (after installation of beta 2)
Created attachment 400 [details] The output of lspcidrake -v
(In reply to comment #3) > Does the display work in the installed system? Yes, the display works fine in the installed system. In the installed system (in MCC / Set up the graphical server) the result of this test is an empty grey screen.
@Anssi: is the test function supposed to work in the drakx installer?
Keywords: NEEDINFO => TriagedCC: (none) => anssi.hannula
It probably won't work in most cases anymore due to KMS... and bug #226.
CC: (none) => marja11Depends on: (none) => 226
Source RPM: (none) => drakx-installer-stage2
Isn't it just a matter that we don't include the various drm modules and related firmwares in the installer? I would like to see the /var/log/Xorg.9.log from such a test in the installer on your card
Keywords: (none) => NEEDINFOCC: (none) => thierry.vignaudSummary: Error when testing graphic card & monitor configuration => Error when testing graphic card & monitor configuration with KMS
@Thierry: Even if we did, the installer can't unload the KMS modules, so if the user selects another driver after testing, the testing will break anyway. (And maybe the loading of the KMS modules for the test would also break the installer GUI, dunno).
(In reply to comment #10) > I would like to see the /var/log/Xorg.9.log from such a test in the installer > on your card @ Thierry Gerald supplied /root/drakx/report.bug.gz, doesn't everything that happens during install go in there? Or does it but you want the file from a more recent install?
@ Thierry One of these days I must resize my Cauldron's / and /home, so I'll be doing a fresh Mageia 1 install. That'll be on a machine that gives the frozen black screen when pushing the test button during install. Is /var/log/Xorg.9.log all you need?
Created attachment 926 [details] This is my /var/log/Xorg.9.log after the test in the installer (a new installation of Mageia 1).
Thx, Gerald. I was mixing up bugreports, so my supplying /var/log/Xorg.9.log wouldn't have helped on this bug ;)
Keywords: NEEDINFO => (none)Assignee: bugsquad => thierry.vignaud
Indeed, we fail due to missing drm modules in the installer. @annsi: we use fb, so even if we swith from vesa fb to kms fb, it should not break (maybe). We could disable testing in the installer if that involves KMS.
Source RPM: drakx-installer-stage2 => drakx-kbd-mouse-x11
Pinging. because nothing happened to this report since more than 3 months ago, and it still has the status NEW or REOPENED.
Should be OK in beta2 (maybe even beta1)
Status: NEW => RESOLVEDResolution: (none) => FIXED