Bug 21899

Summary: installation GUI locked up with selected bootloader location /dev/fd0
Product: Mageia Reporter: Felix Miata <mrmazda>
Component: InstallerAssignee: Mageia tools maintainers <mageiatools>
Status: RESOLVED OLD QA Contact:
Severity: normal    
Priority: Normal CC: marja11, ouaurelien, zen25000
Version: 6   
Target Milestone: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Source RPM: drakx-installer-stage2, grub2 CVE:
Status comment:
Attachments: .tgz of /root/drakx

Description Felix Miata 2017-10-20 04:24:43 CEST
Created attachment 9741 [details]
.tgz of /root/drakx

Installation method: HTTP via grub loading all-nonfree.rdz and vmlinuz with these cmdline options:
automatic=met:http,int:eth0,ser:mirrors.us.kernel.org,dir:/mageia/distrib/6/x86_64,netw:static,ip:192.168.#.#,gat:192.168.#.#,dns:192.168.#.#,dom:mydomain,hos:k8mmv net.ifnames=0 readonly=1 nokmsboot vga=791 video=1024x768@60
gfxcard is Radeon AGP rv250 (9000)

I found two selections available in mga6 for bootloader location on multi-multiboot BIOS system to /dev/sda14 / target:
1-/dev/sda
2-/dev/fd0

Since overwriting /dev/sda is not acceptable, finding no other alternatives in attempting to proceed, I selected /dev/fd0. The result was the GUI hung. I could switch to tty[1-6], and see reported success in bootloader installation and beyond, but not return to tty7 (assumed location of installer). The installation seems to have completed anyway. I'm  running it booted from the master bootloader on /dev/sda3.

See also: Bug 20543 - No boot device choices in Grub2 installation screen
Marja Van Waes 2017-10-21 18:26:20 CEST

CC: (none) => marja11, zen25000
Source RPM: (none) => drakx-installer-stage2, grub2
Assignee: bugsquad => mageiatools

Comment 1 Marja Van Waes 2017-10-27 19:58:57 CEST
Mass-change status to NEW for all bugs that were filed as UNCONFIRMED between October 9 and now, and that still have that status now.

From now on all newly filed bugs will have the NEW status again, like before, regardless of who files the report.

Ever confirmed: 0 => 1
Status: UNCONFIRMED => NEW

Comment 2 Aurelien Oudelet 2020-08-05 16:34:40 CEST
This message is a reminder that Mageia 6 is end of life.

Mageia stopped maintaining and issuing updates for Mageia 6. At that time this bug will be closed as OLD (EOL).

Package Maintainer: If you wish for this bug to remain open because you plan to 
fix it in a currently maintained version, simply change the 'version' to a later 
Mageia version prior to Mageia 6's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that we cannot 
be able to fix it before Mageia 6 was end of life.
If you would still like to see this bug fixed and are able to reproduce it against a later version of Mageia, you are encouraged to click on "Version" and change it against that version of Mageia.

Although we aim to fix as many bugs as possible during every release's lifetime, 
sometimes those efforts are overtaken by events. Often a more recent Mageia 
release includes newer upstream software that fixes bugs or makes them obsolete.

--
Mageia Bugsquad

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