Hi, Am 01.09.2013 16:24, schrieb Guillaume Gardet: > Le 31/08/2013 21:44, Andreas Färber a écrit : >> Am 31.08.2013 07:46, schrieb Andreas Färber: >>> Unfortunately copypac'ed kernel-f+s failed for Factory although it >>> succeeded for 12.2, so I'm guessing this is a binutils/gcc issue: >>> >>> https://build.opensuse.org/package/show/devel:ARM:Factory:Contrib:armStone/kernel-f+s >>> >>> [ 443s] AS arch/arm/kernel/debug.o >>> [ 443s] arch/arm/kernel/debug.S: Assembler messages: >>> [ 443s] arch/arm/kernel/debug.S:161: Error: ARM register expected -- >>> `ldr r2,[ r3,#(0x08)]' >>> [ 443s] arch/arm/kernel/debug.S:161: Error: ARM register expected -- >>> `ldr r2,[ r3,#(0x18)]' >>> [ 443s] arch/arm/kernel/debug.S:161: Error: ARM register expected -- >>> `ldr r2,[ r3,#(0x10)]' >>> [ 443s] arch/arm/kernel/debug.S:163: Error: ARM register expected -- >>> `ldr r2,[ r3,#(0x08)]' >>> [ 443s] arch/arm/kernel/debug.S:163: Error: ARM register expected -- >>> `ldr r2,[ r3,#(0x18)]' >>> [ 443s] arch/arm/kernel/debug.S:163: Error: ARM register expected -- >>> `ldr r2,[ r3,#(0x10)]' >>> [ 443s] make[1]: *** [arch/arm/kernel/debug.o] Error 1 >>> [ 443s] make: *** [arch/arm/kernel] Error 2 >> I've found a patch to backport, fixing the build. Apparently newer gas >> versions trip over the whitespace after '['. Doh. ;) >> >> However the newly built kernel complains about an unsatisfied >> kernel-uname-r = 3.3.7-F+S and, when ignored, does not boot: > > Could you explain the "complain" with a full log, please?
Not this week. zypper in kernel-f+s offered to either not install it or to ignore this dependency. I chose the latter. Question is, where does such a dependency come from and how could it be satisfied? >> Loading file "/boot/zImage" from mmc device 0:1 (xxa1) >> 2861728 bytes read >> ## Booting kernel from zImage at 40800000 >> XIP Kernel Image ... OK >> >> Starting kernel ... >> >> Uncompressing Linux... done, booting the kernel. >> >> >> The openSUSE:12.2:ARM:Contrib:Armstone kernel-f+s still boots okay. >> >> Is there anything I can try other than forward-porting the diff against >> upstream v3.3.7 to a version known working with our binutils/gcc? > > Did you check console args (device and speed) that u-boot passed to the > kernel? No, I didn't change the U-Boot environment. It's the same kernel sources (modulo trivial whitespace patch) and same kernel config, just different OBS build environments. I got the system up again by writing the /boot/zImage file from 12.2 contrib .rpm onto the SD card and then did zypper rm and some manual rm -rf for cleanup and then zypper in from the 12.2 contrib repo and that installs without that question and works fine with my 12.3 rootfs. Andreas -- SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg -- To unsubscribe, e-mail: [email protected] To contact the owner, e-mail: [email protected]
