I have tried with different antennas, including ones from an older router that is able to deliver good signal around my place. That's why I do not believe the range is related to pigtails or antennas.

I do not say that better antennas won't help, just that Idoubt that they will improve the range to such degree to be able to switch BPI-R4 as my main router.

wifi status will show the radio and interface association, in some of my earlier snapshot tests I couldn't get a defined interface associated with radio2 due to a missing network device.

In your case it looks correctly associated.

In terms of config, do you mean kernel config? If so, unfortunately kernel needs to be compiled with IKCONFIG support to be able to extract it from /proc/config.gz

1 Like

Sorry, I was unclear in my prior messages. Since my GE800 has openwrt as its basis, I want to see what they do to create the interfaces and device configurations for the wireless. I know that it uses a different radio, but I feel that more info about what TP-Link generates in my mainstream off the shelf router for the wifi 6ghz radio, maybe we could try to use a similar approach to get ours working.

As I look at it (i ran the branch through getunblocked) it seems to suggest that some of what we need is in the driver source.

I think it's rather that not everything is working yet and the drivers haven't matured yet

1 Like

Is there some reason there is a hard limit on the target image build size? I'm hitting a limit error when making the image step despite having set the rootfs/overlay size to 1500MB.
Is this something to do with the nand/spi stepped install process needing small images? Can we simply avoid this by producing a raw image for the emmc ; boot to failsafe nand - image and switch to emmc so this isn't a problem?

WARNING: Image file /var/home/aenertia/build/openwrt-upstream/openwrt/build_dir/target-aarch64_cortex-a53_musl/linux-mediatek_filogic/tmp/openwrt-mediatek-filogic-bananapi_bpi-r4-sdcard.img.gz is too big: 66912256 > 46137344

steps for expanding the f2fs overlay on emmc for the bpi-r3 do not work (parted resize production (parittion 5) then, f2fs.resize on /dev/block/mmcblk0p128). So other than creating a 6th partition and have it be a seperate userdata mount the install it's problematic.

unselect the initramfs option on menuconfig

3 Likes

Duh; thanks I knew it must be something braindead.

Just a heads up your bannapir4 branch is failing to auth anything ; main from openwrt is working fine.

Guys is it normal for SFP module to slide out from the wan/lan port even though the mechanism is locked in

No, there should be some locking mechanism (depending on the module you have)

  1. DACs usually have an extra plastic latch to pull
  2. Ethernet usually have a mechanism where you unplug the cable and then lever the golden part down
  3. Fiber usually have live a ring (colored) which you have to lever down

and on my BPI-R4 all modules lock fine - but funnily all ports seem to be a bit "distorted", like they used very low quality parts for the ports (especially the USB port looks like beaten up - SFPs are a bit skewed, so perhaps there is something bent which prevent your locking mechanism?)

Wait pulling the latch down locks it?

Welp for some reason my message needs to be approved by a mod lol

Edit (the message I was originally trying to send just here):

I mean when I pull the tab down and insert it into the slot and as I lift it when I reach half way I hear a little click and it add tension to the gold tab and then I fully click it and lock it on, I can still pull out the SFP with a little tug is that normal, sorry for these noob questions never used an SFP before

I don't actually know, and I'm not terribly sure. I can't imagine that would be right for any tech, but even still, I think it is probably fine and just "don't yank on it" being that it is made for fiber, no one should be yanking on it anyway

No, it should always lock automatically when inserting. Just ejecting needs some "magic" like pulling latch, lever down, etc

this is not normal, maybe there is some damaged locking mechanism ? it must lock itself when You push it correctly . what brand ? give us some pics - we like pick of nice gear.

1 Like

yes that was my experience ... I didn't used an sfp either until I got a couple for the bananapi4. What I did was to only have the board and check that was fully inserted but yes it does click :wink: i don't think the latch is required it just needs to insert in the back

1 Like

It's an ampcom one

ok so lan port locks in nice and tight and doesnt come out even with a tug but a tug on the wan port and it just come off

edit: the lan one is quite patchy sometimes locks sometimes doesnt

ok yeah solved, just the plate at the bottom in the middle needed some small lifting up and it locks in properly now

Having a similar issue, updated fw to latest snapshot on my device and now I have "new" radios - it's now 5 instead of 3.
probably some duplications created on the upgrade script

that's odd ... can you share your /etc/config/wireless ?