On 26.11.14 10:00, Freek de Kruijf wrote:
Op dinsdag 25 november 2014 14:09:06 schreef u:
On 25/11/14 09:32, Freek de Kruijf wrote:
Op dinsdag 25 november 2014 04:00:44 schreef Sid Boyce:
I use large sizes of SD cards.
After burning the image, e.g to /dev/sdb, remove the SD card and insert it again.
"gparted /dev/sdb"
Add the space of the rootfs partition to the unused space and change rootfs to the total calculated, click resize and Apply. Regards Sid.
I did that on a 16 GB card and removed /var/lib/YaST2/reconfig_system in order to be able to use it headless, but that did not work. However putting the freshly burned image in the RPi removing the card a little later from the RPi, removing /var/lib/YaST2/reconfig_system and reinserting the card in the RPi gave me a working system, accessible via ssh and with a large rootfs. There is also a swap partition at the end of about 500 MiB. Will try to remove that reconfig file right after burning to see if I get a working headless system with expanded rootfs.
That's strange as I have always done it that way on Beaglebone, Pandaboard, ODROID-X, ODROID-U3 and Parallella-16.
I always do "fsck -a /dev/sdb[12]" after resizing and on the odd occasion it reports that it cleared a dirty bit on the VFAT partition. Successfully boots every time. Regards Sid.
When applying the 13.2 image on the SD card, now there are three partitions on the card. A FAT partition, an ext3 partition and the rootfs is ext4. After initial use on the RPi there is a fourth partition at the end, a swap partition. So are we talking about the same type of image, a 13.2 image?
I tried the procedure to remove the reconfig file right after burning and before actually using the card in the RPi, but that did not work. Did not do a "fsck -a /dev/sdg{123}" after burning. Should I?
BTW. I noticed a change in naming of the image, first I used: openSUSE-13.2-ARM-JeOS-raspberrypi.armv7l-1.12.1-Build29.4.raw.xz now I use: openSUSE-13.2-ARM-JeOS-raspberrypi.armv6l-1.12.1-Build30.1.raw.xz
If I am right the architecture of the RPi is armv6l and not armv7l, isn't it? So now we have a properly named image?
I fixed the build to virtually run on an armv6 CPU rather than an armv7 CPU to fix up the file name. The contents should still be identical. The trick with the RPi image really is to synchronize GPT and MBR into a working hybrid GPT setup, just like on Apple Macs. You can also use the "gptsync" tool if you like. Alex -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org