Greetings. Today we are pleased to release BIOS version V001 for Radxa X4.
Main Features
Supports CPU PL1 and PL2 customization and performance related settings
Improve memory compatibility, support 4/8/12GB memory
Supports RTC timed wake-up
2.5G wired network support POE, PXE, WOL function.
Support software or hardware reset RP2040 to bootsel
More detailed documentation refer to https://docs.radxa.com/en/x/x4
BIOS update tools at https://docs.radxa.com/en/x/x4/bios/update-bios
Is it possible to enable In-band ECC support in the BIOS of the Radxa X4?
Not support for now
I have read a few guides and it seems the board suffers from high temperatures meaning that the current case/fan options dont do its justice. I feel this is crtitic… Do you guys have been trough the same ? Will there be an solution?
Guess this was the wildest ive seen.
The X4 was verified with our case.
With default BIOS, aida64 running fpu, the cpu stabilized at around 60 degrees.
With CPU TDP PL1 not limited, cpu temps are around 90 degrees.
The key point is that the cpu and the heat sink should have good contact and the thermal conductivity of the silicone should be higher than 11W/ (m-K).
Anyway, x86 needs better Thermal Solutions than arm.
based on my test results I can confirm the same results as you’ve stated ryan 62 degrees at full max load. 33-36 at idle
Great. thanks for your confirm
Hi,
I have a new RADXA X4 with 64GB emmc on board.
But I’m not able to boot from this storage. In your help you have a option to
auto enable it ( Advanced->SDIO Configuration).
You have made this help with an older bios version.
With this new Version I do not see this option.
So for me the emmc is useless when I cannot boot form it…
Hello friend
The emmc for X4 is always available
In the latest BIOS, we also can see the emmc list at Advanced->SDIO configuration
And we can install windows/linux both into emmc and bootup
Can you confirm the BIOS version you saw in the BIOS? and follow the docs to install the system into emmc
Hi Ryann,
thank’s for your fast response. Now I tried to install Ubuntu this works fine. But when I try to install my custom OS (barebox + linux) I can’t see the EFI boot device. When do you show the boot device? What do you expect? When I do the same on a Intel NUC device or a LivaQ2 device i can boot my image?
this is my fdisk -l output
Disk /dev/mmcblk0: 58 GB, 62537072640 bytes, 122142720 sectors
1908480 cylinders, 4 heads, 16 sectors/track
Units: sectors of 1 * 512 = 512 bytes
Device Boot StartCHS EndCHS StartLBA EndLBA Sectors Size Id Type
/dev/mmcblk0p1 * 128,0,1 447,3,16 8192 28671 20480 10.0M ef EFI (FAT-12/16/32)
/dev/mmcblk0p2 768,0,1 1023,3,16 49152 10534911 10485760 5120M 83 Linux
/dev/mmcblk0p3 1023,3,16 1023,3,16 10534912 21020671 10485760 5120M 83 Linux
/dev/mmcblk0p4 1023,3,16 1023,3,16 21020672 122142719 101122048 48.2G 83 Linux
Disk /dev/mmcblk0boot0: 4 MB, 4194304 bytes, 8192 sectors
128 cylinders, 4 heads, 16 sectors/track
Units: sectors of 1 * 512 = 512 bytes
and this is on the EFI partition
root@foo:~ ll /mnt/
drwxr-xr-x 4 root root 16384 Jan 1 1970 .
drwxr-xr-x 20 root root 4096 Dec 1 00:00 …
drwxr-xr-x 4 root root 2048 Dec 1 00:00 EFI
drwxr-xr-x 2 root root 2048 Dec 1 00:00 network-drivers
root@foo:~ ll /mnt/EFI/
drwxr-xr-x 4 root root 2048 Dec 1 00:00 .
drwxr-xr-x 4 root root 16384 Jan 1 1970 …
drwxr-xr-x 2 root root 2048 Dec 1 00:00 BAREBOX
drwxr-xr-x 2 root root 2048 Dec 1 00:00 BOOT
root@foo:~ ll /mnt/EFI/BAREBOX/
drwxr-xr-x 2 root root 2048 Dec 1 00:00 .
drwxr-xr-x 4 root root 2048 Dec 1 00:00 …
-rwxr-xr-x 1 root root 1369 Dec 1 00:00 state.dtb
root@foo:~ ll /mnt/EFI/BOOT/
drwxr-xr-x 2 root root 2048 Dec 1 00:00 .
drwxr-xr-x 4 root root 2048 Dec 1 00:00 …
-rwxr-xr-x 1 root root 590090 Dec 1 00:00 BOOTx64.EFI
Please try extended EFI partition to 100MB, we have previously encountered the problem that the efi partition is less than 100MB and cannot be boot
