Re: Debian 9 on hercules
In the mean time the hang problem has been fixed, on both the official Hyperion and SDL Fish Hyperion forks, and also on my fork of the Spinhawk Hercules (https://github.com/Peter-J-Jansen/spinhawk; a pull request has been issued). However, installing Debian 9 directly under Hercules still encounters problems with both the CTCI and OSA layer 2 and layer 3 devices. (I will investigate this further after my vacation, and try to find and fix the problem.) Only the installation of Debian 9 under VM works fine. The resulting Debian 9 works fine, also when IPL‘d directly under Hercules. Peter Jansen Sent from my iPhone > On 7 Feb 2018, at 01:25, Jerry Heyman <heym...@acm.org> wrote: > > I have downloaded the latest Debian 9 DVD ISO for s390x - > debian-9.3.0-s390x-DVD-1.iso - and the installation hang > issue is still present. Is there an actual solution for Debian 9, or can > someone point me to where I can download a > Debian 8 s390x ISO? > > Thanks! > > jerry > > > > -- > Sent from: http://debian.2.n7.nabble.com/debian-s390-f1775584.html >
Re: Debian 9 on hercules
I have downloaded the latest Debian 9 DVD ISO for s390x - debian-9.3.0-s390x-DVD-1.iso - and the installation hang issue is still present. Is there an actual solution for Debian 9, or can someone point me to where I can download a Debian 8 s390x ISO? Thanks! jerry -- Sent from: http://debian.2.n7.nabble.com/debian-s390-f1775584.html
Re: Debian 9 on hercules
I too have experienced the installation problem of Debian 9.2.1 on Hercules
ending with the last visible message on the Hercules console log being
"Configure the network device".
Reading the assumption of a possible Hercules bug in this thread, I verified
the Hercules source ("service.c"), and added some extra debugging code. The
result of this (bit more than trivial) exercise is that I cannot find any
problems on the Hercules side of things. The fact that Debian 8.9.0 does
this correctly also reinforces my suspicion that this is probably not a
Hercules bug, but rather a Debian 9 or Debian 9 installer bug.
As a side note, my successful circumvention to obtain a working Debian 9.2.1
s390x installation was to perform it under VM under Hercules. The final
result IPL's just fine under Hercules without VM, using Hercules Spinhawk
3.13 or Hercules 4.0 Hyperion, both the official Hyperion as well as the SDL
Hyperion by "Fish". I am now in the process of (a) trying to find out why
the CTCM device does not always come on-line by itself, sometimes I need to
"shutdown -r now" a few times on the Hercules console, (b) learning how to
do a persistent addition of an LCS device, (c) repeating the same
installation with a QETH device under Hyperion, which works, but also not
always comes on-line by itself, and if it does, ignores the static IP
address setup but goes DHCP instead. I might need to ask for support later,
right now I'm still in the learning phase of things.
Thanks,
Peter J. Jansen
Re: Debian 9 on hercules
On 08/19/2017 09:34 PM, Philipp Kern wrote: >> So it's not kernel issue or anything else. It must be something wrong >> with installer itself. Should I report a problem somewhere? or we are >> only ones who can't do fresh install on hercules? > > I'm happy to retest if you can give me the hercules.cnf you used. Bercik sent me their config and I'm able to confirm the bad behavior. But it looks to me as if console messages are swallowed. As soon as I add sleep() calls around all my writes, they succeed. (Which makes printf debugging very weird.) And indeed, if I enter ".1" it continues with "The following device numbers might belong to CTC or ESCON connections.". So all that happens is that either Hercules or the kernel while sending swallows the output and you can't actually see the prompts. That also matches the fact that there are very few startup messages from the kernel altogether. Essentially every message that doesn't have a bunch of other messages following (plus the first of the batch) lands on the console, the other ones are discarded. That makes me incredibly suspicious that this is a problem in Hercules. It's also not in the typescript generated by script(1), so it's not simply overwriting screen content either. I guess we'd need to either raise this with the Hercules people or instrument Hercules to see where the lines are missed. Kind regards Philipp Kern signature.asc Description: OpenPGP digital signature
Re: Debian 9 on hercules
On 19.08.2017 20:40, Bercik wrote: > Hello again, > > I did it! Problem is not fixed, but I figured out a workaround: > - install Debian 8.1 > - do upgrade with 9 sources.list > - do dist-upgrade after that > > > proof: > bercik@rescue:~$ cat /etc/issue.net > Debian GNU/Linux 9 > bercik@rescue:~$ uname -a > Linux rescue 4.9.0-3-s390x #1 SMP Debian 4.9.30-2+deb9u3 (2017-08-06) > s390x GNU/Linux > bercik@rescue:~$ date > sob, 19 sie 2017, 20:38:28 CEST > bercik@rescue:~$ > > > So it's not kernel issue or anything else. It must be something wrong > with installer itself. Should I report a problem somewhere? or we are > only ones who can't do fresh install on hercules? I'm happy to retest if you can give me the hercules.cnf you used. Kind regards Philipp Kern
Re: Debian 9 on hercules
Title: Re: Debian 9 on hercules Hello again, I did it! Problem is not fixed, but I figured out a workaround: - install Debian 8.1 - do upgrade with 9 sources.list - do dist-upgrade after that proof: bercik@rescue:~$ cat /etc/issue.net Debian GNU/Linux 9 bercik@rescue:~$ uname -a Linux rescue 4.9.0-3-s390x #1 SMP Debian 4.9.30-2+deb9u3 (2017-08-06) s390x GNU/Linux bercik@rescue:~$ date sob, 19 sie 2017, 20:38:28 CEST bercik@rescue:~$ So it's not kernel issue or anything else. It must be something wrong with installer itself. Should I report a problem somewhere? or we are only ones who can't do fresh install on hercules? -- Regards, Bartłomiej "Bercik" Kacprzak W Twoim liście datowanym 1 sierpnia 2017 (20:47:50) można przeczytać: Hello list, I also confirm Bercik's finding from an previous e-mail (18 Jun 2017, https://lists.debian.org/debian-s390/2017/06/msg6.html) - Debian 9 IPL stops when network interfaces configuration is coming up. Last visible message is "Configure the network device". Debian 8.9 with same Hercules configuration shows the expected network configuration menu. Tested with: Debian 9.1 netinst p.s. while using Debian 8.9, the SSH server for the installer fails to sent the password prompt (ie. transport layer is working, but user authentication isn't) - any ideas? BR Ivan
AW: Debian 9 on hercules
I had a similar problem on a z13 configuring multiple OSAs. Generally I let sshd wait for the interfaces to be fully initialized and sshd would successfully start afterwards and the system came up.I'll be able to check my modification on Monday, maybe that will help on hercules, too.Greetings,Ben.--So Long, and Thanks for All the FishVon: Ivan PozderovicGesendet: Dienstag, 1. August 2017 21:06An: debian-s390@lists.debian.orgAntwort an: Ivan PozderovicBetreff: Re: Debian 9 on herculesHello list,I also confirm Bercik's finding from an previous e-mail (18 Jun 2017, https://lists.debian.org/debian-s390/2017/06/msg6.html) - Debian 9 IPL stops when network interfaces configuration is coming up.Last visible message is "Configure the network device".Debian 8.9 with same Hercules configuration shows the expected network configuration menu.Tested with: Debian 9.1 netinstp.s. while using Debian 8.9, the SSH server for the installer fails to sent the password prompt (ie. transport layer is working, but user authentication isn't) - any ideas?BRIvan
Re: Debian 9 on hercules
Hello list, I also confirm Bercik's finding from an previous e-mail (18 Jun 2017, https://lists.debian.org/debian-s390/2017/06/msg6.html) - Debian 9 IPL stops when network interfaces configuration is coming up. Last visible message is "Configure the network device". Debian 8.9 with same Hercules configuration shows the expected network configuration menu. Tested with: Debian 9.1 netinst p.s. while using Debian 8.9, the SSH server for the installer fails to sent the password prompt (ie. transport layer is working, but user authentication isn't) - any ideas? BR Ivan
Debian 9 on hercules
Hello folks, I'll be brief: tried to install new Debian 9 into hercules. IPL stops when we are about to set up network interfaces. - Tried with netinstall, xfce and clean IPL from reader. - Tried with hercules 3.07 and new hyperion I remember that other distros (RHEL, SLES, Ubuntu) stopped with comment they require modern hardware (modern CPU versions), but here I get nothing... it just stops. Log here: 4.761929! Brought up 8 CPUs 5.008546! clocksource: jiffies: mask: 0x max_cycles: 0x, ma 6.470271! VFS: Disk quotas dquot_6.6.0 6.573463! NET: Registered protocol family 1 25.021915! Freeing initrd memory: 10152K (0100 - 019ea00 25.216489! audit: initializing netlink subsys (disabled) 25.338155! Block layer SCSI generic (bsg) driver version 0.4 loaded (major 2 25.442243! registered taskstats version 1 25.827984! ima: No TPM chip found, activating TPM-bypass 27.853568! ctcm: CTCM driver initialized 28.254244! random: crng init done Starting system log daemon: syslogd, klogd. 1;24r 4l(B)0 m 1;24r H J 24;1H m 1;24r 4l(B)0 m 1;24r H J 24;1H m Configure the network device Any ideas? -- Regards, Bartłomiej "Bercik" Kacprzak
