lanefu

quick update.. armbian now produces a qcow2 image for the virtual-qemu build... I installed virgl but still working on a script to launch...

Your priorities are correct

the July 1st error was legit, but the certificate was fixed soon afterwards.

Can you share error messages please.

spoke with @Igor and issue may be related to u-boot.... will investigate more.. just making note here

but I hate doing that.

Just another reminder... Planning meeting tomorrow! Release Planning meeting 2021-07-10 1400GMT #armbian irc.libera.chat

In uboot there's a folder containing files that end in defconfig Those files are whats used based on what's configured here https://github.com/armbian/build/blob/master/config/boards/pinebook-pro.csc If you run make menuconfig you can load one of those defconfig files and then save accordingly

Resolved via https://github.com/armbian/build/pull/2979!

because that's what we configured... gnome just happens to install Wayland anyway.

Hirsute gnome builds as wayland due to ubuntu defaults The rest are x.org as far as i know.

Yep! DHCP renewal seems to freak out chrony and caused the system clock to rollback.... Been stable since I switched to static IP.. now to find a real fix....

hi @kentAVR Sorry I see that the confusion was now. It was around user provided Kernel Configuration vs user provide Kernel Source Config. here's an example of a kernel source config you could override.. https://github.com/armbian/build/blob/master/config/sources/families/rockchip64.conf and yes, yourre correct, the pattern for providing a kernel build config in the top of the userpatches/ folder following the appropriate naming convention.

awesome thanks for clarifying, keep an eye on the thread I'm sure someone will chime in!

Not really a good fit for me, sorry.. Are you looking for someone to do the work to add U-boot and kernel support, or looking for someone to integrate u-boot and kernel support into Armbian? Do you have any budget, or is this just seeking community interest?

Interest on the armbian side usually happens after there's patches in existence for mainline u-boot and mainline linux kernel

Make the folder. https://github.com/armbian/build/blob/master/lib/configuration.sh#L125

Blobs are going to be firmware blobs https://github.com/armbian/firmware and sometimes things to make uboot work. Like the arm trusted firmware things i dont understand. Some "legacy" labeled kernels containing bsp kernels may have some blobs and things for acceleration. The intent is as little as possible and especislly with our mainline kernel based builds. There's not a simple answer to your question. Older Allwinner and Rockchip based images will have higher potential levels of purity. Dig in and share your conclusions

Release Planning meeting 2021-07-10 1400GMT #armbian irc.libera.chat

Had similar report for a user of stable helios4 after their rootfs package updated. Ive modified jira issue to reflect broader scope

hmmmmmmm https://askubuntu.com/questions/1288683/dhclient-doesnt-renew-lease-when-ntp-syncs-the-time-backwards /var/log/syslog and /var/log/kernel and /var/log/dmesg

interesting yeah started gettin some NIC stuff on my pineh64 recently after I moved up my kernel.. haven't tried disabling wifi drive.. kept on thinking it was the clock rolling backwards. need to do more testing.. will look into module blacklikst tho

Run armbian-config and choose an alternate mirror

thanks @djurny this is awesome

lane@Ippon-LJ-M1:~$ ssh tritium-h5 lsusb --tree lane@tritium-h5's password: Permission denied, please try again. lane@tritium-h5's password: /: Bus 09.Port 1: Dev 1, Class=root_hub, Driver=musb-hdrc/1p, 480M /: Bus 08.Port 1: Dev 1, Class=root_hub, Driver=ohci-platform/1p, 12M /: Bus 07.Port 1: Dev 1, Class=root_hub, Driver=ohci-platform/1p, 12M /: Bus 06.Port 1: Dev 1, Class=root_hub, Driver=ohci-platform/1p, 12M /: Bus 05.Port 1: Dev 1, Class=root_hub, Driver=ohci-platform/1p, 12M /: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=ehci-platform/1p, 480M |__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/4p, 480M |__ Port 3: Dev 3, If 0, Class=Hub, Driver=hub/4p, 480M |__ Port 3: Dev 6, If 0, Class=Vendor Specific Class, Driver=ch341, 12M |__ Port 4: Dev 5, If 0, Class=Vendor Specific Class, Driver=ch341, 12M |__ Port 4: Dev 4, If 0, Class=Vendor Specific Class, Driver=ch341, 12M /: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=ehci-platform/1p, 480M /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=ehci-platform/1p, 480M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-platform/1p, 480M