Hello everyone,
I joined the Forum today.
I had installed **openSUSE-42.3(Leap) 64-bit ** successfully onto my DELL 14 Inspiron 5447 Laptop with ease.
It was performing and functioning amazing,till yesterday.
But due to some of my “noobish” attitude as I tinkered within the Yast2 the software access level,some issues and problems have cropped up.
Konsole Terminal is not starting by clicking it.
The worst of all is that Yast2 is not opening even after providing the correct root/superuser password.:disapointed:
But** Terminal** is working fine,and here is what it shows :—>
linux-n5q8:/home/kg17Taban # yast2
amdgpu_device_initialize: DRM version is 1.6.0 but this driver is only compatible with 3.x.x.
/sbin/yast2: line 447: 7054 Segmentation fault (core dumped) $y2ccbin $Y2UI_ARGS “$@”
**
linux-n5q8:/home/kg17Taban #
**
I am inside **MATE **desktop of **openSUSE-42.3(Leap) 64-bit.
Since you can open a terminal window, type this; sudo zypper rm amdgpu-pro
It’ll ask for your root password, then follow instructions to uninstall the driver - I’m guessing the package name is amdgpu-pro. May require a reboot afterwards.
It refers to using the AMD uninstaller, I’m guessing it makes changes such as blacklisting the radeon module or possibly modifying initrd. You should follow the instructions on that page under the uninstalling the amd gpu driver.
I don’t know if the SDB is missing something, in any case compared to the AMD documentation the SDB is missing a perhaps important step checking to make sure required dependencies exist. Also, unlike the SDB the AMD documentation just installs directly instead of setting up a local repo.
You might be able to determine that you’re missing a dependency even after your install by running the following in an elevated console (you probably have to be in your repository’s root directory). Use xterm if konsole isn’t working.
amdgpu-pro-preinstall.sh --check
If uninstalling doesn’t work, then you might inspect the contents of the “amdgpu-pro” package and try to manually remove with YMMV results, Ask if you want to do this and need help. instead I recommend you first disable the AMD repo you created and use your openSUSE DVD to “upgrade” to try to repair your system.
Or, consider that your system is brand new.
Sometimes when a system is brand new, there are few if any settings and files that are worth saving (or a small number of files which can be transferred elsewhere), it’s simpler and better in the long run to just wipe clean and re-install to make sure no “junk” is left in your system.
As for the SDB you referenced, that’s brand new and I don’t know has ever been discussed before so I don’t know what to make of it. Since I personally don’t use or manage any systems with an ATI GPU currently, I can’t evaluate how accurate or complete the information is in it… But if you think you really read everything in detail and determined these drivers <should> have worked, I think you should post a note on the SDB that it didn’t work for you, details about your hardware and a link to this Forum thread. In any case, I have a strong misgiving that the AMD documentation describes how to test your system before installing and the SDB does not mention this.
There really isn’t a certain solution for discovering dependencies.
You can try either of the following…
If your root partition is BTRFS, you can try rolling back to a snapshot prior to when you installed amdcpu pro. Think hard for the exact day (maybe time) and then using either the snapper command line (my recommendation) or the YaST snapper module, find a snapshot with a date/time prior to that installation, then roll back.
Re-install the problem package, then list the contents of the RPM using the following command
rpm -ql *packagename *
Then uninstall the package, and manually make sure every file in the package list is removed (often configuration files are not removed)
