| Summary: | IPFire with aarch64 processor won't boot after upgrading to 177 | ||
|---|---|---|---|
| Product: | IPFire | Reporter: | Roberto Peña <contacto> |
| Component: | --- | Assignee: | Assigned to nobody - feel free to grab it and work on it <nobody> |
| Status: | CLOSED NOTABUG | QA Contact: | |
| Severity: | Crash | ||
| Priority: | - Unknown - | CC: | adolf.belka, arne.fitzenreiter, michael.tremer |
| Version: | 2 | Flags: | adolf.belka:
needinfo+
|
| Hardware: | aarch64 | ||
| OS: | Unspecified | ||
| Attachments: |
Boot Log file
Working boot on NanoPi R4S after upgrade from core164 |
||
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. 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. Created attachment 1250 [details]
Working boot on NanoPi R4S after upgrade from core164
Is this bug still valid with Core Update 182? 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. |
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.