19 20:15, Karsten Wiborg wrote:
> The information is sufficient now. Still, using a random MAC address
> is an emergency fallback. The device is simply broken.
> I contacted GPD, let's see whether they respond something.
>
> In parallel I'll add a random MAC address as
Hi Andrew, Heiner,
the device is a really small notebook. So detaching mains still leaves
the battery which is delicately built in. So can't currently remove
power completely.
Anyway can I deliver more debugging data to you guys which might add
support for the r8169 for this device?
Regards,
Kar
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
>
Hi Andrew,
On 30/06/2019 19:56, Andrew Lunn wrote:
> 0x6e = 0110 1110b. Bit 1 is the Locally Administered bit. Meaning this
> is not an MAC address from a vendor pool, but one generated locally.
>
> http://www.noah.org/wiki/MAC_address
Didn't know that. Thanks for pointing that out.
> If linux w
Hi Heiner,
On 30/06/2019 19:42, Heiner Kallweit wrote:
> Vendor driver uses this code, do you see the related messages in syslog?
>
> if (!is_valid_ether_addr(mac_addr)) {
> netif_err(tp, probe, dev, "Invalid ether addr %pM\n",
> mac_addr);
>
Hi Andrew,
On 30/06/2019 16:55, Andrew Lunn wrote:
> Hi Karsten
>
> What MAC address do you get with the vendor driver? Is it the same MAC
> address every time you reboot, or does it look random.
>
> The BIOS is expected to program the MAC address into the hardware. It
> could be that the vendor
Hi Heiner,
On 30/06/2019 11:12, Heiner Kallweit wrote:
> Indeed the MAC is missing:
> [2.839776] r8169 :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.
Hi Heiner,
thanks for the speedy reply.
On 6/30/19 12:09 AM, Heiner Kallweit wrote:
> If r8169 (the mainline driver) is running, why do you want to switch
> to r8168 (the Realtek vendor driver)? The latter is not supported by
> the kernel community.
Well I did install r8168 because r8169 is not w
6_64-linux-gnu --target=x86_64-linux-gnu
Thread model: posix
gcc version 8.3.0 (Debian 8.3.0-6)
Regards,
Karsten Wiborg
On 6/29/19 10:34 PM, Karsten Wiborg wrote:
> Hello,
>
> writing to you because of the r8168-dkms-README.Debian.
>
> I am using a GPD MicroPC running Debian Buster w
ata?
Thank you very much in advance for hopefully looking into this matter.
Regards,
Karsten Wiborg
10 matches
Mail list logo
