Jump to content

Werner

Administrators
  • Posts

    4436
  • Joined

  • Last visited

Reputation Activity

  1. Like
    Werner got a reaction from Ximodel in edited   
    You received a 'like', restriction should be gone now.
    Try armbianmonitor -U (take note the U is large), This will output the stuff directly to console/file.
  2. Like
    Werner got a reaction from wolf7250 in Anyone managed to successfully install OMV5 on Helios4?   
    It has been just a few days since release so they probably did not update their wiki yet.
     
    https://www.armbian.com/newsflash/armbian-20-05-kagu/
  3. Like
    Werner reacted to Ximodel in edited   
    As regards bbr, it is not fixed after the upgrade. 
     
    I would like to provide any help if I can, but ironically, when i ran the following command right after upgrade
    sudo armbianmonitor -u System diagnosis information will now be uploaded to Please post the URL in the forum where you've been asked for. "the URL" is disappearing and I don't even know what is going wrong...
     
    And would you like to help me with the reply restriction? 1 reply a day is so harsh that I cannot give immediate information
  4. Like
    Werner reacted to yaa314 in Trouble installing headers/Installing wifi driver   
    Hi, it seemed i had to wait a day to reply
     
    Oddly yes, i get the same result when i run find / -name rtl8188eu*  thus showing it as already installed but the dongle still does not work. I am using another dongle for now that worked out of the box.
    However, i do wish to resolve the headers issue since any program i need to build runs into the same issue. Any ideas?
     
    Thanks in advance
  5. Like
    Werner reacted to KenUnix in Newbie NanoPi R1 Questions   
    Hi,
     
    I have a few questions about the NanoPi R1 system.
     
    1) The (USB > TTL) debug serial port is that 3.3v or 5v?  I need to get the correct adapter.
    2) Hooking up a serial debug cable is there enough room to close the front plate?
    3) Can the system run from eMMc and get software upgraded from the SD-Card?
    4) I could not not find clear procedures for this.  Am not familiar with OpenWRT.
    5) Can the Ethernet port be used to talk to a P.C. running Windows (putty) or would the micro-USB to P.C. be better?
    6) I would eventually use WiFi for remote access and updates.
    7) Can the NanoPi R1 run Apache WEB server?
    8) Can this run Debian or Ubuntu? If so where would the downloads be found?
     
    Looks like a fine product. If it works out I may buy several. I do have experience with Linux (several flavors) and the Beaglebone.
    My history goes back to 1974 and Unix from Bell Labs.
     
     
  6. Like
    Werner reacted to sgjava in Nanopi M1 nightly image not expanding/booting   
    @Igor I hate when that happens. I've been stuck on something for days and weeks sometimes and it's something crazy like that. Happens to every dev.
  7. Like
    Werner reacted to Igor in Nanopi M1 nightly image not expanding/booting   
    It seems that (faster loading) lz4 compression does not play well. Several days several people throw away and on the end its one liner 
    https://github.com/armbian/build/commit/436a5681b517f0fec96175713f583ccf1cb7272d
  8. Like
    Werner got a reaction from rreignier in OV5640 device tree overlay for OrangePi One H3   
    According to https://cateee.net/lkddb/web-lkddb/VIDEO_OV5640.html the OV5640 is in mainline since 4.13 so any earlier implementation must have been custom.
  9. Like
    Werner reacted to jhcarter in Armbian 20.05.1 Focal images could be broken   
    I also experienced this issue on OrangePi boards this week.
     
    I just built images (build host Focal) using the @Werner a2957ca8 commit for:
     
    OrangePi PC
    OrangePi PC+
    Olimex Lime 2
     
    All booted successfully.  All failed to boot with the images currently on the Armbian download page.
     
    Thanks for your work on this.  Let me know if I can help.
  10. Like
    Werner reacted to piter75 in kernel 5.4.43 Rock PI 4B not starting   
    u-boot does not recognise the storage and tries to boot from network.
    I see that you have built yourself an image yesterday but it is probably using some old Armbian build repository revision as it still uses v2017.09 u-boot which is switched to mainline for RockPi 4 in current sources.
     
    Did you also try to use the ready made v20.05.1 images from https://dl.armbian.com/rockpi-4b/archive/? Does it also get stuck with them?
     
    Please use Spoiler next time for boot log ;-)
  11. Like
    Werner reacted to e97 in [Development] RK3399 media script   
    Working on Wayland integration and would like a good starting point.
     
    Please post which boards work and specific test results.
     
    I'll keep the list updated.
     
     Board  Overall   GPU
     accelerated
     Desktop
     WebGL  VPU encode  VPU decode
     4K@60
     10-bit
     HEVC
     OpenGL ES 3.2  OpenCL 1.2  NanoPi TC4  ?        OK      NanoPi M4  ?        Some freezing      RockPro 64  OK  OK
     X11
     OK
    Chromium
     ?  OK  OK  OK  Khadas EDGE  ?        OK      RockPi 4B   Install failed        ?      ROCK960C  ?        OK                                                      
    last updated: 2020-06-01
  12. Like
    Werner reacted to guidol in [Info] compiling/running z80pack imsaisim/altairsim on armbian Desktop   
    If you know the movie "Wargames" then you may know the computer of "David Lightman" a IMSAI 8080
     
    Udo Munk did create the software z80pack (last version from 2017 v1.36 at https://www.autometer.de/unix4fun/z80pack/ )
    which does include
    - IMSAI 8080
    - Altair
    - Cromemco Z1
    and 
    - cpmsim
    Emulation.
     
    Against the text based cpmsim emulation the other features a graphical frontpanel with "blinken lights"
     
    Yesterday I did try to compile/start my favourite IMSAI 8080.
    I did follow the instructions - which I collect and wrote for me - see attached to this message.
     
    But yesterdy I only got limited success (after many "bad" compiles with missing dependencies) in starting the IMSAI 8080 emulation.
    I did get the graphical frontend *yeah* - but after POWERON/RUN the computer I didnt get any terminal-output
     
    After MANY retries I did give up  
    Today I did the same compile-session on a PC with Ubuntu MATE 20.04LTS and it did work in the first try  
     
    At first I got no idea what wasnt working....but then I discovered that - when moving the graphical frontpanel - the terminal-output was written VERY SLOWLY to the terminal-screen *Aha*
     
    Because the garphical frontpanel seem to work perfectly (and did also compile very well) I searched inside the directorys of imsaisim and found in the "conf"-directory the file system.conf
     
    There in system.conf is a line where the FPS-rate of the frontpanel as default is configured to 60 FPS (Frames per second).
    While taking a look at htop the NanoPi A64 (where my armbian buster Desktop does run) the cpu-utilization is near 90%
     
    So my gut instinct did tell me thats to much and the NanoPi has to much work with the frontpanel than writing to the terminal.
     
    I changed the framerate in
    - for the IMSAI 8080: ~/z80pack-1.36/imsaisim/conf/systemconf
    - for the Altair: ~/z80pack-1.36/altairsim/conf/systemconf
    - for the Cromemco Z1: ~/z80pack-1.36/cromemcosim/conf/systemconf
    to
    # front panel framerate fp_fps 10 After that change all 3 emulators with graphical frontend did startup and give output on the terminal
     
    I contacted Udo Munk via email about this topic and he already knew it
    He wrote that he had implemented the FPS option, because some lower-spec systems had problems to achieve the power for producing a framerate of 60 FPS for the frontpanel.
     
     
    Here my write-up / documentation how I did compile /  successfully start the IMSAI 8080 emulation:
    (many thanks to John Kennedy from the FB-Group Altair 8800 for double-checking my instructions!)
    ====================================================================== My normal evironment for compiling source: ====================================================================== apt install gcc libncurses5-dev liblua5.3-dev git make zip unzip -y ====================================================================== Getting z80pack-source: ====================================================================== cd ~ wget https://www.autometer.de/unix4fun/z80pack/ftp/z80pack-1.36.tgz tar -xvf z80pack-1.36.tgz cd ~/z80pack-1.36/ ====================================================================== Dependencies named by z80pack: ====================================================================== libjpeg X11 OpenGL c++ compiler (g++) libpthread ====================================================================== Packages for the z80pack-dpendencies: ------------------------------------- apt install libjpeg-dev x11-common libpthread-stubs0-dev libxmu-dev apt install mesa-common-dev z80asm libglu1-mesa-dev freeglut3-dev ====================================================================== ==> <== ==> I built all packages of z80pack in the following order: <== ==> <== ==> ATTENTION: for some commands you may have to use sudo <== ====================================================================== 1.) FRONTPANEL ====================================================================== cd ~/z80pack-1.36/frontpanel/ make -f Makefile.linux NOTE: Be sure to copy libfrontpanel.so to a shared library path! NOTE: cp ~/z80pack-1.36/frontpanel/libfrontpanel.so /usr/lib make -f Makefile.linux clean ====================================================================== 2.) CPMSIM ====================================================================== cd ~/z80pack-1.36/cpmsim/srcsim/ make -f Makefile.linux make -f Makefile.linux clean ====================================================================== 3.) CPMSIM-TOOLS ====================================================================== if you are user root: mkdir /root/bin if you are user pi: mkdir /home/pi/bin cd ~/z80pack-1.36/cpmsim/srctools make make install NOTE: (does install in /root/bin/) NOTE: Tools installed in /root/bin, make sure it is NOTE: included in the systems search PATH NOTE: export PATH=$PATH:/root/bin NOTE: or NOTE: export PATH=$PATH:/home/pi/bin make clean ====================================================================== 4.) ALTAIRSIM ====================================================================== cd ~/z80pack-1.36/altairsim/srcsim/ make -f Makefile.linux make -f Makefile.linux clean NOTE: change framerate to "fp_fps 10" in NOTE: ~/z80pack-1.36/altairsim/conf/system.conf ====================================================================== 5.) CROMEMCOSIM ====================================================================== cd ~/z80pack-1.36/cromemcosim/srcsim/ make -f Makefile.linux make -f Makefile.linux clean NOTE: change framerate to "fp_fps 10" in NOTE: ~/z80pack-1.36/cromemcosim/conf/system.conf ====================================================================== 6.) IMSAISIM ====================================================================== cd ~/z80pack-1.36/imsaisim/srcsim/ make -f Makefile.linux make -f Makefile.linux clean NOTE: change framerate to "fp_fps 10" in NOTE: ~/z80pack-1.36/imsaisim/conf/system.conf ====================================================================== PREPARE 1st start of imsaisim; ====================================================================== cp ~/z80pack-1.36/frontpanel/libfrontpanel.so /usr/lib cd ~/z80pack-1.36/imsaisim rm conf ln -s conf_2d conf export PATH=$PATH:/root/bin NOTE: maybe add the export-command to your ~/.bashrc ====================================================================== START of IMSAI 8080 CPM v2.2 from the x-terminal on the desktop (needs to be a "x-terminal) for connecting to the X-Server for creating the graphical frontpanel: ====================================================================== ./cpm22 NOTE: maybe root has to give access-rights: NOTE: chmod -R 666 ~/z80pack-1.36/imsaisim/disks NOTE: on the x-terminal root and the to the desktop logged in user can NOTE :start the application and connect to the X-server on a NOTE: SSH-terminal ONLY the to the desktop logged in user can start the NOTE: application and connect to the X-server to give root access to NOTE: the X-server from a SSH-terminal the he to the desktop logged NOTE: in user has to give root access via the xhost command: NOTE: xhost SI:localuser:root ====================================================================== POWER-UP the IMSAI 8080 in the graphical frontpanel ====================================================================== Press "POWER ON " upper part on the first switch on the right side (POWER ON / POWER OFF) Press "RUN" upper part of the third (red) switch (RUN/STOP) ====================================================================== Exit the IMSAI 8080 ====================================================================== Enter "bye" on the CP/M-commandline OR press "POWER OFF " lower part on the first switch on the right side (POWER ON / POWER OFF) OR close the graphical frontpanel with the close button X (Window-Manager-close)  
    Pictures (screenshots are done with Mirage as you can see) of my "success"




  13. Like
    Werner got a reaction from Igor in Armbian 20.05.1 Focal images could be broken   
    I wished you would not have asked because I have no freakin clue...
  14. Like
    Werner reacted to Igor in Armbian v20.05 (Kagu) Planning Thread   
    Release is out: https://www.armbian.com/newsflash/armbian-20-05-kagu/
     
    Now the bug hunting season.
  15. Like
    Werner reacted to martinayotte in Orangepi 3 h6 allwiner chip   
    I will start working on that soon ...
  16. Like
    Werner reacted to 5kft in Orangepi 3 h6 allwiner chip   
    Done and done   https://armbian.atlassian.net/browse/AR-285
     
    Thanks for doing the testing!
     
  17. Like
    Werner reacted to 5kft in Orangepi 3 h6 allwiner chip   
    I just pushed a patch with the test changes for this to my local repo:  https://github.com/5kft/build/commit/b75929e99f67a5d628bc031a1c4e73ab287c7df7.  This patch is against the "sunxi-current" target. 
     
    I can make a PR for this change, but again I don't have an H6 board to test any of this on, and I'd rather not do a PR until we know it works.  Also, I'm not sure what the appropriate critical temperature is for the H6, so in this patch I left it at 105C just like for the H3/H5.
     
    It'd be great if you could give this a try on your OPi1+.  You should be able to change directory to "/sys/class/thermal/thermal_zone0", and see the six new trip points.  To test these changes on my H3s and H5s, I used "armbianmonitor -m" in "screen", with both "stress" and the appropriate "cpuburn" for the architecture (see https://github.com/ssvb/cpuburn-arm).  The reported CPU clock rate should change appropriately when the temperature passes the various trip points.
     
    If this works I'd be happy to submit a PR for this change.
     
  18. Like
    Werner got a reaction from Myy in Patchfolder cleanup helper   
    The output for target files which are affected by multiple patches is now better.

  19. Like
    Werner reacted to JrRockeTer in Nanopi-M4V2 won't booting from eMMC and does not see eMMC: SOLVED eMMC plugs in opposite way than original M4   
    Thanks pieter75, that was my problem!
    I don't know how I missed this, NicoD had this in his video on the M4V2, which I had watched but I missed it.
    Thanks very much !!
  20. Like
    Werner reacted to Igor in Armbian v20.05 (Kagu) Planning Thread   
    In the moment of replying to this mine are also not working yet
     
    Before:
    One 7z archive: image, signature and sha packed in

    Now:
    Three files: image.gz, signature and sha
     
     
     
    https://www.armbian.com/odroid-c4/
    Yes, I also do at least one experiment. This will not change in the future just like that.
     

    Yes. 

    Here is already changed (even I think we don't use this document at the download pages anymor):
    https://github.com/armbian/documentation/blob/master/docs/User-Guide_Getting-Started-Download-Page.md
     
    Not changed in main document:
    https://github.com/armbian/documentation/blob/master/docs/User-Guide_Getting-Started.md
     
    and elsewhere where we had this info. If anywhere.
     
     
  21. Like
    Werner reacted to Myy in Patchfolder cleanup helper   
    Interesting approach.
     
    I'd just like to mention that factorizing is required, if the patches apply to the same file AND the same blocks (functions, DTS, ...).
     
    If you create THAT big patch that add 50 entries to a single DTS file, and the mainline DTS file gets updated with the addition of, like, 3 entries out of the 50, then you won't be able to apply your big patch AND you'll need to rework it.
    Since you won't be able to apply it again, you can either pray that 3-way merging works, or you'll have to do a copy-paste of every missing entry from the patch, back to the DTS file AND regenerate a patch from there.
     
    Now, if you got 5 patches affecting "that same function" or "that same DTS block", then yes, merging is required.
     
    Anyway, this tool should greatly help in reducing the number of patches. Just don't do a blind factorization, it will back-fire very quickly.
  22. Like
    Werner got a reaction from Myy in Patchfolder cleanup helper   
    Ever since patchfolders were created for different branches and different board families it has become more and more a nightmare to maintain these folders and keep them clean.
     
    Instead of taking the approach to clear one or more of these folders by myself, last but not least due to lack of necessary skills, I was thinking maybe I can provide some tools that make such tasks a little easier for somebody else.
    Last but not least was (and still is) this a perfect opportunity to pratice with my quite new Python skills.
     
    https://github.com/EvilOlaf/refactorpatches
     
    What this script basically does is break down all patches in a certain folder and check which files are targeted by each individual diff (if you choose to split them up) and sort the output by the target file.
    This way it should be an easy thing to merge patches that affect the same file and therefore it is no longer necessary to take care about the order to apply them.
     
    Requirements from apt: patchutils, python3
    Requirements from Pypi: none but just make sure the prettytable.py is in the same folder as main refactor.py.
     
    I have tested this with random patch folders for kernel patches and for what it is expected to do at the current state it seems to just work as it should.
    There is still a ton of room for improvements.
     
    Let me know what do you think or if it is useful at all. Even if it is not I had fun coding and using Python
     

  23. Like
    Werner reacted to 5kft in Armbian v20.05 (Kagu) Planning Thread   
    Fixed!  I marked this as Done (both sunxi-current and sunxi-dev, tested on both for H5 and H3) 
  24. Like
    Werner 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":
     
     
  25. Like
    Werner reacted to guidol 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)
     
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines