From owner-freebsd-alpha Mon Apr 15 5: 2:11 2002 Delivered-To: freebsd-alpha@freebsd.org Received: from pyxis.eclipse.net.uk (pyxis.eclipse.net.uk [212.104.129.226]) by hub.freebsd.org (Postfix) with ESMTP id F11B037B404 for ; Mon, 15 Apr 2002 05:01:57 -0700 (PDT) Received: from Bester (unknown [212.104.147.174]) by pyxis.eclipse.net.uk (Postfix) with SMTP id 6E0C97C17 for ; Mon, 15 Apr 2002 13:01:55 +0100 (BST) Message-ID: <006101c1e476$2a9b76f0$0500a8c0@Bester> From: To: References: <283a01c1e174$f29288b0$0500a8c0@Bester> <15541.51428.541308.526996@grasshopper.cs.duke.edu> Subject: Re: DP 1 on alphaserver 2100a install report Date: Mon, 15 Apr 2002 13:07:46 +0100 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_005E_01C1E47E.89361640" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4807.1700 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4910.0300 Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org 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 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
Thanks all for your help.

quick = run=20 down.

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

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.

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.
As a reward here's a picture of them = both=20 immediately after I moved them upstairs.
 
http://w= ww.whiterose.net/~mrpink/cam/archive/alphas.jpg
http:= //www.whiterose.net/~mrpink/cam/archive/ramboards.jpg
:)

Pink
----- Original Message ----- =
From: Andrew = Gallatin
Sent: Thursday, April 11, 2002 = 6:33=20 PM
Subject: Re: DP 1 on alphaserver = 2100a=20 install report


<moved from -current>

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

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

Cheers,

Drew

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

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