Jump to content

km1kze

Members
  • Posts

    23
  • Joined

  • Last visited

Posts posted by km1kze

  1. 9 hours ago, 5kft said:

    Hi @km1kze, yes - that's correct.  I made the overlay change as with the newer kernel and board support there are a number of boards that provide implicit support for 1.3v regulators, and as such this overlay explicitly should be used with 1.3v regulators.  Similarly, I could make a 1.4v overclock overlay (e.g., for the NEO Core2) that would support 1.4GHz - I just haven't gotten around to doing this yet.  In any case, I'm glad to hear that this is working for you now!

    @5kft Thank you for making this possible!

  2. Ok I decided to give a second try with the new  armbian - I re-soldered a mosfet in that place and is not working, I've got this when checking cpufreq-info (I added the overlay line in armbianEnv.txt and the cpufrequtils max frequency):

     

      cpufreq stats: 120 MHz:0.00%, 240 MHz:44.43%, 480 MHz:0.63%, 648 MHz:0.98%, 816 MHz:0.92%, 960 MHz:0.43%, 1.01 GHz:52.60%  (94)

     

    I have 1.1v on 1V2C pad, with a fresh image  Armbian_5.75_Orangepizeroplus2-h5_Ubuntu_bionic_next_4.19.20.img

    First I thought it may be a solder error, or a damaged component . But I tried with an old image  Armbian_5.34.171121_Orangepizeroplus2-h5_Ubuntu_xenial_next_4.13.14.img and I've got 1.3v on 1V2C pad, so I guess is a software problem?

     

    LATER EDIT:

    ok just found out that the overlay name was changed for some reason from cpu-clock-1.3GHz in cpu-clock-1.3GHz-1.3v - now it seems to work (hope will help future modders)

  3. On 9/6/2018 at 11:54 AM, gyrex said:

    Edit: Sorry, had a massive brain fart and forgot to put the microSD card back in. It's working now :)

     

    I'm hoping someone might be able to help me... I bought BSN20's from aliexpress here https://www.aliexpress.com/item/10pcs-lot-BSN20-M8W-SOT-23-new-original/32705392701.html?spm=a2g0s.9042311.0.0.16904c4dCoV0Uu

     

    And soldered one to my Orange Pi Zero Plus board but now it doesn't power up. It was powering up OK before soldering the voltage regulator. Has anyone soldered one to an Orange Pi Zero Plus and did it work ok?

     

    I soldered one of those on my board and it worked, but had some problems with 5v pins not giving enough voltage - but it boot up with no problems (I did the patching of armbian like it was presented in the first posts, by compiling it, etc.)

    After I removed the mosfet the 5v pins were working as they should.

  4. 8 minutes ago, teenytinycactus said:

    Can anyone please confirm the markings on the transistors they received from aliexpress? I bought from a link in this thread and it has "J1 6" on it. Is that.... suitable? I'll probably hold off soldering it.

     

    Don't remember what was written on them, but if you bought from my link, they're good 

     

    You can also see a J1 marking on the original mosfet from the orange pi zero H2+

    https://www.toysforscience.com/wp-content/uploads/2017/08/1482138186-1.jpg

  5. On 6/11/2018 at 11:13 AM, guidol said:

    try to put a 

    sleep 5 

    before the first command. sometimes it works if the system waits some seconds to complete other services.

    If it wont work try 

    sleep 10

    an then you could shorten the time at every boot until it works. 

     

    In very bad circumstances add a sleep between the conmmands..... some SBCs need more time than others....but a H5 should be fast enough :)

     

    Unfortunately is not working... I think is something else here

    If I simply run the command like this

     

    sudo echo "255" > /sys/class/leds/orangepi\:red\:status/brightness

     in terminal is not working, not even if I enter as root with

    sudo su

    sudo  echo "255" > /sys/class/leds/orangepi\:red\:status/brightness

    then it says:

    bash: /sys/class/leds/orangepi:red:status/brightness: Permission denied

     

    it only works with

    sudo -s

    sudo  echo "255" > /sys/class/leds/orangepi\:red\:status/brightness

     

    * maybe is there a way to directly put these settings in the .dts file? will something like default-brightness-level work?

  6. well it seems that my h5 orange pi was not dead (yet :D)

    I connected an usb ethernet and installed the image @guidol suggested and updated with the hdmi off/leds on patch

    my board is looking like an Xmas tree now and fully functional! thank you guys!

     

    1. the led behavior is not saved after reboot, how can I achieve that? I tried putting in /etc/rc.local this but not working:

       echo "255" > /sys/class/leds/orangepi\:red\:status/brightness

       echo "heartbeat" > /sys/class/leds/orangepi\:red\:status/trigger

       echo "mmc0" > /sys/class/leds/orangepi\:green\:pwr/trigger

     

    2. this armbian version has the cpu capped to 816Mhz? I remember that without the mosfet I could reach 1152Mhz on an armbian build. Is because this version (5.44) or there is other explanation?

  7. 55 minutes ago, 5kft said:

    Indeed, this is strange...   Perhaps it's just not worth it to do the mod - it's still not clear why Xunlong doesn't stuff this part.  Perhaps this power circuit is too unreliable with their H5-based boards?

     

     

    Yeah, I can confirm that my eMMC is not loading now and HDMI is dead (the mosfet is removed ).. Tried to load an image that I knew it worked and nothing... didn't check with UART yet to see if is alive, but have 1.09v-1.1v on 1v2c and correct voltages on pins.  There is a 1_5V pad somewhere near GPIOs, but it had a lower voltage - 1.36 v, do you have a similar value on that?

  8. I used an original Samsung Galaxy Note 2014 tablet adapter of 2.5A (measured it and it recharge the tablet at more than 12Wh and it surely has 2.5A)- also some other Chinese ones (2A at least), still the same thing

    I took the mosfet out from the board and now the 5v are there. This is pretty weird, maybe is a fault in the board? While the mosfet was there, I also had at 1V2C around 1.3v, but maybe there are other pads I could check if is fully working?

  9. On 6/1/2018 at 3:00 PM, reverend_t said:

    Does anyone have a more recent purchase of this board? Have Xunlong started inluding the mosfet?

    Mine was bought in March, I contacted the seller in April and said is a new "update" to ensure board functionality - no more explanations.

    In the meantime I just observed that this mosfet addition has a bigger drawback than the HDMI deactivation .. I have on all 5v pins something like 4.2v ... Basically the only way to communicate with the board will be through UART - to setup WIFI for headless .. A keyboard or any other USB device will not be functional. Saying that, and seeing how Shenzhen Xunlong Software is raising the prices to these boards (+25% in the last couple of months) it will be more practical to buy something from the NanoPi series...

  10. The mosfets arrived and finaly managed to make a test, and it works! Thank you again 5kft !

     

    For me it worked with this Armbian version: Armbian_5.34.171121_Orangepizeroplus2-h5_Ubuntu_xenial_next_4.13.14.img, then compiled  with the build compilation tips shown by 5kft  in a previous post. It seems it runs at 1296 Mhz from the start, I didn't need to update cpufrequtils.

    Surprisingly, it stays in idle at a lower temperature than before. Idle now is 38 celsius -although with a temperature meter is around 45. Before it was 55 - real it was with 2-3 degrees more (ambient temperature around 25).

     

    20:33:36: 1296MHz  0.02   0%   0%   0%   0%   0%   0% 38.2°C  0/11

     

    pi@orangepizeroplus2:~$ cpufreq-info -c 1
    cpufrequtils 008: cpufreq-info (C) Dominik Brodowski 2004-2009
    Report errors and bugs to cpufreq@vger.kernel.org, please.
    analyzing CPU 1:
      driver: cpufreq-dt
      CPUs which run at the same hardware frequency: 0 1 2 3
      CPUs which need to have their frequency coordinated by software: 0 1 2 3
      maximum transition latency: 6.24 ms.
      hardware limits: 240 MHz - 1.30 GHz
      available frequency steps: 240 MHz, 408 MHz, 648 MHz, 816 MHz, 912 MHz, 960 MHz, 1.01 GHz, 1.06 GHz, 1.10 GHz, 1.15 GHz, 1.25 GHz, 1.30 GHz
      available cpufreq governors: conservative, userspace, powersave, ondemand, performance, schedutil
      current policy: frequency should be within 1.30 GHz and 1.30 GHz.
                      The governor "ondemand" may decide which speed to use
                      within this range.
      current CPU frequency is 1.30 GHz.
      cpufreq stats: 240 MHz:0.04%, 408 MHz:1.33%, 648 MHz:0.14%, 816 MHz:0.12%, 912 MHz:0.08%, 960 MHz:0.08%, 1.01 GHz:0.07%, 1.06 GHz:0.04%, 1.10 GHz:0.05%, 1.15 GHz:0.04%, 1.25 GHz:0.04%, 1.30 GHz:97.98%  (254)
    pi@orangepizeroplus2:~$ sudo sysbench --test=cpu --cpu-max-prime=20000 --num-threads=4 run && cat /sys/devices/virtual/thermal/thermal_zone0/temp
    sysbench 0.4.12:  multi-threaded system evaluation benchmark
    
    Running the test with following options:
    Number of threads: 4
    
    Doing CPU performance benchmark
    
    Threads started!
    Done.
    
    Maximum prime number checked in CPU test: 20000
    
    
    Test execution summary:
        total time:                          7.0661s
        total number of events:              10000
        total time taken by event execution: 28.2527
        per-request statistics:
             min:                                  2.82ms
             avg:                                  2.83ms
             max:                                  5.55ms
             approx.  95 percentile:               2.83ms
    
    Threads fairness:
        events (avg/stddev):           2500.0000/1.87
        execution time (avg/stddev):   7.0632/0.00
    
    56450

     

  11. Hi,

    I'm a bit of a newb, but I'm in search of a OS to make my board functional (Orange Pi Plus2 H5)

    I installed Armbian_5.42_Orangepizeroplus2-h5_Debian_stretch_dev_4.16.0.7z

    The problem with this version is that the CPU and temperature shows nothing in armbianmonitor , and the UART, I2C, etc options from armbian-config are missing. Wifi is working, desktop from armbian-config didn't install - but I could install xfce manually and seems to work

    Also the CPU seems capped to a low frequency (probably the classic 912Mhz), having 11s in sysbench compared to 8s in the previous Armbian version (which was clocked by default to 1152Mhz)

     

    However, is the first linux distro/version that successfully installed on eMMC

  12. I manage to track where these commands come from...

    I searched for a part of the command string with this (run from /etc directory):

    sudo grep -R  "run-parts --report /etc/cron.daily"

     

    And found out that it was inside a crontab file (called the system wide crontab - more info here )

     

    After some research I managed to stop the annoying emails by writing

    > /dev/null

    after every command found in that crontab, and then restart the cron

    sudo service cron reload

     

     

  13. Hello all,

     

    I started to receive unsolicited e-mails from my Nanopi NEO and couldn't figure it out what are triggering them. I checked my crontab and there is nothing there.

    Please if someone knows to clarify this, I would be very grateful, I'm relatively new to linux.

     

    My root crontab:

    00 02 1 * * sh /home/pi/updategeoip.sh
    0 6 * * * /sbin/shutdown -r now
    */5 * * * * python /home/pi/tempalert.py 2>&1

     

    My user crontab:

    0,15,30,45 * * * * sh /home/pi/sendip.sh &>/dev/null

     

    The e-mail is sent everyday at 06:25 +0000 and seems to be activated by this command:

    test -x /usr/sbin/anacron || ( cd / && run-parts --report /etc/cron.daily )

     

    The content of the (failed) e-mails:
     

    The response was:
    
    DNS Error: 11584654 DNS type 'mx' lookup of localhost responded with code NXDOMAIN Domain name not found: localhost
    
    Final-Recipient: rfc822; postmaster@localhost
    Action: failed
    Status: 4.0.0
    Diagnostic-Code: smtp; DNS Error: 11584654 DNS type 'mx' lookup of localhost responded with code NXDOMAIN
     Domain name not found: localhost
    Last-Attempt-Date: Mon, 25 Sep 2017 23:25:11 -0700 (PDT)
    
    
    ---------- Forwarded message ----------
    From: root <****private e-mail address*****>
    To: root
    Cc:
    Bcc:
    Date: Tue, 26 Sep 2017 06:25:07 +0000
    Subject: Cron <root@nanopineo> test -x /usr/sbin/anacron || ( cd / && run-parts --report /etc/cron.daily )
    /etc/cron.daily/log2ram:
    sending incremental file list
    ./
    auth.log
    kern.log
    lastlog
    mail.log
    syslog
    syslog.1
    syslog.2.gz
    syslog.3.gz
    syslog.4.gz
    wtmp
    lightdm/
    lightdm/lightdm.log
    lightdm/lightdm.log.1.gz
    lightdm/lightdm.log.2.gz
    unattended-upgrades/unattended-upgrades.log
    
    sent 20,636,219 bytes  received 307 bytes  13,757,684.00 bytes/sec
    total size is 25,864,247  speedup is 1.25

     

  14. Hello people,

     

    I'm using Armbian 5.30 - kernel 3.4.113 on a Nanopi NEO. and I'm relatively new to this stuff, so please bear with me.

    I successfully managed to install an LCD screen on SPI (ILI9341) using this command:

    sudo modprobe fbtft_device custom name=fb_ili9341 gpios=reset:1,dc:201,led:6 speed=16000000 rotate=90 bgr=1

     

    So far so good, but the resolution of the screen is too little and can't load anything - for example Dosbox. I would want to replicate the trick that already exists on Raspberry/Raspbian, and that is to framebuffer a higher res screen (at least 640x480) on the tiny LCD's resolution of 320x240.

     

    This is the program that is used for Raspberry, for reference:

    https://github.com/tasanakorn/rpi-fbcp

     

    Can someone please tell me if is possible?

    Thank you

     

     

×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines