Jump to content

Search the Community

Showing results for 'Hash Sum mismatch'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Armbian
    • Armbian project administration
  • Community
    • Announcements
    • SBC News
    • Framework and userspace feature requests
    • Off-topic
  • Using Armbian
    • Beginners
    • Software, Applications, Userspace
    • Advanced users - Development
  • Standard support
    • Amlogic meson
    • Allwinner sunxi
    • Rockchip
    • Other families
  • Community maintained / Staging
    • TV boxes
    • Amlogic meson
    • Allwinner sunxi
    • Marvell mvebu
    • Rockchip
    • Other families
  • Support

Categories

  • Official giveaways
  • Community giveaways

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


Matrix


Mastodon


IRC


Website URL


XMPP/Jabber


Skype


Github


Discord


Location


Interests

Found 17 results

  1. My system has `linux-image-current-bcm2712` package installed with version 24.2.5 which I believe is the current Arbian release. I installed `linux-headers-current-bcm2712`, but this package has version 24.2.1. So I end up with system running `6.6.23-current-bcm2712` with headers for `6.6.18-current-bcm2712` and I can't build extra drivers in result. Any hints? I love technical forums that don't understand markdown, it makes life so much easier...
  2. Hello fellow Armbian folk, I've been a happy armbian user for many years. Recently, I've been trying to upgrade to bookworm from bullseye on my cubietruck, however have been hampered by Hash Sum mismatch errors from multiple armbian mirrors. I have followed all instructions on clearing the /var/lib/apt/files, apt clean, but nothing seems to help. I've tried multiple armbian mirrors with no luck. So now I'm seeking some community support.
  3. artifact-uboot: include BOOTCONFIG in u-boot artifact version hash artifact-uboot: include BOOTCONFIG in u-boot artifact version hash HOW did we get this far without this? should cause rebuild of all u-boots, hopefully View the full article
  4. kernel drivers: replace all "branch:xxx" references with sha1; hash the whole of patch/misc stacktraces: introduce get_stacktrace_element_by_index() to get a specific stracktrace element git: fetch_from_repo(): introduce FETCH_FROM_REPO_CALLBACK_IF_REF_MUTABLE function defined in FETCH_FROM_REPO_CALLBACK_IF_REF_MUTABLE is called if reference is mutable which is anything that's not commit: or tag: and really there's no guarantee that tag: is immutable, but lets assume drivers-harness: hash the whole of patch/misc; throw error if driver does fetch_from_repo with mutable ref this should make drivers hash consistent, at the expense of being moar tiresome any changes at any patches or drivers-related bash code will cause all kernels to be rebuilt opposed to "some changes caused all kernels to be rebuilt" drivers_network: replace all "branch:xxx" references with sha1; add notice about it AR-1861 View the full article
  5. rockchip-rk3588: add -Wno-error=enum-int-mismatch to u-boot CFLAGS so it builds with gcc 13+ rockchip-rk3588: add -Wno-error=enum-int-mismatch to u-boot CFLAGS so it builds with gcc 13+ this applies to all u-boots in this family View the full article
  6. Please this Error context msg [ Check MD5 sum of installed packages failed ] what is the reason? https://paste.next.armbian.com/gigojaropu
  7. artifact: kernel: force D0000 drivers hash for artifact_version if EXTRAWIFI=no artifact: kernel: force D0000 drivers hash for artifact_version if EXTRAWIFI=no View the full article
  8. artifact-uboot: include more variables into hash, for ATF & rk stuff More vars hashed into u-boot version, mostly for ATF and rk stuff. This will cause a full rebuild of all uboots, but better be safe than sorry. Impact of not having this: certain changes to u-boot in board or family won't be detected. View the full article
  9. Description We don’t need to scare people with displaying odd hash version. Before: _ _ _____ _____ ___ ___ __ | | | | ____| ___|_ _| __ _( _ ) / /_ | | | | _| | |_ | | \ \/ / _ \| '_ \ | |_| | |___| _| | | > < (_) | (_) | \___/|_____|_| |___| /_/\_\___/ \___/ Welcome to Armbian 23.05.0-trunk--1-PC7446-V521e-H1f65-Be6c1 Jammy with Linux 5.15.106-x86 No end-user support: built from trunk After: _ _ _____ _____ ___ ___ __ | | | | ____| ___|_ _| __ _( _ ) / /_ | | | | _| | |_ | | \ \/ / _ \| '_ \ | |_| | |___| _| | | > < (_) | (_) | \___/|_____|_| |___| /_/\_\___/ \___/ Welcome to Armbian 23.05.0-trunk Jammy with Linux 5.15.106-x86 No end-user support: built from trunk Jira reference number AR-1654 How Has This Been Tested? [x] Manual execution Checklist: [x] My code follows the style guidelines of this project [x] I have performed a self-review of my own code [x] I have commented my code, particularly in hard-to-understand areas [ ] I have made corresponding changes to the documentation [x] My changes generate no new warnings [x] Any dependent changes have been merged and published in downstream modules View the full article
  10. artifact-armbian-bsp-cli: hash more variables included in /etc/armbian-release View the full article
  11. Now changes to most variables/hooks affecting u-boot are correctly hashed and changes cause a recompile/cache miss as they should Extra: UBOOT_CONFIGURE=yes experimental, nothing fancy or magic, might be useful for some, does not export patches, only the defconfig bare. Goes a bit crazy if multiple targets (runs and exports twice+). View the full article
  12. I'm getting this error when running apt update (as root): Get:13 https://armbian.hosthatch.com/apt buster/main armhf Packages [592 kB] Err:13 https://armbian.hosthatch.com/apt buster/main armhf Packages Ign:15 https://us.mirrors.fossho.st/armbian/apt buster/main armhf Contents (deb) Fetched 718 kB in 18s (40.9 kB/s) Reading package lists... Done E: Failed to fetch https://armbian.hosthatch.com/apt/dists/buster/main/binary-armhf/Packages.gz E: Failed to fetch https://armbian.tnahosting.net/apt/dists/buster/buster-desktop/Contents-armhf.gz Hash Sum mismatch Hashes of expected file: - Filesize:96109 [weak] - SHA512:85a1dd0e1f1a8717d19b27f557d43a52d66684e2de10136938a14db8c3885e045d4b3844b3e3cca6054374c543237111a950d5d9a73ee5949f90e0db14bc88f6 - SHA256:77d0e508761d7498af6dd22e8187455ad817987dc556cdb3a98620290a6fb85e - SHA1:315817cdcdf715e2975a7b17a7ae48908fd753d7 [weak] - MD5Sum:1b9b596862c66cc1bc43efe3247c3850 [weak] Hashes of received file: - SHA512:eaf8261721500c8bf2060cd5e1b4dc3a8ba2db113d0752491b75c50f30e8292faa705cf1d07c25c38be5462eccaf5ad40b0581e9d8cd1845d24be6ef7e61f9f5 - SHA256:8d69eb084de8f77619f25b57597c496de97b326881a3b1ba97b0f3eefc314734 - SHA1:ddc15dfea93fe6db51059b991a7a7523120a6b96 [weak] - MD5Sum:f9f5009580fae5763565b687213efff6 [weak] - Filesize:96109 [weak] Last modification reported: Fri, 20 Nov 2020 10:41:49 +0000 Release file created at: Tue, 01 Dec 2020 20:39:06 +0000 E: Some index files failed to download. They have been ignored, or old ones used instead. I trimmed the beginning a bit, but I'm pretty sure I left enough context. Does some package source need to re-issue their signatures? Is anyone else having this problem?
  13. Hello. As I try to update my system I get this: E: Failed to fetch https://minio.k-space.ee/armbian/apt/dists/buster/buster-desktop/Contents-armhf.gz Hash Sum mismatch Hashes of expected file: - Filesize:1851 [weak] - SHA512:ef7aab67fc05cc3e30b82f41967566ecef6fad070817c4115867fe23e0368ccb2849acf850f41250a169d95eb6b4dd7dd2cc14e2f1a92244432100cdaf036991 - SHA256:880e52b050d4c7d2fbd0c5058e380455bb51ca313a4d07c7f25ed61edf469050 - SHA1:699022efd6136b78286e76516a096a2cb6a2eea3 [weak] - MD5Sum:a65883df7850b338094dfc9e2c16125a [weak] Hashes of received file: - SHA512:b66793d4c902406157497ee2480ba1a1acd92512df70138d425c952024154e084838c4ff3c05c60bc8418de4f62a17a454b6202b8e77582fc55dbe1be638ef52 - SHA256:49b62e32c4e8174d1171d60f19af2565506d48c1491c056bc81866694848597f - SHA1:13fb2a29e79a613ea13822ea68cb59d477fdc03f [weak] - MD5Sum:9e68d2e35701971733c9258fca78007e [weak] - Filesize:1851 [weak] Last modification reported: Sun, 18 Oct 2020 16:31:58 +0000 Release file created at: Sun, 08 Nov 2020 13:58:39 +0000 Can the repo be out of sync? This got to be fixed.
  14. Hello I'm just wondering that there are two release files in /etc and why they have different VERSION values. In armbian-image-release file, VERSION is 20.08.1 But it is 21.08.8 in armbian-relase file. armbian-config and welcome massages also show version as 21.08.8 So I think 21.08.8 is correct one, but then why armbian-image-release has incorrect version value? Is it a bug? Or am I missing something? Please help me. Thank you.
  15. https://dl.armbian.com/orangepipc/archive/ Armbian_20.02.1_Orangepipc_buster_current_5.4.20_desktop.7z Just checked a fresh buster desktop image. And found a tiny issue. If you will try to install linux-headers-current-sunxi using the latest v20.02.1 image (buster, K5.4.20), you will get the v5.3.9 headers It would be nice to get the v5.4.20 headers instead Quick tip for other users - headers package can be found here - https://apt.armbian.com/pool/main/l/linux-5.4.20-sunxi/
  16. I downloaded the kernel source and kernel headers on a rk3288 rockchip (tinkerboardS) and noticed there was a mismatch between kernel version, armbian release and chipset (rockchip64) - see below. root@tinkerboard:~# uname -a Linux tinkerboard 4.4.174-rockchip #7 SMP Sun Feb 10 11:57:26 CET 2019 armv7l armv7l armv7l GNU/Linux root@tinkerboard:~# cat /etc/armbian-release # PLEASE DO NOT EDIT THIS FILE BOARD=tinkerboard BOARD_NAME="Tinkerboard" BOARDFAMILY=rockchip VERSION=5.75 LINUXFAMILY=rockchip BRANCH=default ARCH=arm IMAGE_TYPE=stable BOARD_TYPE=conf INITRD_ARCH=arm KERNEL_IMAGE_TYPE=zImage root@tinkerboard:/usr/src# ls * linux-rockchip64-default_4.4.178_5.85_config.xz linux-source-4.4.178-rockchip64.tar.xz
  17. Hello i found it on both my Opi PC+ and Opi Plus 2E , Both ARMBIAN 5.59.180918 nightly Debian GNU/Linux 9 (stretch) 4.14.70-sunxi. As i get some stability issues with Jeedom i'm playing with frequencies and governors and found that strange thing : root@orangepipcplus:~# cat /etc/default/cpufrequtils && cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_available_frequencies # WARNING: this file will be replaced on board support package (linux-root-...) upgrade ENABLE=true MIN_SPEED=408000 MAX_SPEED=1296000 GOVERNOR=ondemand 240000 480000 648000 816000 912000 960000 1008000 1104000 1200000 1296000 root@orangepipcplus:~# it seems there is a mismatch between MIN_SPEED=408000 in cpufrequtils and the one returned by scaling_available_frequencies 480000 is it normal or there is an error somewhere. can it be an instability cause ? best regards
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines