Jump to content

Igor

Administrators
  • Posts

    12715
  • Joined

  • Last visited

Other groups

Management Contributor/Maintainer

Profile Information

  • Gender
    Not Telling

Recent Profile Visitors

30316 profile views
  1. Damn Rockchip. I have no issues (except PCI timeouts) with this: Armbian_22.11.1_Rockpi-4b_jammy_current_5.15.79_gnome_desktop.img.xz https://paste.armbian.com/sahalaxuru
  2. Impossible. Perhaps you stumbled to archive mirrors which contains all old images? Here you can observe which mirrors we have and how they are organised: https://github.com/armbian/mirror No, because this is best mirror for your location.
  3. Can you try to use recommended flashing tools? I never tried Rufus ... try decompressing image before using it with Rufus. That might be a problem?
  4. No, problem is identified, but we don't have resources / money to proceed from here. For us, this is 24/7, for you - when something breaks down.
  5. We came this far, we tried with workaround, it doesn't work well, but from here on a slow and painful research needs to be done. We have done our part, more we can't afford.
  6. You are not running kernel provided by Armbian. Perhaps that is the reason?
  7. It is difficult to say what is wrong, but if you are using Armbian you should follow Armbian documentation, not something in between. It can be very different. Vendors are usually using binary boot loaders and proprietary tools they got from chip vendor, while we use open source tools we and community developed. After you erase or disable (connecting pin 23 and 25) SPI, you don't need to do anything else then booting from SD card and using standard armbian-install utility to flash to eMMC boot/eMMC root or eMMC boot/NVME root. We invested a lot of efforts to keep the same install procedure on very different methods ... If there are any hacks needed, they are exposed at download pages https://www.armbian.com/rockpi4/ If you have eMMC to SD card adaptor, that you flash directly and it should work. But like I said, without logs we are in the dark ...
  8. Armbian didn't make OMV. AFAIK there is no need for any special installation as used to be via armbian-config. Just check official OMV install instructions for installing over Armbian Debian. It has to be Debian, otherwise it does not work. I don't know much about OMV internals or installation ...
  9. Release delayed for (at least) one week. Health issues + status too unknown.
  10. You can try to make an image from stock u-boot and kernel if you like. Just proceed this way: https://docs.armbian.com/Developer-Guide_Adding-Board-Family/ but it is unknown how much of work that represent. I can be an easy job, but can also take weeks to months.
  11. Igor

    Mainline kernel

    Boot log: Unusable for any use case ... just a teaser. https://armbian.atlassian.net/browse/AR-1408
  12. Wireguard does not build as its already present in the kernel and that DKMS package is needed (is build-able) only for kernels older then 5.5.y. I have recently re-imaged my HC4 NAS and everything works perfectly OOB: ___ _ _ _ _ _ ____ _ _ / _ \ __| |_ __ ___ (_) __| | | | | |/ ___| || | | | | |/ _` | '__/ _ \| |/ _` | | |_| | | | || |_ | |_| | (_| | | | (_) | | (_| | | _ | |___|__ _| \___/ \__,_|_| \___/|_|\__,_| |_| |_|\____| |_| Welcome to Armbian 22.08.8 Jammy with Linux 5.19.17-meson64 System load: 2% Up time: 13 days 21:42 Memory usage: 58% of 3.70G IP: 10.0.60.7 CPU temp: 49°C Usage of /: 12% of 15G RX today: 1.2 GiB ZFS pool: Online odroidhc4:~:# modinfo wireguard filename: /lib/modules/5.19.17-meson64/kernel/drivers/net/wireguard/wireguard.ko.xz alias: net-pf-16-proto-16-family-wireguard alias: rtnl-link-wireguard Ofc you can go several steps back and assemble image from raw Debian and generic ARM Linux kernel. But you will probably certainly run into more troubles.
  13. You can. But until this is resolved, it works (well) only in Ubuntu userland as we build with Ubuntu compilers.
×
×
  • Create New...