- openSUSE ARM

[opensuse-arm] Cloud ARM servers
by Bill Merriam 10 Dec '17

10 Dec '17

I discovered today that a hosting provider in Europe offers very cheap ARMv7 and ARMv8 cloud servers. https://www.scaleway.com/ The following observations are from a few hours of testing and may not be correct. It appears the ARM servers are NOT virtualized but run on special miniature servers. The ARMv7 uses a Marvell 385 SOC and the ARMv8 uses a Cavium SOC. Marvell is in the process of buying Cavium. Opensuse does not generally appear among the offered distributions. The exception to this was opensuse 13.2 on the ARMv7 system. I was able to upgrade it to 42.3 but they don't use the kernel from my image. I guess they need a custom kernel. Their kernel has many limitations. It doesn't support iptables so you can't have a firewall. I am hoping someone can convince them to offer an ARMv8 Leap 42.3 with a decent kernel. Bill -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

2 1

[opensuse-arm] Re: [opensuse-factory] New Tumbleweed snapshot 20171120 released!
by Andreas Färber 27 Nov '17

27 Nov '17

Hi Daniel, Let's move the discussion to opensuse-arm list. Am 23.11.2017 um 12:07 schrieb Daniel Molkentin: > On 11/22/2017 06:31 PM, Andreas Färber wrote: >> Am 22.11.2017 um 04:25 schrieb Dominique Leuenberger: >>> ==== kernel-source ==== >>> Version update (4.13.12 -> 4.14.0) >>> Subpackages: kernel-default kernel-default-devel kernel-devel kernel-docs kernel-macros kernel-syms >>> >>> - Update to 4.14-final. >> On the aarch64 based Pine64 board it has been observed that the updated >> dtb-allwinner package now requires the axp20x-regulator module in the >> initrd for using the MMC driver, and its parent module axp20x-rsb does >> not get loaded automatically even if added to the initrd. > I would prefer if that would be fixed in the kernel by adding the proper > dependencies. > Is there any chance for that? There's multiple issues at play here: 1) This is not a module compile-time dependency issue, but rather a run-time dependency issue, which AFAIU dracut is not resolving today. As a result the JeOS images in openSUSE:Factory:ARM etc. contain a number of add_drivers entries to load such extra modules: https://build.opensuse.org/package/view_file/openSUSE:Factory:ARM/JeOS/conf… That is of course ugly and would be nice to get resolved differently. Dracut would need to parse the Device Tree in /sys/firmware/ to discover what regulator, clock, power domain, etc. nodes are being referenced, then read their "compatible" strings and resolve them to the modules to add. The kernel uses generic API calls such as clk_get() and regulator_get(), thus no compile-time dependency for e.g. mmc modules. However when updating from 4.13 to 4.14 or from 4.14-rc4 to -rc8 it would've still read the current Device Tree and not discovered this new dependency for next boot. And Kiwi images get built in KVM, which will have a different Device Tree than the user's system or even ACPI. So I don't see a full solution yet. Let me know if I should report this somewhere upstream - it didn't seem a distro-specific issue for our Bugzilla. https://www.kernel.org/pub/linux/utils/boot/dracut/dracut.html#_troubleshoo… explains what info to include in a bug report, but not actually where to file it. ;) No link on dracut.wiki.kernel.org either. 2) axp20x-rsb driver does have MODULE_DEVICE_TABLE(of, ...), so it is unclear to me why the DT -> module resolution for auto-loading is not working here. https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/dri… It is almost certainly an upstream kernel issue, possibly in sunxi-rsb bus driver. Stefan has already reported this on #linux-sunxi. > Otherwise, the "proper" dracut patch would > looks something like the attached one. Hm, instmod is just the equivalent of "add_drivers", is it? That would not be enough here. Also not all ARM systems need this driver, it's an extra chip on some boards only. What you could do is more generally add all =drivers/mfd drivers. But if we keep adding drivers by category instead of addressing the underlying discovery issue, we risk at some point the initrd getting too large for low-RAM systems. 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

2 1

Re: [opensuse-arm] Re: EspressoBin
by Matwey V. Kornilov 27 Nov '17

27 Nov '17

2017-10-22 9:31 GMT+03:00 Rick Ashford <Rick.Ashford(a)suse.com>: > There is a great thread on the Armbian forum about the EspressoBin, and it > helped me get things up and running with Tumbleweed. > > One of the guys there has a public Dropbox link that includes their images > for flashing the u-boot loader: > https://www.dropbox.com/sh/kmgmo1uubhcczx5/AAAYEvTIFxpBr0dHG2QcapTza?dl=0 > > The thread: > https://forum.armbian.com/index.php?/topic/4089-espressobin-support-develop… > > With their boot loader I was able to finally use BTRFS images as well as PXE > boot. It also has an EFI load function in the help that I need to get around > to trying. Well, If armian u-boot is able to boot our standard EFI-Grub JeOS, then we can recommend to use it with openSUSE and don't reinvent the wheel. > > Rick Ashford > Sales Engineering Manager - West > SUSE Linux > rick.ashford(a)suse.com > Office: 512-782-4318 > Mobile: 512-731-3035 > > On Oct 21, 2017, at 12:32 PM, Matwey V. Kornilov <matwey.kornilov(a)gmail.com> > wrote: > > 2017-10-21 19:47 GMT+03:00 Matwey V. Kornilov <matwey.kornilov(a)gmail.com>: > > 2017-10-21 19:35 GMT+03:00 Matwey V. Kornilov <matwey.kornilov(a)gmail.com>: > > 2017-10-20 18:02 GMT+03:00 Matwey V. Kornilov <matwey.kornilov(a)gmail.com>: > > 2017-10-20 17:37 GMT+03:00 Alexander Graf <agraf(a)suse.de>: > > > > On 20.10.17 16:21, Matwey V. Kornilov wrote: > > 20.10.2017 17:12, Alexander Graf пишет: > > > > On 20.10.17 13:57, Matwey V. Kornilov wrote: > > Hi, > > > I've just received EspressoBin 1G. Any success stories how to run openSUSE? > > > > I think you'll basically have to somehow flash a working U-Boot with > > distro boot onto it and then just dd the tumbleweed/42.3 iso onto a usb > > stick and cross your fingers that gets you to a point where you can > > install :) > > > It has microsd card, I think it should be able to boot from sd, no? > > I also need to to find serial console pins on the board :) > > > There seems to be a lengthy discussion on the mailing list. I guess you > > can select the boot device using DIP switches though? > > > Yes, I can. I think it is preferred way. Need to find expected layout > > to place u-boot image. > > > Well, at least while booting from SATA, they say that BootRom looks > > for code starting with zero offset, which implies that there can not > > be any GPT partition table. > > Probably, it is similar for SD. If so, we need to flash our EFI-aware > > u-boot instead of upstream one. > > > > Well, SATA flash image from here > > > http://wiki.espressobin.net/tiki-index.php?page=Boot+ESPRESSObin+from+SATA+… > > > suits for booting from microsd card, when it is flushed from zero > > offset and boot selection switchs are set to 7. > > > At least, there is non-destructive way to check out u-boot image. > > > Double checked. Seems that microsd boot doesn't work and is not > supported. At least for my V5 board. > It just falls back to SPINOR > > > > > http://espressobin.net/forums/topic/how-to-flash-u-boot/ > > > > Alex > > > > > -- > > With best regards, > > Matwey V. Kornilov > > > > > -- > > With best regards, > > Matwey V. Kornilov > > > > > -- > > With best regards, > > Matwey V. Kornilov > > > > > -- > With best regards, > Matwey V. Kornilov > -- > To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org > To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org > > -- With best regards, Matwey V. Kornilov -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

2 10

[opensuse-arm] Re: [opensuse-factory] New Tumbleweed snapshot 20171120 released!
by Andreas Färber 22 Nov '17

22 Nov '17

Am 22.11.2017 um 04:25 schrieb Dominique Leuenberger: > ==== kernel-source ==== > Version update (4.13.12 -> 4.14.0) > Subpackages: kernel-default kernel-default-devel kernel-devel kernel-docs kernel-macros kernel-syms > > - Update to 4.14-final. > - commit c152297 > - rpm/kernel-binary.spec.in: rename kGraft to KLP (fate#323682) > - commit 0ed191d On the aarch64 based Pine64 board it has been observed that the updated dtb-allwinner package now requires the axp20x-regulator module in the initrd for using the MMC driver, and its parent module axp20x-rsb does not get loaded automatically even if added to the initrd. https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/a… Workaround is to add to your /etc/dracut.conf.d/sunxi_modules.conf: force_drivers+=" axp20x-rsb " and (if after the update) to re-run dracut by, e.g., mkinitrd. Without such an initrd change it will wait indefinitely for the root partition on SD card on next boot. Selecting an older kernel in GRUB will not help - only manually loading an older dtb in U-Boot can help (if e.g. you had multiversion enabled). 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

1 0

[opensuse-arm] Error in C++ compiler on Rasberry Pi 2
by Freek de Kruijf 22 Nov '17

22 Nov '17

Recently I tried to use all Tumbleweed images on my three Raspberry Pi's (1B, 2B, and 3B). I did not experience problems with booting the image. Also upgrading to the newest version works OK. After that I tried to generate a third party package from GitHub, SBFspot, om my Raspberry Pi 2B. Generating means a.o. compiling a C++ module. The compiler produced a fatal internal error, which I reported on bugzilla. https://bugzilla.opensuse.org/show_bug.cgi?id=1068967 I would not expect such an error from a compiler. Should I report this error also somewhere upstream? If, yes, where? -- fr.gr. Freek de Kruijf member openSUSE -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

1 0

[opensuse-arm] Samsung Chromebook (Snow) status?
by Daniel Bischof 20 Nov '17

20 Nov '17

Hi, I tried openSUSE-Tumbleweed-ARM-XFCE-chromebook.armv7l-2017.07.22-Build1.1 recently, but it just beeps and kicks me back to the boot screen immediately. No messages on screen, partition resizing, etc. Any hints? Some cgpt magic I could try from ChromeOS perhaps? Best regards, --D. -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

4 10

[opensuse-arm] armvl7 guest kernel crashes on build.opensuse.org
by Harald Welte 20 Nov '17

20 Nov '17

Since about Novebmer 15 I'm experiencing guest kernel crashes on build.opensuse.org when building armv7l packages. I reported this to the OBS folks in https://lists.opensuse.org/opensuse-buildservice/2017-11/msg00035.html but in https://lists.opensuse.org/opensuse-buildservice/2017-11/msg00036.html I was redirected to opensuse-arm, as the problem appears to be with the guest kernel and not with the build node. Regards, Harald -- - Harald Welte <laforge(a)gnumonks.org> http://laforge.gnumonks.org/ ============================================================================ "Privacy in residential applications is a desirable marketing option." (ETSI EN 300 175-7 Ch. A6)

3 2

[opensuse-arm] Moving SoC specific files from JeOS/KIWI config.sh to separate packages
by Stefan Brüns 18 Nov '17

18 Nov '17

Hi, currently config.sh creates several SoC specific files ad-hoc (i.e. using echo). This has several drawbacks: - it bloats config.sh (e.g 840 lines for the omap beagle /var/lib/alsa/ asound.state) - it creates files which are not tracked by RPM - most importantly, these files are never updated All these files could be moved into some SoC specific package, e.g. soc- config-$(kiwi-iname). If there are no objections, I will prepare an appropriate package and submit to Factory. The next step then is to remove the config file creation from the JeOS files and Require the SoC specific package instead. The list of affected files (sorted by kiwi image name): arndale: /etc/dracut.conf.d/exynos_modules.conf [1] /etc/modprobe.d/90-blacklist-xhci.conf chromebook: /etc/dracut.conf.d/exynos_modules.conf [1] /etc/X11/xorg.conf.d/50-touchpad.conf /etc/modules-load.d/cros-ec-keyb.conf beagle: /etc/dracut.conf.d/omap_modules.conf /etc/modprobe.d/50-omapdrm.conf /var/lib/alsa/asound.state panda: /etc/dracut.conf.d/omap_modules.conf /etc/modprobe.d/50-omapdrm.conf beaglebone: /etc/dracut.conf.d/beagleboneblack_modules.conf pine64, cubietruck, cubieboard, olinuxino: /etc/dracut.conf.d/sunxi_modules.conf sabrelite: /etc/dracut.conf.d/sabrelite_modules.conf /etc/modules-load.d/imx6.conf raspberrypi: /etc/dracut.conf.d/raspberrypi_modules.conf [2] /etc/modprobe.d/90-blacklist-vc4.conf raspberrypi2: /etc/dracut.conf.d/raspberrypi_modules.conf [2] raspberrypi3: /etc/dracut.conf.d/raspberrypi_modules.conf [2] /etc/modprobe.d/50-rpi3.conf socfpgade0nanosoc: /etc/dracut.conf.d/socfpga_modules.conf odroidc2, nanopik2: /etc/dracut.conf.d/meson_gxbb_modules.conf m400: /etc/sysconfig/network/ifcfg-enp1s0 Kind regards, Stefan [1] contents of exynos_modules.conf for chromebook and arndale differs [2] contents of raspberrypi_modules.conf for rpi1/rpi2/rpi3 differs -- Stefan Brüns / Bergstraße 21 / 52062 Aachen home: +49 241 53809034 mobile: +49 151 50412019

4 4

[opensuse-arm] xf86-video-armsoc crashes X server
by Guillaume Gardet 18 Nov '17

18 Nov '17

Hi, I did not tested Chromebook for a while... and it was quite broken. I fixed our JeOS image boot, and now, I am working on graphic images. The problem is if we use xf86-video-armsoc, it crashes X server. A workaround is to use FBDEV driver, but it would be nice to fix ARMSOC driver! If you have any idea or want to join to help to fix it, please do it. :) GDB output: ******************************************************************************** Program terminated with signal SIGABRT, Aborted. #0 0xb6967e5c in raise () from /lib/libc.so.6 Thread 1 (Thread 0xb6fc3010 (LWP 1967)): #0 0xb6967e5c in raise () from /lib/libc.so.6 No symbol table info available. #1 0xb69695e0 in abort () from /lib/libc.so.6 No symbol table info available. #2 0x005cf7b8 in OsAbort () at utils.c:1361 No locals. #3 0x00497f20 in ddxGiveUp (error=EXIT_ERR_ABORT, error@entry=6184816) at xf86Init.c:1011 i = <optimized out> #4 0x0049800c in AbortDDX (error=6184816, error@entry=EXIT_ERR_ABORT) at xf86Init.c:1055 i = <optimized out> #5 0x005d590c in AbortServer () at log.c:874 No locals. #6 0x005d6490 in FatalError (f=0x60142c "Caught signal %d (%s). Server aborting\n") at log.c:1015 args = {__ap = 0xbef1e024} args2 = {__ap = 0xbef1e024} beenhere = 1 #7 0x005cc49c in OsSigHandler (signo=11, sip=0xbef1e040, unused=<optimized out>) at osinit.c:154 unused = <optimized out> sip = 0xbef1e040 signo = 11 #8 <signal handler called> No symbol table info available. #9 xf86InitViewport (pScr=0x835398) at xf86Cursor.c:104 No locals. #10 0x0049a1cc in InitOutput (pScreenInfo=0xbef1e604, pScreenInfo@entry=0x639464 <screenInfo>, argc=6440076, argc@entry=4534188, argv=0x833c88, argv@entry=0x0) at xf86Init.c:634 i = 0 j = <optimized out> k = <optimized out> scr_index = <optimized out> modulelist = <optimized out> optionlist = 0x859008 screenpix24 = <optimized out> pix24 = <optimized out> pix24From = X_DEFAULT pix24Fail = 0 autoconfig = <optimized out> sigio_blocked = 0 want_hw_access = <optimized out> configured_device = <optimized out> #11 0x00452fac in dix_main (argc=4534188, argv=0x0, envp=<optimized out>) at main.c:197 i = <optimized out> alwaysCheckForInput = {0, 1} #12 0xb6950b68 in __libc_start_main () from /lib/libc.so.6 No symbol table info available. #13 0x0043affc in _start () at ../sysdeps/arm/start.S:110 No locals. Backtrace stopped: previous frame identical to this frame (corrupt stack?) ******************************************************************************** Xorg.0.log is here: ******************************************************************************** [ 46.639] X.Org X Server 1.19.5 Release Date: 2017-10-12 [ 46.639] X Protocol Version 11, Revision 0 [ 46.639] Build Operating System: openSUSE SUSE LINUX [ 46.639] Current Operating System: Linux linux 4.13.12-1-lpae #1 SMP PREEMPT Wed Nov 8 11:21:09 UTC 2017 (9151c66) armv7l [ 46.639] Kernel command line: root=/dev/disk/by-id/mmc-SU04G_0x06500ce9-part3 loader=uboot disk=/dev/disk/by-id/mmc-SU04G_0x06500ce9 resume=/dev/disk/by-id/mmc-SU04G_0x06500ce9-part4 loglevel=3 splash=silent plymouth.enable=0 console=ttySAC3,115200n8 console=tty [ 46.639] Build Date: 16 November 2017 01:04:09PM [ 46.640] [ 46.640] Current version of pixman: 0.34.0 [ 46.640] Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. [ 46.640] Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. [ 46.640] (==) Log file: "/var/log/Xorg.0.log", Time: Thu Oct 26 14:30:03 2017 [ 46.653] (==) Using config file: "/etc/X11/xorg.conf" [ 46.653] (==) Using config directory: "/etc/X11/xorg.conf.d" [ 46.653] (==) Using system config directory "/usr/share/X11/xorg.conf.d" [ 46.671] (==) ServerLayout "DefaultLayout" [ 46.671] (**) |-->Screen "DefaultScreen" (0) [ 46.671] (**) | |-->Monitor "<default monitor>" [ 46.672] (**) | |-->Device "Mali FBDEV" [ 46.672] (**) | |-->GPUDevice "Mali FBDEV" [ 46.672] (**) | |-->GPUDevice "DefaultDevice" [ 46.672] (==) No monitor specified for screen "DefaultScreen". Using a default monitor configuration. [ 46.672] (**) Option "DontZap" "false" [ 46.672] (**) Option "StandbyTime" "0" [ 46.672] (**) Option "SuspendTime" "0" [ 46.672] (**) Option "OffTime" "0" [ 46.672] (==) Automatically adding devices [ 46.672] (==) Automatically enabling devices [ 46.672] (==) Automatically adding GPU devices [ 46.672] (==) Max clients allowed: 256, resource mask: 0x1fffff [ 46.684] (WW) The directory "/usr/share/fonts/Type1/" does not exist. [ 46.684] Entry deleted from font path. [ 46.684] (WW) The directory "/usr/share/fonts/100dpi" does not exist. [ 46.684] Entry deleted from font path. [ 46.687] (WW) The directory "/usr/share/fonts/cyrillic" does not exist. [ 46.687] Entry deleted from font path. [ 46.687] (WW) The directory "/usr/share/fonts/misc/sgi" does not exist. [ 46.687] Entry deleted from font path. [ 46.688] (==) FontPath set to: /usr/share/fonts/misc:unscaled, /usr/share/fonts/75dpi:unscaled, /usr/share/fonts/ghostscript/, /usr/share/fonts/truetype/, built-ins [ 46.688] (==) ModulePath set to "/usr/lib/xorg/modules" [ 46.688] (**) Extension "XFree86-DGA" is disabled [ 46.688] (II) The server relies on udev to provide the list of input devices. If no devices become available, reconfigure udev or disable AutoAddDevices. [ 46.688] (II) Loader magic: 0x6f0ed0 [ 46.688] (II) Module ABI versions: [ 46.688] X.Org ANSI C Emulation: 0.4 [ 46.688] X.Org Video Driver: 23.0 [ 46.688] X.Org XInput driver : 24.1 [ 46.689] X.Org Server Extension : 10.0 [ 46.692] (++) using VT number 7 [ 46.692] (II) systemd-logind: logind integration requires -keeptty and -keeptty was not provided, disabling logind integration [ 46.695] (II) xfree86: Adding drm device (/dev/dri/card0) [ 46.702] (II) no primary bus or device found [ 46.702] falling back to /sys/devices/platform/exynos-drm/drm/card0 [ 46.702] (II) LoadModule: "glx" [ 46.708] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so [ 46.863] (II) Module glx: vendor="X.Org Foundation" [ 46.863] compiled for 1.19.5, module version = 1.0.0 [ 46.863] ABI class: X.Org Server Extension, version 10.0 [ 46.863] (II) LoadModule: "armsoc" [ 46.864] (II) Loading /usr/lib/xorg/modules/drivers/armsoc_drv.so [ 46.871] (II) Module armsoc: vendor="X.Org Foundation" [ 46.871] compiled for 1.19.5, module version = 1.4.1 [ 46.871] Module class: X.Org Video Driver [ 46.871] ABI class: X.Org Video Driver, version 23.0 [ 46.871] (II) ARMSOC: Driver for ARM Mali compatible chipsets [ 46.891] (WW) Falling back to old probe method for armsoc [ 46.891] (II) No BusID or DriverName specified - opening /dev/dri/card0 [ 46.891] (II) Got BusID exynos-drm [ 46.916] (II) Opened DRM [ 46.916] (II) DeviceName is [/dev/dri/card0] [ 46.916] (II) bus_id is [exynos-drm] [ 46.916] (II) DriverName is [exynos] [ 46.916] (II) version is [1.0.0] [ 46.917] (II) Screen:0, CRTC:0 [ 46.933] (II) No BusID or DriverName specified - opening /dev/dri/card0 [ 46.933] (II) Got BusID exynos-drm [ 46.966] (II) Opened DRM [ 46.966] (II) DeviceName is [/dev/dri/card0] [ 46.966] (II) bus_id is [exynos-drm] [ 46.966] (II) DriverName is [exynos] [ 46.966] (II) version is [1.0.0] [ 46.966] (II) Screen:1, CRTC:1 [ 46.983] (EE) Screen 1 deleted because of no matching config section. [ 46.983] (II) UnloadModule: "armsoc" [ 46.983] (**) ARMSOC(0): Depth 24, (--) framebuffer bpp 32 [ 46.983] (==) ARMSOC(0): RGB weight 888 [ 46.983] (==) ARMSOC(0): Using gamma correction (1.0, 1.0, 1.0) [ 46.983] (==) ARMSOC(0): Default visual is TrueColor [ 46.983] (II) No BusID or DriverName specified - opening /dev/dri/card0 [ 46.983] (II) Got BusID exynos-drm [ 47.016] (II) Opened DRM [ 47.016] (II) DeviceName is [/dev/dri/card0] [ 47.016] (II) bus_id is [exynos-drm] [ 47.016] (II) DriverName is [exynos] [ 47.016] (II) version is [1.0.0] [ 47.016] (II) ARMSOC(0): Chipset: Mali [ 47.016] (**) ARMSOC(0): Option "Debug" "true" [ 47.016] (II) ARMSOC(0): Buffer Flipping is Enabled [ 47.017] (II) ARMSOC(0): umplock is Enabled [ 47.017] (II) ARMSOC(0): Setting the video modes ... [ 47.017] (II) ARMSOC(0): drmmode_pre_init:1654: Entering [ 47.017] (II) ARMSOC(0): drmmode_pre_init:1671 Got KMS resources [ 47.017] (II) ARMSOC(0): drmmode_pre_init:1674 4 connectors, 3 encoders [ 47.017] (II) ARMSOC(0): drmmode_pre_init:1677 3 crtcs, 0 fbs [ 47.017] (II) ARMSOC(0): drmmode_pre_init:1680 0x0 minimum resolution [ 47.017] (II) ARMSOC(0): drmmode_pre_init:1683 4096x4096 maximum resolution [ 47.017] (II) ARMSOC(0): drmmode_crtc_init:882: Entering [ 47.017] (II) ARMSOC(0): Got CRTC: 0 (id: 36) [ 47.017] (II) ARMSOC(0): drmmode_crtc_init:897: Exiting [ 47.017] (II) ARMSOC(0): drmmode_output_init:1337: Entering [ 47.036] (II) ARMSOC(0): Output eDP-1 has no monitor section [ 47.036] (II) ARMSOC(0): drmmode_output_init:1404: Exiting [ 47.050] (II) ARMSOC(0): drmmode_output_get_modes:980 count_modes: 0 [ 47.051] (II) ARMSOC(0): Not using default mode "640x350" (vrefresh out of range) [ 47.051] (II) ARMSOC(0): Not using default mode "320x175" (doublescan mode not supported) [ 47.051] (II) ARMSOC(0): Not using default mode "640x400" (vrefresh out of range) [ 47.051] (II) ARMSOC(0): Not using default mode "320x200" (doublescan mode not supported) [ 47.051] (II) ARMSOC(0): Not using default mode "720x400" (vrefresh out of range) [ 47.051] (II) ARMSOC(0): Not using default mode "360x200" (doublescan mode not supported) [ 47.051] (II) ARMSOC(0): Not using default mode "640x480" (unknown reason) [ 47.051] (II) ARMSOC(0): Not using default mode "320x240" (doublescan mode not supported) [ 47.051] (II) ARMSOC(0): Not using default mode "640x480" (vrefresh out of range) [ 47.051] (II) ARMSOC(0): Not using default mode "320x240" (doublescan mode not supported) [ 47.051] (II) ARMSOC(0): Not using default mode "640x480" (vrefresh out of range) [ 47.051] (II) ARMSOC(0): Not using default mode "320x240" (doublescan mode not supported) [ 47.051] (II) ARMSOC(0): Not using default mode "640x480" (vrefresh out of range) [ 47.051] (II) ARMSOC(0): Not using default mode "320x240" (doublescan mode not supported) [ 47.051] (II) ARMSOC(0): Not using default mode "800x600" (vrefresh out of range) [ 47.051] (II) ARMSOC(0): Not using default mode "400x300" (doublescan mode not supported) [ 47.051] (II) ARMSOC(0): Not using default mode "800x600" (unknown reason) [ 47.051] (II) ARMSOC(0): Not using default mode "400x300" (doublescan mode not supported) [ 47.051] (II) ARMSOC(0): Not using default mode "800x600" (vrefresh out of range) [ 47.051] (II) ARMSOC(0): Not using default mode "400x300" (doublescan mode not supported) [ 47.051] (II) ARMSOC(0): Not using default mode "800x600" (vrefresh out of range) [ 47.051] (II) ARMSOC(0): Not using default mode "400x300" (doublescan mode not supported) [ 47.051] (II) ARMSOC(0): Not using default mode "800x600" (vrefresh out of range) [ 47.051] (II) ARMSOC(0): Not using default mode "400x300" (doublescan mode not supported) [ 47.051] (II) ARMSOC(0): Not using default mode "1024x768i" (vrefresh out of range) [ 47.051] (II) ARMSOC(0): Not using default mode "512x384i" (doublescan mode not supported) [ 47.051] (II) ARMSOC(0): Not using default mode "1024x768" (unknown reason) [ 47.051] (II) ARMSOC(0): Not using default mode "512x384" (doublescan mode not supported) [ 47.051] (II) ARMSOC(0): Not using default mode "1024x768" (vrefresh out of range) [ 47.052] (II) ARMSOC(0): Not using default mode "512x384" (doublescan mode not supported) [ 47.052] (II) ARMSOC(0): Not using default mode "1024x768" (vrefresh out of range) [ 47.052] (II) ARMSOC(0): Not using default mode "512x384" (doublescan mode not supported) [ 47.052] (II) ARMSOC(0): Not using default mode "1024x768" (vrefresh out of range) [ 47.052] (II) ARMSOC(0): Not using default mode "512x384" (doublescan mode not supported) [ 47.052] (II) ARMSOC(0): Not using default mode "1152x864" (vrefresh out of range) [ 47.052] (II) ARMSOC(0): Not using default mode "576x432" (doublescan mode not supported) [ 47.052] (II) ARMSOC(0): Not using default mode "1280x960" (hsync out of range) [ 47.052] (II) ARMSOC(0): Not using default mode "640x480" (doublescan mode not supported) [ 47.052] (II) ARMSOC(0): Not using default mode "1280x960" (vrefresh out of range) [ 47.052] (II) ARMSOC(0): Not using default mode "640x480" (doublescan mode not supported) [ 47.052] (II) ARMSOC(0): Not using default mode "1280x1024" (hsync out of range) [ 47.052] (II) ARMSOC(0): Not using default mode "640x512" (doublescan mode not supported) [ 47.052] (II) ARMSOC(0): Not using default mode "1280x1024" (vrefresh out of range) [ 47.052] (II) ARMSOC(0): Not using default mode "640x512" (doublescan mode not supported) [ 47.052] (II) ARMSOC(0): Not using default mode "1280x1024" (vrefresh out of range) [ 47.052] (II) ARMSOC(0): Not using default mode "640x512" (doublescan mode not supported) [ 47.052] (II) ARMSOC(0): Not using default mode "1600x1200" (hsync out of range) [ 47.052] (II) ARMSOC(0): Not using default mode "800x600" (doublescan mode not supported) [ 47.052] (II) ARMSOC(0): Not using default mode "1600x1200" (vrefresh out of range) [ 47.052] (II) ARMSOC(0): Not using default mode "800x600" (doublescan mode not supported) [ 47.052] (II) ARMSOC(0): Not using default mode "1600x1200" (vrefresh out of range) [ 47.052] (II) ARMSOC(0): Not using default mode "800x600" (doublescan mode not supported) [ 47.052] (II) ARMSOC(0): Not using default mode "1600x1200" (vrefresh out of range) [ 47.052] (II) ARMSOC(0): Not using default mode "800x600" (doublescan mode not supported) [ 47.052] (II) ARMSOC(0): Not using default mode "1600x1200" (vrefresh out of range) [ 47.052] (II) ARMSOC(0): Not using default mode "800x600" (doublescan mode not supported) [ 47.052] (II) ARMSOC(0): Not using default mode "1792x1344" (hsync out of range) [ 47.052] (II) ARMSOC(0): Not using default mode "896x672" (doublescan mode not supported) [ 47.052] (II) ARMSOC(0): Not using default mode "1792x1344" (vrefresh out of range) [ 47.052] (II) ARMSOC(0): Not using default mode "896x672" (doublescan mode not supported) [ 47.052] (II) ARMSOC(0): Not using default mode "1856x1392" (hsync out of range) [ 47.052] (II) ARMSOC(0): Not using default mode "928x696" (doublescan mode not supported) [ 47.052] (II) ARMSOC(0): Not using default mode "1856x1392" (vrefresh out of range) [ 47.052] (II) ARMSOC(0): Not using default mode "928x696" (doublescan mode not supported) [ 47.053] (II) ARMSOC(0): Not using default mode "1920x1440" (hsync out of range) [ 47.053] (II) ARMSOC(0): Not using default mode "960x720" (doublescan mode not supported) [ 47.053] (II) ARMSOC(0): Not using default mode "1920x1440" (vrefresh out of range) [ 47.053] (II) ARMSOC(0): Not using default mode "960x720" (doublescan mode not supported) [ 47.053] (II) ARMSOC(0): Not using default mode "832x624" (vrefresh out of range) [ 47.053] (II) ARMSOC(0): Not using default mode "416x312" (doublescan mode not supported) [ 47.053] (II) ARMSOC(0): Not using default mode "1400x1050" (hsync out of range) [ 47.053] (II) ARMSOC(0): Not using default mode "700x525" (doublescan mode not supported) [ 47.053] (II) ARMSOC(0): Not using default mode "1400x1050" (vrefresh out of range) [ 47.053] (II) ARMSOC(0): Not using default mode "700x525" (doublescan mode not supported) [ 47.053] (II) ARMSOC(0): Not using default mode "1920x1440" (vrefresh out of range) [ 47.053] (II) ARMSOC(0): Not using default mode "960x720" (doublescan mode not supported) [ 47.053] (II) ARMSOC(0): Not using default mode "2048x1536" (hsync out of range) [ 47.053] (II) ARMSOC(0): Not using default mode "1024x768" (doublescan mode not supported) [ 47.053] (II) ARMSOC(0): Not using default mode "2048x1536" (vrefresh out of range) [ 47.053] (II) ARMSOC(0): Not using default mode "1024x768" (doublescan mode not supported) [ 47.053] (II) ARMSOC(0): Not using default mode "2048x1536" (vrefresh out of range) [ 47.053] (II) ARMSOC(0): Not using default mode "1024x768" (doublescan mode not supported) [ 47.053] (II) ARMSOC(0): No remaining probed modes for output eDP-1 [ 47.053] (II) ARMSOC(0): Output eDP-1 connected [ 47.053] (WW) ARMSOC(0): Unable to find initial modes [ 47.053] (EE) ARMSOC(0): Output eDP-1 enabled but has no modes [ 47.053] (II) ARMSOC(0): drmmode_pre_init:1715: Exiting [ 47.053] (II) ARMSOC(0): Got KMS resources [ 47.069] (==) ARMSOC(0): DPI set to (96, 96) [ 47.069] (II) Loading sub module "dri2" [ 47.069] (II) LoadModule: "dri2" [ 47.069] (II) Module "dri2" already built-in [ 47.069] (II) Loading sub module "exa" [ 47.069] (II) LoadModule: "exa" [ 47.069] (II) Loading /usr/lib/xorg/modules/libexa.so [ 47.076] (II) Module exa: vendor="X.Org Foundation" [ 47.076] compiled for 1.19.5, module version = 2.6.0 [ 47.076] ABI class: X.Org Video Driver, version 23.0 [ 47.076] (II) Loading sub module "fb" [ 47.076] (II) LoadModule: "fb" [ 47.077] (II) Loading /usr/lib/xorg/modules/libfb.so [ 47.086] (II) Module fb: vendor="X.Org Foundation" [ 47.086] compiled for 1.19.5, module version = 1.0.0 [ 47.086] ABI class: X.Org ANSI C Emulation, version 0.4 [ 47.086] (II) ARMSOC(0): ARMSOCPreInit:940: Exiting [ 47.086] (EE) [ 47.086] (EE) Backtrace: [ 47.086] (EE) 0: /usr/bin/X (xorg_backtrace+0x54) [0x699dec] [ 47.086] (EE) 1: /usr/bin/X (0x4e2000+0x1bc440) [0x69e440] [ 47.087] (EE) 2: /lib/libc.so.6 (__default_rt_sa_restorer+0x0) [0xb68d6480] [ 47.087] (EE) 3: /usr/bin/X (xf86InitViewport+0xb8) [0x561ba0] [ 47.087] (EE) 4: /usr/bin/X (InitOutput+0xddc) [0x56c1cc] [ 47.087] (EE) 5: /usr/bin/X (0x4e2000+0x42fac) [0x524fac] [ 47.087] (EE) 6: /lib/libc.so.6 (__libc_start_main+0x120) [0xb68bdb68] [ 47.087] (EE) [ 47.087] (EE) Segmentation fault at address 0x18 [ 47.087] (EE) Fatal server error: [ 47.087] (EE) Caught signal 11 (Segmentation fault). Server aborting [ 47.087] (EE) [ 47.087] (EE) Please consult the The X.Org Foundation support at http://wiki.x.org for help. [ 47.088] (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information. [ 47.088] (EE) [ 47.105] (EE) Server terminated with error (1). Closing log file. ******************************************************************************** Guillaume -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

2 3

[opensuse-arm] [aarch64] Tumbleweed repositories is outdated
by Manu Maier 14 Nov '17

14 Nov '17

The last images are from the 17-Jun-2017 http://download.opensuse.org/ports/aarch64/tumbleweed/images/?C=M;O=D and the latest packages from 21-Sep-2017 http://download.opensuse.org/ports/aarch64/tumbleweed/repo/oss/suse/aarch64… The repositories should be updated. Greetings, Manu N��r��y隊Z)z{.�櫛맲��r��z�^�ˬz��N�(�֜��^� ޭ隊Z)z{.�櫛�0��Ǩ�

6 5

[opensuse-arm] JeOS-2017-03-13 image for RPi 1 installs OK, Grub fails on reboot
by Alex Armstrong 14 Nov '17

14 Nov '17

-----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 9

[opensuse-arm] aaa_base for Tumbleweed on RPi3 (aarch64) lacks a number of entries for /etc/passwd, /etc/group and /etc/shadow
by Freek de Kruijf 27 Oct '17

27 Oct '17

I tried to use postfix in Tumbleweed on a Raspberry Pi 3B system with aarch64. I got an error message that account nobody is missing. I inspected some files delivered by aaa_base to set-up /etc/passwd, /etc/group, and /etc/shadow and found only root mentioned in the template for /etc/passwd. In Leap 42.3 for the same system these templates contain a lot more entries. Bug report: https://bugzilla.opensuse.org/show_bug.cgi?id=1065411 -- fr.gr. member openSUSE Freek de Kruijf -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

2 2

[opensuse-arm] Enable SPI
by Alexander Bergmann 25 Oct '17

25 Oct '17

Hi everyone, I'm not sure how to enable SPI in openSUSE Leap 43.3. I've changed the config.txt file and added "dtparam=spi=on", this has however no affect on the hardware. The same steps are working in Raspbian. #> cat /proc/device-tree/soc/spi@7e204000/status disabled Any ideas? Ciao, Alex~ -- Alexander Bergmann <abergmann(a)suse.com>, Security Engineer, GPG:9FFA4886 SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton HRB 21284 (AG Nürnberg)

3 4

[opensuse-arm] EspressoBin
by Matwey V. Kornilov 21 Oct '17

21 Oct '17

Hi, I've just received EspressoBin 1G. Any success stories how to run openSUSE? -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

2 7

[opensuse-arm] TW AArch64 images not published?
by Guillaume Gardet 17 Oct '17

17 Oct '17

Hi, Images from http://download.opensuse.org/ports/aarch64/tumbleweed/ are quite old: 17th of June 2017. I guess images publishing has problems? ISO files seem to be OK. Guillaume -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

1 0

[opensuse-arm] ARM64 installation DVD link on web page
by Loic Devulder 16 Oct '17

16 Oct '17

Hi! Small question: on this web page https://software.opensuse.org/distributions/tumbleweed we can find a link to download TW Ports, like the page we can found for Leap. But on the TW Ports there is no ARM64 link as for Leap: https://software.opensuse.org/distributions/tumbleweed/ports. Is a link to the installation DVD could be added like Leap or the other architectures? -- Loic Devulder - Senior QA Engineer email: ldevulder(a)suse.de Container & Storage Solutions Quality Assurance team (qa-css) SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg GF: F. Imendörffer, J. Smithard, J. Guild, D. Upmanyu, G. 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 5

[opensuse-arm] EFI boot device-tree
by Frank Kunz 15 Oct '17

15 Oct '17

Hi, I'm doing some test with EFI boot on an olinuxino board here: https:// build.opensuse.org/package/show/home:frank_kunz:branches:openSUSE:Factory:A… JeOS-olinuxinolime The image works and the kernel has a device-tree visible under /proc/device- tree. With non EFI configurations the device-tree is loaded by uboot from the boot partition dtb directory and is then passed to the kernel by boot command. For EFI there is no dtb directory. Also I haven't found a *.dtb file on the filesystem anywhere. How does the kernel get the device-tree in EFI boot mode? The background is that some hardware specific configurations need to be done per use case in the device-tree. E.g. adding a battery or a touch screen. Without the device-tree settings the kernel will not probe the devices. Enabling that on u-boot boot mode can be done by either modifying the device-tree file or create overlays and load them by u-boot script with "fdt apply" command. How can this be configured in EFI mode? Br, Frank -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

3 5

[opensuse-arm] Nue OpenSUSE Build Service power outage / ARM
by Dirk Müller 13 Oct '17

13 Oct '17

Hi all, due to a large area power cut planned for this Saturday (tomorrow) affecting the building the SUSE and openSUSE server rooms are hosted we're going to shut down the OBS ARM architecture workers later today in a controlled fashion in order to not have them a hard power loss when this happens. As the servers are in a restricted environment it will probably take a few days to get everything back online. I'll start working on that on Monday during european office hours. Greetings, Dirk -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

2 1

[opensuse-arm] Cargo bootstrap
by Dirk Müller 12 Oct '17

12 Oct '17

Hi, is anyone working already on the rust/cargo bootstrap for armv6/v7/aarch64 ? I don't want to waste/duplicate work. TIA, Dirk -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

2 1

[opensuse-arm] KVM on RPi3
by Loic Devulder 11 Oct '17

11 Oct '17

Hi guys! I would like to test virtual machines on my rpi3 (just for fun of course! with the limited memory...). I tried with a Leap 42.3 but I ran into some issue, mainly missing packages or not installed with the kvm_server pattern. So I had to add the "Virtualization" repo from OBS. But even with it, I get the following error when I try to create a VM: Initialization of device arm_gic failed: KVM with user space irqchip only works when the host kernel supports KVM_CAP_ARM_USER_IRQ I was able to execute a VM (YES!) after installing a 4.13 kernel from "Kernel Untested" repo. So, "simple" question: is it plan to add KVM_CAP_ARM_USER_IRQ in the official Leap 42.3 kernel? Or is it better to use Tumbleweed for KVM testing on rpi3? -- Loic -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

3 5

[opensuse-arm] RPi3 camera module
by Alexander Bergmann 08 Oct '17

08 Oct '17

Hi, did anyone get the Raspberry Pi camera module working on a RPi3 with openSUSE Leap etc.? I couldn't find a package providing me raspistill. And the raspi-config script would add the line 'start_x=1' to '/boot/efi/config.txt' to enable the camera. This however will somehow break my setup and the system is not booting anymore. Any help would be appreciated. ;) Ciao, Alex~ -- Alexander Bergmann <abergmann(a)suse.com>, Security Engineer, GPG:9FFA4886 SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton HRB 21284 (AG Nürnberg)

2 1

[opensuse-arm] RPi3 poor WiFi performance
by Alexander Bergmann 07 Oct '17

07 Oct '17

Hi everyone, I've just installed Leap 42.3 on my RPi3 last night and had some bad WiFi performance. The SSH connection was nearly unusable. 21/21 packets, 0% loss, min/avg/ewma/max = 409.441/1454.630/1399.198/3025.166 ms At the end simply switching off the power_save option did the trick to have a working connection again. Details got discussed here [1]. #> iw dev wlan0 set power_save off The question is now, if we could disable power saving by default. There is already a patch [2] from the raspberrypi.org guys that is exactly doing that. Ciao, Alex~ [1] https://www.raspberrypi.org/forums/viewtopic.php?f=28&t=138312#p919552 [2] https://github.com/lede-project/source/blob/master/package/kernel/mac80211/… -- Alexander Bergmann <abergmann(a)suse.com>, Security Engineer, GPG:9FFA4886 SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton HRB 21284 (AG Nürnberg)

3 2

[opensuse-arm] Upgrade of RPi3 to latest Tumbleweed shows a number of errors
by Freek de Kruijf 04 Oct '17

04 Oct '17

I used the image: openSUSE-Tumbleweed-ARM-JeOS-raspberrypi3.aarch64-2017.09.09-Build3.11.raw.xz to initialize the SD card. After that, with some fiddling, I upgraded the system to Tumbleweed 20170920, including the kernel to 4.13.2-1. After the reboot I see the following error messages: sep 14 18:32:58 rpi3tum kernel: kvm [1]: Invalid trigger for IRQ4, assuming level low sep 14 18:32:58 rpi3tum kernel: OF: /soc/usb@7e980000: could not get #phy- cells for /phy and quite a lot of messages like: okt 03 23:42:29 rpi3tum kernel: bcm2835-dma 3f007000.dma: swiotlb buffer is full (sz: 221172 bytes) okt 03 23:42:29 rpi3tum kernel: bcm2835-dma 3f007000.dma: DMA: Out of SW-IOMMU space for 221172 bytes okt 03 23:42:29 rpi3tum kernel: mmcblk0: error -22 transferring data, sector 3465216, nr 1024, cmd response 0x900, card status 0xb00 okt 03 23:42:29 rpi3tum kernel: bcm2835-dma 3f007000.dma: swiotlb buffer is full (sz: 221172 bytes) -- fr.gr. member openSUSE Freek de Kruijf -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

2 6

[opensuse-arm] Raspberry Pi1 is not booting
by Manu Maier 02 Oct '17

02 Oct '17

Hello, i test the factory image[1] of the Raspberry Pi 1 and is not booting. At Grub it makes a restart. U-Boot 2017.09 (Sep 13 2017 - 15:14:30 +0000) DRAM: 416 MiB RPI Model B+ (0x10) 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... 4 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... 22299 bytes read in 121 ms (179.7 KiB/s) Found EFI removable media binary efi/boot/bootarm.efi reading efi/boot/bootarm.efi 475136 bytes read in 54 ms (8.4 MiB/s) ## Starting EFI application at 01000000 ... Scanning disk sdhci(a)7e300000.blk... Found 1 disks Welcome to GRUB! data abort pc : [<18ad3570>] lr : [<19f909b8>] reloc pc : [<feb7a570>] lr : [<000379b8>] sp : 19b5bf80 ip : 00000010 fp : 19f63aa8 r10: 00000007 r9 : 00000000 r8 : 19b5bffc r7 : 18ad3070 r6 : 18ad4000 r5 : 00000001 r4 : 00000000 r3 : 00000008 r2 : 00000010 r1 : 00000000 r0 : 00000000 Flags: nZCv IRQs off FIQs off Mode SVC_32 Resetting CPU ... resetting ... RPi2 and RPi3 boot without problems. Greetings, Manu [1] http://download.opensuse.org/ports/armv7hl/factory/images/openSUSE-Tumblewe…

2 7

[opensuse-arm] https://kernelci.org/
by Loic Devulder 22 Sep '17

22 Sep '17

Hi! For those who don't know, interesting QA site for Linux kernel: https://kernelci.org/ Lot of ARM boards are used! :) Loic -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

1 0

[opensuse-arm] vcgencmd for openSUSE
by Roger Oberholtzer 22 Sep '17

22 Sep '17

Is there an equivalent command to vcgencmd on openSUSE for the Raspberry Pi 3 (64-bit)? http://www.elinux.org/RPI_vcgencmd_usage I see some discussion at https://github.com/Hexxeh/rpi-update/issues/220 -- Roger Oberholtzer -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

2 1

[opensuse-arm] Khadas VIM2 Max TV Box
by Loic Devulder 22 Sep '17

22 Sep '17

Hi all! Sounds a very interesting card: https://www.gearbest.com/tv-box/pp_676880.html?lkid=10642329 64GB of eMMC for this price is not too bad, as 3GB of RAM too (4GB could have been better :-p). According to the specs this card has UEFI boot, it would be good to try to install UEFI aarch64 version :-) Just need to see the status of S912 SoC in the mainline kernel (at least in the openSUSE kernel). Now I still don't know what to choose between Rock64 and this one... -- Loic -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

3 8

[opensuse-arm] Upgrade of openSUSE Tumbleweed on RPI1 fails
by Freek de Kruijf 18 Sep '17

18 Sep '17

I used the latest JeOS image 2017.05.23-Build1.1 for the RPi1 (armv6l) on a SD card and booted the system, which went OK. After that I did a "zypper dup --no-recommends" on that system which, at the end, shows the following message: Output of grub2-arm-uboot-2.02-6.1.armv6hl.rpm %posttrans script: update-bootloader: 2017-09-04 11:31:09 <3> update-bootloader-1244 run_command.274: '/usr/lib/bootloader/grub2-efi/install' failed with exit code 1, output: <<<<<<<<<<<<<<<< target = arm-efi ls: cannot access '/sys/firmware/efi/efivars': No such file or directory + /usr/sbin/grub2-install --target=arm-efi --no-nvram --removable Installing for arm-efi platform. /usr/sbin/grub2-install: error: cannot find a GRUB drive for /dev/ mmcblk0p2. Check your device.map. >>>>>>>>>>>>>>>> However /dev/mmcblk0p2 does exist as shows the following output of "df -h" # df -h Filesystem Size Used Avail Use% Mounted on devtmpfs 176M 8,0K 176M 1% /dev tmpfs 201M 0 201M 0% /dev/shm tmpfs 201M 372K 200M 1% /run /dev/mmcblk0p2 3,0G 1,2G 1,7G 41% / /dev/mmcblk0p1 200M 3,7M 197M 2% /boot/efi tmpfs 201M 0 201M 0% /sys/fs/cgroup tmpfs 41M 0 41M 0% /run/user/0 File a bug report? -- fr.gr. member openSUSE Freek de Kruijf -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

5 17

[opensuse-arm] Leap/Tumbleweed DVD installation Raspberry Pi 3
by Loic Devulder 15 Sep '17

15 Sep '17

Hi guys! For those who want to do a fresh DVD installation on their Raspberry Pi 3, I have updated the wiki page with the procedure I use to do this: https://en.opensuse.org/HCL:Raspberry_Pi3 I hope that there isn't lot of mistake in my howto :) Thanks to Alex for his help! Regards, Loic -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

1 0

[opensuse-arm] Re: U-Boot configs/packages renamed => need update in OBS
by Guillaume Gardet 14 Sep '17

14 Sep '17

Le 13/09/2017 à 22:30, Dirk Müller a écrit : > Hi Guillaume, > >> Could you update OBS accordingly, please? > If I understood correctly this was only for Base:System:Staging, which you can do yourself. done now anyway, good to know this once it gets submitted to Base:System (I can do it there then as well, but right now the version in there does not provide that yet). I forgot that I was able to do it for Staging. It is on the way to Base:System, see: https://build.opensuse.org/request/show/525904 Guillaume > > Greetings, > Dirk > > -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

1 0

[opensuse-arm] U-Boot configs/packages renamed => need update in OBS
by Guillaume Gardet 13 Sep '17

13 Sep '17

Hi Dirk, A merge and rename happened upstream: The following old configs: mvebu_db-88f7040-nand_defconfig mvebu_db-88f7040_defconfig mvebu_db-88f8040_defconfig are now merged to a single new config: mvebu_db_armada8k_defconfig Could you update OBS accordingly, please? Guillaume -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

1 0

[opensuse-arm] Raspberry Pi 3 upgrade Leap 42.2 -> 42.3
by Roger Oberholtzer 13 Sep '17

13 Sep '17

I have a functioning Leap 42.2 image for my Raspberry Pi 3. It is kept up-to-date. I know that 42.2 will probably be around for a while. But I am thinking of upgrading to 42.3. I would imagine one follows the usual course of updating the repos and doing a zypper dup? On a copy of the 42.2, of course. Any gottchas I might need to consider? Has anyone else done this? -- Roger Oberholtzer -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

2 1

[opensuse-arm] Strange armv7l JeOS image among armv6l E20, LXQT and XFCE images
by Freek de Kruijf 11 Sep '17

11 Sep '17

In the repository: http://download.opensuse.org/repositories/devel:/ARM:/Factory:/Contrib:/ RaspberryPi/images/ there are images dating back to March 2017 with architecture armv6l for E20, LXQT and XFCE. A strange image with architecture armv7l is there for JeOS with a very recent date 04-Sep-2017. These are images with the upstream kernel. -- fr.gr. member openSUSE Freek de Kruijf -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

1 0

[opensuse-arm] Leap/Tumbleweed installation on RPi3
by Loic Devulder 07 Sep '17

07 Sep '17

Hi guys! Quick question before wasting my time by trying it: is it possible to install Leap/Tumbleweed on a RPi3 using the ISO directly (like a "normal" PC)? By ISO I mean with PXE or USB key (as RPi3 can boot on USB). Using the image is good but I would like to try a custom installation. -- Loic Devulder - Senior QA Engineer email: ldevulder(a)suse.de Cloud & Storage Solutions Quality Assurance team (qa-css) SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg GF: F. Imendörffer, J. Smithard, J. Guild, D. Upmanyu, G. 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

2 2

[opensuse-arm] Tumbleweed AArch64 not publishing anymore?
by Guillaume Gardet 06 Sep '17

06 Sep '17

Hi, it seems that AARch64 Tumbleweed is no more updated on download.opensuse.org server. AArch64 images are from June whereas newer images are available on OBS. Update repo is from 4th of august. kernel is 4.11.8 whereas 4.12.8 is ready in OBS. Is there a never ending build problem which prevent publishing or maybe just a publish problem? Guillaume -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

3 4

[opensuse-arm] network issues in ARM build worker network (build.opensuse.org)
by Dirk Müller 06 Sep '17

06 Sep '17

Hi, not sure for how long, but there were network issues due to a misconfiguration on the admin server in the ARM build network that caused almost all jobs to fail with things like "connect to opensuse-src:5252 timed out" and similar issues. I only stumbled over it because I was watching a few jobs. This has been fixed now, if you're affected, feel free to rebuild (it doesn't seem to automatically rebuild). Greetings, Dirk -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

2 1

[opensuse-arm] Overlay images for Raspberry Pi 3
by Roger Oberholtzer 06 Sep '17

06 Sep '17

I am considering using the Raspberry Pi 3 in a project. My testing to date has been with Leap 42.2. It has really worked well. I have a couple of questions: 1. I would like to run openSUSE in such a way that the OS image is read-only. All files that change are in RAM. I have built openSUSE images like this (for standard PCs) using KIWI. Live openSUSE images are also built this way. Has anyone done this for the PI 3? I know that the boot starts out a bit different. Could that be a problem here? 2. If there is no technical reason against this (from the Pi 3 POV), I would imagine my next step would be to copy the appropriate items in OBS into my OBS project, and attempt changes there. Or is there a better approach? What would be the projects to copy? I would prefer to copy as little as possible so that I do not branch off somewhere. I still want to run the released versions of things - except for the kiwi change to get the overlay file system stuff set up. 3. Is it possible to boot the PI 3 via PXE? My motivation would be that the OS image need not be on the SD card. I have looked at resources like https://www.raspberrypi.org/documentation/hardware/raspberrypi/bootmodes/ne…. So I would think this should work - if I can make the previous items work. -- Roger Oberholtzer -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

2 1

[opensuse-arm] WiFi on RPi3 with kernel 4.12
by Freek de Kruijf 04 Sep '17

04 Sep '17

Today I am pleasantly surprised to see the installation of the 4.12 kernel on my RPi3 with Tumbleweed. Talk has been on this mailing list that this version would bring us support for WiFi. However I don't see any other network device other than lo and eth0. How do I get a wlan0 device? -- fr.gr. member openSUSE Freek de Kruijf -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

2 1

[opensuse-arm] Kernel configs for new boards
by Rick Ashford 31 Aug '17

31 Aug '17

What is the preferred method for submitting changes to the default kernel configs and device trees to add support for new boards? Pull requests on GitHub? Patch requests in OBS? Something else? I am in the process of trying to get the EspressoBin board enabled for Tumbleweed. I have it working with my own 4.12 build, but I'd like to make it so the Tumbleweed kernel supports it out of the box. -- Rick Ashford Sales Engineering Manager - West rick.ashford(a)suse.com M:(512)731-3035

2 1

[opensuse-arm] Raspberry Pi 3 Ad-Hoc WiFi
by Roger Oberholtzer 29 Aug '17

29 Aug '17

I am trying to set the wlan0 interface on a Raspberry Pi 3 to be Ad-Hoc instead of Managed. I am using commands that I have used on openSUSE that work. But I cannot get it to work on the Pi 3. The network is managed by wicked. The commands are: ip link set wlan0 down iwconfig wlan0 essid myId mode Ad-Hoc ip link set wlan0 up ip addr add 10.1.1.10 dev wlan0 route add default gw 10.1.1.10 It is the iwconfig command that fails: # iwconfig wlan0 essid myId mode Ad-Hoc Error for wireless request "Set Mode" (8B06) : SET failed on device wlan0 ; Device or resource busy. And I do not know why. How can it be busy? ip addr reports: 3: wlan0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast state DOWN group default qlen 1000 link/ether b8:27:eb:9a:00:74 brd ff:ff:ff:ff:ff:ff I have also tried this in YaST. There is no error reported, but the device is unchanged. The settings are remembered by YaST. But the device is unchanged. There are some errors in the log: [91050.345081] brcmfmac: brcmf_cfg80211_change_iface: iface validation failed: err=-16 [91090.214264] brcmfmac: brcmf_cfg80211_change_iface: iface validation failed: err=-16 [92274.237410] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready [92274.353955] brcmfmac: brcmf_cfg80211_escan: Connecting: status (3) [92274.353974] brcmfmac: brcmf_cfg80211_scan: scan error (-11) [92322.032508] brcmfmac: brcmf_cfg80211_change_iface: iface validation failed: err=-16 [92350.696929] brcmfmac: brcmf_sdio_readframes: RXHEADER FAILED: -110 [92350.696948] brcmfmac: brcmf_sdio_rxfail: abort command, terminate frame, send NAK [92376.662941] brcmfmac: brcmf_cfg80211_change_iface: iface validation failed: err=-16 I found similar instructions at https://www.raspberrypi.org/forums/viewtopic.php?f=36&t=18771 and it seemed to work for that user. It was with Raspbian. I am not sure what to make of the error. -- Roger Oberholtzer -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

2 2

[opensuse-arm] Wireless interface on Raspberry Pi 3
by Roger Oberholtzer 29 Aug '17

29 Aug '17

My wireless device does not show up on my Raspberry Pi 3, running an up-to-date Leap 42.2 I have seen a number of places suggest editing /etc/dracut.conf.d/raspberrypi_modules.conf and removing sdhci-iproc so that the file becomes: add_drivers+=" bcm2835-sdhost bcm2835_dma mmc_block " # Workaround for Wifi # omit_drivers+=" sdhci-iproc" Then run mkinitrd -f Two questions;: 1. Is this the appropriate edit? 2. Does one run mkinitrd and not dracut on the Raspberry? I really do not want to mess up the initrd file! -- Roger Oberholtzer -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

5 9

[opensuse-arm] eSATA support broken in Leap 42.3
by Alessio Adamo 28 Aug '17

28 Aug '17

Hi guys, After a Tumbleweed upgrade broke my Cubox-i Pro, since Leap was going to be released soon, I decided to switch to Leap. By the way, I'm interested in your thoughts about Leap ARM stability compared to Tumbleweed. Anyway, going back on topic... I banged my head against the wall for two days trying to boot from eSATA but the partitions wouldn't mount. I thought there was something wrong with boot.scr configuration or maybe with the rootfs. Finally, I decided to try Tumbleweed and it worked like a charm. Any ideas what could be wrong with Leap? Thanks Alessio -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

2 1

[opensuse-arm] DSI output on raspberry Pi 1, 2 or 3 ?
by Guillaume Gardet 24 Aug '17

24 Aug '17

Hi, does someone tested the DSI output on RPi 1, 2 or 3 with Tumbleweed ? I may buy the 7" touchscreen for the RPi, but I would be sure it will work with Tumbleweed before. ;) Guillaume -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

2 2

[opensuse-arm] Yundoo Y8 rk3399 Settop Box
by Loic Devulder 21 Aug '17

21 Aug '17

Hi all! Interesting article to follow: https://lurchi.wordpress.com/2017/08/16/yundoo-y8-rk3399-settop-box-part-1/ It seems to have pins for serial access, good :-) -- Loic Devulder - Senior QA Engineer email: ldevulder(a)suse.de Cloud & Storage Solutions Quality Assurance team (qa-css) SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg GF: F. Imendörffer, J. Smithard, J. Guild, D. Upmanyu, G. 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

1 1

[opensuse-arm] aarch64 installer?
by Peter Czanik 10 Aug '17

10 Aug '17

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 3

[opensuse-arm] ARM-EFI: Where is the device-tree?
by Frank Kunz 09 Aug '17

09 Aug '17

Hello, I'm trying to get the USB-OTG interface working on the DE0-nano-SoC (socfpga) board by using openSUSE tumbleweed. The image uses ARM-EFI boot and there is no dtb file on the boot partition. When Linux is running the device-tree is visible on /proc/device-tree and /sys/firmware, so there is a device-tree. But there is no dtb file which I can change for debug purpose. So how to modify the device-tree with ARM-EFI boot? Br, Frank -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

3 3

[opensuse-arm] aarch64 installer?
by Peter Czanik 28 Jul '17

28 Jul '17

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

1 0

[opensuse-arm] Build a downstream kernel in OBS
by Oscar C 27 Jul '17

27 Jul '17

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 3

[opensuse-arm] Raspberry Pi Zero boot broken after update
by Andreas Färber 23 Jul '17

23 Jul '17

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

2 1

[opensuse-arm] Orange Pi Prime
by Vladimir Nadvornik 20 Jul '17

20 Jul '17

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

2 2