September 2015 - openSUSE ARM - openSUSE Mailing Lists

[opensuse-arm] Attempt to run KIWI on unsupported architecture 'armv8l'
by Dirk Müller 12 Apr '17

12 Apr '17

Hi, this is a known OBS bug, asked the admins to deploy a fix shortly. Greetings, Dirk -- 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] Tests of latest images for RPi1
by Freek de Kruijf 16 Nov '15

16 Nov '15

Build336.2 from repositories/devel:/ARM:/Factory:/Contrib:/RaspberryPi:/upstream/ boots, the SD is partitioned and the resulting system boots. However the Ethernet connection does not become active. The lights stay off. I could not find a method to list the journal on the SD partition on a system where the SD is mounted. Build325.2 from repositories/devel:/ARM:/Factory:/Contrib:/RaspberryPi/ does the low level boot, but after that, like before, can't find the boot image on the 3rd partition. Upgrading a system build earlier with a working image works OK. Finally the problem using the command "yast lan" is solved. -- 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 5

[opensuse-arm] Re: [opensuse-kernel] Re: armv7hl kernel-default config have tegra20 serial output broken
by Misha Komarovskiy 06 Oct '15

06 Oct '15

Hello, I have no experience with kgdb. As system restarts after panic timeout i wanted to catch oops message in kernel output via serial console. --- Best Regards, Misha Komarovskiy zombahatgmaildotcom On Sat, Aug 1, 2015 at 1:46 PM, Matwey V. Kornilov <matwey.kornilov(a)gmail.com> wrote: > 01.08.2015 12:48, Misha Komarovskiy пишет: >> Hello, >> I found that latest images for my armv7 board (paz00/ac100) which use >> kernel-default have kernel panic on start without any output to serial >> console, but serial output was working last time i tested image back >> in may. >> >> I cloned kernel-source git repo made sequence-patched kernel and >> recompiled it with >> enabling DEBUG_LL,TEGRA UART_A and EARLYPRINTK config options added to >> config/armv7hl/default config, but found that there is no ttyS0 >> output, only earlycon here is paste: >> http://paste.opensuse.org/31390203 >> > > Have you tried to use kgdb? Does it not work too? > >> Recompiling same kernel with multi_v7_defconfig config and same >> debug/earlyprintk options have no panics and normal serial output: >> http://paste.opensuse.org/13080662 >> >> Maybe kernel-default config require some extra tricks now to have serial output? >> I want to catch that panic. >> --- >> Best Regards, >> Misha Komarovskiy >> zombahatgmaildotcom >> > > > -- > To unsubscribe, e-mail: opensuse-kernel+unsubscribe(a)opensuse.org > To contact the owner, e-mail: opensuse-kernel+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

3 11

[opensuse-arm] openSUSE_Factory_ARM: systemd-tmpfiles: command not found
by Michael Ströder 06 Oct '15

06 Oct '15

HI! I'm building in a local OBS branch: https://build.opensuse.org/package/show/home:stroeder:branches:server:dns/u… All builds work ok but all openSUSE_Factory_ARM builds fail with this message: /.build_patchrpmcheck_scr: line 22: systemd-tmpfiles: command not found postinstall script of unbound-1.5.5rc1-21.1.armv6hl.rpm failed Any clue? Ciao, Michael.

2 2

[opensuse-arm] Drop 12.2 and 12.3 ARM build in X11:Enlightenment:Factory
by Tomáš Čech 01 Oct '15

01 Oct '15

Hi, is there chance that anyone would be using and requiring 12.2 and 12.3 ARM builds of X11:Enlightenment:Factory? I should either drop the support or fix it but I'd rather drop it and have just latest distro versions as build targets... Is anyone still using that? If there is noone during the week, I'll just drop it. Thanks. Tomas Cech Sleep_Walker -- 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] have same soname but different type
by Michael Ströder 30 Sep '15

30 Sep '15

Updating a rasperry pi results in a lot of messages saying "have same soname but different type" (see below). Anything to be concerned about? Ciao, Michael. Additional rpm output: /sbin/ldconfig: libraries libtasn1.so.6.4.2 and libtasn1.so.6.5.1 in directory /usr/lib have same soname but different type. (14/65) Installing: libsystemd0-224-1.1 ..................................................................................................................................................................[done] Additional rpm output: /sbin/ldconfig: libraries libsystemd.so.0.6.0 and libsystemd.so.0.10.1 in directory /usr/lib have same soname but different type. (15/65) Installing: libsensors4-3.4.0-1.2 ................................................................................................................................................................[done] Additional rpm output: /sbin/ldconfig: libraries libsystemd.so.0.6.0 and libsystemd.so.0.10.1 in directory /usr/lib have same soname but different type. /sbin/ldconfig: libraries libsystemd.so.0.6.0 and libsystemd.so.0.10.1 in directory /usr/lib have same soname but different type. (16/65) Installing: libseccomp2-2.2.3-2.1 ................................................................................................................................................................[done] Additional rpm output: /sbin/ldconfig: libraries libsystemd.so.0.6.0 and libsystemd.so.0.10.1 in directory /usr/lib have same soname but different type. /sbin/ldconfig: libraries libsystemd.so.0.6.0 and libsystemd.so.0.10.1 in directory /usr/lib have same soname but different type. (17/65) Installing: libdbus-1-3-1.8.18-3.1 ...............................................................................................................................................................[done] Additional rpm output: /sbin/ldconfig: libraries libsystemd.so.0.6.0 and libsystemd.so.0.10.1 in directory /usr/lib have same soname but different type. /sbin/ldconfig: libraries libsystemd.so.0.6.0 and libsystemd.so.0.10.1 in directory /usr/lib have same soname but different type. (18/65) Installing: libavahi-common3-0.6.31-25.3 .........................................................................................................................................................[done] Additional rpm output: /sbin/ldconfig: libraries libsystemd.so.0.6.0 and libsystemd.so.0.10.1 in directory /usr/lib have same soname but different type. /sbin/ldconfig: libraries libsystemd.so.0.6.0 and libsystemd.so.0.10.1 in directory /usr/lib have same soname but different type. (19/65) Installing: libapparmor1-2.10-4.1 ................................................................................................................................................................[done] Additional rpm output: /sbin/ldconfig: libraries libsystemd.so.0.6.0 and libsystemd.so.0.10.1 in directory /usr/lib have same soname but different type. /sbin/ldconfig: libraries libsystemd.so.0.6.0 and libsystemd.so.0.10.1 in directory /usr/lib have same soname but different type. (20/65) Installing: libXmuu1-1.1.2-5.1 ...................................................................................................................................................................[done] Additional rpm output: /sbin/ldconfig: libraries libsystemd.so.0.6.0 and libsystemd.so.0.10.1 in directory /usr/lib have same soname but different type. (21/65) Installing: libXext6-1.3.3-3.1 ...................................................................................................................................................................[done] Additional rpm output: /sbin/ldconfig: libraries libsystemd.so.0.6.0 and libsystemd.so.0.10.1 in directory /usr/lib have same soname but different type. (22/65) Installing: iproute2-4.2-1.1 .....................................................................................................................................................................[done] (23/65) Installing: hwinfo-21.21-1.2 .....................................................................................................................................................................[done] Additional rpm output: /sbin/ldconfig: libraries libsystemd.so.0.6.0 and libsystemd.so.0.10.1 in directory /usr/lib have same soname but different type. /sbin/ldconfig: libraries libsystemd.so.0.6.0 and libsystemd.so.0.10.1 in directory /usr/lib have same soname but different type.

1 0

[opensuse-arm] kiwi initrd: perl modules installed but not used
by Matwey V. Kornilov 27 Sep '15

27 Sep '15

Hello, In initrd from openSUSE:Factory:ARM JeOS there is > du -sch usr/lib/perl5 2,4M usr/lib/perl5 At the same time, there is no /usr/bin/perl, and I have not found who needs this modules. Maybe the perl modules have to be dropped as well? -- 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] kiwi initrd drivers
by Matwey V. Kornilov 26 Sep '15

26 Sep '15

Hello, In JeOS.kiwi for armv7hl I see the following: <drivers> <file name="drivers/ata/*"/>  <file name="drivers/dma/*"/>  <file name="drivers/gpio/*"/>  <file name="drivers/gpu/*"/>  <file name="drivers/mmc/*"/>  <file name="drivers/phy/*"/>  </drivers> but in the generated initrd I see that all drivers are present: lib/modules/4.3.0-rc2-1.g2b75354-default/kernel/drivers> ls ata cdrom dma gpu hwmon input media mfd mmc ntb phy ptp soc thermal uwb video block char gpio hid iio md message misc net parport pps scsi ssb usb vhost virtio And I cannot understand how this is supposed to work. What <drivers> is used for? -- 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] 13.2 ARM updates
by Volker Kuhlmann 23 Sep '15

23 Sep '15

oS 13.2 on a cubieboard: # zypper up Loading repository data... Warning: Repository 'openSUSE-13.2-repo-update' appears to be outdated. Consider using a different mirror or server. Same after zypper ref (which zypper up does first anyway). This came up in May too, without answer. # zypper lr -u | grep upda http://download.opensuse.org/ports/update/13.2/ Is this the correct repo to use for 13.2 ARM updates? If yes, the answer is obvious - the latest update in there is 25 June! 13.2 x86 has updates every few days. Some of them won't be appliccable to ARM, but I'm sure libgcrypt and gnutls are, and I'd have guessed there to have been some kernel fixes too. The kernel, dtb-sun4i, dracut and u-boot are from factory (by necessity, the 13.2 ones don't work). Are mainstream updates not available for ARM / ports? I hope not. 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

6 11

[opensuse-arm] start startx automatically?
by Jimmy PIERRE 15 Sep '15

15 Sep '15

Greetings, Using http://download.opensuse.org/repositories/devel:/ARM:/Factory:/Contrib:/Ras… I need to ssh and start startx manually... Please advise accordlingly!. Cheers, Jimmy -- 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] Raspberry Pi with OpenSuSe: I am lost
by Edgar Dombrowski 14 Sep '15

14 Sep '15

Hi, Raspberry Pi-Friends. I am lost. Following the different advices in this forum, I have downoaded the different xz-files as listend in the Repos for the OS13,2- arm-v6i- and the arm-v7l-versions for installation into the Raspbi B+ and 2B. But it always failed when booting. What can I do? The Mikro-CD-cards are ok as success when loading varios Debian-Squeeze. Thank you for your assistance Edgar Dombroiwski, DJ3PU, Munich -- 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] How to upgrade kernel on Raspberry Pi
by Olav Reinert 07 Sep '15

07 Sep '15

Hi, I've got a Raspberry Pi running openSUSE Factory. The kernel is kernel-raspberrypi-3.11.4-1.7.armv6hl Recently, a new kernel update was installed: kernel-raspberrypi-3.11.4-10.1.armv6hl However, even though the new kernel seems to be installed correctly, the Pi still boots into the old kernel. How do I make it boot into the new kernel? Regards, Olav -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

4 9

Re: [opensuse-arm] New 8250 OMAP serial driver
by Andreas Färber 03 Sep '15

03 Sep '15

Hi, Am 28.08.2015 um 09:22 schrieb Misha Komarovskiy: > On Mon, Aug 24, 2015 at 8:01 PM, Matwey V. Kornilov > <matwey.kornilov(a)gmail.com <mailto:matwey.kornilov@gmail.com>> wrote: > > Still no luck. > > > I noticed that current default and vanilla configs contain some platform > specific defines: > > grep -ni debug_ll * > default:7724:# CONFIG_DEBUG_LL is not set > default:7727:CONFIG_DEBUG_LL_INCLUDE="debug/bcm63xx.S" > lpae:7335:# CONFIG_DEBUG_LL is not set > lpae:7337:CONFIG_DEBUG_LL_INCLUDE="mach/debug-macro.S" > vanilla:7719:# CONFIG_DEBUG_LL is not set > vanilla:7722:CONFIG_DEBUG_LL_INCLUDE="debug/bcm63xx.S" > > maybe wrong debug macro may break some platform drivers? As you can see, CONFIG_DEBUG_LL is not enabled, so you can ignore CONFIG_DEBUG_LL_* defaults. lpae simply doesn't enable bcm63xx. Regards, Andreas P.S. No need for HTML here. :) -- 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

3 6

[opensuse-arm] Force to load module in kiwi initrd
by Guillaume Gardet 02 Sep '15

02 Sep '15

Hi Marcus, We are facing a problem with our Chromebook image. We need to load (manually) some module to get the display working. WIth dracut, we passed the right option (force_driver+="some modules"), so it is ok on 2nd boot but our 1st boot (with kiwi initrd) still show a black screen because we need to load the modules manually (which are not auto-loaded). Does kiwi support such an option? Guillaume -- 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] Samsung Chromebook current tumbleweed images
by Misha Komarovskiy 02 Sep '15

02 Sep '15

Hello, Just tried latest 316/318 Tumbleweed images for Samsung Chromebook and noticed that u-boot wont auto load boot.scr now and output contain alot errors about extlinux pxeboot. If i load boot.scr manualy, with ext2load mmc 1:2 0x50000000 boot.scr and then source 0x50000000 boot starts fine. Also lcd screen stays black after kernel start, probably some drm module still missing. --- Best Regards, Misha Komarovskiy zombahatgmaildotcom -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

4 32