On 11/02/2012 10:07 AM, Derek Atkins wrote:
"David A. Marlin" <dmarlin@xxxxxxxxxx> writes:
On 11/01/2012 10:52 AM, Derek Atkins wrote:
David,
I would be happy to help, however I have been unable to get the F17-GA
image to run on my Guruplug.. If I could get that running then I could
attempt to help with the F18 work.
Thank you for offering to help. I was looking at the F17-GA test results:
https://fedoraproject.org/wiki/Architectures/ARM/Quality_Assurance/2012-06-18-VFAD-Fedora_17_Test_Day#Overall_Test_Results_and_Board_Assignment
and the Kirkwood image was tested on GuruPlug. Perhaps you can ping
one of the testers of that image for help getting it working on your
Guruplug.
Thank you for the pointer. I see one difference between the uboot
settings I was using and what they used for testing is that I was
following the wiki which said:
setenv bootargs 'console=ttyS0,115200 root=LABEL=rootfs rootwait'
Whereas they used:
setenv bootargs 'console=ttyS0,115200 root=/dev/sdb2 rootwait'
So perhaps there is an issue with the LABEL? I will try again with this
different setting and see if that helps. If so, then perhaps the wiki
needs to be updated.
All the images we create have the root partition labeled 'rootfs',
however if you know the physical device where the root partition
resides, you can use it directly as they did (i.e., /dev/sdb2). The
only time using the label should be an issue is if more than one device
used the same label, i.e., if the same disk image was copied to more
than one device, however some people have reported problems using the
label with certain versions of U-Boot.
I'll report back.
Thank you, and good luck.
d.marlin
=======
-derek
_______________________________________________
arm mailing list
arm@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/arm
