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
