initial console

initial console

[Xavier Grave]

Hi,

I have the following message at boot :

Freeing unused kernel memory: 220k init 12k pmac 4k chrp 4k openfirmware
Warning: unable to open an initial console.
Kernel panic: No init found.  Try passing init= option to kernel.
Rebooting in 180 seconds..

if I give this argument init=/sbin/init it's the same.

Also hen I try to enable virtual terminual I have the following very early:

TCP: Hash tables configured (established 4096 bind 4096)
Starting kswapd v1.8
pc_keyb: controller jammed (0xFF).
pc_keyb: controller jammed (0xFF).
and so on...

Thanks in advance for anyhelp.

xavier
configuration: CPU 603e + Prep Board

33 (0) 1 69 15 79 59
De chacun selon ses forces, a chacun selon ses besoins


** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

Re: initial console

[Gabriel Paubert]

	Hi,

On Wed, 18 Oct 2000, Xavier Grave wrote:

> I have the following message at boot :
>
> Freeing unused kernel memory: 220k init 12k pmac 4k chrp 4k openfirmware
> Warning: unable to open an initial console.
> Kernel panic: No init found.  Try passing init= option to kernel.
> Rebooting in 180 seconds..
>
> if I give this argument init=/sbin/init it's the same.
>

CONFIG_SERIAL_CONSOLE is missing ?
console=ttyS0 in the kernel boot args ?

> Also hen I try to enable virtual terminual I have the following very early:
>
> TCP: Hash tables configured (established 4096 bind 4096)
> Starting kswapd v1.8
> pc_keyb: controller jammed (0xFF).
> pc_keyb: controller jammed (0xFF).
> and so on...


Expected with an MVME2300.


	Gabriel

P.S:  I still don't understand why my bootloader would not properly
reconfigure the PCI resources to give you access to the SCSI board.
Do you have somewhere a printout of the bootlog, it should list all the
PCI resources before and after reorganization.


** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

Re: initial console

[Xavier Grave]

On Wed, 18 Oct 2000, Gabriel Paubert wrote:
>
> CONFIG_SERIAL_CONSOLE is missing ?
grep CONFIG_SERIAL_CONSOLE .config
CONFIG_SERIAL_CONSOLE=y

> console=ttyS0
With or without the same result...

> > pc_keyb: controller jammed (0xFF).
> > pc_keyb: controller jammed (0xFF).
> > and so on...
>
>
> Expected with an MVME2300.
The error message disappeared after a few hundred of message.

> P.S:  I still don't understand why my bootloader would not properly
> reconfigure the PCI resources to give you access to the SCSI board.
> Do you have somewhere a printout of the bootlog, it should list all the
> PCI resources before and after reorganization.
Sorry, I've lost the output of the kernel I have compiled with your patch.
Can I use your patch with the latest linuxppc_2_5 from fsmlab ?
If so I'll try it one more time. But the actual kernel (from
fsmlab) recognize and configure my SCSI board.

xavier

33 (0) 1 69 15 79 59
De chacun selon ses forces, a chacun selon ses besoins


** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

Re: initial console

[Gabriel Paubert]

On Wed, 18 Oct 2000, Xavier Grave wrote:

> On Wed, 18 Oct 2000, Gabriel Paubert wrote:
> >
> > CONFIG_SERIAL_CONSOLE is missing ?
> grep CONFIG_SERIAL_CONSOLE .config
> CONFIG_SERIAL_CONSOLE=y
>
> > console=ttyS0
> With or without the same result...
>
> > > pc_keyb: controller jammed (0xFF).
> > > pc_keyb: controller jammed (0xFF).
> > > and so on...
> >
> >
> > Expected with an MVME2300.
> The error message disappeared after a few hundred of message.
>
> > P.S:  I still don't understand why my bootloader would not properly
> > reconfigure the PCI resources to give you access to the SCSI board.
> > Do you have somewhere a printout of the bootlog, it should list all the
> > PCI resources before and after reorganization.
> Sorry, I've lost the output of the kernel I have compiled with your patch.
> Can I use your patch with the latest linuxppc_2_5 from fsmlab ?
> If so I'll try it one more time. But the actual kernel (from
> fsmlab) recognize and configure my SCSI board.

No, all my patches are relative to the official kernel tree. I have
2.4.0-test9 running on an MVME2600 right now (built in NCR53C825).
It might be a sym53c8xx driver problem too, I have only used ncr53c8xx.

	Regards,
	Gabriel.


** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

Re: initial console

[Geert Uytterhoeven]

On Wed, 18 Oct 2000, Xavier Grave wrote:
> I have the following message at boot :
>
> Freeing unused kernel memory: 220k init 12k pmac 4k chrp 4k openfirmware
> Warning: unable to open an initial console.
> Kernel panic: No init found.  Try passing init= option to kernel.
> Rebooting in 180 seconds..
>
> if I give this argument init=/sbin/init it's the same.
>
> Also hen I try to enable virtual terminual I have the following very early:
>
> TCP: Hash tables configured (established 4096 bind 4096)
> Starting kswapd v1.8
> pc_keyb: controller jammed (0xFF).
> pc_keyb: controller jammed (0xFF).
> and so on...
>
> Thanks in advance for anyhelp.
>
> xavier
> configuration: CPU 603e + Prep Board

What does /dev/console look like?

Did you enable any device that can provide a console functionality, like e.g.
CONFIG_VT, CONFIG_SERIAL_CONSOLE?

Gr{oetje,eeting}s,

						Geert

--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
							    -- Linus Torvalds


** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

Re: initial console

[Xavier Grave]

First of all : thanks.
On Wed, 18 Oct 2000, Geert Uytterhoeven wrote:
> What does /dev/console look like?
Under 2.2.17 kernel (which boot...)
[root@ipnpwpc3 /dev]>ls -la /dev/console
crw-r--r--    1 root     root       5,   1 oct 19 08:24 /dev/console
is this good or not ? Do you need more information ?
If so how can I get it ?
> Did you enable any device that can provide a console functionality, like e.g.
> CONFIG_VT, CONFIG_SERIAL_CONSOLE?
[xavier@ipnpcu5 linuxppc_2_5]>grep VT .config
CONFIG_VT=y
CONFIG_VT_CONSOLE=y
[xavier@ipnpcu5 linuxppc_2_5]>grep CONFIG_SERIAL_CONSOLE .config
CONFIG_SERIAL_CONSOLE=y

33 (0) 1 69 15 79 59
De chacun selon ses forces, a chacun selon ses besoins


** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

Re: initial console

[Geert Uytterhoeven]

On Thu, 19 Oct 2000, Xavier Grave wrote:
> First of all : thanks.
> On Wed, 18 Oct 2000, Geert Uytterhoeven wrote:
> > What does /dev/console look like?
> Under 2.2.17 kernel (which boot...)
> [root@ipnpwpc3 /dev]>ls -la /dev/console
> crw-r--r--    1 root     root       5,   1 oct 19 08:24 /dev/console
> is this good or not ? Do you need more information ?

Major 5 minor 1 is correct.

Gr{oetje,eeting}s,

						Geert

--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
							    -- Linus Torvalds


** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

Re: initial console

[Chris Leishman]

On Wed, Oct 18, 2000 at 11:25:48AM +0200, Xavier Grave wrote:
>
> Hi,
>
> I have the following message at boot :
>
> Freeing unused kernel memory: 220k init 12k pmac 4k chrp 4k openfirmware
> Warning: unable to open an initial console.
> Kernel panic: No init found.  Try passing init= option to kernel.
> Rebooting in 180 seconds..
>
> if I give this argument init=/sbin/init it's the same.
>

I know it sounds dumb, but have you ensured that you've got the root partition
set correctly?  I've seen these errors before when I had a root partition
specified that didn't contain /dev or /sbin/init.

Perhaps add root=/dev/<whatever it is for you> as another arguemnt.

Chris

** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

Re: initial console

[Xavier Grave]

On Thu, 19 Oct 2000, Chris Leishman wrote:
> I know it sounds dumb, but have you ensured that you've got the root partition
> set correctly?  I've seen these errors before when I had a root partition
> specified that didn't contain /dev or /sbin/init.

/dev/sda5 on / type ext2 (rw,errors=remount-ro,errors=remount-ro)
proc on /proc type proc (rw)
devpts on /dev/pts type devpts (rw,gid=5,mode=620)
/dev/sda2 on /boot type ext2 (rw)
/dev/sda6 on /home type ext2 (rw)
/dev/sda7 on /export/data1 type ext2 (rw)
/dev/sda8 on /export/data2 type ext2 (rw)

And I give the following argument root=/dev/sda5
with the 2.4.0 kernel it fails but with a 2.2.17 kernel it works.

33 (0) 1 69 15 79 59
De chacun selon ses forces, a chacun selon ses besoins


** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

Re: initial console

[Alois Fertl]

The problem you are seeing here is probably prep_init in prep_setup.c
not copying the arguments passed by the boot loader into the kernels command
line. Your root=/dev/sda5 is probably ignored.
Look at your early log messages during boot. There should be a line
"Boot arguments: ..." telling you those things seen by the kernel.

In case the arguments aren't as you typed them, try putting the following
lines at the beginning of prep_init:

+       if (r6) {
+               *(char *)(r7 + KERNELBASE) = 0;
+               strcpy(cmd_line, (char *)(r6 + KERNELBASE));
+       }

What hardware is this running on? If it is Motorola VME this failure is only
the starting point and other trouble will follow. There are additional fixes
but I can't verify them against a working source at the moment. test9 and test10
from fmlabs currently both panic during init as soon as the process starts using
the hard drive (this is on a PowerStack).

Xavier Grave wrore:
>
> On Thu, 19 Oct 2000, Chris Leishman wrote:
> > I know it sounds dumb, but have you ensured that you've got the root partition
> > set correctly?  I've seen these errors before when I had a root partition
> > specified that didn't contain /dev or /sbin/init.
>
> /dev/sda5 on / type ext2 (rw,errors=remount-ro,errors=remount-ro)
> proc on /proc type proc (rw)
> devpts on /dev/pts type devpts (rw,gid=5,mode=620)
> /dev/sda2 on /boot type ext2 (rw)
> /dev/sda6 on /home type ext2 (rw)
> /dev/sda7 on /export/data1 type ext2 (rw)
> /dev/sda8 on /export/data2 type ext2 (rw)
>
> And I give the following argument root=/dev/sda5
> with the 2.4.0 kernel it fails but with a 2.2.17 kernel it works.
>
> 33 (0) 1 69 15 79 59
> De chacun selon ses forces, a chacun selon ses besoins
>


** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

Re: initial console

[Xavier Grave]

On Wed, 18 Oct 2000, Alois Fertl wrote:
>
> The problem you are seeing here is probably prep_init in prep_setup.c
> not copying the arguments passed by the boot loader into the kernels command
> line. Your root=/dev/sda5 is probably ignored.
> Look at your early log messages during boot. There should be a line
> "Boot arguments: ..." telling you those things seen by the kernel.
Indeed, The kernel argument I give is :
root=/dev/sda5
and during the boot when I look more closely :
PReP architecture
Boot arguments: /dev/sda1

> In case the arguments aren't as you typed them, try putting the following
> lines at the beginning of prep_init:
>
> +       if (r6) {
> +               *(char *)(r7 + KERNELBASE) = 0;
> +               strcpy(cmd_line, (char *)(r6 + KERNELBASE));
> +       }
Ok, this is fine my kernel boots ! Thank you very much.
> What hardware is this running on? If it is Motorola VME this failure is only
> the starting point and other trouble will follow. There are additional fixes
> but I can't verify them against a working source at the moment. test9 and
> test10
> from fmlabs currently both panic during init as soon as the process starts
> using the hard drive (this is on a PowerStack).

I have a MVME2303 from motorola diskless + a PMC with a 53c895 pci board
for my disk. With the 2.2.17 kernel all works well.
And now with the latest fsmlabs + your hack all function !

O+ xavier

33 (0) 1 69 15 79 59
De chacun selon ses forces, a chacun selon ses besoins


** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

Re: initial console

[Matt Porter]

On Thu, Oct 19, 2000 at 02:16:35PM +0200, Xavier Grave wrote:
>
> On Wed, 18 Oct 2000, Alois Fertl wrote:
> >
> > The problem you are seeing here is probably prep_init in prep_setup.c
> > not copying the arguments passed by the boot loader into the kernels command
> > line. Your root=/dev/sda5 is probably ignored.
> > Look at your early log messages during boot. There should be a line
> > "Boot arguments: ..." telling you those things seen by the kernel.
> Indeed, The kernel argument I give is :
> root=/dev/sda5
> and during the boot when I look more closely :
> PReP architecture
> Boot arguments: /dev/sda1
>
> > In case the arguments aren't as you typed them, try putting the following
> > lines at the beginning of prep_init:
> >
> > +       if (r6) {
> > +               *(char *)(r7 + KERNELBASE) = 0;
> > +               strcpy(cmd_line, (char *)(r6 + KERNELBASE));
> > +       }
> Ok, this is fine my kernel boots ! Thank you very much.
> > What hardware is this running on? If it is Motorola VME this failure is only
> > the starting point and other trouble will follow. There are additional fixes
> > but I can't verify them against a working source at the moment. test9 and
> > test10
> > from fmlabs currently both panic during init as soon as the process starts
> > using the hard drive (this is on a PowerStack).
>
> I have a MVME2303 from motorola diskless + a PMC with a 53c895 pci board
> for my disk. With the 2.2.17 kernel all works well.
> And now with the latest fsmlabs + your hack all function !

Sorry, I had this change locally but hadn't pushed it yet. :)  The other
option on PReP is to build with /dev/nvram support and then (on a
PPCBUG system) use 'gevedit bootargs' to set a kernel argument command
line like "root=/dev/sda5".  That's often more convenient then hard
coding in your parameters like with the PReP cmd_line config option.

--
Matt Porter
MontaVista Software, Inc.
mporter@mvista.com

** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

Initial Console

[Prabhu Chawandi]

Hi All,

   Initial console /dev/console in  the kernel is directed to /dev/ttyS0,

Any bosy is having info, where exavtly in which file has been done so..

if not what exactly is happening to initialize console to ttyS0.


Please have your words...


thanks
prabhu
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Initial Console

[Prabhu Chawandi]

Hi All,

   Initial console /dev/console in  the kernel is directed to /dev/ttyS0,

Any bosy is having info, where exavtly in which file has been done so..

if not what exactly is happening to initialize console to ttyS0.


Please have your words...


thanks
prabhu

Re: Initial Console

[Geert Uytterhoeven]

On Mon, 13 Oct 2008, Prabhu Chawandi wrote:
>    Initial console /dev/console in  the kernel is directed to /dev/ttyS0,

Depends...

> Any bosy is having info, where exavtly in which file has been done so..

drivers/char/tty_io.c, look for `TTYAUX_MAJOR, 1'.

> if not what exactly is happening to initialize console to ttyS0.

... depends on the list of available console devices, and the `console=' kernel
command line parameter.

Gr{oetje,eeting}s,

						Geert

--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
							    -- Linus Torvalds