[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

console=ttyS* affects booting ...



Hello,

I have the following problems with kernel recently ported for IDT334 big endian. for ramdisk image i am using big endian debian( namely root.bin) initrd.

1> my kernel port for mips IDT334 board boots fine till it tries to
open /dev/console..there it simply hangs....no message

2>i am downloading kernel image through serial link (kermit on /dev/ttyS0) with bps 1152008n . I am mentioning kernel command line like root=/dev/ram console=ttyS0,1152008 init=/bin/sh.

now after console_init() in init/main.c i get only junk characters in my kermit screen.. if i Do not mention console=ttyS0,* it goes fine till opening of /dev/console..

if i specify console=ttyS1 in my kernel command line , booting get considerably slow..

i don't understand why specifying console=ttyS0,115200 results in junk
characters in kermit screen..?

what is wrong going here?

3> just to mention in my .config file
CONFIG_DEVFS_FS
CONFIG_DEVFS_MOUNT options are set..

4>if i try to open /dev/ttyS0 or /dev/ttyS1 in main.c it says file doesn't exist (errno 2) and goes further , there if i try to execve /bin/sh ( just for testing purpose)
i get o/p like..and then it hangs.
Got cpu at 2aac2880.
Got cpu at 2aac2884.
Got cpu at 2aac2888.
Got cpu at 2aac288c.
Got cpu at 2aac2890.
Got cpu at 2aac2894.
Got cpu at 2aac2898.
Got cpu at 2aac289c.
Got cpu at 2aac28a0.
Got cpu at 2aac28a4.
Got cpu at 2aac28a8.
Got cpu at 2aac28dc.
Got cpu at 2aac287c.
Got cpu at 2aac2880.
Got cpu at 2aac2884.
Got cpu at 2aac2888.
Got cpu at 2aac288c.


but if i do "mount -o loop ramdisk /mnt" and check for ttyS* i can see these files.

if i comment CONFIG_DEVFS_FS and CONFIG_DEVFS_MOUNT options in .config files and try opening
/dev/ttyS0 or /dev/ttyS1 it simply hangs.

I need a hint to go forward.

Best Regards,
Ashish



Reply to: