You are not logged in.
I ran sudo pacman -Syu and it upgraded the linux kernel.
But the grub bootloader still tries to boot into the old kernel.
I have my 512 mb efi partition mounted on /boot/efi.
Pls tell me how to fix this thanks.
Last edited by pyrole (2022-07-15 22:51:20)
Offline
Also here is my lsblk output:
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
sda 8:0 1 0B 0 disk
nvme0n1 259:0 0 953.9G 0 disk
├─nvme0n1p1 259:1 0 513M 0 part /boot/efi
├─nvme0n1p2 259:2 0 100G 0 part /
├─nvme0n1p3 259:3 0 16G 0 part [SWAP]
└─nvme0n1p4 259:4 0 837.4G 0 part /homeOffline
cat /proc/cmdlineOffline
cat /proc/cmdline
Thanks for helping.....
BOOT_IMAGE=/bppt/vmlinuz-linux root=UUID=81eec35c-a903-4bfe-b3b1-2137f7931093 rw quiet resume=UUID=1211ccb3-5aed-448c-b45a-e96b2d1f3cd1 loglevel=3 audit=0 Also my arch is on other laptop and i am typing this output by hand so pls forgive if there are any small typos, I'll try my best to double check everything.
Offline
ls /boot
file /boot/vmlinuz-linux
ls /boot/efiOffline
ls /boot file /boot/vmlinuz-linux ls /boot/efi
amd-ucode.img efi grub initramfs-linux-fallback.img initramfs-linux.img intel-ucode.img vmlinuz-linux
/boot/vmlinuz-linux: Linux kernel x86 boot executable bzImage, version 5.18.11-arch1-1 ....... i dont think the rest is of use if it is I will share
EFI initramfs-linux-fallback.img initramfs-linux.img vmlinuz-linuxalso the vmlinuz-linux in /boot/efi is the same version as that in /boot
....
So lemme tell you what all happened from the start.
Initially my uname -r showed the older kernel version when compared to my version of vmlinuz-linux in /boot
So i ran
sudo mount /dev/nvme0n1p1 /boot
sudo pacman -S linux
grub-install --target=x86_64-efi --efi-directory=/boot/efi --bootloader-id=GRUB
grub-mkconfig -o /boot/grub/grub.cfgI picked up the above commands from other similar problem solutions.
Offline
sudo mount /dev/nvme0n1p1 /bootThat should have been "sudo mount /dev/nvme0n1p1 /boot/efi"?
nvme0n1p1 is supposed to be /boot/efi and you're loading the kernel/booting from the root partition.
Initially my uname -r showed the older kernel version when compared to my version of vmlinuz-linux in /boot
Does it still?
Offline
sudo mount /dev/nvme0n1p1 /bootThat should have been "sudo mount /dev/nvme0n1p1 /boot/efi"?
nvme0n1p1 is supposed to be /boot/efi and you're loading the kernel/booting from the root partition.Initially my uname -r showed the older kernel version when compared to my version of vmlinuz-linux in /boot
Does it still?
1. But wasn't nvme0n1p1 already mounted on /boot/efi as shown in lsblk?
2. No now uname -r shows the latest kernel version same as vmlinuz
3. Also pls tell me how do I fix this mess I made and what all I should have done from the beginning itself
Last edited by pyrole (2022-07-14 21:34:48)
Offline
I wanted to check whether that was a typo.
If it wasn't and you augmented the /boot path of your root partition w/ the EFI partition this explains why you've a kernel there and also why the relevant kernel (in /boot - w/o mounting anything there!) wasn't updated.
The updated kernel went, falsely, into the EFI partition.
You can remove it and the initramfs' from /boot/efi.
Offline
I wanted to check whether that was a typo.
If it wasn't and you augmented the /boot path of your root partition w/ the EFI partition this explains why you've a kernel there and also why the relevant kernel (in /boot - w/o mounting anything there!) wasn't updated.
The updated kernel went, falsely, into the EFI partition.You can remove it and the initramfs' from /boot/efi.
Yes that wasn't a typo, also the nvme0n1p1 got unmounted as soon as i rebooted so now it is only mounted to /boot/efi
Can you kindly tell me the appropriate commands i need to run for each step?
Last edited by pyrole (2022-07-14 21:38:51)
Offline
Can you kindly tell me the appropriate commands i need to run for each step?
What command for what step? Removing files???
Also, is there still an issue w/ the boot (since you're no longer booting a dated kernel)?
Offline
What command for what step? Removing files???
i mean yeah i deleted both the initramfs and vmlinuz form /boot/efi so i just wanted to confirm with you if thos exact files were supposed to be deleted.....
Also how do we fix the boot issue?
Offline
Also how do we fix the boot issue?
Since you're no longer booting a dated kernel it's not clear whether and what that issue would be (see my previous post)
Please post the system journal for a failing boot, https://wiki.archlinux.org/title/System … al_to_view
Offline
Also how do we fix the boot issue?
Since you're no longer booting a dated kernel it's not clear whether and what that issue would be (see my previous post)
Please post the system journal for a failing boot, https://wiki.archlinux.org/title/System … al_to_view
Yes the kernel moduels still aren't getting loaded on boot.
I didn't quiet understand how to get the system journal on the link you provided : (
Also even if I get it idk how to share it with you, currently i am using a second laptop and the broken arch is on my first, it has only tty's working so how do i share the outputs?
Last edited by pyrole (2022-07-14 22:10:10)
Offline
deleted
Last edited by pyrole (2022-07-14 22:09:47)
Offline
it has only tty's working so how do i share the outputs?
First link below.
If you can boot the system (despite the error) and have network access, just post "sudo journalctl -b".
Also check "systemctl status systemd-modules-load" - I assume the only thing that fails is the nvidia module and this is actually just an extension of https://bbs.archlinux.org/viewtopic.php?id=278042 …
Offline
it has only tty's working so how do i share the outputs?
First link below.
If you can boot the system (despite the error) and have network access, just post "sudo journalctl -b".
Also check "systemctl status systemd-modules-load" - I assume the only thing that fails is the nvidia module and this is actually just an extension of https://bbs.archlinux.org/viewtopic.php?id=278042 …
Ok so we can consider the nvidia fail to be redundant because I reinstalled my OS, so in this install I haven't touched the nvidia driver.
After the install I didn't do many changes, just few installations, lightdm, xfce4 and all which were working normally, the only problem arrised when i did pacman -Syu and I expected this problem because I had faced this in previous installation too but i forgot how i fixed it.
For sudo journalctl -b:
http://ix.io/44nP
Also I could not "boot" into the system, as in I was only able to access the tty nothing else.
systemctl status systemd-modules-load:
http://ix.io/44nR
Also since I messed quiet some shit up, i can easily reinstall my Arch and maybe you can guide me from there if that would be easier for you? What i mean is when i reinstall my problem is almost the same as in this post:
https://bbs.archlinux.org/viewtopic.php?id=270312
Except that i have an efi partition.....
But now the problem is something else i guess so just lemme know if you want me to reinstall a clean OS or try to fix this one.
Last edited by pyrole (2022-07-14 22:36:11)
Offline
Ok so we can consider the nvidia fail to be redundant because I reinstalled my OS, so in this install I haven't touched the nvidia driver.
![]()
Jul 15 03:12:32 Dell-G15-Aryan kernel: traps: Missing ENDBR: _nv011433rm+0x0/0x10 [nvidia]
Jul 15 03:12:32 Dell-G15-Aryan kernel: ------------[ cut here ]------------
Jul 15 03:12:32 Dell-G15-Aryan kernel: kernel BUG at arch/x86/kernel/traps.c:252!
Jul 15 03:12:32 Dell-G15-Aryan kernel: invalid opcode: 0000 [#1] PREEMPT SMP NOPTI
Jul 15 03:12:32 Dell-G15-Aryan kernel: CPU: 5 PID: 349 Comm: systemd-modules Tainted: P OE 5.18.11-arch1-1 #1 50398f5e5a828e0d0e099049385fd5e709a30e3e
Jul 15 03:12:32 Dell-G15-Aryan kernel: Hardware name: Dell Inc. Dell G15 5511/0284MK, BIOS 1.6.0 09/28/2021
Jul 15 03:12:32 Dell-G15-Aryan kernel: RIP: 0010:exc_control_protection+0xc2/0xd0
Jul 15 03:12:32 Dell-G15-Aryan kernel: Code: 8b 93 80 00 00 00 be f9 00 00 00 48 c7 c7 4b e1 46 83 e8 e1 d3 4f ff e9 72 ff ff ff 48 c7 c7 32 e1 46 83 e8 cb 21 fb ff 0f 0b <0f> 0b 66 66 2e 0f 1f 84 00 00 00 00 00 90 66 0f 1f 00 55 53 48 89
Jul 15 03:12:32 Dell-G15-Aryan kernel: RSP: 0018:ffffabaf80fbfb78 EFLAGS: 00010002
Jul 15 03:12:32 Dell-G15-Aryan kernel: RAX: 0000000000000033 RBX: ffffabaf80fbfb98 RCX: 0000000000000027
Jul 15 03:12:32 Dell-G15-Aryan kernel: RDX: 0000000000000000 RSI: 0000000000000001 RDI: ffff9f0cbb7616a0
Jul 15 03:12:32 Dell-G15-Aryan kernel: RBP: 0000000000000003 R08: 0000000000000000 R09: ffffabaf80fbf998
Jul 15 03:12:32 Dell-G15-Aryan kernel: R10: 0000000000000003 R11: ffffffff83ccaa08 R12: 0000000000000000
Jul 15 03:12:32 Dell-G15-Aryan kernel: R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000
Jul 15 03:12:32 Dell-G15-Aryan kernel: FS: 00007fa0ce744280(0000) GS:ffff9f0cbb740000(0000) knlGS:0000000000000000
Jul 15 03:12:32 Dell-G15-Aryan kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Jul 15 03:12:32 Dell-G15-Aryan kernel: CR2: 0000564a9c3ec108 CR3: 00000001016fa003 CR4: 0000000000f70ee0
Jul 15 03:12:32 Dell-G15-Aryan kernel: PKRU: 55555554
Jul 15 03:12:32 Dell-G15-Aryan kernel: Call Trace:
Jul 15 03:12:32 Dell-G15-Aryan kernel: <TASK>
Jul 15 03:12:32 Dell-G15-Aryan kernel: asm_exc_control_protection+0x22/0x30
Jul 15 03:12:32 Dell-G15-Aryan kernel: RIP: 0010:_nv011433rm+0x0/0x10 [nvidia]
Jul 15 03:12:32 Dell-G15-Aryan kernel: Code: 66 2e 0f 1f 84 00 00 00 00 00 48 83 ec 08 e8 57 10 1e 00 48 83 c4 08 48 89 c7 e9 bb ff ff ff 66 2e 0f 1f 84 00 00 00 00 00 90 <48> 89 f7 e9 18 08 00 00 0f 1f 84 00 00 00 00 00 48 89 f7 e9 18 08
Jul 15 03:12:32 Dell-G15-Aryan kernel: RSP: 0018:ffffabaf80fbfc48 EFLAGS: 00010202
Jul 15 03:12:32 Dell-G15-Aryan kernel: RAX: ffffffffc36f88f0 RBX: ffffffffc590d170 RCX: 0000000000000000
Jul 15 03:12:32 Dell-G15-Aryan kernel: RDX: 000000000003f6bb RSI: 0000000000000010 RDI: ffffffffc590d170
Jul 15 03:12:32 Dell-G15-Aryan kernel: RBP: ffff9f096757dfe0 R08: 0000000000000020 R09: ffffffffc590d1b0
Jul 15 03:12:32 Dell-G15-Aryan kernel: R10: ffffffffc58c3eb0 R11: 0000000000000000 R12: 0000000000000010
Jul 15 03:12:32 Dell-G15-Aryan kernel: R13: ffff9f096757b000 R14: 00007fa0cede1343 R15: ffffabaf80fbfdc8
Jul 15 03:12:32 Dell-G15-Aryan kernel: ? _nv034913rm+0x20/0x20 [nvidia 698248abac66cac3ddc3cdea779c5eccd3653bcd]
Jul 15 03:12:32 Dell-G15-Aryan kernel: _nv011431rm+0x24/0xe0 [nvidia 698248abac66cac3ddc3cdea779c5eccd3653bcd]
Jul 15 03:12:32 Dell-G15-Aryan kernel: _nv034914rm+0xe/0xa0 [nvidia 698248abac66cac3ddc3cdea779c5eccd3653bcd]
Jul 15 03:12:32 Dell-G15-Aryan kernel: _nv034917rm+0x1d/0x30 [nvidia 698248abac66cac3ddc3cdea779c5eccd3653bcd]
Jul 15 03:12:32 Dell-G15-Aryan kernel: _nv034919rm+0x2f/0x40 [nvidia 698248abac66cac3ddc3cdea779c5eccd3653bcd]
Jul 15 03:12:32 Dell-G15-Aryan kernel: _nv015567rm+0x15/0x70 [nvidia 698248abac66cac3ddc3cdea779c5eccd3653bcd]
Jul 15 03:12:32 Dell-G15-Aryan kernel: _nv000642rm+0x9/0x20 [nvidia 698248abac66cac3ddc3cdea779c5eccd3653bcd]
Jul 15 03:12:32 Dell-G15-Aryan kernel: ? cdev_add+0x4d/0x60
Jul 15 03:12:32 Dell-G15-Aryan kernel: rm_init_rm+0x17/0x60 [nvidia 698248abac66cac3ddc3cdea779c5eccd3653bcd]
Jul 15 03:12:32 Dell-G15-Aryan kernel: nvidia_init_module+0x242/0x613 [nvidia 698248abac66cac3ddc3cdea779c5eccd3653bcd]
Jul 15 03:12:32 Dell-G15-Aryan kernel: ? nvidia_init_module+0x613/0x613 [nvidia 698248abac66cac3ddc3cdea779c5eccd3653bcd]
Jul 15 03:12:32 Dell-G15-Aryan kernel: nvidia_frontend_init_module+0x50/0x91 [nvidia 698248abac66cac3ddc3cdea779c5eccd3653bcd]
Jul 15 03:12:32 Dell-G15-Aryan kernel: ? nvidia_init_module+0x613/0x613 [nvidia 698248abac66cac3ddc3cdea779c5eccd3653bcd]https://wiki.archlinux.org/title/NVIDIA#Installation - see the blue note.
Last edited by seth (2022-07-14 22:41:37)
Offline
https://wiki.archlinux.org/title/NVIDIA#Installation - see the blue note.
Wait whaaaaaaaat but howww..... I reinstalled it from scratch : (
It was my gpu all along damnnn.
So how do we fix that??? I tried reading the nvidia article you shared but ummm what am i looking for ?
Offline
see the blue note
Offline
see the blue note
Is this what you mean ?
Due to FS#74886/FS#74891, nvidia does not boot on Linux 5.18 on systems with Intel CPUs. Until this is fixed, a workaround is disabling the Indirect Branch Tracking CPU security feature by setting the ibt=off kernel parameter from the bootloader. This security feature is responsible for mitigating a class of exploit techniques, but is deemed safe as a temporary stopgap solution. You can alternatively try nvidia-open and continue using IBT.
If yes, which file has the ibt kernel parameter? Also after making that change do i run sudo grub-mkconfig -o /boot/grub/grub.cfg?
Offline
The "kernel parameter" token in the wiki is a link. Do you think you want to click it?
Offline
journal after adding ibt=off to grub.cfg
http://ix.io/44o3
Offline
The "kernel parameter" token in the wiki is a link. Do you think you want to click it?
Sir I did click the link and tried to understand it to my best of abilities..... Then i added ibt=off to the grub.cfg because that was what i understood then i did grub update.
Where did i go wrong?
Offline
Jul 15 04:27:28 Dell-G15-Aryan kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-linux root=UUID=81eec35c-a903-4bfe-b3b1-2137f7931093 rw quiet resume=UUID=1211ccb3-5aed-448c-b45a-e96b2d1f3cd1 loglevel=3 audit=0Does not show ibt=off. What is the contents of grub.cfg?
Offline