Jump to content

Igor

Administrators
  • Posts

    14514
  • Joined

  • Last visited

Posts posted by Igor

  1. 11 hours ago, Kriston said:

    This board is gaining popularity due to the Orange Pi manufacturer's good reputation with Arm.

     

    Lowest price is what makes it popular. But software is the biggest key of the package and there they are among the worst.

     

    11 hours ago, Kriston said:

    What would I need to modify in the build process?

     

    On this SoC, we will be cooperating with SoC maker's board directly - working with Orangepi is too damaging for us:

    https://www.cnx-software.com/2025/04/27/muse-pi-pro-feature-packed-credit-card-sized-spacemit-m1-risc-v-sbc/

    This will probably be done in a couple of weeks, so you can follow that and adjust accordingly.

  2. Long time no see! :)

     

    On 10/17/2025 at 9:15 PM, sgjava said:

     initramfs only loads usbhid.

     

    This doesn't look right. I checked docents of commits and so far couldn't find anything that would stand out. nand-sata-install only copies / rsync file-system, recreate boot scripts and flash boot-loader if necessary. If usb_storage is missing from initird, its normal that it doesn't boot. Its as module:

    https://github.com/armbian/build/blob/main/config/kernel/linux-odroidxu4-current.config#L1274

     

    I would say its something to do with initird generation. Could be on the build / distro tools side.

     

    @belegdol perhaps knows something?

  3. 1 hour ago, EricaLina said:

    Does anyone have any clues to give as to setting up dual screen on the Nanopi m6?


    What do you mean by that? You mean LCD screen on the device and HDMI monitor. This should probably work OOB on vendor 6.1.y kernel. It should also work with mainline, but I haven't tested that and I am not sure that this is included in latest stable build as it was added not long ago. Try build from sources, use EDGE kernel perhaps.

     

    1 hour ago, EricaLina said:

    I searched the forum and found nothing.

     

    It is very specific case - probably nobody asked for that before. At least I don't recall.

     

    1 hour ago, EricaLina said:

    The forum shows one post for the Nanopi m6 and I know that can't be right.

     

    Core features are based on SoC, so when you are looking for clues, look wider - Orange 5 *, Khadas Edge 2, Bananapi M7, ... all that carries RK3588 SoC.

     

    1 hour ago, EricaLina said:

    Currently installing X on a minimal install.


    Best is to start with recommended Gnome image. That is most polished.

  4. On 10/3/2025 at 3:28 AM, monetschemist said:

    there is a complaint about a CRC error

     

    "*** Warning - bad CRC, using default environment"


    This is safe to ignore. 

    It is strange why Ubuntu doesn't work, while Bookworm does. This could be some build infrastructure issue.

     

    On 10/3/2025 at 3:28 AM, monetschemist said:

    If anyone generates a new Ubuntu 24.04 image


    https://docs.armbian.com/Developer-Guide_Build-Preparation/

  5. On 10/1/2025 at 12:12 PM, laibsch said:

    is probably in the best position to answer when a new image for your board might be available.


    Sige5 is community supported and those boards receive automatic generated images only - once per week. Since GitHub introduced additional limitations few months ago, we can't (auto)produce desktop images anymore - only one Debian stable minimal per CSC build target. However, this might change in the future.

  6. 1 hour ago, Warma said:

    will I run into problems with some packages


    Kernel packages comes from the same (main) repository. This won't cause you problems, if you upgrade from bookworm to trixie, but we can't guarantee for packages that comes from Debian.

     

    You might try this way:
    https://docs.armbian.com/User-Guide_Armbian-Config/System/#stable-distro-upgrade

    Note that you might need to download updated Armbian key:
     

    wget -qO - https://apt.armbian.com/armbian.key | gpg --dearmor | \
    sudo tee /usr/share/keyrings/armbian.gpg > /dev/null
    cat << EOF | sudo tee /etc/apt/sources.list.d/armbian-config.sources > /dev/null
    Types: deb
    URIs: https://github.armbian.com/configng
    Suites: stable
    Components: main
    Signed-By: /usr/share/keyrings/armbian.gpg
    EOF

     

  7. I think official stand from open ZFS project is: "ZFS is not designed for 32-bit kernels" ... it still might work(ed). IMO stay on kernel 6.6.y. I doubt there is anything wrong on Armbian side ... worth experimenting with Ubuntu Noble minimal image to rule out possible headers incompatibility.

  8. We already did that. I think the problem is that our keys are not packed (yet) but added at build time. When a person upgrades from Bookworm to Trixie, this will show up, while on new Trixie images this shouldn't manifest. @zital debian Is this the case?

    https://github.com/armbian/configng/commit/5d866b9b105bfd46cb341c21c70ba76e32e1fea2

    We are signing with old and new key (which is aligned with current standards) since then.

  9. 2 hours ago, indianajones said:

    So does that mean that the GOVERNOR and CPUMIN params are useless and can be discarded?

     

    Currently yes. A replacement for this package / service needs to be found and implement - in case you want to get involved. 

     

    2 hours ago, indianajones said:

    And BTW your Armbian tools are utterly fantastic.


    Thank you! It's a work of many people, impossible for me to poke into every issue or feature that exists :)

  10. 1 hour ago, Sam Rossiter said:

    I think I need to rebase the Olimex fork back to the main Armbian Repo?


    Recommended. It looks like its not that far away.
     

    1 hour ago, Sam Rossiter said:

    Or should I fork the Armbian repo and then re-apply the Olimex changes to the fork?


    With rebase you will see the diff and if this is all you need to apply.

  11. 13 hours ago, Xorcist said:

    Any clues on what I might be missing?

     

    tl;dr; You need to fix the driver code similar we do it here https://github.com/armbian/build/tree/main/patch/misc 
     

    I tried this:

    https://github.com/albertogviana/YT6801 (but tuxedo v1.0.30 might have this already fixed)


    https://paste.armbian.com/xeraretaxu.diff
    I fix the most obvious errors, but don't have time to deal with this code.

     

    13 hours ago, Xorcist said:

    Then I rolled back the Kernel to 6.12.32 and tried to install the headers again them through armbian-config


    Some intermediate or old kernels might be missing matched headers. They are present at latest kernel (tested).

     

    BTW, it works for me:
     

    khadas-mind:Downloads:% sudo dpkg -i tuxedo-yt6801_1.0.30tux4_all.deb
    Selecting previously unselected package tuxedo-yt6801.
    (Reading database ... 158138 files and directories currently installed.)
    Preparing to unpack tuxedo-yt6801_1.0.30tux4_all.deb ...
    Unpacking tuxedo-yt6801 (1.0.30tux4) ...
    Setting up tuxedo-yt6801 (1.0.30tux4) ...
    Loading new tuxedo-yt6801-1.0.30tux4 DKMS files...
    Building for 6.12.44-current-x86
    Building initial module for 6.12.44-current-x86
    Done.
    
    yt6801.ko:
    Running module version sanity check.
     - Original module
       - No original module exists within this kernel
     - Installation
       - Installing to /lib/modules/6.12.44-current-x86/updates/dkms/
    depmod...
    (Re)load module if possible
    khadas-mind:Downloads:% modinfo yt6801 
    filename:       /lib/modules/6.12.44-current-x86/updates/dkms/yt6801.ko
    license:        GPL
    license:        GPL
    author:         Motorcomm Electronic Tech. Co., Ltd.
    version:        1.0.30
    description:    Motorcomm YT6801 Gigabit Ethernet Driver
    srcversion:     13DED66BAFB05DCB4D65DE6
    alias:          pci:v00001F0Ad00006801sv*sd*bc*sc*i*
    depends:        
    name:           yt6801
    retpoline:      Y
    vermagic:       6.12.44-current-x86 SMP preempt mod_unload modversions 
    parm:           debug:FUXI ethernet debug level (0=none,...,16=all) (int)

     

×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines