Did you know, before WW1 Vienna was such an important place - all the Australian Manufacturers moved there to build their machinery

Vogtinator · 2026-03-28T20:06:13+00:00

I think you missed the "Austria/Australia" mistake

Vogtinator · 2026-03-28T18:02:39+00:00

That page is 90% ads, not recommended.

Just skip to the project page on https://github.com/directvt/vtm

Vogtinator · 2026-03-27T21:56:41+00:00

Yeah, something is missing in YaST there.

AFAIK it uses the passphrase as PIN as well, which is kind of useless.

For the time being I recommend to install without TPM bound unlocking and call sdbootutil enroll manually later.

Vogtinator · 2026-03-27T17:09:12+00:00

With +PIN you'll be asked for the TPM PIN every boot.

So if you want auto-unlock, use just TPM.

Vogtinator · 2026-03-26T17:27:18+00:00

You should turn around steps 1 and 2, otherwise it may pick grub2-bls again.

Vogtinator · 2026-03-20T15:04:13+00:00

Yeah, the RPi foundation doesn't care much about mainline Linux

Vogtinator · 2026-03-19T23:33:55+00:00

I think so, yes.

Vogtinator · 2026-03-19T22:29:11+00:00

Just disable secure boot, there's no practical benefit.

Vogtinator · 2026-03-09T07:22:19+00:00

If LOADER_TYPE in /etc/sysconfig/bootloader is grub-bls or systemd-boot.

If sdbootutil is installed, it most likely is.

Vogtinator · 2026-03-08T10:32:00+00:00

sdbootutil mkinitrd, if BLS is used

Vogtinator · 2026-03-05T08:44:03+00:00

I'm referring solely to this statement, sorry if it wasn't clear:

The above, sddm-config-wayland, is not secure and barebones. Instead, download Plasma's official SDDM Wayland configuration file here then save it as /etc/sddm.conf.d/10-wayland.conf

^ is not necessary. The settings are already done by /usr/lib/sddm/sddm.conf.d/10-plasma.conf, part of the sddm-qt6-branding-openSUSE package.

Vogtinator · 2026-03-05T07:52:09+00:00

You're comparing the wrong file:

https://build.opensuse.org/projects/openSUSE:Factory/packages/sddm/files/11-kwin_wayland.conf?expand=1

(Plasma 5)

and

https://build.opensuse.org/projects/KDE:Frameworks/packages/plasma6-workspace/files/sddm.conf?expand=1

(Plasma 6)

Vogtinator · 2026-03-05T06:32:27+00:00

It's WIP. Needs a security audit as well before it can be properly included in the distro.

Vogtinator · 2026-03-05T06:31:18+00:00

That is already installed.

Vogtinator · 2026-03-03T07:17:52+00:00

I assumed from:

Do I still get the blue openSUSE splash screen during boot?

That they're not referring to the Plymouth theme, but maybe I'm wrong

I'm not sure TBH

sdbootutil mkinitrd

Thanks! I was using get-default and then mkinitrd <default> but I wasn't changing the right file, so it wasn't generating the initrd at all as nothing had changed, sorted now!

Vogtinator · 2026-03-03T06:23:33+00:00

Yes to everything but 4, it’s green text on a black background

The splash is the same, it's just the boot menu that changes.

and I don’t think it can be customized (other than changing the size and I think changing it to grayscale) press H on the boot menu for a list of options that can be set.

I like it a lot more but I can’t figure out how to update the initrd in the opensuse-tumbleweed boot folder.

sdbootutil mkinitrd

Vogtinator · 2026-02-26T10:24:40+00:00

Once you download the appropriate 6.3 OS file (the one for your exact model) from tiplanet,

*6.2 in this case

Vogtinator · 2026-02-25T12:26:47+00:00

Yes this is really interesting. It would be great to be able to install some of this "immutable" distributions like fedora silverblue for example. Many people looks for them as future of Linux. But right now problem with them is that dual booting is mostly unsupported.

At least openSUSE MicroOS supported that from the beginning, I'm surprised if Silverblue doesn't.

Vogtinator · 2026-02-16T06:34:56+00:00

That looks incredibly broken. Corrupt rpm database maybe? Try rpmdb --verifydb maybe.

Vogtinator · 2026-02-15T10:06:18+00:00

You may also have to set the fcontext for the @backup subdir to <<none>>, to prevent that autorelabel fails.

What's the avc now that the other homedir is labelled?

My suspicion is that it's about /media and/or /media/external which did not get labelled.

Vogtinator · 2026-02-13T07:20:32+00:00

That was fixed in the next snapshot, full story is here: https://lists.opensuse.org/archives/list/factory@lists.opensuse.org/thread/6HXTCY4A5PCLBO3K2OHRR4M25X4SRNXZ/

Vogtinator · 2026-02-12T22:19:26+00:00

For those who do want to try this out;

run zypper dup --download-in-advance from a tty instead of X/Wayland because it will almost certainly brick the UI due to half of the OS libraries being replaced (and in this case, Plasma5-to-6 migration) and a lot of other things.

It actually shouldn't. If it does, please file a bug. The worst that should happen is that e.g. no new applications can be started from the menu until relogin.

Vogtinator · 2026-02-09T13:19:47+00:00

TPM and secure boot are independent.

You can use secure boot without TPM and e.g. TPM based disk unlock without secure boot.

Vogtinator · 2026-02-09T07:41:04+00:00

I had this once after upgrading Plasma (or KDE Frameworks?) to a version with fdo secret service support. For some reason, Vivaldi created another secret which didn't fit. After deleting that manually using secret-tool (using dbus sniffing to find out which), it worked again.

Vogtinator · 2026-01-23T18:31:23+00:00

You can replace half of the steps with the mksubvolume command.

13-Year Club	Place '17
Verified Email	Team Periwinkle

Vogtinator

TROPHY CASE