Bug 10786 - Installer seems to select the wrong video driver, then stalls.
Summary: Installer seems to select the wrong video driver, then stalls.
Status: RESOLVED OLD
Alias: None
Product: Mageia
Classification: Unclassified
Component: Installer (show other bugs)
Version: 3
Hardware: i586 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Thomas Backlund
QA Contact:
URL:
Whiteboard:
Keywords: NEEDINFO
Depends on:
Blocks:
 
Reported: 2013-07-17 02:52 CEST by John Smith
Modified: 2014-12-03 16:28 CET (History)
1 user (show)

See Also:
Source RPM:
CVE:
Status comment:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description John Smith 2013-07-17 02:52:07 CEST 
Description of problem:

With the LiveCD KDE, when either trying to run Mageia or install it, the installer gets as far as OK'ing the "Reached target graphical interface" line but goes no further, even after 60min. Pressing the power-off button starts Mageia closing down stuff, so it hasn't crashed, only stalled.

Adding the kernel option "xdriver=vesa" allows it to run/install properly.

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


How reproducible:

Every time on my system.  Zotac Atom 330 m/b with onboard GeForce graphics, 2gig ram and a 32gb SSD. No CD/DVD drive. Installing Mageia from a USB drive.

Steps to Reproduce:

Just  boot from the USB drive.

1.
2.
3.


Reproducible: 

Steps to Reproduce:
Comment 1 claire robinson 2013-07-17 08:39:43 CEST 
Can you add the output of "lspcidrake -v" as root please John.

Assignee: bugsquad => tmb

Samuel Verschelde 2013-08-27 15:17:15 CEST

Keywords: (none) => NEEDINFO
CC: (none) => stormi

Comment 2 Dick Gevers 2014-12-03 16:28:05 CET 
Requested information not provided during 15 months, for which reason we regret we must close the report as OLD.

Besides pre-5 installers cannot now be fixed anymore. Please reopen if you see the same with M5 installer. In such case do give the requested info. please.

Thanks.

Status: NEW => RESOLVED
Resolution: (none) => OLD
Note You need to log in before you can comment on or make changes to this bug.