From: dkwo <dkwo@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [ISSUE] [CLOSED] eth0: link not detected/ready
Date: Wed, 12 Apr 2023 18:04:21 +0200 [thread overview]
Message-ID: <20230412160421.XOPW9iy1-MHHazQwPO9lV2IZnxbVNMxrTqxNf1Fh0Kg@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-43148@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 2779 bytes --]
Closed issue by dkwo on void-packages repository
https://github.com/void-linux/void-packages/issues/43148
Description:
### Is this a new report?
Yes
### System Info
Void 6.2.8_1 x86_64-musl GenuineIntel uptodate rrnFFFFFFFFF
### Package(s) Affected
I wish I knew
### Does a report exist for this bug with the project's home (upstream) and/or another distro?
_No response_
### Expected behaviour
eth0 is up
### Actual behaviour
eth0 has no-carrier
### Steps to reproduce
the ethernet cable is attached to monitor, which is connected via usb cable to lenovo dock, to which laptop is connected.
with void installer: eth0 is up
with my system: eth0 has no-carrier
relevant dmesg:
```
[ 2.811695] usb 2-4.2.1.2: new SuperSpeed USB device number 5 using xhci_hcd
[ 2.825807] usb 2-4.2.1.2: New USB device found, idVendor=0bda, idProduct=8153, bcdDevice=33.00
[ 2.825823] usb 2-4.2.1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=6
[ 2.825830] usb 2-4.2.1.2: Product: USB 10/100/1000 LAN
[ 2.825835] usb 2-4.2.1.2: Manufacturer: Realtek
[ 2.825839] usb 2-4.2.1.2: SerialNumber: 0033000001
[ 25.821484] usbcore: registered new interface driver cdc_ether
[ 26.220409] cdc_ncm 2-4.2.1.2:2.0: MAC-Address: XXX
[ 26.220422] cdc_ncm 2-4.2.1.2:2.0: setting rx_max = 16384
[ 26.220657] cdc_ncm 2-4.2.1.2:2.0: setting tx_max = 16384
[ 26.221487] cdc_ncm 2-4.2.1.2:2.0 eth0: register 'cdc_ncm' at usb-0000:00:14.0-4.2.1.2, CDC NCM (NO ZLP), XXX
[ 26.221651] usbcore: registered new interface driver cdc_ncm
[ 26.228984] usbcore: registered new interface driver cdc_wdm
[ 26.230680] usbcore: registered new interface driver cdc_mbim
```
with XXX being the actual mac
```
$ ip link
4: eth0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast state DOWN mode DEFAULT group default qlen 1000
link/ether XXX brd ff:ff:ff:ff:ff:ff
```
i tried downgrading the kernel, linux-firmware, using dracut: same issue.
compared to installer, i'm using booster initramfs, booting from efistub
```
$ ls /var/service
acpid agetty-tty2 agetty-tty4 agetty-tty6 cronie nanoklogd runsvdir-dkwo socklog-unix udevd
agetty-tty1 agetty-tty3 agetty-tty5 chronyd dhcpcd pipewire seatd tlp wpa_supplicant
$ cat /etc/xbps.d/ignore.conf
ignorepkg=sudo
ignorepkg=dracut
ignorepkg=dbus
$ cat /etc/booster.yaml
busybox: true
enable_lvm: true
modules: i915
modules_force_load: usbkbd
$ cat /etc/default/efibootmgr-kernel-hook
# Options for the kernel hook script installed by the efibootmgr package.
MODIFY_EFI_ENTRIES=1
OPTIONS="loglevel=4 rd.luks.name=(actual uuid)=cryptroot root=/dev/cryptroot/root rd.luks.options=discard"
DISK="/dev/nvme0n1"
PART=1
```
Any ideas?
prev parent reply other threads:[~2023-04-12 16:04 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-31 21:48 [ISSUE] eth0 has no-carrier dkwo
2023-03-31 22:03 ` dkwo
2023-04-01 15:43 ` eth0 does not become ready dkwo
2023-04-03 19:02 ` dkwo
2023-04-03 19:51 ` dkwo
2023-04-03 19:51 ` dkwo
2023-04-03 20:12 ` eth0: link not ready dkwo
2023-04-03 20:13 ` dkwo
2023-04-03 20:14 ` dkwo
2023-04-03 20:33 ` dkwo
2023-04-03 23:03 ` eth0: link not detected/ready dkwo
2023-04-12 16:04 ` dkwo
2023-04-12 16:04 ` dkwo [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20230412160421.XOPW9iy1-MHHazQwPO9lV2IZnxbVNMxrTqxNf1Fh0Kg@z \
--to=dkwo@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).