July 2015 - openSUSE ARM - openSUSE Mailing Lists

Re: [opensuse-arm] Experiences with Build317.3 for RPi2
by Dirk Müller 09 Jul '15

09 Jul '15

Hi, > Sorry for the slow response on this, I did not have time to look into this > recently. It appears that the issue is that the first boot does not detect > the MMC anymore, so it doesn't find the boot partition and goes into a > rescue reboot. I have reverted the commit that most likely is causing this > issue and am going to debug it further in the next day(s). hopefully the > next image build after build 317.6 should be working again. took slightly longer than anticipated since the kernel didn't build with gcc 5.x anymore, so I had to revert to gcc 4.8, but the image now works again, and I've moved all changes to :Staging and debug that image. 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] Cross-compiling for ARM
by Stefan Bruens 07 Jul '15

07 Jul '15

Hi, I tried to cross-compile some stuff for ARMv7hl on a x86_host, but have some issues. The installed compiler/binutils are: cross-armv7hl-gcc49-4.9.0+r211729-2.1.7.x86_64 cross-arm-binutils-2.25.0-215.1.x86_64 both from the devel:gcc OBS repository The first issue is the assembler (as) is not found by the compiler. According to "armv7hl-suse-linux-gnueabi-gcc-4.9 -v --print-search-dirs" it uses: /usr/lib64/gcc/armv7hl-suse-linux-gnueabi/4.9/ /usr/lib64/gcc/armv7hl-suse-linux-gnueabi/ /usr/lib64/gcc/armv7hl-suse-linux-gnueabi/4.9/../../../../armv7hl-suse-linux- gnueabi/bin/armv7hl-suse-linux-gnueabi/4.9/ /usr/lib64/gcc/armv7hl-suse-linux-gnueabi/4.9/../../../../armv7hl-suse-linux- gnueabi/bin/ and then falls back to $PATH. I can work around this by setting the GCC env var COMPILER_PATH to /usr/arm- suse-linux-gnueabi/bin/ , where the binutils are located. The problem here obviously is the different architecture in the gcc and binutils package, as the last search dir entry points to /usr/armv7hl-suse- linux-gnueabi/bin/ instead of /usr/arm-suse-linux-gnueabi/bin The second issue it hit is a missing "unwind.h". The x86_64 gcc provides one for its arch in /usr/lib64/gcc/x86_64-suse-linux/4.9/include/unwind.h, but the armv7hl gcc is missing it. Kind regards, Stefan -- Stefan Brüns / Bergstraße 21 / 52062 Aachen home: +49 241 53809034 mobile: +49 151 50412019 work: +49 2405 49936-424 -- 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] Experiences with Build317.3 for RPi2
by Freek de Kruijf 05 Jul '15

05 Jul '15

Still the same problem as before. The system boots the openSUSE kernel, which apparently crashes. After which it boots again. The partitioning of the SD card does not seem to changed. -- 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] Build326.4 for RPi1 does not produce a proper ext4 partition
by Freek de Kruijf 04 Jul '15

04 Jul '15

I copied this image to my SD card and tried to mount the ext4 partition. Using parted showed that it it was not a proper ext4 partition. Did not know how to make it right without destroying the content. -- 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

Re: [opensuse-arm] Experiences with Build325.4 for RPi1
by Freek de Kruijf 01 Jul '15

01 Jul '15

Op woensdag 1 juli 2015 13:53:47 schreef Alexander Graf: > On 30.06.15 17:43, Freek de Kruijf wrote: > > Op dinsdag 30 juni 2015 11:49:09 schreef u: > >> On 06/30/15 11:24, Freek de Kruijf wrote: > >>> Op dinsdag 30 juni 2015 10:57:31 schreef Alexander Graf: > >>>> On 06/30/15 10:55, Freek de Kruijf wrote: > >>>>> Earlier a second boot of a system generated with this build for > >>>>> Raspberry > >>>>> Pi 1B did not work. Now I have a system that works and can be booted > >>>>> again. > >>>>> > >>>>> However trying to start a module with yast (ncurses), I tried network, > >>>>> software repositories and software all end in the following error > >>>>> message: > >>>>> > >>>>> /sbin/yast: line 426: 19947 Segmentation fault $ybindir/y2base > >>>>> $module "$@" "$SELECTED_GUI" $Y2_GEOMETRY $Y2UI_ARGS > >>>>> > >>>>> However 19947 in the above message differs with the type of module > >>>>> called > >>>>> and with the locale used. > >>>>> > >>>>> The repository still does not contain the ruby 2.2 modules for > >>>>> libstorage. > >>>>> I build these modules, which went OK. I noticed gcc5 was used. > >>>>> > >>>>> I will continue with this build to configure the applications I use. > >>>> > >>>> Do you think you could gdb the y2base binary to figure out where > >>>> exactly > >>>> it segfaults? > >>> > >>> Alex, I have no experience with gdb. I know it is used to debug and one > >>> can > >>> set breakpoints and step through the code, but that's all I know. > >> > >> No worries, there's always a first time :). In this case, all we need is > >> to attach to the program and then do 'bt' when we see the segfault. > >> > >>> I tried to run yast in one console and did "gdb -p process-id" in > >>> another > >>> after installing yast2-core-debugger. However it likes to have > >>> yast2-core- > >>> debuginfo which is not available. After giving a c in gdb and selecting > >>> software in the ncurses console, gdb continues with the following > >>> output: > >>> > >>> (gdb) c > >>> Continuing. > >>> Detaching after fork from child process 20159. > >>> [Thread 0xb601f450 (LWP 20077) exited] > >>> [Thread 0xb631b450 (LWP 20076) exited] > >>> [Inferior 1 (process 20075) exited normally] > >> > >> This means that the process was doing just fine, no segfault. So maybe a > >> different PID was the one broken? Which PID did you attach to? According > >> to the log, "y2base" is the application that faults. > >> > >> If you can't find it, try to attach strace -f to the yast binary to > >> figure out which binary gets executed. The strace should also at least > >> print out which PID segfaulted. > > > > Attached you will find strace.2. I can't find anything about a segfault. > > Search for this line: > > [pid 25753] --- SIGSEGV {si_signo=SIGSEGV, si_code=SEGV_MAPERR, > si_addr=0x10} --- > > That's where the segfault occurs :). I entered the following bug in bugzilla: https://bugzilla.opensuse.org/show_bug.cgi?id=936788 The problem is apparently in the package yast2-pkg-bindings. -- 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] Experiences with Build326.2 for RPi1 and Build316.1 for RPi2
by Freek de Kruijf 01 Jul '15

01 Jul '15

The Build for RPi1 works, but has the same problem as with the previous build when trying to use YaST with ncurses. The Build for RPi2 does not work. The same problem. After booting the openSUSE image the system boots from the start after some time and repeats this. So apparently the openSUSE image crashes. Inspecting the micro-SD card after this process shows no changes in the partitioning of this card. -- 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