lanefu

Hey this is just kind of a general question.. i have a v4 board does it have an additional set of irregularities that i need to worry about. Like are the assumptions for v5 that i cant make for v4?

LOL yeah uhmm your branch is kind of the goto for the orangepi builds https://github.com/armbian/build/blob/master/config/sources/sun50iw6.conf#L54

Should we tag the last commit before changing to the 5.0 work?

So what’s the suggested strategy for dealing with the patches? Like whats a method to determine which do we trash, which do we assume is mainlined already, which need to be fixed etc.... Sent from my iPad using Tapatalk

It’s for spam mitigation. After your reputation score goes up it won’t have to be approved. There are several moderators in all time zones so response time for approval is usually reasonable. Sent from my iPad using Tapatalk

@FlashBurn @ebin-dev Should we consider the patch PR a WIP and leave open until the v5 stability is figured out?

Put resolvers in /etc/dnsmasq/resolv.conf Sent from my SM-G950U using Tapatalk

yep reboots always failed and had to powercycle.

Ive got a oneplus how can i help debug?

Your upstream resolvers should be definef in this file using the standard convention nameserver x.x.x.x resolv-file=/etc/dnsmasq/resolv.conf no-resolv These lines aren't what you're looking for Remove them. They require more parameters and are for a different purpose. The server argument is for directing request for a specific domain to an alternate name server: server=8.8.8.8 server=8.8.4.4

I just tried script out on my lepotato... glmark2 worked on the mali test... and mpv was able to play fullscreen blueray mkvs... still ironing out browser

Not for Opi3... defective by design.. http://linux-sunxi.org/H6#Errata Check out espressobin if you need SATA and MiniPCIe

your work area is encrypted!

i dig the space one...... anyway keep 'em up... like its probably not unreasonable to bundle a few of them on the desktop builds..... like Mate comes with like 10 versions of their logo/theme. When you feel like you're at a stopping point and are feeling comfortable with things, let me know and we can fire up a poll

Same after flashing flash-image-ddr3-1g-2cs-1000_800.bin as well

I tried the patched debs. on my v4 espressobin.. running the 1000 800 firmware... seems to just kind hang shorly after kernel loads..

The spirit of my question was more around just polling "what logo do you like?" to the masses as a fun thing, not creating a coup or forcing a decision... anyway maybe i wasn't following close enough to chime in appropriately.

Somebody gotta fill the shoes. Rather Igor than me. I'm thankfull for all the work and time he, you and all the others have put in this. This is/became a big project that comes with many big and small problems. It's a big effort of different people with different thoughts an behaviours to try and find a way, and deside what's priority. Somebody has to decide. This can clash with others their idea's. Hasn't life always been since Kindergarden. Would you let to setup a poll on the forum?

Yep that’s exactly what I’m thinking. Sent from my iPad using Tapatalk

Okay good to know. I'll explore some options, including just cross compiling with the appropriate toolchain. Would you need it to build on every commit or merge to satisfy CI, or just like as a nightly?

that's definitely odd that it got erased. The armbian repo just has armbian packages, so you'll need to recreate sources.list. see if this tool can help https://debgen.simplylinux.ch/

I'm definitely digging the new forum section layout. I just had a thought after seeing this post in the bug tracker section. It's obviously not a bug. We should make a simple "Feature Request" forum section. That would be an obvious read to many, as an appropriate place to post, and easy for moderators to move topics to it. As a bonus no-one is obligated to respond, accommodate the request, or tell them to search the forum harder. It would also be less clutter in the more technical development forums. Any thoughts in favor or against creating a Feature Request forum section?

lane@armbian-builder:~/GIT/build/config$ fgrep -Rin lima * kernel/linux-sunxi64-dev.config:3805:CONFIG_DRM_LIMA=m kernel/linux-sunxi-next.config:4133:CONFIG_DRM_LIMA=m kernel/linux-sunxi-dev.config:4149:CONFIG_DRM_LIMA=m kernel/linux-sunxi64-next.config:3889:CONFIG_DRM_LIMA=m root@armdocker-2:/var/log# fgrep lima * grep: apt: Is a directory armbian-hardware-monitor.log:[ 3.011837] lima 1c40000.gpu: bus rate = 200000000 armbian-hardware-monitor.log:[ 3.011849] lima 1c40000.gpu: mod rate = 384000000 armbian-hardware-monitor.log:[ 3.013102] lima 1c40000.gpu: gp - mali400 version major 1 minor 1 armbian-hardware-monitor.log:[ 3.013166] lima 1c40000.gpu: pp0 - mali400 version major 1 minor 1 armbian-hardware-monitor.log:[ 3.013219] lima 1c40000.gpu: pp1 - mali400 version major 1 minor 1 armbian-hardware-monitor.log:[ 3.013262] lima 1c40000.gpu: l2 cache 64K, 4-way, 64byte cache line, 64bit external bus armbian-hardware-monitor.log:[ 3.014431] [drm] Initialized lima 1.0.0 20170325 for 1c40000.gpu on minor 1 So the lima driver is already there and built, but that's only a small piece of the battle. Integrating the GPU, with the video muxer, building approriate fbturbo X11 display driver, and putting all those pieces together is the difficult and unpolished parts. You'll see people cobbling some working implementations by hand, but nothing is really documented in a fashion to make it easy to do in a repeatable, automated way with armbian-builder. That process needs lots of help.... maybe this thread can figure that out. who knows.. Anyway I'm sure you can see lots of periodic dialog about the Mali blobs and the Lima driver on the forum that might offer some additional perspective. See development Section This wiki page about sunxi Media IP cores does a good job of capturing all the layers that make up a working video subsystem for H3 and kind of SBCs in general. I'm going to move this thread over to one of the general topics, since this is about an enhancement and not a bug.

Hey @ktsaou thanks for chiming in. I see your point about the viewers... By running netdata in headless mode and shipping the metrics to another instance for reviewing them, the footprint would be consistent. Would you be able to speak to TK's concerned about CPU load reading being skewed by changing cpu frequency scaling? Also do you foresee adding armhf and aarch64 builds to your nightlies, or whatever is retrieved by the kickstart install script?

Which distro? Is it part of a different package?