Hi,
if i take a working Tezi Image and i simple uncompress the *.bootfs.tar.xz and without changing i compress again to *.bootfs.tar.xz i have smaller size.
Then i can install with EasyInstaller, but when i start the board the Kernel doesn’t starts:
CPU: Freescale i.MX6Q rev1.6 996 MHz (running at 792 MHz)
CPU: Extended Commercial temperature grade (-20C to 105C) at 27C
Reset cause: POR
DRAM: 1 GiB
PMIC: device id: 0x10, revision id: 0x21, programmed
Core: 127 devices, 21 uclasses, devicetree: separate
WDT: Started watchdog@20bc000 with servicing every 1000ms (128s timeout)
MMC: FSL_SDHC: 1, FSL_SDHC: 2, FSL_SDHC: 0
Loading Environment from MMC… Reading from MMC(0)… OK
In: serial@2020000
Out: serial@2020000
Err: serial@2020000
Model: Toradex 0027 Apalis iMX6Q 1GB V1.1Y
Serial#: 11057085
Net: eth0: ethernet@2188000
Hit any key to stop autoboot: 0
MMC: no card present
MMC: no card present
switch to partitions #0, OK
mmc0(part 0) is current device
Scanning mmc 0:1…
MMC: no card present
MMC: no card present
No EFI system partition
No EFI system partition
Failed to persist EFI variables
No EFI system partition
Failed to persist EFI variables
No EFI system partition
Failed to persist EFI variables
Loading Boot0000 ‘mmc 0’ failed
EFI boot manager: Cannot load any image
Can you please tell me why?
Thank you in advance,
Patrick
Hi, I’m the Toradex AI Assistant. The Toradex Support team will follow up with you shortly!
Did you like my answer?
Hello Patrick,
Thank you for reaching out with your question. When you decompress and then recompress the bootfs.tar.xz file from a Toradex Easy Installer image, the resulting file might differ in size due to variations in compression settings or algorithms. This can lead to issues if the recompressed file does not match the expected format or integrity required by the boot process.
Here are some potential reasons and steps to address the issue:
Compression Settings: Ensure you are using the same compression settings as the original file. The xz compression tool has various options that can affect the output, such as compression level and dictionary size. Using different settings might result in a file that is not compatible with the bootloader’s expectations.
File Integrity: Verify that the recompressed file maintains the integrity of the original. Any corruption or alteration during the decompression or recompression process can prevent the system from booting. Use checksums (e.g., SHA256) to compare the original and recompressed files.
File System Compatibility: Ensure that the file system used during recompression is compatible with the bootloader. Some file systems might introduce metadata or other changes that affect the boot process.
Testing: Try using the original compression tool and settings used by Toradex to create the initial image. This might involve using specific versions of the xz tool or specific command-line options.
By following these steps, you should be able to identify and resolve the issue with the recompressed bootfs.tar.xz file. If the problem persists, consider starting with a fresh image and carefully documenting each step to identify where the process might be going wrong.
I hope this helps you resolve the issue. If you have any more questions, feel free to ask.
Best regards,
Toradex AI Assistant
Please, also check if these links can help you solve your problem:
As the Toradex AI Assistant stated, you may have used different compression settings or algorithms to obtain the newly compressed bootfs.tar.xz file, which would explain the size difference.
Could you please share more information about what you intend to do with this? If your goal is to change something inside the bootfs to generate a custom image, going this way would not be the correct approach.
