That must be prolific. Get ch340 few of them for testing.
Because there are 2 dram model version
R4S 1gb uses ddr3
R4S 4gb uses ddr4
I have ddr3 version which i had to compile u-boot separately and been using it on opnsense since then.
then we have two add to u-boot builds. can you tell me the parameter for both ram types.
If this compile i can add it to the u-boot lfs.
1 Like
I will look at what config i used for 1gb version.
Which model do you have?
I have no r4s only a r2s that works now.
I cannot buy all boards. But this makes testing complicated.
Me too. So i request for sample device.
Have you a special contact? I have tried this long time ago and get no response.
Hi @arne_f.
If you want, I can donate you one of NanoPI R4S for make your magic things 
.
Send my please in private your address.
Thank you and @spikerguy for making it possible.
1 Like
Not really.
If you want I can arrange RockPro64 for you as I have special contact at Pine64. Rockpro64 can be used with pcie lan adaptor.
They do respond but too slow.
Great. Thank you for supporting ipfire. 
I thought folks might find this interesting. (Especially with four ethernet ports)
1 Like
Rpi after all the accessories and board have always been expensive.
Idk how can they utilize 4 lan and 6 sata on that soc.
It would bottle neck with all 4 lan connected at 1Gb.
If I have to Buy
Carrier board - $99
Rpi4 CM - $76
Psu - $5
Carrier board case not available yet. Approx $25
That’s more than $200 and I could just go with $150 intel celeron nuc with dual Lan.
New Arm devices coming soon with router use case in mind.
Most likely the 2.5g Ethernet are connected over pcie.
Soc is powerful and memory size can go upto 8gb which is decent enough for router use case.
The Soc support is been adding in linux kernel since 5.15 while someone is already working on uefi support to replace uboot.
Would love to hear from Ipfire team on what they think about these devices.
IPFire also support uEFI on aarch64 so it should work if all needed drivers are enabled in the kernel without the u-boot/dtb addaptions for every new board.
2 Likes
That is the aim for rockchip to get uefi for their new soc lineup.
Rk35xx
Hi Arne.F
Sorry it took me so long to test, but tried core162 on my CM4 running on the seeedstudios carrier board. Fresh install, only problem I could find is that the WiFi on the CM4 board is not found. During the setup process there are only two interfaces to chose from, 1) the CM4’s Ethernet controller and 2) the seeedstudios USB3 controller which is where the other Ethernet port resides. I attempted to try and figure out why core162 does not see the WiFi controller verses core160 which found the controller, but I believe this is beyond my current linux skills. I am willing to help diagnosis this, but need some help, assuming this is not the desired end state.
hello,
make build dies without error… any ideas?
fresh ubuntu:
Linux darkmind 5.10.60.1-microsoft-standard-WSL2 #1 SMP Wed Aug 25 23:20:18 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux
build setup:
sudo aptitude install git make g++ bison gawk automake autopoint libtool cmake zstd
sudo apt-get install binfmt-support
sudo apt install gcc make gcc-aarch64-linux-gnu binutils-aarch64-linux-gnu
git clone git://git.ipfire.org/ipfire-2.x.git ipfire2_master
sudo ./make.sh --target=aarch64 downloadsrc
sudo ./make.sh --target=aarch64 gettoolchain
sudo ./make.sh --target=aarch64 build
dies:
Packaged toolchain compilation
Checking for necessary space on disk [ DONE ]
dae@darkmind:~/ipfire2_master$
How do I get more info about this?
(I cant get shell too. dies on the same point)
Thanks
I am presuming that you are cross-compiling as you are defining a target.
Have you got qemu installed as I have seen in development mailing list emails that it is required for the cross-compile to work.
Yes i have and the qemu static that is described in this thread earlier.
The only thing I can think of is to go through the make.sh script to see where it is stopping. It gets to the
step and passes it as you get the [DONE] message.
After that the script creates the build and lower directories. You can check if those have been built.
Then it does the mount --binds of various directories so you can check the directory tree to see if they get created or not. Then it enters the chroot … and see if you can see where it is stopping maybe with some additional print commands at certain stages to see which path it is taking.
Beyond the above I don’t have any other thoughts.
It’s clearly stopping before it gets to the first lfsmake2 line as nothing is being printed.
Just as a quick check that you got a successful download of the aarch64 toolchain, as I have presumed this.
aarch64 toolchain seems ok?!
dae@darkmind:~/ipfire2_master/build/tools_aarch64$ ls -la
total 68
drwxr-xr-x 13 root root 4096 Jul 1 2021 .
drwxr-xr-x 10 root root 4096 Jan 16 10:44 ..
-rw-r--r-- 1 root root 0 Jul 1 2021 .toolchain-successful
drwxr-xr-x 4 root root 4096 Jul 1 2021 aarch64-unknown-linux-gnu
drwxr-xr-x 2 root root 12288 Jul 1 2021 bin
drwxr-xr-x 3 root root 4096 Jul 1 2021 ccache
drwxr-xr-x 3 root root 4096 Jul 1 2021 etc
drwxr-xr-x 37 root root 4096 Jul 1 2021 include
drwxr-xr-x 21 root root 12288 Jul 1 2021 lib
lrwxrwxrwx 1 root root 3 Jul 1 2021 lib64 -> lib
drwxr-xr-x 6 root root 4096 Jul 1 2021 libexec
drwxr-xr-x 5 root root 4096 Jul 1 2021 man
drwxr-xr-x 2 root root 4096 Jul 1 2021 sbin
drwxr-xr-x 17 root root 4096 Jul 1 2021 share
drwxr-xr-x 3 root root 4096 Jul 1 2021 var