not getting command prompt at the console

not getting command prompt at the console

[Rajat Jain]

Hi All,

I just finished porting linux kernel 2.6.15 to a MIPS based board. The
board now boots up beautifully ... and here is the console log:


========================================
<snip>
......
VFS: Disk quotas dquot_6.5.1
Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
Initializing Cryptographic API
io scheduler noop registered
io scheduler anticipatory registered
io scheduler deadline registered
io scheduler cfq registered
rtc: SRM (post-2000) epoch (2000) detected
Real Time Clock Driver v1.12
Serial: 8250/16550 driver $Revision: 1.90 $ 1 ports, IRQ sharing disabled
serial8250: ttyS0 at I/O 0x3f8 (irq = 4) is a ST16654
RAMDISK driver initialized: 16 RAM disks of 4096K size 1024 blocksize
Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
ide: Assuming 50MHz system bus speed for PIO modes; override with idebus=xx
mice: PS/2 mouse device common for all mice
NET: Registered protocol family 2
IP route cache hash table entries: 512 (order: -1, 2048 bytes)
TCP established hash table entries: 2048 (order: 1, 8192 bytes)
TCP bind hash table entries: 2048 (order: 1, 8192 bytes)
TCP: Hash tables configured (established 2048 bind 2048)
TCP reno registered
TCP bic registered
Diplomat-IP FE device reset...
Diplomat-IP FE init ok, Rx buffer=0x8038dba8, Tx buffer=0x803adba8.
Warning: FE driver bd table wrong,old bd_id_r=0  new bd_id_r=15
IP-Config: Guessing netmask 255.255.255.0
IP-Config: Complete:
      device=eth0, addr=192.168.1.75, mask=255.255.255.0, gw=255.255.255.255,
     host=192.168.1.75, domain=, nis-domain=(none),
     bootserver=255.255.255.255, rootserver=192.168.1.76, rootpath=
Looking up port of RPC 100003/2 on 192.168.1.76
Looking up port of RPC 100005/1 on 192.168.1.76
VFS: Mounted root (nfs filesystem).
Freeing prom memory: 0kb freed
Freeing unused kernel memory: 144k freed
Algorithmics/MIPS FPU Emulator v1.5
===========================================

Next, I expected to see a command prompt which never comes. At this
point if I debug, I find the processor executing the idle process.

I am successfully hable to telnet to the board and fire whatever
commands I want though. How do I bring the prompt to the serial
console?

My root FS seems OK since the same root FS is working for the same
board for an ancient kernel (2.4.20)

Any ideas, anyone?

Thanks,

Rajat

not getting command prompt at the console

[Rajat Jain]

Hi All,

I just finished porting linux kernel 2.6.15 to a MIPS based board. The
board now boots up beautifully ... and here is the console log:


========================================
<snip>
......
VFS: Disk quotas dquot_6.5.1
Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
Initializing Cryptographic API
io scheduler noop registered
io scheduler anticipatory registered
io scheduler deadline registered
io scheduler cfq registered
rtc: SRM (post-2000) epoch (2000) detected
Real Time Clock Driver v1.12
Serial: 8250/16550 driver $Revision: 1.90 $ 1 ports, IRQ sharing disabled
serial8250: ttyS0 at I/O 0x3f8 (irq = 4) is a ST16654
RAMDISK driver initialized: 16 RAM disks of 4096K size 1024 blocksize
Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
ide: Assuming 50MHz system bus speed for PIO modes; override with idebus=xx
mice: PS/2 mouse device common for all mice
NET: Registered protocol family 2
IP route cache hash table entries: 512 (order: -1, 2048 bytes)
TCP established hash table entries: 2048 (order: 1, 8192 bytes)
TCP bind hash table entries: 2048 (order: 1, 8192 bytes)
TCP: Hash tables configured (established 2048 bind 2048)
TCP reno registered
TCP bic registered
Diplomat-IP FE device reset...
Diplomat-IP FE init ok, Rx buffer=0x8038dba8, Tx buffer=0x803adba8.
Warning: FE driver bd table wrong,old bd_id_r=0  new bd_id_r=15
IP-Config: Guessing netmask 255.255.255.0
IP-Config: Complete:
      device=eth0, addr=192.168.1.75, mask=255.255.255.0, gw=255.255.255.255,
     host=192.168.1.75, domain=, nis-domain=(none),
     bootserver=255.255.255.255, rootserver=192.168.1.76, rootpath=
Looking up port of RPC 100003/2 on 192.168.1.76
Looking up port of RPC 100005/1 on 192.168.1.76
VFS: Mounted root (nfs filesystem).
Freeing prom memory: 0kb freed
Freeing unused kernel memory: 144k freed
Algorithmics/MIPS FPU Emulator v1.5
===========================================

Next, I expected to see a command prompt which never comes. At this
point if I debug, I find the processor executing the idle process.

I am successfully hable to telnet to the board and fire whatever
commands I want though. How do I bring the prompt to the serial
console?

My root FS seems OK since the same root FS is working for the same
board for an ancient kernel (2.4.20)

Any ideas, anyone?

Thanks,

Rajat
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

Re: not getting command prompt at the console

[Erik Mouw]

[-- Attachment #1: Type: text/plain, Size: 961 bytes --]

On Thu, Feb 22, 2007 at 03:19:10PM +0530, Rajat Jain wrote:
> Hi All,
> 
> I just finished porting linux kernel 2.6.15 to a MIPS based board. The
> board now boots up beautifully ... and here is the console log:

[...]

> Next, I expected to see a command prompt which never comes. At this
> point if I debug, I find the processor executing the idle process.
> 
> I am successfully hable to telnet to the board and fire whatever
> commands I want though. How do I bring the prompt to the serial
> console?

Run a getty on the serial device (I suppose you're using a serial
port).

> My root FS seems OK since the same root FS is working for the same
> board for an ancient kernel (2.4.20)

Could be that the serial driver changed or that you forgot to compile a
driver for the serial device.


Erik

-- 
They're all fools. Don't worry. Darwin may be slow, but he'll
eventually get them. -- Matthew Lammers in alt.sysadmin.recovery

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

Re: not getting command prompt at the console

[Raseel Bhagat]

Hi Rajat,

On 2/22/07, Erik Mouw <mouw@nl.linux.org> wrote:
> On Thu, Feb 22, 2007 at 03:19:10PM +0530, Rajat Jain wrote:
> > Next, I expected to see a command prompt which never comes. At this
> > point if I debug, I find the processor executing the idle process.
> >
> > I am successfully hable to telnet to the board and fire whatever
> > commands I want though. How do I bring the prompt to the serial
> > console?
>
> Run a getty on the serial device (I suppose you're using a serial
> port).
> Could be that the serial driver changed or that you forgot to compile a
> driver for the serial device.
>

Also , assuming you are using a serial console , check your entries in
the inittab file .
It should look  something like :
ttyS0::respawn:/sbin/getty ttyS0 115200 linux

Re: not getting command prompt at the console

[Raseel Bhagat]

Hi Rajat,

On 2/22/07, Erik Mouw <mouw@nl.linux.org> wrote:
> On Thu, Feb 22, 2007 at 03:19:10PM +0530, Rajat Jain wrote:
> > Next, I expected to see a command prompt which never comes. At this
> > point if I debug, I find the processor executing the idle process.
> >
> > I am successfully hable to telnet to the board and fire whatever
> > commands I want though. How do I bring the prompt to the serial
> > console?
>
> Run a getty on the serial device (I suppose you're using a serial
> port).
> Could be that the serial driver changed or that you forgot to compile a
> driver for the serial device.
>

Also , assuming you are using a serial console , check your entries in
the inittab file .
It should look  something like :
ttyS0::respawn:/sbin/getty ttyS0 115200 linux
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

Re: not getting command prompt at the console

[Erik Mouw]

[-- Attachment #1: Type: text/plain, Size: 802 bytes --]

On Thu, Feb 22, 2007 at 04:20:08PM +0530, Raseel Bhagat wrote:
> On 2/22/07, Erik Mouw <mouw@nl.linux.org> wrote:
> >Run a getty on the serial device (I suppose you're using a serial
> >port).
> >Could be that the serial driver changed or that you forgot to compile a
> >driver for the serial device.
> >
> 
> Also , assuming you are using a serial console , check your entries in
> the inittab file .
> It should look  something like :
> ttyS0::respawn:/sbin/getty ttyS0 115200 linux

If the device is indeed called "ttyS0". Remember it's a MIPS board, not
a peecee. For example, on StrongARM SA11x0 you need to use ttySA0
instead of ttyS0.

Erik

-- 
They're all fools. Don't worry. Darwin may be slow, but he'll
eventually get them. -- Matthew Lammers in alt.sysadmin.recovery

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

RE: not getting command prompt at the console

[Ajay Singh (ajaysi)]

> My root FS seems OK since the same root FS is working for the 
> same board for an ancient kernel (2.4.20)
> 
See if this helps:
http://mail.nl.linux.org/kernelnewbies/2005-03/msg00030.html

> Any ideas, anyone?
> 
> Thanks,
> 
> Rajat
> 
> --
> To unsubscribe from this list: send an email with 
> "unsubscribe kernelnewbies" to ecartis@nl.linux.org Please 
> read the FAQ at http://kernelnewbies.org/FAQ
> 

--
To unsubscribe from this list: send an email with
"unsubscribe kernelnewbies" to ecartis@nl.linux.org
Please read the FAQ at http://kernelnewbies.org/FAQ

Re: not getting command prompt at the console

[Raseel Bhagat]

Hi,

On 2/22/07, Erik Mouw <mouw@nl.linux.org> wrote:

> > Also , assuming you are using a serial console , check your entries in
> > the inittab file .
> > It should look  something like :
> > ttyS0::respawn:/sbin/getty ttyS0 115200 linux
>
> If the device is indeed called "ttyS0". Remember it's a MIPS board, not
> a peecee. For example, on StrongARM SA11x0 you need to use ttySA0
> instead of ttyS0.
>

Correct.  Thanks for the correction Erik.
My point being, you sould have such an entry in your inittab when
working on a serial console.
I have faced this problem before and spent hours trying to figure out
what was only a silly-mistake.

Re: not getting command prompt at the console

[Raseel Bhagat]

Hi,

On 2/22/07, Erik Mouw <mouw@nl.linux.org> wrote:

> > Also , assuming you are using a serial console , check your entries in
> > the inittab file .
> > It should look  something like :
> > ttyS0::respawn:/sbin/getty ttyS0 115200 linux
>
> If the device is indeed called "ttyS0". Remember it's a MIPS board, not
> a peecee. For example, on StrongARM SA11x0 you need to use ttySA0
> instead of ttyS0.
>

Correct.  Thanks for the correction Erik.
My point being, you sould have such an entry in your inittab when
working on a serial console.
I have faced this problem before and spent hours trying to figure out
what was only a silly-mistake.

--
To unsubscribe from this list: send an email with
"unsubscribe kernelnewbies" to ecartis@nl.linux.org
Please read the FAQ at http://kernelnewbies.org/FAQ