here is the journalctl boot log for sda6 /zlink4 booted by it's own install of grub (self grub)
(it was reinstalled for this purpose .. to show it works .. however plymouth does not show on the screen at all on boot but does on shutdown ) now one change is addition of a vt.handoff=1 to the end of the grub entry (originally a $vt_handoff) i'll shortly revert this and regenerate this log again.. size is about same as zlink1 version also about 1 minute long note every problem boot has a much shorter journalctl boot log..why? some stuff is not getting done .. only because the source of the grub- install has changed and the controlling partition grub.cfg used instead .. ?? these are generic auto-generated by update-grub .. so why the different behaviours ** Attachment added: "zlink4 / sda6 boot log -- self grub boot" https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1821609/+attachment/5252840/+files/zl04-apr-4-sgrub-currentboot.log -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1821609 Title: lightdm login screen briefly appears and then blanks out on Intel(R) Core(TM)2 Duo CPU T5870 (using "foreign grub") To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1821609/+subscriptions _______________________________________________ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
