Has anyone else had major issues with the 570 drivers?

Every time I've tried to update to them since the repo switch last week they've broken KDE on X11 (can only use software renderer) which forces me to switch to wayland. After switching to wayland I get huge system-wide lag spikes whenever there's a window with transparency open, and every game (OpenGL, Vulkan, and DXVK) I've tried to run struggles to even get 10 fps when before I was hitting 165 without any issues.

I've tried both doing a normal zypper dup and going into Yast Software and installing every nvidia 570 package I can bc zypper dup just doesn't install the kernel firmware at all since it's now in a new package and I'm not sure what else it would miss since it only installs two packages normally.

If anyone else has had a similar experience please share, and if anyone has any idea what I could be doing wrong I'm all ears because I've been looking forward to the supposed better VK3D performance and finally getting to try using wayland.

Edit: I forgot to mention that flatpak OBS can't use NVENC encoder anymore, nvidia-smi reports the drivers correctly, and I've updated flatpak drivers to 570 as well.

Edit 2: Running on desktop with a 7800X3D and 3080ti, integrated graphics are disabled in BIOS so it can only use the GPU.

I remember doing this once being able to use a 2nd hard drive for Steam to use it as storage. Now, Recently had to reinstall steam and reformat it all. I can't for the life of me, get my 2nd nvme be recognized by steam for it to store my games on the drive.

I'm using the non-flatpak version of Steam.

My nvme is mounted in /home/name/2TB (ssd name, i know creative)

Mounted from: /dev/nvme0n1

Its format is btrfs.

I've looked into the permissions of the folder, I would believe I'm missing to give it permission. However to the folder I named steam inside my 2TB, I gave it both Others and Owning Group Permissions for rwx. So, I'm a bit of a loss on what to do.

Hi, I'm messing with Aeon on a separate hard drive right now, and my understanding (so I thought) was that Aeon is the only way to install Gnome on MicroOS

I am not really interested in encrypting my drive if I do go through with the process of switching to a RO fs, and I tend to want to do quite a bit of customization to newly installed systems. Would installing MicroOS server and then adding a pattern like microos_gnome_desktop make more sense for my use case?

Other related questions:

2. Is it possible to replace selinux pattern with apparmor in MicroOS?

3. Would MicroOS base + patterns provide more flexibility than Aeon?

4. Would you suggest just going with Aeon instead, even if you were a tinkerer? Why/why not?

Thanks

Hi, I installed Aeon on a separate hard drive by flashing the opensuse-aeon.x86_64.raw and extending the partition, because I couldn't get past FDE script not seeing my disk. It's mostly just a test to see if I can wrap my workflow around a read-only filesystem, but I'm pretty wedded to a few packages/patterns I would usually install right away on a new system. Below are the ones I think need to be "root installed" in order to work correctly:

• libvirt (lots of dependencies)
• virt-manager (lots of dependencies)
• zsh
• arp-scan (use at least 10s of times a day)
• wireshark and libpcap
• docker-ce typically with docker repo
• sublime-text with their repo, also (I think flatpak version is still 3? That's kind of lame...)
• creation of initrd and kernel command-line flags files /etc/kernel/cmdline and /etc/modules-load.d/vfio.conf

These packages are not so intertwined with the system, but a lot easier to maintain as packages than installing in userspace -- I'm realizing as I write this, I use mise for python and nodejs, so I'll see if I can manage go and rust with mise:

• neovim, glow, ptyxis, bat, dust-du, etc. etc.
• cargo (and rust dev environment)
• golang ( ' ' )
• . . . you get the idea . . .

Questions:

1. If I install all these in tukit like a "normal package", is this frowned-upon? How many "layered packages" is too many?

2. Speaking of layered, is Aeon/MicroOS's RO filesystem less succeptible to extremely slow updates/boots compared to Silverblue due to the way its engineered? ("layering" packages on Silverblue with rpm-ostree leads to awful update/package maintenance performance)

3. Are there better ways to do this stuff? Recommendations?

Thanks

Edit: markdown formatting issues; removed 4th question to roll into another post

OpenSUSE Portal:GNOME shows this screenshot that has the icons on the left side of the screen. https://en.opensuse.org/images/4/4e/GNOME_3.8_Screenshot-activities.jpg

Is this still possible? I can't find any setting for it

I don’t know why this screen shows up every time I turn on my pc, nor do I know what it even is. Everything else works fine so I never gave it that much thought, but I'd like to know why it shows up if it's something important and if there's any way to skip it.

... and made it cumbersome to use it. systemctl stop docker was a workaround but cumbersome as well.

So, today, I found out that the kernel logs those network changes under log level 6 (see cat /dev/kmsg to find out) and my system was set up (by default?) to log everything with level 7 and below, see the first number in cat /proc/sys/kernel/printk.

So, my fix was to create a file /etc/sysctl.d/60-printk-less-docker-network-on-console.conf

cat kernel.printk=5 4 1 7

and rerun systemd-sysctl with

catbus:/etc # systemctl restart systemd-sysctl.service 

Maybe, this helps someone some time - let me know!

im new to linux generally, previously for a while i used fedora and switched to tumbleweed ,how to i solve this and why does it occur?

https://preview.redd.it/5pbmdvazp2he1.jpg?width=1289&format=pjpg&auto=webp&s=354a53aa981e08abed00b57865ef7732860fad50

every time ive tried to use droidcam, my phone is detected, but other applications dont recieve the video stream. how can I fix this issue? i have V4L2Loopback installed, but not the special dc version. is there any way to get it installed? or is there a different way i need to go?

I've got a vdo - (linux v6.9 in-tree module description)[https://docs.kernel.org/admin-guide/device-mapper/vdo.html] - as a home volume on my desktop running Fedora 41 and I really like it. Wanted to try out Aeon on my laptop because I'm tired of tinkering, but I noticed Debian and Ubuntu have issues activating a vdo on boot. How's the vdo compatibility in OpenSuSE, anyone using it?

BTW I'm not holding my breath about being able to use vdo for /home on Aeon because of the immutable nature of the OS, but it'd be nice if I didn't have to re-activate one after each reboot.

https://preview.redd.it/dpez613g9zge1.png?width=1065&format=png&auto=webp&s=371a5092ed6d76674dc835d556ff61ba0d9a7ed6

Only today i noticed i am stuck to an old snapshot. The command sudo transactional-update dup create new snapshots but after a reboot it always boot the same old snapshot.

How do i enable a new snapshot?

I’ve been trying to install Budgie Desktop on openSUSE, and I keep running into this weird conflict with GNOME and GDM. What’s confusing is that on pretty much every other distro (Arch, Fedora, Ubuntu, etc.), Budgie works just fine alongside GNOME and GDM without any issues. It feels like openSUSE is still treating Budgie as if it’s heavily tied to GNOME, even though that hasn’t been the case for a while.

I know openSUSE has strict package management with zypper, but this seems more like an unnecessary conflict rule rather than an actual technical problem. I’m thinking about compiling Budgie from source just to see if that avoids the issue, but honestly, I’d rather not go through all that if there’s a simpler fix.

Has anyone else dealt with this? Is there a better workaround than force-installing or removing GDM/GNOME entirely?

T

Just showin me openSUSE desktop! ^w^

on debian based stuff its linux-headers-version but idk what its called on opensuse.

sorry this is dumb im trying to get droidcam desktop working with the rpm and its guide is for fedora and idk what the actual package name is. also is jansson a neccesary package? i have libjansson but thats apparently not the same thing

I've been running Arch for about 6 years, but I need a bit more reliability for my current job, and I was thinking of trying openSUSE. Besides the obvious differences in thing like release schedules, package managers, etc, what are some things I should know before trying it out? Is my knowledge of how to manage/fix an Arch install generally transferrable? (One of my biggest concern is losing the usefulness of the Arch wiki). Are there any fundamental differences in how the system is managed? Are there things I shouldn't do on tumbleweed that are commonly done in Arch? Etc.

Thanks for the help!

It just shows a network icon with a red x and "No available connections". Rolling back doesn't help it seems... 😢

During the installation I opted for full disk encryption. When I turn on the computer and it prompts me for my password, the text is tiny. After typing it in all further text is the normal,size. How do I increase the password prompt text size?

Greetings, folks. I'm trying to get Hyprland set up on Tumbleweed and xterm isn't playing nicely with Wayland. Besides that, it's a rather homely terminal.

I've got things generally working but I'm unable to use the Yast GUI since the terminal won't open and thus I can't authenticate as root.

Any ideas here would be super groovy.

For some applications, fuse mount via GVFS are not practical, for example when using wine via Bottles.
In the past I solved this using a CIFS mount via /etc/fstab but this is not really possible with Aeon except using transactional-update shell which is a big no-no according to the documentation.

How can I solve this the Aeon way?

I"m in the process of setting up a new Tumbleweed installation and I"ve set the correct resolution / font size in KDE but the login screen remains tiny. I've been looking online for advice and all I can find is adding certain strings into /etc/sddm.conf or /etc/sddm.conf/d/kde_settings.conf but on my installation neither of these exist. Can someone point me in the right direction please?

I've been running MicroOS for more than a year, with no issues. The system is set to update itself every sunday morning and reboot itself via rebootmgr at 2:30 UTC. The system was set up as minimal and then docker-ce and assorted dependencies. The machine is set up as a single node swarm and runs about 15 containers.

After the update and reboot on Sunday Jan 26th I started getting all sorts of stack traces from docker a few times each day. The dockerd process timedout while talking to the leader (itself?).
I've rolled back to the state as it was on Sunday Jan 19th and disabled automatic updates.

Here's a list of the updated packages on the infamous Jan 26th update:

The following 63 packages are going to be upgraded:

MicroOS-release MicroOS-release-appliance NetworkManager NetworkManager-bluetooth NetworkManager-wwan btrfsmaintenance ca-certificates-mozilla chrony chrony-pool-openSUSE coreutils coreutils-systemd device-mapper dracut glibc glibc-gconv-modules-extra glibc-locale glibc-locale-base iproute2 kernel-default kexec-tools lastlog2 libblkid1 libcbor0_11 libdevmapper-event1_03 libdevmapper1_03 libfdisk1 liblastlog2-2 libmount1 libncurses6 libnm0 libparted-fs-resize0 libparted2 libsmartcols1 libsubid5 libuuid1 libxml2-2 libxml2-tools libxslt1 libzypp login_defs logrotate ncurses-utils parted permctl permissions permissions-config policycoreutils rsync selinux-policy selinux-policy-targeted shadow suse-module-tools suse-module-tools-scriptlets terminfo-base ucode-amd update-bootloader util-linux util-linux-systemd vim-data-common vim-small xen-libs zypper zypper-needs-restarting

The following product is going to be upgraded:

openSUSE MicroOS

20250117-0 -> 20250124-0

The following package requires a system reboot:

kernel-default

63 packages to upgrade.

Any ideas what may have caused this?

Hi all,
if you consider using BTRFS as a filesystem for your next Linux machine: DON'T USE IT!

At least when you rely on a usable and stable system under all circumstances, I would stay away from it. Stay away by miles. A brief explanation what happened to me and why I think this rules BTRFS out:

I wanted to replace my nvme volume (dual boot Windows 11 / Suse Tumbleweed) for a volume with more capacity. So I used Clonezilla, like many times before, to create a complete volume backup. As it turned out, after completing the backup, the target volume was f*cked, for whatever reason. Okay, maybe Clonezilla can't handle BTRFS volumes (according to their website, BTRFS is supported, though!!). But now I realized that the source volume is also broken. I can't read it anymore. And this, my friends, is an ABSOLUTE NO GO!! Creating a backup causes read processes on the source volume, never ever should it happen that it renders a source volume unreadable. Even considered that I used Clonezilla in a wrong way (which I didn't), something like that shouldn't happen. NEVER.

After searching the net I found some more or less similar problems, so it seems that I'm not the only one having this trouble.

I'm an IT pro, in the Windows world, though. A behavior like this would disqualify a file system for any serious use case! If my boss would ask me if we could use this file system for Linux workstations, I'd highly recommend to throw BTRFS out of the windows immediately!

Thanks for reading.

Outside of a VPS provider (like Vultr) that allows you to use your own ISO, what VPS providers currently offer openSUSE as an image choice?

Hello, for a while I've had issues with my main monitor. After an update introduced brightness control it used to flicker so I had to turn it off and on again to fix it. That was anoying, but I didn't bother fixing it. But after the update to nvidia 570(which finally fixed discord screensharing, even audio, yay!) it seemingly boots fine, but then it shuts off on the desktop after 1-2 seconds. It fixes again when I disconnect the hdmi cable connected to it and replug it again, but KDE sets the resolution to 1024x768 (Monitor is 1920x1080) which can be changed. After this procedure it works as it should, even after waking from sleep(Well if the pc does wake up sucessfully). You can see how this is annoying.

Now my question is: Is my monitor dying or is this fixable? My second monitor works perfectly fine, none of the issues occur on it(connected over dvi if that matters). I already tried a second hdmi cable with no luck. I tried wayland but the same thing happened.

Setup: GTX1650S, driver version570.86.16, KDE on x11, newest Tumbleweed snapshot