From: Karsten Wiborg <karsten.wiborg@web.de>
To: Heiner Kallweit <hkallweit1@gmail.com>,
nic_swsd@realtek.com, romieu@fr.zoreil.com
Cc: netdev@vger.kernel.org
Subject: Re: r8169 not working on 5.2.0rc6 with GPD MicroPC
Date: Sun, 30 Jun 2019 14:40:14 +0200 [thread overview]
Message-ID: <62684063-10d1-58ad-55ad-ff35b231e3b0@web.de> (raw)
In-Reply-To: <b104dbf2-6adc-2eee-0a1a-505c013787c0@gmail.com>
Hi Heiner,
On 30/06/2019 11:12, Heiner Kallweit wrote:
> Indeed the MAC is missing:
> [ 2.839776] r8169 0000:02:00.0 eth0: RTL8168h/8111h,
> 00:00:00:00:00:00, XID 541, IRQ 126
>
> This works with RTL8168h in other systems, so I'd say you should
> check with the vendor. Maybe it's a BIOS issue.
Tested some more. Found out that the Realtek-supplied r8168-8.046.00 is
buggy (compilation bugged out, see one of my last mails). I just
succeeded in compiling r8168-8.047.00, which ran straight out of the
box. So the NIC is fine and not defect.
I do agree with you: I definitely would prefer an opensource driver but
the r8169 simply didn't work.
In regard of my success with r8168-8.047.00, do you still think it might
be a BIOS-issue?
Regards,
Karsten
next prev parent reply other threads:[~2019-06-30 12:45 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-29 20:34 r8169 not working on 5.2.0rc6 with GPD MicroPC Karsten Wiborg
2019-06-29 21:19 ` Karsten Wiborg
2019-06-29 22:09 ` Heiner Kallweit
2019-06-30 0:14 ` Karsten Wiborg
2019-06-30 9:12 ` Heiner Kallweit
2019-06-30 12:40 ` Karsten Wiborg [this message]
2019-06-30 14:55 ` Andrew Lunn
2019-06-30 16:03 ` Karsten Wiborg
2019-06-30 17:42 ` Heiner Kallweit
2019-06-30 21:29 ` Karsten Wiborg
2019-06-30 21:55 ` Heiner Kallweit
2019-06-30 22:21 ` Karsten Wiborg
2019-07-01 5:50 ` Heiner Kallweit
2019-07-01 13:35 ` Andrew Lunn
2019-07-01 18:15 ` Karsten Wiborg
2019-07-01 18:51 ` Heiner Kallweit
2019-07-01 19:07 ` Karsten Wiborg
2019-06-30 17:56 ` Andrew Lunn
2019-06-30 21:44 ` Karsten Wiborg
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=62684063-10d1-58ad-55ad-ff35b231e3b0@web.de \
--to=karsten.wiborg@web.de \
--cc=hkallweit1@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=nic_swsd@realtek.com \
--cc=romieu@fr.zoreil.com \
/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).