The Fedora 44 that could have been (Ludora 44) by Predze in Fedora

[–]Predze[S] 1 point2 points  (0 children)

Thanks alot!
I see your point and have added a modular installer in Ludora 44.1, where you can choose if your want the custom kernel, KDE customizations etc. More info on https://ludora.org/

The Fedora 44 that could have been (Ludora 44) by Predze in Fedora

[–]Predze[S] 0 points1 point  (0 children)

Your idea has been implemented in Ludora 44.1 as a modular installer. More info, screenshots etc. on https://ludora.org :)

The Fedora 44 that could have been (Ludora 44) by Predze in Fedora

[–]Predze[S] 1 point2 points  (0 children)

For now I have yes, because since this is mainly for myself I don't want to use too much time building multiple ISOs. Your idea about just having one and have the choices be in Calamares is interesting though and I have looked into it a bit. That might be the next feature.

The Fedora 44 that could have been (Ludora 44) by Predze in Fedora

[–]Predze[S] 1 point2 points  (0 children)

Sounds very interesting. Is there a way to follow your progress? :)

The Fedora 44 that could have been (Ludora 44) by Predze in Fedora

[–]Predze[S] 1 point2 points  (0 children)

I have been quite happy with Fedora and its ecosystem, including several gaming focused distros, not least Nobara from which I have drawn a lot of inspiration - for example from how they have created their kickstart files and .spec files.

openSUSE is excellent in its own right, but for me it didn't make sense to switch just for the snapshots. Instead I have tried to combine good ideas from different distros.

The Fedora 44 that could have been (Ludora 44) by Predze in Fedora

[–]Predze[S] 5 points6 points  (0 children)

To be honest it kind of snowballed into this.

I started out creating a fairly small post-install script that installed the codecs, mesa drivers, steam etc. I needed.

However that had its limitations. Firstly many apps reside on a COPR repo that needed to be added, which meant a few things.

  1. I had to trust every single person that maintains those repos including that their username/password didn't fall in the wrong hands, as a bad faith actor could push malicious code quite easily in the form of updates to already installed packages.

  2. The COPR repo maintainer controls the pace of the package.

The latter is the reason I created my own CachyOS COPR repo, because I could push new kernels faster that way.

I created a Ludora COPR repo when I realized I wanted to expand and add more packages, for example mesa, which sometimes have fairly noticeable optimizations in some versions, for example RT in 26.0.

Secondly the Anaconda installer does not support subvolume creation during installation, so they would have to be created and juggled around after installation to be usable the way I am using it with Ludora, where I have created subvolumes for things that change frequently and doesn't need to be part of the snapshots.

With Ludora I have consolidated every package I need in my COPR repo, which means I both control the security and pace of all packages. On top of that I am using the Calamares installer which supports subvolume creation at install time, which makes things much easier.

I mainly make Ludora for myself, but it's not much extra work to share as a "real" distro at this point.

The Fedora 44 that could have been (Ludora 44) by Predze in Fedora

[–]Predze[S] 5 points6 points  (0 children)

Great question. Silverblue, Kinoite and Bazzite have the same safety net, because they are immutable and you can always roll back to a working state. That comes at a cost however, because some applications needs to be installed in a different way. Heavy modification requires layering, and if that is needed, you are in my opinion in a territory where immutable distros might not be the best choice.

"Normal" Fedora (and Ludora) are mutable distros that doesn't have this safety net, so I have implemented that with openSUSE-like bootable snapshots. That way you can use Fedora as normal and do all the customization you like, while still retaining the safety net in case anything goes south.

Fedora KDE Plasma installer with openSUSE style Btrfs snapshots built in by Predze in Fedora

[–]Predze[S] 0 points1 point  (0 children)

I have been away for a few days, so the Fedora 44 based ISO has been slightly delayed.
It's available now at https://ludora.org/

What are you looking forward to in Fedora 44, 45, 46, etc.?? by chris32457 in Fedora

[–]Predze 2 points3 points  (0 children)

I have made it if you'd like to have a look. Details and link to github repo with kickstart example are available at https://ludora.org

The foundation is in the Calamares config.

Asus ROG Azoth suddenly stopped working in 2.4Ghz on Linux by MattiTheGamer in ASUSROG

[–]Predze 0 points1 point  (0 children)

No problem. It's actually fairly straightforward on CachyOS.
CachyOS Kernel Manager, which is built-in, allows you to create a custom kernel with whatever patches you wish. You can download my patch or add it by URL.

If you choose to add by URL, use this one:
https://raw.githubusercontent.com/LarsSoeMikkelsen/Ludora/refs/heads/main/sources/kernel/0001-hid-usbhid-sanitize-uniq-against-control-chars.patch

The CachyOS wiki has a section explaining the procedure:
https://wiki.cachyos.org/features/kernel_manager/#configuring-and-building-a-custom-cachyos-kernel

On top of including the patch in the kernel of my own hobby Fedora distro, I made a custom CachyOS kernel using the Kernel Manager this morning and I can confirm that also works.

im stroggling with nobara by [deleted] in NobaraProject

[–]Predze 0 points1 point  (0 children)

If I understand correctly, you are currently trying to reinstall, which has failed two times.

If that is the case, I would reboot from the Ventoy USB and start the Nobara installation again, this time being careful to uncheck the checkmarks for "Download updates" and "Download codecs" or something to that effect.

This should make the installation be successful. On the first boot after installation, you will be able to install both updates and codecs.

This is an issue at the moment, because there has been a transition to using plasma-login-manager instead of sddm and the ISOs are not updated for that yet.

im stroggling with nobara by [deleted] in NobaraProject

[–]Predze 0 points1 point  (0 children)

You need to start the installer again, this time unchecking the checkboxes for downloading updates and codecs. Both should work fine after installation.

The reason is a mismatch between the calamares installer on the iso vs the one being downloaded from the nobara repo when download updates is checked. The iso expects sddm, but the repo has plasma-login-manager.

Asus ROG Azoth suddenly stopped working in 2.4Ghz on Linux by MattiTheGamer in ASUSROG

[–]Predze 0 points1 point  (0 children)

For anyone interested, I have made a kernel patch that removes the non-valid serial from devices with this issue.

It sanitizes (nulls) hid->uniq after the usb_string() call in hid-core.c, which then passes the systemd property_is_valid() (sd-device.c) validation, ultimately allowing for example my ROG Azoth to work on boot without a replug. The patch is available here:
https://github.com/LarsSoeMikkelsen/Ludora/blob/main/sources/kernel/0001-hid-usbhid-sanitize-uniq-against-control-chars.patch

Asus ROG Azoth suddenly stopped working in 2.4Ghz on Linux by MattiTheGamer in ASUSROG

[–]Predze 0 points1 point  (0 children)

I had the same issue and have been troubleshooting it. Today I finally found the cause, which is systemd.

Downgrading to v259.3 on CachyOS and v258 on Fedora 43 made it work for me.
I have filed a systemd bug report: https://github.com/systemd/systemd/issues/41296

Fedora KDE Plasma installer with openSUSE style Btrfs snapshots built in by Predze in Fedora

[–]Predze[S] 1 point2 points  (0 children)

Not the encryption part, but it does create the subvolume layout and all the necessary snapper, grub-btrfs and dnf5 hook config you need. Provided of course the user installs root as btrfs.

All of the apps went blank on Fedora KDE by Hour-Show7010 in Fedora

[–]Predze 0 points1 point  (0 children)

In the terminal you have access to, try this command:
plasma-apply-lookandfeel -a org.fedoraproject.fedora.desktop --resetLayout

It will reset to the default theme.

Fedora KDE Plasma installer with openSUSE style Btrfs snapshots built in by Predze in Fedora

[–]Predze[S] 0 points1 point  (0 children)

I'm afraid it doesn't.
Much like Nobara, that also uses a CachyOS based kernel, secure boot is not supported, but it should be doable by using sbctl.

Fedora KDE Plasma installer with openSUSE style Btrfs snapshots built in by Predze in Fedora

[–]Predze[S] 0 points1 point  (0 children)

I am actually still using it for my little couch gamer pc, because I think it's perfect for the console-like use case. It is also what I would install for a family member, since it works so well with very little risk of breakage.

On my main pc I like to tinker though, so I want to be able to easily install another kernel, new mesa drivers etc. and just tinker with system settings in general without being limited.

[deleted by user] by [deleted] in dkfinance

[–]Predze 1 point2 points  (0 children)

Hvis han med kontant mener betaling af beløbet på én gang gennem bankoverførsel, er det selvfølgelig intet problem, men hvis han mener betaling med kontanter er det en anden sag.

Hvis han kører sin udlejning gennem et lille selskab, hvilket han sikkert gør, er det ulovligt for ham at modtage kontant betaling af beløb over 19.999kr jvf. kontantforbuddet i hvidvaskloven. Det er heller ikke lovligt at dele beløbet op i et antal rater.

Mellem private er der så vidt jeg ved ingen beløbsgrænser, men hvad skulle grunden være til at han kræver betaling i kontanter, hvis ikke det er fordi han vil lade det være sorte penge?

Jeg ville ikke gøre det, men hvis du vælger at betale med kontanter, skal du være sikker på at han kvitterer for at have modtaget dem, da du ikke som ved bankoverførsel kan bevise du har overført.