Bug 23467 - Stage 1 in VBox incorrectly sizes window and Stage 2 fails in X
Summary: Stage 1 in VBox incorrectly sizes window and Stage 2 fails in X
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: Installer (show other bugs)
Version: Cauldron
Hardware: All Linux
Priority: Normal normal
Target Milestone: ---
Assignee: ISO building group
QA Contact:
URL:
Whiteboard:
Keywords: NEEDINFO
Depends on:
Blocks:
 
Reported: 2018-08-20 03:23 CEST by Frank Griffin
Modified: 2018-11-17 14:53 CET (History)
5 users (show)

See Also:
Source RPM:
CVE:
Status comment:


Attachments

Description Frank Griffin 2018-08-20 03:23:58 CEST
Doing a network install in current cauldron in a VirtualBox VM, stage 1 incorrectly sizes the VM window truncating on the right and bottom what would normally be the curses display.  Enough of the display remains to proceed through stage 1, but then the attempt to launch stage 2 fails in starting X.

Unfortunately, the attempt to start X loops in retry, and quickly scrolls the original messages off VC1.

Upon advice from BitTwister I tried the install specifying "linux nomodeset", which proceeded to work perfectly.
Comment 1 Marja Van Waes 2018-08-20 21:58:44 CEST
And you do not need to specify "linux nomodeset" when using a Mageia 6 or other previous stable network iso, right?

Keywords: (none) => NEEDINFO
Assignee: bugsquad => isobuild
CC: (none) => marja11

Comment 2 Frank Griffin 2018-08-21 01:27:57 CEST
Actually, I've always used cauldron for installs, but I've never noticed this effect before with them.  I do maintain a local MGA6 repository so I could try with that if you like.
Comment 3 Frank Griffin 2018-08-21 16:31:09 CEST
Yes, MGA6 nonfree ISO works perfectly.
Comment 4 Chris B 2018-08-24 13:41:50 CEST
Confirmed. Using the latest netinstall.iso (Cauldron). xorg error message.
Only 'linux nomodeset' works.
After the installation nomodeset is not needed.

Has the installer a problem with the early loading of the (now inbuilt) vboxvideo module?

CC: (none) => shybluenight

Thierry Vignaud 2018-08-24 14:16:14 CEST

CC: (none) => mageia, thierry.vignaud, tmb

Comment 5 Martin Whitaker 2018-11-06 01:13:26 CET
This is caused by the inclusion of the vboxvideo kernel driver in the all.rdz image. This creates a dri device. When X detects this, it auto-selects the vesa driver, which only works if you add the nomodeset boot option.

The easy fix is to exclude the vboxvideo driver. The system will then fall back to using the frame buffer device, as it did in Mageia 6.
Comment 6 Martin Whitaker 2018-11-17 14:53:10 CET
I've excluded the vboxvideo driver. If someone wants to fix this a different way, go ahead, but please wait until we have a working set of beta1 ISOs.

Status: NEW => RESOLVED
Resolution: (none) => FIXED


Note You need to log in before you can comment on or make changes to this bug.