Bug 13239 - IPFire with aarch64 processor won't boot after upgrading to 177
Summary: IPFire with aarch64 processor won't boot after upgrading to 177
Status: CLOSED NOTABUG
Alias: None
Product: IPFire
Classification: Unclassified
Component: --- (show other bugs)
Version: 2
Hardware: aarch64 Unspecified
: - Unknown - Crash
Assignee: Assigned to nobody - feel free to grab it and work on it
QA Contact:
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2023-08-08 06:21 UTC by Roberto Peña
Modified: 2024-06-10 09:13 UTC (History)
3 users (show)

See Also:
adolf.belka: needinfo+

Attachments
Boot Log file (20.90 KB, text/plain)
2023-08-08 06:21 UTC, Roberto Peña 		Details
Working boot on NanoPi R4S after upgrade from core164 (30.54 KB, text/plain)
2023-08-08 16:41 UTC, Arne.F 		Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Roberto Peña 2023-08-08 06:21:40 UTC 
Created attachment 1249 [details]
Boot Log file

aarch64 with the CU176 working correctly is updated without any apparent problem to the CU177 and no longer boots.
Comment 1 Arne.F 2023-08-08 07:18:37 UTC 
I have last tested the update to https://git.ipfire.org/?p=ipfire-2.x.git;a=commit;h=d95a414ce12306762849b4df8a50ddd18a838129 from pakfire testing
which works on my OrangePi R1 Plus LTS. (RK3328)

I have not found relevant changes to the final version yet.
Comment 2 Arne.F 2023-08-08 16:30:36 UTC 
I cannot reproduce this problem with the final core177 build.

I have tested a fresh install on RPi3, RPi4, OrangePi R1 Plus LTS and NanoPi R4S and also the update on NanoPi R4S from core164.
Comment 3 Arne.F 2023-08-08 16:41:18 UTC 
Created attachment 1250 [details]
Working boot on NanoPi R4S after upgrade from core164
Comment 4 Adolf Belka 2024-01-24 13:28:21 UTC 
Is this bug still valid with Core Update 182?
Comment 5 Adolf Belka 2024-06-10 09:13:56 UTC 
As there has been no further feedback in the last 5 months it looks like this is not a bug with CU182 to CU185.

It has been marked as not being a bug.

If this is incorrect and the issue still exists thne the bug can be re-opened and the required information provided.