Gunjan Gupta

Assuming you simply pressed enter for every prompt, your root password should be empty. So you should be able to login with username as root and just press enter when prompted for password

Yes, it was fixed as part of https://github.com/armbian/build/pull/6040

Look at the path of the patch and you will understand why. In the PR I have patched both 6.1 and 6.6 kernel. In 6.1 kernel, there is no sun50i-h616-orangepi-zero.dtsi and hence changes were needed in sun50i-h616-orangepi-zero2.dts. However, as 6.6 kernel has sun50i-h616-orangepi-zero.dtsi, changes were done in the same.

We are aware of the same. We even say so on the download page for Orange Pi Zero 2 - https://www.armbian.com/orange-pi-zero-2/. I have recently fixed the wifi for it and I will try to fix hdmi also to be part of 24.02 release. But as I said, I will try, no promises there. Depends on the bandwidth and the tasks I am juggling at the moment. Also you can see on the download page that we have written "Maintainence cost are on behalf of Armbian Team" which basically translate to we are trying to keep this device maintained and working, but we don't have any funding for the same. Fixing stuff takes a lot of time and efforts for both development and testing which is not being paid by anyone.

The bug is in core-utils package, so only developers of core-utils can comment about that. It works for me on my nanopi duo2 which is also a Allwinner H3 based board. So not sure what triggers it. May be it has to do something with timezone, or whether daylight saving time is followed or not. In my case, we don't follow daylight saving time in my country.

Its same, but is in different file. The changes that you tested on zero2 impacts both zero2 and zero3. If you use the edge kernel deb file from that build on zero3, wifi will work on zero3 as well.

Hmm, interesting...Not sure why that happened. This is caused by sprd_ng module aka uwe5622 wifi driver. Same thing happens on Orange Pi 3 LTS as well.

The changes in the PR is done in the way so that wifi should be working on both zero2 and zero3 on edge kernel. Its just there is no board config file for zero3, and as zero3 is not currently a supported board I only need confirmation for zero2.

The sun4i-drm patch needs a lot of work before it can merge into Armbian and without it there will be no HDMI support. It conflicts with a lot of other patches. I am planning to work on it next week. All thats needed is building an image for current and edge kernels, flash it on sdcard and boot on zero2. See if you are provided an option to connect to wifi and if you are able to connect to it.

Upstream bug - https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1036335

@pixdriftCould you please test wifi on Zero2 using my orangepizero2 branch? Once confirmed, I would be able to get this merged - https://github.com/armbian/build/pull/6040

@Aleksey GavrikovWe were not able to fix this before we made 23.11 release. We have now fixed the issue and the PR is merged. Fix will be available in beta apt repository first (beta.armbian.com) and will be included in next release. As the fix is in bootloader, once new linux-u-boot-* package is provided via apt, Bootloader has to be reflashed on the system (See https://docs.armbian.com/User-Guide_Getting-Started/#how-to-update-u-boot). Ethernet should start working after reboot.

Happy to help. I am waiting for my Zero3. It should be delivered in 10-15 days. Once its here, will integrate the changes into Armbian.

@pixdriftI didn't do it for Zero2, I did it for Zero2w. A friend of mine has got that device asked my help to get alpine running on it with6.6 kernel and getting hdmi and wifi working. We used armbian build framework to ease kernel compilation efforts.

You are on 23.8.1 with kernel 6.1.59. Thats pretty old. Why not try updating to latest packages. Might fix your issue

@Stephen GrafThats upto the maintainers of the boards. As of now, I don't have any H616 boards. I am about to raise a PR that should get wifi running, so keep an eye on Armbian build repository.

@Stephen GrafHere is my understanding of zero2 board status wifi, bluetooth - broken due to missing dts changes HDMI - broken missing dts and sun4i-drm patches. I found out there are patches that only add zero2.dts part of hdmi changes, ignoring sun50-h616.dtsi side and then to counteract compilation failure another patch is added to remove the same. Its quite weird to be honest. Not sure why its done like that. sound - Should also be broken either due to missing dts patches or also due to missing driver for audio hub. Not sure gpio - should be working fine i2c, spi - might be working fine after enabling overlays? CC @ALIGMSTEN as he has a zero2 and should be able to confirm the same.

Its not just dts changes you need. You are also going to need changes for sun4i-drm module. I have tried to get sun4i-drm patch for h616 in. It conflicts with few other drm patches that I had to disable, but I got the display and wifi working with 6.6 kernel on Orange Pi Zero2w. Code can be found here - https://github.com/viraniac/armbian_build/tree/zero2w PS: I don't have a zero2, Zero2w or Zero3 device, changes were tested by a friend on his zero2w.

Most of the Armbian kernels are made by taking the upstream kernel and applying patches on top of it. If you go to https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/log/fs/ext4/file.c?h=v6.1.66, you will see that the commit at the top is the one that caused the bug. In the same url, if you change the version to 6.1.63, you can see the commit is not there. Hence we are not affected. Fun Fact, first commit after we had made v23.11 release was upgrading to 6.1.64 kernel, and it was only published to beta repository. Currently beta repository is using 6.1.66 kernel for current branch.

Could you please share more detail about why you think 6.1.63 is affected? As I can see in the links you have shared, the problematic commit was introduced in 6.1.64. So 6.1.63 is not affected. Am I missing something?

@Timo12357Thanks for reporting the issue. I was able to reproduce it. I have been handling maintenance of Orange Pi 3 LTS for past couple of months and was mostly using xfce. Hence I was not aware of this issue. I will try to solve it, but that would take some time. Meanwhile, I suggest you to give xfce image a try the login screen on xfce is similarly broken because of an upstream bug in lightdm, but you can install sddm on xfce image instead and that should get you better user experience.

@IgorI think the problem is caused by the way the packages are published. I think we ran the build for bookworm and jammy, but when publishing we updated the Package list of bullseye as well. Thats how bullseye is now getting armbian-bsp-cli package for 23.11 version. As build was not run for bullseye, the bullseye specific base-files package didn't got updated. I think we need to modify our repo updating job to also take account of what distributions to be updated, instead of updating all of the distributions. That should fix these kind of upgrade issues when we drop support for older OS. Lets disccuss this further in today's meeting

Possibility, yes. Would we provide it? Most likely not. Still you can try to port Armbian to your device. Assuming the SoC is supported quite well in the upstream kernel, the process can be pretty straight forward. See the developer section of the Documentation for details on how to port Armbian to a new device.

Easiest way to resolve would be to upgrade to bookworm. If there is no special reason for you to be using bullseye, just upgrade to bookworm. You can find the instructions for the same in the documentation. We did posted in the announcement section a couple of days ago that we are facing technical issues due to which some images and packages are not getting synced. And as mentioned in the announcement we are working on it. Please be patient. Everything will be resolved momentarily. Still I will raise the topic in our weekly meeting to see if this was intentional (e.g. ending support for bulleye ?) or just a glitch. In the later case it will be resolved soon.

@HorstNeofetch is not Armbian specific command. Its used in a lot of distributions to show device information. For Armbian specific things, go through the https://docs.armbian.com/User-Guide_Getting-Started/ make sure to check all of the links given in the sidebar on the left. Those informations will definitely come in handy.