* Michael Grig <mg...@ho...> on Fri, Nov 30, 2001:
> Hi,
>=20
> Thanks for your quick response to my last message. Indeed upgrading to
> 3.0.2 with the lastest patch solved my problem.
> On a related note, why are you guys using the 3.0 series anyway?
> Wouldn't it be better to stick with something stable, like 2.95.3,
> instead of having to continuously track a moving target?
>=20
The SH backend in GCC 2.95.x isn't stable enough. Check the linux-sh and
linuxsh-dev mailing list archives for more info.
> Anyway, I decided to give the debian dc distro a try. Unfortunatly, as
> I still lack a DC keyboard, I have to log in from the serial terminal.
> (which should be possible according to the distro README).
>=20
> First I tried connecting (using minicom) to an already running system,
> but as that did not work, I devised a new strategy: I connect to the
> bootloader during the boot, interupt it, and issue:
> mount
> load -v /boot/vmlinux
> load -v -r -b 0x8c400000 /boot/initrd.gz
> exec -c "mem=3D16M init=3D/busybox console=3DttySC1,115200 /etc/profile"
>=20
> and it happily redirects all boot messages to the serial console,
> however when it gets to the login, it still issues it on the tty0
> and not on the serial console!!
>=20
> What am I missing here?
>=20
Hit return in minicom and you should see a login prompt. This will work
even if the system has already booted. You can see how this works in
/etc/inittab.
M. R.
|
