New to Linux
I have downloaded the Debian 40r5 for S390 ISO and have burned it onto CD. When I load the CD into the HMC (zSeries z9BC) and try to do the "Load from CD/DVD" operation I get: ""An error has occurred while trying to obtain a list of the software that can be loaded." I am not sure if this is an HMC or a Debian message. It has a message number of ACT36201 but I cannot find a reference to that message. Does anyone have an idea what I have done wrong? Thanks, ..Larry Larry D. Martin Mainframe Systems Support Office of Information Technology and Communications 301.883.7335 .. This E-mail and any of its attachments may contain Prince George’s County Government or Prince George's County 7th Judicial Circuit Court proprietary information, which is privileged and confidential. This E-mail is intended solely for the use of the individual or entity to which it is addressed. If you are not the intended recipient of this E-mail, you are hereby notified that any dissemination, distribution, copying, or action taken in relation to the contents of and attachments to this E-mail is strictly prohibited and may be unlawful. If you have received this E-mail in error, please notify the sender immediately and permanently delete the original and any copy of this E-mail and any printout.
Disk Complete Device Name
I am installing Debian Linux on S390 for the first time. I am at the point of the install where it says: Choose Disk: The instructions say to enter the complete device number. I provide the 4 digit ucb address and it says "an invalid device number has been chosen". What does this mean? Thanks, ..Larry Larry D. Martin Mainframe Systems Support Office of Information Technology and Communications 301.883.7335 .. This E-mail and any of its attachments may contain Prince George’s County Government or Prince George's County 7th Judicial Circuit Court proprietary information, which is privileged and confidential. This E-mail is intended solely for the use of the individual or entity to which it is addressed. If you are not the intended recipient of this E-mail, you are hereby notified that any dissemination, distribution, copying, or action taken in relation to the contents of and attachments to this E-mail is strictly prohibited and may be unlawful. If you have received this E-mail in error, please notify the sender immediately and permanently delete the original and any copy of this E-mail and any printout.
IODF
I have an IOCDS which defines 8 paths (CHPIDs) to our disk devices. One (and only one) of those CHPIDs is not properly assigned to my Linux LP (the other 7 are correct. Does anyone know if that will keep the Linux kernel from recognizing the available disks? I only have 2 devices permitted to the Linux LP. Thanks, ..Larry Larry D. Martin Mainframe Systems Support Office of Information Technology and Communications 301.883.7335 .. This E-mail and any of its attachments may contain Prince George’s County Government or Prince George's County 7th Judicial Circuit Court proprietary information, which is privileged and confidential. This E-mail is intended solely for the use of the individual or entity to which it is addressed. If you are not the intended recipient of this E-mail, you are hereby notified that any dissemination, distribution, copying, or action taken in relation to the contents of and attachments to this E-mail is strictly prohibited and may be unlawful. If you have received this E-mail in error, please notify the sender immediately and permanently delete the original and any copy of this E-mail and any printout.
Trying To Get Started
I am trying to install Linux in an LPAR on a Z9. This is a County government so no money is available for z/VM. I downloaded Debian 405 some time ago and that loads up to the point that it tries to continue the install from a mirror site. At this point all I can get is "Server not there or kernel is unavailable". So I tried to download 503 from the default site and the ftp starts and then just stops. So I tried a different site (carroll.aset.psu.edu) and that site had 501 for download. I downloaded CD1 and loaded it - it very quickly gets a kernel failure and a Disabled Wait. What site and what release should I use to burn a CD1 and then what site should I use to complete the installation? Thanks,..Larry Larry D. Martin Mainframe Systems Support Office of Information Technology and Communications 301.883.7335 This E-mail and any of its attachments may contain Prince George’s County Government or Prince George's County 7th Judicial Circuit Court proprietary information, which is privileged and confidential. This E-mail is intended solely for the use of the individual or entity to which it is addressed. If you are not the intended recipient of this E-mail, you are hereby notified that any dissemination, distribution, copying, or action taken in relation to the contents of and attachments to this E-mail is strictly prohibited and may be unlawful. If you have received this E-mail in error, please notify the sender immediately and permanently delete the original and any copy of this E-mail and any printout.
RE: Trying To Get Started
Thank you for the feed back. I appears that without VM, I am going to have to IPL initially from tape. I have seen instructions on building the tape, so it should work. Thanks again..Larry -Original Message- From: Frans Pop [mailto:elen...@planet.nl] Sent: Wednesday, September 23, 2009 11:38 AM To: debian-s390@lists.debian.org Subject: Re: Trying To Get Started First of all, when you ask a question on a mailing list, please always follow up to that mailing list instead of replying to the person who replied to you. On Wednesday 23 September 2009, Martin, Larry D wrote: > I downloaded 5.0.3 from mirrors.usc.edu and that seemed to work fine. I > then burned CD1 (using Easy CD Creator). I then use the HMC and "Load > from CD/ROM". > > I get the following: > > [17179570.168401] Kernel panic - not syncing: VFS: Unable to mount root > fs on unknown-block(1,0) > > Can I not use this technique to install Debian? What is the proper > methodology? I have just confirmed that booting from CD does not work. We'll have to look into that. As I said in my previous mail, it is a rather unusual installation method (only confirmed by the fact that nobody reported it is broken, and has been for quite some time). Please use the "generic" images I linked to in my previous mail instead. Unfortunately I cannot give you detailed instructions myself on how exactly to use them as I'm only familiar with the Hercules emulator [1] and not with real hardware. Cheers, FJP [1] On hercules it is done by defining a '3505' type device as kernel.debian parmfile.debian initrd.debian autopad eof and IPLing off that. -- To UNSUBSCRIBE, email to debian-s390-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org This E-mail and any of its attachments may contain Prince George’s County Government or Prince George's County 7th Judicial Circuit Court proprietary information, which is privileged and confidential. This E-mail is intended solely for the use of the individual or entity to which it is addressed. If you are not the intended recipient of this E-mail, you are hereby notified that any dissemination, distribution, copying, or action taken in relation to the contents of and attachments to this E-mail is strictly prohibited and may be unlawful. If you have received this E-mail in error, please notify the sender immediately and permanently delete the original and any copy of this E-mail and any printout.
RE: Future of the s390 port
You download the ISO file for the S390 distribution and burn the CD. You then use the the CD in the HMC and use the "Load from CD-ROM or Server method" (specify the directory as "/boot". When I did this a few weeks ago I got a "kernel panic" as I reported on this list. The tape files can be written to a tape and then IPL directly from that tape drive; however, that drive must be offline to ALL other LPARs on the system. Thanks, .Larry -Original Message- From: Stephen Powell [mailto:zlinux...@wowway.com] Sent: Friday, October 09, 2009 3:23 PM To: debian-s390@lists.debian.org Subject: Re: Future of the s390 port > > That would be great. Please see [1] for details. If you need additional > info, just ask. > > Cheers, > FJP > > [1] http://lists.debian.org/debian-s390/2009/09/msg00027.html > It sounds to me like you are asking for information on how to create a mainframe-bootable CD. I'm afraid I don't know the answer. If you have a specific .iso image that you want me to download and try to see if it will boot, I can do that for you. But I don't pretend to know how to create one. I can see, though, from the link above, that you are using the "generic" sub-architecture files. Have you tried using the "tape" files? The reason I ask is that, on the Multiprise 3000, the CD-ROM could be used as an emulated tape or via the "Load from CD-ROM or Server" method. I just wonder if the tape files are what you should use in that .ins file. Hey it's just a guess, but it's worth a try. -- To UNSUBSCRIBE, email to debian-s390-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org This E-mail and any of its attachments may contain Prince George’s County Government or Prince George's County 7th Judicial Circuit Court proprietary information, which is privileged and confidential. This E-mail is intended solely for the use of the individual or entity to which it is addressed. If you are not the intended recipient of this E-mail, you are hereby notified that any dissemination, distribution, copying, or action taken in relation to the contents of and attachments to this E-mail is strictly prohibited and may be unlawful. If you have received this E-mail in error, please notify the sender immediately and permanently delete the original and any copy of this E-mail and any printout.
Installation Question
Does anyone know if the problem installing Debian on zSeries from CD-ROM has been corrected? Thanks, Larry Larry D. Martin Mainframe Systems Support Office of Information Technology and Communications 301.883.7335 This E-mail and any of its attachments may contain Prince George’s County Government or Prince George's County 7th Judicial Circuit Court proprietary information, which is privileged and confidential. This E-mail is intended solely for the use of the individual or entity to which it is addressed. If you are not the intended recipient of this E-mail, you are hereby notified that any dissemination, distribution, copying, or action taken in relation to the contents of and attachments to this E-mail is strictly prohibited and may be unlawful. If you have received this E-mail in error, please notify the sender immediately and permanently delete the original and any copy of this E-mail and any printout.
RE: Installation Question
The S390 directory appears to me to be empty this week. There was stuff there last week (can I point to that?). Thanks,.Larry -Original Message- From: Frans Pop [mailto:elen...@planet.nl] Sent: Friday, December 11, 2009 11:54 AM To: debian-s390@lists.debian.org Subject: Re: Installation Question Frans Pop wrote: > Martin, Larry D wrote: >> Does anyone know if the problem installing Debian on zSeries from CD-ROM >> has been corrected? > > Yes, it has. Hm. Except that for Lenny (stable) we haven't had any new CD builds since it was fixed. That will only happen at the next stable point release (which is overdue). The weekly built CD for Squeeze [1] should work though and should be usable to install Lenny too. You'll need to change the debconf priority to "medium" before the mirror selection step to get a choice of which release to install. Cheers, FJP [1] http://cdimage.debian.org/cdimage/weekly-builds/s390/iso-cd/ -- To UNSUBSCRIBE, email to debian-s390-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org This E-mail and any of its attachments may contain Prince George’s County Government or Prince George's County 7th Judicial Circuit Court proprietary information, which is privileged and confidential. This E-mail is intended solely for the use of the individual or entity to which it is addressed. If you are not the intended recipient of this E-mail, you are hereby notified that any dissemination, distribution, copying, or action taken in relation to the contents of and attachments to this E-mail is strictly prohibited and may be unlawful. If you have received this E-mail in error, please notify the sender immediately and permanently delete the original and any copy of this E-mail and any printout.
RE: Installation Question
Thanks..Larry -Original Message- From: Frans Pop [mailto:elen...@planet.nl] Sent: Wednesday, December 16, 2009 11:59 AM To: debian-s390@lists.debian.org Subject: Re: Installation Question Martin, Larry D wrote: > The S390 directory appears to me to be empty this week. Yes, unfortunately there was a build error this week (which sometimes happens for daily and weekly builds). The images should be back next Monday. > There was stuff there last week (can I point to that?). Afraid not. Full CD/DVD images just take too much space to keep multiple versions around. Cheers, FJP -- To UNSUBSCRIBE, email to debian-s390-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org This E-mail and any of its attachments may contain Prince George’s County Government or Prince George's County 7th Judicial Circuit Court proprietary information, which is privileged and confidential. This E-mail is intended solely for the use of the individual or entity to which it is addressed. If you are not the intended recipient of this E-mail, you are hereby notified that any dissemination, distribution, copying, or action taken in relation to the contents of and attachments to this E-mail is strictly prohibited and may be unlawful. If you have received this E-mail in error, please notify the sender immediately and permanently delete the original and any copy of this E-mail and any printout.
RE: Installation Question
The iso directory for s390 is empty (as far as I can tell) again this week. Thanks, .Larry -Original Message- From: Frans Pop [mailto:elen...@planet.nl] Sent: Wednesday, December 16, 2009 11:59 AM To: debian-s390@lists.debian.org Subject: Re: Installation Question Martin, Larry D wrote: > The S390 directory appears to me to be empty this week. Yes, unfortunately there was a build error this week (which sometimes happens for daily and weekly builds). The images should be back next Monday. > There was stuff there last week (can I point to that?). Afraid not. Full CD/DVD images just take too much space to keep multiple versions around. Cheers, FJP -- To UNSUBSCRIBE, email to debian-s390-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org This E-mail and any of its attachments may contain Prince George’s County Government or Prince George's County 7th Judicial Circuit Court proprietary information, which is privileged and confidential. This E-mail is intended solely for the use of the individual or entity to which it is addressed. If you are not the intended recipient of this E-mail, you are hereby notified that any dissemination, distribution, copying, or action taken in relation to the contents of and attachments to this E-mail is strictly prohibited and may be unlawful. If you have received this E-mail in error, please notify the sender immediately and permanently delete the original and any copy of this E-mail and any printout.
RE: Installation Question
Thank you. I downloaded and started the install. All goes well until the install asks which site I want to use. I chose ftp.us.debian.org (and a couple of others) and I get "...site either not available or does not contain a valid release..." What site should I chose to complete the install? Thanks again, Larry -Original Message- From: Frans Pop [mailto:elen...@planet.nl] Sent: Monday, December 21, 2009 4:13 PM To: debian-s390@lists.debian.org Subject: Re: Installation Question On Monday 21 December 2009, Frans Pop wrote: > Martin, Larry D wrote: > > The iso directory for s390 is empty (as far as I can tell) again this > > week. > > Unfortunately the server that hosts the Debian Installer images for s390 > looks to be down today, which means that the server that builds the CD > images could not download them and so the weekly CD build failed. > > There's nothing much I can do about that. Sorry for the inconvenience. I've just created a "bootable" s390 CD for Lenny. You can download it from: http://cdimage.debian.org/cdimage/unofficial/fjp/ Cheers, FJP -- To UNSUBSCRIBE, email to debian-s390-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org This E-mail and any of its attachments may contain Prince George’s County Government or Prince George's County 7th Judicial Circuit Court proprietary information, which is privileged and confidential. This E-mail is intended solely for the use of the individual or entity to which it is addressed. If you are not the intended recipient of this E-mail, you are hereby notified that any dissemination, distribution, copying, or action taken in relation to the contents of and attachments to this E-mail is strictly prohibited and may be unlawful. If you have received this E-mail in error, please notify the sender immediately and permanently delete the original and any copy of this E-mail and any printout.
RE: Installation Question
Thank you. I am now in the SSH session. I have made it to "Configure Disks" and am not sure what the format of the address is. I have two volumes 108E and 108F and I tried 0.0.108E but that failed. Any suggestions? On the first menu on SSH I chose "Start Installation". Should I have chosen to Start a Shell? Thanks, Larry -Original Message- From: Frans Pop [mailto:elen...@planet.nl] Sent: Tuesday, December 22, 2009 5:47 PM To: debian-s390@lists.debian.org Subject: RE: Installation Question Martin, Larry D wrote: > All goes well until the install asks which site I want to use. I chose > ftp.us.debian.org (and a couple of others) and I get "...site either not > available or does not contain a valid release..." The ftp.us.debian.org mirror works perfectly for me (using the same CD). Sounds as if you don't have an internet connection because of incorrect networking setup. But that's hard to tell without knowing the actual errors. Did you already switch to using an SSH session to complete the installation, or are you still using the text interface from the console? If you're still on the console you can see them by choosing "Execute a shell" from the installer's main menu and typing 'cat /var/log/syslog'. If you're using SSH, you can see the syslog by starting a second session and choosing the "Start shell" option and then use either cat or nano to view the syslog. If you need help, please copy and paste the full syslog (if possible). -- To UNSUBSCRIBE, email to debian-s390-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org This E-mail and any of its attachments may contain Prince George’s County Government or Prince George's County 7th Judicial Circuit Court proprietary information, which is privileged and confidential. This E-mail is intended solely for the use of the individual or entity to which it is addressed. If you are not the intended recipient of this E-mail, you are hereby notified that any dissemination, distribution, copying, or action taken in relation to the contents of and attachments to this E-mail is strictly prohibited and may be unlawful. If you have received this E-mail in error, please notify the sender immediately and permanently delete the original and any copy of this E-mail and any printout.
RE: Installation Question
It appears that Debian does not think the disks are usable because they are "reachable" from another partition. When I did the IOCDS for our machine I actually had the two volumes for Linux reachable from four LPARs. One of the four is linux, one is inactive, one has the volumes offline, and the last one is a coupling facility LPAR. Does anyone have an IOCDS that shows 3390's properly defined for Debian? Or any other suggestions? The disks are definitely reachable from the LPAR into which I am loading Linux. Thanks, .Larry -Original Message- From: Frans Pop [mailto:elen...@planet.nl] Sent: Wednesday, December 23, 2009 9:33 AM To: debian-s390@lists.debian.org Subject: Re: Installation Question A: http://en.wikipedia.org/wiki/Top_post Q: Were do I find info about this thing called top-posting? A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing in e-mail? A: No. Q: Should I include quotations after my reply? Martin, Larry D wrote: > I am now in the SSH session. I have made it to "Configure Disks" and am > not sure what the format of the address is. I have two volumes 108E and > 108F and I tried 0.0.108E but that failed. > > Any suggestions? No idea. For me the available dasds have always been listed and I could just select them. AFAICT the last format should be correct. You may have to check that the devices really are available. I don't think I can help much with this. Maybe this walktrough of an installation in the Hercules s390 emulator will help for reference: http://www.josefsipek.net/docs/s390-linux/hercules-s390.html > On the first menu on SSH I chose "Start Installation". Should I have > chosen to Start a Shell? I assume you mean "Start menu", but that's correct. The shell is available mainly for troubleshooting. You can use it to enter commands manually, check the syslog, etc. You should only have *one* menu SSH session open, but you can have multiple shell sessions if you want. Cheers, FJP -- To UNSUBSCRIBE, email to debian-s390-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org This E-mail and any of its attachments may contain Prince George’s County Government or Prince George's County 7th Judicial Circuit Court proprietary information, which is privileged and confidential. This E-mail is intended solely for the use of the individual or entity to which it is addressed. If you are not the intended recipient of this E-mail, you are hereby notified that any dissemination, distribution, copying, or action taken in relation to the contents of and attachments to this E-mail is strictly prohibited and may be unlawful. If you have received this E-mail in error, please notify the sender immediately and permanently delete the original and any copy of this E-mail and any printout.
RE: Installation Question
Steve,
Thanks.
>If I remember right,
>there is an initial screen which displays all the DASD devices it
>recognizes.
Unfortunately the list is empty (recognizes none) and then prompts me to enter
an address, which, of course fails.
Thanks again, ..Larry
-Original Message-
From: Stephen Powell [mailto:zlinux...@wowway.com]
Sent: Wednesday, December 23, 2009 11:41 AM
To: debian-s390@lists.debian.org
Subject: RE: Installation Question
On 2009-12-23, Larry Martin wrote:
> It appears that Debian does not think the disks are usable because
> they are "reachable" from another partition.
> When I did the IOCDS for our machine I actually had the two volumes
> for Linux reachable from four LPARs. One of the four is linux, one
> is inactive, one has the volumes offline, and the last one is a
> coupling facility LPAR.
> Does anyone have an IOCDS that shows 3390's properly defined for Debian?
> Or any other suggestions? The disks are definitely reachable from the
> LPAR into which I am loading Linux.
> Thanks, .Larry
Larry,
I'm not sure what you mean by "reachable". Do you mean shared? Here
are some excerpts from our IOCP statements for a z890 (2086) with an IBM
DS6800 1750-511 RAID box for our DASD, which is attached to the host via
four FICON chpids. The RAID box defines 512 devices: 6100-61FF and
6300-63FF. 6100-6112 and 6300-6312 (38 devices) are emulated 3390-9
devices. The rest are 3390-3 devices. None of these devices support
PVA. These are IOCP statements generated by HCD/HCM running under z/OS,
which are slightly different in format from the native IOCP format. But
you'll get the idea.
--
TITLE 'SYS1.IODF01 - 2006-10-10 12:08:22 '
*
ID NAME=DOLC01,UNIT=2086,MODEL=A04,MODE=LPAR,LEVEL=H040331, *
SCR='DOLC01 06-10-1012:08:22SYS*
1IODF01 '
RESOURCE PARTITION=((CSS(0),(MVSPROD,1),(MVSTECH,3),(MVSTEST,2*
),(ZOSPROD,4),(ZVMPROD,5))),MAXDEV=((CSS(0),64512)),*
DESCL=('MVS PRODUCTION LPAR','','MVS TES*
T LPAR','',''),USAGE=(OS,OS,OS,OS,OS)
.
.
.
CHPID PATH=(CSS(0),20),SHARED,*
PARTITION=((MVSPROD,MVSTECH,MVSTEST,ZOSPROD,ZVMPROD),(=)*
),DESC='IBM DS6800 DASD',TYPE=FC,PCHID=120
CHPID PATH=(CSS(0),21),SHARED,*
PARTITION=((MVSPROD,MVSTECH,MVSTEST,ZOSPROD,ZVMPROD),(=)*
),DESC='IBM DS6800 DASD',TYPE=FC,PCHID=121
.
.
.
CHPID PATH=(CSS(0),30),SHARED,*
PARTITION=((MVSPROD,MVSTECH,MVSTEST,ZOSPROD,ZVMPROD),(=)*
),DESC='IBM DS6800 DASD',TYPE=FC,PCHID=130
CHPID PATH=(CSS(0),31),SHARED,*
PARTITION=((MVSPROD,MVSTECH,MVSTEST,ZOSPROD,ZVMPROD),(=)*
),DESC='IBM DS6800 DASD',TYPE=FC,PCHID=131
.
.
.
CNTLUNIT CUNUMBR=6100,PATH=((CSS(0),20,30,21,31)),*
UNITADD=((00,256)),SHARED=N,CUADD=1,SERIAL='13-AFALA', *
DESC='DS6800 1750-511 Control Unit',UNIT=1750
IODEVICE ADDRESS=(6100,256),UNITADD=00,CUNUMBR=(6100),STADET=Y*
,SERIAL='13-AFALA', *
DESC='DS6800 1750-511 mod-9 && mod-3s',UNIT=3390
CNTLUNIT CUNUMBR=6300,PATH=((CSS(0),21,31,20,30)),*
UNITADD=((00,256)),SHARED=N,CUADD=3,SERIAL='13-AFALA', *
DESC='DS6800 1750-511 Control Unit',UNIT=1750
IODEVICE ADDRESS=(6300,256),UNITADD=00,CUNUMBR=(6300),STADET=Y*
,SERIAL='13-AFALA',
DESC='DS6800 1750-511 mod-9 && mod-3s',UNIT=3390
--
The above IOCP definitions use the ESCON Multi-Image Facility (EMIF)
to allow the DASD devices to be shared by all LPARs. (EMIF works for
FICON as well as ESCON.)
If a normal mainframe operating system, such as z/OS or z/VM, can "see"
the DASD, then Linux should be able to "see" it too. If not, then you're
probably doing something wrong in the installation. If I remember right,
there is an initial screen which displays all the DASD devices it
recognizes. You have to explicitly select all the devices you are going
to use on that screen, though some of them may be pre-selected. Then
there is another screen later on where you can create partitions,
assign mount points, etc. If you don't select the devices on the first
screen, they won't be available on the second screen.
Also, keep in mind that (a) the Debian installer supports only CKD DASD
devices and (b) the Debian installer supports only the cdl format
(compatible disk layout). You said that your devices were 3390s, which
are CKD devices; so that should be OK.
I do all of my Linux installs in a virtu
FW: Installation Question
Update: With no other changes Suse 10.1 recognizes the disk. What is the difference in the install processes - as it relates to disk discovery? Thanks, ..Larry -Original Message- From: Stephen Powell [mailto:zlinux...@wowway.com] Sent: Wednesday, December 23, 2009 1:17 PM To: debian-s390@lists.debian.org Subject: RE: Installation Question On 2009-12-23, Marry Martin wrote: > Unfortunately the list is empty (recognizes none) and then prompts me > to enter an address, which, of course fails. > > Thanks again, ..Larry When you get to the screen that is supposed to show the recognized dasd devices, and nothing shows up, open another SSH session in another window on your desktop. Login as "installer" using the password that you specified earlier, but don't run the installer menu. Instead, escape to a shell. First of all, make sure that the dasd drivers are loaded # lsmod You should see both "dasd_mod" and "dasd_eckd_mod" as loaded modules. If not, manually load them with modprobe. If that doesn't work, you've got serious problems. Did you mess with the installer components to be downloaded? Did you deselect some of them? If both modules are loaded, issue # cd /sys/bus/ccw/devices # ls -Al|more You should see a directory listed for each device number recognized, regardless of whether it is dasd or not. It will be of the form 0.0., where "" is a hexadecimal number. (Note that hex digits a-f are lower case!) See if the device is listed there. If it is, cd to that directory. For example, # cd 0.0.108e # ls -Al You can check the values of these variables with "cat". For example, # cat online If it responds with "0", then the device was recognized, but it is offline. Check the "use_diag" and "readonly" variables to make sure they are zero as well, then try to set the device online with # echo 1 >online Then verify that it came online with another # cat online This time, it should say "1", which means that it is online. If this works, do the same for your other volume: # cd ../0.0.108f . . . If that works, then come back to the original install session, select "Back", then invoke that step again. With luck, it will find the dasd devices now. P.S. Please do not attach my entire original e-mail at the end of your next posting. Just quote the relevant portions with the > character above your response. Also, please try to keep your input lines to a maximum of 80 characters. Thanks. -- To UNSUBSCRIBE, email to debian-s390-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org This E-mail and any of its attachments may contain Prince George’s County Government or Prince George's County 7th Judicial Circuit Court proprietary information, which is privileged and confidential. This E-mail is intended solely for the use of the individual or entity to which it is addressed. If you are not the intended recipient of this E-mail, you are hereby notified that any dissemination, distribution, copying, or action taken in relation to the contents of and attachments to this E-mail is strictly prohibited and may be unlawful. If you have received this E-mail in error, please notify the sender immediately and permanently delete the original and any copy of this E-mail and any printout.
RE: FW: Installation Question
-Original Message- From: Stephen Powell [mailto:zlinux...@wowway.com] Sent: Monday, January 11, 2010 9:59 AM To: debian-s390@lists.debian.org Subject: Re: FW: Installation Question On 2010-01-11 at 08:00:18 -0500, Larry D Martin wrote: > Update: With no other changes Suse 10.1 recognizes the disk. > What is the difference in the install processes - as it relates to disk > discovery? > > Thanks, ..Larry >As requested previously, (1) please don't "top post" but use the usenet >style >of quoting, and (2) please try to keep the maximum length of a line to 80 >bytes or less. (See http://en.wikipedia.org/wiki/Posting_style and >http://www.debian.org/MailingLists/index.html#codeofconduct.) >I will let those who are more knowledgeable about the internals of Debian >Installer answer your specific question, if they choose to do so; >but did you try my suggestions? And if so, what were the results? I have not tried your suggestions (yet) I have kept them and will get back to that. I amjust trying to get "some" Linux running. Thanks for all of the help and suggestions.Larry -- To UNSUBSCRIBE, email to debian-s390-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org This E-mail and any of its attachments may contain Prince George’s County Government or Prince George's County 7th Judicial Circuit Court proprietary information, which is privileged and confidential. This E-mail is intended solely for the use of the individual or entity to which it is addressed. If you are not the intended recipient of this E-mail, you are hereby notified that any dissemination, distribution, copying, or action taken in relation to the contents of and attachments to this E-mail is strictly prohibited and may be unlawful. If you have received this E-mail in error, please notify the sender immediately and permanently delete the original and any copy of this E-mail and any printout.
New user help
I am doing an install on an IBM Z9 LPAR of 6.0.3. The install was going smoothly until I got to "Configure direct access storage device". I supplied an address and was ask if I wanted to format it; I said yes and when it finished it went back to the previous screen. It just keeps alternating these screens. In another session if I do # cat /proc/dasd/devices I get: 0.0.2249(ECKD) at ( 94: 0) is dasda : active at blocksize: 4096, 1803060 blocks, 7043 MB 0.0.224a(ECKD) at ( 94: 4) is dasdb : active at blocksize: 4096, 1803060 blocks, 7043 MB How do I move forward? Thanks, ...Larry Larry D. Martin Mainframe Systems Support Office of Information Technology and Communications 301.883.7335
RE: New user help
Philipp, I would be happy to do that. I know almost nothing about Linux or its commands. Can you suggest a technique? I do have the file name on my terminal but do not know how to list it. Thanks, ...Larry -Original Message- From: Philipp Kern [mailto:pk...@debian.org] Sent: Thursday, December 22, 2011 2:23 PM To: Martin, Larry D Cc: 'debian-s390@lists.debian.org' Subject: Re: New user help On Thu, Dec 22, 2011 at 07:38:14AM -0500, Martin, Larry D wrote: > I am doing an install on an IBM Z9 LPAR of 6.0.3. > The install was going smoothly until I got to "Configure direct access > storage device". I supplied an address and was ask if I wanted to > format it; I said yes and when it finished it went back to the > previous screen. It just keeps alternating these screens. > > In another session if I do # cat /proc/dasd/devices I get: > 0.0.2249(ECKD) at ( 94: 0) is dasda : active at blocksize: 4096, > 1803060 blocks, 7043 MB > 0.0.224a(ECKD) at ( 94: 4) is dasdb : active at blocksize: 4096, > 1803060 blocks, 7043 MB Could you provide us with a dump of /var/log/syslog, please? Thanks Philipp Kern -- To UNSUBSCRIBE, email to debian-s390-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/c5425ab399786d45b95ac958d3a276140222804...@pgexchis01.co.pg.md.us
Trying to install SQUEEZE
I downloaded 6.0.4 and started the install. Just as with 6.0.3 I get stuck at "Configure direct access storage devices (DASD)". I provide an address, the system asks if I would like to format. Replying Yes/No does not matter. When I select "Continue" it asks to format and when I answer ir goes back to choose device. I attempted to ask this question on 6.0.3 but never got a resolution. Someone suggested it was because there were too many devices available. What I need to know is if there is a way to get the install to proceed without changing my IOCDS. (by the way this is LPAR mode on a z9 BC). I would really like to get this installed. I think that I subscribed to this list but did not get emails before. Please feel free to respond off list (since this is probably boring to most members). Thanks for any suggestions. Larry
S390 Release 6.0.5
I am trying to boot from CD at the HMC into an LPAR but I cannot find a valid mirror site. I have tried 6 or 7 in the US but it always comes back and says not a valid mirror. Is there a list of valid mirrors for this S390 release? Thanks, .Larry This E-mail and any of its attachments may contain Prince George’s County Government or Prince George's County 7th Judicial Circuit Court proprietary information or Protected Health Information, which is privileged and confidential. This E-mail is intended solely for the use of the individual or entity to which it is addressed. If you are not the intended recipient of this E-mail, you are hereby notified that any dissemination, distribution, copying, or action taken in relation to the contents of and attachments to this E-mail is strictly prohibited by federal law and may expose you to civil and/or criminal penalties. If you have received this E-mail in error, please notify the sender immediately and permanently delete the original and any copy of this E-mail and any printout.
s390x Install
I am trying once again to install Debian on an lpar. I have downloaded the latest wheezy and have made it to the dasd configuration. I am now stuck in the loop where it continues to ask for a device. I was told once that this is because the list of eligible devices was too large. I thought I saw an entry on this list that said a file could be edited to get past this point. Can someone tell me what file this might be (and also what command do I use to edit the file?). Thanks,...Larry This E-mail and any of its attachments may contain Prince George’s County Government or Prince George's County 7th Judicial Circuit Court proprietary information or Protected Health Information, which is privileged and confidential. This E-mail is intended solely for the use of the individual or entity to which it is addressed. If you are not the intended recipient of this E-mail, you are hereby notified that any dissemination, distribution, copying, or action taken in relation to the contents of and attachments to this E-mail is strictly prohibited by federal law and may expose you to civil and/or criminal penalties. If you have received this E-mail in error, please notify the sender immediately and permanently delete the original and any copy of this E-mail and any printout.
SSH Connection
I have just completed the install of wheezy on a z9 LPAR. I booted the system and it is running. I can log on to the system from the HMC (Operating System Messages) but cannot connect via putty. I did the install via a putty connection (port 22) but now it will not connect. Do I need to start something? And if so what is the command? Thanks,Larry This E-mail and any of its attachments may contain Prince George’s County Government or Prince George's County 7th Judicial Circuit Court proprietary information or Protected Health Information, which is privileged and confidential. This E-mail is intended solely for the use of the individual or entity to which it is addressed. If you are not the intended recipient of this E-mail, you are hereby notified that any dissemination, distribution, copying, or action taken in relation to the contents of and attachments to this E-mail is strictly prohibited by federal law and may expose you to civil and/or criminal penalties. If you have received this E-mail in error, please notify the sender immediately and permanently delete the original and any copy of this E-mail and any printout.
Unable to run kde or gnome
I have installed Debian (2.6.32-5-s390x Sun Sep 23 08:59:07 UTC 2012) on a z9 - LPAR mode. I can login but cannot get either gnome or kde to work. Whenever I issue startx, I get: xf860OpenConsole: Cannot open /dev/tty0 (No such file or directory). I have tried to research this via Google but have not found any answer that works. In /dev I do have a tty but no tty0. Also, what editor do I have available in line mode? Thanks, ..Larry This E-mail and any of its attachments may contain Prince George’s County Government or Prince George's County 7th Judicial Circuit Court proprietary information or Protected Health Information, which is privileged and confidential. This E-mail is intended solely for the use of the individual or entity to which it is addressed. If you are not the intended recipient of this E-mail, you are hereby notified that any dissemination, distribution, copying, or action taken in relation to the contents of and attachments to this E-mail is strictly prohibited by federal law and may expose you to civil and/or criminal penalties. If you have received this E-mail in error, please notify the sender immediately and permanently delete the original and any copy of this E-mail and any printout.
Re: Unable to run kde or gnome
I had a suggestion to run vncserver and I can try that (once I figure out how). What I really want to know is how to fix the 'startx' so that it works. I think I need to update the config file, but with what? When I type startx I get the following: X.Org X Server 1.7.7 Release Date: 2010-05-04 X Protocol Version 11, Revision 0 Build Operating System: Linux 2.6.32-5-s390x s390 Debian Current Operating System: Linux ibmlgclinux 2.6.32-5-s390x #1 SMP Sun Sep 23 0 Kernel command line: root=/dev/disk/by-path/ccw-0.0.2249-part1 BOOT_IMAGE=0 Build Date: 30 October 2011 10:34:03PM xorg-server 2:1.7.7-14 (Julien Cristau ) Current version of pixman: 0.16.4 Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: "/var/log/Xorg.0.log", Time: Wed Nov 21 07:30:15 2012 (==) Using system config directory "/usr/share/X11/xorg.conf.d" (==) No Layout section. Using the first Screen section. (==) No screen section available. Using defaults. (**) |-->Screen "Default Screen Section" (0) (**) | |-->Monitor "" (==) No monitor specified for screen "Default Screen Section". Using a default monitor configuration. (==) Automatically adding devices (==) Automatically enabling devices (WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist. Entry deleted from font path. (==) FontPath set to: /usr/share/fonts/X11/misc, /usr/share/fonts/X11/100dpi/:unscaled, /usr/share/fonts/X11/75dpi/:unscaled, /usr/share/fonts/X11/Type1, /usr/share/fonts/X11/100dpi, /usr/share/fonts/X11/75dpi, /var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType, built-ins (==) ModulePath set to "/usr/lib/xorg/modules" (II) The server relies on udev to provide the list of input devices. If no devices become available, reconfigure udev or disable AutoAddDevi. (II) Loader magic: 0x5d1e4c (II) Module ABI versions: X.Org ANSI C Emulation: 0.4 X.Org Video Driver: 6.0 X.Org XInput driver : 7.0 X.Org Server Extension : 2.0 Fatal server error: xf86OpenConsole: Cannot find a free VT: Invalid argument Please consult the The X.Org Foundation support at http://wiki.x.org for help. Please also check the log file at "/var/log/Xorg.0.log" for additional informat. (WW) xf86CloseConsole: KDSETMODE failed: Bad file descriptor (WW) xf86CloseConsole: VT_GETMODE failed: Bad file descriptor Thanks, .Larry This E-mail and any of its attachments may contain Prince George’s County Government or Prince George's County 7th Judicial Circuit Court proprietary information or Protected Health Information, which is privileged and confidential. This E-mail is intended solely for the use of the individual or entity to which it is addressed. If you are not the intended recipient of this E-mail, you are hereby notified that any dissemination, distribution, copying, or action taken in relation to the contents of and attachments to this E-mail is strictly prohibited by federal law and may expose you to civil and/or criminal penalties. If you have received this E-mail in error, please notify the sender immediately and permanently delete the original and any copy of this E-mail and any printout.
RE: Unable to run kde or gnome
Thanks to all. I have VNCSERVER working. Now to see what productive things we might be able to do. Thanks,...Larry -Original Message- From: Philipp Kern [mailto:pk...@debian.org] Sent: Wednesday, November 21, 2012 10:39 AM To: Martin, Larry D Cc: debian-s390@lists.debian.org Subject: Re: Unable to run kde or gnome On Wed, Nov 21, 2012 at 10:08:18AM -0500, Martin, Larry D wrote: > Any idea why startx will not run. If I run it as root I get all the > messages I posted earlier and if I run it as a user I get that I am not > authorized. > > When I type gdm3 all I get is repeated messages about the display > running for 0.2nnn seconds and have to to get out of the loop. As I said it's not supported. I don't know what else to tell you. There's nothing startx could draw a display on. gdm/xdm/kdm needs an xdmcp configuration before they can be used. Xnest seems indeed one way to go. Another one is vncserver. But I already said all of that (granted, except Xnest, thanks for the hint.) Try startx on any x86 Linux box. It might start an X session on VT7 if you're root, but not in your Putty. (That question is not s390-related, so debian-u...@lists.debian.org might be a better fit for support.) Kind regards Philipp Kern This E-mail and any of its attachments may contain Prince George’s County Government or Prince George's County 7th Judicial Circuit Court proprietary information or Protected Health Information, which is privileged and confidential. This E-mail is intended solely for the use of the individual or entity to which it is addressed. If you are not the intended recipient of this E-mail, you are hereby notified that any dissemination, distribution, copying, or action taken in relation to the contents of and attachments to this E-mail is strictly prohibited by federal law and may expose you to civil and/or criminal penalties. If you have received this E-mail in error, please notify the sender immediately and permanently delete the original and any copy of this E-mail and any printout. -- To UNSUBSCRIBE, email to debian-s390-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/c5425ab399786d45b95ac958d3a2761402eba37...@pgexchis01.co.pg.md.us
