AMD Radeon HD 6670/7670 (NOT SOLVED)

[Fornhamfred]

I have just installed a snapshot from the production machine to another machine with the above graphics. The system shows the display as default, how do I change this please?

Code: Select all

System:
  Host: mx17 Kernel: 4.15.14-antix.1-amd64-smp x86_64 bits: 64 
  Desktop: Xfce 4.12.3 Distro: MX-17.1_x64 Horizon December 15, 2017 
Machine:
  Type: Desktop Mobo: ASUSTeK model: P8Z68-V LX v: Rev X.0x 
  serial: <root required> UEFI: American Megatrends v: 0703 date: 10/21/2011 
CPU:
  Topology: Quad Core model: Intel Core i5-2500K bits: 64 type: MCP 
  L2 cache: 6144 KiB 
  Speed: 1696 MHz min/max: 1600/5900 MHz Core speeds (MHz): 1: 1656 2: 1720 
  3: 1773 4: 2618 
Graphics:
  Card-1: AMD Turks XT [Radeon HD 6670/7670] driver: N/A 
  Display: x11 server: X.Org 1.19.2 driver: vesa resolution: 1024x768~N/A 
  OpenGL: renderer: N/A v: N/A 
Audio:
  Card-1: Intel 6 Series/C200 Series Family High Definition Audio 
  driver: snd_hda_intel 
  Card-2: AMD Turks HDMI Audio [Radeon HD 6500/6600 / 6700M Series] 
  driver: snd_hda_intel 
  Sound Server: ALSA v: k4.15.14-antix.1-amd64-smp 
Network:
  Card-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet 
  driver: r8169 
  IF: eth0 state: up speed: 1000 Mbps duplex: full mac: c8:60:00:6a:a4:b1 
Drives:
  HDD Total Size: 1.82 TiB used: 8.15 GiB (0.4%) 
  ID-1: /dev/sda vendor: Seagate model: ST2000DL003-9VT166 size: 1.82 TiB 
Partition:
  ID-1: / size: 19.10 GiB used: 6.02 GiB (31.5%) fs: ext4 dev: /dev/sda6 
  ID-2: /home size: 28.71 GiB used: 2.13 GiB (7.4%) fs: ext4 dev: /dev/sda7 
  ID-3: swap-1 size: 15.62 GiB used: 0 KiB (0.0%) fs: swap dev: /dev/sda5 
Sensors:
  System Temperatures: cpu: 37.0 C mobo: N/A 
  Fan Speeds (RPM): cpu: 0 
Repos:
  Active apt repos in: /etc/apt/sources.list.d/antix.list 
  1: deb http://nl.mxrepo.com/antix/stretch/ stretch main
  Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list 
  1: deb http://ftp.uk.debian.org/debian/ stretch-updates main contrib non-free
  Active apt repos in: /etc/apt/sources.list.d/debian.list 
  1: deb http://ftp.uk.debian.org/debian/ stretch main contrib non-free
  2: deb http://security.debian.org/ stretch/updates main contrib non-free
  Active apt repos in: /etc/apt/sources.list.d/megasync.list 
  1: deb https://mega.nz/linux/MEGAsync/Debian_9.0/ ./
  Active apt repos in: /etc/apt/sources.list.d/mx.list 
  1: deb http://nl.mxrepo.com/mx/repo/ stretch main non-free
  Active apt repos in: /etc/apt/sources.list.d/various.list 
  1: deb http://download.virtualbox.org/virtualbox/debian/ stretch contrib
Info:
  Processes: 210 Uptime: 13m Memory: 7.77 GiB used: 973.8 MiB (12.2%) 
  Shell: bash inxi: 3.0.10 

[Stevo]

If that's newly released hardware, the odds are high that it will need the newest kernel, Mesa stack, and firmware-amd-graphics it can get. I'm pretty sure we just moved the most recent firmware packages to main, though. Mesa can be upgraded from stretch-backports or our experimental+test repo combination.

Then there might be some kernel boot command to get the system to use the amdgpu driver, but I'm not sure how that would go...if we can figure what needs what, a script to do all this automatically or having it in MX-Tweak would sure be a nice addition.

[kmathern]

...Then there might be some kernel boot command to get the system to use the amdgpu driver ...

I think the HD 6670/7670 is a older GPU and should use the radeon driver, not the amdgpu driver.

So the question is why is it using the vesa driver?

Maybe Fornhamfred could post the output of the command below so we can make sure the radeon driver isn't being disabled by some kernel boot-time option such as nomodeset, etc. Also post the /etc/X11/xorg.conf file if one is present.

Code: Select all

cat /proc/cmdline

[Fornhamfred]

...Then there might be some kernel boot command to get the system to use the amdgpu driver ...

I think the HD 6670/7670 is a older GPU and should use the radeon driver, not the amdgpu driver.

So the question is why is it using the vesa driver?

Maybe Fornhamfred could post the output of the command below so we can make sure the radeon driver isn't being disabled by some kernel boot-time option such as nomodeset, etc. Also post the /etc/X11/xorg.conf file if one is present.

Code: Select all

cat /proc/cmdline

cat /proc/cmdline
BOOT_IMAGE=/boot/vmlinuz-4.15.14-antix.1-amd64-smp root=UUID=7fcafe45-ab3b-4db6-9107-cbf646296e84 ro nomodeset quiet

Code: Select all

#-----------------------------------------------------------------------------
# xorg.conf file
#
# Generated by make-xorg-conf sometime around Tue Oct  9 18:27:42 BST 2018
#
# If you want to save customizations, delete the line above or this
# file will get automatically deleted on the next live boot.
#
# Command line parameters: --output=/etc/X11/xorg.conf safe
#-----------------------------------------------------------------------------

Section "Monitor"
    Identifier "Monitor0"
    Option "DPMS" "true"
EndSection

Section "Device"
    Identifier "Device0"
    Driver     "vesa"
EndSection

Section "Screen"
    Identifier      "Screen0"
    Monitor         "Monitor0"
    Device          "Device0"
EndSection

[kmathern]

Remove the /etc/X11/xorg.conf file, use Grub Customizer to remove the nomodeset kernel parameter and generate a new grub.cfg.
After you do a reboot it should be using the radeon driver.

[Fornhamfred]

Remove the /etc/X11/xorg.conf file, use Grub Customizer to remove the nomodeset kernel parameter and generate a new grub.cfg.
After you do a reboot it should be using the radeon driver.

Removed the nomodeset but do not understand what the kernel parameter is. This is the file now

Code: Select all

savedefault
	load_video
	insmod gzio
	if [ x$grub_platform = xxen ]; then insmod xzio; insmod lzopio; fi
	insmod part_msdos
	insmod ext2
	set root='hd0,msdos6'
	if [ x$feature_platform_search_hint = xy ]; then
	  search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos6 --hint-efi=hd0,msdos6 --hint-baremetal=ahci0,msdos6  7fcafe45-ab3b-4db6-9107-cbf646296e84
	else
	  search --no-floppy --fs-uuid --set=root 7fcafe45-ab3b-4db6-9107-cbf646296e84
	fi
	echo	'Loading Linux 4.15.14-antix.1-amd64-smp ...'
	linux	/boot/vmlinuz-4.15.14-antix.1-amd64-smp root=UUID=7fcafe45-ab3b-4db6-9107-cbf646296e84 ro   quiet
	echo	'Loading initial ramdisk ...'
	initrd	/boot/initrd.img-4.15.14-antix.1-amd64-smp

[Fornhamfred]

I have been unable to resolve this problem which seems to be because the system the snapshot was made from has nvidia graphics and this machine has radeon. Installing from the snapshot still had nvidia in the system.
I have now installed from the Sept MX17.1 and the display and Radeon driver is installed correctly.

[kmathern]

Re:

Removed the nomodeset but do not understand what the kernel parameter is.

The radeon driver uses kernel modesetting (kms) and won't work properly if the nomodeset parameter is used.


Like I posted before, removing the nomodeset parameter and also removing(deleting) the /etc/X11/xorg.conf file should get it to using the radeon driver. Since the nvidia driver was installed on the system that the snapshot was made on, I guess there's also the possibility of there being a nvidia config file in the /etc/X11.xorg.conf.d/ directory, such as a '20-nvidia.conf' file, it should be removed too if there is one.

[Fornhamfred]

Re:

Removed the nomodeset but do not understand what the kernel parameter is.

The radeon driver uses kernel modesetting (kms) and won't work properly if the nomodeset parameter is used.


Like I posted before, removing the nomodeset parameter and also removing(deleting) the /etc/X11/xorg.conf file should get it to using the radeon driver. Since the nvidia driver was installed on the system that the snapshot was made on, I guess there's also the possibility of there being a nvidia config file in the /etc/X11.xorg.conf.d/ directory, such as a '20-nvidia.conf' file, it should be removed too if there is one.

As I posted I have re-installed a fresh copy to the machine but if I get time in the next few days I will replicate the original install and see if the same problem is replicated. If so has anyone else tried installing from a snapshot from a machine with nvidia graphics to one with radeon?

[Fornhamfred]

I have made a new snapshot on my production machine and installed it again on the test rig. One error that was mine previously was that I forgot that grub was being booted from another distro so the changes I made in grub customiser on mx17 were not being actioned.
OK I have removed nomodeset, the xorg.conf and any other versions backup etc and modified the grub instructions on the other distro and the system is booting with the correct radeon driver and display details. No replacement xorg.conf file has been generated. However during startup there are errors shown modprob error could not insert nvidia current. How do I cure this?