> On 07/31/2014 09:22 PM, Robert Moskowitz wrote:
>> I believe the problem is with the internal ethernet.  I attached an old USB 
>> Realtek ethernet adapter I have and the following occured:
>>
>>
>> [18306.819334] rtl8150 2-1:1.0: eth1: rtl8150 is detected
>> [18306.830541] usbcore: registered new interface driver rtl8150
>> [18307.151989] net eth1: eth1: allmulti set
>> [18307.156660] net eth1: eth1: allmulti set
>>
>> Then I plugged a cable in (that at first kept popping out as the tab is 
>> broken on it):
>>
>> [18459.380425] net eth1: eth1: allmulti set
>> [18460.881679] net eth1: eth1: allmulti set
>> [18466.198143] net eth1: eth1: allmulti set
>> [18466.207443] net eth1: eth1: allmulti set
>> [18471.231729] IPv6: ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready
>> [18471.238275] net eth1: eth1: allmulti set
>> [18471.278214] net eth1: eth1: allmulti set
>> [18472.731966] net eth1: eth1: allmulti set
>>
>>
>> #ip addr show
>> 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 ce:52:c8:ae:9a:66 brd ff:ff:ff:ff:ff:ff
>> 3: eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state 
>> UP group default qlen 1000
>>     link/ether 00:e0:4c:03:52:57 brd ff:ff:ff:ff:ff:ff
>>     inet 208.83.67.142/29 brd 208.83.67.143 scope global dynamic eth1
>>        valid_lft 86394sec preferred_lft 86394sec
>>     inet6 2607:f4b8:3:13:2e0:4cff:fe03:5257/64 scope global noprefixroute 
>> dynamic
>>        valid_lft 2592002sec preferred_lft 604802sec
>>     inet6 fe80::2e0:4cff:fe03:5257/64 scope link
>>        valid_lft forever preferred_lft forever
>>
>> # ping 208.83.67.148
>> PING 208.83.67.148 (208.83.67.148) 56(84) bytes of data.
>> 64 bytes from 208.83.67.148: icmp_seq=1 ttl=63 time=3.56 ms
>> 64 bytes from 208.83.67.148: icmp_seq=2 ttl=63 time=4.33 ms
>>
>>
>> So you can see that the Realtek is working, but the internal Cubieboard 
>> ethernet is not.  This ethernet is working in both the F19 and F20 remixes. 
>> Its MAC addr is local scope.
>>
>> Now that a connection is up I can install a few things to try...
>
> Networkmanager will not automatically activate onboard nics
> (for security) reasons, where as it will activate hotplugged ones.
>
> To activate the onboard nic do:
>
> nmcli c add type 802-3-ethernet ifname eth0

That's a change in the usual mode of operation, when did that happen
and where was it advertised?

Peter
_______________________________________________
arm mailing list
[email protected]
https://admin.fedoraproject.org/mailman/listinfo/arm

Reply via email to