Mark, I mis stated yast in the earlier email. It is the SLES IPL 00C installation with full specifications including autoinst, that gives up on finding the source before the CTC connects. The console shows the CTC0 connecting after the install program has shifted to a manual install. After this no matter how I attempt to select CTC and give it response the install program will not proceed but reverts right back to the network device question even though the CTC selected even though it is already connected. It is like it thinks it is bad selection and will not reconsider it. I have tried several things to reset or get it to accept/proceed with the CTC response information. Some are: tapping off the answers and taking the defaults that are being presented, giving bogus address responses, selecting other connection methods different not connected responses. Re-IPLing 00C clear, etc.
The only way I have been successful to get the CTC to be accepted is to replace the parmfile SUSE with the simple 1 line parmfile (knocking out the autoinst along with the other stuff). Even then I have throw away the SLES ipl of 00C and reipl 00C. Followed by giving bad addresses for the ctc and failing and then on the 2nd iteration giving the right information. Some how the defaults are remembered through a logoff/logon different parmfile SLES invocation. I will paste the 2 parmfiles and a given console of the network device selection prompt loop. Autoinst attempted parmfile: ramdisk_size=65536 root=/dev/ram1 ro init=/linuxrc TERM=dumb instnetdev=ctc pointopoint=199.42.190.45 hostip=199.42.190.3 Gateway=199.42.190.45 Nameserver=127.0.0.1 Netmask=255.255.255.255 dhcp=2 readchannel=0.0.0e00 writechannel=0.0.0e01 ctcprotocol=0 install=ftp://199.42.190.8/ autoyast=http://199.42.190.48/suse/autoinst.xml usessh=1 sshpassword=temp Simple parmfile: ramdisk_size=65536 root=/dev/ram1 ro init=/linuxrc TERM=dumb Console of SLES install giving up and looping through prompts on the CTC network device prompts: sles 0000003 FILES PURGED RDR FILE 0006 SENT FROM CLIENT PUN WAS 0006 RECS 076K CPY 001 A NOHOLD NOKEEP RDR FILE 0007 SENT FROM CLIENT PUN WAS 0007 RECS 0010 CPY 001 A NOHOLD NOKEEP RDR FILE 0008 SENT FROM CLIENT PUN WAS 0008 RECS 104K CPY 001 A NOHOLD NOKEEP 0000003 FILES CHANGED 0000003 FILES CHANGED Linux version 2.6.16.46-0.12-default ([EMAIL PROTECTED]) (gcc version 4.1.2 20070115 (prerelease) (SUSE Linux)) #1 SMP Thu May 17 14:0 0:09 UTC 2007 We are running under VM (64 bit mode) Detected 1 CPU's Boot cpu address 0 Built 1 zonelists Kernel command line: ramdisk_size=65536 root=/dev/ram1 ro init=/linuxrc TERM=dumb instnetdev=ctc pointopoint=199. 42.190.45 hostip=199.42.190.3 Gateway=199.42.190.45 Nameserver=127.0.0.1 Netmask=255.255.255.255 dhc p=2 PID hash table entries: 4096 (order: 12, 131072 bytes) Dentry cache hash table entries: 131072 (order: 8, 1048576 bytes) Inode-cache hash table entries: 65536 (order: 7, 524288 bytes) Memory: 496640k/524288k available (4494k kernel code, 0k reserved, 1221k data, 204k init) Security Framework v1.0.0 initialized Mount-cache hash table entries: 256 checking if image is initramfs... it is Freeing initrd memory: 8128k freed cpu 0 phys_idx=0 vers=FF ident=04912A machine=2066 unused=0000 Brought up 1 CPUs migration_cost=1000 NET: Registered protocol family 16 debug: Initialization complete cio: Channel measurements not available, continuing. audit: initializing netlink socket (disabled) audit(1216779850.524:1): initialized VFS: Disk quotas dquot_6.5.1 Dquot-cache hash table entries: 512 (order 0, 4096 bytes) Initializing Cryptographic API io scheduler noop registered io scheduler anticipatory registered io scheduler deadline registered (default) io scheduler cfq registered RAMDISK driver initialized: 16 RAM disks of 65536K size 1024 blocksize md: md driver 0.90.3 MAX_MD_DEVS=256, MD_SB_DISKS=27 md: bitmap version 4.39 Channel measurement facility using basic format (autodetected) NET: Registered protocol family 2 IP route cache hash table entries: 32768 (order: 6, 262144 bytes) TCP established hash table entries: 131072 (order: 9, 2097152 bytes) TCP bind hash table entries: 65536 (order: 8, 1048576 bytes) TCP: Hash tables configured (established 131072 bind 65536) TCP reno registered NET: Registered protocol family 1 Freeing unused kernel memory: 204k freed Moving into tmpfs... done. >>> SUSE Linux Enterprise Server 10 installation program v2.0.67 (c) 1996-2007 SUSE Linux Products GmbH <<< Starting udev ... ... udev running SCSI subsystem initialized NET: Registered protocol family 17 loop: loaded (max 8 devices) Starting hardware detection... Searching for info file... NET: Registered protocol family 10 lo: Disabled Privacy Extensions IPv6 over IPv4 tunneling driver qdio: loading QDIO base support version 2 qeth: loading qeth S/390 OSA-Express driver CTC driver initialized IUCV lowlevel driver initialized iucv: NETIUCV driver initialized ctc0: read: ch-0.0.0e00, write: ch-0.0.0e01, proto: 0 sit0: Disabled Privacy Extensions *** Could not find the SUSE Linux Enterprise Server 10 Installation Source. Activating manual setup program. >>> Linuxrc v2.0.67 (Kernel 2.6.16.46-0.12-default) <<< Main Menu 1) Settings 2) System Information 3) Kernel Modules (Hardware Drivers) 4) Start Installation or System 5) Verify Installation CD-ROM/DVD 6) Eject CD 7) Exit or Reboot 8) Power off > ctc0: connected with remote side ****** NOTE CTC0 CONNECTED HERE ***** 4 Start Installation or System 1) Start Installation or Update 2) Boot Installed System 3) Start Rescue System > 1 Choose the source medium. 1) CD-ROM 2) Network 3) Hard Disk > 2 Choose the network protocol. 1) FTP 2) HTTP 3) NFS 4) SMB / CIFS (Windows Share) 5) TFTP > 1 Please select the type of your network device. 1) OSA-2 or OSA Express 2) Hipersockets -------------------- 3) Channel To Channel (CTC) 4) ESCON 5) Inter-User Communication Vehicle (IUCV) > 3 0.0.0e00 3088/08 0.0.0e01 3088/08 Device address for read channel [0.0.0e00]> Device address for write channel [0.0.0e01]> Select protocol for this CTC device. 1) Compatibility mode (default) 2) Extended mode 3) Compatibility mode for OS/390 and z/OS peers > Please select the type of your network device. 1) OSA-2 or OSA Express 2) Hipersockets -------------------- 3) Channel To Channel (CTC) 4) ESCON 5) Inter-User Communication Vehicle (IUCV) > 3 0.0.0e00 3088/08 0.0.0e01 3088/08 Device address for read channel [0.0.0e00]> Device address for write channel [0.0.0e01]> Select protocol for this CTC device. 1) Compatibility mode (default) 2) Extended mode 3) Compatibility mode for OS/390 and z/OS peers > 1 Please select the type of your network device. 1) OSA-2 or OSA Express 2) Hipersockets -------------------- 3) Channel To Channel (CTC) 4) ESCON 5) Inter-User Communication Vehicle (IUCV) > 3 0.0.0e00 3088/08 0.0.0e01 3088/08 Device address for read channel [0.0.0e00]> 0.0.0e00 Device address for write channel [0.0.0e01]> 0.0.0e01 Select protocol for this CTC device. 1) Compatibility mode (default) 2) Extended mode 3) Compatibility mode for OS/390 and z/OS peers > 1 Please select the type of your network device. 1) OSA-2 or OSA Express 2) Hipersockets -------------------- 3) Channel To Channel (CTC) 4) ESCON 5) Inter-User Communication Vehicle (IUCV) > ..... Etc....... Thank you Paul -----Original Message----- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Mark Post Sent: Friday, July 11, 2008 12:21 PM To: [email protected] Subject: Re: #autoinst - parmfile - yast gives up before CTC0 connects. >>> On Fri, Jul 11, 2008 at 11:56 AM, in message <[EMAIL PROTECTED]>, "Sienicki, Paul K" <[EMAIL PROTECTED]> wrote: > Mark, > > The CTC connects but after yast has given up on finding the source. > Is there a way to delay the source/nosource decision? Not that I'm aware of. However, if you select the "Start Installation" option, the installer should already have all the information it needs. It should present them as defaults to the questions it will ask, and then once you SSH into the system, the AutoYaST code will kick in and take off. Mark Post ---------------------------------------------------------------------- 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
