hi folks. i could use some help. i’ve been running duel boot endeavouros and windows 10 on a microsoft surface book 3 for about two years. it was initially installed and managed by someone with much more experience than me, but ive been doing it on my own for most of that time, and contacting them for help is no longer an option. ive taught myself quite a bit and until now ive been able to solve any problems that have arisen with help from past forum posts, but i’ve finally hit a wall.
yesterday i updated my system using yay, as i do about once a week. everything seemed normal and i rebooted as usual. the system booted without a problem, but once the login screen appeared, it was completely unresponsive. no keyboard, touchscreen, or track pad reaction. i can’t log in and I couldn’t get to tty from that screen. i did some digging on forums and managed to get to tty from the boot settings. i looked through my journal log and it seems like the problem is nvidia-uvm. i tried what i saw recommended on other forums ( -Syu nvidia-uvm) which i think would work, but all i got was a slew of warnings and errors about my mirrors (see images below). it seems like my computer isn’t connected to the internet. i couldn’t get wlan0 connect, so i got an ethernet to usbc converter. the system is registering it but won’t connect to it. so far i haven’t found any forums that have helped with the ethernet problem.
i’ve also tried downgrading nvidia and downgrading the whole system, which just produces the same mirror errors.
because it won’t connect to the internet, i can’t post the journal or errors directly, but i’m including pictures of the things i’ve mentioned. if there’s any other info that could help yall let me know.
i can boot to windows just fine. i get the same problems when i try to boot linux fallback and when i try to boot wayland (i mostly use x11)
Tried the dhclient -r ?
That should interrogate the router for an IP address.
Then try ping 8.8.8.8 to see if the network is live. then try ping endeavouros.com. If it can’t get that then the DNS is still down, so inspect that with cat /etc/resolv.conf
@itslee
Please check your /etc/pacman.conf file and make sure your repos have been changed to match this.
# The testing repositories are disabled by default. To enable, uncomment the
# repo name header and Include lines. You can add preferred servers immediately
# after the header, and they will be used before the default mirrors.
[endeavouros]
SigLevel = PackageRequired
Include = /etc/pacman.d/endeavouros-mirrorlist
#[core-testing]
#Include = /etc/pacman.d/mirrorlist
[core]
Include = /etc/pacman.d/mirrorlist
#[extra-testing]
#Include = /etc/pacman.d/mirrorlist
[extra]
Include = /etc/pacman.d/mirrorlist
# If you want to run 32 bit applications on your x86_64 system,
# enable the multilib repositories as required here.
#[multilib-testing]
#Include = /etc/pacman.d/mirrorlist
[multilib]
Include = /etc/pacman.d/mirrorlist
Edit: Then you can try running an update.
Edit: In case you weren’t aware.
Edit: After checking this you may have to arch-chroot from a live ISO to see if you can fix your issue by updating and possibly reinstalling kernels.
this definitely changed things!! i’m still getting all my mirror warnings, i got them while i was running the update too, but it seems like most of it updated. should i try the nvidia things before i try arch-chroot? im not sure i know how to do that.
edit: this may be unrelated but when i was in /etc/pacman.conf i saw a line that said “Ignorepkg = linux” which seemed very wrong, so i wrote it out. was i right to do that?
