-= MVME 2300 boot args=-

-= MVME 2300 boot args=-

[Lionel TAILLURAT]

Hi,

I have a full working kernel with VME bus support (thx Gabriel for your
patch and your help).

The problem now is that I can't have the boot args working !

During the configuration of the kernel, I write "root=/dev/sda2
console=ttyS0" in the "initial kernel command string" , and only
"console=ttyS0" is shown at boot prompt and the kernel don't see my
haddrive!

If I use the command (in PPCBUG):
GEVEDIT bootargs
bootargs=root=/dev/sda2 console=ttyS0

result : same as above !

Whats wrong ?

I always need to write by hand "root=/dev/sda2" !

Please help me !

Thx in advance.
-------------------------------------------------------
Lionel TAILLURAT
TECHNICAL SERVICE

ECRIN AUTOMATISMES -industrial computer's-
Rue du pré-de-l'Horme
B.P 15
38921 CROLLES CEDEX
FRANCE
Tel :(33) 4 76 92 20 01
Fax :(33) 4 76 08 03 18
Email: Lionel.TAILLURAT@ecrin.com
---------------------------------------------------------


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

Re: -= MVME 2300 boot args=-

[Gabriel Paubert]

On Wed, 26 Jul 2000, Lionel TAILLURAT wrote:

>
> Hi,
>
> I have a full working kernel with VME bus support (thx Gabriel for your
> patch and your help).
>
> The problem now is that I can't have the boot args working !
>
> During the configuration of the kernel, I write "root=/dev/sda2
> console=ttyS0" in the "initial kernel command string" , and only
> "console=ttyS0" is shown at boot prompt and the kernel don't see my
> haddrive!
>
> If I use the command (in PPCBUG):
> GEVEDIT bootargs
> bootargs=root=/dev/sda2 console=ttyS0

Prepboot still ha to be upgraded to take the arguments from the NVRAM. If
you wnat to give it a try, it's not that complex,  just that I never fond
the time to do it. It also still ignores the config option. Sorry...

Nevertheless for the root device option, the right way to do it would be
to use the same scheme as the Intel port. You can type make zImage
ROOTDEV=/dev/sda2 for example. By default, it will automagically (on
Intel pc) take the current root device which is very convenient.

> Whats wrong ?

My code :-(

	Regards,
	Gabriel.


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

Re: -= MVME 2300 boot args=-

[Crusman]

Hi,

I resolve the problem with the following Haddrive map :

sda2:  Prep boot partition starting at the first sector of the harddrive.
sda1:  root partition.
sda3:  swap partition.

and all work well.


Regards

Lionel.

-----Message d'origine-----
De : Gabriel Paubert <paubert@iram.es>
À : Lionel TAILLURAT <Lionel.TAILLURAT@ecrin.com>
Cc : ppc_mailing_list <linuxppc-embedded@lists.linuxppc.org>
Date : samedi 29 juillet 2000 19:08
Objet : Re: -= MVME 2300 boot args=-


>
>On Wed, 26 Jul 2000, Lionel TAILLURAT wrote:
>
>>
>> Hi,
>>
>> I have a full working kernel with VME bus support (thx Gabriel for your
>> patch and your help).
>>
>> The problem now is that I can't have the boot args working !
>>
>> During the configuration of the kernel, I write "root=/dev/sda2
>> console=ttyS0" in the "initial kernel command string" , and only
>> "console=ttyS0" is shown at boot prompt and the kernel don't see my
>> haddrive!
>>
>> If I use the command (in PPCBUG):
>> GEVEDIT bootargs
>> bootargs=root=/dev/sda2 console=ttyS0
>
>Prepboot still ha to be upgraded to take the arguments from the NVRAM. If
>you wnat to give it a try, it's not that complex,  just that I never fond
>the time to do it. It also still ignores the config option. Sorry...
>
>Nevertheless for the root device option, the right way to do it would be
>to use the same scheme as the Intel port. You can type make zImage
>ROOTDEV=/dev/sda2 for example. By default, it will automagically (on
>Intel pc) take the current root device which is very convenient.
>
>> Whats wrong ?
>
>My code :-(
>
> Regards,
> Gabriel.
>
>
>


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

Re: -= MVME 2300 boot args=-

[Gabriel Paubert]

On Sun, 30 Jul 2000, Crusman wrote:

> Hi,
>
> I resolve the problem with the following Haddrive map :
>
> sda2:  Prep boot partition starting at the first sector of the harddrive.
> sda1:  root partition.
> sda3:  swap partition.

Fine, mine is root on sda1, swap on sda2 and prepboot on sda3 at the end
of the disk with an extented partition between sda2 and sda3.

> and all work well.

Yes, this does not mean that we should not trry to improve it. I just
booted 2.4.0-test5 this morning. I hope to make patches available soon,
especially for timing which is horrendous in the official kernel right
now (in several weeks now, I've never seen one of my machines locked on
the NTP server be off by more than 20 microseconds, versus tens of
milliseconds in the stock kernel).

	Regards,
	Gabriel.


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