Re: [opensuse-arm] Fwd: Updates for Leap Ports
On Mon, 30 Jul 2018 12:43:44 +0200 Axel Braun wrote: > Maybe someone in this group knows the answer? > > -- Weitergeleitete Nachricht -- > > Betreff: Updates for Leap Ports > Datum: Dienstag, 24. Juli 2018, 20:19:46 CEST > Von: Axel Braun > An: opensuse-fact...@opensuse.org > > Good evening, > > quick question - once an update is accepted to Leap 15 Maintenance, > when and how is this pushed to openSUSE-Ports-Leap-15-Update Repo? > > Thanks > Axel > - > > > Hi, In theory, every update should be propagated to all the supported arches, except when the package does not build or has no functionaly on a given arch. E.g, we don't need to ship mainframe specific tools on x86 or arm* Is there a specific package or repo causing problems ? Cheers, Peter -- To unsubscribe, e-mail: opensuse-arm+unsubscr...@opensuse.org To contact the owner, e-mail: opensuse-arm+ow...@opensuse.org
Re: [solved] Re: [opensuse-arm] How to get openSUSE aarch64 on a RPi3B+?
2018-07-30 21:38 GMT+02:00 Sten Bert : > > Am 30.07.18 um 20:42 schrieb Andreas Färber: >> >> Am 30.07.2018 um 07:33 schrieb Sten Bert: >>> >>> Here's my result for Leap 15.0 from >>> >>> http://download.opensuse.org/ports/aarch64/distribution/leap/15.0/appliances/: >>> >>> xzcat >>> >>> openSUSE-Leap15.0-ARM-JeOS-efi.aarch64-2018.07.02-Buildlp150.1.1.install.tar.xz >>> | dd bs=4M of=/dev/sdf iflag=fullblock oflag=direct; sync >> >> .tar.xz != .raw.xz >> And that's not a -raspberrypi3 image either. >> >> If you dd the wrong file it can't possibly work. :) >> >>> >>> openSUSE-Leap15.0-ARM-LXQT-raspberrypi3.aarch64-2018.07.02-Buildlp150.1.1.raw.xz >>> >>> - booted after activating 1st partition as active, but stopped with >>> "incompatible licence, Press any key to continue" >> >> Don't understand what exactly you're doing there and where exactly >> you're seeing that message. >> >>> - with and without extraconfig.txt >> >> If it boots, you don't have to touch extraconfig.txt. You only need that >> if ubootconfig.txt with that contents is missing (it was moved from one >> file to another and - Murphy's Law - the Tumbleweed image got published >> in between). >> >> Cheers, >> Andreas >> >> P.S. Please don't top-post. > > SUCCESS - SUCCESS - SUCSESS - SUCCESS > > Andreas you're so right, > taking the "Raspberry3"-named images worked! > > The challenge was to find out the right image for the RPi3B+ among the > plenty of ARM images. > Following results for systematic attempts on 2 Raspberry3 images from > http://download.opensuse.org/ports/aarch64: > Valid for all: arm_control=0x200 is already in config.txt (no > extraconfig.txt necessary) > > 1) Leap 15.0 JeOS: > openSUSE-Leap15.0-ARM-JeOS-raspberrypi3.aarch64-2018.07.02-Buildlp150.1.1.raw.xz.part > - booting to login prompt - wonderful! > > 2) Leap 15.0 LXQT: > openSUSE-Leap15.0-ARM-LXQT-raspberrypi3.aarch64-2018.07.02-Buildlp150.1.1.raw.xz > - "You are in emergency mode. ..." > - Timed out waiting for device dev-disk-by\x2duuid-9982\x2d4ABD.device. > - Dependency failed for /boot/efi. > - Dependency failed for Local File Systems. > > - after several attempts - success > > I have some trouble in the LXQt DE with "libEGL warning: DRI2: failed to > authenticate" - but I think this sould ba a separate thread. > > Alessio, > thanks for your help, but unfortunately I could only get JeOS. > osc getbinaries openSUSE:Factory:ARM:Live X11:X11-raspberrypi3.aarch64 > images aarch64 > Server returned an error: HTTP Error 404: Not Found My mistake. My explanation was indeed confusing. The first JeOS should stay, only the one defining the image name should change: JeOS:X11-raspberrypi3.aarch64 JeOS:KDE-raspberrypi3.aarch64 JeOS:XFCE-raspberrypi3.aarch64 And so on Sorry about that. Alessio > > Regards > > > -- > To unsubscribe, e-mail: opensuse-arm+unsubscr...@opensuse.org > To contact the owner, e-mail: opensuse-arm+ow...@opensuse.org > -- To unsubscribe, e-mail: opensuse-arm+unsubscr...@opensuse.org To contact the owner, e-mail: opensuse-arm+ow...@opensuse.org
[opensuse-arm] Re: [solved] Re: How to get openSUSE aarch64 on a RPi3B+?
On Mon 30 Jul 2018 09:38:55 PM CDT, Sten Bert wrote: >Am 30.07.18 um 20:42 schrieb Andreas Färber: >> Am 30.07.2018 um 07:33 schrieb Sten Bert: >>> Here's my result for Leap 15.0 from >>> http://download.opensuse.org/ports/aarch64/distribution/leap/15.0/appliances/: >>> >>> xzcat >>> openSUSE-Leap15.0-ARM-JeOS-efi.aarch64-2018.07.02-Buildlp150.1.1.install.tar.xz >>> | dd bs=4M of=/dev/sdf iflag=fullblock oflag=direct; sync >> .tar.xz != .raw.xz >> And that's not a -raspberrypi3 image either. >> >> If you dd the wrong file it can't possibly work. :) >> >>> openSUSE-Leap15.0-ARM-LXQT-raspberrypi3.aarch64-2018.07.02-Buildlp150.1.1.raw.xz >>> >>> - booted after activating 1st partition as active, but stopped with >>> "incompatible licence, Press any key to continue" >> Don't understand what exactly you're doing there and where exactly >> you're seeing that message. >> >>> - with and without extraconfig.txt >> If it boots, you don't have to touch extraconfig.txt. You only need >> that if ubootconfig.txt with that contents is missing (it was moved >> from one file to another and - Murphy's Law - the Tumbleweed image >> got published in between). >> >> Cheers, >> Andreas >> >> P.S. Please don't top-post. >SUCCESS - SUCCESS - SUCSESS - SUCCESS > >Andreas you're so right, >taking the "Raspberry3"-named images worked! > >The challenge was to find out the right image for the RPi3B+ among the >plenty of ARM images. >Following results for systematic attempts on 2 Raspberry3 images from >http://download.opensuse.org/ports/aarch64: >Valid for all: arm_control=0x200 is already in config.txt (no >extraconfig.txt necessary) > >1) Leap 15.0 JeOS: >openSUSE-Leap15.0-ARM-JeOS-raspberrypi3.aarch64-2018.07.02-Buildlp150.1.1.raw.xz.part >- booting to login prompt - wonderful! > >2) Leap 15.0 LXQT: >openSUSE-Leap15.0-ARM-LXQT-raspberrypi3.aarch64-2018.07.02-Buildlp150.1.1.raw.xz >- "You are in emergency mode. ..." >- Timed out waiting for device dev-disk-by\x2duuid-9982\x2d4ABD.device. >- Dependency failed for /boot/efi. >- Dependency failed for Local File Systems. > >- after several attempts - success > >I have some trouble in the LXQt DE with "libEGL warning: DRI2: failed >to authenticate" - but I think this sould ba a separate thread. > >Alessio, >thanks for your help, but unfortunately I could only get JeOS. >osc getbinaries openSUSE:Factory:ARM:Live X11:X11-raspberrypi3.aarch64 >images aarch64 >Server returned an error: HTTP Error 404: Not Found > >Regards > Hi That's because the prefix is JeOS not X11 ;) A quick browse on OBS openSUSE:Factory:ARM:Live soon figured that out FWIW, you may be interested in this forum thread as well; http://forums.opensuse.org/showthread.php?t=531539 -- Cheers Malcolm °¿° SUSE Knowledge Partner (Linux Counter #276890) SLES 15 | GNOME Shell 3.26.2 | 4.12.14-25.3-default HP 255 G4 Notebook | E2-7110 X4 @ 1.80 GHz | AMD Radeon R3 up 2 days 19:12, 2 users, load average: 0.44, -- To unsubscribe, e-mail: opensuse-arm+unsubscr...@opensuse.org To contact the owner, e-mail: opensuse-arm+ow...@opensuse.org
[solved] Re: [opensuse-arm] How to get openSUSE aarch64 on a RPi3B+?
Am 30.07.18 um 20:42 schrieb Andreas Färber: Am 30.07.2018 um 07:33 schrieb Sten Bert: Here's my result for Leap 15.0 from http://download.opensuse.org/ports/aarch64/distribution/leap/15.0/appliances/: xzcat openSUSE-Leap15.0-ARM-JeOS-efi.aarch64-2018.07.02-Buildlp150.1.1.install.tar.xz | dd bs=4M of=/dev/sdf iflag=fullblock oflag=direct; sync .tar.xz != .raw.xz And that's not a -raspberrypi3 image either. If you dd the wrong file it can't possibly work. :) openSUSE-Leap15.0-ARM-LXQT-raspberrypi3.aarch64-2018.07.02-Buildlp150.1.1.raw.xz - booted after activating 1st partition as active, but stopped with "incompatible licence, Press any key to continue" Don't understand what exactly you're doing there and where exactly you're seeing that message. - with and without extraconfig.txt If it boots, you don't have to touch extraconfig.txt. You only need that if ubootconfig.txt with that contents is missing (it was moved from one file to another and - Murphy's Law - the Tumbleweed image got published in between). Cheers, Andreas P.S. Please don't top-post. SUCCESS - SUCCESS - SUCSESS - SUCCESS Andreas you're so right, taking the "Raspberry3"-named images worked! The challenge was to find out the right image for the RPi3B+ among the plenty of ARM images. Following results for systematic attempts on 2 Raspberry3 images from http://download.opensuse.org/ports/aarch64: Valid for all: arm_control=0x200 is already in config.txt (no extraconfig.txt necessary) 1) Leap 15.0 JeOS: openSUSE-Leap15.0-ARM-JeOS-raspberrypi3.aarch64-2018.07.02-Buildlp150.1.1.raw.xz.part - booting to login prompt - wonderful! 2) Leap 15.0 LXQT: openSUSE-Leap15.0-ARM-LXQT-raspberrypi3.aarch64-2018.07.02-Buildlp150.1.1.raw.xz - "You are in emergency mode. ..." - Timed out waiting for device dev-disk-by\x2duuid-9982\x2d4ABD.device. - Dependency failed for /boot/efi. - Dependency failed for Local File Systems. - after several attempts - success I have some trouble in the LXQt DE with "libEGL warning: DRI2: failed to authenticate" - but I think this sould ba a separate thread. Alessio, thanks for your help, but unfortunately I could only get JeOS. osc getbinaries openSUSE:Factory:ARM:Live X11:X11-raspberrypi3.aarch64 images aarch64 Server returned an error: HTTP Error 404: Not Found Regards -- To unsubscribe, e-mail: opensuse-arm+unsubscr...@opensuse.org To contact the owner, e-mail: opensuse-arm+ow...@opensuse.org
Re: [opensuse-arm] How to debug Grub config
2018-07-30 21:47 GMT+03:00 Andreas Färber : > Am 30.07.2018 um 18:35 schrieb Matwey V. Kornilov: >> 2018-07-30 14:23 GMT+03:00 Alexander Graf : >>> On 07/29/2018 01:19 PM, Matwey V. Kornilov wrote: I am (stilL) trying to boot openSUSE on Rock64. I use JeOS image from Contrib:Rockchip and manually built bootloader (with 0001-XXX-openSUSE-XXX-Prepend-partition-.patch). > [...]>> What U-Boot version are you basing on? There were a few >>> bugs with the device path exposure in 2018.05 IIRC. >> >> I am running downstream u-boot with rock64 support: >> https://github.com/ayufan-rock64/linux-u-boot >> It is based on 2017.09 > > What's missing for Rock64 in upstream? There's some RK3328 EVB code: > https://git.denx.de/?p=u-boot.git;a=tree;f=board/rockchip/evb_rk3328;h=1d01065444611e4512a57072f97a6f39c30239fa;hb=HEAD config, dts, and the most important thing is that memory initialization in TPL should be different for Rock64 than for EVB. But TPL doesn't work currently even in downstream (I have to use rockchip proprietary binary), so it can be easy to cherry-pick partial support (SPL + U-Boot). > > Regards, > Andreas > > -- > SUSE Linux GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany > GF: Felix Imendörffer, Jane Smithard, Graham Norton > HRB 21284 (AG Nürnberg) -- With best regards, Matwey V. Kornilov -- To unsubscribe, e-mail: opensuse-arm+unsubscr...@opensuse.org To contact the owner, e-mail: opensuse-arm+ow...@opensuse.org
Re: [opensuse-arm] How to debug Grub config
Am 30.07.2018 um 18:35 schrieb Matwey V. Kornilov: > 2018-07-30 14:23 GMT+03:00 Alexander Graf : >> On 07/29/2018 01:19 PM, Matwey V. Kornilov wrote: >>> I am (stilL) trying to boot openSUSE on Rock64. I use JeOS image from >>> Contrib:Rockchip and manually built bootloader (with >>> 0001-XXX-openSUSE-XXX-Prepend-partition-.patch). [...]>> What U-Boot version are you basing on? There were a few >> bugs with the device path exposure in 2018.05 IIRC. > > I am running downstream u-boot with rock64 support: > https://github.com/ayufan-rock64/linux-u-boot > It is based on 2017.09 What's missing for Rock64 in upstream? There's some RK3328 EVB code: https://git.denx.de/?p=u-boot.git;a=tree;f=board/rockchip/evb_rk3328;h=1d01065444611e4512a57072f97a6f39c30239fa;hb=HEAD Regards, Andreas -- SUSE Linux GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Felix Imendörffer, Jane Smithard, Graham Norton HRB 21284 (AG Nürnberg) -- To unsubscribe, e-mail: opensuse-arm+unsubscr...@opensuse.org To contact the owner, e-mail: opensuse-arm+ow...@opensuse.org
Re: [opensuse-arm] How to get openSUSE aarch64 on a RPi3B+?
Am 30.07.2018 um 07:33 schrieb Sten Bert: > Here's my result for Leap 15.0 from > http://download.opensuse.org/ports/aarch64/distribution/leap/15.0/appliances/: > > xzcat > openSUSE-Leap15.0-ARM-JeOS-efi.aarch64-2018.07.02-Buildlp150.1.1.install.tar.xz > | dd bs=4M of=/dev/sdf iflag=fullblock oflag=direct; sync .tar.xz != .raw.xz And that's not a -raspberrypi3 image either. If you dd the wrong file it can't possibly work. :) > openSUSE-Leap15.0-ARM-LXQT-raspberrypi3.aarch64-2018.07.02-Buildlp150.1.1.raw.xz > > - booted after activating 1st partition as active, but stopped with > "incompatible licence, Press any key to continue" Don't understand what exactly you're doing there and where exactly you're seeing that message. > - with and without extraconfig.txt If it boots, you don't have to touch extraconfig.txt. You only need that if ubootconfig.txt with that contents is missing (it was moved from one file to another and - Murphy's Law - the Tumbleweed image got published in between). Cheers, Andreas P.S. Please don't top-post. -- SUSE Linux GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Felix Imendörffer, Jane Smithard, Graham Norton HRB 21284 (AG Nürnberg) -- To unsubscribe, e-mail: opensuse-arm+unsubscr...@opensuse.org To contact the owner, e-mail: opensuse-arm+ow...@opensuse.org
Re: [opensuse-arm] How to debug Grub config
On 07/30/2018 06:35 PM, Matwey V. Kornilov wrote: 2018-07-30 14:23 GMT+03:00 Alexander Graf : Hi Matwey, On 07/29/2018 01:19 PM, Matwey V. Kornilov wrote: Hello, I am (stilL) trying to boot openSUSE on Rock64. I use JeOS image from Contrib:Rockchip and manually built bootloader (with 0001-XXX-openSUSE-XXX-Prepend-partition-.patch). And currently I see the following new issue: mmc1 is current device Scanning mmc 1:2... 52462 bytes read in 43 ms (1.2 MiB/s) Failed to mount ext2 filesystem... ** Unrecognized filesystem type ** Scanning mmc 1:1... Found EFI removable media binary efi/boot/bootaa64.efi reading efi/boot/bootaa64.efi 1247744 bytes read in 58 ms (20.5 MiB/s) ## Starting EFI application at 0200 ... Card did not respond to voltage select! mmc_init: -95, time 10 Scanning disk rksd...@ff52.blk... Scanning disk rksd...@ff50.blk... Found 2 disks Welcome to GRUB! ethernet@ff54 Waiting for PHY auto negotiation to complete. TIMEOUT ! Could not initialize PHY ethernet@ff54 GNU GRUB version 2.02 Minimal BASH-like line editing is supported. For the first word, TAB lists possible command completions. Anywhere else TAB lists possible device or file completions. grub> I see that both dtb file and EFI GRUB executable are loaded. But instead of GRUB menu I see GRUB command line. I suppose it means that grub failed to fetch GRUB configuration. How could I debug further what is wrong? Correct. Grub failed to fetch the configuration because it failed to initialize the prefix correctly. If you run "set" on the command line, you should be able to see that the prefix is wrong. You can as interim step set it manually using the set command and then run "normal". That should get you a working grub menu. Indeed, the prefix is (hd0)/efi/boot, instead of (hd0,gpt1)/efi/boot. The really important question is why grub could not determine its prefix correctly though. What U-Boot version are you basing on? There were a few bugs with the device path exposure in 2018.05 IIRC. I am running downstream u-boot with rock64 support: https://github.com/ayufan-rock64/linux-u-boot It is based on 2017.09 Yes, that probably has one or two bugs in the device path support. Can you try upstream instead? Alex -- To unsubscribe, e-mail: opensuse-arm+unsubscr...@opensuse.org To contact the owner, e-mail: opensuse-arm+ow...@opensuse.org
Re: [opensuse-arm] How to debug Grub config
2018-07-30 14:23 GMT+03:00 Alexander Graf : > Hi Matwey, > > On 07/29/2018 01:19 PM, Matwey V. Kornilov wrote: >> >> Hello, >> >> I am (stilL) trying to boot openSUSE on Rock64. I use JeOS image from >> Contrib:Rockchip and manually built bootloader (with >> 0001-XXX-openSUSE-XXX-Prepend-partition-.patch). And currently I see the >> following new issue: >> >> mmc1 is current device >> Scanning mmc 1:2... >> 52462 bytes read in 43 ms (1.2 MiB/s) >> Failed to mount ext2 filesystem... >> ** Unrecognized filesystem type ** >> Scanning mmc 1:1... >> Found EFI removable media binary efi/boot/bootaa64.efi >> reading efi/boot/bootaa64.efi >> 1247744 bytes read in 58 ms (20.5 MiB/s) >> ## Starting EFI application at 0200 ... >> Card did not respond to voltage select! >> mmc_init: -95, time 10 >> Scanning disk rksd...@ff52.blk... >> Scanning disk rksd...@ff50.blk... >> Found 2 disks >> Welcome to GRUB! >> >> ethernet@ff54 Waiting for PHY auto negotiation to complete. >> TIMEOUT ! >> Could not initialize PHY ethernet@ff54 >> GNU GRUB version 2.02 >> >> Minimal BASH-like line editing is supported. For the first word, TAB >> lists possible command completions. Anywhere else TAB lists possible >> device or file completions. >> >> >> >> grub> >> >> >> I see that both dtb file and EFI GRUB executable are loaded. But instead >> of GRUB menu I see GRUB command line. I suppose it means that grub >> failed to fetch GRUB configuration. How could I debug further what is >> wrong? > > > Correct. Grub failed to fetch the configuration because it failed to > initialize the prefix correctly. If you run "set" on the command line, you > should be able to see that the prefix is wrong. You can as interim step set > it manually using the set command and then run "normal". That should get you > a working grub menu. > Indeed, the prefix is (hd0)/efi/boot, instead of (hd0,gpt1)/efi/boot. > The really important question is why grub could not determine its prefix > correctly though. What U-Boot version are you basing on? There were a few > bugs with the device path exposure in 2018.05 IIRC. I am running downstream u-boot with rock64 support: https://github.com/ayufan-rock64/linux-u-boot It is based on 2017.09 > > > Alex > -- With best regards, Matwey V. Kornilov -- To unsubscribe, e-mail: opensuse-arm+unsubscr...@opensuse.org To contact the owner, e-mail: opensuse-arm+ow...@opensuse.org
Re: [opensuse-arm] How to debug Grub config
Hi Matwey, On 07/29/2018 01:19 PM, Matwey V. Kornilov wrote: Hello, I am (stilL) trying to boot openSUSE on Rock64. I use JeOS image from Contrib:Rockchip and manually built bootloader (with 0001-XXX-openSUSE-XXX-Prepend-partition-.patch). And currently I see the following new issue: mmc1 is current device Scanning mmc 1:2... 52462 bytes read in 43 ms (1.2 MiB/s) Failed to mount ext2 filesystem... ** Unrecognized filesystem type ** Scanning mmc 1:1... Found EFI removable media binary efi/boot/bootaa64.efi reading efi/boot/bootaa64.efi 1247744 bytes read in 58 ms (20.5 MiB/s) ## Starting EFI application at 0200 ... Card did not respond to voltage select! mmc_init: -95, time 10 Scanning disk rksd...@ff52.blk... Scanning disk rksd...@ff50.blk... Found 2 disks Welcome to GRUB! ethernet@ff54 Waiting for PHY auto negotiation to complete. TIMEOUT ! Could not initialize PHY ethernet@ff54 GNU GRUB version 2.02 Minimal BASH-like line editing is supported. For the first word, TAB lists possible command completions. Anywhere else TAB lists possible device or file completions. grub> I see that both dtb file and EFI GRUB executable are loaded. But instead of GRUB menu I see GRUB command line. I suppose it means that grub failed to fetch GRUB configuration. How could I debug further what is wrong? Correct. Grub failed to fetch the configuration because it failed to initialize the prefix correctly. If you run "set" on the command line, you should be able to see that the prefix is wrong. You can as interim step set it manually using the set command and then run "normal". That should get you a working grub menu. The really important question is why grub could not determine its prefix correctly though. What U-Boot version are you basing on? There were a few bugs with the device path exposure in 2018.05 IIRC. Alex -- To unsubscribe, e-mail: opensuse-arm+unsubscr...@opensuse.org To contact the owner, e-mail: opensuse-arm+ow...@opensuse.org
[opensuse-arm] Fwd: Updates for Leap Ports
Maybe someone in this group knows the answer? -- Weitergeleitete Nachricht -- Betreff: Updates for Leap Ports Datum: Dienstag, 24. Juli 2018, 20:19:46 CEST Von: Axel Braun An: opensuse-fact...@opensuse.org Good evening, quick question - once an update is accepted to Leap 15 Maintenance, when and how is this pushed to openSUSE-Ports-Leap-15-Update Repo? Thanks Axel - -- To unsubscribe, e-mail: opensuse-arm+unsubscr...@opensuse.org To contact the owner, e-mail: opensuse-arm+ow...@opensuse.org
Re: [opensuse-arm] How to get openSUSE aarch64 on a RPi3B+?
In the case of Tumbleweed, you can download the latest images with the following command: $ osc getbinaries openSUSE:Factory:ARM:Live JeOS:JeOS-raspberrypi3.aarch64 images aarch64 Depending on the flavor, just substitute JeOS with E20, KDE, XFCE, LXQT, X11 For Leap: $ osc getbinaries openSUSE:Leap:15.0:Ports:Live JeOS:JeOS-raspberrypi3.aarch64 images_arm aarch64 2018-07-30 7:33 GMT+02:00 Sten Bert : > Thank you guys for the replies! > > Andreas, when I write "But none of them boots a RPi3B+!", that means - I've > tested these appliances! > > Here's my result for Leap 15.0 from > http://download.opensuse.org/ports/aarch64/distribution/leap/15.0/appliances/: > xzcat > openSUSE-Leap15.0-ARM-JeOS-efi.aarch64-2018.07.02-Buildlp150.1.1.install.tar.xz > | dd bs=4M of=/dev/sdf iflag=fullblock oflag=direct; sync > 114+1 records in > 114+1 records out > 479426560 bytes (479 MB, 457 MiB) copied, 40.2379 s, 11.9 MB/s > > - left an unpartitioned medium - not booting (that's logical): > > # fdisk -l /dev/sdf > Disk /dev/sdf: 30.2 GiB, 32395755520 bytes, 63272960 sectors > Units: sectors of 1 * 512 = 512 bytes > Sector size (logical/physical): 512 bytes / 512 bytes > I/O size (minimum/optimal): 512 bytes / 512 bytes > > .. for TW (hope t h i s is the current version): > xzcat > openSUSE-Tumbleweed-ARM-JeOS-efi.aarch64-2018.05.11-Build1.1.install.tar.xz > | dd bs=4M of=/dev/sdf iflag=fullblock oflag=direct; sync > 114+1 records in > 114+1 records out > 479426560 bytes (479 MB, 457 MiB) copied, 40.2379 s, 11.9 MB/s > > - same as above > > > openSUSE-Leap15.0-ARM-LXQT-raspberrypi3.aarch64-2018.07.02-Buildlp150.1.1.raw.xz > > - booted after activating 1st partition as active, but stopped with > "incompatible licence, Press any key to continue" > - with and without extraconfig.txt > > > OBS search gives me 6 pages of result and "osc ls openSUSE:Tumbleweed" has > no results. Please excuse my weak knowledge about OBS. As I had to move from > SUSE STUDIO - this stuff is new for me. > > Regards Sten > > Am 29.07.18 um 20:10 schrieb Freek de Kruijf: > >> Op zondag 29 juli 2018 17:20:32 CEST schreef Sten Bert: >>> >>> 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+! >> >> No I wasn't. Sorry I missed the + in your subject. Still you always have >> to dd >> to the whole disk, so /dev/sdf; not /dev/sdf1, when you use an image. >> >> If I understand the message from Andreas correctly, you can use the image >> for >> Tumbleweed or Leap 15.0, which you apparently already have. However after >> dd- >> ing, you do "mount /dev/sdf1 /mnt". In /mnt/ there is a file >> extraconfig.txt >> or you create that file and enter a line "arm_control=0x200", most likely >> without the "'s. After "umount /mnt", you put the SD in the RPi3B+ and >> boot. >> That should do the trick. >> >> Good luck. >> > > -- > To unsubscribe, e-mail: opensuse-arm+unsubscr...@opensuse.org > To contact the owner, e-mail: opensuse-arm+ow...@opensuse.org > -- To unsubscribe, e-mail: opensuse-arm+unsubscr...@opensuse.org To contact the owner, e-mail: opensuse-arm+ow...@opensuse.org
