Hi, thanks for the response!
Does experimental support for amdgpu means that the kernel is quite possibly unstable?
And also how to I access the kernel command line to set the module parameters like described in the link you sent?
Hi, thanks for the response!
Does experimental support for amdgpu means that the kernel is quite possibly unstable?
And also how to I access the kernel command line to set the module parameters like described in the link you sent?
Don’t have to be unstable… Gentoo Wiki has a great and clean feature table:
https://wiki.gentoo.org/wiki/Radeon#Feature_support
https://wiki.gentoo.org/wiki/AMDGPU#Feature_support
GCN1 is “Southern Islands”.
Maybe this is more clear, how to set it up:
Ok. thanks this is a bit more cleaner, but the problem now is that I don’t have any files on my modprobe.d folder or at least it doesn’t seems to be any.
Maybe I am interpreting things wrong, this commands are supposed to be imputed on the terminal?
With only the MODULES=(amdgpu radeon) that has to be on the mkinitcpio.conf file.
Is that right?
Yes these config files need to be created.
Yes… this for the terminal:
su && \
echo -e "options amdgpu si_support=1\noptions amdgpu cik_support=1" > /etc/modprobe.d/amdgpu.conf \
echo -e "options radeon si_support=0\noptions radeon cik_support=0" > /etc/modprobe.d/radeon.conf
su -c 'echo -e "options amdgpu si_support=1\noptions amdgpu cik_support=1" > /etc/modprobe.d/amdgpu.conf echo -e "options radeon si_support=0\noptions radeon cik_support=0" > /etc/modprobe.d/radeon.conf'
For this:
You can type:
sudo nano /etc/mkinitcpio.conf
and add the modules there.
Ok just one more question before I try this:
If I execute this commands without creating the files, will it create them for me, or I have to create them first?
su &&
echo -e “options amdgpu si_support=1\noptions amdgpu cik_support=1” > /etc/modprobe.d/amdgpu.conf
echo -e “options radeon si_support=0\noptions radeon cik_support=0” > /etc/modprobe.d/radeon.conf
It should create it… sorry, my failure… this works:
su -c 'echo -e "options amdgpu si_support=1\noptions amdgpu cik_support=1" > /etc/modprobe.d/amdgpu.conf && echo -e "options radeon si_support=0\noptions radeon cik_support=0" > /etc/modprobe.d/radeon.conf'
Ok I will try this now, and will update you on the results.
Wait there’s one more thing on the modules there is one that is empty with only this MODULES=" ", is this the one where I have to put this MODULES=(amdgpu radeon) on?
Old method:
MODULES="amdgpu radeon"
New method:
MODULES=(amdgpu radeon)
Thats all…
If sudo mkinitcpio -P
shows no errors then it is ok.
There was 2 errors that were about kernel 5.7 maybe because I don’t have them installed.
==> Building image from preset: /etc/mkinitcpio.d/linux57.preset: 'default'
-> -k /boot/vmlinuz-5.7-x86_64 -c /etc/mkinitcpio.conf -g /boot/initramfs-5.7-x86_64.img
==> ERROR: '/lib/modules/5.7.19-2-MANJARO' is not a valid kernel module directory
==> Building image from preset: /etc/mkinitcpio.d/linux57.preset: 'fallback'
-> -k /boot/vmlinuz-5.7-x86_64 -c /etc/mkinitcpio.conf -g /boot/initramfs-5.7-x86_64-fallback.img -S autodetect
==> ERROR: '/lib/modules/5.7.19-2-MANJARO' is not a valid kernel module directory
Here it is
I assume you have removed already the kernel 5.7?
If yes, then remove all residual files from your /boot folder and sub-folders containing “5.7” in the filenames by "rm"
command via terminal.
Afterwards:
sudo mkinitcpio -P
Don’t expect me to repeat this.
I think I removed it because it was causing some freezing issues.
How do I remove this residual files?
On the boot folders there are only 2 files mentioning 5.7.
initramfs-5.7-x86_64.img and initramfs-5.7-x86_64-fallback.img
Should I delete them? Are you sure it’s safe to remove it?
Please run this again:
I saw that i forgot &&
between the commands. Sorry, where is my brain today???
Do I have to run this again too?
sudo nano /etc/mkinitcpio.conf
MODULES=(amdgpu radeon)
Also is this command supposed to give any output?
If sudo nano /etc/mkinitcpio.conf
only shows MODULES=(amdgpu radeon)
then this is a problem
It should look like this:
# 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 radeon)
# 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 resume autodetect modconf block keyboard keymap mdadm_udev lvm2 filesystems fsck"
# COMPRESSION
# Use this to compress the initramfs image. By default, gzip compression
# is used. Use 'cat' to create an uncompressed image.
#COMPRESSION="cat"
#COMPRESSION="pigz"
#COMPRESSION="gzip"
#COMPRESSION="bzip2"
#COMPRESSION="lzma"
COMPRESSION="xz"
#COMPRESSION="lzop"
#COMPRESSION="lz4"
# COMPRESSION_OPTIONS
# Additional options for the compressor
COMPRESSION_OPTIONS=(-T0)
The file is identical to this one, so I guess it’s all good?
I was asking if I had to redo this two things again.
And if
su -c ‘echo -e “options amdgpu si_support=1\noptions amdgpu cik_support=1” > /etc/modprobe.d/amdgpu.conf && echo -e “options radeon si_support=0\noptions radeon cik_support=0” > /etc/modprobe.d/radeon.conf’
Was supposed to give any output
I thought that installing amdgpu-experimental
was equivalent to all this process? And a way to avoid all this “mess”.
But the learning experience is worthwhile I guess
Yeah kinda of a mess, but it’s worth it I guess
to check if that was correct:
type this:
cat /etc/modprobe.d/amdgpu.conf
cat /etc/modprobe.d/radeon.conf
This will show the content of the files.