@Ricardo I updated the guide to explain how to get improved speaker sound qualiy, if you wanna check it out.
Also its kinda odd that Arch doesn’t have gnome 43 yet, lol.
Thank you for your comment too btw.
1 Like
There is a type in fprintd in this line.
I’ll check out the audio stuff, thanks!
I’d also suggest just blindly nabbing the entire fonts pattern, and grabbing opi or zyp/zow(when it’s finished), the latter tools allow you to interact cleanly with the OBS.
I’d also recommend, heavily, grabbing packman as well.
@Senhara Again this wasn’t supposed to be a full guide. Just things specific to the Framework for the most part.
Hi! I was running openSUSE for a while, then switched to Kubuntu for a bit. Now I am trying to reinstall openSUSE TW but am having trouble getting the installer to load on boot. I keep getting punted to a screen where I am told that the installer can’t find the repo, and to try and re-enter the URL. It seems like this is caused by a lack of ability to pick up my network card, and the installer isn’t loading the network module correctly. Interestingly, when I use a much older ISO, (on kernel 5.12) the same issue happens. If anyone had an ISO from kernel 5.18/19 sitting around I could give that a try to see if it is a kernel issue. Anyone have any ideas for how to resolve the issue?
1 Like
@Isaac_Peetoom_Heida Could it just be an issue with the installer? Have you tried using the offline installer? I have an offline installer with Snapshot20221029 that I used and I was able to connect just fine after installation.
@slothlike when I tried with the offline installer, the installer also failed to pick up my network card. Interestingly, when I tried the Krypton live image, it picked up the network card and showed my wifi network, but wouldn’t let me connect. If the offline image doesn’t seem to ship with the drivers required to pick up the network card, is it still a good idea to install?
@Isaac_Peetoom_Heida Right I should have clarified, when I tried the offline installer, it failed to recognize the network card but once it was installed it worked just fine. It also seems I’m not the only one:
That’s why I said it could just be a bug or issue with the installer itself. That being said, I’m not completely sure with the current version of the installer so I can’t say anything for certain.
3 Likes
@Isaac_Peetoom_Heida I am sorry I wasn’t able to help, (like a lot of my projects I can never stick to them, this guide included 
), but I am glad you were able to get help! Thanks @slothlike.
I am now back on fedora after coming to the unfortunate realization that a large number of rpm packages out there favour RHEL distros over SUSE ones, but I still like openSUSE, and I am going to polish off this guide a bit more and hopefully keep up with the comments a bit better too!
Could you specify whether this post is for Tumbleweed or Leap in the title?
Hi, I have a few questions.
-
Is the fingerprint setup still needed with Tumbleweed? In the Fedora 38 guide it’s not needed anymore but it was in Fedora 37. Furthermore, the openSUSE Wiki says that fingerprinters should be detected automatically.
-
For enabling the brightness hotkeys the guide written by the OP recommends adding
blacklist hid-sensor-hubto/etc/modprobe.d/framework-als-blacklist.conf. Meanwhile, the Ubuntu guide*, the Mint guide* and the Manjaro guide* say to addGRUB_CMDLINE_LINUX_DEFAULT="quiet splash module_blacklist=hid_sensor_hub"to/etc/default/grub, followed bysudo grub-update. The Fedora guide instead uses the commandsudo grubby --update-kernel=ALL --args="module_blacklist=hid_sensor_hub". So there’s three different approaches, what’s the correct one for openSUSE, or do they all work? -
The Ubuntu, Mint and Manjaro guides also recommend adding
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash nvme.noacpi=1"to/etc/default/grub, followed bysudo grub-update, for less battery drain from the SSD when suspending. For Fedora the guide instead uses the commandsudo grubby --update-kernel=ALL --args="nvme.noacpi=1". This is missing from the OP’s guide, but as all other distros seem to need manual intervention I would assume that’s also the case for openSUSE, or does it automatically use the right battery-saving setting? -
The Ubuntu, Mint and Manjaro guides - but not Fedora! - furthermore recommend adding
wifi.powersave = 2to/etc/NetworkManager/conf.d/default-wifi-powersave-on.confin order to prevent Wifi dropoffs. Is this needed for openSUSE (specifically Tumbleweed) or does it “just work” like it apparently does on Fedora?
'* sorry, I had to remove the links because I am a new user and not allowed to use links for some silly reason! Just follow the link to the Fedora guide and then on the left you’ll see the Ubuntu/Mint/Manjaro guides.
Hi OP here. I unfortunately have switched to just using Arch on all of my systems so unfortunately I am not quite in the loop anymore of the status of how things work in openSUSE anymore unfortunately. As for that thing about improving SSD battery drain, I honestly just didn’t know that option existed. Thanks for bringing it to my attention though because it is something I actually kind of want to use now.
Linux Support Lead here. We have not vetted any distro not appearing on the Linux page. And this explains what all of this means.
It’s been a minute since I have run OpenSUSE myself. Running GRUB, I would emulate the Fedora guide (and the grub methods mentioned). Then after adding to grub config, grub2-mkconfig -o /boot/efi/EFI/grub.cfg
Basically repeat to match Fedora 37/38 guides.
Power save changes should not be needed on newer kernels (guides to be updated on that), but if you experience dropping of wifi, use them.
EasyEffects now has a package in zypper.
Also after running pam-config --add --fprintd,
I get:
WARNING: module /lib/security/pam_fprintd.so is not installed.
Some searching makes led me to bugs reported on a redhat forum and an openSuse forum. The recommended fixes did not work for me, wondering if anybody ran into anything similar.
1 Like
I have the same problem and I am running openSUSE Tumbleweed. It looks like pam_fprintd.so is not part of any of the packages in that location. What I did do was locate where the file does exist and linked it.
sudo ln -s /usr/lib64/security/pam_fprintd.so /lib/security/pam_fprintd.so
Running the pam-config command did work but it looks like it still isn’t quite configured properly. Plasma does register the finger prints but the fingerprints do not unlock the system. I must be missing something. 
Hey Nathan, I was on the same boat. Try this, it works for me now:
https://en.opensuse.org/SDB:Using_fingerprint_authentication
1 Like
@Nathan_Wolf Nice to see I wasn’t the only one. I think the fingerprint sensor occasionally worked for me in the end. I haven’t tried yalls suggestions, but glad to see there are paths forward for others.
Bigger problem might be that I go bouldering often. It became hard for me to tell if it is the sensor not working or my fingers’ skin being too worn. It kinda de-incentivizes me from properly troubleshooting.
1 Like
Bouldering! Golly, that is not a hobby that has much draw for me but I totally respect the drive. Climbing walls are about as much as I do. I’m pretty great at falling off of them.
I have found that the fingerprint sensor using openSUSE Tumbleweed with Plasma 6 is pretty decent. It’s at least as good as my Pixel 7 phone in getting it right. The only issue I seem to have is that I only get like two tries before Plasma rejects checking it again. So, not much different, again, than my Pixel. I think I need some more time to warm up to using the fingerprint sensor in general. It works, but I am on the fence if I want to use it.
1 Like