[Silvan]

Many thanks for adding openmamba-KDE6 to your WSL howto project and for sharing in this forum!

[Silvan]

Good. User can just be added to the sysadmin group to give root permissions with sudo, adding to this group is also recommended for polkit policies.

[Silvan]

Hello,
the command to add a user in openmamba is  useradd. See also man useradd.

You need to install KDE Plasma 6 because you used rootfs-base for the installation`? The command is:

sudo dnf install desktop-base-kde

If you need the graphical login manager also sudo dnf install sddm may be needed.

[Silvan]

einar.hjortdal wrote:

Silvan wrote:

A contributor might want to start learning and creating packages for openmamba in his local environment and if you express that you have this interest the discussion might evolve into discussing the technical details on how to do this.

I would like that. And if necessary, I may host my own user rpm repository, with packages built according to openmamba standards.

Good,
the most straightforward and interesting way to start is by creating and using a Docker buildvm image which provides you locally with the webbuild interface, which is what is used to create and update openmamba packages. I’ve checked that it currently works correctly by cloning the openmamba-docker-buildvm repository:

git clone https://src.openmamba.org/openmamba/openmamba-docker-buildvm

and follow the instructions in the project page.

We can discuss about any doubts or problems before or after you have setup the Docker buildvm container.

[Silvan]

einar.hjortdal wrote:

Silvan wrote:

Contributing by making packages which openmamba users might install would require by the way some sort of user identification for legal reasons. If there is interest for this we can go into more detail.

I am surprised by this. Is this a requirement of the openmamba project, or is it an actual european/local issue? I value my online anonymity

There is currently no policy about accepting contributors in openmamba. I’m responsible of openmamba servers and consequently about the risks of accepting people to do things for which I might become at least part of a chain of responsibilities. openmamba is in fact a single maintainer driven distribution which makes it different from a community driven distribution, maybe I should make this more clear so that users may better target their interest, questions and comments accordignly.

A packager might well remain under a pseudonym for the public but I need to accept only trusted people (by me) for binary packages submissions on openmamba repositories. Because you cited Arch Linux, you may have already read their policy for maintainer where candidates need to be presented by two sponsoring maintainers and voted for admission. Contributing to AUR is far less strict because people are only expected to send the PKGBUILD file (plus any patches and other related files), a text file which can be easily audited. The same may be applied to .spec files but openmamba distributes binary packages so things are different in terms of letting anybody to upload packages.

A contributor might want to start learning and creating packages for openmamba in his local environment and if you express that you have this interest the discussion might evolve into discussing the technical details on how to do this. This might be a step allowing to evaluate the quality of the produced packages followed by giving the authorization to send contributions to the openmamba hosted repositories.

• This reply was modified 3 weeks, 4 days ago by Silvan.

[Silvan]

As of today and for the last years there have been no users contributing so there are currently no contributions although a repository called devel-contrib exists for this.

So, if you are looking for contributions you will find nothing, if instead you want to propose yourself as a contributor, i.e. making packages that will be hosted in the openmamba devel-contrib repository and eventually be imported to the base repository, I may work to refresh and provide the tools and interfaces for contributors to make rpm packages according to openmamba standards. Contributing by making packages which openmamba users might install would require by the way some sort of user identification for legal reasons. If there is interest for this we can go into more detail.

The two /etc/yum.repos.d and /etc/yum/repos.d folders exist and are both supported because some external software  may provide their repository expecting to use the first path, while other tools like dnf (and openmamba) use the second path. One folder should be a symlink to the other but I have given this change a low priority because replacing folders with symlinks has always been a pain with rpm.

[Silvan]

Nothing was specifically patched. Generally speaking the only relevant update might be the kernel update but if you update daily it was not in today updates.

I find it more likely that by running cpupower-gui you fixed its behaviour at startup, because in the old report there was this in the logs:

cpupower-gui[5372]: Applying configuration...
systemd[5330]: cpupower-gui-user.service: Main process exited, code=exited, status=255/EXCEPTION
systemd[5330]: cpupower-gui-user.service: Failed with result 'exit-code'.
systemd[5330]: Failed to start cpupower-gui-user.service.

These considerations are based on and limited by the information I have.

[Silvan]

You may want to try to remove the cpupower-gui package which is currently the only guess about CPU frequency improperly set.
For further investigations from this side you may also want to send two reports: one after boot when the system is slow and another after a sleep/resume cycle.

[Silvan]

The described symptoms of low preformances are related to VSCode and Edge. According to a former report VSCode is manually installed in user home and the report showed a lot of processes running.

In order to be able to help troubleshooting bad performances in openmamba installation itself it is adviced to report the issue when no custom software is installed and running, i.e. no scripts and processes from third party software or else recognize that the performance throubleshooting help requested is related to running custom installed VSCode and Edge. Additionally, openmamba provides VSCode with the package visual-studio-code-bin which I frequently use for software development.

General comments follow.
When observing slow performance with an openmamba component, i.e. extracting a tar archive as written in former report, the operation can be monitored for CPU and and I/O usage. If it is a CPU performance problem, tools would report 100% usage of one or more cores. A tool like cpupower-gui might help to check and set the CPU usage for appropriate performances in terms of clock frequency. When I/O is causing slowness, different things might be checked which I’m skipping here. When no system log errors are show, CPU and I/O usage are reported as idle while uncompressing but the user sees slowness it would be the kernel that is not working correctly. openmamba uses the LTS 6.6 kernel, if the hardware is recent it might be better supported by more recent kernel. This (which kernel version when it works better) can be cross-checked since you have reported a list of other Linux distribution where you don’t have the issue.

 

[Silvan]

For anybody which might be interested I explain in short (for advanced users and untested) how to start to to manually install a minimal distribution of openmamba:

1. boot any Linux OS with networking
2. use i.e. curl or wget to download the openmamba rootfs-base archive from the download page
3. initialize the destination storage by creating the partition table (GPT or MSDOS) and a FAT32 EFI boot partition (2-300 MBytes) and an ext4 partition
4. format the partitions respectively with the mkfs.vfat and mkfs.ext4
5. mount on some mount point the O.S. partition (ext4) and bind mount the boot partition at /boot, aso bind mount /dev,/sys,/proc,/run from the running O.S.
6. run chroot to get an openmamba chroot shell in the O.S. partition
7. install the kernel (dnf install kernel-mamba-x86_64)
8. install grub packages (dnf install grub grub-efi-x86_64)
9. set a login password for the root user with passwd command
10. exit from chroot, unmount and try rebooting
11. you expected that probably something might not work, this can be discussed and fixed

[Silvan]

Calamares installs by cloning the squasfs which runs the ISO image. Either it is not possible or I don’t know how do what you say with Calamares plus it has not been a priority for openmamba so far.

[Silvan]

For reference, the issue with nvidia-470 driver has been discussed here. Thank you for testing and providing useful information to fix the package.

• This reply was modified 1 month, 3 weeks ago by Silvan.

[Silvan]

There is not an ISO provided without desktop mostly because it would need an installer from terminal. For a headless installation the available options are rootfs-base archive and the docker image.

[Silvan]

Hi,
the package providing legacy nvidia_470 driver is known needing to be reviewed and from the contents of your post it seems that the nvidia module fails to build.
As a first step, the system should correctly work with the Intel GPU, but the report you sent shows that the graphical subsystem is giving priority to the nouveau driver which is know to behave bad on many chipsets, so I would first of all remove both the nouveau and the nvidia drivers:

sudo dnf remove xf86-video-nouveau xorg-drv-video-nvidia_470

Then the system is expected to behave normally using Intel GPU while trying to fix the nvidia_470 driver would be a next step.

[Silvan]

Hi,
the problem affects systems which have been updated between 1st and 2nd of July and should be fixed manually by issuing the following command from a terminal:

sudo rpm -U https://openmamba.org/pub/openmamba/base/RPMS.x86_64/librepo-1.18.0-1mamba.x86_64.rpm

• This reply was modified 8 months, 3 weeks ago by Silvan.

[Author]

Posts