On Thu, Aug 10, 2017 at 10:28 PM, Rance Hall <ranceh@xxxxxxxxx> wrote: > Fedora Arm Team: > > I write to ask for your help with troubleshooting and solving a problem that > seems to be unique to Fedora 26 on my pcduino3_nano device from Linksprite. > > The device has an onboard NAND flash drive with an old custom version of > ubuntu installed. I can use this system to verify that the networking works > as expected when the ubuntu image is booted. > > I have prepared both a Fedora 25 arm XFCE sd card and a Fedora 26 arm XFCE > sd card. > > Under the Ubuntu system dmesg says this about eth0: > > [ 19.843724] eth0: PHY ID 001cc915 at 0 IRQ 0 (sunxi_gmac-0:00) active > [ 19.843737] eth0: PHY ID 001cc915 at 1 IRQ 0 (sunxi_gmac-0:01) > [ 30.344377] eth0: no IPv6 routers present > [ 34.676435] eth0: PHY ID 001cc915 at 0 IRQ 0 (sunxi_gmac-0:00) active > [ 34.676448] eth0: PHY ID 001cc915 at 1 IRQ 0 (sunxi_gmac-0:01) > [ 34.701645] ADDRCONF(NETDEV_UP): eth0: link is not ready > [ 39.893312] eth0: PHY ID 001cc915 at 0 IRQ 0 (sunxi_gmac-0:00) active > [ 39.893327] eth0: PHY ID 001cc915 at 1 IRQ 0 (sunxi_gmac-0:01) > [ 39.910555] ADDRCONF(NETDEV_UP): eth0: link is not ready > > When a cable is plugged into this interface networking works normally. > > ifconfig reports that the mac address of this interface is a2:40:c9:6a:6b:f6 > > Under Fedora 26 dmesg reports this about eth0: > > [ 36.478651] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready > [ 36.655906] sun7i-dwmac 1c50000.ethernet eth0: RX IPC Checksum Offload > disabled > [ 36.669475] sun7i-dwmac 1c50000.ethernet eth0: No MAC Management Counters > available > [ 36.683220] sun7i-dwmac 1c50000.ethernet eth0: PTP not supported by HW > [ 36.744921] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready > > Under Fedora 26 the mac address reported for the exact same hardware is: > 02:4d:05:40:d1:11 > > I don't understand why two different os'es report 2 different mac addresses > for the same physical nic. I know you can spoof nics, but I've not set this > up so it shouldnt be happening. I'm not particularly surprised, in both cases the "stable" MAC is generated based on information in the SoC and I believe the algorithm did change for some reason. Is it stable on that address between reboots of Fedora? > Also under Fedora 26 the nic can obtain an ip address via dhcp, but I've yet > to find a network task it can perform once configured. It can't ping, use > the tcp stack browse the web, or any other task I tried. Is the firewall blocking? What does "iptables -L" show? > It isn't fedora itself as I can insert a usb wifi dongle and networking > fires up and works just fine, this tells me there is something specifically > wrong with the kernel driver or some othe part of the system that is > specific to the interface. > > I'm willing to help troubleshoot and answer any questions, I just don't > happen to know what would be useful/helpful at this point outside of what > I've already provided. > > Thanks for any help you can provide. > > Rance > > _______________________________________________ > arm mailing list -- arm@xxxxxxxxxxxxxxxxxxxxxxx > To unsubscribe send an email to arm-leave@xxxxxxxxxxxxxxxxxxxxxxx > _______________________________________________ arm mailing list -- arm@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to arm-leave@xxxxxxxxxxxxxxxxxxxxxxx
