On Fri, Jan 31, 2003 at 10:53:43AM -0000, ashish anand wrote: | 1> if i mention at kernel command line console=/dev/ttyS0,* | immedialtely after console_init() in init/main.c i get junk | characters on my kermit screen no mater whatever speed i | specify.. <snip> | if i don't specify it boots , mounts ramdisk and tries to open | the | /dev/console and there it says "Warning :unable to open an initial | console" Hi Ashish! I think both problems are not related. For the first problem, I think you're missing parity/stop bit settings on the kermit. I think by default (ie. if you don't specify console speeds), it would use 9600 bps. About the "unable to open initial console" problem, probably you're using devfs, which isn't getting mounted on bootup. | 2> if i try to open /dev/ttyS0 or /dev/ttyS1 it says file doesn't | exist.. | where on my ramdisk image if i do "mount -o loop ramdisk /mnt" | i can see these files. How do you see this? Are you able to telnet to the board, and see this? | 3> should console be linked to ttyS* and appropiately inittab | getty entry should be edited.? Shouldn't be required. -- Chirag Kantharia, symonds.net/~chyrag/ -- Kernelnewbies: Help each other learn about the Linux kernel. Archive: http://mail.nl.linux.org/kernelnewbies/ FAQ: http://kernelnewbies.org/faq/
