It may not be a good title for this post, but it causes me a lot of problems…
I have in a Client a NanoPI R1S-H3 which asked to update to 166.
My mind said not to update it, put a 500 in the “/opt/pakfire/db/core/mine” file and then there would be no update warnings.
Big mistake.
Due to the IPS error (all the time trying to finish an endless task, I had the 164), my heart acted.
Now I don’t have access to IPFire.
32Bit?
I don’t know. For future sailors…
I have tried to do a clean installation of 166 and I get the following. And from there, it doesn’t happen:
U-Boot SPL 2021.07 (Mar 31 2022 - 14:39:26 +0000)
DRAM: 512 MiB
Trying to boot from MMC1
U-Boot 2021.07 (Mar 31 2022 - 14:39:26 +0000) OrangePi Zero - IPFire.org
CPU: Allwinner H3 (SUN8I 1680)
Model: Xunlong Orange Pi Zero
DRAM: 512 MiB
MMC: mmc@1c0f000: 0, mmc@1c10000: 2
Loading Environment from FAT... *** Warning - bad CRC, using default environment
In: serial
Out: serial
Err: serial
Net: phy interface0
eth0: ethernet@1c30000
starting USB...
Bus usb@1c1a000: USB EHCI 1.00
Bus usb@1c1a400: USB OHCI 1.0
Bus usb@1c1b000: USB EHCI 1.00
Bus usb@1c1b400: USB OHCI 1.0
scanning bus usb@1c1a000 for devices... 1 USB Device(s) found
scanning bus usb@1c1a400 for devices... 1 USB Device(s) found
scanning bus usb@1c1b000 for devices... 2 USB Device(s) found
scanning bus usb@1c1b400 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.scr
2514 bytes read in 2 ms (1.2 MiB/s)
## Executing script at 43100000
114 bytes read in 1 ms (111.3 KiB/s)
Load uEnv.txt...
...
Set console to ttyS0,115200
5851160 bytes read in 270 ms (20.7 MiB/s)
24335 bytes read in 7 ms (3.3 MiB/s)
7396356 bytes read in 341 ms (20.7 MiB/s)
Ramdisk loaded...
Kernel image @ 0x42000000 [ 0x000000 - 0x594818 ]
## Loading init Ramdisk from Legacy Image at 43400000 ...
Image Name:
Image Type: ARM Linux RAMDisk Image (lzma compressed)
Data Size: 7396292 Bytes = 7.1 MiB
Load Address: 00000000
Entry Point: 00000000
Verifying Checksum ... OK
## Flattened Device Tree blob at 43000000
Booting using the fdt blob at 0x43000000
EHCI failed to shut down host controller.
Loading Ramdisk to 498f2000, end 49fffbc4 ... OK
Using Device Tree in place at 43000000, end 43008f0e
Starting kernel ...
U-Boot SPL 2021.07 (Mar 31 2022 - 14:39:26 +0000)
DRAM: 512 MiB
Trying to boot from MMC1
U-Boot 2021.07 (Mar 31 2022 - 14:39:26 +0000) OrangePi Zero - IPFire.org
CPU: Allwinner H3 (SUN8I 1680)
Model: Xunlong Orange Pi Zero
DRAM: 512 MiB
MMC: mmc@1c0f000: 0, mmc@1c10000: 2
Loading Environment from FAT... *** Warning - bad CRC, using default environment
In: serial
Out: serial
Err: serial
Net: phy interface0
eth0: ethernet@1c30000
starting USB...
Bus usb@1c1a000: USB EHCI 1.00
Bus usb@1c1a400: USB OHCI 1.0
Bus usb@1c1b000: USB EHCI 1.00
Bus usb@1c1b400: USB OHCI 1.0
scanning bus usb@1c1a000 for devices... 1 USB Device(s) found
scanning bus usb@1c1a400 for devices... 1 USB Device(s) found
scanning bus usb@1c1b000 for devices... 2 USB Device(s) found
scanning bus usb@1c1b400 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.scr
2514 bytes read in 2 ms (1.2 MiB/s)
## Executing script at 43100000
114 bytes read in 1 ms (111.3 KiB/s)
Load uEnv.txt...
...
Set console to ttyS0,115200
5851160 bytes read in 270 ms (20.7 MiB/s)
24335 bytes read in 7 ms (3.3 MiB/s)
7396356 bytes read in 341 ms (20.7 MiB/s)
Ramdisk loaded...
Kernel image @ 0x42000000 [ 0x000000 - 0x594818 ]
## Loading init Ramdisk from Legacy Image at 43400000 ...
Image Name:
Image Type: ARM Linux RAMDisk Image (lzma compressed)
Data Size: 7396292 Bytes = 7.1 MiB
Load Address: 00000000
Entry Point: 00000000
Verifying Checksum ... OK
## Flattened Device Tree blob at 43000000
Booting using the fdt blob at 0x43000000
EHCI failed to shut down host controller.
Loading Ramdisk to 498f2000, end 49fffbc4 ... OK
Using Device Tree in place at 43000000, end 43008f0e
Starting kernel ...
It scares me more and more to update the machines (with all due respect to the work of the developers, without underestimating the work done).
Greetings.
Hi,
while I don’t expect this to cause any damage, silencing update warnings this way does not sound like a good idea to me as well.
What do you mean by that? To my understanding, the NanoPi’s sould be 64-bit ARM.
Aside from this, your issue reads very much like a couple of bug reports (#12680, #12684, #12771) related to boot loops or boot troubles on some ARM devices. Not running these, I am unfortunately not really able to help you substantially, aside from noting that we need to update u-boot.
I can absolutely understand that, and usually also update remote machines after proving a Core Update runs stable for a day or two on systems I have physical access to.
With ARM devices currently making up less than two percent of all IPFire installations, and the IPFire project running really low on manpower for quite some time (which is also the reason why, much to my dismay, no progress regarding IPFire 3.x has been made recently 
), we really rely on testing feedback from the community for this architecture.
So: Thank you for testing Core Updates, that really helps to spot flaws before they are being shipped.
Thanks, and best regards,
Peter Müller
Hi,
well, this one boils down to this issue as well.
Sorry for the inconvenience, and best regards,
Peter Müller