Mark,
Thank you for the offer, I actually figured out the issue and resolved it.
First, as I was building my new initrd.img file and ftping it around I
forgot to set locsite fix 80 on the client (z/VM). Then I discovered that
if I look at the 2.4.9-37 oco tarball there is a ocord.img. If I open up
redhat.exec and insert a punch line after initrd.img for ocord.img then
all is well.
Now I am attempting the install, It seems I may not have the FTP site laid
out correctly. Any advice on how best to set up the FTP directory
structure. I have /ftp/RedHat/CD1 and /ftp/RedHat/CD2, is there another
way to setup the directory tree that is preferred?
Thank you!
Eric Sammons
(804)697-3925
FRIT - Infrastructure Engineering
"Post, Mark K" <[EMAIL PROTECTED]>
Sent by: Linux on 390 Port <[EMAIL PROTECTED]>
07/23/2003 01:40 PM
Please respond to Linux on 390 Port
To: [EMAIL PROTECTED]
cc:
Subject: Re: Known problems with HSI, QETH, configurations
during RedHat 7 .2 install?
Eric,
If you're interested, I can set up an account on my LCDS system for you to
upload the initrd. I'll try taking a look at it to see what might be
wrong.
Mark Post
-----Original Message-----
From: Eric Sammons [mailto:[EMAIL PROTECTED]
Sent: Wednesday, July 23, 2003 10:18 AM
To: [EMAIL PROTECTED]
Subject: Re: Known problems with HSI, QETH, configurations during RedHat
7 .2 install?
OK I have reviewed the procedures and I have implemented them. The thing
that concerned me right away was the kernel version numbers. My current
redhat.img and initrd.img files are based on kernel 2.4.9-37. The
procedures are for 2.4.9-17. I went ahead and made the initrd_oso.img
file and uploaded it (version 2.4.9-17) and as I would expect it does not
work. I am getting an error regarding the reading of /dev/ram0.
In looking at 2.4.9-37 I see no mkocord script nor do I see any procedures
for installing this and making a new initrd.img. Any ideas on where to go
from here? I have a couple of things in mind that I will try but I am
interested in understanding what others may have done in this situation.
Thanks!
Eric Sammons
FRIT - Infrastructure Engineering
"Post, Mark K" <[EMAIL PROTECTED]>
Sent by: Linux on 390 Port <[EMAIL PROTECTED]>
07/22/2003 12:22 PM
Please respond to Linux on 390 Port
To: [EMAIL PROTECTED]
cc:
Subject: Re: Known problems with HSI, QETH, configurations
during RedHat 7 .2 install?
http://www10.software.ibm.com/developerworks/opensource/linux390/docu/RedHat
-OCO-HowTo.pdf
Mark Post
-----Original Message-----
From: Eric Sammons [mailto:[EMAIL PROTECTED]
Sent: Tuesday, July 22, 2003 12:19 PM
To: [EMAIL PROTECTED]
Subject: Re: Known problems with HSI, QETH, configurations during RedHat
7 .2 install?
I am still looking, but I have not been able to find the instructions for
"rolling my own extra initrd". Anyone know specifically where they are
and will I be able to do work this process prior to actually installing an
image. Remeber the problems I see are related to the install process, I
very much would like to see the FTP install work, but if I have to I will
fall back to CTC.
Thanks!
Eric Sammons
FRIT - Infrastructure Engineering
"Post, Mark K" <[EMAIL PROTECTED]>
Sent by: Linux on 390 Port <[EMAIL PROTECTED]>
07/22/2003 10:36 AM
Please respond to Linux on 390 Port
To: [EMAIL PROTECTED]
cc:
Subject: Re: Known problems with HSI, QETH, configurations
during RedHat 7 .2 install?
Eric,
Actually, you have it backwards. SuSE is the distribution that was
including the IBM OCO modules, Red Hat does not. You'll need to go to the
IBM developerWorks site, download the OCO modules for the kernel level
you'll be using, and roll your own "extra" initrd (initial ram disk). The
instructions to do that should also be on the developerWorks site.
http://www10.software.ibm.com/developerworks/opensource/linux390/index.shtml
Mark Post
-----Original Message-----
From: Eric Sammons [mailto:[EMAIL PROTECTED]
Sent: Tuesday, July 22, 2003 9:20 AM
To: [EMAIL PROTECTED]
Subject: Known problems with HSI, QETH, configurations during RedHat 7.2
install?
I apologize for sending this again; however, I was recently informed that
my original E-mail was being blocked by spam filters. Hopefully this time
the E-mail will get to everyone.
Thank you!
================================ Original
=====================================
I am in the process of installing my first RedHat guest image. I have
installed SuSE and of course we used Channel to Channel given the known
issues with the Gig Adapters (OCO I believe).
I am now attempting to bring up RedHat; however, not finding any known
issues with the Gig Adapters I thought I would try an FTP install. So I
have my FTP system, I have my REDHAT PRM A file. I have it booting up to
the shell and asking me to now to connect to it via the given IP address.
The problem is I don't see the network adapter and I don't see an adapter
with the requested IP address. So the question now is, am I doing
something wrong or is there in fact a problem with the HSI configuration?
I am installing these images into a z/VM environment, so they are guests
and they are connecting to guest LANs.
Here is what I have thus far:
* * * Top of File * * *
root=/dev/ram0 ro ip=off DASD=292,200,201
HOST=somehost.somewhere.something:hsi0:???.???.???.4
NETWORK=???.???.???.0:255.255.255.224:???.???.???.31:???.???.???.30
RPMSERVER=???.???.???.???:/ftp/RedHat
/dev/dasdb1:/,/dev/dasdc1:/usr
INSTALL=default DTZ=EST5EDT
SWAP=/dev/dasda1
* * * End of File * * *
During the boot process I am prompted to answer two questions:
hwc low level driver: can write messages
hwc low level driver: can not read state change notifications
hwc low level driver: can read commands
hwc low level driver: can read priority commands
Linux version 2.4.9-37BOOT ([EMAIL PROTECTED]) (gcc version 2.95.3
20010315 (r
elease)) #1 SMP Wed Apr 24 17:32:38 CEST 2002
We are running under VM
This machine has an IEEE fpu
On node 0 totalpages: 32768
zone(0): 32768 pages.
zone(1): 0 pages.
zone(2): 0 pages.
Kernel command line: root=/dev/ram0 ro ip=off DASD=292,200,201
HOST=somehost.somewhere.something:hsi0:???.???.???.4
NETWORK=???.???.???.0:255.255.255.224:???.???.???.31:???.???.???.30
RPMSERVER=???.???.???.156:/ftp/RedHat
/dev/dasdb1:/,/dev/dasdc1:/usr
INSTALL=default DTZ=EST5EDT
SWAP=/dev/dasda1
Highest subchannel number detected (hex) : 0018
Calibrating delay loop... 778.24 BogoMIPS
Memory: 119772k/131072k available (1626k kernel code, 0k reserved, 844k
data, 64
k init)
Dentry-cache hash table entries: 16384 (order: 5, 131072 bytes)
Inode-cache hash table entries: 8192 (order: 4, 65536 bytes)
Mount-cache hash table entries: 2048 (order: 2, 16384 bytes)
Buffer-cache hash table entries: 8192 (order: 3, 32768 bytes)
Page-cache hash table entries: 32768 (order: 6, 262144 bytes)
debug: Initialization complete
debug: reserved 4 areas of 4 pages for debugging ccwcache
POSIX conformance testing by UNIFIX
Detected 1 CPU's
Boot cpu address 0
cpu 0 phys_idx=0 vers=FF ident=0F11AA machine=2064 unused=0000
init_mach : starting machine check handler
init_mach : machine check buffer : head = 0023EDF0
init_mach : machine check buffer : tail = 0023EDF4
init_mach : machine check buffer : free = 0023EDF8
init_mach : CRW entry buffer anchor = 0023EDFC
init_mach : machine check handler ready
Linux NET4.0 for Linux 2.4
Based upon Swansea University Computer Society NET3.039
mach_handler : ready
mach_handler : waiting for wakeup
Starting kswapd v1.8
VFS: Diskquotas version dquot_6.5.0 initialized
pty: 256 Unix98 ptys configured
block: queued sectors max/low 79394kB/26464kB, 256 slots per queue
RAMDISK driver initialized: 16 RAM disks of 35840K size 1024 blocksize
md: md driver 0.90.0 MAX_MD_DEVS=256, MD_SB_DISKS=27
md: Autodetecting RAID arrays.
md: autorun ...
md: ... autorun DONE.
debug: reserved 4 areas of 16 pages for debugging cio_msg
debug: cio_msg: new level 2
debug: reserved 4 areas of 16 pages for debugging cio_trace
debug: cio_trace: new level 2
debug: reserved 4 areas of 4 pages for debugging cio_crw
debug: cio_crw: new level 6
NET4: Linux TCP/IP 1.0 for NET4.0
IP Protocols: ICMP, UDP, TCP, IGMP
IP: routing cache hash table of 512 buckets, 8Kbytes
TCP: Hash tables configured (established 4096 bind 8192)
NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
RAMDISK: Compressed image found at block 0
Freeing initrd memory: 4667k freed
EXT2-fs warning: checktime reached, running e2fsck is recommended
VFS: Mounted root (ext2 filesystem).
Freeing unused kernel memory: 16k freed
Starting the S/390 initrd to configure networking. Version is 0.51
Invalid MTU , skipping
Please enter parameters you need to pass to the channel device layer.
This includes the I/O ports of your ctc, escon, qeth, hsi and lcs devices.
Additional parameters for QETH devices such as the portname
should be entered at the next prompt, not here !
(e.g. "ctc0,0x600,0x601" will activate the ctc0 interface at I/O
ports 0x600,0x601):
qeth0,0xbfe0,0xbfe1,0xbfe2 <--------------- My Answer
Each OSA-Express feature in QDIO mode must be associated with a port name
Please enter additional parameters for your QETH device
(e.g. "add_parms,0x10,{lo_devno,hi_devno},portname:port_name")
Press enter if you don't want to enter additional parameters
add_parms,0x10,0xbfe0,0xbfe2,no_router,portname:VT21LAN1
<----------------------------- My Answer
IPv6 v0.8 for NET4.0
IPv6 over IPv4 tunneling driver
Please enter your DNS server(s), separated by colons (:):
You might encounter problems without a nameserver, especially
with FTP installs
Please enter your DNS search domain(s) (if any), separated by colons (:):
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
sit0 Link encap:IPv6-in-IPv4
NOARP MTU:1480 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use
Iface
127.0.0.1 0.0.0.0 255.255.255.255 UH 0 0 0 lo
Starting portmap.
Loading DASD kernel module. This can take a while.
dasd:initializing...
debug: reserved 2 areas of 1 pages for debugging dasd
dasd:Registered successfully to major no 94
dasd:initialization finished
dasd(eckd):ECKD discipline initializing
dasd(eckd):0200 on sch 11: 3390/0A(CU:3990/01) Cyl:1400 Head:15 Sec:224
dasd(eckd):0200 on sch 11: 3390/0A(CU:3990/01): Configuration data read
debug: reserved 2 areas of 1 pages for debugging dasdb
dasd(eckd):/dev/dasdb(94:4),[EMAIL PROTECTED]:(4kB blks): 1008000kB at 48kB/trk
classic d
isk layout
dasd(eckd):0201 on sch 12: 3390/0A(CU:3990/01) Cyl:1400 Head:15 Sec:224
dasd(eckd):0201 on sch 12: 3390/0A(CU:3990/01): Configuration data read
debug: reserved 2 areas of 1 pages for debugging dasdc
dasd:waiting for responses...
dasd(eckd):/dev/dasdc(94:8),[EMAIL PROTECTED]:(4kB blks): 1008000kB at 48kB/trk
classic d
isk layout
Partition check:
dasdb:CMS1/ 511200: dasdb dasdb1
dasdc:CMS1/ 511201: dasdc dasdc1
dasd(eckd):We are interested in: CU 3880/00
dasd(eckd):We are interested in: CU 3990/00
dasd(eckd):We are interested in: CU 2105/00
dasd(eckd):We are interested in: CU 9343/00
Journalled Block Device driver loaded
Starting telnetd and sshd to allow login over the network.
Please connect now to ???.???.???.4 and start 'loader' from this shell.
sh-2.05#
Any help is appreciated.
Thank you!
Eric Sammons
(804)697-3925
FRIT - Infrastructure Engineering
