I need some urgent #Linux help.

[hellomiakoda@pdx.social]

@hazelnot Ah, looks like it's building now, meaning it's done bitching it can't remove 590! Rs for luck!

[hazelnot@sunbeam.city]

@hellomiakoda what does "Rs for luck" mean? 😅

Like, the letter "R"?

[hellomiakoda@pdx.social]

@hazelnot It did! Alright, let's see what a reboot does... [anxiety noises]

[ds@infosec.exchange]

@hellomiakoda I'm not sure how much i can help with this but just a thought - assuming it is a laptop, do you have the option (eg in bios/uefi) to use an integrated gpu instead of the nvidia?

If you can switch to an igpu it won't solve your problem as such, but might at least make it easier to concentrate on the x11/wayland problem first and then tackle nvidia once you've got a usable desktop again...

[hellomiakoda@pdx.social]

@ds Sadly no. This laptop was one model year PRIOR to these being able to use the integrated graphics. It's all nVidia, all the time. I was so sad to have been so close to being able to switch between them.

[hellomiakoda@pdx.social]

@hazelnot Crossing your fingers is R in american sign lanague. I used to know someone who was mute who used that phrase all the time... and it stuck with me.

[hellomiakoda@pdx.social]

@hazelnot It rebooted, but no login screen. However, it did move further down on the boot text. So something changed.

[hellomiakoda@pdx.social]

@hazelnot Jan 09 17:16:31 Skye sddm[971]: Failed to read display number from pipe

Jan 09 17:16:33 Skye sddm[971]: Running: /usr/bin/X -nolisten tcp -background none -seat seat0 vt2 -auth /run/sddm/xauth_oSoGSa -noreset -displayfd 16
Jan 09 17:16:33 Skye sddm[971]: Failed to read display number from pipe

Something is configured for X, I think.

[ktneely@infosec.exchange]

@hellomiakoda as others have mentioned, there may be multiple things going on, which can be different to troubleshoot. Since you mentioned the drivers are dropping support for your chipset, maybe doing something like

pacman -Q | grep nvidia

And then manually installing the version that had been working will get your GUI working again.

[hellomiakoda@pdx.social]

@ktneely It appears the driver issue is probably resolved. I had to install 580. Right now, it seems SDDM is trying to run on X, and Manjaro removed X... so no sddm. I can't get sddm going.

[ktneely@infosec.exchange]

@hellomiakoda I'm not familiar with SDDM, you could install another DM, or it looks like there's some experimental Wayland support out that you have to enable/install: https://wiki.archlinux.org/title/SDDM#Wayland

[hellomiakoda@pdx.social]

@ktneely I was wrong, it doesn't seem to be using the nvidia drivers at all. Ok, back to focusing on that. God damn it, what a fucking mess

[hellomiakoda@pdx.social]

@Unlikelylass Open source drivers seem to be loading no matter what i do... and they're not working.

[hellomiakoda@pdx.social]

@hazelnot I GOT IT!!! I HAVE SDDM!!! Thank you! Though, your suggestion is incomplete. I needed linux618-headers, THEN nvidia-580xx-dkms, along with additional nvidia-580xx packages. BUT, what you said started me on the path that lead me to it working again!

[hellomiakoda@pdx.social]

Alrighty! I got it working again! @hazelnot's suggestion was incomplete, but got me down the right path.
First, I needed linux618-headers (or whatever kernel you're using)
THEN nvidia-580xx-dkms
as well as
nvidia-580xx-utils
nvidia-580xx-settings
lib32-nvidia-580xx-utils

The following also got installed, but unsure if necessary or had any effect.
opencl-nvidia-580xx
libxnvctrl-580xx

[darcmoughty@infosec.exchange]

@hellomiakoda @hazelnot@sunbeam.city I was going to recommend going the opposite direction and seeing if the nouveau/nvk open source driver was an option, but I'm not sure what the status is on that particular card.

[markus@hubzilla.markusgarlichs.de]

@Miakoda :neurodiversity: this should fix the issue - install the nvidia-580xx-dkms and nvidia-580xx-utils driver from AUR.

[hellomiakoda@pdx.social]

@markus Yes. I found I also needed linux618-headers

[oblomov@sociale.network]

@hellomiakoda two paths I see are: drop the proprietary driver if mesa has decent enough support for your card, which should allow Wayland to work; or install a WM that still supports X11 and use that instead of KDE.