Re: Slackware 10.0 install failure - dasd_eckd_mod stuck in initializing state
Extremely bad form to answer my own post, but given the timezone differences, I thought everyone might like to know today that persistence pays off, that is, the seventh (or was it eighteenth?) reboot eventually worked, in that the eckd module eventually finished initialising, and the setup command was able to find them, and the rest of the install kicked off. What a very curious turn of events, is all I can say. I'll be repeating this tomorrow, just to make sure (and to fix up a couple of install errors that broke the install anyway). cheers Peter Peter Bishop Mainframe IT Outsourcing Service Delivery EDS Asia-Pacific Phone:+61 2 9378 0113 + mailto:[EMAIL PROTECTED] _ From: Bishop, Peter G Sent: Tuesday, 19 July 2005 3:49 PM To: 'linux-390@vm.marist.edu' Subject: Slackware 10.0 install failure - dasd_eckd_mod stuck in initializing state Hi List, I'm trying to install the Slackware from the site at http://ftp.ibiblio.org/pub/Linux/distributions/slack390/slack390-10.0/ and am at the point where the VM reader install files are IPLed and ready to start formatting DASD. When I first did this, I did a dasdfmt and got a cannot open type error, as in: [EMAIL PROTECTED]:/1 dasdfmt -b 4096 -f /dev/dasda -p dasdfmt -b 4096 -f /dev/dasda -p dasdfmt: Unable to open device /dev/dasda: No such device [EMAIL PROTECTED]:/2 So I tried a few things and finally saw that there was something amiss in driver land: lsmod Module Size Used by reiserfs 243712 0 (unused) jfs 188472 0 (unused) ext3 73168 0 (unused) dasd_diag_mod 5996 0 (autoclean) (unused) jbd52056 0 [ext3] dasd_eckd_mod 57896 1 (initializing) dasd_fba_mod5340 0 (unused) dasd_mod 51036 3 [dasd_diag_mod dasd_eckd_mod dasd_fba_mod] qeth 149528 1 qdio 38224 1 [qeth] [EMAIL PROTECTED]:/5 cat /proc/dasd/devices cat /proc/dasd/devices 0200(none) at ( 94: 0) is dasda : accepted 0201(none) at ( 94: 4) is dasdb : unknown [EMAIL PROTECTED]:/6 I trawled around in the archives, and found this very similar, almost identical incidence, but am none the wiser: http://www2.marist.edu/htbin/wlvtype?LINUX-VM.47871 (actually this link is the end of that particular thread). I've rebooted numerous times, reformatted the minidisks in question both from VM:Secure and native CPFMTXA, enlarged the ramdisk size, re-downloaded the initrd and vminstall images (i.e. the VM reader install image, not the tape install one). I even made these minidisks available to a SLES8 system here and ran a dasdfmt/fdasd on them to make sure they were OK. Even then, they were still not acceptable to the Slackware installer. Now I'm sorta stuck - anyone care to opine on where I went wrong and even better, what I can do to get these disks going? At the moment, I'm in a tight loop doing reboots until it works. Plenty of console logs, etc., for any who wants them. cheers Peter Peter Bishop Mainframe IT Outsourcing Service Delivery EDS Asia-Pacific Phone:+61 2 9378 0113 + mailto:[EMAIL PROTECTED] -- 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
OSA problem
Hi! We had a problem with the OSA card: Linux messages: Jul 18 22:07:41 neptunus kernel: qeth: Link failure on eth0 (CHPID 0x1) -- there is a network problem or someone pulled the cable or disabled the port.Discarding outgoing packets. Jul 18 22:07:41 neptunus kernel: qeth: recovery was scheduled on irq 0x205 (eth0) with problem 0x1 Jul 18 22:07:41 neptunus kernel: qeth: You are lucky! Somebody either fixed the network problem, plugged the cable back in or enabled the OSA port on eth0 (CHPID 0x1). The link has come up. Eariler this we got this message when the cable was really pulled, but now nothing happened. The problem was not fixed, there was no communication. I've tried to ping, but nothing happened. (then I have tried floodping, than 6 packet sent, and thedots stopped) We had to shut down and start the channel on the HMC, after that: Jul 19 08:05:35 neptunus kernel: mach_handler : wakeup ... Jul 19 08:05:35 neptunus kernel: free_irq(0205) - device 0190 busy, retry count exceeded Jul 19 08:05:35 neptunus kernel: free_irq(0207) - device 0192 busy, retry count exceeded Jul 19 08:06:02 neptunus last message repeated 2 times Jul 19 08:06:12 neptunus kernel: qeth: recovery was scheduled on irq 0x205 (eth0) with problem 0xb Jul 19 08:06:37 neptunus kernel: qdio : Did not get interrupt on clear_IO, irq=0x207. Jul 19 08:06:43 neptunus kernel: qeth: recovered device 0x190/0x191/0x192 (eth0) successfully. When the z/OS guys tried to restart tcpip (before the channel restart): IST1222I DATA DEVICE 0192 IS INOPERATIVE, NAME IS MPCIP190 412 IST1578I DEVICE INOP DETECTED FOR MPCIP190 BY ISTLLCWC CODE = 100 IST314I END EZZ4310I ERROR: CODE=80100040 REPORTED ON DEVICE MPCIP190. DIAGNOSTIC CODE: 00 EZZ4309I ATTEMPTING TO RECOVER DEVICE MPCIP190 There was no Hardware Message on the HMC. What do you think, do we have a hardware problem (I've found in a book describing IST1578I, code 100: probable hardware error) - or what happend to OSA? Thanks: István -- 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: The way of confirmation of applied APAR and PTF on z/VM.
One method could be via SERVICE-rexx, i.e.: SERVICE ALL STATUS PTF- or APAR-identifier Of course you should have the rights to do so (Userid MAINT or appropr. rights). Pls. have a look at it via HELP VMSES MENU or check the manual z/VM 5.1 VMSES/E Introduction Reference ciao Lutz - Lutz Hamann BETA Systems Software AG z/OS System Engineering - mainframe_s390 [EMAIL PROTECTED] ahoo.co.jpTo Sent by: Linux on LINUX-390@VM.MARIST.EDU 390 Port cc [EMAIL PROTECTED] IST.EDU Subject The way of confirmation of applied APAR and PTF on z/VM. 19.07.2005 09:42 Please respond to Linux on 390 Port [EMAIL PROTECTED] IST.EDU Hi,all Please teach me. I want to confirm the APARs and PTFs already applied to z/VM V5.1. But I don't know the way of confirm. Please teach me the way of confirm. Thank you. - K.M. __ Save the earth http://pr.mail.yahoo.co.jp/ondanka/ -- 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
Re: SLES9 Installation - Very Basic
What I've done, rather than copy all the files from each CD / ISO is to loop mount the ISO files on an accessible system, and use them from there. The mount would look something like: mount -t iso9660 -o loop /home/isos/suse9-64-CD1.iso /media/SuSE9-64/sles9/CD1 There's actually a specific set of directory names, documented on the first CD, so that everything will be properly found by an install. The structure I have is: /media/SuSE9-64/ -- This is the directory I give as the base during the install. |-- sles9 | |- CD1 |-- core9 |- CD1 |- CD2 |- CD3 ... There are a couple of files to be copied / created in addition to the CDs, but it works well. I'm using FTP to do the installs, but I think it would work the same way for NFS. If you have a lot of ISO images, you may need to increase the number of loop devices on the system. Using the loop mount eliminates the need to copy all of the individual files, and would allow you to replace a single ISO file, if something were updated (unlikely), rather than having to copy all of the individual files. This is as close to having a CD reader on the virtual machine as you can get. :-) -- Robert P. Nix Mayo Foundation RO-CE-8-857 200 First Street SW 507-284-0844Rochester, MN 55905 - In theory, theory and practice are the same, but in practice, theory and practice are different. -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Smith, Ann (ISD, IT) Sent: Monday, July 18, 2005 4:27 PM To: LINUX-390@VM.MARIST.EDU Subject: SLES9 Installation - Very Basic I have finally ordered SLES9 for zseries. I ordered media which I have received. There are 6 CD's for SLES9 64-bit for zseries and 6 CD's for 31-bit for s/390. I did not realize there was a 31-bit SLES9. Why did I think SLES9 was 64-bit only? I'm not sure anyone can answer that question. But hopefully they can answer the one regarding setting up an installation server for network installations- What is the best method to use for getting the data off the CD's to disk and installing using NFS? The release notes in /docu on CD1 just say to enter mkdir -p installroot/sles9/CD1 then copy contents of CD1 into the directory mkdir -p installroot/core9/CD1 then copy contents of CD2 into this directory mkdir -p installroot/core9/CD2 then copy contents of CD3 into this directory and so on ... I guess I just use cp command with -x and -a for this method and let yast do the rest. On the other hand the Redbook on LPAR to virtual servers in Two Days (sg246695.pdf) says to use dd to create ISO images and use mksles9root to creat the SLES9 install tree. Which method is preferred? * PRIVILEGED AND CONFIDENTIAL: This communication, including attachments, is for the exclusive use of addressee and may contain proprietary, confidential and/or privileged information. If you are not the intended recipient, any use, copying, disclosure, dissemination or distribution is strictly prohibited. If you are not the intended recipient, please notify the sender immediately by return e-mail, delete this communication and destroy all copies. * -- 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
Re: SLES9 Installation - Very Basic
Thanks. This is the method we've been trying to use. But we keep running out of space (unpack's of rpm files). We may try ext3 rather than reiser. I don't know if it will matter. -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] Behalf Of Cameron Seader Sent: Monday, July 18, 2005 5:28 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: SLES9 Installation - Very Basic On Monday 18 July 2005 3:27 pm, Smith, Ann (ISD, IT) wrote: Make a SLES 9 install server, The doc on this is on CD1 under the docu directory. -Cameron I have finally ordered SLES9 for zseries. I ordered media which I have received. There are 6 CD's for SLES9 64-bit for zseries and 6 CD's for 31-bit for s/390. I did not realize there was a 31-bit SLES9. Why did I think SLES9 was 64-bit only? I'm not sure anyone can answer that question. But hopefully they can answer the one regarding setting up an installation server for network installations- What is the best method to use for getting the data off the CD's to disk and installing using NFS? The release notes in /docu on CD1 just say to enter mkdir -p installroot/sles9/CD1 then copy contents of CD1 into the directory mkdir -p installroot/core9/CD1 then copy contents of CD2 into this directory mkdir -p installroot/core9/CD2 then copy contents of CD3 into this directory and so on ... I guess I just use cp command with -x and -a for this method and let yast do the rest. On the other hand the Redbook on LPAR to virtual servers in Two Days (sg246695.pdf) says to use dd to create ISO images and use mksles9root to creat the SLES9 install tree. Which method is preferred? * PRIVILEGED AND CONFIDENTIAL: This communication, including attachments, is for the exclusive use of addressee and may contain proprietary, confidential and/or privileged information. If you are not the intended recipient, any use, copying, disclosure, dissemination or distribution is strictly prohibited. If you are not the intended recipient, please notify the sender immediately by return e-mail, delete this communication and destroy all copies. * -- 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 -- Cameron Seader Novell, Inc. [EMAIL PROTECTED] Tel: 801.861.2686 Cell: 801.913.5992 Fax: 801.861.9478 -- 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
Re: SLES9 Installation - Very Basic
Worked a lot better with ext3. It actually completed and we're ipl'ing. Thanks to all who responded on their method of installation. I did not receive any service packs. I guess I'll need to use the Novell customer care portal. -Original Message- From: Smith, Ann (ISD, IT) Sent: Tuesday, July 19, 2005 9:11 AM To: 'Linux on 390 Port' Subject: RE: SLES9 Installation - Very Basic Thanks. This is the method we've been trying to use. But we keep running out of space (unpack's of rpm files). We may try ext3 rather than reiser. I don't know if it will matter. -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] Behalf Of Cameron Seader Sent: Monday, July 18, 2005 5:28 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: SLES9 Installation - Very Basic On Monday 18 July 2005 3:27 pm, Smith, Ann (ISD, IT) wrote: Make a SLES 9 install server, The doc on this is on CD1 under the docu directory. -Cameron I have finally ordered SLES9 for zseries. I ordered media which I have received. There are 6 CD's for SLES9 64-bit for zseries and 6 CD's for 31-bit for s/390. I did not realize there was a 31-bit SLES9. Why did I think SLES9 was 64-bit only? I'm not sure anyone can answer that question. But hopefully they can answer the one regarding setting up an installation server for network installations- What is the best method to use for getting the data off the CD's to disk and installing using NFS? The release notes in /docu on CD1 just say to enter mkdir -p installroot/sles9/CD1 then copy contents of CD1 into the directory mkdir -p installroot/core9/CD1 then copy contents of CD2 into this directory mkdir -p installroot/core9/CD2 then copy contents of CD3 into this directory and so on ... I guess I just use cp command with -x and -a for this method and let yast do the rest. On the other hand the Redbook on LPAR to virtual servers in Two Days (sg246695.pdf) says to use dd to create ISO images and use mksles9root to creat the SLES9 install tree. Which method is preferred? * PRIVILEGED AND CONFIDENTIAL: This communication, including attachments, is for the exclusive use of addressee and may contain proprietary, confidential and/or privileged information. If you are not the intended recipient, any use, copying, disclosure, dissemination or distribution is strictly prohibited. If you are not the intended recipient, please notify the sender immediately by return e-mail, delete this communication and destroy all copies. * -- 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 -- Cameron Seader Novell, Inc. [EMAIL PROTECTED] Tel: 801.861.2686 Cell: 801.913.5992 Fax: 801.861.9478 -- 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
Debian/390 and LCS support
Hello. We are trying to build a new linux/390 image from Debian/390 3.1.0 (Sarge) and when we select LCS as network interface, at end of initial install we can't access ethernet network, even no error message is received. We did a test using same hardware (9672/OSA card/port) using an old image from Debian/390 3.0.1 (Woody) and we select same LCS option and all runs ok. We can continue installation from Debian FTP site. So seems that something is wrong with LCS module (initrd/kernel/parmfile files downloaded for initial IPL = RAM disk). Anyone has any hint about? Carlos Alberto Bodra Sao Paulo - Brasil -- 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
mksles9root script
We are running SLES8 and SLES9 as z/VM guest. We are about to install SLES9x and I am creating the NFS install directory. Does anyone know if there is a version of the mksles9root script that includes the 3 SLES9x SP2 iso images? Thanks. Peter This Email message and any attachment may contain information that is proprietary, legally privileged, confidential and/or subject to copyright belonging to Pepco Holdings, Inc. or its affiliates (PHI). This Email is intended solely for the use of the person(s) to which it is addressed. If you are not an intended recipient, or the employee or agent responsible for delivery of this Email to the intended recipient(s), you are hereby notified that any dissemination, distribution or copying of this Email is strictly prohibited. If you have received this message in error, please immediately notify the sender and permanently delete this Email and any copies. PHI policies expressly prohibit employees from making defamatory or offensive statements and infringing any copyright or any other legal right by Email communication. PHI will not accept any liability in respect of such communications. -- 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
SLES9 service packs 1 and 2
How are folks getting service pack 2 for SLES9 ? I can only find SP1 from the Novell customer care portal. Are you getting it from a SuSE site? * PRIVILEGED AND CONFIDENTIAL: This communication, including attachments, is for the exclusive use of addressee and may contain proprietary, confidential and/or privileged information. If you are not the intended recipient, any use, copying, disclosure, dissemination or distribution is strictly prohibited. If you are not the intended recipient, please notify the sender immediately by return e-mail, delete this communication and destroy all copies. * -- 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: SLES9 service packs 1 and 2
On Tuesday 19 July 2005 8:59 am, Smith, Ann (ISD, IT) wrote: You will need to logon to portal.suse.com and go to Patch support Database and select versions/products and you can download it from there, just select your architecture and look for SP2 and begin downloading. -Cameron How are folks getting service pack 2 for SLES9 ? I can only find SP1 from the Novell customer care portal. Are you getting it from a SuSE site? * PRIVILEGED AND CONFIDENTIAL: This communication, including attachments, is for the exclusive use of addressee and may contain proprietary, confidential and/or privileged information. If you are not the intended recipient, any use, copying, disclosure, dissemination or distribution is strictly prohibited. If you are not the intended recipient, please notify the sender immediately by return e-mail, delete this communication and destroy all copies. * -- 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 -- Cameron Seader Novell, Inc. [EMAIL PROTECTED] Tel: 801.861.2686 Cell: 801.913.5992 Fax: 801.861.9478 -- 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: SLES9 service packs 1 and 2
The information can be found under CORE of your release on portal. Details: s390: http://portal.suse.com/psdb/d217ab2113221d24870fee955dc766cf.html s390x: http://portal.suse.com/psdb/ad5d207a398847172fbd448b7fc0b61d.html Long story short: http://sdb.suse.de/download/s390/update/SUSE-CORE/9/images/ http://sdb.suse.de/download/s390x/update/SUSE-CORE/9/images/ portal login/password required of course, ~ Daniel -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Smith, Ann (ISD, IT) Sent: Tuesday, July 19, 2005 10:59 AM To: LINUX-390@VM.MARIST.EDU Subject: SLES9 service packs 1 and 2 How are folks getting service pack 2 for SLES9 ? I can only find SP1 from the Novell customer care portal. Are you getting it from a SuSE site? * PRIVILEGED AND CONFIDENTIAL: This communication, including attachments, is for the exclusive use of addressee and may contain proprietary, confidential and/or privileged information. If you are not the intended recipient, any use, copying, disclosure, dissemination or distribution is strictly prohibited. If you are not the intended recipient, please notify the sender immediately by return e-mail, delete this communication and destroy all copies. * -- 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
Re: SLES9 service packs 1 and 2
I downloaded it from SuSE. -- Robert P. Nix Mayo Foundation RO-CE-8-857 200 First Street SW 507-284-0844Rochester, MN 55905 - In theory, theory and practice are the same, but in practice, theory and practice are different. -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Smith, Ann (ISD, IT) Sent: Tuesday, July 19, 2005 9:59 AM To: LINUX-390@VM.MARIST.EDU Subject: SLES9 service packs 1 and 2 How are folks getting service pack 2 for SLES9 ? I can only find SP1 from the Novell customer care portal. Are you getting it from a SuSE site? * PRIVILEGED AND CONFIDENTIAL: This communication, including attachments, is for the exclusive use of addressee and may contain proprietary, confidential and/or privileged information. If you are not the intended recipient, any use, copying, disclosure, dissemination or distribution is strictly prohibited. If you are not the intended recipient, please notify the sender immediately by return e-mail, delete this communication and destroy all copies. * -- 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
3590 tape with SLES 9
Hi all, I am trying to use a 3590 tape with SLES 9, I am able to get the tape module running OK: backup:/dev # lstape TapeNo BusID CuType/Model DevType/Model BlkSize State Op MedStateN/A 0.0.0181 3590/60 3590/11 N/A OFFLINE --- N/A But I cannot communicate with the tape in any way. I have a /proc/device char like this: Character devices: 1 mem 4 ttyS 4 ttysclp 5 /dev/tty 5 /dev/console 5 /dev/ptmx 9 st 10 misc 21 sg 128 ptm 136 pts 162 raw 227 ttyTUB 228 fs3270 254 tape [note the 254] I don't have a /dev/ with major 254. Even if I do a mknod char 254 0 (or mknod char 254 1) I am not able to see the tape. What am I missing? Any ideas would be appreciated. Thanks for your time, Tiago -- 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: Slackware 10.0 install failure - dasd_eckd_mod stuck in initializing state
Yes, this seems to be a frequent, but not 100% consistent problem. The insmod/modprobe command segfaults during the load of the DASD driver(s), leaving the disks unusable. The error message that gets generated usually reports the problem as being in rmmod' though, which just confuses things more. The only things I've found to get around this are to: 1. Not modify the ramdisk size parameter in the kernel parmfile 2. Keep trying I'm hoping that when I build the new initrd for 10.1, that the newer version of the module utilities won't exhibit this behavior. The _truly_ odd thing is that the binaries on the initrd are the exact same ones that get installed on the DASD file system, and in the final environment, this problem never shows up. Mark Post -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Bishop, Peter G Sent: Tuesday, July 19, 2005 2:44 AM To: LINUX-390@VM.MARIST.EDU Subject: Re: Slackware 10.0 install failure - dasd_eckd_mod stuck in initializing state Extremely bad form to answer my own post, but given the timezone differences, I thought everyone might like to know today that persistence pays off, that is, the seventh (or was it eighteenth?) reboot eventually worked, in that the eckd module eventually finished initialising, and the setup command was able to find them, and the rest of the install kicked off. What a very curious turn of events, is all I can say. I'll be repeating this tomorrow, just to make sure (and to fix up a couple of install errors that broke the install anyway). cheers Peter Peter Bishop Mainframe IT Outsourcing Service Delivery EDS Asia-Pacific Phone:+61 2 9378 0113 + mailto:[EMAIL PROTECTED] _ From: Bishop, Peter G Sent: Tuesday, 19 July 2005 3:49 PM To: 'linux-390@vm.marist.edu' Subject: Slackware 10.0 install failure - dasd_eckd_mod stuck in initializing state Hi List, I'm trying to install the Slackware from the site at http://ftp.ibiblio.org/pub/Linux/distributions/slack390/slack390-10.0/ and am at the point where the VM reader install files are IPLed and ready to start formatting DASD. When I first did this, I did a dasdfmt and got a cannot open type error, as in: [EMAIL PROTECTED]:/1 dasdfmt -b 4096 -f /dev/dasda -p dasdfmt -b 4096 -f /dev/dasda -p dasdfmt: Unable to open device /dev/dasda: No such device [EMAIL PROTECTED]:/2 So I tried a few things and finally saw that there was something amiss in driver land: lsmod Module Size Used by reiserfs 243712 0 (unused) jfs 188472 0 (unused) ext3 73168 0 (unused) dasd_diag_mod 5996 0 (autoclean) (unused) jbd52056 0 [ext3] dasd_eckd_mod 57896 1 (initializing) dasd_fba_mod5340 0 (unused) dasd_mod 51036 3 [dasd_diag_mod dasd_eckd_mod dasd_fba_mod] qeth 149528 1 qdio 38224 1 [qeth] [EMAIL PROTECTED]:/5 cat /proc/dasd/devices cat /proc/dasd/devices 0200(none) at ( 94: 0) is dasda : accepted 0201(none) at ( 94: 4) is dasdb : unknown [EMAIL PROTECTED]:/6 I trawled around in the archives, and found this very similar, almost identical incidence, but am none the wiser: http://www2.marist.edu/htbin/wlvtype?LINUX-VM.47871 (actually this link is the end of that particular thread). I've rebooted numerous times, reformatted the minidisks in question both from VM:Secure and native CPFMTXA, enlarged the ramdisk size, re-downloaded the initrd and vminstall images (i.e. the VM reader install image, not the tape install one). I even made these minidisks available to a SLES8 system here and ran a dasdfmt/fdasd on them to make sure they were OK. Even then, they were still not acceptable to the Slackware installer. Now I'm sorta stuck - anyone care to opine on where I went wrong and even better, what I can do to get these disks going? At the moment, I'm in a tight loop doing reboots until it works. Plenty of console logs, etc., for any who wants them. cheers Peter Peter Bishop Mainframe IT Outsourcing Service Delivery EDS Asia-Pacific Phone:+61 2 9378 0113 + mailto:[EMAIL PROTECTED] -- 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
Re: SLES9 service packs 1 and 2
Thank you again! -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] Behalf Of Cameron Seader Sent: Tuesday, July 19, 2005 10:57 AM To: LINUX-390@VM.MARIST.EDU Subject: Re: SLES9 service packs 1 and 2 On Tuesday 19 July 2005 8:59 am, Smith, Ann (ISD, IT) wrote: You will need to logon to portal.suse.com and go to Patch support Database and select versions/products and you can download it from there, just select your architecture and look for SP2 and begin downloading. -Cameron How are folks getting service pack 2 for SLES9 ? I can only find SP1 from the Novell customer care portal. Are you getting it from a SuSE site? * PRIVILEGED AND CONFIDENTIAL: This communication, including attachments, is for the exclusive use of addressee and may contain proprietary, confidential and/or privileged information. If you are not the intended recipient, any use, copying, disclosure, dissemination or distribution is strictly prohibited. If you are not the intended recipient, please notify the sender immediately by return e-mail, delete this communication and destroy all copies. * -- 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 -- Cameron Seader Novell, Inc. [EMAIL PROTECTED] Tel: 801.861.2686 Cell: 801.913.5992 Fax: 801.861.9478 -- 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
Re: PHP issue;
SuSE's response was to wait for the developer in-charge of PHP to incorporate a release of PHP that supports 64bit systems. Meanwhile I continue to sit idle. Would it be a bad thing to download and install the PHP source myself? I don't feel very comfortable with this but right now I don't see any other choice. Does anyone else have a suggestion? Thanks, Doug -Original Message- From: Clark, Douglas Sent: Thursday, July 14, 2005 3:30 PM To: 'LINUX-390@VM.MARIST.EDU' Cc: Clark, Douglas Subject: RE: PHP issue; Any experts The version of PHP I am running on the mainframe is 4.3.4 which is what came from SuSE. The release notes from PHP version 4.3.5 states a number of fixes were applied to correct 64bit issues and I hope by upgrading to a later version I will correct my problem. I have a maintenance contract with SuSE/Novell (I get to download the patches) but not a support contract. Does downloading the latest source code and installing it violate the maintenance contract? Will I get patches for versions of PHP that I am no longer running? I have always relied on the download and what is supplied directly from SuSE in the past so this is new ground for me. TIA Doug -Original Message- From: Clark, Douglas Sent: Wednesday, July 13, 2005 8:27 PM To: LINUX-390@VM.MARIST.EDU Cc: Clark, Douglas Subject:PHP issue; Any experts I have run into a problem running PHP code using preg_match_all. I'm racking my brain trying to figure out a solution. Maybe someone else knows the answer? I have two boxes that I'm working on, and I've moved some PHP code from one box using PHP version 4.2.2 (Intel running Red Hat) to another using PHP version 4.3.4 (z890 running SuSE S390x). -- 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
SLES9 Install VIA FTP
Has anyone attempted to install SLES9 via FTP where the FTP server was a z/OS platform? If you have successfully accomplished this I would like to compare notes about your success and my failure. Jim Chappell 503-745-7841 503-349-5603(cell) MS:C3E-IDS [EMAIL PROTECTED] - My other PC is a S/390 running z/OS and LINUX - The floggings will continue until morale improves. -- 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: PHP issue;
On Maw, 2005-07-19 at 08:36 -0700, [EMAIL PROTECTED] wrote: SuSE's response was to wait for the developer in-charge of PHP to incorporate a release of PHP that supports 64bit systems. Meanwhile I continue to sit idle. Would it be a bad thing to download and install the PHP source myself? I don't feel very comfortable with this but right now I don't see any other choice. Does anyone else have a suggestion? You can build php in a different location to the default one when building from source and have several PHP versions installed then using the file name endings to select php3,4,4andabit etc. Alan -- 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: PHP issue;
-Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED] Sent: Tuesday, July 19, 2005 10:37 AM To: LINUX-390@VM.MARIST.EDU Subject: Re: PHP issue; SuSE's response was to wait for the developer in-charge of PHP to incorporate a release of PHP that supports 64bit systems. Meanwhile I continue to sit idle. Would it be a bad thing to download and install the PHP source myself? I don't feel very comfortable with this but right now I don't see any other choice. Does anyone else have a suggestion? Thanks, Doug Personal opinion time. If it were me, I'd have done exactly the same thing. It is not as if you are really unsupported. PHP does not affect the kernel or modules or ... It only affects PHP and Apache. If you have a problem that is not PHP, still report it back to SuSE. If SuSE (or anybody else's) attitude is you made a change, so go roll a hoop! (hopefully not likely), then I'd basically tell them no fix, no money! Again, I really don't see SuSE doing this. It would be like IBM saying You run CA-1 on z/OS and are having a problem with ISPF? Well, we cannot help you because you have non IBM software installed! If you have a problem with PHP, you can still report it directly back to the maintainer. They may well say we don't have a zSeries for testing, but if you have given them really good debugging information, I'll bet they would a least give a look. It may have an effect on other 64-bit systems, such as the EM64T from Intel or the AMD Athlon64 or Opteron. Again, personal opinion. But then, I maintain what __used to be__ a RH 9.0 Linux/Intel system at home from source since RH stopped maintaining or updating anything other than RHEL. I don't use Fedora, but I guess that I could. Actually, I have SuSE 9.0 Professional on my laptop, so if I upgrade the other Linux, it will be to SuSE. -- John McKown Senior Systems Programmer UICI Insurance Center Information Technology This message (including any attachments) contains confidential information intended for a specific individual and purpose, and its' content is protected by law. If you are not the intended recipient, you should delete this message and are hereby notified that any disclosure, copying, or distribution of this transmission, or taking any action based on it, is strictly prohibited. -- 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
Idea from the Hercules list
One thing that appears pretty often in the Linux world are ISO images. These are a bit tough to work with, in the absence of an already functional system, on the mainframe. So the idea would be to splat the ISO image onto FBA disk and then define a minidisk to cover just the extents used by the image, and then treat the image from Linux as a raw FBA device with an iso9660 filesystem on it. That should work, right? I'm not actually sure that it's an at all useful idea, though. Adam -- 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: Idea from the Hercules list
So the idea would be to splat the ISO image onto FBA disk and then define a minidisk to cover just the extents used by the image, and then treat the image from Linux as a raw FBA device with an iso9660 filesystem on it. I've done this. Works. Been thinking about it for YEARS, and finally got it done. The way it turned out was easier than I originally imagined. The result is an ISO formatted CD which can be eyeballed on a Windows PC (or any Linux machine) and can also be byte-for-byte copied to FBA media and IPLed. If Hercules would map a CD-ROM to a 9336 or 3370, Herc could boot directly from the CD. (But at this time, Herc requires a byte-for-byte copy of the CD into an ordinary disk file, then boot.) [sigh] It uses FBA IPL, rather than SCSI/SAN IPL. (I do not know if SCSI/SAN IPL would render FBA IPL unusable, but hope to see.) I found that the ISO filesystem reserves some 32K at the start. (maybe 64K; ran empirical checks twice with different results; then too, I may have messed up my octal kon-ver-zhuns) I sized an FBA disk to look like a CD (about 600M) and defined a partition starting after 64K and running up to the 512M line. (Wrestling with 'fdisk', the nearest start boundary was 1M.) Then defined the boot partition there (starting at 512M). I put an EXT2 FS into that main partition just for work space. THIS is where things got easier than I originally imagined. With EXT2 root in the big partition and EXT2 boot in the after 512 partition, you get a bootable FBA disk. Duh! So I now have two of these, and copy parts of the bootable EXT2-on-FBA over to the ISO-on-FBA, along with the .iso file created by 'mkisofs'. It looks like this: 0CD1 600M . 0CD2 600M IPL text at 0 . IPL text at 0 part 2 at 1M .. part 2 at 1M part 1 at 512M part 1 at 512M In this case, the partition numbers are out of order. Ignore 'fdisk' if it complains about that. CD1 gets two EXT2 FS, root in part 2 and /boot in part 1. Run 'zipl' and the IPL text gets laid down at offset zero rendering the disk perfectly bootable. Next, make an ISO FS of that root filesystem (I kept boot mounted under it, but you don't strictly have to), then copy first 64K of CD1 to same range on CD2 resulting .iso file, SKIPPING 64K!, to offset 64K of CD2 part 1 of CD1 to part 1 of CD2 To summarize: take the working IPL text from CD1 and the physical content of its partition 1, then combine with the .iso file. Voi-la! Bootable CD. -- R; -- 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: SLES9 Installation - Very Basic
test - can't seem to append to the list Mike MacIsaac [EMAIL PROTECTED] (845) 433-7061 -- 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: SLES9 Installation - Very Basic
Hello from Gregg C Levine I see you fine Mike. What's the system telling you? - Gregg C Levine [EMAIL PROTECTED] --- Remember the Force will be with you. Always. Obi-Wan Kenobi -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Michael MacIsaac Sent: Tuesday, July 19, 2005 1:37 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: [LINUX-390] SLES9 Installation - Very Basic test - can't seem to append to the list Mike MacIsaac [EMAIL PROTECTED] (845) 433-7061 -- 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
SLES9 install under VM
Hey folks, I'm new to the Linux world (but not to VM) and trying to install SLES9 un z/VM 5.1. We have a guest defined with a CTC coupled to the TCPIP machine. During the install process the ctc becomes inoperative when we try to attach to the FTP server. TCPIP message indicates DTCCTC091E CTCA device DEV8810: Received DEVICEend interrupt on device 8810 -- probable CTCA restart I have tried lots of different things but can't get by this. Has anybody done an install of this type? Any suggestions where I can look? Bob Bates Citigroup Technology Infrastructure 916-374-5017 -- 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: SLES9 install under VM
I would definitely suggest working with the Virtual Switch. It is much easier to configure and work with. Bates, Bob wrote: Hey folks, I'm new to the Linux world (but not to VM) and trying to install SLES9 un z/VM 5.1. We have a guest defined with a CTC coupled to the TCPIP machine. During the install process the ctc becomes inoperative when we try to attach to the FTP server. TCPIP message indicates DTCCTC091E CTCA device DEV8810: Received DEVICEend interrupt on device 8810 -- probable CTCA restart I have tried lots of different things but can't get by this. Has anybody done an install of this type? Any suggestions where I can look? Bob Bates Citigroup Technology Infrastructure 916-374-5017 -- 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 -- Rich Smrcina VM Assist, Inc. Main: (262)392-2026 Cell: (414)491-6001 Ans Service: (360)715-2467 rich.smrcina at vmassist.com Catch the WAVV! http://www.wavv.org WAVV 2006 - Chattanooga, TN - April 7-11, 2006 -- 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: SLES9 Installation - Very Basic
I have updated the mksles9script for SP2 on http://mikemacisaac.com/mksles9root (my longer appends seem to be getting dropped) Mike MacIsaac [EMAIL PROTECTED] (845) 433-7061 -- 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: SLES9 and VM Shared Kernel
Hi list, i just want to give a final update for this problem. Some weeks ago, i tried to implement the VM shared kernel using SLES9. But without success. So i asked SUSE, but SuSE does not support the VM shared kernel !!! They said that if i want to use this option, i will have to install a native kernel from kernel.org. Regards, Tobias -- 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: SLES9 install under VM
Fully aggreed and I'd underline Richs statement :-) VSWITCH is my favored solution for implementing zLinux-guests ... ciao Lutz - Lutz Hamann BETA Systems Software AG z/OS System Engineering - Rich Smrcina [EMAIL PROTECTED] omTo Sent by: Linux on LINUX-390@VM.MARIST.EDU 390 Port cc [EMAIL PROTECTED] IST.EDU Subject Re: SLES9 install under VM 19.07.2005 20:47 Please respond to Linux on 390 Port [EMAIL PROTECTED] IST.EDU I would definitely suggest working with the Virtual Switch. It is much easier to configure and work with. Bates, Bob wrote: Hey folks, I'm new to the Linux world (but not to VM) and trying to install SLES9 un z/VM 5.1. We have a guest defined with a CTC coupled to the TCPIP machine. During the install process the ctc becomes inoperative when we try to attach to the FTP server. TCPIP message indicates DTCCTC091E CTCA device DEV8810: Received DEVICEend interrupt on device 8810 -- probable CTCA restart I have tried lots of different things but can't get by this. Has anybodydone an install of this type? Any suggestions where I can look? Bob Bates Citigroup Technology Infrastructure 916-374-5017 -- 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 -- Rich Smrcina VM Assist, Inc. Main: (262)392-2026 Cell: (414)491-6001 Ans Service: (360)715-2467 rich.smrcina at vmassist.com Catch the WAVV! http://www.wavv.org WAVV 2006 - Chattanooga, TN - April 7-11, 2006 -- 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
YOU server
At one time I activated the YOU server on our SLES9 guest. I want to remove it now. I find that it has stashed away tons of rpms under /var/s390. I am inclined to trash and reclaim the space. Anyone done this? Any adverse effects? __ Ranga Nathan / CSG Systems Programmer - Specialist; Technical Services; BAX Global Inc. Irvine-California Tel: 714-442-7591 Fax: 714-442-2840 -- 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
V=R?
Hi I have one question about running linux on z/VM and z/VM memory management. My current environment (production) Total real memory = 12GB Total page volumes = +- 5GB Total memory allocation to linux servers (guests) = 7104MB (+- 7GB) Paging usage = 40 - 50% (2GB - 2.5GB) XSTORE = 2GB (just recently added after noticing paging did happen in z/VM though we have enough real memory) Main storage used by z/VM is only 5GB (meaning at any one time, 2 GB or more will be swapped off) Operating Systems: z/VM 4.4 SLES 8.1 SP4 (31-bit) I observed that by default, memory mode for linux guest is V=V. Hence, z/VM takes control of memory management. Since I have enough real memory, why z/VM still does the paging? Any way to avoid paging on z/VM. I would prefer to let linux server to have real memory (V=R). Any comments on this? And how to set it in the user direct? Any fine-tuning can be done? I also heard that V=R will not be supported in z/VM 5.1. Is it true? Thanks for your attention. Regards, Johnny Tan Sent via the AlumMail https://alumni.nus.edu.sg -- 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
