It was brought to my attention that the F18 Alpha lacked a Kirkwood image, which we had for F17. We have been creating images for F18 using livemedia-creator (anaconda and lorax), where the F17 images were manually created using a custom script.
The process we use is described on the wiki:
http://fedoraproject.org/wiki/Architectures/ARM/Installer
All the builders we have used for creating the F18 images are F17 armv7hl (hard-fp) systems. I personally have no experience with the Kirkwood devices, so I don't know what is needed to set up the image or configure the bootloader.
We would appreciate volunteers running F17 on Kirkwood devices to help in creating an F18 image for those devices. The only development involved would be customizing the kickstart file to 1) include any special packages required for the device, and 2) set up any bootloader specific files/scripts needed for the device. The remainder of the effort would be to build and test the image. The hardware requirements include an ARMv5 device running F17-GA or later with access to external storage (requires space for the packages being installed and the resulting image) and swap (requires >1GB total memory).
We have created v7hl images using a Trim Slice (1GB memory plus 500MB swap) with external (USB) hard drive, so something similar would probably work.
I am willing to provide assistance and answer questions about using the tools and modifying the kickstart config file, but I have no ARMv5 hardware on which to build or test these images.
Thank you,
d.marlin
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.
-derek
David Marlin dmarlin@redhat.com writes:
It was brought to my attention that the F18 Alpha lacked a Kirkwood image, which we had for F17. We have been creating images for F18 using livemedia-creator (anaconda and lorax), where the F17 images were manually created using a custom script.
The process we use is described on the wiki:
http://fedoraproject.org/wiki/Architectures/ARM/Installer
All the builders we have used for creating the F18 images are F17 armv7hl (hard-fp) systems. I personally have no experience with the Kirkwood devices, so I don't know what is needed to set up the image or configure the bootloader.
We would appreciate volunteers running F17 on Kirkwood devices to help in creating an F18 image for those devices. The only development involved would be customizing the kickstart file to 1) include any special packages required for the device, and 2) set up any bootloader specific files/scripts needed for the device. The remainder of the effort would be to build and test the image. The hardware requirements include an ARMv5 device running F17-GA or later with access to external storage (requires space for the packages being installed and the resulting image) and swap (requires >1GB total memory).
We have created v7hl images using a Trim Slice (1GB memory plus 500MB swap) with external (USB) hard drive, so something similar would probably work.
I am willing to provide assistance and answer questions about using the tools and modifying the kickstart config file, but I have no ARMv5 hardware on which to build or test these images.
Thank you,
d.marlin
arm mailing list arm@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/arm
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-1...
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.
Thanks again,
d.marlin =======
-derek
David Marlin dmarlin@redhat.com writes:
It was brought to my attention that the F18 Alpha lacked a Kirkwood image, which we had for F17. We have been creating images for F18 using livemedia-creator (anaconda and lorax), where the F17 images were manually created using a custom script.
The process we use is described on the wiki:
http://fedoraproject.org/wiki/Architectures/ARM/Installer
All the builders we have used for creating the F18 images are F17 armv7hl (hard-fp) systems. I personally have no experience with the Kirkwood devices, so I don't know what is needed to set up the image or configure the bootloader.
We would appreciate volunteers running F17 on Kirkwood devices to help in creating an F18 image for those devices. The only development involved would be customizing the kickstart file to 1) include any special packages required for the device, and 2) set up any bootloader specific files/scripts needed for the device. The remainder of the effort would be to build and test the image. The hardware requirements include an ARMv5 device running F17-GA or later with access to external storage (requires space for the packages being installed and the resulting image) and swap (requires >1GB total memory).
We have created v7hl images using a Trim Slice (1GB memory plus 500MB swap) with external (USB) hard drive, so something similar would probably work.
I am willing to provide assistance and answer questions about using the tools and modifying the kickstart config file, but I have no ARMv5 hardware on which to build or test these images.
Thank you,
d.marlin
arm mailing list arm@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/arm
"David A. Marlin" dmarlin@redhat.com 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-1...
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.
I'll report back.
-derek
On 11/02/2012 10:07 AM, Derek Atkins wrote:
"David A. Marlin" dmarlin@redhat.com 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-1...
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
David,
I'd be very happy to help with building images. I have a Dreamplug currently running F18 from an old nightly snapshot, which has been fully updated via yum. I'd happily put F17 on that and have a go at creating some images, or would it be acceptable to create the images on an F18 system?
I have a USB hard drive available, so that's not a problem. You make reference to 1Gb of memory, but my Dreamplugs and Sheevaplugs have 512Mb of memory. Will that be sufficient if there is enough swap space?
I've never used kickstart files before but am happy to learn.
Would the guys at Seneca College have anything useful to help with this, since I see that the nightly composes of images started again yesterday?
With best wishes, Quentin
On Wed, 2012-10-31 at 17:09 -0500, David Marlin wrote:
It was brought to my attention that the F18 Alpha lacked a Kirkwood image, which we had for F17. We have been creating images for F18 using livemedia-creator (anaconda and lorax), where the F17 images were manually created using a custom script.
The process we use is described on the wiki:
http://fedoraproject.org/wiki/Architectures/ARM/Installer
All the builders we have used for creating the F18 images are F17 armv7hl (hard-fp) systems. I personally have no experience with the Kirkwood devices, so I don't know what is needed to set up the image or configure the bootloader.
We would appreciate volunteers running F17 on Kirkwood devices to help in creating an F18 image for those devices. The only development involved would be customizing the kickstart file to 1) include any special packages required for the device, and 2) set up any bootloader specific files/scripts needed for the device. The remainder of the effort would be to build and test the image. The hardware requirements include an ARMv5 device running F17-GA or later with access to external storage (requires space for the packages being installed and the resulting image) and swap (requires >1GB total memory).
We have created v7hl images using a Trim Slice (1GB memory plus 500MB swap) with external (USB) hard drive, so something similar would probably work.
I am willing to provide assistance and answer questions about using the tools and modifying the kickstart config file, but I have no ARMv5 hardware on which to build or test these images.
Thank you,
d.marlin
arm mailing list arm@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/arm
On 11/01/2012 12:21 PM, Quentin Armitage wrote:
David,
I'd be very happy to help with building images. I have a Dreamplug currently running F18 from an old nightly snapshot, which has been fully updated via yum. I'd happily put F17 on that and have a go at creating some images, or would it be acceptable to create the images on an F18 system?
It would be acceptable, but it is currently untested. The only potential issue I can see is that the F18 tools (anaconda and lorax) do not yet make images, so you would have to install the F17 versions from xpfa. I'm not sure if that would cause dependency issues (F17 tools on F18).
I have a USB hard drive available, so that's not a problem. You make reference to 1Gb of memory, but my Dreamplugs and Sheevaplugs have 512Mb of memory. Will that be sufficient if there is enough swap space?
My understanding is that as long as the total memory is sufficient (RAM + swap) it should be ok. Again, I have not tested this, as my builders all have 1GB or greater, but it should work.
I've never used kickstart files before but am happy to learn.
There are examples on the Installer wiki page, and I'll be happy to help. The only things that are different between platforms, and that would need to change, is the package list (if the *plugs need any special packages that are not already included) and the bootloader setup in the %post section. The commands in the %post section are just bash commands, so no new scripting language or special commands are required. I'd start with the trimslice kickstart as a base, since it is the simplest, and modify from there.
Would the guys at Seneca College have anything useful to help with this, since I see that the nightly composes of images started again yesterday?
I can't answer for them, but IIUC once we have stable kickstart config files into git (spins-kickstart) and the F18 tools are working for images, I believe this will all be done through koji. In the mean time, it's a manual process, but nothing says it could not be scripted (i.e., a cron job at seneca).
Please look over the Installer wiki and let me know if you have questions.
Thank you,
d.marlin =======
With best wishes, Quentin
On Wed, 2012-10-31 at 17:09 -0500, David Marlin wrote:
It was brought to my attention that the F18 Alpha lacked a Kirkwood image, which we had for F17. We have been creating images for F18 using livemedia-creator (anaconda and lorax), where the F17 images were manually created using a custom script.
The process we use is described on the wiki:
http://fedoraproject.org/wiki/Architectures/ARM/InstallerAll the builders we have used for creating the F18 images are F17 armv7hl (hard-fp) systems. I personally have no experience with the Kirkwood devices, so I don't know what is needed to set up the image or configure the bootloader.
We would appreciate volunteers running F17 on Kirkwood devices to help in creating an F18 image for those devices. The only development involved would be customizing the kickstart file to 1) include any special packages required for the device, and 2) set up any bootloader specific files/scripts needed for the device. The remainder of the effort would be to build and test the image. The hardware requirements include an ARMv5 device running F17-GA or later with access to external storage (requires space for the packages being installed and the resulting image) and swap (requires >1GB total memory).
We have created v7hl images using a Trim Slice (1GB memory plus 500MB swap) with external (USB) hard drive, so something similar would probably work.
I am willing to provide assistance and answer questions about using the tools and modifying the kickstart config file, but I have no ARMv5 hardware on which to build or test these images.
Thank you,
d.marlin
arm mailing list arm@lists.fedoraproject.org mailto:arm@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/arm
On 11/01/2012 10:21 AM, Quentin Armitage wrote:
Would the guys at Seneca College have anything useful to help with this, since I see that the nightly composes of images started again yesterday?
That's me playing with the old nightly generation tools. Best to stick with official media.
-
Brendan Conoboy -
d.marlin -
Derek Atkins -
Quentin Armitage