Problem installing F19 under Hercules 3.09
Ian Shorter
mcisho at yahoo.com
Mon Aug 19 14:43:04 UTC 2013
----- Original Message -----
From: Jan Stodola <jstodola at redhat.com>
To: Ian Shorter <mcisho at yahoo.com>; s390x at lists.fedoraproject.org
Cc:
Sent: Monday, 19 August 2013, 14:05
Subject: Re: Problem installing F19 under Hercules 3.09
On 08/18/2013 02:34 PM, Ian Shorter wrote:
> I'm trying to install F19 s390x under Hercules 3.09 running on an F19 x86_64 machine, but without success. When I had Hercules defined with NUMCPU 1, I usually ended up with the install in a 6-instruction loop. Having read elsewhere that single cpu's might be a problem, Hercules is now defined with NUMCPU 2, which produces different results.
>
> I always get to the "Please ssh install at blah.blah.blah (192.168.236.200) to begin the install" message. I ssh and start the vncveiwer. The vncveiwer window in blank (black), although sometimes a grey rectangle appears, until it is closed. The ssh messages for the last three attempts were:-
>
> Attempt one.
>
> Please manually connect your vnc client to blah.blah.blah:1 (192.168.236.200) to begin the install.
> [xcb] Unknown request in queue while dequeuing
> [xcb] Most likely this is a multi-threaded client and XInitThreads has not been called
> [xcb] Aborting, sorry about that.
> python: xcb_io.c:179: dequeue_pending_request: Assertion `!xcb_xlib_unknown_req_in_deq' failed.
>
> Attempts two and three
>
> Please manually connect your vnc client to blah.blah.blah:1 (192.168.236.200) to begin the install.
>
> (anaconda:824): Gdk-WARNING **: anaconda: Fatal IO error 11 (Resource temporarily unavailable) on X server :1.
>
> My generic.prm contains:-
> ro ramdisk_size=40000 cio_ignore=all,!0.0.0009 rd.dasd=0.0.0120 ip=192.168.236.200:192.168.236.100:192.168.236.100:24:blah.blah.blah:ctc0:none rd.znet=ctc,0.0.0600,0.0.0601,protocol=0 root=live:http://dl.fedoraproject.org/pub/fedora-secondary/releases/19/Fedora/s390x/os/images/install.img nameserver=192.168.3.206 vnc
>
> I assume the problem is a timing issue, but I don't know where to start looking. What info, if any, can I provide? Any suggestions gratefully received.
>
> Regards, Ian
>
> _______________________________________________
> s390x mailing list
> s390x at lists.fedoraproject.org
> https://admin.fedoraproject.org/mailman/listinfo/s390x
Hi Ian,
I also have F19/x86_64 with hercules-3.09-1.fc19 and installation of
F19/s390x in vnc mode is running fine so far - packages are being
installed at the moment. Here are my configuration files:
hercules.cnf contains:
CPUSERIAL 002623 # CPU serial number
CPUMODEL 2064 # CPU model number: 3090, 7490, 2064
MAINSIZE 1024 # Main storage size in megabytes
NUMCPU 2 # Number of CPUs
CNSLPORT 3270 # TCP port number to which consoles connect
OSTAILOR LINUX # OS tailoring
LOADPARM 0120.... # IPL parameter
ARCHMODE ESAME # Architecture mode S/370, ESA/390 or ESAME
TZOFFSET +0100 # Central Europe
LOGOPT NOTIMESTAMP # Avoid timestamps for log messages
TIMERINT 200 # Increase timers update interval, improves
performance
TODDRAG 2 # Higher TOD clock drag means less interrupts ->
higher performance
PANRATE SLOW # Slowest update
TRACEOPT NOREGS # Don't display registers
LDMOD hdt3088.so hdt3420.so hdt3505.so
000C 3505 /home/jstodola/fedora_s390x/kernel.img
/home/jstodola/fedora_s390x/parm /home/jstodola/fedora_s390x/initrd.img
autopad
0120 3390 /home/jstodola/fedora_s390x/disk.img
0600,0601 CTCI -n /dev/net/tun 192.168.1.3 192.168.1.4
parameter file contains:
ro ramdisk_size=40000 cio_ignore=all,!0.0.0009 rd.dasd=0.0.0120
rd.znet=ctc,0.0.0600,0.0.0601,protocol=0
ip=192.168.1.3:192.168.1.4:192.168.1.4:255.255.255.0::ctc0:none
nameserver=xx.xx.xx.xx
inst.repo=http://secondary.fedoraproject.org/pub/fedora-secondary/releases/19/Fedora/s390x/os/
I hope it helps.
Regards,
Jan
Hi Jan
Thanks for your info, sadly it didn't help me, I still get the same problem(s). What processor does you machine have? Mine is an Intel i3 dual core.
Regards, Ian
More information about the s390x
mailing list