edit: found an issue in second hostapd service file which prevents hostapd to be started…passed pidfile is wrong…just add the “2” like in PID-variable above
edit: uploaded new version with fixed uboot (missing emmc-partconf, sata-config) and fixed service file and prepared pppoe/ipv6tunnel
i try to extract some parts of my very complicated firewall file as basic config for r3…
But it seems like there is missing something to load the driver…
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 006: ID 0cf3:7015 Qualcomm Atheros Communications TP-Link TL-WN821N v3 / TL-WN822N v2 802.11n [Atheros AR7010+AR9287]
Bus 001 Device 002: ID 1a40:0101 Terminus Technology Inc. Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
[ 145.751888] usb 1-2: USB disconnect, device number 3
[ 149.112288] usb 1-2: new high-speed USB device number 4 using xhci-mtk
[ 525.118105] usb 1-2: USB disconnect, device number 4
[ 530.412270] usb 1-2: new high-speed USB device number 5 using xhci-mtk
[ 1071.635854] usb 1-2: USB disconnect, device number 5
[ 1074.902278] usb 1-2: new high-speed USB device number 6 using xhci-mtk
I am using the Bookworm image - but could not find better place to put the question??
@frank-w
if i use your bullseye image , why can´t use your kernel deb package , he
will not boot the new installed kernel by dpkg -i .
the bullyseys dist boot allways the default kernel.
with your debain image for the r2 and your kernel build deb package work this
well , i upgrade the kernel with dpkg and the r2 boot the new version.
how can do this behavior with the r3 bullseye dist with your kernel build repository
and the generated deb package.
The default kernel deb only unpacks the kernel,but not tell uboot to use the new file.
So you just need to add the new filename to the uEnv.txt
fit=bpi-r3-6.6.x.itb
I want to avoid overwriting the old kernel so added version to the file,but have not tried to modify uEnv.txt in deb script of kernel as this needs to add a script in the deb.
the modification , and copy , of the uEnv.txt did not work .
per default in your bullseys dist , there is no uEnv.txt in /boot
i try to copy and modify out of the deb file , this file but the bpir3 will allways boot the default kernel.
There is no uEnv.txt in the deb file…there is an itb which should be in /boot now…this file is the one fit var in uEnv.txt has to point to. /boot needs to be mountpoint of mmcblkXp5 (default in my image)
Just create the file there and add the fit line with correct filename
You do not need uImage_nodt and dtb…only the itb. The other 2 files are for making tests with overlays or using separate dtb. And i see no uEnv.txt there…default value for fit var is bpi-r3.itb,so this is why it works
Hello.
I burned the Debian Bullseye Image to the SD card. Is there a possibility to connect via LAN? I don’t have a UART. After booting from the SD card, I don’t get an IP asres and thus I don’t have a connection via SSH.
R3 should have 192.168.1.1 on lan-ports. If your Client has address (also manually assignable) in this /24 subnet you should be able to ping r3 and connect vis ssh.
Are you sure r3 is succesful booted? For deeper analysis uart is required.
Btw. Current Debian stable is bookworm. I have automatic builds (from my BPI-Router-Images repo) on my gdrive.
Hello.
Thanks a lot for the response. I burned Bookworm to an SD card. I managed to connect to the Banana Pi via LAN. I connected a parent router with internet access to the WAN. Unfortunately Banana Pi is not connected to the internet. Need to set something up? Without internet I am not able to do the next setup steps.
By the way. What is the WiFi password r3_ap0?
It depends what your settings are set for internet on r3 (from dhcp). Check dns-settings and routes. For client internet you will need nat on wan and forward enabled via sysctl.
Wifi settings are in /etc/hostapd/ afair i had set default pw to 12345678
Thanks for the info.
I managed to get both wlan0 and wlan1 working, which I included in bridge lanbr0 and let them distribute ip addresses from the bridge pool. It totally works. Just one small problem that I can’t seem to resolve. After rebooting the Banana Pi wlan0 and wlan1 broadcast wifi but won’t connect the client until I run systemctl restart systemd-networkd via ssh. What is wrong? Do both wlan0 and wlan1 really have the same MAC address?