Jump to content

Werner

Administrators
  • Posts

    4471
  • Joined

  • Last visited

Everything posted by Werner

  1. Could be a loose connection/slack joint. Hard to tell remotely Yeah that one should do.
  2. I don't know. You can check by yourself (something like code { font-family: Consolas,"courier new"; color: crimson; background-color: rgba(0, 0, 0, 0.2); padding: 2px; font-size: 105%; } apt-cache search linux*current-rockchip64) Well that would rather be a downgrade than an upgrade Anyway while switching kernel again would work the module you want to build and need the headers for will not.
  3. You need the kernel headers matching your kernel version. Older headers will not work. However we had (have?) some issues with the repository so you may need to switch to a different kernel version which also has the matching headers in the repo.
  4. There never was a cert since it is just a simple redirect to https://armbian.myspreadshop.net/ so feel free to use this address.
  5. If desktop version supports HDMI then CLI and minimal do as well.
  6. 1. Not using CP2102 as it cannot handle 1.5mbaud. CP2104 for example does. 2. not using random UART you find on the GPIO but using the actual debug UART connectors: https://wiki.friendlyelec.com/wiki/images/7/7c/NanoPi_NEO3-layout.jpg 3. @lpirl can be right too. I used to own a Neo3 just like yours but it died on me.
  7. Oddly there are no bcm2712 packages whatsoever in stable repo. At least not on my mirror. However there are current and edge packages in beta including headers. 13236 ./pool/main/l/linux-headers-current-bcm2712/linux-headers-current-bcm2712_24.2.0-trunk.480_arm64__6.6.13-S374f-D719f-P0000-Cb2aaH4168-HK01ba-Vc222-B4d80-R448a.deb 25531 ./pool/main/l/linux-6.6.13/linux-image-current-bcm2712_24.2.0-trunk.480_arm64__6.6.13-S374f-D719f-P0000-Cb2aaH4168-HK01ba-Vc222-B4d80-R448a.deb 120 ./pool/main/l/linux-dtb-current-bcm2712/linux-dtb-current-bcm2712_24.2.0-trunk.480_arm64__6.6.13-S374f-D719f-P0000-Cb2aaH4168-HK01ba-Vc222-B4d80-R448a.deb
  8. Yes, it is relevant. Without an sdcard with operating instructions (boot loader and OS to say) the board simply does absolutely nothing since there is no other storage on.
  9. Use legacy if you need those. Do not run bleeding edge stuff if you don't know how to deal with such issues.
  10. I don't know. However using the serial console you get an idea if the board is the issue or your usb-ethernet adapter.
  11. Your baudrate is wrong. Try 115200 instead of 15200 as suggested in the video.
  12. serial console is best way to debug boot and connectivity issues: https://debug.armbian.de
  13. SSH is always enabled by default. However I remember there is a rare case where sshd cannot start properly for some reason. serial console is the best way to debug this (and restart sshd) Buy a few extra. They are dirt cheap
  14. Usually the filesystem expands itself across the whole sdcard on first boot...odd.
  15. Providing logs with armbianmonitor -u helps with troubleshooting and significantly raises chances that issue gets addressed.
  16. Providing logs with armbianmonitor -u helps with troubleshooting and significantly raises chances that issue gets addressed.
  17. As long as you do not redistribute an image with built-in ZFS no. https://docs.kernel.org/admin-guide/tainted-kernels.html
  18. Whole documentation is needs updates. Like all the build switches (kernel, kernel-config, uboot,...) are missing...
  19. Providing logs with armbianmonitor -u helps with troubleshooting and significantly raises chances that issue gets addressed. Try installing armbian-firmware-full via apt
  20. Player left the game. Case closed.
  21. for legacy: https://forum.armbian.com/topic/25590-problems-installing-zfs-dkms-config_modules-not-enabled/?do=findComment&comment=179556
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines