Jump to content

going

Members
  • Posts

    492
  • Joined

  • Last visited

Reputation Activity

  1. Like
    going reacted to dd5xl in worked im for Banana Pi M3   
    My DDRAM is "H9CCNNNBJTMLARNUM" where according to the datasheet the B" should be read as a "8" (8GB density).
     
    And yes, I've read the specs and voltages as well.
    From my experiences any platform has to be tuned in terms of clocks and voltages to become stable. You can't rely e.g. on a PMIC delivering exactly the voltages as programmed in the registers due to chip variations and PCB layout constraints.
     
    Its not the programmed value but the effective voltage at the consuming chip which makes the difference.
     
  2. Like
    going reacted to dd5xl in worked im for Banana Pi M3   
    @goingI'm on Armbian 24.2:

     
    bert@bananapim3:~$ lsb_release -a No LSB modules are available. Distributor ID: Debian Description: Armbian 24.2.0-trunk.550 bookworm Release: 12 Codename: bookworm bert@bananapim3:~$ uname -a Linux bananapim3 6.1.63-current-sunxi #1 SMP Mon Nov 20 10:52:19 UTC 2023 armv7l GNU/Linux  
  3. Like
    going reacted to dd5xl in worked im for Banana Pi M3   
    @going I'm still on CONFIG_DRAM_CLK=480 as preset by defconfig.
     
    Please see my .config against U-Boot V2024.01 below!
     

     
     
    BananaPiM3_u-boot_2024.zip
  4. Like
    going got a reaction from highlander0681 in None of the images work.. OrangePi Zero2   
    You won't believe it, but sometimes it seems to me that artificial intelligence begins to mock my messages.
    I apologize.
     
  5. Like
    going reacted to Gunjan Gupta in Orange Pi Zero 3   
    I have the same experience based on my last 7 months of being here. I totally agree with you.
     
    I also don't disagree with the idea of making it simpler for the non-techie user as long as its not something that is going to increase development and maintenance burden for Armbian. I know no matter how simple we make for them, a lot of them will just try it once and will say its easier to do things on raspberry pi and move on. Simply because its easier for them to find guides for it and they are more geared towards end result than the learning they gather in the process.
  6. Like
    going got a reaction from Gunjan Gupta in Orange Pi Zero 3   
    A short comment on the discussion.
     
    I never use armbian-config. It doesn't help me figure out the essence of the problem.
    I am considering the overlays that are provided by Armbian as a template for possible use.
    A script that switches something can be harmful. I'm just turning it off.
    Next, I pull out the DTB from the working system, which was actually applied.
     
    I open the schematic diagram of the printed circuit board and the schematic diagram of the device that I want to attach to the board.
    I write out the available pin numbers in the table that I could use.
    I take an overlay file found on the Internet or an existing one as a basis and rewrite it to suit my needs.
     
    Next, compile this file, add it to the download and check its operability.
    This algorithm ensures that nothing superfluous appears in the applied device tree.
     
    We can add a lot of automation. We can even connect neural networks to recognize circuit diagrams.😁
    But an experienced user will still try to get around (ignore) all this.
    And an inexperienced user will not understand why something is not working for him.
    He just did not extract the DTB from the running OS and he does not see the real state of things.
     
    It seems to me that helping the user to start thinking with his own head is the best solution.
  7. Like
    going got a reaction from bahtiyar57 in worked im for Banana Pi M3   
    @Tu Hu Until we do the verification, you can use my image. It was created in my version of the build system.
    Armbian_23.10_Bananapim3_bookworm_edge_6.4.10_minimal.zip
  8. Like
    going reacted to bahtiyar57 in Banana Pi M3 crashes if ETH plugged   
    Disabling EEE on my router settings solved the problem.
     
     
    EDIT:
    Is there an option to disable EEE directly from Armbain?
  9. Like
    going got a reaction from bahtiyar57 in Banana Pi M3 crashes if ETH plugged   
    @bahtiyar57
     
     
    _________________ FTDI232 BPI | _________________ | | 3.3v |_____ ____ UART GND o|---------------|o GND o| | || | | Linux TX o|---------------|o RX o| | USB|| |====USB cable===| console RX o|---------------|o TX o |____||____| | "minicom" _________________| |________5v______| o| 3.3v
    o|
    This is the jumper on the device.
    I use this scheme. Everyone uses this scheme. It's safe.
  10. Like
    going got a reaction from Werner in Banana Pi M3 crashes if ETH plugged   
    @bahtiyar57
     
     
    _________________ FTDI232 BPI | _________________ | | 3.3v |_____ ____ UART GND o|---------------|o GND o| | || | | Linux TX o|---------------|o RX o| | USB|| |====USB cable===| console RX o|---------------|o TX o |____||____| | "minicom" _________________| |________5v______| o| 3.3v
    o|
    This is the jumper on the device.
    I use this scheme. Everyone uses this scheme. It's safe.
  11. Like
    going got a reaction from AaronNGray in worked im for Banana Pi M3   
    @Gunjan Gupta I apologize. The machine translator wrote changing the meaning. 
    It should be tested by someone who has these boards. First of all, it's me.
    Yes.
    I'm not suggesting anything. I'm just thinking. I will not make the decisions to do this or that.
     
    My thoughts on the code:
    function post_config_uboot_target__extra_configs_for_bananapipro() { display_alert "$BOARD" "set dram clock" "info" run_host_command_logged scripts/config --set-val CONFIG_DRAM_CLK "384" } I didn't see the difference in the names bananapipro and bananapim3.
    I'm sorry, the glasses are on my nose.
    But that doesn't change the point. The user will only see the message:
    bananapipro set dram clock
    What if he added his own custom patch? Does the build system allow the user to add patches today?
    Maybe give the user the opportunity to set the value of this variable? For example:
    UBOOT_CONFIG_DRAM_CLK="${UBOOT_CONFIG_DRAM_CLK:-384}" function post_config_uboot_target__extra_configs_for_bananapipro() { display_alert "$BOARD" "set dram clock to $UBOOT_CONFIG_DRAM_CLK" "info" run_host_command_logged scripts/config --set-val CONFIG_DRAM_CLK "$UBOOT_CONFIG_DRAM_CLK" } Please don't listen to my grumbling, but do as you see fit.
  12. Like
    going reacted to AaronNGray in worked im for Banana Pi M3   
    @going Armbian_23.10_Bananapim3_bookworm_edge_6.4.10_minimal - boots and expands fine, the caps lock light works as well now ! reboots fine. sudo apt-get update works,  sudo apt-get upgrade works, and reboots.
     
    Armbian_community_24.2.0-trunk.449_Bananapim3_bookworm_current_6.6.13 - boots and expands fine, caps lock light works. sudo reboot now, shuts down, and fails on reboot, power down/up reboot fails too. Attached logs
    system.journalsystem.journalsystem.journal
    kern.log syslog system@11efa2ed424246fabfc13bc624702e97-0000000000000001-00060fba61d3372c.journal
  13. Like
    going got a reaction from AaronNGray in worked im for Banana Pi M3   
    @Tu Hu Until we do the verification, you can use my image. It was created in my version of the build system.
    Armbian_23.10_Bananapim3_bookworm_edge_6.4.10_minimal.zip
  14. Like
    going reacted to Werner in worked im for Banana Pi M3   
    https://debug.armbian.de
  15. Like
    going got a reaction from bahtiyar57 in thermal thermal_zone0: failed to read out thermal zone (-110)   
    The version of the package from Armbian is the release number. Judging by the screenshot you provided, it is 23.8.1.
    The version of my package is 6.4.14-Armbian.23.10 that is, it will always be less than the Armbian.
    It probably needs to be frozen from updates.
     
    Try to check it out. Type:
    sudo apt upade
    sudo apt --list upgradable
     
    P.S.I don't use their repository. I assemble all the packages and the image myself.
  16. Like
    going reacted to ag123 in NPU   
    here is some 2 cents comments, if you are meaning NPUs like these:
     
    https://github.com/rockchip-linux/rknpu2
     
    - hardware interfaces are kept as trade secrets and not published anywhere
     
    1st the hardware interfaces are practically undocumented, what they provide is mostly an 'sdk' with some binary blobs
    it practically means there is *no way* to use the NPU as those binary blobs in turn depend on device drivers which again are binary blobs (no source)
    and there is no hardware documentation any where about the technical details, registers etc. 
    if that at least those are published, one could possibly start coding something to test things on the NPU.
     
    then that for things like ethos-n78
    https://www.arm.com/products/silicon-ip-cpu/ethos/ethos-n78
    you can find some info here
    https://developer.arm.com/Processors/Ethos-N78
    but that it seemed the real SOCs with that chip is no where to be seen let alone any boards found with them.
     
    - IO / cpu scheduling 
     
    cpu frequency scaling / governors are well documented
    https://www.kernel.org/doc/Documentation/cpu-freq/governors.txt
    https://docs.kernel.org/scheduler/schedutil.html
    https://www.kernel.org/doc/html/latest/scheduler/
    and for 'simple' ARM (or RISC V) chips, any sort of 'elaborate' scheduling are probably going to just burn more cpu cycles with little to gain.
    but that nevertheless the source codes and the documentations are there so that one can try to develop your own governor if you prefer.
    and that the elaborate 'advanced' schedutil governor is already there in the kernel, likely in Armbian as well.
    Hence, one can proceed to improve that if one deem that the state-of-the-art currently isn't adequate.
     
    and if one wants to do some manual scheduling there is the plain old "nice" command
    https://www.scaler.com/topics/linux-nice/
     
    ----
    well my thoughts, scheduling and NPU are 2 unrelated issues, it is possible to handle 'elaborate' scheduling without an NPU, this is currently the state-of-the-art from the 'lowly' ARM boards that we are running, to top tier high core count Intel Xeon / AMD Epyc processors and running all that loads ranging from amazon, google, chatgpt etc, no issues.
     
    The other thing being the NPUs itself, currently many SOC IP owners, held their hardware interfaces as *trade secrets* and refused to release them.
    You would need to jump that hoop to even use the NPU without any documentation, or else use their proprietary binary blob software, which won't work outside their proprietary binary blob distributions.
     
    This withheld *trade secret* about the NPU is the biggest pitfall / trap to those buying those boards with those SOCs and wanting to use the NPU. you get *no support*, *no help*, *no nothing* after you buy the board which purportedly has the NPU. practically *useless*. don't even bother to try it for any 'test' 'AI' stuff, you may at best get a *binary blob demo* and that's it (and it is not anywhere close to even using it for any practical purpose, let alone scheduling).
     
    And much more than that, using an NPU practically means that your neural network model must be *quantized*, if you know what that means. All those small NPU hardware normally handles like 8 bit integers, 16 bit integers or at best 16 bit floats. This practically means that you would need to spend a lot of effort to *convert* even ordinary neural networks into the *quantized* form that can be processed by the NPU, if you can't convert that it is  unusable. Even if you managed to convert that there is a risk of lost of precision, e.g. if you convert a 32 bit float down to an 8 bit int, you may practically be quantizing a number space of 4 billion numbers (actually more) to 256 quantized levels. that is the extreme of the information loss, and at the end of the day, if it even works, you may simply get *wrong* results, and again it is practically *useless*.
     
  17. Like
    going reacted to bahtiyar57 in thermal thermal_zone0: failed to read out thermal zone (-110)   
    worked. Thank you.

  18. Like
    going got a reaction from bahtiyar57 in thermal thermal_zone0: failed to read out thermal zone (-110)   
    @bahtiyar57 I am aware of this regression in the latest kernel changes for sunxi.
    Try installing an older kernel using the armbian-config utility, for example:
    for current - 5.15.93-sunxi
    for edge - 6.1.11-sunxi
     
    If you want to build the kernel yourself, write here.
    I will provide you with the necessary changes for the A83T processor.
  19. Like
    going got a reaction from bahtiyar57 in thermal thermal_zone0: failed to read out thermal zone (-110)   
    Try updating the kernel
  20. Like
    going got a reaction from bahtiyar57 in thermal thermal_zone0: failed to read out thermal zone (-110)   
    ____ ____ _ __ __ _____ | __ )| _ \(_) | \/ |___ / | _ \| |_) | | | |\/| | |_ \ | |_) | __/| | | | | |___) | |____/|_| |_| |_| |_|____/ Welcome to Armbian 23.10 Bookworm with Linux 6.4.14 No end-user support: built from trunk & unsupported (bookworm) userspace! System load: 6% Up time: 3 min Memory usage: 5% of 1.96G IP: 192.168.100.101 CPU temp: 38°C Usage of /: 12% of 7.3G ========================================================================== leo@bananapim3:~$ armbianmonitor -m Two CPU clusters are available for monitoring Stop monitoring using [ctrl]-[c] Time CPU_cl0/CPU_cl1 load %cpu %sys %usr %nice %io %irq Tcpu C.St. 12:35:38 1344/1152 MHz 0.14 8% 1% 1% 0% 5% 0% 39.1 °C 0/5 12:35:43 1344/1344 MHz 0.13 0% 0% 0% 0% 0% 0% 38.7 °C 0/5 12:35:48 1344/ 768 MHz 0.12 0% 0% 0% 0% 0% 0% 39.5 °C 0/5 12:35:54 1152/1344 MHz 0.11 0% 0% 0% 0% 0% 0% 38.8 °C 0/5 12:35:59 1344/1152 MHz 0.10 0% 0% 0% 0% 0% 0% 39.4 °C 0/5 12:36:04 1344/1152 MHz 0.09 0% 0% 0% 0% 0% 0% 39.7 °C 0/5 12:36:09 768/1344 MHz 0.08 0% 0% 0% 0% 0% 0% 39.7 °C 0/5 12:36:14 1152/1344 MHz 0.08 0% 0% 0% 0% 0% 0% 39.4 °C 0/5^C  
    This is my last kernel build for this platform.
    It shows the temperature correctly.
    You can simply download and install this kernel at:
    https://github.com/The-going/PKG_test/tree/master/linux-edge-sunxi-6.4.14
     
    The *dtb*.deb package is not required.
  21. Like
    going got a reaction from bahtiyar57 in thermal thermal_zone0: failed to read out thermal zone (-110)   
    wget https://github.com/The-going/PKG_test/raw/master/linux-edge-sunxi-6.4.14/linux-image-edge-sunxi_6.4.14-Armbian.23.10_armhf.deb  
  22. Like
    going got a reaction from bahtiyar57 in thermal thermal_zone0: failed to read out thermal zone (-110)   
    #!/usr/bin/bash url="https://github.com/The-going/PKG_test/raw/master/linux-edge-sunxi-6.4.14/" pkg="linux-headers-edge-sunxi_6.4.14-Armbian.23.10_armhf.deb \ linux-libc-dev_6.4.14-Armbian.23.10_armhf.deb \ linux-image-edge-sunxi_6.4.14-Armbian.23.10_armhf.deb" for p in $pkg do wget ${url}${p} done create dl.sh in target dir
    chmod +x dl.sh
    ./dl.sh
     
    sudo dpkg -i linux-image-edge-sunxi_6.4.14-Armbian.23.10_armhf.deb
  23. Like
    going reacted to ag123 in Building Armbian using Ubuntu (jammy) in a systemd-nspawn container   
    Updated section on loop devices in systemd-nspawn container
    https://gist.github.com/ag88/05245121cce37cb8f029424a20752e35
    Currently systemd-nspawn do not support loop devices needed in the compile.sh build. This section documents some workarounds to create loop devices in a systemd-nspawn container. Use this shell script to start systemd-nspawn
    #!/usr/bin/bash sudo systemd-nspawn -b --capability=CAP_MKNOD \ --property=DeviceAllow="block-loop rwm" \ --property=DeviceAllow="block-blkext rwm" \ --property=DeviceAllow="/dev/loop-control rwm" \ -D /opt/armbian-build  
    when the container is started up, in the shell within the container, use this shell script to create the loop devices
    #!/usr/bin/bash if ! test -e /dev/loop-control; then sudo mknod /dev/loop-control c 10 237 fi for i in 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15; do if ! test -e /dev/loop${i}; then sudo mknod /dev/loop${i} b 7 ${i} fi done  
    In current tests, the above did create the loop devices, but is inadequate to fully resolve the issue with loop devices in armbian build compile.sh.
  24. Like
    going reacted to Igor in Startups fail after root file system moved to SSD   
    Perhaps it doesn't work. More resources / ideas / background:
    https://www.google.com/search?q=blacklist+USB+UAS+armbian
    https://www.cnx-software.com/2020/08/12/how-to-fix-unreliable-usb-hard-drives-stalled-transfers-linux-windows/
    https://leo.leung.xyz/wiki/How_to_disable_USB_Attached_Storage_(UAS)
  25. Like
    going reacted to jock in Repository for v4l2request hardware video decoding (rockchip, allwinner)   
    Hello, this quick tutorial is to introduce an experimental Debian and Ubuntu APT repository to install ffmpeg and mpv compiled with v4l2request and v4l2drmprime patches developed by Linux kernel, LIbreELEC and Kodi folks to allow hardware video decoding on stateless decoders like those implemented in Rockchip and Allwinner SoCs for h.264, h.265, vp8 and vp9 codecs.
     
    The repository introduces a new package ffmpeg-v4l2request that integrates and substitues the base ffmpeg package and its related packages.
    Also provides mpv 0.35.1 for Ubuntu Jammy, which has an overrall better support for hardware video decoders.
     
    Preconditions:
    Kernel should be 6.1 or more recent armhf or arm64 architecture Supported operating systems are Debian Bookworm and Ubuntu Jammy Rockchip and Allwinner have already been tested, but this should work on other platforms with stateless decoders supported in kernel  
    APT REPOSITORY SETUP
    To install the repository, just copy and paste the lines for your operating system in a terminal
     
    For Debian Bookworm:
    $ sudo wget http://apt.undo.it:7241/apt.undo.it.asc -O /etc/apt/trusted.gpg.d/apt.undo.it.asc $ echo "deb http://apt.undo.it:7241/debian bookworm main" | sudo tee /etc/apt/sources.list.d/apt.undo.it.list  
    For Ubuntu Jammy:
    $ sudo wget http://apt.undo.it:7241/apt.undo.it.asc -O /etc/apt/trusted.gpg.d/apt.undo.it.asc $ echo "deb http://apt.undo.it:7241/ubuntu jammy main" | sudo tee /etc/apt/sources.list.d/apt.undo.it.list  
    INSTALL FFMPEG AND MPV PACKAGES
    $ sudo apt update $ sudo apt install ffmpeg-v4l2request mpv  
    SETUP MPV CONFIG FILE
    $ sudo mkdir -p /etc/mpv $ echo -e "hwdec=drm\ndrm-drmprime-video-plane=primary\ndrm-draw-plane=overlay" | sudo tee /etc/mpv/mpv.conf  
    You can now play your videos using mpv and they should run with hardware decoding if supported, either in virtual terminals or in X11/Wayland windows!
    Enjoy!
     
    Notes:
    your mileage may vary a lot: the more recent is the kernel version, the better is support (you may need edge kernel) bug: when rendered in X11/Wayland window, video may show scattered tiles during frames bug: Lima driver (Mali 400/450) shows a red/pink tint when video is played in X11/Wayland (see https://github.com/mpv-player/mpv/issues/12968) (workaround below: https://forum.armbian.com/topic/32449-repository-for-v4l2request-hardware-video-decoding-rockchip-allwinner/?do=findComment&comment=177968) Panfrost driver should work flawlessy 10 bit HEVC are generally supported on all Rockchip devices (rk322x, rk3288, rk33x8, rk3399), but Allwinner H3 have no hardware support for that  
     
     
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines