[fedora-arm] Fedora-Minimal-armhfp-21-20140905-sda.raw.xz - Cubietruck ethernet not working

Robert Moskowitz rgm at htt-consult.com
Fri Sep 5 18:33:52 UTC 2014


On 09/05/2014 01:50 PM, Sean Omalley wrote:
> I am guessing it added the /etc/sysconfig/network-scripts/

There is no ifcfg-eth0 on any of my F21 test builds.  In fact there is 
none on my F20 notebooks (or whatever the device name for the ethernet 
adapter is for each notebook).  It seems this is no longer created by 
default.  Which is a pain, because if you use system-config-network, it 
does not work for the interface until you create at least a default 
content ifcfg-<device name> file.

>
> There should be a line in the ifcfg-eth0 file, and changing
> ONBOOT=no to ONBOOT=yes
> should fix the immediate problem.

Yes. If there was an ifcfg-eth0, I would expect to see an ONBOOT=yes line.

>
> There is a line with the mac address (HWADDR) and one with the UUID.

MACaddr is now in /etc/udev/rules.d/70-persistent-net.rules which also 
does not exist be default anymore.  I have a script that another fellow 
gave me that can create one.  I have used it on my production F20 
cubieboard2 to control the MACaddr and such.

>
> I thought I read where these files were originally missing, in one of 
> the boot logs, but it maybe I have the wrong one, or maybe the  HWADDR 
> or device is wrong and it is being reconstructed with the correct 
> information on the second boot.? I don't know. :)

I know they are not there.  If you want to deviant from defaults, you 
have to build them yourself.

>
>
>
>
>
> On Friday, September 5, 2014 12:35 PM, Robert Moskowitz 
> <rgm at htt-consult.com> wrote:
>
>
>
>     So tried:
>
>     # systemctl restart NetworkManager.service
>     [ 2811.279655] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
>     [root at localhost <mailto:root at localhost> ~]# [ 2812.083261]  No MAC
>     Management Counters available
>     [ 2812.100459] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
>     [ 2813.087030] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
>     [ 2815.068718] stmmaceth 1c50000.ethernet eth0: Link is Up -
>     100Mbps/Full - flow control off
>     [ 2815.077039] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
>
>     # ip addr
>     1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN
>     group default
>         link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
>         inet 127.0.0.1/8 scope host lo
>             valid_lft forever preferred_lft forever
>         inet6 ::1/128 scope host
>             valid_lft forever preferred_lft forever
>     2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast
>     state UP group default qlen 1000
>         link/ether 86:80:43:3c:42:e1 brd ff:ff:ff:ff:ff:ff
>         inet 208.83.67.186/28 brd 208.83.67.191 scope global dynamic eth0
>             valid_lft 14180sec preferred_lft 14180sec
>         inet6 2607:f4b8:3:3:8480:43ff:fe3c:42e1/64 scope global
>     noprefixroute dynamic
>             valid_lft 35sec preferred_lft 25sec
>         inet6 fe80::8480:43ff:fe3c:42e1/64 scope link
>             valid_lft forever preferred_lft forever
>
>     So I now have a working ethernet.  But I poweroff and poweron:
>
>     # ip addr
>     1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN
>     group default
>         link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
>         inet 127.0.0.1/8 scope host lo
>             valid_lft forever preferred_lft forever
>         inet6 ::1/128 scope host
>             valid_lft forever preferred_lft forever
>     2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast
>     state UP group default qlen 1000
>         link/ether 5a:d5:ab:5f:50:63 brd ff:ff:ff:ff:ff:ff
>
>     Note the different MAC addr on new boot.
>
>     # systemctl restart NetworkManager.service
>     [  131.763025] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
>     [root at localhost <mailto:root at localhost> ~]# [  132.424848]  No MAC
>     Management Counters available
>     [  132.438088] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
>     [  133.809917] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
>     [  135.408087] stmmaceth 1c50000.ethernet eth0: Link is Up -
>     100Mbps/Full - flow control off
>     [  135.416411] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
>
>     ]# ip addr
>     1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN
>     group default
>         link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
>         inet 127.0.0.1/8 scope host lo
>             valid_lft forever preferred_lft forever
>         inet6 ::1/128 scope host
>             valid_lft forever preferred_lft forever
>     2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast
>     state UP group default qlen 1000
>         link/ether 5a:d5:ab:5f:50:63 brd ff:ff:ff:ff:ff:ff
>         inet 208.83.67.187/28 brd 208.83.67.191 scope global dynamic eth0
>             valid_lft 14338sec preferred_lft 14338sec
>         inet6 2607:f4b8:3:3:58d5:abff:fe5f:5063/64 scope global
>     noprefixroute dynamic
>             valid_lft 28sec preferred_lft 18sec
>         inet6 fe80::58d5:abff:fe5f:5063/64 scope link
>             valid_lft forever preferred_lft forever
>
>     Note the different IP address due to the different MACaddr.
>
>     Now I am part of the IEEE 802 MAC privacy study group where we are
>     discussing randomizing MAC addresses for privacy reasons, but I keep
>     exhausting my DHCP pool with each boot!  This test, I did not.
>     There was
>     NO DHCP query on poweron until I restarted NetworkManager.
>
>     What test next?
>
>
>     On 09/05/2014 11:54 AM, Peter Robinson wrote:
>     > On Fri, Sep 5, 2014 at 4:48 PM, Robert Moskowitz
>     <rgm at htt-consult.com <mailto:rgm at htt-consult.com>> wrote:
>     >> Still no Ethernet working on my Cubietruck.
>     > Minimal install works fine on mine
>     >
>     >> # systemctl -l status network.service
>     > systemctl status NetworkManager.service
>     >
>     > ip addr
>     >
>     > ifup eth0
>     > _______________________________________________
>     > arm mailing list
>     > arm at lists.fedoraproject.org <mailto:arm at lists.fedoraproject.org>
>     > https://admin.fedoraproject.org/mailman/listinfo/arm
>
>
>     _______________________________________________
>     arm mailing list
>     arm at lists.fedoraproject.org <mailto:arm at lists.fedoraproject.org>
>     https://admin.fedoraproject.org/mailman/listinfo/arm
>
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.fedoraproject.org/pipermail/test/attachments/20140905/9dad76cd/attachment-0001.html>


More information about the test mailing list