I'm see that iso images available but can't understand how to use it. All manuals says about compressed *.raw.xz images which must be unpacked (at least under windows) to write on SD card. I've tried to use win32dd or some other raw copy tools to write iso image to SD card (and even tried USB stick) but no luck. May be someone can explain how to use iso installer images to install system like it installed on normal PC.
On Sat, Jul 15, 2017 at 1:54 AM, shashilx@shashilx.com wrote:
I'm see that iso images available but can't understand how to use it. All manuals says about compressed *.raw.xz images which must be unpacked (at least under windows) to write on SD card. I've tried to use win32dd or some other raw copy tools to write iso image to SD card (and even tried USB stick) but no luck. May be someone can explain how to use iso installer images to install system like it installed on normal PC.
The iso installers are more for 64 bit enterprise devices and they are used just like
On Sat, Jul 15, 2017 at 12:10 PM, Peter Robinson pbrobinson@gmail.com wrote:
On Sat, Jul 15, 2017 at 1:54 AM, shashilx@shashilx.com wrote:
I'm see that iso images available but can't understand how to use it. All manuals says about compressed *.raw.xz images which must be unpacked (at least under windows) to write on SD card. I've tried to use win32dd or some other raw copy tools to write iso image to SD card (and even tried USB stick) but no luck. May be someone can explain how to use iso installer images to install system like it installed on normal PC.
The iso installers are more for 64 bit enterprise devices and they are used just like you would on an x86 device.
What are you trying to achieve?
I want to run installer and install from scratch on RPi 3 instead of using ready-to-use .raw image.
compressed *.raw.xz images which must be unpacked (at least under windows) to write on SD card.
https://en.wikipedia.org/wiki/XZ_Utils provides links to programs that should expand the .xz file on a Windows system. The expanded file is what must be copied to a SD card and used in an ARM device.
Note that the raw image has a modest size (in order to fit on an 8GB SD card.) I usually use 16GB or 32GB SD cards, and expand the ext4 root filesystem on the SD card to the maximum possible size for the card in use, before I boot on an ARM device. Any Fedora system can do this (x86 architecture is fine) using the parted, e2fsck, and resize2fs commands. This is not a necessary step, but it is easy to run out of space when there is only a few gigabytes available, as in the raw image.
It would be convenient if the First Boot operation offered an option to resize the root filesystem. Someone may have already done this, yet I failed to notice because of my habit.
Have no problems with uncompress it just want to use installer iso image but can't understand where I must put iso image (write to USB? or it can be writed to SD card, installer loads in RAM so I can use installation source as destination source?)
----- Original Message -----
Have no problems with uncompress it just want to use installer iso image but can't understand where I must put iso image (write to USB? or it can be writed to SD card, installer loads in RAM so I can use installation source as destination source?)
The script is for deploying the disk images. To do an actual installation on the rpi3 you would need to run a tftp server and pxe boot. Anaconda requires more than 1G RAM for a network install, so you will also need to nfs mount the squashfs. If you dont want to go through the pain of setting up the tftp server, you can likely hack up a minimal usb stick with the kernel/initrd and squashfs from the installation repo and a custom extlinux.conf pointing to the repo in the apend line. In either case you will need a mSD with the firmware and U-boot and install to USB attached disk.
Paul
arm mailing list -- arm@lists.fedoraproject.org To unsubscribe send an email to arm-leave@lists.fedoraproject.org