You are not logged in.
Hi, latest kernel that boots on my laptop is 6.4.12.
The newer ones (6.4.13 and 6.5.3) block the boot at loading initial ramdisk.
I tried the lts an it boots fine.
Arch is installed since two years on a btrfs filesystem and the vga is an integrated Intel hd 530.
I did some researces finding nothing useful, any help is appreciated.
Offline
The newer ones (6.4.13 and 6.5.3) block the boot at loading initial ramdisk.
Have you confirmed the boot is really stuck rather than just the display by examining the journal? Arch never released a 6.4.13 package where did that come from?
Offline
My wrong, you are right, it was 6.5.2 not 6.4.13.
Journal -b doesn't show any error
Offline
What if you Disable modesetting? If that fails try blacklisting i915. If that fails try adding the following Kernel parameters and see if any more output is produced:
ignore_loglevel earlycon=efifb earlyprintk=vga,keep
Offline
Tried adding to 6.5.3 these kernel parameters with no luck:
nomodeset i915.modeset=0
module_blacklist=i915
Adding
ignore_loglevel earlycon=efifb earlyprintk=vga,keep
produces more output but it's incomprehensible to me. There's only a suspicious line that says:
unknown kernel command line parameter "BOOT_IMAGE=/vmlinuz-linux", will be passed to user space
Last edited by Sandrino (2023-09-16 19:36:38)
Offline
Please post a link to an image of the incomprehensible output.
Offline
Last edited by Sandrino (2023-09-16 19:55:16)
Offline
Ops, the image quality on phone is good but the uploaded one in terrible
edit: changed image host
Last edited by Sandrino (2023-09-16 19:55:53)
Offline
https://i.ibb.co/8DZWWp5/IMG-20230916-210020-004.jpg and https://i.postimg.cc/4ZvQp32x/IMG-20230 … 20-004.jpg look equal to me.
Probably post your complete system journal for a 6.4.12 boot:
sudo journalctl -b | curl -F 'file=@-' 0x0.st
Offline
Offline
set 16 22:23:18 drinopc kernel: DMI: ASUSTeK COMPUTER INC. N752VX/N752VX, BIOS N752VX.303 04/17/2019
set 16 22:23:18 drinopc kernel: DMAR: [Firmware Bug]: No firmware reserved region can cover this RMRR [0x0000000068800000-0x0000000078ffffff], contact BIOS vendor for fixes
set 16 22:23:18 drinopc kernel: DMAR: [Firmware Bug]: Your BIOS is broken; bad RMRR [0x0000000068800000-0x0000000078ffffff]
BIOS vendor: American Megatrends Inc.; Ver: N752VX.303; Product Version: 1.0
Is there a BIOS/UEFI update available?
set 16 22:23:18 drinopc kernel: nouveau 0000:01:00.0: [drm] Cannot find any crtc or sizes
"module_blacklist=nouveau"
Alternatively your GPU is still supported by the nvidia driver.
Probably also add "initcall_blacklist=simpledrm_platform_driver_init" to the https://wiki.archlinux.org/title/Kernel_parameters to get rid of the simpledrm device.
Offline
There isn't any bios update.
There is an Nvidia 950m but isn't installed, the Intel igpu is running
Going to try the suggested kernel parameter
Offline
Adding
initcall_blacklist=simpledrm_platform_driver_init
to 6.5.3 doesn't solve the issue, stuck at loading initial ramdisk
Offline
Did you also blacklist nouveau?
The GPU is very much "installed" and addressed by the kernel and nouvau in particular has a track record of stalling the PCI bus…
Offline
Adding
module_blacklist=nouveau
doesn't solve
Offline
Did you also blacklist nouveau?
The GPU is very much "installed" and addressed by the kernel and nouvau in particular has a track record of stalling the PCI bus…
I didn't installed any Nvidia driver
Offline
nouveau is the kernel in-tree driver for nvidia GPUs.
Try "acpi=off"
Offline
nouveau is the kernel in-tree driver for nvidia GPUs.
Try "acpi=off"
Something is changed, system boots but it's impossible to login, no input typing the password
Offline
What about pci=noacpi
Offline
What about pci=noacpi
Doesn't boot
edit: installing Nvidia driver can solve this issue?
Last edited by Sandrino (2023-09-16 21:43:04)
Offline
Probably not.
Does "noapic" [sic!] work?
Offline
Probably not.
Does "noapic" [sic!] work?
Unfortunately no.
Offline
Something is changed, system boots but it's impossible to login, no input typing the password
What exactly is the environment at this point? A rescue shell? Normal console login? Some graphical DM (GDM etc)?
Do you get away w/ "acpi=noirq"?
Offline
Something is changed, system boots but it's impossible to login, no input typing the password
What exactly is the environment at this point? A rescue shell? Normal console login? Some graphical DM (GDM etc)?
Do you get away w/ "acpi=noirq"?
"acpi=noirq" doesn't fix
SDDM login
edit: just to inform, sometimes it gets stuck at loading initial ramdisk even running a working kernel and I have to reboot to start the system. It has always done so. Maybe a crappy PC
Last edited by Sandrino (2023-09-17 15:41:00)
Offline
"rootdelay=5" (waits 5 seconds before trying to mount the root FS
or
"boot_delay=1000", if it boots, that'll be slooooowly
"i8042.dumbkbd" along acpi=off might get you a keyboard and us a journal from an acpi-less boot of the "bad" kernel.
Offline