RE: [opensuse-arm] OpenSUSE 13.1 for armv7 upgrade
Thanks for your reply again. I tried to upgrade as follows and it failed. 1. I changed the repository to http://download.opensuse.org/ports/armv7hl/distribution/13.1/repo/oss/ (and removed the old repositories) 2. I did "zypper dup" 3. then about 576 packages needed to be upgraded, etc 4. it downloaded all these packages 5. it installed 23 packages 6. then it failed. This is the log ("rtas" is my hostname): ( 21/845) Installing: xbitmaps-1.1.1-9.1.1 ...............................[done] ( 22/845) Installing: yast2-trans-stats-2.19.0-14.1.3 ....................[done] ( 23/845) Installing: glibc-2.18-4.4.1 ...................................[done] Additional rpm output: /usr/sbin/glibc_post_upgrade: While trying to execute /usr/sbin/iconvconfig child terminated abnormally warning: %post(glibc-2.18-4.4.1.armv7hl) scriptlet failed, exit status 115 ( 24/845) Installing: libgcc_s1-4.8.1_20130909-3.2.7 ....................[error] Installation of libgcc_s1-4.8.1_20130909-3.2.7 failed: (with --nodeps --force) Error: Subprocess failed. Error: RPM failed: Command was killed by signal 4 (Illegal instruction). Abort, retry, ignore? [a/r/i] (a): r ( 24/845) Installing: libgcc_s1-4.8.1_20130909-3.2.7 ....................[error] Installation of libgcc_s1-4.8.1_20130909-3.2.7 failed: (with --nodeps --force) Error: Subprocess failed. Error: RPM failed: Command was killed by signal 4 (Illegal instruction). Abort, retry, ignore? [a/r/i] (a): a Problem occured during or after installation or removal of packages: Installation aborted by user Please see the above error message for a hint. There are some running programs that use files deleted by recent upgrade. You may wish to restart some of them. Run 'zypper ps' to list these programs. rtas:~ # zypper ps Check failed: Executing 'lsof' failed (132). rtas:~ # zypper dup Illegal instruction rtas:~ # Any hints how to continue? Thanks a lot.
-------- Oorspronkelijk bericht -------- Onderwerp: Re: [opensuse-arm] OpenSUSE 13.1 for armv7 upgrade Le 19/11/2013 15:52, G. Heim a écrit :
Thanks for your quick answer. I have a mirabox and I suppose the standard kernel won't work anyway (it took me quite some time to get a running kernel when I installed OpenSUSE 12.3).
Our kernel-default should work if you pass a valid device tree for the mirabox.
I already made an image of my SD card, thanks for the hint.
So, you could upgrade the software in your rootfs, but not the kernel ATM. So that means the rootfs for OpenSUS 13.1 is already available? Where can I get it and how do I upgrade?
Yes and no.
I mean you can do a "zypper dup" using 13.1 repos: http://download.opensuse.org/ports/armv7hl/distribution/13.1/repo/oss/
Otherwise, the 13.1 rootfs is available here: http://download.opensuse.org/ports/armv7hl/distribution/13.1/appliances/?C=M... Grab the latest armv7 rootfs tbz file.
Please tell us if all is ok once updated.
Guillaume
Thanks again.
----------------------------------------
Date: Tue, 19 Nov 2013 14:29:18 +0100 From: guillaume.gardet@free.fr To: heelgeheim@hotmail.com; opensuse-arm@opensuse.org Subject: Re: [opensuse-arm] OpenSUSE 13.1 for armv7 upgrade
Hi,
Le 19/11/2013 14:13, G. Heim a écrit :
Hi all,
OpenSUSE 13.1 for PC just came out. I understood that there will be an armv7 version. Is that correct? And if so, when and where can I find it? Currently, our ARM images are not ready. What is your board?
What is the (preferably easy) way to upgrade my existing 12.3 to 13.1 (by not reinstalling everything)? I would recommand to backup your system (make an image of your SD card) to restore it if things goes wrong.
Moreover, kernel for 13.1 is not good ATM (does not boot on beagleboard and pandaboard, at least).
So, you could upgrade the software in your rootfs, but not the kernel ATM.
Guillaume
Thanks. -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
-- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
On 19.11.2013, at 20:49, G. Heim <heelgeheim@hotmail.com> wrote:
Thanks for your reply again.
I tried to upgrade as follows and it failed. 1. I changed the repository to http://download.opensuse.org/ports/armv7hl/distribution/13.1/repo/oss/ (and removed the old repositories) 2. I did "zypper dup" 3. then about 576 packages needed to be upgraded, etc 4. it downloaded all these packages 5. it installed 23 packages 6. then it failed.
This is the log ("rtas" is my hostname):
( 21/845) Installing: xbitmaps-1.1.1-9.1.1 ...............................[done] ( 22/845) Installing: yast2-trans-stats-2.19.0-14.1.3 ....................[done] ( 23/845) Installing: glibc-2.18-4.4.1 ...................................[done] Additional rpm output: /usr/sbin/glibc_post_upgrade: While trying to execute /usr/sbin/iconvconfig child terminated abnormally warning: %post(glibc-2.18-4.4.1.armv7hl) scriptlet failed, exit status 115
( 24/845) Installing: libgcc_s1-4.8.1_20130909-3.2.7 ....................[error] Installation of libgcc_s1-4.8.1_20130909-3.2.7 failed: (with --nodeps --force) Error: Subprocess failed. Error: RPM failed: Command was killed by signal 4 (Illegal instruction).
Abort, retry, ignore? [a/r/i] (a): r ( 24/845) Installing: libgcc_s1-4.8.1_20130909-3.2.7 ....................[error] Installation of libgcc_s1-4.8.1_20130909-3.2.7 failed: (with --nodeps --force) Error: Subprocess failed. Error: RPM failed: Command was killed by signal 4 (Illegal instruction).
Abort, retry, ignore? [a/r/i] (a): a Problem occured during or after installation or removal of packages: Installation aborted by user
Please see the above error message for a hint. There are some running programs that use files deleted by recent upgrade. You may wish to restart some of them. Run 'zypper ps' to list these programs. rtas:~ # zypper ps Check failed: Executing 'lsof' failed (132). rtas:~ # zypper dup Illegal instruction rtas:~ #
Any hints how to continue?
Ouch. This is the Mirabox I suppose? So you're running on an Amada 370 SoC. That core does not have NEON extensions, which should be fine, since IIRC we build without NEON. Maybe something changed in the compiler flags to 13.1 one or we have a compiler bug emitting NEON instructions after all though. Do you think you could just put a 13.1 rootfs into a chroot and call $ /chroot/lib/ld-linux.so.2 directly? If that works, try $ /chroot/lib/ld-linux.so.2 --library-path /chroot/lib /chroot/bin/ls If any of the two commands give you an illegal instruction, you can then try to run it in gdb: $ gdb --args /chroot/lib/ld-linux.so.2 --library-path /chroot/lib /chroot/bin/ls (gdb) run It will tell you which instruction it stumbled over on. We can then debug on from that point. Alex -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
Hey, Will there be a version for the pi? I know it's an ArmV6. Chuck On Wed, Nov 20, 2013 at 8:24 AM, Alexander Graf <agraf@suse.de> wrote:
On 19.11.2013, at 20:49, G. Heim <heelgeheim@hotmail.com> wrote:
Thanks for your reply again.
I tried to upgrade as follows and it failed. 1. I changed the repository to http://download.opensuse.org/ports/armv7hl/distribution/13.1/repo/oss/ (and removed the old repositories) 2. I did "zypper dup" 3. then about 576 packages needed to be upgraded, etc 4. it downloaded all these packages 5. it installed 23 packages 6. then it failed.
This is the log ("rtas" is my hostname):
( 21/845) Installing: xbitmaps-1.1.1-9.1.1 ...............................[done] ( 22/845) Installing: yast2-trans-stats-2.19.0-14.1.3 ....................[done] ( 23/845) Installing: glibc-2.18-4.4.1 ...................................[done] Additional rpm output: /usr/sbin/glibc_post_upgrade: While trying to execute /usr/sbin/iconvconfig child terminated abnormally warning: %post(glibc-2.18-4.4.1.armv7hl) scriptlet failed, exit status 115
( 24/845) Installing: libgcc_s1-4.8.1_20130909-3.2.7 ....................[error] Installation of libgcc_s1-4.8.1_20130909-3.2.7 failed: (with --nodeps --force) Error: Subprocess failed. Error: RPM failed: Command was killed by signal 4 (Illegal instruction).
Abort, retry, ignore? [a/r/i] (a): r ( 24/845) Installing: libgcc_s1-4.8.1_20130909-3.2.7 ....................[error] Installation of libgcc_s1-4.8.1_20130909-3.2.7 failed: (with --nodeps --force) Error: Subprocess failed. Error: RPM failed: Command was killed by signal 4 (Illegal instruction).
Abort, retry, ignore? [a/r/i] (a): a Problem occured during or after installation or removal of packages: Installation aborted by user
Please see the above error message for a hint. There are some running programs that use files deleted by recent upgrade. You may wish to restart some of them. Run 'zypper ps' to list these programs. rtas:~ # zypper ps Check failed: Executing 'lsof' failed (132). rtas:~ # zypper dup Illegal instruction rtas:~ #
Any hints how to continue?
Ouch. This is the Mirabox I suppose? So you're running on an Amada 370 SoC.
That core does not have NEON extensions, which should be fine, since IIRC we build without NEON. Maybe something changed in the compiler flags to 13.1 one or we have a compiler bug emitting NEON instructions after all though.
Do you think you could just put a 13.1 rootfs into a chroot and call
$ /chroot/lib/ld-linux.so.2
directly? If that works, try
$ /chroot/lib/ld-linux.so.2 --library-path /chroot/lib /chroot/bin/ls
If any of the two commands give you an illegal instruction, you can then try to run it in gdb:
$ gdb --args /chroot/lib/ld-linux.so.2 --library-path /chroot/lib /chroot/bin/ls (gdb) run
It will tell you which instruction it stumbled over on. We can then debug on from that point.
Alex
-- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
-- Terror PUP a.k.a Chuck "PUP" Payne (678) 636-9678 ----------------------------------------- Discover it! Enjoy it! Share it! openSUSE Linux. ----------------------------------------- openSUSE -- en.opensuse.org/User:Terrorpup openSUSE Ambassador/openSUSE Member Community Manager -- Southeast Linux Foundation (SELF) skype,twiiter,identica,friendfeed -- terrorpup freenode(irc) --terrorpup/lupinstein Register Linux Userid: 155363 Have you tried SUSE Studio? Need to create a Live CD, an app you want to package and distribute , or create your own linux distro. Give SUSE Studio a try. www.susestudio.com. See you at Southeast Linux Fest, June 7-9, 2013 in Charlotte, NC. www.southeastlinuxfest.org -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
On 20.11.2013 14:31, Chuck Payne wrote:
Hey,
Will there be a version for the pi? I know it's an ArmV6.
Well, this one at least pretends to be a 13.1: http://www.zq1.de/~bernhard/linux/opensuse/raspberrypi-opensuse-20131110x.im... and works fine on my Pi. Klaas
On Wed, Nov 20, 2013 at 8:24 AM, Alexander Graf <agraf@suse.de> wrote:
On 19.11.2013, at 20:49, G. Heim <heelgeheim@hotmail.com> wrote:
Thanks for your reply again.
I tried to upgrade as follows and it failed. 1. I changed the repository to http://download.opensuse.org/ports/armv7hl/distribution/13.1/repo/oss/ (and removed the old repositories) 2. I did "zypper dup" 3. then about 576 packages needed to be upgraded, etc 4. it downloaded all these packages 5. it installed 23 packages 6. then it failed.
This is the log ("rtas" is my hostname):
( 21/845) Installing: xbitmaps-1.1.1-9.1.1 ...............................[done] ( 22/845) Installing: yast2-trans-stats-2.19.0-14.1.3 ....................[done] ( 23/845) Installing: glibc-2.18-4.4.1 ...................................[done] Additional rpm output: /usr/sbin/glibc_post_upgrade: While trying to execute /usr/sbin/iconvconfig child terminated abnormally warning: %post(glibc-2.18-4.4.1.armv7hl) scriptlet failed, exit status 115
( 24/845) Installing: libgcc_s1-4.8.1_20130909-3.2.7 ....................[error] Installation of libgcc_s1-4.8.1_20130909-3.2.7 failed: (with --nodeps --force) Error: Subprocess failed. Error: RPM failed: Command was killed by signal 4 (Illegal instruction).
Abort, retry, ignore? [a/r/i] (a): r ( 24/845) Installing: libgcc_s1-4.8.1_20130909-3.2.7 ....................[error] Installation of libgcc_s1-4.8.1_20130909-3.2.7 failed: (with --nodeps --force) Error: Subprocess failed. Error: RPM failed: Command was killed by signal 4 (Illegal instruction).
Abort, retry, ignore? [a/r/i] (a): a Problem occured during or after installation or removal of packages: Installation aborted by user
Please see the above error message for a hint. There are some running programs that use files deleted by recent upgrade. You may wish to restart some of them. Run 'zypper ps' to list these programs. rtas:~ # zypper ps Check failed: Executing 'lsof' failed (132). rtas:~ # zypper dup Illegal instruction rtas:~ #
Any hints how to continue?
Ouch. This is the Mirabox I suppose? So you're running on an Amada 370 SoC.
That core does not have NEON extensions, which should be fine, since IIRC we build without NEON. Maybe something changed in the compiler flags to 13.1 one or we have a compiler bug emitting NEON instructions after all though.
Do you think you could just put a 13.1 rootfs into a chroot and call
$ /chroot/lib/ld-linux.so.2
directly? If that works, try
$ /chroot/lib/ld-linux.so.2 --library-path /chroot/lib /chroot/bin/ls
If any of the two commands give you an illegal instruction, you can then try to run it in gdb:
$ gdb --args /chroot/lib/ld-linux.so.2 --library-path /chroot/lib /chroot/bin/ls (gdb) run
It will tell you which instruction it stumbled over on. We can then debug on from that point.
Alex
-- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
-- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
Yes, it is a Mirabox.
Do you think you could just put a 13.1 rootfs into a chroot and call
Yes, I will try later on this week. Thanks a lot for your help. ----------------------------------------
Subject: Re: [opensuse-arm] OpenSUSE 13.1 for armv7 upgrade
On 19.11.2013, at 20:49, G. Heim <heelgeheim@hotmail.com> wrote:
Thanks for your reply again.
I tried to upgrade as follows and it failed. 1. I changed the repository to http://download.opensuse.org/ports/armv7hl/distribution/13.1/repo/oss/ (and removed the old repositories) 2. I did "zypper dup" 3. then about 576 packages needed to be upgraded, etc 4. it downloaded all these packages 5. it installed 23 packages 6. then it failed.
This is the log ("rtas" is my hostname):
( 21/845) Installing: xbitmaps-1.1.1-9.1.1 ...............................[done] ( 22/845) Installing: yast2-trans-stats-2.19.0-14.1.3 ....................[done] ( 23/845) Installing: glibc-2.18-4.4.1 ...................................[done] Additional rpm output: /usr/sbin/glibc_post_upgrade: While trying to execute /usr/sbin/iconvconfig child terminated abnormally warning: %post(glibc-2.18-4.4.1.armv7hl) scriptlet failed, exit status 115
( 24/845) Installing: libgcc_s1-4.8.1_20130909-3.2.7 ....................[error] Installation of libgcc_s1-4.8.1_20130909-3.2.7 failed: (with --nodeps --force) Error: Subprocess failed. Error: RPM failed: Command was killed by signal 4 (Illegal instruction).
Abort, retry, ignore? [a/r/i] (a): r ( 24/845) Installing: libgcc_s1-4.8.1_20130909-3.2.7 ....................[error] Installation of libgcc_s1-4.8.1_20130909-3.2.7 failed: (with --nodeps --force) Error: Subprocess failed. Error: RPM failed: Command was killed by signal 4 (Illegal instruction).
Abort, retry, ignore? [a/r/i] (a): a Problem occured during or after installation or removal of packages: Installation aborted by user
Please see the above error message for a hint. There are some running programs that use files deleted by recent upgrade. You may wish to restart some of them. Run 'zypper ps' to list these programs. rtas:~ # zypper ps Check failed: Executing 'lsof' failed (132). rtas:~ # zypper dup Illegal instruction rtas:~ #
Any hints how to continue?
Ouch. This is the Mirabox I suppose? So you're running on an Amada 370 SoC.
That core does not have NEON extensions, which should be fine, since IIRC we build without NEON. Maybe something changed in the compiler flags to 13.1 one or we have a compiler bug emitting NEON instructions after all though.
Do you think you could just put a 13.1 rootfs into a chroot and call
$ /chroot/lib/ld-linux.so.2
directly? If that works, try
$ /chroot/lib/ld-linux.so.2 --library-path /chroot/lib /chroot/bin/ls
If any of the two commands give you an illegal instruction, you can then try to run it in gdb:
$ gdb --args /chroot/lib/ld-linux.so.2 --library-path /chroot/lib /chroot/bin/ls (gdb) run
It will tell you which instruction it stumbled over on. We can then debug on from that point.
Alex --
To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
Dear Alex, Thanks for your reply. I tried to do what you suggest below but I'm a bit lost. This is what I did. 1. I downloaded http://download.opensuse.org/ports/armv7hl/distribution/13.1/appliances/open... 2. mkdir rootfs 3. as root, tar xjf <file> -C rootfs (as on http://en.opensuse.org/openSUSE:OpenSUSE_on_your_ARM_board) 3. I did as root: mount --bind /proc rootfs/proc mount --bind /sys rootfs/sys mount --bind /dev rootfs/dev cp /etc/resolv.conf rootfs/etc/ chroot rootfs4. Then I tried what you suggested below:
$ /chroot/lib/ld-linux.so.2
[it did not work with /chroot, I suppose you meant /lib/ld-linux.so.2] rtas:/ # /lib/ld-linux.so.2 bash: /lib/ld-linux.so.2: No such file or directory rtas:/ # /lib/ld-linux.so.3 Usage: ld.so [OPTION]... EXECUTABLE-FILE [ARGS-FOR-PROGRAM...] You have invoked `ld.so', the helper program for shared library executables. This program usually lives in the file `/lib/ld.so', and special directives in executable files using ELF shared libraries tell the system's program loader to load the helper program from this file. This helper program loads the shared libraries needed by the program executable, prepares the program to run, and runs it. You may invoke this helper program directly from the command line to load and run an ELF executable file; this is like executing that file itself, but always uses this helper program from the file you specified, instead of the helper program file specified in the executable file you run. This is mostly of use for maintainers to test new versions of this helper program; chances are you did not intend to run this program. --list list all dependencies and how they are resolved --verify verify that given object really is a dynamically linked object we can handle --inhibit-cache Do not use /etc/ld.so.cache --library-path PATH use given PATH instead of content of the environment variable LD_LIBRARY_PATH --inhibit-rpath LIST ignore RUNPATH and RPATH information in object names in LIST --audit LIST use objects named in LIST as auditors
$ /chroot/lib/ld-linux.so.2 --library-path /chroot/lib /chroot/bin/ls
rtas:/ # /lib/ld-linux.so.3 --library-path /lib /bin/ls Illegal instruction [I did it again] rtas:/ # /lib/ld-linux.so.3 --library-path /lib /bin/ls bin dev home media opt root sbin srv tmp var boot etc lib mnt proc run selinux sys usr
$ gdb --args /chroot/lib/ld-linux.so.2 --library-path /chroot/lib /chroot/bin/ls (gdb) run
tas:/ # gdb bash: gdb: command not found [apparenty not installed, I try to install with yast] rtas:/ # yast The /proc filesystem is not mounted. If you are running in a chroot environment, bind-mount missing filesystems. [I don't understand, I did mount it] anfortas:/> zypper Illegal instruction anfortas:/> zypper Usage: zypper [--global-options] <command> [--command-options] [arguments] Does this help? Thanks. ----------------------------------------
Subject: Re: [opensuse-arm] OpenSUSE 13.1 for armv7 upgrade From: agraf@suse.de Date: Wed, 20 Nov 2013 14:24:47 +0100 CC: guillaume.gardet@free.fr; opensuse-arm@opensuse.org To: heelgeheim@hotmail.com
On 19.11.2013, at 20:49, G. Heim <heelgeheim@hotmail.com> wrote:
Thanks for your reply again.
I tried to upgrade as follows and it failed. 1. I changed the repository to http://download.opensuse.org/ports/armv7hl/distribution/13.1/repo/oss/ (and removed the old repositories) 2. I did "zypper dup" 3. then about 576 packages needed to be upgraded, etc 4. it downloaded all these packages 5. it installed 23 packages 6. then it failed.
This is the log ("rtas" is my hostname):
( 21/845) Installing: xbitmaps-1.1.1-9.1.1 ...............................[done] ( 22/845) Installing: yast2-trans-stats-2.19.0-14.1.3 ....................[done] ( 23/845) Installing: glibc-2.18-4.4.1 ...................................[done] Additional rpm output: /usr/sbin/glibc_post_upgrade: While trying to execute /usr/sbin/iconvconfig child terminated abnormally warning: %post(glibc-2.18-4.4.1.armv7hl) scriptlet failed, exit status 115
( 24/845) Installing: libgcc_s1-4.8.1_20130909-3.2.7 ....................[error] Installation of libgcc_s1-4.8.1_20130909-3.2.7 failed: (with --nodeps --force) Error: Subprocess failed. Error: RPM failed: Command was killed by signal 4 (Illegal instruction).
Abort, retry, ignore? [a/r/i] (a): r ( 24/845) Installing: libgcc_s1-4.8.1_20130909-3.2.7 ....................[error] Installation of libgcc_s1-4.8.1_20130909-3.2.7 failed: (with --nodeps --force) Error: Subprocess failed. Error: RPM failed: Command was killed by signal 4 (Illegal instruction).
Abort, retry, ignore? [a/r/i] (a): a Problem occured during or after installation or removal of packages: Installation aborted by user
Please see the above error message for a hint. There are some running programs that use files deleted by recent upgrade. You may wish to restart some of them. Run 'zypper ps' to list these programs. rtas:~ # zypper ps Check failed: Executing 'lsof' failed (132). rtas:~ # zypper dup Illegal instruction rtas:~ #
Any hints how to continue?
Ouch. This is the Mirabox I suppose? So you're running on an Amada 370 SoC.
That core does not have NEON extensions, which should be fine, since IIRC we build without NEON. Maybe something changed in the compiler flags to 13.1 one or we have a compiler bug emitting NEON instructions after all though.
Do you think you could just put a 13.1 rootfs into a chroot and call
$ /chroot/lib/ld-linux.so.2
directly? If that works, try
$ /chroot/lib/ld-linux.so.2 --library-path /chroot/lib /chroot/bin/ls
If any of the two commands give you an illegal instruction, you can then try to run it in gdb:
$ gdb --args /chroot/lib/ld-linux.so.2 --library-path /chroot/lib /chroot/bin/ls (gdb) run
It will tell you which instruction it stumbled over on. We can then debug on from that point.
Alex -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
participants (4)
-
Alexander Graf -
Chuck Payne -
G. Heim -
Klaas Freitag