On Sat, 5 Jun 1999, Charlie Baylis wrote:
> With 2.0.35 init reports id[1-6] respawning too fast, then stops.
Ah! I've just fallen foul of this this afternoon, I'm sorry. Fix it by
editing the file /etc/inittab; find the line
id:3:initdefault:
and add this line after it:
fp::sysinit:/sbin/insmod -f /lib/modules/misc/fpem.o
This reinstates loading of the Acorn FP emulator early enough in the
boot sequence for people that don't have NWFPE compiled into their
kernels.
> What I did was:
> rpm -i --force --ignorearch --nodeps `find . -name '*.rpm'`
> which in retrospect seems like a bad idea.
Oo-ee... yowch. :)
I think a slightly more cautious one-at-a-time in-a-sensible-order
approach would be good here; although admittedly I've never actually
tried upgrading an old system with my old RPMs, so I don't actually
know what works and what doesn't -- I need to find another RPC...
> I first noticed something was wrong when I logged out on a VT and init
> complained about mingetty respawning too fast, and IIRC /dev/tty1: invalid
> operation appeared in the logs. So I thought, fine, I'll d/l the 2.2 source,
> and see if that fixes it. I then discovered that the new insmod won't touch
> my kernel modules so the system is broken either way. :(
Invalid operation? Try:
% cd /dev
% MAKEDEV generic
> I can boot 2.0 with parameter init=/bin/ash, so I'll have a go at compiling
> a 2.2 kernel with suitable configuration.
No no, just try the fix above first. It should get your system
operational.
--
Chris <[EMAIL PROTECTED]> ( http://www.fluff.org/chris )
unsubscribe: body of `unsubscribe linux-arm' to [EMAIL PROTECTED]
