guidol

In the mainline kernel, meson-gxl-s905d-phicomm-n1.dts has been around for a long time, but there has been a problem of high CPU load. I fixed it and it has been stable for several months, so it is shared for reference .
I think the cause of the problem is that the IRQ is wrong. The original value is 29 and needs to be changed to 25.
// SPDX-License-Identifier: (GPL-2.0+ OR MIT) /* * Copyright (c) 2018 He Yangxuan */ /dts-v1/; #include "meson-gxl-s905d-p230.dts" / { compatible = "phicomm,n1", "amlogic,s905d", "amlogic,meson-gxl"; model = "Phicomm N1"; cvbs-connector { status = "disabled"; }; leds { compatible = "gpio-leds"; status { label = "n1:white:status"; gpios = <&gpio_ao GPIOAO_9 GPIO_ACTIVE_HIGH>; default-state = "on"; }; }; }; &cvbs_vdac_port { status = "disabled"; }; &external_phy { /delete-property/ reset-gpios; interrupts = <25 IRQ_TYPE_LEVEL_LOW>; };  

Ok ! I passed the main hurdles ... The worst one was that many obsolete time32 helpers that are now definitively gone/erased, but we still need them for out-of-the-tree wifi drivers, so I had to put them back using timekeeping32.patch.
I will do few more test images for my different Allwinner boards, then I will be ready for commit ...

Hey Sorry. @TonyMac32 and I came across this issue the other day.. There's a second step needed.... create a file in your build filed called .ignore_changes
 
I've updated the FORCE_CHECKOUT section of the documentation
 
touch .ignore_changes  

Suggestion for future releases: On the release date / once it's released make a topic in Announcements telling people of the new release. Or is Twitter now the main way to communicate such things? 
 

I've started the work of switching SUNXI-DEV to 5.6.y, as usual, few DT duplicates and fixes ...
But I've faced also a big change related to 'file_operations' been changed to 'proc_ops' in all places over the kernel, which cause that all our EXTRAWIFI needs to be fixed.
I hope to get it done by the end of this evening ...
 

If you want to build a "stable" image from the same code as the images we publish use v20.02 branch.
 
If you want to build "unstable" image with latest and greatest us master branch.

check out the branch direclty and try what i said here
 
 

Wait. The PCB was broken, the cells not. And I fixed it that time.
It can be charged and discharged the same time. The problem is that as soon as I disconnect mains the SBC restarts probably due to voltage drop on switch-over. This may be fixable using a small capacitor or something. I found the PCB I bought: https://www.ebay.com/itm/5V-2A-Power-Bank-Charger-Board-Charging-Circuit-Board-Step-Up-Module-Dual-USB/362589551623

git fetch git checkout v20.02-rc1 sudo ./compile.sh FORCE_CHECKOUT=no  
Unofficial release notes https://gist.github.com/lanefu/e32eb43aaaa7928c51ca8890af58c841#file-temp_notes-md

git checkout master
git pull
sudo ./compile.sh
 
will take you back to the master branch that you normally use.... FYI master is a rolling release..which may have looked like 19.11.x but its actually newer.. In fact we've updated the version in master release to reflect it as v20.05-trunk
 
 

Also, don't mix up between NEO and NEO2, they are not the same processors, the first is a H3 and the second H5, so using the wrong image make them not booting at all ...

link filtering to special known domains only for new users?
because if I post instructions I also add a link to a page where I did find the info for my solution.

I often edit my posts... maybe for correcting a word, entry or a new command or link
and this sometimes days later.
 
I also got sometimes problems, that not all editing options are available when editing a post against the editing options while creating a new post.
 
In a other forum the where the timed editing option is enabled there is much "thread-overhead" because some people have to add something to the thread because they cant edit it anymore.....
They dont got spammers (I dont see there any) - maybe they check in a other way?

I think very strongly that validating email should be (one of?) main steps to graduate from Validation -> Member. Anybody can put in whatever they want for an email address, it's all BS until they have validated it. And in the meantime they can be posting already...
 
Most of spammers I see, never even validated their email...
 
Some number of Likes (perhaps along with other criteria like post count, and/or time on forum) I think is probably a good idea for this "Trusted Member" (or whatever we want to call it) intermediate level. I think Likes especially are hard to fake.

link filtering to special known domains only for new users?
because if I post instructions I also add a link to a page where I did find the info for my solution.

This will be the Moderator counterpart to the Announcement thread I made about the same issue where I asked for help from regular forum Members. In this thread, I will discuss methodology I developed to deal with these sort of spammers, once someone has Flagged such post(s).
 
Humor
 
But first, some humor. Does anyone remember this guy? Anyway, that old infomercial kept playing over and over in my head today while I was working on this. I think we stumbled across some of his students! OK, carrying on...
 
What Not To Do
 
First thing to probably point out, let's not simply edit out these links one by one as we come across them. That doesn't really solve the problem. In fact it makes it worse by eliminating the "trail of bread crumbs" so to speak, the easiest way we have to "get them all" (which is by recursive searching). Allow me to explain...
 
These links seem to be posted in groups, by a small number of spammers. Once you catch on to one part of a cluster of them, it is actually pretty easy to methodically work your way through and find quite a few more, and "get them all" (within a given cluster).
 
Modus Operandi
 
But let me back up even more, for those who are totally unaware of this issue. What these people (we think they are human) are doing, is to register, and then post some at least seemingly relevant information in some topic, at least enough to get their post(s) approved. Then they come back some days or even weeks (!) later, and edit their post(s) to insert spam links. To see some actual examples, have a look at the Announcement post linked in the beginning.
 
1. Check Profile
 
So, once I found one such post / Member, the first thing I would do is look at their profile. Typically they will have from 1-5 posts or so. I would right click, and open each new post in another tab. Sometimes you will have to search then in the thread (using your browser search function, Ctrl-F in Firefox) to find the post. You will quickly be able to determine whether they are a spammer or not (you will see all the spam links in all their few handful of posts).
 
2. Flag as Spammer
 
Once you are certain they are a spammer, there are a couple ways you can "Flag as Spammer." Since you already have their profile open, you can click that button in there. Other way is to mouse over their avatar, and then the gear at bottom right opens another little menu that gives you the same option. This should be the first real action you take, because it does a couple things all at once (which will save you some time):
it Hides (not Deletes) all their posts, and Bans them from the site (permanently)  
Note that the above are subject to Admin settings, and these are the current settings as of this writing.
 
3. Being Thorough
 
Now, if you like to be thorough (I do) I will also kind of go through the threads that contain their spam posts (especially after their post(s)) and look for the following:
did any other user (usually unintentionally, or on accident) quote the spam links? if so, edit out those spam links by hand and leave a note what you did make sure no actually useful content was hidden (I have yet to find this in even one case)  
4. What Must Be Done (at Minimum)
 
However at a very minimum, you should be taking down a list of all these spam links you come across. This is key to the whole process. Methodically complete all of the above for each spammer and each of his posts. When you are done you should have a list of spam links, and one or more Banned spammers, with all their posts Hidden.
 
5. Working our URL List of Spam Links
 
Next step, we do a regular search on the forums for each of the spam links in turn. I like to leave this search window up, and again right click and open each result in a new tab, do whatever I need to do, and then come back to the main search result list, and keep going. Some pointers for this phase:
Some results will be ones you already discovered Other results will lead you to additional spam posts and/or users. Take care of each of them in turn (as above) and continue to add to your URL list. Scratch each spam URL off your list once you have worked your way through all the results for that particular spam URL. Some times you may have to "massage" the URL a bit if it is too close to common search terms shorten to base URL add quotes around it prepend "https://www." etc...  
6. The End
 
Get yourself a cold, tasty, delicious adult beverage of your choosing. You earned it. You have made the world a slightly better place than it was this morning. You have Maintained Civilization. Etc. 
 
I think that just about covers it. Any questions, comments are welcomed.
 
One thing I would like to re-iterate, if you don't have the time / patience for this, just Flag the post(s) and leave it for someone else who does. I think it's better to handle these properly and thoroughly than to half-arse it, deleting few links and then handicapping our ability to "get them all" later on.
 
Thanks!
 
EDIT: As an example, I will include my working list, below. This is what I came up with in a couple of hours this afternoon, all starting from one link that @Igor sent me in IRC (this is a bulleted checklist and table from org-mode; names of non spammers vindicated in my search have been removed):
 
 

Yeah, but my guess is it is not intended by the developers over there to work this way
 
https://gist.github.com/EvilOlaf/ee16e3325b702a95b264dfc65937a78d
 
The last command before it dies is debconf-apt-progress -- apt-get --yes --no-install-recommends install netcat idn2 sqlite3 dns-root-data lighttpd php-common php-cgi php-sqlite3
If I run it by hand it dies the same way.
THOUGH if I remove the debconf-apt-progress it runs fine....
 
I provided a bunch of log files to pihole and cews kind a confirmed the issue. Lets see if they can fix it.

for the LEDs you can try the following:

ls -l /sys/class/leds
(here as example from a NanoPi Neo2):
lrwxrwxrwx 1 root root 0 Feb 20 21:50 nanopi:green:status -> ../../devices/platform/leds/leds/nanopi:green:status
lrwxrwxrwx 1 root root 0 Feb 20 21:50 nanopi:red:pwr -> ../../devices/platform/leds/leds/nanopi:red:pwr
 
then echo none to the trigger of the led-name: 
 
echo 'none' > /sys/class/leds/[name_of_the_led]/trigger
 
so it should look like this:
 
echo 'none' > /sys/class/leds/nanopi:green:status/trigger
 
You only have to check the led-names of your board and add the commands in /etc/rc.local before "exit 0"

For what it's worth, I've been running 5.5.0-rc2 on a number of NanoPi boards (NEO 2s and NEO 2 Blacks) for several weeks now, including one running mosquitto+Influx+Grafana+nginx+a lot of Python processes, and they've all worked flawlessly.

I got some Sunxi/Sunxi64 board running 5.5.0-rc2 running for some days (one or two weeks) and couldnt find any freezes.
Today dev is going on my systems to 5.5.0-rc6 - I will see if there will be any freezes.
 
Running Boards are OPi Zero, OPi One, BPI M2 Berry, NanoPi A64, NanoPi Neo2

Now I paid attention to the numbers of visitors
I have never seen such an influx of guests ....
 
14 Members, 0 Anonymous, 1208 Guests (See full list)

Problem solved!
 
The dtb file is wrong on newer Kernels after 5.3.9
There is an added option called dai-tdm-slot-width (description) in the sound category which is set to high (0x20). When you set this to 0x10 (decimal 16, I think 16Bit for audio!?) the Sound is in normal speed.
There is another typo, I think, in line 897 phy-names is set to "phy" but the name of the phy is "hdmi-phy" so its in old dtb's too.
Corrected dts for Orange Pi PC in attachment.
Please test this on other boards...
EDIT: Confirmed on sunvell R69 1.3 with Kernel 5.5.0cr2
 
Regards
devicetree-5.4.8.dts

USB on the back does not work => Information:
 
I compiled Armbian (Bionic, 5.5.0rc2) and tested it on my r69 h2 ver. 1.3 blue PCB with nothing special.
Everything works fine except the USB on the back.
After some investigation I checked the dtb file and there is the back-USB port configured as OTG.
I dont' know if is this a bug or a feature but if you want to use both USB you have ti change the dtb file.
After decompile change line 322 in dtb from "otg" to "host", compile it again and replace the orginal file in /boot
I added the corrected dts and the compiled dtb file for Kernel 5.5.0rc2.
 
sun8i-h2-plus-sunvell-r69.dtb sun8i-h2-plus-sunvell-r69.dts

Hi everyone. I have compiled sunxi-next u-boot and activated the SoC internal analog audio codec, now I am testing the mali node. Audio Working!
Commit:
https://github.com/juanesf/u-boot/commits/master
 

I did that on a NanoPi Neo with the FriendlyARM PCM5102A Hat
( https://www.friendlyarm.com/index.php?route=product/product&amp;product_id=169 )
using kernel 4.14.87-sunxi and armbian 5.67 (or later would be only 5.65?)
(before that I did use legacy kernel 3.4.x with the PCM510A)

and the armbian-BuildSystem
plus (THANKS to) informations in threads from  @dony71 , @Christos, @Valery Rezvyakov
and the the Reference-Threads you could find above
 
----------------------------------------------------------------------------------------------------------------------------------
BACKUP DTB (on NanoPi Neo)
----------------------------------------------------------------------------------------------------------------------------------
cp /boot/dtb/sun8i-h3-nanopi-neo.dtb /boot/dtb/sun8i-h3-nanopi-neo.dtb_org
 
----------------------------------------------------------------------------------------------------------------------------------
CONVERT dtb to dts (on NanoPi Neo)
----------------------------------------------------------------------------------------------------------------------------------
dtc -I dtb -O dts /boot/dtb/sun8i-h3-nanopi-neo.dtb -o /boot/dtb/sun8i-h3-nanopi-neo.dts
 
----------------------------------------------------------------------------------------------------------------------------------
EDIT /boot/dtb/sun8i-h3-nanopi-neo.dts
----------------------------------------------------------------------------------------------------------------------------------
nano /boot/dtb/sun8i-h3-nanopi-neo.dts
 
- change: status from "disabled" to "okay"
----------------------------------------------------------------------------------------------------------------------------------
FROM
 
                i2s@1c22000 {                         #sound-dai-cells = <0x0>;                         compatible = "allwinner,sun8i-h3-i2s";                         reg = <0x1c22000 0x400>;                         interrupts = <0x0 0xd 0x4>;                         clocks = <0x3 0x38 0x3 0x54>;                         clock-names = "apb", "mod";                         dmas = <0x13 0x3 0x13 0x3>;                         resets = <0x3 0x2b>;                         dma-names = "rx", "tx";                         status = "disabled";                         phandle = <0x4e>;                 };  

TO
 
                i2s@1c22000 {                         #sound-dai-cells = <0x0>;                         compatible = "allwinner,sun8i-h3-i2s";                         reg = <0x1c22000 0x400>;                         interrupts = <0x0 0xd 0x4>;                         clocks = <0x3 0x38 0x3 0x54>;                         clock-names = "apb", "mod";                         dmas = <0x13 0x3 0x13 0x3>;                         resets = <0x3 0x2b>;                         dma-names = "rx", "tx";                         status = "okay";                         phandle = <0x4e>;                 };
----------------------------------------------------------------------------------------------------------------------------------
CONVERT (BACK) dts to dtb (on NanoPi Neo)
----------------------------------------------------------------------------------------------------------------------------------
dtc -I dts -O dtb /boot/dtb/sun8i-h3-nanopi-neo.dts -o /boot/dtb/sun8i-h3-nanopi-neo.dtb_I2S_okay
 
----------------------------------------------------------------------------------------------------------------------------------
COPY new dtb over dtb (on NanoPi Neo)
----------------------------------------------------------------------------------------------------------------------------------
cp /boot/dtb/sun8i-h3-nanopi-neo.dtb_I2S_okay /boot/dtb/sun8i-h3-nanopi-neo.dtb
                
----------------------------------------------------------------------------------------------------------------------------------
COPY sun8i-h3-I2S-out.dts to home (working directory on NanoPi Neo)
----------------------------------------------------------------------------------------------------------------------------------
copy sun8i-h3-I2S-out.dts -->  /home/guido/
 
----------------------------------------------------------------------------------------------------------------------------------
armbian-add-overlay (on NanoPi Neo)
does only work if you got the kernel-headers installed for your actual kernel-version
(at this time the lastest kernel-header are (via armbian-config -> Software -> Install Headers)
Linux kernel headers for 4.14.84-sunxi on armhf - so NOT for kernel 4.19.y)
----------------------------------------------------------------------------------------------------------------------------------
root@npi-neo(192.168.6.24):/home/guido# armbian-add-overlay ./sun8i-h3-I2S-out.dts
Compiling the overlay
Copying the compiled overlay file to /boot/overlay-user/
Reboot is required to apply the changes

----------------------------------------------------------------------------------------------------------------------------------
dtbo is created (on NanoPi Neo)
----------------------------------------------------------------------------------------------------------------------------------
root@npi-neo(192.168.6.24):/home/guido# ls -l /boot/overlay-user/
insgesamt 4
-rw-r--r-- 1 root root 1323 Dez  7 19:34 sun8i-h3-I2S-out.dtbo
 
----------------------------------------------------------------------------------------------------------------------------------
user-overlay is created in /boot/armbianEnv.txt (on NanoPi Neo)
----------------------------------------------------------------------------------------------------------------------------------
verbosity=1 logo=disabled console=both disp_mode=1920x1080p60 overlay_prefix=sun8i-h3 overlays=usbhost1 usbhost2 rootdev=UUID=33ca90d6-130b-4d5f-a8f4-95b3b97ef5c0 rootfstype=ext4 usbstoragequirks=0x2537:0x1066:u,0x2537:0x1068:u user_overlays=sun8i-h3-I2S-out  
----------------------------------------------------------------------------------------------------------------------------------
now REBOOT (on NanoPi Neo)
----------------------------------------------------------------------------------------------------------------------------------
root@npi-neo(192.168.6.24):~# lsmod|grep i2s
sun4i_i2s              16384  0
snd_soc_core          118784  2 sun4i_i2s,sun8i_codec_analog
snd_pcm                69632  3 sun4i_i2s,snd_pcm_dmaengine,snd_soc_core
 
----------------------------------------------------------------------------------------------------------------------------------
EDIT config-default.conf (on armbian-BuildSystem)
----------------------------------------------------------------------------------------------------------------------------------
cd /home/guido/build
nano ./config-default.conf
replace content /home/guido/build/config-default.conf with attached
config-default.conf_nanopineo
./compile
-> With this conf, script compilation will stop to overwrite kernel source to build patch
-> At that time, overwrite original Kconfig with the one you modified above
(at "Make changes to U-Boot" press ENTER to proceed)
wait for
"Make your changes to /home/guido/build/cache/sources/linux-mainline/linux-4.14.y then press ENTER"
BUT DONT PRESS ENTER YET
 
----------------------------------------------------------------------------------------------------------------------------------
EDIT/SAVE Kconfig in a 2nd shell-Window (on armbian-BuildSystem)
----------------------------------------------------------------------------------------------------------------------------------
nano /home/guido/build/cache/sources/linux-mainline/linux-4.14.y/sound/soc/codecs/Kconfig
 
the part FROM
 
config SND_SOC_PCM5102A     tristate TO
 
config SND_SOC_PCM5102A     tristate "Texas Instruments PCM5102A CODEC - I2S"  
----------------------------------------------------------------------------------------------------------------------------------
NOW PRESS ENTER in the 1st shell-Windows (.compile.sh) (on armbian-BuildSystem)
----------------------------------------------------------------------------------------------------------------------------------
-> Then script compilation will stop again to ask whether you want to add pcm5102a to compile
-> Default is N, so you need to enter m for module compilation
Texas Instruments PCM5102A CODEC - I2S (SND_SOC_PCM5102A) [N/m/?] (NEW) m = m for module compilation
 
After compile is complete
 
----------------------------------------------------------------------------------------------------------------------------------
copy (via SCP/FTP?) the .deb's from /home/guido/build/output/debs (on armbian-BuildSystem) 
to /home/guido/ (on the NanoPi Neo)
----------------------------------------------------------------------------------------------------------------------------------
 
----------------------------------------------------------------------------------------------------------------------------------
INSTALL the .deb's (here only header and image - because it was already 5.67 (on NanoPi Neo)
----------------------------------------------------------------------------------------------------------------------------------
cd /home/guido 
dpkg -i ./linux-headers-next-sunxi_5.67_armhf.deb
dpkg -i ./linux-image-next-sunxi_5.67_armhf.deb
(image did include the .ko module for the pcm5102a)
 
----------------------------------------------------------------------------------------------------------------------------------
now REBOOT (on NanoPi Neo)
----------------------------------------------------------------------------------------------------------------------------------
 
=====================================================================================
=====================================================================================
!!!!!!!!!!!!!!!!!!!!!!!!!!!!! ATTENTION: !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
After reboot my NanoPi Neo show the following armbian-version:
ARMBIAN 5.65 stable Debian GNU/Linux 9 (stretch) 4.14.84-sunxi
and 2 upgrades for headers&image (without the PCM5102A support)
please keep in mind to freeze the kernel-updates in armbian-config
for not to loose the support (module) for the PCM5120A!
armbian-config -> system -> Freeze Disable kernel upgrades
=====================================================================================
=====================================================================================

----------------------------------------------------------------------------------------------------------------------------------
BE HAPPY about a successful i2s mapping in dmesg (on NanoPi Neo)
----------------------------------------------------------------------------------------------------------------------------------
root@npi-neo(192.168.6.24):~# dmesg|grep -i i2s
[    6.911751] asoc-simple-card sound_i2s: pcm5102a-hifi <-> 1c22000.i2s mapping ok
 
----------------------------------------------------------------------------------------------------------------------------------
I enabled also ananlog-Codec (on NanoPi Neo)
----------------------------------------------------------------------------------------------------------------------------------
root@npi-neo(192.168.6.24):/home/guido# aplay -l
**** Liste der Hardware-Geräte (PLAYBACK) ****
Karte 0: Codec [H3 Audio Codec], Gerät 0: CDC PCM Codec-0 []
  Sub-Geräte: 1/1
  Sub-Gerät #0: subdevice #0
Karte 1: I2Smaster [I2S-master], Gerät 0: 1c22000.i2s-pcm5102a-hifi pcm5102a-hifi-0 []
  Sub-Geräte: 1/1
  Sub-Gerät #0: subdevice #0

----------------------------------------------------------------------------------------------------------------------------------
/etc/asound.conf (on NanoPi Neo) - later I2S did switch automatically to card 0
----------------------------------------------------------------------------------------------------------------------------------
 
pcm.!default {     type hw     card 1     device 0 } ctl.!default {     type hw     card 1 }  
----------------------------------------------------------------------------------------------------------------------------------
Reference-Threads
----------------------------------------------------------------------------------------------------------------------------------
 
config-default.conf.mod_nanopineo
sun8i-h3-I2S-out.dts