Both commands returned: command not found
Also I should mention I deleted some AMDGPU repos from /etc/yum.repos.d/ were they not important? Just making sure
Both commands returned: command not found
Also I should mention I deleted some AMDGPU repos from /etc/yum.repos.d/ were they not important? Just making sure
Please to make everyoneās life easier next times just copy/paste the console outputs (including your commands) ![]()
Maybe you donāt have om-mirror-selector installed (?)
rpm -qa|grep mirror
The command didnāt output anything
I also wish I could copy paste things here, but when I use the desktop environment it kicks me out in 1 minute, unlike the TTY session
Iām currently on the phone, typing on a screen, slowly each thing which fighting the auto correct, Iām sorry that I canāt provide the proper details that I would of preferred to give myself
Ok, weāll be more lucky next time.
Unfortunately without any full log to read itās hard to catch what the userās issue is about ![]()
Alright, I ran the update command as expected it made the system unusable
Iāll reinstall open mandriva and check if any issues persists
Everything works now, here are some logs of when I had issues that I couldnāt share easily:
Xorg.0.log.txt (56.7 KB)
xfail.txt (485.3 KB)
The main issue that happened while fixing amdgpu repo was me switching from Rock to Rolling, the X server just gave up working properly during that time, and maybe there was issues with systemd and X11? In any case, Iāve learned a lot, thank you all for the support!
I wish you an amazing day
Fixed the issue mentioned in the post by going into /etc/yum.repos.d/ and removing the AMPGPU repos that were causing issues, there shouldnāt be any AMDGPU repos there in the first place.
![]()
I didnāt need this repo, donāt remember how it got put there, Iām as confused as you there
![]()
Good thinking, I did that too on the new OpenMandriva Rock I installed, there was no such repo added or AMDGPU issues.
Probably something I did at one point but forgot
If there is something in the repo selector or the welcome that is doing that, we probably should find out and fix that. If you could retrace your steps it might help figure that out.
Nah, the repo selector works properly, tried doing what I usually do on the new install, everything works fine
This topic was automatically closed 15 days after the last reply. New replies are no longer allowed.