{"id":1336,"date":"2015-02-23T21:26:01","date_gmt":"2015-02-23T21:26:01","guid":{"rendered":"http:\/\/rglinuxtech.com\/?p=1336"},"modified":"2015-02-23T21:26:01","modified_gmt":"2015-02-23T21:26:01","slug":"arm-kernel-4-0-rc1-not-much-joy-yet","status":"publish","type":"post","link":"https:\/\/rglinuxtech.com\/?p=1336","title":{"rendered":"ARM – Kernel 4.0-rc1 – Not Much Joy….Yet.."},"content":{"rendered":"

Tried Kernel 4.0-rc1<\/strong> on the CuBox-i4 Pro<\/strong> (from kernel.org<\/em><\/strong>) and the Odroid U3<\/strong> (from https:\/\/github.com\/tobiasjakobi\/linux-odroid\/tree\/odroid-4.0.y<\/a>), and the results are a bit of a mixed bag..<\/p>\n

The CuBox boots OK, but – although eth0<\/em> appears to be present – networking doesn’t work..<\/p>\n

Fedora release 22 (Twenty Two)<\/strong>\r\nKernel 4.0.0-rc1 on an armv7l (ttymxc0)<\/strong>\r\n................<\/strong>\r\n[root@rgcubox ~]# uname -a<\/strong>\r\nLinux rgcubox 4.0.0-rc1 #1 SMP Mon Feb 23 01:02:22 EST 2015 armv7l armv7l armv7l GNU\/Linux<\/strong>\r\n......................<\/strong>\r\n$ ifconfig<\/strong>\r\neth0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500<\/strong>\r\n ether d0:63:b4:00:31:3d txqueuelen 1000 (Ethernet)<\/strong>\r\n RX packets 0 bytes 0 (0.0 B)<\/strong>\r\n RX errors 0 dropped 0 overruns 0 frame 0<\/strong>\r\n TX packets 0 bytes 0 (0.0 B)<\/strong>\r\n TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0<\/strong>\r\n..........................<\/strong><\/pre>\n
# systemctl status network.service -l<\/strong>\r\n\u25cf network.service - LSB: Bring up\/down networking<\/strong>\r\n Loaded: loaded (\/etc\/rc.d\/init.d\/network)<\/strong>\r\n Active: failed (Result: exit-code) since Mon 2015-02-23 13:53:14 EST; 29s ago<\/strong>\r\n Docs: man:systemd-sysv-generator(8)<\/strong>\r\n Process: 384 ExecStart=\/etc\/rc.d\/init.d\/network start (code=exited, status=1\/FAILURE)<\/strong><\/pre>\n
Feb 23 13:53:12 rgcubox network[384]: Could not load file '\/etc\/sysconfig\/network-scripts\/ifcfg-lo'<\/strong>\r\nFeb 23 13:53:13 rgcubox network[384]: Could not load file '\/etc\/sysconfig\/network-scripts\/ifcfg-lo'<\/strong>\r\nFeb 23 13:53:13 rgcubox network[384]: Could not load file '\/etc\/sysconfig\/network-scripts\/ifcfg-lo'<\/strong>\r\nFeb 23 13:53:13 rgcubox network[384]: [ OK ]<\/strong>\r\nFeb 23 13:53:14 rgcubox network[384]: Bringing up interface eth0: Error: Connection activation failed: Connection 'System eth0' is not available on the device eth0 at this time.<\/strong>\r\nFeb 23 13:53:14 rgcubox network[384]: [FAILED]<\/strong>\r\n. etc.................<\/strong>   (and yes, all the necessary ifcfg files are in the right place!)<\/pre>\n
The Odroid U3 fails to boot:<\/p>\n
........<\/strong>\r\nhub 1-3:1.0: USB hub found<\/strong>\r\nhub 1-3:1.0: 3 ports detected<\/strong>\r\nINFO: rcu_preempt detected stalls on CPUs\/tasks: { 0} (detected by 1, t=12002 jiffies, g=-249, c=-250, q=33)<\/strong>\r\nTask dump for CPU 0:<\/strong>\r\nswapper\/0 R running 0 1 0 0x00000002<\/strong>\r\nBacktrace:<\/strong>\r\n[<ee081c8c>] (0xee081c8c) from [<ee081cbc>] (0xee081cbc)<\/strong>\r\nBacktrace aborted due to bad frame pointer <ee0142c0><\/strong><\/pre>\n
So.. More testing is needed!\u00a0\u00a0 The CuBox might<\/span> possibly be affected by compiling the kernel with the Fedora 22 5.0<\/strong> version of gcc<\/strong>, but this is unverified at the moment..\u00a0\u00a0 I may (re)compile the (working) 3.19.0 kernel with gcc 5.0, to test this..<\/p>\n
Robert Gadsdon.\u00a0\u00a0\u00a0 February 23, 2015.<\/em><\/p>\n
 <\/p>\n","protected":false},"excerpt":{"rendered":"
Tried Kernel 4.0-rc1 on the CuBox-i4 Pro (from kernel.org) and the Odroid U3 (from https:\/\/github.com\/tobiasjakobi\/linux-odroid\/tree\/odroid-4.0.y), and the results are a bit of a mixed bag.. The CuBox boots OK, but – although eth0 appears to be present – networking doesn’t work.. Fedora release 22 (Twenty Two) Kernel 4.0.0-rc1 on an armv7l (ttymxc0) ……………. [root@rgcubox ~]# uname -a …<\/span> Continue reading →<\/span><\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_monsterinsights_skip_tracking":false,"_monsterinsights_sitenote_active":false,"_monsterinsights_sitenote_note":"","_monsterinsights_sitenote_category":0,"footnotes":""},"categories":[862,14,16,794,19,20],"tags":[1174,1027,1019,1026,362],"class_list":["post-1336","post","type-post","status-publish","format-standard","hentry","category-cubox","category-kernel","category-linux-arm","category-odroid","category-opinion","category-performance-2","tag-arm","tag-cubox-i4-pro-network-fail","tag-kernel-4-0-rc1","tag-odroid-u3-boot-fail","tag-testing"],"_links":{"self":[{"href":"https:\/\/rglinuxtech.com\/index.php?rest_route=\/wp\/v2\/posts\/1336","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/rglinuxtech.com\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/rglinuxtech.com\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/rglinuxtech.com\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/rglinuxtech.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=1336"}],"version-history":[{"count":1,"href":"https:\/\/rglinuxtech.com\/index.php?rest_route=\/wp\/v2\/posts\/1336\/revisions"}],"predecessor-version":[{"id":1337,"href":"https:\/\/rglinuxtech.com\/index.php?rest_route=\/wp\/v2\/posts\/1336\/revisions\/1337"}],"wp:attachment":[{"href":"https:\/\/rglinuxtech.com\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=1336"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/rglinuxtech.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=1336"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/rglinuxtech.com\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=1336"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}