From: Karsten Wiborg <karsten.wiborg@web.de>
To: Heiner Kallweit <hkallweit1@gmail.com>, Andrew Lunn <andrew@lunn.ch>
Cc: nic_swsd@realtek.com, romieu@fr.zoreil.com, netdev@vger.kernel.org
Subject: Re: r8169 not working on 5.2.0rc6 with GPD MicroPC
Date: Mon, 1 Jul 2019 00:21:11 +0200 [thread overview]
Message-ID: <116e4be6-e710-eb2d-0992-a132f62a8727@web.de> (raw)
In-Reply-To: <de38facc-37ed-313f-cf1e-1ec6de9810c8@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1269 bytes --]
Hi Heiner,
On 30/06/2019 23:55, Heiner Kallweit wrote:
> This one shows that the vendor driver (r8168) uses a random MAC address.
> Means the driver can't read a valid MAC address from the chip, maybe due
> to a broken BIOS.
> Alternatively you could use r8169 and set a MAC address manually with
> ifconfig <if> hw ether <MAC address>
Hmm, did some more testing:
did a rmmod r8168 and (after "un"blacklisting the r8169) modprobed the
r8169. This time r8169 came up nicely but with a complete different MAC
(forgot to not than one though).
So I guess the vendor compilation did other stuff besides just compiling
the r8168 kernel module.
Did another test:
blacklisted the r8168, renamed r8168.ko to r8168.bak, depmod -a and
powercycled the system. Funny it came up with both r8168 and r8169
loaded and I got my intended IP address from. DHCP, so r8168 somewhat
got loaded and used his MAC.
Did another rmmod r8168, rmmod r8169 and then modprobe r8169.
Even though I did NOT configure a MAC address myself manually it came up
with a new MAC address and of course got a dynamich IP address.
So I don't know where the vendor somewhat changed something (with his
compiling/installing) to the effect that r8169 now works?!?
Regards,
Karsten
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 4156 bytes --]
next prev parent reply other threads:[~2019-06-30 22:21 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
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 [this message]
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=116e4be6-e710-eb2d-0992-a132f62a8727@web.de \
--to=karsten.wiborg@web.de \
--cc=andrew@lunn.ch \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.