dudepron

  • Posts

    9
  • Joined

  • Last visited

dudepron's Achievements

  1. I've tried without and with --no-allow-insecure-repositories and --allow-unauthenticated Cert issue on the remote? ns1@ns1:~$ sudo apt-get update Hit:1 http://security.debian.org buster/updates InRelease Hit:2 http://httpredir.debian.org/debian buster InRelease Hit:3 http://httpredir.debian.org/debian buster-updates InRelease Ign:4 https://apt.armbian.com buster InRelease Err:5 https://apt.armbian.com buster Release Redirection from https to 'http://armbian.tnahosting.net/apt/dists/buster/Release' is forbidden [IP: 173.45.128.12 443] Reading package lists... Done E: The repository 'https://apt.armbian.com buster Release' no longer has a Release file. N: Updating from such a repository can't be done securely, and is therefore disabled by default. N: See apt-secure(8) manpage for repository creation and user configuration details. ns1@ns1:~$ sudo apt-get update --no-allow-insecure-repositories Hit:1 http://security.debian.org buster/updates InRelease Hit:2 http://httpredir.debian.org/debian buster InRelease Hit:3 http://httpredir.debian.org/debian buster-updates InRelease Ign:4 https://apt.armbian.com buster InRelease Err:5 https://apt.armbian.com buster Release Redirection from https to 'http://armbian.tnahosting.net/apt/dists/buster/Release' is forbidden [IP: 173.45.128.12 443] Reading package lists... Done E: The repository 'https://apt.armbian.com buster Release' no longer has a Release file. N: Updating from such a repository can't be done securely, and is therefore disabled by default. N: See apt-secure(8) manpage for repository creation and user configuration details. ns1@ns1:~$ sudo apt-get update --allow-unauthenticated Hit:1 http://security.debian.org buster/updates InRelease Hit:2 http://httpredir.debian.org/debian buster InRelease Hit:3 http://httpredir.debian.org/debian buster-updates InRelease Ign:4 https://apt.armbian.com buster InRelease Err:5 https://apt.armbian.com buster Release Redirection from https to 'http://armbian.tnahosting.net/apt/dists/buster/Release' is forbidden [IP: 173.45.128.12 443] Reading package lists... Done E: The repository 'https://apt.armbian.com buster Release' no longer has a Release file. N: Updating from such a repository can't be done securely, and is therefore disabled by default. N: See apt-secure(8) manpage for repository creation and user configuration details. ns1@ns1:~$
  2. I was able to get uboot updated. I copied the files from here https://apt.armbian.com/pool/main/l/linux-5.3.1-cubox/ to my SD card. I am getting closer. Oh, this is a buster server deployment if that matters. This is what I get now... I have armbianEnv.txt with ``` verbosity=1 rootdev=/dev/mmcblk0p1 rootfstype=ext4 ``` ``` U-Boot SPL 2018.01-armbian (Sep 27 2019 - 23:10:03) Trying to boot from MMC1 U-Boot 2018.01-armbian (Sep 27 2019 - 23:10:03 +0200) CPU: Freescale i.MX6Q rev1.5 996 MHz (running at 792 MHz) CPU: Extended Commercial temperature grade (-20C to 105C) at 35C Reset cause: POR Board: MX6 Cubox-i Watchdog enabled DRAM: 2 GiB MMC: FSL_SDHC: 0, FSL_SDHC: 1 auto-detected panel HDMI Display: HDMI (1024x768) In: serial Out: serial Err: serial Net: FEC starting USB... USB0: Port not available. USB1: USB EHCI 1.00 scanning bus 1 for devices... 1 USB Device(s) found scanning usb for storage devices... 0 Storage Device(s) found Hit any key to stop autoboot: 0 switch to partitions #0, OK mmc0 is current device Scanning mmc 0:1... Found U-Boot script /boot/boot.scr 1845 bytes read in 132 ms (12.7 KiB/s) ## Executing script at 12000000 0 bytes read in 101 ms (0 Bytes/s) 51 bytes read in 120 ms (0 Bytes/s) 37518 bytes read in 5767 ms (5.9 KiB/s) ** File not found /boot/uInitrd ** ** Unrecognized filesystem type ** ** File not found uInitrd ** 5263872 bytes read in 408 ms (12.3 MiB/s) Wrong Ramdisk Image Format Ramdisk image is corrupt or invalid SCRIPT FAILED: continuing... MMC: no card present mmc_init: -123, time 48 Device 0: device type unknown ... is now current device ** Bad device usb 0 ** ** Bad device usb 0 ** AHCI 0001.0300 32 slots 1 ports 3 Gbps 0x1 impl SATA mode flags: ncq stag pm led clo only pmp pio slum part No port device detected! Device 0: Model: Firm: Ser#: Type: Hard Disk Capacity: not available ... is now current device ** Bad device size - sata 0 ** FEC Waiting for PHY auto negotiation to complete........ ```
  3. I can access the device via Uboot, but just cannot get the image to load.
  4. Recent upgrade to armbian (5.3.1) on my Cubox has left it unbootable. It appears that it is looking for the older version of the boot image (5.1.6 IIRC) and says that is unable to find a flattened device tree. I tired to copy the files from a new SD install of 5.3.1 to the /boot and that didn't seem to work either. I am not sure if this is an old Uboot (2013?) and a new image or what. What is the best way to recover without losing my data on the SD?
  5. Thanks for the quick response.
  6. Just upgraded to the new Jessie image 4.4.1. Is there any concern with this bad CRC warning? Do I need to update the u-boot.img? If so, how. U-Boot SPL 2013.10-rc4 (Feb 03 2016 - 16:37:42) Boot Device: SD1 spl: error reading image u-boot.img, err - -1 Load image from RAW... U-Boot 2013.10-rc4 (Feb 03 2016 - 16:37:42) CPU: Freescale i.MX6Q rev1.5 at 792 MHz Reset cause: POR Board: MX6-CuBox-i DRAM: 2 GiB MMC: FSL_SDHC: 0 *** Warning - bad CRC, using default environment In: serial Out: serial Err: serial Net: FEC [PRIME] Hit any key to stop autoboot: 0 mmc0 is current device ** File not found /boot.scr ** ** File not found /uEnv.txt ** ** File not found /zImage ** ** File not found /uImage ** 563 bytes read in 131 ms (3.9 KiB/s) Running bootscript from mmc ... ## Executing script at 10800000 33996 bytes read in 252 ms (130.9 KiB/s) 4325272 bytes read in 342 ms (12.1 MiB/s) Kernel image @ 0x10800000 [ 0x000000 - 0x41ff98 ] ## Flattened Device Tree blob at 18000000 Booting using the fdt blob at 0x18000000 Using Device Tree in place at 18000000, end 1800b4cb Starting kernel ... Uncompressing Linux... done, booting the kernel. Debian GNU/Linux 8 cubox-i ttymxc0 cubox-i login