Discussion:
SLES-10 install issue
(too old to reply)
Joseph M. DeAngelo
2007-03-25 21:53:52 UTC
Permalink
I think I got no reply the last time because I failed to document my
issue. I'm trying to install SLES-10 under Hercules running under
Windows Vista. I have gotten things to IPL to a point, but I cannot
get SLES to load onto my virtual DASD. I have tried

ipl d:\suse.ins

and

ipl 0580 clr

with the tapeipl.tdf file of:

@TDF
D:\boot\s390x\tapeipl.ikr fixed recsize 1024
TM
D:\boot\s390x\initrd fixed recsize 1024
TM
D:\boot\s390x\parmfile text recsize 1024
TM
TM
EOT

I always get to a point where I get a message about:

*** Could not find the SUSE Linux Enterprise Server 10 Installation
CD.
Linux V2.0.46y (Kernel 2.6.16.21-0.8-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
From that point forward, nothing seems to work. If I choose .5, it
says:

Insert Installation CD-ROM or DVD

*** No CD-ROM or DVD found.

Yet, the DVD from which I booted is still in drive D:. If I choose
option 4, it similarly cannot find the CD from which to install the
system. What must I do to get around this.??

Here is my Hercules.conf file:

#
# Hercules Emulator Control file...
# Description:
# MaxShutdownSecs: 15
#
#
# System parameters
#

ARCHMODE z/Arch
CNSLPORT 3270
CONKPALV (3,1,10)
CODEPAGE default
CPUMODEL 3090
CPUSERIAL 002623
CPUVERID FD
ECPSVM NO
HTTPPORT 8081 NOAUTH
LOADPARM 0120....
LPARNAME HERCULES
MAINSIZE 256
MOUNTED_TAPE_REINIT ALLOW
NUMCPU 1
OSTAILOR LINUX
PANRATE 50
SHCMDOPT NODIAG8
SYSEPOCH 1900
TIMERINT 50
TZOFFSET -0600
YROFFSET 0

HERCPRIO 0
TODPRIO -20
DEVPRIO 8
CPUPRIO 15

# Card Readers

000C 3505 ./util/zzsacard.bin

# Card Punches

000D 3525 punch00d.txt ascii

# Line Printers

000E 1403 print00e.txt crlf

# Console Printers

0009 3215-C / noprompt

# Display Terminals

001F 3270

# DASD Devices

0120 3390 C:/Users/Public/HerculesDevices/Dasd/DASD.3390-1
0121 3390 C:/Users/Public/HerculesDevices/Dasd/WORK02.3390-
1.alts
0122 3390 C:/Users/Public/HerculesDevices/Dasd/WORK03.3390-
1.alts
0123 3390 C:/Users/Public/HerculesDevices/Dasd/WORK04.3390-
1.alts
0124 3390 C:/Users/Public/HerculesDevices/Dasd/WORK05.3390-
1.alts
0125 3390 C:/Users/Public/HerculesDevices/Dasd/WORK06.3390-
1.alts

# TAPE Devices

0580 3480 C:/Users/Public/HerculesDevices/Tape/tapeipl.tdf
chunksize=65535 compress=1 method=1 level=4 maxsizeM=170
eotmargin=131072

# CTC Adapters

0E20 CTCI 192.168.250.70 192.168.250.69
0E21 CTCI 192.168.250.70 192.168.250.69
Tim Pinkawa
2007-03-25 22:17:16 UTC
Permalink
Post by Joseph M. DeAngelo
I think I got no reply the last time because I failed to document my
issue. I'm trying to install SLES-10 under Hercules running under
Windows Vista. I have gotten things to IPL to a point, but I cannot
get SLES to load onto my virtual DASD. I have tried
*snip*

Installing mainframe Linux is unlike most other platforms. When you
IPL off the ins file or the tdf file, it's kind of like booting off a
floppy on a PC (with Hercules, you're actually booting off tape).
It'll get you started, but you need another source to finish the
installation. You're not actually booting with the full disc and
Hercules hardware has no concept of a "CD" or "DVD". (on the real
hardware today, you can directly access the CD through various
methods, but not with Hercules yet AFAIK) You need to make the CD
contents available over the network. Common ways of doing this is with
an FTP server, HTTP server, NFS server, or SMB (Windows file sharing)
server. Since you're already on a Windows platform, SMB is probably
the easiest. Share the installation folder through Windows, then on
the Hercules console, select SMB as your source. The server is the IP
address of your desktop machine and the folder is whatever name the
folder is shared as. If it's a CD-ROM drive, the default name is
probably D. Also make sure any firewalls you have don't block Windows
file sharing. If anything is unclear, let me know and I'll try to
clarify.

Hope this helps,
Tim
Joseph M. DeAngelo
2007-03-25 23:09:10 UTC
Permalink
Thanks for the quick reply. I'll try anything. Unfortunately, I'm
short a few facts.

On my Windows Vista system, I enabled sharing on my DVD drive and
called the share name SLESonD to point to the entire DVD. That did
not work, so I copied the entire DVD to Public\SLES10 and enabled
sharing on Public. I can access Public from external machines just
fine. Here is the log of that attempt:

17:56:30.889 Hercules started; process-id=00000C00
17:56:31.021 00000C00 17:56:31 Hercules Version 3.04
17:56:31.021 00000C00 17:56:31 (c)Copyright 1999-2006 by Roger
Bowler, Jan Jaeger, and others
17:56:31.021 00000C00 17:56:31 Built on Feb 22 2006 at 23:08:46
17:56:31.021 00000C00 17:56:31 Build information:
17:56:31.022 00000C00 17:56:31 Win32 (MSVC) build
17:56:31.022 00000C00 17:56:31 Modes: S/370 ESA/390 z/Arch
17:56:31.022 00000C00 17:56:31 Max CPU Engines: 8
17:56:31.022 00000C00 17:56:31 Using fthreads instead of pthreads
17:56:31.022 00000C00 17:56:31 With Dynamic loading support
17:56:31.022 00000C00 17:56:31 Loadable module default base
directory is .
17:56:31.022 00000C00 17:56:31 Using shared libraries
17:56:31.022 00000C00 17:56:31 HTTP Server support
17:56:31.022 00000C00 17:56:31 No SIGABEND handler
17:56:31.022 00000C00 17:56:31 Machine dependent assists: cmpxchg1
cmpxchg4 cmpxchg8 fetch_dw store_dw
17:56:31.023 00000C00 17:56:31 Running on NEO Windows_NT-6.0 i686 MP=2
17:56:31.027 00000C00 Crypto module loaded (c) Copyright Bernard van
der Helm, 2003-2005
17:56:31.027 00000C00 HHCCF008E Error in C:/Program
Files/hercules/hercules-3.04/hercules.cnf line 12: Unrecognized
keyword CONKPALV
17:56:31.027 00000C00 HHCCF008E Error in C:/Program
Files/hercules/hercules-3.04/hercules.cnf line 22: Unrecognized
keyword MOUNTED_TAPE_REINIT
17:56:31.027 00000C00 HHCCF008E Error in C:/Program
Files/hercules/hercules-3.04/hercules.cnf line 28: Unrecognized
keyword TIMERINT
17:56:31.028 00000C00 HHCCF065I Hercules: tid=00000A98, pid=3072,
pgid=3072, priority=0
17:56:31.040 00000C00 HHCDA020I
C:/Users/Public/HerculesDevices/Dasd/DASD.3390-1 cyls=1114 heads=15
tracks=16710 trklen=56832
17:56:31.040 00000C00 HHCDA020I
C:/Users/Public/HerculesDevices/Dasd/WORK02.3390-1.alts cyls=1114
heads=15 tracks=16710 trklen=56832
17:56:31.040 00000C00 HHCDA020I
C:/Users/Public/HerculesDevices/Dasd/WORK03.3390-1.alts cyls=1114
heads=15 tracks=16710 trklen=56832
17:56:31.040 00000C00 HHCDA020I
C:/Users/Public/HerculesDevices/Dasd/WORK04.3390-1.alts cyls=1114
heads=15 tracks=16710 trklen=56832
17:56:31.041 00000C00 HHCDA020I
C:/Users/Public/HerculesDevices/Dasd/WORK05.3390-1.alts cyls=1114
heads=15 tracks=16710 trklen=56832
17:56:31.041 00000C00 HHCDA020I
C:/Users/Public/HerculesDevices/Dasd/WORK06.3390-1.alts cyls=1114
heads=15 tracks=16710 trklen=56832
17:56:31.041 00000C00 HHCTE001I Console connection thread started:
tid=0000047C, pid=3072
17:56:31.042 00000C00 HHCTE003I Waiting for console connection on
port 3270
17:56:31.046 00000C00 HHCTA998I Device 0580 :
C:/Users/Public/HerculesDevices/Tape/tapeipl.tdf is a Optical Media
Attachment (OMA) tape
17:56:31.046 00000C00 XXXXXXXXX Device 0580 :
parameter: 'chunksize=65535'
17:56:31.046 00000C00 XXXXXXXXX Device 0580 : parameter: 'compress=1'
17:56:31.046 00000C00 XXXXXXXXX Device 0580 : parameter: 'method=1'
17:56:31.046 00000C00 XXXXXXXXX Device 0580 : parameter: 'level=4'
17:56:31.046 00000C00 XXXXXXXXX Device 0580 :
parameter: 'maxsizeM=170'
17:56:31.046 00000C00 XXXXXXXXX Device 0580 :
parameter: 'eotmargin=131072'
17:56:31.046 00000C00 HHCTA100I 0580: Now Displays: " NT RDY "
17:56:31.060 00000C00 C:\Program Files\hercules\hercules-3.04
\TunTap32.dll version 3.2.1.160 initiated
17:56:31.111 00000C00 HHCCT073I 0E20: TUN device tun0 opened
17:56:31.111 00000C00 HHCCF069I Run-options enabled for this run:
17:56:31.111 00000C00 NUMCPU: 1
17:56:31.111 00000C00 ASN-and-LX-reuse: DISabled
17:56:31.111 00000C00 DIAG8CMD: DISabled
17:56:31.111 00000C00 HHCCP002I CPU0000 thread started: tid=00000D48,
pid=3072, priority=15
17:56:31.112 00000C00 HHCCP003I CPU0000 architecture mode z/Arch
17:56:31.112 00000C00 HHCTT002I Timer thread started: tid=000004CC,
pid=3072, priority=-20
17:56:31.113 00000C00 HHCDG001I dyngui.dll initiated
17:56:31.114 00000C00 HHCHT001I HTTP listener thread started:
tid=00000F3C, pid=3072
17:56:31.114 00000C00 HHCHT013I Using HTTPROOT directory "C:\Program
Files\hercules\hercules-3.04\html\"
17:56:31.114 00000C00 HHCHT006I Waiting for HTTP requests on port 8081
17:57:00.138 00000C00 ipl D:\suse.ins
17:57:00.177 00000C00 HHCCP007I CPU0000 architecture mode set to
ESA/390
17:57:00.177 00000C00 CPU0000: SIGP Set architecture mode (12)
CPU0000, PARM 00000001: CC 0
17:57:00.177 00000C00 HHCCP007I CPU0000 architecture mode set to
z/Arch
17:57:00.198 00000C00 HHCCP014I CPU0000: Addressing exception
CODE=0005 ILC=6
17:57:00.198 00000C00 PSW=00001001 80000000 000000000001016E
INST=E50150000000 TPROT 0(5),0(0)
17:57:00.198 00000C00 R:0000000010000000: Translation exception 0005
17:57:00.198 00000C00 R:0000000000000000:K:06=00080000 80000298
02000018 60000050 .......q....-..&
17:57:00.198 00000C00 R0=0000000000000000 R1=0000000000020000
R2=0000000000000000 R3=00000000005CC478
17:57:00.198 00000C00 R4=0000000000000000 R5=0000000010000000
R6=0000000000000000 R7=0000000000000000
17:57:00.198 00000C00 R8=0000000000000000 R9=0000000010000000
RA=0000000000000010 RB=0000000000000000
17:57:00.198 00000C00 RC=0000000000010400 RD=0000000000010002
RE=0000000080010010 RF=0000000000000000
17:57:00.914 00000C00 HHCCP041I SYSCONS interface active
17:57:00.917 00000C00 HHCCP041I SYSCONS interface active
17:57:01.017 00000C00 Linux version 2.6.16.21-0.8-default
(***@buildhost) (gcc version 4.1.0 (SUSE L
17:57:01.017 00000C00 inux)) #1 SMP Mon Jul 3 18:25:39 UTC 2006
17:57:01.017 00000C00 We are running native (64 bit mode)
17:57:01.017 00000C00 Detected 1 CPU's
17:57:01.017 00000C00 Boot cpu address 0
17:57:01.017 00000C00 Built 1 zonelists
17:57:01.017 00000C00 Kernel command line: ramdisk_size=65536
root=/dev/ram1 ro init=/linuxrc TERM=dum
17:57:01.017 00000C00 b
17:57:01.017 00000C00
17:57:01.017 00000C00
17:57:01.017 00000C00
17:57:01.017 00000C00 PID hash table entries: 2048 (order: 11, 65536
bytes)
17:57:01.017 00000C00 Dentry cache hash table entries: 65536 (order:
7, 524288 bytes)
17:57:01.017 00000C00 Inode-cache hash table entries: 32768 (order:
6, 262144 bytes)
17:57:01.017 00000C00 Memory: 239616k/262144k available (4298k kernel
code, 0k reserved, 1401k data, 1
17:57:01.017 00000C00 96k init)
17:57:01.325 00000C00 Security Framework v1.0.0 initialized
17:57:01.325 00000C00 Mount-cache hash table entries: 256
17:57:01.325 00000C00 checking if image is initramfs...
17:57:27.039 00000C00 it is
17:57:53.312 00000C00 Freeing initrd memory: 8067k freed
17:57:53.312 00000C00 cpu 0 phys_idx=0 vers=00 ident=002623
machine=3090 unused=8000
17:57:53.312 00000C00 Brought up 1 CPUs
17:57:53.312 00000C00 migration_cost=1000
17:57:53.312 00000C00 NET: Registered protocol family 16
17:57:53.312 00000C00 debug: Initialization complete
17:57:53.312 00000C00 cio: Was not able to determine available CHSCs.
17:57:53.440 00000C00 HHCCP041I SYSCONS interface active
17:57:53.441 00000C00 HHCCP041I SYSCONS interface active
17:57:53.462 00000C00 TC classifier action (bugs to
netdev-***@public.gmane.org cc hadi-fAAogVwAN2Kw5LPnMra/***@public.gmane.org)
17:57:53.462 00000C00 audit: initializing netlink socket (disabled)
17:57:53.462 00000C00 audit(1174841873.384:1): initialized
17:57:53.462 00000C00 VFS: Disk quotas dquot_6.5.1
17:57:53.462 00000C00 Dquot-cache hash table entries: 512 (order 0,
4096 bytes)
17:57:53.462 00000C00 Initializing Cryptographic API
17:57:53.462 00000C00 io scheduler noop registered
17:57:53.462 00000C00 io scheduler anticipatory registered
17:57:53.462 00000C00 io scheduler deadline registered (default)
17:57:53.462 00000C00 io scheduler cfq registered
17:57:53.462 00000C00 RAMDISK driver initialized: 16 RAM disks of
65536K size 1024 blocksize
17:57:53.462 00000C00 md: md driver 0.90.3 MAX_MD_DEVS=256,
MD_SB_DISKS=27
17:57:53.462 00000C00 md: bitmap version 4.39
17:57:53.462 00000C00 Channel measurement facility using basic format
(autodetected)
17:57:53.462 00000C00 NET: Registered protocol family 2
17:57:53.642 00000C00 IP route cache hash table entries: 4096 (order:
3, 32768 bytes)
17:57:53.642 00000C00 TCP established hash table entries: 16384
(order: 6, 262144 bytes)
17:57:53.642 00000C00 TCP bind hash table entries: 16384 (order: 6,
262144 bytes)
17:57:53.642 00000C00 TCP: Hash tables configured (established 16384
bind 16384)
17:57:53.642 00000C00 TCP reno registered
17:57:53.642 00000C00 NET: Registered protocol family 1
17:57:53.642 00000C00 Freeing unused kernel memory: 196k freed
17:57:53.790 00000C00 Moving into tmpfs...
17:57:55.821 00000C00 done.
17:57:56.371 00000C00
17:57:56.371 00000C00 >>> SUSE Linux Enterprise Server 10
installation program v2.0.46 (c) 1996-2006 S
17:57:56.371 00000C00 USE Linux Products GmbH <<<
17:57:56.371 00000C00
17:57:56.371 00000C00 Starting udev ...
17:57:58.141 00000C00 ... udev running
17:57:59.842 00000C00 SCSI subsystem initialized
17:58:01.422 00000C00 NET: Registered protocol family 17
17:58:35.393 00000C00 loop: loaded (max 8 devices)
17:58:38.337 00000C00 Starting hardware detection...
17:58:40.827 00000C00
17:58:41.667 00000C00 Searching for info file...
17:58:42.467 00000C00
17:58:42.467 00000C00 *** Could not find the SUSE Linux Enterprise
Server 10 Installation CD.
17:58:42.467 00000C00
17:58:42.467 00000C00 Activating manual setup program.
17:58:42.467 00000C00
17:58:42.467 00000C00 >>> Linuxrc v2.0.46 (Kernel 2.6.16.21-0.8-
default) <<<
17:58:42.467 00000C00
17:58:42.467 00000C00 Main Menu
17:58:42.467 00000C00
17:58:42.467 00000C00 1) Settings
17:58:42.467 00000C00 2) System Information
17:58:42.467 00000C00 3) Kernel Modules (Hardware Drivers)
17:58:42.467 00000C00 4) Start Installation or System
17:58:42.467 00000C00 5) Verify Installation CD-ROM/DVD
17:58:42.467 00000C00 6) Eject CD
17:58:42.467 00000C00 7) Exit or Reboot
17:58:42.467 00000C00 8) Power off
17:58:42.467 00000C00
17:58:42.467 00000C00 >
18:01:23.783 00000C00 .4
18:01:23.891 00000C00 4
18:01:23.891 00000C00
18:01:23.891 00000C00 Start Installation or System
18:01:23.891 00000C00
18:01:23.891 00000C00 1) Start Installation or Update
18:01:23.891 00000C00 2) Boot Installed System
18:01:23.891 00000C00 3) Start Rescue System
18:01:23.891 00000C00
18:01:23.891 00000C00 >
18:01:25.999 00000C00 .1
18:01:26.102 00000C00 1
18:01:26.102 00000C00
18:01:26.102 00000C00 Choose the source medium.
18:01:26.102 00000C00
18:01:26.103 00000C00 1) CD-ROM
18:01:26.103 00000C00 2) Network
18:01:26.103 00000C00 3) Hard Disk
18:01:26.103 00000C00
18:01:26.103 00000C00 >
18:01:28.310 00000C00 .2
18:01:28.412 00000C00 2
18:01:28.412 00000C00
18:01:28.412 00000C00 Choose the network protocol.
18:01:28.412 00000C00
18:01:28.412 00000C00 1) FTP
18:01:28.412 00000C00 2) HTTP
18:01:28.412 00000C00 3) NFS
18:01:28.412 00000C00 4) SMB / CIFS (Windows Share)
18:01:28.412 00000C00 5) TFTP
18:01:28.412 00000C00
18:01:28.412 00000C00 >
18:01:34.848 00000C00 .4
18:01:34.953 00000C00 4
18:01:34.953 00000C00
18:01:34.953 00000C00 Please select the type of your network device.
18:01:34.953 00000C00
18:01:34.953 00000C00 1) OSA-2 or OSA Express
18:01:34.953 00000C00 2) Hipersockets
18:01:34.953 00000C00 --------------------
18:01:34.953 00000C00 3) Channel To Channel (CTC)
18:01:34.953 00000C00 4) ESCON
18:01:34.953 00000C00 5) Inter-User Communication Vehicle (IUCV)
18:01:34.953 00000C00
18:01:34.953 00000C00 >
18:01:37.568 00000C00 .3
18:01:37.673 00000C00 3
18:01:48.343 00000C00 CTC driver initialized
18:01:49.874 00000C00
18:01:49.874 00000C00 0.0.0e20 3088/08
18:01:49.874 00000C00 0.0.0e21 3088/08
18:01:49.874 00000C00
18:01:49.874 00000C00
18:01:49.874 00000C00 Device address for read channel>
18:02:06.278 00000C00 .0.0.0e20
18:02:06.416 00000C00 0.0.0e20
18:02:06.416 00000C00
18:02:06.416 00000C00 Device address for write channel>
18:02:13.334 00000C00 .0.0.0e21
18:02:13.442 00000C00 0.0.0e21
18:02:13.442 00000C00
18:02:13.442 00000C00 Select protocol for this CTC device.
18:02:13.442 00000C00
18:02:13.442 00000C00 1) Compatibility mode (default)
18:02:13.442 00000C00 2) Extended mode
18:02:13.442 00000C00 3) Compatibility mode for OS/390 and z/OS peers
18:02:13.442 00000C00
18:02:13.443 00000C00 >
18:02:21.197 00000C00 .1
18:02:21.350 00000C00 1
18:02:23.452 00000C00 ctc0: read: ch-0.0.0e20, write: ch-0.0.0e21,
proto: 0
18:02:23.452 00000C00
18:02:23.452 00000C00 Automatic configuration via DHCP?
18:02:23.452 00000C00
18:02:23.453 00000C00 1) Yes
18:02:23.453 00000C00 2) No
18:02:23.453 00000C00
18:02:23.453 00000C00 >
18:02:28.133 00000C00 .2
18:02:28.256 00000C00 2
18:02:28.256 00000C00
18:02:28.256 00000C00 Enter your IP address>
18:02:44.154 00000C00 .192.168.250.70
18:02:44.287 00000C00 192.168.250.70
18:02:44.287 00000C00
18:02:44.287 00000C00 Enter the IP address of the PLIP partner
192.168.250.70!>
18:02:54.966 00000C00 .192.168.250.69
18:02:55.122 00000C00 192.168.250.69
18:02:55.122 00000C00
18:02:55.122 00000C00 Enter the IP address of your name server. If
you do not use a name server,
18:02:55.122 00000C00 press ESC 192.168.250.70!>
18:02:55.137 00000C00 ctc0: connected with remote side
18:03:06.827 00000C00 .192.168.250.3
18:03:06.932 00000C00 192.168.250.3
18:03:06.932 00000C00
18:03:06.932 00000C00 Enter the IP address of the SMB server
192.168.250.69!>
18:03:12.019 00000C00 .192.168.250.69
18:03:12.123 00000C00 192.168.250.69
18:03:12.123 00000C00
18:03:12.123 00000C00 Enter the share name on the SMB server>
18:03:21.838 00000C00 .Public
18:03:21.944 00000C00 Public
18:03:21.944 00000C00
18:03:21.944 00000C00 Enter the directory on the server>
18:03:40.853 00000C00 .SLES10
18:03:40.957 00000C00 SLES10
18:03:40.957 00000C00
18:03:40.957 00000C00 If you want to access the share as guest,you do
not need to specify user name,
18:03:40.957 00000C00 password, and workgroup.
18:03:40.957 00000C00 Access the share as guest?
18:03:40.957 00000C00
18:03:40.957 00000C00 1) Yes
18:03:40.957 00000C00 2) No
18:03:40.957 00000C00
18:03:40.957 00000C00 >
18:03:44.348 00000C00 .1
18:03:44.457 00000C00 1
18:03:44.457 00000C00 Trying to mount the share
18:03:44.457 00000C00
18:03:44.457 00000C00 "//192.168.250.69/Public"
18:03:48.196 00000C00 CIFS VFS: Send error in SessSetup = -13
18:03:48.336 00000C00 CIFS VFS: cifs_mount failed w/return code = -13
18:03:48.346 00000C00
18:03:48.346 00000C00 *** SMB/CIFS mount failed
18:03:48.346 00000C00
18:03:48.346 00000C00 Choose the network protocol.
18:03:48.346 00000C00
18:03:48.346 00000C00 1) FTP
18:03:48.346 00000C00 2) HTTP
18:03:48.346 00000C00 3) NFS
18:03:48.346 00000C00 4) SMB / CIFS (Windows Share)
18:03:48.346 00000C00 5) TFTP
18:03:48.346 00000C00
18:03:48.346 00000C00 >
Post by Tim Pinkawa
Post by Joseph M. DeAngelo
I think I got no reply the last time because I failed to document my
issue. I'm trying to install SLES-10 under Hercules running under
Windows Vista. I have gotten things to IPL to a point, but I cannot
get SLES to load onto my virtual DASD. I have tried
*snip*
Installing mainframe Linux is unlike most other platforms. When you
IPL off the ins file or the tdf file, it's kind of like booting off a
floppy on a PC (with Hercules, you're actually booting off tape).
It'll get you started, but you need another source to finish the
installation. You're not actually booting with the full disc and
Hercules hardware has no concept of a "CD" or "DVD". (on the real
hardware today, you can directly access the CD through various
methods, but not with Hercules yet AFAIK) You need to make the CD
contents available over the network. Common ways of doing this is with
an FTP server, HTTP server, NFS server, or SMB (Windows file
sharing)
Post by Tim Pinkawa
server. Since you're already on a Windows platform, SMB is probably
the easiest. Share the installation folder through Windows, then on
the Hercules console, select SMB as your source. The server is the IP
address of your desktop machine and the folder is whatever name the
folder is shared as. If it's a CD-ROM drive, the default name is
probably D. Also make sure any firewalls you have don't block
Windows
Post by Tim Pinkawa
file sharing. If anything is unclear, let me know and I'll try to
clarify.
Hope this helps,
Tim
Tim Pinkawa
2007-03-26 00:52:00 UTC
Permalink
Post by Joseph M. DeAngelo
Thanks for the quick reply. I'll try anything. Unfortunately, I'm
short a few facts.
On my Windows Vista system, I enabled sharing on my DVD drive and
called the share name SLESonD to point to the entire DVD. That did
not work, so I copied the entire DVD to Public\SLES10 and enabled
sharing on Public. I can access Public from external machines just
I don't have Vista so I'm not entirely sure how public folders are set
up, but it seems like a major issue if each machine has one public
folder named Public. Open up a command prompt and type "net share" to
list the name and path of each share and make sure the 'Share name'
matches the 'Resource' you're trying to access.

Tim
Joseph M. DeAngelo
2007-03-26 01:40:07 UTC
Permalink
It looks like they replaced the "Documents and Settings" folder with
a "Users" folder. I suppose I did not even need to add a share for
Public since Users was already exposed.

Microsoft Windows [Version 6.0.6000]
Copyright (c) 2006 Microsoft Corporation. All rights reserved.

C:\Users\jmd>net share

Share name Resource Remark

----------------------------------------------------------------------
---------
C$ C:\ Default share
IPC$ Remote IPC
ADMIN$ C:\Windows Remote Admin
D D:\
Public C:\Users\Public
SLESonD D:\
Users C:\Users
The command completed successfully.


C:\Users\jmd>

I guess I'll try to find a way to jury rig an ftp server next. I'm
thinking that I'm missing something very fundamental. Are all Linux
under Hercules installations done as network installs?
Post by Tim Pinkawa
Post by Joseph M. DeAngelo
Thanks for the quick reply. I'll try anything. Unfortunately, I'm
short a few facts.
On my Windows Vista system, I enabled sharing on my DVD drive and
called the share name SLESonD to point to the entire DVD. That did
not work, so I copied the entire DVD to Public\SLES10 and enabled
sharing on Public. I can access Public from external machines just
I don't have Vista so I'm not entirely sure how public folders are set
up, but it seems like a major issue if each machine has one public
folder named Public. Open up a command prompt and type "net share" to
list the name and path of each share and make sure the 'Share name'
matches the 'Resource' you're trying to access.
Tim
Paul Dembry
2007-03-26 16:26:39 UTC
Permalink
I guess I'll try to find a way to jury rig an ftp server next. I'm
thinking that I'm missing something very fundamental. Are all Linux
under Hercules installations done as network installs?
Even better from a debugging standpoint is to use an HTTP installation. You
can often get much clearer error messages from Apache.
Paul
Joseph M. DeAngelo
2007-03-26 17:56:40 UTC
Permalink
I don't need to do this. I've found the problem. The process of
installing over a network from a windows share that is served by a
Windows Vista machine does not work. I created a share on an XP
machine and I'm finally getting the install to work.

Advice to anyone using HercGUI on Windows. These matters are either
not documented or obscurely documented. No slight intended.

1) YOU MUST Run HercGUI as Administrator
2) you may not load the OS from a Windows share served by Windows
Vista. I read a report somewhere to the effect that Samba has a
similar issue.
Post by Paul Dembry
I guess I'll try to find a way to jury rig an ftp server next. I'm
thinking that I'm missing something very fundamental. Are all Linux
under Hercules installations done as network installs?
Even better from a debugging standpoint is to use an HTTP
installation. You
Post by Paul Dembry
can often get much clearer error messages from Apache.
Paul
David Wade
2007-03-26 19:07:36 UTC
Permalink
I think the issues with VISTA are that by default it insists on SMB signing.

Dave Wade
Illegitimi Non Carborundum

-----Original Message-----
From: hercules-390-***@public.gmane.org [mailto:hercules-390-***@public.gmane.org] On Behalf Of Joseph M. DeAngelo
Sent: 26 March 2007 18:57
To: hercules-390-***@public.gmane.org
Subject: [hercules-390] Re: SLES-10 install issue



I don't need to do this. I've found the problem. The process of
installing over a network from a windows share that is served by a
Windows Vista machine does not work. I created a share on an XP
machine and I'm finally getting the install to work.

Advice to anyone using HercGUI on Windows. These matters are either
not documented or obscurely documented. No slight intended.

1) YOU MUST Run HercGUI as Administrator
2) you may not load the OS from a Windows share served by Windows
Vista. I read a report somewhere to the effect that Samba has a
similar issue.
Post by Paul Dembry
I guess I'll try to find a way to jury rig an ftp server next. I'm
thinking that I'm missing something very fundamental. Are all Linux
under Hercules installations done as network installs?
Even better from a debugging standpoint is to use an HTTP
installation. You
Post by Paul Dembry
can often get much clearer error messages from Apache.
Paul
[Non-text portions of this message have been removed]
Joseph M. DeAngelo
2007-03-26 20:47:36 UTC
Permalink
Thanks, but I'm not sure what to make of that.

Could you please illustrate what I might have done in order to get
the SLES-10 DVD to be read? Or is it the case that I had to use an
XP server?

I'm really curous aboutt the fact that zSeries Linux discusses the
ability to load from a CD-ROM which I imagine is connected to a real
mainframe or VM. Is there no support for such a device within
Hercules?
Post by David Wade
I think the issues with VISTA are that by default it insists on SMB signing.
Dave Wade
Illegitimi Non Carborundum
-----Original Message-----
Sent: 26 March 2007 18:57
Subject: [hercules-390] Re: SLES-10 install issue
I don't need to do this. I've found the problem. The process of
installing over a network from a windows share that is served by a
Windows Vista machine does not work. I created a share on an XP
machine and I'm finally getting the install to work.
Advice to anyone using HercGUI on Windows. These matters are either
not documented or obscurely documented. No slight intended.
1) YOU MUST Run HercGUI as Administrator
2) you may not load the OS from a Windows share served by Windows
Vista. I read a report somewhere to the effect that Samba has a
similar issue.
Post by Paul Dembry
I guess I'll try to find a way to jury rig an ftp server next. I'm
thinking that I'm missing something very fundamental. Are all Linux
under Hercules installations done as network installs?
Even better from a debugging standpoint is to use an HTTP
installation. You
Post by Paul Dembry
can often get much clearer error messages from Apache.
Paul
[Non-text portions of this message have been removed]
Greg Smith
2007-03-26 21:20:28 UTC
Permalink
Post by Joseph M. DeAngelo
Thanks, but I'm not sure what to make of that.
Could you please illustrate what I might have done in order to get
the SLES-10 DVD to be read? Or is it the case that I had to use an
XP server?
I'm really curous aboutt the fact that zSeries Linux discusses the
ability to load from a CD-ROM which I imagine is connected to a real
mainframe or VM. Is there no support for such a device within
Hercules?
You can _load_ from CD or DVD on hercules just like you can on a real
machine. I'm not sure you can install linux (or any other OS) on a real
machine from the CD or DVD (which is physically in the HMC). I've
always done networking installs on a real machine.If you can, then I
suppose the CD or DVD is certainly not a CCW device. Hercules as yet
does not support non-CCW devices (ie qdio, siga).

I don't do windows much anymore and certainly not Vista. However, there
may be problems on Vista due to the WinPCAP driver. Don't drivers on
Vista have to be signed? Maybe Fish will enlighten us about what he
knows about it.

Greg
paul_landay
2007-03-27 11:28:52 UTC
Permalink
Post by Joseph M. DeAngelo
I think I got no reply the last time because I failed to document my
issue. I'm trying to install SLES-10 under Hercules running under
Windows Vista. I have gotten things to IPL to a point, but I cannot
get SLES to load onto my virtual DASD.
<snip>
Post by Joseph M. DeAngelo
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
<snip>
Post by Joseph M. DeAngelo
Yet, the DVD from which I booted is still in drive D:. If I choose
option 4, it similarly cannot find the CD from which to install the
system. What must I do to get around this.??
I haven't done sles10 under hercules, but below are some notes
from installing sles10 on a real s390x system, using a sles10-i686
system as an FTP install server for the sles10-s390x DVD. The
notes below show using a real qdio device, but using ctc should
be similiar.

There is some talk of CTC in linux-s390* being removed entirely
in the next major Novell/RedHat releases. According to this page:
http://www.novell.com/documentation/sles10/index.html?page=/documentation/sles10/sles_zseries/data/sec_appdendix_inst_netcontypes.html
CTC is not supported (but may still work) for install in sles10.

Setting up the sles10-i686 FTP install server:
mkdir DVD1
mount -r -o loop SLES-10-s390x-GMC.iso DVD1
# Set up the install server
mkdir /sles10
yast2
Misc
Installation Server
Server Configuration
Configure as FTP Source
Directory to Contain Sources: /sles10
FTP Server Root Directory: /srv/ftp
Directory Alias: <blank>
Add
Source Name: GMC
Use ISO Images
directory with ISO Images: /home/planday/sles10-s390x

Using the sles10-s390x installer:
4) Start Installation or System
1) Start Installation or Update
2) Network
1) FTP
1) OSA-2 or OSA Express
1) QDIO
1) Ethernet
0.0.2bd0
0.0.2bd1
0.0.2bd2
GIGE2BD0
2) No (to OSI Layer 2)
2) No (to DHCP)
<snip> ip info
1) Yes
ftp userid
ftp password
2) No (Do not use HTTP proxy)
../../sles10/GMC

This page talks about making the SLES10 install media
available via a Windows server (NFS, SMB, FTP):
http://www.novell.com/documentation/sles10/index.html?page=/documentation/sles10/sles_zseries/data/sec_prep_makeavail.html
There are some significant limitations to using a
Windows machine as an install server.

Paul Landay
Joseph M. DeAngelo
2007-03-27 16:19:54 UTC
Permalink
Thank you for that example. I had done an S/390 install of Linux 7
under Redhat 8 many years ago. I recall it being much more of a
control file driven process. I wanted to try the Windows environment
because I liked the HercGUI by Fish. I do recall that the starter
system under Linux 7 was able to install from the CD's of the host
Linux Intel system. I thought I must not be "getting" something
about how to do it.

I do have a question. If the CTC interface is no longer going to be
supportted, how is one to create a network connection with the
outside world? I have not noticed any documentation about that. If
you could point me to some documentation about the preferred
interface and some notion of how one defines that to Hercules, that
would be most helpful.

Thanks.
Post by paul_landay
Post by Joseph M. DeAngelo
I think I got no reply the last time because I failed to document my
issue. I'm trying to install SLES-10 under Hercules running
under
Post by paul_landay
Post by Joseph M. DeAngelo
Windows Vista. I have gotten things to IPL to a point, but I cannot
get SLES to load onto my virtual DASD.
<snip>
Post by Joseph M. DeAngelo
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
<snip>
Post by Joseph M. DeAngelo
Yet, the DVD from which I booted is still in drive D:. If I
choose
Post by paul_landay
Post by Joseph M. DeAngelo
option 4, it similarly cannot find the CD from which to install the
system. What must I do to get around this.??
I haven't done sles10 under hercules, but below are some notes
from installing sles10 on a real s390x system, using a sles10-i686
system as an FTP install server for the sles10-s390x DVD. The
notes below show using a real qdio device, but using ctc should
be similiar.
There is some talk of CTC in linux-s390* being removed entirely
http://www.novell.com/documentation/sles10/index.html?
page=/documentation/sles10/sles_zseries/data/sec_appdendix_inst_netcon
types.html
Post by paul_landay
CTC is not supported (but may still work) for install in sles10.
mkdir DVD1
mount -r -o loop SLES-10-s390x-GMC.iso DVD1
# Set up the install server
mkdir /sles10
yast2
Misc
Installation Server
Server Configuration
Configure as FTP Source
Directory to Contain Sources: /sles10
FTP Server Root Directory: /srv/ftp
Directory Alias: <blank>
Add
Source Name: GMC
Use ISO Images
directory with ISO Images: /home/planday/sles10-s390x
4) Start Installation or System
1) Start Installation or Update
2) Network
1) FTP
1) OSA-2 or OSA Express
1) QDIO
1) Ethernet
0.0.2bd0
0.0.2bd1
0.0.2bd2
GIGE2BD0
2) No (to OSI Layer 2)
2) No (to DHCP)
<snip> ip info
1) Yes
ftp userid
ftp password
2) No (Do not use HTTP proxy)
../../sles10/GMC
This page talks about making the SLES10 install media
http://www.novell.com/documentation/sles10/index.html?
page=/documentation/sles10/sles_zseries/data/sec_prep_makeavail.html
Post by paul_landay
There are some significant limitations to using a
Windows machine as an install server.
Paul Landay
paul_landay
2007-03-27 16:47:15 UTC
Permalink
Post by Joseph M. DeAngelo
Thank you for that example. I had done an S/390 install of Linux 7
under Redhat 8 many years ago. I recall it being much more of a
control file driven process. I wanted to try the Window environment
because I liked the HercGUI by Fish. I do recall that the starter
system under Linux 7 was able to install from the CD's of the host
Linux Intel system. I thought I must not be "getting" something
about how to do it.
I only started using control files with RHEL5-s390x installs,
so I wasn't aware of them when I did SLES10-s390x stuff.
I found the RHEL5 control files to be very syntax sensitive,
i.e. extra blanks, missing or extra quotes caused the parser
within the installer (anaconda?) to choke.
Post by Joseph M. DeAngelo
I do have a question. If the CTC interface is no longer going to be
supportted, how is one to create a network connection with the
outside world? I have not noticed any documentation about that. If
you could point me to some documentation about the preferred
interface and some notion of how one defines that to Hercules, that
would be most helpful.
For real zSeries systems the qeth/qdio OSA seems to be the
typical environment. When doing Linux on zSeries in a z/VM
environment the layer2/vswitch support gives you virtual OSAs.

For hercules I think LCS is still viable.

Paul Landay
Joseph M. DeAngelo
2007-03-28 20:10:13 UTC
Permalink
I see that you are correct about the Novell site showing CTC as
unsupported, but my SLES-10 has no such warning. I tried to convert
to LCS anyway and ran into several problems.

1) until I get the networking defined I get a warning message every
second like this:

10:22:31.354 00000E44 HHCLC042E Port 00: Read error: Permission denied
10:22:32.354 00000E44 HHCLC042E Port 00: Read error: Permission denied
10:22:33.354 00000E44 HHCLC042E Port 00: Read error: Permission denied

2) I answered the questions as best I knew how, but when it asked for
a port number, I was not sure what to answer and used the example in
the Novell document -- port 2. It seems to like that.

3) As soon as I attempted to connect with the samba share zLinux
crashed. Below is the Herc log with the Read error messages
excerpted. It does this after I specify the gateway IP if I use the
IP of the host machine.

10:20:58.461 00000E44 *** Could not find the SUSE Linux Enterprise
Server 10 Installation CD.
10:20:58.461 00000E44
10:20:58.461 00000E44 Activating manual setup program.
10:20:58.461 00000E44
10:20:58.461 00000E44 >>> Linuxrc v2.0.46 (Kernel 2.6.16.21-0.8-
default) <<<
10:20:58.692 00000E44
10:20:58.692 00000E44 Main Menu
10:20:58.692 00000E44
10:20:58.692 00000E44 1) Settings
10:20:58.692 00000E44 2) System Information
10:20:58.692 00000E44 3) Kernel Modules (Hardware Drivers)
10:20:58.692 00000E44 4) Start Installation or System
10:20:58.693 00000E44 5) Verify Installation CD-ROM/DVD
10:20:58.693 00000E44 6) Eject CD
10:20:58.693 00000E44 7) Exit or Reboot
10:20:58.693 00000E44 8) Power off
10:20:58.693 00000E44
10:20:58.693 00000E44 >
10:21:43.935 00000E44 .4
10:21:44.037 00000E44 4
10:21:44.037 00000E44
10:21:44.037 00000E44 Start Installation or System
10:21:44.037 00000E44
10:21:44.037 00000E44 1) Start Installation or Update
10:21:44.037 00000E44 2) Boot Installed System
10:21:44.037 00000E44 3) Start Rescue System
10:21:44.037 00000E44
10:21:44.037 00000E44 >
10:21:47.730 00000E44 .1
10:21:47.836 00000E44 1
10:21:47.836 00000E44
10:21:47.836 00000E44 Choose the source medium.
10:21:47.836 00000E44
10:21:47.836 00000E44 1) CD-ROM
10:21:47.836 00000E44 2) Network
10:21:47.836 00000E44 3) Hard Disk
10:21:47.836 00000E44
10:21:47.836 00000E44 >
10:21:50.792 00000E44 .2
10:21:50.897 00000E44 2
10:21:50.897 00000E44
10:21:50.897 00000E44 Choose the network protocol.
10:21:50.897 00000E44
10:21:50.897 00000E44 1) FTP
10:21:50.897 00000E44 2) HTTP
10:21:50.897 00000E44 3) NFS
10:21:50.897 00000E44 4) SMB / CIFS (Windows Share)
10:21:50.897 00000E44 5) TFTP
10:21:50.897 00000E44
10:21:50.897 00000E44 >
10:21:59.789 00000E44 .4
10:21:59.897 00000E44 4
10:21:59.897 00000E44
10:21:59.897 00000E44 Please select the type of your network device.
10:21:59.897 00000E44
10:21:59.897 00000E44 1) OSA-2 or OSA Express
10:21:59.897 00000E44 2) Hipersockets
10:21:59.897 00000E44 --------------------
10:21:59.897 00000E44 3) Channel To Channel (CTC)
10:21:59.897 00000E44 4) ESCON
10:21:59.897 00000E44 5) Inter-User Communication Vehicle (IUCV)
10:21:59.897 00000E44
10:21:59.897 00000E44 >
10:22:03.013 00000E44 .1
10:22:03.118 00000E44 1
10:22:03.118 00000E44
10:22:03.118 00000E44 Please choose the CCW bus interface.
10:22:03.118 00000E44
10:22:03.118 00000E44 1) QDIO
10:22:03.118 00000E44 2) LCS
10:22:03.118 00000E44
10:22:03.118 00000E44 >
10:22:05.496 00000E44 .2
10:22:05.599 00000E44 2
10:22:05.599 00000E44
10:22:05.599 00000E44 Please choose the physical medium.
10:22:05.599 00000E44
10:22:05.599 00000E44 1) Ethernet
10:22:05.599 00000E44 2) Token Ring
10:22:05.599 00000E44
10:22:05.599 00000E44 >
10:22:08.344 00000E44 .1
10:22:08.449 00000E44 1
10:22:15.358 00000E44 lcs: Loading LCS driver
10:22:16.678 00000E44
10:22:16.678 00000E44 0.0.fc20 3088/60
10:22:16.678 00000E44 0.0.fc21 3088/60
10:22:16.678 00000E44
10:22:16.678 00000E44
10:22:16.678 00000E44 Device address for read channel>
10:22:30.442 00000E44 .0.0.fc20
10:22:30.549 00000E44 0.0.fc20
10:22:30.549 00000E44
10:22:30.549 00000E44 Device address for write channel>
10:22:37.419 00000E44 .0.0.fc21
10:22:37.521 00000E44 0.0.fc21
10:22:37.521 00000E44
10:22:37.521 00000E44 Enter the relative port number>
10:23:28.912 00000E44 .2
10:23:29.014 00000E44 2
10:23:31.983 00000E44 HHCTU024E tap0: Invalid gateway address: NULL.
10:23:37.086 00000E44 lcs: LCS device eth0 without IPv6 support
10:23:37.086 00000E44 lcs: LCS device eth0 with Multicast support
10:23:37.106 00000E44
10:23:37.106 00000E44 Automatic configuration via DHCP?
10:23:37.106 00000E44
10:23:37.106 00000E44 1) Yes
10:23:37.106 00000E44 2) No
10:23:37.106 00000E44
10:23:37.106 00000E44 >
10:23:43.160 00000E44 .2
10:23:43.266 00000E44 2
10:23:43.266 00000E44
10:23:43.266 00000E44 Enter your IP address>
10:23:55.407 00000E44 .192.168.250.70
10:23:55.512 00000E44 192.168.250.70
10:23:55.512 00000E44
10:23:55.512 00000E44 Enter your netmask. For a normal class C
network, this is usually
10:23:55.512 00000E44 255.255.255.0 255.255.255.0!>
10:24:04.672 00000E44 .255.255.255.0
10:24:04.779 00000E44 255.255.255.0
10:24:04.779 00000E44
10:24:04.779 00000E44 If you need a gateway to reach the server,
enter the IP address of the
10:24:04.779 00000E44 gateway. If you do not need a gateway, enter
your own IP address
10:24:04.779 00000E44 192.168.250.70!>
10:24:31.277 00000E44 .192.168.250.70
10:24:31.384 00000E44 192.168.250.70
10:24:32.622 00000E44
10:24:32.622 00000E44 Enter the IP address of your name server. If
you do not use a name server,
10:24:32.622 00000E44 press ESC 192.168.250.70!>
10:24:38.549 00000E44 .192.168.250.3
10:24:38.652 00000E44 192.168.250.3
10:24:38.652 00000E44
10:24:38.652 00000E44 Enter the IP address of the SMB server
192.168.250.70!>
10:24:44.337 00000E44 .192.168.250.44
10:24:44.443 00000E44 192.168.250.44
10:24:44.443 00000E44
10:24:44.443 00000E44 Enter the share name on the SMB server>
10:24:49.090 00000E44 .home
10:24:49.194 00000E44 home
10:24:49.194 00000E44
10:24:49.194 00000E44 Enter the directory on the server>
10:24:53.316 00000E44 .SLES10
10:24:53.424 00000E44 SLES10
10:24:53.424 00000E44
10:24:53.424 00000E44 If you want to access the share as guest,you do
not need to specify user name,
10:24:53.424 00000E44 password, and workgroup.
10:24:53.424 00000E44 Access the share as guest?
10:24:53.424 00000E44
10:24:53.424 00000E44 1) Yes
10:24:53.424 00000E44 2) No
10:24:53.424 00000E44
10:24:53.424 00000E44 >
10:24:55.302 00000E44 .1
10:24:55.404 00000E44 1
10:24:55.404 00000E44 Trying to mount the share
10:24:55.405 00000E44
10:24:55.405 00000E44 "//192.168.250.44/home"
10:24:58.384 00000E44 HHCCP014I CPU0000: Operation exception
CODE=0001 ILC=2
10:24:58.384 00000E44 PSW=04040001 80000000 00000000209F48FE
INST=0001 ?????
10:24:58.384 00000E44 R0=0000000000000000 R1=0000000000503098
R2=000000000000002D R3=0400000000000000
10:24:58.384 00000E44 R4=00000000209F48FA R5=0000000000000000
R6=0000000000000000 R7=000000000000000B
10:24:58.384 00000E44 R8=0000000000000006 R9=000000001E526A30
RA=000000001E9BE640 RB=000000001E9BE8F8
10:24:58.384 00000E44 RC=000000001E525400 RD=00000000209FD208
RE=00000000209F48FA RF=000000001E42D9A8
10:24:58.384 00000E44 C0=0000000014B54E02 C1=00000000005C7007
C2=00000000000103C0 C3=0000000000000000
10:24:58.384 00000E44 C4=0000000000000000 C5=FFFFFFFFFFFFFFFF
C6=0000000010000000 C7=00000000005C7007
10:24:58.384 00000E44 C8=0000000000000000 C9=0000000000000000
CA=0000000000000000 CB=0000000000000000
10:24:58.384 00000E44 CC=0000000000000000 CD=000000001EAC81C7
CE=00000000D9000000 CF=0000000000000000
10:24:58.393 00000E44 kernel BUG at drivers/s390/net/lcs.c:702
10:24:58.393 00000E44 illegal operation: 0001 #1!
10:24:58.393 00000E44 CPU: 0 Tainted: G X
10:24:58.393 00000E44 Process swapper (pid: 0, task:
0000000000500310, ksp: 0000000000593d78)
10:24:58.393 00000E44 Krnl PSW : 0404000180000000 00000000209f48fe
(lcs_irq+0x77a/0xafc lcs!)
10:24:58.394 00000E44 Krnl GPRS: 0000000000000000 0000000000503098
000000000000002d 0400000000000000
10:24:58.394 00000E44 00000000209f48fa 0000000000000000
0000000000000000 000000000000000b
10:24:58.394 00000E44 0000000000000006 000000001e526a30
000000001e9be640 000000001e9be8f8
10:24:58.394 00000E44 000000001e525400 00000000209fd208
00000000209f48fa 000000001e42d9a8
10:24:58.394 00000E44 Krnl Code: a7 58 00 03 41 a0 a1 58 50 50 b0 00
b9 09 00 ba eb 1b 00 05
10:24:58.394 00000E44 Call Trace:
10:24:58.394 00000E44 ( <00000000209f48fa>! lcs_irq+0x776/0xafc lcs!)
10:24:58.394 00000E44 <000000000033c394>!
ccw_device_call_handler+0x84/0xd0
10:24:58.394 00000E44 <0000000000338aac>! ccw_device_irq+0xfc/0x190
10:24:58.394 00000E44 <000000000033255c>! do_IRQ+0x108/0x154
10:24:58.394 00000E44 <000000000010fccc>! io_return+0x0/0x10
10:24:58.394 00000E44 <000000000042eaba>!
_spin_unlock_irqrestore+0x36/0x40
10:24:58.394 00000E44 ( <000000000000000a>! 0xa)
10:24:58.394 00000E44 <070000001e9be8d8>! 0x70000001e9be8d8
10:24:58.394 00000E44 <000000000038c012>! qdisc_restart+0x13e/0x280
10:24:58.395 00000E44 <000000000037109e>! dev_queue_xmit+0x48a/0x70c
10:24:58.395 00000E44 <00000000003ec932>! arp_solicit+0x42a/0x450
10:24:58.395 00000E44 <000000000037a4b2>!
neigh_timer_handler+0x35e/0x428
10:24:58.395 00000E44 <0000000000153bd4>!
run_timer_softirq+0x660/0x704
10:24:58.395 00000E44 <0000000000149014>! __do_softirq+0x6c/0x108
10:24:58.395 00000E44 <000000000010f046>! do_softirq+0xba/0xf4
10:24:58.395 00000E44 <000000000010fe54>! ext_no_vtime+0x16/0x1a
10:24:58.395 00000E44 <0000000000107e2e>! cpu_idle+0x192/0x1b4
10:24:58.395 00000E44 ( <0000000000107d0a>! cpu_idle+0x6e/0x1b4)
10:24:58.395 00000E44 <0000000000594836>! start_kernel+0x2ee/0x2fc
10:24:58.395 00000E44 <0000000000100046>! _stext+0x46/0xa0
10:24:58.395 00000E44
10:24:58.395 00000E44 <0>Kernel panic - not syncing: Fatal exception
in interrupt
10:24:58.395 00000E44 HHCCP011I CPU0000: Disabled wait state
10:24:58.396 00000E44 PSW=00020001 80000000 0000000000104C4E
Post by paul_landay
Post by Joseph M. DeAngelo
Thank you for that example. I had done an S/390 install of Linux 7
under Redhat 8 many years ago. I recall it being much more of a
control file driven process. I wanted to try the Window
environment
Post by paul_landay
Post by Joseph M. DeAngelo
because I liked the HercGUI by Fish. I do recall that the
starter
Post by paul_landay
Post by Joseph M. DeAngelo
system under Linux 7 was able to install from the CD's of the host
Linux Intel system. I thought I must not be "getting" something
about how to do it.
I only started using control files with RHEL5-s390x installs,
so I wasn't aware of them when I did SLES10-s390x stuff.
I found the RHEL5 control files to be very syntax sensitive,
i.e. extra blanks, missing or extra quotes caused the parser
within the installer (anaconda?) to choke.
Post by Joseph M. DeAngelo
I do have a question. If the CTC interface is no longer going to be
supportted, how is one to create a network connection with the
outside world? I have not noticed any documentation about that.
If
Post by paul_landay
Post by Joseph M. DeAngelo
you could point me to some documentation about the preferred
interface and some notion of how one defines that to Hercules, that
would be most helpful.
For real zSeries systems the qeth/qdio OSA seems to be the
typical environment. When doing Linux on zSeries in a z/VM
environment the layer2/vswitch support gives you virtual OSAs.
For hercules I think LCS is still viable.
Paul Landay
Continue reading on narkive:
Loading...