Hello, this started to happened a couple of days ago, sometimes the system takes 3-4 attempts to just boot into the display manager.
And also I’m having crashes that makes the system reboot itself.
Could someone please help me?
I couldn’t find a solution by myself.
Specs:
Asus rog strix g15
Ryzen 7 6800HS (8) @ 4.79 GHz GHz
NVIDIA GeForce RTX 3050 Mobile @ GHz
AMD Ryzen 7 6800HS (8) @ 4.79 GHz GHz
RAM 2.15 GiB / 30.60 GiB (7%)Did anything change that might have triggered the issue?
When posting an issue, you should include enough detail to allow others with access to similar hardware to reproduce the conditions. This is easiest if your system is fully updated:
A good starting point is to post the output from running inxi -Fzxx in a terminal (as pre-formatted text).
Random crashes are often due to a hardware problem. If the crashes are due to a software bug, the journal should reference the same software component each time the system crashes. You will need to run journalctl in a terminal and use the -b <N> option to select previous boots. It is often helpful to note the time of each crash. See: https://linuxhandbook.com/journalctl-command/.
If you find similar entries associated with crashes, please post an example (as pre-formatted text).
The most common hardware problem causing random crashes is RAM that is defective or misconfigured. Fedora provides a memtest86+ package that adds an entry to boot the memory tester. Usually you should run the default test configuration for many hours --overnight for several nights or over a weekend.
Is it when booting → to the log-in screen (freeze trying to load log-in)? Or is it log-in screen → desktop (freeze going to desktop)?
Understood, this is my inxi -Fzxx output:
System:
Kernel: 6.14.9-300.fc42.x86_64 arch: x86_64 bits: 64 compiler: gcc v: 15.1.1
Desktop: i3 v: 4.24 dm: Ly Distro: Fedora Linux 42 (Workstation Edition)
Machine:
Type: Laptop System: ASUSTeK product: ROG Strix G513RC_G513RC v: 1.0
serial: <superuser required>
Mobo: ASUSTeK model: G513RC v: 1.0 serial: <superuser required>
UEFI: American Megatrends LLC. v: G513RC.327 date: 02/16/2023
Battery:
ID-1: BAT0 charge: 43.1 Wh (94.9%) condition: 45.4/56.0 Wh (81.1%)
volts: 16.7 min: 15.9 model: AS3GXSC3KC G513-36 serial: <filter>
status: not charging
ID-2: hidpp_battery_0 charge: 36% condition: N/A volts: 3.8 min: N/A
model: Logitech G502 LIGHTSPEED Wireless Gaming Mouse serial: <filter>
status: discharging
CPU:
Info: 8-core model: AMD Ryzen 7 6800HS with Radeon Graphics bits: 64
type: MT MCP arch: Zen 3+ rev: 1 cache: L1: 512 KiB L2: 4 MiB L3: 16 MiB
Speed (MHz): avg: 1368 min/max: 400/4787 boost: enabled cores: 1: 1368
2: 1368 3: 1368 4: 1368 5: 1368 6: 1368 7: 1368 8: 1368 9: 1368 10: 1368
11: 1368 12: 1368 13: 1368 14: 1368 15: 1368 16: 1368 bogomips: 102207
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
Graphics:
Device-1: NVIDIA GA107M [GeForce RTX 3050 Mobile] vendor: ASUSTeK
driver: nvidia v: 575.57.08 arch: Ampere pcie: speed: 2.5 GT/s lanes: 8
ports: active: none off: HDMI-A-1 empty: DP-6,eDP-2 bus-ID: 01:00.0
chip-ID: 10de:25a2
Device-2: Advanced Micro Devices [AMD/ATI] Rembrandt [Radeon 680M]
vendor: ASUSTeK driver: amdgpu v: kernel arch: RDNA-2 pcie: speed: 16 GT/s
lanes: 16 ports: active: eDP-1 empty: DP-1, DP-2, DP-3, DP-4, DP-5,
Writeback-1 bus-ID: 05:00.0 chip-ID: 1002:1681 temp: 45.0 C
Display: x11 server: X.Org v: 21.1.16 with: Xwayland v: 24.1.6
compositor: Picom v: 12.5 driver: X: loaded: modesetting,nvidia
alternate: fbdev,nouveau,nv,vesa dri: radeonsi
gpu: amdgpu,nvidia,nvidia-nvswitch display-ID: :0 screens: 1
Screen-1: 0 s-res: 3840x1080 s-dpi: 80
Monitor-1: HDMI-A-1 mapped: HDMI-0 note: disabled pos: primary,left
model: AOC 27G2G8 res: N/A dpi: 82 diag: 686mm (27")
Monitor-2: eDP-1 mapped: eDP-1-1 pos: right model: Najing CEC Panda 0x004d
res: 1920x1080 hz: 144 dpi: 142 diag: 395mm (15.5")
API: OpenGL v: 4.6.0 vendor: nvidia v: 575.57.08 glx-v: 1.4
direct-render: yes renderer: NVIDIA GeForce RTX 3050 Laptop GPU/PCIe/SSE2
API: EGL Message: EGL data requires eglinfo. Check --recommends.
Info: Tools: api: glxinfo de: kscreen-console,kscreen-doctor
gpu: nvidia-settings,nvidia-smi wl: nwg-displays,wlr-randr x11: xdriinfo,
xdpyinfo, xprop, xrandr
Audio:
Device-1: NVIDIA GA107 High Definition Audio vendor: ASUSTeK
driver: snd_hda_intel v: kernel pcie: speed: 16 GT/s lanes: 8
bus-ID: 01:00.1 chip-ID: 10de:2291
Device-2: Advanced Micro Devices [AMD] Audio Coprocessor vendor: ASUSTeK
driver: snd_pci_acp6x v: kernel pcie: speed: 16 GT/s lanes: 16
bus-ID: 05:00.5 chip-ID: 1022:15e2
Device-3: Advanced Micro Devices [AMD] Family 17h/19h/1ah HD Audio
vendor: ASUSTeK driver: snd_hda_intel v: kernel pcie: speed: 16 GT/s
lanes: 16 bus-ID: 05:00.6 chip-ID: 1022:15e3
API: ALSA v: k6.14.9-300.fc42.x86_64 status: kernel-api
Server-1: JACK v: 1.9.22 status: off
Server-2: PipeWire v: 1.4.5 status: active with: 1: pipewire-pulse
status: active 2: wireplumber status: active 3: pipewire-alsa type: plugin
4: pw-jack type: plugin
Network:
Device-1: MEDIATEK MT7922 802.11ax PCI Express Wireless Network Adapter
vendor: Foxconn driver: mt7921e v: kernel pcie: speed: 5 GT/s lanes: 1
bus-ID: 02:00.0 chip-ID: 14c3:0616
IF: wlo1 state: down mac: <filter>
Device-2: Realtek RTL8125 2.5GbE vendor: ASUSTeK driver: r8169 v: kernel
pcie: speed: 5 GT/s lanes: 1 port: e000 bus-ID: 03:00.0 chip-ID: 10ec:8125
IF: enp3s0 state: up speed: 1000 Mbps duplex: full mac: <filter>
IF-ID-1: ham0 state: unknown speed: 10000 Mbps duplex: full mac: <filter>
Bluetooth:
Device-1: Foxconn / Hon Hai Wireless_Device driver: btusb v: 0.8 type: USB
rev: 2.1 speed: 480 Mb/s lanes: 1 bus-ID: 1-4:3 chip-ID: 0489:e0e2
Report: btmgmt ID: hci0 rfk-id: 0 state: up address: <filter> bt-v: 5.2
lmp-v: 11
Drives:
Local Storage: total: 476.94 GiB used: 151.25 GiB (31.7%)
ID-1: /dev/nvme0n1 vendor: Micron model: 2400 MTFDKBA512QFM
size: 476.94 GiB speed: 63.2 Gb/s lanes: 4 serial: <filter> temp: 22.9 C
Partition:
ID-1: / size: 179.3 GiB used: 150.68 GiB (84.0%) fs: btrfs
dev: /dev/nvme0n1p6
ID-2: /boot size: 973.4 MiB used: 539.8 MiB (55.5%) fs: ext4
dev: /dev/nvme0n1p5
ID-3: /boot/efi size: 96 MiB used: 49.8 MiB (51.9%) fs: vfat
dev: /dev/nvme0n1p1
ID-4: /home size: 179.3 GiB used: 150.68 GiB (84.0%) fs: btrfs
dev: /dev/nvme0n1p6
Swap:
ID-1: swap-1 type: zram size: 8 GiB used: 0 KiB (0.0%) priority: 100
dev: /dev/zram0
Sensors:
System Temperatures: cpu: 50.6 C mobo: N/A
Fan Speeds (rpm): cpu: 2700
GPU: device: nvidia screen: :0.0 temp: 42 C device: amdgpu temp: 46.0 C
Info:
Memory: total: 32 GiB note: est. available: 30.6 GiB used: 4.66 GiB (15.2%)
Processes: 457 Power: uptime: 14m wakeups: 0 Init: systemd v: 257
target: graphical (5) default: graphical
Packages: pm: rpm pkgs: N/A note: see --rpm pm: flatpak pkgs: 115
Compilers: clang: 20.1.6 gcc: 15.1.1 Shell: Bash v: 5.2.37 running-in: kitty
inxi: 3.3.38
Output from journalctl -k -p 0..3 -b -2 --no-pager :
Jun 13 13:44:41 fedora kernel: ACPI BIOS Error (bug): Failure creating named object [\_TZ.TZ01], AE_ALREADY_EXISTS (20240827/dswload2-326)
Jun 13 13:44:41 fedora kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20240827/psobject-220)
Jun 13 13:44:41 fedora kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.GPP2], AE_NOT_FOUND (20240827/dswload2-162)
Jun 13 13:44:41 fedora kernel: ACPI Error: AE_NOT_FOUND, During name lookup/catalog (20240827/psobject-220)
Jun 13 13:44:41 fedora kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.GPP2.WWAN], AE_NOT_FOUND (20240827/dswload2-162)
Jun 13 13:44:41 fedora kernel: ACPI Error: AE_NOT_FOUND, During name lookup/catalog (20240827/psobject-220)
Jun 13 13:44:41 fedora kernel: hub 6-0:1.0: config failed, hub doesn't have any ports! (err -19)
Jun 13 17:44:46 fedora kernel:
I will give it a look and let you know 
Is it in the middle of the booting process. Suddenly stops at around 4-5 seconds of load and goes back to the grub selector menu and so on for 3 to 4 times, until finally loads correctly and shows the display manager.
What DE are you using? I would expect mutter for GNOME on Workstation.
Depending on how used the AMD GPU is; if you have bad RAM settings/stability, I’ve seen AMD GPUs react to that more. I’d do the memtest, but I’d also try setting RAM to for-sure stable options (like 2133MHz 1.4V DDR4) first and see if anything changes.
I’m using i3WM.
When you say “AMD GPU” do you mean AMD integrated graphics? Because I’m using an nvidia gpu on hybrid mode through supergfxctl.
All right, I’ll give a you an update @gnwiii @Espionage724 in 10 hours aprox (already late here). Also, thank you both in advance for your time and help 
The ACPI errors are usually not a problem, but see: https://bbs.archlinux.org/viewtopic.php?id=284843 for discussion of the hub doesn't have any ports! (err -19) error and then https://bugzilla.kernel.org/show_bug.cgi?id=220181.
I ran the all the test of memtest86+ in paralell mode at night, the result was 0 errors.
So I just wait for the patch to be in the next mainstream kernel version?
Making sure you're not a bot!.
does the external HDMI monitor work? What’s the refresh rate?
ports: active: none
off: HDMI-A-1
empty: DP-6,eDP-2
does the system boot if you remove the blacklist entries for nouveau in grub menu?
Yes. Is 240hz, more precise 239.96 looking at xrandr if I remember correctly.
I don’t think it’s a good idea since I installed and signed the nvidia drivers using the rpm fusion method. But if necessary I could try.
Ah i3wm and X11. Could you try to change that to 60 or 120 or whatever is supported by the monitor? You could also try to remove rhgb from the kernel args. This will disable plymouth and you can see boot messages on the console.
There was a similar inxi output but with kde /wayland, but the system booted only had issues driving the HDMI monitor.
It looks like the proposal is to patch for older USB2 only systems. From an LHDB profile for your model, your system appears to have only USB4, so the patch may not apply. You could view the xHC port information in your system and compare with the bug report.
After some more research, I may post a suggestion that the patch should consider USB4-only systems as well.
I am going to replace the nvme with a new one to check if that is the cause of the problem. I will update when that happens.