Re: device name changed after upgrade to bookworm [was: Cubox-i bullseye -> bookworm Upgrade failure]

2023-09-29 Thread Rainer Dorsch
Am Donnerstag, 28. September 2023, 05:23:39 CEST schrieb Fan Naibed: > I'll be looking for better ways of setting up headless SBCs if anyone > has good pointers. Thanks! I have a cubox-i and use a serial console to access debug output. This makes me independent of any network connection at least

Re: device name changed after upgrade to bookworm [was: Cubox-i bullseye -> bookworm Upgrade failure]

2023-09-27 Thread Fan Naibed
On 2023-08-04 10:01, Rainer Dorsch wrote: I found the root cause of the issue myself: In /etc/network/interfaces I had to replace eth0 with end0: # The primary network interface allow-hotplug eth0 iface eth0 inet dhcp # This is an autoconfigured IPv6 interface iface eth0 inet6 auto I hope tha

Re: Cubox-i bullseye -> bookworm Upgrade failure

2023-08-30 Thread Rainer Dorsch
Am Dienstag, 29. August 2023, 17:24:30 CEST schrieb Steve Langasek: > On Tue, Aug 29, 2023 at 02:38:20PM +0200, Rainer Dorsch wrote: > > Am Dienstag, 15. August 2023, 21:31:50 CEST schrieb Steve Langasek: > > > > How about alerting end-user that "did you know your interface name > > > > will change

Re: Cubox-i bullseye -> bookworm Upgrade failure

2023-08-29 Thread Steve Langasek
On Tue, Aug 29, 2023 at 02:38:20PM +0200, Rainer Dorsch wrote: > Am Dienstag, 15. August 2023, 21:31:50 CEST schrieb Steve Langasek: > > > How about alerting end-user that "did you know your interface name > > > will change after the reboot thus possibly breaking your network > > > configuration?".

Re: Cubox-i bullseye -> bookworm Upgrade failure

2023-08-29 Thread Rainer Dorsch
Am Dienstag, 15. August 2023, 21:31:50 CEST schrieb Steve Langasek: > > How about alerting end-user that "did you know your interface name > > will change after the reboot thus possibly breaking your network > > configuration?". I heard there are certain Release Notes that were used > > to say thin

Re: Cubox-i bullseye -> bookworm Upgrade failure

2023-08-15 Thread Paul Wise
On Fri, 2023-08-04 at 10:55 +0300, Reco wrote: > Enjoy your (un)Predictable Interface Names. > Try adding "net.ifnames=0" to kernel's commandline. Personally, I would switch away from hardcoding interface names. ifupdown can do interface name wildcards and mac matching. The other solutions for t

Re: Cubox-i bullseye -> bookworm Upgrade failure

2023-08-15 Thread Steve Langasek
On Mon, Aug 14, 2023 at 08:02:32AM +0300, Reco wrote: > On Sun, Aug 13, 2023 at 04:53:13PM -0500, Steve Langasek wrote: > > On Fri, Aug 04, 2023 at 10:55:44AM +0300, Reco wrote: > > > On Fri, Aug 04, 2023 at 08:55:21AM +0200, Rainer Dorsch wrote: > > > > dmesg reports for end0: > > > > [7.77180

Re: Cubox-i bullseye -> bookworm Upgrade failure

2023-08-13 Thread Reco
Hi. On Sun, Aug 13, 2023 at 04:53:13PM -0500, Steve Langasek wrote: > On Fri, Aug 04, 2023 at 10:55:44AM +0300, Reco wrote: > > On Fri, Aug 04, 2023 at 08:55:21AM +0200, Rainer Dorsch wrote: > > > dmesg reports for end0: > > > [7.771809] fec 2188000.ethernet eth0: registered PHC device

Re: Cubox-i bullseye -> bookworm Upgrade failure

2023-08-13 Thread Steve Langasek
On Fri, Aug 04, 2023 at 10:55:44AM +0300, Reco wrote: > On Fri, Aug 04, 2023 at 08:55:21AM +0200, Rainer Dorsch wrote: > > dmesg reports for end0: > > [7.771809] fec 2188000.ethernet eth0: registered PHC device 0 > > [7.942031] fec 2188000.ethernet end0: renamed from eth0 > Enjoy your (un)

Re: Cubox-i bullseye -> bookworm Upgrade failure

2023-08-07 Thread Rainer Dorsch
Am Freitag, 4. August 2023, 09:57:18 CEST schrieb RobJE Debian ARM: > Hi, > > On 04-08-2023 08:55, Rainer Dorsch wrote: > > Hi, > > > > I did a test installation with a bullseye installer on a cubox-i and then > > upgraded to bookworm. After the upgrade the network was gone. Even booting > > with

device name changed after upgrade to bookworm [was: Cubox-i bullseye -> bookworm Upgrade failure]

2023-08-04 Thread Rainer Dorsch
Hi, I found the root cause of the issue myself: In /etc/network/interfaces I had to replace eth0 with end0: # The primary network interface allow-hotplug eth0 iface eth0 inet dhcp # This is an autoconfigured IPv6 interface iface eth0 inet6 auto I hope that helps somebody to debug his network is

Re: Cubox-i bullseye -> bookworm Upgrade failure

2023-08-04 Thread Reco
Hi. On Fri, Aug 04, 2023 at 08:55:21AM +0200, Rainer Dorsch wrote: > dmesg reports for end0: > [7.771809] fec 2188000.ethernet eth0: registered PHC device 0 > [7.942031] fec 2188000.ethernet end0: renamed from eth0 Enjoy your (un)Predictable Interface Names. Try adding "net.ifname

Re: Cubox-i bullseye -> bookworm Upgrade failure

2023-08-04 Thread RobJE Debian ARM
Hi, On 04-08-2023 08:55, Rainer Dorsch wrote: Hi, I did a test installation with a bullseye installer on a cubox-i 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. Any hints and ideas a

Cubox-i bullseye -> bookworm Upgrade failure

2023-08-04 Thread Rainer Dorsch
Hi, I did a test installation with a bullseye installer on a cubox-i 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. Any hints and ideas are welcome. root@test-machine:~# uname -a Linu