ARM – Configs for Odroid U3 and CuBox-i4Pro..

I have just posted copies of recent kernel configs for the Odroid U3 and CuBox-i4Pro..

Odroid U3 – Kernel config for 4.4 :   http://pastebin.com/NveRajaZ

CuBox-i4Pro – Kernel config for 4.4.1:  http://pastebin.com/Kbexi0A5

These do not include working WiFi, as 2.4GHz is pretty useless at my location…

Robert Gadsdon.   February 2, 2016.


Comments

ARM – Configs for Odroid U3 and CuBox-i4Pro.. — 10 Comments

  1. kernel boots ok but ethernet cable has no link after the odroid-u3 finishes booting. “ifconfig usb0 up” doesn’t help either. would you please describe how to get ethernet working?

    • The Ethernet connection should appear as eth0:
      $ ifconfig
      eth0: flags=4163 mtu 1500
      inet xxx.xxx.xxx.xxx netmask 255.255.255.0 broadcast 192.168.0.255
      inet6 xxxx::xxxx:xxxx:xxxx:xxxx prefixlen 64 scopeid 0x20 ether 6e:f0:ca:6f:94:33 txqueuelen 1000 (Ethernet)
      RX packets 2878875 bytes 2112658220 (1.9 GiB)
      RX errors 0 dropped 33979 overruns 0 frame 0
      TX packets 765993 bytes 71525091 (68.2 MiB)
      TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

      The boot process should show the connection:

      $ dmesg |grep eth0
      [ 1.851915] smsc95xx 1-2:1.0 eth0: register ‘smsc95xx’ at usb-12580000.ehci-2, smsc95xx USB 2.0 Ethernet, 6e:f0:ca:6f:94:33
      [ 14.091534] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
      [ 14.136143] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
      [ 15.717547] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
      [ 15.718943] smsc95xx 1-2:1.0 eth0: link up, 100Mbps, full-duplex, lpa 0xC5E1

      RG.

      • finally, after many months, i’ve figured it out. thank you (and, of course, tobias) very much!

        details: for about a year now i’ve been using a 10 port usb hub (connected to the vertical usb port) to power my odroid (aka without the hardkernel power adapter) and everything i tried worked with the hardkernel kernel. with kernels > 4.1+ from tobias jakobi’s git, “dmesg|grep eth0” yielded no result and smsc95xx was being initialized as a hub (thus no eth0, only usb0). using the power adapter again (the only difference from a “standard” usage i could think of after your reply), smsc95xx is initialized as eth0 and i’ll finally be able to use a newer kernel with f23 on my odroid-u3’s.

  2. Do you get display on an HDMI monitor from Odroid U3 with this new 4.4 Kernel ?

    I tried your configuration, but could’t get it
    to display on HDMI monitor. On boot, monitor tries to switch between HDMI / Analog input couple of times and goes off.

    Kernel boots, and I could shutdown by blindly typing in
    the command etc though there is no display!.

    ( Sent from Odroid U3, Slackware 14.2-current, Kernel 3.8.13.27 )

    • I don’t have HDMI connected, and use a UART/USB console connection, and vncserver for network-attached sessions..
      RG.

  3. HDMI works completly fine here on my X2. System is attached to 1080p panel via HDMI. Also works on a smaller panel (1280×1024) attached via DVI (through a passive convertor).

    – Tobias

  4. Hello and thanks for all your work w/ Fedora and Cubox i4-pro and Odroid-C2.

    I currently have a Cubox i4-pro that only seems to want to run with OSes loaded by the Solid-Run Ignition OS tool, and I have an Odroid C2 on the way that I understand currently only works with a custom HardKernel-provided 3.14 kernel.

    I was wondering if you could help me to get on the right track with 3 things:
    – 1. Is Cubox i4-pro workable with Fedora 24?
    – 2. How reasonable is it to assume the Odroid C2 will work with 4.7-based Fedora 25?
    – 3. For a non hardware whiz like me with limited ARM experience but plenty of x86 sysadmin experience, do you have any advice on how to get up to speed with ARM Linux? A lot of what I’ve seen covered is strictly for people looking to learn ARM programming, or for people in your case who are deep into the internals of various SOCs which is far beyond where I’m at currently.

    Thanks!

    • My CuBox is running Fedora 24 without any problems – currently on Kernel 4.6.4…. My C2 is still on the ancient HK 3.14.xx kernel, also with F24..

      The C2 ‘mainline’ kernel is still missing vital components – such as MMC support – and these have not made it into the released 4.7 kernel..
      I have noticed that a patch has recently been submitted for ‘meson-gxbb – add MMC support’ but I have not had an opportunity to test this on the C2, yet.. This might possibly make it into the final 4.8 kernel, but may be delayed until 4.9..

      So far, all the released Fedora aarch64 versions have been for ‘server’ support, with uEFI, which means that the standard Anaconda install script will fail on a non-uEFI ‘workstation’ system, such as the C2..

      Brief hints on getting started with ARM stuff..
      1. Need to understand about Device Trees and U-Boot.. Only one of my ARM/ARM64 systems (the Hikey) uses EFI/GRUB..
      2. Need to compile kernel, as standard Distro-supplied versions may not work..
      3. Need a UART/console connection for each ARM device, to be able to control/test boot process with U-Boot…
      4. Check the linux-arm-kernel mailing list, for up-to-date patch info..

      RG.

  5. Hi!

    I’m struggling with an Odroid U3, don’t have UART 1.8V, only 3.3V, which is hardening the task in every way. So, I see that you could get your U3 running with U-Boot mainline and kernel mainline. I can compile U-Boot mainline, write it on SD Card with sd_fusing script, create boot.scr as well, but all I can get is the blue led solid and nothing more. If I then write u-boot from hardkernel (even not using sd_fusing, only dd … seek=63 /dev/sdb on a VirtualBox) and recreate original boot.scr, it boots again (only 3.8.13.30 of course).

    Can you share any thoughts on your experience with this board? Like U-Boot version, how to correctly write it to SD Card, your boot.cmd?

    Many thanks!

    • I haven’t done anything with the U3 since early 2016, and most of that is in earlier articles..
      U-boot instructions can be found in ~/u-boot/doc/readme.ODROID
      I don’t use boot.scr/boot.cmd etc.. I put any changes to the u-boot parameters in at the u-boot prompt, and then just use >saveenv.. Gives more flexibility when booting different kernel/patch versions during tests etc..
      RG.

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.