From: Daniel Ann <hidden> Date: 2005-07-30 01:12:49
Hi folks,
Just wondering if anyone could lend a hand with this problem I have
with serial console. I'm trying to boot up my board (very similar to
sandpoint using MPC8245) with kernel 2.6.12.3, and most of it is
working but console will display up to,
[snip]
RAMDISK: Compressed image found at block 0
VFS: Mounted root (ext2 filesystem) readonly.
Freeing unused kernel memory: 112k init =
=20
I've done series of printk in sys_execve() to see if /sbin/init is
working, and found out it went thru the whole rcS file okay. Mind you,
printk is successfully displaying the output on the console while I'm
still not getting anything from the user processes.
Having all the kernel boot up log on console means that I've done some
part right. But why am I not getting anything from the user processes
on the console screen ?
Is there anything I need to do on the kernel config ?
--=20
Daniel
On Sat, 2005-07-30 at 10:06 +0900, Daniel Ann wrote:
Hi folks,
Just wondering if anyone could lend a hand with this problem I have
with serial console. I'm trying to boot up my board (very similar to
sandpoint using MPC8245) with kernel 2.6.12.3, and most of it is
working but console will display up to,
[snip]
RAMDISK: Compressed image found at block 0
VFS: Mounted root (ext2 filesystem) readonly.
Freeing unused kernel memory: 112k init
I've done series of printk in sys_execve() to see if /sbin/init is
working, and found out it went thru the whole rcS file okay. Mind you,
printk is successfully displaying the output on the console while I'm
still not getting anything from the user processes.
Having all the kernel boot up log on console means that I've done some
part right. But why am I not getting anything from the user processes
on the console screen ?
Is there anything I need to do on the kernel config ?
Do you have a /dev/console device node in your initrd? If not, that is
one of the reasons you could be seeing that problem. Make
sure /dev/null is there too.
josh
Hi Daniel,
On Friday 29 July 2005 22:06, Daniel Ann wrote:
Hi folks,
Just wondering if anyone could lend a hand with this problem I have
with serial console. I'm trying to boot up my board (very similar to
sandpoint using MPC8245) with kernel 2.6.12.3, and most of it is
working but console will display up to,
[snip]
RAMDISK: Compressed image found at block 0
VFS: Mounted root (ext2 filesystem) readonly.
Freeing unused kernel memory: 112k init
I've done series of printk in sys_execve() to see if /sbin/init is
working, and found out it went thru the whole rcS file okay. Mind you,
printk is successfully displaying the output on the console while I'm
still not getting anything from the user processes.
Having all the kernel boot up log on console means that I've done some
part right. But why am I not getting anything from the user processes
on the console screen ?
Please verify that you have a /dev/console in your rootfs, and that it's =
being=20
correctly acessed by the init process.
HTH,
--=20
Ricardo Scop.
\|/
___ -*-
(@ @)/|\
/ V \| R SCOP Consult.
/( )\ Linux-based communications
--^^---^^+------------------------------
rscop@matrix.com.br
+55 51 999-36-777
Porto Alegre, RS - BRazil
From: Daniel Ann <hidden> Date: 2005-07-30 01:34:24
Looks like I have /dev/console
0 crw------- 1 root root 5, 1 Sep 26 2002 console
0 crw-rw-rw- 1 root root 4, 64 Jun 17 2004 ttyS0
I havent yet figured out how I should go about seeing if init is
correctly accessing it tho. Let me take a look at busybox init part.
BTW, any more reasons why this problem might exist ?
On 7/30/05, Ricardo Scop [off-list ref] wrote:
Hi Daniel,
=20
On Friday 29 July 2005 22:06, Daniel Ann wrote:
quoted
Hi folks,
Just wondering if anyone could lend a hand with this problem I have
with serial console. I'm trying to boot up my board (very similar to
sandpoint using MPC8245) with kernel 2.6.12.3, and most of it is
working but console will display up to,
[snip]
RAMDISK: Compressed image found at block 0
VFS: Mounted root (ext2 filesystem) readonly.
Freeing unused kernel memory: 112k init
I've done series of printk in sys_execve() to see if /sbin/init is
working, and found out it went thru the whole rcS file okay. Mind you,
printk is successfully displaying the output on the console while I'm
still not getting anything from the user processes.
Having all the kernel boot up log on console means that I've done some
part right. But why am I not getting anything from the user processes
on the console screen ?
Please verify that you have a /dev/console in your rootfs, and that it's =
being
correctly acessed by the init process.
=20
HTH,
=20
--
Ricardo Scop.
=20
\|/
___ -*-
(@ @)/|\
/ V \| R SCOP Consult.
/( )\ Linux-based communications
--^^---^^+------------------------------
rscop@matrix.com.br
+55 51 999-36-777
Porto Alegre, RS - BRazil
=20
=20
From: Daniel Ann <hidden> Date: 2005-07-30 01:36:45
I too have /dev/null
0 crw-rw-rw- 1 root root 1, 3 Aug 31 2001 null
However, Im not using initrd. null, and console devices are in my RAMDISK t=
ho.
On 7/30/05, Josh Boyer [off-list ref] wrote:
On Sat, 2005-07-30 at 10:06 +0900, Daniel Ann wrote:
quoted
Hi folks,
Just wondering if anyone could lend a hand with this problem I have
with serial console. I'm trying to boot up my board (very similar to
sandpoint using MPC8245) with kernel 2.6.12.3, and most of it is
working but console will display up to,
[snip]
RAMDISK: Compressed image found at block 0
VFS: Mounted root (ext2 filesystem) readonly.
Freeing unused kernel memory: 112k init
I've done series of printk in sys_execve() to see if /sbin/init is
working, and found out it went thru the whole rcS file okay. Mind you,
printk is successfully displaying the output on the console while I'm
still not getting anything from the user processes.
Having all the kernel boot up log on console means that I've done some
part right. But why am I not getting anything from the user processes
on the console screen ?
Is there anything I need to do on the kernel config ?
=20
Do you have a /dev/console device node in your initrd? If not, that is
one of the reasons you could be seeing that problem. Make
sure /dev/null is there too.
=20
josh
=20
=20
From: Daniel Ann <hidden> Date: 2005-07-30 05:46:28
I've got a feeling that this has alot to do with IRQ.
Would I be correct to assume printk doesnt require interrupt to work
but printf does ?
After doing some testing, I've found my network interface ping-able
when I got printf working in 2.4.31. But if I alter the openpic source
to not initialize the interrupt, it also stop displaying at the same
point and network interface isnt pingable.
I guess my next problem would be then, why isnt my openpic working. :(
I've done exactly the same as what I did with 2.4.31 and that works.
Hmmm. Something must have changed in 2.6.12.3.
I dont think this is has anything to do with serial console, so I'm
gonna end the thread here.
Thanks.
On 7/30/05, Daniel Ann [off-list ref] wrote:
I too have /dev/null
0 crw-rw-rw- 1 root root 1, 3 Aug 31 2001 null
=20
However, Im not using initrd. null, and console devices are in my RAMDISK=
tho.
=20
On 7/30/05, Josh Boyer [off-list ref] wrote:
quoted
On Sat, 2005-07-30 at 10:06 +0900, Daniel Ann wrote:
quoted
Hi folks,
Just wondering if anyone could lend a hand with this problem I have
with serial console. I'm trying to boot up my board (very similar to
sandpoint using MPC8245) with kernel 2.6.12.3, and most of it is
working but console will display up to,
[snip]
RAMDISK: Compressed image found at block 0
VFS: Mounted root (ext2 filesystem) readonly.
Freeing unused kernel memory: 112k init
I've done series of printk in sys_execve() to see if /sbin/init is
working, and found out it went thru the whole rcS file okay. Mind you=
,
quoted
quoted
printk is successfully displaying the output on the console while I'm
still not getting anything from the user processes.
Having all the kernel boot up log on console means that I've done som=
e
quoted
quoted
part right. But why am I not getting anything from the user processes
on the console screen ?
Is there anything I need to do on the kernel config ?
Do you have a /dev/console device node in your initrd? If not, that is
one of the reasons you could be seeing that problem. Make
sure /dev/null is there too.
josh
From: Anton Wöllert <hidden> Date: 2005-07-30 10:37:56
Daniel Ann wrote:
Hi folks,
Having all the kernel boot up log on console means that I've done some
part right. But why am I not getting anything from the user processes
on the console screen ?
Is there anything I need to do on the kernel config ?
Hi, we've had the same problem some time ago on a tqm850l (mpc850). Our
problem was, that we had registered two serial consoles in the kernel
config or something like that. we had to disable all serial-driver stuff
and enable just the platform-specific serial-console driver. we tracked
this down with inserting a printk(buf) into the tty_write fs-op of the
serial-port driver in drivers/char/tty_io.c. the ttyS0 was used but has
taken another serial-driver than the platform specific.
may this help you :)
anton
From: Daniel Ann <hidden> Date: 2005-08-01 01:27:01
Thanks for your input Anton.
I'm not all that certain about sandpoint platform has its own serial
driver so I've worked with 8250.c. Anyway, I've got it working now. It
was problem with interrupt. As soon as I changed interrupt from EGDE
to LEVEL it began working. Altho I'm faced with yet another problem
with openpic but I'm digging thru it at the moment.
BTW, I have no idea why EDGE didnt work and LEVEL does.
Cheers,
Daniel
On 7/30/05, Anton W=F6llert [off-list ref] wrote:
Daniel Ann wrote:
quoted
Hi folks,
Having all the kernel boot up log on console means that I've done some
part right. But why am I not getting anything from the user processes
on the console screen ?
Is there anything I need to do on the kernel config ?
=20
Hi, we've had the same problem some time ago on a tqm850l (mpc850). Our
problem was, that we had registered two serial consoles in the kernel
config or something like that. we had to disable all serial-driver stuff
and enable just the platform-specific serial-console driver. we tracked
this down with inserting a printk(buf) into the tty_write fs-op of the
serial-port driver in drivers/char/tty_io.c. the ttyS0 was used but has
taken another serial-driver than the platform specific.
=20
may this help you :)
=20
=20
anton
=20
Dear Daniel,
I also meet this problem on MPC8245 with linux-2.6.12.3, and I found it =
uses
LEVEL for interrupt in sandpoint.c. Do you have any idea for it?
Thanks,
Johnson Cheng
-----Original Message-----
From: linuxppc-embedded-bounces@ozlabs.org
[mailto:linuxppc-embedded-bounces@ozlabs.org] On Behalf Of Daniel Ann
Sent: Monday, August 01, 2005 9:27 AM
To: Anton W=F6llert
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: Serial console
Thanks for your input Anton.
I'm not all that certain about sandpoint platform has its own serial
driver so I've worked with 8250.c. Anyway, I've got it working now. It
was problem with interrupt. As soon as I changed interrupt from EGDE
to LEVEL it began working. Altho I'm faced with yet another problem
with openpic but I'm digging thru it at the moment.
BTW, I have no idea why EDGE didnt work and LEVEL does.
Cheers,
Daniel
On 7/30/05, Anton W=F6llert [off-list ref] wrote:
Daniel Ann wrote:
quoted
Hi folks,
Having all the kernel boot up log on console means that I've done =
some
quoted
part right. But why am I not getting anything from the user =
processes
quoted
on the console screen ?
Is there anything I need to do on the kernel config ?
=20
Hi, we've had the same problem some time ago on a tqm850l (mpc850). =
Our
problem was, that we had registered two serial consoles in the kernel
config or something like that. we had to disable all serial-driver =
stuff
and enable just the platform-specific serial-console driver. we =
tracked
this down with inserting a printk(buf) into the tty_write fs-op of the
serial-port driver in drivers/char/tty_io.c. the ttyS0 was used but =
has
taken another serial-driver than the platform specific.
=20
may this help you :)
=20
=20
anton
=20
From: Kumar Gala <hidden> Date: 2005-08-02 13:39:57
On Aug 1, 2005, at 10:38 PM, JohnsonCheng wrote:
Dear Daniel,
I also meet this problem on MPC8245 with linux-2.6.12.3, and I =20
found it uses
LEVEL for interrupt in sandpoint.c. Do you have any idea for it?
All internal interrupts on the MPC8245/1 should be LEVEL interrupts.
- kumar
-----Original Message-----
From: linuxppc-embedded-bounces@ozlabs.org
[mailto:linuxppc-embedded-bounces@ozlabs.org] On Behalf Of Daniel Ann
Sent: Monday, August 01, 2005 9:27 AM
To: Anton W=F6llert
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: Serial console
Thanks for your input Anton.
I'm not all that certain about sandpoint platform has its own serial
driver so I've worked with 8250.c. Anyway, I've got it working now. It
was problem with interrupt. As soon as I changed interrupt from EGDE
to LEVEL it began working. Altho I'm faced with yet another problem
with openpic but I'm digging thru it at the moment.
BTW, I have no idea why EDGE didnt work and LEVEL does.
Cheers,
Daniel
On 7/30/05, Anton W=F6llert [off-list ref] wrote:
quoted
Daniel Ann wrote:
quoted
Hi folks,
Having all the kernel boot up log on console means that I've done =20=
quoted
quoted
some
part right. But why am I not getting anything from the user =20
processes
on the console screen ?
Is there anything I need to do on the kernel config ?
Hi, we've had the same problem some time ago on a tqm850l =20
(mpc850). Our
problem was, that we had registered two serial consoles in the kernel
config or something like that. we had to disable all serial-driver =20=
quoted
stuff
and enable just the platform-specific serial-console driver. we =20
tracked
this down with inserting a printk(buf) into the tty_write fs-op of =20=
quoted
the
serial-port driver in drivers/char/tty_io.c. the ttyS0 was used =20
but has
taken another serial-driver than the platform specific.
may this help you :)
anton
From: Daniel Ann <hidden> Date: 2005-08-03 00:16:38
Right. Guess I found it hard way :)
After using LEVEL interrupt, it all works now.
On 8/2/05, Kumar Gala [off-list ref] wrote:
=20
On Aug 1, 2005, at 10:38 PM, JohnsonCheng wrote:
=20
quoted
Dear Daniel,
I also meet this problem on MPC8245 with linux-2.6.12.3, and I
found it uses
LEVEL for interrupt in sandpoint.c. Do you have any idea for it?
=20
All internal interrupts on the MPC8245/1 should be LEVEL interrupts.
=20
- kumar
=20
quoted
-----Original Message-----
From: linuxppc-embedded-bounces@ozlabs.org
[mailto:linuxppc-embedded-bounces@ozlabs.org] On Behalf Of Daniel Ann
Sent: Monday, August 01, 2005 9:27 AM
To: Anton W=F6llert
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: Serial console
Thanks for your input Anton.
I'm not all that certain about sandpoint platform has its own serial
driver so I've worked with 8250.c. Anyway, I've got it working now. It
was problem with interrupt. As soon as I changed interrupt from EGDE
to LEVEL it began working. Altho I'm faced with yet another problem
with openpic but I'm digging thru it at the moment.
BTW, I have no idea why EDGE didnt work and LEVEL does.
Cheers,
Daniel
On 7/30/05, Anton W=F6llert [off-list ref] wrote:
quoted
Daniel Ann wrote:
quoted
Hi folks,
Having all the kernel boot up log on console means that I've done
some
part right. But why am I not getting anything from the user
processes
on the console screen ?
Is there anything I need to do on the kernel config ?
Hi, we've had the same problem some time ago on a tqm850l
(mpc850). Our
problem was, that we had registered two serial consoles in the kernel
config or something like that. we had to disable all serial-driver
stuff
and enable just the platform-specific serial-console driver. we
tracked
this down with inserting a printk(buf) into the tty_write fs-op of
the
serial-port driver in drivers/char/tty_io.c. the ttyS0 was used
but has
taken another serial-driver than the platform specific.
may this help you :)
anton