Jump to content

raschid

Members
  • Posts

    116
  • Joined

  • Last visited

Posts posted by raschid

  1. 2 hours ago, thepro said:

    ... with attached SATA disk...

     

    I have the same issue on a BananaPi M1 with an attached SATA disk.

    It is running SAMBA, a media server, an iperf server, it monitors and log weather data from an attached weather station and does some home automation.

     

    "Freeze" means the system is becoming unresponsive to ssh, cron etc. while still responding to ping and the the reset button. A cpu-load triggered system LED remains solid on.

     

    The system ran completely stable on Bananian for nearly three years until I switched to armbian in January.

    Initially the freezes occured quite infrequently with the systmem running ok for weeks.
    I installed a daemon to monitor system load and dump "ps aux" is load exceeds 2 - but that never happens:  The system becomes unresponsive before the daemon can kick in.

     

    After upgrading last Saturday it froze after just 22 hours. I am travelling right now - it's quite unsettling to think of the little bugger running at max overload for the next 5 days.

     

    I will downgrade as soon as I am back as @theprosuggests.

     

    TL;DR: Current armbians builds on A20 platforms seem to be unstable and have been for some time. Upgrading the current builds seems to make things worse.

  2. So in armbian-config / Systen settings / Install "Install to SATA, eMMC, NAND or USB" you hit OK and did not get the option:

    "1   Boot from eMMC - system on eMMC"?

     

    Can you post the output of lsblk to check that the OS "sees" the eMMC? That should look something like this:

    test@sunvell:~$ lsblk
    NAME         MAJ:MIN RM  SIZE RO TYPE MOUNTPOINT
    mmcblk0      179:0    0 29.7G  0 disk
    └─mmcblk0p1  179:1    0 29.4G  0 part /
    mmcblk1      179:8    0  7.3G  0 disk
    └─mmcblk1p1  179:9    0  7.2G  0 part
    mmcblk1boot0 179:16   0    4M  1 disk
    mmcblk1boot1 179:24   0    4M  1 disk

     

  3. Did you build your kernel with the armbian build system? Like this:

    # git clone --depth 1 https://github.com/armbian/build
    # cd build
    # ./compile.sh BOARD=sunvell-r69

    Use the <NEXT> kernel. There have been changes recently to DRAM timing which have increased stability.

    To transfer the OS from SD-Card to eMMC use $sudo armbian-config. There is an option in the "Systems"-menu to transfer the OS to the internal eMMC.

  4. There's a typo in my code above - it should say &usb_otg, not &usb_org (thick fingers, sorry!):

    &usb_otg {
        dr_mode = "host";
        status = "okay";
    };

    Did you catch that? If not, maybe give at another go with the above modification.

    This tag corresponds to the following part of the friendlyelec "all-in-one" dts:

    		usb@01c19000 {
    			compatible = "allwinner,sun8i-h3-musb";
    			reg = <0x1c19000 0x400>;
    			clocks = <0x4 0x20>;
    			resets = <0x4 0x11>;
    			interrupts = <0x0 0x47 0x4>;
    			interrupt-names = "mc";
    			phys = <0x1c 0x0>;
    			phy-names = "usb";
    			extcon = <0x1c 0x0>;
    			status = "okay";
    			dr_mode = "otg";
    		};

    Based on that I would try exchanging "host" for "otg" in the dr_mode tag.

     

  5. 26 minutes ago, guidol said:

    now all the others cards (8GB Ultra and 32GB Exteme) DO boot again in the first try

    Good news but still odd: the legacy image's FEX file indicates a DRAM clock of 576MHz. Never mind, I created a pull request with an updated u-boot patch which should solve the issue for other users as well.

    Thx for raising the issue and the extensive testing :)

     

×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines