Page 2 of 6
Re: MX 17 Repository: The Backported Debian Kernel Thread
Posted: Wed Jun 13, 2018 11:56 pm
by sacules
Indeed. However, I can't use VirtualBox as a host, I get the following error:
Code: Select all
Kernel driver not installed (rc=-1908)
The VirtualBox Linux kernel driver (vboxdrv) is either not loaded or there is a permission problem with /dev/vboxdrv. Please reinstall virtualbox-dkms package and load the kernel module by executing
'modprobe vboxdrv'
as root.
where: suplibOsInit what: 3 VERR_VM_DRIVER_NOT_INSTALLED (-1908) - The support driver is not installed. On linux, open returned ENOENT.
Re: MX 17 Repository: The Backported Debian Kernel Thread
Posted: Thu Jun 14, 2018 1:09 am
by Stevo
The 4.17 kernel requires an upgrade of Vbox to 5.2.12, which can be installed from the test repo. You'll also need to install the 4.17 linux-headers for your kernel.
Re: MX 17 Repository: The Backported Debian Kernel Thread
Posted: Thu Jun 14, 2018 7:52 am
by richb
I installed the 4.17 kernel. I thought the amdgpu driver was installed by default with this kernel. However it was not on my system. I have forgotten how to enable the driver. Can you guide me?
Re: MX 17 Repository: The Backported Debian Kernel Thread
Posted: Thu Jun 14, 2018 4:08 pm
by Stevo
The amdgpu driver actually is in two parts; one is built into the kernel, and the other is xserver-xorg-video-amdgpu, which should already be installed. However, I don't have any hardware to test how the stock Debian xserver-driver works with the new kernel, but sacules' post seems to show that it works and has improved functionality. I'm not sure if you need to use a config file to switch from radeon to amdgpu, but kmathern would no doubt know. What are you showing with "inxi -G" now?
Re: MX 17 Repository: The Backported Debian Kernel Thread
Posted: Thu Jun 14, 2018 7:07 pm
by richb
Code: Select all
Graphics: Card-1: AMD Kaveri [Radeon R7 Graphics] driver: radeon v: kernel
Display: x11 server: X.Org 1.19.2 driver: ati,radeon unloaded: fbdev,modesetting,vesa
resolution: 1920x1080~60Hz
OpenGL: renderer: Gallium 0.4 on AMD KAVERI (DRM 2.50.0 / 4.17.0-1-amd64 LLVM 3.9.1)
v: 4.3 Mesa 13.0.6
I recall enabling it with an earlier kernel but forgot the steps.
Re: MX 17 Repository: The Backported Debian Kernel Thread
Posted: Thu Jun 14, 2018 7:38 pm
by Stevo
Do either of the two ways in the answers here seem familiar?
https://askubuntu.com/questions/927601/ ... o-i-change
My preference would be to try blacklisting the radeon driver first.
Re: MX 17 Repository: The Backported Debian Kernel Thread
Posted: Thu Jun 14, 2018 7:48 pm
by richb
neither seem familiar. I tried the modprobe solution but got a failure to find the added line.
I thought there was another way to another way to blacklist the radeon driver without editing /etc/default grub,
Tried another method to blacklist the radeon driver. I edited /etc/modeprobe.d by adding a blacklist.conf file and adding "blacklist radeon" to that file. Tat had no effect.
Re: MX 17 Repository: The Backported Debian Kernel Thread
Posted: Thu Jun 14, 2018 9:24 pm
by kmathern
I haven't been able to get the amdgpu driver to work on my Kabini GPU with 4.16 or 4.17 kernels.
I'm familiar with the boot parameters mentioned in Stevo's askubuntu link
(radeon.si_support=*, radeon.cik_support=*, amdgpu.si_support=*, amdgpu.cik_support=*), and they used to work okay for me with 4.13, 4.14 & 4.15 kernels but so far not 4.16 or 4.17.
A /etc/modprode.d file like the one shown below
(I called it 'amdgpu_si_cik.conf') also used to work for me with 4.13, 4.14 & 4.15 kernels.
Code: Select all
##################################################################
# Uncomment lines below to enable optional amdgpu driver support #
# for Southern Islands (si) and Sea Islands (cik) GPUs with 4.13 #
# series kernels and higher. #
# #
# GCN generation 1 / Southern Islands chipsets: #
# CAPE VERDE, PITCAIRN, TAHITI, OLAND, HAINAN #
# #
# GCN generation 2 / Sea Islands chipsets: #
# BONAIRE, KABINI, KAVERI, HAWAII, MULLINS #
##################################################################
#options radeon si_support=0 cik_support=0
#options amdgpu si_support=1 cik_support=1
Re: MX 17 Repository: The Backported Debian Kernel Thread
Posted: Fri Jun 15, 2018 12:42 pm
by sacules
Stevo wrote: ↑Thu Jun 14, 2018 1:09 am
The 4.17 kernel requires an upgrade of Vbox to 5.2.12, which can be installed from the test repo. You'll also need to install the 4.17 linux-headers for your kernel.
Already had the headers, will try upgrading Vbox.
richb wrote: ↑Thu Jun 14, 2018 7:07 pm
Code: Select all
Graphics: Card-1: AMD Kaveri [Radeon R7 Graphics] driver: radeon v: kernel
Display: x11 server: X.Org 1.19.2 driver: ati,radeon unloaded: fbdev,modesetting,vesa
resolution: 1920x1080~60Hz
OpenGL: renderer: Gallium 0.4 on AMD KAVERI (DRM 2.50.0 / 4.17.0-1-amd64 LLVM 3.9.1)
v: 4.3 Mesa 13.0.6
I recall enabling it with an earlier kernel but forgot the steps.
I had a similar issue some months ago and solved it by upgrading the mesa drivers to the last version, which you can find in the test repos.
Re: MX 17 Repository: The Backported Debian Kernel Thread
Posted: Fri Jun 15, 2018 1:38 pm
by Stevo
sacules wrote: ↑Fri Jun 15, 2018 12:42 pm
Stevo wrote: ↑Thu Jun 14, 2018 1:09 am
The 4.17 kernel requires an upgrade of Vbox to 5.2.12, which can be installed from the test repo. You'll also need to install the 4.17 linux-headers for your kernel.
Already had the headers, will try upgrading Vbox.
richb wrote: ↑Thu Jun 14, 2018 7:07 pm
Code: Select all
Graphics: Card-1: AMD Kaveri [Radeon R7 Graphics] driver: radeon v: kernel
Display: x11 server: X.Org 1.19.2 driver: ati,radeon unloaded: fbdev,modesetting,vesa
resolution: 1920x1080~60Hz
OpenGL: renderer: Gallium 0.4 on AMD KAVERI (DRM 2.50.0 / 4.17.0-1-amd64 LLVM 3.9.1)
v: 4.3 Mesa 13.0.6
I recall enabling it with an earlier kernel but forgot the steps.
I had a similar issue some months ago and solved it by upgrading the mesa drivers to the last version, which you can find in the test repos.
Stretch-backports has a newer mesa, or we currently have 18.0.4 in a separate experimental repo. I was a bit leery of having it in the test repo, since there are some that upgrade
everything from there in one fell swoop.