August 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] 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

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

[opensuse-arm] Perl 5.22 is not published
by Oscar C 31 Aug '15

31 Aug '15

Hi, I'm trying to install the update 5.22.0 of perl but although it's build it's not yet on the repository (openSUSE:Factory:ARM), the published version is 5.20.1. Is there any problem? -- Thanks! -- 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] New 8250 OMAP serial driver
by Matwey V. Kornilov 24 Aug '15

24 Aug '15

Hello, First test with CONFIG_SERIAL_8250_OMAP=y has been failed. However, you are welcome to try: http://download.opensuse.org/repositories/home:/matwey:/JeOS-omap-serial/im… Now, I don't see any output from console. However, the system is successfully booted and available by ssh. In dmesg I see авг 17 02:03:08 linux kernel: WARNING: Your 'console=ttyO0' has been replaced by 'ttyS0' авг 17 02:03:08 linux kernel: This ensures that you still see kernel messages. Please авг 17 02:03:08 linux kernel: update your kernel commandline. and that is how it should to be. Serial device seems to be here: linux:/ # head /proc/tty/driver/serial serinfo:1.0 driver revision: 0: uart:8250 mmio:0x44E09000 irq:154 tx:7266 rx:0 RTS|CTS|DTR|DSR agetty is started on /dev/ttyS0 but no communication here. -- 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] Tests with latest Raspberry Pi images
by Freek de Kruijf 24 Aug '15

24 Aug '15

I tested a number of images from both Contrib:/RaspberryPi:/upstream as Contrib:/RaspberryPi/. From the last one I never got a working image, from upstream the last one that works is Build330.10 from Aug 6. All images for Raspberry Pi 2B are usable. -- 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] U-Boot 2015.10-rc1 ASIX Usb ethernet dongle
by Misha Komarovskiy 21 Aug '15

21 Aug '15

Hello, With update to U-Boot 2015.10-rc1 ASIX Usb ethernet dongle not detected as ethernet device anymore, but visible as usb device in usb info, tested on Chromebook Snow. Worked fine with 2015.07-rc3 in both usb2 and usb3 ports. Maybe this happen because of removal "add_snow_usb_boot.patch"? I didn't tried clean upstream versions yet, specific snow patch was my first guess. --- 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

2 4

[opensuse-arm] kiwi fails to build Tumbleweed ARM images
by Guillaume Gardet 14 Aug '15

14 Aug '15

Hi Marcus, Tumbleweed ARM images fails to build on OBS. The problem is that it cannot find the pre bootloader install script (uboot-image-*-setup). See the build log: ******************************************************************************** [ 1906s] Aug-14 11:01:45 <1> : Creating uBoot initrd image... [ 1906s] Aug-14 11:01:45 <1> : EXEC [mkimage -A arm -O linux -T ramdisk -C none -a 0x0 -e 0x0 -n 'Initrd' -d /tmp/kiwiboot.ptkelf/boot/initrd.vmx /tmp/kiwiboot.ptkelf/boot/initrd.uboot] [ 1906s] Aug-14 11:01:45 <1> : EXEC [rm -f /tmp/kiwiboot.ptkelf/boot/initrd.vmx 2>&1] [ 1906s] Aug-14 11:01:45 <1> : Creating boot.script uboot config file... [ 1906s] Aug-14 11:01:45 <1> : Calling pre bootloader install script: [ 1906s] Aug-14 11:01:45 <1> : --> uboot-image-raspberrypi-setup [ 1907s] bash: uboot-image-raspberrypi-setup: No such file or directory [ 1907s] Aug-14 11:01:46 <3> : Call failed, see console log ******************************************************************************** Any idea why? 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 1 and 2 images from of Aug 6
by Freek de Kruijf 14 Aug '15

14 Aug '15

Results of the test with images for RPi 1 and 2 from Aug 6 Raspberry Pi 1: from RapberryPi1/ image works, however command "yast lan" crashes; from RaspberryPi1:/upstream image builds a corrupt ext4 partition Raspberry Pi 2: from RaspberryPi2/ image does not boot (non of these images ever booted) from RaspberryPi2:/Staging image works. I compared the installed packages from the two working images and found some obvious differences, kernel and firmware, but other packages only has differences in the building versions, the part of the version of the package after the last -. Except: llibmicrohttpd10-0.9.41-1.2 <-> ibmicrohttpd10-0.9.42-1.1 libyui-ncurses-pkg6-2.46.2-1.4 <-> libyui-ncurses-pkg6-2.47.0-1.1 libzypp-15.4.0-1.1 <-> libzypp-15.9.0-1.1 vim-7.4.788-1.1 <-> vim-7.4.712-1.1 yast2-bootloader-3.1.127-1.1 <-> yast2-bootloader-3.1.138-1.1 zypper-1.12.3-1.1 <-> zypper-1.12.8-1.1 This dpes not give me a clue why "yast lan" crashes on the RPi1 and is OK on the RPI2. -- 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 6