Alex - thank you for your little hints,

/dev/sdf1 was choosen, 'cause /dev/sdf got me into the rainbow-screen (desperately!) After dd-ing the card automount(?) gets me 2 mounts in the filemanager: ROOT, EFI. What else should I do, than umount them?
(openSUSE-Leap42.3-ARM-JeOS-raspberrypi3.aarch64-2017.07.26-Build1.1.raw.xz)
The filesystem isn't destroyed, when I look a the card the next time.

>>I have a perfectly running system with this image. Indeed /dev/sdf1 needs to be /dev/sdf, there will be two partitions on the SD card and a lot of unused space.<<

Freek - are you talking about the RPi3b+?
I have the actual (this year - 2018) board RPi3B+ and I'm looking for an (openSUSE!)image, that at least boots this board! From http://download.opensuse.org/ports/aarch64/ I took different xz-Images (15.0 JeOS, 15.0 LXQT, 42.3 JeOS). - They all produce different sd-card partition layouts! But none of them boots a RPi3B+!

How can I get this running?

Regards ...


Am 27.07.18 um 11:38 schrieb Alexander Graf:

On 27.07.18 11:19, Sten Bert wrote:
Freek,

Unfortunally - no success!
Her'e my outputs:

./sd-card.sh
2+0 records in
1024+0 records out
1024 bytes (1.0 kB, 1.0 KiB) copied, 0.00331344 s, 309 kB/s

# df -h /dev/sdf1
Filesystem      Size  Used Avail Use% Mounted on
/dev/sdf1        31G   16K   31G   1% /run/media/root/A402-8523

# xzcat
openSUSE-Leap42.3-ARM-JeOS-raspberrypi3.aarch64-2017.07.26-Build1.1.raw.xz
| dd bs=4M of=/dev/sdf1 iflag=fullblock oflag=direct; sync
of= needs to be /dev/sdf, not /dev/sdf1 :).

383+1 records in
383+1 records out
1607467008 bytes (1.6 GB, 1.5 GiB) copied, 136.038 s, 11.8 MB/s

# df -h /dev/sdf1
Filesystem      Size  Used Avail Use% Mounted on
/dev/sdf1        31G   16K   31G   1% /run/media/root/A402-8523

Shouldn't be a difference there before/after?
Please also make sure you do not have any file system mounted when you
do the dd. Otherwise an unmount afterwards might corrupt the newly
written file system.


Alex

--
To unsubscribe, e-mail: [email protected]
To contact the owner, e-mail: [email protected]

Reply via email to