Hi Peter
I did this:
mkinitrd -v -f --preload=dasd_mod --preload=dasd_diag_mod
initrd-2.6.9-55.0.2.E 2.6.9-55.0.2.EL
Creating initramfs
Looking for deps of module dasd_mod
Looking for deps of module dasd_diag_mod dasd_mod
Looking for deps of module dasd_mod
Looking for deps of module ide-disk
Looking for deps of module dasd_mod
Looking for deps of module dasd_eckd_mod dasd_mod
Looking for deps of module dasd_mod
Looking for deps of module dasd_fba_mod dasd_mod
Looking for deps of module dasd_mod
Looking for deps of module ext3 jbd
Looking for deps of module jbd
Using modules: ./kernel/drivers/s390/block/dasd_mod.ko
./kernel/drivers/s390/bl
ock/dasd_diag_mod.ko ./kernel/drivers/s390/block/dasd_eckd_mod.ko
./kernel/drive
rs/s390/block/dasd_fba_mod.ko ./kernel/fs/jbd/jbd.ko
./kernel/fs/ext3/ext3.ko
/sbin/nash -> /tmp/initrd.qg2007/bin/nash
/sbin/insmod.static -> /tmp/initrd.qg2007/bin/insmod
/sbin/udev.static -> /tmp/initrd.qg2007/sbin/udev
/etc/udev/udev.conf -> /tmp/initrd.qg2007/etc/udev/udev.conf
copy from
/lib/modules/2.6.9-55.0.2.EL/./kernel/drivers/s390/block/dasd_mod.ko(e
lf64-s390) to /tmp/initrd.qg2007/lib/dasd_mod.ko(elf64-s390)
copy from
/lib/modules/2.6.9-55.0.2.EL/./kernel/drivers/s390/block/dasd_diag_mod
.ko(elf64-s390) to /tmp/initrd.qg2007/lib/dasd_diag_mod.ko(elf64-s390)
copy from
/lib/modules/2.6.9-55.0.2.EL/./kernel/drivers/s390/block/dasd_eckd_mod
.ko(elf64-s390) to /tmp/initrd.qg2007/lib/dasd_eckd_mod.ko(elf64-s390)
copy from
/lib/modules/2.6.9-55.0.2.EL/./kernel/drivers/s390/block/dasd_fba_mod.
ko(elf64-s390) to /tmp/initrd.qg2007/lib/dasd_fba_mod.ko(elf64-s390)
copy from
/lib/modules/2.6.9-55.0.2.EL/./kernel/fs/jbd/jbd.ko(elf64-s390) to /tm
p/initrd.qg2007/lib/jbd.ko(elf64-s390)
copy from
/lib/modules/2.6.9-55.0.2.EL/./kernel/fs/ext3/ext3.ko(elf64-s390) to /
tmp/initrd.qg2007/lib/ext3.ko(elf64-s390)
Loading module dasd_mod with options
dasd=800,801(diag),802-83f,900-90f(diag)
Loading module dasd_diag_mod
Loading module dasd_eckd_mod
Loading module dasd_fba_mod
Loading module jbd
Loading module ext3
And then: ,
zipl -V
Using config file '/etc/zipl.conf'
Target device information
Device..........................: 5e:00
Partition.......................: 5e:01
Device name.....................: dasda
DASD device number..............: 0800
Type............................: disk partition
Disk layout.....................: ECKD/compatible disk layout
Geometry - heads................: 15
Geometry - sectors..............: 12
Geometry - cylinders............: 10016
Geometry - start................: 24
File system block size..........: 4096
Physical block size.............: 4096
Device size in physical blocks..: 76800
Building bootmap '/boot//bootmap'
Building menu 'rh-automatic-menu'
Adding #1: IPL section '2.6.9-55.0.2.EL' (default)
kernel image......: /boot/vmlinuz-2.6.9-55.0.2.EL at 0x10000
kernel parmline...: 'dasd=800,801(diag),802-83f,900-90f(diag)
possible_cpus=3
root=LABEL=/' at 0x1000
initial ramdisk...: /boot/initrd-2.6.9-55.0.2.EL.img at 0x800000
Adding #2: IPL section '2.6.9-42.0.10.E'
kernel image......: /boot/vmlinuz-2.6.9-42.0.10.EL at 0x10000
kernel parmline...: 'root=LABEL=/' at 0x1000
initial ramdisk...: /boot/initrd-2.6.9-42.0.10.EL.img at 0x800000
Adding #3: IPL section '2.6.9-42.0.8.EL'
kernel image......: /boot/vmlinuz-2.6.9-42.0.8.EL at 0x10000
kernel parmline...: 'root=LABEL=/' at 0x1000
initial ramdisk...: /boot/initrd-2.6.9-42.0.8.EL.img at 0x800000
Adding #4: IPL section 'linux'
kernel image......: /boot/vmlinuz-2.6.9-42.EL at 0x10000
kernel parmline...: 'root=LABEL=/' at 0x1000
initial ramdisk...: /boot/initrd-2.6.9-42.EL.img at 0x800000
Preparing boot device: dasda (0800).
Preparing boot menu
Interactive prompt......: enabled
Menu timeout............: 15 seconds
Default configuration...: '2.6.9-55.0.2.EL'
Syncing disks...
Done.
Unfortunately, after reboot, same results...
Cheers
Pat
,
Patrick Carroll | Enterprise Architect
L.L.Bean, Inc.(r) | Double L St. | Freeport ME 04033
http://www.llbean.com | [EMAIL PROTECTED] | 207.552.2426
-----Original Message-----
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of
Peter 1 Oberparleiter
Sent: Monday, November 26, 2007 12:38 PM
To: [email protected]
Subject: Re: Missing DIAG discipline; was RE:
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
----------------------------------------------------------------------
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
