From: dkwo <dkwo@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: eth0: link not ready
Date: Mon, 03 Apr 2023 22:13:38 +0200 [thread overview]
Message-ID: <20230403201338.PZVdIYXVaB7ZThzkUrhbmm06rVbz9w12laHOBdc4NW4@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: 790 bytes --]
New comment by dkwo on void-packages repository
https://github.com/void-linux/void-packages/issues/43148#issuecomment-1494920248
Comment:
```
$ doas ethtool eth0
Settings for eth0:
Supported ports: [ ]
Supported link modes: Not reported
Supported pause frame use: No
Supports auto-negotiation: No
Supported FEC modes: Not reported
Advertised link modes: Not reported
Advertised pause frame use: No
Advertised auto-negotiation: No
Advertised FEC modes: Not reported
Speed: Unknown!
Duplex: Half
Auto-negotiation: off
Port: Twisted Pair
PHYAD: 0
Transceiver: internal
MDI-X: Unknown
Current message level: 0x00000007 (7)
drv probe link
Link detected: no
```
only differences being speed and link detection
next prev parent reply other threads:[~2023-04-03 20:13 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 [this message]
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 ` [ISSUE] [CLOSED] " dkwo
2023-04-12 16:04 ` dkwo
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=20230403201338.PZVdIYXVaB7ZThzkUrhbmm06rVbz9w12laHOBdc4NW4@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).