gcc-defaults is wrong, unless proven that this occurs with all gcc
versions.
** Package changed: gcc-defaults (Ubuntu Natty) => gcc-4.5 (Ubuntu Natty)
** Also affects: gcc-linaro
Importance: Undecided
Status: New
** Tags added: toolchain
--
You received this bug notification because
Added gcc since you wouldn't have thought -marm would break something
like that.
** Also affects: gcc-defaults (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad
This bug was fixed in the package busybox - 1:1.17.1-7ubuntu3
---
busybox (1:1.17.1-7ubuntu3) natty; urgency=low
* drop -marm from armel build options to make run-init work again
(LP: #683683)
-- Oliver GrawertThu, 02 Dec 2010 15:09:33 +0100
** Changed in: busybox (Ubuntu Na
doing the same as above with the natty toolchain works fine as well, so
it seems the -marm gets in our way.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/683683
Title:
run-init on omap3, omap4 in na
rebuilding nattys busybox under mavericks toolchain (and dropping -marm)
makes it work fine
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/683683
Title:
run-init on omap3, omap4 in natty dies with "r
** Also affects: busybox (Ubuntu)
Importance: Undecided
Status: New
** Changed in: klibc (Ubuntu)
Status: Confirmed => Invalid
** Changed in: busybox (Ubuntu)
Status: New => Confirmed
** Changed in: busybox (Ubuntu)
Importance: Undecided => High
** Also affects: busyb
1.17.1-6ubuntu1 is the first package exposing the problem
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/683683
Title:
run-init on omap3, omap4 in natty dies with "run-init: Unknown error 17718852"
There is a .37 kernel package for omap in the linaro maintainers kernel
ppa if anyone is inclined to try it. There is also a meta package
there. Beware that the omap4 support is still a work in progress. The
main missing feature is framebuffer.
ppa:linaro-maintainers/kernel
--
You received th
If I replace the /bin/sh in the broken natty initrd with one from a
maverick final the problem goes away. The difference is the busybox-
initramfs package, natty is 1:1.17.1-7ubuntu2 maverick is
1:1.15.3-1ubuntu5. No other changes were made.
--
You received this bug notification because you are
Now running with the same SD card on my beagle C4 which boots to a login
... I get no debug output at all ... it's like we're never running init
out of the uInitrd ...
anyway out of time today.
--
run-init on omap3, omap4 in natty dies with "run-init: Unknown error 17718852"
https://bugs.launchp
so using some echo magic sprinkles in the initrd this seems to be coming
from the init script itself ... and the line 331 in the error message in
line 331 in init which is the following command :
exec run-init ${rootmnt} ${init} "$@" <${rootmnt}/dev/console >${rootmnt}/dev/co
nsole 2>&1
>From my
That was me ... I have an microSD / SD adapter, using the netbook-efl
image, booted on the C4 ... moved the microSD card over to the Beagle Xm
failed as noted above in this bug
--
run-init on omap3, omap4 in natty dies with "run-init: Unknown error 17718852"
https://bugs.launchpad.net/bugs/6836
Seems we have a successful boot on the C4 and a failed boot with the
*same* sd card with the XM.
--
run-init on omap3, omap4 in natty dies with "run-init: Unknown error 17718852"
https://bugs.launchpad.net/bugs/683683
You received this bug notification because you are a member of Ubuntu
Bugs, whi
** Tags added: iso-testing
--
run-init on omap3, omap4 in natty dies with "run-init: Unknown error 17718852"
https://bugs.launchpad.net/bugs/683683
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@
Debugging info on what run-init is being called with:
13:58:17 < NCommander> ogra_ac: rootmnt is "/root"
13:58:22 < NCommander> init is "/sbin/init"
13:58:26 < NCommander> arguments: "fixrtc"
Arguments to run-init are sane and correct.
--
run-init on omap3, omap4 in natty dies with "run-init: Un
I've now been able to replicate this on my beagle xm (but not my C4)
same headless 1201 natty build, same linaro-media create, same hwpack.
Boot log:
http://pastebin.ubuntu.com/538759/
--
run-init on omap3, omap4 in natty dies with "run-init: Unknown error 17718852"
https://bugs.launchpad.net/bu
Using linaro's natty daily snapshot for headless dated 1201 and the
hwpack for omap3 dated 1201 and using a linaro-media create that was
branched on 11-23 (but with no local changes) my beagle board C4 boots.
tty doesn't work but serial cons is fine:
here's the boot log.
http://pastebin.ubuntu.c
Looking at the error and the m68k bug noted, and remembering some planet
postings about armhf (Debian) and *buntu’s ARM related things, I can only wonder
if the same is true about klibc not knowing the correct (syscall? procedure
call?) ABI.
--
run-init on omap3, omap4 in natty dies with "run-in
researching the archive, it seems that klibc did not change since
maverick (not even a rebuild with the new toolchain). initramfs-tools
only had a minor change as well.
i was suspecting something with the handed over args to be wrong.
passing init=/bin/bash shows the same behavior, running run-ini
19 matches
Mail list logo
