Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 15 Apr 2002 13:07:46 +0100
From:      <pink@eclipse.co.uk>
To:        <freebsd-alpha@FreeBSD.ORG>
Subject:   Re: DP 1 on alphaserver 2100a install report
Message-ID:  <006101c1e476$2a9b76f0$0500a8c0@Bester>
References:  <XFMail.20020411104727.jhb@FreeBSD.org><283a01c1e174$f29288b0$0500a8c0@Bester> <15541.51428.541308.526996@grasshopper.cs.duke.edu>

next in thread | previous in thread | raw e-mail | index | archive | help
This is a multi-part message in MIME format.

------=_NextPart_000_005E_01C1E47E.89361640
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Thanks all for your help.

quick run down.

got hold of serial lead.
switched over to serial console.
moved box to other side of room :) (has to be mentioned cos that's no =
small feat :) )
hooked up to terminal software
booted machine
started install.
install went fine (YAY)
Very happy Pink.
for a while....
IPV6 problem raises it's head, solution build new kernel.
build kernel gives error :(

I'll detail the error later when I've grabbed dmesg and other such =
output to give you guys something to work with. Still curious as to why =
the graphics adapter output causes failure on 5.0 when it has always =
been supported in previous releases I've tried.

Anyway thanks guys we have an SMP OS on the box. Now I just have to get =
it talking to the outside world on IPv4.

As a reward here's a picture of them both immediately after I moved them =
upstairs.

http://www.whiterose.net/~mrpink/cam/archive/alphas.jpg
http://www.whiterose.net/~mrpink/cam/archive/ramboards.jpg
:)

Pink
----- Original Message -----=20
From: Andrew Gallatin=20
To: pink@eclipse.co.uk=20
Cc: freebsd-alpha@FreeBSD.ORG=20
Sent: Thursday, April 11, 2002 6:33 PM
Subject: Re: DP 1 on alphaserver 2100a install report



<moved from -current>

Can you provide the output of "show conf" from the SRM console,
please?

FWIW, I suspect there may be some sort of problem with your graphics
card (like its an usupported TGA card showing a new failure mode).  I
suggest you try to insall using a serial console (96008N1, disconnect
keyboard and power-cycle box to redirct console to serial port).

Cheers,

Drew

pink@eclipse.co.uk writes:
 > I have downloaded 5.0DP1-alpha
 >=20
 > I'm attempting to install on an DEC alphaServer 2100a
 >=20
 > During initial boot from the CD the machine appears to hang with =
screen
 > corruption.
 >=20
 > All the initialisation seems to be fine until just after the SCSI =
interface
 > check.
 >=20
 > I get the waiting 15 seconds for SCSI devices to settle.
 > Then a list of the disk interfaces.
 > da0 to da5
 > (there are six discs)
 >=20
 > Then immediately after the last device check (da5) I get screen =
corruption.
 > The screen corruption is different each time and seems to have no =
familiar
 > pattern to it.
 >=20
 > So I removed all but one of the disks to see if it was the disk check =
itself
 > that was causing problems.
 > With only a single drive in place I get the same failure after da0.
 >=20
 > Looking at a recent Dmesg from my i386 box it would appear the next =
thing
 > after the disk interface check is mounting of the root partition.
 >=20
 > I would assume this root partition mount point is on the CD and it is
 > failing on this. Am I correct in this assumption?
 >=20
 >=20
 > If anyone wants more info on this then let me know what you require =
and I
 > will do my best to provide it.
 >=20
 > If anyone wants to give me any hints or tips as to what I can do next =
then
 > please do. I have a few things I'm going to try as soon as I get time =
but
 > would welcome any others as my BSD experience is in my opinion very =
limited.
 >=20
 > Pink.
 >=20
 >=20
 > To Unsubscribe: send mail to majordomo@FreeBSD.org
 > with "unsubscribe freebsd-current" in the body of the message
 >=20

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message

------=_NextPart_000_005E_01C1E47E.89361640
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 5.50.4913.1100" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2>Thanks all for your help.<BR><BR>quick =
run=20
down.<BR><BR>got hold of serial lead.<BR>switched over to serial=20
console.<BR>moved box to other side of room :) (has to be mentioned cos =
that's=20
no small feat :) )</FONT></DIV>
<DIV style=3D"FONT: 10pt arial">hooked up to terminal software</DIV>
<DIV style=3D"FONT: 10pt arial">booted machine</DIV>
<DIV style=3D"FONT: 10pt arial">started install.<BR>install went fine=20
(YAY)<BR>Very happy Pink.</DIV>
<DIV style=3D"FONT: 10pt arial">for&nbsp;a while....<BR>IPV6 problem =
raises it's=20
head, solution build new kernel.<BR>build kernel gives error =
:(<BR><BR>I'll=20
detail the error later when I've grabbed dmesg and other such output to =
give you=20
guys something to work with. Still curious as to why the graphics =
adapter output=20
causes failure on 5.0 when it has always been supported in previous =
releases=20
I've tried.<BR><BR>Anyway thanks guys we have an SMP OS on the box. Now =
I just=20
have to get it talking to the outside world on IPv4.<BR></DIV>
<DIV style=3D"FONT: 10pt arial">As a reward here's a picture of them =
both=20
immediately after I moved them upstairs.</DIV>
<DIV style=3D"FONT: 10pt arial">&nbsp;</DIV>
<DIV style=3D"FONT: 10pt arial"><A=20
href=3D"http://www.whiterose.net/~mrpink/cam/archive/alphas.jpg">http://w=
ww.whiterose.net/~mrpink/cam/archive/alphas.jpg</A></DIV>
<DIV style=3D"FONT: 10pt arial"><A=20
href=3D"http://www.whiterose.net/~mrpink/cam/archive/ramboards.jpg">http:=
//www.whiterose.net/~mrpink/cam/archive/ramboards.jpg</A></DIV>
<DIV style=3D"FONT: 10pt arial">:)</DIV>
<DIV style=3D"FONT: 10pt arial"><BR>Pink<BR>----- Original Message ----- =
</DIV>
<DIV=20
style=3D"BACKGROUND: #e4e4e4; FONT: 10pt arial; font-color: =
black"><B>From:</B> <A=20
title=3Dgallatin@cs.duke.edu href=3D"mailto:gallatin@cs.duke.edu">Andrew =

Gallatin</A> </DIV>
<DIV style=3D"FONT: 10pt arial"><B>To:</B> <A title=3Dpink@eclipse.co.uk =

href=3D"mailto:pink@eclipse.co.uk">pink@eclipse.co.uk</A> </DIV>
<DIV style=3D"FONT: 10pt arial"><B>Cc:</B> <A =
title=3Dfreebsd-alpha@FreeBSD.ORG=20
href=3D"mailto:freebsd-alpha@FreeBSD.ORG">freebsd-alpha@FreeBSD.ORG</A> =
</DIV>
<DIV style=3D"FONT: 10pt arial"><B>Sent:</B> Thursday, April 11, 2002 =
6:33=20
PM</DIV>
<DIV style=3D"FONT: 10pt arial"><B>Subject:</B> Re: DP 1 on alphaserver =
2100a=20
install report</DIV>
<DIV><FONT face=3DArial size=3D2></FONT><FONT face=3DArial=20
size=3D2></FONT><BR></DIV><BR>&lt;moved from -current&gt;<BR><BR>Can you =
provide=20
the output of "show conf" from the SRM console,<BR>please?<BR><BR>FWIW, =
I=20
suspect there may be some sort of problem with your graphics<BR>card =
(like its=20
an usupported TGA card showing a new failure mode).&nbsp; I<BR>suggest =
you try=20
to insall using a serial console (96008N1, disconnect<BR>keyboard and=20
power-cycle box to redirct console to serial=20
port).<BR><BR>Cheers,<BR><BR>Drew<BR><BR><A=20
href=3D"mailto:pink@eclipse.co.uk">pink@eclipse.co.uk</A> =
writes:<BR>&nbsp;&gt; I=20
have downloaded 5.0DP1-alpha<BR>&nbsp;&gt; <BR>&nbsp;&gt; I'm attempting =
to=20
install on an DEC alphaServer 2100a<BR>&nbsp;&gt; <BR>&nbsp;&gt; During =
initial=20
boot from the CD the machine appears to hang with screen<BR>&nbsp;&gt;=20
corruption.<BR>&nbsp;&gt; <BR>&nbsp;&gt; All the initialisation seems to =
be fine=20
until just after the SCSI interface<BR>&nbsp;&gt; check.<BR>&nbsp;&gt;=20
<BR>&nbsp;&gt; I get the waiting 15 seconds for SCSI devices to=20
settle.<BR>&nbsp;&gt; Then a list of the disk interfaces.<BR>&nbsp;&gt; =
da0 to=20
da5<BR>&nbsp;&gt; (there are six discs)<BR>&nbsp;&gt; <BR>&nbsp;&gt; =
Then=20
immediately after the last device check (da5) I get screen=20
corruption.<BR>&nbsp;&gt; The screen corruption is different each time =
and seems=20
to have no familiar<BR>&nbsp;&gt; pattern to it.<BR>&nbsp;&gt; =
<BR>&nbsp;&gt; So=20
I removed all but one of the disks to see if it was the disk check=20
itself<BR>&nbsp;&gt; that was causing problems.<BR>&nbsp;&gt; With only =
a single=20
drive in place I get the same failure after da0.<BR>&nbsp;&gt; =
<BR>&nbsp;&gt;=20
Looking at a recent Dmesg from my i386 box it would appear the next=20
thing<BR>&nbsp;&gt; after the disk interface check is mounting of the =
root=20
partition.<BR>&nbsp;&gt; <BR>&nbsp;&gt; I would assume this root =
partition mount=20
point is on the CD and it is<BR>&nbsp;&gt; failing on this. Am I correct =
in this=20
assumption?<BR>&nbsp;&gt; <BR>&nbsp;&gt; <BR>&nbsp;&gt; If anyone wants =
more=20
info on this then let me know what you require and I<BR>&nbsp;&gt; will =
do my=20
best to provide it.<BR>&nbsp;&gt; <BR>&nbsp;&gt; If anyone wants to give =
me any=20
hints or tips as to what I can do next then<BR>&nbsp;&gt; please do. I =
have a=20
few things I'm going to try as soon as I get time but<BR>&nbsp;&gt; =
would=20
welcome any others as my BSD experience is in my opinion very=20
limited.<BR>&nbsp;&gt; <BR>&nbsp;&gt; Pink.<BR>&nbsp;&gt; <BR>&nbsp;&gt; =

<BR>&nbsp;&gt; To Unsubscribe: send mail to <A=20
href=3D"mailto:majordomo@FreeBSD.org">majordomo@FreeBSD.org</A><BR>&nbsp;=
&gt; with=20
"unsubscribe freebsd-current" in the body of the message<BR>&nbsp;&gt;=20
<BR><BR>To Unsubscribe: send mail to <A=20
href=3D"mailto:majordomo@FreeBSD.org">majordomo@FreeBSD.org</A><BR>with=20
"unsubscribe freebsd-current" in the body of the =
message<BR></BODY></HTML>

------=_NextPart_000_005E_01C1E47E.89361640--


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-alpha" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?006101c1e476$2a9b76f0$0500a8c0>