Jump to content

Werner

Administrators
  • Posts

    4424
  • Joined

  • Last visited

Reputation Activity

  1. Like
    Werner got a reaction from Igor in Raspberry Pi4 apt-get update problems   
    Yeah, why not. As CSC of course.
  2. Like
    Werner reacted to SteeMan in Newbie developer question   
    Post the log of your build
  3. Like
    Werner reacted to Spooky in Kernel 6.1 for Orange Pi 5+   
    Hey @amazingfate, the above-mentioned av1 decoder issue was fixed, turned out that the Rock 5A and a few other boards did not have the av1d node enabled in the device tree. I did update ffmpeg and added some patches to mpv last night, after testing everything it looks good to go. 

    The packages ffmpeg, librga, libv4l-rkmpp, mpp, and mpv are ready to be copied to your PPA. 

    https://launchpad.net/~jjriek/+archive/ubuntu/rockchip-multimedia/+packages?field.name_filter=&field.status_filter=published&field.series_filter=jammy
  4. Like
    Werner got a reaction from VioletGiraffe in How to enable extra kernel modules when compiling from source?   
    There are actual two ways. You can use code { font-family: Consolas,"courier new"; color: crimson; background-color: rgba(0, 0, 0, 0.2); padding: 2px; font-size: 105%; } ./compile.sh KERNEL_CONFIGURE=yes which will continue to assemble an image with the modified config file which is more user friendly.
    On the other hand there is code { font-family: Consolas,"courier new"; color: crimson; background-color: rgba(0, 0, 0, 0.2); padding: 2px; font-size: 105%; } ./compile.sh kernel-config which will export the modified kernel config into code { font-family: Consolas,"courier new"; color: crimson; background-color: rgba(0, 0, 0, 0.2); padding: 2px; font-size: 105%; } output/ folder and stops there which is more developer friendly.
    If you chose latter route you need to move the exported config to userpatches or overwrite the one in code { font-family: Consolas,"courier new"; color: crimson; background-color: rgba(0, 0, 0, 0.2); padding: 2px; font-size: 105%; } config/kernel/. Once you done that simply execute code { font-family: Consolas,"courier new"; color: crimson; background-color: rgba(0, 0, 0, 0.2); padding: 2px; font-size: 105%; } ./compile.sh and the modified config will be used.
  5. Like
    Werner got a reaction from VioletGiraffe in How to enable extra kernel modules when compiling from source?   
    Hi,
     
    =y means the driver/functionality is directly compiled into the kernel
    =m means it will be built and made available as kernel module
     
  6. Like
    Werner reacted to SteeMan in Orange Pi Zero 3   
    When you have been involved with Armbian for a length of time (and read a few of igor's rants 🙂 ) you will realize why what was said here will not be received well by many within Armbian.
    It isn't that what you are saying isn't a reasonable comment.  The problem is that Armbian is under resourced by probably an order of magnitude.  Discussions are continually occurring on how the project can survive let alone move forward.  Many of those conversations involve discussing how more can be done with less resources, ways to cut features/scope to make what exists manageable.  So by you saying to "put [more work] onto developers in Armbian is far better than ..." you are hitting a nerve.  In the current environment that will never pass muster.  Any proposed solution needs to maintain or reduce developer work in the long term.  So any feature suggestion is going to be measured first against that metric, then secondarily by the merits of that feature. 
     
    This whole dtd discussion is fundamentally a request for a new feature for Armbian.  Regardless of the merits of your focus on the end user experience, that isn't the way Armbian has handled dtbs in any of the existing boards that are supported.  I'm not saying that what exists is good or desireable, but it is what it is.  Can it be improved, sure.  Can it be improved and at the same time not increase maintenance costs going forward, maybe.
     
  7. Like
    Werner got a reaction from highlander0681 in None of the images work.. OrangePi Zero2   
    https://debug.armbian.de
  8. Like
    Werner reacted to going 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.
  9. Like
    Werner reacted to jmaus in RPi5 kernel headers   
    Absolute awesome. Thank you @Igor for the fast response. Now all the kernel and kernel headers are there and I can compile additional kernel modules. Highly appreciated!
  10. Like
    Werner got a reaction from bedna in I just want to buy a t-shirt or two...   
    There never was a cert since it is just a simple redirect to https://armbian.myspreadshop.net/ so feel free to use this address.
  11. Like
    Werner got a reaction from going in worked im for Banana Pi M3   
    https://debug.armbian.de
  12. Like
    Werner got a reaction from leeson in /var/log is 100% full - how to move to HDD?   
    if the whole OS is no longer on a SD card you can disable ramlog in /etc/default/armbian-ramlog.
  13. Like
    Werner got a reaction from Gunjan Gupta in NPU   
    Player left the game. Case closed.
  14. Like
    Werner reacted to simonswine in Problems installing zfs-dkms -> config_modules not enabled?   
    I have hit this problem (on a non-dkms OS), it helped patching this symbol restriction:
     
    https://github.com/armbian/linux-rockchip/pull/142
  15. Like
    Werner got a reaction from Marco Schirrmeister in ZFS module not built on Jammy/Bookworm legacy/edge. Solutions or alternatives ?   
    https://openzfs.github.io/openzfs-docs/Developer Resources/Building ZFS.html
     
    [ 424.596656] zfs: module license taints kernel. [ 425.491531] ZFS: Loaded module v2.2.99-311_gd9cb42da9, ZFS pool version 5000, ZFS filesystem version 5  
    tested on OPi5 with kernel 6.7.1
     
    Getting it working on legacy 5.10.y rk Android-hackedtogether kernel is a bot tougher.
    https://github.com/radxa/kernel/issues/54
    Spoiler: patching method does not work anymore, at least not for me . Tested with 5.10.160...
     
  16. Like
    Werner got a reaction from SERG_V in How to turn off zram   
    Check /etc/default/armbian-zram-whatever file. Don't remember the exact name
     
  17. Like
    Werner 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*.
     
  18. Like
    Werner got a reaction from ag123 in Orange Pi Zero 3   
    "legacy" is a term that thas been established years ago when there wasn't much confusion about it. However things have changed and now it is, depending on board family, either an old-LTS just for historical purpose or a vendor kernel which may or may not significantly outdated but working.
    Anyway there are discussion about renaming that into "vendor" or something, however the impact would be huge if not done carefully.
     
    If anyone steps up doing, testing and maintaining this, why not? We won't simply due to lack of human resources.
  19. Like
    Werner got a reaction from bahtiyar57 in thermal thermal_zone0: failed to read out thermal zone (-110)   
    You should be up-to-date regarding "current" branch. Since "edge" kernels are not available through this you can try building and installing those packages by yourself.
    https://docs.armbian.com/Developer-Guide_Build-Preparation/
     
    Anyway also an option is to try an older one, like 5.15.y and see if the issue disappears....
  20. Like
    Werner got a reaction from pixdrift in Orange Pi Zero 3   
    "legacy" is a term that thas been established years ago when there wasn't much confusion about it. However things have changed and now it is, depending on board family, either an old-LTS just for historical purpose or a vendor kernel which may or may not significantly outdated but working.
    Anyway there are discussion about renaming that into "vendor" or something, however the impact would be huge if not done carefully.
     
    If anyone steps up doing, testing and maintaining this, why not? We won't simply due to lack of human resources.
  21. Like
    Werner got a reaction from manuti in H2: Sunvell R69 Android TV Box (AliExpress)   
    https://docs.armbian.com/User-Guide_Getting-Started/#how-to-prepare-a-sd-card
  22. Like
    Werner got a reaction from jock in ch340 hardware support fails after current Tinkerboard image updated to default desktop in armbian-config   
    It is quite common that boards actually like slight overvoltage. This is last but not least to compensate for voltage drop across connectors, wiring and the PCB itself.
    As an example the official PSU for Orange Pi 5 boards, while being marked as 5vdc output, in reality output around 5.3 volts.
    Also cellphone chargers are not recommended since they are not designed to handle variable but constant charging loads. Also voltage very likely drops well below 5 volts under load.
  23. Like
    Werner reacted to SteeMan in OrangePiPC + Armbian embedded microphone issue   
    That is because this board is not supported, and you were posting in the supported boards section of the forum. 
  24. Like
    Werner reacted to pixdrift in Orange Pi Zero 3   
    Well.. one small line for orangepizero3.wip, one giant leap for Orange Pi Zero 3

    The overlay PR fix from @Stephen Graf has been merged into Armbian.. thanks for sticking with it.. awesome to have more people contributing 
    https://github.com/armbian/build/commit/08623d0e37dc02cb728b264f1e64771ddaba8025

     
  25. Like
    Werner reacted to Stephen Graf in Orange Pi Zero 3   
    @Gunjan Gupta No offence taken.  I am always impressed by people who have to communicate in a language other than their native. Keep giving me advice and I will keep trying to learn.
     
    In that respect can you tell me why this dts does not compile:
     
    sysadmin@orangepizero3:/mnt/dtbo$ dtc -O dtb -o sun50i-h616-i2c3.dtbo sun50i-h616-i2c3.dts
    sun50i-h616-i2c3.dts:19.29-23.19: ERROR (phandle_references): /fragment@1/__overlay__: Reference to non-existent node or label "i2c3_ph_pins"
    ERROR: Input tree has errors, aborting (use -f to force output)
    sysadmin@orangepizero3:/mnt/dtbo$ more sun50i-h616-i2c3.dts
    /dts-v1/;
    / {
            compatible = "allwinner,sun50i-h616";
            fragment@0 {
                    target-path = "/aliases";
                    __overlay__ {
                            i2c3 = "/soc/i2c@5002c00";
                            i2c3_ph_pins = "/soc/pinctrl@300b000/i2c3-ph-pins";
                    };
            };

            fragment@1 {
                    target = <0xffffffff>;
                    __overlay__ {
                            status = "okay";
                            pinctrl-names = "default";
                            pinctrl-0 = <&i2c3_ph_pins>;
                    };
            };
            __fixups__ {
                    i2c3 = "/fragment@1:target:0";
            };
    };
     
     
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines