Khadas Edge2 Pro review – A Rockchip RK3588S SBC tested with Ubuntu 22.04

We’ve had a sample of the Khadas Edge2 single board computer powered by Rockchip RK3588S octa-core Cortex-A76/A55 processor for a couple of weeks, and now that the board is officially launched we can post our review of the board with Ubuntu 22.04, and we’ll check out Android 12 later on.

Khadas Edge2 Pro accessories

The Khadas Edge2 comes in two variants: Basic and Pro, We received the Edge2 Pro SBC with 16GB RAM and 64GB flash that ships with two WiFi antennas by default, but the company also sent a low-profile fansink and thermal pad for cooling that in theory would be optional, but in practice, it is required as while the board runs fairly cool considering the performance it brings, it still needs a heatsink to prevent overheating and throttling. The fan may not really be necessary though as we’ll see below.

I’d recommend installing the antennas before the fansink. The MHF4 antenna connectors are tiny, and I find antennas really hard to insert on the board properly. They can detach easily too, and I ended up damaging one of the connectors, just like I did with the Khadas VIM4 featuring the exact same tiny connectors. The Khadas VIM1S SBC has a larger u.FL connector, and it’s much easier to install the single antenna that comes with the board. I wish Khadas could use those on all their boards, but space on the PCB may be an issue.

The board remains fairly slim even after the heatsink is installed. I measured the thickness to be about 11mm with a caliper.

Installing Ubuntu 22.04 with OOWOW system

Let’s connect the board to an HDMI connector and a keyboard because connecting it to a USB PD adapter to power it up. If you don’t like to mess around with MicroSD cards and/or USB cables together with Windows or command line tools, you’ll love the Khadas boards as they now come with the OOWOW system that allows the user to download and flash his/her selected OS image with an easy to use interface.

 

Upon the boot first, we are greeted with the OOWOW Wizard in order to configure WiFi, and then select an OS image.

 

At the time of testing, Android 11, Android 12, Ubuntu 22.04 Desktop and Ubuntu 22.04 Server were available. I went with the Ubuntu 22.04 (Gnome) Desktop image, and after a couple of minutes I was greeted with a login prompt.

The default password for the Khadas user is simply “khadas”. We are not asked to change the username or password upon the first login, so it might be something that needs to be implemented later to comply with some new regulations, especially openssh-server is enabled by default if I remember correctly. For the time being, we can just change the password manually.

Ubuntu 22.04 system info on Khadas Edge2

Let’s check out some system information starting with the kernel log obtained with dmesg.

After connecting to my WiFi router, I did a system upgrade, and rebooted the system. Let’s get more details:

It’s running Ubuntu 22.04 on Linux 5.10.66, and we’ve got about 16 GB RAM and a 57GB root partition as expected. Let’s install and run inxi:

We can see the Cortex-A76 are clocked at up to 2304 MHz, and the Cortex-A55 cores up to 1,800 MHz, but more on that latter. ZRAM is also enabled (good!) although with 16GB we have plenty of physical memory.

Khadas Edge2 benchmarks in Linux

We can now run some Linux benchmarks on the Khadas Edge2 board to compare it to the Rockchip RK3588-powered ROCK 5B, Raspberry Pi 4, and other single board computers. Note that after a reboot, the CPU default to the performance governor.

I started with the usual sbc-bench.sh from Thomas kaiser:

If we look at the full results, we can see the measured frequency for the Corex-A76 cores is 2,257 MHz for one two-core cluster, and 2,259 for the other two-core cluster, as about the 2.25GHz advertised by Khadas. The system temperature never exceeded 61.9°C during the benchmark in a room with an ambient temperature of 28°C, so the cooling solution is perfectly suitable, and throttling did not occur. I initially thought the fan was never used, but looking closer the fan was indeed activated. It’s just close to silent.

The Khadas Edge2 SBC has about the same performance as the Rock 5B, as one would have expected, and is quite faster than the Khadas VIM4 powered by an Amlogic A311D2 processor, more than twice as fast as a Raspberry Pi 4. The ODROID-N2+ SBC based on the older Amlogic S922X processor @ 2.4 GHz is in the middle of the pack.

Let’s now switch to a browser benchmark with Speedometer 2.0.

I’m using a small 10.1-inch display with 1280×720 resolution, but I forced it to 1920×1080 with 125% fractional scaling before testing.

But just to make sure, I tested it again once while connected to a Full HD display with 1920×1080 resolution and no fractional scaling, and I got similar results at 78.84 points in Chromium and 53.14 in Firefox, so it’s not that different.

The Khadas Edge2 board is almost four times faster than an overclocked Raspberry Pi 4 in this particular benchmark. Note that improvements to Chromium and 3D graphics acceleration may play a role here too, but performance is nonetheless impressive. As seen with other Arm SBCs, Chromium performs quite better than Firefox with Speedometer 2.0.

Let’s run some benchmarks from the Phoronix TestSuite to compare Khadas Edge2 to UP 4000 SBC with an Intel Celeron N3350 dual-core Apollo Lake processor clocked at 2.4 GHz along as Jetson Nano and Raspberry Pi 4. You’ll find the full results on the Openbenchmarking website.

As we can some of the tests failed to complete:

But the Khadas Edge2 Pro was outperforming all other platforms in all tests that were completed, except for SQLite.  So I’d expect the Rockchip RK3588S to offer similar performance as some Gemini Lake or even Jasper Lake systems.

Note that the Khadas Edge2 was the only platform with the governor set to performance:

Phoronix provides an out-of-the-box “benchmark experience”, and it should be noted the scores of other systems may have been higher if the governor was set to performance, to what extent is hard to know.

3D graphics acceleration in Ubuntu 22.04

When I first tested 3D graphics supports, I ran glxinfo:

It seems to indicate 3D graphics acceleration is not enabled as it’s relying on the llvmpipe software driver. But that command is only valid for X11, and Khadas’ Ubuntu 22.04 image is using Wayland windowing system instead.

So we need to use eglinfo instead, and we can see the Mali GPU driver is used:

There’s an error in the output above, but I could confirm this works using glmark2-es2-wayland with instructions from Khadas. We are first asked to set to GPU governor to performance:

Now we can install the program and run the program:

Here’s the output from glmark2-es2-wayland:

A 4,005 score is quite impressive and four times the ODROID-N2+ score (970 points), and the Khadas Edge2 fares much better even after “optimizations” where the ODROID-N2+ board can get 1,244 points.

We can also play some games using the PPSSPP emulator:

Just type PPSSPP in the dash to launch the emulator and install some games.

The Tetris-like game above runs at 60 fps without issues. Finally, we were told SuperTuxkart would work fine, but it only showed in a quarter window, and changing the display settings within the game did not help.

The strange thing is that it works on Khadas’ side, and it’s unclear why it doesn’t for me.

There’s also one specific use case where 3D graphics acceleration does not work: dual display setups with one monitor connected to the HDMI, and the other through the USB-C port. In that case, the system will switch to the X11 windowing system, and 3D graphics acceleration is only supported with Wayland.

Khadas Edge2 NPU support

Another good news is that NPU support is working at launch with Python and C++ SDKs. I had to use the SDK and samples from a 7z file, but the code has now been released on Github.

We’ll first need to install dependencies and the NPU toolchain to run the Python samples:

We can now try a sample such as resnet18:

The program basically loads the image “space_shuttle_224.jpg” and a pre-trained model and finds it’s the Space Shuttle or maybe just a spaceship with 99.96% probability against other pre-trained objects.

We can also try the face_mask demo:

There’s nothing interesting about the terminal output, but the Python program will generate an image (out.jpg) with a box to show where the face mask(s) is/are.

I’ve replaced the image in /data/img/face.jpg with a crowd wearing face masks to check out the results:

As you can see above, the resulting out.jpg does not come with any boxes meaning the program did not detect any masks in the photo. I think we would have to change a few parameters in the Python program to match our image:

I’m just not sure which ones, and Khadas was not able to help in time for this review. I’ll update this section if a solution is found.

Storage testing and benchmarks

I’ve installed iozone3 to first test the 64GB eMMC flash performance:

We’ve got sequential reads up to 300 MB/s, writes up to 200 MB/s, and decent random R/W performance. For comparison, the eMMC flash in a Raspberry Pi CM4 is limited to 100MB/s.

Now let’s test the USB 3.0 Type-C (5Gbps) port with ORICO USB 3.2 Gen 1 enclosure fitted with an Apacer NVMe SSD capable of up to 1,800 MB/s reads, and 1,100 MB/s writes, and formatted with EXT-4.

I’ve repeated the test several times, with the same results. about 342 MB/s sequential reads and 398MB/s write speeds. I think that’s roughly what we should expect over a 5 Gbps USB port although some optimizations may push that over 400MB/s.

Networking (WiFi & 2.5GbE)

Let’s check out WiFi 6 performance bearing in mind I only have the larger antenna connected:

• Upload
  
  $ iperf3 -t 60 -c 192.168.31.48 -i 10 Connecting to host 192.168.31.48, port 5201 [ 5] local 192.168.31.197 port 43180 connected to 192.168.31.48 port 5201 [ ID] Interval Transfer Bitrate Retr Cwnd [ 5] 0.00-10.00 sec 543 MBytes 455 Mbits/sec 0 3.15 MBytes [ 5] 10.00-20.00 sec 539 MBytes 452 Mbits/sec 0 3.15 MBytes [ 5] 20.00-30.00 sec 540 MBytes 453 Mbits/sec 1 2.97 MBytes [ 5] 30.00-40.00 sec 488 MBytes 409 Mbits/sec 0 3.01 MBytes [ 5] 40.00-50.00 sec 489 MBytes 410 Mbits/sec 0 3.01 MBytes [ 5] 50.00-60.00 sec 576 MBytes 483 Mbits/sec 0 3.01 MBytes - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval Transfer Bitrate Retr [ 5] 0.00-60.00 sec 3.10 GBytes 444 Mbits/sec 1 sender [ 5] 0.00-60.02 sec 3.10 GBytes 443 Mbits/sec receiver iperf Done.

  1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16

  $ iperf3 -t 60 -c 192.168.31.48 -i 10 Connecting to host 192.168.31.48, port 5201 [  5] local 192.168.31.197 port 43180 connected to 192.168.31.48 port 5201 [ ID] Interval           Transfer     Bitrate         Retr  Cwnd [  5]   0.00-10.00  sec   543 MBytes   455 Mbits/sec    0   3.15 MBytes       [  5]  10.00-20.00  sec   539 MBytes   452 Mbits/sec    0   3.15 MBytes       [  5]  20.00-30.00  sec   540 MBytes   453 Mbits/sec    1   2.97 MBytes       [  5]  30.00-40.00  sec   488 MBytes   409 Mbits/sec    0   3.01 MBytes       [  5]  40.00-50.00  sec   489 MBytes   410 Mbits/sec    0   3.01 MBytes       [  5]  50.00-60.00  sec   576 MBytes   483 Mbits/sec    0   3.01 MBytes       - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval           Transfer     Bitrate         Retr [  5]   0.00-60.00  sec  3.10 GBytes   444 Mbits/sec    1             sender [  5]   0.00-60.02  sec  3.10 GBytes   443 Mbits/sec                  receiver   iperf Done.

• Download
  
  ----------------------------------------------------------- Server listening on 5201 ----------------------------------------------------------- Accepted connection from 192.168.31.197, port 43182 [ 5] local 192.168.31.48 port 5201 connected to 192.168.31.197 port 43184 [ ID] Interval Transfer Bitrate Retr Cwnd [ 5] 0.00-10.00 sec 988 MBytes 829 Mbits/sec 0 3.03 MBytes [ 5] 10.00-20.00 sec 981 MBytes 823 Mbits/sec 0 3.03 MBytes [ 5] 20.00-30.00 sec 985 MBytes 826 Mbits/sec 0 3.03 MBytes [ 5] 30.00-40.00 sec 991 MBytes 832 Mbits/sec 0 3.03 MBytes [ 5] 40.00-50.00 sec 985 MBytes 826 Mbits/sec 0 3.03 MBytes [ 5] 50.00-60.00 sec 984 MBytes 825 Mbits/sec 0 3.03 MBytes [ 5] 60.00-60.02 sec 1.25 MBytes 663 Mbits/sec 0 3.03 MBytes - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval Transfer Bitrate Retr [ 5] 0.00-60.02 sec 5.78 GBytes 827 Mbits/sec 0 sender ----------------------------------------------------------- Server listening on 5201 -----------------------------------------------------------

  1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19

  ----------------------------------------------------------- Server listening on 5201 ----------------------------------------------------------- Accepted connection from 192.168.31.197, port 43182 [  5] local 192.168.31.48 port 5201 connected to 192.168.31.197 port 43184 [ ID] Interval           Transfer     Bitrate         Retr  Cwnd [  5]   0.00-10.00  sec   988 MBytes   829 Mbits/sec    0   3.03 MBytes       [  5]  10.00-20.00  sec   981 MBytes   823 Mbits/sec    0   3.03 MBytes       [  5]  20.00-30.00  sec   985 MBytes   826 Mbits/sec    0   3.03 MBytes       [  5]  30.00-40.00  sec   991 MBytes   832 Mbits/sec    0   3.03 MBytes       [  5]  40.00-50.00  sec   985 MBytes   826 Mbits/sec    0   3.03 MBytes       [  5]  50.00-60.00  sec   984 MBytes   825 Mbits/sec    0   3.03 MBytes       [  5]  60.00-60.02  sec  1.25 MBytes   663 Mbits/sec    0   3.03 MBytes       - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval           Transfer     Bitrate         Retr [  5]   0.00-60.02  sec  5.78 GBytes   827 Mbits/sec    0             sender ----------------------------------------------------------- Server listening on 5201 -----------------------------------------------------------

That’s pretty good, and the download speed is not that far from what we’d get with a Gigabit Ethernet port.

While Khadas Edge2 does not come with an Ethernet port at all, it’s still possible to add 2.5GbE through a 2.5GbE USB Type-C dongle.

Ultra-compact boards are nice, but as you can see, I had to remove the USB mouse and HDMI cable to test 2.5GbE. This could easily be resolved with an extension cable. Let’s get to the results:

• Upload
  
  Accepted connection from 192.168.31.112, port 33996 [ 5] local 192.168.31.48 port 5201 connected to 192.168.31.112 port 33998 [ ID] Interval Transfer Bitrate [ 5] 0.00-10.00 sec 702 MBytes 589 Mbits/sec [ 5] 10.00-20.00 sec 1.40 GBytes 1.20 Gbits/sec [ 5] 20.00-30.00 sec 1.09 GBytes 936 Mbits/sec [ 5] 30.00-40.00 sec 472 MBytes 396 Mbits/sec [ 5] 40.00-50.00 sec 1.30 GBytes 1.11 Gbits/sec [ 5] 50.00-60.00 sec 480 MBytes 403 Mbits/sec [ 5] 60.00-61.30 sec 0.00 Bytes 0.00 bits/sec - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval Transfer Bitrate [ 5] 0.00-61.30 sec 5.40 GBytes 757 Mbits/sec receiver

  1 2 3 4 5 6 7 8 9 10 11 12 13

  Accepted connection from 192.168.31.112, port 33996 [  5] local 192.168.31.48 port 5201 connected to 192.168.31.112 port 33998 [ ID] Interval           Transfer     Bitrate [  5]   0.00-10.00  sec   702 MBytes   589 Mbits/sec                   [  5]  10.00-20.00  sec  1.40 GBytes  1.20 Gbits/sec                   [  5]  20.00-30.00  sec  1.09 GBytes   936 Mbits/sec                   [  5]  30.00-40.00  sec   472 MBytes   396 Mbits/sec                   [  5]  40.00-50.00  sec  1.30 GBytes  1.11 Gbits/sec                   [  5]  50.00-60.00  sec   480 MBytes   403 Mbits/sec                   [  5]  60.00-61.30  sec  0.00 Bytes  0.00 bits/sec                   - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval           Transfer     Bitrate [  5]   0.00-61.30  sec  5.40 GBytes   757 Mbits/sec                  receiver

• Download
  
  Accepted connection from 192.168.31.112, port 33992 [ 5] local 192.168.31.48 port 5201 connected to 192.168.31.112 port 33994 [ ID] Interval Transfer Bitrate Retr Cwnd [ 5] 0.00-10.00 sec 509 MBytes 427 Mbits/sec 83 112 KBytes [ 5] 10.00-20.00 sec 460 MBytes 386 Mbits/sec 88 80.6 KBytes [ 5] 20.00-30.00 sec 479 MBytes 401 Mbits/sec 75 94.7 KBytes [ 5] 30.00-40.00 sec 507 MBytes 426 Mbits/sec 70 191 KBytes [ 5] 40.00-50.00 sec 500 MBytes 419 Mbits/sec 74 139 KBytes [ 5] 50.00-60.00 sec 470 MBytes 394 Mbits/sec 79 83.4 KBytes - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval Transfer Bitrate Retr [ 5] 0.00-60.00 sec 2.86 GBytes 409 Mbits/sec 470 sender -----------------------------------------------------------

  1 2 3 4 5 6 7 8 9 10 11 12 13

  Accepted connection from 192.168.31.112, port 33992 [  5] local 192.168.31.48 port 5201 connected to 192.168.31.112 port 33994 [ ID] Interval           Transfer     Bitrate         Retr  Cwnd [  5]   0.00-10.00  sec   509 MBytes   427 Mbits/sec   83    112 KBytes       [  5]  10.00-20.00  sec   460 MBytes   386 Mbits/sec   88   80.6 KBytes       [  5]  20.00-30.00  sec   479 MBytes   401 Mbits/sec   75   94.7 KBytes       [  5]  30.00-40.00  sec   507 MBytes   426 Mbits/sec   70    191 KBytes       [  5]  40.00-50.00  sec   500 MBytes   419 Mbits/sec   74    139 KBytes       [  5]  50.00-60.00  sec   470 MBytes   394 Mbits/sec   79   83.4 KBytes       - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval           Transfer     Bitrate         Retr [  5]   0.00-60.00  sec  2.86 GBytes   409 Mbits/sec  470             sender -----------------------------------------------------------

Truly horrific numbers, but I can see the cdc_ncm driver is loaded:

I wanted to use the r8152 driver instead, but the method I used on my laptop somehow did not work, and I’m not ready to spend countless hours again making a Realtek 2.5GbE USB dongle work properly…

So I switched to a MINI USB-C dock with Gigabit Ethernet.

and it works well in both directions:

• Upload
  
  Accepted connection from 192.168.31.104, port 40016 [ 5] local 192.168.31.48 port 5201 connected to 192.168.31.104 port 40018 [ ID] Interval Transfer Bitrate [ 5] 0.00-10.00 sec 1.09 GBytes 932 Mbits/sec [ 5] 10.00-20.00 sec 1.09 GBytes 933 Mbits/sec [ 5] 20.00-30.00 sec 1.09 GBytes 933 Mbits/sec [ 5] 30.00-40.00 sec 1.09 GBytes 933 Mbits/sec [ 5] 40.00-50.00 sec 1.09 GBytes 933 Mbits/sec [ 5] 50.00-60.00 sec 1.09 GBytes 933 Mbits/sec [ 5] 60.00-60.00 sec 437 KBytes 902 Mbits/sec - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval Transfer Bitrate [ 5] 0.00-60.00 sec 6.52 GBytes 933 Mbits/sec receiver

  1 2 3 4 5 6 7 8 9 10 11 12 13

  Accepted connection from 192.168.31.104, port 40016 [  5] local 192.168.31.48 port 5201 connected to 192.168.31.104 port 40018 [ ID] Interval           Transfer     Bitrate [  5]   0.00-10.00  sec  1.09 GBytes   932 Mbits/sec                   [  5]  10.00-20.00  sec  1.09 GBytes   933 Mbits/sec                   [  5]  20.00-30.00  sec  1.09 GBytes   933 Mbits/sec                   [  5]  30.00-40.00  sec  1.09 GBytes   933 Mbits/sec                   [  5]  40.00-50.00  sec  1.09 GBytes   933 Mbits/sec                   [  5]  50.00-60.00  sec  1.09 GBytes   933 Mbits/sec                   [  5]  60.00-60.00  sec   437 KBytes   902 Mbits/sec                   - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval           Transfer     Bitrate [  5]   0.00-60.00  sec  6.52 GBytes   933 Mbits/sec                  receiver

• Download
  
  Accepted connection from 192.168.31.104, port 40020 [ 5] local 192.168.31.48 port 5201 connected to 192.168.31.104 port 40022 [ ID] Interval Transfer Bitrate Retr Cwnd [ 5] 0.00-10.00 sec 1.10 GBytes 944 Mbits/sec 0 645 KBytes [ 5] 10.00-20.00 sec 1.10 GBytes 942 Mbits/sec 0 987 KBytes [ 5] 20.00-30.00 sec 1.10 GBytes 942 Mbits/sec 0 987 KBytes [ 5] 30.00-40.00 sec 1.10 GBytes 942 Mbits/sec 0 987 KBytes [ 5] 40.00-50.00 sec 1.10 GBytes 942 Mbits/sec 0 987 KBytes [ 5] 50.00-60.00 sec 1.10 GBytes 942 Mbits/sec 0 987 KBytes - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval Transfer Bitrate Retr [ 5] 0.00-60.00 sec 6.58 GBytes 942 Mbits/sec 0 sender -----------------------------------------------------------

  1 2 3 4 5 6 7 8 9 10 11 12 13

  Accepted connection from 192.168.31.104, port 40020 [  5] local 192.168.31.48 port 5201 connected to 192.168.31.104 port 40022 [ ID] Interval           Transfer     Bitrate         Retr  Cwnd [  5]   0.00-10.00  sec  1.10 GBytes   944 Mbits/sec    0    645 KBytes       [  5]  10.00-20.00  sec  1.10 GBytes   942 Mbits/sec    0    987 KBytes       [  5]  20.00-30.00  sec  1.10 GBytes   942 Mbits/sec    0    987 KBytes       [  5]  30.00-40.00  sec  1.10 GBytes   942 Mbits/sec    0    987 KBytes       [  5]  40.00-50.00  sec  1.10 GBytes   942 Mbits/sec    0    987 KBytes       [  5]  50.00-60.00  sec  1.10 GBytes   942 Mbits/sec    0    987 KBytes       - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval           Transfer     Bitrate         Retr [  5]   0.00-60.00  sec  6.58 GBytes   942 Mbits/sec    0             sender -----------------------------------------------------------

Bluetooth

I’ve tried Bluetooth by connecting my phone to the Khadas Edge2 Pro board. The good news is that Bluetooth is enabled and the connection was successful.

I was not able to send files though, as the Khadas board only shows up as an audio device. So I tried to use it as a speaker through the connected HDMI display, and the audio would consistently cut.

I could also connect the board to a Bluetooth headset, but I had the same problem with the audio cutting regularly.

It might work better with Bluetooth HID devices, but I don’t have any to test.

GPIO testing

The GPIO situation is exactly the same as on the Rock 5B board.

and we can control those through sysfs:

The main difference is on the hardware side since the Khadas Edge2 does not come with a typical female header, but instead two FPC connectors for I/O that require add-on boards.

I can also see WiringPiu library is installed, but could not test it due to time constraints:

VPU (Video Processing Unit)

Khadas told me both hardware and software video decoding work on the Khadas Edge2. I first tried a 4K YouTube video in Firefox.

It’s relying on software decode considering the relatively high CPU usage, but a 4K video @ 30 fps plays fine without any frames dropped, except a few at the beginning.

We’ll need to use gstreamer to play an H.264 video with hardware decoding. I was given this command line:

It just did not work for me:

That’s the tricky part of having to review a board before launch and without documentation…

We can try to find the proper decoder with gst-inpect:

It looks like mppvideodec should be used instead of v4l2h264dec, but I could not manage to find the right command…

[Update from Khadas:

Edge2 gstreamer hardware decoder under Ubuntu 22.04 still has some issues need to fix up, so at this moment it doesn’t work properly due to the waylans sink issue.

Power consumption

Some power consumption numbers for reference:

• Power off – 0.0 Watt
• Idle – 2.9 Watts
• 4K YouTube Video in Firefox (full screen) – 7.5 to 10.9 Watts
• Stress test on all 8 cores (stress -c 8) – 9.0 Watts

That’s quite a power-efficient board considering the processing power of the device. It also further illustrates the CPU is only part of the equation in modern complex SoCs, as 4K video playback’s peak power consumption is close to 11 Watts.

Summary

The Khadas Edge2 Pro performs well in Ubuntu 22.04, and features on Linux are better supported than I would have expected at that time, with great progress since I tested Debian 11 on the Rock 5B board just two months ago. I still have several issues here and there, but that should be expected considering I got the board before it launched.

The Khadas Edge2 has just launched as part of Khadas’ Autumn launch event both as a maker kit as reviewed here and an Arm mini PC with enclosure. Other products part of the launch include the entry-level Khadas VIM1S SBC, and devices for audiophiles: the Tone2 DAC and BT Magic module. You can purchase the Khadas Edge2 on Amazon or Khadas online store.

Khadas promises to ship the Edge2 Maker Kits ship within 2 days once the order is confirmed, and Edge2 ARM PCs will ship on or before mid-December 2022.

Continue reading Khadas Edge2 review with Android 12.

Support CNX Software! Donate via cryptocurrencies, become a Patron on Patreon, or purchase goods on Amazon or Aliexpress