From: Stephen Hemminger <stephen@networkplumber.org>
To: netdev@vger.kernel.org
Subject: Fw: [Bug 200967] New: No network with U.S. Robotics USR997902
Date: Wed, 29 Aug 2018 08:02:36 -0700 [thread overview]
Message-ID: <20180829080236.43391048@xeon-e3> (raw)
Begin forwarded message:
Date: Wed, 29 Aug 2018 04:36:20 +0000
From: bugzilla-daemon@bugzilla.kernel.org
To: stephen@networkplumber.org
Subject: [Bug 200967] New: No network with U.S. Robotics USR997902
https://bugzilla.kernel.org/show_bug.cgi?id=200967
Bug ID: 200967
Summary: No network with U.S. Robotics USR997902
Product: Networking
Version: 2.5
Kernel Version: 4.18.5
Hardware: x86-64
OS: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: IPV4
Assignee: stephen@networkplumber.org
Reporter: kyrimis@alumni.princeton.edu
Regression: No
Created attachment 278193
--> https://bugzilla.kernel.org/attachment.cgi?id=278193&action=edit
dmesg and hwinfo output
(I am reporting this upstream as instructed by OpenSUSE, where I had originally
reported this problem.)
After upgrading to kernel 4.18 (originally noticed the problem with kernel
4.18.0, the problem persists with kernel 4.18.5), I could no longer connect to
the network.
A similar machine, which I upgraded at the same time, had no problem, so I
thought that the problem might be due to my using a network card instead of the
motherboard's built-in network controller. Sure enough, configuring the
built-in controller and connecting that to the network worked fine.
According to lspci, the card that doesn't work with the new kernel is:
U.S. Robotics USR997902 10/100/1000 Mbps PCI Network Card (rev 10)
Ifconfig shows that the network controller has been recognized as such, but
that it has not obtained an IP address.
The problem did not occur with kernel 4.17.14.
I have attached the output of hwinfo and dmesg for kernels 4.17.14 and 4.18.5,
with the network cable connected to the U.S. Robotics controller (enp5s0).
--
You are receiving this mail because:
You are the assignee for the bug.
reply other threads:[~2018-08-29 19:00 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20180829080236.43391048@xeon-e3 \
--to=stephen@networkplumber.org \
--cc=netdev@vger.kernel.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).