Unable to open an initial console

Unable to open an initial console

[Addison Baldwin]

I was sucessful to port U-Boot to our 8272 board. Now I'm experiencing
a problem:

Our Kernel hangs with the message that says it was trasnferring
control to linux. A post morten analyzes indicated that it stopped at
"Unable to open an initial console" in the memory sapce where console
output should be out (in the sdram, like I had found somewhere in this
list, how to do it).

I have checked the bootargs values, it is ok:
bootargs root=3D/dev/ram console=3DttyS0,115200

 We also checked our "/dev" and there was a link to console, pointing
ttyS0. Also, ttyS0 was there too.

Does anyone have any idea how to fix it?

Re: Unable to open an initial console

[Vitaly Bordug]

Addison Baldwin wrote:
> I was sucessful to port U-Boot to our 8272 board. Now I'm experiencing
> a problem:
> 
> Our Kernel hangs with the message that says it was trasnferring
> control to linux. A post morten analyzes indicated that it stopped at
> "Unable to open an initial console" in the memory sapce where console
> output should be out (in the sdram, like I had found somewhere in this
> list, how to do it).
> 
> I have checked the bootargs values, it is ok:
> bootargs root=/dev/ram console=ttyS0,115200
> 
Only for 2.4, 2.6 is different for this.
console=ttyCPM0 should be there, and that device does have different major/minor comparing to ttyS0.
Note that the UART has to be enabled explicitly in kernel config, for more info, search this list archives.

>  We also checked our "/dev" and there was a link to console, pointing
> ttyS0. Also, ttyS0 was there too.
> 
> Does anyone have any idea how to fix it?
> _______________________________________________
> Linuxppc-embedded mailing list
> Linuxppc-embedded@ozlabs.org
> https://ozlabs.org/mailman/listinfo/linuxppc-embedded
> 
> 


-- 
Sincerely, 
Vitaly

Re: Unable to open an initial console

[Addison Baldwin]

Thank you!

I had to create the /dev/ttyCPM0 and had to point /dev/console to it.
Now the console is working fine!

Best Regards,
Addison Baldwin

On 12/16/05, Vitaly Bordug <vbordug@ru.mvista.com> wrote:
> Addison Baldwin wrote:
> > I was sucessful to port U-Boot to our 8272 board. Now I'm experiencing
> > a problem:
> >
> > Our Kernel hangs with the message that says it was trasnferring
> > control to linux. A post morten analyzes indicated that it stopped at
> > "Unable to open an initial console" in the memory sapce where console
> > output should be out (in the sdram, like I had found somewhere in this
> > list, how to do it).
> >
> > I have checked the bootargs values, it is ok:
> > bootargs root=3D/dev/ram console=3DttyS0,115200
> >
> Only for 2.4, 2.6 is different for this.
> console=3DttyCPM0 should be there, and that device does have different ma=
jor/minor comparing to ttyS0.
> Note that the UART has to be enabled explicitly in kernel config, for mor=
e info, search this list archives.
>
> >  We also checked our "/dev" and there was a link to console, pointing
> > ttyS0. Also, ttyS0 was there too.
> >
> > Does anyone have any idea how to fix it?
> > _______________________________________________
> > Linuxppc-embedded mailing list
> > Linuxppc-embedded@ozlabs.org
> > https://ozlabs.org/mailman/listinfo/linuxppc-embedded
> >
> >
>
>
> --
> Sincerely,
> Vitaly
>

Re: Unable to open an initial console

[Nigel Cunningham]

Hi.

On Sat, 2005-12-17 at 06:01, Addison Baldwin wrote:
> I was sucessful to port U-Boot to our 8272 board. Now I'm experiencing
> a problem:
> 
> Our Kernel hangs with the message that says it was trasnferring
> control to linux. A post morten analyzes indicated that it stopped at
> "Unable to open an initial console" in the memory sapce where console
> output should be out (in the sdram, like I had found somewhere in this
> list, how to do it).
> 
> I have checked the bootargs values, it is ok:
> bootargs root=/dev/ram console=ttyS0,115200
> 
>  We also checked our "/dev" and there was a link to console, pointing
> ttyS0. Also, ttyS0 was there too.

Are you using an initrd or initramfs? If so, the device node needs to
exist on that filesystem. This message will only occur if the kernel is
unable to open /dev/console for rw access.

Hope this helps.

Nigel