LM 17.3 update that destroyed my kernel (when I tried to install the 15.20 driver again, blue-messed up DKMS error at 93

Forum rules
Before you post read how to get help. Topics in this forum are automatically closed 6 months after creation.
Locked
fruitkiller

LM 17.3 update that destroyed my kernel (when I tried to install the 15.20 driver again, blue-messed up DKMS error at 93

Post by fruitkiller »

%...error.

Thankfully I had other Kernels installed, I'm now using 4.4-0.59. So I went there but some programs don't work on it, and others work where they used not to (Audacious now playing my turntable through the desktop stereo system and easily ripping vinyls into flac/mp3.

The update was this one :

Code: Select all

Commit Log for Mon Jul 24 14:12:46 2017


Upgraded the following packages:
imagemagick (8:6.7.7.10-6ubuntu3.7) to 8:6.7.7.10-6ubuntu3.8
imagemagick-common (8:6.7.7.10-6ubuntu3.7) to 8:6.7.7.10-6ubuntu3.8
libdrm-amdgpu1 (2.4.67-1ubuntu0.14.04.1) to 2.4.67-1ubuntu0.14.04.2
libdrm-dev (2.4.67-1ubuntu0.14.04.1) to 2.4.67-1ubuntu0.14.04.2
libdrm-intel1 (2.4.67-1ubuntu0.14.04.1) to 2.4.67-1ubuntu0.14.04.2
libdrm-intel1:i386 (2.4.67-1ubuntu0.14.04.1) to 2.4.67-1ubuntu0.14.04.2
libdrm-nouveau2 (2.4.67-1ubuntu0.14.04.1) to 2.4.67-1ubuntu0.14.04.2
libdrm-nouveau2:i386 (2.4.67-1ubuntu0.14.04.1) to 2.4.67-1ubuntu0.14.04.2
libdrm-radeon1 (2.4.67-1ubuntu0.14.04.1) to 2.4.67-1ubuntu0.14.04.2
libdrm-radeon1:i386 (2.4.67-1ubuntu0.14.04.1) to 2.4.67-1ubuntu0.14.04.2
libdrm2 (2.4.67-1ubuntu0.14.04.1) to 2.4.67-1ubuntu0.14.04.2
libdrm2:i386 (2.4.67-1ubuntu0.14.04.1) to 2.4.67-1ubuntu0.14.04.2
libmagickcore5 (8:6.7.7.10-6ubuntu3.7) to 8:6.7.7.10-6ubuntu3.8
libmagickwand5 (8:6.7.7.10-6ubuntu3.7) to 8:6.7.7.10-6ubuntu3.8
x11proto-randr-dev (1.5.0-1~trusty1) to 1.5.0-1~trusty2
xserver-common (2:1.15.1-0ubuntu2.7) to 2:1.15.1-0ubuntu2.9
xserver-xephyr (2:1.15.1-0ubuntu2.7) to 2:1.15.1-0ubuntu2.9
xserver-xorg-core (2:1.15.1-0ubuntu2.7) to 2:1.15.1-0ubuntu2.9
xserver-xorg-dev (2:1.15.1-0ubuntu2.7) to 2:1.15.1-0ubuntu2.9
xtrans-dev (1.3.5-1~ubuntu14.04.1) to 1.3.5-1~ubuntu14.04.2
Of course, nowadays Update Manager does not show us all the packages that get installed, it was xtrans that likely messed up things, although all the xserver* files I should have ignored.

After that like I say in the title, my file amd-driver-installer-15.20.1046-x86.x86_64.run and I also had "amd-driver-installer-15.302-x86.x86_64.run" which I tried first I think to install.

Right now, I've used all the knowledge I already had, plus some additional stuff I found online on the Ubuntu help questions that always show up so much more at the top of anything else...

So, I installed "amd-driver-installer-15.20.1046-x86.x86_64.run" while in another session where I turned off mdm. All the requisites, I even made packages that would be named fglrx*...strangely. In LM 17.3's Driver Manager before all of this, all the other free drivers were greyed out and the only choice was "ATI/AMD HD Radeon 7850 Pitcairn blah blah".

Right now it tells me I am using a proprietary device...it looks like this : https://my.mixtape.moe/mrvtdq.png

And it's not like I changed OS's, I didn't, I switched to another what I thought would be a temporary thing only. So I just, created files from the amd-radeon-15.30 and also 15.20 Proprietary Driver, which doesn't make my Theme look pale..and the AMD Catalyst program doesn't work, it tells me "here was a problem initializing Catalyst Control Center Linux edition. It could be caused by the following.

No AMD graphics driver is installed, or the AMD driver is not functioning properly.
Please install the AMD driver appropriate for you AMD hardware, or configure using aticonfig."

Right now I'm running 15,20 since it's what I was running back when on the checked as recommended 3.19-0.32, but I also created the packages for the 15.30 driver, apparently there is a way to get your prop driver installed this way...despite them all being named fglrx...

Code: Select all

/catalyst15.12/fglrx-15.302 $ ls
amd-driver-installer-15.302-x86.x86_64.run  doc fglrx-amdcccle_15.302-0ubuntu1_amd64.deb  fglrx-dev_15.302-0ubuntu1_amd64.deb
check.sh fglrx_15.302-0ubuntu1_amd64.deb  fglrx-core_15.302-0ubuntu1_amd64.deb      fglrx-installer_15.302-0ubuntu1_amd64.changes
the .changes file instals itself, I tried the 15.302 driver on an old 3.13 driver, the latest one that's still good until April 2009 on Mint 17.3
It was a failure, I tried to do it with the fglrx files, fglrx -i fglrx-amdcccle[...].deb. And it didn't do anything.
So I tried it with the tried and true manner, got a DKMS error and all went to crap, I got 2 dead kernels, a 3.19.80 and that 3.13 driver...they don't even let me press S because it's unable to mount drives it mounts automatically when I click them in Places.

I want the real proprietary driver, not this. Please, just give me help about that subject, do not question my motives about why I want it (I already gave some answers..I also game through CrossOver and Steam) and the difference is quite something even just in caja when my theme is seen, right now it's a kind of distant beige-ish dark-ish background and my files are in green. Well it's not solid colours, like when I booted back in Windows 7 just to see if my eyes were funny. No, it's these non-proprietary, proprietary drivers that cause me a major headache, since 2 days. The number of Purges, programs doing miraculously more than I wanted, programs doing absolutely nothing/destroying a Kernel by having it not have any video driver and the safe mode console is useless since everything is Read Only.
Last edited by LockBot on Wed Dec 28, 2022 7:16 am, edited 1 time in total.
Reason: Topic automatically closed 6 months after creation. New replies are no longer allowed.
fruitkiller

Re: LM 17.3 update that destroyed my kernel (when I tried to install the 15.20 driver again, blue-messed up DKMS error a

Post by fruitkiller »

So you guys encourage me to use nouveau or whatever..k, thanks.
Locked

Return to “Graphics Cards & Monitors”