There's a delay between the time the module gets loaded and udev notices
and creates the device node.  This has bit us on other devices (tape,
fcp) as well.   We've had some discussions with Red Hat about it, and
there's supposed to be some kind of fix in RHEL 4.5 or 5.0.

-----Original Message-----
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of
Susan Zimmerman
Sent: Monday, July 02, 2007 1:43 PM
To: [email protected]
Subject: Re: [LINUX-390] vmcp during boot results in Error: Could not
open device /dev/vmcp: No such device


Hi Mark.

I moved vmcp to the INITRD_MODULES but it still results in the same
message.

during boot:

Starting udev
Creating devices
Loading kernel/drivers/s390/char/vmcp.ko
z/VM CP interface loaded
.
.
.

Error: Could not open device /dev/vmcp: No such device
       +++ RC=3 +++




my settings now are:



INITRD_MODULES="vmcp"

## Type:                string
## ServiceRestart:      boot.loadmodules
#
# This variable contains the list of modules to be loaded
# once the main filesystem is active
#
MODULES_LOADED_ON_BOOT=""

>From what I can tell, the device exists...

OSA-LNX1:/ # ls -l /dev/vmc*
crw-------  1 root root 10, 62 Jun 29 13:06 /dev/vmcp
OSA-LNX1:/ #


Thanks again for any and all help!

Susan



------------------------------

Date:    Fri, 29 Jun 2007 14:34:23 -0600
From:    Mark Post <[EMAIL PROTECTED]>
Subject: Re: vmcp during boot results in  Error: Could not open device
/dev/vmcp: No such device

>>> On Fri, Jun 29, 2007 at  4:31 PM, in message
<OF230BA289.CD61A39D-ON85257309.00706852-85257309.0070
[EMAIL PROTECTED]>=
,
Susan Zimmerman <[EMAIL PROTECTED]> wrote:=20
> Hi Listers.
>=20
> I am trying to issue a vmcp command within a boot script and receive
the
> following message during boot:
>=20
>  Error: Could not open device /dev/vmcp: No such device
>         +++ RC=3D3 +++
>=20
> Once the system is booted, I can see the device...
>=20
> Any ideas on how to make this device permanent?

Which distribution are you running?  On SLES, you can add vmcp to the
list
=
of modules that need to be in the initrd by editing
/etc/sysconfig/kernel
INITRD_MODULES=3D"vmcp"

Mark Post

----------------------------------------------------------------------

----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or
visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--------------------------------------------------------

This message w/attachments (message) may be privileged, confidential or 
proprietary, and if you are not an intended recipient, please notify the 
sender, do not use or share it and delete it. Unless specifically indicated, 
this message is not an offer to sell or a solicitation of any investment 
products or other financial product or service, an official confirmation of any 
transaction, or an official statement of Merrill Lynch. Subject to applicable 
law, Merrill Lynch may monitor, review and retain e-communications (EC) 
traveling through its networks/systems. The laws of the country of each 
sender/recipient may impact the handling of EC, and EC may be archived, 
supervised and produced in countries other than the country in which you are 
located. This message cannot be guaranteed to be secure or error-free. This 
message is subject to terms available at the following link: 
http://www.ml.com/e-communications_terms/. By messaging with Merrill Lynch you 
consent to the foregoing.
--------------------------------------------------------

----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390

Reply via email to