I have [Searched] the forum for my issue and found nothing related or helpful
I have checked the [Resources) ([Resources Index]
I have reviewed the for relevant information
I have read the the [Release Notes and Errata]
OpenMandriva Lx version:
25.12 (Rome) Rolling for znver1
Desktop environment (KDE, LXQT…):
Doesn’t work
Description of the issue (screenshots if relevant):
Ever since the clean install of the latest OpenMandriva Rome, whenever the AMDGPU repo would get refreshed, it would output how it could not resolve host name.
I tried looking online (and in the resources above before posting this) and I couldn’t figure out how it would get resolved.
Today I tried to change from Rock release to Rolling release in the package manager UI of OpenMandriva, which let KDE to stop working due to AMDGPU repo not being available
I tried installing plasma without a desktop environment, but all repos output errors such as:
“Curl error (6) Could not resolve host name for repo Radeon AMD GPU 30.20.1”
Repo Radeon graphics 7.1.1
Repo Radeon rocm
Apologies for some oddities in the post, I’m currently on the phone while my main pc doesn’t have a desktop environment currently
Relevant informations (hardware involved, software version, logs or output…):
I’m on zen3 CPU and rDNA 3 GPU
I enabled additional repos from the repo selection of open mandriva
Yup, I can access the computer using the terminal, just no visual interface due to amdgpu repos not working
The amdgpu driver is a kernel module, to my knowledge, there should be nothing to install or enable. If you get a graphical desktop using startx then it sure would seem that graphics is working meaning amdgpu driver is working.
The repos are name main, extra, non-free, and restricted. I do not know what AMDGPU Repo even is. And I do have AMD graphics. My graphic hardware:
Edit: I may not fully understand the problem but it sounds more like something wrong with sddm or something with authentication. The output of dmesg orjournalctl is likely to tell us what the problem is. To start with lets get the output of dmesg like this:
dmesg > dmesg.txt
That creates the file dmesg.txt which you can post here. You want to do this after a boot that did not automatically boot to graphical desktop. Let’s see what that tells us.
I should correct myself, yes there are repos with radeon or amdgpu but those are not for user install that I know of. I presume that they are used by kernel.,org to add the modules to the Linux kernel packages. (As I understand things.)
this is what I see everytime I update open mandriva from the open mandriva GUI updater, at first I ignored it, but then this AMDGPU thing is what messed up the switch from Rock to Rolling, plus all GPU sensors are missing on plasma system monitor when I was on Rock
Thankfully I now know about the startx command, so whenever I log in on the TTY session I gotta do this command to properly start things
I do not see any problem in your dmesg log that I recognize. I am not a developer. The dmesg covers the boot process up to, but not including, when the system would start loading the graphical desktop. So unless I missed something a dev would see the boot process looks like it is working OK.
Why are the amd and rocm repos there? Those are not OpenMandriva repos. These:
Are not realated to OpenMandriva we can not do anything about that. I would disable those until I had my system sorted. There may be good reasons to have those, but simplify to solve the current problem.
Is one mirror of a list of mirrors, If you are using the default OM repo setup then Mirrorbits is redirecting you to another mirror. That is demonstrated by this line:
Repositories loaded.
But there is a problem, a big one:
Failed to resolve the transaction:
Problem: The operation would result in removing the following protected packages: systemd
There is a fix for that here. systemd is the init system and it does affect the loading of the desktop so this may well be the problem, in any case this must be corrected before proceeding further in problem solving.
Now back to the title of this thread. Repo of AMDGPU could not resolve host. That has nothing to do with OpenMandriva. I would suggest you contact where ever you got those repos from. I believe that would be https://repo.radeon.com. We can’t do a thing about dnfor curl not finding that url.
Edit: I admit to being slow to recognize what this problem was, it should have been obvious even to this old man.
As far as the desktop not starting automatically that should not be happening and we are happy to help with that. But the title of the thread should be changed to reflect that or a new thread with a descriptive title started.
While trying to remove the libre wolf repo that cause issues I noticed there was additional AMDGPU repo in /etc/yum.repos.d/ so I removed those and the errors when away but
Removed 6 files, 8 directories (total of 19 MiB). 0 errors occurred.
repo id repo name
rolling-znver1 OpenMandriva Rolling - znver1
Updating and loading repositories:
OpenMandriva Rolling - znver1 100% | 1.1 MiB/s | 5.8 MiB | 00m05s
Repositories loaded.
Failed to resolve the transaction:
Problem: The operation would result in removing the following protected packages: systemd
You can try to add to command line:
–skip-broken to skip uninstallable packages
Press enter to close konsole
While running the update GUI, it is still trying to remove systemD, is there something else I should remove?
I did the fix mentioned to stop the updating process trying to remove systemd
Although sudo dsync --allowerasing --refresh threw an error saying it didn’t know what dsync meant
Now the login kinda works, it goes to UI login on boot, but after login it hangs 30 seconds before the session starts (black screen and a white _ blincking top left as if it is a terminal)
When updating, it’ll say there is a curl error Openmandriva mirror lite server rolling repo (no other errors yay)
Also tries to remove 3gb and add 100mb worth of packages, and some of the packages included in the removed 3gb worry me because they look quite important like dnf and sudo
Also after the session starts, it lasts about 1 or 2 minutes before it forcefully logs me out