geerlingguy / sbc-reviews

Jeff Geerling's SBC review data - Raspberry Pi, Radxa, Orange Pi, etc.
MIT License
503 stars 11 forks source link

ArmSoM Sige7 / Banana Pi BPI-M7 #56

Open geerlingguy opened 5 hours ago

geerlingguy commented 5 hours ago

DSC01643

Basic information

Linux/system information

# output of `screenfetch`
PASTE_HERE

# output of `uname -a`
PASTE_HERE

Benchmark results

CPU

Power

Disk

MANUFACTURER_AND_MODEL_OF_DISK_HERE

Benchmark Result
iozone 4K random read TODO MB/s
iozone 4K random write TODO MB/s
iozone 1M random read TODO MB/s
iozone 1M random write TODO MB/s
iozone 1M sequential read TODO MB/s
iozone 1M sequential write TODO MB/s
wget https://raw.githubusercontent.com/geerlingguy/pi-cluster/master/benchmarks/disk-benchmark.sh
chmod +x disk-benchmark.sh
sudo MOUNT_PATH=/ TEST_SIZE=1g ./disk-benchmark.sh

Run benchmark on any attached storage device (e.g. eMMC, microSD, NVMe, SATA) and add results under an additional heading.

Also consider running PiBenchmarks.com script.

Network

iperf3 results:

(Be sure to test all interfaces, noting any that are non-functional.)

GPU

glmark2-es2 / glmark2-es2-wayland results:

1. Install glmark2-es2 with `sudo apt install -y glmark2-es2`
2. Run `glmark2-es2`
3. Replace this block of text with the results.

Note: This benchmark requires an active display on the device. Not all devices may be able to run glmark2-es2, so in that case, make a note and move on!

TODO: See this issue for discussion about a full suite of standardized GPU benchmarks.

Memory

tinymembench results:

Click to expand memory benchmark result ``` # Run the two commands below, then replace this code block with the full result. git clone https://github.com/rojaster/tinymembench.git && cd tinymembench && make ./tinymembench ```

sbc-bench results

Run sbc-bench and paste a link to the results here:

wget https://raw.githubusercontent.com/ThomasKaiser/sbc-bench/master/sbc-bench.sh
sudo /bin/bash ./sbc-bench.sh -r

Phoronix Test Suite

Results from pi-general-benchmark.sh:

geerlingguy commented 4 hours ago

Regarding OSes, ArmSoM provides a download link to a Google Drive folder with a bunch of distros to choose from: https://drive.google.com/drive/folders/1ijH2PoVUtHwe7fyiIpiQ7bsDZV3nx-MB

I am going to try out Debian, specifically armsom-sige7-debian-bullseye-xfce4-arm64-20241029

geerlingguy commented 4 hours ago

Hmm... the device seems not to boot up with that image flashed to a microSD card.

When I plug in power to the 'Power' USB-C port, I see the red LED light up, but nothing else happens, and there's no HDMI output either. Also no blinking on the Ethernet port (I'm plugged into the 'LAN' port).

geerlingguy commented 3 hours ago

Trying again with ubuntu-22.04-preinstalled-desktop-arm64-armsom-sige7 this time...

When I flashed the Debian image, Etcher gave me a warning about the partitions, it didn't do it with this Ubuntu image, so maybe that's a good sign...

Well... halfway through the image writing process, I get this warning:

Screenshot 2024-11-08 at 4 11 07 PM

I shall now attempt with ubuntu-22.04.3-preinstalled-server-arm64-armsom-sige7!

geerlingguy commented 3 hours ago

The Ubuntu server image does seem to boot—I get both the 'R' and 'G' LEDs lit up when I plug in power, and both remain lit constantly. I got HDMI output after 5-10 seconds, and that was all well and good... but then a few seconds later, it would shut back down / reset. Going to capture the screen output to see where in boot it's failing.

The Ethernet jack even lights up for about .5 seconds towards the end of the false-boot-loop.

It gets stuck at this point:

image

This is all I'm able to capture:

https://github.com/user-attachments/assets/85972b92-1dea-4972-915a-e64c4d878212

geerlingguy commented 3 hours ago

Ah, just found the Sige7 FAQ:

Q1: My ArmSoM-Sige7 cannot boot / is stuck in an infinite boot loop.

The ArmSoM-Sige7 supports USB PD power negotiation for higher voltage requirements, such as 9V, 12V, 15V, and 20V, to meet the total system power load requirements (around 30W, including WiFi, SSD, USB peripherals, etc.). Currently, PD negotiation is implemented in the kernel driver, and we need to boot to the kernel to start the negotiation. However, some power supplies may not be patient while waiting for the ArmSoM-Sige7 to negotiate and will cut off power when a timeout occurs, leading to an infinite boot loop.

Also maybe useful: ArmSoM Sige7 docs: https://docs.armsom.org/armsom-sige7

geerlingguy commented 3 hours ago

Also to boot off NVMe, they just posted this in the forum: Sige7 installation system to NVMe startup

geerlingguy commented 3 hours ago

Now that I have this thing booting... I don't know how to log in. I've tried ubuntu/ubuntu, armsom/armsom, and root/root so far...

After seeing the issue Sige7 username and password and trying armsom a few more times... I tried registering an account on the ArmSoM forum, but after waiting 10 minutes I still haven't received the activation email.

So I can't ask there for help, maybe this image is not the best image to use, but the Debian image did not seem to be able to flash at all... 1 hour in and I haven't been able to boot this board to the point I can access it yet :(

quintuple-lained commented 3 hours ago

now this might be a stupid question but wouldnt chrooting into the boot medium from a different machine and running passwd solve the login issue?

geerlingguy commented 1 hour ago

That could, however I don't have my Linux workstation booted up right now, and also don't have my SD card reader plugged into it, it'd be a lot of friction to hack at the default password that way. I also want to make sure I can set this thing up in a way I could recommend to viewers of a potential video in the future, I don't want people to have to have a Linux machine they can use to hack in their own password on the base install :)

EyalRo commented 1 hour ago

If you have access to the filesystem, there's always the trick of editing/etc/shadow and overwriting the row for root with an empty password root::0:0:root:/root:/bin/bash, then logging in with root and no password.

Edit/addition: you could also share the shadow file contents with the the greater internet, and we could track back to the password using way too much computing power. It's not something your readers will have to do because we could share the found password with them.