openSUSE ARM July 2017

arm@lists.opensuse.org

13 participants
12 discussions

[opensuse-arm] JeOS-2017-03-13 image for RPi 1 installs OK, Grub fails on reboot

by Alex Armstrong

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Greetings, I was testing: openSUSE-Tumbleweed-ARM-JeOS-raspberrypi.armv6l-2017.03.13-Build1.8.raw.xz from: http://download.opensuse.org/repositories/devel:/ARM:/Factory:/Contrib:/Ras… On RaspberryPi 1 Model B It installs fine - expands the file system, creates the dracut based init and boots to a usable system. But when I reboot, grub fails with: error: attempt to read or write outside of partition. and drops me to the grub rescue system. Poking around the rescue system, I've found that I can see 4 partitions, one which is ext2 and has the normal Linux files. From here, most of the recovery guides say to set the root and prefix variables and then load the normal module. I can execute the commands: set root=(hd0,gpt2) set prefix=(hd0,gpt2)/boot/grub2 and list the files in the various directories - normal.mod exists in /boot/grub2/arm-efi/ - but when I try: insmod normal I still get the error: attempt to read or write outside of partition. Somewhat interestingly, if I miss-type the prefix (say; /boot/grub) the error changes to a "file not found" one. I was hoping someone might have some ideas about what to try next. - -Alex -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iEYEARECAAYFAljUJnYACgkQYZYc2javKOllFQCeNiB6oZYpnKxgmKsbdUtcQNrO mOIAoJBXe8913EIzBfD04P/PqfPjFv9e =ZZC3 -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

3 years, 8 months

[opensuse-arm] aarch64 installer?

by Peter Czanik

Hi, I wanted to install Leap 42.3 on my SoftIron box, but the installer seems to be unavailable. If I click on 42.3 at http://download.opensuse.org/ports/aarch64/distribution/leap/ I get a 404 error. Last week an RC version installed fine, but now that's also unavailable. Any estimates, when 42.3 for Aarch64 becomes available? Bye, CzP -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

3 years, 11 months

[opensuse-arm] aarch64 installer?

by Peter Czanik

3 years, 12 months

[opensuse-arm] Build a downstream kernel in OBS

by Oscar C

Hi, Is there a guide on how to build a downstream kernel in obs like a upstream genuine kernel? I have a CHIP allwinner R8 with debian but I would like to use opensuse instead. I found a link in the wiki to a script which is supposed to help with this (http://users.suse.com/~dmueller/contrib_kernel.sh) but like is dead to me. Thanks! -- Cheers

3 years, 12 months

[opensuse-arm] Raspberry Pi Zero boot broken after update

by Andreas Färber

Hi, Updating my Raspberry Pi Zero to latest Tumbleweed plus staging U-Boot, I get an exception in GRUB. Could this be related to the native builds? U-Boot 2017.07-rc3 (Jul 10 2017 - 12:54:03 +0000) DRAM: 416 MiB RPI Zero (0x900093) MMC: sdhci@7e300000: 0 reading uboot.env ** Unable to read "uboot.env" from mmc0:1 ** Using default environment In: serial Out: vidconsole Err: vidconsole Net: No ethernet found. starting USB... USB0: Core Release: 2.80a scanning bus 0 for devices... 3 USB Device(s) found scanning usb for storage devices... 0 Storage Device(s) found Hit any key to stop autoboot: 0 switch to partitions #0, OK mmc0 is current device Scanning mmc 0:1... 21968 bytes read in 249 ms (85.9 KiB/s) Found EFI removable media binary efi/boot/bootarm.efi reading efi/boot/bootarm.efi 105984 bytes read in 30 ms (3.4 MiB/s) ## Starting EFI application at 01000000 ... Scanning disk sdhci(a)7e300000.blk... Found 1 disks Welcome to GRUB! data abort pc : [<18b36628>] lr : [<18b4e178>] reloc pc : [<febda628>] lr : [<febf2178>] sp : 19b5c150 ip : 00000074 fp : 00000001 r10: 18b58cb8 r9 : 00000000 r8 : 18b360e4 r7 : 18b36080 r6 : 00000000 r5 : 18b36978 r4 : 19b5c290 r3 : 00000000 r2 : 00000000 r1 : 18b4e478 r0 : 18b36080 Flags: nZCv IRQs off FIQs off Mode SVC_32 Resetting CPU ... resetting ... 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+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

4 years

[opensuse-arm] Orange Pi Prime

by Vladimir Nadvornik

Hi, I have new Orange Pi Prime board and I'd like to run openSUSE on it :) So far I took armbian image and replaced all userspace with openSUSE. It works ok for running osc and build. Then I tried to compile u-boot 2017-07 from Base:System:Staging. The board config is already there but it seems that there is problem with building SPL - there is this message during build: [ 246s] WARNING: BL31 file bl31.bin NOT found, resulting binary is non-functional [ 246s] Please read the section on ARM Trusted Firmware (ATF) in board/sunxi/README.sunxi64 BTW, the already enabled board Orange Pi PC2 seems to have the same problem. I haven't found anything like this in build service, do I understand it correctly that it needs to be packaged? Vladimir -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

4 years

Re: [opensuse-arm] tumbleweed updates for armv6hl ?

by Marcus Gould

Hi, (Please note that I've joined this mailinglist since this thread started) Re: [opensuse-arm] tumbleweed updates for armv6hl ? <https://lists.opensuse.org/opensuse-arm/2017-07/msg00021.html> * From: Michael Ströder <michael@xxxxxxxxxxxx> * Date: Thu, 13 Jul 2017 11:51:56 +0200 * Message-id: <74530af2-0e5e-6dd0-090e-80984ec86c63(a)stroeder.com <https://lists.opensuse.org/opensuse-arm/2017-07/msg00021.html>> Dirk Müller wrote: Unfortunately armv6hl is in a pretty bad state because it is still built in qemu emulation, and noone maintains that emulation layer. [..] Over the long run we need to find a different solution though (which could be dropping it alltogether, in the worst case). For now I take it as a positive sign that someone does actually care about it being available :-) Hmm, I have several rpi1 boards and it would be nice if they do not turn into Elektroschrott. The video output does not work but I use them headless anyway. Until two weeks ago zypper dup worked but currently the update is stuck with this message: Problem: libzypp-16.9.0-1.1.armv6hl requires libsolv-tools = 0.6.27, but this requirement cannot be provided deleted providers: libsolv-tools-0.6.27-2.1.armv6hl Solution 1: Following actions will be done: deinstallation of libzypp-16.9.0-1.1.armv6hl deinstallation of zypper-1.13.25-1.1.armv6hl Solution 2: keep obsolete libsolv-tools-0.6.27-2.1.armv6hl Solution 3: break libzypp-16.9.0-1.1.armv6hl by ignoring some of its dependencies I'd like to register myself as a RaspPi+armv6hl user who cares about the repo being available :-) and mention that I am also seeing similar sorts of issues: # *zypper dup --no-allow-vendor-change -d* Warning: You are about to do a distribution upgrade with all enabled repositories. Make sure these repositories are compatible before you continue. See 'man zypper' for more information about this command. Loading repository data... Reading installed packages... Computing distribution upgrade... 36 Problems: Problem: nothing provides zypper(auto-agree-with-product-licenses) needed by SUSEConnect-0.3.2-1.1.armv6hl Problem: libzypp-16.9.0-1.1.armv6hl requires libsolv-tools = 0.6.27, but this requirement cannot be provided Problem: yast2-perl-bindings-3.2.0-1.1.armv6hl requires perl = 5.24.0, but this requirement cannot be provided Problem: yast2-core-3.2.2-1.1.armv6hl requires perl = 5.24.0, but this requirement cannot be provided Problem: vim-8.0.566-2.1.armv6hl requires perl = 5.24.0, but this requirement cannot be provided Problem: yast2-perl-bindings-3.2.0-1.1.armv6hl requires perl = 5.24.0, but this requirement cannot be provided [3 More] Problem: yast2-core-3.2.2-1.1.armv6hl requires perl = 5.24.0, but this requirement cannot be provided [11 More] Problem: yast2-perl-bindings-3.2.0-1.1.armv6hl requires perl = 5.24.0, but this requirement cannot be provided [13 More] Problem: yast2-core-3.2.2-1.1.armv6hl requires perl = 5.24.0, but this requirement cannot be provided Problem: nothing provides zypper(auto-agree-with-product-licenses) needed by SUSEConnect-0.3.2-1.1.armv6hl Solution 1: keep obsolete SUSEConnect-0.3.0-1.1.armv6hl Solution 2: break SUSEConnect-0.3.2-1.1.armv6hl by ignoring some of its dependencies Choose from above solutions by number or skip, retry or cancel [1/2/s/r/c] (c): If I sit tight and wait, will this get fixed in some future maintenance? Thanks, Marcus.

4 years

[opensuse-arm] openSUSE-Leap42.3-ARM-JeOS-beaglebone.armv7l-2017.07.15

by Matwey V. Kornilov

Hello, I've just checked openSUSE-Leap42.3-ARM-JeOS-beaglebone.armv7l-2017.07.15 It boots and works as usual. So it seems that BBB is ready to 42.3 release. -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

4 years

[opensuse-arm] [FYI] larger amount of rebuild on TW aarch64

by Dirk Müller

Hi, in order to get rid of some older lib dependencies and enable ruby 2.4 stack I need to rebuild larger amounts of packages. Greetings, Dirk -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

4 years

[opensuse-arm] Re: Converting products to the new system

by Adrian Schröter

On Mittwoch, 12. Juli 2017, 08:19:02 CEST wrote Dominique Leuenberger / DimStar: > On Wed, 2017-07-12 at 08:13 +0200, Adrian Schröter wrote: > > Hi, > > > > Dimstar has started to convert the product builds to the new > > product-builder in Factory yesterday. > > > > Andreas Schwab did start also for ARM. > > > > I created the new definitions also for zSystems and PowerPC now. > > Shouldn't the package from openSUSE:Factory trickle through to the > ports? Yes, and it does. > They are all project lniks against openSUSE:Factory. Seems odd > that there is extra work involved in the ports (other than keeping the > .group files updated, which is done by bots - update pending) We do maintain the product configurations currently seperatly. You could of course also merge ARM/PPC/zSystems into your main package. We would not need the additional container then. However, that means you may need to change stuff in openSUSE:Factory to fix product builds in openSUSE:Factory:ARM. > As for removing _product from openSUSE:Factory - I think that's a good > thing to do, BUT it will, as far as I've seen, likely crash the factory > dashobard (is that finally under maintenance of the OBS team, see > fate#320770) I don't see that we committed to that, but we can take a look ;) -- Adrian Schroeter email: adrian(a)suse.de SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg) Maxfeldstraße 5 90409 Nürnberg Germany -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

4 years

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

openSUSE ARM July 2017