Jump to content

Werner

Administrators
  • Posts

    5915
  • Joined

  • Last visited

Other groups

Management Contributor/Maintainer

Profile Information

  • Gender
    Male
  • Location
    Federal republic of Germany

Contact Methods

  • Website URL
    https://github.com/EvilOlaf
  • Github
    EvilOlaf
  • Discord
    werner

Recent Profile Visitors

42304 profile views
  1. Okay so then we have some issues here This is clearly wrong since these packages come from upstream Debian and cannot/will not work with Armbian kernels. This shall be reported here: https://github.com/armbian/configng/ Then you were lucky some working headers were present https://docs.armbian.com/Developer-Guide_Build-Preparation/ Or in very short: git clone the repo ./compile.sh BOARD=rockpi-4bplus BRANCH=current kernel Check output/debs for your packages Install via dpkg -i on the target board
  2. We don't ship headers for each and every trunk image. Way too much data. Simplest solution is to use the framework to create a complete set of kernel deb packages. Those will include matching headers.
  3. moved to staging
  4. Upstream support for rk3588 is still wip. For desktop usage I suggest to either try "edge" which may have the feature you want already merged in or try "vendor" kernel which is based on Rockchip BSP.
  5. We neither deal with nor do we support 3rd party images/OS.
  6. You are not using Armbian. This is a fork of Armbian which uses our name without permission and they do not contribute to the core development process. They trick you into thinking that you will get some sort of support at this place which isn't the case. We do not support 3rd party forks.
  7. https://paste.armbian.com/hicilanono Works just fine
  8. Booting from mtd/nvme should just work. Most common problems: - dirty mtd/emmc. vendor/unmatching boot loader can cause issues. - mixup between m.2 sata and actual nvme. Correct overlay/dt must be used - wrong rootfs uuid in armbianEnv.txt after running armbian-install (after done, do not reboot but mount freshly written nvme to a random folder and check if the uuid is correct)
  9. Since we do not add any Intel drivers this regression may come from upstream. You could test nightly build which have kernel 7.0. Also total random guess: Perhaps more recent kernels expect more recent firmware blobs, perhaps the ones on the board are outdated (or are expected to be on a different place)? No clue though through which package those are shipped though. Seems like the files have been touched last around 7 month ago: https://git.kernel.org/pub/scm/linux/kernel/git/iwlwifi/linux-firmware.git/tree/intel/iwlwifi
  10. Perhaps related https://github.com/armbian/firmware/commit/36ec4377c197af9ced4a02aaa660ade54c83f93d
  11. Providing logs with armbianmonitor -u helps with troubleshooting and significantly raises chances that issue gets addressed.
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines