On 10/31/2014 08:55 PM, Andy Moorhouse wrote:
Hello,
I've started to experiment with RSEL on my Odroid U3:
http://hardkernel.com/main/products/prdt_info.php
Is anyone else using this board? There is no Wiki for it. I would be
happy to write one, if useful - basically I flashed the official Odroid
Fedora 20, then did what seems to be the "usual" thing of copying
/lib/modules & /lib/firmware.
A wiki entry would be very useful.
One problem straight away is that CPU2 and CPU3 are continually being
started up and shutdown. I get dmesg errors about them, like this:
CPU2: Booted secondary processor
CPU3: Booted secondary processor
... a few seconds
CPU2: Shutdown
CPU3: Shutdown
I know the hardware is OK as it is fine with the official Fedora &
Ubuntu images. Any ideas?
I have never seen anything like this before. Could it be power
management in the kernel doing this? Could it be that other distros boot
with the "quiet" kernel boot option so this is still happening just not
getting logged?
Does it happen if you generate a load on all 4 CPUs? Or does it in that
case just stay running with all 4 CPUs without shutting them down?
The other thing to check is to boot Fedora and check what kernel modules
are loaded, if anything is in /etc/sysconfig/modules/ and/or
/etc/modprobe.d/ and copy those across if they contain anything that
seems relevant. It might also be worth checking cpuspeed or whatever
recent Fedora uses and see if there is a specific CPU power management
governor in play that you might need to load a module for and activate.
Also - I would like to be able to ssh onto my RSEL Odroid, but yum
install openssh-server fails with broken dependencies (installed
telnet-server & started xinetd to allow me to get on to copy & paste this!):
Error: Package: openssh-server-5.3p1-52.el6.2.armv5tel (rsel6)
Requires: openssh = 5.3p1-52.el6.2
Installed: openssh-5.3p1-84.1.el6.armv5tel (installed)
openssh = 5.3p1-84.1.el6
Available: openssh-5.3p1-52.el6.2.armv5tel (rsel6)
openssh = 5.3p1-52.el6.2
First do:
yum update
That should get you the updated redsleeve-release package, which will in
turn point you at the up to date repository.
Then you can use yum to install and update anything else.
Now that you mentioned this, maybe I should reduce the old legacy
repository to just the updated release package to avoid further
confusion and save some space on the server...
Many thanks for any help, I like the RSEL project and hope it continues!
_______________________________________________
users mailing list
[email protected]
http://lists.redsleeve.org/mailman/listinfo/users
