{"id":1338,"date":"2015-02-24T23:44:25","date_gmt":"2015-02-24T23:44:25","guid":{"rendered":"http:\/\/rglinuxtech.com\/?p=1338"},"modified":"2015-02-24T23:45:20","modified_gmt":"2015-02-24T23:45:20","slug":"arm-kernel-4-0-rc1-fix-for-cubox-i4-pro-networking","status":"publish","type":"post","link":"https:\/\/rglinuxtech.com\/?p=1338","title":{"rendered":"ARM &#8211; Kernel 4.0-rc1 &#8211; Fix for CuBox-i4 Pro Networking.."},"content":{"rendered":"<p>The CuBox-i4 Pro booted Kernel 4.0-rc1 OK, but &#8211; although <em>eth0<\/em> was present &#8211; there was no network connection possible..<\/p>\n<p>I found a similar problem described on the Linux Arm Kernel mailing list:\u00a0 <a title=\"http:\/\/lists.infradead.org\/pipermail\/linux-arm-kernel\/2015-February\/325249.html\" href=\"http:\/\/lists.infradead.org\/pipermail\/linux-arm-kernel\/2015-February\/325249.html\" target=\"_blank\">http:\/\/lists.infradead.org\/pipermail\/linux-arm-kernel\/2015-February\/325249.html<\/a><\/p>\n<p>According to the info there, I changed <strong>linux\/arch\/arm\/mach-imx\/mach-imx6q.c<\/strong> as follows:<\/p>\n<p>Around line 214, change<\/p>\n<pre><strong>clksel = ptp_clk == enet_ref ? IMX6Q_GPR1_ENET_CLK_SEL_ANATOP :\r\n                                    IMX6Q_GPR1_ENET_CLK_SEL_PAD;<\/strong><\/pre>\n<p>to<\/p>\n<pre><strong>clksel = ptp_clk != enet_ref ? IMX6Q_GPR1_ENET_CLK_SEL_ANATOP :\r\n                                    IMX6Q_GPR1_ENET_CLK_SEL_PAD;<\/strong><\/pre>\n<p>Recompile \/ install, and networking now works correctly..<\/p>\n<pre><strong>......................<\/strong>\r\n<strong>fec 2188000.ethernet eth0: Link is Up - 1Gbps\/Full - flow control rx\/tx<\/strong>\r\n<strong>IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready<\/strong>\r\n<strong>......................<\/strong><\/pre>\n<pre><strong>Fedora release 22 (Twenty Two)<\/strong>\r\n<strong>Kernel 4.0.0-rc1 on an armv7l (ttymxc0)<\/strong>\r\n<strong>.......................<\/strong>\r\n<strong>[root@rgcubox ~]# route<\/strong>\r\n<strong>Kernel IP routing table<\/strong>\r\n<strong>Destination Gateway Genmask Flags Metric Ref Use Iface<\/strong>\r\n<strong>default dsl_router 0.0.0.0 UG 100 0 0 eth0<\/strong>\r\n<strong>192.168.0.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0<\/strong>\r\n<strong>192.168.0.0 0.0.0.0 255.255.255.0 U 100 0 0 eth0<\/strong>\r\n<strong>[root@rgcubox ~]# ping rglinux-i7<\/strong>\r\n<strong>PING rglinux-i7 (192.168.0.2) 56(84) bytes of data.<\/strong>\r\n<strong>64 bytes from rglinux-i7 (192.168.0.2): icmp_seq=1 ttl=64 time=0.341 ms<\/strong>\r\n<strong>64 bytes from rglinux-i7 (192.168.0.2): icmp_seq=2 ttl=64 time=0.173 ms<\/strong>\r\n<strong>64 bytes from rglinux-i7 (192.168.0.2): icmp_seq=3 ttl=64 time=0.171 ms\r\n--- rglinux-i7 ping statistics ---<\/strong>\r\n<strong>3 packets transmitted, 3 received, 0% packet loss, time 1999ms<\/strong>\r\n<strong>rtt min\/avg\/max\/mdev = 0.171\/0.228\/0.341\/0.080 ms<\/strong><\/pre>\n<p>So &#8211; I now have Kernel 4.0-rc1 running successfully on the CuBox-i4 Pro..<\/p>\n<p><em>Robert Gadsdon.\u00a0 February 24, 2015.<\/em><\/p>\n","protected":false},"excerpt":{"rendered":"<p>The CuBox-i4 Pro booted Kernel 4.0-rc1 OK, but &#8211; although eth0 was present &#8211; there was no network connection possible.. I found a similar problem described on the Linux Arm Kernel mailing list:\u00a0 http:\/\/lists.infradead.org\/pipermail\/linux-arm-kernel\/2015-February\/325249.html According to the info there, I changed linux\/arch\/arm\/mach-imx\/mach-imx6q.c as follows: Around line 214, change clksel = ptp_clk == enet_ref ? IMX6Q_GPR1_ENET_CLK_SEL_ANATOP : IMX6Q_GPR1_ENET_CLK_SEL_PAD; <span class=\"excerpt-dots\">&hellip;<\/span> <a class=\"more-link\" href=\"https:\/\/rglinuxtech.com\/?p=1338\"><span class=\"more-msg\">Continue reading &rarr;<\/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":[5,6,862,11,14,16,19,20],"tags":[1174,863,1028,161,1019,1029,1175],"class_list":["post-1338","post","type-post","status-publish","format-standard","hentry","category-compilation","category-crash-and-burn","category-cubox","category-hacks","category-kernel","category-linux-arm","category-opinion","category-performance-2","tag-arm","tag-cubox-i4-pro","tag-eth0-not-working","tag-fix","tag-kernel-4-0-rc1","tag-mach-imx6q-c","tag-success"],"_links":{"self":[{"href":"https:\/\/rglinuxtech.com\/index.php?rest_route=\/wp\/v2\/posts\/1338","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=1338"}],"version-history":[{"count":3,"href":"https:\/\/rglinuxtech.com\/index.php?rest_route=\/wp\/v2\/posts\/1338\/revisions"}],"predecessor-version":[{"id":1341,"href":"https:\/\/rglinuxtech.com\/index.php?rest_route=\/wp\/v2\/posts\/1338\/revisions\/1341"}],"wp:attachment":[{"href":"https:\/\/rglinuxtech.com\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=1338"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/rglinuxtech.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=1338"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/rglinuxtech.com\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=1338"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}