"failed to exec /sbin/modprobe -s -k binfmt-4c46, errno=8" booting PPC ltsp clients

[Brad Smith]

Hello all,

I'm not sure if this is a kernel issue or not, but I think it is. I'm
also not sure if it's appropriate for this mailing list either way,
bit I've asked on four other lists so far to no avail, so if someone
here could help enlighten me I'd really appreciate it.

I'm doing some volunteer work for a local school that has a bunch of old
power mac G3/266 machines. I'm trying to breathe some new life into
these systems by setting them up as k12ltsp clients
(http://k12ltsp.org/contents.html). There is a howto
(http://www.ltsp.org/contrib/ltsp-ppc/doc/t1.htm) on using "nubus"
powermacs in this way, but these old G3s are not nubus systems and the
mach kernel included with the HOWTO does not boot on them. I have
installed Yellow Dog 2.3 on one of the G3s and compiled a custom
kernel (2.4.19) with root_nfs support. I would have expected that if
the kernel from the HOWTO didn't run on my machine, then the ramdisk
that is also included would be likewise incompatible, but this does
not seem to be the case. Using my
kernel and the initrd from the howto, the system boots, mounts
/opt/ltsp/ppc from the ltsp
server and then does a pivot_root. After the pivot_root, however,
things go downhill. I get an endless loop of:

failed to exec /sbin/modprobe -s  -k binfmt-4c46, errno=8

At this point I'm a bit out of my element, not being a kernel person
(or a Mac person, for that matter).
But from what I've read this implies that the kernel does not have
support for the requisite type of binary. However, if I boot that same
kernel with a local root, I can mount server:/opt/ltsp/ppc and run the
executables therein perfectly. I can do the same with the contents of
the ramdisk mounted as a loopback device.

So now, frankly, I'm just confused. =;) If anyone has any advice as to how
I might fix this problem, I would greatly, greatly appreciate it.

Thanks!
--Brad
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/