| View previous topic :: View next topic |
| Author |
Message |
pietinger
Moderator
Joined: 17 Oct 2006
Posts: 5649
Location: Bavaria
|
 Posted: Mon Apr 14, 2025 11:33 am Post subject: |
 |
|
alecStewart1,
I had a chat with @zen_desu last night and the question came up whether your system startup is not running at all, or whether you “only” get this error, but your system startup continues to run. If the latter is the case, the (complete) output of dmesg will be able to help us. As far as your kernel is concerned: As soon as it is able to output something on the screen, we have almost everything we need. Because then we would also see a kernel panic or other error messages. But this message comes from the initramfs and that is the last thing the kernel starts (there is no going back from the initramfs to the kernel; the initramfs starts your /sbin/init last). If there were any modules missing in your kernel, we would see that (other error messages). What else can help us: We simply check the “content” of your initramfs - i.e. the init-script. Just do the: https://wiki.gentoo.org/wiki/User:Pietinger/Tutorials/Initramfs_Overview#Inspecting_a_CPIO_file and send it to us via wgetpaste https://wiki.gentoo.org/wiki/Wgetpaste (the same applies to the output of dmesg).
P.S.: At the moment the main difference between "your" kernel and our dist-kernel is: The UEFI-entry for the dist-kernel does not give a "root=..." paramater to the dist-kernel/initramfs. We do. That is the cause I suggested in my last post to do the same ... 
_________________
https://wiki.gentoo.org/wiki/User:Pietinger |
|
| Back to top |
|
 |
alecStewart1
Apprentice
Joined: 03 Jul 2022
Posts: 246
|
| Posted: Mon Apr 14, 2025 11:31 pm Post subject: |
|
|
| zen_desu wrote: | | alecStewart1 wrote: | I do have to keep coming back to this because I feel like it wasn't answered:
Why does gentoo-kernel-bin work, but not the one I've manually built?
I'm fine with investigating ugrd some...but it works with gentoo-kernel-bin. It seems like there's something wrong or missing in my custom config compared to the one provided by gentoo-kernel-bin.
Is this a dumb question? |
Not a dumb question, just real hard to answer without seeing what resolves this.
if you build a kernel with _identical_ config to what is in gentoo-kernel-bin, it should work the same. Something must differ somewhere. |
I have a diff I posted earlier in the thread. It might be hard to figure out what's missing with that, though.
I do have what modules have been loaded by the gentoo-kernel-bin kernel, though:
lspci -nnk | rg 'modules'
| Code: |
Kernel modules: i915, xe
Kernel modules: intel_vsec
Kernel modules: iwlwifi
Kernel modules: mei_me
Kernel modules: snd_hda_intel, snd_soc_avs, snd_sof_pci_intel_tgl
Kernel modules: i2c_i801
Kernel modules: spi_intel_pci
Kernel modules: amdgpu
Kernel modules: snd_hda_intel
Kernel modules: nvme
Kernel modules: igc
|
But also useful:
lsmode | awk '$3 > 0 {print ;}'
| Code: |
Module Size Used by
uhid 20480 1
curve25519_x86_64 32768 1 wireguard
libcurve25519_generic 45056 2 curve25519_x86_64,wireguard
ip6_udp_tunnel 16384 1 wireguard
udp_tunnel 32768 1 wireguard
nft_reject_inet 12288 6
nf_reject_ipv4 12288 1 nft_reject_inet
nf_reject_ipv6 16384 1 nft_reject_inet
nft_reject 12288 1 nft_reject_inet
nft_masq 12288 1
nft_ct 24576 9
nft_chain_nat 12288 1
nf_nat 61440 2 nft_masq,nft_chain_nat
nf_conntrack 180224 3 nf_nat,nft_ct,nft_masq
nf_defrag_ipv6 20480 1 nf_conntrack
nf_defrag_ipv4 12288 1 nf_conntrack
rfcomm 86016 16
snd_hrtimer 12288 1
snd_seq 118784 7 snd_seq_dummy
fuse 245760 2
nf_tables 372736 727 nft_ct,nft_reject_inet,nft_masq,nft_chain_nat,nft_reject
nfnetlink 24576 1 nf_tables
garp 16384 1 8021q
mrp 20480 1 8021q
stp 12288 1 garp
llc 12288 2 stp,garp
libdes 32768 2 des_generic,des3_ede_x86_64
bnep 32768 2
vfat 24576 1
fat 106496 1 vfat
binfmt_misc 24576 1
amdgpu 18190336 33
btrtl 36864 1 btusb
btintel 61440 1 btusb
drm_gpuvm 40960 1 xe
btbcm 20480 1 btusb
btmtk 32768 1 btusb
snd_usb_audio 528384 3
bluetooth 913408 44 btrtl,btmtk,btintel,btbcm,bnep,btusb,rfcomm
snd_usbmidi_lib 53248 1 snd_usb_audio
snd_ump 40960 1 snd_usb_audio
snd_rawmidi 49152 2 snd_usbmidi_lib,snd_ump
snd_seq_device 12288 3 snd_seq,snd_ump,snd_rawmidi
mc 81920 1 snd_usb_audio
usb_storage 86016 1 uas
ff_memless 24576 1 xpad
snd_sof_pci_intel_cnl 24576 1 snd_sof_pci_intel_tgl
snd_sof_intel_hda_generic 36864 2 snd_sof_pci_intel_tgl,snd_sof_pci_intel_cnl
soundwire_intel 77824 1 snd_sof_intel_hda_generic
soundwire_cadence 45056 1 soundwire_intel
snd_sof_intel_hda_common 172032 3 snd_sof_intel_hda_generic,snd_sof_pci_intel_tgl,snd_sof_pci_intel_cnl
snd_soc_hdac_hda 28672 1 snd_sof_intel_hda_common
snd_sof_intel_hda_mlink 32768 3 soundwire_intel,snd_sof_intel_hda_common,snd_sof_intel_hda_generic
intel_rapl_common 49152 1 intel_rapl_msr
snd_sof_intel_hda 20480 2 snd_sof_intel_hda_common,snd_sof_intel_hda_generic
mac80211 1597440 1 iwlmvm
snd_sof_pci 20480 3 snd_sof_intel_hda_generic,snd_sof_pci_intel_tgl,snd_sof_pci_intel_cnl
snd_sof_xtensa_dsp 16384 1 snd_sof_intel_hda_generic
snd_sof 393216 5 snd_sof_pci,snd_sof_intel_hda_common,snd_sof_intel_hda_generic,snd_sof_intel_hda,snd_sof_pci_intel_cnl
intel_uncore_frequency_common 12288 1 intel_uncore_frequency
snd_sof_utils 16384 1 snd_sof
snd_soc_acpi_intel_match 110592 3 snd_sof_intel_hda_generic,snd_sof_pci_intel_tgl,snd_sof_pci_intel_cnl
snd_soc_acpi_intel_sdca_quirks 12288 1 snd_soc_acpi_intel_match
soundwire_generic_allocation 20480 1 soundwire_intel
snd_soc_acpi 16384 2 snd_soc_acpi_intel_match,snd_sof_intel_hda_generic
soundwire_bus 126976 3 soundwire_intel,soundwire_generic_allocation,soundwire_cadence
snd_soc_sdca 12288 2 snd_soc_acpi_intel_sdca_quirks,soundwire_bus
libarc4 12288 1 mac80211
snd_soc_hda_codec 24576 1 snd_soc_avs
snd_hda_ext_core 32768 6 snd_soc_avs,snd_soc_hda_codec,snd_sof_intel_hda_common,snd_soc_hdac_hda,snd_sof_intel_hda_mlink,snd_sof_intel_hda
i915 4620288 2
snd_soc_core 417792 6 snd_soc_avs,snd_soc_hda_codec,soundwire_intel,snd_sof,snd_sof_intel_hda_common,snd_soc_hdac_hda
kvm 1261568 1 kvm_intel
iwlwifi 548864 1 iwlmvm
snd_hda_codec_generic 118784 1
snd_hda_codec_hdmi 86016 1
snd_compress 24576 2 snd_soc_avs,snd_soc_core
amdxcp 12288 1 amdgpu
gpu_sched 57344 2 amdgpu,xe
ac97_bus 12288 1 snd_soc_core
snd_pcm_dmaengine 16384 1 snd_soc_core
drm_panel_backlight_quirks 12288 1 amdgpu
drm_ttm_helper 12288 3 amdgpu,xe
snd_hda_intel 61440 2
ttm 114688 4 amdgpu,drm_ttm_helper,xe,i915
drm_suballoc_helper 12288 2 amdgpu,xe
snd_intel_dspcfg 40960 5 snd_soc_avs,snd_hda_intel,snd_sof,snd_sof_intel_hda_common,snd_sof_intel_hda_generic
drm_client_lib 12288 1 amdgpu
i2c_algo_bit 16384 3 amdgpu,xe,i915
drm_exec 12288 3 drm_gpuvm,amdgpu,xe
snd_intel_sdw_acpi 16384 2 snd_intel_dspcfg,snd_sof_intel_hda_generic
snd_hda_codec 196608 7 snd_hda_codec_generic,snd_soc_avs,snd_hda_codec_hdmi,snd_soc_hda_codec,snd_hda_intel,snd_soc_hdac_hda,snd_sof_intel_hda
drm_display_helper 270336 3 amdgpu,xe,i915
cfg80211 1208320 3 iwlmvm,iwlwifi,mac80211
snd_hda_core 139264 10 snd_hda_codec_generic,snd_soc_avs,snd_hda_codec_hdmi,snd_soc_hda_codec,snd_hda_intel,snd_hda_ext_core,snd_hda_codec,snd_sof_intel_hda_common,
snd_soc_hdac_hda,snd_sof_intel_hda
polyval_generic 12288 1 polyval_clmulni
cec 86016 4 drm_display_helper,amdgpu,xe,i915
mtd 94208 2 spi_nor
snd_hwdep 16384 2 snd_usb_audio,snd_hda_codec
intel_pmc_bxt 12288 1 iTCO_wdt
snd_pcm 172032 14 snd_soc_avs,snd_hda_codec_hdmi,snd_hda_intel,snd_usb_audio,snd_hda_codec,soundwire_intel,snd_sof,snd_sof_intel_hda_common,snd_compress,snd_sof_intel_hda_generic,snd_soc_core,
snd_sof_utils,snd_hda_core,snd_pcm_dmaengine
iTCO_vendor_support 12288 1 iTCO_wdt
drm_kms_helper 221184 6 drm_display_helper,amdgpu,drm_ttm_helper,drm_client_lib,xe,i915
snd_timer 49152 3 snd_seq,snd_hrtimer,snd_pcm
drm_buddy 28672 3 amdgpu,xe,i915
snd 143360 28 snd_hda_codec_generic,snd_seq,snd_seq_device,snd_hda_codec_hdmi,snd_hwdep,snd_hda_intel,snd_usb_audio,snd_usbmidi_lib,snd_hda_codec,snd_sof,snd_timer,snd_compress,
snd_soc_core,snd_ump,snd_pcm,snd_rawmidi
video 73728 3 amdgpu,xe,i915
spi_intel 32768 1 spi_intel_pci
soundcore 12288 1 snd
i2c_smbus 16384 1 i2c_i801
rfkill 36864 5 iwlmvm,bluetooth,cfg80211
pmt_telemetry 12288 1 intel_pmc_core
pmt_class 12288 1 pmt_telemetry
wmi 24576 3 video,wmi_bmof,mxm_wmi
intel_vsec 16384 2 intel_pmc_core,xe
mei_me 49152 2
mei 172032 5 mei_hdcp,mei_pxp,mei_me
nvme 65536 3
nvme_core 217088 4 nvme
nvme_auth 24576 1 nvme_core
|
So maybe that narrows things down a little bit...maybe?
Mod edit: Long lines split to preserve Forum formatting. — JRG |
|
| Back to top |
|
|
zen_desu
Apprentice
Joined: 25 Oct 2024
Posts: 251
|
| Posted: Tue Apr 15, 2025 12:01 am Post subject: |
|
|
If you have qemu installed, could you run `ugrd --test` using the latest dev branch?
You should be able to change between kernel versions with `--kver` to cleanly run the test with different kernels.
You should see something like this:
https://bpa.st/raw/BSDQ
The output may clear your terminal, you can log to a file setting "--log-file" so like `ugrd --test --log-file out.log`
One small but noteworthy change is that it now waits for the user to press space instead of enter.
I've got automated testing ensuring it should print debug info and restart on mount failures now.
_________________
µgRD dev
Wiki writer |
|
| Back to top |
|
|
alecStewart1
Apprentice
Joined: 03 Jul 2022
Posts: 246
|
| Posted: Tue Apr 15, 2025 12:28 am Post subject: |
|
|
| zen_desu wrote: | If you have qemu installed, could you run `ugrd --test` using the latest dev branch?
You should be able to change between kernel versions with `--kver` to cleanly run the test with different kernels.
You should see something like this:
https://bpa.st/raw/BSDQ
The output may clear your terminal, you can log to a file setting "--log-file" so like `ugrd --test --log-file out.log`
One small but noteworthy change is that it now waits for the user to press space instead of enter.
I've got automated testing ensuring it should print debug info and restart on mount failures now. |
Unfortunately I do not have qemu. I'll give it shot...once I build with python3.11 again, because zstandard doesn't build with python3.13 or python3.12. |
|
| Back to top |
|
|
zen_desu
Apprentice
Joined: 25 Oct 2024
Posts: 251
|
| Posted: Tue Apr 15, 2025 2:00 am Post subject: |
|
|
| alecStewart1 wrote: | | zen_desu wrote: | If you have qemu installed, could you run `ugrd --test` using the latest dev branch?
You should be able to change between kernel versions with `--kver` to cleanly run the test with different kernels.
You should see something like this:
https://bpa.st/raw/BSDQ
The output may clear your terminal, you can log to a file setting "--log-file" so like `ugrd --test --log-file out.log`
One small but noteworthy change is that it now waits for the user to press space instead of enter.
I've got automated testing ensuring it should print debug info and restart on mount failures now. |
Unfortunately I do not have qemu. I'll give it shot...once I build with python3.11 again, because zstandard doesn't build with python3.13 or python3.12. |
Are you sure your build system is functioning properly, I have it on 3.12:
| Code: |
[binary R ] dev-python/zstandard-0.23.0-r1-1::gentoo USE="-debug -test" PYTHON_TARGETS="python3_12 (-pypy3) (-pypy3_11) -python3_10 -python3_11 -python3_13" 0 KiB
|
_________________
µgRD dev
Wiki writer |
|
| Back to top |
|
|
alecStewart1
Apprentice
Joined: 03 Jul 2022
Posts: 246
|
| Posted: Tue Apr 15, 2025 2:41 am Post subject: |
|
|
| zen_desu wrote: | | alecStewart1 wrote: | | zen_desu wrote: | If you have qemu installed, could you run `ugrd --test` using the latest dev branch?
You should be able to change between kernel versions with `--kver` to cleanly run the test with different kernels.
You should see something like this:
https://bpa.st/raw/BSDQ
The output may clear your terminal, you can log to a file setting "--log-file" so like `ugrd --test --log-file out.log`
One small but noteworthy change is that it now waits for the user to press space instead of enter.
I've got automated testing ensuring it should print debug info and restart on mount failures now. |
Unfortunately I do not have qemu. I'll give it shot...once I build with python3.11 again, because zstandard doesn't build with python3.13 or python3.12. |
Are you sure your build system is functioning properly, I have it on 3.12:
| Code: |
[binary R ] dev-python/zstandard-0.23.0-r1-1::gentoo USE="-debug -test" PYTHON_TARGETS="python3_12 (-pypy3) (-pypy3_11) -python3_10 -python3_11 -python3_13" 0 KiB
|
|
Oh wonderful, something else might be wrong with my system...
| Code: |
* python-zstandard-0.23.0.gh.tar.gz BLAKE2B SHA512 size ;-) ... [ ok ]
>>> Unpacking source...
>>> Unpacking python-zstandard-0.23.0.gh.tar.gz to /var/tmp/portage/portage/dev-python/zstandard-0.23.0-r2/work
>>> Source unpacked in /var/tmp/portage/portage/dev-python/zstandard-0.23.0-r2/work
>>> Preparing source in /var/tmp/portage/portage/dev-python/zstandard-0.23.0-r2/work/python-zstandard-0.23.0 ...
* Applying zstandard-0.23.0-zstd-1.5.7.patch ...
patching file c-ext/backend_c.c
patching file tests/test_compressor_compress.py
patching file tests/test_compressor_compressobj.py
patching file tests/test_compressor_copy_stream.py
patching file tests/test_compressor_stream_writer.py
patching file tests/test_module_attributes.py
patching file make_cffi.py
Hunk #1 succeeded at 180 with fuzz 1 (offset 1 line).
Hunk #2 succeeded at 205 (offset 1 line).
patching file zstandard/backend_cffi.py [ ok ]
* Build system packages:
* dev-python/gpep517 : 17
* dev-python/installer : 0.7.0
* dev-python/cython : 3.0.12
* dev-python/setuptools : 78.1.0
* dev-python/setuptools-rust : 1.11.0
* dev-python/setuptools-scm : 8.2.1
* dev-python/wheel : 0.45.1
>>> Source prepared.
>>> Configuring source in /var/tmp/portage/portage/dev-python/zstandard-0.23.0-r2/work/python-zstandard-0.23.0 ...
>>> Source configured.
>>> Compiling source in /var/tmp/portage/portage/dev-python/zstandard-0.23.0-r2/work/python-zstandard-0.23.0 ...
* python3_11: running distutils-r1_run_phase distutils-r1_python_compile
* setuptools.build_meta:__legacy__ backend is deprecated. Please see:
* https://projects.gentoo.org/python/guide/qawarn.html#deprecated-pep-517-backends
* The project should use setuptools.build_meta instead.
* Building the wheel for python-zstandard-0.23.0 via setuptools.build_meta
python3.11 -m gpep517 build-wheel --prefix=/usr --backend setuptools.build_meta --output-fd 3 --wheel-dir /var/tmp/portage/portage/dev-python/zstandard-0.23.0-r2/work/python-zstandard-0.23.0-python3_11/wheel --config-json {"--build-option": ["--no-c-backend"]}
2025-04-14 21:35:31,167 gpep517 INFO Building wheel via backend setuptools.build_meta
<string>:41: DeprecationWarning: distutils Version classes are deprecated. Use packaging.version instead.
<string>:42: DeprecationWarning: distutils Version classes are deprecated. Use packaging.version instead.
Traceback (most recent call last):
File "/usr/lib/python3.11/site-packages/cffi/cparser.py", line 337, in _parse
ast = _get_parser().parse(fullcsource)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/lib/python3.11/site-packages/pycparser/c_parser.py", line 147, in parse
return self.cparser.parse(
^^^^^^^^^^^^^^^^^^^
File "/usr/lib/python3.11/site-packages/ply/yacc.py", line 333, in parse
return self.parseopt_notrack(input, lexer, debug, tracking, tokenfunc)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/lib/python3.11/site-packages/ply/yacc.py", line 1201, in parseopt_notrack
tok = call_errorfunc(self.errorfunc, errtoken, self)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/lib/python3.11/site-packages/ply/yacc.py", line 192, in call_errorfunc
r = errorfunc(token)
^^^^^^^^^^^^^^^^
File "/usr/lib/python3.11/site-packages/pycparser/c_parser.py", line 1945, in p_error
self._parse_error(
File "/usr/lib/python3.11/site-packages/pycparser/plyparser.py", line 67, in _parse_error
raise ParseError("%s: %s" % (coord, msg))
pycparser.plyparser.ParseError: /var/tmp/portage/portage/dev-python/zstandard-0.23.0-r2/temp/tmpaa3ycjsn.h:1861:2: before: pragma
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "<frozen runpy>", line 198, in _run_module_as_main
File "<frozen runpy>", line 88, in _run_code
File "/usr/lib/python3.11/site-packages/gpep517/__main__.py", line 445, in <module>
sys.exit(main())
^^^^^^
File "/usr/lib/python3.11/site-packages/gpep517/__main__.py", line 441, in main
return func(args)
^^^^^^^^^^
File "/usr/lib/python3.11/site-packages/gpep517/__main__.py", line 231, in build_wheel
print(build_wheel_impl(args, args.wheel_dir), file=out)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/lib/python3.11/site-packages/gpep517/__main__.py", line 223, in build_wheel_impl
wheel_name = backend.build_wheel(str(wheel_dir), args.config_json)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/lib/python3.11/site-packages/setuptools/build_meta.py", line 435, in build_wheel
return _build(['bdist_wheel'])
^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/lib/python3.11/site-packages/setuptools/build_meta.py", line 426, in _build
return self._build_with_temp_dir(
^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/lib/python3.11/site-packages/setuptools/build_meta.py", line 407, in _build_with_temp_dir
self.run_setup()
File "/usr/lib/python3.11/site-packages/setuptools/build_meta.py", line 320, in run_setup
exec(code, locals())
File "<string>", line 112, in <module>
File "/var/tmp/portage/portage/dev-python/zstandard-0.23.0-r2/work/python-zstandard-0.23.0/make_cffi.py", line 219, in <module>
ffi.cdef(b"\n".join(cdeflines).decode("latin1"))
File "/usr/lib/python3.11/site-packages/cffi/api.py", line 112, in cdef
self._cdef(csource, override=override, packed=packed, pack=pack)
File "/usr/lib/python3.11/site-packages/cffi/api.py", line 126, in _cdef
self._parser.parse(csource, override=override, **options)
File "/usr/lib/python3.11/site-packages/cffi/cparser.py", line 390, in parse
self._internal_parse(csource)
File "/usr/lib/python3.11/site-packages/cffi/cparser.py", line 395, in _internal_parse
ast, macros, csource = self._parse(csource)
^^^^^^^^^^^^^^^^^^^^
File "/usr/lib/python3.11/site-packages/cffi/cparser.py", line 339, in _parse
self.convert_pycparser_error(e, csource)
File "/usr/lib/python3.11/site-packages/cffi/cparser.py", line 368, in convert_pycparser_error
raise CDefError(msg)
cffi.CDefError: parse error
|
|
|
| Back to top |
|
|
alecStewart1
Apprentice
Joined: 03 Jul 2022
Posts: 246
|
| Posted: Tue Apr 15, 2025 2:51 am Post subject: |
|
|
| pietinger wrote: | alecStewart1,
I had a chat with @zen_desu last night and the question came up whether your system startup is not running at all, or whether you “only” get this error, but your system startup continues to run. If the latter is the case, the (complete) output of dmesg will be able to help us. As far as your kernel is concerned: As soon as it is able to output something on the screen, we have almost everything we need. Because then we would also see a kernel panic or other error messages. But this message comes from the initramfs and that is the last thing the kernel starts (there is no going back from the initramfs to the kernel; the initramfs starts your /sbin/init last). If there were any modules missing in your kernel, we would see that (other error messages). What else can help us: We simply check the “content” of your initramfs - i.e. the init-script. Just do the: https://wiki.gentoo.org/wiki/User:Pietinger/Tutorials/Initramfs_Overview#Inspecting_a_CPIO_file and send it to us via wgetpaste https://wiki.gentoo.org/wiki/Wgetpaste (the same applies to the output of dmesg).
P.S.: At the moment the main difference between "your" kernel and our dist-kernel is: The UEFI-entry for the dist-kernel does not give a "root=..." paramater to the dist-kernel/initramfs. We do. That is the cause I suggested in my last post to do the same ... |
For the custom kernel initramfs:
| Code: |
cpio --extract --make-directories --format=newc --no-absolute-filenames < initramfs-6.14.2-gentoo.img
|
I get
| Code: |
tree .
.
├── bin
│ ├── bash
│ ├── cat
│ ├── cp
│ ├── dd
│ ├── grep
│ ├── kmod
│ ├── ls
│ ├── lsblk
│ ├── mkdir
│ ├── mount
│ ├── rm
│ ├── sh -> /bin/bash
│ ├── sleep
│ ├── stty
│ └── umount
├── dev
│ └── pts
├── etc
│ └── profile
├── init
├── initramfs-6.14.2-gentoo.img
├── lib
│ └── modules
│ └── 6.14.2-gentoo
│ ├── kernel
│ │ ├── arch
│ │ │ └── x86
│ │ │ └── crypto
│ │ │ └── sha256-ssse3.ko.zst
│ │ ├── crypto
│ │ │ ├── blake2b_generic.ko.zst
│ │ │ ├── crc32c_generic.ko.zst
│ │ │ ├── xor.ko.zst
│ │ │ └── xxhash_generic.ko.zst
│ │ ├── drivers
│ │ │ ├── gpu
│ │ │ │ └── drm
│ │ │ │ └── drm.ko.zst
│ │ │ ├── misc
│ │ │ │ └── mei
│ │ │ │ ├── mei.ko.zst
│ │ │ │ └── mei-me.ko.zst
│ │ │ ├── net
│ │ │ │ └── ethernet
│ │ │ │ └── intel
│ │ │ │ └── igc
│ │ │ │ └── igc.ko.zst
│ │ │ ├── nvme
│ │ │ │ ├── common
│ │ │ │ │ └── nvme-auth.ko.zst
│ │ │ │ └── host
│ │ │ │ ├── nvme-core.ko.zst
│ │ │ │ └── nvme.ko.zst
│ │ │ └── platform
│ │ │ └── x86
│ │ │ └── intel
│ │ │ └── intel-vsec.ko.zst
│ │ ├── fs
│ │ │ └── btrfs
│ │ │ └── btrfs.ko.zst
│ │ └── lib
│ │ ├── lzo
│ │ │ └── lzo_compress.ko.zst
│ │ ├── raid6
│ │ │ └── raid6_pq.ko.zst
│ │ └── zlib_deflate
│ │ └── zlib_deflate.ko.zst
│ ├── modules.alias
│ ├── modules.alias.bin
│ ├── modules.builtin
│ ├── modules.builtin.alias.bin
│ ├── modules.builtin.bin
│ ├── modules.builtin.modinfo
│ ├── modules.dep
│ ├── modules.dep.bin
│ ├── modules.devname
│ ├── modules.order
│ ├── modules.softdep
│ ├── modules.symbols
│ ├── modules.symbols.bin
│ └── modules.weakdep
├── lib64
│ ├── ld-linux-x86-64.so.2
│ ├── libc.so.6
│ ├── liblzo2.so.2 -> /lib64/liblzo2.so.2.0.0
│ ├── liblzo2.so.2.0.0
│ ├── libm.so.6
│ ├── libtinfo.so.6 -> /lib64/libtinfo.so.6.5
│ ├── libtinfo.so.6.5
│ ├── libtinfow.so.6 -> /lib64/libtinfow.so.6.5
│ └── libtinfow.so.6.5
├── proc
├── root
├── run
├── sbin
│ ├── blkid
│ ├── btrfs
│ ├── modprobe -> /bin/kmod
│ └── switch_root
├── sys
├── target_rootfs
├── tmp
└── usr
├── bin
│ ├── awk -> /usr/bin/gawk
│ ├── bc -> /usr/bin/bc-reference
│ ├── bc-reference
│ ├── gawk
│ └── sleep -> /bin/sleep
└── lib64
├── libacl.so.1 -> /usr/lib64/libacl.so.1.1.2302
├── libacl.so.1.1.2302
├── libattr.so.1 -> /usr/lib64/libattr.so.1.1.2502
├── libattr.so.1.1.2502
├── libblkid.so.1 -> /usr/lib64/libblkid.so.1.1.0
├── libblkid.so.1.1.0
├── libcap.so.2 -> /usr/lib64/libcap.so.2.71
├── libcap.so.2.71
├── liblzma.so.5 -> /usr/lib64/liblzma.so.5.6.4
├── liblzma.so.5.6.4
├── libmount.so.1 -> /usr/lib64/libmount.so.1.1.0
├── libmount.so.1.1.0
├── libpcre2-8.so.0 -> /usr/lib64/libpcre2-8.so.0.14.0
├── libpcre2-8.so.0.14.0
├── libreadline.so.8 -> /usr/lib64/libreadline.so.8.2
├── libreadline.so.8.2
├── libsmartcols.so.1 -> /usr/lib64/libsmartcols.so.1.1.0
├── libsmartcols.so.1.1.0
├── libudev.so.1 -> /usr/lib64/libudev.so.1.7.8
├── libudev.so.1.7.8
├── libuuid.so.1 -> /usr/lib64/libuuid.so.1.3.0
├── libuuid.so.1.3.0
├── libz.so.1 -> /usr/lib64/libz.so.1.3.1
├── libz.so.1.3.1
├── libzstd.so.1 -> /usr/lib64/libzstd.so.1.5.7
└── libzstd.so.1.5.7
45 directories, 93 files
|
Last edited by alecStewart1 on Tue Apr 15, 2025 3:01 am; edited 2 times in total |
|
| Back to top |
|
|
sam_
Developer
Joined: 14 Aug 2020
Posts: 2306
|
| Posted: Tue Apr 15, 2025 2:54 am Post subject: |
|
|
Supposing dev-python/zstandard were unbuildable with certain Python versions, the correct course of action would be to file a bug for that. The issue is actually just showing up when rebuilding dev-python/zstandard. See bug 950259 which had a workaround applied the other week in an ~arch revbump of app-arch/zstd (as dev-python/zstandard uses its headers when building).
Another workaround, other than using that, is to not use Clang to build dev-python/zstandard. |
|
| Back to top |
|
|
zen_desu
Apprentice
Joined: 25 Oct 2024
Posts: 251
|
| Posted: Tue Apr 15, 2025 4:46 am Post subject: |
|
|
| alecStewart1 wrote: | | pietinger wrote: | alecStewart1,
I had a chat with @zen_desu last night and the question came up whether your system startup is not running at all, or whether you “only” get this error, but your system startup continues to run. If the latter is the case, the (complete) output of dmesg will be able to help us. As far as your kernel is concerned: As soon as it is able to output something on the screen, we have almost everything we need. Because then we would also see a kernel panic or other error messages. But this message comes from the initramfs and that is the last thing the kernel starts (there is no going back from the initramfs to the kernel; the initramfs starts your /sbin/init last). If there were any modules missing in your kernel, we would see that (other error messages). What else can help us: We simply check the “content” of your initramfs - i.e. the init-script. Just do the: https://wiki.gentoo.org/wiki/User:Pietinger/Tutorials/Initramfs_Overview#Inspecting_a_CPIO_file and send it to us via wgetpaste https://wiki.gentoo.org/wiki/Wgetpaste (the same applies to the output of dmesg).
P.S.: At the moment the main difference between "your" kernel and our dist-kernel is: The UEFI-entry for the dist-kernel does not give a "root=..." paramater to the dist-kernel/initramfs. We do. That is the cause I suggested in my last post to do the same ... |
For the custom kernel initramfs:
| Code: |
cpio --extract --make-directories --format=newc --no-absolute-filenames < initramfs-6.14.2-gentoo.img
|
I get
| Code: |
tree .
.
├── bin
│ ├── bash
│ ├── cat
│ ├── cp
│ ├── dd
│ ├── grep
│ ├── kmod
│ ├── ls
│ ├── lsblk
│ ├── mkdir
│ ├── mount
│ ├── rm
│ ├── sh -> /bin/bash
│ ├── sleep
│ ├── stty
│ └── umount
├── dev
│ └── pts
├── etc
│ └── profile
├── init
├── initramfs-6.14.2-gentoo.img
├── lib
│ └── modules
│ └── 6.14.2-gentoo
│ ├── kernel
│ │ ├── arch
│ │ │ └── x86
│ │ │ └── crypto
│ │ │ └── sha256-ssse3.ko.zst
│ │ ├── crypto
│ │ │ ├── blake2b_generic.ko.zst
│ │ │ ├── crc32c_generic.ko.zst
│ │ │ ├── xor.ko.zst
│ │ │ └── xxhash_generic.ko.zst
│ │ ├── drivers
│ │ │ ├── gpu
│ │ │ │ └── drm
│ │ │ │ └── drm.ko.zst
│ │ │ ├── misc
│ │ │ │ └── mei
│ │ │ │ ├── mei.ko.zst
│ │ │ │ └── mei-me.ko.zst
│ │ │ ├── net
│ │ │ │ └── ethernet
│ │ │ │ └── intel
│ │ │ │ └── igc
│ │ │ │ └── igc.ko.zst
│ │ │ ├── nvme
│ │ │ │ ├── common
│ │ │ │ │ └── nvme-auth.ko.zst
│ │ │ │ └── host
│ │ │ │ ├── nvme-core.ko.zst
│ │ │ │ └── nvme.ko.zst
│ │ │ └── platform
│ │ │ └── x86
│ │ │ └── intel
│ │ │ └── intel-vsec.ko.zst
│ │ ├── fs
│ │ │ └── btrfs
│ │ │ └── btrfs.ko.zst
│ │ └── lib
│ │ ├── lzo
│ │ │ └── lzo_compress.ko.zst
│ │ ├── raid6
│ │ │ └── raid6_pq.ko.zst
│ │ └── zlib_deflate
│ │ └── zlib_deflate.ko.zst
│ ├── modules.alias
│ ├── modules.alias.bin
│ ├── modules.builtin
│ ├── modules.builtin.alias.bin
│ ├── modules.builtin.bin
│ ├── modules.builtin.modinfo
│ ├── modules.dep
│ ├── modules.dep.bin
│ ├── modules.devname
│ ├── modules.order
│ ├── modules.softdep
│ ├── modules.symbols
│ ├── modules.symbols.bin
│ └── modules.weakdep
├── lib64
│ ├── ld-linux-x86-64.so.2
│ ├── libc.so.6
│ ├── liblzo2.so.2 -> /lib64/liblzo2.so.2.0.0
│ ├── liblzo2.so.2.0.0
│ ├── libm.so.6
│ ├── libtinfo.so.6 -> /lib64/libtinfo.so.6.5
│ ├── libtinfo.so.6.5
│ ├── libtinfow.so.6 -> /lib64/libtinfow.so.6.5
│ └── libtinfow.so.6.5
├── proc
├── root
├── run
├── sbin
│ ├── blkid
│ ├── btrfs
│ ├── modprobe -> /bin/kmod
│ └── switch_root
├── sys
├── target_rootfs
├── tmp
└── usr
├── bin
│ ├── awk -> /usr/bin/gawk
│ ├── bc -> /usr/bin/bc-reference
│ ├── bc-reference
│ ├── gawk
│ └── sleep -> /bin/sleep
└── lib64
├── libacl.so.1 -> /usr/lib64/libacl.so.1.1.2302
├── libacl.so.1.1.2302
├── libattr.so.1 -> /usr/lib64/libattr.so.1.1.2502
├── libattr.so.1.1.2502
├── libblkid.so.1 -> /usr/lib64/libblkid.so.1.1.0
├── libblkid.so.1.1.0
├── libcap.so.2 -> /usr/lib64/libcap.so.2.71
├── libcap.so.2.71
├── liblzma.so.5 -> /usr/lib64/liblzma.so.5.6.4
├── liblzma.so.5.6.4
├── libmount.so.1 -> /usr/lib64/libmount.so.1.1.0
├── libmount.so.1.1.0
├── libpcre2-8.so.0 -> /usr/lib64/libpcre2-8.so.0.14.0
├── libpcre2-8.so.0.14.0
├── libreadline.so.8 -> /usr/lib64/libreadline.so.8.2
├── libreadline.so.8.2
├── libsmartcols.so.1 -> /usr/lib64/libsmartcols.so.1.1.0
├── libsmartcols.so.1.1.0
├── libudev.so.1 -> /usr/lib64/libudev.so.1.7.8
├── libudev.so.1.7.8
├── libuuid.so.1 -> /usr/lib64/libuuid.so.1.3.0
├── libuuid.so.1.3.0
├── libz.so.1 -> /usr/lib64/libz.so.1.3.1
├── libz.so.1.3.1
├── libzstd.so.1 -> /usr/lib64/libzstd.so.1.5.7
└── libzstd.so.1.5.7
45 directories, 93 files
|
|
This looks fine to me, the thing of note being that zstd compressed modules are included because ugrd cannot use the zstandard python module to decompress these modules.
Side note is that ugrd is built using pycpio and (uncompressed) cpio images can be inspected with `pycpio -pi <img.cpio>` where it will show the contents, inodes, and hashes of the archive.
Maybe the kernel is missing a module for zstd decompression?
If you're able to share the debug screen when ugrd fails, that may have some helpful info.
I'd focus on compile issues first though, and possibly rebuild anything involved with booting if things need adjustment.
_________________
µgRD dev
Wiki writer |
|
| Back to top |
|
|
alecStewart1
Apprentice
Joined: 03 Jul 2022
Posts: 246
|
| Posted: Tue Apr 15, 2025 7:55 pm Post subject: |
|
|
| zen_desu wrote: |
This looks fine to me, the thing of note being that zstd compressed modules are included because ugrd cannot use the zstandard python module to decompress these modules.
Side note is that ugrd is built using pycpio and (uncompressed) cpio images can be inspected with `pycpio -pi <img.cpio>` where it will show the contents, inodes, and hashes of the archive.
Maybe the kernel is missing a module for zstd decompression?
If you're able to share the debug screen when ugrd fails, that may have some helpful info.
I'd focus on compile issues first though, and possibly rebuild anything involved with booting if things need adjustment. |
Unfortunately, last night I tried running ugrd with the new configuration stuff, checked if an EFI image was created with efibootmgr -u, there was, and I rebooted and the only bootable media was the Gentoo LiveGUI USB I have plugged in.
Wonderful. I boot into the Gentoo LiveGUI USB, run efibootmgr -u, and there's still no bootable media besides that USB.
SO I believe this might have something do to with me rebuilding packages with python3.11 (as I thought I needed to properly build zstandard) turns out there was an update to the python3.11 that fails to build, and so all of the python packages were screwed up. Maybe.
The error shown was:
| Code: |
Unknown float word ordering. You need to manually preset
ax_cv_c_float_words_bigendian=no (or yes) according to your system.
|
I decided these were problems to deal with another day, because going one step forward and two steps back actually started to annoy me and I needed to cool down.
If I have any time tonight I'll see if there was some update to the python3.11 package or if I need to report a bug. I'm almost tempted to start over from scratch, but I know that's not the Gentoo way and probably won't fix my issue. |
|
| Back to top |
|
|
zen_desu
Apprentice
Joined: 25 Oct 2024
Posts: 251
|
| Posted: Tue Apr 15, 2025 8:02 pm Post subject: |
|
|
| alecStewart1 wrote: | | zen_desu wrote: |
This looks fine to me, the thing of note being that zstd compressed modules are included because ugrd cannot use the zstandard python module to decompress these modules.
Side note is that ugrd is built using pycpio and (uncompressed) cpio images can be inspected with `pycpio -pi <img.cpio>` where it will show the contents, inodes, and hashes of the archive.
Maybe the kernel is missing a module for zstd decompression?
If you're able to share the debug screen when ugrd fails, that may have some helpful info.
I'd focus on compile issues first though, and possibly rebuild anything involved with booting if things need adjustment. |
Unfortunately, last night I tried running ugrd with the new configuration stuff, checked if an EFI image was created with efibootmgr -u, there was, and I rebooted and the only bootable media was the Gentoo LiveGUI USB I have plugged in.
Wonderful. I boot into the Gentoo LiveGUI USB, run efibootmgr -u, and there's still no bootable media besides that USB.
SO I believe this might have something do to with me rebuilding packages with python3.11 (as I thought I needed to properly build zstandard) turns out there was an update to the python3.11 that fails to build, and so all of the python packages were screwed up. Maybe.
The error shown was:
| Code: |
Unknown float word ordering. You need to manually preset
ax_cv_c_float_words_bigendian=no (or yes) according to your system.
|
I decided these were problems to deal with another day, because going one step forward and two steps back actually started to annoy me and I needed to cool down.
If I have any time tonight I'll see if there was some update to the python3.11 package or if I need to report a bug. I'm almost tempted to start over from scratch, but I know that's not the Gentoo way and probably won't fix my issue. |
Your UEFI may remove the entry if the kernel was not bootable.
For debug purposes, it may be useful to try to setup a similar setup in a VM and see how much of this can be replicated. If you're not able to replicate any of these issues, that could point to something being wrong with your current setup. If that breaks too, something about this process may be broken.
_________________
µgRD dev
Wiki writer |
|
| Back to top |
|
|
sam_
Developer
Joined: 14 Aug 2020
Posts: 2306
|
| Posted: Tue Apr 15, 2025 11:35 pm Post subject: |
|
|
| alecStewart1 wrote: | | zen_desu wrote: |
This looks fine to me, the thing of note being that zstd compressed modules are included because ugrd cannot use the zstandard python module to decompress these modules.
Side note is that ugrd is built using pycpio and (uncompressed) cpio images can be inspected with `pycpio -pi <img.cpio>` where it will show the contents, inodes, and hashes of the archive.
Maybe the kernel is missing a module for zstd decompression?
If you're able to share the debug screen when ugrd fails, that may have some helpful info.
I'd focus on compile issues first though, and possibly rebuild anything involved with booting if things need adjustment. |
Unfortunately, last night I tried running ugrd with the new configuration stuff, checked if an EFI image was created with efibootmgr -u, there was, and I rebooted and the only bootable media was the Gentoo LiveGUI USB I have plugged in.
Wonderful. I boot into the Gentoo LiveGUI USB, run efibootmgr -u, and there's still no bootable media besides that USB.
SO I believe this might have something do to with me rebuilding packages with python3.11 (as I thought I needed to properly build zstandard) turns out there was an update to the python3.11 that fails to build, and so all of the python packages were screwed up. Maybe.
The error shown was:
| Code: |
Unknown float word ordering. You need to manually preset
ax_cv_c_float_words_bigendian=no (or yes) according to your system.
|
I decided these were problems to deal with another day, because going one step forward and two steps back actually started to annoy me and I needed to cool down.
If I have any time tonight I'll see if there was some update to the python3.11 package or if I need to report a bug. I'm almost tempted to start over from scratch, but I know that's not the Gentoo way and probably won't fix my issue. |
You should always share the full build.log (and config.log for configure errors like that) and emerge --info. In this case, it's likely a configure test in Python being confused by LTO. |
|
| Back to top |
|
|
alecStewart1
Apprentice
Joined: 03 Jul 2022
Posts: 246
|
| Posted: Thu Apr 17, 2025 5:51 pm Post subject: |
|
|
| zen_desu wrote: |
Your UEFI may remove the entry if the kernel was not bootable.
For debug purposes, it may be useful to try to setup a similar setup in a VM and see how much of this can be replicated. If you're not able to replicate any of these issues, that could point to something being wrong with your current setup. If that breaks too, something about this process may be broken. |
Unfortunately, there were no EFI entries for the custom configured kernel nor for gentoo-kernel-bin (which was working fine). Just the Gentoo LiveGUI USB. So I'm guessing it's all related to the Python issue.
I'll try and resolve that issue with Python either tonight or tomorrow and see if ugrd works again afterwards. |
|
| Back to top |
|
|
pingtoo
Veteran
Joined: 10 Sep 2021
Posts: 1662
Location: Richmond Hill, Canada
|
| Posted: Thu Apr 17, 2025 6:56 pm Post subject: |
|
|
If there are EFI level issues it cannot relate to OS level utilities unless it is OS level utility used for writing data to NVRAM. And I don't think efibootmgr is based on python.
UEFI spec dictate that managing storage are all automated there is very little you can do at EFI boot manager level. so as long as your boot device are functional it should just work. However EFI boot manager need to do two things, one is locate the ESP and second mount the ESP. Each entry in NVRAM were used to identify ESP partition (the UUID portion) and mounting happen automatically as long as the ESP have correct supported file system (FAT based, so FAT12/16/32 all work). There are known UEFI firmware do remove entry automatically if entry specified in NVRAM were not usable. however it does not mean it cannot be examined at EFI boot manager. so if you can boot into EFI shell and if not show at first entering shell, then use the command "map -r". the command should give you some output about "FS[0-9]" and "BLK[0-9]". blkX refer to storage device that your EFI firmware have storage driver for it, fsX refer to EFI firmware have filesystem driver for it.
I wonder may be your ESP file system was corrupted therefor EFI boot manager not able to mount it. you should try to use fsck on your ESP partition to see if it work OK. |
|
| Back to top |
|
|
alecStewart1
Apprentice
Joined: 03 Jul 2022
Posts: 246
|
| Posted: Thu Apr 17, 2025 8:18 pm Post subject: |
|
|
| pingtoo wrote: | If there are EFI level issues it cannot relate to OS level utilities unless it is OS level utility used for writing data to NVRAM. And I don't think efibootmgr is based on python.
|
It's entirely likely the issue is coming form ugrd and the firmware it's created, or maybe somethign with installkernel, and not anything with the code base of ugrd or installkernel but me fidgeting with Python when I shouldn't have.
| pingtoo wrote: |
UEFI spec dictate that managing storage are all automated there is very little you can do at EFI boot manager level. so as long as your boot device are functional it should just work. However EFI boot manager need to do two things, one is locate the ESP and second mount the ESP. Each entry in NVRAM were used to identify ESP partition (the UUID portion) and mounting happen automatically as long as the ESP have correct supported file system (FAT based, so FAT12/16/32 all work). There are known UEFI firmware do remove entry automatically if entry specified in NVRAM were not usable. however it does not mean it cannot be examined at EFI boot manager. so if you can boot into EFI shell and if not show at first entering shell, then use the command "map -r". the command should give you some output about "FS[0-9]" and "BLK[0-9]". blkX refer to storage device that your EFI firmware have storage driver for it, fsX refer to EFI firmware have filesystem driver for it.
I wonder may be your ESP file system was corrupted therefor EFI boot manager not able to mount it. you should try to use fsck on your ESP partition to see if it work OK.
|
I appreciate your input, unfortunately:
gentoo-kernel-bin works fine. It has worked fine for some months.
It was bootable and working fine before I tried rebuilding ugrd/installkernel and related libraries with Python 3.11 again the other day and tried building the kernel manually again.
gentoo-kernel-bin was bootable even when fsck would report on boot that there was a dirty bit in my ESP partition, and even after I would clean that partition with fsck.
Now, even if I cleaned that partition with fsck and reinstalled gentoo-kernel-bin, there were no EFI entries besides the Gentoo LiveGUI USB. I can try creating a EFI entry with manually calling efibootmgr, but if the initramfs is busted then it won't matter.
At this point, I don't encrypt my root partition. I think I'll just try the easy route that pietinger mentioned and baking the firmware into the kernel.
I'm getting a little tried of initramfs building tools working for me for awhile and then suddenly not, and then maybe working again and then not after awhile. Maybe MSI Motherboards have a negative reputation that I hear about IRL for a reason.
I don't know. I kind of just want things to work again and if that means not using an initramfs, so be it. |
|
| Back to top |
|
|
pingtoo
Veteran
Joined: 10 Sep 2021
Posts: 1662
Location: Richmond Hill, Canada
|
| Posted: Thu Apr 17, 2025 10:36 pm Post subject: |
|
|
I understand the frustration, regression always make people feel bad because it feel someone/something is doing thing on purposely against you.
On the other hand, please think of it as growing pain, think of it as beauty of Gentoo. One of reason people choose Gentoo because it is good learning experience.
| alecStewart1 wrote: | Now, even if I cleaned that partition with fsck and reinstalled gentoo-kernel-bin, there were no EFI entries besides the Gentoo LiveGUI USB. I can try creating a EFI entry with manually calling efibootmgr, but if the initramfs is busted then it won't matter.
|
from your post, it seems you are depend on installkernel to create boot entry. Have you try to use efibootmgr to manually create one?
Have you try to boot in to EFI Shell and examine how your firmware discovery devices?
Unless you recreate the file system for your ESP or somehow the ESP damaged. this should not happen. Previously pietinger had request you create a "My" entry that had successes. So if you do this again does the entry gone after reboot?
If you suspect initrd is the reason, have you try to create a entry without initrd to see what happen? If your kernel built with efi stub than at lease you should be able to see kernel boot message show up on screen. (even thought boot may fail at least this demonstrate your idea is correct that problem is with initrd) |
|
| Back to top |
|
|
alecStewart1
Apprentice
Joined: 03 Jul 2022
Posts: 246
|
| Posted: Fri Apr 18, 2025 2:23 am Post subject: |
|
|
| pingtoo wrote: |
Have you try to use efibootmgr to manually create one?
[ ... ]
Previously pietinger had request you create a "My" entry that had successes. So if you do this again does the entry gone after reboot?
|
The one I created myself and the one pietinger asked me to create had the same error of not being about to find the root partition.
| pingtoo wrote: |
Have you try to boot in to EFI Shell and examine how your firmware discovery devices?
Unless you recreate the file system for your ESP or somehow the ESP damaged. this should not happen.
|
I have no idea how to get to the EFI Shell on this motherboard. I can look up and see how.
| pingtoo wrote: | | If you suspect initrd is the reason, have you try to create a entry without initrd to see what happen? If your kernel built with efi stub than at lease you should be able to see kernel boot message show up on screen. (even thought boot may fail at least this demonstrate your idea is correct that problem is with initrd) |
I can try that. |
|
| Back to top |
|
|
pingtoo
Veteran
Joined: 10 Sep 2021
Posts: 1662
Location: Richmond Hill, Canada
|
| Posted: Fri Apr 18, 2025 2:16 pm Post subject: |
|
|
May be it is just me, but I am confused by your posts.
You mention boot entries disappeared from EFI NVRAM. That is the reason prompt me post about examining NVRAM with EFI Shell. If I misunderstood the situation, you can ignore my comments about EFI. (Although, I still think it is good to debug at EFI Shell level but it is not always needed)
If you don't mind can you share "efibootmgr -u" output? may be this will help to understand current condition. If there will be difference from before boot and after boot, please share both so can understand that context. |
|
| Back to top |
|
|
alecStewart1
Apprentice
Joined: 03 Jul 2022
Posts: 246
|
| Posted: Fri Apr 18, 2025 5:58 pm Post subject: |
|
|
| pingtoo wrote: | May be it is just me, but I am confused by your posts.
You mention boot entries disappeared from EFI NVRAM. That is the reason prompt me post about examining NVRAM with EFI Shell. If I misunderstood the situation, you can ignore my comments about EFI. (Although, I still think it is good to debug at EFI Shell level but it is not always needed)
If you don't mind can you share "efibootmgr -u" output? may be this will help to understand current condition. If there will be difference from before boot and after boot, please share both so can understand that context. |
Sure. I'm on the LiveGUI usb still and I got everything rebuilt and updated with emerge.
There's currently entries for the gentoo-kernel-bin and what was created by installkernel when running make -j12 install in the kernel I configured from gentoo-sources that's been giving me the main trouble
efibootmgr -u
| Code: |
BootCurrent: 0001
Timeout: 0 seconds
BootOrder: 01FF,0200,0001
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)
Boot01FF* UMC 1 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 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,tomoyo,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 2 Gentoo Linux 6.14.2 HD(1,GPT,d5d977e1-f515-574f-8949-caf8f2c41559,0x800,0x80000)/\EFI\Gentoo\vmlinuz-6.14.2-gentoo.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,tomoyo,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.img
|
As of note, this is what ugrd spat out when running that make -j12 install I mentioned earlier for the customized kernel:
| Code: |
INSTALL /boot
* Generating AMD CPU Microcode early initramfs image...
* Created temporary directory: /tmp/tmp.eTER3v9NUM
* Created microcode archive at: /boot/amd-uc.img
* Cleaned up temporary directory: /tmp/tmp.eTER3v9NUM
* 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-gentoo
INFO | [cpio_rotate] Setting from arguments: False
INFO | [out_file] Setting from arguments: /tmp/installkernel.staging.6fzpL5k/initrd
INFO | Resolved out_dir to: /tmp/installkernel.staging.6fzpL5k
INFO | Loading config file: /etc/ugrd/config.toml
INFO | Resolved out_dir to: /tmp/installkernel.staging.6fzpL5k
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 | No virtual block devices found, 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, snd_hda_intel, i915, wl, intel_vsec, igc, snd_sof_pci_intel_tgl, snd_soc_avs, xe, snd_sof_pci_intel_cnl, mei_me, amdgpu, iwlwifi
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 | [i915] Failed to process autodetected kernel module dependencies: [i915] Modinfo returned no output.
WARNING | [wl] Failed to process autodetected kernel module dependencies: [wl] Modinfo returned no output.
WARNING | [intel_vsec] Failed to process autodetected kernel module dependencies: [intel_vsec] Modinfo returned no output.
WARNING | [igc] Failed to process autodetected kernel module dependencies: [igc] Modinfo returned no output.
WARNING | [snd_sof_pci_intel_tgl] Failed to process autodetected kernel module dependencies: [snd_sof_pci_intel_tgl] Modinfo returned no output.
WARNING | [snd_soc_avs] Failed to process autodetected kernel module dependencies: [snd_soc_avs] 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 | [btrfs] Unknown kmod extension: /lib/modules/6.14.2-gentoo/kernel/fs/btrfs/btrfs.ko.zst
WARNING | [crc32c] Unknown kmod extension: /lib/modules/6.14.2-gentoo/kernel/crypto/crc32c_generic.ko.zst
WARNING | [zlib_deflate] Unknown kmod extension: /lib/modules/6.14.2-gentoo/kernel/lib/zlib_deflate/zlib_deflate.ko.zst
WARNING | [lzo_compress] Unknown kmod extension: /lib/modules/6.14.2-gentoo/kernel/lib/lzo/lzo_compress.ko.zst
WARNING | [lzo_decompress] Unknown kmod extension: /lib/modules/6.14.2-gentoo/kernel/lib/lzo/lzo_decompress.ko.zst
WARNING | [xor] Unknown kmod extension: /lib/modules/6.14.2-gentoo/kernel/crypto/xor.ko.zst
WARNING | [raid6_pq] Unknown kmod extension: /lib/modules/6.14.2-gentoo/kernel/lib/raid6/raid6_pq.ko.zst
WARNING | [xxhash64] Unknown kmod extension: /lib/modules/6.14.2-gentoo/kernel/crypto/xxhash_generic.ko.zst
WARNING | [sha256] Unknown kmod extension: /lib/modules/6.14.2-gentoo/kernel/arch/x86/crypto/sha256-ssse3.ko.zst
WARNING | [blake2b_256] Unknown kmod extension: /lib/modules/6.14.2-gentoo/kernel/crypto/blake2b_generic.ko.zst
WARNING | [nvme_auth] Unknown kmod extension: /lib/modules/6.14.2-gentoo/kernel/drivers/nvme/common/nvme-auth.ko.zst
WARNING | [nvme_core] Unknown kmod extension: /lib/modules/6.14.2-gentoo/kernel/drivers/nvme/host/nvme-core.ko.zst
WARNING | [nvme] Unknown kmod extension: /lib/modules/6.14.2-gentoo/kernel/drivers/nvme/host/nvme.ko.zst
WARNING | [mei] Unknown kmod extension: /lib/modules/6.14.2-gentoo/kernel/drivers/misc/mei/mei.ko.zst
WARNING | [mei_me] Unknown kmod extension: /lib/modules/6.14.2-gentoo/kernel/drivers/misc/mei/mei-me.ko.zst
WARNING | [handle_usr_symlinks] Skipping /usr merge
INFO | Regenerating kernel module metadata files.
INFO | -- | Generating init functions
INFO | Init kernel modules: btrfs, crc32c, nvme, mei_me
INFO | Included kernel modules: lzo_decompress, zlib_deflate, nvme_core, mei, xxhash64, nvme_auth, sha256, lzo_compress, raid6_pq, xor, blake2b_256
WARNING | Ignored kernel modules: i2c_i801, spi_intel_pci, amdgpu, i915, snd_hda_intel, iwlwifi, wl, intel_vsec, igc, snd_sof_pci_intel_tgl, snd_soc_avs, xe, snd_sof_pci_intel_cnl
WARNING | No initramfs fstab found, skipping mount_fstab.
INFO | Wrote file: /tmp/initramfs_build/etc/profile
INFO | Included functions: check_var, setvar, readvar, wait_for_space, prompt_user, retry, klog, edebug, einfo, ewarn, eerror, rd_fail, rd_restart, _find_init, mount_default_root, parse_cmdline_bool, parse_cmdline_str, mount_base, export_exports, parse_cmdline, print_banner, load_modules, mount_root, do_switch_root
INFO | Wrote file: /tmp/initramfs_build/init
INFO | -- | Packing build
INFO | [ZSTD] Compressing the CPIO data, original size: 13.08 MiB
INFO | Wrote 6.06 MiB to: /tmp/installkernel.staging.6fzpL5k/initrd
INFO | -- | Running checks
* Generated initramfs for kernel: 6.14.2-gentoo
* Running uefi-mkconfig...
* Using kernel commands from "/etc/default/uefi-mkconfig"
* Warning! Kernel command "root=" is missing from loaded configuration!
* Creating UEFI entry "0200" for "/efi/EFI/Gentoo/vmlinuz-6.14.2-gentoo.efi" found on "nvme0n1p1"
* Creating UEFI entry "01FF" for "/efi/EFI/Gentoo/vmlinuz-6.14.2-gentoo-dist.efi" found on "nvme0n1p1"
* Done
|
I'm going to try rebooting and see if I get any either of the EFI entries for Gentoo.
EDIT:
There's this warning a lot put out by ugrd
| Code: |
Unknown kmod extension:
|
For modules files that are *.ko.zst.
Is that something to be concerned about? |
|
| Back to top |
|
|
alecStewart1
Apprentice
Joined: 03 Jul 2022
Posts: 246
|
| Posted: Fri Apr 18, 2025 6:08 pm Post subject: |
|
|
Alright, and prior to booting, neither of these entries besides the first were in the menu:
| Code: |
BootCurrent: 0001
Timeout: 0 seconds
BootOrder: 01FF,0200,0001
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)
Boot01FF* UMC 1 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 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,tomoyo,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 2 Gentoo Linux 6.14.2 HD(1,GPT,d5d977e1-f515-574f-8949-caf8f2c41559,0x800,0x80000)/\EFI\Gentoo\vmlinuz-6.14.2-gentoo.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,tomoyo,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.img
|
And booting back into the Gentoo LiveGUI USB (the only option listed) I run efibootmgr -u:
| Code: |
BootCurrent: 0001
Timeout: 0 seconds
BootOrder: 0001
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)
|
In my EFI partition
| Code: |
livecd / # ls /efi/EFI/Gentoo/
amd-uc.img config-6.14.2-gentoo-dist initramfs-6.14.2-gentoo.img System.map-6.14.2-gentoo vmlinuz-6.14.2-gentoo-dist.efi
config-6.14.2-gentoo initramfs-6.14.2-gentoo-dist.img intel-uc.img System.map-6.14.2-gentoo-dist vmlinuz-6.14.2-gentoo.efi
|
So...I don't know what's happening anymore. |
|
| Back to top |
|
|
alecStewart1
Apprentice
Joined: 03 Jul 2022
Posts: 246
|
| Posted: Fri Apr 18, 2025 6:33 pm Post subject: |
|
|
Let me at least go through the process that I'm doing to rebuild the custom configured kernel.
Initial setup:
| Code: |
cd /usr/src/linux-6.14.2-gentoo
export LLVM=1 LLVM_IAS=1 LTO_CLANG_THIN=1 LD="ld.lld" AR="llvm-ar" NM="llvm-nm" RANLIB="llvm-ranlib" STRIP="llvm-strip" OBJCOPY="llvm-objcopy" OBJDUMP="llvm-objdump"
export LDFLAGS="-fuse-ld=mold -Wl,-O2 -Wl,--sort-common -Wl,--as-needed -Wl,--strip-debug -Wl,--icf=safe -Wl,-z,rewrite-endbr -flto=thin" KLDFLAGS="-fuse-ld=mold -Wl,-O2 -Wl,--sort-common -Wl,--as-needed -Wl,--strip-debug -Wl,--icf=safe -Wl,-z,rewrite-endbr -flto=thin" CFLAGS="-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" 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"
|
Now the make commands. Since the kernel config hasn't changed since the last attempt, I don't bother running make menuconfig:
| Code: |
make -j12 clean
make -j12
make -j12 modules_install
make -j12 install
|
What make -j12 clean returns:
| Code: |
CLEAN arch/x86/lib
CLEAN certs
CLEAN init
CLEAN arch/x86/boot/compressed
CLEAN arch/x86/boot
CLEAN arch/x86/entry/vdso
CLEAN arch/x86/kvm
CLEAN arch/x86/kernel/cpu
CLEAN arch/x86/kernel
CLEAN lib/raid6
CLEAN lib/test_fortify
CLEAN lib
CLEAN security/apparmor
CLEAN security/ipe
CLEAN arch/x86/realmode/rm
CLEAN arch/x86/tools
CLEAN security/tomoyo
CLEAN fs/unicode
CLEAN net/wireless
CLEAN drivers/firmware/efi/libstub
CLEAN drivers/gpu/drm/xe
CLEAN drivers/scsi
CLEAN drivers/tty/vt
CLEAN drivers/video/logo
CLEAN .
CLEAN modules.builtin modules.builtin.modinfo .vmlinux.objs .vmlinux.export.c
|
What make -j12 returns:
http://dpaste.com/BGPUQ6Z2G
I ran
| Code: |
make -j12 >> gentoo-sources-kernel-6.14.2-build.log
|
To get this output.
make -j12 modules_insatll:
http://dpaste.com/E5ZCDHBJP
make -j12 install
| Code: |
INSTALL /boot
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
* Generating AMD CPU Microcode early initramfs image...
* Created temporary directory: /tmp/tmp.bkqHxMsK1z
* Created microcode archive at: /boot/amd-uc.img
* Cleaned up temporary directory: /tmp/tmp.bkqHxMsK1z
* Generating Intel CPU Microcode early initramfs image...
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-gentoo
INFO | [cpio_rotate] Setting from arguments: False
INFO | [out_file] Setting from arguments: /tmp/installkernel.staging.Ar994Bq/initrd
INFO | Resolved out_dir to: /tmp/installkernel.staging.Ar994Bq
INFO | Loading config file: /etc/ugrd/config.toml
INFO | Resolved out_dir to: /tmp/installkernel.staging.Ar994Bq
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 | No virtual block devices found, 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, i915, intel_vsec, amdgpu, xe, snd_hda_intel, mei_me, igc, iwlwifi, snd_sof_pci_intel_cnl, wl, snd_sof_pci_intel_tgl, 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 | [i915] Failed to process autodetected kernel module dependencies: [i915] Modinfo returned no output.
WARNING | [intel_vsec] Failed to process autodetected kernel module dependencies: [intel_vsec] 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 | [wl] Failed to process autodetected kernel module dependencies: [wl] Modinfo returned no output.
WARNING | [snd_sof_pci_intel_tgl] Failed to process autodetected kernel module dependencies: [snd_sof_pci_intel_tgl] Modinfo returned no output.
WARNING | [snd_soc_avs] Failed to process autodetected kernel module dependencies: [snd_soc_avs] Modinfo returned no output.
WARNING | [btrfs] Unknown kmod extension: /lib/modules/6.14.2-gentoo/kernel/fs/btrfs/btrfs.ko.zst
WARNING | [crc32c] Unknown kmod extension: /lib/modules/6.14.2-gentoo/kernel/crypto/crc32c_generic.ko.zst
WARNING | [zlib_deflate] Unknown kmod extension: /lib/modules/6.14.2-gentoo/kernel/lib/zlib_deflate/zlib_deflate.ko.zst
WARNING | [lzo_compress] Unknown kmod extension: /lib/modules/6.14.2-gentoo/kernel/lib/lzo/lzo_compress.ko.zst
WARNING | [lzo_decompress] Unknown kmod extension: /lib/modules/6.14.2-gentoo/kernel/lib/lzo/lzo_decompress.ko.zst
WARNING | [xor] Unknown kmod extension: /lib/modules/6.14.2-gentoo/kernel/crypto/xor.ko.zst
WARNING | [raid6_pq] Unknown kmod extension: /lib/modules/6.14.2-gentoo/kernel/lib/raid6/raid6_pq.ko.zst
WARNING | [xxhash64] Unknown kmod extension: /lib/modules/6.14.2-gentoo/kernel/crypto/xxhash_generic.ko.zst
WARNING | [sha256] Unknown kmod extension: /lib/modules/6.14.2-gentoo/kernel/arch/x86/crypto/sha256-ssse3.ko.zst
WARNING | [blake2b_256] Unknown kmod extension: /lib/modules/6.14.2-gentoo/kernel/crypto/blake2b_generic.ko.zst
WARNING | [nvme_auth] Unknown kmod extension: /lib/modules/6.14.2-gentoo/kernel/drivers/nvme/common/nvme-auth.ko.zst
WARNING | [nvme_core] Unknown kmod extension: /lib/modules/6.14.2-gentoo/kernel/drivers/nvme/host/nvme-core.ko.zst
WARNING | [nvme] Unknown kmod extension: /lib/modules/6.14.2-gentoo/kernel/drivers/nvme/host/nvme.ko.zst
WARNING | [mei] Unknown kmod extension: /lib/modules/6.14.2-gentoo/kernel/drivers/misc/mei/mei.ko.zst
WARNING | [mei_me] Unknown kmod extension: /lib/modules/6.14.2-gentoo/kernel/drivers/misc/mei/mei-me.ko.zst
WARNING | [handle_usr_symlinks] Skipping /usr merge
INFO | Regenerating kernel module metadata files.
INFO | -- | Generating init functions
INFO | Init kernel modules: btrfs, crc32c, nvme, mei_me
INFO | Included kernel modules: lzo_decompress, xor, mei, nvme_auth, xxhash64, sha256, zlib_deflate, blake2b_256, lzo_compress, raid6_pq, nvme_core
WARNING | Ignored kernel modules: i2c_i801, spi_intel_pci, amdgpu, i915, snd_hda_intel, iwlwifi, intel_vsec, xe, igc, snd_sof_pci_intel_cnl, wl, snd_sof_pci_intel_tgl, snd_soc_avs
WARNING | No initramfs fstab found, skipping mount_fstab.
INFO | Wrote file: /tmp/initramfs_build/etc/profile
INFO | Included functions: check_var, setvar, readvar, wait_for_space, prompt_user, retry, klog, edebug, einfo, ewarn, eerror, rd_fail, rd_restart, _find_init, mount_default_root, parse_cmdline_bool, parse_cmdline_str, mount_base, export_exports, parse_cmdline, print_banner, load_modules, mount_root, do_switch_root
INFO | Wrote file: /tmp/initramfs_build/init
INFO | -- | Packing build
INFO | [ZSTD] Compressing the CPIO data, original size: 13.08 MiB
INFO | Wrote 6.06 MiB to: /tmp/installkernel.staging.Ar994Bq/initrd
INFO | -- | Running checks
* Generated initramfs for kernel: 6.14.2-gentoo
* Running uefi-mkconfig...
* Using kernel commands from "/etc/default/uefi-mkconfig"
* Warning! Kernel command "root=" is missing from loaded configuration!
* Creating UEFI entry "0200" for "/efi/EFI/Gentoo/vmlinuz-6.14.2-gentoo-old.efi" found on "nvme0n1p1"
* Creating UEFI entry "01FF" for "/efi/EFI/Gentoo/vmlinuz-6.14.2-gentoo.efi" found on "nvme0n1p1"
* Creating UEFI entry "01FE" for "/efi/EFI/Gentoo/vmlinuz-6.14.2-gentoo-dist.efi" found on "nvme0n1p1"
* Done
|
The current .config file for the custom kernel:
http://dpaste.com/AKGNSVY35
Last edited by alecStewart1 on Fri Apr 18, 2025 6:35 pm; edited 1 time in total |
|
| Back to top |
|
|
pingtoo
Veteran
Joined: 10 Sep 2021
Posts: 1662
Location: Richmond Hill, Canada
|
| Posted: Fri Apr 18, 2025 6:34 pm Post subject: |
|
|
Thank you this help a lot for understand current situation.
While I was investigate this efi issues I came across a news said that some firmware will remove all entries for a given ESP if missing ESP/EFI/BOOT/BOOTx64.EFI.
So can you create a dummy file by touch ESP/EFI/BOOT/BOOTx64.EFI. (Note this is not exact command, because you might need to create the "ESP/EFI/BOOT" directory for example)
Once you create the dummy (or if you want you can make a copy of your real kernel image file in that name). Please try to manually create new entry for EFI boot just to see if it will stick after reboot.
any luck with boot into EFI Shell? it is usually happen at power on time use F2/DEL/F12 of some key to bring up BIOS menu and somewhere that will show something about boot menu. there should give you options to choose boot EFI Shell. |
|
| Back to top |
|
|
zen_desu
Apprentice
Joined: 25 Oct 2024
Posts: 251
|
| Posted: Fri Apr 18, 2025 6:36 pm Post subject: |
|
|
Are you using raid 6? I've noticed it in the kmods ugrd detects, possibly from lsmod. That stands out a bit.
Did you get the zstd stuff, I see my patch for zstd kmods only detects .zstd, not .zst. I'll patch that real quick. https://github.com/desultory/ugrd/pull/286
_________________
µgRD dev
Wiki writer |
|
| Back to top |
|
|
alecStewart1
Apprentice
Joined: 03 Jul 2022
Posts: 246
|
| Posted: Fri Apr 18, 2025 7:27 pm Post subject: |
|
|
| zen_desu wrote: | Are you using raid 6? I've noticed it in the kmods ugrd detects, possibly from lsmod. That stands out a bit.
|
Huh...no, and I don't know where that came from. I'll have to look again.
Awesome, thanks! |
|
| Back to top |
|
|
alecStewart1
Apprentice
Joined: 03 Jul 2022
Posts: 246
|
| Posted: Fri Apr 18, 2025 11:26 pm Post subject: |
|
|
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.
Well, at least I'm back to where I started. The config I have so far:
http://dpaste.com/AKGNSVY35
zen_desu, I'm up-to-date with head of ugrd on 9999.
Here's the dmesg from the Gentoo LiveGUI USB:
http://dpaste.com/GMG32R9LJ |
|
| 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
|
|
Kernel & Hardware
