On 03/14/2014 12:31 AM, Steve Underwood wrote:
On 03/13/2014 11:19 PM, Peter Robinson wrote:
On Thu, Mar 13, 2014 at 3:10 PM, Steve Underwood <steveu@xxxxxxxxxxx>
wrote:
On 03/12/2014 03:59 PM, Peter Robinson wrote:
Hi All,
Just thought I'd put this out on a dedicated thread for those that are
interested.
http://nullr0ute.com/2014/03/booting-pandaboard-with-fedora-20-ga/
The process for the first boot on the GA images is slightly manual and
documented in the post above, in the next few days we'll get some
updates bits out to fix the issue properly moving forward and have the
fixes into rawhide nightlies RSN.
X/display output is the current main issue I'm aware of so you'll need
a serial console.
Let us know of any success, failure or other issues.
Thanks for your patience! There's some more learnt about booting ARM
here and we'll make sure the fix is integrated for any of the other
platforms this issue might affect.
Peter
I have Fedora 20 up on a Pandaboard using those instructions.
However, I
need to enter
etenv bootm_size 0x20000000
setenv bootargs console=${console} vram=${vram} root=LABEL=_/ ro
rootwait
ext4load mmc 0:3 0x82000000 /boot/vmlinuz-3.11.10-301.fc20.armv7hl
ext4load mmc 0:3 0x88080000 /boot/uInitrd-3.11.10-301.fc20.armv7hl
ext4load mmc 0:3 0x88000000
/boot/dtb-3.11.10-301.fc20.armv7hl/omap4-panda.dtb
bootz 0x82000000 0x88080000 0x88000000
every time I boot. The instructions imply that I should only need to
do this
after a kernel upgrade.
Can someone tell me if these changes are really supposed to be
persistent?
If you read the details we need to put out a new version of
arm-boot-config to make the setting persistent. A new kernel will
still use the old settings which are broken. There's a scratch build
[1] if you're game but we want to ensure there's no regressions on
existing supported platforms before pushing out an official update.
[1] http://koji.fedoraproject.org/koji/taskinfo?taskID=6625820
That seems to work OK. Now I can boot properly from a 32G micro-SD
card. Its speed seems reasonable. The ethernet port is working OK. I
have a 32G USB memory stick plugged in and giving respectable speed,
so USB seems solid so far. I have XFCE running at the correct
resolution. I have everything to to date with "yum update". Things are
looking pretty good.
The 802.11 isn't loading automatically. Using "modprobe wl12xx" gets
it loaded, but I haven't checked whether it works so far. I am using
wired ethernet.
The CPU frequency control doesn't seem to be there. I think the OMAP4
should work just like the Sitara on the BeagleBoneBlack. The Sitrara
gives you the directory /sys/devices/system/cpu/cpu0/cpufreq, but I
can't see that on the Panda board. I have kernel-tools installed, and
"cpupower frequency-info" also shows nothing. The machine feels quite
responsive, so I guess its running at full speed.
A word of warning. The kernel in the Fedora 20 distribution has bugs
which cause the whole machine to crash when certain networking
operations are attempted. Update as soon as you get Fedora installed.
The latest kernels seem pretty solid.
Regards,
Steve
Oops, I spoke too soon. With the 3.13.6-200 kernel the XFCE desktop no
longer starts.
Regards,
Steve
_______________________________________________
arm mailing list
arm@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/arm
