Testing the third round of ISOs for 4beta1. With the i586 DVD, I get the output in attachment when loading the boot menu. Trying to boot on HD also produces a line which seems to have encoding issues, see second attachment. Reproducible: Steps to Reproduce:
Created attachment 4485 [details] Bootloader loading
Component: Release (media or process) => InstallerQA Contact: (none) => qa-bugs
CC: sysadmin-bugs => (none)
Created attachment 4486 [details] When selecting boot from HD
Source RPM: (none) => syslinux
I have the same problem with the installation from the CD created with boot-nonfree.iso (boot-nonfree.iso of 13/11/2013)
CC: (none) => paiiou
This is due to last update on syslinux. It will be investigated after beta 1 is out.
Edit : same problem as comment 1
confirmed
Hardware: i586 => AllWhiteboard: (none) => 4beta1
(In reply to Georges Eckenschwiller from comment #3) > I have the same problem with the installation from the CD created with > boot-nonfree.iso (boot-nonfree.iso of 13/11/2013) Besides, the installation is impossible from the CD made with boot.iso
*** Bug 11683 has been marked as a duplicate of this bug. ***
CC: (none) => mageia
I see the same problem when booting the net install images in a VirtualBox VM. Details in https://bugs.mageia.org/show_bug.cgi?id=11683
New test, this morning, with boot-nonfree.iso of 21-11-2013. The strange characters always appear, but the installation starts well. Maybe that I had not waited enough the last time. I test on an old computer, not very fast.
Valid for B2
Summary: Bootloader displays strange characters in 4beta1 => Bootloader displays strange characters in 4beta2Whiteboard: 4beta1 => 4beta2
Priority: Normal => release_blockerBlocks: (none) => 11704Summary: Bootloader displays strange characters in 4beta2 => Bootloader displays strange characters
Should be fixed in drakx-installer-images 2.4.1. Soon in the mirror (see help.msg in isolinux directory)
Fixed
Status: NEW => RESOLVEDCC: (none) => davidwhodginsResolution: (none) => FIXED
What was the fix? I thought it was a syslinux problem as referenced in this commit: http://git.kernel.org/cgit/boot/syslinux/syslinux.git/commit/?h=firmware&id=a2f057c289cbf142cdd6de7d89123df2f21e475a Do we have a reference to the fix?
Ahh never mind, here is the fix: http://gitweb.mageia.org/software/drakx/commit/?id=bc8cf46f070ef8244e0018c91e41170a40528242 Note to Anne: as per my message to cauldron, if you'd used the format "mga#11602" rather than just "#11602" it would have automatically injected a comment on this bug when you pushed the commit :)
*** Bug 12118 has been marked as a duplicate of this bug. ***
CC: (none) => fri
Still visible in today's classical 64-bit iso.
Status: RESOLVED => REOPENEDResolution: FIXED => (none)Whiteboard: 4beta2 => 4RC
_I_ have...
CC: (none) => thierry.vignaud
Wrong bug. Like the other report, you're likely using an old boot.iso
Status: REOPENED => RESOLVEDResolution: (none) => FIXED
I doubt its an old boot.iso since he's afaik referring to the RC DVD released today to QA which is built against a repo synced Tue Dec 24 19:27:24 CET 2013
CC: (none) => tmb
(In reply to Dick Gevers from comment #17) > Still visible in today's classical 64-bit iso. (In reply to Thomas Backlund from comment #20) > I doubt its an old boot.iso since he's afaik referring to the RC DVD > released today to QA which is built against a repo synced Tue Dec 24 > 19:27:24 CET 2013 confirmed with the i586 iso (but yes boot.iso are still ok) Anne ?
Keywords: (none) => PATCHStatus: RESOLVED => REOPENEDResolution: FIXED => (none)
(sorry bug script)
Keywords: PATCH => (none)
I guess it's a different issue (this time in bcd...)
Working with oldies in build tree. Sorry for that mess. fixed for next set of isos