denni_isl

This is in /etc/dnsmasq.conf interface=eth0 # listen=192.168.4.1 dhcp-range=192.168.4.8,192.168.4.250,255.255.255.0,12h server=8.8.8.8 # domain-deeded bogus-priv sudo systemctl restart dnsmasq.service and sudo nmtui, edit connection, wired connection, edit ipv4 configuration, Manual (Shared) 192.168.4.1/24, ok

Sharing is caring. Did finally manage to get this working. So lets make it simple clever. Actually i did this on a 64bit raspian light kernel 6.1 but it must be the same on Armbian 10 jan 24 Sharing the Raspberry Pi's WiFi over the ethernet port sudo apt get update && sudo apt install dnsmasq iptables iptables-persistent dhcpcd5 sudo vim /etc/dhcpcd.conf interface eth0 static ip_address=192.168.4.1/24 ------- sudo mv /etc/dnsmasq.conf /etc/dnsmasq.conf.bk sudo nano /etc/dnsmasq.conf - interface=eth0 dhcp-range=192.168.4.8,192.168.4.250,255.255.255.0,12h server=8.8.8.8 bogus-priv ------ sudo systemctl restart dnsmasq.service ------ sudo vim /etc/sysctl.conf net.ipv4.ip_forward=1 ------- sudo systemctl start dnsmasq ------- sudo sh -c "echo 1 > /proc/sys/net/ipv4/ip_forward" ------- sudo iptables -t nat -A POSTROUTING -o wlan0 -j MASQUERADE sudo iptables -A FORWARD -i wlan0 -o eth0 -m state --state RELATED,ESTABLISHED -j ACCEPT sudo iptables -A FORWARD -i eth0 -o wlan0 -j ACCEPT ------- sudo iptables -L -n -v ---------- sudo sh -c "iptables-save > /etc/iptables.ipv4.nat" --------- sudo vim /etc/rc.local iptables-restore < /etc/iptables.ipv4.nat exit0 --------- sudo reboot -------- Did get a perfect internet connection on odroid n2+ through eth0 - so the rpi4b is now supplying wifi for that board and providing petitboot with netbooting images through netboot_default after exit to shell.

On odroid-n2+ and on the other machine - picocom -b 115200 -l -r /dev/ttyUSB0

- To my surprice I was able to upgrade odroid-n2+ to kernel 6.0.10 on a debian bookworm install. Had previously tried to compile kernel 6.0.9 and 6.0.10 from kernel.org and also through the armbian build with no success. The 6.0.9 and 6.0.10 from kernel.org did work but did both lack wifi connections - did try many dongle without success. This deb package from imola.armbian.com do work like a charm on debian bookworm. ------------------------------------- Did download https://imola.armbian.com/beta/pool/main/l/ linux-dtb-edge-meson64_22.11.0-trunk.0138_arm64.deb linux-headers-edge-meson64_22.11.0-trunk.0138_arm64.deb linux-image-edge-meson64_22.11.0-trunk.0138_arm64.deb linux-source-edge-meson64_22.11.0-trunk.0138_all.deb and did dpkg -i linux............deb -------------------------------------- ls /boot armbianEnv.txt Image armbianEnv.txt.out initrd.img-6.0.10-meson64 armbian_first_run.txt.template System.map-6.0.10-meson64 boot.bmp uImage boot.cmd uInitrd boot.scr uInitrd-6.0.10-meson64 config-6.0.10-meson64 vmlinuz-6.0.10 dtb vmlinuz-6.0.10-meson64 dtb-6.0.10-meson64 -------------------------- ➜ src cat /etc/os-release PRETTY_NAME="Debian GNU/Linux bookworm/sid" NAME="Debian GNU/Linux" VERSION_CODENAME=bookworm ID=debian -------------------------- OS: Armbian (22.08.8) aarch64 Host: Hardkernel ODROID-N2Plu Kernel: 6.0.10-meson64 -------------------------

Use at your own risk and practice with less important drive (of course). ----------------- copy hard drive to .img(.gz) and .img(.gz) hard drive ---- * boot your computer up with a live usb or sd wit gparted > unmount the disk you want to copy > gparted > make the last partition smaller but leave some small additional space > check filesystem * to copy used partitions over to your_hard_drive_copy .img.gz ; - calculate > count= (gparted last sector of the alst partition (/) right mouse button, information, last sector * 512 / bs=4096 > * calculate in console; expr 22171647 \* 512 / 4096 = 2771455 -(2771456)) (+1 sector). - last sector +1 * 512 / 4096 = last sector in bs=4096 * copy used partitions /dev/sdc á .img og .img.gz; sudo dd if=/dev/sdc bs=4096 count=2771456 conv=sync,noerror status=progress of=manjaro_vim3_38okt20.img && gzip manjaro_khad_aml_mini.img * .img over to /dev/sda; dd if=hard_drive_backup.img of=/dev/sda bs=1m status=progress ; sync, * when restored one need to boot again with a live usb or cd with gparted and umount the disk > resize > check filesystem ------------------------------------------------------

The console is completely different now - it used to be blurred. I usually set up usable console; sudo apt install console-data console-setup (for right keyboard) and sudo dpkg-reconfigure keyboard-configuration and sudo dpkg-reconfigure console-data > sudo dpkg-reconfigure console-setup - utf8 - latin1 - termus - 11x22 Now the console on firefly-rk3399 is Cristal clear with the new kernel 6

3 Nov 22 Was able to compile Armbian (22.11.0-trunk) Kernel: 6.0.6-media for firefly-rk3399 with sudo ./compile.sh CLEAN_LEVEL=make,debs,images,alldebs,cache EXTRAWIFI=yes CREATE_PATCHES=yes EXPERT=yes NO_APT_CACHER=yes and apply this patch to drivers/usb/dwc3/core.c + #include <linux/ectcon.h> and copy /boot/dtb/rockchip/firefly-rk3399.dtb from a SD card with Arbian with kernel 5.15.27-media to /boot/dtb/rockchip/ on the new Armbian 22.11.0-trunk kernel 6.0.6 image

After copying rk3399-firefly.dtb from Armbian 22.05-0-trunk Bullseye 5.15.27-media to Armbian_22.11.0-trunk_Firefly-rk3399_sid_current_5.19.14 it did work fine.

Did get Arbian 22.08 bullseye kernel 5.19.16-media to work by copying rk3399-firefly.dtb from a working 5.15.27-media The boot up error Found this

connect tx rx gnd vires to corresponding gpio(not votage) lsusb➜ sudo picocom -b 1500000 -r -l /dev/ttyUSB0

The newest images are not booting out of the box did though get Armbian_22.11.0-trunk_Firefly-rk3399_sid_current_5_19.14.img to boot - it is working quite well with rk3399-roc-pc-plus device blog except there is no wifi at all. Trying to compile with this line bullseye kernel 5.19 server image get tihis error; ------------- This is beound my scope This seems to be the case https://www.kernel.org/doc/html/v5.16/driver-api/usb/dwc3.html

This error was common on my nanopim4v2 and i did have to start it manually all the time. Did fix it by adding rootdelay=5 in /boot/armbianEnv.txt and with the help of serial adapter did apply this method to u-boot. Stop u-boot, printenv (inspecting), setenv bootdelay 5, saveenv (printenv to see if bootdelay shanged), reset. Side issue. The gparted icon did not start gparted on "Armbian 22.02.1 Focal with Linux 5.15.25-rockchip64" rockpro64. Installing poicykit-1-gnome did fix that after reboot. Now it ask for password while starting.

To turn off the annoying heartbeat blue light.

One has to freeze kernel and u-boot upgrades because generation of new uInitr does disable linux kernel hdmi. Disabling of hdmi in u-boot has to be implemented into armbian nanopi-m4v2 u-boot.

Did try few resent images as of beginning of feb 21 for nanopi-m4v2 and compiled my own using the armbian build and tried to move u-boot support for hdmi - bud did have to plug the hdmi cable after starting kernel .... This pilter75 image does bypass u-boot hdmi and therefore allows the kernel control of hdmi https://users.armbian.com/piter75/Armbian_21.05.0-trunk_Nanopim4v2_buster_current_5.10.18_minimal-stability-fix.img.xz There is one problem - USB 3 do flicker. It is not possible to restore with rsync. Might be because I did install full firmware or overclocking. Edit: It is either - USB is working okay without full firmware and overclocking.

Is it the new u-boot hdmi bug (conflict) u-boot hdmi - kernel hdmi https://github.com/armbian/build/pull/2016/files ?

Related; A guide https://zuckerbude.org/armbian-using-create-patches/ to use armbian build script to patch u-boot and kernel and make adjustment to boards device tree blob - dtb.

And the legacy kernel that does always boot up - mbian 21.02.1 Bullseye with Linux 4.4.213-rk3399.

Some progress, rk3399-nanopi-m4.dtb does bring everyting up exept hdmi - the others on the list did just end at Starting kernel ..... rk3399-orangepi-4.dtb does also bring up the board. But no hdmi connection - just UART apt update - apt upgrade and the new image boots up

How does one do that correctly? Did try - fdtfile=rk3399-firefly.dtb

Trying to boot legacy Armbian_20.11.10_Firefly-rk3399_bionic_legacy_4.4.213_desktop

Vondering if this has something to do with AppArmor or the hardware partitions grep APPARMOR /boot/config-* CONFIG_SECURITY_APPARMOR=y CONFIG_SECURITY_APPARMOR_HASH=y CONFIG_SECURITY_APPARMOR_HASH_DEFAULT=y # CONFIG_SECURITY_APPARMOR_DEBUG is not set CONFIG_DEFAULT_SECURITY_APPARMOR=y This is from successful Armbian 21.02.1 Focal with Linux 5.10.12-rockchip64 emmc boot

ArmbianEnv.txt mainline focal 5.10.y from https://www.armbian.com/firefly-rk3399/ sd card boot up does not get any further than - starting kernel....... UART:

Now it boots Armbian 21.02.1 Focal with Linux 5.10.12-rockchip64 successfully every time from emmc.