the 2nd entry needs to be on the same grep line. But based on the output the options in that file aren't being used. On mine both of the options are set to one on amdgpu, and 0 on radeon. do lsinitrd | grep enable_amdgpu_disable_radeon you should see the file being included in the output. If it is not, try running "dracut -f" and reboot. On Mon, Jul 4, 2022 at 3:13 PM Robert Moskowitz <rgm@xxxxxxxxxxxxxxx> wrote: > > > > On 7/4/22 15:19, Roger Heflin wrote: > > try this and see what it shows: > > > > grep -v adfasd /sys/module/*/parameters/si_support > > /sys/module/amdgpu/parameters/si_support:0 > /sys/module/radeon/parameters/si_support:1 > > > /sys/module/*/parameters/cik_support > As root: > > -bash: /sys/module/amdgpu/parameters/cik_support: Permission denied > > > And I checked: > > # cat /etc/modprobe.d/enable_amdgpu_disable_radeon.conf > options amdgpu si_support=1 > options amdgpu cik_support=1 > options radeon si_support=0 > options radeon cik_support=0 > > > > > > to verify that radeon is disabled and amdgpu is enabled. > > > > I tried on mine, an my amd gpu is a really old one while claiming to > > be supported by amdgpu, acts like it is not. > > > > On Mon, Jul 4, 2022 at 10:39 AM Robert Moskowitz <rgm@xxxxxxxxxxxxxxx> wrote: > >> Finally did this: > >> > >> I did not make the change when I got back to my office/home, and things > >> worked fine into mid-sunday when it locked again. Did a dnf update from > >> a character session after power cycle and new kernel, firefox, and > >> linuxfirmware. So decided to see how it would go. > >> > >> And I could work with cnn and youtube and other video stuff that was > >> locking me up. Plus other apps, so I thought maybe things were fixed.... > >> > >> But twice my session aborted without a system lockup and I had to log > >> back in and restart everything. > >> > >> Then I got a lock up again, so I power cycled and hay! New kernel. But > >> I still did as you instructed below, making the file and running > >> dracut. Now on reboot: > >> > >> # lspci -nnk | egrep -i "VGA|DISPLAY" -A3 > >> 00:01.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. > >> [AMD/ATI] Kabini [Radeon HD 8330] [1002:9832] > >> Subsystem: Lenovo Device [17aa:2219] > >> Kernel driver in use: radeon > >> Kernel modules: radeon, amdgpu > >> > >> which is the same as before: > >> > >> It still says using radeon driver? > >> > >> Should I try your radeon_blacklist.conf ? > >> > >> On 6/30/22 08:04, Roger Heflin wrote: > >>> I do not believe anything else is needed. Where dmesg said > >>> "radeon:", it should now say "amdgpu:". amdgpu seems to be the > >>> replacement and/or currently developed driver. And the recent > >>> non-ryzen AMD laptops are using an older AMD cpu + ATI/AMD build-in > >>> video, that originally were blocked from using the (at the time - ) > >>> experimental amdgpu driver. > >>> > >>> It seems pretty likely that there is code from the radeon driver in > >>> the amdgpu driver, a lot of the messages from it look > >>> similar/identical, and on my ryzen system that default uses amdgpu. > >>> > >>> On Thu, Jun 30, 2022 at 6:21 AM Robert Moskowitz <rgm@xxxxxxxxxxxxxxx> wrote: > >>>> Is it correct to assume that I don't have to install anything more to > >>>> get the amdgpu driver? > >>>> > >>>> On 6/30/22 06:22, Roger Heflin wrote: > >>>>> That will not work. > >>>>> > >>>>> If I am reading the module options right (and other peoples comments), > >>>>> amdgpu will not manage a si/cik chipset unless the correct _support is > >>>>> set to 1. > >>>>> > >>>>> On Thu, Jun 30, 2022 at 12:16 AM Samuel Sieb <samuel@xxxxxxxx> wrote: > >>>>>> On 6/29/22 18:25, Roger Heflin wrote: > >>>>>>> The notes I found say to create a file in /etc/modprobe.d > >>>>>>> > >>>>>>> And say call it anything but something like > >>>>>>> enable_amdgpu_disable_radeon.conf and put this in it: > >>>>>>> options amdgpu si_support=1 > >>>>>>> options amdgpu cik_support=1 > >>>>>>> options radeon si_support=0 > >>>>>>> options radeon cik_support=0 > >>>>>>> > >>>>>>> and then do a "dracut --force" and reboot. > >>>>>> The other option is to make a file called radeon-blacklist.conf and put in: > >>>>>> blacklist radeon > >>>>>> > >>>>>> The filenames don't actually matter as long as they end in ".conf". > >>>>>> _______________________________________________ > >>>>>> users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx > >>>>>> To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx > >>>>>> Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ > >>>>>> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > >>>>>> List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx > >>>>>> Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure > >>>>> _______________________________________________ > >>>>> users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx > >>>>> To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx > >>>>> Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ > >>>>> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > >>>>> List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx > >>>>> Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure > _______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
