so why the peculiar behaviour that lightdm works when the partition
installed native grub boots the system
BUT not when a grub installed by another partition is used then lightdm
consistently crashes and the machine locks up..
BUT if i915 is added to /etc/modules in the offending partition it
i915 is loaded just fine on your first journal log:
Mar 25 23:26:06 zlink2 kernel: [drm] Initialized i915 1.6.0 20181204 for
:00:02.0 on minor 0
but it's happening after lightdm is started, so I'd say it's lightdm
which is just being too hasty
** Changed in: xorg-server (Ubuntu)
a little digging and plymouth is supposed to work with drm modesetting
drivers which means i915 has to be loaded for it to work .. so not
seeing it means ..some hardware detection has failed .. is that part of
plymouth or something else?
since it works on the upgraded install on sda1 I suspect a
Kernel module will load if added to /etc/ modules .. I have my sda1
partition running kernel 5.0.0-8.9 as are the iso's tested recently .. my
sda1 partition loads i915 without using /etc/modules.. I notice that the
recent isos do not show Plymouth progress screen at startup..is that
relevant?
If you're sure that's the problem then we would need to figure out which
kernel version it started in. Please try some different kernel versions:
https://kernel.ubuntu.com/~kernel-ppa/mainline/?C=N;O=D
and see if you can find the two closest versions where one doesn't have
the bug and the
** Summary changed:
- lightdm login screen briefly appears and then blanks out on Intel(R)
Core(TM)2 Duo CPU T5870
+ lightdm login screen briefly appears and then blanks out on Intel(R)
Core(TM)2 Duo CPU T5870 - failure to load i915 kernel module
--
You received this bug notification because
