Stevo wrote: ↑Fri Jun 15, 2018 1:38 pmStretch-backports has a newer mesa, or we currently have 18.0.4 and a newer xorg-amdgpu driver 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.sacules wrote: ↑Fri Jun 15, 2018 12:42 pmAlready had the headers, will try upgrading Vbox.
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.richb wrote: ↑Thu Jun 14, 2018 7:07 pmI recall enabling it with an earlier kernel but forgot the steps.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
MX 17 Repository: The Backported Debian Kernel Thread
Re: MX 17 Repository: The Backported Debian Kernel Thread
Re: MX 17 Repository: The Backported Debian Kernel Thread
I figured out a way (actually two ways) to get it to use the amdgpu driver for my Kabini gpu with the 4.17 kernel.
First, here's the inxi output:
I've been able to get it to use the amdgpu driver with either set of the following boot parameters,
these *** :
or these *** :
***: If you have a GCN generation 1 / Southern Islands chipset (CAPE VERDE, PITCAIRN, TAHITI, OLAND, HAINAN), try replacing the 'cik' instances with 'si'.
In both cases, adding the 'amdgpu.dc=0' parameter is what finally got it to work. I don't know what the downside is to using it.
I do see a slight difference in the dmesg report between the two sets of boot parameters.
With the first set I see what's shown below, when it switches from EFI VGA to the amdgpudrmfb:
With the second set of boot parameters it first switches from EFI VGA to the radeondrmfb instead of the amdgpudrmfb, I don't know if that's a problem or not.
First, here's the inxi output:
Code: Select all
$ inxi -SGxxx
System: Host: mx1 Kernel: 4.17.0-1-amd64 x86_64 bits: 64 compiler: gcc v: 6.3.0 Desktop: Xfce 4.12.3
tk: Gtk 2.24.25 info: xfce4-panel wm: Xfwm4 dm: lightdm 1.10.3
Distro: MX-16_x64 Metamorphosis 12 December 2016
Graphics: Card-1: Advanced Micro Devices [AMD/ATI] Kabini [Radeon HD 8240 / R3 Series] driver: amdgpu
v: kernel bus ID: 00:01.0 chip ID: 1002:9838
Display: server: X.Org 1.16.4 driver: amdgpu,ati unloaded: fbdev,modesetting,radeon,vesa
resolution: 1600x900~60Hz
OpenGL: renderer: Gallium 0.4 on AMD KABINI (DRM 3.25.0 / 4.17.0-1-amd64 LLVM 3.9.1)
v: 4.3 Mesa 13.0.6 compat-v: 3.0 direct render: Yes
I've been able to get it to use the amdgpu driver with either set of the following boot parameters,
these *** :
Code: Select all
amdgpu.cik_support=1 amdgpu.dc=0 modprobe.blacklist=radeon
or these *** :
Code: Select all
amdgpu.cik_support=1 radeon.cik_support=0 amdgpu.dc=0
***: If you have a GCN generation 1 / Southern Islands chipset (CAPE VERDE, PITCAIRN, TAHITI, OLAND, HAINAN), try replacing the 'cik' instances with 'si'.
In both cases, adding the 'amdgpu.dc=0' parameter is what finally got it to work. I don't know what the downside is to using it.
I do see a slight difference in the dmesg report between the two sets of boot parameters.
With the first set I see what's shown below, when it switches from EFI VGA to the amdgpudrmfb:
Code: Select all
[ 10.607756] fb: switching to amdgpudrmfb from EFI VGA
[ 11.095718] fbcon: amdgpudrmfb (fb0) is primary device
[ 11.110920] amdgpu 0000:00:01.0: fb0: amdgpudrmfb frame buffer device
With the second set of boot parameters it first switches from EFI VGA to the radeondrmfb instead of the amdgpudrmfb, I don't know if that's a problem or not.
Code: Select all
[ 10.648514] fb: switching to radeondrmfb from EFI VGA
[ 11.748400] fbcon: amdgpudrmfb (fb0) is primary device
[ 11.765293] amdgpu 0000:00:01.0: fb0: amdgpudrmfb frame buffer device
Re: MX 17 Repository: The Backported Debian Kernel Thread
The first suggestion worked for my AMD Kaveri. Thanks
Code: Select all
amdgpu.cik_support=1 amdgpu.dc=0 modprobe.blacklist=radeon
Forum Rules
Guide - How to Ask for Help
richb Administrator
System: MX 23 KDE
AMD A8 7600 FM2+ CPU R7 Graphics, 16 GIG Mem. Three Samsung EVO SSD's 250 GB
Guide - How to Ask for Help
richb Administrator
System: MX 23 KDE
AMD A8 7600 FM2+ CPU R7 Graphics, 16 GIG Mem. Three Samsung EVO SSD's 250 GB
Re: MX 17 Repository: The Backported Debian Kernel Thread
Updating virtualbox and virtualbox-dkms, plus reinstalling the 4.17 headers, has definitely worked!
Re: MX 17 Repository: The Backported Debian Kernel Thread
The "4.17.0-1" kernel in the test repo is now upgraded to a version based on 4.17.2. Since it has the same ABI (-1) as the 4.17.0 version, it will upgrade over that version. I'm not sure if DKMS drivers will automatically rebuild during the upgrade...if you don't see them doing that, you could reinstall the dkms packages in Synaptic to be sure, or "sudo dpkg-reconfigure <package>" them on the command line.
Re: MX 17 Repository: The Backported Debian Kernel Thread
We now have the 4.17.3 version, backported from Sid, in the test repo, replacing 4.17.2. It should upgrade over 4.17.2, but might not update the dkms modules automatically. In that case, you can run
to see which ones are installed, then
to make they build.
Code: Select all
apt policy *-dkms
Code: Select all
sudo dpkg-reconfigure [package1] [package2] ...
Re: MX 17 Repository: The Backported Debian Kernel Thread
This new build includes the internal Virtual Box and Anbox guest drivers, so the virtualbox-guest packages should no longer be required in guests.Stevo wrote: ↑Thu Jul 05, 2018 12:48 pm We now have the 4.17.3 version, backported from Sid, in the test repo, replacing 4.17.2. It should upgrade over 4.17.2, but might not update the dkms modules automatically. In that case, you can run
to see which ones are installed, thenCode: Select all
apt policy *-dkms
to make they build.Code: Select all
sudo dpkg-reconfigure [package1] [package2] ...
I also have it a separate OBS repo that users of other Stretch-based distros might prefer to use instead. Instruction for that are:
As root, add the repo:
Code: Select all
echo 'deb http://download.opensuse.org/repositories/home:/stevenpusser:/kernel-backports/Debian_9.0/ /' > /etc/apt/sources.list.d/home:stevenpusser:kernel-backports.list
Code: Select all
rm -f Release.key && wget -nv https://download.opensuse.org/repositories/home:stevenpusser:kernel-backports/Debian_9.0/Release.key -O Release.key
Code: Select all
apt-key add - < Release.key
apt-get update
Re: MX 17 Repository: The Backported Debian Kernel Thread
Hello,
Shall 4.15.17-1 kernel be pushed in regular updates soon ? I'm testing it since a few days. No problem here.
Shall 4.15.17-1 kernel be pushed in regular updates soon ? I'm testing it since a few days. No problem here.
Re: MX 17 Repository: The Backported Debian Kernel Thread
We don't have any debianized source from upstream Debian for that kernel revision. Refreshing the numerous Debian patches to match the possible source code changes would probably make doing it manually a very onerous job. I'd suggest one of the 4.17 kernels if you want to stay on top.
Re: MX 17 Repository: The Backported Debian Kernel Thread
Have been running the 4.17.4 kernel on AntiX for a few days now on both my main desktop machine and the Lenovo T430 everything has been running very smoothly.
Only thing I had to do was reinstall my nvidia drivers on the Main desktop after the kernel update also late night I updated my nvidia driver to 390.48 from the mx test repo and running sweet too..
Thanks for the updates.
Only thing I had to do was reinstall my nvidia drivers on the Main desktop after the kernel update also late night I updated my nvidia driver to 390.48 from the mx test repo and running sweet too..
Thanks for the updates.
Main : MX 19.1-AHS (i3) 5.4.13-1~mx19+1, Asus B450-i AMD 5 3600 , 32gb Hyper-X 3200 , GTX970 .
Lenovo T430 : Debian10 antiX17 (i3) , 4.20.12 , i5 , 12gb .
Lenovo X220 : Test Machine (ATM)
Lenovo T430 : Debian10 antiX17 (i3) , 4.20.12 , i5 , 12gb .
Lenovo X220 : Test Machine (ATM)