Gunjan Gupta

@javaxsousa I would suggest to share your uboot defconfig changes so that it will be helpful for others as well

Assuming initrd file is intact and you are able to extract it yourself without any errors. This looks like that maybe initrd or kernel is getting overwritten in ram while loading. you can try playing around with their load addresses in u-boot and see if that makes a difference

try replacing GPIO_ACTIVE_HIGH with 0. That will remove need of the including header files. In case you still face compilation issue, please share the output of dtc command

@Gro-Tsen One way you can compile the driver is by running `./compile.sh BRANCH=legacy BOARD=nanopi-r6s kernel-config`. That will show the menuconfig interface to configure the kernel. You can enable the driver you need and when exiting choose to save the config file. Then you can run `./compile.sh BRANCH=legacy BOARD=nanopi-r6s kernel`. to compile the kernel. The resultant deb file will be in output/debs folder. The modified config file will be in config/kernel folder. I will suggest to open a PR with the same so that it will get enabled in the official Armbian kernel as well. Those numbers are generated by hashing various files present in armbian source tree. For example C42aa means that the hash for kernel config file starts with 42aa. For more information see artifact_kernel_prepare_version function in lib/functions/artifacts/artifact-kernel.sh file.

As I understand, the vulnerability seems to be in Arm provided mali drivers and userspace binaries. I am not sure if we use them.

@Eddiie Found the image you mentioned on https://wiki.banana-pi.org/Banana_Pi_BPI-P2_Zero page. Seems to me a third party created image. I don't see the board config for p2 zero in Armbian/build repository, so I am not sure if we ever supported this board. Not sure why the third party image contained Armbian repository urls as that would for sure break the board on upgrade.

Could you please confirm your device? I see the error message is for bananapi p2 zero, but you have reported it with bananapi m2 zero tag. I don't see any patches or config file for p2 zero. Could you please share the link for the image you installed?

Also I am not sure about this. Can you try removing one of the default?

@Peter GregoryAre you sure you are using the right pins? Based on the schematics, SPI1 should be PH5-PH9

@pierre-pretWe have recently done a lot of fixes for this board. Some are included in latest 23.8.3 image while others (for things like ethernet fix and wrong ram size detection by u-boot on reboot) are available from beta repository. If you try building an image again now. I believe you will have much smoother experience. Feel free to let us know if you face any issues.

This is now fixed. Updated u-boot should be available in beta repository within 24 hours.

Try setting console=display in your /boot/armbianEnv.txt file. That should free the 3 pin uart for other use within linux. Please note that the 3 pin uart will still be used during booting by u-boot, ATF and crust.

@Fazik83I have made few changes and have uploaded new Images here - https://drive.google.com/drive/folders/1Pq7iYzIBPhPPACGxDqan0obbl8wNVY8t?usp=sharing Could you please test the same and let me know if it works? PS: The image has console set to serial, so there might be no login prompt on hdmi. If you need to use hdmi, set console=both in boot/armbianEnv.txt file.

Moved to rockchip forum as this is not an Allwinner board

https://support.mozilla.org/en-US/kb/how-to-set-the-home-page

@WernerI believe this should be in the board forum if we have one for Banana Pi M2 zero, or atleast in allwinner unsupported forum. Doesn't seem like a userspace question to me. I don't have the privileges to move it. Could you please do the honors?

@FelSM The format you have used to define gpios for cs-gpios format seems bit odd to me. May be it is just my lack of knowledge, not 100% sure. Generally for allwinner boards, the format I have seen contains 4 parameter i.e. reference to pinctrl node either &pio or &r_pio, pin line number, gpio number and then state. You only have mentioned 3 parameters which makes me a bit confused about what pins you are trying to use as chip selects here.

Based on the schematics of the board, PG8 only support uart1 or gpio function. So you can't set function = spi0 for the same. Now this is a shot in the dark, but may by you can experiment with cs-gpios property.

@IgorS You can now use the follows "./compile.sh BOARD=<board> BRANCH=<branch> <command>" where command can be one of the following uboot, uboot-config, uboot-patch, atf-patch, crust-patch, kernel, kernel-config, kernel-patch, armbian-config, armbian-zsh, plymouth-theme-armbian, firmware, firmware-full, armbian-bsp-cli, armbian-bsp-desktop, armbian-base-files, fake-ubuntu-advantage-tools, rootfs, desktop you can only provide one command though. So probably you use for loop and supply each command through the same.

You only needed to install wireguard-tools package, and I believe that should be already installed in armbian image. Wireguard on the other hand is a metapackage that also tries to install the kernel modules which are already available in armbian. To revert back to armbian kernel, run "apt-get install --reinstall linux-image-current-sunxi linux-dtb-current-sunxi"

Thats sad. You can still try installing edge kernel to tezt it and then revert back to older kernel if it doesn't work as your liking I can see the kernel modules for ST7735 is enabled in our kernels config/kernel/linux-sunxi64-current.config:CONFIG_FB_TFT_ST7735R=m config/kernel/linux-sunxi64-edge.config:CONFIG_FB_TFT_ST7735R=m config/kernel/linux-sunxi64-legacy.config:CONFIG_FB_TFT_ST7735R=m

Looks more like manually installed kernel, given that kernel is a realtime kernel. Ofcourse that does mean its not our issue as its not our kernel

I see fbtft module driver is present in modern kernel as well, so probably you can give it a try may be on a spare sd card if you don't want to experiment things in your current installation. Whats the model number for your screen?

@joaopaulo98 Thanks for reporting this. I see you are using quite an old kernel. Could you please try upgrading to current (6.1) or edge(6.5)? We regenerated images for this board few days back to bring back the wifi support. So if you upgrade to 23.8.3 and use 6.1 or 6.5 it should work fine. Let me know if you face any issues with the same.

Thanks for reporting back. I am going to rework it this week. Will let you know once I have an image ready for testing.