Tiny Core Linux

Tiny Core Base => Corepure64 => Topic started by: catselbow on May 29, 2026, 10:08:12 AM

Title: CorePure64 17 won't boot on Dell Pro Max with Intel Core Ultra 5
Post by: catselbow on May 29, 2026, 10:08:12 AM
Apparently, no version of CorePure64 will boot on a new Dell Pro Max workstation (it has an Intel Core Ultra 5 processor, for what it's worth).  For example, when booting the stock, grub-based TinyCorePure64-17.0.iso from a USB drive the computer hangs with a black screen immediately after tc, tcw, core, or corew is selected fromt the boot menu.  The computer is completely unresponsive and doesn't respond to ctrl-alt-del. It has to be power-cycled.  I've tried kernel parameters like nomodeset, noapic, nolapic, acpi=off, but none of these change the behavior.

If I boot a custom, syslinux-based USB drive, it gets to the point of writing "Loading /corepure64.gz... OK" and then hangs.

A Fedora43 live image does boot without any problems.  Any suggestions would be welcome.  Thanks.
Title: Re: CorePure64 17 won't boot on Dell Pro Max with Intel Core Ultra 5
Post by: Juanito on May 29, 2026, 10:30:54 AM
I wonder if this is due to a uefi incompatibility - does it boot from a CorePlus iso in legacy bios mode?
Title: Re: CorePure64 17 won't boot on Dell Pro Max with Intel Core Ultra 5
Post by: Rich on May 29, 2026, 10:36:55 AM
Hi catselbow
If your system is using a dedicated GPU, try changing it
in the BIOS to the CPUs graphics hardware.
Title: Re: CorePure64 17 won't boot on Dell Pro Max with Intel Core Ultra 5
Post by: gadget42 on May 29, 2026, 10:41:49 AM
mostly for future thread visitors i would reference @Juanito from circa 2015

https://forum.tinycorelinux.net/index.php?topic=19364.0
Title: Re: CorePure64 17 won't boot on Dell Pro Max with Intel Core Ultra 5
Post by: Juanito on May 29, 2026, 12:07:13 PM
I just tried a dell latitude e7640 with 13th Gen Intel Core i7-1365U and it booted CorePure64-17.x, albeit with several acpi errors.
Title: Re: CorePure64 17 won't boot on Dell Pro Max with Intel Core Ultra 5
Post by: catselbow on May 29, 2026, 02:22:08 PM
I wonder if this is due to a uefi incompatibility - does it boot from a CorePlus iso in legacy bios mode?

Unfortunately, this computer is "legacy-free".  uefi is the only option.
Title: Re: CorePure64 17 won't boot on Dell Pro Max with Intel Core Ultra 5
Post by: catselbow on May 29, 2026, 02:24:50 PM
Hi catselbow
If your system is using a dedicated GPU, try changing it
in the BIOS to the CPUs graphics hardware.

The machine only has on-board graphics: Intel Corporation HD Graphics 630 (rev 04)
It's using displayport (the only option)
Title: Re: CorePure64 17 won't boot on Dell Pro Max with Intel Core Ultra 5
Post by: catselbow on May 29, 2026, 02:27:35 PM
I just tried a dell latitude e7640 with 13th Gen Intel Core i7-1365U and it booted CorePure64-17.x, albeit with several acpi errors.

I've used corepur64 for a long time on a lot of other machines, including including i7s, and I've just now tested the USB drive I'm trying with the Dell Pro Max and the drive works fine in other computers.  It just doesn't work on the Pro Max.
Title: Re: CorePure64 17 won't boot on Dell Pro Max with Intel Core Ultra 5
Post by: catselbow on June 01, 2026, 08:20:46 AM
Hi catselbow
If your system is using a dedicated GPU, try changing it
in the BIOS to the CPUs graphics hardware.

The machine only has on-board graphics: Intel Corporation HD Graphics 630 (rev 04)
It's using displayport (the only option)

Correction: I grabbed the video information from the wrong machine.  The problematic machine actually says:

Code: [Select]
# lspci | grep VGA
00:02.0 VGA compatible controller: Intel Corporation Arrow Lake [Intel Graphics] (rev 06)
80:14.5 Non-VGA unclassified device: Intel Corporation Device 7f2f (rev 10)

    [Edit]: Added code tags.  Rich
Title: Re: CorePure64 17 won't boot on Dell Pro Max with Intel Core Ultra 5
Post by: Rich on June 01, 2026, 08:51:52 AM
Hi catselbow

Please use  Code Tags  when posting commands and responses seen in a terminal. To use  Code Tags  click on the  #  icon
above the reply box and paste your text between the  Code Tags  as shown in this example:

Quote
[code][   36.176529] pcm512x 1-004d: Failed to get supply 'AVDD': -517
[   36.176536] pcm512x 1-004d: Failed to get supplies: -517
[   36.191753] pcm512x 1-004d: Failed to get supply 'AVDD': -517[/code]

It will appear like this in your post:
Code: [Select]
[   36.176529] pcm512x 1-004d: Failed to get supply 'AVDD': -517
[   36.176536] pcm512x 1-004d: Failed to get supplies: -517
[   36.191753] pcm512x 1-004d: Failed to get supply 'AVDD': -517

Code Tags  serve as visual markers between what you are trying to say and the information you are posting. They also preserve
spacing so column aligned data displays properly. Code tags also automatically add horizontal and or vertical scrollbars
to accommodate long lines and listings.
Title: Re: CorePure64 17 won't boot on Dell Pro Max with Intel Core Ultra 5
Post by: Rich on June 01, 2026, 08:52:10 AM
Hi catselbow
I suspect you want the  Arrow Lake  controller.
First run:
Code: [Select]
lspci -nn | grep VGAand make a note of the Product ID (PID).
It should show up like this in the lspci command:
Code: [Select]
[8086:PID]You want the hex number after the colon.

Then try adding the following boot code:
Code: [Select]
xe.force_probe=7d51 i915.force_probe=!7d51Change the 7d51 to your PID if it's different.
Title: Re: CorePure64 17 won't boot on Dell Pro Max with Intel Core Ultra 5
Post by: catselbow on June 01, 2026, 04:17:36 PM
Thanks. That doesn't work (the PID here is 7d67 fwiw), but I'll look more into the kernel parameters for the xe and i915 driver to see if I can find something that does.
Title: Re: CorePure64 17 won't boot on Dell Pro Max with Intel Core Ultra 5
Post by: Rich on June 02, 2026, 12:51:43 AM
Hi catselbow
Maybe your video card needs some firmware?
You said:
... A Fedora43 live image does boot without any problems. ...
If you boot it up, do you see any of these directories:
Code: [Select]
/lib/firmware/i915
/lib/firmware/xe

If you do, you can try making an additional initrd and adding it
to your Tinycore USB.

Code: [Select]
mkdir -p test/lib/firmware
cp -a /lib/firmware/i915 test/lib/firmware/
cp -a /lib/firmware/xe test/lib/firmware/
cd test
sudo find . | sudo cpio -o -H newc | gzip > ../IntelFirmware.gz

Modify your boot loader config file like this:
Code: [Select]
initrd /boot/core.gz,/boot/IntelFirmware.gzor this:
Code: [Select]
initrd /boot/core.gz /boot/IntelFirmware.gzThe first version should work with syslinux,extlinux, and grub-legacy.
The second version works with grub 2.
Title: Re: CorePure64 17 won't boot on Dell Pro Max with Intel Core Ultra 5
Post by: catselbow on June 02, 2026, 09:37:24 AM
I tried this, but the results were the same.  With syslinux, I see:

Code: [Select]
Loading /vmlinuz64... ok
Loading /corepure64.gz... ok
Loading /IntelFirmware.gz... ok

and then it hangs.
Title: Re: CorePure64 17 won't boot on Dell Pro Max with Intel Core Ultra 5
Post by: Juanito on June 02, 2026, 10:14:36 AM
the PID here is 7d67 fwiw

I believe that corresponds to intel arrow lake-s graphics - it would be worth checking if you need to force the xe driver with a kernel boot code and if a specific firmware version is needed.

You could also try booting without the “quiet” boot code.
Title: Re: CorePure64 17 won't boot on Dell Pro Max with Intel Core Ultra 5
Post by: Juanito on June 02, 2026, 11:54:01 AM
Ah - the intel xe kernel driver needs filesystems-KERNEL due a dep on the configfs module
Title: Re: CorePure64 17 won't boot on Dell Pro Max with Intel Core Ultra 5
Post by: nick65go on June 02, 2026, 02:34:16 PM
I asked AI: "i915 or xe for Intel Corporation HD Graphics 630" 
Its answer was: "For the Intel Corporation HD Graphics 630, the appropriate Linux graphics driver is i915. The xe driver is a modern, experimental driver intended only for newer Intel processors (11th Gen and later)".
"- i915 Driver: This is the standard, built-in Direct Rendering Manager (DRM) module required for all Kaby Lake processors (which power the HD 630).
- Xe Driver: This driver is designed for newer hardware (Tiger Lake and newer). Attempting to use the xe driver for an HD 630 will not work natively"

FYI: I have a 13th Gen Intel Core i5-1335U
0:02.0 VGA compatible controller [0300]: Intel Corporation Raptor Lake-P [Iris Xe Graphics] [8086:a7a1] (rev 04)" and it works with i915.
but you need to load proper firmware also.
Code: [Select]
209412.739756] i915 0000:00:02.0: [drm] GT0: GuC firmware i915/adlp_guc_70.bin version 70.49.4
[209412.739767] i915 0000:00:02.0: [drm] GT0: HuC firmware i915/tgl_huc.bin version 7.9.3
[209412.756772] i915 0000:00:02.0: [drm] GT0: HuC: authenticated for all workloads
[209412.757442] i915 0000:00:02.0: [drm] GT0: GUC: submission enabled
[209412.757452] i915 0000:00:02.0: [drm] GT0: GUC: SLPC enabled
[209412.757947] i915 0000:00:02.0: [drm] GT0: GUC: RC enabled
Enable Firmware (GuC/HuC): To maximize performance (especially for video encoding/decoding), ensure your distribution's firmware package is installed and enabled (e.g., linux-firmware-intel on Arch).
Title: Re: CorePure64 17 won't boot on Dell Pro Max with Intel Core Ultra 5
Post by: nick65go on June 02, 2026, 03:02:30 PM
Thanks. That doesn't work (the PID here is 7d67 fwiw), but I'll look more into the kernel parameters for the xe and i915 driver to see if I can find something that does.

AI overview: "For your Intel Arrow Lake iGPU (PCI Device ID 8086:7d67), the recommended driver is the xe Linux kernel driver. The older i915 driver does not officially support Arrow Lake’s architecture and may be unstable or require forced probing".

I think your problem is because you did not loaded the proper firmware at the proper boot moment. Sometimes you even need the firmware to be INSIDE a REMASTERED cpio core.gz (so NOT loaded as a nomal tcz). I had this problem and I solved like this for my former AMD A6xxx APU.
All Intel CPU generation 12+ need firmware at boot time for UEFI.
Title: Re: CorePure64 17 won't boot on Dell Pro Max with Intel Core Ultra 5
Post by: Rich on June 02, 2026, 03:07:48 PM
Hi nick65go
... Sometimes you even need the firmware to be INSIDE a REMASTERED cpio core.gz (so NOT loaded as a nomal tcz). ...
That's what I showed catselbow in my reply #12.
And catselbow reply #13 suggests that was done.
Title: Re: CorePure64 17 won't boot on Dell Pro Max with Intel Core Ultra 5
Post by: Rich on June 02, 2026, 03:11:55 PM
Hi catselbow
I think Juanitos suggestion to remove the  quiet  boot code is a good idea.
That may provide some error messages indicating what the problem is.
Title: Re: CorePure64 17 won't boot on Dell Pro Max with Intel Core Ultra 5
Post by: nick65go on June 02, 2026, 03:17:43 PM
Hi Rich!, He did NOT properly done it :P 
1. XE driver + its updated firmware (maybe not from TC repositories, but from kernel hub) must be loaded before anything else.
2. The i915 must be forbid, which I think was not, because usually i915 auto-load as a stupid one itself, and then xe driver is useless.

It happened to me and then grub boot parameters become useless. In TC i915 loads if using the provided gpu-kernel-*tcz + firmware*.tcz. From my experience with TC, for complex/cyborg APU (CPU+GPU) gen 12+,  CORE.gz remaster is mandatory. YMMV.
Title: Re: CorePure64 17 won't boot on Dell Pro Max with Intel Core Ultra 5
Post by: Juanito on June 02, 2026, 03:48:31 PM
I get this using the tinycore intel firmware extension, so it looks OK, but now that I've found the xe driver needs filesystems-KERNEL, I'll try again with that tomorrow.
Code: [Select]
[   66.699899] i915 0000:00:02.0: [drm] Finished loading DMC firmware i915/adlp_dmc.bin (v2.20)
[   66.720033] i915 0000:00:02.0: [drm] GT0: GuC firmware i915/adlp_guc_70.bin version 70.20.0
[   66.720037] i915 0000:00:02.0: [drm] GT0: HuC firmware i915/tgl_huc.bin version 7.9.3
Title: Re: CorePure64 17 won't boot on Dell Pro Max with Intel Core Ultra 5
Post by: nick65go on June 02, 2026, 04:01:00 PM
My remark: firmware for xe are different (other folder, other names) form firmware for i915.
Code: [Select]
❯ ls /usr/lib/firmware/xe/
.rw-r--r-- 195k root 23 Mai 12:28  bmg_guc_70.bin.zst
.rw-r--r-- 152k root 23 Mai 12:28  bmg_huc.bin.zst
.rw-r--r-- 1,7k root 23 Mai 12:28  fan_control_8086_e20b_8086_1100.bin.zst
.rw-r--r-- 1,1M root 23 Mai 12:28  lnl_gsc_1.bin.zst
.rw-r--r-- 197k root 23 Mai 12:28  lnl_guc_70.bin.zst
.rw-r--r-- 167k root 23 Mai 12:28  lnl_huc.bin.zst
.rw-r--r-- 1,1M root 23 Mai 12:28  ptl_gsc_1.bin.zst
.rw-r--r-- 204k root 23 Mai 12:28  ptl_guc_70.bin.zst
.rw-r--r-- 172k root 23 Mai 12:28  ptl_huc.bin.zst
Code: [Select]
ls /usr/lib/firmware/xe | wc
      9      63    1221
ls /usr/lib/firmware/i915 | wc
    130     922   18360
IF xe driver was properly loaded then "firmware i915" should not show-up in dmesg
Title: Re: CorePure64 17 won't boot on Dell Pro Max with Intel Core Ultra 5
Post by: Juanito on June 02, 2026, 04:23:38 PM
I was meaning that the firmware didn’t need to be in an initrd :)
Title: Re: CorePure64 17 won't boot on Dell Pro Max with Intel Core Ultra 5
Post by: Juanito on June 03, 2026, 04:39:05 AM
So, I gave xe a go..

created firmware-xe extension from kernel git:
Code: [Select]
ls /usr/local/lib/firmware/xe
bmg_guc_70.bin
bmg_huc.bin
fan_control_8086_e20b_8086_1100.bin
lnl_gsc_1.bin
lnl_guc_70.bin
lnl_huc.bin
ptl_gsc_1.bin
ptl_guc_70.bin
ptl_huc.bin

..booted with blacklist=i915

loading firmware-xe followed by filesystems-KERNEL followed by graphics-KERNEL resulted in a bunch of xe related kernel modules loading automatically, but got this:
Code: [Select]
dmesg
...
xe 0000:00:02.0: Your graphics device a7a1 is not officially supported
by xe driver in this kernel version. To force Xe probe,
use xe.force_probe='a7a1' and i915.force_probe='!a7a1'
module parameters or CONFIG_DRM_XE_FORCE_PROBE='a7a1' and
CONFIG_DRM_I915_FORCE_PROBE='!a7a1' configuration options.
..and no sign of any firmware being loaded and startx failed with no screens found.

So, booted with xe.force_probe='a7a1' and i915.force_probe='!a7a1'

loading firmware-xe followed by filesystems-KERNEL followed by graphics-KERNEL resulted in the laptop hanging, the only escape being power off :(
Title: Re: CorePure64 17 won't boot on Dell Pro Max with Intel Core Ultra 5
Post by: Rich on June 03, 2026, 07:39:22 AM
Hi Juanito
... So, booted with xe.force_probe='a7a1' and i915.force_probe='!a7a1' ...

 ... resulted in the laptop hanging, the only escape being power off :(
It's possible that only happened because you forced the issue. A7A1 is
listed as one of the aliases when running modinfo on i915.ko.gz. The OP
said his was 7D67 which is not listed as an alias in i915.ko.gz.

As a sidenote, xe.ko.gz doesn't even appear to have an alias section.
Title: Re: CorePure64 17 won't boot on Dell Pro Max with Intel Core Ultra 5
Post by: nick65go on June 03, 2026, 09:44:56 AM
@Juanito: Many thanks for trying XE driver for MY gpu-id a7a1, even if it is not working for now.
For now I use i915 in my CachyOS. AI gave me the results:

"1. For a Raptor Lake-P (RPL-P) device (such as those with device ID a7a1) running Kernel 7.0.10 in early-to-mid 2026, the i915 driver remains the most stable and recommended choice for general daily use and display functionalities

2. For an Intel Core i5-1335U (Raptor Lake-U, Gen12/Iris Xe Graphics) on a 7.0.10 kernel, i915 is the recommended default for stability, but xe is viable and potentially faster for compute workloads if you are comfortable testing it.

3. For an i5-1355U (Raptor Lake-U, Gen 13 Graphics) on a 7.0.x kernel, the i915 driver is recommended for stability, while xe is worth exploring for potential performance gains in compute-heavy workloads."

Sorry, I did not intend to hijack the topic, about initial gpu-id=7D67.
Title: Re: CorePure64 17 won't boot on Dell Pro Max with Intel Core Ultra 5
Post by: nick65go on June 03, 2026, 10:08:48 AM
It seams that XE driver may need also some firmware from i915, because:
Code: [Select]
strings xe.ko | grep firmware | grep bin
Request late binding firmware %s
firmware=xe/nvl_guc_70.55.4.bin
firmware=xe/ptl_guc_70.bin
firmware=xe/bmg_guc_70.bin
firmware=xe/lnl_guc_70.bin
firmware=i915/mtl_guc_70.bin
firmware=i915/dg2_guc_70.bin
firmware=i915/dg1_guc_70.bin
firmware=i915/tgl_guc_70.bin
firmware=i915/adlp_guc_70.bin
firmware=i915/tgl_guc_70.bin
firmware=i915/tgl_guc_70.bin
firmware=i915/tgl_guc_70.bin
firmware=xe/ptl_huc.bin
firmware=xe/bmg_huc.bin
firmware=xe/lnl_huc.bin
firmware=i915/mtl_huc_gsc.bin
firmware=i915/dg1_huc.bin
firmware=i915/tgl_huc.bin
firmware=i915/tgl_huc.bin
firmware=i915/tgl_huc.bin
firmware=i915/tgl_huc.bin
firmware=xe/ptl_gsc_1.bin
firmware=xe/lnl_gsc_1.bin
firmware=i915/mtl_gsc_1.bin
firmware=i915/xe3p_lpd_dmc.bin
firmware=i915/xe3lpd_3002_dmc.bin
firmware=i915/xe3lpd_dmc.bin
firmware=i915/xe2lpd_dmc.bin
firmware=i915/bmg_dmc.bin
firmware=i915/mtl_dmc.bin
firmware=i915/dg2_dmc_ver2_08.bin
firmware=i915/adlp_dmc.bin
firmware=i915/adlp_dmc_ver2_16.bin
firmware=i915/adls_dmc_ver2_01.bin
firmware=i915/dg1_dmc_ver2_02.bin
firmware=i915/rkl_dmc_ver2_03.bin
firmware=i915/tgl_dmc_ver2_12.bin
firmware=i915/icl_dmc_ver1_09.bin
firmware=i915/glk_dmc_ver1_04.bin
firmware=i915/kbl_dmc_ver1_04.bin
firmware=i915/skl_dmc_ver1_27.bin
firmware=i915/bxt_dmc_ver1_07.bin
Title: Re: CorePure64 17 won't boot on Dell Pro Max with Intel Core Ultra 5
Post by: patrikg on June 03, 2026, 10:36:05 AM
It seams that XE driver may need also some firmware from i915, because:
Code: [Select]
strings xe.ko | grep firmware | grep bin

I think you can do:
Code: [Select]
modinfo xeto get what firmware it needs. Even grep for firmware like this:
Code: [Select]
modinfo xe | grep ^firmware:
Title: Re: CorePure64 17 won't boot on Dell Pro Max with Intel Core Ultra 5
Post by: nick65go on June 03, 2026, 11:40:44 AM
It works for me (in firefox I see/have hardware acceleration). I added the following parameters:
for grub2: modprobe.blacklist=i915
and for kernel: module_blacklist=i915 xe.force_probe=a7a1 i915.force_probe=!a7a1
the results are below, using firmware for both i915 + xe !! I post them here, hopping they will help TC users/developers.

Code: [Select]
[    0.000000] Linux version 7.0.10-2-cachyos (linux-cachyos@cachyos) (clang version 22.1.5, LLD 22.1.5) #1 SMP PREEMPT_DYNAMIC Thu, 28 May 2026 21:12:58 +0000
Code: [Select]
sudo dmesg | grep i915
[    0.000000] Command line: BOOT_IMAGE=/boot/vmlinuz-linux-cachyos root=UUID=... rw nowatchdog nvme_load=YES zswap.enabled=0 splash loglevel=3 module_blacklist=i915 xe.force_probe=a7a1 i915.force_probe=!a7a1
[    1.359469] Module i915 is blacklisted
[    5.428446] mei_hdcp 0000:00:16.0-b638ab7e-94e2-4ea2-a552-d1c54b627f04: bound 0000:00:02.0 (ops i915_hdcp_ops [xe])

Code: [Select]
sudo dmesg | grep drm
[    0.542892] ACPI: bus type drm_connector registered
[    0.560624] simple-framebuffer simple-framebuffer.0: [drm] Registered 1 planes with drm panic
[    0.560637] [drm] Initialized simpledrm 1.0.0 for simple-framebuffer.0 on minor 0
[    0.562219] simple-framebuffer simple-framebuffer.0: [drm] fb0: simpledrmdrmfb frame buffer device
[    1.753449] xe 0000:00:02.0: [drm] Running in SR-IOV PF mode
[    1.753486] xe 0000:00:02.0: [drm] Found alderlake_p/raptorlake_u (device ID a7a1) integrated display version 13.00 stepping E0
[    1.753493] xe 0000:00:02.0: [drm] PF: migration disabled: requires memory-based IRQ support
[    1.758097] xe 0000:00:02.0: [drm] Finished loading DMC firmware i915/adlp_dmc.bin (v2.20)
[    2.082555] xe 0000:00:02.0: [drm] Tile0: GT0: Using GuC firmware from i915/adlp_guc_70.bin version 70.49.4
[    2.084742] xe 0000:00:02.0: [drm] Tile0: GT0: Using HuC firmware from i915/tgl_huc.bin version 7.9.3
[    2.257139] xe 0000:00:02.0: [drm] Tile0: GT0: vcs1 fused off
[    2.257145] xe 0000:00:02.0: [drm] Tile0: GT0: vcs3 fused off
[    2.257146] xe 0000:00:02.0: [drm] Tile0: GT0: vcs4 fused off
[    2.257147] xe 0000:00:02.0: [drm] Tile0: GT0: vcs5 fused off
[    2.257148] xe 0000:00:02.0: [drm] Tile0: GT0: vcs6 fused off
[    2.257149] xe 0000:00:02.0: [drm] Tile0: GT0: vcs7 fused off
[    2.257150] xe 0000:00:02.0: [drm] Tile0: GT0: vecs1 fused off
[    2.257151] xe 0000:00:02.0: [drm] Tile0: GT0: vecs2 fused off
[    2.257152] xe 0000:00:02.0: [drm] Tile0: GT0: vecs3 fused off
[    2.297996] xe 0000:00:02.0: [drm] Registered 4 planes with drm panic
[    2.310819] [drm] Initialized xe 1.1.0 for 0000:00:02.0 on minor 0
[    2.321632] fbcon: xedrmfb (fb0) is primary device
[    2.365590] xe 0000:00:02.0: [drm] fb0: xedrmfb frame buffer device
[    2.366916] xe 0000:00:02.0: [drm] PF: migration disabled: requires GuC version >= 70.54.0
Code: [Select]
❯ lsmod | grep i915

~
❯ lsmod | grep xe
xe                   4481024  39
drm_suballoc_helper    20480  1 xe
gpu_sched              73728  1 xe
drm_ttm_helper         20480  1 xe
drm_gpuvm              57344  1 xe
drm_exec               12288  2 drm_gpuvm,xe
drm_gpusvm_helper      61440  1 xe
drm_buddy              32768  1 xe
ttm                   131072  2 drm_ttm_helper,xe
i2c_algo_bit           20480  1 xe
drm_display_helper    290816  1 xe
video                  81920  1 xe
cec                   106496  2 drm_display_helper,xe
intel_vsec             24576  3 intel_pmc_ssram_telemetry,pmt_telemetry,xe
Title: Re: CorePure64 17 won't boot on Dell Pro Max with Intel Core Ultra 5
Post by: nick65go on June 04, 2026, 05:16:36 AM
I will close my comments here, because the subject is about gpu-id=7D67.
But because I have a gpu-id=A7A1, I am interested in TC original version to be successfully for my laptop model, which I intend to keep another 6 years (at least). 

So to summarize:
1. firmware for xe (files from /usr/local/lib/firmware/xe) are not always in need (at lest for my CPU)
2. firmware for i915 are in need (seen from dmesg)
3. GPU driver named i915 must be forbid / blacklist as early as possible at booting -- kernel parameter
4. GPU driver named xe must be force probed as kernel parameters.
5. xe driver depends on kernel module configfs.ko (thanks Juanito to highlight this!) https://docs.kernel.org/gpu/xe/xe_configfs.html

for TC17 is in https://mirrors.dotsrc.org/tinycorelinux/17.x/x86_64/tcz/filesystems-6.18.2-tinycore64.tcz.tree
For my kernel was already built-in
Code: [Select]
❯ cat ./modules.builtin | grep conf
kernel/kernel/configs.ko
kernel/fs/configfs/configfs.ko
Code: [Select]
❯ modinfo configfs
name:           configfs
filename:       (builtin)
alias:          fs-configfs
author:         Oracle
file:           fs/configfs/configfs
license:        GPL
version:        0.0.2
description:    Simple RAM filesystem for user driven kernel subsystem configuration.
Code: [Select]
❯ modinfo xe | grep depends
depends:        ttm,drm_display_helper,video,i2c-algo-bit,cec,drm_gpusvm_helper,drm_exec,drm_gpuvm,drm_ttm_helper,gpu-sched,drm_suballoc_helper,drm_buddy,intel-vsec

Title: Re: CorePure64 17 won't boot on Dell Pro Max with Intel Core Ultra 5
Post by: Juanito on June 04, 2026, 08:38:08 AM
firmware-i915 updated, firmware-xe added, both in the tc-17.x x86_64 repo
Title: Re: CorePure64 17 won't boot on Dell Pro Max with Intel Core Ultra 5
Post by: Juanito on June 04, 2026, 09:12:59 AM
...and, with the updated firmware-i915 (?!) things work.

Bizarrely, when graphics-KERNEL is loaded, both i915 and xe kernel modules load.

Code: [Select]
dmesg | grep -i firmware
xe 0000:00:02.0: [drm] Finished loading DMC firmware i915/adlp_dmc.bin (v2.20)
xe 0000:00:02.0: [drm] Tile0: GT0: Using GuC firmware from i915/adlp_guc_70.bin version 70.49.4
xe 0000:00:02.0: [drm] Tile0: GT0: Using HuC firmware from i915/tgl_huc.bin version 7.9.3

Code: [Select]
dmesg
...
Setting dangerous option force_probe - tainting kernel
Console: switching to colour dummy device 80x25
xe 0000:00:02.0: vgaarb: deactivate vga console
xe 0000:00:02.0: [drm] Running in SR-IOV PF mode
xe 0000:00:02.0: [drm] Found alderlake_p/raptorlake_u (device ID a7a1) integrated display version 13.00 stepping E0
xe 0000:00:02.0: vgaarb: VGA decodes changed: olddecodes=io+mem,decodes=none:owns=io+mem
xe 0000:00:02.0: [drm] Finished loading DMC firmware i915/adlp_dmc.bin (v2.20)
xe 0000:00:02.0: [drm] Tile0: GT0: Using GuC firmware from i915/adlp_guc_70.bin version 70.49.4
xe 0000:00:02.0: [drm] Tile0: GT0: Using HuC firmware from i915/tgl_huc.bin version 7.9.3
xe 0000:00:02.0: [drm] Tile0: GT0: vcs1 fused off
xe 0000:00:02.0: [drm] Tile0: GT0: vcs3 fused off
xe 0000:00:02.0: [drm] Tile0: GT0: vcs4 fused off
xe 0000:00:02.0: [drm] Tile0: GT0: vcs5 fused off
xe 0000:00:02.0: [drm] Tile0: GT0: vcs6 fused off
xe 0000:00:02.0: [drm] Tile0: GT0: vcs7 fused off
xe 0000:00:02.0: [drm] Tile0: GT0: vecs1 fused off
xe 0000:00:02.0: [drm] Tile0: GT0: vecs2 fused off
xe 0000:00:02.0: [drm] Tile0: GT0: vecs3 fused off
mei_hdcp 0000:00:16.0-b638ab7e-94e2-4ea2-a552-d1c54b627f04: bound 0000:00:02.0 (ops 0xffffffffa0448730)
[drm] Initialized xe 1.1.0 for 0000:00:02.0 on minor 0
ACPI: video: Video Device [GFX0] (multi-head: yes  rom: no  post: no)
input: Video Bus as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:00/input/input14
fbcon: xedrmfb (fb0) is primary device
Console: switching to colour frame buffer device 240x75
xe 0000:00:02.0: [drm] fb0: xedrmfb frame buffer device
Setting dangerous option force_probe - tainting kernel

Code: [Select]
cat /var/log/Xorg.0.log | grep -i xe
[   364.966] Kernel command line: BOOT_IMAGE=/boot/vmlinuz64_17 quiet text tce=UUID=8dbbcd1f-1057-4c54-8aea-7088ead72620/tce64_tc17 waitusb=10:UUID=8dbbcd1f-1057-4c54-8aea-7088ead72620 host=boxdell noutc noswap syslog xe.force_probe=a7a1 i915.force_probe=!a7a1
[   365.611] (II) modeset(0): glamor X acceleration enabled on Mesa Intel(R) Iris(R) Xe Graphics (RPL-U)

Code: [Select]
inxi -G -x
Graphics:
  Device-1: Intel Raptor Lake-P [Iris Xe Graphics] vendor: Dell driver: xe
    v: kernel arch: Xe bus-ID: 0000:00:02.0
  Display: server: X.org driver: X: loaded: modesetting unloaded: fbdev,vesa
    dri: iris gpu: xe resolution: <missing: xdpyinfo/xrandr>
    resolution: 1920x1200
  API: EGL v: 1.5 drivers: iris,swrast platforms:
    active: gbm,x11,surfaceless,device inactive: wayland
  API: OpenGL v: 4.6 compat-v: 4.5 vendor: mesa v: 26.0.7 note: glxinfo
    missing (EGL sourced) renderer: Mesa Intel Iris Xe Graphics (RPL-U),
    llvmpipe (LLVM 22.1.0 256 bits)
  API: Vulkan v: 1.4.350 drivers: intel,llvmpipe surfaces: N/A devices: 2
  Info: Tools: api: eglinfo,vulkaninfo
Title: Re: CorePure64 17 won't boot on Dell Pro Max with Intel Core Ultra 5
Post by: nick65go on June 04, 2026, 09:56:54 AM
Bizarrely, when graphics-KERNEL is loaded, both i915 and xe kernel modules load.
there are my additions against i915 loading, both in grub.cfg
for grub2: modprobe.blacklist=i915 (on one individual line)
and for kernel: module_blacklist=i915 xe.force_probe=a7a1 i915.force_probe=!a7a1 (on another/kernel line)
Code: [Select]
❯ inxi -G -x
Graphics:
  Device-1: Intel Raptor Lake-P [Iris Xe Graphics] vendor: Hewlett-Packard
    driver: xe v: kernel arch: Xe bus-ID: 00:02.0
  Device-2: Luxvisions Innotech HP True Vision HD Camera driver: uvcvideo
    type: USB bus-ID: 3-1:2
  Display: wayland server: X.org v: 1.21.1.23 with: Xwayland v: 24.1.12
    compositor: kwin_wayland driver: gpu: xe resolution: 1920x1080~60Hz
  API: EGL v: 1.5 drivers: iris,swrast platforms:
    active: gbm,wayland,x11,surfaceless,device inactive: N/A
  API: OpenGL v: 4.6 vendor: intel mesa v: 26.1.1-arch2.1 glx-v: 1.4
    direct-render: yes renderer: Mesa Intel Iris Xe Graphics (RPL-U)
  API: Vulkan v: 1.4.350 drivers: intel surfaces: N/A devices: 1
  Info: Tools: api: clinfo, eglinfo, glxinfo, vulkaninfo
    de: kscreen-console,kscreen-doctor wl: wayland-info
    x11: xdpyinfo, xprop, xrandr
"Sharing is caring"  :)
Title: Re: CorePure64 17 won't boot on Dell Pro Max with Intel Core Ultra 5
Post by: catselbow on June 05, 2026, 11:05:52 AM
One last post on this, and then I'm going to have to move on to other things:

I re-mastered corepur64.gz so that it incorporates the contents of filesystems-6.18.2-tinycore64.tcz, firmware-i915.tcz, firmware-xe.tcz, graphics-6.18.2-tinycore64.tcz, and i2c-6.18.2-tinycore64.tcz (putting the contents into the appropriate directories under /usr/lib). Then I modified syslinux.cfg to add the kernel parameters "module_blacklist=i915 xe.force_probe=7d67 i915.force_probe=!7d67" and re-created the boot USB. Unfortunately, it still hangs.

I need to get this computer to its final destination, so I can't experiment with it any more, but we'll probably be seeing more of these in the future.