#update broke system

77 messages · Page 1 of 1 (latest)

dire arch
#

If you get into a revovery shell run

grub-mkconfig -o /boot/grub/grub.cfg
#

and also update your system again

dire arch
#

.s litany

patent compassBOT
# dire arch .s litany

Please follow the Standard Litany when asking a question:
What was your environment? What was your operating system, configuration?
What did you do? What did you run or test? Where?
What actually happened? What were the exact results, complete log contents, exact error messages?
What did you expect? What were you aiming to achieve? What result were you looking for?

Vague or superficial questions will yield vague or superficial answers. False information leads to false solutions.

Also see this similar guide on how to ask smart questions.

dire arch
#

.s q

patent compassBOT
# dire arch .s q

When requesting support, please include specific, detailed, and relevant information about your system and issue.

We need such information because we don't know what it's like inside your system, and it's unlikely that we know much about the issue you're facing. The more information you can provide, the better we can help you with your specific issue.

Some examples of frequently requested information include the steps you took before your issue occurred (such as system updates), the steps you took to resolve your issue and their results, and your environment (such as your display manager or desktop environment).

Vague or superficial questions lead to vague or superficial answers. False information leads to false solutions.

dire arch
#

Enter chroot then reinstall kernel and update GRUB

#

.aw chroot

patent compassBOT
dire arch
#

.aw grub

patent compassBOT
dire arch
#

Idk about the last part but glad it worked. Chroot always work

#

You can do that from chroot

#

You should remove the kernel then install it again

#

Be sure to chroot correctly

#

You have to mount your ESP/EFI partition and your root partition

#

That's why it fails

#

Idk. But be sure to properly chroot. Then get rid of all kernels but vanilla Linux. Then regenerate the mkinitcpio and update grub. Then try to boot. You can install Zen and LTS kernels later

#

I recommend having the LTS kernel just in case as fallback

#

Idk about gentoo stuff

#

I'm using knowledge found on the wiki and personal experience

#

Again idk. I'm an Arch user

#

But removing the broken kernel and leaving vanilla one should fix it

#

So you got rid of the broken kernel?

#

Try booting now

#

Remember to update grub

#

You have vanilla kernel so

#

Don't rush

#

Update GRUB then reboot to your system

#

.aw GRUB

patent compassBOT
dire arch
#

You can install LTS kernel as fall back

#

Try again

#

¯\_(ツ)_/¯

#

Reinstalling the Kernel and updating GRUB should fix it

#

That's I meant you to do too

#

... grub issue

patent compassBOT
dire arch
#

... grub-issue

patent compassBOT
dire arch
#

As reference

#

Your penguinOS just freaked out

#

Kernel panic = bsod

#

Chroot again

#

Reinstall grub then update it

#

If that doesn't work wait for someone else

#

You could also install the LTS kernel

#

Remember to install the kernel headers

#

You made a typo

#

You are supposed to mount your partitions on the live ISO, not inside chroot

#

You mounted your root then inside chroot you mounted your boot

#

You have to do it outside chroot

#

Even the wiki says that

#

Weird. I have chrooted a lot and it works. Even the wiki says that

#

I always chroot my EFI partition to /mnt/boot/efi

#

Then root one to /mnt

#

Then proceed to do the changes inside chroot after mounting /mnt

#

That's might be why it throws that warning

#

No need. Re use this one

#

Renaming exists

#

By... Renaming this?

silver cipherBOT
#

🎃✙ Leinnë✦🥀 💾 received a thank you cookie!

dire arch
#

Lol so you installed LTS kernel?

#

So you can boot again?

#

LTS is fine tbh

#

Though I run Zen Kernel.. but LTS is my Fail-Safe fallback Kernel

#

On your booted system try to reinstall the other kernels

#

I mean Zen and vanilla kernels

#

sudo pacman -Rs linux-zen linux && sudo pacman -S linux-zen linux linux-headers linux-zen-headers

#

That should do

#

Forgot sudo pacman -S linux-lts-headers

#

Then skip it

dire arch
#

Weird. But at least you can boot. Make another thread

dire arch
#

Try doing pacstrap and idk what kernel you’re using but

#

For example

#

pacstrap /mnt linux linux-firmware linux-headers

#

If that fails you can Hijack pacman in the mounted partition and downgrade your package my wgeting a prior version kernel