Hello,
In the Message;
Subject : Re: TW: boot problem kernel 5.18.9-2 and higher
Message-ID : <047196af5184d55ed3998c99bea097797a94be83.camel@suse.com>
Date & Time: Sat, 20 Aug 2022 00:08:54 +0000
[SB] == Scott Bradnick has written:
[...]
MN> > How about adding this to the kernel parameter?
MN> >
MN> > i915.modeset=0
[...]
SB> Why would I do that (if things are working in a way I'm happy
SB> with)? To squash those early-in-the-boot-process i915 messages?
In the Message;
Subject : Re: TW: boot problem kernel 5.18.9-2 and higher
Message-ID : <8b7827c580db80b0678a2fbd0a4291d339f2c1da.camel@suse.com>
Date & Time: Fri, 19 Aug 2022 15:30:22 +0000
[SB] == Scott Bradnick has written:
[...]
SB> My main issue, which had persisted for at least 6mos, was that it'd boot to a
SB> black screen (on what I assume was vt7). Using the .run always worked fine (w/o
SB> X11 running of course) and I'd `sudo systemctl restart display-manager.service`
SB> and be greeted with a lightdm login screen. But subsequent reboots always
SB> yielded a black screen. That was solved with a CTRL+ALT+F4, login, `sudo
SB> modprobe nvidia_drm` and `sudo systemctl restart display-manager.service` ; Very
SB> simple, but I wanted to know why it was always the case.
Sorry, I was distracted by this sentence.
The i915.modesete=0 is a setting that does not allow Intel drivers to
be loaded.
In the Message;
Subject : Re: TW: boot problem kernel 5.18.9-2 and higher
Message-ID : <8b7827c580db80b0678a2fbd0a4291d339f2c1da.camel@suse.com>
Date & Time: Fri, 19 Aug 2022 15:30:22 +0000
[SB] == Scott Bradnick has written:
[...]
Now at [re]boot I'm greeted with lightdm consistently.
[...]
You seem to be using two GPUs, one Intel and one NVIDIA.
Of course, this is possible.
What settings are you using?
Regards.
---
┏━━┓彡 Masaru Nomiya mail-to: nomiya @ galaxy.dti.ne.jp
┃\/彡
┗━━┛ "Bill!
You married with Computer.
Not with Me!"
"No..., with money."