On Thu, Jan 08, 2009 at 03:06:04PM -0600, Adam Thornton wrote:
So, is there something I'm doing wrong?
Not that I spot anything.
This is a perfectly normal (if
slow) z/VM development system (yes, it's actually emulated, but for all
that, IBM still
It seems that 2.6.26-2.6.27 have a regression that hangs my machine
during startup of the kernel, that has something to do with HPET. I
can stop it by using hpet=disable. It seems other people have
trouble with other chipsets, too. 2.6.28 seems to be fine.
Maybe it's the same bug? Though my
Dan Dart wrote:
It seems that 2.6.26-2.6.27 have a regression that hangs my machine
during startup of the kernel, that has something to do with HPET. I
can stop it by using hpet=disable. It seems other people have
trouble with other chipsets, too. 2.6.28 seems to be fine.
Maybe it's the same
On Jan 9, 2009, at 12:24 PM, Dan Dart wrote:
It seems that 2.6.26-2.6.27 have a regression that hangs my machine
during startup of the kernel, that has something to do with HPET. I
can stop it by using hpet=disable. It seems other people have
trouble with other chipsets, too. 2.6.28 seems to
booting/IPLing the s390 Lenny debian install from within IBM's z/VM)
Whoops. Got the wrong end of the stick. I was thinking boot problems
with the kernel... since we're using the same (ish) kernel and both
having problems with freezing, I thought it might have some
similarity. Never mind.
Plus.
Ivan Warren wrote:
The question is : would it be possible to have a more recent DI build
for s390 (more recent than October 27th 2008) - and especially with a
newer kernel ?
You could try a daily built image from [1], which uses 2.6.26-12 (current
unstable/testing kernel based on upstream
Lenny 2.6.26-1 fails identically to Lenny d-i. (after aptitude dist-
upgrade). Frans Pop reassigned bug 511334 to the kernel, which seems
right.
Etchnhalf kernel is fine.
Adam
--
To UNSUBSCRIBE, email to debian-s390-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact
Here's how I'd do it:
Set up a new disk (this does require that you can get a new chunk of DASD;
under z/VM, of course, this is usually really easy. LPAR, not so much.)
Mount it from the SuSE system.
Bind-mount /sys, /proc, /dev
debootstrap into the new disk
run mkinitrd/zipl on the new
8 matches
Mail list logo
