Arch Linux

Xx_RiK_xX

Member

Registered: 2023-03-25

Posts: 24

black screen during boot

during the boot, when it shows the triggering uevents part, I get a black screen. same happens with the arch livecd. so I appended nomodeset to the grub parameter, and it boots fine. but adding it causes hyprland to not start. I have a rx 570 with mesa drivers. this is what I have in my boot parameter amdgpu.ppfeaturemask=0xffffffff nowatchdog mitigations=off. this thing started happening a few days ago. I haven't installed anything at that time to cause it.

seth

Member

From: Won't reply 2 private help req

Registered: 2012-09-03

Posts: 75,991

Re: black screen during boot

Do not reboot w/ the power button, use ctrl+alt+del (frenetically) or https://wiki.archlinux.org/title/Keyboa … el_(SysRq)
Then, from the "nomodeset" reboot, post the journal of the bogus boot (-1 means "one boot ago")

sudo journalctl -b -1 | curl -F 'file=@-' 0x0.st

---

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Xx_RiK_xX

Member

Registered: 2023-03-25

Posts: 24

Re: black screen during boot

this is for -1 http://0x0.st/X8h4.txt and this for -2 http://0x0.st/X8hJ.txt I forgot which one caused trouble. so basically. after I set the nomodeset and boot, and then reboot again, I can boot into hyprland. also I rebooted way too many times with the power button didn't knew that ctrl alt del. I checked the disk with btrfs check in the liveiso and it said no errors. is it gonna cause me some serious problem now that I have restarted with the reboot button too many times?

loqs

Member

Registered: 2014-03-06

Posts: 18,913

Re: black screen during boot

May 11 17:12:59 fairytail kernel: amdgpu: Virtual CRAT table created for CPU
May 11 17:12:59 fairytail kernel: amdgpu: Topology: Add CPU node
May 11 17:12:59 fairytail kernel: amdgpu 0000:01:00.0: enabling device (0006 -> 0007)
May 11 17:12:59 fairytail kernel: [drm] initializing kernel modesetting (POLARIS10 0x1002:0x67DF 0x1458:0x2312 0xEF).
May 11 17:12:59 fairytail kernel: [drm] register mmio base: 0xF7E00000
May 11 17:12:59 fairytail kernel: [drm] register mmio size: 262144
May 11 17:12:59 fairytail kernel: [drm] add ip block number 0 <vi_common>
May 11 17:12:59 fairytail kernel: [drm] add ip block number 1 <gmc_v8_0>
May 11 17:12:59 fairytail kernel: [drm] add ip block number 2 <tonga_ih>
May 11 17:12:59 fairytail kernel: [drm] add ip block number 3 <gfx_v8_0>
May 11 17:12:59 fairytail kernel: [drm] add ip block number 4 <sdma_v3_0>
May 11 17:12:59 fairytail kernel: [drm] add ip block number 5 <powerplay>
May 11 17:12:59 fairytail kernel: [drm] add ip block number 6 <dm>
May 11 17:12:59 fairytail kernel: [drm] add ip block number 7 <uvd_v6_0>
May 11 17:12:59 fairytail kernel: [drm] add ip block number 8 <vce_v3_0>
May 11 17:12:59 fairytail kernel: amdgpu 0000:01:00.0: amdgpu: Fetched VBIOS from VFCT
May 11 17:12:59 fairytail kernel: amdgpu: ATOM BIOS: xxx-xxx-xxx
May 11 17:12:59 fairytail kernel: [drm] UVD is enabled in VM mode
May 11 17:12:59 fairytail kernel: [drm] UVD ENC is enabled in VM mode
May 11 17:12:59 fairytail kernel: [drm] VCE enabled in VM mode
May 11 17:12:59 fairytail kernel: Console: switching to colour dummy device 80x25
May 11 17:12:59 fairytail kernel: amdgpu 0000:01:00.0: vgaarb: deactivate vga console
May 11 17:12:59 fairytail kernel: amdgpu 0000:01:00.0: amdgpu: Trusted Memory Zone (TMZ) feature not supported
May 11 17:12:59 fairytail kernel: [drm] vm size is 64 GB, 2 levels, block size is 10-bit, fragment size is 9-bit
May 11 17:12:59 fairytail kernel: amdgpu 0000:01:00.0: amdgpu: VRAM: 4096M 0x000000F400000000 - 0x000000F4FFFFFFFF (4096M used)
May 11 17:12:59 fairytail kernel: amdgpu 0000:01:00.0: amdgpu: GART: 256M 0x000000FF00000000 - 0x000000FF0FFFFFFF
May 11 17:12:59 fairytail kernel: [drm] Detected VRAM RAM=4096M, BAR=256M
May 11 17:12:59 fairytail kernel: [drm] RAM width 256bits GDDR5
May 11 17:12:59 fairytail kernel: [drm] amdgpu: 4096M of VRAM memory ready
May 11 17:12:59 fairytail kernel: [drm] amdgpu: 7968M of GTT memory ready.
May 11 17:12:59 fairytail kernel: [drm] GART: num cpu pages 65536, num gpu pages 65536
May 11 17:12:59 fairytail kernel: [drm] PCIE GART of 256M enabled (table at 0x000000F400300000).
May 11 17:12:59 fairytail kernel: [drm] Chained IB support enabled!
May 11 17:12:59 fairytail kernel: amdgpu: hwmgr_sw_init smu backed is polaris10_smu
May 11 17:12:59 fairytail kernel: [drm] Found UVD firmware Version: 1.130 Family ID: 16
May 11 17:12:59 fairytail kernel: [drm] Found VCE firmware Version: 53.26 Binary ID: 3
May 11 17:12:59 fairytail kernel: [drm] Display Core v3.2.266 initialized on DCE 11.2
May 11 17:12:59 fairytail kernel: [drm] UVD and UVD ENC initialized successfully.
May 11 17:12:59 fairytail kernel: [drm] VCE initialized successfully.
May 11 17:12:59 fairytail kernel: kfd kfd: amdgpu: Allocated 3969056 bytes on gart
May 11 17:12:59 fairytail kernel: kfd kfd: amdgpu: Total number of KFD nodes to be created: 1
May 11 17:12:59 fairytail kernel: amdgpu: Virtual CRAT table created for GPU
May 11 17:12:59 fairytail kernel: amdgpu: Topology: Add dGPU node [0x67df:0x1002]
May 11 17:12:59 fairytail kernel: kfd kfd: amdgpu: added device 1002:67df
May 11 17:12:59 fairytail kernel: amdgpu 0000:01:00.0: amdgpu: SE 4, SH per SE 1, CU per SH 9, active_cu_number 32
May 11 17:12:59 fairytail kernel: amdgpu 0000:01:00.0: amdgpu: Using BOCO for runtime pm
May 11 17:12:59 fairytail kernel: [drm] Initialized amdgpu 3.57.0 20150101 for 0000:01:00.0 on minor 1
May 11 17:12:59 fairytail kernel: amdgpu 0000:01:00.0: [drm] Cannot find any crtc or sizes

For comparison could you please try without `modeset` and also without `amdgpu.ppfeaturemask=0xffffffff`.

Xx_RiK_xX

Member

Registered: 2023-03-25

Posts: 24

Re: black screen during boot

I should have one of the logs without nomodeset.

loqs

Member

Registered: 2014-03-06

Posts: 18,913

Re: black screen during boot

I should have one of the logs without nomodeset.

The -2 log is without `nomodeset` but `amdgpu.ppfeaturemask=0xffffffff` is being used.  I wanted to see if removing that parameter in addition to not using `nomodeset` changes anything in the journal.