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
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
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
