Hello,
I have a Kohjinsha SA1F00A UMPC (from 2007!) with the following specs:
AMD Geode LX800 @ 550 MHz
1 GB RAM (not upgradable)
30 GB HD
It formerly had Windows 95 on it, but obviously that wasn't going to
last, so I chose Alpine because of its long history with older
hardware. I first installed Alpine 3.10 with no issues, then upgraded
to 3.12 when it was available.
Rock solid on 3.12 since 2020.
Yesterday, being bored, I decided to make a change and upgrade to the
latest version (3.18). That was a mistake.
After the upgrade and subsequent reboot, I got the "This kernel requires
the following features" error listing "pae" as the culprit.
I downloaded the x86 ISO for Alpine 3.17 extended and installed that and
it worked again. Then, since I was already blasting away OS versions, I
figured what the hell and upgraded to edge and then rebooted.
Same error.
What happened between 3.17 and 3.18/edge that this error is now
prevalent? Is there something I can do to remediate this, or am I stuck
at 3.17 for the foreseeable future?
On Tue Jun 13, 2023 at 10:47 PM CEST, Paul Gallegos wrote:
> Hello,
>
> I have a Kohjinsha SA1F00A UMPC (from 2007!) with the following specs:
> AMD Geode LX800 @ 550 MHz
> 1 GB RAM (not upgradable)
> 30 GB HD
>
>
> It formerly had Windows 95 on it, but obviously that wasn't going to
> last, so I chose Alpine because of its long history with older
> hardware. I first installed Alpine 3.10 with no issues, then upgraded
> to 3.12 when it was available.
>
> Rock solid on 3.12 since 2020.
>
>
> Yesterday, being bored, I decided to make a change and upgrade to the
> latest version (3.18). That was a mistake.
>
> After the upgrade and subsequent reboot, I got the "This kernel requires
> the following features" error listing "pae" as the culprit.
sounds like https://gitlab.alpinelinux.org/alpine/aports/-/commit/ea95865daefe76f6fa92806f747e98e829320d32
broke it
>
> I downloaded the x86 ISO for Alpine 3.17 extended and installed that and
> it worked again. Then, since I was already blasting away OS versions, I
> figured what the hell and upgraded to edge and then rebooted.
>
> Same error.
>
>
> What happened between 3.17 and 3.18/edge that this error is now
> prevalent? Is there something I can do to remediate this, or am I stuck
> at 3.17 for the foreseeable future?