<div dir="ltr">check for <div><br><div style>CONFIG_AUDITSYSCALL=y</div></div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Thu, Apr 4, 2013 at 2:27 PM, Jochen De Smet <span dir="ltr"><<a href="mailto:jochen.arm@leahnim.org" target="_blank">jochen.arm@leahnim.org</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Making some progress on this, slowly...<br>
<br>
<br>
After moving the USB driver from module to built-in, I was able to make it find<br>
the rootfs on the USB stick. First issue I see is this:<br>
<br>
<28>systemd[1]: No control group support available, not creating root group.<br>
<br>
even though it's definitely enabled in the kernel:<br>
<br>
[root@localhost ~]# zcat /proc/config.gz | grep CGROUP<br>
CONFIG_CGROUPS=y<br>
# CONFIG_CGROUP_DEBUG is not set<br>
CONFIG_CGROUP_NS=y<br>
CONFIG_CGROUP_FREEZER=y<br>
CONFIG_CGROUP_DEVICE=y<br>
# CONFIG_CGROUP_CPUACCT is not set<br>
CONFIG_CGROUP_SCHED=y<br>
# CONFIG_BLK_CGROUP is not set<br>
<br>
<br>
then there were a couple of systemd services failing:<br>
<27>systemd[855]: Failed at step OOM_ADJUST spawning /usr/lib/systemd/systemd-<u></u>readahead: No such file or directory<br>
<29>systemd[1]: systemd-udevd.service: main process exited, code=exited, status=206/OOM_ADJUST<br>
<br>
<br>
I managed to work around both of those by commenting out the OOMScoreAdjust<br>
parameter in their respective systemd config files.<br>
<br>
Next thing was that I forgot to adapt fstab to point to the right UUID for root.<br>
<br>
And now I'm running into this:<br>
<28>systemd[1]: dbus.service start request repeated too quickly, refusing to start.<br>
<br>
repeated a couple dozen times, then it seems to hang. Don't even get the<br>
emergency shell prompt I got through some of the failure above.<br>
<br>
I'll try some more tinkering tonight, but if anyone had any ideas I'll be happy<br>
to hear them.<span class="HOEnZb"><font color="#888888"><br>
<br>
J.</font></span><div class="HOEnZb"><div class="h5"><br>
<br>
<br>
<br>
On 4/1/2013 12:36, Jochen De Smet wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
On 3/29/2013 5:45, Peter Robinson wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hi Jochen,<br>
<br>
What is the release architecture of Debian Squeeze? I believe squeeze<br>
is only built for ARMv4 which might be part of the chroot issue. I<br>
suspect it might be easier to use the kernel from debian to boot<br>
Fedora directly.<br>
<br>
In theory the 3.8.3+ kernels in Fedora might work with it but I don't<br>
think it will because I don't believe everything needed for the device<br>
landed in the 3.8 kernel. I'm hoping the 3.9 kernel will have enough<br>
to support the marvell mvebu devices and hence we'll be able to<br>
support them out of the box for F-19. As the 3.9 kernel comes together<br>
you'll see more details on the list on how to test them on F-18.<br>
<br>
Peter<br>
</blockquote>
I actually started off trying with a 3.8.2 stock kernel, but didn't get very far; then I switched<br>
to the kernel at <a href="https://github.com/MISL-EBU-System-SW/mainline-public.git" target="_blank">https://github.com/MISL-EBU-<u></u>System-SW/mainline-public.git</a>, which I think<br>
got me a kernel that booted but wasn't able to get to the NAND device.<br>
<br>
I just tried copying the fedora rootfs to a USB stick and booting with a root= argument, but it<br>
seems to be unable to find the device at boot time even though it does get automounted, so<br>
I'm guessing some driver isn't built-in.<br>
<br>
I've also tried grabbing the sources for their default kernel and simply rebuilding, then booting<br>
the kernel over the network, but again ended up with something that couldn't read the NAND.<br>
<br>
I'll play around some more with a recompiled kernel + USB root, both their default one and the<br>
mainline-public variety.<br>
<br>
file /bin/ls on the squeeze binary shows:<br>
/bin/ls: ELF 32-bit LSB executable, ARM, version 1 (SYSV), dynamically linked (uses shared libs), for GNU/Linux 2.6.18, stripped<br>
<br>
not sure if that's enough to tell you the architecture version.<br>
<br>
J.<br>
<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
On Wed, Mar 27, 2013 at 12:48 AM, Jochen De Smet <<a href="mailto:jochen.arm@leahnim.org" target="_blank">jochen.arm@leahnim.org</a>> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
I'm trying to get F18 running on the globalscale mirabox.<br>
<br>
It comes preloaded with Debian Squeeze. As a first step I've tried<br>
downloading the generic<br>
rootfs from the <a href="https://fedoraproject.org/wiki/Architectures/ARM/F18/Remixes" target="_blank">https://fedoraproject.org/<u></u>wiki/Architectures/ARM/F18/<u></u>Remixes</a><br>
page; I've<br>
tried both the arm and armhfp versions, and even tried an armv5 kirkwood<br>
rootfs.<br>
<br>
All of them behave the same. I unpack the rootfs into /mnt/f18, and then try<br>
to chroot into<br>
it. The first two or three times I try it, it comes back with either<br>
"Illegal instruction" or<br>
"Segmentation fault", but after a few times I successfully get into the<br>
chroot. Then for pretty<br>
much every command inside it's the same thing. First few times it runs it<br>
fails with one of<br>
the two errors above, then it starts working and appears to keep working for<br>
an indeterminate<br>
amount of time.<br>
<br>
I've tried to start rebuilding rpms from source in the chroot but things<br>
never work long enough<br>
to get anything built.<br>
<br>
I've also (and this part is probably off-topic) tried building rpms from the<br>
debian environment,<br>
and that's failing because gcc gives an error when explicitly compiling for<br>
armv7:<br>
<br>
$ gcc -c ui.c -march=armv7<br>
ui.c:1: error: target CPU does not support ARM mode<br>
<br>
Additionally, I've tried building gcc 4.8.0 from source, and that errors out<br>
with:<br>
<br>
../.././gcc/config/arm/<a href="http://neon.md" target="_blank">neon.md</a><u></u>: In function 'const char*<br>
output_1551(rtx_def**, rtx)':<br>
../.././gcc/config/arm/neon.<u></u>md:3953:1: internal compiler error: Illegal<br>
instruction<br>
[(set_attr "neon_type" "neon_shift_2")]<br>
^<br>
<br>
../.././gcc/config/arm/neon.<u></u>md:3953:1: internal compiler error: Segmentation<br>
fault<br>
<br>
<br>
cpuinfo below:<br>
<br>
# cat /proc/cpuinfo<br>
Processor : Marvell PJ4Bv7 Processor?? rev 1 (v7l)<br>
BogoMIPS : 1199.30<br>
Features : swp half thumb fastmult vfp edsp vfpv3 vfpv3d16<br>
CPU implementer : 0x56<br>
CPU architecture: 7<br>
CPU variant : 0x1<br>
CPU part : 0x581<br>
CPU revision : 1<br>
<br>
Hardware : Marvell Armada-370<br>
Revision : 0000<br>
Serial : 0000000000000000<br>
<br>
<br>
Looking for any help on how to debug or how to proceed.<br>
<br>
J.<br>
<br>
<br>
<br>
<br>
______________________________<u></u>_________________<br>
arm mailing list<br>
<a href="mailto:arm@lists.fedoraproject.org" target="_blank">arm@lists.fedoraproject.org</a><br>
<a href="https://admin.fedoraproject.org/mailman/listinfo/arm" target="_blank">https://admin.fedoraproject.<u></u>org/mailman/listinfo/arm</a><br>
</blockquote></blockquote>
<br>
______________________________<u></u>_________________<br>
arm mailing list<br>
<a href="mailto:arm@lists.fedoraproject.org" target="_blank">arm@lists.fedoraproject.org</a><br>
<a href="https://admin.fedoraproject.org/mailman/listinfo/arm" target="_blank">https://admin.fedoraproject.<u></u>org/mailman/listinfo/arm</a><br>
</blockquote>
<br>
______________________________<u></u>_________________<br>
arm mailing list<br>
<a href="mailto:arm@lists.fedoraproject.org" target="_blank">arm@lists.fedoraproject.org</a><br>
<a href="https://admin.fedoraproject.org/mailman/listinfo/arm" target="_blank">https://admin.fedoraproject.<u></u>org/mailman/listinfo/arm</a></div></div></blockquote></div><br><br clear="all"><div><br></div>-- <br><br>-Jon
</div>