[einar.hjortdal]

[root@buildvm /]# curl https://push.openmamba.org/pub/openmamba/base/SRPMS.base/
curl: (6) Could not resolve host: push.openmamba.org (Timeout while contacting DNS servers)

You guessed right

[einar.hjortdal]

Hi thank you for the reply. I am experienced with rpmbuild. I imagine the /var/autodist/RPM is the usual rpmbuild directory

The build environment is selected just like in your screenshot, but I have no spec to select. I have F5’d but no changes.

Attachments:

You must be logged in to view attached files.

[einar.hjortdal]

I have the container running on my system and the web interface open in my browser.

What I’d like to do is to add a patch the the kernel and get it to package it.

At the top of the web interface I select the base repository, and the SRPMs select appears, but it has no options. What should I do?

I also have spawned a shell in the running container according to the instructions, I suspect I have to setup something else in it through it.

I have also forked the kernel repository on the gitea, to version my changes.

[einar.hjortdal]

Silvan wrote:

discovery is a strict requirement of the KDE Plasma desktop environment as it is provided by openmamba so it is by design a requirement of the desktop-base-kde meta package.

This is what I wanted clarity on.
On other distributions I’ve used previously, discovery is not a strict requirement for plasma.
If this is how it is for openmamba then it is how it is, despite how unnecessary it may seem to me.

[einar.hjortdal]

Is it normal for desktop-base-kde and kwin-x11 to be removed when a user tries to remove discovery? Shouldn’t those packages be independent?

[einar.hjortdal]

I have reinstalled openmamba and I think I understand what is happening:
After installing I tried to remove discover with sudo dnf remove discover

$ sudo dnf remove discover
Dependencies resolved.
================================================================================================================================================================================
Package                                         Architecture                         Version                                      Repository                              Size
================================================================================================================================================================================
Removing:
discover                                        x86_64                               6.4.0-1mamba                                 @rolling                               6.9 M
Removing dependent packages:
desktop-base-kde                                x86_64                               6.0-7mamba                                   @rolling                                35 k
discover-notifier                               x86_64                               6.4.0-1mamba                                 @rolling                               341 k
mambatray                                       x86_64                               5.3-1mamba                                   @System                                 51 k
Removing unused dependencies:
kwin-x11                                        x86_64                               6.4.0-1mamba                                 @rolling                                12 M
libkwin-x11                                     x86_64                               6.4.0-1mamba                                 @rolling                                12 M

Transaction Summary
================================================================================================================================================================================
Remove  6 Packages

Freed space: 32 M
Is this ok [y/N]: n
Operation aborted.

I had discover uninstalled before the plasma 6.4 update.

• This reply was modified 1 year ago by einar.hjortdal.

[einar.hjortdal]

I think the recent merges fixed the issue

[einar.hjortdal]

It must be the nvidia_470 package. I’ve uninstalled I can successfully start kernel 6.12.30
However, if I install nvidia_470 while running kernel 6.12.30, the problem reappears on the next reboot.

[einar.hjortdal]

Silvan wrote:

Hi, does access to any virtual console work by pressing CTRL-ALT-F2..F8? This would allow retrieving log information from the console to identify the cause of the issue. If not, the only way to get useful information would be to start the kernel with the “debug” menu choice (or removing “quiet splash” from Grub command line). Did you by any chance install the “nvidia” proprietary driver?

CTRL-ALT-F2..F8 do not seem to work. Starting the kernel with debug messages doesn’t show any useful messages, the only line shown is the efi stub loaded initrd.

I do have the nvidia_470 package installed on 6.12.20 and it still seems to work when booted with this kernel. I had my own suspicion that the cause of the issue is that, but I have no proof.

[einar.hjortdal]

Silvan wrote:

openmamba is in fact a single maintainer driven distribution

I had no idea. Damn! You’re doing an incredible job.

Silvan wrote:

The same may be applied to .spec files

This is what I had in mind, I had contributed to OpenMandriva a couple years ago and they accepted .spec files and relative patches. Their build system builds the package by pulling sources and compiling when necessary, then puts it on the repository. No uploading of binaries.

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.

[einar.hjortdal]

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

[einar.hjortdal]

I’ll try to be as precise as possible regarding what I did then. When you suggested to check the CPU frequency with cpupower-gui I did the following:

1) fresh boot of openmamba. run cpupower-gui and noticed CPU being stuck at 800Mhz on all threads.

2) sleep/wake the system. cpupower-gui shows CPU clock boosting correctly. Now I did update and a kernel update was included in the update. This doesn’t do good to isolating causes, I agree.

3) rebooted. run cpupower-gui and noticed CPU boosting correctly.

I was not aware that there is a cpupower-gui-user service. I do not know cpupower at all, I thought it was just a utility to show CPU behavior, I do not know if it actually does act on the CPU behavior.

All I can say besides that is that this issue appeared in every installation of openmamba I have done on this system. I hope it’s gone for good on this installation!

[einar.hjortdal]

Today after a system update and a clean boot, the problem was not replicable any longer. Maybe a patch fixed it?

[einar.hjortdal]

Actually, I think cpupower-gui showed a lot! Thanks for the suggestion.

After a boot, cpupower-gui shows each core is stuck at 800Mhz, after a sleep/wake it behaves as expected and boosts up to 4Ghz when needed.

[einar.hjortdal]

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 would like to clarify: the issue shows even without user-installed VSCode and/or Microsoft Edge.

The slowdown can be clearly experienced with Dolphin and KSystemLog, for example.

It is however very obvious when VSCode and Edge are running because they’re more complex programs that use more system resources than anything else my openmamba installation has, as far as I know.

openmamba uses the LTS 6.6 kernel, if the hardware is recent it might be better supported by more recent kernel

The hardware is relatively old: intel i7 4790K and nvidia gtx 780, I do not believe kernel support is the issue.

So far I can consistently replicate the disappearance of the issue after one single sleep/wake cycle. Something clearly happens with that, but I don’t know what.

Every time I boot openmamba, I immediately put the system to sleep and wake it up, this resolves the issue until the next reboot.

Given that sleep/wake reliably solves the issue, do you have any guess for what to investigate?

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.

I can verify if cpupower-gui shows anything before/after a sleep/wake cycle.

• This reply was modified 1 year, 4 months ago by einar.hjortdal.

[Author]

Posts