Hi Peter, Thanks for the response. It was indeed a typo (of the cut-and paste variety). On my test system, I removed all initrd images from /boot (except for initrd-2.6.9-55.0.2.EL) and have the 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: Tuesday, November 27, 2007 4:03 AM To: [email protected] Subject: Re: Missing DIAG discipline; was RE: Linux on 390 Port <[email protected]> wrote on 26.11.2007 19:24:34: > 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 I'm assuming this was just a typo but the line above would create a initrd in file initrd-2.6.9-55.0.2.E while zipl is loading > initial ramdisk...: /boot/initrd-2.6.9-55.0.2.EL.img at 0x800000 The output of mkinitrd also doesn't quite match with the boot messages. Please make sure that you're not accidently loading an outdated version of the initrd. 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
