This is my first post in the forum as I also get my first Banana Pi product today - BPI-R4, I do have some questions about it:
Other than power LED, there are also a few LEDs, other than the SIM/SSD LED, there are also B/G LEDs which is not described anywhere (now I see B one has BLUE light which means booting?)
I guess we can use 10G DAC cable on the SFP+ port without problem?
I tried to download the OpenWrt SD card image to boot, 1GbE ports light up when connected to my client PC but client PC doesnât get any IP, normal?
Finally I saw some messages from console when booting from SD card like the following, so whatâs that?
jffs2: jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x3da40000: 0xff97 instead
B=blue,G=greenâŚthese are leds for user specific usage. We use green as power-indicator,blur is not used yet.
i have no dac cable so not tested yet,i guess it will work,but at least on mainline we have not yet 10g working (missing rss+lro software support),the max is currently at ~5Gbit/s
you mean the bpi openwrt? Have not tried it as we are working on mainline support. It depends on setting on this image if there is a dhcp server running on these portsâŚtry login via lucy or on serial console to check the settings
no idea,but imho mainline openwrt will not use f2fs
But now when I connect power, the RED is always ON, with something booting up the BLUE is also ON, when itâs rebooting it will go off.
So that means using SFP+ RJ45 copper max 5GbE rate?
I downloaded the image from the wiki page, now I need to at least find a way to boot into an OS to verify my board is working (I know the upstream to mainline is just started so I am now asking to see everything working), in case something is wrong I can still send it back to AliExpress.
I assume the wiki download image is kind of âproof of conceptâ image (itâs ok for not being in mainline kernel)
Just received my BPI R4, and I ran into the same issue. In my case, itâs very serious. The error messages flood my serial console and renders it useless. After some digging I figured out the cause.
Note: please low level format the SD and clear all data of SD. itâs very important.
In fact, thatâs not a solution but does hint for some imagination. itâs not a solution because a binary image is bit-by-bit written to the SD card, whether you low format it or not doesnât matter before writing with âbpi-copyâ or BalenaEtcher.
The root cause should be the image itself generated by whatever procedures or tools used by MediaTek/BPI who prepared those official images.
Luckily, there is a quick way to fix it. Regardless you burn the image in Linux by using âbpi-copyâ or in Windows/MacOS by BalenaEtcher, you will need to fix the SD partitions with âfdiskâ in Linux after burning the image.
Simply âfdisk /dev/your sd cardâ and press âwâ and then quit. This will fix it.
If you have fixed it with fdisk, the problem would be the backup gpt at end of disk. You write the image (which is only some megabytes) to offset 0 of the disk. There is the main gpt which is different to the backup gpt at the end of disk.
Afair i had the errors only on first bootup and it looks like it fixes the issue on first run and after reboot there are not much errors.