Physical Intel

Own AI Teams 1. AI Home home network
1

Bare Intel Home

Creates a dual boot iso that can boot up in laptop as well as in the cloud

Bare Intel Home Future

Cloud Intel Home

Cloud Intel Home is the same as the current Bare Intel Home (which is in a ISO Format that duel boots on USB and in the Cloud).

Lean Intel Home

The same laptop previously working tells us its CPU, storage and Proxmox support are probably fine. The regression is in the installer’s boot-media design:

  • The older direct USB used a relatively small installer initramfs and stored other installation material separately on the USB.
  • The current ISO-based Full Hardware image asks GRUB to load the installer plus the complete firmware collection—roughly 500 MB—as one initramfs.
  • This Acer’s older UEFI cannot allocate a suitable contiguous memory area for it.
  • Continuing without the initramfs produces the second kernel panic.

The documentation indicates that by v1.8.23 the project had already moved to the large ISO format, so the successful installation was probably from before v1.8.23 or from the old direct-USB engine.

For the next version, I would not simply restore server-side USB passthrough. A safer design is:

  • Keep Createstation’s web builder inside the unprivileged LXC.
  • For Bare Intel, produce a downloadable raw USB .img or a revised ISO with a small boot initramfs.
  • Keep the large firmware collection as ordinary files on the media and load only what the installer needs.
  • Retain the current ISO output for cloud and VirtualBox.
  • Add an initramfs-size check so this incompatibility cannot silently return.

That would reproduce the important benefit of the old USB layout without allowing the web-builder LXC to access physical USB devices.

problem it is intended on fixing

These two screens are one failure chain:

  1. GRUB cannot allocate a suitable contiguous memory region for Createstation’s large auto-initrd.gz.
  2. After a key is pressed, GRUB starts the kernel without that initramfs.
  3. The kernel therefore cannot find its installer root filesystem and reports:
    VFS: Unable to mount root fs on unknown-block(0,0).

No installation has started and no internal disks have been modified.

The underlying cause is that the Full Hardware image appends Debian’s complete firmware archive—approximately 500 MB—to the installer initramfs. Older UEFI implementations, such as this 2013 Acer Aspire V5-572P BIOS V2.06, can fail to place such a large initramfs even when the laptop has plenty of total RAM. Debian documents the same GRUB problem with large firmware initramfs files and suggests reducing or recompressing them; GNU GRUB has also discussed this exact allocator error with large initramfs images. Debian installer firmware guidance, GNU GRUB discussion.

For an immediate test:

  • Restart instead of continuing past the first error.
  • If the Acer firmware offers Legacy/CSM boot, select the non-UEFI USB entry. The ISO supports both Legacy BIOS and UEFI.
  • If only UEFI is available, check whether Acer provides a newer BIOS for this exact model.
  • Adding RAM may not help because the problem is the firmware memory map and contiguous allocation, not necessarily total memory.

This was not introduced by the v2.0.20 webpage changes: the v2.0.19 and v2.0.20 installer engines are byte-identical.

For the proper next release, I recommend changing the physical-hardware image so the entire firmware collection is not placed in one enormous early initramfs—preferably keeping firmware on the ISO and loading it after the installer boots, with xz recompression as an additional safeguard. We should also add a build-time Full Hardware initramfs size limit. I have not modified or published anything yet.

USB Intel Home

A full bootable Home running from an USB stick instead of having to be installed locally on a computer.

Team Compute solves the privacy vs trust dilemma in everyday physical interaction, introducing new possibilities in every physical interactions, from retail to dating.