SUSEPrime default setup is strange

Question

SUSEPrime default setup is strange

Closed this issue 2 years ago · 8 comments

The current default after installing is to copy in the .conf and .modprobe settings mentioned on the Git page here, but then to not enable the SUSEPrime service or set a default for the next boot. Since suseprime is also pulled in by default with the nvida-G06 drivers this caused some weird stuff for my Optimus setup on the next boot when X.org tried to bring up my Intel graphics card and ended up pulling in the NVIDIA Dedicated card as well, and then having the greeter crash when it tried to connect to X resulting in a blank login screen (for both SDDM and LightDM), but it would work if I dropped to terminal and did Init 3 / Init 5. Unfortunately I'm not sure what a good default setting for this is. My experience was that nvidia was by far the most stable setting but this may an artefact of the Titan GT77 architecture.

Answer 1 · 2022-10-23T15:04:36.000Z

Hmm. What was the setting of prime-select after installation? Check with prime-select get-current.

Answer 2 · 2022-10-23T15:12:33.000Z

I don't believe one was defined, when I enabled the service (later) and rebooted the journal mentioned being unable to find the file. (I can't necessarily duplicate this problem exactly, I've gotten a bunch of different results depending on install order of the modules and previous setting, and most of them require me to drop to console and/or reboot)

…

On Mon, 24 Oct 2022, 01:04 Stefan Dirsch, ***@***.***> wrote: Hmm. What was the setting of prime-select after installation? Check with prime-select get-current. — Reply to this email directly, view it on GitHub <#89 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABKZ337AWB5EHX6ISAQQHDLWEVHY5ANCNFSM6AAAAAARMKBRWA> . You are receiving this because you authored the thread.Message ID: ***@***.***>

Answer 3 · 2022-10-23T15:31:26.000Z

Hmm. By default it should be set to 'nvidia' mode. And the service is being enabled in the %post of the package.

Answer 4 · 2022-10-23T15:53:09.000Z

That's interesting, I definitely had to manually enable the service. And the configuration on reboot (X doing an automatic attempt and the drivers loading too late) wasn't anything like what I got when I set boot to nvidia and then reinstalled the Nvidia drivers (I ended up in a configuration where X was trying to output to a virtual display and reinstalled the drivers as a hail Mary, which worked and also gave me a different nvidia setup, which I think was the intended one where everything ran on the Nvidia GPU ) I wonder if my install broke somewhere and I didn't notice. I'd like to do a full reinstall to check but I've got to get this computer setup pretty quickly. I'll try and come back to this when I have more free time.

…

On Mon, 24 Oct 2022, 01:31 Stefan Dirsch, ***@***.***> wrote: Hmm. By default it should be set to 'nvidia' mode. And the service is being enabled in the %post of the package. — Reply to this email directly, view it on GitHub <#89 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABKZ33Y6NYU5BXOO65NIAULWEVK5RANCNFSM6AAAAAARMKBRWA> . You are receiving this because you authored the thread.Message ID: ***@***.***>

Answer 5 · 2022-10-23T16:01:22.000Z

Just to be clear the Virtual Display wasn't the initial configuration it was a consequence of me trying to use offload later (with 0:2:0 BusID, which partially worked but couldn't use the Nvidia vendor setting) and then switching to something else.

…

On Mon, 24 Oct 2022, 01:52 Kalanyr, ***@***.***> wrote: That's interesting, I definitely had to manually enable the service. And the configuration on reboot (X doing an automatic attempt and the drivers loading too late) wasn't anything like what I got when I set boot to nvidia and then reinstalled the Nvidia drivers (I ended up in a configuration where X was trying to output to a virtual display and reinstalled the drivers as a hail Mary, which worked and also gave me a different nvidia setup, which I think was the intended one where everything ran on the Nvidia GPU ) I wonder if my install broke somewhere and I didn't notice. I'd like to do a full reinstall to check but I've got to get this computer setup pretty quickly. I'll try and come back to this when I have more free time. On Mon, 24 Oct 2022, 01:31 Stefan Dirsch, ***@***.***> wrote: > Hmm. By default it should be set to 'nvidia' mode. And the service is > being enabled in the %post of the package. > > — > Reply to this email directly, view it on GitHub > <#89 (comment)>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/ABKZ33Y6NYU5BXOO65NIAULWEVK5RANCNFSM6AAAAAARMKBRWA> > . > You are receiving this because you authored the thread.Message ID: > ***@***.***> >

Answer 6 · 2022-10-23T17:07:35.000Z

This is all very confusing to me. :-(

Answer 7 · 2022-10-23T17:10:29.000Z

It was for me too XD. But this is the price I pay for using extremely new laptops. SUSE is doing better than Ubuntu which requires deactivating the iGPU to even boot the installer.

…

On Mon, 24 Oct 2022, 03:07 Stefan Dirsch, ***@***.***> wrote: This is all very confusing to me. :-( — Reply to this email directly, view it on GitHub <#89 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABKZ336I3I7HM7IVKLM5RCLWEVWGFANCNFSM6AAAAAARMKBRWA> . You are receiving this because you authored the thread.Message ID: ***@***.***>

Answer 8 · 2022-12-01T14:36:35.000Z

I think this is just a duplicated of issue #90. Therefore also closing as fixed.