#[SOLVED] had to boot into a fallback kernel
115 messages · Page 1 of 1 (latest)
the only thing im truly absolutely sure about is the fact this computer is nvidia-free
did you uninstall anything related to linux-firmware?
what are the exact commands you typed?
sudo pacman -Rns gnome-shell vulkan-radeon vulkan-nouveau nvidia libnautilus-extension nautilus
all i remember
i know i put in a few more but i forgot the names
i'll try to find it in my history
sudo pacman -Rns xorg-server-xvfb
this one too
gnome-shell is a dependency of gdm
that might be a problem
i uninstalled gdm
and what greeter did you install?
"tuigreet" is the only portion of it i remember
sudo pacman -Rns nautilus libnautilus-extension xdg-desktop-portal-gnome gnome-session gnome-shell
what do you see on the screen? completely black? blinking cursor?
blinking cursor after the usual
/dev/nvme----: clean
thing
do you have loglevel set in your kernel parameters?
i dont think so
does systemd print the green [ OK ] stuff on bootup?
theres usually no logs unless i had recently gone into some sort of recovery, emergency shell utility
no, it does not
then you might wanna enable the logs
it usually does this and then sends me into my greeter
also you tried ctrl+alt+f2, did you also try f3 f4 etc?
okay, first add loglevel=4 to your parameters
then boot into the arch iso and we'll be extracting the journal to see what's wrong
would that be in the options menu in grub
cant, left my archiso usb at home
im booted into the fallback kernel rn
thats how im talking here
yeah
then do this
journalctl -b -2 | curl -F 'file=@-' 0x0.st
and tuigreet works normally on the fallback kernel?
yep
okay so let me just quickly say this
the boot before rn was also fallback
the boot before that other fallback boot was just regular
okay then do this
yes
[hour@hourfrozen ~]$ mkinitcpio -P
==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'default'
==> Using default configuration file: '/etc/mkinitcpio.conf'
-> -k /boot/vmlinuz-linux -g /boot/initramfs-linux.img
==> ERROR: Invalid option -g -- '/boot/initramfs-linux.img' must be writable
==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'fallback'
==> Using default configuration file: '/etc/mkinitcpio.conf'
-> -k /boot/vmlinuz-linux -g /boot/initramfs-linux-fallback.img -S autodetect
==> ERROR: Invalid option -g -- '/boot/initramfs-linux-fallback.img' must be writable
with sudo
can you also do
journalctl -xe -b -2 | curl -F 'file=@-' 0x0.st
did it finish with no errors?
a few possibly missing firmware warns but overall it was successful
okay so the journal literally says nothing
which intel driver did you install?
is your system up to date?
mesa drivers, vulkan-intel and a few others that were too weird for me to remember
this might be a bit problematic
so i did a full upgrade and it exited with "One or more errors."
show
cant anymore, history is gone
then try updating again
how many packages are there to update/
i'm asking about the packages
oh
249
i dont have enough free space
when i made the partition for linux i made it only half of the amount of storage i actually had
how big is it?
how big is your partition?
hold on lemme check
do you take care of your cache?
45GiB
what do you mean by this
no
sudo pacman -Scc
should i run this now
yes
good
why? internet?
yep
good morning, gonna try full upgrade again
error: failed to commit transaction (conflicting files)
linux-firmware-nvidia: /usr/lib/firmware/nvidia/ad103 exists in filesystem
linux-firmware-nvidia: /usr/lib/firmware/nvidia/ad104 exists in filesystem
linux-firmware-nvidia: /usr/lib/firmware/nvidia/ad106 exists in filesystem
linux-firmware-nvidia: /usr/lib/firmware/nvidia/ad107 exists in filesystem
Errors occurred, no packages were upgraded.
same thing
oh damn
it seems like you haven't updated in at least two months
that would be correct, lost the power cable
i dont have nvidia tho so i just got confused when i first saw that