CorePure64 17 won't boot on Dell Pro Max with Intel Core Ultra 5

[catselbow]

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.

[Juanito]

I wonder if this is due to a uefi incompatibility - does it boot from a CorePlus iso in legacy bios mode?

[Rich]

Hi catselbow
If your system is using a dedicated GPU, try changing it
in the BIOS to the CPUs graphics hardware.

[gadget42]

mostly for future thread visitors i would reference @Juanito from circa 2015

https://forum.tinycorelinux.net/index.php?topic=19364.0

[Juanito]

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.

[catselbow]

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.

[catselbow]

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)

[catselbow]

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.

[catselbow]

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

[Rich]

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:

[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.

[Rich]

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.

[catselbow]

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.

[Rich]

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.

[catselbow]

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.

[Juanito]

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.