Bug 4340 - Mageia 2 alpha 3 Installation halts on SIS IDE driver load
Summary: Mageia 2 alpha 3 Installation halts on SIS IDE driver load
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: Installer (show other bugs)
Version: Cauldron
Hardware: i586 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard:
Keywords: NEEDINFO
Depends on:
Blocks:
 
Reported: 2012-01-29 21:17 CET by a m
Modified: 2012-02-04 21:23 CET (History)
0 users

See Also:
Source RPM:
CVE:
Status comment:

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

Description a m 2012-01-29 21:17:30 CET 
Description of problem:
On my MSI CX600 notebook when installing Mageia 2 alpha 3 setup halts repeatedly on "CONFIGURING HARDWARE" window with such text:
"Installing driver for hard disk drive controller Silicon Integrated Systems [SIS]|5513 IDE Controller"
There was no errors with previous releases. Controller model detected correctly

Version-Release number of selected component (if applicable):
Mageia 2 alpha 3 x86

How reproducible: always


Steps to Reproduce:
1. boot from DVD
2. select language, accept license
3. system halts with above message on screen
Comment 1 Manuel Hiebel 2012-01-30 01:05:44 CET 
Thanks for the bug report.
Could you provide the file /root/drakx/report.bug.gz as an attachment ?
If you don't have the file, you can switch to console 2 (by pressing 'Ctrl-Alt-F2') during installation, put a floppy in floppy drive or plug a USB key/stick and type: 'bug' then press Enter. It will put report.bug on the floppy/key.

Keywords: (none) => NEEDINFO

Comment 2 a m 2012-02-04 21:23:16 CET 
Thanks for advise, I found what the problem. I have unused partitions on /dev/sda and drakx fails to guess about available space. Setup actually not halts but it takes 11 minutes for bring up the next screen. So this question solved and another one arise. I will post a bug report about drakx's confusion with my partitioning

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