apollon77

  • Content Count

    110
  • Joined

  • Last visited

Reputation Activity

  1. Like
    apollon77 reacted to Werner in usbip not working with ZeroPi (Buster Image) - Device disconnect as soon as I try to bind   
    Patch has been upstreamed and is available in 5.8.6. No changes for us but to remove the previously added patch.
  2. Like
    apollon77 got a reaction from Igor in usbip not working with ZeroPi (Buster Image) - Device disconnect as soon as I try to bind   
    Guys, thank you very much, usbip works again!
     
    You're awesome!
  3. Like
    apollon77 reacted to Werner in usbip not working with ZeroPi (Buster Image) - Device disconnect as soon as I try to bind   
    My bad. I did not even check out the link due to lack of time.
    Anyway I'll take care for it.
     
    https://github.com/armbian/build/pull/2178
    Will merge if checks are successful.
     
    If somebody requesting for help and also helping by him/herself to solve this issue by doing own research we are WAY more motivated to get to a solution . Unfortunately this is not very often the case...
  4. Like
    apollon77 got a reaction from Werner in usbip not working with ZeroPi (Buster Image) - Device disconnect as soon as I try to bind   
    So true ;-)
     
    I'm invested myself very deep in a Smart Home project (ioBroker) as one of the Core Developers (mainly Node.js based) ... so I know exactly what you mean ;-)
  5. Like
    apollon77 reacted to Werner in usbip not working with ZeroPi (Buster Image) - Device disconnect as soon as I try to bind   
    Nope.
     
    But 5.8.5 should not be a big deal. sunxi-current is already on this particular version and it is planned to bump the current Armbian release to 20.08.1 this weekend. If you are impatient however you can grab dtb, header and kernel image for sunxi from my server (https://werner.armbian.de/_2020/Aug31/) or via nightly builds (beta.armbian.com) and simply install those packages by using dpkg -i.
  6. Like
    apollon77 reacted to Igor in usbip not working with ZeroPi (Buster Image) - Device disconnect as soon as I try to bind   
    Add a patch to our build system and you will get support in most recent kernel ... Releasing bug fix update this week. Better than using old unsupported builds.

    Wrote on mobile


  7. Like
    apollon77 got a reaction from tpm8 in Cubietruck freeze after 1-3 days with 5.23 Xenial (uboot problem?)   
    I used some time the last days to do some tests. Here first results with 5.25 official u-boot from armbian:
     
    cubietruck1   -> 2 limatester-runs without freeze (but freezed before and was more stable in operation with u-boot 5.25 then with 5.20) cubietruck2 -> 2 limatester-runs runs without crash (but freezed before and was much more stable in operation with u-boot 5.20 then with 5.24/5!) cubietruck3 -> freeze after 10 mins limatester, multiple tries see above (most start of the "Checkerboard" tests) cubietruck4 -> reproducable freeze at limatester-start at "got 100MB, trying mlock ...", multiple tries cubietruck5 -> 2 limatester-runs without freeze Now I focus my tests on "Cubietruck3" for the beginning and tried the tpm8-u-boot-384 there. Result: Freeze in the second limatester loop ... so Interestingly later then the 10 mins before, but freezed still fast.
     
    Now I test the tpm8-u-boot-432 on that "Cubietruck3" and is currently in limatester-loop #4 (also with 1000MB instead of 100MB) and still running. I can test the whole day. I moved the InfluxDB to a Intel-Nuc (also because of 64bit).
     
    Further plan is:
    - let it run with 432-u-boot for a while
    - try 432-u-boot on "Cubietruck4" and see if limatester starts at least :-)
    - test 432-u-boot also on "Cubietruck5" to see if this works too
     
    Ingo F
  8. Like
    apollon77 got a reaction from tpm8 in Cubietruck freeze after 1-3 days with 5.23 Xenial (uboot problem?)   
    @tpm8: So uboot written:
    root@cubietruck3:~# dd if=u-boot-sunxi-with-spl_20161122.bin of=/dev/mmcblk0 bs=1024 seek=8 530+1 records in 530+1 records out 543026 bytes (543 kB, 530 KiB) copied, 0.124085 s, 4.4 MB/s rebootet ... time counts now :-)
  9. Like
    apollon77 reacted to zador.blood.stained in Cubietruck freeze after 1-3 days with 5.23 Xenial (uboot problem?)   
    The only difference in the defconfig is slightly lower DRAM frequency in Armbian compared to mainline:
    https://github.com/igorpecovnik/lib/blob/master/patch/u-boot/u-boot-sunxi/a10-a20-lower-dram-clk.patch#L89-L99
  10. Like
    apollon77 reacted to tpm8 in Cubietruck freeze after 1-3 days with 5.23 Xenial (uboot problem?)   
    Ok. Mine has SKhynix SKhynix H5TQ4G63AFR-PBC DRAM chips. The board says CUBIETRUCK V1.0-06.06 printed on it.
     
    Link to photo of the board: http://workupload.com/file/hGEwhZh
     
    I also managed to compile latest u-boot. As soon as the other unit arrives I'm going make further tests.
  11. Like
    apollon77 reacted to Igor in Cubietruck freeze after 1-3 days with 5.23 Xenial (uboot problem?)   
    Still running, 
  12. Like
    apollon77 reacted to tpm8 in Cubietruck freeze after 1-3 days with 5.23 Xenial (uboot problem?)   
    ok - here is my feedback, unfortunately uboot 5.24 does not fix it for me.
     
    Cubietruck, Jessie Legacy kernel (3.4.112-sun7i) Image 5.20 with all updates. Stability tests witch cpufreq-ljt-stress-test and Lima Memtester.
     
    uboot 5.23: Kernel crashes after few seconds during load, Error on console:
    Unable to handlE kernel NULL pointer dereference at virtual address 000000 uboot 5.24 beta (linux-u-boot-cubietruck_5.24.161109_armhf.deb): Kernel crashes after few seconds during load, Error on console:
    Unable to handle kernel paging request at virtual address xxxxxx Downgrading uboot to 5.17 or 5.20 - everything is rock solid. No problems during complete runs of cpufreq-ljt-stress-test and Lima Memtester.
     
    Tobias
  13. Like