View previous topic :: View next topic |
Author |
Message |
pingtoo Veteran


Joined: 10 Sep 2021 Posts: 1640 Location: Richmond Hill, Canada
|
Posted: Sat Apr 19, 2025 12:59 am Post subject: |
|
|
alecStewart1 wrote: | Okay, pingtoo is right in apparently in that I need a directory /efi/EFI/BOOT and a filoe /efi/EFI/BOOT/BOOTx64.EFI in order to actually see any other boot entries...weird but it works.
I get to the menu, select the custom configured kernel and I get...a blank black screen. No error messages. |
Very good, at least we pass the EFI boot manager. Not sure which "menu" you refer to? BIOS menu or you mean you were able boot in to linux and use efibootmgr to select default boot entry? Also I recommend once you got the kernel sort out, create a boot entry for fallback to use /efi/EFI/BOOT/bootx64/efi and copy the right kernel.efi file over to /efi/EFI/BOOT/bootx64.efi. this is best practice suggested by UEFI spec.
Code: | [ 2.382311] x86/mm: Checked W+X mappings: passed, no W+X pages found.
[ 2.382685] Run /init as init process
[ 2.383063] with arguments:
[ 2.383064] /init
[ 2.383064] nodhcp
[ 2.383064] secureconsole
[ 2.383065] cdroot
[ 2.383065] with environment:
[ 2.383065] HOME=/
[ 2.383066] TERM=linux
[ 2.383066] BOOT_IMAGE=/boot/gentoo
[ 2.422837] dracut: dracut-106
[ 2.462638] loop: module loaded
[ 2.467988] dracut: root was live:CDLABEL=gentoo-amd64-livegui, is now live:/dev/disk/by-label/gentoo-amd64-livegui
[ 2.516823] dracut Warning: ZFS: No hostid found on kernel command line or /etc/hostid.
[ 2.520922] dracut Warning: ZFS: Pools may not import correctly.
[ 2.537297] dracut: ZFS: no ZFS-on-root.
[ 2.708420] dracut: rd.md=0: removing MD RAID activation |
I am under impression that you want to use ugRD for initrd, but it appear this boot you got dracut.
I don't have much experience with kernel on x86/amd64 but you are in good hand with zen_desu and pietinger and rest of Gentoo community. |
|
Back to top |
|
 |
zen_desu Apprentice

Joined: 25 Oct 2024 Posts: 248
|
Posted: Sat Apr 19, 2025 1:13 am Post subject: |
|
|
pingtoo wrote: | alecStewart1 wrote: | Okay, pingtoo is right in apparently in that I need a directory /efi/EFI/BOOT and a filoe /efi/EFI/BOOT/BOOTx64.EFI in order to actually see any other boot entries...weird but it works.
I get to the menu, select the custom configured kernel and I get...a blank black screen. No error messages. |
Very good, at least we pass the EFI boot manager. Not sure which "menu" you refer to? BIOS menu or you mean you were able boot in to linux and use efibootmgr to select default boot entry? Also I recommend once you got the kernel sort out, create a boot entry for fallback to use /efi/EFI/BOOT/bootx64/efi and copy the right kernel.efi file over to /efi/EFI/BOOT/bootx64.efi. this is best practice suggested by UEFI spec.
Code: | [ 2.382311] x86/mm: Checked W+X mappings: passed, no W+X pages found.
[ 2.382685] Run /init as init process
[ 2.383063] with arguments:
[ 2.383064] /init
[ 2.383064] nodhcp
[ 2.383064] secureconsole
[ 2.383065] cdroot
[ 2.383065] with environment:
[ 2.383065] HOME=/
[ 2.383066] TERM=linux
[ 2.383066] BOOT_IMAGE=/boot/gentoo
[ 2.422837] dracut: dracut-106
[ 2.462638] loop: module loaded
[ 2.467988] dracut: root was live:CDLABEL=gentoo-amd64-livegui, is now live:/dev/disk/by-label/gentoo-amd64-livegui
[ 2.516823] dracut Warning: ZFS: No hostid found on kernel command line or /etc/hostid.
[ 2.520922] dracut Warning: ZFS: Pools may not import correctly.
[ 2.537297] dracut: ZFS: no ZFS-on-root.
[ 2.708420] dracut: rd.md=0: removing MD RAID activation |
I am under impression that you want to use ugRD for initrd, but it appear this boot you got dracut.
I don't have much experience with kernel on x86/amd64 but you are in good hand with zen_desu and pietinger and rest of Gentoo community. |
I think that portion is from the livecd, I'd be interested to see the kernel log when booted to the install, or the log/fail screen if it fails to boot. _________________ µgRD dev
Wiki writer |
|
Back to top |
|
 |
alecStewart1 Apprentice

Joined: 03 Jul 2022 Posts: 239
|
Posted: Sat Apr 19, 2025 2:13 am Post subject: |
|
|
zen_desu wrote: | pingtoo wrote: | alecStewart1 wrote: | Okay, pingtoo is right in apparently in that I need a directory /efi/EFI/BOOT and a filoe /efi/EFI/BOOT/BOOTx64.EFI in order to actually see any other boot entries...weird but it works.
I get to the menu, select the custom configured kernel and I get...a blank black screen. No error messages. |
Very good, at least we pass the EFI boot manager. Not sure which "menu" you refer to? BIOS menu or you mean you were able boot in to linux and use efibootmgr to select default boot entry? Also I recommend once you got the kernel sort out, create a boot entry for fallback to use /efi/EFI/BOOT/bootx64/efi and copy the right kernel.efi file over to /efi/EFI/BOOT/bootx64.efi. this is best practice suggested by UEFI spec.
Code: | [ 2.382311] x86/mm: Checked W+X mappings: passed, no W+X pages found.
[ 2.382685] Run /init as init process
[ 2.383063] with arguments:
[ 2.383064] /init
[ 2.383064] nodhcp
[ 2.383064] secureconsole
[ 2.383065] cdroot
[ 2.383065] with environment:
[ 2.383065] HOME=/
[ 2.383066] TERM=linux
[ 2.383066] BOOT_IMAGE=/boot/gentoo
[ 2.422837] dracut: dracut-106
[ 2.462638] loop: module loaded
[ 2.467988] dracut: root was live:CDLABEL=gentoo-amd64-livegui, is now live:/dev/disk/by-label/gentoo-amd64-livegui
[ 2.516823] dracut Warning: ZFS: No hostid found on kernel command line or /etc/hostid.
[ 2.520922] dracut Warning: ZFS: Pools may not import correctly.
[ 2.537297] dracut: ZFS: no ZFS-on-root.
[ 2.708420] dracut: rd.md=0: removing MD RAID activation |
I am under impression that you want to use ugRD for initrd, but it appear this boot you got dracut.
I don't have much experience with kernel on x86/amd64 but you are in good hand with zen_desu and pietinger and rest of Gentoo community. |
I think that portion is from the livecd, I'd be interested to see the kernel log when booted to the install, or the log/fail screen if it fails to boot. |
Indeed. Unfortunately, all I get is a blank black screen. I'm double checking the kernel config I have for any missing AMDGPU options I need.
Here's the current config I have, although I'm still editing it.
http://dpaste.com/6SBGSMQ5N |
|
Back to top |
|
 |
alecStewart1 Apprentice

Joined: 03 Jul 2022 Posts: 239
|
Posted: Sat Apr 19, 2025 3:04 am Post subject: |
|
|
Yup, another blank black screen.
Here's the config I have:
http://dpaste.com/8TNF9MQWP
EDIT 1:
Newer configuration than the above. Added some stuff that the Gentoo LiveGUI kernel seems to load. Don't know if that will fix things, but I'll try again.
I assume to get an actual message from the kernel upon trying to boot into it I'll have to turn printk on again?
http://dpaste.com/HDPYXSZAF
Okay I can't even compile the kernel successfully with the above configuration.
EDIT 2:
Oh wait, I know why.
EDIT 3:
Just kidding, I don't.
I get the follow error when running
Code: |
make LLVM=1 LLVM_IAS=1 LTO_CLANG_THIN=1 LD="ld.lld" AR="llvm-ar" AS="llvm-as" NM="llvm-nm" RANLIB="llvm-ranlib" STRIP="llvm-strip" OBJCOPY="llvm-objcopy" OBJDUMP="llvm-objdump" KLDFLAGS="-fuse-ld=mold -Wl,-O2 -Wl,--sort-common -Wl,--as-needed -Wl,--strip-debug -Wl,--icf=safe -Wl,-z,rewrite-endbr -flto=thin" KCFLAGS="-O2 -march=alderlake -pipe -mno-cldemote -mno-kl -mno-sgx -mno-widekl -mshstk -fstack-protector-strong -fomit-frame-pointer -flto=thin -fzero-call-used-regs=used" -j12
|
Code: |
LD /usr/src/linux-6.13.8-zen/tools/objtool/objtool-in.o
LINK /usr/src/linux-6.13.8-zen/tools/objtool/objtool
In file included from arch/x86/kernel/asm-offsets.c:10:
In file included from ./include/crypto/aria.h:22:
In file included from ./include/linux/module.h:19:
In file included from ./include/linux/elf.h:6:
In file included from ./arch/x86/include/asm/elf.h:10:
In file included from ./arch/x86/include/asm/ia32.h:7:
In file included from ./include/linux/compat.h:17:
In file included from ./include/linux/fs.h:33:
In file included from ./include/linux/percpu-rwsem.h:7:
In file included from ./include/linux/rcuwait.h:6:
In file included from ./include/linux/sched/signal.h:9:
In file included from ./include/linux/sched/task.h:13:
In file included from ./include/linux/uaccess.h:12:
In file included from ./arch/x86/include/asm/uaccess.h:17:
./arch/x86/include/asm/tlbflush.h:256:37: error: no member named 'asid_transition' in 'mm_context_t'
256 | return mm && READ_ONCE(mm->context.asid_transition);
| ~~~~~~~~~~~ ^
./include/asm-generic/rwonce.h:49:33: note: expanded from macro 'READ_ONCE'
49 | compiletime_assert_rwonce_type(x); \
| ^
./include/asm-generic/rwonce.h:36:35: note: expanded from macro 'compiletime_assert_rwonce_type'
36 | compiletime_assert(__native_word(t) || sizeof(t) == sizeof(long long), \
| ^
././include/linux/compiler_types.h:509:10: note: expanded from macro '__native_word'
509 | (sizeof(t) == sizeof(char) || sizeof(t) == sizeof(short) || \
| ^
././include/linux/compiler_types.h:542:22: note: expanded from macro 'compiletime_assert'
542 | _compiletime_assert(condition, msg, __compiletime_assert_, __COUNTER__)
| ^~~~~~~~~
././include/linux/compiler_types.h:530:23: note: expanded from macro '_compiletime_assert'
530 | __compiletime_assert(condition, msg, prefix, suffix)
| ^~~~~~~~~
././include/linux/compiler_types.h:522:9: note: expanded from macro '__compiletime_assert'
522 | if (!(condition)) \
| ^~~~~~~~~
In file included from arch/x86/kernel/asm-offsets.c:10:
In file included from ./include/crypto/aria.h:22:
In file included from ./include/linux/module.h:19:
In file included from ./include/linux/elf.h:6:
In file included from ./arch/x86/include/asm/elf.h:10:
In file included from ./arch/x86/include/asm/ia32.h:7:
In file included from ./include/linux/compat.h:17:
In file included from ./include/linux/fs.h:33:
In file included from ./include/linux/percpu-rwsem.h:7:
In file included from ./include/linux/rcuwait.h:6:
In file included from ./include/linux/sched/signal.h:9:
In file included from ./include/linux/sched/task.h:13:
In file included from ./include/linux/uaccess.h:12:
In file included from ./arch/x86/include/asm/uaccess.h:17:
./arch/x86/include/asm/tlbflush.h:256:37: error: no member named 'asid_transition' in 'mm_context_t'
256 | return mm && READ_ONCE(mm->context.asid_transition);
| ~~~~~~~~~~~ ^
./include/asm-generic/rwonce.h:49:33: note: expanded from macro 'READ_ONCE'
49 | compiletime_assert_rwonce_type(x); \
| ^
./include/asm-generic/rwonce.h:36:35: note: expanded from macro 'compiletime_assert_rwonce_type'
36 | compiletime_assert(__native_word(t) || sizeof(t) == sizeof(long long), \
| ^
././include/linux/compiler_types.h:509:39: note: expanded from macro '__native_word'
509 | (sizeof(t) == sizeof(char) || sizeof(t) == sizeof(short) || \
| ^
././include/linux/compiler_types.h:542:22: note: expanded from macro 'compiletime_assert'
542 | _compiletime_assert(condition, msg, __compiletime_assert_, __COUNTER__)
| ^~~~~~~~~
././include/linux/compiler_types.h:530:23: note: expanded from macro '_compiletime_assert'
530 | __compiletime_assert(condition, msg, prefix, suffix)
| ^~~~~~~~~
././include/linux/compiler_types.h:522:9: note: expanded from macro '__compiletime_assert'
522 | if (!(condition)) \
| ^~~~~~~~~
|
Here's the kernel config:
http://dpaste.com/9B3NRZ5L3 |
|
Back to top |
|
 |
alecStewart1 Apprentice

Joined: 03 Jul 2022 Posts: 239
|
Posted: Sat Apr 19, 2025 11:48 pm Post subject: |
|
|
zen_desu
Trying things with different kernel source, ugrd doesn't detect compressed firmware, maybe?
Code: |
make LLVM=1 LLVM_IAS=1 LTO_CLANG_THIN=1 LD="ld.lld" AR="llvm-ar" AS="llvm-as" NM="llvm-nm" RANLIB="llvm-ranlib" STRIP="llvm-strip" OBJCOPY="llvm-objcopy" OBJDUMP="llvm-objdump" KLDFLAGS="-fuse-ld=mold -Wl,-O2 -Wl,--sort-common -Wl,--as-needed -Wl,--strip-debug -Wl,--icf=safe -Wl,-z,rewrite-endbr -flto=thin" KCFLAGS="-O2 -march=alderlake -pipe -mno-cldemote -mno-kl -mno-sgx -mno-widekl -mshstk -fstack-protector-strong -fomit-frame-pointer -flto=thin -mllvm=-polly -mllvm=-polly-vectorizer=stripmine -mllvm=-polly-omp-backend=LLVM -mllvm=-polly-parallel -mllvm=-polly-num-threads=9 -mllvm=-polly-scheduling=dynamic -fzero-call-used-regs=used" -j12 install
INSTALL /boot
* Generating AMD CPU Microcode early initramfs image...
* Created temporary directory: /tmp/tmp.tZSfLzjE5g
* Created microcode archive at: /boot/amd-uc.img
* Cleaned up temporary directory: /tmp/tmp.tZSfLzjE5g
* Generating Intel CPU Microcode early initramfs image...
microcode bundle 1: /lib/firmware/intel-ucode/06-97-02
001/001: sig 0x00090672, pf_mask 0x07, 2024-08-01, rev 0x0038, size 225280
sig 0x00090672, pf_mask 0x07, 2024-08-01, rev 0x0038
sig 0x00090675, pf_mask 0x07, 2024-08-01, rev 0x0038
sig 0x000b06f2, pf_mask 0x07, 2024-08-01, rev 0x0038
sig 0x000b06f5, pf_mask 0x07, 2024-08-01, rev 0x0038
sig 0x000b06f6, pf_mask 0x07, 2024-08-01, rev 0x0038
sig 0x000b06f7, pf_mask 0x07, 2024-08-01, rev 0x0038
microcode bundle 2: /lib/firmware/intel-ucode/06-97-05
002/001: sig 0x00090672, pf_mask 0x07, 2024-08-01, rev 0x0038, size 225280
sig 0x00090672, pf_mask 0x07, 2024-08-01, rev 0x0038
sig 0x00090675, pf_mask 0x07, 2024-08-01, rev 0x0038
sig 0x000b06f2, pf_mask 0x07, 2024-08-01, rev 0x0038
sig 0x000b06f5, pf_mask 0x07, 2024-08-01, rev 0x0038
sig 0x000b06f6, pf_mask 0x07, 2024-08-01, rev 0x0038
sig 0x000b06f7, pf_mask 0x07, 2024-08-01, rev 0x0038
selected microcodes:
001/001: sig 0x00090672, pf_mask 0x07, 2024-08-01, rev 0x0038, size 225280
001/001: sig 0x00090675, pf_mask 0x07, 2024-08-01, rev 0x0038, size 225280
001/001: sig 0x000b06f2, pf_mask 0x07, 2024-08-01, rev 0x0038, size 225280
001/001: sig 0x000b06f5, pf_mask 0x07, 2024-08-01, rev 0x0038, size 225280
001/001: sig 0x000b06f6, pf_mask 0x07, 2024-08-01, rev 0x0038, size 225280
001/001: sig 0x000b06f7, pf_mask 0x07, 2024-08-01, rev 0x0038, size 225280
iucode_tool: Writing selected microcodes to: /boot/intel-uc.img
INFO | Processing module: ugrd.base.base
INFO | Processing module: ugrd.base.core
INFO | Processing module: ugrd.fs.mounts
INFO | Adding library path: /usr/lib64
INFO | Processing module: ugrd.base.cmdline
INFO | Processing module: ugrd.base.banner
INFO | Processing module: ugrd.kmod.kmod
INFO | Processing module: ugrd.kmod.standard_mask
INFO | Processing module: ugrd.fs.cpio
INFO | Processing module: ugrd.base.checks
INFO | [kernel_version] Setting from arguments: 6.14.2
INFO | [cpio_rotate] Setting from arguments: False
INFO | [out_file] Setting from arguments: /tmp/installkernel.staging.SC0p9Iq/initrd
INFO | Resolved out_dir to: /tmp/installkernel.staging.SC0p9Iq
INFO | Loading config file: /etc/ugrd/config.toml
INFO | Resolved out_dir to: /tmp/installkernel.staging.SC0p9Iq
INFO | -- | Running ugrd v2.0.0
INFO | -- | Running build tasks
INFO | Detected init at: /sbin/init
INFO | Source path for libgcc_s: /usr/lib/gcc/x86_64-pc-linux-gnu/14/libgcc_s.so.1
INFO | Using default shell: /bin/sh
WARNING | Virtual block devices unavailable, disabling device mapper autodetection.
INFO | [/dev/nvme0n1p3] Auto-enabling kernel modules for device: nvme
INFO | [/dev/nvme0n1p3] Autodetected mount type from device: btrfs
INFO | [root] Autodetected mount source: uuid=963bf518-69b3-41af-8366-617ba5aa3ef5
INFO | [mounts] Updating mount: root
INFO | Auto-enabling module: btrfs
INFO | Processing module: ugrd.fs.btrfs
WARNING | [get_kernel_version] Kernel version is already set, skipping.
INFO | Autodetected kernel modules: nvme, intel_vsec, xe, snd_sof_pci_intel_tgl, i915, snd_hda_intel, amdgpu, iwlwifi, igc, mei_me, snd_sof_pci_intel_cnl, snd_soc_avs
WARNING | Cleaning build directory: /tmp/initramfs_build
INFO | Processing module: ugrd.kmod.novideo
INFO | Processing module: ugrd.kmod.nosound
INFO | Processing module: ugrd.kmod.nonetwork
INFO | Setting shebang to: #!/bin/sh -l
WARNING | [snd_sof_pci_intel_tgl] Failed to process autodetected kernel module dependencies: [snd_sof_pci_intel_tgl] Modinfo returned no output.
ERROR | [i915] Firmware file does not exist: /lib/firmware/i915/mtl_guc_70.bin
ERROR | [i915] Firmware file does not exist: /lib/firmware/i915/dg2_guc_70.bin
ERROR | [i915] Firmware file does not exist: /lib/firmware/i915/adlp_guc_70.bin
ERROR | [i915] Firmware file does not exist: /lib/firmware/i915/adlp_guc_70.1.1.bin
ERROR | [i915] Firmware file does not exist: /lib/firmware/i915/adlp_guc_69.0.3.bin
ERROR | [i915] Firmware file does not exist: /lib/firmware/i915/tgl_guc_70.bin
ERROR | [i915] Firmware file does not exist: /lib/firmware/i915/tgl_guc_70.1.1.bin
ERROR | [i915] Firmware file does not exist: /lib/firmware/i915/tgl_guc_69.0.3.bin
ERROR | [i915] Firmware file does not exist: /lib/firmware/i915/dg1_guc_70.bin
ERROR | [i915] Firmware file does not exist: /lib/firmware/i915/tgl_guc_70.1.1.bin
ERROR | [i915] Firmware file does not exist: /lib/firmware/i915/tgl_guc_70.1.1.bin
ERROR | [i915] Firmware file does not exist: /lib/firmware/i915/ehl_guc_70.1.1.bin
ERROR | [i915] Firmware file does not exist: /lib/firmware/i915/ehl_guc_70.1.1.bin
ERROR | [i915] Firmware file does not exist: /lib/firmware/i915/icl_guc_70.1.1.bin
ERROR | [i915] Firmware file does not exist: /lib/firmware/i915/cml_guc_70.1.1.bin
ERROR | [i915] Firmware file does not exist: /lib/firmware/i915/kbl_guc_70.1.1.bin
ERROR | [i915] Firmware file does not exist: /lib/firmware/i915/kbl_guc_70.1.1.bin
ERROR | [i915] Firmware file does not exist: /lib/firmware/i915/glk_guc_70.1.1.bin
ERROR | [i915] Firmware file does not exist: /lib/firmware/i915/kbl_guc_70.1.1.bin
ERROR | [i915] Firmware file does not exist: /lib/firmware/i915/bxt_guc_70.1.1.bin
ERROR | [i915] Firmware file does not exist: /lib/firmware/i915/skl_guc_70.1.1.bin
ERROR | [i915] Firmware file does not exist: /lib/firmware/i915/mtl_huc_gsc.bin
ERROR | [i915] Firmware file does not exist: /lib/firmware/i915/dg2_huc_gsc.bin
ERROR | [i915] Firmware file does not exist: /lib/firmware/i915/tgl_huc.bin
ERROR | [i915] Firmware file does not exist: /lib/firmware/i915/tgl_huc_7.9.3.bin
ERROR | [i915] Firmware file does not exist: /lib/firmware/i915/tgl_huc.bin
ERROR | [i915] Firmware file does not exist: /lib/firmware/i915/tgl_huc_7.9.3.bin
ERROR | [i915] Firmware file does not exist: /lib/firmware/i915/dg1_huc.bin
ERROR | [i915] Firmware file does not exist: /lib/firmware/i915/tgl_huc_7.9.3.bin
ERROR | [i915] Firmware file does not exist: /lib/firmware/i915/tgl_huc_7.9.3.bin
ERROR | [i915] Firmware file does not exist: /lib/firmware/i915/ehl_huc_9.0.0.bin
ERROR | [i915] Firmware file does not exist: /lib/firmware/i915/ehl_huc_9.0.0.bin
ERROR | [i915] Firmware file does not exist: /lib/firmware/i915/icl_huc_9.0.0.bin
ERROR | [i915] Firmware file does not exist: /lib/firmware/i915/cml_huc_4.0.0.bin
ERROR | [i915] Firmware file does not exist: /lib/firmware/i915/kbl_huc_4.0.0.bin
ERROR | [i915] Firmware file does not exist: /lib/firmware/i915/kbl_huc_4.0.0.bin
ERROR | [i915] Firmware file does not exist: /lib/firmware/i915/glk_huc_4.0.0.bin
ERROR | [i915] Firmware file does not exist: /lib/firmware/i915/kbl_huc_4.0.0.bin
ERROR | [i915] Firmware file does not exist: /lib/firmware/i915/bxt_huc_2.0.0.bin
ERROR | [i915] Firmware file does not exist: /lib/firmware/i915/skl_huc_2.0.0.bin
ERROR | [i915] Firmware file does not exist: /lib/firmware/i915/mtl_gsc_1.bin
ERROR | [i915] Firmware file does not exist: /lib/firmware/i915/xe3lpd_dmc.bin
ERROR | [i915] Firmware file does not exist: /lib/firmware/i915/xe2lpd_dmc.bin
ERROR | [i915] Firmware file does not exist: /lib/firmware/i915/bmg_dmc.bin
ERROR | [i915] Firmware file does not exist: /lib/firmware/i915/mtl_dmc.bin
ERROR | [i915] Firmware file does not exist: /lib/firmware/i915/dg2_dmc_ver2_08.bin
ERROR | [i915] Firmware file does not exist: /lib/firmware/i915/adlp_dmc.bin
ERROR | [i915] Firmware file does not exist: /lib/firmware/i915/adlp_dmc_ver2_16.bin
ERROR | [i915] Firmware file does not exist: /lib/firmware/i915/adls_dmc_ver2_01.bin
ERROR | [i915] Firmware file does not exist: /lib/firmware/i915/dg1_dmc_ver2_02.bin
ERROR | [i915] Firmware file does not exist: /lib/firmware/i915/rkl_dmc_ver2_03.bin
ERROR | [i915] Firmware file does not exist: /lib/firmware/i915/tgl_dmc_ver2_12.bin
ERROR | [i915] Firmware file does not exist: /lib/firmware/i915/icl_dmc_ver1_09.bin
ERROR | [i915] Firmware file does not exist: /lib/firmware/i915/glk_dmc_ver1_04.bin
ERROR | [i915] Firmware file does not exist: /lib/firmware/i915/kbl_dmc_ver1_04.bin
ERROR | [i915] Firmware file does not exist: /lib/firmware/i915/skl_dmc_ver1_27.bin
ERROR | [i915] Firmware file does not exist: /lib/firmware/i915/bxt_dmc_ver1_07.bin
WARNING | [iwlwifi] Failed to process autodetected kernel module dependencies: [iwlwifi] Modinfo returned no output.
WARNING | [igc] Failed to process autodetected kernel module dependencies: [igc] Modinfo returned no output.
WARNING | [snd_sof_pci_intel_cnl] Failed to process autodetected kernel module dependencies: [snd_sof_pci_intel_cnl] Modinfo returned no output.
WARNING | [snd_soc_avs] Failed to process autodetected kernel module dependencies: [snd_soc_avs] Modinfo returned no output.
WARNING | [handle_usr_symlinks] Skipping /usr merg
|
Those
Code: |
ERROR | [i915] Firmware file does not exist:
|
errors are accurate...because the firmware is compressed with .zst as the file extension.
Code: |
ls /lib/firmware/i915/
adlp_dmc.bin.zst bxt_dmc_ver1.bin.zst cml_guc_49.0.1.bin.zst dg1_huc_7.7.1.bin.zst ehl_guc_69.0.3.bin.zst icl_dmc_ver1_09.bin.zst kbl_guc_33.0.0.bin.zst mtl_huc_gsc.bin.zst skl_guc_ver1.bin.zst tgl_guc_62.0.0.bin.zst
adlp_dmc_ver2_09.bin.zst bxt_guc_32.0.3.bin.zst cml_guc_62.0.0.bin.zst dg1_huc_7.9.3.bin.zst ehl_guc_70.1.1.bin.zst icl_guc_32.0.3.bin.zst kbl_guc_49.0.1.bin.zst rkl_dmc_ver2_02.bin.zst skl_guc_ver4.bin.zst tgl_guc_69.0.3.bin.zst
adlp_dmc_ver2_10.bin.zst bxt_guc_33.0.0.bin.zst cml_guc_69.0.3.bin.zst dg1_huc.bin.zst ehl_huc_9.0.0.bin.zst icl_guc_33.0.0.bin.zst kbl_guc_62.0.0.bin.zst rkl_dmc_ver2_03.bin.zst skl_guc_ver6_1.bin.zst tgl_guc_70.1.1.bin.zst
adlp_dmc_ver2_12.bin.zst bxt_guc_49.0.1.bin.zst cml_guc_70.1.1.bin.zst dg2_dmc_ver2_06.bin.zst glk_dmc_ver1_04.bin.zst icl_guc_49.0.1.bin.zst kbl_guc_69.0.3.bin.zst skl_dmc_ver1_23.bin.zst skl_guc_ver6.bin.zst tgl_guc_70.bin.zst
adlp_dmc_ver2_14.bin.zst bxt_guc_62.0.0.bin.zst cml_huc_4.0.0.bin.zst dg2_dmc_ver2_07.bin.zst glk_guc_32.0.3.bin.zst icl_guc_62.0.0.bin.zst kbl_guc_70.1.1.bin.zst skl_dmc_ver1_26.bin.zst skl_guc_ver9_33.bin.zst tgl_huc_7.0.12.bin.zst
adlp_dmc_ver2_16.bin.zst bxt_guc_69.0.3.bin.zst cnl_dmc_ver1_06.bin.zst dg2_dmc_ver2_08.bin.zst glk_guc_33.0.0.bin.zst icl_guc_69.0.3.bin.zst kbl_guc_ver9_14.bin.zst skl_dmc_ver1_27.bin.zst skl_huc_2.0.0.bin.zst tgl_huc_7.0.3.bin.zst
adlp_guc_62.0.3.bin.zst bxt_guc_70.1.1.bin.zst cnl_dmc_ver1_07.bin.zst dg2_guc_70.1.2.bin.zst glk_guc_49.0.1.bin.zst icl_guc_70.1.1.bin.zst kbl_guc_ver9_39.bin.zst skl_dmc_ver1.bin.zst skl_huc_ver01_07_1398.bin.zst tgl_huc_7.5.0.bin.zst
adlp_guc_69.0.3.bin.zst bxt_guc_ver8_7.bin.zst dg1_dmc_ver2_02.bin.zst dg2_guc_70.4.1.bin.zst glk_guc_62.0.0.bin.zst icl_huc_9.0.0.bin.zst kbl_huc_4.0.0.bin.zst skl_guc_32.0.3.bin.zst tgl_dmc_ver2_04.bin.zst tgl_huc_7.9.3.bin.zst
adlp_guc_70.1.1.bin.zst bxt_guc_ver9_29.bin.zst dg1_guc_49.0.1.bin.zst dg2_guc_70.bin.zst glk_guc_69.0.3.bin.zst icl_huc_ver8_4_3238.bin.zst kbl_huc_ver02_00_1810.bin.zst skl_guc_33.0.0.bin.zst tgl_dmc_ver2_06.bin.zst tgl_huc.bin.zst
adlp_guc_70.bin.zst bxt_huc_2.0.0.bin.zst dg1_guc_62.0.0.bin.zst dg2_huc_gsc.bin.zst glk_guc_70.1.1.bin.zst kbl_dmc_ver1_01.bin.zst mtl_dmc.bin.zst skl_guc_49.0.1.bin.zst tgl_dmc_ver2_08.bin.zst xe2lpd_dmc.bin.zst
adls_dmc_ver2_01.bin.zst bxt_huc_ver01_07_1398.bin.zst dg1_guc_69.0.3.bin.zst ehl_guc_33.0.4.bin.zst glk_huc_4.0.0.bin.zst kbl_dmc_ver1_04.bin.zst mtl_dmc_ver2_10.bin.zst skl_guc_62.0.0.bin.zst tgl_dmc_ver2_12.bin.zst xe3lpd_dmc.bin.zst
bmg_dmc.bin.zst bxt_huc_ver01_8_2893.bin.zst dg1_guc_70.1.1.bin.zst ehl_guc_49.0.1.bin.zst glk_huc_ver03_01_2893.bin.zst kbl_dmc_ver1.bin.zst mtl_gsc_1.bin.zst skl_guc_69.0.3.bin.zst tgl_guc_35.2.0.bin.zst
bxt_dmc_ver1_07.bin.zst cml_guc_33.0.0.bin.zst dg1_guc_70.bin.zst ehl_guc_62.0.0.bin.zst icl_dmc_ver1_07.bin.zst kbl_guc_32.0.3.bin.zst mtl_guc_70.bin.zst skl_guc_70.1.1.bin.zst tgl_guc_49.0.1.bin.zst
|
|
|
Back to top |
|
 |
zen_desu Apprentice

Joined: 25 Oct 2024 Posts: 248
|
Posted: Sun Apr 20, 2025 12:14 am Post subject: |
|
|
alecStewart1 wrote: | zen_desu
Trying things with different kernel source, ugrd doesn't detect compressed firmware, maybe?
Code: |
make LLVM=1 LLVM_IAS=1 LTO_CLANG_THIN=1 LD="ld.lld" AR="llvm-ar" AS="llvm-as" NM="llvm-nm" RANLIB="llvm-ranlib" STRIP="llvm-strip" OBJCOPY="llvm-objcopy" OBJDUMP="llvm-objdump" KLDFLAGS="-fuse-ld=mold -Wl,-O2 -Wl,--sort-common -Wl,--as-needed -Wl,--strip-debug -Wl,--icf=safe -Wl,-z,rewrite-endbr -flto=thin" KCFLAGS="-O2 -march=alderlake -pipe -mno-cldemote -mno-kl -mno-sgx -mno-widekl -mshstk -fstack-protector-strong -fomit-frame-pointer -flto=thin -mllvm=-polly -mllvm=-polly-vectorizer=stripmine -mllvm=-polly-omp-backend=LLVM -mllvm=-polly-parallel -mllvm=-polly-num-threads=9 -mllvm=-polly-scheduling=dynamic -fzero-call-used-regs=used" -j12 install
INSTALL /boot
* Generating AMD CPU Microcode early initramfs image...
* Created temporary directory: /tmp/tmp.tZSfLzjE5g
* Created microcode archive at: /boot/amd-uc.img
* Cleaned up temporary directory: /tmp/tmp.tZSfLzjE5g
* Generating Intel CPU Microcode early initramfs image...
microcode bundle 1: /lib/firmware/intel-ucode/06-97-02
001/001: sig 0x00090672, pf_mask 0x07, 2024-08-01, rev 0x0038, size 225280
sig 0x00090672, pf_mask 0x07, 2024-08-01, rev 0x0038
sig 0x00090675, pf_mask 0x07, 2024-08-01, rev 0x0038
sig 0x000b06f2, pf_mask 0x07, 2024-08-01, rev 0x0038
sig 0x000b06f5, pf_mask 0x07, 2024-08-01, rev 0x0038
sig 0x000b06f6, pf_mask 0x07, 2024-08-01, rev 0x0038
sig 0x000b06f7, pf_mask 0x07, 2024-08-01, rev 0x0038
microcode bundle 2: /lib/firmware/intel-ucode/06-97-05
002/001: sig 0x00090672, pf_mask 0x07, 2024-08-01, rev 0x0038, size 225280
sig 0x00090672, pf_mask 0x07, 2024-08-01, rev 0x0038
sig 0x00090675, pf_mask 0x07, 2024-08-01, rev 0x0038
sig 0x000b06f2, pf_mask 0x07, 2024-08-01, rev 0x0038
sig 0x000b06f5, pf_mask 0x07, 2024-08-01, rev 0x0038
sig 0x000b06f6, pf_mask 0x07, 2024-08-01, rev 0x0038
sig 0x000b06f7, pf_mask 0x07, 2024-08-01, rev 0x0038
selected microcodes:
001/001: sig 0x00090672, pf_mask 0x07, 2024-08-01, rev 0x0038, size 225280
001/001: sig 0x00090675, pf_mask 0x07, 2024-08-01, rev 0x0038, size 225280
001/001: sig 0x000b06f2, pf_mask 0x07, 2024-08-01, rev 0x0038, size 225280
001/001: sig 0x000b06f5, pf_mask 0x07, 2024-08-01, rev 0x0038, size 225280
001/001: sig 0x000b06f6, pf_mask 0x07, 2024-08-01, rev 0x0038, size 225280
001/001: sig 0x000b06f7, pf_mask 0x07, 2024-08-01, rev 0x0038, size 225280
iucode_tool: Writing selected microcodes to: /boot/intel-uc.img
INFO | Processing module: ugrd.base.base
INFO | Processing module: ugrd.base.core
INFO | Processing module: ugrd.fs.mounts
INFO | Adding library path: /usr/lib64
INFO | Processing module: ugrd.base.cmdline
INFO | Processing module: ugrd.base.banner
INFO | Processing module: ugrd.kmod.kmod
INFO | Processing module: ugrd.kmod.standard_mask
INFO | Processing module: ugrd.fs.cpio
INFO | Processing module: ugrd.base.checks
INFO | [kernel_version] Setting from arguments: 6.14.2
INFO | [cpio_rotate] Setting from arguments: False
INFO | [out_file] Setting from arguments: /tmp/installkernel.staging.SC0p9Iq/initrd
INFO | Resolved out_dir to: /tmp/installkernel.staging.SC0p9Iq
INFO | Loading config file: /etc/ugrd/config.toml
INFO | Resolved out_dir to: /tmp/installkernel.staging.SC0p9Iq
INFO | -- | Running ugrd v2.0.0
INFO | -- | Running build tasks
INFO | Detected init at: /sbin/init
INFO | Source path for libgcc_s: /usr/lib/gcc/x86_64-pc-linux-gnu/14/libgcc_s.so.1
INFO | Using default shell: /bin/sh
WARNING | Virtual block devices unavailable, disabling device mapper autodetection.
INFO | [/dev/nvme0n1p3] Auto-enabling kernel modules for device: nvme
INFO | [/dev/nvme0n1p3] Autodetected mount type from device: btrfs
INFO | [root] Autodetected mount source: uuid=963bf518-69b3-41af-8366-617ba5aa3ef5
INFO | [mounts] Updating mount: root
INFO | Auto-enabling module: btrfs
INFO | Processing module: ugrd.fs.btrfs
WARNING | [get_kernel_version] Kernel version is already set, skipping.
INFO | Autodetected kernel modules: nvme, intel_vsec, xe, snd_sof_pci_intel_tgl, i915, snd_hda_intel, amdgpu, iwlwifi, igc, mei_me, snd_sof_pci_intel_cnl, snd_soc_avs
WARNING | Cleaning build directory: /tmp/initramfs_build
INFO | Processing module: ugrd.kmod.novideo
INFO | Processing module: ugrd.kmod.nosound
INFO | Processing module: ugrd.kmod.nonetwork
INFO | Setting shebang to: #!/bin/sh -l
WARNING | [snd_sof_pci_intel_tgl] Failed to process autodetected kernel module dependencies: [snd_sof_pci_intel_tgl] Modinfo returned no output.
ERROR | [i915] Firmware file does not exist: /lib/firmware/i915/mtl_guc_70.bin
ERROR | [i915] Firmware file does not exist: /lib/firmware/i915/dg2_guc_70.bin
ERROR | [i915] Firmware file does not exist: /lib/firmware/i915/adlp_guc_70.bin
ERROR | [i915] Firmware file does not exist: /lib/firmware/i915/adlp_guc_70.1.1.bin
ERROR | [i915] Firmware file does not exist: /lib/firmware/i915/adlp_guc_69.0.3.bin
ERROR | [i915] Firmware file does not exist: /lib/firmware/i915/tgl_guc_70.bin
ERROR | [i915] Firmware file does not exist: /lib/firmware/i915/tgl_guc_70.1.1.bin
ERROR | [i915] Firmware file does not exist: /lib/firmware/i915/tgl_guc_69.0.3.bin
ERROR | [i915] Firmware file does not exist: /lib/firmware/i915/dg1_guc_70.bin
ERROR | [i915] Firmware file does not exist: /lib/firmware/i915/tgl_guc_70.1.1.bin
ERROR | [i915] Firmware file does not exist: /lib/firmware/i915/tgl_guc_70.1.1.bin
ERROR | [i915] Firmware file does not exist: /lib/firmware/i915/ehl_guc_70.1.1.bin
ERROR | [i915] Firmware file does not exist: /lib/firmware/i915/ehl_guc_70.1.1.bin
ERROR | [i915] Firmware file does not exist: /lib/firmware/i915/icl_guc_70.1.1.bin
ERROR | [i915] Firmware file does not exist: /lib/firmware/i915/cml_guc_70.1.1.bin
ERROR | [i915] Firmware file does not exist: /lib/firmware/i915/kbl_guc_70.1.1.bin
ERROR | [i915] Firmware file does not exist: /lib/firmware/i915/kbl_guc_70.1.1.bin
ERROR | [i915] Firmware file does not exist: /lib/firmware/i915/glk_guc_70.1.1.bin
ERROR | [i915] Firmware file does not exist: /lib/firmware/i915/kbl_guc_70.1.1.bin
ERROR | [i915] Firmware file does not exist: /lib/firmware/i915/bxt_guc_70.1.1.bin
ERROR | [i915] Firmware file does not exist: /lib/firmware/i915/skl_guc_70.1.1.bin
ERROR | [i915] Firmware file does not exist: /lib/firmware/i915/mtl_huc_gsc.bin
ERROR | [i915] Firmware file does not exist: /lib/firmware/i915/dg2_huc_gsc.bin
ERROR | [i915] Firmware file does not exist: /lib/firmware/i915/tgl_huc.bin
ERROR | [i915] Firmware file does not exist: /lib/firmware/i915/tgl_huc_7.9.3.bin
ERROR | [i915] Firmware file does not exist: /lib/firmware/i915/tgl_huc.bin
ERROR | [i915] Firmware file does not exist: /lib/firmware/i915/tgl_huc_7.9.3.bin
ERROR | [i915] Firmware file does not exist: /lib/firmware/i915/dg1_huc.bin
ERROR | [i915] Firmware file does not exist: /lib/firmware/i915/tgl_huc_7.9.3.bin
ERROR | [i915] Firmware file does not exist: /lib/firmware/i915/tgl_huc_7.9.3.bin
ERROR | [i915] Firmware file does not exist: /lib/firmware/i915/ehl_huc_9.0.0.bin
ERROR | [i915] Firmware file does not exist: /lib/firmware/i915/ehl_huc_9.0.0.bin
ERROR | [i915] Firmware file does not exist: /lib/firmware/i915/icl_huc_9.0.0.bin
ERROR | [i915] Firmware file does not exist: /lib/firmware/i915/cml_huc_4.0.0.bin
ERROR | [i915] Firmware file does not exist: /lib/firmware/i915/kbl_huc_4.0.0.bin
ERROR | [i915] Firmware file does not exist: /lib/firmware/i915/kbl_huc_4.0.0.bin
ERROR | [i915] Firmware file does not exist: /lib/firmware/i915/glk_huc_4.0.0.bin
ERROR | [i915] Firmware file does not exist: /lib/firmware/i915/kbl_huc_4.0.0.bin
ERROR | [i915] Firmware file does not exist: /lib/firmware/i915/bxt_huc_2.0.0.bin
ERROR | [i915] Firmware file does not exist: /lib/firmware/i915/skl_huc_2.0.0.bin
ERROR | [i915] Firmware file does not exist: /lib/firmware/i915/mtl_gsc_1.bin
ERROR | [i915] Firmware file does not exist: /lib/firmware/i915/xe3lpd_dmc.bin
ERROR | [i915] Firmware file does not exist: /lib/firmware/i915/xe2lpd_dmc.bin
ERROR | [i915] Firmware file does not exist: /lib/firmware/i915/bmg_dmc.bin
ERROR | [i915] Firmware file does not exist: /lib/firmware/i915/mtl_dmc.bin
ERROR | [i915] Firmware file does not exist: /lib/firmware/i915/dg2_dmc_ver2_08.bin
ERROR | [i915] Firmware file does not exist: /lib/firmware/i915/adlp_dmc.bin
ERROR | [i915] Firmware file does not exist: /lib/firmware/i915/adlp_dmc_ver2_16.bin
ERROR | [i915] Firmware file does not exist: /lib/firmware/i915/adls_dmc_ver2_01.bin
ERROR | [i915] Firmware file does not exist: /lib/firmware/i915/dg1_dmc_ver2_02.bin
ERROR | [i915] Firmware file does not exist: /lib/firmware/i915/rkl_dmc_ver2_03.bin
ERROR | [i915] Firmware file does not exist: /lib/firmware/i915/tgl_dmc_ver2_12.bin
ERROR | [i915] Firmware file does not exist: /lib/firmware/i915/icl_dmc_ver1_09.bin
ERROR | [i915] Firmware file does not exist: /lib/firmware/i915/glk_dmc_ver1_04.bin
ERROR | [i915] Firmware file does not exist: /lib/firmware/i915/kbl_dmc_ver1_04.bin
ERROR | [i915] Firmware file does not exist: /lib/firmware/i915/skl_dmc_ver1_27.bin
ERROR | [i915] Firmware file does not exist: /lib/firmware/i915/bxt_dmc_ver1_07.bin
WARNING | [iwlwifi] Failed to process autodetected kernel module dependencies: [iwlwifi] Modinfo returned no output.
WARNING | [igc] Failed to process autodetected kernel module dependencies: [igc] Modinfo returned no output.
WARNING | [snd_sof_pci_intel_cnl] Failed to process autodetected kernel module dependencies: [snd_sof_pci_intel_cnl] Modinfo returned no output.
WARNING | [snd_soc_avs] Failed to process autodetected kernel module dependencies: [snd_soc_avs] Modinfo returned no output.
WARNING | [handle_usr_symlinks] Skipping /usr merg
|
Those
Code: |
ERROR | [i915] Firmware file does not exist:
|
errors are accurate...because the firmware is compressed with .zst as the file extension.
Code: |
ls /lib/firmware/i915/
adlp_dmc.bin.zst bxt_dmc_ver1.bin.zst cml_guc_49.0.1.bin.zst dg1_huc_7.7.1.bin.zst ehl_guc_69.0.3.bin.zst icl_dmc_ver1_09.bin.zst kbl_guc_33.0.0.bin.zst mtl_huc_gsc.bin.zst skl_guc_ver1.bin.zst tgl_guc_62.0.0.bin.zst
adlp_dmc_ver2_09.bin.zst bxt_guc_32.0.3.bin.zst cml_guc_62.0.0.bin.zst dg1_huc_7.9.3.bin.zst ehl_guc_70.1.1.bin.zst icl_guc_32.0.3.bin.zst kbl_guc_49.0.1.bin.zst rkl_dmc_ver2_02.bin.zst skl_guc_ver4.bin.zst tgl_guc_69.0.3.bin.zst
adlp_dmc_ver2_10.bin.zst bxt_guc_33.0.0.bin.zst cml_guc_69.0.3.bin.zst dg1_huc.bin.zst ehl_huc_9.0.0.bin.zst icl_guc_33.0.0.bin.zst kbl_guc_62.0.0.bin.zst rkl_dmc_ver2_03.bin.zst skl_guc_ver6_1.bin.zst tgl_guc_70.1.1.bin.zst
adlp_dmc_ver2_12.bin.zst bxt_guc_49.0.1.bin.zst cml_guc_70.1.1.bin.zst dg2_dmc_ver2_06.bin.zst glk_dmc_ver1_04.bin.zst icl_guc_49.0.1.bin.zst kbl_guc_69.0.3.bin.zst skl_dmc_ver1_23.bin.zst skl_guc_ver6.bin.zst tgl_guc_70.bin.zst
adlp_dmc_ver2_14.bin.zst bxt_guc_62.0.0.bin.zst cml_huc_4.0.0.bin.zst dg2_dmc_ver2_07.bin.zst glk_guc_32.0.3.bin.zst icl_guc_62.0.0.bin.zst kbl_guc_70.1.1.bin.zst skl_dmc_ver1_26.bin.zst skl_guc_ver9_33.bin.zst tgl_huc_7.0.12.bin.zst
adlp_dmc_ver2_16.bin.zst bxt_guc_69.0.3.bin.zst cnl_dmc_ver1_06.bin.zst dg2_dmc_ver2_08.bin.zst glk_guc_33.0.0.bin.zst icl_guc_69.0.3.bin.zst kbl_guc_ver9_14.bin.zst skl_dmc_ver1_27.bin.zst skl_huc_2.0.0.bin.zst tgl_huc_7.0.3.bin.zst
adlp_guc_62.0.3.bin.zst bxt_guc_70.1.1.bin.zst cnl_dmc_ver1_07.bin.zst dg2_guc_70.1.2.bin.zst glk_guc_49.0.1.bin.zst icl_guc_70.1.1.bin.zst kbl_guc_ver9_39.bin.zst skl_dmc_ver1.bin.zst skl_huc_ver01_07_1398.bin.zst tgl_huc_7.5.0.bin.zst
adlp_guc_69.0.3.bin.zst bxt_guc_ver8_7.bin.zst dg1_dmc_ver2_02.bin.zst dg2_guc_70.4.1.bin.zst glk_guc_62.0.0.bin.zst icl_huc_9.0.0.bin.zst kbl_huc_4.0.0.bin.zst skl_guc_32.0.3.bin.zst tgl_dmc_ver2_04.bin.zst tgl_huc_7.9.3.bin.zst
adlp_guc_70.1.1.bin.zst bxt_guc_ver9_29.bin.zst dg1_guc_49.0.1.bin.zst dg2_guc_70.bin.zst glk_guc_69.0.3.bin.zst icl_huc_ver8_4_3238.bin.zst kbl_huc_ver02_00_1810.bin.zst skl_guc_33.0.0.bin.zst tgl_dmc_ver2_06.bin.zst tgl_huc.bin.zst
adlp_guc_70.bin.zst bxt_huc_2.0.0.bin.zst dg1_guc_62.0.0.bin.zst dg2_huc_gsc.bin.zst glk_guc_70.1.1.bin.zst kbl_dmc_ver1_01.bin.zst mtl_dmc.bin.zst skl_guc_49.0.1.bin.zst tgl_dmc_ver2_08.bin.zst xe2lpd_dmc.bin.zst
adls_dmc_ver2_01.bin.zst bxt_huc_ver01_07_1398.bin.zst dg1_guc_69.0.3.bin.zst ehl_guc_33.0.4.bin.zst glk_huc_4.0.0.bin.zst kbl_dmc_ver1_04.bin.zst mtl_dmc_ver2_10.bin.zst skl_guc_62.0.0.bin.zst tgl_dmc_ver2_12.bin.zst xe3lpd_dmc.bin.zst
bmg_dmc.bin.zst bxt_huc_ver01_8_2893.bin.zst dg1_guc_70.1.1.bin.zst ehl_guc_49.0.1.bin.zst glk_huc_ver03_01_2893.bin.zst kbl_dmc_ver1.bin.zst mtl_gsc_1.bin.zst skl_guc_69.0.3.bin.zst tgl_guc_35.2.0.bin.zst
bxt_dmc_ver1_07.bin.zst cml_guc_33.0.0.bin.zst dg1_guc_70.bin.zst ehl_guc_62.0.0.bin.zst icl_dmc_ver1_07.bin.zst kbl_guc_32.0.3.bin.zst mtl_guc_70.bin.zst skl_guc_70.1.1.bin.zst tgl_guc_49.0.1.bin.zst
|
|
Correct, not a huge blocker but small annoyance, `modinfo` doesn't return the filename with compression, so using that path info, you won't find anything.
If this is something you care about, I can try to work it in. I'd recommend just keeping the modules uncompressed on disk (if you have filesystem compression).
In 99% of cases, no kmod firmware is needed to boot. You can/should avoid including modules/firmware into the initramfs unless they are required to boot. It's not the end of the world if those end up in the initrd, but it's essentially needless duplication.
I generally avoid including GPU drivers, as the EFI Framebuffer is sufficient. Are you entirely sure you need the GPU for any sort of video output?
Another thing of note is that the kmod detection uses current into. Looking at that output, it seems a lot of the modules currently in use are not listed in the module info of the target kernel. Usually this stuff should report as builtin, so looking at that, it seems you may be missing config for several pieces of your hardware in your kernel config. _________________ µgRD dev
Wiki writer |
|
Back to top |
|
 |
alecStewart1 Apprentice

Joined: 03 Jul 2022 Posts: 239
|
Posted: Sun Apr 20, 2025 1:24 am Post subject: |
|
|
zen_desu wrote: |
Correct, not a huge blocker but small annoyance, `modinfo` doesn't return the filename with compression, so using that path info, you won't find anything.
If this is something you care about, I can try to work it in. I'd recommend just keeping the modules uncompressed on disk (if you have filesystem compression).
In 99% of cases, no kmod firmware is needed to boot. You can/should avoid including modules/firmware into the initramfs unless they are required to boot. It's not the end of the world if those end up in the initrd, but it's essentially needless duplication.
I generally avoid including GPU drivers, as the EFI Framebuffer is sufficient. Are you entirely sure you need the GPU for any sort of video output?
Another thing of note is that the kmod detection uses current into. Looking at that output, it seems a lot of the modules currently in use are not listed in the module info of the target kernel. Usually this stuff should report as builtin, so looking at that, it seems you may be missing config for several pieces of your hardware in your kernel config. |
Ah got it. Appreciate the response. Back into menuconfig I go... |
|
Back to top |
|
 |
pingtoo Veteran


Joined: 10 Sep 2021 Posts: 1640 Location: Richmond Hill, Canada
|
Posted: Sun Apr 20, 2025 11:06 am Post subject: |
|
|
One more thing I like to point out, you could take out the word "quiet" from your kernel command line argument. May be for debug increase kernel log level to more verbose by add "loglevel=7" to kernel command line.
Just in case it is graphic card issue add "nomodeset" to kernel command line for last resort. |
|
Back to top |
|
 |
alecStewart1 Apprentice

Joined: 03 Jul 2022 Posts: 239
|
Posted: Mon Apr 21, 2025 12:16 am Post subject: |
|
|
Alright, I'm beginning to feel like I'm wasting my time at this point and should just go initramfs-less.
I have the following from efibootmgr
Code: |
BootCurrent: 0001
Timeout: 0 seconds
BootOrder: 01FE,01FF,0000,0001
Boot0000* Gentoo 6.14.2 (CachyOS Kernel, test) HD(1,GPT,d5d977e1-f515-574f-8949-caf8f2c41559,0x800,0x80000)/\EFI\BOOT\BOOTx64.EFI root=UUID=963bf518-69b3-41af-8366-617ba5aa3ef5 ro init_on_alloc=1 init_on_free=1 spectre_v2=on spec_store_bypass_disable=seccomp randomize_kstack_offset=on random.trust_cpu=off pti=on page_poison=1 page_alloc.shuffle=1 hardened_usercopy=1 mce=0 vsyscall=none rng_core.default_quality=512 apparmor=1 security=apparmor lsm=landlock,lockdown,yama,loadpin,safesetid,smack,tomoyo,apparmor,ipe,bpf driver=free amdgpu.modeset=1 video=DP-1:2560x1440@165 zswap.enabled=1 zswap.compressor=zstd zswap.zpool=zsmalloc zswap.max_pool_percent=15 initrd=\EFI\BOOT\amd-uc.img initrd=\EFI\BOOT\intel-uc.img initrd=initramfs.cpio
Boot0001* UEFI: Patriot Memory PMAP, Partition 2 PciRoot(0x0)/Pci(0x14,0x0)/USB(10,0)/HD(2,GPT,3c14bf9d-d220-4e30-9902-40b3f5d1d6eb,0x23c,0x1680)
Boot01FE* UMC 1 Gentoo Linux 6.14.2 HD(1,GPT,d5d977e1-f515-574f-8949-caf8f2c41559,0x800,0x80000)/\EFI\Gentoo\vmlinuz-6.14.2.efi ro quiet init_on_alloc=1 init_on_free=1 spectre_v2=on spec_store_bypass_disable=seccomp randomize_kstack_offset=on random.trust_cpu=off pti=on page_poison=1 page_alloc.shuffle=1 hardened_usercopy=1 mce=0 vsyscall=none rng_core.default_quality=512 apparmor=1 security=apparmor lsm=landlock,lockdown,yama,loadpin,safesetid,smack,tomoyo,apparmor,ipe,bpf driver=free amdgpu.modeset=1 video=DP-1:2560x1440@165 zswap.enabled=1 zswap.compressor=zstd zswap.zpool=zsmalloc zswap.max_pool_percent=15 initrd=\EFI\Gentoo\amd-uc.img initrd=\EFI\Gentoo\intel-uc.img initrd=\EFI\Gentoo\initramfs-6.14.2.img
Boot01FF* UMC 2 Gentoo Linux 6.13.2 HD(1,GPT,d5d977e1-f515-574f-8949-caf8f2c41559,0x800,0x80000)/\EFI\Gentoo\vmlinuz-6.13.2.efi ro quiet init_on_alloc=1 init_on_free=1 spectre_v2=on spec_store_bypass_disable=seccomp randomize_kstack_offset=on random.trust_cpu=off pti=on page_poison=1 page_alloc.shuffle=1 hardened_usercopy=1 mce=0 vsyscall=none rng_core.default_quality=512 apparmor=1 security=apparmor lsm=landlock,lockdown,yama,loadpin,safesetid,smack,tomoyo,apparmor,ipe,bpf driver=free amdgpu.modeset=1 video=DP-1:2560x1440@165 zswap.enabled=1 zswap.compressor=zstd zswap.zpool=zsmalloc zswap.max_pool_percent=15 initrd=\EFI\Gentoo\amd-uc.img initrd=\EFI\Gentoo\intel-uc.img initrd=\EFI\Gentoo\initramfs-6.13.2.img
|
Let's go in order.
Boot0000 is an entry I manually made, and uses cachyos-sources from gentoo-zh. All the files in this entry I moved into the respected paths. It compiles fine, ugrd reports no warnings about missing modinfo or modules or whatever, so in theory it should work. This entry, when I select it in the EFI boot menu just kicks me back to the EFI Boot menu.
Okay next one down is the LiveGUI USB, so that's nothing to worry about.
Boot1FE is the EFI entry of cachyos-sources, but it's EFI entry installkernel + uefi-mkconfig creates. That takes me to a blank black screen, I hear my computer fans start to speed up like they're doing something and then...nothing. Still a blank black screen.
Boot01FF is what was created from xanmod-kernel from gentoo-zh. Selecting it just takes to the blank black screen, no fans spinning up or anything like the previous entry.
Here are the diffs between the configs files for all of these kernels compared to gentoo-kernel-bin, which works every single time.
(Yes, the gentoo-kernel-bin isn't in the efibootmgr output, as I deleted the entry.)
gentoo-kernel-bin -> cachyos-sources
diff -Naru /usr/src/linux-6.14.2-gentoo-dist/.config /usr/src/linux-6.14.2-cachyos/.config
gentoo-kernel-bin -> xanmod-kernel
diff -Naru /usr/src/linux-6.14.2-gentoo-dist/.config /etc/portage/savedconfig/sys-kernel/xanmod-kernel-6.13.2
I'm going to remove quiet from /etc/default/uefi-mkconfig kernel cmdline bit and retry one of the entries that give a blank black screen.
After that, I'm just sticking with gentoo-kernel-bin for now. I'm getting really tired of configuring for the past 3-4 days only for it to not work. My sound still doesn't work, but at least I can boot into a kernel and get a GUI. Maybe going without an initramfs would fix this, but I don't feel like thinking about that at the moment. At one point things were working, now they aren't. That's all I know at this point. |
|
Back to top |
|
 |
zen_desu Apprentice

Joined: 25 Oct 2024 Posts: 248
|
Posted: Mon Apr 21, 2025 12:19 am Post subject: |
|
|
the initramfs should not have much of an impact on sound/video unless the initramfs is failing to properly load those drivers, and leaves things in a broken state. This is unlikely, especially if the initramfs doesn't attempt to load/init those modules/drivers.
Once the initramfs has completed, it should be about equivalent to how the system would be if you booted it using root= with no initramfs.
I think the key here is kernel config, which as you've seen, is not easy and a bit more of an art than a science. _________________ µgRD dev
Wiki writer |
|
Back to top |
|
 |
alecStewart1 Apprentice

Joined: 03 Jul 2022 Posts: 239
|
Posted: Mon Apr 21, 2025 12:40 am Post subject: |
|
|
zen_desu wrote: | the initramfs should not have much of an impact on sound/video unless the initramfs is failing to properly load those drivers, and leaves things in a broken state. This is unlikely, especially if the initramfs doesn't attempt to load/init those modules/drivers.
|
No, the initramfs is definitely not the issue. It's another "it was working and now it isn't" ordeal. At some point, sound through my card to displayport was working fine. I didn't have to touch anything once it was working, and now it isn't.
zen_desu wrote: |
I think the key here is kernel config, which as you've seen, is not easy and a bit more of an art than a science.
|
There's got to be something I'm marking as <*> when it should be <M>, or vice versa.
As of not, booting without quiet and with nomodeset, I see the following when the cachyos-source kernel boots in:
Code: |
EFI stub: Loaded initrd from command line option
EFI stub: Measured initrd data in PCR 9
|
And it just hangs there indefinitely until I shutdown the computer.
EDIT:
Here's something I've found in one of my diffs:
Code: |
-CONFIG_ACPI_VIDEO=m
+CONFIG_ACPI_VIDEO=y
|
So in gentoo-kernel-bin, CONFIG_ACPI_VIDEO is set to <M> and not <*>. Maybe something of note?
Last edited by alecStewart1 on Mon Apr 21, 2025 12:48 am; edited 1 time in total |
|
Back to top |
|
 |
zen_desu Apprentice

Joined: 25 Oct 2024 Posts: 248
|
Posted: Mon Apr 21, 2025 12:43 am Post subject: |
|
|
alecStewart1 wrote: | zen_desu wrote: | the initramfs should not have much of an impact on sound/video unless the initramfs is failing to properly load those drivers, and leaves things in a broken state. This is unlikely, especially if the initramfs doesn't attempt to load/init those modules/drivers.
|
No, the initramfs is definitely not the issue. It's another "it was working and now it isn't" ordeal. At some point, sound through my card to displayport was working fine. I didn't have to touch anything once it was working, and now it isn't.
zen_desu wrote: |
I think the key here is kernel config, which as you've seen, is not easy and a bit more of an art than a science.
|
There's got to be something I'm marking as <*> when it should be <M>, or vice versa.
As of not, booting without quiet and with nomodeset, I see the following when the cachyos-source kernel boots in:
Code: |
EFI stub: Loaded initrd from command line option
EFI stub: Measured initrd data in PCR 9
|
And it just hangs there indefinitely until I shutdown the computer. |
If you can't see it do anything, the safest assumption is there was a kernel panic or at least something is hanging.
I'd try to make things modules first, if possible, then build them in. You can use modinfo to see if something reports needing firmware. _________________ µgRD dev
Wiki writer |
|
Back to top |
|
 |
pingtoo Veteran


Joined: 10 Sep 2021 Posts: 1640 Location: Richmond Hill, Canada
|
Posted: Mon Apr 21, 2025 12:45 am Post subject: |
|
|
What about all the other entires? |
|
Back to top |
|
 |
alecStewart1 Apprentice

Joined: 03 Jul 2022 Posts: 239
|
Posted: Mon Apr 21, 2025 12:50 am Post subject: |
|
|
pingtoo wrote: | What about all the other entires? |
For
Code: |
Boot0000* Gentoo 6.14.2 (CachyOS Kernel, test) HD(1,GPT,d5d977e1-f515-574f-8949-caf8f2c41559,0x800,0x80000)/\EFI\BOOT\BOOTx64.EFI root=UUID=963bf518-69b3-41af-8366-617ba5aa3ef5 ro init_on_alloc=1 init_on_free=1 spectre_v2=on spec_store_bypass_disable=seccomp randomize_kstack_offset=on random.trust_cpu=off pti=on page_poison=1 page_alloc.shuffle=1 hardened_usercopy=1 mce=0 vsyscall=none rng_core.default_quality=512 apparmor=1 security=apparmor lsm=landlock,lockdown,yama,loadpin,safesetid,smack,tomoyo,apparmor,ipe,bpf driver=free amdgpu.modeset=1 video=DP-1:2560x1440@165 zswap.enabled=1 zswap.compressor=zstd zswap.zpool=zsmalloc zswap.max_pool_percent=15 initrd=\EFI\BOOT\amd-uc.img initrd=\EFI\BOOT\intel-uc.img initrd=initramfs.cpio
|
It just kicked me back to the EFI boot menu.
The xanmod entry:
Code: |
Boot01FF* UMC 2 Gentoo Linux 6.13.2 HD(1,GPT,d5d977e1-f515-574f-8949-caf8f2c41559,0x800,0x80000)/\EFI\Gentoo\vmlinuz-6.13.2.efi ro quiet init_on_alloc=1 init_on_free=1 spectre_v2=on spec_store_bypass_disable=seccomp randomize_kstack_offset=on random.trust_cpu=off pti=on page_poison=1 page_alloc.shuffle=1 hardened_usercopy=1 mce=0 vsyscall=none rng_core.default_quality=512 apparmor=1 security=apparmor lsm=landlock,lockdown,yama,loadpin,safesetid,smack,tomoyo,apparmor,ipe,bpf driver=free amdgpu.modeset=1 video=DP-1:2560x1440@165 zswap.enabled=1 zswap.compressor=zstd zswap.zpool=zsmalloc zswap.max_pool_percent=15 initrd=\EFI\Gentoo\amd-uc.img initrd=\EFI\Gentoo\intel-uc.img initrd=\EFI\Gentoo\initramfs-6.13.2.img
|
Did the same thing as the cachyos-sources entry. |
|
Back to top |
|
 |
pingtoo Veteran


Joined: 10 Sep 2021 Posts: 1640 Location: Richmond Hill, Canada
|
Posted: Mon Apr 21, 2025 1:07 am Post subject: |
|
|
Give me a few minutes to prepare a new boot entry.
The idea is similar to pietinger suggested "My" entry except lets take out all the unnecessary command line arguments temporarily and introduce few kernel debug argument to see what happen. I think we will use your custom build kernel for this test. |
|
Back to top |
|
 |
pingtoo Veteran


Joined: 10 Sep 2021 Posts: 1640 Location: Richmond Hill, Canada
|
Posted: Mon Apr 21, 2025 1:32 am Post subject: |
|
|
Here is the command, Code: | efibootmgr -c -d /dev/nvme0n1 -p 1 -L "Debug" -l \EFI\Gentoo\vmlinuz-6.14.2.efi -u "initrd=\EFI\Gentoo\initramfs-6.14.2.img root=UUID=963bf518-69b3-41af-8366-617ba5aa3ef5 S debug nomodeset earlycon=efi loglevel=7" | I am not a X86 machine person, so I never used efibootmgr. I just copy from post in this thread. so if you spot something does not looks right and you know what need to be correct please go ahead, just post your correction after test. (I intentionally skip other CPU firmware patches. CPU default should just work without patch)
This try may not necessary achieve a complete boot but it is in hope we will see kernel boot messages so we can understand how far the boot sequence go. |
|
Back to top |
|
 |
alecStewart1 Apprentice

Joined: 03 Jul 2022 Posts: 239
|
Posted: Mon Apr 21, 2025 2:00 pm Post subject: |
|
|
pingtoo wrote: | Here is the command, Code: | efibootmgr -c -d /dev/nvme0n1 -p 1 -L "Debug" -l \EFI\Gentoo\vmlinuz-6.14.2.efi -u "initrd=\EFI\Gentoo\initramfs-6.14.2.img root=UUID=963bf518-69b3-41af-8366-617ba5aa3ef5 S debug nomodeset earlycon=efi loglevel=7" | I am not a X86 machine person, so I never used efibootmgr. I just copy from post in this thread. so if you spot something does not looks right and you know what need to be correct please go ahead, just post your correction after test. (I intentionally skip other CPU firmware patches. CPU default should just work without patch)
This try may not necessary achieve a complete boot but it is in hope we will see kernel boot messages so we can understand how far the boot sequence go. |
Unfortunately that also just gives:
Code: |
EFI stub: Loaded initrd from command line option
EFI stub: Measured initrd data in PCR 9
|
And hangs indefinitely.
Time for me to look at the diffs I posted earlier, I guess. |
|
Back to top |
|
 |
zen_desu Apprentice

Joined: 25 Oct 2024 Posts: 248
|
Posted: Mon Apr 21, 2025 5:24 pm Post subject: |
|
|
It's next to impossible to debug a blank screen, I feel your best options to dig deeper are to do testing on a VM where you can attach to the serial interface and see more log info (potentially), or work from a known working kernel to a custom one using very small steps, I'd say no more than 5 or 10 config changes between each reboot. _________________ µgRD dev
Wiki writer |
|
Back to top |
|
 |
pingtoo Veteran


Joined: 10 Sep 2021 Posts: 1640 Location: Richmond Hill, Canada
|
Posted: Mon Apr 21, 2025 5:54 pm Post subject: |
|
|
alecStewart1 wrote: | pingtoo wrote: | Here is the command, Code: | efibootmgr -c -d /dev/nvme0n1 -p 1 -L "Debug" -l \EFI\Gentoo\vmlinuz-6.14.2.efi -u "initrd=\EFI\Gentoo\initramfs-6.14.2.img root=UUID=963bf518-69b3-41af-8366-617ba5aa3ef5 S debug nomodeset earlycon=efi loglevel=7" | I am not a X86 machine person, so I never used efibootmgr. I just copy from post in this thread. so if you spot something does not looks right and you know what need to be correct please go ahead, just post your correction after test. (I intentionally skip other CPU firmware patches. CPU default should just work without patch)
This try may not necessary achieve a complete boot but it is in hope we will see kernel boot messages so we can understand how far the boot sequence go. |
Unfortunately that also just gives:
Code: |
EFI stub: Loaded initrd from command line option
EFI stub: Measured initrd data in PCR 9
|
And hangs indefinitely.
Time for me to look at the diffs I posted earlier, I guess. |
When "EFI stub: ..." show, it mean a efistub kernel loaded and execute by EFI Boot service. so this prove the first part of the kernel file is OK. However from your description it seems to me that rest of kernel file was corrupted, was there any indicator (fans, leds) that show something is going on? (I mean after the two EFI stub: lines)
As zen_desu said, there is not much we can do if all we got is blank screen.
However It is a little bit hard for me to imaging this happen. I feel we missing something in our conversation, so may be you are thinking one way whereas I am asking something else.
Can you share "efibootmgr -u" output so I can see what was setup.
Also if you create yet another new entry but switch the kernel image file to use gentoo dist binary kernel but leave the rest parameters as is, try it to see if you still get blank screen. |
|
Back to top |
|
 |
alecStewart1 Apprentice

Joined: 03 Jul 2022 Posts: 239
|
Posted: Tue Apr 22, 2025 2:29 am Post subject: |
|
|
pingtoo wrote: |
When "EFI stub: ..." show, it mean a efistub kernel loaded and execute by EFI Boot service. so this prove the first part of the kernel file is OK. However from your description it seems to me that rest of kernel file was corrupted, was there any indicator (fans, leds) that show something is going on? (I mean after the two EFI stub: lines)
As zen_desu said, there is not much we can do if all we got is blank screen.
However It is a little bit hard for me to imaging this happen. I feel we missing something in our conversation, so may be you are thinking one way whereas I am asking something else.
Can you share "efibootmgr -u" output so I can see what was setup.
Also if you create yet another new entry but switch the kernel image file to use gentoo dist binary kernel but leave the rest parameters as is, try it to see if you still get blank screen. |
efibootmgr -u
Code: |
BootCurrent: 01FF
Timeout: 0 seconds
BootOrder: 0000,01FE,01FF,0200,0201,0001
Boot0000* Debug HD(1,GPT,d5d977e1-f515-574f-8949-caf8f2c41559,0x800,0x80000)/\EFI\Gentoo\vmlinuz-6.14.2.efi initrd=\EFI\Gentoo\initramfs-6.14.2.img root=UUID=963bf518-69b3-41af-8366-617ba5aa3ef5 S debug nomodeset earlycon=efi loglevel=7
Boot0001* UEFI: Patriot Memory PMAP, Partition 2 PciRoot(0x0)/Pci(0x14,0x0)/USB(10,0)/HD(2,GPT,3c14bf9d-d220-4e30-9902-40b3f5d1d6eb,0x23c,0x1680)
Boot01FE* UMC 1 Gentoo Linux 6.14.3 HD(1,GPT,d5d977e1-f515-574f-8949-caf8f2c41559,0x800,0x80000)/\EFI\Gentoo\vmlinuz-6.14.3-gentoo-dist.efi ro loglevel=8 init_on_alloc=1 init_on_free=1 spectre_v2=on spec_store_bypass_disable=seccomp randomize_kstack_offset=on random.trust_cpu=off pti=on page_poison=1 page_alloc.shuffle=1 hardened_usercopy=1 mce=0 vsyscall=none rng_core.default_quality=512 apparmor=1 security=apparmor lsm=landlock,lockdown,yama,loadpin,safesetid,smack,tomoyo,apparmor,ipe,bpf driver=free amdgpu.modeset=1 video=DP-1:2560x1440@165 zswap.enabled=1 zswap.compressor=zstd zswap.zpool=zsmalloc zswap.max_pool_percent=15 initrd=\EFI\Gentoo\amd-uc.img initrd=\EFI\Gentoo\intel-uc.img initrd=\EFI\Gentoo\initramfs-6.14.3-gentoo-dist.img
Boot01FF* UMC 2 Gentoo Linux 6.14.2 HD(1,GPT,d5d977e1-f515-574f-8949-caf8f2c41559,0x800,0x80000)/\EFI\Gentoo\vmlinuz-6.14.2-gentoo-dist.efi ro loglevel=8 init_on_alloc=1 init_on_free=1 spectre_v2=on spec_store_bypass_disable=seccomp randomize_kstack_offset=on random.trust_cpu=off pti=on page_poison=1 page_alloc.shuffle=1 hardened_usercopy=1 mce=0 vsyscall=none rng_core.default_quality=512 apparmor=1 security=apparmor lsm=landlock,lockdown,yama,loadpin,safesetid,smack,tomoyo,apparmor,ipe,bpf driver=free amdgpu.modeset=1 video=DP-1:2560x1440@165 zswap.enabled=1 zswap.compressor=zstd zswap.zpool=zsmalloc zswap.max_pool_percent=15 initrd=\EFI\Gentoo\amd-uc.img initrd=\EFI\Gentoo\intel-uc.img initrd=\EFI\Gentoo\initramfs-6.14.2-gentoo-dist.img
Boot0200* UMC 3 Gentoo Linux 6.14.2 HD(1,GPT,d5d977e1-f515-574f-8949-caf8f2c41559,0x800,0x80000)/\EFI\Gentoo\vmlinuz-6.14.2.efi ro loglevel=8 init_on_alloc=1 init_on_free=1 spectre_v2=on spec_store_bypass_disable=seccomp randomize_kstack_offset=on random.trust_cpu=off pti=on page_poison=1 page_alloc.shuffle=1 hardened_usercopy=1 mce=0 vsyscall=none rng_core.default_quality=512 apparmor=1 security=apparmor lsm=landlock,lockdown,yama,loadpin,safesetid,smack,tomoyo,apparmor,ipe,bpf driver=free amdgpu.modeset=1 video=DP-1:2560x1440@165 zswap.enabled=1 zswap.compressor=zstd zswap.zpool=zsmalloc zswap.max_pool_percent=15 initrd=\EFI\Gentoo\amd-uc.img initrd=\EFI\Gentoo\intel-uc.img initrd=\EFI\Gentoo\initramfs-6.14.2.img
Boot0201* UEFI OS HD(1,GPT,d5d977e1-f515-574f-8949-caf8f2c41559,0x800,0x80000)/\EFI\BOOT\BOOTX64.EFI
|
I made one entry earlier using the gentoo-kernel-bin kernel image (I got rid of it) and it went through the normal boot process fine. It didn't start a graphical login (sddm is what I use) since nomodeset was in the kernel boot params, but I got a TTY login prompt and I could login to that fine, I just didn't have any graphics besides TTY.
Don't know what to tell you. |
|
Back to top |
|
 |
pingtoo Veteran


Joined: 10 Sep 2021 Posts: 1640 Location: Richmond Hill, Canada
|
Posted: Tue Apr 22, 2025 10:41 am Post subject: |
|
|
Thank you very much for the information.
Here is my train of thoughts, I think something gone wrong during the build of kernel so the binary produce was not usable. Than it is also possible one key configuration not set, therefor nothing show on screen. I believe we need to establish a baseline as reference. we also need to simplified initial objective to make problem space small.
So I propose if we can set out initial objective as getting boot messages display on screen, no matter if we get to login prompt. then this way a narrow focus on build and configuration of kernel should help speed up the diagnostic.
Further I suggest, you create/keep a boot entry using gentoo-kernel-bin kernel image with the simplified kernel command line arguments I suggest in "Boot0000* Debug ..." and boot into this entry to confirm all these kernel command line arguments does allow messages display on screen. So this could be the reference point.
Once having the reference working (as defined by the inital objective) kernel. Let's try to compare the working reference kernel .config with your custom build kernel .config to see diff can be spot on how the default console setup.
Finally review the kernel build process to see if we can first try to use traditional build (gcc based), no special optimization setup, just so we can establish a reference in case I don't know where need to work but someone with more experience can jump in to have a look.
If you think my idea is OK, please let me know I will provide some instructions to establish a context so we can keep in sync. |
|
Back to top |
|
 |
alecStewart1 Apprentice

Joined: 03 Jul 2022 Posts: 239
|
Posted: Sat Apr 26, 2025 4:12 am Post subject: |
|
|
Sorry pingtoo, been a busy week at work.
That all sounds fine. If it helps, here's the following information.
Any compiled kernel on my system doesn't work. All will seemingly crash on booting into the EFI image, and the following message appaears:
Code: |
EFI stub: Loaded initrd from command line option
EFI stub: Measured initrd data in PCR 9
|
And nothing else happens. The gentoo-kernel-bin works.
(Part of me is feeling like this is some issue related to my bootstrapped clang system, but I can't quite state that's the possibility yet.)
Manually build the kernel myself, the cachy-sources kernel from the gentoo-zh and the dist-kernel configuration for kernel version 6.14.3 have the following diff:
http://dpaste.com/CR6LQ79TC
cachyos-sources has the following USE flags enabled:
Code: | asus bbr3 bore clang-polly crypto fixes rt symlink zstd -amd-pstate -amd-tlb-broadcast -aufs -build -deckify -dkms-clang -polly -prjc -t2 |
To manually build the cachyos-sources kernel, I did so with the following commands
Code: |
export LLVM=1 LLVM_IAS=1 LTO_CLANG=1
make LLVM=1 LLVM_IAS=1 LTO_CLANG_THIN=1 CPU_FLAGS_X86="aes avx avx2 f16c fma3 mmx mmxext pclmul popcnt rdrand sha sse sse2 sse3 sse4_1 sse4_2 ssse3 vpclmulqdq" LD="ld.lld" AR="llvm-ar" AS="llvm-as" NM="llvm-nm" RANLIB="llvm-ranlib" STRIP="llvm-strip" OBJCOPY="llvm-objcopy" OBJDUMP="llvm-objdump" KLDFLAGS="-fuse-ld=mold -Wl,-O2 -Wl,--sort-common -Wl,--as-needed -flto=thin -Wl,--strip-debug -Wl,--icf=safe -Wl,-z,rewrite-endbr" KCFLAGS="-O3 -march=alderlake -pipe -mno-cldemote -mno-kl -mno-sgx -mno-widekl -mshstk -fstack-protector-strong -fomit-frame-pointer -flto=thin -mllvm=-polly -fzero-call-used-regs=used" -j12 -d
make -j12 modules_install
make -j12 install
|
My /etc/default/uefi-mkconfig:
Code: |
ENTRY_LABEL_LIMIT=false
KERNEL_CONFIG="%entry_id %linux_name Linux %kernel_version ; ro earlyprintk=efi efi=debug debug loglevel=8 init_on_alloc=1 init_on_free=1 spectre_v2=on spec_store_bypass_disable=seccomp randomize_kstack_offset=on random.trust_cpu=off pti=on page_poison=1 page_alloc.shuffle=1 hardened_usercopy=1 mce=0 vsyscall=none rng_core.default_quality=512 apparmor=1 security=apparmor lsm=landlock,lockdown,yama,loadpin,safesetid,smack,tomoyo,apparmor,ipe,bpf driver=free amdgpu.modeset=1 video=DP-1:2560x1440@165 zswap.enabled=1 zswap.compressor=zstd zswap.zpool=zsmalloc zswap.max_pool_percent=15"
|
My /etc/ugrd/config.toml:
Code: |
# This config will decrypt the LUKS volume with uuid "fdf442da-0574-4531-98c7-55227a041f1d", mapping it to "/dev/mapper/root"
# Note: In most cases, the uuid of the LUKS volume will be detected from the root mount. It's set as an example here.
# It will attempt to mount the btrfs volume with label "rootfs" to /target_rootfs
# It will pull all current kernel modules from lspci -k results
# It will try to process the cmdline and mount the rootfs based on the root= parameter
modules = [
# "ugrd.crypto.cryptsetup", # This is included by the gpg module
# "ugrd.crypto.gpg", # This is included by the smartcard module
# "ugrd.crypto.smartcard",
]
# Mask the parse_cmdline function to prevent it from running
# Can be applied to any function
#mask.init_pre = 'parse_cmdline'
# By default, all kmod categories are ignored. This can be disabled by category
# Modules can define these options if needed, and users should not need to set them
# In most cases, kmods in these categories are not needed to boot the system
#kmod_ignore_video = false
#kmod_ignore_sound = false
#kmod_ignore_network = false
# The initramfs will be built in /tmp/initramfs if "build_dir" is not specified not specified
#out_dir = "/usr/src/initramfs"
#out_dir = "/boot"
# By default, xz compression is used. This can be disabled or set to zstd if the zstandard python module is installed
cpio_compression = "zstd" # Use zstd compression
#cpio_compression = false # No compression
# Optionally supply a kernel version, uses the current kernel version if not specified
#kernel_version = "6.1.53-gentoo-dist"
# lspci based detection is usually helpful
kmod_autodetect_lspci = true
# lsmod detection can be helpful, but can bring in unnecessary modules
#kmod_autodetect_lsmod = true
# If no kernel modules are needed, or installed, no_kmod should be set
#no_kmod = true
# ugrd is designed for merged-usr systems. If using a split-usr system, automatic symlink creation can be disabled:
merge_usr = false
# on systems using glibc in the userspace, libgcc is often required. If it's not necessary, pulling it can be diabled with:
#find_libgcc = false
# By default, ugrd will keep retrying to mount base mounts and the rootfs, unless space is pressed
# The default timeout between attempts is 1s, and the default number of retries is infinite
#mount_timeout = 0.25 # Wait 0.25 seconds between mount attempts, instead of 1s.
#mount_retries = 5 # Retry mounting the rootfs 5 times, if unset, it will retry indefinitely
# The location of the gpg public key, if using a smartcard and gpg encrypted keyfile
#sc_public_key = "/etc/ugrd/pubkey.gpg"
#auto_mounts = ['/boot'] # Automatically create mount config for /boot on the host
# Optionally specify the root mountpoint information manually, it should be detected automatically
# Whatever options are set manually will be validated against the current root mount
#[mounts.root]
# The label of the root filesystem, a uuid or partuuid could be used instead
#label = "rootfs"
# This is necessary if the keyfile is on another device.
# The keyfile could be added as a dependency. if it's on the same device.
#[mounts.boot]
#type = "vfat"
#uuid = "4886-A631"
# If the root is a LUKS volume, specify the LUKS volume information
# The name of the LUKS volume should match the name of the device in /dev/mapper
#[cryptsetup.root]
# The UUID of the encrypted volume, mounted at /dev/mapper/root, should be detected automatically
#uuid = "fdf442da-0574-4531-98c7-55227a041f1d"
# If a GPG encrypted key file is used, the key_type must be set to gpg.
# If using a plain keyfile, this can be left unset.
#key_type = "gpg"
# The key file must either be included as a dependency, or it must be under an external mountpoint.
# Key file under /boot, which is configured as an auto_mount
#key_file = "/boot/rootfs.luks.gpg"
# Key file included as a dependency
#key_file = "/etc/ugrd/rootfs.luks.gpg"
#include_key = true
# If the key file is on storage not accessible to the build system, validation can be disabled:
#validate_key = false
# If using detached headers, the header file can be treated similarly to the key file
#header_file = "/boot/rootfs.luks.header"
#header_file = "/etc/ugrd/rootfs.luks.header"
#include_header = true
#validate_header = false
|
And of course, emerge --info --verbose, just in case:[/code]
http://dpaste.com/BC2YZB6J6 |
|
Back to top |
|
 |
pingtoo Veteran


Joined: 10 Sep 2021 Posts: 1640 Location: Richmond Hill, Canada
|
Posted: Sat Apr 26, 2025 7:32 am Post subject: |
|
|
alecStewart1 wrote: | Sorry pingtoo, been a busy week at work. |
No worries, we all have to attend our life, something just have higher priorities than satisfy curious mind.
I just going to need a moment of two to find the train of thoughts. |
|
Back to top |
|
 |
NeddySeagoon Administrator


Joined: 05 Jul 2003 Posts: 55182 Location: 56N 3W
|
Posted: Sat Apr 26, 2025 11:43 am Post subject: |
|
|
pingtoo,
Either the kernel has panicked before mounting the initrd or the framebuffer driver is in a mess, so there is no video output.
Once the initrd is mounted as root and its init script is in control, errors should drop you to a shell.
That's only useful if you have a console though.
alecStewart1,
Is there any chance of getting a serial console on a real serial port?
Is measured boot or secure boot in use?
They can stop things dead too.
We can try some analysis.
Post your and pastebin your current non working kernel .config file.
Getting a console will be a step in the right direction and that's all I would aim to do, to start with. _________________ Regards,
NeddySeagoon
Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail. |
|
Back to top |
|
 |
pingtoo Veteran


Joined: 10 Sep 2021 Posts: 1640 Location: Richmond Hill, Canada
|
Posted: Sat Apr 26, 2025 1:18 pm Post subject: |
|
|
NeddySeagoon wrote: | pingtoo,
Either the kernel has panicked before mounting the initrd or the framebuffer driver is in a mess, so there is no video output.
Once the initrd is mounted as root and its init script is in control, errors should drop you to a shell.
That's only useful if you have a console though. |
Currently I suspect it is something wrong in the decompress phase of kernel. I know it pass the EFI stub because those "EFI stub: ..." but nothing after so it could be the kernel proper after EFI stub was wrong so decompress failed (or the decompressor code was wrong) |
|
Back to top |
|
 |
|
|
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
|
|