Modesetting is normally what we want for Kaby Lake class graphics. A viable alternate is intel.
Message: Advanced graphics data unavailable in console for root.
On the vttys we can’t get the information we want from inxi, or with any convenience, from anything else. When using inxi with -G, we want inxi to be run from within X.
On the machine that has the i915.modeset=0 I get this unless i delete the y:
# inxi -Gayz
Error 10: Unsupported value: 0 for option: y
Check -h for correct parameters.
This error is because on this machine you didn’t take the -U inxi upgrade step.
# inxi -Gaz
...
**Device-2: Realtek Integrated Webcam HD** type: USB driver: uvcvideo
bus ID: 1-5:2 chip ID: 0bda:568c serial: <filter>
This is a different web cam, which could explain why this machine is different, and exhibiting the thread subject problem. It might be worth trying blacklisting of uvcvideo on this machine.
Display: server: X.org 1.20.3 compositor: **marco** v: 1.24.0 driver: N/A
note: display driver n/a unloaded: **fbdev**,modesetting,**vesa** alternate: intel
N/A is one result of disabling KMS](Mode setting - Wikipedia) (caused by i915.modeset=0). I’m bothered that neither of the two alternates FBDEV or VESA are used, but I suspect that Marco requires X be running with compositing enabled, which neither FBDEV nor VESA support, and results in a dead end to X.
Google links Marco to Mate. I never use Mate. I’d try some X session other than Mate. IceWM should be at the ready if you are reaching a running LightDM window manager.
Please provide the URL from
susepaste /var/log/Xorg.0.log
from a failing machine booted with neither i915.modeset=0 nor nomodeset on the the linu line in Grub. If this must be obtained from a subsequent boot, either the current/retrieval boot needs to be with 3 appended to the linu line in grub (to prevent X from starting), or (with X started), susepaste Xorg.0.log.old instead.