Currently proprietary hardware are handled by nouveau

[For Bug Fix]: Failed to boot from ISO - findfs unable to resolve LABEL=RLXOS

As already told that rlxos is booting successfully on our every test system (boot uefi or legacy) but most users are facing the issue findfs: unable to resolve LABEL=RLXOS. So its little bit difficult to resolve a issue which we are not able to reproduce on our systems.

Its a little try to know more about the issue. I have create 3 ISOs that just boot, search-and-mount system image from ISO and print a success message present inside system image.

You can get the ISO from here: https://apps.rlxos.dev/iso-test/

• rlxos-grs-zero: 37 MiB contains minimal set of dynamic modules.
• rlxos-grs-uba: 42 MiB contains targeted set of dynamic modules i.e usb (host, storage).
• rlxos-grs-all: 47 MiB contains all recommended set of dynamic modules.

Test Order

rlxos-grs-all
      |
      |---> Fail : report here
      |---> Pass
               |----> rlxos-grs-uba
                                |
                                |---> Fail: report here
                                |---> Pass
                                          |---> rlxos-grs-zero
                                                         |
                                                    Report here either fail or pass

All the 3 ISOs are pack with grub-rescue method to test the proper working of initial ramdisk image.

URL that may help:

Source Code: https://github.com/rlxos/initramfs/

Script that generate ISO: https://github.com/rlxos/initramfs/blob/main/test/test.sh

Bug Report: #1

Kernel Configuration: https://github.com/rlxos/kernel-config/blob/main/config.x86_64

Hello,

When i m going to the flathub, i choose Clementine. I click "Install" then the file is charging on a directory. But you must transfer it in another directory. However it doesn't work.

See attached files.

my mail : [email protected]

Problem with https://rlxos.dev/: title is always Home - rlxos, even in download page.

Update the documentation accordingly. Swupd is not an "in-house" developed package manager. It is developed by Intel and Clear Linux Project. Reference: https://github.com/clearlinux/swupd-client/blob/master/docs/swupd.1.rst

The wording on the docs should be changed to avoid future problems.

• IBM Plex Sans fonts as default UI Fonts
• Fira Mono for monospace
• Panel theme tweaks

How to reproduce

• Touch screen working fine in normal laptop mode
• Fold device in tablet mode
• After 10 - 20 sec, touch screen stop working?
• Unfold back to laptop mode make things work again

I'm suggesting the integration of dm-verity as a mechanism to verify the integrity of the root partition during the boot phase. dm-verity provides a robust and proven solution to detect any unauthorized modifications that might have occurred while the system was powered off.

msg error on boot: cant find rootfs LABEL=RLXOS, stop boot!

• GRUB2 Bootloader
• OS-INSTALLER update installation process configure.sh for grub2 bootloader
• SYSTEM-IMAGE update system image for bios system

update swupd::upgrader method to add tree to support package layering

instead of replacing with current infrastructure, will create a new board boards/amd64-secure for EFI only devices with secure boot enabled

When I try to update the system, by typing in bolt update my system, it returns

upgrading system
error: loading sysroot: openat(boot/loader/version): No such file or directory
failed to get system updates
hello

That is a freshly installed system, from an ISO downloaded yesterday. I am using rlxos workstation, Linux kernel version 6.0.7 with EFI support. The laptop is Lenovo X380 Yoga. Restarting the system did not help.

• Bluetooth: blueman
• User Manager: User Admin??
• Service Manager: ???
• Ostree and Updater Manager: ??
• Display Manager: Lightdm-gtk-greeter-settings
• Printer Settings: Printer Config

Variants:

• Core
• Desktop
• Workstation

Channels:

• Experimental
• Stable

• BUILDSTREAM Plugin for AppImage build process
• BUILDSTREAM Configurations for multiple AppImages
• METADATA export for AppImage configurations
• SOFTWARE CENTER support for AppImage METADATA

Would be helpful to write a couple of paragraphs on how to build a custom image and stuff

Export the alias to container name for better shell script

#!/bin/sh

distrobox enter ubuntu-22-10 gcc main.c -o ubuntu-22-10-a.out
distrobox enter ubuntu-21-04 gcc main.c -o ubuntu-21-04-a.out
distrobox enter debian       gcc main.c -o debian-a.out
distrobox enter arch         gcc main.c -o arch-a.out

can be rewritten as

#!/bin/sh

ubuntu-22-10 gcc main.c -o ubuntu-22-10-a.out
ubuntu-21-04 gcc main.c -o ubuntu-21-04-a.out
debian       gcc main.c -o debian-a.out
arch         gcc main.c -o arch-a.out

and still able to use distrobox flags like --root

Describe the bug
Using build.sh, as provided by the official rlxOS repository, leads to a build failure fairly early on at the "reinstalling pkgupd" section of the script. Executing the same command (sudo pkgupd in pkgupd --force --skip-depends) outside the script does not yield an error.

To Reproduce
Steps to reproduce the behavior:

1. Install newest build of rlxOS in GNOME Boxes
2. Install both git and docker via pkgupd
3. git clone https://github.com/itsManjeet/rlxos.git
4. Start docker daemon by running "sudo dockerd"
5. Execute "sudo ./build.sh -p desktop"
6. After docker has pulled ~300mb, script tries to execute "pkgupd in pkgupd --force --skip-depends"
7. "Error! Failed to reinstall pkgupd"

Expected behavior
Script should build rlxOS. Executing "sudo pkgupd in pkgupd --force --skip-depends" outside the script does work as expected.

Additional information
I am currently trying to learn as much as I can about the current state of immutable Linux distributions, including the different strategies projects use to build bootable images (Lorax, Buildstream, etc.), which leads to me occasionally stumbling across an issue when it comes to reproducing official builds. Hope, that this isn't just a case of me being incapable of following the build instructions. Additionally, I would love if there was some more in-depth information on how PKGUPD handles the immutable nature of rlxOS, compared to for example rpm-ostree on Silverblue. I will dive into the source code of PKGUPD myself, so I can get a better understanding how it works, though a technical explanation by the creator would of course be very helpful.

swupd layers add <LAYER_ID> devel fail without any error