NVIDIA driver 334.21 is out, but still needs the nv-linux.h patch for kernel 3.14 (tested with 3.14-rc5). See previous article at http://rglinuxtech.com/?p=1035 for details of the patch..
Robert Gadsdon. March 4, 2014.
Reply
Updated the test (x86_64) system and the DreamPlug (armv5) to kernel 3.14-rc5, and the same comments apply as for 3.14-rc4.. http://rglinuxtech.com/?p=1070
Fedora release 18 (Spherical Cow) Kernel 3.14.0-rc5 on an armv5tel (ttyS0) ........... # uname -a Linux rgdreamplug 3.14.0-rc5 #1 PREEMPT Mon Mar 3 22:07:22 GMT 2014 armv5tel armv5tel armv5tel GNU/Linux
Latest – patched – NVIDIA and VMware drivers all compile / load OK on x86_64…
Details of changes are here: https://lkml.org/lkml/2014/3/2/257
Robert Gadsdon. March 4, 2014.
After a lot of ‘hacking’, I managed to get the Odroid U3 to boot with Kernel 3.14-rc3, from http://git.prahal.homelinux.net/odroid.git/ , but there were persistent issues with USB, which refused to recognise any devices connected (apart from the USB memory stick (usb-storage) connection built-in to the kernel at compile time).
Fedora release 20 (Heisenbug) Kernel 3.14.0-rc3 on an armv7l (ttySAC1) ........... $ uname -a Linux rgodroid 3.14.0-rc3 #1 SMP PREEMPT Thu Feb 27 18:34:06 GMT 2014 armv7l armv7l armv7l GNU/Linux
So.. Back to the Hardkernel version of Kernel 3.8.13.18 for the time being, and I have managed to get rid of the ubuntu/debian-proprietary bits from the kernel tree, and re-edit the Makefile to remove all references.. I have had some odd issues with USB connections with this version, but at least the USB keyboard and mouse work OK!
Robert Gadsdon. March 1, 2014.
Updated the test system to Kernel 3.14-rc4, and the VMware 10.0.1 (patched) and NVIDIA 331.49 (patched) compile and load OK..
Details of changes are here: https://lkml.org/lkml/2014/2/23/234
Updated the Dreamplug to 3.14-rc4 as well:
Fedora release 18 (Spherical Cow) Kernel 3.14.0-rc4 on an armv5tel (ttyS0)
The Odroid is not (yet) supported by the standard kernel-org tree, but hopefully it will soon be, as the version of 3.8.13 available is ancient and buggy, and still has various proprietary bits..
Robert Gadsdon. February 24, 2014.
Updated to Kernel 3.13.4, and the latest NVIDIA driver 331.49 and (patched) VMware 10.0.1 compile and load/run OK..
Details of changes are here: https://www.kernel.org/pub/linux/kernel/v3.x/ChangeLog-3.13.4
I had still been having problems with the uvcvideo driver (with a Logitech C525 webcam), since updating from kernel 3.12 to kernel 3.13 – and the problems is also in 3.14-rc3.. I discovered that having two USB-connected video devices active at the same time caused one or the other to fail:
[ 713.855382] uvcvideo: Failed to submit URB 0 (-28). [ 714.185786] uvcvideo: Failed to submit URB 0 (-28). [ 714.262135] uvcvideo: Failed to submit URB 0 (-28).
After some more testing, I was able to find a workaround, by making sure that the usb video devices were connected to different root hubs:
Bus 010 Device 002: ID 046d:0826 Logitech, Inc. < uvcvideo webcam > Bus 008 Device 006: ID 14f7:0500 TechniSat Digital GmbH DVB-PC TV Star HD < dvb satellite receiver >
Once this was done, then both devices work correctly – at the same time..
This particular problem is not one that many users will encounter, but hopefully it will be fixed at some point..
Robert Gadsdon. February 21, 2014.
Just updated to NVIDIA driver version 331.49, and it installs and runs OK on Kernel 3.13 (3.13.3) without the need for any patches.
It can be made to work for Kernel 3.14, by editing the previous 3.13/3.14 combo patch mentioned in a previous article, and removing everything except the nv-linux.h portion of the patch.
Robert Gadsdon. February 19, 2014.
Update: Logged in, and was immediately aware of EXT4 filesystem errors..
[ 2520.305000] EXT4-fs error (device sda1): ext4_lookup:1437: inode #261634: comm xauth: deleted inode referenced: 307878 [ 2520.315000] EXT4-fs error (device sda1): ext4_lookup:1437: inode #261634: comm xauth: deleted inode referenced: 307878 [ 2520.325000] EXT4-fs error (device sda1): ext4_lookup:1437: inode #261634: comm xauth: deleted inode referenced: 307878 [ 2520.330000] EXT4-fs error (device sda1): ext4_lookup:1437: inode #261634: comm xauth: deleted inode referenced: 307878 [ 2520.340000] EXT4-fs error (device sda1): ext4_lookup:1437: inode #261634: comm xauth: deleted inode referenced: 307878 [ 2520.350000] EXT4-fs error (device sda1): ext4_lookup:1437: inode #261634: comm xauth: deleted inode referenced: 307878 EXT4-fs (sda1): initial error at 1392848030: ext4_lookup:1437: inode 261634 EXT4-fs (sda1): last error at 1392848030: ext4_lookup:1437: inode 261634
So – I have reverted to 3.8.13.18 again, for the time being! Fortunately, I was able to run fsck against the USB stick, to fix the (several!) errors.. So – I would not recommend trying this, for the time being!
RG.
Finally found the correct info for loading the ‘device tree’ 3.13 kernel for the Odroid U3 – from http://git.prahal.homelinux.net/odroid.git/tree/refs/heads/odroid_G9.
Most of the up-to-date (device tree) kernel boot instruction examples I found were for the XU model, and didn’t work for the U2/U3, but I finally found a combined zImage-with-dtb set of instructions, that actually worked, to produce the boot image, as follows:
Compile the kernel / zImage / dtbs / modules etc., and then: cat arch/arm/boot/zImage arch/arm/boot/dts/exynos4412-odroidu2.dtb > /boot/uboot/zImage_w_dtb
Then make a boot.scr image from the following boot.txt:
setenv initrd_high "0xffffffff"
setenv fdt_high "0xffffffff"
setenv fb_x_res "1920"
setenv fb_y_res "1080"
setenv hdmi_phy_res "1080"
setenv bootargs "console=tty1 console=ttySAC1,115200n8 fb_x_res=${fb_x_res} fb_y_res=${fb_y_res} hdmi_phy_res=${hdmi_phy_res} root=/dev/sda1 rootwait rw mem=2047M"
setenv bootcmd "fatload mmc 0:1 0x40008000 zImage_w_dtb; bootm 0x40008000"
boot
And the result:
Fedora release 20 (Heisenbug) Kernel 3.13.0 on an armv7l (ttySAC1) ................ # uname -a Linux rgodroid 3.13.0 #1 SMP PREEMPT Wed Feb 19 21:24:15 GMT 2014 armv7l armv7l armv7l GNU/Linux
The Odroid u-boot should be capable of loading the zImage and dtb separately, but I cannot – so far – find any details on how to do this for the U2/U3..
Thanks are due to Alban Browaeys, for all his work on producing this kernel version – patched for the Odroid U2/U3, and to the folks at ArchLinux, for the original boot.txt example I used as a starting point..
Robert Gadsdon. February 19, 2014.
Thanks to invaluable information from Mace Moneta, I have now been able to find the location of the (recent) release of Pidora 20 — now, for some reason, known as ‘Pidora 2014‘..
For details and links, see the comments section at the bottom of my previous article: http://rglinuxtech.com/?p=1048
I started the upgrade (from Pidora 19), which took several hours after the downloads had finished, and showed just how slow the Pi is!
After the download had completed, the first attempt to upgrade failed:
Running transaction check Running transaction test Transaction check error: file /usr/share/pixmaps/poweredby.png conflicts between attempted installs of pidora-logos-1-5.rpfr20.noarch and fedora-logos-httpd-21.0.1-1.fc20.noarch
So.. I re-ran the upgrade, as follows:
# yum --nogpgcheck distro-sync --exclude=pidora-logos
Many warning messages scrolled by:
....... /sbin/ldconfig: libraries libgpg-error.so.0.9.0 and libgpg-error.so.0.10.0 in directory /lib have same soname but different type. Updating : 2:libogg-1.3.0-6.fc20.armv6hl 101/2042 /sbin/ldconfig: libraries libfreetype.so.6.10.0 and libfreetype.so.6.10.2 in directory /lib have same soname but different type. /sbin/ldconfig: libraries libgpg-error.so.0.9.0 and libgpg-error.so.0.10.0 in directory /lib have same soname but different type. Updating : libtevent-0.9.19-1.fc20.armv6hl 102/2042 /sbin/ldconfig: libraries libfreetype.so.6.10.0 and libfreetype.so.6.10.2 in directory /lib have same soname but different type. /sbin/ldconfig: libraries libgpg-error.so.0.9.0 and libgpg-error.so.0.10.0 in directory /lib have same soname but different type. ......... etc...
But – finally – the upgrade completed..
Then, any attempt to do a # yum update failed, due to the previous conflict:
Transaction check error: file /usr/share/pixmaps/poweredby.png from install of pidora-logos-1-5.rpfr20.noarch conflicts with file from package fedora-logos-httpd-21.0.1-1.fc20.noarch
The usual # yum -y update –nogpgcheck –skip-broken doesn’t fix this, and this conflict stops any further yum updates from completing…
So… I manually downloaded the pidora-logos-1-5.rpfr20.noarch rpm, from http://koji.pidora.ca/koji/buildinfo?buildID=77112, and ‘forced’ the install, using
rpm -ivh <rpm file> --nodeps --force..
Finally!
Pidora release 2014 (Raspberry Pi Fedora Remix) Kernel 3.13.3+ on an armv6l (ttyAMA0)
- and Yum works OK, now..
After all the hard work that has gone in to producing this Pidora distro, I can’t understand why the release is so badly publicised.. The ‘Pidora’ Wiki hasn’t been updated for months, and still just refers to ‘Pidora 18′, as does the entry on the Raspberry Pi website itself.. Hopefully this will change, soon..
Robert Gadsdon. February 18, 2014.
Fedora 20 - KDE Desktop on ODROID U3
Found a suitable source tree for (old!) kernel 3.8.13.16:
git clone -b odroid-3.8.y --single-branch https://github.com/hardkernel/linux
- which compiled on the device itself with no problems – the old-fashioned way (# make zImage, etc..) and installed and ran without problems:
Fedora release 20 (Heisenbug) Kernel 3.8.13.16 on an armv7l (ttySAC1) ......... # uname -a Linux rgodroid 3.8.13.16 #1 SMP PREEMPT Wed Feb 12 16:53:50 EST 2014 armv7l armv7l armv7l GNU/Linux
The 3.12 source at that location was OK for the XU, but not (yet) for the U2/U3 – which is the model I have.. After some more searching, I found what appears to be a compatible version of kernel 3.13.0 at http://git.prahal.homelinux.net/odroid.git/tree/refs/heads/odroidu2_G8.
Next, I will compile this and discover how to get it installed, using device tree, and dtbs with uboot!
I now have KDE4 installed and running, and the response is good, once you disable most of the ‘window effects’… VLC is available (via rpmfusion) but – so far – doesn’t display the video, for some reason.. SMPLAYER (mplayer) does work, but at the moment HD playback is a bit sluggish.. I will get round to sorting this out later, after the ‘new’ kernel etc..
Robert Gadsdon. February 14, 2014..
Just updated the Raspberry Pi to Kernel 3.13.2, from GitHub:
# git clone -b rpi-3.13.y --single-branch https://github.com/raspberrypi/linux
No problems and the system runs OK..
Pidora release 19 (Raspberry Pi Fedora Remix) Kernel 3.13.2+ on an armv6l (ttyAMA0) ........ $ uname -a Linux rgpi 3.13.2+ #1 PREEMPT Wed Feb 12 14:12:55 GMT 2014 armv6l armv6l armv6l GNU/Linux
The Pi kernel updates are tracking the kernel.org stable releases quite nicely, but – sadly – the Pidora project seems to have stalled – again.. There have been no Pidora 19 updates for some time now.. Looking on the Koji build system, there are even some ‘Pidora 20′ armv6l builds for several rpms, now, but no sign of a Pidora 20 release, yet..
The situation is far better for armv7l and Fedora, and I now have Fedora 20 running on my new Odroid U3:
Fedora release 20 (Heisenbug) Kernel 3.8.13.4 on an armv7l (ttySAC1)
Robert Gadsdon. February 12, 2014.