[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: wheezy installer images fail on hercules

On Sun, May 27, 2012 at 10:40:15AM +0200, Andreas Metzler wrote:
> On 2012-05-22 Philipp Kern <pkern@debian.org> wrote:
> > On Sun, May 20, 2012 at 12:37:44AM +0200, Philipp Kern wrote:
> >> Indeed, thanks for the report.  It seems that the kernel driver
> >> switched from cu3088 to ctcm (the driver name is hardcoded in
> >> s390-netdevice).  Furthermore I only see
> >> «/sys/bus/ccw/devices/0.0.0a00», i.e. just one device instead of
> >> its write partner 0.0.0a01.  The same issue has been fixed in
> >> sysconfig-hardware with #566632, but there both devices turned up.
> > This works for me (with the adjusted initrd):
> > 0A00.2  CTCI
> > Does that also work for you, Andreas, with the squeeze kernel?
> -v please. ;-) I am s390 agnostic, I would need something like "at the
> hercules console type in the exact string when X happens"

That network line should work with the squeeze d-i.  It should also work with
the newest s390 (or s390x) daily.  And as said the line in the tutorial was

> BTW I have been unable to complete installations with stable images
> either. - The virtual machine just hangs at some point during the
> unpack phase. Symptoms like a hardware/heating or memory problem. I
> have never experienced anything like this in other circumstances but
> hercules generates a rather peculiar workload (100% CPU for a long
> time). Or is this related to AMD64 kernel with i386 userland? 

I guess you'd need to be more specific here. amd64 vs. i386 shouldn't be any
problem, it's a pure user-level program.  However it's very intense for
anything laptop-ish or desktop without proper cooling.

This means that you get to the SSH installer, configure everything and then it
hangs without you being able to invoke a new SSH connection?

Kind regards
Philipp Kern

Reply to: