You are not logged in.
I am hoping I am just missing something simple with this.
After upgrading my laptop today from 3.15 to 3.16 my network adapter and Xorg stopped working.
Network adapter is giving me the error:
timed out wating for device sys-subsytem-net-devices-ens5.sevice
And Xorg is giving me:
(EE) No devices detected
(EE) no screens found
Well I have been googling around and checking out the Arch forums and came across a thread with the same Xorg error. When I was typing my response to it I realized:
uname -a
Linux MacBook 3.15.8-1-ARCH #1 SMP PREEMPT Fri Aug 1 08:51:42 CEST 2014 x84_64 GNU/Linux
What did I miss that the new kernel is not loading?
I am using Grub2 as a boot loader.
Last edited by kramlegan (2014-08-15 14:42:00)
Offline
I assume you rebooted.
Was your boot partition mounted on the /boot mount point when you upgraded the kernel? If not, the new kernel was written to /boot by pacman, but the boot partition would remain unchanged. Note that if it was not mounted, you should be able to look in /boot and see the new kernel. Then, if you mount the boot partition and you look in /boot, you will see the contents of your (unmodified) boot partition, and your new kernel (in the /boot directory) will be hidden and that branch replaced.
If you are not sure, post the output of mount and the contents of your /etc/fstab file.
Last edited by ewaller (2014-08-15 06:15:09)
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
Offline
Thank you for your reply.
/boot was not mounted.
I cannot easily post the output of mount and /etc/fstab since networking is now not working on this box and it is quite a bit of information to type out. Ugh.
in fstab (summarized) I have
/
/home
swap
and mount has no boot or /boot entry ($mount |grep boot)
So how do I fix this issue? Will copying what I have in "unmounted" /boot to partition /boot simply fix this?
(I am assuming not running the updated kernel is why networking and Xorg is not working now correct?)
Offline
The easiest way is to mount the boot partition and then re-install linux using sudo pacman -S linux
It should install from the cache -- you should not need a network connection.
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
Offline
I am unable to mount the boot partition now.
I get the error
mount: unknown filesystem type 'vfat'
It looks like it has to do with running the incorrect kernel.
https://bbs.archlinux.org/viewtopic.php?id=28437
the key is that the kernel is updated ( e.g. from 2.23 -> 2.24 ).
the vfat kernel module reside in difference directory (/lib/modules/XXXx-2.24/)after update.
but the kernel version in /proc is the old one , until you reboot.
if you don't reboot, when load the vfat module, the insmod will search the /lib/modules/`uname -r` , which can found nothing to load. well, what you get is nothing but some string like
# modprobe vfat
Any other suggestions on how to fix this?
Offline
If still booted, you can downgrade to the previous kernel
# pacman -U /var/cache/pacman/pkg/linux...
and mount /boot then before upgrading again.
Offline
This worked!
After downgrating
mounting /boot
upgrading again
Thank you everyone! I am back up and running.
Offline
Strike0's suggest might well work. It will restore the correct modules for the kernel that is running.
A more direct solution would be to use a chroot enviorment.
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
Offline
kramlegan: You better check before next update where your /boot entry in fstab went on holiday to. In post #3 you don't list it at least.
Offline
Thank you for the reminder. I added /boot back to fstab.....rebooted and it is there now. Should be good to go. Thanks again.
Offline
You're welcome. While this is a fresh thread, let me add: I don't know why you removed the /boot mount in the first place, but if you prefer it like that there are a number of ways. For example you could specify a bash alias which takes care of mounting, updating and unmounting. Or: mount /boot just read-only. This way updates including your bootloader/kernel/mkinitcpio will fail initially, but you see it error out and can remount "rw" to repeat.
Offline
To be honest I did not add it to fstab when I did the install....I questioned if it needed to be there and forgot to research/go back and add it. Looks like I answered my own question.
Offline
Also, in case you didn't do it yet, you may want to remove remaining files on the _unmounted_ /boot directory, to avoid future confusion.
Regards
Last edited by rebootl (2014-08-16 14:55:51)
Personal website: reboot.li
GitHub: github.com/rebootl
Offline