Kernel Update leads to xOrg error
Clash Royale CLAN TAG#URR8PPP
up vote
0
down vote
favorite
Basically every time I update to a new kernel using pacman -Syyu, the output of pacman -Q linux && uname -r does not correspond with each other. Example:
[alexander_schoch@Arch: ~]$ pacman -Q linux && uname -r
linux 4.15.7-1
4.15.6-1-ARCH
After a reboot, the system cannot start xOrg anymore, as it crashes with the error no screens fount [EE]. Every time this occurs, i have to boot into a live stick of arch, chroot into my system and run pacman -Sy linux which updates it to the newest verstion. What am I doing wrong?
EDIT 2:
[alexander_schoch@Arch: ~]$ cat /etc/fstab
# Static information about the filesystems.
# See fstab(5) for details.
# <file system> <dir> <type> <options> <dump> <pass>
arch-linux kernel
edited Mar 10 at 5:25
jasonwryan
46.7k14127175
asked Mar 6 at 20:38
Alexander Schoch
96
 |Â
show 5 more comments
up vote
0
down vote
favorite
Basically every time I update to a new kernel using pacman -Syyu, the output of pacman -Q linux && uname -r does not correspond with each other. Example:
[alexander_schoch@Arch: ~]$ pacman -Q linux && uname -r
linux 4.15.7-1
4.15.6-1-ARCH
After a reboot, the system cannot start xOrg anymore, as it crashes with the error no screens fount [EE]. Every time this occurs, i have to boot into a live stick of arch, chroot into my system and run pacman -Sy linux which updates it to the newest verstion. What am I doing wrong?
EDIT 2:
[alexander_schoch@Arch: ~]$ cat /etc/fstab
# Static information about the filesystems.
# See fstab(5) for details.
# <file system> <dir> <type> <options> <dump> <pass>
arch-linux kernel
edited Mar 10 at 5:25
jasonwryan
46.7k14127175
asked Mar 6 at 20:38
Alexander Schoch
96
That generally indicates/bootwas not mounted for the kernel upgrade.
– jasonwryan
Mar 6 at 20:40
@jasonwryan I manually mounted the partition usingmount /dev/sda5 /bootand runpacman -Syyu linuxafterwards. The problem still occurs.
– Alexander Schoch
Mar 6 at 20:44
Yes, but are you sure it is mounted when the kernel is first upgraded? If it isn't, the second-Syyu linuxwill not fix it.
– jasonwryan
Mar 6 at 21:01
What do you mean by that? Aftermount /dev/sda5 /boot, the partition should definitely be mounted, but how can I go for sure?
– Alexander Schoch
Mar 6 at 21:03
Because the update has already failed and the modules replaced; it won't work again unless you chroot in or update from a live media with the --root option.
– jasonwryan
Mar 6 at 21:05
 |Â
show 5 more comments
up vote
0
down vote
favorite
up vote
0
down vote
favorite
Basically every time I update to a new kernel using pacman -Syyu, the output of pacman -Q linux && uname -r does not correspond with each other. Example:
[alexander_schoch@Arch: ~]$ pacman -Q linux && uname -r
linux 4.15.7-1
4.15.6-1-ARCH
After a reboot, the system cannot start xOrg anymore, as it crashes with the error no screens fount [EE]. Every time this occurs, i have to boot into a live stick of arch, chroot into my system and run pacman -Sy linux which updates it to the newest verstion. What am I doing wrong?
EDIT 2:
[alexander_schoch@Arch: ~]$ cat /etc/fstab
# Static information about the filesystems.
# See fstab(5) for details.
# <file system> <dir> <type> <options> <dump> <pass>
arch-linux kernel
edited Mar 10 at 5:25
jasonwryan
46.7k14127175
asked Mar 6 at 20:38
Alexander Schoch
96
Basically every time I update to a new kernel using pacman -Syyu, the output of pacman -Q linux && uname -r does not correspond with each other. Example:
[alexander_schoch@Arch: ~]$ pacman -Q linux && uname -r
linux 4.15.7-1
4.15.6-1-ARCH
After a reboot, the system cannot start xOrg anymore, as it crashes with the error no screens fount [EE]. Every time this occurs, i have to boot into a live stick of arch, chroot into my system and run pacman -Sy linux which updates it to the newest verstion. What am I doing wrong?
EDIT 2:
[alexander_schoch@Arch: ~]$ cat /etc/fstab
# Static information about the filesystems.
# See fstab(5) for details.
# <file system> <dir> <type> <options> <dump> <pass>
arch-linux kernel
edited Mar 10 at 5:25
jasonwryan
46.7k14127175
asked Mar 6 at 20:38
Alexander Schoch
96
edited Mar 10 at 5:25
jasonwryan
46.7k14127175
edited Mar 10 at 5:25
jasonwryan
46.7k14127175
edited Mar 10 at 5:25
jasonwryan
46.7k14127175
46.7k14127175
asked Mar 6 at 20:38
Alexander Schoch
96
asked Mar 6 at 20:38
Alexander Schoch
96
asked Mar 6 at 20:38
Alexander Schoch
96
96
That generally indicates/bootwas not mounted for the kernel upgrade.
– jasonwryan
Mar 6 at 20:40
@jasonwryan I manually mounted the partition usingmount /dev/sda5 /bootand runpacman -Syyu linuxafterwards. The problem still occurs.
– Alexander Schoch
Mar 6 at 20:44
Yes, but are you sure it is mounted when the kernel is first upgraded? If it isn't, the second-Syyu linuxwill not fix it.
– jasonwryan
Mar 6 at 21:01
What do you mean by that? Aftermount /dev/sda5 /boot, the partition should definitely be mounted, but how can I go for sure?
– Alexander Schoch
Mar 6 at 21:03
Because the update has already failed and the modules replaced; it won't work again unless you chroot in or update from a live media with the --root option.
– jasonwryan
Mar 6 at 21:05
 |Â
show 5 more comments
That generally indicates/bootwas not mounted for the kernel upgrade.
– jasonwryan
Mar 6 at 20:40
@jasonwryan I manually mounted the partition usingmount /dev/sda5 /bootand runpacman -Syyu linuxafterwards. The problem still occurs.
– Alexander Schoch
Mar 6 at 20:44
Yes, but are you sure it is mounted when the kernel is first upgraded? If it isn't, the second-Syyu linuxwill not fix it.
– jasonwryan
Mar 6 at 21:01
What do you mean by that? Aftermount /dev/sda5 /boot, the partition should definitely be mounted, but how can I go for sure?
– Alexander Schoch
Mar 6 at 21:03
Because the update has already failed and the modules replaced; it won't work again unless you chroot in or update from a live media with the --root option.
– jasonwryan
Mar 6 at 21:05
That generally indicates
/boot was not mounted for the kernel upgrade.– jasonwryan
Mar 6 at 20:40
That generally indicates
/boot was not mounted for the kernel upgrade.– jasonwryan
Mar 6 at 20:40
@jasonwryan I manually mounted the partition using
mount /dev/sda5 /boot and run pacman -Syyu linux afterwards. The problem still occurs.– Alexander Schoch
Mar 6 at 20:44
@jasonwryan I manually mounted the partition using
mount /dev/sda5 /boot and run pacman -Syyu linux afterwards. The problem still occurs.– Alexander Schoch
Mar 6 at 20:44
Yes, but are you sure it is mounted when the kernel is first upgraded? If it isn't, the second
-Syyu linux will not fix it.– jasonwryan
Mar 6 at 21:01
Yes, but are you sure it is mounted when the kernel is first upgraded? If it isn't, the second
-Syyu linux will not fix it.– jasonwryan
Mar 6 at 21:01
What do you mean by that? After
mount /dev/sda5 /boot, the partition should definitely be mounted, but how can I go for sure?– Alexander Schoch
Mar 6 at 21:03
What do you mean by that? After
mount /dev/sda5 /boot, the partition should definitely be mounted, but how can I go for sure?– Alexander Schoch
Mar 6 at 21:03
Because the update has already failed and the modules replaced; it won't work again unless you chroot in or update from a live media with the --root option.
– jasonwryan
Mar 6 at 21:05
Because the update has already failed and the modules replaced; it won't work again unless you chroot in or update from a live media with the --root option.
– jasonwryan
Mar 6 at 21:05
 |Â
show 5 more comments
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
Â
draft saved
draft discarded
Â
draft saved
draft discarded
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f428606%2fkernel-update-leads-to-xorg-error%23new-answer', 'question_page');
);
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
That generally indicates
/bootwas not mounted for the kernel upgrade.– jasonwryan
Mar 6 at 20:40
@jasonwryan I manually mounted the partition using
mount /dev/sda5 /bootand runpacman -Syyu linuxafterwards. The problem still occurs.– Alexander Schoch
Mar 6 at 20:44
Yes, but are you sure it is mounted when the kernel is first upgraded? If it isn't, the second
-Syyu linuxwill not fix it.– jasonwryan
Mar 6 at 21:01
What do you mean by that? After
mount /dev/sda5 /boot, the partition should definitely be mounted, but how can I go for sure?– Alexander Schoch
Mar 6 at 21:03
Because the update has already failed and the modules replaced; it won't work again unless you chroot in or update from a live media with the --root option.
– jasonwryan
Mar 6 at 21:05