I don't think you're on crack,
but the book might be. 4,64 is a UART class serial line.
Not likely your zSeries will have that. But all HW have 5,1 console.
Well, neither is on crack. The 3215/sclp console driver use 4,64 as device
node, so the dd-book is correct. But nevertheless you have
Richard Troth wrote:
Adam Thornton wote:
OK, so, am I on CRACK or does the Linux 2.6 device drivers book say to
create 4,64 ?
I don't think you're on crack,
but the book might be. 4,64 is a UART class serial line.
Not likely your zSeries will have that. But all HW have 5,1 console.
What is the magic incantation I need in order to get zipl to recognize a
2.6 style DASD device for its root filesystem? I've got ECKD built into
the kernel. What do I need in my udev configuration to get the DASD
devices recognized? I'm planning on using the
/dev/dasd/0.0.150/part1 style
Are you using the 1.3.0 version of the s390-tools?
Mark Post
-Original Message-
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Adam
Thornton
Sent: Monday, April 26, 2004 11:56 AM
To: [EMAIL PROTECTED]
Subject: 2.6 device node help
What is the magic incantation I need
On Mon, 2004-04-26 at 11:05, Post, Mark K wrote:
Are you using the 1.3.0 version of the s390-tools?
Probably not. Still, would it matter in the initial IPL? I can't find
the root device, whether I call it /dev/dasd/0.0.0150/part1 or
/dev/dasd/0150/part1 (which is what it was before). The IPL
It might. New boot sectors, bootloader code, etc. I would give it a try.
Mark Post
-Original Message-
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Adam
Thornton
Sent: Monday, April 26, 2004 12:24 PM
To: [EMAIL PROTECTED]
Subject: Re: 2.6 device node help
On Mon
Probably not. Still, would it matter in the initial IPL?
It doesn't. Finding the root device is a kernel issue.
I can't find
the root device, whether I call it /dev/dasd/0.0.0150/part1 or
/dev/dasd/0150/part1 (which is what it was before). The IPL record
shows the new kernel paramters
on 390 Port [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: Re: 2.6 device node help
Date: Mon, 26 Apr 2004 11:24:08 -0500
On Mon, 2004-04-26 at 11:05, Post, Mark K wrote:
Are you using the 1.3.0 version of the s390-tools?
Probably not. Still, would it matter in the initial IPL? I can't find
On Mon, 2004-04-26 at 13:05, Cornelia Huck wrote:
I can't find
the root device, whether I call it /dev/dasd/0.0.0150/part1 or
/dev/dasd/0150/part1 (which is what it was before). The IPL record
shows the new kernel paramters when I boot.
Did you use devfs before and now want to use udev
/dev/dasda1 works fine.
Now, however, I've got another problem a bit lower down the boot
sequence:
Kernel command line: root=/dev/dasda1 ro noinitrd dasd=0.0.0150-0.0.015f
console=ttyS0
I've manually created /dev/ttyS0 as 4,64
But then, as I boot, I get:
VFS: Mounted root (ext3
I've manually created /dev/ttyS0 as 4,64
You don't have a device for 4,64.
Warning: unable to open an initial console.
So what you need to do is replace your 4,64 /dev/ttyS0
with a 5,1 /dev/ttyS0 or (better!) change that parm line
and be sure you have /dev/console for 5,1.
-- R;
On Monday 26 April 2004 18:24, Adam Thornton wrote:
Probably not. Still, would it matter in the initial IPL? I can't find
the root device, whether I call it /dev/dasd/0.0.0150/part1 or
/dev/dasd/0150/part1 (which is what it was before). The IPL record
shows the new kernel paramters when I
On Mon, 2004-04-26 at 17:29, Richard Troth wrote:
I've manually created /dev/ttyS0 as 4,64
You don't have a device for 4,64.
Warning: unable to open an initial console.
So what you need to do is replace your 4,64 /dev/ttyS0
with a 5,1 /dev/ttyS0 or (better!) change that parm line
OK, so, am I on CRACK or does the Linux 2.6 device drivers book say to
create 4,64 ?
I don't think you're on crack,
but the book might be. 4,64 is a UART class serial line.
Not likely your zSeries will have that. But all HW have 5,1 console.
-- R;
14 matches
Mail list logo
