1. Forum
  2. Usenet
  3. LINUX.DEBIAN.PORTS.ARM

  • Re: device name changed after upgrade to bookworm [was: Cubox-i bullsey

    From Fan Naibed@21:1/5 to Rainer Dorsch on Thu Sep 28 05:30:01 2023
    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 that helps somebody to debug his network issues.

    Rainer

    I hope that helps somebody to debug his network issues.

    Rainer, Thank you very much for reporting your issue and workaround fix.

    A couple days ago I had the same network issue after upgrading Debian
    testing on Pine64 H64B (previous discussion: https://lists.debian.org/debian-arm/2021/09/msg00001.html ). This is an
    arm64 system. I was eventually able to get it running Debian testing,
    but it had later stopped responding to remote logins after an upgrade
    some weeks or months ago. So a couple days ago, I finally connected it
    to a monitor and saw it was dropping to "emergency mode" when rebooted.
    Oddly, logging in as root, doing essentially nothing except looking at
    logs, df -h, etc, then continuing, it ran OK long enough to do an
    upgrade that ran into the renamed ethernet interface issue. The good
    news is: After renaming from eth0 to end0 in interfaces, ethernet worked
    again. The bad news is: After upgrading another time, the system drops
    to "emergency mode" after every reboot. I haven't had time to find
    anything obvious in logs, or to add a comment to your bug report.

    I have several other headless SBCs, mostly raspberry pis from 1 through
    4. After getting them all running Debian testing, they have all slowly
    stopped responding over the network after upgrades. One of them, also
    just checked with a display, acts like it has a bad sd card, but I
    expect others may be having this renamed interface issue, because they
    were all originally set up with the same interfaces file using "eth0",
    IIRC.

    I know it's called "testing" for a reason, but for the most part my
    experiences with testing on x86_64 desktop systems has been much more
    stable, probably because network "just worked" without hand file
    editing. :)

    I'll be looking for better ways of setting up headless SBCs if anyone
    has good pointers. Thanks!

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Rainer Dorsch@21:1/5 to All on Fri Sep 29 22:10:01 2023
    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 and since I use it, I never had to connect a monitor anymore. Works particular well, if you have two devices nearby, then you can use one device to monitor the serial console of the other device. Even if you don't have the second device, transporting and connecting a small second device is typically ways easier than carring around and connecting a monitor and keyboard. The requirement is certainly that your device has a serial interface, but many do have that.

    I typically use

    busybox microcom -d 20 -s 115200 /dev/ttyUSB0

    but there are also other serial console tools.

    Hope that helps
    Rainer

    --
    Rainer Dorsch
    http://bokomoko.de/

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)