Hi Justin,
thanks for the elaborate followup.
Just a few quick answers:
> Did the installer give you a 70-persistent-net.rules file? It seems a
> bit of a pointless mechanism for hardware like yours...
I did not check on the test system (on which I installed bullseye and upgraded
to bookworm)
Rainer Dorsch wrote:
>> Are you saying that armhf machines still used one of the old interface
>> naming schemes (https://wiki.debian.org/NetworkInterfaceNames) on
>> bullseye, and hadn't yet switched over to "predictable" names?
>
> That is at least what I observed. I don't have insights, why a
Hi Justin,
many thanks for the quick follow-up.
Am Mittwoch, 30. August 2023, 07:46:04 CEST schrieben Sie:
> Are you saying that armhf machines still used one of the old interface
> naming schemes (https://wiki.debian.org/NetworkInterfaceNames) on
> bullseye, and hadn't yet switched over to "pred
Rainer Dorsch wrote:
> I did a test installation with a bullseye installer on a cubox-i
> (armhf architecture) and then upgraded to bookworm. After the upgrade
> the network was gone. Even booting with the previous kernel
> 5.10.0-23-armmp does not bring the network back.
>
> After some more inves
Package: release-notes
Severity: normal
Dear Maintainer,
I did a test installation with a bullseye installer on a cubox-i
(armhf architecture) and then upgraded to bookworm. After the upgrade
the network was gone. Even booting with the previous kernel
5.10.0-23-armmp does not bring the network ba
5 matches
Mail list logo
