hi Uwe .
i just found a solution .
these are what i have done :
1) first , i comment the blacklisting :
sudo nano /etc/modprobe.d/blacklist-amdgpu.conf
# blacklist amdgpu
2) then , i recreate the initramfs
sudo update-initramfs -u
3) at last , i explicitely set amdgpu to be charged at startup :
echo "amdgpu" | sudo tee -a /etc/modules
4) restart :
sudo reboot
5) then , some verifications :
lsmod amdgpu
sudo dmesg | grep amdgpu
6) all is now ok .
thanks .
On Thu, 6 Feb 2025 21:27:34 +0100 alain <compte.perso.de-al...@bbox.fr>
wrote:
> hi Uwe .
>
>
> the first time i ran the "modprobe amdgpu" command ,
>
> it was not working as well as now .
>
> run this command made my second screen to be set on .
>
> then , gdm restarts and i have to put in again my password .
>
> at last , the gnome desktop opened and all seems to go fine .
>
>
> i made a script with your commands and i reboot the pc before
runnning it .
>
>
> now , i give you the result of your script .
>
>
> it seems that amdgpu is blacklisted , but why ? i do not know at all .
>
> it is a big mistery for me .
>
>
> here are the rapports (its very long)
>
>
>
> root@sid:/home/alain/Téléchargements/dépannage# bash script1.sh
> /etc/modprobe.d
> /etc/modprobe.d/amd64-microcode-blacklist.conf
> # The microcode module attempts to apply a microcode update when
> # it autoloads. This is not always safe, so we block it by default.
> blacklist microcode
> /etc/modprobe.d/blacklist-amdgpu.conf
> blacklist amdgpu
> /etc/modprobe.d/blacklist.conf
>
> # replaced with zenpower
> blacklist k10temp
> /etc/modprobe.d/dkms.conf
> # modprobe information used for DKMS modules
> #
> # This is a stub file, should be edited when needed,
> # used by default by DKMS.
> /etc/modprobe.d/intel-microcode-blacklist.conf
> # The microcode module attempts to apply a microcode update when
> # it autoloads. This is not always safe, so we block it by default.
> blacklist microcode
> /etc/modprobe.d/mdadm.conf
> # mdadm module configuration file
> # set start_ro=1 to make newly assembled arrays read-only initially,
> # to prevent metadata writes. This is needed in order to allow
> # resume-from-disk to work - new boot should not perform writes
> # because it will be done behind the back of the system being
> # resumed. See http://bugs.debian.org/415441 for details.
>
> options md_mod start_ro=1
> /run/modprobe.d
