Jump to content


  • Posts

  • Joined

  • Last visited

Profile Information

  • Location
    Vermont Western Cape South Africa

Contact Methods

  • Github

Recent Profile Visitors

744 profile views
  1. CHANGE: armbianEnv DOCKER FORCE CGROUPS V1: [working docker for legacy builds] extraargs=systemd.unified_cgroup_hierarchy=0 alistair@orangepizero2:~$ sudo docker run hello-world Hello from Docker! This message shows that your installation appears to be working correctly. To generate this message, Docker took the following steps: 1. The Docker client contacted the Docker daemon. 2. The Docker daemon pulled the "hello-world" image from the Docker Hub. (arm64v8) 3. The Docker daemon created a new container from that image which runs the executable that produces the output you are currently reading. 4. The Docker daemon streamed that output to the Docker client, which sent it to your terminal. To try something more ambitious, you can run an Ubuntu container with: $ docker run -it ubuntu bash Share images, automate workflows, and more with a free Docker ID: https://hub.docker.com/ For more examples and ideas, visit: https://docs.docker.com/get-started/ Possibly also (if you haven't): Debian builds update-alternatives --set iptables /usr/sbin/iptables-legacy Rootless: haven't tried.
  2. 'Green Light occasionally', your operating system, is from Orange Pi and not Armbian. Take a look at the downloads page.
  3. The pointer is correct and what got me through the traps before differentiating with xlate, I am uncertain about the exact shift. What do you suggest?
  4. Thank you @mcerveny, refreshing to have such constructive input. Was aware that gpu was at max, I should have changed that back. To clarify how are you compiling, xunlong?
  5. If you addressing me and above patch @mcerveny I'm happy to play here, its not serious. I cant speak for mainline process. In similar vein could quite happily carry on and not 'contribute' getting the 'stuffs' I need working and abuse. However I am completely against that type of behavior, and why I choose to donate and contribute.
  6. Hi nope, fun in spare time approach here, arm64-dts-allwinner-h616-Add-efuse_xlate-cpufreq.patch. Will submit pr to armbian 5.19.17 this week, if @going and @mcerveny can please review.
  7. Nice, looks like you standing up on Orangepi there? Interesting, I've been working low down your list, testing cpu-frequency-scaling for a while, which I think now will submit PR to 5.19 for others to try. The patch addresses all variants, but is not optimized, limited to 1512 Mhz, still WIP is the frequency calc's and micro-volt testing. All that you list has been in progress for a while, but has not seen the light here for lack of someone knowledgeable having time or perhaps interest, and that it seems there are still issues to be worked out in some parts. @going is doing an incredible job at maintaining sunxi here for us to develop off.
  8. Hi @carlos8agomez, which module are you using, assuming w1_gpio? There is an alternative that supports your sensor type, kernel driver w1_therm (W1_THERM_DS18B20, 0x28). For example, you could try MOSI, PH7, pin 19, gpio 231 (apparently better transfer, I have no clue though, can’t verify, not tried anything) this is SPI 1 bus, which could add to your complications. Unfortunately that is not enabled by default in the current or edge images, and will require you to do this. @orangepizero2:~ $ ls -l /dev/spidev* ls: cannot access '/dev/spidev*': No such file or directory @orangepizero2:~ $ dmesg | grep spi* [ 1.599280] sun6i-spi 5010000.spi: Failed to request TX DMA channel [ 1.599290] sun6i-spi 5010000.spi: Failed to request RX DMA channel For a user to do that you will have added an overlay, this is again not by default for Zero2 here now, and note what @lampra advised at the beginning of mainline development. You could probably be better off looking at PC10, however there could also be issues that would require you to dig deeper, and there is an overlay to write, paying attention to compatible = "allwinner,sun50i-h616 "; and its nodes. If you struggle with any of this I would suggest at least, reading the documentation, pin outs and their respective assignments, and trying @lampra suggestion above. Sorry I can’t be more helpful, than suggestions, I have not actually tried to do this for One wire sensors on opiz2.
  9. Hi, You can compile with: ./compile.sh CREATE_PATCHES="yes" The build will pause; atf, uboot, kernel, with each stop you can make your respective changes. Haven't looked much at boot options - perhaps someone with experience can chime in?
  10. Hi, haven't tried myself, think you have to add these lines to /boot/armbianEnv.txt. Check https://linux-sunxi.org/1-Wire regards hardware, reading further not sure which pin opiz2, have you looked at manual? What have you tried? Tell us a bit more and perhaps we can help, .. uname -a etc. Which sensor? what protocol(com can be different), hook up etc.. Also read up about overlays and MOSI PH7. There's lots of info in the forums. Might not be possible with current or edge configurations etc .. without personal efforts.... overlays=w1-gpio param_w1_pin=???? param_w1_pin_int_pullup=0
  11. Building from htop source on the board and configuring very simple exercise. alistair@orangepizero2:~$ htop --version htop 3.2.2-dev libsensors finds thermal on device 'opiz2' without configuration. I had a try to use the library by writing to it in c++, unfortunately had numerous compile issues, have not been able to extract the info I wanted yet. Time intervals are as @going has noted I did not look at source, beyond build at all and did not find configuration option, could easily missed if there.
  12. Thank you @going, will have a go later this evening.
  13. Right thank you both for the reasons and solutions, to add must be bullseye here, because same issue with new build. Other info: from htop-dev
  14. If am doing this right here result. Cpufreq and temperature not displaying. alistair@orangepizero2:~$ sudo apt remove htop Reading package lists... Done Building dependency tree... Done Reading state information... Done The following packages will be REMOVED: htop 0 upgraded, 0 newly installed, 1 to remove and 0 not upgraded. After this operation, 257 kB disk space will be freed. Do you want to continue? [Y/n] y (Reading database ... 131780 files and directories currently installed.) Removing htop (3.1.0-0~armbian20.08.2+1) ... Processing triggers for man-db (2.9.4-2) ... Processing triggers for mailcap (3.69) ... Processing triggers for desktop-file-utils (0.26-1) ... alistair@orangepizero2:~$ sudo apt install htop Reading package lists... Done Building dependency tree... Done Reading state information... Done Suggested packages: strace The following NEW packages will be installed: htop 0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded. Need to get 88.5 kB of archives. After this operation, 257 kB of additional disk space will be used. Get:1 http://apt.armbian.com bullseye/bullseye-utils arm64 htop arm64 3.1.0-0~armbian20.08.2+1 [88.5 kB] Fetched 88.5 kB in 3s (34.7 kB/s) Selecting previously unselected package htop. (Reading database ... 131772 files and directories currently installed.) Preparing to unpack .../htop_3.1.0-0~armbian20.08.2+1_arm64.deb ... Unpacking htop (3.1.0-0~armbian20.08.2+1) ... Setting up htop (3.1.0-0~armbian20.08.2+1) ... Processing triggers for mailcap (3.69) ... Processing triggers for desktop-file-utils (0.26-1) ... Processing triggers for man-db (2.9.4-2) ... alistair@orangepizero2:~$ htop --version htop 2.2.0 - (C) 2004-2020 Hisham Muhammad Released under the GNU GPL.
  15. Well that strange apt says already latest? alistair@orangepizero2:~$ sudo apt install htop [sudo] password for alistair: Reading package lists... Done Building dependency tree... Done Reading state information... Done htop is already the newest version (3.1.0-0~armbian20.08.2+1). 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. alistair@orangepizero2:~$
  • Create New...