Can't connect via SSH

[dKenGuru]

Raspberry Pi Zero2 W and Ethernet adapter via USB.
Flashed SD by alpine-rpi-3.23.3-aarch64.img. Moved headless.apkovl.tar.gz root of this microSD card. Edit usercfg.txt and cmdline.txt. Zero2 get IP from router DHCP. But I can't get SSH connection.

[macmpi]

Hi,

Moved headless.apkovl.tar.gz root of this microSD card

It must be a-is at root of SD: do not uncompress.

Unsure why you need to modify default usercfg.txt and cmdline.txt: can you provide?
Which chipset/driver does your usb-ethernet dongle uses? Have you checked it is part of kernel config?
If not built-in, it may need to be loaded (modules=xxx in cmdline.txt).
Have you tried over wifi by supplying wpa_supplicant.conf also? This may help debug the ethernet side.

[dKenGuru]

It is not uncompress. Just archive.
usercfg.txt

dtoverlay=dwc2

cmdline.txt

modules=loop,squashfs,sd-mod,usb-storage modules-load=dwc2,g_ether quiet console=tty1

It's works fine with DietPi. But now want to try Alpine. Zero2W get IP from router and bound it. So connection is working. But SSH is unavailable.

[macmpi]

ok, you seem to be mixing-up few things maybe.

• DietPi is Debian based (like PiOS), which Alpine is not: some conventions are different, in particular modules-load= statement in config.txt, which is modules= in Alpine. (Alpine wiki is a good source of info, as there is a leaning curve to fully leverage Alpine: very worth it!)
• Anyhow (guessing from your changes), you likely intend to use ethernet usb-gadget, not a usb-ethernet dongle, right ? Then stick to directions from this project README, and do not mix with how you did things on DietPi or else. (no need to alter cmdline.txt at all and dtoverlay statement in incomplete in usercfg.txt. Also in that mode, IP address will be 10.42.0.2 (no DHCP) and host side must be in same sub-network (typically 10.42.0.1).

[dKenGuru]

I try to use microUSB to Ethernet adapter.
Remove any lines in usercfg.txt.
cmdline.txt

modules=loop,squashfs,sd-mod,usb-storage,dwc2,g_ether quiet console=tty1

Zero2 get IP, I can login via SSH, but after some seconds it drops me and I cant login again. Reboots does not help. Zero2 can't bound any IP.

[macmpi]

I try to use microUSB to Ethernet adapter.

Which one? Which chipset/driver?

dwc2,g_ether

why this? Seems irrelevant/erroneous

Have you tried wifi interface?

[dKenGuru]

Which one? Which chipset/driver?

I don't know. It's simple adapter with microUSB from one side, and RJ45 from other. And it is perfect working on Pi OS or DietPi with additional lines in cmdline.txt and usercfg.txt.

So I need same scenario with Alpine. Zero2 must get IP from router DHCP and available via Ethernet adapter connected to microUSB.
I don't understand, why Zero2 bound IP from router, but not accessible via SSH. Or why it was, but drop me after some seconds and no more connected via SSH.

why this? Seems irrelevant/erroneous

What must be there? https://trac.gateworks.com/wiki/linux/OTG#USBDeviceMode

[macmpi]

What must be there? https://trac.gateworks.com/wiki/linux/OTG#USBDeviceMode

To clarify, you are in either 2 cases below (NOT both), depending on the cable/peripheral you use to connect Pi device:

1. USB-gadget mode, eventually supporting ethernet (over plain USB cable) feature (ref that page you quoted, that starts with: A Device mode cable allows connection to a USB host such as a PC):
   USB cable sockets on both ends, connecting PiZero USB to host computer USB: then dwc2 and g_ether may somehow make sense (with caviars here as ALHB transparently takes care of that on its own).
2. USB-ethernet adapter/dongle (USB on one end, ethernet port on the other end: has electronic components inside): then kernel must have proper driver for that peripheral device. Maybe it is mainstream ASIX/Realtek or other which are well supported by default...maybe not: anyhow g_ether is not relevant and dwc2 may be counterproductive in some circumstances.

So, based on peripheral you use, I assume you are in case 2: can you confirm (eventually attach a picture)?
If so, please remove dwc2 and g_ether statements anywhere, or your device may be in some improper configuration.
Just use default Alpine release's config.txt/cmdline.txt (and no usercfg.txt) to start with, without any own customization, and let's see & report how it goes.

Again, is there anything preventing you from using Pi wifi interface?
While I understand you want to use the USB dongle, wifi may temporarily help figure-out issues by debugging on that other interface over SSH.

[macmpi]

Had a chance to test with some Realtek r8152 based USB-ethernet dongle on a PiZeroW, and it works fine with default files (no dwc2 and g_ether involvement).
In such usecase, enabling dwc2 without explicit dr_mode=host option may generate some conflicts (inadequate mode detection) depending on cable/USB port wiring on PiZeroW (replicated original issues with dwc2 alone). Anyhow there is no reason to prefer dwc2 over default dwc_otg usb driver in that scenario.
So KISS rule applies: just use default files and roll.
(I'd bet you may not need to load those drivers on PiOS or DietPi either...).

[dKenGuru]

Ah, thx! Try USB-Ethernet adapter without any additional settings and it woks out of box. Successfully install Alpine.
Sorry for this ticket.

[macmpi]

Glad it helped.
Feel free to mark the helping answer (may help others) an close discussion.
Have fun with Alpine!