Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#72410 - Installer cannot handle internal GPU on Gigabyte B550m Pro-p

Attached to Project: Arch Linux
Opened by jonas (jonix) - Wednesday, 13 October 2021, 13:22 GMT
Last edited by David Runge (dvzrv) - Thursday, 14 October 2021, 16:34 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To David Runge (dvzrv)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Hi.

I just bought a new mb; Gigabyte B550M Aorus Pro-p with a Ryzen 5000. When installing archlinux the prompt says before screen goes blank: "Triggering uevents". I had it running for 1 hour without artificial life on screen. It did listens to ctr+alt+del, implying some invisible life form. I tried installing openSuse and Debian - both works fine.

Then installing an external graphic card. installing archlinux then works fine. If that was it, I probably wouldn't have written this bug report.

Since the internal GPU is far better than the since long obsolete external GPU used for installing archlinux, I removed it. Then same thing happens - blank screen.

So archlinux cannot handle the internal GPU of motherboard Gigabyte B550M Pro-p.

I tried to install a serie of BIOS from F10-F14b along the way but no effect. Now running the latest F14b.

I installed arch from a UEFI Sandisk 16GB (both arclinux and archlabs, both not working)

I have no logfiles to provide, but will display whatever asked for.

thanks
Jonas
This task depends upon

Closed by  David Runge (dvzrv)
Thursday, 14 October 2021, 16:34 GMT
Reason for closing:  Not a bug
Additional comments about closing:  Hardware issues most likely introduced by kernel version
Comment by loqs (loqs) - Wednesday, 13 October 2021, 16:37 GMT
Did you try disabling modesetting [1] or blacklisting [2] the amdgpu module?

[1] https://wiki.archlinux.org/title/Kernel_mode_setting#Disabling_modesetting
[2] https://wiki.archlinux.org/title/Kernel_module#Using_kernel_command_line_2
Comment by jonas (jonix) - Wednesday, 13 October 2021, 21:21 GMT

thanx for support

No I did mot. But I'll try to modeset tomorrow (nomodeset and nouveau.modeset=0). What would be the implication of modesetting in this case? Would it render the GPU fully functional?

I guess blacklisting will make the internal GPU invisible and thus inactive, and my system in need of a new GPU.


regards
Comment by loqs (loqs) - Wednesday, 13 October 2021, 21:54 GMT
modesetting is required for Wayland or X11 with hardware acceleration. With the GPU module blacklisted you may still have basic display support.
Installing with modesetting disabled or the GPU module blacklisted would allow you to upgrade to the latest kernel which might have fixed the issue and also adds persistent storage to record kernel messages even when the screen is blank.
Comment by jonas (jonix) - Thursday, 14 October 2021, 08:18 GMT
Hi
I ran (without external GPU) the installer with modeset (nomodeset and nouveau.modeset=0) and all went well. in grub I have to redo modeset commands and screen is ok. I updated but nothing available. I edited then the /etc/default/grub with the "modesets" The system is now behaving ok. I try the command " xrandr --mode "1920x1080" ", but it doesn't recognize that mode, so obviously the GPU functionality is limited. Can it be fixed??



Thanx for help. bless u from danger!

Loading...