Jump to content

hrip6

Members
  • Posts

    15
  • Joined

  • Last visited

Posts posted by hrip6

  1. 1 minute ago, zador.blood.stained said:

    /boot/script.bin is a symlink by default to one of the files in /boot/bin. You can delete the symlink, copy the required file from /boot/bin/ to /boot/script.bin and edit it to your needs, this way it won't be touched by upgrades.

    Wonderful, by this way I can upgrade without my changes, that's great. Thanks for the tips.

  2. 14 minutes ago, nihilista said:

    Now with 5.31 i upgraded all my 3 devices (bananapro,orange pi pro, nanopi), all running fine...so big thx to devs.:thumbup:

    Yeah, only one small thing is if we have changed in kernel and script.bin, then we have to do it again. It is a must-have after upgrading :D. Because I do some changes in script.bin to running digital sensor and control some GPIOs, so I have to re-compile it after upgrade success.

     

    Edit - How to keep script.bin not be touched by upgrades [thanks to zador.blood.stained]: 

    Quote

    /boot/script.bin is a symlink by default to one of the files in /boot/bin. You can delete the symlink, copy the required file from /boot/bin/ to /boot/script.bin and edit it to your needs, this way it won't be touched by upgrades.

     

  3. 13 minutes ago, hrip6 said:

    The answer is [will be updated in 10 minutes]

    | __ )  __ _ _ __   __ _ _ __   __ _  |  _ \(_)
    |  _ \ / _` | '_ \ / _` | '_ \ / _` | | |_) | |
    | |_) | (_| | | | | (_| | | | | (_| | |  __/| |
    |____/ \__,_|_| |_|\__,_|_| |_|\__,_| |_|   |_|
    
    Welcome to ARMBIAN 5.31 stable Debian GNU/Linux 8 (jessie) 3.4.113-sun7i
    System load:   0.62 0.50 0.23   Up time:       3 min
    Memory usage:  12 % of 984MB

    Up and running within about 7 minutes.  On-screen when process is running: http://sprunge.us/ELKE.

    Before and after, all function working without problem.

    14 minutes ago, Aux said:

    A good idea, but for serial debug session has no tools

    Have a look here: http://wiki.lemaker.org/LeMaker_Guitar:Debug_COM

  4. 2 hours ago, Igor said:

    I just test the upgrade once again. Starting with this image: https://dl.armbian.com/bananapi/archive/Armbian_5.25_Bananapi_Debian_jessie_next_4.9.7.7z

     

    apt update

    apt upgrade

     

    Zero problems.

     

    1 hour ago, FrankM said:

    My Problems are solved.

     

    1 hour ago, tkaiser said:

    after 5.31 upgrade: http://sprunge.us/PfGa (Armbian 5.31 with kernel 4.11.5 and obvisouly network connectivity)

     

    @Aux @Wolf2000 : How many more need to test before you accept that the problem is on your end, not on the build/upgrade? This is the first time I see Igor and tkaiser tried that hard to help you out. But without your attempts to test the hardware, then I think no one can help you but yourself. However, I think if you already have your setup running for a year without problem, and you do not want to change the hardware, then why upgrade when the old ones can serve your purpose?

    At first, I don't want to upgrade because mine is working fine. And now it's on upgrading process, just because I want to see will I get into the same problem as yours. The answer is [will be updated in 10 minutes].

     

    Regards.

  5. On 6/5/2017 at 6:02 PM, Eugo said:

    But after apt-get upgrade / dist-upgrade and installing some software (apache2, zsh, logwatch, fail2ban, ...) it brings me back to the same problem during the boot process

     

    15 hours ago, Eugo said:

    Just took the image file Armbian_5.25_Bananapipro_Ubuntu_xenial_next_4.9.7 from https://dl.armbian.com/bananapipro/

    I think in your case, I will re-flash with a fresh image, then do every step with a reboot. apt-get dist-upgrade -> reboot, apt-get upgrade -> reboot, install one by one to find out exactly what cause the problem. If Igor has try to replicate your problem but without success, then it likely to be your hardware or the way you install and set up the system (any tweak can cause trouble).

  6. 11 minutes ago, Igor said:

    I am glad you managed to fix the issue.

    Thanks Igor, that's all I need.

     

    I apologize for any negative feelings I brought to you, and for those who viewed this thread.

     

    I was so stress as the children here, in a poor community hospital, they need my system to be satisfied. So I'm a little bit annoying to you guys. You was busy, I understand, it was a coincidence that should not happened. Good luck to you and wish you always happy for everything you sharing now and future.

     

    By the way, if you can, please delete all the post that does not relevant to the OP. I'll do mine first.

  7. First of all, thanks for your answer. At least I'm not talking to myself. Before came here to ask a question, I have tried all of the post in the Internet, include every guides not in English, but could not see the problem. Only until yesterday, when that post came up, it gives me the answer.

     

    -- This unnecessary conversation has been removed by author --

     

    Anyways, thanks a lot for being here with me. Appreciate your works on Armbian. Have a good day.

  8. Finally I have found what cause the problem, it's just a small thing that I find in the other new blog (maybe the blog just published lol). In their Troubleshooting section, I found exactly same in my case: http://aplaceto.win/2017/06/06/ds18b20-temperature-sensor-with-banana-pi-m1-armbian-5-25-_3-4-113/

     

    I have that tweak from here a year ago, still have it in my server but have no apparently effect, so I decided to delete it, and the system is back to normal.

     

    -- This unnecessary conversation has been removed by author --

     

    Anyway, thanks to this friendly forum...

  9. On 02.05.2017 at 0:05 PM, nkahl said:

    now comes a tutorial for how to set up a DS18B20 temperature sensor on a Banana Pi

     

    Hi, I am trying to get the DS18b20 working on Banana Pi running ARMBian 3.4.113 but it was not successful.

     

    Would you give me some time on that project please, thanks in advance: 

     

     

  10. Hi everyones,

     

    Last week, I tried to read the value from DS18b20 temperature sensor to log it in the monitor system I already have. But I could not get its value.

    I connect the DS18b20 with 4.7k pull up resistor to the pin 16th on the board, which is I guess is IO-4 [PH20] pin.

     

    What I have tried?

    - I have tried this: http://www.linuxx.eu/2014/09/banana-pi-temperature-sensor-ds18b20.html

           Step I did: Convert the /boot/script.bin to bananapi.fex, then add [w1_para] gpio = 4 to the end of file, save and convert it back to /boot/script.bin. Reboot.

           Problem: No w1 dir found in the /sys/bus (expecting it will show w1 dir but it's not).  Use modprobe w1-gpio -> ERROR: no such device.

    - I have found the method with .dtb file, however I could not find any .dtb file in /boot. So I fail on very beginning step.

     

    If anyone happen to have this digital sensor work on 3.4.113-sun7i,  please help me on this project. I appreciate any suggestions. Thank you so much.

     

    This is the Linux version I'm working (can be found at https://dl.armbian.com/bananapi/archive/Armbian_5.25_Bananapi_Debian_jessie_default_3.4.113.7z):

    cat /proc/version
    Linux version 3.4.113-sun7i (root@devel) (gcc version 5.4.0 20160609 (Ubuntu/Linaro 5.4.0-6ubuntu1~16.04.4) ) #17 SMP PREEMPT Thu Feb 23 19:43:34 CET 2017

     

  11. 10 hours ago, nemonein said:

    @hrip6 Thanks, But that's not the point that I want to talk about.

    Yeah, just try to help ;)

    10 hours ago, tkaiser said:

    Armbian reserves 5% on 4GB cards, 2% on 8GB cards and 1% above. This is not related to swap or 'Reserved block count' but due to partitioning.

    Thanks for again let me learning from you. I thought this about reserve block which is have on almost Linux kernel, but is this an Armbian function only?

  12. I have pretty the same:

     

    Disk /dev/mmcblk0: 14.9 GiB, 16018046976 bytes, 31285248 sectors
    Units: sectors of 1 * 512 = 512 bytes
    Sector size (logical/physical): 512 bytes / 512 bytes
    I/O size (minimum/optimal): 512 bytes / 512 bytes
    Disklabel type: dos
    Disk identifier: 0xe2f8e3ae
    
    Device         Boot Start      End  Sectors  Size Id Type
    /dev/mmcblk0p1       2048 30659519 30657472 14.6G 83 Linux
    
    root@bananapi:~# df -h /dev/mmcblk0p1
    Filesystem      Size  Used Avail Use% Mounted on
    /dev/mmcblk0p1   15G  1.4G   13G  10% /

    Disk has 14.9 GiB. Have only 1 partition with the size of 14.6 GiB. The gap of 0.3 GiB has gone in reserved space maybe, but AFAIK this should be 5%. I'm not sure about this. Try this to set 5% to 0% (be careful if you are going to do this on system partition, it might have negative affect):

    sudo tune2fs -m 0 /dev/mmcblk0p1

    This sets the reserved blocks to 0%. You can verify that this actually worked with:

    sudo tune2fs -l /dev/mmcblk0p1 | grep 'Reserved block count'
    
      Reserved block count:     41413
        ### This is in my case (I didn't run the command to set 5% to 0% before as it's my system partition)

    Disclaimer: I would not say this will work, but you can get your own experience at least xD

  13. This is my result:

     

    Spoiler
    
     http://sprunge.us/YgJe
                                                                  random    random
                  kB  reclen    write  rewrite    read    reread    read     write
              102400       4     1340     1648     5425     5423     5379      549
              102400      16     4861     4007    11461    11461    11418      992
              102400     512     9104     8312    17827    17781    17806     1380
              102400    1024     7285     7567    18370    18439    18413     2876
              102400   16384     7895     8395    19257    19292    19287     7401

     

    Card info:

    Spoiler
    
    ### mmc0:aaaa info:
    
                     cid: 03534453553136478020cb458600d865 
                     csd: 400e00325b59000076b27f800a404013 
                     scr: 0235800100000000 
                    date: 08/2013 
                    name: SU16G 
                    type: SD 
    preferred_erase_size: 4194304 
                   fwrev: 0x0 
                   hwrev: 0x8 
                   oemid: 0x5344 
                  manfid: 0x000003 
                  serial: 0x20cb4586 
                  uevent: DRIVER=mmcblk MMC_TYPE=SD MMC_NAME=SU16G MODALIAS=mmc:block 
              erase_size: 512

     

    armbianmonitor -u: http://sprunge.us/hUhE

     

    Too slow Micro SD Card you think :(? I'm newbie and playing with Banana Pi for a year ago but I still have some problem with it :((

×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines