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

Re: wheezy installer images fail on hercules

On 2012-05-27 Philipp Kern <pkern@hub.kern.lc> wrote:
> On Sun, May 27, 2012 at 10:40:15AM +0200, Andreas Metzler wrote:
>>> 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
> wrong.

I did not get that. So I understand I should change s390.cnf like

-# network                               s390     realbox
-0A00,0A01  CTCI -n /dev/net/tun -t 1500
+0A00.2  CTCI

This does not seem to make difference. (I am using 192.168.0.x
instead of 10.1.1.x)
0:0009 3215                                                                     
0:000C 3505 * eof                                                               
0:000E 1403 ./prt/print00e.txt crlf                                             
0:001F 3270                                                                     
0:0120 3390 ./dasd/3390.LINUX.0120 [3339 cyls] open                             
0:0581 3420 *                                                                   
0:0A00 3088 CTCI (tun0) open                            
0:0A01 3088 CTCI (tun0) open                            

"the newest s390 (or s390x) daily" - That is the one from May 8, 2012?

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

ametzler@argenau:/tmp/EXIM4$ uname -a && dpkg-architecture  -qDEB_HOST_ARCH
Linux argenau 3.2.0-2-amd64 #1 SMP Sun May 13 08:48:40 UTC 2012 x86_64 GNU/Linux

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

That is what I was suspecting.

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

No, it hangs at some later point. Non-deteministic.

cu andreas
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'

Reply to: