Arch Linux

Roken

Member

From: South Wales, UK

Registered: 2012-01-16

Posts: 1,366

Peculiar GRUB/TTY behaviour

MODS: Please move this is it is better somewhere else.

A couple of weeks agio I accidentally installed Windows 10 to an internal HD (yes, it was an accident, it was meant to go on a USB drive), but that's by the by. I decided to keep it around as a "just in case" thing.

I updated grub to give me an option to boot Windows (my default is Arch using the zen kernel), and the grub.cfg entry for Windows is:

### BEGIN /etc/grub.d/30_os-prober ###
menuentry 'Windows 10 (on /dev/sdc1)' --class windows --class os $menuentry_id_option 'osprober-chain-F6BE1754BE170CAD' {
	insmod part_msdos
	insmod ntfs
	set root='hd2,msdos1'
	if [ x$feature_platform_search_hint = xy ]; then
	  search --no-floppy --fs-uuid --set=root --hint-ieee1275='ieee1275//disk@0,msdos1' --hint-bios=hd2,msdos1 --hint-efi=hd2,msdos1 --hint-baremetal=ahci2,msdos1  F6BE1754BE170CAD
	else
	  search --no-floppy --fs-uuid --set=root F6BE1754BE170CAD
	fi
	parttool ${root} hidden-
	drivemap -s (hd0) ${root}
	chainloader +1

No problems so far, and both Arch zen, Arch standard and Windows all boot.

I don't use the quiet option for any Linux boot, since I like to see what's going on, and make life easier to debug if something goes wrong.

However, if I boot Windows, and then restart from within windows (using the Restart option), neither grub nor the terminal messages during boot appear. The screen remains blank.

If I wait a little, my default Arch does boot and the desktop appears, so it isn't a critical situation, but it is rather disconcerting.

If I shut down from windows and then power on again, or reboot from Linux, then everything behaves as expected, and so I'm assuming something to do with a lock or some such thing in the graphics drivers after booting Windows, but is there anything I can do to grub to prevent/reset this at the outset?

---

Ryzen 5900X 12 core/24 thread - RTX 3090 FE 24 Gb, Asus B550-F Gaming MB, 128Gb Corsair DDR4, Fractal Design Define 7 XL, 5 HD (2 NvME PCI, 4SSD) + 1 x optical.
Linux user #545703

/ is the root of all problems.

V1del

Forum Moderator

Registered: 2012-10-16

Posts: 25,361

Re: Peculiar GRUB/TTY behaviour

Looks like a BIOS/UEFI/firmware bug that doesn't properly reinit state on reboot, might be fixed by an update here (...or if this is an UEFI and all systems are configured for UEFI try to disable legacy/CSM compat if that's there...)

Alternatively GRUB can be configured to enforce a certain mode itself, see https://wiki.archlinux.org/index.php/GR … resolution