Linux on 390 Port <[email protected]> wrote on 26.11.2007 16:23:33:
> Linux on 390 Port <[email protected]> wrote on 26.11.2007
> > Has DIAG access to a DASD worked before on your system (i.e. not at
> > reboot but by manual activation)?
> Yes...methinks that this started after a mkinitrd/zipl
Ok, did some tests and ran into the same issue.. on RHEL5. Apparently
there are two problems:
1) mkinitrd does not include support for dasd_diag_mod - I'm assuming you
specified the module using mkinitrd's --with= switch
2) a kernel bug prevents devices that failed to be activated during dasd
module load to be activated later on
Because of 1) and the fact that the --with switch adds modules too late in
the initialization sequence, you seem to be running into 2). As a
workaround, use the following method:
mkinitrd initrd-<version> <version> --preload=dasd_mod
--preload=dasd_diag_mod
Regards,
Peter
--
Peter Oberparleiter
Linux on System z Development
IBM Deutschland Entwicklung GmbH
----------------------------------------------------------------------
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
