- openSUSE ARM

[opensuse-arm] Raspi LXQT Image_: Falkon crashes
by Axel Braun 30 Oct '18

30 Oct '18

Hi, I installed a new image with LXQT desktop today, together with falkon as browser. When calling it, it crashes. From the command line: linux:~ # falkon libEGL warning: DRI2: failed to authenticate [1030/140331.137334:WARNING:stack_trace_posix.cc(648)] Failed to open file: / root/#26439 (deleted) Error: No such file or directory [1867:1896:1030/140331.881644:ERROR:gl_implementation.cc(246)] Failed to load /usr/bin/libGLESv2.so: /usr/bin/libGLESv2.so: cannot open shared object file: No such file or directory Falkon: 1 extensions loaded [1867:1896:1030/140342.503582:ERROR:gl_surface_qt.cpp(701)] Requested OpenGL implementation is not supported. Implementation: 0 *** stack smashing detected ***: <unknown> terminated Received signal 6 #0 0xffff84bf0a80 <unknown> #1 0xffff83984714 <unknown> #2 0xffff84bf0e64 <unknown> #3 0xffff8a7586c0 ([vdso]+0x6bf) #4 0xffff894ff5e8 __GI_raise #5 0xffff89500c0c __GI_abort #6 0xffff8953ac48 __libc_message #7 0xffff895b12a8 __GI___fortify_fail_abort #8 0xffff895b1260 __stack_chk_fail_local #9 0xffff839dc84c <unknown> #10 0xffff8556d344 <unknown> #11 0xffff85579bb8 <unknown> #12 0xffff8557c404 <unknown> #13 0xffff8557d444 <unknown> #14 0xffff85576fe8 <unknown> #15 0xffff85577820 <unknown> #16 0xffff85576930 <unknown> #17 0xffff85578e24 <unknown> #18 0xffff84c73d40 <unknown> #19 0xffff84c0d140 <unknown> #20 0xffff84c0df98 <unknown> #21 0xffff84c0e37c <unknown> #22 0xffff84c0f394 <unknown> #23 0xffff84c2d4c0 <unknown> #24 0xffff84c49068 <unknown> #25 0xffff84c4452c <unknown> #26 0xffff827f8058 start_thread #27 0xffff8959fe2c thread_start [end of stack trace] Calling _exit(1). Core file will not be generated. linux:~ # I installed Mesa-libGLESv2-2, but that did not fix it. Any ideas? Bugreport? Thanks Axel -- 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] Raspi Update of Leap 15: DNS broken
by Axel Braun 30 Oct '18

30 Oct '18

Hi, I Installed a new image with LXQT desktop today, and ran an update afterwards. After the reboot the DNS did not work anymore. TCP/IP itself was working. Wicked was set by default. After changing the network to Networkmanager and another reboot it worked again. Is wicked broken? Cheers Axel -- 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] Try to use Leap15 cubietruck image
by Karsten Keil 19 Oct '18

19 Oct '18

Hi, I tried to update my 42.3 cubietruck to leap 15, but it seems the current image does not work, it's end up on on "[ OK ] Reached target Remote File Systems.". I tried this several times with different SD cards - always the same (sha256 on the image is OK). The tumbleweed image boots fine, it stops for a while on the same stage on the first boot, but has an additional line on the serial console: ... "[ OK ] Reached target Remote File Systems." Starting dracut pre-mount hook..." then it continues with expanding the disk. Here the full serial output from the leap15 boot: U-Boot SPL 2018.03 (Apr 12 2018 - 15:19:29 +0000) DRAM: 2048 MiB CPU: 912000000Hz, AXI/AHB/APB: 3/2/2 Trying to boot from MMC1 U-Boot 2018.03 (Apr 12 2018 - 15:19:29 +0000) Allwinner Technology CPU: Allwinner A20 (SUN7I) Model: Cubietech Cubietruck I2C: ready DRAM: 2 GiB MMC: SUNXI SD/MMC: 0 Loading Environment from FAT... *** Warning - bad CRC, using default environment Failed (-5) Loading Environment from MMC... *** Warning - bad CRC, using default environment Failed (-5) Setting up a 1024x768 vga console (overscan 0x0) In: serial Out: vga Err: vga Allwinner mUSB OTG (Peripheral) SCSI: Target spinup took 0 ms. AHCI 0001.0100 32 slots 1 ports 3 Gbps 0x1 impl SATA mode flags: ncq stag pm led clo only pmp pio slum part ccc apst Net: eth0: ethernet@01c50000 Warning: usb_ether using MAC address from ROM , eth1: usb_ether starting USB... USB0: USB EHCI 1.00 USB1: USB OHCI 1.0 USB2: USB EHCI 1.00 USB3: USB OHCI 1.0 scanning bus 0 for devices... 1 USB Device(s) found scanning bus 2 for devices... 1 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... Found U-Boot script /boot.scr 2576 bytes read in 21 ms (119.1 KiB/s) ## Executing script at 43100000 switch to partitions #0, OK mmc0 is current device 6956352 bytes read in 725 ms (9.1 MiB/s) 22721440 bytes read in 1520 ms (14.3 MiB/s) 52901 bytes read in 240 ms (214.8 KiB/s) ## Flattened Device Tree blob at 43000000 Booting using the fdt blob at 0x43000000 Using Device Tree in place at 43000000, end 4300fea4 Starting kernel ... Welcome to openSUSE Leap 15.0 dracut-044-lp150.13.3 (Initramfs)! [ OK ] Listening on udev Control Socket. [ OK ] Listening on Journal Socket (/dev/log). [ OK ] Reached target Local File Systems. [ OK ] Listening on Journal Socket. [ OK ] Reached target Swap. [ OK ] Created slice System Slice. Starting dracut cmdline hook... [ OK ] Reached target Slices. Starting Create list of required st�.|ce nodes for the current kernel... [ OK ] Reached target Timers. [ OK ] Listening on Journal Audit Socket. Starting Journal Service... [ OK ] Started Dispatch Password Requests to Console Directory Watch. [ OK ] Reached target Encrypted Volumes. [ OK ] Reached target Paths. [ OK ] Listening on udev Kernel Socket. [ OK ] Reached target Sockets. Starting Load Kernel Modules... [ OK ] Started Journal Service. [ OK ] Started Create list of required sta�.|vice nodes for the current kernel. Starting Create Static Device Nodes in /dev... [ OK ] Started Load Kernel Modules. Starting Apply Kernel Variables... [ OK ] Started Create Static Device Nodes in /dev. [ OK ] Started Apply Kernel Variables. [ OK ] Started dracut cmdline hook. Starting dracut pre-udev hook... [ OK ] Started dracut pre-udev hook. Starting udev Kernel Device Manager... [ OK ] Started udev Kernel Device Manager. Starting dracut pre-trigger hook... [ OK ] Started dracut pre-trigger hook. Starting udev Coldplug all Devices... Mounting Kernel Configuration File System... [ OK ] Started udev Coldplug all Devices. [ OK ] Mounted Kernel Configuration File System. [ OK ] Reached target System Initialization. [ OK ] Reached target Basic System. Starting dracut initqueue hook... [ OK ] Found device /dev/disk/by-uuid/fe3ad73f-0035-4969-9a3f-479234fd9162. [ OK ] Reached target Initrd Root Device. [ OK ] Started dracut initqueue hook. Starting dracut pre-mount hook... [ OK ] Reached target Remote File Systems (Pre). [ OK ] Reached target Remote File Systems. Any ideas what to do ? Best regards Karsten -- 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] next build of tumbleweed?
by Tomáš Čech 09 Oct '18

09 Oct '18

Hi, it seems that I have been hit by GnuTLS bug which is already fixed in Tumbleweed for x86_64 but not for armv7. Fixes I need are with changelog * Fri Sep 14 2018 Luis Henriques <lhenriques(a)suse.com> - Backport of upstream fixes (boo#1108450) * gnutls-3.6.3-backport-upstream-fixes.patch Fixes taken from upstream commits: * * 3df5b7bc8a64 ("cert-cred: fix possible segfault when resetting cert retrieval function") * * 42945a7aab6d ("allow no certificates to be reported by the gnutls_certificate_retrieve_function callbacks") * * 10f83e36ed92 ("hello_ext_parse: apply the test for pre-shared key ext being last on client hello") The patch was taken from https://github.com/weechat/weechat/issues/1231 I don't want to rebuild subtree of system which uses gnutls just for myself. Do you have idea when next snapshot could be available?

2 1

[opensuse-arm] How to debug Grub config
by Matwey V. Kornilov 04 Oct '18

04 Oct '18

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 02000000 ... Card did not respond to voltage select! mmc_init: -95, time 10 Scanning disk rksdmmc(a)ff520000.blk... Scanning disk rksdmmc(a)ff500000.blk... Found 2 disks Welcome to GRUB! ethernet@ff540000 Waiting for PHY auto negotiation to complete......... TIMEOUT ! Could not initialize PHY ethernet@ff540000 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? -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

5 10

[opensuse-arm] Support for Banana Pi M64
by Freek de Kruijf 22 Sep '18

22 Sep '18

I experienced problems with the 1GB memory of the Raspberry Pi 3, so I went to a Banana Pi M64, which has almost the same specifications as the RPi3, except it has 2 GB memory, and it uses a slightly different CPU. I even found an image to run openSUSE Tumbleweed on it from a year ago. The image used the same repository as the repository for the RPi3 (aarch64). However upgrading to a newer version of Tumbleweed failed. As far as I could see the only issue is a slightly different kernel and boot system. Currently I am trying to implement my services on it using Debian Stretch. I would very much like to use openSUSE on it, because I am more familiar with it. Debian is quite different, both in managing packages as in configuration of the services. If I can be of assistance in implementing openSUSE on a Banana Pi M64 I am quite willing to do that. Don't know if I have the necessary knowledge. -- 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 1

[opensuse-arm] Cubox-i Tumbleweed JeOS images broken
by Josua Mayer 15 Sep '18

15 Sep '18

Hi everybody, I just tried the two available JeOS images for cubox-i: openSUSE-Tumbleweed-ARM-JeOS-cuboxi.armv7l-2018.08.13-Snapshot20180905.raw.xz openSUSE-Tumbleweed-ARM-JeOS-cuboxi.armv7l-2018.08.13-Snapshot20180822.raw.xz Both fail at booth with Loading kernel... Loading initrd... [ 0.303128] Initramfs unpacking failed: junk in compressed archive [ 1.653868] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) So something seems wrong with that initrd. The microsd is not at fault: - tried 2 cards - tried leap 15.0 image on one of the cards: works br Josua Mayer Appendix: the kernel part of the log - skipped u-boot Loading kernel... Loading initrd... [ 0.303128] Initramfs unpacking failed: junk in compressed archive [ 1.653868] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) [ 1.662151] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 4.17.13-1-default #1 openSUSE Tumbleweed (unreleased) [ 1.671896] Hardware name: Freescale i.MX6 Quad/DualLite (Device Tree) [ 1.678469] [<c0321000>] (unwind_backtrace) from [<c0319640>] (show_stack+0x20/0x28) [ 1.686231] [<c0319640>] (show_stack) from [<c0de3998>] (dump_stack+0xb8/0xe4) [ 1.693470] [<c0de3998>] (dump_stack) from [<c036c1a0>] (panic+0xf0/0x28c) [ 1.700366] [<c036c1a0>] (panic) from [<c15018ec>] (mount_block_root+0x26c/0x31c) [ 1.707862] [<c15018ec>] (mount_block_root) from [<c1501a30>] (mount_root+0x94/0x98) [ 1.715619] [<c1501a30>] (mount_root) from [<c1501b94>] (prepare_namespace+0x160/0x1a8) [ 1.723635] [<c1501b94>] (prepare_namespace) from [<c1501420>] (kernel_init_freeable+0x42c/0x440) [ 1.732523] [<c1501420>] (kernel_init_freeable) from [<c0df8a44>] (kernel_init+0x18/0x128) [ 1.740801] [<c0df8a44>] (kernel_init) from [<c03010ac>] (ret_from_fork+0x14/0x28) [ 1.748376] Exception stack(0xee947fb0 to 0xee947ff8) [ 1.753435] 7fa0: 00000000 00000000 00000000 00000000 [ 1.761619] 7fc0: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 [ 1.769801] 7fe0: 00000000 00000000 00000000 00000000 00000013 00000000 [ 1.776435] CPU1: stopping [ 1.779157] CPU: 1 PID: 0 Comm: swapper/1 Not tainted 4.17.13-1-default #1 openSUSE Tumbleweed (unreleased) [ 1.788902] Hardware name: Freescale i.MX6 Quad/DualLite (Device Tree) [ 1.795453] [<c0321000>] (unwind_backtrace) from [<c0319640>] (show_stack+0x20/0x28) [ 1.803211] [<c0319640>] (show_stack) from [<c0de3998>] (dump_stack+0xb8/0xe4) [ 1.810445] [<c0de3998>] (dump_stack) from [<c031d5ac>] (handle_IPI+0x338/0x360) [ 1.817856] [<c031d5ac>] (handle_IPI) from [<c0302c40>] (gic_handle_irq+0x98/0x9c) [ 1.825438] [<c0302c40>] (gic_handle_irq) from [<c030203c>] (__irq_svc+0x5c/0x94) [ 1.832925] Exception stack(0xee987eb8 to 0xee987f00) [ 1.837982] 7ea0: 00000000 00000000 [ 1.846168] 7ec0: 2e066000 20000093 00000000 00000001 c170df98 c170dfe8 00000001 ef6cec00 [ 1.854354] 7ee0: 69e21c10 ee987f54 ee987f08 ee987f08 c0c2af94 c0c2af98 20000013 ffffffff [ 1.862548] [<c030203c>] (__irq_svc) from [<c0c2af98>] (cpuidle_enter_state+0x428/0x480) [ 1.870651] [<c0c2af98>] (cpuidle_enter_state) from [<c0c2b060>] (cpuidle_enter+0x40/0x54) [ 1.878929] [<c0c2b060>] (cpuidle_enter) from [<c03a0740>] (call_cpuidle+0x30/0x50) [ 1.886598] [<c03a0740>] (call_cpuidle) from [<c03a0be4>] (do_idle+0x234/0x290) [ 1.893919] [<c03a0be4>] (do_idle) from [<c03a0f1c>] (cpu_startup_entry+0x28/0x2c) [ 1.901502] [<c03a0f1c>] (cpu_startup_entry) from [<c031cfc4>] (secondary_start_kernel+0x17c/0x1a8) [ 1.910562] [<c031cfc4>] (secondary_start_kernel) from [<103034ac>] (0x103034ac) [ 1.917979] Rebooting in 90 seconds.. -- 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] Updates for Leap 15.0 on aarch64?
by Olav Reinert 09 Sep '18

09 Sep '18

Hi all, I'm running Leap 15.0 on my Raspberry Pi 3, the aarch64 port. It all works great, but I've noticed that the system doesn't receive any updates. Zypper only has one repository registered, which is the main download repo (see below). That's perfect for installing new packages, but it doesn't receive any updates (as expected). For example, the kernel hasn't changed since Leap 15 was released. Is there an update repository for Leap 15 on aarch64? Thanks, Olav pi3:~ # zypper lr -u Repository priorities are without effect. All enabled repositories share the same priority. # | Alias | Name | Enabled | GPG Check | Refresh | URI --+-----------------------------------+------------------------------ -----+---------+-----------+---------+--------------------------------- ------------------------------------------- 1 | openSUSE-Ports-Leap-15.0-repo-oss | openSUSE-Ports-Leap-15.0-repo- oss | Yes | (r ) Yes | Yes | http://download.opensuse.org/port s/aarch64/distribution/leap/15.0/repo/oss/ pi3:~ # rpm -qi kernel-default Name : kernel-default Version : 4.12.14 Release : lp150.11.3 Architecture: aarch64 Install Date: Sun Jun 10 20:19:13 2018 Group : System/Kernel Size : 263289216 License : GPL-2.0 Signature : RSA/SHA256, Wed May 16 22:37:53 2018, Key ID b88b2fd43dbdc284 Source RPM : kernel-default-4.12.14-lp150.11.3.nosrc.rpm Build Date : Wed May 16 22:22:37 2018 Build Host : obs-arm-2 Relocations : (not relocatable) Packager : https://bugs.opensuse.org Vendor : openSUSE URL : http://www.kernel.org/ Summary : The Standard Kernel Description : The standard kernel for both uniprocessor and multiprocessor systems. Source Timestamp: 2018-05-11 10:28:30 +0200 GIT Revision: a9fee0989a17203b0fa48196e464a738f1222412 GIT Branch: openSUSE-15.0 Distribution: openSUSE Leap 15.0 -- 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] Control output pin on RPi
by Volker Kuhlmann 06 Sep '18

06 Sep '18

Has anyone ever managed to control an output pin on a raspberry pi 3 B+? Don't laugh! Using python gpiozero [2] a few days ago produced crash output indicating 4 different ways of accessing IO pins were tried and all failed. [1] (Running as root worked no better.) Now the same thing dies with Traceback (most recent call last): File "/usr/lib/python3.6/site-packages/gpiozero/pins/pi.py", line 71, in pin pin = self.pins[n] KeyError: 4 During handling of the above exception, another exception occurred: ... File "/usr/lib/python3.6/site-packages/gpiozero/pins/local.py", line 67, in _get_revision raise PinUnknownPi('unable to locate Pi revision in /proc/cpuinfo') gpiozero.exc.PinUnknownPi: unable to locate Pi revision in /proc/cpuinfo indicating someone's relying on what looks like proprietory kernel extensions. Trying wiringpi means installing the whole gcc lafaffel, on a minimal system. Is there a something like a 3-liner cli program that can flick an output pin on request and JUST WORKS(TM) on openSUSE? (leap 15) Thanks, Volker [1] /usr/lib/python3.6/site-packages/gpiozero/devices.py:452: PinFactoryFallback: Falling back from rpigpio: module 'RPi.GPIO' has no attribute 'IN' 'Falling back from %s: %s' % (name, str(e)))) /usr/lib/python3.6/site-packages/gpiozero/devices.py:452: PinFactoryFallback: Falling back from rpio: No module named 'RPIO' 'Falling back from %s: %s' % (name, str(e)))) /usr/lib/python3.6/site-packages/gpiozero/devices.py:452: PinFactoryFallback: Falling back from pigpio: failed to connect to localhost:8888 'Falling back from %s: %s' % (name, str(e)))) /usr/lib/python3.6/site-packages/gpiozero/devices.py:452: PinFactoryFallback: Falling back from native: unable to open /dev/gpiomem or /dev/mem; upgrade your kernel or run as root 'Falling back from %s: %s' % (name, str(e)))) %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% Can't connect to pigpio at localhost(8888) Did you start the pigpio daemon? E.g. sudo pigpiod Did you specify the correct Pi host/port in the environment variables PIGPIO_ADDR/PIGPIO_PORT? E.g. export PIGPIO_ADDR=soft, export PIGPIO_PORT=8888 Did you specify the correct Pi host/port in the pigpio.pi() function? E.g. pigpio.pi('soft', 8888) %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% Traceback (most recent call last): File "./pi-out-set", line 7, in <module> from gpiozero import LED File "/usr/lib/python3.6/site-packages/gpiozero/__init__.py", line 22, in <module> from .devices import ( File "/usr/lib/python3.6/site-packages/gpiozero/devices.py", line 486, in <module> Device.pin_factory = _default_pin_factory() File "/usr/lib/python3.6/site-packages/gpiozero/devices.py", line 453, in _default_pin_factory raise BadPinFactory('Unable to load any default pin factory!') gpiozero.exc.BadPinFactory: Unable to load any default pin factory! [2] from gpiozero import LED import sys out = LED(4) state = sys.argv[1] if state == "on" or state == "1": out.on() else: out.off() -- Volker Kuhlmann http://volker.top.geek.nz/ Please do not CC list postings to me. -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

7 20

[opensuse-arm] Cubieboard2 versions 2012+2015
by Volker Kuhlmann 29 Aug '18

29 Aug '18

There are 2 different cubieboard2 versions: http://dl.cubieboard.org/model/CubieBoard2/ The 2012 one has nand flash, or TSD flash but I expect that's uncommen. The 2015 one has EMMC or TSD flash, nand flash versions don't exist, and a battery for a RTC. Apparently the EMMC and TSD versions are interchangeable, and that flash behaves like an SD card. http://dl.cubieboard.org/model/CubieBoard2/CubieBoard2-20151211-EMMC/Docs/L… Has anyone tested openSUSE on a 2015 version of cubieboard2? Or is the JeOS image for the 2012 version? Or both? Thanks, Volker -- Volker Kuhlmann http://volker.top.geek.nz/ Please do not CC list postings to me. -- 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 repo 2018-08-26
by ralph.gauer＠bwc-illmensee.de 27 Aug '18

27 Aug '18

Hi, is there any chance that the Tumbleweed repo will be getting updates soon? The current release for both armv6hl and armv7hl is "openSUSE Tumbleweed 20180622". Ralph -- 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] ARM repos
by Volker Kuhlmann 24 Aug '18

24 Aug '18

Leap 15.0 ARM comes preconfigured with a list of repositories that can be added in yast. Unfortunately, they're all the x86_64 ones. Which repos can I use for ARM systems - is there a list somewhere? And is it separate for leap, factory, tumbleweed? Looking at e.g. https://build.opensuse.org/project/show/security, ARM architecure building is only enabled for factory_ARM. I'm looking for some packages for leap 15.0. Am I supposed to use the factory packages, or how can I get leap packages? Thanks muchly, Volker -- Volker Kuhlmann http://volker.top.geek.nz/ Please do not CC list postings to me. -- 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] ChromeOS, Crostini and ARM64
by Bill Merriam 22 Aug '18

22 Aug '18

I have a Samsung Chromebook Plus which as a Rockchip 3399 processor. It now has Crostini which lets me run Linux distributions in containers. https://www.reddit.com/r/Crostini/ Naturally I want to run openSUSE. These folks have lots of containers, including openSUSE but not openSUSE for ARM64. https://uk.images.linuxcontainers.org/ https://us.images.linuxcontainers.org/ Does anybody know to get or make an ARM64 openSUSE container suitable for Crostini? Bill -- 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] Which packages for yast2?
by Volker Kuhlmann 21 Aug '18

21 Aug '18

Which packages do I have to install on a JeOS image to get the yast2 GUI? It's not yast2-x11, and yast2-control-center-qt wants to install 195 packages and 325MB - really? Surely the yast GUI doesn't need ghostscript, gstreamer, graphviz, a whole pile of languages I couldn't possibly understand, mozilla-nspr and more mozilla stuff, or parallel-printer-support, when yast TUI doesn't need all that?? Thanks muchly, Volker -- Volker Kuhlmann http://volker.top.geek.nz/ Please do not CC list postings to me. -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

5 5

[opensuse-arm] How to get openSUSE aarch64 on a RPi3B+?
by Sten Bert 17 Aug '18

17 Aug '18

I'm referring to: https://en.opensuse.org/HCL:Raspberry_Pi3 -> "USB key installation method" -> 2. Copy the firmware and bootloader ... u-boot.bin ========== Leap 42.3: works http://download.opensuse.org/ports/aarch64/distribution/leap/42.3/repo/oss/… TW: won't boot - rainbow screen (see release date!) http://download.opensuse.org/ports/aarch64/tumbleweed/repo/oss/aarch64/u-bo… Leap 15.0: won't boot - rainbow screen! http://download.opensuse.org/ports/aarch64/distribution/leap/15.0/repo/oss/… raspberrypi-firmware: ===================== Leap 42.3: too old https://opensuse.pkgs.org/42.3/opensuse-oss/raspberrypi-firmware-2016.09.02… TW: dead link! https://opensuse.pkgs.org/tumbleweed/opensuse-oss/raspberrypi-firmware-2018… Leap 15.0: the only choice https://opensuse.pkgs.org/15.0/opensuse-oss/raspberrypi-firmware-2018.03.13… Was happy to see agraf's changelog from 2018-03-14: - Update to 3347884 (2018-03-13) - Add support for new RPi3 B+ (bsc#1085262) So we have a mess with u-boot.bin (=Leap 42.3) and raspberrypi-firmware (=Leap 15.0), that enables the sd-card starting on a RPi3 B+! How to continue? Download the Leap 42.3 ISO (or the Tumbleweed ISO, or the Leap 15.0 ISO)? All installations made with kernel command line "modprobe.blacklist=vc4", as recommended. Started with TW ISO on USB key: openSUSE-Tumbleweed-DVD-aarch64-Snapshot20180622.iso - Installation starts, left me with a black background and a white mouse-cursor when switching to graphical part. Leap 15.0: openSUSE-Leap-15.0-DVD-aarch64-Build124.1.iso - dto. Leap 42.3: - openSUSE-Leap-42.3-DVD-aarch64-Build0200-Media.iso Installation process starts, but wants to prepare the USB key (itself) for installation instead of mmcblk0 (sd card). Trying to adapt the partition scheme from USB0 -> mmc with expert setting fails (system hanging)! How to go on? Any help appreciated! THX in advance. -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

10 35

[opensuse-arm] Chromebook Snow progress?
by Daniel Bischof 15 Aug '18

15 Aug '18

Hi, I regularly fetch the latest Chromebook JeOS images via --- osc getbinaries openSUSE:Factory:ARM:Live JeOS:JeOS-chromebook images armv7l --- and test them on my Chromebook. The images still fail to boot for me ("Starting Kernel", then black screen forever), but since openSUSE-Tumbleweed-ARM-JeOS-chromebook.armv7l-2018.07.23-Build1.1 there are messages that Grub is loading and a splash screen just like on x86_64. The Leap 15 JeOS image doesn't boot either. It is still unclear to me, why the Chromebook images fail. I saw U-Boot patches regarding MMC mode and device tree blob files, not sure whether these are relevant for my issues. Is somebody out there, who's successfully running the openSUSE armv7l port on Snow? ChromeOS updates are no longer available for Snow, so running an alternative OS is more desireable than ever... Best regards, --D. --- Daniel Bischof <suse-bugz(a)bischof.org> -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

3 6

[opensuse-arm] JeOS QA
by Matwey V. Kornilov 14 Aug '18

14 Aug '18

Hello, I am sorry to say, but currently openSUSE-Tumbleweed-ARM-JeOS-efi.aarch64-2018.08.13-Build1.1.raw has two breaking bugs: https://bugzilla.opensuse.org/show_bug.cgi?id=1104850 (broken GRUB) https://bugzilla.opensuse.org/show_bug.cgi?id=1092590 (broken 'secure' random in kernel) This is not how it should be. We probably need a way to test JeOS-efi.aarch64 in OpenQA to avoid such unattended issues with JeOSes. -- 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] Espressobin image not starting
by Frank Kunz 14 Aug '18

14 Aug '18

Hello, from JeOS revision log I found: Dirk Mueller (dirkmueller) committed 5 months ago (revision 602) - Drop JeOS-espressobin: use JeOS-efi.aarch64 instead - JeOS-rock64: the board now boots, but the image deploying requires manual quircks So I tried openSUSE-Tumbleweed-ARM-JeOS-efi.aarch64-2018.05.11-Build1.1.raw.xz and it cannot find the boot disk/partition: Kiwi output: ... ++ /usr/sbin/hwinfo --disk ++ cut -f2 -d: ++ grep -E 'Device File:|BIOS id' ++ sed '-es@(.*)@@' ++ tr -d ' ' + diskDevices='/dev/ram11 /dev/ram2 /dev/ram0 /dev/ram9 /dev/ram7 /dev/ram14 /dev/ram5 /dev/ram12 /dev/ram3 /dev/ram10 /dev/ram1 /dev/ram8 /dev/ram15 /dev/ram6 /dev/ram13 /dev/ram4' + lookupBiosBootDevice ... Maybe a specific mmc driver needs to be loaded, but how to do that for the generic JeOS-efi.aarch64 image? Br, Frank -- 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] CPU frequency / temperature management for NanoPi NEO
by opsyzone 07 Aug '18

07 Aug '18

Hi, I tried to rsync some Gigabytes of files to my NanoPi NEO and suddenly it stopped working: It had run really hot. Do we have some kind of CPU heat- or frequency-control available? Thanks for your answers Peter -- 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] Fwd: Updates for Leap Ports
by Axel Braun 31 Jul '18

31 Jul '18

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 <axel.braun(a)gmx.de> An: opensuse-factory(a)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+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

3 2

[opensuse-arm] openSUSE Leap 15.0 Ports
by Alexander Bergmann 27 Jul '18

27 Jul '18

Hi, I just noticed that we do not have 'openSUSE Leap 15.0 Ports' available inside OBS. Are there any afforts already to make the Ports available for 15.0? Cheers, 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] Helios4
by Paul Gonin 26 Jul '18

26 Jul '18

Hi, This arm based NAS kit is interesting. https://kobol.io/helios4/ What would be the level of difficulty to have openSUSE (pref. Leap) available for it ? thanks Paul -- 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] Z-turn Lite
by Matwey V. Kornilov 25 Jul '18

25 Jul '18

Hi, Does anybody tried Z-turn Lite board with combined CPU/FPGA SoC? It seems to be the most inexpensive model based on Xilinx Zynq SoC. http://www.myirtech.com/list.asp?id=565 -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

2 4

[opensuse-arm] Rock64 - anyone using one
by Steve Moring 25 Jul '18

25 Jul '18

Has anyone been using a rock64, interested in your thoughts. Can you run the opensuse arm distribution on it? Do you have to do anything special to get the hdmi 2.0 port to fully exploit uhd? -Steve -- 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] openSUSE get full GPU performance ?
by Xavier Primer 24 Jul '18

24 Jul '18

Hi , I'm newbie in openSUSE .. I'm running openSUSE on Raspberry Pi 3 machine. openSUSE on Raspberry Pi 3 get full GPU performance/capabilities ? Thanks, see you. -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

1 0

[SOLVED] Re: [opensuse-arm] resize the swap partition
by Xavier Primer 24 Jul '18

24 Jul '18

> Op dinsdag 24 juli 2018 15:01:10 CEST schreef Xavier Primer: > >> Hi, >> >> I'm newbie in openSUSE ... >> >> I'm running openSUSE on Raspberry Pi 3 machine. >> >> How can I resize the swap partition ? >> >> Thanks, see you. > > > I use next to the swap partition on the RPi3 a swap file. > You create the file using: > > fallocate --length ?MiB /var/swapfile > > /var/swapfile can be any path to a file, replace ? with the required size. > I > use 512. > Initialize the file using > > mkswap /var/swapfile > > If you need the swap space occasionally you can can use: > > swapon /var/swapfile > > otherwise make an entry in /etc/fstab like: > > /var/swapfile none swap sw 0 0 > > mount -a > > will mount the swapfile right after creation, otherwise it will be made > available in the boot process. > > You can inspect the swap space using: > > swapon --bytes > > -- > fr.gr. > > member openSUSE > Freek de Kruijf > Hi Freek , Your idea work fine. Thanks for your explained answer. See you. -- 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] resize the swap partition
by Xavier Primer 24 Jul '18

24 Jul '18

Hi, I'm newbie in openSUSE ... I'm running openSUSE on Raspberry Pi 3 machine. How can I resize the swap partition ? Thanks, see you. -- 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] Status of analog audio on Leap 15 / Raspberry Pi?
by Colin Beckingham 24 Jul '18

24 Jul '18

Hi, I am trying to run openSUSE Leap 15 on Raspberry Pi 3. Yast does not find any audio devices to configure. Raspbian has no problem finding and using the audio out port. The sound module (snd-bcm2835) loads correctly but aplay finds only the HDMI audio. There is some advice in other forums about setting "amixer cset numid=3 1" to direct audio to the analog port but in opensuse amixer numid=3 seems to point to a volume control rather than a PCM device switcher. Is the analog port supported at this time? aplay -l **** List of PLAYBACK Hardware Devices **** card 0: vc4hdmi [vc4-hdmi], device 0: MAI PCM vc4-hdmi-hifi-0 [] Subdevices: 1/1 Subdevice #0: subdevice #0 cat /proc/asound/devices 2: [ 0] : control 3: [ 0- 0]: digital audio playback 33: : timer -- 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] Can't mount USB-Harddisk on my NanoPi NEO
by opsyzone 24 Jul '18

24 Jul '18

Hello everybody, please do excuse if this is some kind of frequently asked question. I am quite new to this. Incidentally I came across one of these NanoPi things and installed openSUSE-Tumbleweed-ARM-JeOS-nanopineo.armv7l-2018.05.11-Build1.1 on it. Also I found some old notebook on which I put x86_64 Leap 15 to get an idea what OpensSUSE would look like nowadays. When I plug my USB-Drive into my notebook an run # dmesg I get a lot of messages about a scsi device beeing detected and named [sdb]. When I connect it to my NanoPi, I can't see anything similar. So, what do I have to do or to look for? Thanks for your answers Peter -- 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] Rasberry Pi 3B image openSUSE Tumbleweed starts on Banana Pi M64
by Freek de Kruijf 23 Jul '18

23 Jul '18

Instead of a Banana Pi M3 I got a Banana Pi M64, of which I was uncertain that the processor was the same as the one on a Raspberry Pi 3B. Still I did put the image for the Raspberry Pi 3B (aarch64) on a micro-SD card and booted the BPi. I was very happy to see the system came alive. Before this I did put the Debian image on the eMMC and was able to boot that system without a micro-SD card. On this system I inserted the micro-SD with the above mentioned openSUSE system, which came alive. The initialization of the system was not completely as it should be. There was no swap at the end of the micro-SD card and the root partition was not enlarged. I did put the swap on the eMMC, effectively erasing what was there and enlarged the root partition on the micro-SD. However after that I did a "zypper dup --no-recommends" and did a reboot. The system does not start anymore. My experiments with it will be continued, but if you have any advice I will be happy to receive it. -- 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 4

[opensuse-arm] Help with grub boot
by Alessio Adamo 22 Jul '18

22 Jul '18

Hi guys, I have installed Leap 15.0 on a MicroSD for my cubox-i. I used to run an old, unupdated Tumbleweed with rootfs on /dev/sda2. Now that the boot is accomplished via grub2, efi and uboot, what is the minimum amount of data I should keep on the MicroSD to have a bootable system? The entire /boot dir? Many thanks in advance Alessio -- 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] UHD 4k support
by Steve Moring 19 Jul '18

19 Jul '18

Hi, I've seen a few people have UHD monitors working with their raspberry pi3's. I'm confused by a constraint that appears to be an X constraint, and that's the size of the desktop. Has anyone gotten this to work successfully using an openSUSE build? This works: #cvt -r 3840 2160 60 #xrandr --newmode "3840x2160" 533.00 3840 3888 3920 4000 2160 2163 2168 2222 +hsync -vsync #xrandr --addmode HDMI-1 3840x2160 This doesn't: #xrandr --output HDMI-1 --mode "3840x2160" --rate 60 --fb 4096x4096 -- panning 4096x4096 error is: xrandr: screen cannot be larger than 2048x2048 (desired size 4096x4096) How do I change the default to something larger than 2048x2048 (desired is 4096x4096)? Is there a way to change it dynamically, or do I need to do some work with xorg.conf files? -Steve -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

2 4

[opensuse-arm] Leap 15.0 repo for OBS
by Alessio Adamo 19 Jul '18

19 Jul '18

Hi guys, for my cubox-i I switched from Tumbleweed to Leap 15.0. I had few packages built via OBS based on Tumbleweed that now I should switch to Leap as well. Can you please tell me which repo I should add? The standard Leap 15.0 repo seems not to support armv7l. Thank you in advance. 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] Images for Banana Pi M3 available?
by Freek de Kruijf 15 Jul '18

15 Jul '18

Apparently there are images for Tumbleweed and Leap 15.0 for the Banana Pi M2. Question: Are there also images for the Banana Pi M3 or should the images for Raspberry Pi 3B also work for this 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 2

[opensuse-arm] Raspberry Pi 3 X11 display question
by Steve Moring 10 Jul '18

10 Jul '18

Hi, It would appear that X is setup with a maximum of 2048x2048 for the virtual desktop size. There doesn't appear to be any X configuration that is setting this (from my reading I'd expect it to be 32767x32767) as it is with openSUSE 15 Leap on the Intel builds. What am I missing? Images I've tested this on: openSUSE-Leap15.0-ARM-X11-raspberrypi3.aarch64-2018.07.02- Buildlp150.1.1.raw.xz openSUSE-Leap15.0-ARM-XFCE-raspberrypi3.aarch64-2018.07.02- Buildlp150.1.1.raw.xz openSUSE-Leap15.0-ARM-LXQT-raspberrypi3.aarch64-2018.07.02- Buildlp150.1.1.raw.xz openSUSE-Leap15.0-ARM-KDE-raspberrypi3.aarch64-2018.07.02- Buildlp150.1.1.raw.xz xrandr --verbose output: Screen 0: minimum 320 x 200, current 1920 x 1080, maximum 2048 x 2048 HDMI-1 connected primary 1920x1080+0+0 (0x45) normal (normal left inverted right x axis y axis) 941mm x 529mm Identifier: 0x42 Timestamp: 66434 Subpixel: unknown Gamma: 1.0:1.0:1.0 Brightness: 1.0 Clones: CRTC: 0 CRTCs: 0 Transform: 1.000000 0.000000 0.000000 0.000000 1.000000 0.000000 0.000000 0.000000 1.000000 filter: EDID: 00ffffffffffff00047258053c279074 311b0103805e35782aa191a9544d9c26 0f5054bfef80714f8140818081c08100 9500b300d1c04dd000a0f0703e803020 3500ad113200001a565e00a0a0a02950 2f203500ad113200001a000000fd0032 3c1e8c3c000a202020202020000000fc 00416365722045543433304b0a20012e 020341f1506101600304121305141f10 0706026b5f23090707830100006b030c 001000383c2000200167d85dc4017880 00e305e001e40f050000e60607016060 45023a801871382d40582c4500ad1132 00001e011d007251d01e206e285500ad 113200001e8c0ad08a20e02d10103e96 00ad1132000018000000000000000098 non-desktop: 0 range: (0, 1) link-status: Good supported: Good, Bad 1920x1080 (0x45) 148.500MHz +HSync +VSync *current h: width 1920 start 2008 end 2052 total 2200 skew 0 clock 67.50KHz v: height 1080 start 1084 end 1089 total 1125 clock 60.00Hz 1920x1080 (0x46) 148.500MHz +HSync +VSync h: width 1920 start 2448 end 2492 total 2640 skew 0 clock 56.25KHz v: height 1080 start 1084 end 1089 total 1125 clock 50.00Hz 1920x1080 (0x47) 148.352MHz +HSync +VSync h: width 1920 start 2008 end 2052 total 2200 skew 0 clock 67.43KHz v: height 1080 start 1084 end 1089 total 1125 clock 59.94Hz 1920x1080i (0x48) 74.250MHz +HSync +VSync Interlace h: width 1920 start 2008 end 2052 total 2200 skew 0 clock 33.75KHz v: height 1080 start 1084 end 1094 total 1125 clock 60.00Hz 1920x1080i (0x49) 74.250MHz +HSync +VSync Interlace h: width 1920 start 2448 end 2492 total 2640 skew 0 clock 28.12KHz v: height 1080 start 1084 end 1094 total 1125 clock 50.00Hz 1920x1080i (0x4a) 74.176MHz +HSync +VSync Interlace h: width 1920 start 2008 end 2052 total 2200 skew 0 clock 33.72KHz v: height 1080 start 1084 end 1094 total 1125 clock 59.94Hz 1680x1050 (0x4b) 119.000MHz +HSync -VSync h: width 1680 start 1728 end 1760 total 1840 skew 0 clock 64.67KHz v: height 1050 start 1053 end 1059 total 1080 clock 59.88Hz 1280x1024 (0x4c) 135.000MHz +HSync +VSync h: width 1280 start 1296 end 1440 total 1688 skew 0 clock 79.98KHz v: height 1024 start 1025 end 1028 total 1066 clock 75.02Hz 1280x1024 (0x4d) 108.000MHz +HSync +VSync h: width 1280 start 1328 end 1440 total 1688 skew 0 clock 63.98KHz v: height 1024 start 1025 end 1028 total 1066 clock 60.02Hz 1440x900 (0x4e) 88.750MHz +HSync -VSync h: width 1440 start 1488 end 1520 total 1600 skew 0 clock 55.47KHz v: height 900 start 903 end 909 total 926 clock 59.90Hz 1280x960 (0x4f) 108.000MHz +HSync +VSync h: width 1280 start 1376 end 1488 total 1800 skew 0 clock 60.00KHz v: height 960 start 961 end 964 total 1000 clock 60.00Hz 1280x800 (0x50) 71.000MHz +HSync -VSync h: width 1280 start 1328 end 1360 total 1440 skew 0 clock 49.31KHz v: height 800 start 803 end 809 total 823 clock 59.91Hz 1152x864 (0x51) 108.000MHz +HSync +VSync h: width 1152 start 1216 end 1344 total 1600 skew 0 clock 67.50KHz v: height 864 start 865 end 868 total 900 clock 75.00Hz 1280x720 (0x52) 74.250MHz +HSync +VSync h: width 1280 start 1390 end 1430 total 1650 skew 0 clock 45.00KHz v: height 720 start 725 end 730 total 750 clock 60.00Hz 1280x720 (0x53) 74.250MHz +HSync +VSync h: width 1280 start 1720 end 1760 total 1980 skew 0 clock 37.50KHz v: height 720 start 725 end 730 total 750 clock 50.00Hz 1280x720 (0x54) 74.176MHz +HSync +VSync h: width 1280 start 1390 end 1430 total 1650 skew 0 clock 44.96KHz v: height 720 start 725 end 730 total 750 clock 59.94Hz 1024x768 (0x55) 78.750MHz +HSync +VSync h: width 1024 start 1040 end 1136 total 1312 skew 0 clock 60.02KHz v: height 768 start 769 end 772 total 800 clock 75.03Hz 1024x768 (0x56) 75.000MHz -HSync -VSync h: width 1024 start 1048 end 1184 total 1328 skew 0 clock 56.48KHz v: height 768 start 771 end 777 total 806 clock 70.07Hz 1024x768 (0x57) 65.000MHz -HSync -VSync h: width 1024 start 1048 end 1184 total 1344 skew 0 clock 48.36KHz v: height 768 start 771 end 777 total 806 clock 60.00Hz 832x624 (0x58) 57.284MHz -HSync -VSync h: width 832 start 864 end 928 total 1152 skew 0 clock 49.73KHz v: height 624 start 625 end 628 total 667 clock 74.55Hz 800x600 (0x59) 50.000MHz +HSync +VSync h: width 800 start 856 end 976 total 1040 skew 0 clock 48.08KHz v: height 600 start 637 end 643 total 666 clock 72.19Hz 800x600 (0x5a) 49.500MHz +HSync +VSync h: width 800 start 816 end 896 total 1056 skew 0 clock 46.88KHz v: height 600 start 601 end 604 total 625 clock 75.00Hz 800x600 (0x5b) 40.000MHz +HSync +VSync h: width 800 start 840 end 968 total 1056 skew 0 clock 37.88KHz v: height 600 start 601 end 605 total 628 clock 60.32Hz 800x600 (0x5c) 36.000MHz +HSync +VSync h: width 800 start 824 end 896 total 1024 skew 0 clock 35.16KHz v: height 600 start 601 end 603 total 625 clock 56.25Hz 720x576 (0x5d) 27.000MHz -HSync -VSync h: width 720 start 732 end 796 total 864 skew 0 clock 31.25KHz v: height 576 start 581 end 586 total 625 clock 50.00Hz 720x480 (0x5e) 27.027MHz -HSync -VSync h: width 720 start 736 end 798 total 858 skew 0 clock 31.50KHz v: height 480 start 489 end 495 total 525 clock 60.00Hz 720x480 (0x5f) 27.000MHz -HSync -VSync h: width 720 start 736 end 798 total 858 skew 0 clock 31.47KHz v: height 480 start 489 end 495 total 525 clock 59.94Hz 720x480i (0x60) 13.514MHz -HSync -VSync Interlace h: width 720 start 739 end 801 total 858 skew 0 clock 15.75KHz v: height 480 start 488 end 494 total 525 clock 60.00Hz 720x480i (0x61) 13.500MHz -HSync -VSync Interlace h: width 720 start 739 end 801 total 858 skew 0 clock 15.73KHz v: height 480 start 488 end 494 total 525 clock 59.94Hz 640x480 (0x62) 31.500MHz -HSync -VSync h: width 640 start 656 end 720 total 840 skew 0 clock 37.50KHz v: height 480 start 481 end 484 total 500 clock 75.00Hz 640x480 (0x63) 31.500MHz -HSync -VSync h: width 640 start 664 end 704 total 832 skew 0 clock 37.86KHz v: height 480 start 489 end 492 total 520 clock 72.81Hz 640x480 (0x64) 30.240MHz -HSync -VSync h: width 640 start 704 end 768 total 864 skew 0 clock 35.00KHz v: height 480 start 483 end 486 total 525 clock 66.67Hz 640x480 (0x65) 25.200MHz -HSync -VSync h: width 640 start 656 end 752 total 800 skew 0 clock 31.50KHz v: height 480 start 490 end 492 total 525 clock 60.00Hz 640x480 (0x66) 25.175MHz -HSync -VSync h: width 640 start 656 end 752 total 800 skew 0 clock 31.47KHz v: height 480 start 490 end 492 total 525 clock 59.94Hz 720x400 (0x67) 28.320MHz -HSync +VSync h: width 720 start 738 end 846 total 900 skew 0 clock 31.47KHz v: height 400 start 412 end 414 total 449 clock 70.08Hz Composite-1 unknown connection (normal left inverted right x axis y axis) Identifier: 0x43 Timestamp: 66434 Subpixel: unknown Clones: CRTCs: 0 Transform: 1.000000 0.000000 0.000000 0.000000 1.000000 0.000000 0.000000 0.000000 1.000000 filter: mode: NTSC supported: NTSC, NTSC-J, PAL, PAL-M non-desktop: 0 range: (0, 1) link-status: Good supported: Good, Bad 720x480 (0x68) 13.500MHz Interlace h: width 720 start 734 end 798 total 858 skew 0 clock 15.73KHz v: height 480 start 483 end 486 total 502 clock 62.69Hz Is there a preferred way to set the Virtual Desktop size, or is there a specific reason that it's set to 2048x2048? -Steve -- 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] Why JeOS-efi removal?
by Andreas Färber 06 Jul '18

06 Jul '18

Hi Guillaume, Why is your sr#621203 deleting the JeOS-efi flavor? I don't see any discussion here about this change, nor any bug report referenced. Thanks, 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] Tests of ARM Leap 15.0
by Guillaume Gardet 29 Jun '18

29 Jun '18

Hi, here are some results of my tests of Leap 15.0 images. * JeOS-beagle : OK. (DVI output not working on BBxM, as on Tumbleweed) * JeOS-beaglebone: OK on BB Black. HDMI not tested. * XFCE-raspberrypi2: OK * XFCE-sabrelite : USB not working (fine in TW), only 1/4 of the screen is used for display (same in TW), otherwise ok. => not blocking since Ethernet is working and will allow updates. * KDE-chromebook: (not built, JeOS needs to be updated) u-boot ok, but get a black screen then, no repartition happened (same in latest TW). openQA looks fine: https://openqa.opensuse.org/tests/overview?distri=opensuse&version=15.0&bui… * Firefox problem is fixed in devel and Factory. Should be released to Leap:15.0 through updates. * Gnome terminal problem is an openQA problem (color font mismatch) If people could also share there tests, it would help to decide when we could release Leap 15.0 for ARM. :) Guillaume -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

10 26

Re: Re : [opensuse-arm] Version-agnostic link to Leap images
by Alessio Adamo 28 Jun '18

28 Jun '18

Hi Guillaume, indeed for Leap it shouldn't be a pressing feature, but since the links are hardcoded in Ignition, if a new fix is required in the future, it will be necessary to go through a git pull request again. If it's not much trouble, it will be a nice feature to have. Many thanks in advance. Alessio 2018-06-28 14:01 GMT+02:00 <guillaume.gardet(a)free.fr>: > > Hi, > > For 42.3, we had symlinks for rootfs only. > > Once (really) published, version numbers should not change anymore. > Please note, that we still need to update the current version. > > Dirk, do you think we could get symlinks without version numbers included for Leap 15.0? > By the way, we should push the current version since the published version is broken for a number of boards. > > > Guillaume > > > ----- Alessio Adamo <alessio.adamo(a)gmail.com> a écrit : >> Hi guys, >> >> I own a cubox-i and I'm working to add support for Leap images to >> Ignition (a GUI to download and flash SD cards with your favorite >> distro; https://wiki.solid-run.com/doku.php?id=products:imx6:software:os:ignition) >> For maintenance reasons, a version-agnostic symlink to the latest Leap >> image would be of great help (for Tumbleweed there is already). >> Do you think it can be done in conjunction with next image publication? >> >> Kind regards >> >> Alessio >> -- >> To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org >> To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org >> > -- 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] Version-agnostic link to Leap images
by Alessio Adamo 28 Jun '18

28 Jun '18

Hi guys, I own a cubox-i and I'm working to add support for Leap images to Ignition (a GUI to download and flash SD cards with your favorite distro; https://wiki.solid-run.com/doku.php?id=products:imx6:software:os:ignition) For maintenance reasons, a version-agnostic symlink to the latest Leap image would be of great help (for Tumbleweed there is already). Do you think it can be done in conjunction with next image publication? Kind regards 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] Image building
by Axel Braun 27 Jun '18

27 Jun '18

Hello, one question re. image building for Raspi: I want to enhance an existing image, pack and provide it for download. It is a bit more complicated, so kiwi-builds were not successful so far. Idea would be to copy the image with dd and compress it, or use a tool like clonezilla as alternative (although this is quite complicated for average users). Any better suggestions or proposals? Thanks Axel -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

3 2

[opensuse-arm] Issues with Leap 15 image LXQT
by Axel Braun 27 Jun '18

27 Jun '18

Hello, I have installed the LXQT Leap 15 image on a new Raspi, and noticed some issues with that: - there is no update repository set-up. is this by intention? - Firefox crashes with a segfault on start - chromium starts, but in default setup (as root) it can only be started from command line, as it needs an additional parameter - the File manager (fcpacman-qt) does not start: the screen flickers shortly, and nothing happens. Probably the dependecy on the base package fcpackman is not porperly set in the spec file. - for the wishlist: a simple text editor installed by default For he rest...nice! Cheers Axel -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

4 4

Re: [opensuse-arm] Tests of ARM Leap 15.0
by Guillaume Gardet 26 Jun '18

26 Jun '18

Hi, Le 25/06/2018 à 17:35, suse-bugz(a)bischof.org a écrit : > Hi Guillaume, > > On Mon, 25 Jun 2018, Guillaume Gardet wrote: > >> Le 22/06/2018 à 16:03, Frank Kunz a écrit : >>> Am 20.06.2018 um 08:58 schrieb Guillaume Gardet: >>> >>>>> there is also some effect for the efi part. So also other boards >>>>> might be affected by that missing path? >>>> It should not hurt here, as it will just not switch folder. But >>>> /usr/src/packages/KIWIROOT-oem/boot/u-boot-with-spl.sfp should be >>>> changed to boot/u-boot-with-spl.sfp in installation script. >>>> >>>> I will send an update for TW and Leap 15.0 to get u-boot installed >>>> properly for your board. >>>> >>>> Guillaume >>>> >>> Now it works. Thank you for your support. >> >> Great. Enjoy openSUSE on your board. :) >> >> If you have time, please add what works and what does not work for your board, on the wiki page: >> https://en.opensuse.org/openSUSE:Supported_ARM_boards#Board_Status >> There are both Leap and Tumbleweed tables. > > https://en.opensuse.org/openSUSE:Supported_ARM_boards#Board_Status > > states that Chromebooks (Samsung XE303C12) work with both Tumbleweed (image version 2018.06.14) and Leap 15. > > I probably missed something, but where are those images? > > http://download.opensuse.org/ports/armv7hl/tumbleweed/images/ > > is at 11 May (used to be 05 May until yesterday)... Yes, known problem, the source of this problem has been identified, we are working on this to get latest images published. That's explain why 2018.06.14 has not been published there yet. In the meantime, you can get the latest image from command line: osc getbinaries openSUSE:Factory:ARM:Live JeOS:JeOS-chromebook images armv7l Just replace JeOS-chromebook with XFCE-chromebook or any flavor you need. Guillaume > > > Best regards, > > --Daniel. -- 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] Is there any support for the Raspberry Pi Camera in an openSUSE image/repository?
by Freek de Kruijf 25 Jun '18

25 Jun '18

The question says it all! Is there any support for the Raspberry Pi Camera in an openSUSE image/ repository? -- 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

3 3

[opensuse-arm] opensuse.org and openSUSE ARM
by Matwey V. Kornilov 19 Jun '18

19 Jun '18

Hi all, I think it is important that there is no way to figure out that openSUSE available at ARM architecture reading site www.opensuse.org Trying to "download" Linux, I end up on https://software.opensuse.org/distributions/leap?locale=en where only x86_64 is available. In my opinion we could highlight presence of ARM port for a few best-supported SBCs (for instance, Raspberry Pi, BeagleBone, QEMU/EFI). What do you think? -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

5 6

[opensuse-arm] Problem running python script using GPIO
by Freek de Kruijf 15 Jun '18

15 Jun '18

I am using a Raspberry Pi 1B to count some pulses on one of the GPIO pins, using Python script. This script runs fine on an older version of Tumbleweed, namely 20160625. When I run my script on the current version, 20180502, it throws an error message: GPIO.add_event_detect(PIN, GPIO.FALLING, callback=cb, bouncetime=100) RuntimeError: Failed to add edge detection I found a message from Frank Kunz about using the pins via sysfs, of which I have the feeling this related. Maybe not! The solution that was mentioned was installing the pinmux driver. However I can't find such a thing. -- 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

4 7

[opensuse-arm] Debugging 64-bit systems on the Raspberry Pi
by Petr Tesarik 14 Jun '18

14 Jun '18

Hi all, this is JFYI. I had some success with hardware debugging of a RPi3 board using JTAG, and some people thought it's worth sharing how I did it. If you're interested, details are described in this blog article: https://www.suse.com/c/debugging-raspberry-pi-3-with-jtag/ Petr T -- 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] Factory/Tumbleweed for ARM: gcc8 rebuild running
by Dirk Müller 12 Jun '18

12 Jun '18

Hi, as of this monday morning we have gcc8 in Factory:ARM (it entered x86 end of last week). a full rebuild of aarch64 and armv7l with that compiler is running, expect some delays in the publish of the next snapshot. hopefully this is finished by the end of this week. 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] Tumbleweed images for Raspberry Pi 3B and 3B+
by Cor Slot 08 Jun '18

08 Jun '18

Hi When will new Tumbleweed images be published for Raspberry Pi 3 (3B, 3B+)? Images on http://download.opensuse.org/ports/aarch64/tumbleweed/images/ are dated Feb 02, 2018 and don't work on the 3B+. Or can I use an alternative method to install Tumbleweed on a 3B+? (how?) Thanks. Cheers, Cor. suse(a)vger.net -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

6 10

[opensuse-arm] rock64
by Mark Petersen 06 Jun '18

06 Jun '18

Hello, I'm trying to get openSUSE running on my rock64 2GB SBC. I've tried to follow the HCL guide from here: https://en.opensuse.org/ HCL:Rock64 but things must have changed in the github repo. There are no rpm's in the repo so the rest of the process doesn't work. I used xzcat/dd to write the image to both emmc & sd from here: http:// download.opensuse.org/repositories/devel:/ARM:/Factory:/Contrib:/Rockchip/ images/openSUSE-Tumbleweed-ARM-JeOS-rock64.aarch64-2018.05.24-Build5.1.raw.xz but the board won't boot. I don't get any output on the serial console. Could someone provide some guidance? Thanks. Mark -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

5 6

Re : Re: [opensuse-arm] Tests of ARM Leap 15.0
by guillaume.gardet＠free.fr 06 Jun '18

06 Jun '18

Hi Paul, ----- Paul Gonin <paul.gonin(a)gmail.com> a écrit : > Hi Guillaume, > > Where is the Leap15 image for pine64 ? There is no Leap 15 image for Pine64. Guillaume > > Thanks > Paul > > Le mar. 5 juin 2018 à 12:37, Guillaume Gardet <guillaume.gardet(a)free.fr> a > écrit : > > > Hi, > > > > here are some results of my tests of Leap 15.0 images. > > * JeOS-beagle : OK. (DVI output not working on BBxM, as on Tumbleweed) > > * JeOS-beaglebone: OK on BB Black. HDMI not tested. > > * XFCE-raspberrypi2: OK > > * XFCE-sabrelite : USB not working (fine in TW), only 1/4 of the screen is > > used for display (same in TW), otherwise ok. => not blocking since Ethernet > > is working and will allow updates. > > * KDE-chromebook: (not built, JeOS needs to be updated) u-boot ok, but get > > a black screen then, no repartition happened (same in latest TW). > > > > openQA looks fine: > > https://openqa.opensuse.org/tests/overview?distri=opensuse&version=15.0&bui… > > * Firefox problem is fixed in devel and Factory. Should be released to > > Leap:15.0 through updates. > > * Gnome terminal problem is an openQA problem (color font mismatch) > > > > If people could also share there tests, it would help to decide when we > > could release Leap 15.0 for ARM. :) > > > > > > Guillaume > > > > > > -- > > To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org > > To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org > > > > -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

1 0