It took me a bit to work out issues with the serial console to get back into testing. Those issues are for a separate list...
I can get Minimal to go through the install process and set timezone, root password, and userid. When I go to log in I get:
Fedora release 21 (Twenty One) Kernel 3.16.0-0.rc7.git1.1.fc21.armv7hl on an armv7l (ttyS0)
localhost login: root Password: [ 64.141895] cfg80211: Calling CRDA to update world regulatory domain [ 66.257749] eth0: device MAC address c2:f5:e1:51:08:dd [ 66.450111] No MAC Management Counters available [ 66.712730] No MAC Management Counters available [ 66.718353] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 68.632241] stmmaceth 1c50000.ethernet eth0: Link is Up - 100Mbps/Full - flow control off [ 68.649252] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
Last login: Wed Dec 31 19:04:26 on ttyS0 [root@localhost ~]# ifconfig -bash: ifconfig: command not found [root@localhost ~]# echo $PATH /usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin:/root/bin [root@localhost ~]#
No commands work. I know the IP address this device gets assigned so I tried pinging and ssh:
]# ping 208.87.63.186 PING 208.87.63.186 (208.87.63.186) 56(84) bytes of data. 64 bytes from 208.87.63.186: icmp_seq=1 ttl=47 time=78.8 ms 64 bytes from 208.87.63.186: icmp_seq=2 ttl=47 time=77.1 ms ^C --- 208.87.63.186 ping statistics --- 2 packets transmitted, 2 received, 0% packet loss, time 1001ms rtt min/avg/max/mdev = 77.167/78.009/78.852/0.887 ms # ssh 208.87.63.186 -l root ssh: connect to host 208.87.63.186 port 22: Connection refused
You can probably ping it yourself, but port 22 is blocked at the firewall router.
I powered off and rebooted, and still the same behaviour. I did a screen capture of the install, so can provide that if it would help (54K). Note I have had this problem since I started on Minimal with the 20140724 build, but have not been able to stablily test it. I believe my setup now provides a reliable test of the build on a Cubieboard 2.
Further note that I have a F19 and F20 remix working on this system on other SD cards. I can boot any of the versions just by switching which card is in it.
Thank you and I await advise on what to provide next (or a build that works for me).
On Thu, Jul 31, 2014 at 2:35 PM, Robert Moskowitz rgm@htt-consult.com wrote:
It took me a bit to work out issues with the serial console to get back into testing. Those issues are for a separate list...
I can get Minimal to go through the install process and set timezone, root password, and userid. When I go to log in I get:
Fedora release 21 (Twenty One) Kernel 3.16.0-0.rc7.git1.1.fc21.armv7hl on an armv7l (ttyS0)
localhost login: root Password: [ 64.141895] cfg80211: Calling CRDA to update world regulatory domain [ 66.257749] eth0: device MAC address c2:f5:e1:51:08:dd [ 66.450111] No MAC Management Counters available [ 66.712730] No MAC Management Counters available [ 66.718353] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 68.632241] stmmaceth 1c50000.ethernet eth0: Link is Up - 100Mbps/Full - flow control off [ 68.649252] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
Last login: Wed Dec 31 19:04:26 on ttyS0 [root@localhost ~]# ifconfig -bash: ifconfig: command not found [root@localhost ~]# echo $PATH /usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin:/root/bin [root@localhost ~]#
No commands work. I know the IP address this device gets assigned so I tried pinging and ssh:
the ip command as replaced pretty much all stuff (actually around 10 years ago!) but once you get use it it is much nicer. There's a quick start here http://andys.org.uk/bits/2010/02/24/iproute2-life-after-ifconfig/ or you can do "yum install net-tools" and get the old ones back.
You can probably ping it yourself, but port 22 is blocked at the firewall router.
firewall-cmd --help
I powered off and rebooted, and still the same behaviour. I did a screen capture of the install, so can provide that if it would help (54K). Note I have had this problem since I started on Minimal with the 20140724 build, but have not been able to stablily test it. I believe my setup now provides a reliable test of the build on a Cubieboard 2.
It's expected behaviour so I'm not sure why you'd expect it to change, if you don't need a firewall you can just "yum remove firewalld"
Thank you and I await advise on what to provide next (or a build that works for me).
So I'm not sure what isn't working. The two issues you had above with network config and firewall are by design and there's a lot of good docs on the Fedora wiki and elsewhere that cover them and I've given you alternatives to the default. Is there anything else you need?
Peter
On 07/31/2014 09:55 AM, Peter Robinson wrote:
On Thu, Jul 31, 2014 at 2:35 PM, Robert Moskowitz rgm@htt-consult.com wrote:
It took me a bit to work out issues with the serial console to get back into testing. Those issues are for a separate list...
I can get Minimal to go through the install process and set timezone, root password, and userid. When I go to log in I get:
Fedora release 21 (Twenty One) Kernel 3.16.0-0.rc7.git1.1.fc21.armv7hl on an armv7l (ttyS0)
localhost login: root Password: [ 64.141895] cfg80211: Calling CRDA to update world regulatory domain [ 66.257749] eth0: device MAC address c2:f5:e1:51:08:dd [ 66.450111] No MAC Management Counters available [ 66.712730] No MAC Management Counters available [ 66.718353] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 68.632241] stmmaceth 1c50000.ethernet eth0: Link is Up - 100Mbps/Full - flow control off [ 68.649252] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
Last login: Wed Dec 31 19:04:26 on ttyS0 [root@localhost ~]# ifconfig -bash: ifconfig: command not found [root@localhost ~]# echo $PATH /usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin:/root/bin [root@localhost ~]#
No commands work. I know the IP address this device gets assigned so I tried pinging and ssh:
the ip command as replaced pretty much all stuff (actually around 10 years ago!) but once you get use it it is much nicer. There's a quick start here http://andys.org.uk/bits/2010/02/24/iproute2-life-after-ifconfig/ or you can do "yum install net-tools" and get the old ones back.
Whow, I have been asleep at the switch on this one. Did not see it in any notes, but then that is more than likely my fault. So I got a lot of reading to do, and then figure out why no IP addresses (v4 or v6) are getting assigned. I figure out enough of the IP command to see no addresses. Even if there is a problem with my DHCP server, I am sending out RA messages, so there should be a global IP address. I will dig a bit and see if I can get addressing to come up properly.
Of course with no addressing, the address I *THOUGHT* this box took was actually another test box that has SSH on another port, of course ssh was not connecting. 'firewall-cmd --list-all-zones' shows that the ssh service is allowed in; no change to default setups there.
ANd I cannot install net-tools until I get addressing working.
So at least I know I have a 'working' system to some definition of working and I can go off and learn what has changed and how to live with the changes.
thank you
the ip command as replaced pretty much all stuff (actually around 10 years ago!) but once you get use it it is much nicer. There's a quick start here http://andys.org.uk/bits/2010/02/24/iproute2-life-after-ifconfig/ or you can do "yum install net-tools" and get the old ones back.
Whow, I have been asleep at the switch on this one. Did not see it in any notes, but then that is more than likely my fault. So I got a lot of reading to do, and then figure out why no IP addresses (v4 or v6) are getting assigned. I figure out enough of the IP command to see no addresses. Even if there is a problem with my DHCP server, I am sending out RA messages, so there should be a global IP address. I will dig a bit and see if I can get addressing to come up properly.
Of course with no addressing, the address I *THOUGHT* this box took was actually another test box that has SSH on another port, of course ssh was not connecting. 'firewall-cmd --list-all-zones' shows that the ssh service is allowed in; no change to default setups there.
ANd I cannot install net-tools until I get addressing working.
The other useful command is nmcli which is the NetworkManager command line. You could also try a plain old "ifup eth0" and see if that makes a difference.
Peter
On 07/31/2014 10:31 AM, Peter Robinson wrote:
the ip command as replaced pretty much all stuff (actually around 10 years ago!) but once you get use it it is much nicer. There's a quick start here http://andys.org.uk/bits/2010/02/24/iproute2-life-after-ifconfig/ or you can do "yum install net-tools" and get the old ones back.
Whow, I have been asleep at the switch on this one. Did not see it in any notes, but then that is more than likely my fault. So I got a lot of reading to do, and then figure out why no IP addresses (v4 or v6) are getting assigned. I figure out enough of the IP command to see no addresses. Even if there is a problem with my DHCP server, I am sending out RA messages, so there should be a global IP address. I will dig a bit and see if I can get addressing to come up properly.
Of course with no addressing, the address I *THOUGHT* this box took was actually another test box that has SSH on another port, of course ssh was not connecting. 'firewall-cmd --list-all-zones' shows that the ssh service is allowed in; no change to default setups there.
ANd I cannot install net-tools until I get addressing working.
The other useful command is nmcli which is the NetworkManager command line. You could also try a plain old "ifup eth0" and see if that makes a difference.
Looks like more digging is called for:
# 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
# ifup eth0 /sbin/ifup: configuration for eth0 not found. Usage: ifup <configuration>
Could it be that the MAC addr is local scope? But this is needed on many SOC boards; not unique to Cubies.