Christos
-
Posts
306 -
Joined
-
Last visited
Content Type
Forums
Store
Crowdfunding
Applications
Events
Raffles
Community Map
Posts posted by Christos
-
-
Just did another build with the 'Legacy' kernel v4.4.213 (instead of the 'current' that I did previously) and the /boot/dtb/overlay folder exists.
Armbian_21.05.0-trunk_Tinkerboard_focal_legacy_4.4.213_xfce_desktop.img
So, in new 5.x Tinkerboard kernels, by choosing 'current' there is no /boot/dtb/overlay folder but exist in legacy kernel 4.4.213.
Is that 'by design' or is simply the build system broken for Tinkerboard with 5.x kernel ?
-
Hi,
New build, Armbian_21.05.0-trunk_Tinkerboard_focal_current_5.10.22_xfce_desktop.img.
The build finished ok and the image after flashing is working just fine, but..
unfortunately there is no /boot/dtb/overlay folder and of course none and its .dtbo entries are found anywere.
Am I missing something ?
Is the latest build system broken for Tinkerboard ?
Do I need to specify something during the build process menu ?
/PS
Just checked with the Armbian ready-made provided image for Tinkerboard, the
Armbian_21.02.1_Tinkerboard_focal_current_5.10.12_desktop.img.xz
and
Armbian_21.02.3_Tinkerboard_buster_current_5.10.21_xfce_desktop.img.xz
they also lack the /boot/dtb/overlay folder..
-
On 11/22/2019 at 5:20 AM, nikkov said:
I made some investigation and found that unstable phase is a consequence of sigma-delta modulation for audio PLL from this commit
Sigma-delta modulation make more exact frequency but it leads variable phase of clocks. This means that with the kernel> 4.15 some codecs will not work, as they will not be able to synchronize with the clocks.
My PCM5102A may work only with 48k, but not higher
Hi @nikkov
Although quite more than a year old thread but it looks that I also stumbled on that problem too.
Terrible phase noise of the produced bitclock in all samplerates tested (48/96/192KHz). Attached the relevant oscilloscope screenshot.
It seems that this bitclock phase instability, jitter, creates problems in codec/DAC/ADC parts that have internal PLL and the outcome in my case is a bit of audible noise during play.
Tested the same board/hardware with a RPi and it works ok, but with OPiPC and latest Armbian with kernel 5.10.8 is having this audible output noise problem.
Did you manage to have a fix or possibly reverted the mentioned patch succesfully ?
Christos
-
When running this
sudo cat /sys/kernel/debug/clk/clk_summaryI get the list of clocks and the specific interest is in these
pll-audio-base 0 0 0 24576000 50000 0 50000 pll-audio-8x 0 0 0 49152000 50000 0 50000 i2s1 0 0 0 49152000 50000 0 50000 pll-audio-4x 0 0 0 24576000 50000 0 50000 i2s0 0 0 0 24576000 50000 0 50000 i2s2 0 0 0 24576000 50000 0 50000 pll-audio-2x 0 0 0 12288000 50000 0 50000 pll-audio 0 0 0 24576000 50000 0 50000 ac-dig 0 0 0 24576000 50000 0 50000 spdif 0 0 0 24576000 50000 0 50000Now, the i2s0 (which interests me) is under pll-audio-4x and has 24576000Hz
So the is20 is clocked at 24576000Hz, but I want it to be clocked at 49152000Hz
The question is this, how can I move the i2s0 under pll-audio-8x with 49152000Hz ?
Can I simply instruct it via a DT overlay that its master clock will be 49152000Hz?
Should I need to re-parent it ? Is there an example on how this can be done via a DT overlay for i2s0 or does it need kernel source patching ? Is it even feasible ?
Christos
-
Hi @jeanrhum
For my case I wanted to examine the running DT so I executed
dtc -I fs -O dts /proc/device-treewhich was segfault in Debian.
The plain decompile of a specific dtb works though eg
dtc -I dtb -O dts /boot/dtb/sun8i-h3-orangepi-pc.dtbMy kernel in both Debian and Ubuntu is the same 'current', 5.10.8
Christos
-
Just seen this thread, I also tried to decompile DT on a H3 OPiPC running Armbian (21.02)
Got exactly that behavior first a bunch of warnings and then segfault, on Debian builds desktop or console.
On Ubuntu Focal it was giving the warnings too but at the end it decompiled successfully and showing the dts.
Just letting you know if you still going on with this project.
Christos
-
Hi,
Need to interface a multichannel codec to an OPiPC, having 8 channels out and 6 channels in.
So trying to find any example of an overlay for H3 with TDM usage on simple-audio-card giving more than 2 channels in/out.
Seen that the latest i2s driver for H3 (sun2i-i2s.c) does support TDM (DSP_A/DSP_B) but did not found any relevant overlay for H3 so far.
Any help is appreciated.
Christos
-
Thanks @Igor ,
I thought based on what you said that there is some other method with armbian-config, ok no worries.
I got it now, it seems that the remove auto login service is a one-off, so it runs once after 10mins and removes the auto login and it never runs again so if we put again back the deleted file everything will be ok.
Thanks again
Christos
-
Ohh.. ok @Igor,
So its not a gremlin :-))
It got really weird but now its explained, thanks.
So, what is the appropriate procedure if someone wants to have the autologin always enabled?
You mentioned armbian-config but I could not find any relevant option there to use, could it be removed at some time or should I look better?
-
Thanks @Igor
Hmm.. file (22-armbian-autologin.conf) looks not present now
christos@orangepipc:/etc/lightdm/lightdm.conf.d$ ls -l total 4 -rw-r--r-- 1 root root 110 Jan 15 18:39 11-armbian.conf christos@orangepipc:/etc/lightdm/lightdm.conf.d$I added the file manually with the indicated contents and now it does work and autologin is ok.
Did though a new install and seen that the specific autologin config file is there present..
I'm gonna use another microsd just in case, it a first to have such issue (using SanDisk A1 16GB) but who knows.
Thanks
Christos
-
Hi,
Just did a new armbian build
Armbian_21.02.0-trunk_Orangepipc_buster_current_5.10.6_desktop
and flashed the image.
It works ok but after some reboot times the auto login to desktop is not working anymore and it prompts for user login.
Tried quite a few times to re-install but always after a few shutdown and start again cycles it reverts to login prompt and not auto login.
Also tried to find a solution in the forum but the files and config involved in previous solutions is no longer valid in the newer builds (/usr/share/lightdm/lightdm.conf.d/60-lightdm-gtk-greeter.conf or /etc/default/nodm).
So the question is this, how can I configure the systen for having auto login ?
Christos
-
Indeed after a fresh checkout things got better and now I can build ok the supported items in build system.
The problem is that jessie build bails out with error, though as @Igor said, the 3.4.113 can still be compiled with xenial and the 19.08 branch (for as long as it does..)
A minor but time consuming task is that whenever we have to make a new fresh checkout, it takes so many hours to re-download all the cached components specifically the toolchains and thats a real bummer.
Thanks for your hints.
-
6 minutes ago, lanefu said:
That test was from latest checkout?
Have you tried cleaning your cache folder?
It was from a checkout a few months back, in June, though from what I know and see, the build script perform any update required.
Will do tomorrow a full clean new checkout and report back.
-
Thank you @count-doku , @Igor
It seems though that the problem here might be more than just jessie or 3.4.113.
Please have a look at the logs posted above and on those following
My Armbian build host is Ubuntu Bionic 18.04 (x64)
Tried a few builds with the mainline kernel, Strech and Ubuntu, all of them gave error
Armbian build for (AllWinner H3) OPiPC, Mainline kernel, Debian 9 Strech, Server/console, full os image
Setting up libsasl2-modules-db:armhf (2.1.27~101-g0780600+dfsg-3+deb9u1) ... Setting up libsasl2-2:armhf (2.1.27~101-g0780600+dfsg-3+deb9u1) ... Setting up libssl1.0.2:armhf (1.0.2u-1~deb9u1) ... Processing triggers for libc-bin (2.24-11+deb9u4) ... Setting up libssl1.1:armhf (1.1.0l-1~deb9u1) ... Setting up openssl (1.1.0l-1~deb9u1) ... Processing triggers for libc-bin (2.24-11+deb9u4) ... [ o.k. ] Installing packages for [ Armbian ] Reading package lists... Building dependency tree... Reading state information... E: Unable to locate package armbian-firmware [ error ] ERROR in function create_rootfs_cache [ debootstrap.sh:229 ] [ error ] Installation of Armbian packages failed [ o.k. ] Process terminated [ error ] ERROR in function unmount_on_exit [ image-helpers.sh:62 ] [ error ] debootstrap-ng was interrupted [ o.k. ] Process terminatedArmbian build for (AllWinner H3) OPiPC, Mainline kernel, Ubuntu Xenial 16.04 LTS, Server/console, full os image
Setting up console-setup (1.108ubuntu15.5) ... update-initramfs: deferring update (trigger activated) Processing triggers for libc-bin (2.23-0ubuntu11) ... Processing triggers for systemd (229-4ubuntu21.23) ... Processing triggers for initramfs-tools (0.122ubuntu8.16) ... Processing triggers for resolvconf (1.78ubuntu7) ... Processing triggers for ca-certificates (20170717~16.04.2) ... Updating certificates in /etc/ssl/certs... 17 added, 42 removed; done. Running hooks in /etc/ca-certificates/update.d... done. [ o.k. ] Installing packages for [ Armbian ] Reading package lists... Building dependency tree... Reading state information... E: Unable to locate package armbian-firmware [ error ] ERROR in function create_rootfs_cache [ debootstrap.sh:229 ] [ error ] Installation of Armbian packages failed [ o.k. ] Process terminated [ error ] ERROR in function unmount_on_exit [ image-helpers.sh:62 ] [ error ] debootstrap-ng was interrupted [ o.k. ] Process terminatedArmbian build for (AllWinner H3) OPiPC, Mainline kernel, Ubuntu Bionic 18.04 LTS, Desktop, full os image
Setting up python3-gi (3.26.1-2ubuntu1) ... Setting up libgssapi-krb5-2:armhf (1.16-2ubuntu0.1) ... Setting up libavahi-client3:armhf (0.7-3.1ubuntu1.2) ... Setting up ubuntu-minimal (1.417.3) ... Setting up networkd-dispatcher (1.7-0ubuntu3.3) ... Installing new version of config file /etc/default/networkd-dispatcher ... Setting up libcups2:armhf (2.2.7-1ubuntu2.7) ... Processing triggers for initramfs-tools (0.130ubuntu3) ... Processing triggers for libc-bin (2.27-3ubuntu1) ... Processing triggers for systemd (237-3ubuntu10.33) ... Processing triggers for hicolor-icon-theme (0.17-2) ... Processing triggers for mime-support (3.60ubuntu1) ... [ o.k. ] Installing packages for [ Armbian ] Reading package lists... Building dependency tree... Reading state information... E: Unable to locate package armbian-firmware [ error ] ERROR in function create_rootfs_cache [ debootstrap.sh:229 ] [ error ] Installation of Armbian packages failed [ o.k. ] Process terminated [ error ] ERROR in function unmount_on_exit [ image-helpers.sh:62 ] [ error ] debootstrap-ng was interrupted [ o.k. ] Process terminatedIt looks to me that the problem is generic to all builds, could it be related to this ? What happenned to those apps and their repo?
E: Unable to locate package armbian-firmware E: Unable to locate package mmc-utilsAnyway, as it is right now, it seems that I cannot build anything related to H3, legacy kernel or mainline, no H3 build succeeds.
Did not test though any other CPU..
I do not know if I am missing something, I hope you can find a solution.
-
Hi @Igor
Thanks for answering.
The platform I use is OPiPC and I do indeed need the 3.4.113.
Tried every possible combination, (with BUILD_TAG or without, server or desktop etc) of either debian or ubuntu with the default/legacy 3.4.113.
It looks that all of them during build do stop with the exact same message
Reading state information... E: Unable to locate package armbian-firmware E: Unable to locate package mmc-utils [ error ] ERROR in function create_rootfs_cache [ debootstrap.sh:229 ] [ error ] Installation of Armbian packages failed [ o.k. ] Process terminated [ error ] ERROR in function unmount_on_exit [ image-helpers.sh:62 ] [ error ] debootstrap-ng was interrupted [ o.k. ] Process terminatedObviously that is something different than phasing out jessie.
If I understand it correctly, Armbian can no longer be build with the default/legacy sunxi kernel for OrangePi H3 in any way ? so Armbian has abandoned the 3.4.113 ?
Is that correct ?
-
It has been a while since I did a build and did not notice this change.
My environment relies on jessie thus I compile with this.
sudo ./compile.sh SET_EXPERT=yes RELEASE=jessieWhen tried a build got these errors during compile
Err http://httpredir.debian.org jessie-backports/main armhf Packages 404 Not Found [IP: ::1 3142] Err http://httpredir.debian.org jessie-backports/contrib armhf Packages 404 Not Found [IP: ::1 3142] Err http://apt.armbian.com jessie/main armhf Packages 404 Not Found [IP: ::1 3142] Err http://httpredir.debian.org jessie-backports/non-free armhf Packages 404 Not Found [IP: ::1 3142] Err http://apt.armbian.com jessie/jessie-utils armhf Packages 404 Not Found [IP: ::1 3142] Err http://apt.armbian.com jessie/jessie-desktop armhf Packages 404 Not Found [IP: ::1 3142] Fetched 10.1 MB in 8s (1187 kB/s) W: Failed to fetch http://apt.armbian.com/dists/jessie/main/binary-armhf/Packages 404 Not Found [IP: ::1 3142] W: Failed to fetch http://apt.armbian.com/dists/jessie/jessie-utils/binary-armhf/Packages 404 Not Found [IP: ::1 3142] W: Failed to fetch http://apt.armbian.com/dists/jessie/jessie-desktop/binary-armhf/Packages 404 Not Found [IP: ::1 3142] W: Failed to fetch http://httpredir.debian.org/debian/dists/jessie-backports/main/binary-armhf/Packages 404 Not Found [IP: ::1 3142] W: Failed to fetch http://httpredir.debian.org/debian/dists/jessie-backports/contrib/binary-armhf/Packages 404 Not Found [IP: ::1 3142] W: Failed to fetch http://httpredir.debian.org/debian/dists/jessie-backports/non-free/binary-armhf/Packages 404 Not Found [IP: ::1 3142] E: Some index files failed to download. They have been ignored, or old ones used instead. [ o.k. ] Upgrading base packages [ Armbian ]And after a while the compilation stopped with this
Processing triggers for libc-bin (2.19-18+deb8u10) ... Processing triggers for ca-certificates (20141019+deb8u4) ... Updating certificates in /etc/ssl/certs... 0 added, 0 removed; done. Running hooks in /etc/ca-certificates/update.d....done. [ o.k. ] Installing packages for [ Armbian ] Reading package lists... Building dependency tree... Reading state information... E: Unable to locate package armbian-firmware E: Unable to locate package mmc-utils [ error ] ERROR in function create_rootfs_cache [ debootstrap.sh:229 ] [ error ] Installation of Armbian packages failed [ o.k. ] Process terminated [ error ] ERROR in function unmount_on_exit [ image-helpers.sh:62 ] [ error ] debootstrap-ng was interrupted [ o.k. ] Process terminatedThen I searched through the forum and seen this thread.
Is there a way to reference the archived jessie when performing a build ?
It seems that the build scripts use the previous place of jessie.
Can someone change the build scripts and when they refer to jessie to automatically point/refer to the new place you puted them ?
regards,
Christos
PS
My build is OrangePiPC default/legacy 3.4.113, jessie, console/server.
-
-
-
Hi,
Tried a new Armbian build for OPiPC today, legacy (3.4.113) and seen that only Debian 9 is available (not showing Debian 8), so build fails since Debian 9 cannot work with legacy.
So, is Armbian dropping legacy kernels (3.4.113) on Debian?
Need Debian 8 console/server with legacy, so what can I do ?
[ error ] ERROR in function source [ configuration.sh:90 ] [ error ] Building Debian Stretch images with selected kernel is not supported [ o.k. ] Process terminated -
-
Hi,
Can someone help me on how we can set a uBoot splash screen (with a .bmp) instead of the running boot text?
Need this in a OPiPC, legacy (3.4.113).
Any help is welcome.
Christos
-
-
Thanks @WarHawk_AVG
Unfortunately could not setup a hotspot in OPiPC using the armbian-config.
Tried to use various usb/wifi dongles and with none that I used got any results.
Also, I bought one of the specified in the download page as supported, the Comfast with RTL8811AU chipset.
OPiPC runnning latest 5.51 Debian (8) legacy kernel 3.4.113 simply does not even recognizes it for use as client.
Not creating the wlan0 device at all.
___ ____ _ ____ ____ / _ \ _ __ __ _ _ __ __ _ ___ | _ \(_) | _ \ / ___| _ | | | | '__/ _` | '_ \ / _` |/ _ \ | |_) | | | |_) | | _| |_ | |_| | | | (_| | | | | (_| | __/ | __/| | | __/| |___ |_ _| \___/|_| \__,_|_| |_|\__, |\___| |_| |_| |_| \____| |_| |___/ Welcome to ARMBIAN 5.51 user-built Debian GNU/Linux 8 (jessie) 3.4.113-rt143-sun8i System load: 0.00 0.03 0.05 Up time: 22 min Memory usage: 16 % of 997MB IP: 192.168.1.70 CPU temp: 51°C Usage of /: 11% of 15G dmesg [ 826.660215] ehci_irq: highspeed device connect [ 826.910179] usb 4-1: new high-speed USB device number 5 using sunxi-ehci [ 827.062370] usb 4-1: New USB device found, idVendor=0bda, idProduct=a811 [ 827.062406] usb 4-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 827.062437] usb 4-1: Product: 802.11ac WLAN Adapter [ 827.062460] usb 4-1: Manufacturer: Realtek [ 827.062483] usb 4-1: SerialNumber: 00e04c000001 root@orangepipcplus:~# ifconfig eth0 Link encap:Ethernet HWaddr e2:bd:ab:0f:e9:b7 inet addr:192.168.1.70 Bcast:192.168.1.255 Mask:255.255.255.0 inet6 addr: 2a02:582:d0e:e00:e0bd:abff:fe0f:e9b7/64 Scope:Global inet6 addr: fe80::e0bd:abff:fe0f:e9b7/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:567 errors:0 dropped:0 overruns:0 frame:0 TX packets:855 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:45453 (44.3 KiB) TX bytes:138041 (134.8 KiB) Interrupt:114 lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) root@orangepipcplus:~#So, am I missing something? Do I need to do something in order for the device to be identified?
Is the download page with supported/tested interfaces valid ?
https://www.armbian.com/orange-pi-pc/
Can I use the Comfast RTL8811AU dongle?
-
Hi,
Got Debian (8) legacy 3.4.113 server/console and would like to setup a WiFi hotspot. (latest Armbian build 5.51)
Seen two methods in Armbian docs
1. -> https://docs.armbian.com/User-Guide_Advanced-Features/#how-to-set-wireless-access-point
and via armbian_config in https://docs.armbian.com/User-Guide_Armbian-Config/
2. -> https://www.youtube.com/watch?v=__BJtInOQFY
So I'm a bit buffled about it.
Got some questions
Got a RTL8188CUS is it suported nowadays? or should I get a specific other one?
Do I need to have internet/ethernet/lan connection active during the hotspot creation via armbian_config?
After I execute the armbian config method, there are a few screens as in the video, probing various methods, and then the system without reporting any error returns to its menu selection but do not show the "Manage..access point".
After that what do I need to do have the WiFi hotspot up?
How can I give it the required parameters eg ip, passphrase key for users to connect, SSID etc, is there any guide for it ?
PS.
Also tried with a OPiPCPlus that has onboard wlan and armbian config result is the same, did not give the "Manage .. access point" menu after run. It also not support WiFi access point creation?
Tinkerboard build, no overlay folder
in Tinkerboard
Posted
Ok @Igor , thanks for the answer.
I know and understand, no worries.
I've seen that the 'legacy' works just fine and it gives me the features that I need, eg to have the ability to create and test my own driver additions and overlays in a well proven way that is universal in all Armbian images.
Thanks again.