Hi David,
david wrote:
> I managed to get the kernel compile to work and generate a linuximage file,
> wrote that to the SD card along with u-boot, popped the SD card in and
> booted things. All appears to go well until after the "loading modules"
> line. Then I get the following error:
>
> starting pid 458, tty '/dev/console': '/sbin/getty -L 115200 ttySAC0 vt100'
> process '/sbin/getty -L 115200 ttySAC0 vt100' (pid 458) exited. Scheduling
> for restart.
Longer time ago someone made a patch which renames the serial TTY device node
names to the corresponding device driver name. Stupid idea, but happened.
Enable the telnetd service in your BSP configuration to be able to login via
telnet. Then take a look into the dev/ directory, which name your 2.6.38
kernel really uses for the serial lines. This name you should use in the
"ptxdist platformconfig":
console options --->
(ttySAC0) console name <--- insert this name here
Then a "ptxdist clean root; ptxdist images" and your root filesystem should be
again in sync with your kernel.
A better patch would be to fix this ugly name in the serial line driver for
the S3C6410 CPU.
> This error will repeat over and over, just spawning new pid numbers then
> exiting.
Another idea could be: the 2.6.38 kernel is very old. Many things have
happened since this kernel release how the Linux kernel interacts
with 'udev'. Maybe you must switch to an older revision of 'udev' to make it
work with the 2.6.38 kernel. In older kernels 'udev' is responsible to create
all the required device nodes in the dev/ directory. In recent kernels, the
kernel does it by its own. So, 'udev' must match the kernel revision.
Send me your kernel patch to my account and I will take a look.
Regards,
Juergen
--
Pengutronix e.K. | Juergen Beisert |
Linux Solutions for Science and Industry | http://www.pengutronix.de/ |
