You are not logged in.
Pages: 1
Hello friends,
I ran Arch for a a couple years now as my main OS and I never had anything break after updates until now.
I ran pacman -Syu then shutdown. The next morning I had two new issues I can't seem to figure out how to fix:
1. No wired connection working. ip link only shows "lo" as an interface. All other interfaces are gone some how.
2. mouse and keyboard do not work after starting X
Now I tried doing some research on google about why I only have "lo" showing as an interface but I don't seem to get any where.
I appreciate any help.
Thank you
Edit: I forgot to mention I get this on startup:
"A start job is running for sys-subsystem-net-devices-eth0.device (0/1min30secs)"
It counts down to 130 then continues the boot.
Last edited by letmeinyourbasement (2017-05-25 18:47:15)
Offline
What is the output of ip link ?
I'll wager it does not include eth0 as the name of one of your interfaces.
edit: Read Eric, read
What are the output of uname -a and of pacman -Q linux ?
I'll wager the versions do not match
BTW, Welcome to Arch Linux.
Last edited by ewaller (2017-05-25 18:53:45)
Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
Sometimes it is the people no one can imagine anything of who do the things no one can imagine. -- Alan Turing
---
How to Ask Questions the Smart Way
Online
What is the output of ip link ?
I'll wager it does not include eth0 as the name of one of your interfaces.BTW, Welcome to Arch Linux.
Thank you for your reply and your welcome!
Yes you are right it does not include eth0:
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
Edit: Looks like you are right again. They do not match...
Linux xxlas 4.10.13-1-ARCH #1 SMP PREEMPT Thu Apr 27 12:15:09 CEST 2017 x86_64 GNU/Linux
linux 4.11.2-1
Last edited by letmeinyourbasement (2017-05-25 18:57:58)
Offline
Did you catch my edits? I think we were posting at the same time. I am almost certain you are picking up a stale (old) kernel in your boot loader and it cannot find it modules as they have been updated for a newer kernel. Check the versions per my edited #3
Last edited by ewaller (2017-05-25 18:57:02)
Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
Sometimes it is the people no one can imagine anything of who do the things no one can imagine. -- Alan Turing
---
How to Ask Questions the Smart Way
Online
Alright so like I said earlier, they are not the same versions.
After some googling it may be an issue with my /boot?
I ran lsblk and I don't see /boot listed under MOUNTPOINT in any of the devs. Could this possibly be the issue?
Edit: After digging around some more there seems to be some issue with my fstab mounting the /boot
I find this in /etc/fstab
/dev/sdd1 vfat rw,relatime,fmask=0022,dmask=022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro 0 2
/dev/mapper/root / ext4 defaults 0 1
/dev/mapper/tmp /tmp tmpfs defaults 0 0
And this is my lsblk:
sdc disk
sdc1 part
sdc2 part
lvm-tmp lvm
tmp crypt /tmp
lvm-lvroot lvm
root crypt /
Last edited by letmeinyourbasement (2017-05-25 19:37:57)
Offline
What has probably has happened is the the boot partition was not mounted on the /boot mountpoint when the kernel was updated. Mount the boot partition on /boot, then reinstall the kernel using pacman -S linux
Then reboot and see if the problem goes away.
If it does, now comes the cleanup. First, ensure that the boot partition is unmounted (it should be after the reboot as we have not fixed that yet). Look in /boot. With nothing mounted there, it should be empty. Make it so.
Then, fix your /etc/fstab to mount the boot partition on start up. reboot and prove to yourself your fixes to /etc/fstab do work. Next time the kernel updates, the boot partition will be installed where it belongs -- on the partition, not inside the mount point.
Last edited by ewaller (2017-05-25 19:58:33)
Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
Sometimes it is the people no one can imagine anything of who do the things no one can imagine. -- Alan Turing
---
How to Ask Questions the Smart Way
Online
Alright so I'm not able to mount my boot partition since its in vfat (I don't know why I choose this extention on install...) and the system says its an unknown filesystem.
So what I'll do is chroot into the system with my live USB and reinstall the kernal and fix the booting.
I will update when complete.
Offline
Alright so I'm not able to mount my boot partition since its in vfat (I don't know why I choose this extention on install...)
How did you install Arch?
Offline
letmeinyourbasement wrote:Alright so I'm not able to mount my boot partition since its in vfat (I don't know why I choose this extention on install...)
How did you install Arch?
With a live USB.
Offline
jasonwryan wrote:letmeinyourbasement wrote:Alright so I'm not able to mount my boot partition since its in vfat (I don't know why I choose this extention on install...)
How did you install Arch?
With a live USB.
Please paste your full pacman log.
Offline
Pages: 1