guidol

Members
  • Content Count

    1417
  • Joined

  • Last visited


Reputation Activity

  1. Like
    guidol got a reaction from Igor in OpiOne: /dev/zram0 = /var/log full while apt update   
    There I only have the default-file-entrys:
     
     
    I did now edit my /usr/lib/armbian/armbian-zram-config and inserted the lines from the fix at the right place (which were missing).
    The fix inserted/corrected the SystemMaxUse=20M in /etc/systemd/journald.conf
     
    Before a reboot I did enter a "journalctl --vacuum-size=5M"
     
    And after the reboot I have:
    root@opi-one(192.168.6.114):~# df Dateisystem 1K-Blöcke Benutzt Verfügbar Verw% Eingehängt auf /dev/zram0 49584 19676 26324 43% /var/log Many thanks at @Igor
     
     
  2. Like
    guidol reacted to Shoka in Error updating build scripts.   
    I encountered this running apt-get update, not during a build.
     
    Tried several fixes without success.
    Eventually fixed it using info from the bug report for the last time it occurred in 2018.
    here
    sudo apt-key adv --keyserver pool.sks-keyservers.net --recv-keys ED75B5A4483DA07C Harry
  3. Like
    guidol reacted to martinayotte in Switching SUNXI-DEV to 5.6.y   
    I've done a fresh "git clone" to get rid of the issue.
    I'm now doing a new a new "tour of my Allwinner garden" with 5.6.1, and then I will do some commits ...
  4. Like
    guidol reacted to jock in [WIP] Armbian for RK322X devices   
    Hello,
     
    following the recent thread on LibreElec forum about an unofficial image for rk3229 devices, I would like to make public the work made by me and @fabiobassa about bringing rk322x support to armbian.
    For those which are interested, at the moment it is available on github -> here <-
    It is still a work in progress status, but all the fundamentals are in place. Stability, performance and features have already reached an almost mature status.
    Most of the love has been poured into supporting and bringing up the legacy rockchip 4.4 kernel, but in the near future the goal is to fully support the mainline kernel.
     
    What works:
    Three tested rk322x tv box boards: MXQ-4K - target: xt-mx4vr-v01 Schishion V88 - target: xt-mx4vr-v01 MXQ-4K Pro target: r329q  
    Should work flawlessy on boards with RK3228a, RK3228b and RK3229, with either DDR2 and DDR3 memories. RK3228a boards may have some issues on mainline kernel although. Mainline u-boot OPTEE provided as Trusted Execution Environment All 4 cores are working Ethernet Serial UART (configured at 115200 bps, not 1.5Mbps!) Thermals and frequency scaling OTG USB 2.0 port (also as boot device!) EHCI/OHCI USB 2.0 ports MMC subsystem (including eMMC, SD and sdio devices) Hardware video acceleration (fully supported via RKMPP on legacy kernel, partial support via hantro kernel driver on mainline) NAND is available only on legacy (but not as boot device due to mailine u-boot missing the rockchip NAND driver) SSV6051 wifi over SDIO only on legacy (crappy driver, it is blacklisted and requires to be removed from blacklist from /etc/modprobe.d/blacklist.conf) Full GPU acceleration on legacy kernel, mainline kernel has lima driver compiled in but X11 does not work with (you are still free to compile and install mali kernel driver on mainline yourself, until lima matures) U-boot boot order priority: first the sdcard, then the USB OTG port and eventually the internal eMMC; you can install u-boot (and the whole system) in the internal eMMC and u-boot will always check for images on external sdcard/USB first.  
     
     
    Building:
    You can build your own image follow the common steps to build armbian for other tv boxes devices (ie: when you are in the moment to choose the target board, switch to CSC/TVB/EOL boards and select "r329q" or "xt-mx4vr-v01" from the list). In case your board is not listed here, I suggest you to try with xt-mx4vr-v01 board, which has more chances to boot.
     
    Prebuilt images:
    If you don't want to build Armbian yourself, there are some prebuilt images already available:
     
    Armbian 20.05.0 Ubuntu Focal Desktop 20.04 - kernel 4.4.194 - xt-mx4vr-v01 board Armbian 20.05.0 Ubuntu Focal Desktop 20.04 - kernel 4.4.194 - r329q board Armbian 20.05.0 Debian Buster Minimal - kernel 5.4.21 - xt-mx4vr-v01 board (only RK3228b and RK3229) Armbian 20.05.0 Debian Buster Minimal - kernel 5.4.21 - r329q board (only RK3228b and RK3229)  

    Quick installation instructions:
    If you already erased the internal eMMC, the board will boot from SD card. If you didn't, follow the instructions below to backup and/or erase the internal eMMC. As as alternative, there is a procedure using the libreelec bootloader described by @hexdump in a post below that does not require erasing the internal memory. flash the image on the sdcard, plug it in and plug the power cord. In alternative, you can burn the image directly to the eMMC (instructions below) Wait some seconds, the led should start blinking soon. HDMI output during u-boot is not available yet, so just wait for the kernel log and login prompt; the first time the boot process will take a couple of minutes or more because the filesystem is going to be resized. As usual, armbian default credentials are user: root password: 1234  
    Backup the existing firmware:
    You may want to first backup your existing firmware. You may do so using rkdeveloptool and maskrom/rockusb mode:
     
    Obtain a copy of rkdeveloptool: a compiled binary is available in the official rockchip-linux rkbin github repository. If you prefer, you can compile it yourself from the sources available at official rockchip repository Unplug the power cord from the tv box Plug an end of an USB Male-to-male cable into the OTG port (normally it is the lone USB port on the same side of the Ethernet, HDMI, analog AV connectors) Plug the other end of the USB Male-to-male cable into an USB port of your computer If everyting went well, using lsusb you should see a device with ID 2207:320b change directory and move into rkbin/tools directory, run ./rkdeveloptool rfi then take note of the FLASH SIZE megabytes (my eMMC is 8Gb, rkdeveloptool reports 7393 megabytes) run ./rkdeveloptool rl 0x0 $((FLASH_SIZE * 2048)) backup.data (change FLASH_SIZE with the value you obtained the step before) once done, the internal eMMC is backed up to backup.data file  
    Restore the firmware:
    First we have to restore the original bootloader, then restore the original firmware.
    Running rkdeveloptool with these switches will accomplish both the jobs:
    ./rkdeveloptool db ../rk32/rk322x_loader_v1.04.232.bin Downloading bootloader succeeded. ./rkdeveloptool ul ../rk32/rk322x_loader_v1.04.232.bin Upgrading loader succeeded. ./rkdeveloptool wl 0x0 backup.data Write LBA from file (100%)  
    Erase the eMMC and boot from SD:
    To let the boards boot from SD, we need to erase the internal eMMC/NAND. The SoC will first look for a bootloader in internal memory, it won't find anything and so will go further looking into external SD.
     
    Clearly you need to erase the internal eMMC/NAND just once.
     
    Obtain a copy of rkdeveloptool: a compiled binary is available in the official rockchip-linux rkbin github repository. If you prefer, you can compile it yourself from the sources available at official rockchip repository Unplug the power cord from the board Plug an end of an USB Male-to-male cable into the OTG port (normally it is the lone USB port on the same side of the Ethernet, HDMI, analog AV connectors) Plug the other end of the USB Male-to-male cable into an USB port of your computer If everyting went well, using lsusb you should see a device with ID 2207:320b run ./rkdeveloptool -ef and wait a few seconds once done, the internal eMMC is erased and the device will boot from the sdcard from now on  
    Boot from the internal eMMC:
    You can burn the image directly to the internal eMMC so the device will boot without the extra SD card. You can do this step later using the included armbian-config utility which transfers the whole running system on the internal eMMC, so I suggest to first try booting from the sdcard using the other method.
    Most of the procedure is similar to the above:
     
    Obtain a copy of rkdeveloptool: a compiled binary is available in the official rockchip-linux rkbin github repository. If you prefer, you can compile it yourself from the sources available at official rockchip repository Unplug the power cord from the board Plug an end of an USB Male-to-male cable into the OTG port (normally it is the lone USB port on the same side of the Ethernet, HDMI, analog AV connectors) Plug the other end of the USB Male-to-male cable into an USB port of your computer If everyting went well, using lsusb you should see a device with ID 2207:320b Decompress the Armbian image you downloaded run ./rkdeveloptool wl 0x0 <armbian-image.img> once done unplug the USB cord and then plug back the power cord  
     
    Note: rockchip devices cannot be bricked. If the internal flash does not contain a bootable system, they will always boot from the sdcard. If, for a reason, the bootable system on the internal flash is corrupted or is unable to boot correctly, you can always force the maskrom mode shorting the eMMC clock pin on the PCB. Just google around if you get stuck on a faulty bootloader, the technique is pretty simple and requires a simple screwdriver.
     
    I will continue to work on this project and refine both the legacy and mainline kernel and when the support will be in the same ballpark as other targets I will ask @Igor if it is a good idea to merge it into the main armbian repository.
     
    Critics, suggestions and contributions are welcome!
     
    Credits:
    @fabiobassa for his ideas, inspiration, great generosity in giving the boards for development and testing. The project of bringing rk322x into armbian would not have begun without his support! Justin Swartz, for his work and research to bring mainline linux on rk3229 (repository here) @knaerzche for his great contribution to libreelec support and mainline patches
  5. Like
    guidol reacted to martinayotte in Switching SUNXI-DEV to 5.6.y   
    hummm ! Trying to prepare for commit my previous work, I faced a huge git merge conflict ...
    I had to do a new "git clone" to get rid of the conflict ... I'm now working on redoing every fixes one by one ...
    Maybe it will take few days ...
     
  6. Like
    guidol reacted to Werner in Added Nanopi R2S   
    It is listed now: https://www.friendlyarm.com/index.php?route=product/product&product_id=282
  7. Like
    guidol reacted to mantouboji in SPI on OrangePi One Success   
    After some hack,  I use the SPI port on OPi One to connect with a MAX6675 board. 
     
    The SPI port on One is SPI0,  so armbianEnv.txt should include these:
     
    overlays=spi-spidev param_spidev_spi_bus=0 param_spidev_spi_cs=0  
    the MAX6675 connects to OPi One as:
     
    MAX6675                       One GPIO
    ------------------------------------------
    VCC                                 PIN17
    GND                                PIN20
    SCK                                 PIN23
    CS                                   PIN24
    SO                                  PIN21
     
     
    Then use the attachment program to read from MAX6675
    readmax6675.c
  8. Like
    guidol got a reaction from lanefu in Rename Supporter to Donator   
    no problem  I had issues to center the text - so you did it.
    I only did try to help out a little bit  
  9. Like
    guidol reacted to Werner in Rename Supporter to Donator   
    Same as I do
  10. Like
    guidol got a reaction from Igor in Rename Supporter to Donator   
    no problem  I had issues to center the text - so you did it.
    I only did try to help out a little bit  
  11. Like
    guidol got a reaction from Werner in Rename Supporter to Donator   
    no problem  I had issues to center the text - so you did it.
    I only did try to help out a little bit  
  12. Like
    guidol reacted to flippy in Fix dtb of aml s905d phicomm n1 box   
    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>; };  
  13. Like
    guidol reacted to martinayotte in Switching SUNXI-DEV to 5.6.y   
    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 ...
  14. Like
    guidol reacted to lanefu in Armbian 20.02 (Chiru) Release Thread   
    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  
  15. Like
    guidol reacted to count-doku in Armbian 20.02 (Chiru) Release Thread   
    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? 
     
  16. Like
    guidol reacted to martinayotte in Switching SUNXI-DEV to 5.6.y   
    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 ...
     
  17. Like
    guidol reacted to lanefu in Armbian 20.02 (Chiru) Release Thread   
    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.
  18. Like
    guidol reacted to lanefu in Armbian 20.02 (Chiru) Release Thread   
    check out the branch direclty and try what i said here
     
     
  19. Like
    guidol reacted to Werner in Is it possible to shutdown properly an OrangePi Zero in case of power loss?   
    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
  20. Like
    guidol reacted to lanefu in Armbian 20.02 (Chiru) Release Thread   
    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
  21. Like
    guidol reacted to lanefu in Armbian 20.02 (Chiru) Release Thread   
    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
     
     
  22. Like
    guidol reacted to martinayotte in [RESOLVED] Nanopi Neo2 don't boot, all leds on   
    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 ...
  23. Like
    guidol got a reaction from Tido in [Moderation] Dealing with subtle spammers placing "tiny little ads"   
    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.
  24. Like
    guidol got a reaction from Tido in [Moderation] Dealing with subtle spammers placing "tiny little ads"   
    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?
  25. Like
    guidol reacted to TRS-80 in [Moderation] Dealing with subtle spammers placing "tiny little ads"   
    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.