Comment 6 for bug 2047456

1. I edited grub in Lubuntu Noble installed in my Toshiba: to get an extra menuentry with 'nosplash' instead of 'quiet splash'. It did not help much, because I could not even see the grub menu, when connected to the external screen.

2. I cold-booted with the external screen disconnected, selected the menuentry with 'nosplash', connected the external screen pressed Enter and it worked. Text was scrolling on both screens, and I could even log in on the external screen. So in this case, the problem started already at grub and never recovered, but when connected after that, things worked well.

3. I cold-booted with the external screen disconnected, selected the default menuentry with 'quiet splash', connected the external screen pressed Enter and it worked. I could even log in on the external screen. So in this case, the problem started already at grub and never recovered, but when connected after that, things worked well.

4. I rebooted with the external screen disconnected, selected the default menuentry with 'quiet splash', connected the external screen pressed Enter and it worked. I could even log in on the external screen. So in this case, the problem started already at grub and never recovered, but when connected after that, things worked well.

-o-

These results makes me think that we should blame the fancy semi-graphical grub menu, at least when running Lubuntu Noble in the Toshiba. Maybe there is some race condition, when deciding where to send the graphics or what resolution to use.

Grub is seen when booting the HP Probook, so there must be a problem also later in the boot process.

-o-

Next I intend to connect the internal drive (a SATA SSD) via a USB to SATA adapter and boot different computers from the same Noble system. (I think it is most important to debug the developing LTS version.)