Hey,
I recently did a BIOS Update and my Windows+Linux were connected. For some reason Windows overwrite or just did write the Bootmanager to my EFI where my Linux usually was listed.
My Windows is on a SSD and I fixed that part. Created a new EFI partition and so on.
The Linux part is on a NVME. There I have a partition for my EFI part and a second partition is my root. I deleted the Bootmanager folder of Windows on that first partition. After that I did grub-install and grub-mkconfig. So mounted everything and executed that without any errors. I checked with efibootmgr -v and my bootloader id was present. But if I boot my nvme it always end in the grub shell. My linux does not appear. Did I miss something ?
#[Solved] GRUB does not list Linux anymore
mighty pike
jagged osprey
chroot, mount the efi, and reinstall the kernel, kernel heders, as well as any u-code package you have
@mighty pike should probably tag you as it's an hour later
oh and then after that re-run the grub-mkconfig
sorry, I'm kinda amped up from a real life situation, adnrenaline and near panic attack.
mighty pike
I did get a bit further. He see my bootloader id now. But when I try to it, it can't mount my boot anymore. Should I still try the way you described ?
jagged osprey
yes, iso, chroot into root, with efi mounted, reinstall the kernel and kernel headers, and any ucode you have, and then redo the grub-mkconfig.
Also whilst there run lsblk -f and make sure that your /etc/fstab has that UUID for the /boot
mighty pike
sorry, I'm kinda amped up from a real life situation, adnrenaline and near panic...
Hope you are ok. More important is your health then my failing boot. ^^
jagged osprey
just more liable to miss out obvious things, like the fstab, for example
mighty pike
mount /dev/nvmep1 /mnt/boot
That is correct or ? I did this all time but now where you say EFI mounted I'm not sure if that was my fail.
jagged osprey
if the efi is p1, then yeah, did you do that before or after chrooting?
mighty pike
First I mount my root and then the boot
jagged osprey
share lsblk -f
mighty pike
share `lsblk -f`
Is it ok if I share it as picture ?
jagged osprey
if you don't have internet for some reason I guess, but then I don't see how you'd do pacman commands...
why not just do it how I said?
.s ix
mighty pike
Is it possible in chroot to post it in discord ?
jagged osprey
share link
mighty pike
Hm, he did not provide me link. Just said no results to fetch.
urban flax
try running grub-mkconfig -o /boot/grub/grub.cfg in chroot.
jagged osprey
try running grub-mkconfig -o /boot/grub/grub.cfg in chroot.
the problem appears now to be the fstab
mighty pike
Now I have wait
urban flax
the problem appears now to be the fstab
oh
jagged osprey
Hm, he did not provide me link. Just said no results to fetch.
should be like that
jagged osprey
it's not showing the uuid, which is very strange
jagged osprey
the issue isn't grub
the issue is you remade a partition
so the partition has a new UUID, as the UUID will change
but your fstab has not been updated with the new UUID
mighty pike
Ahh
jagged osprey
if grub is an issue you don't need to reinstall grub, just follow the kernel installation grub-mkconfig I said above
mighty pike
Yeah, I did it now, still no UUID there.
I did run the ix.io again. It's the same link.
mighty pike
For the disk self or for the Partition ? Otherwise there is no UUID that he can find
Is for the /dev/nvme0n1
http://ix.io/4Ino that's it if I do it on first Partition where my boot is
Omg got you wrong sry
That's what you wanted see, sry my fail.
Could it be he generate the uuid for my root but not the boot ?
It looks so different of the size
mighty pike
I checked out the grub.cfg. There is a menu entry for the root. With the 'Arch Linux, with Linux linux (Fallback initramfs)' it's setting the first Partition (Boot Partition) as root.
I think there should be another entry for the boot or not ?
mighty pike
When I go with the submenu with fallback. I can see that. Still sayin can't boot and emergency mode.
jagged osprey
her, I see UUID's!
awesome
show me cat /etc/fstab
I bet boot does not show as 43AE-C5D4
whilst you're there reinstall your kernel and re-do the grub-mkconfig command
(though mount the vfat partition first obviously)
(also spoken to the vet on the phone, they think my dog is absolutely fine, so just gotta calm myself down)
mighty pike
Reminder: That is not chroot. Above the last link was made while chroot.
There he listed it too
mighty pike
(also spoken to the vet on the phone, they think my dog is absolutely fine, so j...
(Nice to hear, maybe I got it wrong. I thought it was the first time you had something.)
jagged osprey
regardless, did you compare the fstab to the above uuid?
mighty pike
(also spoken to the vet on the phone, they think my dog is absolutely fine, so j...
How do you mean that with the vfat first ? Because without mount /mnt first I can't mount it before that
jagged osprey
do cat /etc/fstab and tell me the UUID of your /boot
mighty pike
jagged osprey
that's interesting, it's the same as what you showed above
is the image above old?
mighty pike
is the image above old?
That was some minutes ago. When I did boot with fallback initframs
I did reinstall linux linux-headers amd-ucode. That's correct or ?
jagged osprey
yeah, and then you redid the grub-mkconfig right?
mighty pike
Now I'm in chroot again
jagged osprey
I assume your CPU is amd
mighty pike
Yeah Ryzen
mighty pike
Like above that mentioned.
After that I did again cat fstab
It's the same link.
So I redid right now again
mighty pike
Interesting to is, can't enter emergency mode with "normal" arch. So my keyboard is not working then. Only if I start with the option above
efibootmgr -v you mean ?
jagged osprey
don't think you'll need the v
mighty pike
jagged osprey
BootCurrent: 000A
Timeout: 1 seconds
BootOrder: 0009,0001,0000,000A
Boot0000* arch_grub HD(1,GPT,32bab553-e9d3-ab45-939a-6741991a734c,0x800,0x190000)/File(\EFI\ARCH_GRUB\GRUBX64.EFI)
Boot0001* Windows Boot Manager HD(3,GPT,c2825457-cf15-4422-98c3-c8cd77404634,0x3a101800,0x12c000)/File(\EFI\MICROSOFT\BOOT\BOOTMGFW.EFI)57494e444f5753000100000088000000780000004200430044004f0042004a004500430054003d007b00390064006500610038003600320063002d0035006300640064002d0034006500370030002d0061006300630031002d006600330032006200330034003400640034003700390035007d00000000000100000010000000040000007fff0400
Boot0009* UEFI OS HD(1,GPT,32bab553-e9d3-ab45-939a-6741991a734c,0x800,0x190000)/File(\EFI\BOOT\BOOTX64.EFI)0000424f
Boot000A* UEFI: Intenso, Partition 1 PciRoot(0x0)/Pci(0x1,0x2)/Pci(0x0,0x0)/Pci(0x8,0x0)/Pci(0x0,0x1)/USB(1,0)/HD(1,GPT,96ff0129-376f-4fb5-aa18-dfa4116051ec,0x800,0x1d7d7d0)0000424f
that's interesting
Boot0009* UEFI OS HD(1,GPT,32bab553-e9d3-ab45-939a-6741991a734c,0x800,0x190000)/File(\EFI\BOOT\BOOTX64.EFI)0000424f is that perhaps your old one?
mighty pike
Yes
mighty pike
Hm sure, I press F11 to choose. Then there is that entry you mentioned and my arch_grub. I press arch_grub.
So when I start my PC and choose what to boot
Because if I choose that what you mentioned he is going into grub shell
Does it interfere with the other one ?
jagged osprey
looking at it again I think it's actually a sort of, duplicate entry
try sudo efibootmgr -n 0000 just to be sure, and see if that works, if it doesn't, test something else for me, by editing the fstab to not mount /boot (just comment it out with # at the start) and then boot, I cannot for the life of me work out why it would not show all the options, or why it has an issue with your vfat partition
mighty pike
So 0000 is the arch_grub ? That's the boot up where I can see my Arch listed ?
jagged osprey
next step I would say is remake the fat 32 filesystem on your efi, mount it, chroot, reinstall grub, reinstall kernel and ucode, re-do the grub-mkconfig again :/
jagged osprey
So 0000 is the arch_grub ? That's the boot up where I can see my Arch listed ?
.s tias
cosmic needleBOT
mighty pike
Not working 😦
mighty pike
next step I would say is remake the fat 32 filesystem on your efi, mount it, chr...
By that you mean just to format it again ?
jagged osprey
By that you mean just to format it again ?
essentially
jagged osprey
what commands have you run?
mighty pike
Before mounting
mkfs.fat -F 32 /dev/nvme0n1p1
mount /dev/nvme0n1p2 /mnt
mount /dev/nvme0n1p1 /mnt/boot
sudo arch-chroot /mnt
sudo pacman -S linux linux-headers amd-ucode
grub-install --target=x86_64-efi --efi-directory=/boot/EFI --bootloader-id=arch_grub --receck
(EFI folder was not present, so I created it at boot and rerun the command)
grub-mkconfig -o /boot/grub/grub.cfg
exit
umount -R /mnt
reboot
jagged osprey
grub-install --target=x86_64-efi --efi-directory=/boot/EFI --bootloader-id=arch_grub --recheck
That failed.
you should mount it to /boot/efi if that's what you want to do
mighty pike
Ahh
jagged osprey
oh wait
I see
you made /boot/efi
that should be fine actually I think
I do not understand, at all, why that has not worked.
mighty pike
So i can leave EFI folder and just write '/boot' ?
Fstab seems to be fine too
Looks like before everything
I try again to start it
jagged osprey
hmmm
go into /boot, delete /boot/EFI, and then do:
grub-install --target=x86_64-efi --efi-directory=/boot --bootloader-id=grub_arch --recheck
just to be sure that that isn't related to the problem, and then reinstall the kernels again and redo the mkconfig
mighty pike
My fail, I said I created it but did not mount on /boot/EFI again. But I still did your way described way. Sadly now I'm having a different problem
jagged osprey
what's the new issue?
mighty pike
jagged osprey
yeah that's expected
the uuid should change after mkfs
so just change it to the new one
mighty pike
Through chroot or emergency mode ?
jagged osprey
mount /mnt and /boot or /boot/efi and then before chrooting, try lsblk -f
mighty pike
Ach ok
jagged osprey
chroot will be best way
don't know what was going wrong before but hopefully this is the end of it
if changing the UUID doesn't work temporarily comment out /boot and we'll try from live
mighty pike
After that I need to bake you a cake
jagged osprey
I'll settle for a body guard for the dog during walks.
let me know if you can't get the uuid either inside of or outside of chroot
mighty pike
Then normal exit ?
jagged osprey
yes, and then cat it to make sure you did it right
best to have both the uuid and the fstab uuid entry on the screen for comparison
mighty pike
Uff, did it. Now if I try to boot again failed to boot ... and 100% sure fstab is correct
So failed to mount boot again
jagged osprey
it's failing to mount /boot?
mighty pike
Yes, instantly
jagged osprey
did you remake the partition at the start?
mighty pike
No only formatting
jagged osprey
so it's not like you changed it to be linux file system
jagged osprey
gonna repeat myself here, you didn't use cfdisk or fdisk or anything similar?
mighty pike
Inside chroot btw I don't see the UUID
mighty pike
gonna repeat myself here, you didn't use cfdisk or fdisk or anything similar?
No
I did not touch the Partition
Only formatted it.
jagged osprey
hmmm
mighty pike
That was before chroot
That was the new ID and I just enter it.
Seems for me to be correct
jagged osprey
http://ix.io4InQ
yeah even if I correct the address this is still wrong
can you recheck the link?
jagged osprey
I also do wonder what sdb1 is
jagged osprey
okay so
we're gonna comment out the /boot line with #
then we're gonna reboot
and then when it loads into the live system we're going to directly copy and paste the uuid
because something is amiss and I cannot see what
mighty pike
Sry but where is # on the keyboard en ? I have a ger and can't find in Google pictures of layout
jagged osprey
just to the left of the enter button for me
alternaively, try changing the 2 to a 0 might work?
jagged osprey
Sry but where is # on the keyboard en ? I have a ger and can't find in Google pi...
just under ]
just to the right of '
just above shift
just to the left of enter
jagged osprey
it's the same on my keyboard, so not sure what's up
the very worst comes to the very worst:
cp /etc/fstab /etc/fstab2
then delete the entry from /etc/fstab
save, reboot
mighty pike
Like that yeah ?
jagged osprey
cool
mighty pike
Yeah just copied it and parsed
jagged osprey
wait, how?
mighty pike
Vim
jagged osprey
did you manage to boot into your system live?
I don't understand where you copied it from?
jagged osprey
yeah but how did you access discord from chroot?
jagged osprey
ohhhhh
yeah
okay
lol
stupid cookies
now you can hopefully boot up correctly
mighty pike
jagged osprey
though don't update your kernel or anything without /boot mounted
mighty pike
That's how my fstab look now
jagged osprey
yeah, good
mighty pike
Ok I will just exit and reboot
jagged osprey
this is, not a sustainable option for keeping your computer working to be clear, just a temporary setup
in fact, if this doesn't work, why am I making it difficult
iso, mount /mnt mount /mnt/boot, genfstab
maybe mount your windows partition somewhere as well
like mkdir /mnt/mnt/windows, mount ntfs /dev/<windows> /mnt/mnt/windows
mighty pike
I'm trying booting it, but it will timeout again I think.
jagged osprey
if it does it'll likely show a different issue
mighty pike
Or do nothing like it seems
jagged osprey
when you say nothing, what is it showing you?
jagged osprey
Hey,
I recently did a BIOS Update and my Windows+Linux were connected. For some...
I don't understand how that would have an effect
it feels like there's information missing
shall I see if someone more intelligent than me is around lol
mighty pike
I'm not sure either. I try to explain why I did the BIOS update.
I bought a new GPU (7700XT). Then I had some issues because it was laggy while gaming. I did a BIOS update. Before that I deinstalled my Nvidia driver from Linux and windows. After Windows somehow wrote his Boot manager to the Linux Boot Partition.
jagged osprey
@civic sand can't boot with /boot active in the fstab (the uuid and everything else looks right), when we comment out /boot, we get this. This all started with a bios update apparently. But I don't know how that would effect these things.
ohhh
you don't have GPU drivers installed?
jagged osprey
chroot with /boot mounted, and then install the nvidia drivers
mighty pike
But I have now the AMD RX 7700XT there. Still I should install it ?
jagged osprey
oh wait, amd?
mighty pike
Yeah that's my new card
jagged osprey
okay, yeah, install the drivers for that card
mighty pike
That's why I removed Nvidia before using that
mighty pike
Mesa is the correct driver or not ?
mighty pike
Hm I did install mesa or it is installed.
jagged osprey
but I'm not really an amd person
mighty pike
I try the propertery
jagged osprey
yeah you do want mesa installed
but not just mesa?
xf86-video-amdgpu - did you install that?
mighty pike
I did just install mesa. I thought that was enough
Wait I look
Nope...
Installed it now
Should I change the fstab now too ?
jagged osprey
https://wiki.archlinux.org/title/AMDGPU_PRO
that's the proprietary one if you want it instead, but, you can try that later
you have /boot mounted to right?
mighty pike
Yes
jagged osprey
yeah can try edited the fstab
did it trigger a mkinitcpio out of interest?
if not, reinstall kernel again
mighty pike
No it didn't
jagged osprey
have you got linux-firmware installed?
jagged osprey
Make sure you do not have nomodeset or vga= as a kernel parameter, since amdgpu requires KMS.
Check that you have not disabled amdgpu by using any kernel module blacklisting.
mighty pike
Linux Firmware is installed already
jagged osprey
might be worth doing an -Syu whilst you're there as well
mighty pike
Did I get it correct that I need specify amdgpu in modules mkinitcpio ?
In conf file
So, it should now be everything be ready.
Do I need to do a grub-mkconfig again ?
Do you have idea what that's mean ? Unknown Filesystem type vfat ?
jagged osprey
it seems to say on google it's likely a kernel version mis match, but, you reinstalled grub, so that makes 0 sense to me
mighty pike
I have no idea too anymore. I did downgrade my kernel from 6.5.5 to 6.5.3. Now it's stay endless in that screen. But not even throw any error something else
No timeout or so.
jagged osprey
lol
mighty pike
Maybe you know that. When I start the Linux initframs it says uname 6.5.3
Even before I downgradr
But that should be normal or not ?
jagged osprey
if uname says that, make sure that pacman -Qi linux is the same version, if it's not, install that version
jagged osprey
that's the iso lol
mighty pike
Hm, maybe I get something wrong. What you mean with iso ? Mean the live USB ?
jagged osprey
yeah we don't want the usb, we want the actual system itself
mighty pike
That's not working when I'm as chroot in ?
Ahh, now I get I think
That's what I use
Can't use keyboard by the normal
But I think I did it worse with the downgrade.
I upgrad again with chroot
No connection to create link
But like I said it's the fallback initframs. If I use the 'Arch Linux' normal one, my keyboard is not working. There it shows me the emergency mode too but can't enter something
jagged osprey
can you chroot in and install 6.5.3? or have you already done that?
mighty pike
So I did it in that mode where I'm currently in. Should I try it again but now in chroot ?
jagged osprey
yeah try it in chroot
mighty pike
Should I just downgrade like I did before ?
mighty pike
Then normally exit correct ?
jagged osprey
you had boot mounted right?
mighty pike
Yes
jagged osprey
yeah try unmounting and rebooting
mighty pike
Now it stays again in a loop. But first time the display is black for a second and then he seems to start again showing.
jagged osprey
can you access TTY?
mighty pike
Omg forgot about that completely... yeah I can
jagged osprey
don't need to upload it
lsblk -f will tell you what is and isnt mounted
just a are both mounted or not
jagged osprey
I'd try an -Syu now I think
jagged osprey
presumably it triggered a mkinitcpio?
mighty pike
Yes it installed 6.5.5 Linux again
jagged osprey
Could be a coincidence, and that the kernel has a bug?
mighty pike
Yeah I tried to Google it now too. Seems like it does not matter what we do. Should I maybe just for the purpose try the 6.4 kernel ?
jagged osprey
I can't see that doing anything but sure?
@pastel sage in case you're about, know much about needing to downgrade the kernel to get it to work because the uname -a and pacman -Qi versions are different?
mighty pike
Or should I try the linux-lts ?
wraith jay
you need to sort out the mismatch between your pac-man hooks and how you generate your boot environment
going forward i started forcing ALL drivers needed to get me to default target
jagged osprey
wait...could not having nvidia drivers and having a hook for nvidia be causing this?
in ls /etc/pacman.d/hooks/is there an nvidia hook?
wraith jay
it’s possible, i’ve had pac-man hooks fail silently on kernel upgrade but still complete the system upgrade despite no working boot environment
jagged osprey
if that's the issue I'll laugh my ass off
wraith jay
and by fail silently i mean allow the upgrade to complete and just give you the wall of text that is easy to ignore that it totally failed
mighty pike
you need to sort out the mismatch between your pac-man hooks and how you generat...
Can you explain that part to me in German ? I did not get the problem 100%
wraith jay
I don’t speak german lol
wraith jay
ha it is because of my job and yea it’s german lol
most ppl think it’s from the techno song
mighty pike
I chrooted but hooks aren't even present
jagged osprey
On mkinitcpio are there any errors?
mighty pike
Is there a command that I can check that or logs ?
jagged osprey
Easiest way, reinstall the kernel 🤣
mighty pike
Is that so correct ? The fallback by 'Building image from preset' is a bit confusing for me
Still no hooks there hm
Mkinitcpio using default configuration should be fine I think
jagged osprey
in `ls /etc/pacman.d/hooks/`is there an nvidia hook?
And this?
jagged osprey
can you show me the end of the mkinitcpio?
mighty pike
Mean in the conf ?
jagged osprey
Is that so correct ? The fallback by 'Building image from preset' is a bit confu...
I mean the end of this?
jagged osprey
what's the vboxhost thing?
jagged osprey
ah fair
mighty pike
Is it possible just to install linux-lts without removing linux?
Ahh I need to remove it and the do a grub-mkconfig or ?
jagged osprey
You can but I don’t think it’ll solve anything
pastel sage
<@540756183737171969> in case you're about, know much about needing to downgrade...
I’m busy right now so I can’t stick around to help, but that could be due to the boot partition not being mounted properly (fstab issue).
mighty pike
Hm
jagged osprey
I’m busy right now so I can’t stick around to help, but that could be due to the...
Appreciate the response, the fstab seems correct, tbat was my first thought too though
Remember if you do try the lts kernel to install the lts headers
mighty pike
You were right, it changed nothing.
jagged osprey
Sorry, wish I was wrong
lofty turret
your grub is probably pointing somewhere else
could you mount only your root
and ls /mnt/boot
if you see vmlinuz there, then there's your kernel
mint flicker
if ur missing vmlinuz and for some reason pacman kernel install isnt putting it there, you might temporarily be able to get away with shoving a kernel binary in there urself
mint flicker
<@540756183737171969> in case you're about, know much about needing to downgrade...
depending on what the uname -a and pacman -Qi are this might need a specific kver
and depending on that kver it could be unavailable from repos
lofty turret
the thing is they dont know where grub is pointing to
theres another kernel grub is pointing to
mint flicker
wtf
lofty turret
that can happen
mint flicker
manually run os prober see what it does
jagged osprey
your grub is probably pointing somewhere else
@mighty pike read iobz messages from here
mint flicker
it might have old concept of where kernel should be
lofty turret
could you mount only your root
do this first
i wanna know if it's inside the root filesystem and not the esp
jagged osprey
Thing is though that efi got wiped, and grub reinstalled, then the kernel reinstalled, then the mkconfig done
mighty pike
Yeah I try it right now
mint flicker
lol is it unmounted and installing in directory /mnt/boot and not actually boot part
lofty turret
what does it show?
mighty pike
Ahh wait, my mistake. I did chroot
jagged osprey
Then ls /boot
lofty turret
lol is it unmounted and installing in directory /mnt/boot and not actually boot ...
nah it's because sometimes when people install grub if you forget to mount your esp specially when in fstab it's on /boot
it will get installed on /boot of the root filesystem and not the esp
jagged osprey
And that’s with efi not mounted?
mighty pike
Yes
jagged osprey
@lofty turret damn that’s a good catch
@mighty pike you did grub install on /boot but without efi mounted to /boot
mighty pike
Sry, my english is not so good and I'm not 100% aware of the problem
lofty turret
just change the mountpoint of the esp in fstab
and update your kernel now
mighty pike
But that I need to do as chroot correct ?
lofty turret
yes
mighty pike
That's my current fstab
But if I update the kernel it should be mounted to boot ?
Tbh, I'm not sure what to do right now sry.
lofty turret
youre at chroot right?
change /boot to /boot/efi in fstab
mkdir /boot/efi
pacman -S linux
exit
reboot
mighty pike
Yeah, but without mounting boot correct ?
lofty turret
yeah
and now, from now on you will no longer mount it to /boot whenever to chroot
you will now mount it to /boot/efi since that's what we changed it to
mighty pike
Because I did no changes now in the fstab. I didn't get that what I need to change there
/boot to /boot/efi ?
lofty turret
you can open it again in a text editor and change it
mighty pike
Thx guys for your help. I will restart
Hm, still sayin that fails to boot. Now logically /boot/efi.
lofty turret
Hm, still sayin that fails to boot. Now logically /boot/efi.
did you pacman -S linux at chroot?
lofty turret
just to test if it's actually what it's pointing
could you mount only your root and
rm /mnt/boot/vmlinuz-linux
then reboot and see if it proceeds to boot
if it does then that isnt where grub is pointing
if it doesnt try pacman -S linux again in chroot only mounting root
mighty pike
I think it's the first. I got again failed to mount /boot/efi
lofty turret
I think it's the first. I got again failed to mount /boot/efi
ok so,
mount your root
mount your efi partition to /mnt/boot/efi
chroot in
grub-install --target=x86_64-efi --efi-directory=/boot/efi
grub-mkconfig -o /boot/grub/grub.cfg```
exit and reboot@mighty pike@mighty pike
i shouldve just said earlier to reinstall grub, mb quickest solutions sometimes go over my head
lofty turret
-efi
mighty pike
Hm I don't know if I'm doing something essentially wrong. Still got the error..
I did exactly that order.
lofty turret
aight we'll just use that
umount /mnt/boot/efi
rm -rf /mnt/boot/*
mount /dev/fkjfbndfkds /mnt/boot
arch-chroot /mnt
pacman -S linux
#not needed but just to make sure
grub-install --target=x86_64-efi --efi-directory=/boot
grub-mkconfig -o /boot/grub/grub.cfg
also change back the thing on fstab to /boot
if this still doesnt work im sorry i have no more ideas
mighty pike
No chroot after mount boot ?
lofty turret
there is
mighty pike
Ahh
Hm, thx for your help guys @jagged osprey @lofty turret @mint flicker Still not working but I don't want to waste your time anymore.
stoic fernBOT
vegancookies, i0bz, and x86asm_ received a thank you cookie!
mint flicker
any error message?
mighty pike
Just failing to mount
The same error.
So the boot. Idk, if it is kernel relevant. With 6.5.3 I don't get that error but it still don't boot up completely. But I can use the console there. That error is so weird, make no sense to me
mint flicker
GPT or MBR
mighty pike
GPT
jagged osprey
Hm, thx for your help guys <@183577215324258304> <@743395404900728862> <@8215692...
I don't consider it a waste of time, clearly there's a knowledge gap we all have, and experiences like these help us bridge them 🙂
mighty pike
I don't consider it a waste of time, clearly there's a knowledge gap we all have...
Yeah of course, but it's your free time. For me that is cool too, learned a lot really. I don't want to steal someones free time. ^^
For me it's like that, I like to work with people who are motivated like me. I had that at a company where I was trainee. Sadly where I'm now there is big leak of passion. Was today a bit like the old days. ^^
jagged osprey
have you backed up everything on your arch partition?
mighty pike
have you backed up everything on your arch partition?
Not now. I want to try it later again, just sitting since yesterday. I needed a break. The thing is, even if I would delete everything and do it again. I'm not sure if it is working then. My lvim conf is safe and so on like some code projects. That's why I think what is the way to go and reading threads right now. But we did already the most things from now what I read. The only thing is the grub. I saw someone he said he did grub not in chroot and then grub-mkconfig
And I think it could relate to what iod said, but I still don't understand 100% what the reason is
I did check after the last try with fdisk if my boot partition is really an EFI System. That was my last attempt until nown
jagged osprey
just want to make sure if you want to just try reinstalling from scratch that you don't lose any data
mighty pike
So finally I got a bit further. I can enter tty with 6.5.5 kernel. I saw that my root was vmlinuz and after deleting it, he did not find it. So somehow that grub pointed there. I can get in tty now. But it stays in the loading screen. So I think that is related to what @lofty turret said.
mighty pike
[Solved] GRUB does not list Linux anymore
jagged osprey
So is the new issue the graphics drivers?
mighty pike
So is the new issue the graphics drivers?
Yep ^^
mighty pike
So is the new issue the graphics drivers?
So it's in a loop. But tty is working. Journal said sddm display server number find. But not sure if that could be the reason for it.