You are not logged in.
when I try to turn on the PC, after the list of "ok" it gives me a black screen with an underscore at the top left... then I tried to enter the alternative console with CTRL+ALT+F3 and if I try to running sudo pacman -Syu tells me it can't resolve the hosts and therefore doesn't work.
Also after checking the iwctl that i was connected to a WiFi I tried to ping google.com obtaining as result "Temporary failure in name resolution".
I checked the "pacman.log" and the last time I used the laptop I uninstalled some packages:
"qt5-webkit" and its dependencies
"woff2"
"ruby-erb"
"ruby"
"rubygems"
"hyphen"
"gperf"
"gendesk"
"rhash"
"cppdap"
"asar"
"nodejs"
"libngtcp2"
"libuv"
I also tried checking "journalctl -b" finding several red lines:
x86/cpu: SGX disabled by BIOS
these 2 lines repeated several times:
APCI BIOS Error (bug): Failing creating named object [_SB.PC.I0.XHC.RHUB.SS06._PLD], AE_ALREADY_EXISTS (20240322/dswload2-326)
APCI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20240322/psobject-220)
nouveau 0000:02:00.0: bus: MMIO read of 00000000 FAULT at 6013d4 [ PRIVRING ]
Bluetooth: hci0: Failed to send firmware data (-38)
nl80211: kernel reports: Match already configured
nouveau 0000:02:00.0: bus: MMIO read of 00000000 FAULT at 619444 [ PRIVRING ]
some other bluetooth error
Offline
Are you using a nvidia GPU with the proprietary drivers?
Offline
Yes, I'm using a nvidia GPU, how can i check drivers?
Offline
Offline
The nvidia drivers are installed, btw I connected via cable and managed to update the system with "sudo pacman -Syu", after which I tried to reinstall the packages I listed previously, and now while booting it get stucked here:
...
[ OK ] Started WPA supplicant.
[ 6.546256] Bluetooth: hci0: Malformed MSFT vendor event: 0x02 arch
"and a blinking underscore"
Last edited by Lory.exe (2024-10-19 14:17:25)
Offline
enter the alternative console with CTRL+ALT+F3 and if I try to running
So you can switch the VT and login from a TTY, the problem is your graphical session.
I also tried checking "journalctl -b" finding several red lines:
Just like red-letter bibles, red-letter journals don't quite capture the important stuff
If you cannot get an internet connection from the broken system, dump the journal of the boot into a file, usb-walk that to a system w/ internet and post/upload it.
If you're it posting here and in general please use [code][/code] tags.
Offline