Jump to content

guidol

Members
  • Posts

    1791
  • Joined

  • Last visited

Reputation Activity

  1. Like
    guidol reacted to Igor in THE testing thread   
    Edit: replaced with hires pictures.
     




  2. Like
    guidol got a reaction from Tido in Update PHP ?   
    @Club AC-News
    I checked on my old FOX G20 with Kernel 4.9.124 and debian-stretch and in the normal debian-repositories there is only PHP v7.0
     
    But it seem that you are not the only one who needs >= v7.3 on stretch
     
    And YES you have to add something manually:
    before you can install a new php-version: ========================================== sudo apt-get update sudo apt-get upgrade sudo apt install ca-certificates apt-transport-https wget -q https://packages.sury.org/php/apt.gpg -O- | sudo apt-key add - echo "deb https://packages.sury.org/php/ stretch main" | sudo tee /etc/apt/sources.list.d/php.list after that for PHP v7.3: ============= sudo apt install php7.3 sudo apt install php7.3-cli php7.3-common php7.3-curl php7.3-mbstring php7.3-mysql php7.3-xml or for PHP v7.4: ============= sudo apt install php7.4 sudo apt install php7.4-cli php7.4-common php7.4-curl php7.4-mbstring php7.4-mysql php7.4-xml for additonal informations (like configuring Apache/Nginx-Webserver to run PHP) check the following URLs:
    https://tecnstuff.net/how-to-install-php-on-debian-9/
    https://tecadmin.net/install-php-debian-9-stretch/
  3. Like
    guidol reacted to 5kft in Armbian v20.05 (Kagu) Planning Thread   
    @Igor - I just checked in a new patch that fixes the thermal throttling issues (see https://github.com/armbian/build/commit/cc55d03a7b306e80f6fae1e16de1942af5fe9701).  I have tested it extensively on the H5 (Nano Pi NEO2 Black) and throttling works great now.
     
    Example run after several minutes of "cpuburn-a53":
     
    The new patch includes the same changes for the H3, and I tested on an Orange Pi Zero H2+ with no heatsink, using both "stress" and "cpuburn-a7", and it works great.  Here's an example run using "cpuburn-a7":
     
     
  4. Like
    guidol got a reaction from Heisath in Date synchronization   
    All these messages show us, that you network isnt working or isnt working correct.
     
    How did you configure your network? Network-Manager? /etc/network/interfaces? armbian-config?
     
    Can you ping 8.8.8.8?
    Can you ping armbian.com?
    What says ifconfig for eth0 or wlan0?
    whats the IP of your gateway/DNS?
    what is the content of /etc/resolv.conf (when not using network-manager)
     
  5. Like
    guidol got a reaction from Werner in Date synchronization   
    All these messages show us, that you network isnt working or isnt working correct.
     
    How did you configure your network? Network-Manager? /etc/network/interfaces? armbian-config?
     
    Can you ping 8.8.8.8?
    Can you ping armbian.com?
    What says ifconfig for eth0 or wlan0?
    whats the IP of your gateway/DNS?
    what is the content of /etc/resolv.conf (when not using network-manager)
     
  6. Like
    guidol got a reaction from manuti in Orrange Pi PC is restarting and losing wifi connection   
    additionally to the 2 USB-devices
    - WLAN/WiFi Realtek 
    Bus 004 Device 002: ID 0bda:8179 Realtek Semiconductor Corp. RTL8188EUS 802.11n Wireless Network Adapter
    - USB Stick sda Kingston DataTraveler 3.0
    Bus 003 Device 002: ID 0930:6545 Toshiba Corp. Kingston DataTraveler 102/2.0 / HEMA Flash Drive 2 GB / PNY Attache 4GB Stick
     
    you do use more than 1008Mhz on the OPi PC (H3-CPU):
    Time CPU load %cpu %sys %usr %nice %io %irq CPU C.St.
    13:43:55: 1368MHz 1.20 44% 18% 12% 0% 13% 0% 72.8°C 0/8
    13:43:56: 1368MHz 1.20 75% 27% 31% 1% 12% 2% 71.2°C 0/8 13:43:56:
     
    which is often unstable and does heat up the cpu (too much).
     
    Try to set the max. Mhz to 1008 in armbian.config -> system -> cpu
    (around 500 Mhz for min.) and governor ondemand.
     
    Maybe then it will be more stable
     
     
  7. Like
    guidol got a reaction from FredrikA in c270 usb cam not recognized   
    My Logitech C270 is found by armbian as UVC-camera:
     
    # lsusb
    Bus 005 Device 003: ID 046d:0825 Logitech, Inc. Webcam C270
     
    [70995.555217] usb 5-1: new high-speed USB device number 3 using ehci-platform
    [70995.931843] usb 5-1: New USB device found, idVendor=046d, idProduct=0825, bcdDevice= 0.12
    [70995.931859] usb 5-1: New USB device strings: Mfr=0, Product=0, SerialNumber=2
    [70995.931867] usb 5-1: SerialNumber: 91E09A20
    [70996.019769] uvcvideo: Found UVC 1.00 device <unnamed> (046d:0825)
    [70996.133336] uvcvideo 5-1:1.0: Entity type for entity Extension 4 was not initialized!
    [70996.133361] uvcvideo 5-1:1.0: Entity type for entity Extension 6 was not initialized!
    [70996.133374] uvcvideo 5-1:1.0: Entity type for entity Extension 7 was not initialized!
    [70996.133388] uvcvideo 5-1:1.0: Entity type for entity Processing 2 was not initialized!
    [70996.133401] uvcvideo 5-1:1.0: Entity type for entity Extension 3 was not initialized!
    [70996.133413] uvcvideo 5-1:1.0: Entity type for entity Camera 1 was not initialized!
    [70996.133914] input: UVC Camera (046d:0825) as /devices/platform/soc/1c1d000.usb/usb5/5-1/5-1:1.0/input/input0
    [70996.134373] usbcore: registered new interface driver uvcvideo
    [70996.134383] USB Video Class driver (1.1.1)
    [70997.474714] usb 5-1: set resolution quirk: cval->res = 384
    [70997.476055] usbcore: registered new interface driver snd-usb-audio
     
    System diagnosis information has been uploaded to http://ix.io/2mBL
     
  8. Like
    guidol reacted to Werner in Switching SUNXI-DEV to 5.6.y   
    Fixes pushed.
  9. Like
    guidol got a reaction from Tido in [Info] Pihole-lighttpd issue with debian buster / bullseye   
    Pi-hole 5.0 is out of the BETA-Phase !   
    and has NO PROBLEMS to be installed on armbian focal   
    ( System diagnosis information has been uploaded to http://ix.io/2mgt )
    Just use:
    sudo apt install php-cgi php-common php php-sqlite3 -y && curl -sSL https://install.pi-hole.net | bash 
     
    Pi-hole v5.0 is here! (2020-05-10 )
    see: https://pi-hole.net/2020/05/10/pi-hole-v5-0-is-here/#page-content
    After a successful beta testing and development period (many thanks to the beta testers!),
    we are pleased to announce the release of 5.0 for general availability!
     
    Important notice (One-way-ticket)
    There are many fundamental changes between Pi-hole 4.x and 5.0 – as such, this is strictly a one way operation.  
    Once you move from 4.x to 5.0, there is no way to go back; you will need to restore from a backup. 
     
    Pi-hole 4.x to 5.0
    To update to this new version from version 4.x,  run pihole -up  
     
    Pi-hole 5.0 BETA to new 5.0 release:
    If you have been running the 5.0 beta release, run pihole checkout master 
    to move from the beta to the master branch.
  10. Like
    guidol got a reaction from linuxjosef in Thermal Throtteling not working in 5.3 and 5.4 kernel on Orange Pi Zero Plus   
    @linuxjosef did you try to set the cpu governor to "conservative"?
  11. Like
    guidol got a reaction from linuxjosef in Thermal Throtteling not working in 5.3 and 5.4 kernel on Orange Pi Zero Plus   
    I have some board where ondemand not really throttle down, but with conservative they ever did throttle down
  12. Like
    guidol got a reaction from Tido in Armbian v20.05 (Kagu) Planning Thread   
    @Igor @RussianNeuroMancer for the chronyd-bug with ubunutu focal you could take a look here
    https://bugs.launchpad.net/ubuntu/+source/chrony/+bug/1878005
    where they found a problem/solution:
    * Chrony can't start on platorms that map gettimeofday to clock_gettime64() * This is due to syscall filtering being correct on some but generic enough to cover all areas. as a temporary solution they wrote:
     
    So we will need to whitelist the clock_gettime64() system call in chronyd’s seccomp filter. I’ll send a patch upstream. Meanwhile, you can disable the seccomp filter by running (as root): # sed -i '/DAEMON_OPTS=/s/"-F -1"/"-F 0"/' /etc/default/chrony # systemctl restart chrony.service BTW: My NanoPi A64 with  armbian focal  kernel 5.6.12 is running
    chronyd v3.5-6ubuntu6 normally:

    System diagnosis information has been uploaded to http://ix.io/2mbU 
  13. Like
    guidol reacted to Igor in Armbian v20.05 (Kagu) Planning Thread   
    Yesterday stress test https://dl.armbian.com/_test-reports/2020-05-15_19.45.41.html was fatal for OPi Lite 2. Board powered off ... probably throttling is not working well (on all H6 ?) and critical temperature was reached.
     
    @guidol Thanks.
  14. Like
    guidol got a reaction from Igor in Armbian v20.05 (Kagu) Planning Thread   
    @Igor @RussianNeuroMancer for the chronyd-bug with ubunutu focal you could take a look here
    https://bugs.launchpad.net/ubuntu/+source/chrony/+bug/1878005
    where they found a problem/solution:
    * Chrony can't start on platorms that map gettimeofday to clock_gettime64() * This is due to syscall filtering being correct on some but generic enough to cover all areas. as a temporary solution they wrote:
     
    So we will need to whitelist the clock_gettime64() system call in chronyd’s seccomp filter. I’ll send a patch upstream. Meanwhile, you can disable the seccomp filter by running (as root): # sed -i '/DAEMON_OPTS=/s/"-F -1"/"-F 0"/' /etc/default/chrony # systemctl restart chrony.service BTW: My NanoPi A64 with  armbian focal  kernel 5.6.12 is running
    chronyd v3.5-6ubuntu6 normally:

    System diagnosis information has been uploaded to http://ix.io/2mbU 
  15. Like
    guidol got a reaction from RussianNeuroMancer in Armbian v20.05 (Kagu) Planning Thread   
    @Igor @RussianNeuroMancer for the chronyd-bug with ubunutu focal you could take a look here
    https://bugs.launchpad.net/ubuntu/+source/chrony/+bug/1878005
    where they found a problem/solution:
    * Chrony can't start on platorms that map gettimeofday to clock_gettime64() * This is due to syscall filtering being correct on some but generic enough to cover all areas. as a temporary solution they wrote:
     
    So we will need to whitelist the clock_gettime64() system call in chronyd’s seccomp filter. I’ll send a patch upstream. Meanwhile, you can disable the seccomp filter by running (as root): # sed -i '/DAEMON_OPTS=/s/"-F -1"/"-F 0"/' /etc/default/chrony # systemctl restart chrony.service BTW: My NanoPi A64 with  armbian focal  kernel 5.6.12 is running
    chronyd v3.5-6ubuntu6 normally:

    System diagnosis information has been uploaded to http://ix.io/2mbU 
  16. Like
    guidol got a reaction from Werner in EXT4-fs zram0 Checksum error   
    You dont have a Raspberry Pi 4 with armbian These are Rockchip64 SBCs  
    because there is no armbian for the Raspberry Pi
  17. Like
    guidol reacted to Igor in OpiOne: /dev/zram0 = /var/log full while apt update   
    Anything is possible when using bleeding edge stuff  
  18. Like
    guidol got a reaction from TonyMac32 in Very Small Platforms - Rockchip 3308 and Allwinner V3s   
    For Retro-reasons:
    I did buy a old Acme Systems FOX G20 (because it was cheap (10EUR) -
    normally I would like own a Acme Systems Arietta G25 because of the formfactor / pinout).
    The Fox has only 400Mhz and 64MB of Ram (Arietta has 128 or 256MB but same CPU-Speed)
    but could boot a wheezy (Sorry no armbian) in 9MB
    I do find it very cool this very low memory useage - while running the SSH/FTP-Server.
     
    Also I like the company name  
    Reminds me at the companys allways could be seen in Cartoon series
    (ACME Co. = https://en.wikipedia.org/wiki/Acme_Corporation )

    The original image on the companys webpage was "infected" with emdebian wheezy-grip which is long EOL
    So I had to multistrap a new rootfs from the pure debian archive wheezy and transplant the modules/firmware to the newer rootfs (kernel is the same).

    Was something nice to learn here while staying home



  19. Like
    guidol got a reaction from Tido in Very Small Platforms - Rockchip 3308 and Allwinner V3s   
    For Retro-reasons:
    I did buy a old Acme Systems FOX G20 (because it was cheap (10EUR) -
    normally I would like own a Acme Systems Arietta G25 because of the formfactor / pinout).
    The Fox has only 400Mhz and 64MB of Ram (Arietta has 128 or 256MB but same CPU-Speed)
    but could boot a wheezy (Sorry no armbian) in 9MB
    I do find it very cool this very low memory useage - while running the SSH/FTP-Server.
     
    Also I like the company name  
    Reminds me at the companys allways could be seen in Cartoon series
    (ACME Co. = https://en.wikipedia.org/wiki/Acme_Corporation )

    The original image on the companys webpage was "infected" with emdebian wheezy-grip which is long EOL
    So I had to multistrap a new rootfs from the pure debian archive wheezy and transplant the modules/firmware to the newer rootfs (kernel is the same).

    Was something nice to learn here while staying home



  20. Like
    guidol reacted to le51 in Need support for the PecanPi DAC   
    I agree with Guidol's point of view.
     
    But, so far
    if you already have a tinkerboard lying on your desk if you know how to use etcher (or any other tool for creating a bootable disk) Then by following instructions given above and these on how to compile armbian you should be able to get your DAC up and running under armbian. And, maybe you will just have to adapt the "compatibility" line in the dts file ...
    I would be glad to help you further, but without having the tinkerboard, and without having this dac it's hard to do more ...
  21. Like
    guidol reacted to linuxjosef in Thermal Throtteling not working in 5.3 and 5.4 kernel on Orange Pi Zero Plus   
    No, I only tried ondemand. If you think this might help, I'll try it.
  22. Like
    guidol got a reaction from Tido in Armbian v20.05 (Kagu) Planning Thread   
    for non-multimedia: got a Pihole on a C2 Armbian Buster with Linux 5.6.8-meson64 without problems
    "sleeping" idle at 33 degree
     
    package bsp-kernel[20.05.0-trunk]  u-boot[20.05.0-trunk]   dtb       [20.05.0-trunk]
    firmware                 [20.05.0-trunk]   config[20.05.0-trunk]   branch [dev]
     
  23. Like
    guidol got a reaction from Igor in Armbian v20.05 (Kagu) Planning Thread   
    for non-multimedia: got a Pihole on a C2 Armbian Buster with Linux 5.6.8-meson64 without problems
    "sleeping" idle at 33 degree
     
    package bsp-kernel[20.05.0-trunk]  u-boot[20.05.0-trunk]   dtb       [20.05.0-trunk]
    firmware                 [20.05.0-trunk]   config[20.05.0-trunk]   branch [dev]
     
  24. Like
    guidol reacted to JORGETECH in Ubuntu 20.04 mini.iso URL documentation update needed   
    Ubuntu changed the location of the mini.iso file for the minimal Ubuntu (Server?) installer in their file servers (since the 20.04 release), it's now located here:
     
    http://archive.ubuntu.com/ubuntu/dists/focal/main/installer-amd64/current/legacy-images/netboot/mini.iso
     
    The docs should be changed since it could be confusing for new users/developers.
  25. Like
    guidol reacted to flippy in Fix dtb of aml s905d phicomm n1 box   
    I improved the dts of Phicomm N1 again.
    The reasons are:
    1. The Ethernet card of N1 is not very compatible with some switches. When the ethernet phy is activated, the flow control sometimes cannot be turned on, so  will get bad results during the speedtest.net . For this reason, I added a dts separately force_thresh_dma_mode, which is equivalent to flow control in software mode. But there are also side effects: tx performance is reduced. In addition, as auxiliary optimization items, set snps, aal; snps, txpbl = <0x8>; snps, rxpbl = <0x4>; their role is to improve the performance of the network card.
    2. The phy reset-delay-us value of N1 is sometimes not enough. When running openwrt, sometimes the ethernet phy cannot be enabled, so the reset-delay-us value is increased.
    Provide two dts files:
    meson-gxl-s905d-phicomm-n1.dts: This is the default dts, used in most occasions, when the flow control can be turned on normally, this is the best choice
    meson-gxl-s905d-phicomm-n1-thresh.dts: This is a dts with the force_thresh_dma_mode option enabled. It is applicable when flow control cannot be turned on. You can use force_thresh_dma_mode to control flow at the cost of a small amount of performance loss.
    meson-gxl-s905d-phicomm-n1.dts meson-gxl-s905d-phicomm-n1-thresh.dts
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines