You are not logged in.
(This part might not be important) I just installed DaVinci Resolve and attempted to import a video file. I heard my fans start going, so I thought it was doing something, but checking System Monitor showed it was using 4% CPU but not reading anything. I thought it was a formatting issue, so I restarted Resolve and tried to convert the file to a different format using FFMPEG.
I walked away for a few minutes and noticed that my computer had suspended, but I could not turn it back on. I kept trying to move the mouse and press keys, but the screen remained black. After a while, I decided to force it to shut down, which caused something really weird - attempting to start it again, I noticed the power button was flashing blue, but I didn't get the count (usually on Alienware laptops, it flashes red a set amount and blue a set amount to indicate a specific error) and when it started after over a minute, GRUB had entirely disappeared from the menu.
I booted into a live install image from a USB, reinstalled grub, and checked the journalctl. It seems to be something to do with my GPU, and the strange problem in the BIOS makes me think there's something horribly wrong with my hardware, despite me only having this laptop for a few weeks.
Here's my journalctl: http://0x0.st/XaQJ.txt
Offline
nouveau is known for issues with newer graphics cards, try installing the proprietary nvidia driver: https://wiki.archlinux.org/title/NVIDIA#Installation
Offline
I'm not even using nouveau. Running lspci -v confirms I'm using the proprietary driver.
Offline
# lspci -k | grep 'in use:'<49,17,III,I> Fama di loro il mondo esser non lassa;
<50,17,III,I> misericordia e giustizia li sdegna:
<51,17,III,I> non ragioniam di lor, ma guarda e passa.
Offline
I'm using the proprietary driver. That command just returns a simplified version of the output I've already seen.
Last edited by Dragin (2024-07-02 21:53:31)
Offline
Your log shows you using nouveau and you might want to post that output so we can judge whether things look correctly
If you are using the prop driver now, repost a new journal log reflecting that and whether you still have issue that prompted your initial post. FWIW if that journal was from a live disk then that's not quite surprising but also useless since it wouldn't reflect a faulty situation from your actual system. Produce the problem, reboot "safely" with https://wiki.archlinux.org/title/Keyboa … el_(SysRq) and post the journal of the crashing boot with
sudo journalctl -b-1Last edited by V1del (2024-07-03 07:28:25)
Offline