Arch Linux

herbertwatson

Member

Registered: 2020-09-08

Posts: 4

[SOLVED] Very odd problem after new install

I have a habit of keeping my computer on for days or even weeks at a time without restarting. I decided to restart today and now almost everything has broke. My display driver is totally broke and more importantly my internet is not functioning. To start when I boot my computer I no longer get the resolution adjustment like I usually do and it stays in the same low resolution mode. When I login to my non-root account everything seems broken. I cannot open anything, I cannot move the mouse, the status bar works fine but it seems like Xorg is crippled to only updating the clock on the status bar. When I login to the root account the most apparent thing I notice is that the internet does not work. Network Manager is running and seems to be functioning just fine, but it cannot detect any connections. according to ip a my device is UP. I double checked and made sure all the systemd services are enabled and running. I have never come across something like this before. Could it be a kernel module that failed to start? I cannot do anything on my system because of this.

Last edited by herbertwatson (2020-09-08 14:33:09)

herbertwatson

Member

Registered: 2020-09-08

Posts: 4

Re: [SOLVED] Very odd problem after new install

I just checked journalctl and i received this error:

 Sep 08 01:28:31 thinkpad kernel: DMAR: [Firmware Bug]: No firmware reserved region can cover this RMRR [0x00000000db800000-0x00000000df9fffff], contact BIOS vendor for fixes 

I have not made any BIOS changes.

herbertwatson

Member

Registered: 2020-09-08

Posts: 4

Re: [SOLVED] Very odd problem after new install

Now that I look at ip a again it doesn't even list my wifi or ethernet card. I am very confused.

seth

Member

From: Won't reply 2 private help req

Registered: 2012-09-03

Posts: 77,733

Re: [SOLVED] Very odd problem after new install

Please don't bump. If nobody responded yet, simply edit and mend your post.

On topic: you probably ran a kernel update w/o having the /boot directory mounted and now run a kernel that doesn't match the installed one.
Post the outputs of

uname -a; pacman -Qs linux

---

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

herbertwatson

Member

Registered: 2020-09-08

Posts: 4

Re: [SOLVED] Very odd problem after new install

I used an install media to chroot into my system and then I updated using pacman and reinstalled the kernel. This fixed my issue.

ewaller

Administrator

From: Pasadena, CA

Registered: 2009-07-13

Posts: 20,701

Re: [SOLVED] Very odd problem after new install

The problem was likely the kernel being loaded by the boot loader was different than the installed kernel; the kernel that was running could not find its drivers.

You probably have not yet solved, the root problem.  At some time in the future, your kernel my update itself.  If the boot volume is not properly mounted on /boot, then your boot volume will not be updated with the new kernel.
Can you post your /etc/fstab file?

---

Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
The shortest way to ruin a country is to give power to demagogues.— Dionysius of Halicarnassus
---
How to Ask Questions the Smart Way