My experience installing and using OM on my daily driver

Support
1

Hello,

I am finally ready to move my daily driver notebook to OM and wanted to let you know about how it went and my struggles. So far no help needed and this is just informative for other users or the devs.

I have a SSD with Windows on the machine and another SSD with arch on luks encrypted btrfs. Since I want to run the arch installation in a VM on OM when I finished the move, I wanted to install OM on a new partition side by side to the arch installation.

So I booted the OM live iso with Ventoy (which works now!) and used the partition manager to shrink the partition. Here I expected some issues, but that also worked easy and flawless.

Then I tried installing OM on the new partition (option replace partition in the calamares installer), which gave me an error at the end of the installation process, which seems to be the same error as here (Installation from USB fails with bootloader script exception - #33 by 0x6A7232). So I tried the workaround by setting installEFIFallback to false in /etc/calamares/modules/bootloader.conf and reinstalled and that worked.

Then I tried booting into OM and of course, although I knew that this would be a problem, I installed the wayland znver version and have a nvidia dGPU and a second monitor connected to it and it showed only a black screen and nothing else (as already reported by several people). I tried removing all connected devices and booting the recovery mode (or what it is called in the boot menu), but still no luck. It only shows this

Loading Linux 6.14.0-desktop-20mv2590 ...
Loading initial ramdisk ...
_

EFI stub: Loaded initrd from LINUX_EFI_INITRD_MEDIA_GUID device path
EFI stub: Measured initrd data into PCR 9

I then tried booting arch, which still worked and I also tried booting Windows, which still worked (from both the BIOS boot menu and from the OM grub boot menu). So that’s a good thing at least.

Now I am currently downloading the znver X11 version and try again. I’ll post here again and let you know how that went.

  • OpenMandriva Lx version: OpenMandrivaLx.rolling-snapshot.20250326.3802-plasma6.znver1.iso

  • Desktop environment (KDE, LXQT…): KDE

  • Relevant informations (hardware involved, software version, logs or output…): ROG Zephyrus G15 with AMD Ryzen CPU and a dGPU nvidia RTX 3080

1 Like
2

I am moving this to Support because it is more appropriate even if you don’t necessarily want others to assist with it.

2 Likes
3

I am moving slowly, but here is an update.

The system boots now. It worked with the X11 version and later I installed wayland which worked. I also had troubles with the kernel 6.14 so I am using 6.13.9 now.

For TeamViewer I installed it from the website, but it didn’t work with wayland and errored with “Aborted (core dumped)”. To get it working I need to start it with QT_QPA_PLATFORM=xcb teamviewer, so I created an alias for it.

For Anydesk I used the flatpak version, since the dnf version did not work.

I installed the asus driver for my laptop according to https://asus-linux.org/ and asusctl and supergfxctl without issues, but when I rebooted my wifi was not working anymore. I thought it had to do with the installation, but after some troubleshooting I found the issue. I dual-boot and had Windows hibernated and that seemed to have somehow locked the wifi card. After shutting Windows down it worked again. Weird is that it worked before and it works now when I hibernate Windows.

Installing netbird didn’t work, because I got some GPG error for the repo. I fixed this by changing from repo_gpgcheck=1 to repo_gpgcheck=0 in /etc/yum.repos.d/netbird.repo

Nextcloud was also not so smooth. I installed it via dnf, but that version crashed when I enabled experimental features for the virtual files support. The flatpak version worked for the virtual files though and so I use this now. For the dolphin support I installed the dnf package nextcloud-client-dolphin, which depends on the dnf version of nextcloud, so I have this also installed. I disabled the autostart for the dnf nextcloud client and removed it from the menu. I also manually added a menu entry for the flatpak version, since it somehow wasn’t created. I also enabled autostart for the flatpak version and this set up works for me now.

To get access to my Windows disk (which is bitlocker locked) I used dislocker and mounted it with sudo dislocker -V /dev/sda1 -p315442-000000-000000-000000-000000-000000-000000-000000 -- /media/windows (replace your own bitlocker key and source partition) and then mount -o loop /media/windows/dislocker-file /media/mount. This worked

That’s where I am right now and still lots of stuff on my todo list until I can use OM on my daily driver. And don’t get a bad impression here, I am listing all the stuff I had troubles with or which needed special treatment, not the things that went without issues (which is the majority).

The next things I want to do is setting a VNC server up, which is easy with x11vnc, but since I want to use wayland, I have to find out how.

1 Like
4

Thanks for moving it. I was thinking about putting it in “Support” but was unsure.

1 Like
5

Good. Me too.

Please file a bug report. :smiley:

The flatpak might be much newer. Please file a bug report.

Our default limit of kernels installed at one time is limited to 3. If you would like to raise that limit, you can easily do so by editing

/etc/dnf/dnf.conf

and changing the number on the line

installonly_limit=3

I changed mine to 9, but I am not worried about space.

6

The dnf version of anydesk works now. I just tried it.

This is a nextcloud issue and effects new versions of Nextcloud. The flatpak version is actually older and thus unaffected. Here is the bug report: [Bug]: macOS Virtual files VFS not working on Nextcloud 3.15.3 · Issue #7979 · nextcloud/desktop · GitHub

edit: Whoops, wrong bug report for macOS. But there are several VFS bug reports already.

1 Like
7

If this topic is going to turn into support request please open a new topic for each issue instead.
If the good-willing people will start to reply here we can’t have them documented for the posterity.