Install and boot Mageia 7.1. Clt-Alt-F2 (reminder to use the right-side Control key as Vbox does not capture the left-control key) The user can type their username+password on a totally blank console screen. So the "input" is working, it is only the visual in plain-text console that is not appearing. The fix for this is to amend the grub default settings. Edit /etc/default/grub, remove " vga=791" , and in it's place use " nokmsboot". To note: if "vga=791" is removed and no " nokmsboot" is used, then the Graphical service will fail to start, though the plain text will show up. To note: I would of though "vga=" is obsolete and should be discouraged as I was reading some long while ago that it is not compatible with "kernel modesetting". thanks
::::: the "input" works on the blank console screen, as after I type "reboot" --- the system immediately reboots...
It's working here with ... BOOT_IMAGE=/boot/vmlinuz-5.5.6-desktop-2.mga7 root=UUID=b14ec558-4c45-4923-888b-e023644737fd ro noiswmd audit=0 vga=788 Try changing the Display settings for that guest, on the Screen tab, to use the VBoxSVGA Graphics Controller.
CC: (none) => davidwhodgins
Leaving this with you, Dave.
Setting to "VBoxSVGA" does the trick. The default is 'VMSVGA' on the host here, --- it must be that the guest additions were taking effect. Plain text now works(as well as the graphics login manager), but the plain-text login comes in a small frame. Is it possible to try another video mode for the text console? Mageia removed /sbin/v86d and the module uvesafb relies on it. From what I read vga= has become deprecated and it is problematic for intel-driver setups... Suppose I were to try Mageia on native hardware, this can be an issue. thanks
We've had no reports of still using vga= causing problems, so at this point I'm not too worried about it. $ grep GFX /etc/default/grub GRUB_GFXMODE=1024x768x32 GRUB_GFXPAYLOAD_LINUX=text The values are set, so it should be ok to remove the vga= parameter if desired, and grub2 should handle it. Experiment with different values if the current settings are not what you want. I'm going to close this bug as the setting for the graphics controller is up to the person setting up the vb guest, and the vb defaults are decided by virtualbox.
Status: NEW => RESOLVEDResolution: (none) => INVALID
I could use a gfxmode that the vbox driver supports, I can list its modes via the vbox application window, clicking on its icon. https://imgur.com/a/xaPACk1 It would be great if there was an encouraging instruction for a Virtualbox-howto for users to check out Mageia. The Mageia-installed stock Vbox guest additions needed to be uninstalled, and I had to manually install guest additions from the native host's iso. (currrently there is a draft https://wiki.mageia.org/en/VirtualBox -- but it is still lacking clarity -- perhaps I can suggest this to the doc-team If this helps for anyone trying Mageia on Virtualbox:: - Removed vbox packages x11-driver-video-vboxvideo, virtualbox-guest-additions, - Mounted via Vbox application -- host native's release of guest-box additions, - ran "su -l -c /path/to/VBoxLinuxAdditions.run" after mounting its iso within the virtualbox environment. ) GRUB_GFXMODE=1366x768x32 is a mode that is supported on boot-up. I suppose I can use the systemd-vconsole-setup.service to enable(it is disabled by default), and then setup /etc/vconsole.setup for font things. I noticed that "drakconf" has a bootloader option, and I did not use it. Other than ^ all that, I did a dnf update, and for some reason it overwrote the /etc/default/grub. Is there an option to tell drakconf to ignore the bootloader section? I presume dnf probably follows drakconf settings of things. If I make changes to it, any next update by dnf will overwrite the file. I take note of this because on Mageia's wiki there is mention about editing /etc/default/grub but no mention about it possibly being overwritten by system updates. https://wiki.mageia.org/en/Troubleshooting_section_for_the_manual#You_get_a_grub_prompt_.28Grub_2.29 "Find the line GRUB_CMDLINE_LINUX_DEFAULT=" splash quiet resume....." and move the cursor to the end of it, see the red circle in the screenshot, then press SPACE to add a blank space, then carefully type in the kernel boot parameter(s) that you need to add." I was pretty sure it was being overwritten as it was occuring twice. lol
iirc it was the line containing "GRUB_CMDLINE_LINUX_DEFAULT=" that was getting overwritten/resetted by a system update.