Re: Catch 22 with eckd dasd on debian woody
John, It's actually fairly simple. Use the starter kernel and initrd1/2. Once the system is up, do an lsmod command to see if any of the DASD drivers are loaded. If not insmod it, with the device numbers of your root file system and the one containing your /usr file system if it is separate. (Not knowing what version you're running, I can't tell you the exact names of the driver modules. They could be dasd, or dasd_mod, etc.) Mount your root file system on /mnt, and your /usr file system on /mnt/usr. Then, chroot to /mnt. Re-run zipl. Do an exit. Then, unmount your /mnt/usr and /mnt file systems. Reboot from DASD. Mark Post -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of John P Taylor Sent: Thursday, September 16, 2004 10:47 AM To: [EMAIL PROTECTED] Subject: Catch 22 with eckd dasd on debian woody In a scenario where I've corrupted the boot 'record' on the dasd that I IPL from, or the root partition is not not bootable, how can I recover? If I bring-up the debian starter-image kernel initrd ( initrd2), I'm not sure if dasd_mod should be loaded from initrd or is built into the kernel in this environment (how can I tell? I have no config file to look at). modprobe dasd or dasd_mod say's that neither module is found (which may be fine if it's build into the kernel). cat /proc/dasd/devices shows nothing. I can bring up SLES or RHEL starter systems in a similar way I can get the dasd seen by the kernel by modprob/insmod dasd_mod/dasd_eckd_mod but neither of those starter systems can mount the partitions presumably becase there is no support for the devfs? I've tried building debian kernel with support for all filesystems and devfs and modular dasd drivers, but I could never get what I built to boot. Any thoughts appreciated. John P Taylor. -- 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
Catch 22 with eckd dasd on debian woody
In a scenario where I've corrupted the boot 'record' on the dasd that I IPL from, or the root partition is not not bootable, how can I recover? If I bring-up the debian starter-image kernel initrd ( initrd2), I'm not sure if dasd_mod should be loaded from initrd or is built into the kernel in this environment (how can I tell? I have no config file to look at). modprobe dasd or dasd_mod say's that neither module is found (which may be fine if it's build into the kernel). cat /proc/dasd/devices shows nothing. I can bring up SLES or RHEL starter systems in a similar way I can get the dasd seen by the kernel by modprob/insmod dasd_mod/dasd_eckd_mod but neither of those starter systems can mount the partitions presumably becase there is no support for the devfs? I've tried building debian kernel with support for all filesystems and devfs and modular dasd drivers, but I could never get what I built to boot. Any thoughts appreciated. John P Taylor. -- 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
Re: Catch-22
On Fri, 2003-03-07 at 19:08, Kenneth Illingsworth wrote: When I try to install the libgnomeprint rpm via webmin, I get the following dependency error: error: failed dependencies: gnome-print = 0.29 is needed by libgnomeprint15-0.29-6 Yet, when I try to install gnome-print: error: failed dependencies: libgnomeprint15 = 0.29 is needed by gnome-print-0.29-6 libgnomeprint.so.15 is needed by gnome-print-0.29-6 Install both at the same time (same command). RPM knows about this and cares that the beginning and end state of the transaction are valid, not per file
Catch-22
When I try to install the libgnomeprint rpm via webmin, I get the following dependency error: error: failed dependencies: gnome-print = 0.29 is needed by libgnomeprint15-0.29-6 Yet, when I try to install gnome-print: error: failed dependencies: libgnomeprint15 = 0.29 is needed by gnome-print-0.29-6 libgnomeprint.so.15 is needed by gnome-print-0.29-6 Both RPM's were acquired from the MSC mirror (ftp://mirror.mcs.anl.gov/pub/redhat/redhat/linux/7.2/en/os/s390/RedHat/RPMS/). It appears that this is one instance where one has to enable 'ignore dependencies' on one of the RPM's in order to get them both installed. This seemed to work, but I still thought that this needed you comments. Thank you.
Re: Catch-22
For the MVS folks out there, think if it as an SMP/E co-requisite. They have to go on at the same time. Just to make sure there's no confusion, what Alan's saying is do this: rpm -Uvh gnome-print-0.29-?.s390.rpm libgnomeprint15-0.29-6.s390.rpm Mark Post -Original Message- From: Alan Cox [mailto:[EMAIL PROTECTED] Sent: Friday, March 07, 2003 3:19 PM To: [EMAIL PROTECTED] Subject: Re: Catch-22 On Fri, 2003-03-07 at 19:08, Kenneth Illingsworth wrote: When I try to install the libgnomeprint rpm via webmin, I get the following dependency error: error: failed dependencies: gnome-print = 0.29 is needed by libgnomeprint15-0.29-6 Yet, when I try to install gnome-print: error: failed dependencies: libgnomeprint15 = 0.29 is needed by gnome-print-0.29-6 libgnomeprint.so.15 is needed by gnome-print-0.29-6 Install both at the same time (same command). RPM knows about this and cares that the beginning and end state of the transaction are valid, not per file
