You are not logged in.
I have been trying to set up a new PC, the installation was ok and when I started to install AMDGPU drivers problems have begun. I followed the installation guide for amdgpu drivers and installed
mesa xf86-video-amdgpu libva-mesa-driver libva-vdpau-driver mesa-vdpau Also I have blacklisted radeon module
$ cat /etc/modprobe.d/radeon.conf
blacklist radeonAlso added in modules firstly as said in wiki
$ cat /etc/mkinitcpio.conf
...
MODULES="amdgpu radeon"
...and generated it with mkinitcpio -p linux
finally added in grub kernel arguments with
$ cat /etc/default/grub | head -10
# GRUB boot loader configuration
GRUB_DEFAULT=0
GRUB_TIMEOUT=5
GRUB_DISTRIBUTOR="Arch"
GRUB_CMDLINE_LINUX_DEFAULT="quiet radeon.si_support=0 radeon.cik_support=0 amdgpu.si_support=1 amdgpu.cik_support=1"
GRUB_CMDLINE_LINUX=""and then generated grub config with
sudo grub-mkconfig -o /boot/grub/grub.cfghowever when it starts the screen is frozen and when i use lscpi -v in ssh it doesnt display any module
01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Hawaii PRO [Radeon R9 290/390] (prog-if 00 [VGA controller])
Subsystem: PC Partner Limited / Sapphire Technology Hawaii PRO [Radeon R9 290/390]
Flags: fast devsel, IRQ 16
Memory at e0000000 (64-bit, prefetchable) [size=256M]
Memory at f0000000 (64-bit, prefetchable) [size=8M]
I/O ports at e000 [size=256]
Memory at f7d00000 (32-bit, non-prefetchable) [size=256K]
Expansion ROM at 000c0000 [disabled] [size=128K]
Capabilities: <access denied>
Kernel modules: radeon, amdgpuWhat am I doing wrong?
Last edited by Guisanti (2018-03-14 17:57:44)
Offline
Post a dmesg, and remove radeon from the modules array, it makes little sense to not want to use it and then include it in mkinitcpio.conf regardless (and use
MODULES=(amdgpu)instead, so you are in line with the new format.)
Offline
Post a dmesg, and remove radeon from the modules array, it makes little sense to not want to use it and then include it in mkinitcpio.conf regardless (and use
MODULES=(amdgpu)instead, so you are in line with the new format.)
I have found that the problem is that the kernel parameters are not correctly passed at the boot because I have inputed the kernel parameters on grub startup and now everything works however is not a clean solution to change parameters this way, should I still post dmesg?
Last edited by Guisanti (2017-12-16 02:07:29)
Offline
Well if that is the issue and it is solved by properly configuring your bootloader, then you probably don't need to (have you forgotten to regenerate your GRUB config after making your changes?)
Offline
Well if that is the issue and it is solved by properly configuring your bootloader, then you probably don't need to (have you forgotten to regenerate your GRUB config after making your changes?)
I have found that I forgot to mark the problem as solved. The problem was that I was using an EFI partition and forgot to mount it to save the changes on bootloader.
Offline