Thats different.
amdgpu wasnt listed before.
But you still want it instead of radeon.
**EDIT. oh wait a sec. ** Please do this first:
I notice you are on kernel 5.6 which is EOL.
Lets make sure you are up to date and install a current stable kernel:
My apologies, I know you had already pointed that out but I sincerely thought I had updated to the latest kernel. I used the graphical settings manager to install kernel 5.8 and it shows as running there. I also thought that this line in my inxi output meant I’m running kernel 5.8.1-3, which is the same version number as shown in the graphical settings manager:
[leo@leo-zen ~]$ mhwd -li
> Installed PCI configs:
--------------------------------------------------------------------------------
NAME VERSION FREEDRIVER TYPE
--------------------------------------------------------------------------------
video-linux 2018.05.04 true PCI
Warning: No installed USB configs!
Ok …
Lets edit a few things: /etc/mkinitcpio.conf on the MODULES line we want it to look like this MODULES=(amdgpu)
And at /etc/default/grub on the GRUB_CMDLINE_LINUX line we want it to look like this (assuming no other options): GRUB_CMDLINE_LINUX="radeon.modeset=0"
Then run
I edited the files and ran the commands but now Manjaro doesn’t boot, so I changed to a terminal through Alt+F2 to undo the changes, but not before getting the output of inxi -Gazy:
Graphics:
Device-1: AMD Mullins [Radeon R3 Graphics] vendor: Hewlett-Packard
driver: N/A alternate: radeon, amdgpu bus ID: 00:01.0 chip ID: 1002:9850
Device-2: Cheng Uei Precision Industry (Foxlink) type: USB driver: uvcvideo
bus ID: 2-1.2:4 chip ID: 05c8:038f serial: <filter>
Display: server: X.org 1.20.8 driver: ati unloaded: modesetting,radeon
alternate: fbdev,vesa tty: 200x56
Message: Advanced graphics data unavailable in console. Try -G --display
Ok, now I get a completely black screen upon boot and I can’t change to a terminal. I’m afraid I don’t know how to get out of this one I suppose we’d use kernel parameters to get to a terminal and undo the changes but I’m not familiar enough with them.
Also, just to be clear, I undid the previous changes to the config files before installing amd-experimental so that Manjaro would boot again. You recommended a reboot from a terminal so I got the impression that you might think Manjaro still wasn’t booting.
I’ve followed the instructions to boot into runlevel 3 as detailed in your post but Manjaro still booted to an unresponsive blackscreen. I’m sure I followed the right procedure because I tried it in another computer with Manjaro and it worked correctly, so since I haven’t moved anything into this install yet I ended up simply reinstalling Manjaro instead to get around the problem.
Any more ideas?
Thank you for your help so far, I’ve learned quite a bit.
I tried it again and got the same result: Manjaro doesn’t boot but upon changing to a TTY the output of inxi -Gazy shows no driver loaded.
I don’t think I made any typo in editing the files according to cscs’ instructions, but here are the contents of the edited files, just in case:
/etc/mkinitcpio.conf:
# vim:set ft=sh
# MODULES
# The following modules are loaded before any boot hooks are
# run. Advanced users may wish to specify all system modules
# in this array. For instance:
# MODULES=(piix ide_disk reiserfs)
MODULES=(amdgpu)
# BINARIES
# This setting includes any additional binaries a given user may
# wish into the CPIO image. This is run last, so it may be used to
# override the actual binaries included by a given hook
# BINARIES are dependency parsed, so you may safely ignore libraries
BINARIES=()
# FILES
# This setting is similar to BINARIES above, however, files are added
# as-is and are not parsed in any way. This is useful for config files.
FILES=""
# HOOKS
# This is the most important setting in this file. The HOOKS control the
# modules and scripts added to the image, and what happens at boot time.
# Order is important, and it is recommended that you do not change the
# order in which HOOKS are added. Run 'mkinitcpio -H <hook name>' for
# help on a given hook.
# 'base' is _required_ unless you know precisely what you are doing.
# 'udev' is _required_ in order to automatically load modules
# 'filesystems' is _required_ unless you specify your fs modules in MODULES
# Examples:
## This setup specifies all modules in the MODULES setting above.
## No raid, lvm2, or encrypted root is needed.
# HOOKS=(base)
#
## This setup will autodetect all modules for your system and should
## work as a sane default
# HOOKS=(base udev autodetect block filesystems)
#
## This setup will generate a 'full' image which supports most systems.
## No autodetection is done.
# HOOKS=(base udev block filesystems)
#
## This setup assembles a pata mdadm array with an encrypted root FS.
## Note: See 'mkinitcpio -H mdadm' for more information on raid devices.
# HOOKS=(base udev block mdadm encrypt filesystems)
#
## This setup loads an lvm2 volume group on a usb device.
# HOOKS=(base udev block lvm2 filesystems)
#
## NOTE: If you have /usr on a separate partition, you MUST include the
# usr, fsck and shutdown hooks.
HOOKS="base udev autodetect modconf block keyboard keymap filesystems"
# COMPRESSION
# Use this to compress the initramfs image. By default, gzip compression
# is used. Use 'cat' to create an uncompressed image.
#COMPRESSION="gzip"
#COMPRESSION="bzip2"
#COMPRESSION="lzma"
#COMPRESSION="xz"
#COMPRESSION="lzop"
#COMPRESSION="lz4"
# COMPRESSION_OPTIONS
# Additional options for the compressor
#COMPRESSION_OPTIONS=()
/etc/default/grub:
GRUB_DEFAULT=saved
GRUB_TIMEOUT=10
GRUB_TIMEOUT_STYLE=hidden
GRUB_DISTRIBUTOR="Manjaro"
GRUB_CMDLINE_LINUX_DEFAULT="quiet apparmor=1 security=apparmor udev.log_priority=3"
GRUB_CMDLINE_LINUX="radeon.modeset=0"
# If you want to enable the save default function, uncomment the following
# line, and set GRUB_DEFAULT to saved.
GRUB_SAVEDEFAULT=true
# Preload both GPT and MBR modules so that they are not missed
GRUB_PRELOAD_MODULES="part_gpt part_msdos"
# Uncomment to enable booting from LUKS encrypted devices
#GRUB_ENABLE_CRYPTODISK=y
# Uncomment to use basic console
GRUB_TERMINAL_INPUT=console
# Uncomment to disable graphical terminal
#GRUB_TERMINAL_OUTPUT=console
# The resolution used on graphical terminal
# note that you can use only modes which your graphic card supports via VBE
# you can see them in real GRUB with the command 'videoinfo'
GRUB_GFXMODE=auto
# Uncomment to allow the kernel use the same resolution used by grub
GRUB_GFXPAYLOAD_LINUX=keep
# Uncomment if you want GRUB to pass to the Linux kernel the old parameter
# format "root=/dev/xxx" instead of "root=/dev/disk/by-uuid/xxx"
#GRUB_DISABLE_LINUX_UUID=true
# Uncomment to disable generation of recovery mode menu entries
GRUB_DISABLE_RECOVERY=true
# Uncomment and set to the desired menu colors. Used by normal and wallpaper
# modes only. Entries specified as foreground/background.
GRUB_COLOR_NORMAL="light-gray/black"
GRUB_COLOR_HIGHLIGHT="green/black"
# Uncomment one of them for the gfx desired, a image background or a gfxtheme
#GRUB_BACKGROUND="/usr/share/grub/background.png"
GRUB_THEME="/usr/share/grub/themes/manjaro/theme.txt"
# Uncomment to get a beep at GRUB start
#GRUB_INIT_TUNE="480 440 1"
We did that already (the options would have been added by amdgpu-experimental)
The problem is … the card is sorta recognized as volcanic+ … none of which should need the things anyways … but it still wont load amdgpu properly … if forced (disable radeon) we are still left with black screen.
… maybe … an idea would be to use xorg to load amdgpu.
ex: /etc/X11/xorg.conf.d/99-amdgpu.conf
Yeah in the thread the OP was faced to the same problem, but adding amdgu and radeon to MODULES= should help, instead of only amdgpu. Sorry, i dont use a amd gpu just saying what happened there and it worked somehow for him.
Ok … that could be a difference … I neglected to add radeon as the secondary module.
But … now that you mention it … I think its a problem with the experimental package (this is actually my first time recommending it! )
It seems it adds a few more things . namely
# enable Display Core for Linux >=4.15
options amdgpu dc=1
# Add 10bit color support
options amdgpu deep_color=1
# Enable experimental hardware support in generall
options amdgpu exp_hw_support=1
Whereas I would have just done boot options:
radeon.si_support=0 amdgpu.si_support=1
or
radeon.cik_support=0 amdgpu.cik_support=1
(depending on whether it was southern or sea island and along with mkinitcpio)
So its possible that something like the dc option is actually the issue.
In any case … sure … I agree … might as well try the manual/minimal way and see.