From owner-freebsd-alpha Sun Oct 3 0: 0:35 1999 Delivered-To: freebsd-alpha@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 11E2214EC9 for ; Sun, 3 Oct 1999 00:00:32 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from beppo.feral.com (beppo [192.67.166.79]) by feral.com (8.8.7/8.8.7) with ESMTP id AAA21424; Sun, 3 Oct 1999 00:00:31 -0700 Date: Sun, 3 Oct 1999 00:00:30 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: Don Cc: alpha@FreeBSD.ORG Subject: Re: NCR Problem In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > (da0:ncr0:0:6:0): READ(06). CDB: 8 0 0 10 0 0 > (da0:ncr0:0:6:0): extraneous data discarded. > (da0:ncr0:0:6:0): COMMAND FAILED (9 0) @0xfffffe000057a000. > (da0:ncr0:0:6:0): xpt_done > (da0:ncr0:0:6:0): camisr(da0:ncr0:0:6:0): xpt_action > (da0:ncr0:0:6:0): READ(06). CDB: 8 0 0 10 0 0 > (da0:ncr0:0:6:0): xpt_setup_ccb > (da0:ncr0:0:6:0): xpt_action > (da0:ncr0:0:6:0): extraneous data discarded. > (da0:ncr0:0:6:0): COMMAND FAILED (9 0) @0xfffffe000057a000. Block 16 is attempting to be read for 0 bytes. Something is very bogus here. There were some changes today that may or may not clear this- see if that helps. If not, we have to figure why the hell a zero byte read is being sent down. Why there's any dataphase at all is a mystery too. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Sun Oct 3 2:23:36 1999 Delivered-To: freebsd-alpha@freebsd.org Received: from panzer.kdm.org (panzer.kdm.org [216.160.178.169]) by hub.freebsd.org (Postfix) with ESMTP id 153ED14BF6 for ; Sun, 3 Oct 1999 02:23:33 -0700 (PDT) (envelope-from ken@panzer.kdm.org) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id DAA64199; Sun, 3 Oct 1999 03:22:54 -0600 (MDT) (envelope-from ken) Message-Id: <199910030922.DAA64199@panzer.kdm.org> Subject: Re: NCR Problem In-Reply-To: from Matthew Jacob at "Oct 3, 1999 00:00:30 am" To: mjacob@feral.com Date: Sun, 3 Oct 1999 03:22:54 -0600 (MDT) Cc: don@calis.blacksun.org (Don), alpha@FreeBSD.ORG From: "Kenneth D. Merry" X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Matthew Jacob wrote... > > (da0:ncr0:0:6:0): READ(06). CDB: 8 0 0 10 0 0 > > (da0:ncr0:0:6:0): extraneous data discarded. > > (da0:ncr0:0:6:0): COMMAND FAILED (9 0) @0xfffffe000057a000. > > (da0:ncr0:0:6:0): xpt_done > > (da0:ncr0:0:6:0): camisr(da0:ncr0:0:6:0): xpt_action > > (da0:ncr0:0:6:0): READ(06). CDB: 8 0 0 10 0 0 > > (da0:ncr0:0:6:0): xpt_setup_ccb > > (da0:ncr0:0:6:0): xpt_action > > (da0:ncr0:0:6:0): extraneous data discarded. > > (da0:ncr0:0:6:0): COMMAND FAILED (9 0) @0xfffffe000057a000. > > Block 16 is attempting to be read for 0 bytes. Something is very > bogus here. There were some changes today that may or may not clear this- > see if that helps. If not, we have to figure why the hell a zero byte read > is being sent down. Why there's any dataphase at all is a mystery too. If he is using -current, then this is almost certainly because of PHK's changes. It should have been fixed by his checkin earlier Saturday. I reproduced this behavior on my test system that has an Adaptec controller. The symptoms were the same -- a READ command with a block number specified but with no length. I'm not sure why there is a data phase at all, but my guess is that the drive tries to return at least one block. In any case, cvsup again, try a new kernel and see if the problem goes away. Ken -- Kenneth Merry ken@kdm.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Sun Oct 3 8: 9:51 1999 Delivered-To: freebsd-alpha@freebsd.org Received: from calis.blacksun.org (Calis.blacksun.org [168.100.186.40]) by hub.freebsd.org (Postfix) with ESMTP id 4FE7414D21 for ; Sun, 3 Oct 1999 08:09:47 -0700 (PDT) (envelope-from don@calis.blacksun.org) Received: from localhost (don@localhost) by calis.blacksun.org (8.9.3/8.9.2) with ESMTP id LAA08153; Sun, 3 Oct 1999 11:09:54 -0400 (EDT) (envelope-from don@calis.blacksun.org) Date: Sun, 3 Oct 1999 11:09:54 -0400 (EDT) From: Don To: "Kenneth D. Merry" Cc: mjacob@feral.com, alpha@FreeBSD.ORG Subject: Re: NCR Problem In-Reply-To: <199910030922.DAA64199@panzer.kdm.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > If he is using -current, then this is almost certainly because of PHK's > changes. It should have been fixed by his checkin earlier Saturday. > > I reproduced this behavior on my test system that has an Adaptec > controller. The symptoms were the same -- a READ command with a block > number specified but with no length. > > I'm not sure why there is a data phase at all, but my guess is that the > drive tries to return at least one block. > > In any case, cvsup again, try a new kernel and see if the problem goes > away. Current from this morning fixed this problem. -Don To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Sun Oct 3 21:33:18 1999 Delivered-To: freebsd-alpha@freebsd.org Received: from mail.cybcon.com (mail.cybcon.com [216.190.188.5]) by hub.freebsd.org (Postfix) with ESMTP id 7771214D46 for ; Sun, 3 Oct 1999 21:33:06 -0700 (PDT) (envelope-from wwoods@cybcon.com) Received: from freebsd.cybcon.com (pm3a-6.cybcon.com [205.147.75.135]) by mail.cybcon.com (8.9.0/8.9.0) with SMTP id VAA09978 for ; Sun, 3 Oct 1999 21:33:01 -0700 (PDT) From: william woods Reply-To: wwoods@cybcon.com To: freebsd-alpha@freebsd.org Subject: Alphngs when booting ... help Date: Sun, 3 Oct 1999 21:28:12 -0700 X-Mailer: KMail [version 1.0.28] Content-Type: text/plain MIME-Version: 1.0 Message-Id: <99100321305400.00333@freebsd.cybcon.com> Content-Transfer-Encoding: 8bit Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I have an Alphastation 200 4/233 that I just did a make world on going from 3.2-Release to 3.3-Stable. After Make world I compiled a new kernel and installed it. When I went to reboot, it gets to "jumping to bootstrap code" then hangs there Anyone have any ideas for me? William Woods FreeBSD 3.3-Stable -----BEGIN GEEK CODE BLOCK----- Version: 3.1 GIT d++ s+:+ a C+++ UB+++ P+ L++ E- W++ N+ o+ K- w O- M-- V PS-- PE++ Y+ PGP t+ 5+ X R- tv- b++ DI+ D G e++ h---- r+++ y++++ ------END GEEK CODE BLOCK------ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Sun Oct 3 23: 4:30 1999 Delivered-To: freebsd-alpha@freebsd.org Received: from arthur.vortex4.net (arthur.vortex4.net [140.174.185.252]) by hub.freebsd.org (Postfix) with ESMTP id 596F915121 for ; Sun, 3 Oct 1999 23:04:25 -0700 (PDT) (envelope-from friend@arthur.vortex4.net) Received: (from friend@localhost) by arthur.vortex4.net (8.8.8/8.8.8) id XAA09163 for freebsd-alpha@freebsd.org; Sun, 3 Oct 1999 23:05:25 -0700 (PDT) (envelope-from friend) Date: Sun, 3 Oct 1999 23:05:25 -0700 From: Dave To: freebsd-alpha@freebsd.org Subject: Re: Status of XFree86 on Alpha? Message-ID: <19991003230525.J1233@vortex4.net> References: Mime-Version: 1.0 Content-Type: multipart/signed; boundary=TA4f0niHM6tHt3xR; micalg=pgp-md5; protocol="application/pgp-signature" X-Mailer: Mutt 0.95.6i In-Reply-To: ; from Tom Bartol on Mon, Sep 27, 1999 at 10:41:03AM -0700 X-Operating-System: FreeBSD arthur.vortex4.net 2.2.8-STABLE FreeBSD 2.2.8-STABLE X-System-Stats: 8:31PM up 9 days, 6:47, 2 users, load averages: 0.10, 0.04, 0.01 Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org --TA4f0niHM6tHt3xR Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Getting the same sorts of problems; System is a PC164SX w/a Diamond Stealth 3D 2000...under twm got wierd stripes of titlebar color in some resolution modes..fvwm2 looked fine but I couldn't move windows... afterstep is prety mellow but the toolbar is a set of solid black boxes lined up on the side of the screen, but clicking on one of them launches xterms :> If I click and produce the application laucher menu over an xterm the menu becomes the new permanent background of the xterm...also switching out to a console with ctrl-alt-f2 made the system wig and reboot. So what's with all of these netcape ports saying they don't work on alpha? I managed to get netscape working under debian + XFree86; Is the x86 emulation not as far along in FreeBSD? On Mon, Sep 27, 1999 at 10:41:03AM -0700, Tom Bartol wrote: >=20 > Hi, >=20 > I've been trying to build and run Xfree86 on FreeBSD-current for the Alpha > and have run into several problems I'd like to report and compare notes > on. Please CC me and wathey@salk.edu on your responses directly as we > aren't (yet) subscribed to freebsd-alpha. >=20 > We are running FreeBSD-current for Alpha as of 19990923 and have cvsupped > our ports tree on that date as well. The machine is a 533MHz PC164LX with > 64MB RAM and a Matrox Millenium II with 4MB. >=20 > Problems/Observations: >=20 > 1) We could "make" XFree86 but a "make install" failed due to a missing > /usr/include/sys/pci_ioctl.h. We noticed that patch-4 for for > /usr/port/x11/XFree86 includes a patch to "#include " = =20 > however this file does not exist in /usr/include/sys on our system. =20 > "make world" in /usr/src does not install this file. We found the file in > /usr/src/sys/pci and copied it by hand to /usr/include/sys. After this a > "make install" for XFree86 succeeded. FreeBSD for Intel does not have > this file in /usr/include/sys and XFree86 does not require it on Intel. >=20 > 2) SuperProbe segfaults. gdb doesn't like the core file so we have no > clue about the problem here. >=20 > 3) We configured X to run the X_SVGA server for our Matrox Millenium II. > The server starts up fine but some windows are filled with black and > menus pop up empty until you run the mouse cursor over the locations where > the text should be. >=20 > Can anyone tell us if this is normal for the current status of XFree86 for > FreeBSD-current on the Alpha. I scanned the freebsd-alpha mail archive > but could glean any insights into this matter. Is there some miss > configuration on our system causing pci_ioctl.h to be skipped during a > "make world"? Should we be using a different brand of video card? >=20 > Thanks for your help, >=20 > Tom >=20 >=20 >=20 >=20 > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-alpha" in the body of the message --=20 Dave Cotton System Administrator Vortex4 Internet Services friend@vortex4.net --TA4f0niHM6tHt3xR Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: 2.6.2 iQCVAwUBN/hDopezAGueKuk9AQEemQP+ImpXpK6IhcuAdMXbx8eBgXyRgVBx45/e BOT9qvfwyKq2vf1Pme6qwD5LUCLBtIaMv75po7RpUzsPWGIUPyyI1UvtkkJoTS8v q6GxHZ7ZMS/IPrq3NkbnnHoAP9fcuBWfKtva4/mVzUowigIhtjvTvm7HNodwwakL z75BpiutOMQ= =zgl+ -----END PGP SIGNATURE----- --TA4f0niHM6tHt3xR-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Mon Oct 4 7:40:23 1999 Delivered-To: freebsd-alpha@freebsd.org Received: from mailext02.compaq.com (mailext02.compaq.com [207.18.199.33]) by hub.freebsd.org (Postfix) with ESMTP id 41FF715813 for ; Mon, 4 Oct 1999 07:40:12 -0700 (PDT) (envelope-from Maurice.Marks@compaq.com) Received: by mailext02.compaq.com (Postfix, from userid 60001) id A38519A96F; Mon, 4 Oct 1999 09:40:10 -0500 (CDT) Received: from mailext02.compaq.com (localhost [127.0.0.1]) by mailext02.compaq.com (Postfix) with ESMTP id 9E8B990D84 for ; Mon, 4 Oct 1999 09:40:10 -0500 (CDT) Received: from mailint12.im.hou.compaq.com([not looked up]) (peer mailint12.compaq.com[207.18.199.190]) by mailext02.compaq.com with ESMTP id rcv002737; Mon, 4 Oct 1999 09:40:06 -0500 (CDT) Received: by mailint12.im.hou.compaq.com (Postfix, from userid 60001) id 2BD004FB13; Mon, 4 Oct 1999 09:39:50 -0500 (CDT) Received: from mailint12.im.hou.compaq.com (localhost [127.0.0.1]) by mailint12.im.hou.compaq.com (Postfix) with ESMTP id 247D04C904 for ; Mon, 4 Oct 1999 09:39:50 -0500 (CDT) Received: from exctay-gh02.tay.cpqcorp.net([not looked up]) (peer exctay-gh02.tay.cpqcorp.net[16.103.129.52]) by mailint12.im.hou.compaq.com with ESMTP id rcv012688; Mon, 4 Oct 1999 09:39:48 -0500 (CDT) Received: by exctay-gh02.tay.cpqcorp.net with Internet Mail Service (5.5.2559.0) id <412BS8JT>; Mon, 4 Oct 1999 10:39:48 -0400 Message-ID: <9996FB0C6AB3D111B9FB0000F81E38A2067241FC@lkgexc1.tay.dec.com> From: "Marks, Maurice" To: "'freebsd-alpha@freebsd.org'" Subject: Problem booting on DS10 Date: Mon, 4 Oct 1999 10:39:47 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2559.0) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I've been trying to boot a recent (9/15) 4.0 snapshot on a DS10 system. It hangs probing the PCI bus(the last messages I see are: preloaded elf kernel ... preloaded mfsroot ... pcib0: <21271 PCI host bus adapter> on tsunami0 I've tried several SCSI adapters, several PCI graphics cards, and two versions of the Alpha firmware (5.4 and 5.5-1) without success. Has anyone successfully booted FreeBSD on a DS10? Please let me know what you did! /maurice marks(compaq) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Mon Oct 4 10:22:56 1999 Delivered-To: freebsd-alpha@freebsd.org Received: from arthur.vortex4.net (arthur.vortex4.net [140.174.185.252]) by hub.freebsd.org (Postfix) with ESMTP id 6413C14E16 for ; Mon, 4 Oct 1999 10:22:52 -0700 (PDT) (envelope-from friend@arthur.vortex4.net) Received: (from friend@localhost) by arthur.vortex4.net (8.8.8/8.8.8) id KAA10352; Mon, 4 Oct 1999 10:23:10 -0700 (PDT) (envelope-from friend) Date: Mon, 4 Oct 1999 10:23:10 -0700 From: Dave To: Doug Rabson Cc: freebsd-alpha@freebsd.org Subject: Re: Status of XFree86 on Alpha? Message-ID: <19991004102309.L1233@vortex4.net> References: <19991003230525.J1233@vortex4.net> Mime-Version: 1.0 Content-Type: multipart/signed; boundary="dxRQSzdsN/lOP445"; micalg=pgp-md5; protocol="application/pgp-signature" X-Mailer: Mutt 0.95.6i In-Reply-To: ; from Doug Rabson on Mon, Oct 04, 1999 at 10:23:12AM +0100 X-Operating-System: FreeBSD arthur.vortex4.net 2.2.8-STABLE FreeBSD 2.2.8-STABLE X-System-Stats: 8:31PM up 9 days, 6:47, 2 users, load averages: 0.10, 0.04, 0.01 Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org --dxRQSzdsN/lOP445 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable On Mon, Oct 04, 1999 at 10:23:12AM +0100, Doug Rabson wrote: > On Sun, 3 Oct 1999, Dave wrote: >=20 > >=20 > > Getting the same sorts of problems; System is a PC164SX w/a Diamond > > Stealth 3D 2000...under twm got wierd stripes of titlebar color in > > some resolution modes..fvwm2 looked fine but I couldn't move windows... > > afterstep is prety mellow but the toolbar is a set of solid black > > boxes lined up on the side of the screen, but clicking on one of > > them launches xterms :> If I click and produce the application > > laucher menu over an xterm the menu becomes the new permanent > > background of the xterm...also switching out to a console with > > ctrl-alt-f2 made the system wig and reboot. >=20 > Thats very odd. I'm suspicious about the window manager (does it work on > Linux/alpha?). I use kde on my alpha and it works very nicely. >=20 I actually never got further than fvwm2 on debian before I managed to get the right kind of scsi controller to let me boot FreeBSD :> I'll give kde a shot...my suspicion is that it's a problem with my X configuration, 'cause some of the video glitches look similar to others I've had in the past...I just thought I oughta throw some data in the pool since other people are having the same trouble :> > >=20 > > So what's with all of these netcape ports saying they don't work > > on alpha? I managed to get netscape working under debian + XFree86; > > Is the x86 emulation not as far along in FreeBSD? >=20 > We don't have any x86 emulation in FreeBSD/alpha. It would be nice but the > only x86 emulator available is GPL and I don't have the time to write one. >=20 Ergh...so it netscape out of reach then? I kind of need a 128-bit ssl browser...am I going to have to live with lynx-ssl or is a better solution available? > -- > Doug Rabson Mail: dfr@nlsystems.com > Nonlinear Systems Ltd. Phone: +44 181 442 9037 >=20 --=20 Dave Cotton System Administrator Vortex4 Internet Services friend@vortex4.net --dxRQSzdsN/lOP445 Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: 2.6.2 iQCVAwUBN/jifJezAGueKuk9AQHkwAP+NzzX/GdMI0FykVhA4ngfssNgrcg1S1ZO vIAC/4TVZUqN7SA0qUX9LlZR71onFeuQIH47agdgAfvawc22XD18ct+tVn1q+d8N oQScCqYaRz5NJeaQzv6/OYWakiqkIh54pitDyjAQCwoVjs4O2lH7874G0RItk9d5 CrpXorrzIIY= =dw9u -----END PGP SIGNATURE----- --dxRQSzdsN/lOP445-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Mon Oct 4 10:40:20 1999 Delivered-To: freebsd-alpha@freebsd.org Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by hub.freebsd.org (Postfix) with ESMTP id 5FB781514A for ; Mon, 4 Oct 1999 10:40:13 -0700 (PDT) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.1/8.9.1) with ESMTP id NAA11044; Mon, 4 Oct 1999 13:40:12 -0400 (EDT) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.9.3/8.9.1) id NAA10399; Mon, 4 Oct 1999 13:39:42 -0400 (EDT) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Mon, 4 Oct 1999 13:39:42 -0400 (EDT) To: "Marks, Maurice" Cc: "'freebsd-alpha@freebsd.org'" Subject: Re: Problem booting on DS10 In-Reply-To: <9996FB0C6AB3D111B9FB0000F81E38A2067241FC@lkgexc1.tay.dec.com> References: <9996FB0C6AB3D111B9FB0000F81E38A2067241FC@lkgexc1.tay.dec.com> X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14328.58408.543210.232004@grasshopper.cs.duke.edu> Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Maurice, I'm the author of the platform support for the family of machine which includes the DS10 & XP1000. While XP1000 support is working & fairly well tested, support for DS10 is currently known to be broken. I don't have access to a DS10 right now, but I am awaiting the arrival of a number of DS10s from our reseller. When they arrive, I *hope* to be able to fix the problem in short order. I'm guessing the machines won't arrive until the end of this week at best, most likely sometime next week. If you need your DS10 to work sooner than that, let's start talking off-line... Also, if you have a chance, I would appreciate the output of 'show conf' from the SRM console on a DS10. Thanks, Drew ------------------------------------------------------------------------------ Andrew Gallatin, Sr Systems Programmer http://www.cs.duke.edu/~gallatin Duke University Email: gallatin@cs.duke.edu Department of Computer Science Phone: (919) 660-6590 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Mon Oct 4 21: 1:37 1999 Delivered-To: freebsd-alpha@freebsd.org Received: from halla2.dacom.co.kr (halla2.dacom.co.kr [164.124.1.108]) by hub.freebsd.org (Postfix) with SMTP id A8E4714BEA for ; Mon, 4 Oct 1999 21:01:03 -0700 (PDT) (envelope-from sio2@halla2.dacom.co.kr) Received: (from sio2@localhost) by halla2.dacom.co.kr (8.6.12H1/8.6.9) id MAA02720 for freebsd-alpha@freebsd.org; Tue, 5 Oct 1999 12:55:17 GMT Message-Id: <199910051255.MAA02720@halla2.dacom.co.kr> Subject: How can I use my old alpha? To: freebsd-alpha@freebsd.org Date: Tue, 5 Oct 1999 12:55:15 +0000 () From: "Hwang GyuSeog" X-Mailer: ELM [version 2.4 PL25 ME8b] Content-Type: text Content-Length: 229 Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi All! I have one alpha systems. It's label is Model: PE42A-A9 CPU KN17 DEC 3000 600 Series BA47A SN: AB41602PWP I've bought it on 1994. Very old. I wan't porting FreeBSD on it. How can I do this job??? Thanks advance! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Tue Oct 5 2:16:11 1999 Delivered-To: freebsd-alpha@freebsd.org Received: from herring.nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (Postfix) with ESMTP id 91DE015023 for ; Tue, 5 Oct 1999 02:15:30 -0700 (PDT) (envelope-from dfr@nlsystems.com) Received: from salmon.nlsystems.com (salmon.nlsystems.com [10.0.0.3]) by herring.nlsystems.com (8.9.3/8.8.8) with ESMTP id KAA05163; Tue, 5 Oct 1999 10:16:20 +0100 (BST) (envelope-from dfr@nlsystems.com) Date: Tue, 5 Oct 1999 10:16:20 +0100 (BST) From: Doug Rabson To: Hwang GyuSeog Cc: freebsd-alpha@freebsd.org Subject: Re: How can I use my old alpha? In-Reply-To: <199910051255.MAA02720@halla2.dacom.co.kr> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Tue, 5 Oct 1999, Hwang GyuSeog wrote: > Hi All! > > I have one alpha systems. It's label is > Model: PE42A-A9 CPU KN17 > DEC 3000 600 Series BA47A > SN: AB41602PWP > > I've bought it on 1994. Very old. > > I wan't porting FreeBSD on it. > How can I do this job??? > > Thanks advance! Currently our support for this system is limited to diskless since the driver for its scsi controller hasn't been ported to the CAM framework. -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Tue Oct 5 6:18:24 1999 Delivered-To: freebsd-alpha@freebsd.org Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by hub.freebsd.org (Postfix) with ESMTP id 6C77B15039 for ; Tue, 5 Oct 1999 06:18:15 -0700 (PDT) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.1/8.9.1) with ESMTP id JAA29938; Tue, 5 Oct 1999 09:18:12 -0400 (EDT) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.9.3/8.9.1) id JAA11908; Tue, 5 Oct 1999 09:17:42 -0400 (EDT) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Tue, 5 Oct 1999 09:17:41 -0400 (EDT) To: "Hwang GyuSeog" Cc: freebsd-alpha@FreeBSD.ORG Subject: Re: How can I use my old alpha? In-Reply-To: <199910051255.MAA02720@halla2.dacom.co.kr> References: <199910051255.MAA02720@halla2.dacom.co.kr> X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14329.63795.295767.810384@grasshopper.cs.duke.edu> Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hwang GyuSeog writes: > Hi All! > > I have one alpha systems. It's label is > Model: PE42A-A9 CPU KN17 > DEC 3000 600 Series BA47A > SN: AB41602PWP > > I've bought it on 1994. Very old. > > I wan't porting FreeBSD on it. > How can I do this job??? > > Thanks advance! The DEC3000 series of machine will only work in a diskless configuration because their disk controller is currently unsupported. If you want a machine that "just works", my advice is to run NetBSD on the 3000 family of systems. However, if you're interested in contributing to the FreeBSD/alpha project you could port the esp driver to CAM or, (better still) write a turbochannel front-end for the already CAM amd SCSI driver (/sys/pci/amd.c) Cheers, Drew ------------------------------------------------------------------------------ Andrew Gallatin, Sr Systems Programmer http://www.cs.duke.edu/~gallatin Duke University Email: gallatin@cs.duke.edu Department of Computer Science Phone: (919) 660-6590 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Wed Oct 6 4:43:50 1999 Delivered-To: freebsd-alpha@freebsd.org Received: from post.bgnett.no (post.bgnett.no [194.54.96.133]) by hub.freebsd.org (Postfix) with ESMTP id 507C514EB9; Wed, 6 Oct 1999 04:43:35 -0700 (PDT) (envelope-from erik@habatech.no) Received: from bsdbox.habatech.no ([62.92.133.3]) by post.bgnett.no (8.8.8/8.8.8) with ESMTP id NAA21153; Wed, 6 Oct 1999 13:43:32 +0200 (CEST) (envelope-from erik@habatech.no) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Date: Wed, 06 Oct 1999 13:43:18 +0200 (CEST) From: "Erik H. Bakke" To: freebsd-current@freebsd.org, freebsd-alpha@freebsd.org Subject: Still ATA problems Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I am still having problems with the ATA driver. I am seeing the same error messages as has been reported on the lists during the last few weeks, both on i386 and alpha platforms. On the i386, the problem is just an irritating itch, but it seems to be far more serious on the alpha, where the system reboots instantly when the problems occur. On reboot, the system stops at the probing of disks, reporting a timeout. Then, the system reboots again, probing and rebooting in an endless loop. I have the latest sources, as cvsupped today, October 6th. I can provide more information on the system configuration if needed, but I have no access to it right now. ===========================+================+=============================== Erik H. Bakke | | To be or not to be... Senior Consultant/Developer|erik@habatech.no| Is simply a question of Habatech AS | | binary logic ===========================+================+============================== To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Wed Oct 6 5: 0:15 1999 Delivered-To: freebsd-alpha@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id 77F7D15313; Wed, 6 Oct 1999 05:00:07 -0700 (PDT) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id NAA22825; Wed, 6 Oct 1999 13:59:58 +0200 (CEST) (envelope-from sos) From: Soren Schmidt Message-Id: <199910061159.NAA22825@freebsd.dk> Subject: Re: Still ATA problems In-Reply-To: from "Erik H. Bakke" at "Oct 6, 1999 01:43:18 pm" To: erik@habatech.no (Erik H. Bakke) Date: Wed, 6 Oct 1999 13:59:58 +0200 (CEST) Cc: freebsd-current@FreeBSD.ORG, freebsd-alpha@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org It seems Erik H. Bakke wrote: > I am still having problems with the ATA driver. > I am seeing the same error messages as has been reported on the lists during > the last few weeks, both on i386 and alpha platforms. > On the i386, the problem is just an irritating itch, but it seems to be > far more serious on the alpha, where the system reboots instantly when the > problems occur. > On reboot, the system stops at the probing of disks, reporting a timeout. > Then, the system reboots again, probing and rebooting in an endless loop. > > I have the latest sources, as cvsupped today, October 6th. > > I can provide more information on the system configuration if needed, but I > have no access to it right now. I have a new version almost ready that should fix this problem, including the panic on the alpha. It just a bit more testing then I'll commit it... -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Wed Oct 6 6:22:22 1999 Delivered-To: freebsd-alpha@freebsd.org Received: from post.bgnett.no (post.bgnett.no [194.54.96.133]) by hub.freebsd.org (Postfix) with ESMTP id CB3F914D07; Wed, 6 Oct 1999 06:22:01 -0700 (PDT) (envelope-from erik@habatech.no) Received: from bsdbox.habatech.no ([62.92.133.3]) by post.bgnett.no (8.8.8/8.8.8) with ESMTP id PAA21827; Wed, 6 Oct 1999 15:21:52 +0200 (CEST) (envelope-from erik@habatech.no) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <199910061159.NAA22825@freebsd.dk> Date: Wed, 06 Oct 1999 15:21:38 +0200 (CEST) From: "Erik H. Bakke" To: Soren Schmidt Subject: Re: Still ATA problems Cc: freebsd-alpha@FreeBSD.ORG, freebsd-current@FreeBSD.ORG Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On 06-Oct-99 Soren Schmidt wrote: > > I have a new version almost ready that should fix this problem, including > the panic on the alpha. It just a bit more testing then I'll commit it... > If you want, I can give it a test on a 164SX-based alpha... ===========================+================+=============================== Erik H. Bakke | | To be or not to be... Senior Consultant/Developer|erik@habatech.no| Is simply a question of Habatech AS | | binary logic ===========================+================+============================== To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Wed Oct 6 9: 1:56 1999 Delivered-To: freebsd-alpha@freebsd.org Received: from po9.andrew.cmu.edu (PO9.ANDREW.CMU.EDU [128.2.10.109]) by hub.freebsd.org (Postfix) with ESMTP id A8D121512F for ; Wed, 6 Oct 1999 09:01:52 -0700 (PDT) (envelope-from tcrimi+@andrew.cmu.edu) Received: (from postman@localhost) by po9.andrew.cmu.edu (8.9.3/8.9.3) id MAA26696 for freebsd-alpha@freebsd.org; Wed, 6 Oct 1999 12:01:50 -0400 (EDT) Received: via switchmail; Wed, 6 Oct 1999 12:01:49 -0400 (EDT) Received: from unix14.andrew.cmu.edu via qmail ID ; Wed, 6 Oct 1999 12:01:02 -0400 (EDT) Received: from unix14.andrew.cmu.edu via qmail ID ; Wed, 6 Oct 1999 12:01:02 -0400 (EDT) Received: from mms.4.60.Jun.27.1996.03.02.53.sun4.51.EzMail.2.0.CUILIB.3.45.SNAP.NOT.LINKED.unix14.andrew.cmu.edu.sun4m.54 via MS.5.6.unix14.andrew.cmu.edu.sun4_51; Wed, 6 Oct 1999 12:01:02 -0400 (EDT) Message-ID: <4ryr8y_00UwG0PvkY0@andrew.cmu.edu> Date: Wed, 6 Oct 1999 12:01:02 -0400 (EDT) From: Thomas Valentino Crimi To: freebsd-alpha@freebsd.org Subject: New Signals - breaks Alpha makeworld Cc: Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org There is a slight #include problem with the Alpha header files, it all boils down to u_int* being used used /sys/alpha/include/alpha_cpu.h In building yacc.. cc -O -pipe -c /usr/src/usr.bin/yacc/main.c In file included from /usr/include/machine/frame.h:34, from /usr/include/machine/ucontext.h:34, from /usr/include/sys/ucontext.h:34, from /usr/include/sys/signal.h:238, from /usr/include/signal.h:44, from /usr/src/usr.bin/yacc/main.c:52: /usr/include/machine/alpha_cpu.h:299: syntax error before `alpha_ldbu' Now, shoudl this be fixed with an #include as being a necessary pre-requisite to include signals.h, with that we're placing a requirement on programmers that they'll never catch when testing on i386, meaning running into this more than once (already more than a few programs will break compiling, yacc is merely the first in the make world chain. I've currently included sys/types.h in alpha_cpu.h, which is hackish but at least gets the world built. I'm now doing the buildworld to see what breaks, but I can't see it's clear what the optimial solution is. I would say to put in the extra #include in alpha_cpu or possibly higher up in the chain, but requiring it in all applications probably means we're going to be doing a few bouts of patching. The kernel built without a hitch. Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Wed Oct 6 12:59:23 1999 Delivered-To: freebsd-alpha@freebsd.org Received: from herring.nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (Postfix) with ESMTP id 670B214CE9 for ; Wed, 6 Oct 1999 12:59:14 -0700 (PDT) (envelope-from dfr@nlsystems.com) Received: from salmon.nlsystems.com (salmon.nlsystems.com [10.0.0.3]) by herring.nlsystems.com (8.9.3/8.8.8) with ESMTP id UAA45259; Wed, 6 Oct 1999 20:59:44 +0100 (BST) (envelope-from dfr@nlsystems.com) Date: Wed, 6 Oct 1999 20:59:44 +0100 (BST) From: Doug Rabson To: Thomas Valentino Crimi Cc: freebsd-alpha@freebsd.org Subject: Re: New Signals - breaks Alpha makeworld In-Reply-To: <4ryr8y_00UwG0PvkY0@andrew.cmu.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Wed, 6 Oct 1999, Thomas Valentino Crimi wrote: > > There is a slight #include problem with the Alpha header files, it all > boils down to u_int* being used used /sys/alpha/include/alpha_cpu.h In > building yacc.. > > cc -O -pipe -c /usr/src/usr.bin/yacc/main.c > In file included from /usr/include/machine/frame.h:34, > from /usr/include/machine/ucontext.h:34, > from /usr/include/sys/ucontext.h:34, > from /usr/include/sys/signal.h:238, > from /usr/include/signal.h:44, > from /usr/src/usr.bin/yacc/main.c:52: > /usr/include/machine/alpha_cpu.h:299: syntax error before `alpha_ldbu' > > > Now, shoudl this be fixed with an #include as being a > necessary pre-requisite to include signals.h, with that we're placing a > requirement on programmers that they'll never catch when testing on > i386, meaning running into this more than once (already more than a few > programs will break compiling, yacc is merely the first in the make > world chain. > > I've currently included sys/types.h in alpha_cpu.h, which is hackish > but at least gets the world built. I'm now doing the buildworld to see > what breaks, but I can't see it's clear what the optimial solution is. > I would say to put in the extra #include in alpha_cpu or possibly higher > up in the chain, but requiring it in all applications probably means > we're going to be doing a few bouts of patching. > The kernel built without a hitch. I think the latest version of sys/alpha/include/ucontext.h no longer needs to include frame.h at all. -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Wed Oct 6 13:58:36 1999 Delivered-To: freebsd-alpha@freebsd.org Received: from nimbus.skycache.com (nimbus.skycache.com [207.239.230.67]) by hub.freebsd.org (Postfix) with ESMTP id 900B31576C for ; Wed, 6 Oct 1999 13:58:03 -0700 (PDT) (envelope-from rharris@nimbus.skycache.com) Received: from localhost (rharris@localhost) by nimbus.skycache.com (8.9.3/8.9.3) with SMTP id QAA11697 for ; Wed, 6 Oct 1999 16:57:28 -0400 (EDT) Date: Wed, 6 Oct 1999 16:57:26 -0400 (EDT) From: Rob Harris To: freebsd-alpha@freebsd.org Subject: /usr/ports/lang/egcs broken Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I'm sure it's something stupid like a missing header file or a broken sym-link, but when I try to compile the egcs port on my alpha under 3.3-STABLE, It barfs on just about every line with a "vsprintf" line in it. I commented out most of them, since they looked like just error reporting routines, but now I can't read the errors to figure out what I did wrong. *sigh* Anyone else have any ideas? --Rob ____________________________________________________________________________ Rob Harris 9885 North Washington Blvd. ph: 301.598.0500 SkyCache, Inc. Laurel, MD 20723 x2236 rharris@skycache.com "My opinions are my own." fax: 301.598.0837 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ "I've said it before, and I'll say again. Democracy just doesn't work." -Kent Brockman, Springfield USA To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Wed Oct 6 21:50:54 1999 Delivered-To: freebsd-alpha@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 6F23514DEB for ; Wed, 6 Oct 1999 21:50:34 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from beppo.feral.com (beppo [192.67.166.79]) by feral.com (8.8.7/8.8.7) with ESMTP id VAA03203 for ; Wed, 6 Oct 1999 21:49:26 -0700 Date: Wed, 6 Oct 1999 21:49:26 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: freebsd-alpha@freebsd.org Subject: anyone seen this? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org This is -current, maybe a couple of days old...Sure is hard to focus on *your* bugs when you trip over this.... Disklabel of a disk got me: trap entry = 0x3 (instruction fault) a0 = 0x2 a1 = 0xfffffe000099c400 a2 = 0xffffffffffffffff pc = 0xfffffc00004de19c ra = 0xfffffc00003a00fc curproc = 0xfffffe0007aa4900 pid = 257, comm = disklabel Stopped at Ldotrap+0x8: or zero,zero,t10 db> t Ldotrap() at Ldotrap+0x8 db> x/i 0xfffffc00004de19c Ldotrap+0x8: or zero,zero,t10 db> x/i 0xfffffc00003a00fc dscheck+0x7c: ldah gp,0x1c(ra) db> cont panic: trap panic Stopped at Debugger+0x2c: ldq ra,0(sp) <0xfffffe00084cd6d0> db> cont syncing disks... 28 28 25 15 3 done (da5:isp1:0:131:0): SYNCHRONIZE CACHE. CDB: 35 0 0 0 0 0 0 0 0 0 (da5:isp1:0:131:0): NOT READY Automatic reboot in 15 seconds - press a key on the console to abort Rebooting... halted CPU 0 halt code = 5 HALT instruction executed PC = fffffc00004b0e80 CPU 0 booting To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Wed Oct 6 22: 1: 6 1999 Delivered-To: freebsd-alpha@freebsd.org Received: from mail.toplink.net (mail.toplink.net [195.2.171.8]) by hub.freebsd.org (Postfix) with ESMTP id 1E57114DEB for ; Wed, 6 Oct 1999 22:01:03 -0700 (PDT) (envelope-from ks@hirvi.net) Received: (from uucp@localhost) by mail.toplink.net (8.9.3/8.9.3) with UUCP id HAA08051 for freebsd-alpha@FreeBSD.ORG; Thu, 7 Oct 1999 07:00:51 +0200 (CEST) Received: from karhu.hirvi.net (karhu.hirvi.net [195.2.174.97]) by karhu.hirvi.net (8.9.3/8.9.3) with ESMTP id HAA31331 for ; Thu, 7 Oct 1999 07:00:39 +0200 (CEST) Date: Thu, 7 Oct 1999 07:00:39 +0200 (CEST) From: Kai Schmidt To: freebsd-alpha@FreeBSD.ORG Subject: Installing 3.3 on a Multia Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hello, I tried to install Free BSD 3.3 on a Multia last night. I used the two floppies from the 4.0 snapshot which worked fine on the 3.1 install. Everything went smooth Free BSD seems to install. After the sucessful install I tred to reboot the system and failed. I did a boot dka0 -flags a. But with or without flags the system starts coming up and wants to boot /boot/kernel. There it fails, because it is unable to open /boot/kernel. On this machine I had running Red Hat 6.0 sucessfully before. Any hints? Oh, I lost the bookmark from the web page where somebody desribed how he did the Free BSD install on a Multia. If anybody still knows the URL, please send it to me. Regards Kai -- Kai Schmidt ks@hirvi.net 72218 Wildberg To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Thu Oct 7 1:21:16 1999 Delivered-To: freebsd-alpha@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id 457A914D44 for ; Thu, 7 Oct 1999 01:21:13 -0700 (PDT) (envelope-from gnats@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.9.3/8.9.2) id BAA32693; Thu, 7 Oct 1999 01:20:01 -0700 (PDT) (envelope-from gnats@FreeBSD.org) Received: by hub.freebsd.org (Postfix, from userid 32767) id 252A514D03; Thu, 7 Oct 1999 01:11:17 -0700 (PDT) Message-Id: <19991007081117.252A514D03@hub.freebsd.org> Date: Thu, 7 Oct 1999 01:11:17 -0700 (PDT) From: jch@oleane.net To: freebsd-gnats-submit@freebsd.org X-Send-Pr-Version: www-1.0 Subject: alpha/14175: route for ip aliasing Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >Number: 14175 >Category: alpha >Synopsis: route for ip aliasing >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-alpha >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Thu Oct 7 01:20:01 PDT 1999 >Closed-Date: >Last-Modified: >Originator: Jean-Claude >Release: 3.3 >Organization: OLEANE >Environment: FreeBSD cendrillon.oleane.net 3.3-RELEASE FreeBSD 3.3-RELEASE #2: Mon Sep 27 12:22:59 GMT 1999 root@cendrillon.oleane.net:/usr/src/sys/compile/CENDRILLON alpha >Description: I add an alias on my network interface (de0), and when I do a 'netstat -rn' I dont have the complete route. I've 192.168.1 instead of 192.168.1.0 perhaps it's normal.... >How-To-Repeat: ifconfig de0 inet 192.168.1.20 netmask 255.255.255.0 alias netstat -rn >Fix: >Release-Note: >Audit-Trail: >Unformatted: To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Thu Oct 7 1:39:23 1999 Delivered-To: freebsd-alpha@freebsd.org Received: from herring.nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (Postfix) with ESMTP id C70E814E2D for ; Thu, 7 Oct 1999 01:39:19 -0700 (PDT) (envelope-from dfr@nlsystems.com) Received: from salmon.nlsystems.com (salmon.nlsystems.com [10.0.0.3]) by herring.nlsystems.com (8.9.3/8.8.8) with ESMTP id JAA97475; Thu, 7 Oct 1999 09:40:35 +0100 (BST) (envelope-from dfr@nlsystems.com) Date: Thu, 7 Oct 1999 09:40:35 +0100 (BST) From: Doug Rabson To: Kai Schmidt Cc: freebsd-alpha@freebsd.org Subject: Re: Installing 3.3 on a Multia In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Thu, 7 Oct 1999, Kai Schmidt wrote: > Hello, > > I tried to install Free BSD 3.3 on a Multia last night. > > I used the two floppies from the 4.0 snapshot which worked fine on the > 3.1 install. Everything went smooth Free BSD seems to install. > > After the sucessful install I tred to reboot the system and failed. I > did a boot dka0 -flags a. But with or without flags the system starts > coming up and wants to boot /boot/kernel. There it fails, because it > is unable to open /boot/kernel. > > On this machine I had running Red Hat 6.0 sucessfully before. > > Any hints? Exactly what message is printed when it fails to boot? -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Thu Oct 7 1:39:27 1999 Delivered-To: freebsd-alpha@freebsd.org Received: from herring.nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (Postfix) with ESMTP id 8DC2E14EB9 for ; Thu, 7 Oct 1999 01:39:21 -0700 (PDT) (envelope-from dfr@nlsystems.com) Received: from salmon.nlsystems.com (salmon.nlsystems.com [10.0.0.3]) by herring.nlsystems.com (8.9.3/8.8.8) with ESMTP id JAA96668; Thu, 7 Oct 1999 09:39:16 +0100 (BST) (envelope-from dfr@nlsystems.com) Date: Thu, 7 Oct 1999 09:39:16 +0100 (BST) From: Doug Rabson To: Matthew Jacob Cc: freebsd-alpha@freebsd.org Subject: Re: anyone seen this? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Wed, 6 Oct 1999, Matthew Jacob wrote: > > This is -current, maybe a couple of days old...Sure is hard to focus on > *your* bugs when you trip over this.... Looks like a divide by zero but I can't see any further than that without a stacktrace. Can some just send an alpha system to Poul so that he can test before committing stuff.. -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Thu Oct 7 1:41:50 1999 Delivered-To: freebsd-alpha@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id AE9BA14CF1; Thu, 7 Oct 1999 01:41:48 -0700 (PDT) (envelope-from dfr@FreeBSD.org) Received: (from dfr@localhost) by freefall.freebsd.org (8.9.3/8.9.2) id BAA36576; Thu, 7 Oct 1999 01:41:48 -0700 (PDT) (envelope-from dfr@FreeBSD.org) Date: Thu, 7 Oct 1999 01:41:48 -0700 (PDT) From: Message-Id: <199910070841.BAA36576@freefall.freebsd.org> To: dfr@FreeBSD.org, freebsd-alpha@FreeBSD.org, freebsd-bugs@FreeBSD.org Subject: Re: alpha/14175: route for ip aliasing Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Synopsis: route for ip aliasing Responsible-Changed-From-To: freebsd-alpha->freebsd-bugs Responsible-Changed-By: dfr Responsible-Changed-When: Thu Oct 7 01:39:38 PDT 1999 Responsible-Changed-Why: Misfiled PR To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Thu Oct 7 9: 7:48 1999 Delivered-To: freebsd-alpha@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 0D91814E4D for ; Thu, 7 Oct 1999 09:07:42 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from beppo.feral.com (beppo [192.67.166.79]) by feral.com (8.8.7/8.8.7) with ESMTP id IAA04742; Thu, 7 Oct 1999 08:59:51 -0700 Date: Thu, 7 Oct 1999 08:59:51 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: Doug Rabson , "Jordan K. Hubbard" Cc: freebsd-alpha@freebsd.org Subject: Re: anyone seen this? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Or a serial line to beast's console so he (and others) can do this? On Thu, 7 Oct 1999, Doug Rabson wrote: > On Wed, 6 Oct 1999, Matthew Jacob wrote: > > > > > This is -current, maybe a couple of days old...Sure is hard to focus on > > *your* bugs when you trip over this.... > > Looks like a divide by zero but I can't see any further than that without > a stacktrace. Can some just send an alpha system to Poul so that he can > test before committing stuff.. > > -- > Doug Rabson Mail: dfr@nlsystems.com > Nonlinear Systems Ltd. Phone: +44 181 442 9037 > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Thu Oct 7 12:22:37 1999 Delivered-To: freebsd-alpha@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 6D37E1517C for ; Thu, 7 Oct 1999 12:22:32 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from beppo.feral.com (beppo [192.67.166.79]) by feral.com (8.8.7/8.8.7) with ESMTP id MAA05631 for ; Thu, 7 Oct 1999 12:21:27 -0700 Date: Thu, 7 Oct 1999 12:21:27 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: alpha@freebsd.org Subject: is anyone who was responsible for breaking this going to fix it? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org cc -O -pipe -I/usr/obj/usr/src/tmp/usr/include -c /usr/src/usr.bin/yacc/main.c In file included from /usr/obj/usr/src/tmp/usr/include/machine/frame.h:34, from /usr/obj/usr/src/tmp/usr/include/machine/ucontext.h:34, from /usr/obj/usr/src/tmp/usr/include/sys/ucontext.h:34, from /usr/obj/usr/src/tmp/usr/include/sys/signal.h:238, from /usr/obj/usr/src/tmp/usr/include/signal.h:44, from /usr/src/usr.bin/yacc/main.c:51: /usr/obj/usr/src/tmp/usr/include/machine/alpha_cpu.h:299: syntax error before `alpha_ldbu' /usr/obj/usr/src/tmp/usr/include/machine/alpha_cpu.h:299: syntax error before `*' /usr/obj/usr/src/tmp/usr/include/machine/alpha_cpu.h:299: warning: data definition has no type or storage class /usr/obj/usr/src/tmp/usr/include/machine/alpha_cpu.h:300: syntax error before `alpha_ldwu' /usr/obj/usr/src/tmp/usr/include/machine/alpha_cpu.h:300: syntax error before `*' /usr/obj/usr/src/tmp/usr/include/machine/alpha_cpu.h:300: warning: data definition has no type or storage class /usr/obj/usr/src/tmp/usr/include/machine/alpha_cpu.h:301: syntax error before `*' /usr/obj/usr/src/tmp/usr/include/machine/alpha_cpu.h:302: syntax error before `*' /usr/obj/usr/src/tmp/usr/include/machine/alpha_cpu.h:303: syntax error before `alpha_sextb' /usr/obj/usr/src/tmp/usr/include/machine/alpha_cpu.h:303: warning: parameter names (without types) in function declaration /usr/obj/usr/src/tmp/usr/include/machine/alpha_cpu.h:303: warning: data definition has no type or storage class /usr/obj/usr/src/tmp/usr/include/machine/alpha_cpu.h:304: syntax error before `alpha_sextw' /usr/obj/usr/src/tmp/usr/include/machine/alpha_cpu.h:304: warning: parameter names (without types) in function declaration /usr/obj/usr/src/tmp/usr/include/machine/alpha_cpu.h:304: warning: data definition has no type or storage class /usr/obj/usr/src/tmp/usr/include/machine/alpha_cpu.h:320: syntax error before `vm_offset_t' *** Error code 1 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Thu Oct 7 21:30:27 1999 Delivered-To: freebsd-alpha@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id 9AD0614BDE for ; Thu, 7 Oct 1999 21:30:25 -0700 (PDT) (envelope-from gnats@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.9.3/8.9.2) id VAA97566; Thu, 7 Oct 1999 21:30:00 -0700 (PDT) (envelope-from gnats@FreeBSD.org) Received: by hub.freebsd.org (Postfix, from userid 32767) id 0E6F314BDE; Thu, 7 Oct 1999 21:21:02 -0700 (PDT) Message-Id: <19991008042102.0E6F314BDE@hub.freebsd.org> Date: Thu, 7 Oct 1999 21:21:02 -0700 (PDT) From: aron@cs.rice.edu To: freebsd-gnats-submit@freebsd.org X-Send-Pr-Version: www-1.0 Subject: alpha/14200: kldstat command has formatting problems on 64-bit machines Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >Number: 14200 >Category: alpha >Synopsis: kldstat command has formatting problems on 64-bit machines >Confidential: no >Severity: non-critical >Priority: medium >Responsible: freebsd-alpha >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Thu Oct 7 21:30:00 PDT 1999 >Closed-Date: >Last-Modified: >Originator: Mohit Aron >Release: FreeBSD 4.0-19990809 >Organization: Rice University >Environment: FreeBSD wallis.cs.rice.edu 4.0-19990809-SNAP FreeBSD 4.0-19990809-SNAP #38: Tue Sep 14 19:15:32 CDT 1999 aron@wallis.cs.rice.edu:/usr/home/aron/FreeBSD-src/sys/compile/WALLIS alpha >Description: The kldstat command gives information about the address, size etc of loadable kernel modules. However, on 64-bit machines, the addresses are 64-bits wide. This makes the address value run into the size value in the output of the kldstat command. For example, here's a sample output of kldstat on a 500MHz Alphastation: Id Refs Address Size Name 1 1 0xfffffc0000300000 3eab80 kernel Notice how the address and size fields run into each other due to inadequate space provided for the address on a 64-bit machine. >How-To-Repeat: Simply issue the command 'kldstat' on an alpha. >Fix: Just modify the kldstat program to reserve sufficient space for printing out the address field on 64-bit machines. >Release-Note: >Audit-Trail: >Unformatted: To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Thu Oct 7 22:27:34 1999 Delivered-To: freebsd-alpha@freebsd.org Received: from bos-gate2.raytheon.com (bos-gate2.raytheon.com [199.46.198.231]) by hub.freebsd.org (Postfix) with ESMTP id 2DEC6150E7 for ; Thu, 7 Oct 1999 22:27:26 -0700 (PDT) (envelope-from xdufresn@raytheon.com) Received: from mail1.icg.raytheon.com (mail1.icg.raytheon.com [199.46.170.42]) by bos-gate2.raytheon.com (8.9.3/8.9.3) with ESMTP id AAA15123 for ; Fri, 8 Oct 1999 00:25:28 -0500 (CDT) Received: from smtp-lv01.rsc.raytheon.com (smtp-lv01.rsc.raytheon.com [138.126.175.22]) by mail1.icg.raytheon.com (8.9.3/8.9.3) with ESMTP id AAA23352 for ; Fri, 8 Oct 1999 00:41:32 -0500 (CDT) Received: from rtxmail1.rsc.raytheon.com (rtxmail1.rsc.raytheon.com [138.126.175.35]) by smtp-lv01.rsc.raytheon.com (8.9.3/8.9.3) with ESMTP id AAA24225 for ; Fri, 8 Oct 1999 00:27:03 -0500 (CDT) Received: from raytheon.com (darth.rsc.raytheon.com [138.126.168.48]) by rtxmail1.rsc.raytheon.com (8.9.3/8.9.3) with ESMTP id AAA28885 for ; Fri, 8 Oct 1999 00:27:03 -0500 (CDT) Message-ID: <37FD8007.89495E21@raytheon.com> Date: Fri, 08 Oct 1999 00:24:23 -0500 From: Michael DuFresne X-Mailer: Mozilla 4.7 [en] (X11; U; SunOS 5.6 sun4u) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-alpha@FreeBSD.ORG Subject: (no subject) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org subscribe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Thu Oct 7 23:14:28 1999 Delivered-To: freebsd-alpha@freebsd.org Received: from mail.toplink.net (mail.toplink.net [195.2.171.8]) by hub.freebsd.org (Postfix) with ESMTP id A062215468 for ; Thu, 7 Oct 1999 23:14:21 -0700 (PDT) (envelope-from ks@hirvi.net) Received: (from uucp@localhost) by mail.toplink.net (8.9.3/8.9.3) with UUCP id IAA23961; Fri, 8 Oct 1999 08:14:09 +0200 (CEST) Received: from karhu.hirvi.net (karhu.hirvi.net [195.2.174.97]) by karhu.hirvi.net (8.9.3/8.9.3) with ESMTP id IAA32874; Fri, 8 Oct 1999 08:13:37 +0200 (CEST) Date: Fri, 8 Oct 1999 08:13:37 +0200 (CEST) From: Kai Schmidt To: Doug Rabson Cc: freebsd-alpha@FreeBSD.ORG Subject: Re: Installing 3.3 on a Multia In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Thu, 7 Oct 1999, Doug Rabson wrote: > > Any hints? > Exactly what message is printed when it fails to boot? I can't get hold of the machine right now, but as far as I remember it said: can't open /boot/kernel I have a second multia here, I will try it this evening to reproduce the problem. Regards Kai -- Kai Schmidt ks@hirvi.net 72218 Wildberg To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Fri Oct 8 2: 9:49 1999 Delivered-To: freebsd-alpha@freebsd.org Received: from herring.nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (Postfix) with ESMTP id 73A45158B7 for ; Fri, 8 Oct 1999 02:09:41 -0700 (PDT) (envelope-from dfr@nlsystems.com) Received: from salmon.nlsystems.com (salmon.nlsystems.com [10.0.0.3]) by herring.nlsystems.com (8.9.3/8.8.8) with ESMTP id KAA54591; Fri, 8 Oct 1999 10:12:13 +0100 (BST) (envelope-from dfr@nlsystems.com) Date: Fri, 8 Oct 1999 10:12:13 +0100 (BST) From: Doug Rabson To: Matthew Jacob Cc: alpha@freebsd.org Subject: Re: is anyone who was responsible for breaking this going to fix it? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Thu, 7 Oct 1999, Matthew Jacob wrote: > > > cc -O -pipe -I/usr/obj/usr/src/tmp/usr/include -c > /usr/src/usr.bin/yacc/main.c > In file included from /usr/obj/usr/src/tmp/usr/include/machine/frame.h:34, > from > /usr/obj/usr/src/tmp/usr/include/machine/ucontext.h:34, > from /usr/obj/usr/src/tmp/usr/include/sys/ucontext.h:34, > from /usr/obj/usr/src/tmp/usr/include/sys/signal.h:238, > from /usr/obj/usr/src/tmp/usr/include/signal.h:44, > from /usr/src/usr.bin/yacc/main.c:51: Fixed. -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Sat Oct 9 1: 4:16 1999 Delivered-To: freebsd-alpha@freebsd.org Received: from mail.toplink.net (mail.toplink.net [195.2.171.8]) by hub.freebsd.org (Postfix) with ESMTP id 3950214FB2 for ; Sat, 9 Oct 1999 01:04:11 -0700 (PDT) (envelope-from ks@hirvi.net) Received: (from uucp@localhost) by mail.toplink.net (8.9.3/8.9.3) with UUCP id KAA15421; Sat, 9 Oct 1999 10:04:00 +0200 (CEST) Received: from karhu.hirvi.net (karhu.hirvi.net [195.2.174.97]) by karhu.hirvi.net (8.9.3/8.9.3) with ESMTP id KAA37532; Sat, 9 Oct 1999 10:01:19 +0200 (CEST) Date: Sat, 9 Oct 1999 10:01:19 +0200 (CEST) From: Kai Schmidt To: Doug Rabson Cc: freebsd-alpha@FreeBSD.ORG Subject: Re: Installing 3.3 on a Multia In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Thu, 7 Oct 1999, Doug Rabson wrote: > > Any hints? > Exactly what message is printed when it fails to boot? It prints this message: CPU 0 booting (boot dka0.0.0.6.0 -flags 0) block 0 of dka0.0.0.6.0 is a valid boot block reading 15 blocks from dka0.0.0.6.0 bootstrap code read in base = 166000, image_start = 0, image_bytes = 1e00 initializing HWRPB at 2000 initializing page table at 158000 initializing machine state setting affinity to the primary CPU jumping to bootstrap code Loading /boot/loader Can't open file /boot/loader Then something like this shows up: R2 R3 R4 R29 saved starting at 01F565B0 R2 = 00111A30 R3 = 01F54440 R4 = 01F54518 R29 = 01F565D8 PC = 0006A83C PD = 00111A30 (krn$_process) FP = 01F565D8 SP = 01F565D8 R2 R3 R4 R5 R29 saved starting at 01F565E0 R2 = 00000000 R3 = 00000000 R4 = 00000000 R5 = 00000000 R29 = 00000000 Brk 0 at 0012FF08 0012FF08! BPT Regards Kai -- Kai Schmidt ks@hirvi.net 72218 Wildberg To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Sat Oct 9 2:32:54 1999 Delivered-To: freebsd-alpha@freebsd.org Received: from public.bta.net.cn (public.bta.net.cn [202.96.0.97]) by hub.freebsd.org (Postfix) with ESMTP id E51B214DBA for ; Sat, 9 Oct 1999 02:32:43 -0700 (PDT) (envelope-from robinson@netrinsics.com) Received: from netrinsics.com (robinson@TCE-E-7-182-13.bta.net.cn [202.106.182.13]) by public.bta.net.cn (8.9.3/8.9.3) with ESMTP id RAA06573 for ; Sat, 9 Oct 1999 17:26:54 +0800 (CST) Received: (from robinson@localhost) by netrinsics.com (8.9.3/8.8.7) id RAA03434 for freebsd-alpha@freebsd.org; Sat, 9 Oct 1999 17:33:06 +0800 (CST) (envelope-from robinson) Date: Sat, 9 Oct 1999 17:33:06 +0800 (CST) From: Michael Robinson Message-Id: <199910090933.RAA03434@netrinsics.com> To: freebsd-alpha@freebsd.org Subject: How 64-bit is Alpha FreeBSD? Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I'd like to know what kind of restrictions there are on how big an mmap object can be, how big of an address space one process can have, and other similar things which are limited by the 32-bit word size on the i386 port. Any information, or pointers to information, will be greatly appreciated. -Michael Robinson To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Sat Oct 9 12:10:18 1999 Delivered-To: freebsd-alpha@freebsd.org Received: from uni4nn.gn.iaf.nl (osmium.gn.iaf.nl [193.67.144.12]) by hub.freebsd.org (Postfix) with ESMTP id 4EA6114DF3 for ; Sat, 9 Oct 1999 12:10:13 -0700 (PDT) (envelope-from wilko@yedi.iaf.nl) Received: from yedi.iaf.nl (uucp@localhost) by uni4nn.gn.iaf.nl (8.9.2/8.9.2) with UUCP id VAA09525 for freebsd-alpha@freebsd.org; Sat, 9 Oct 1999 21:01:16 +0200 (MET DST) Received: (from wilko@localhost) by yedi.iaf.nl (8.9.3/8.9.3) id VAA07147 for freebsd-alpha@freebsd.org; Sat, 9 Oct 1999 21:04:24 +0200 (CEST) (envelope-from wilko) From: Wilko Bulte Message-Id: <199910091904.VAA07147@yedi.iaf.nl> Subject: netbooting 3000/400 To: freebsd-alpha@freebsd.org (FreeBSD-alpha mailing list) Date: Sat, 9 Oct 1999 21:04:24 +0200 (CEST) X-Organisation: Private FreeBSD site - Arnhem, The Netherlands X-pgp-info: PGP public key at 'finger wilko@freefall.freebsd.org' X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I know that this is sort-of a known problem, but I hope to find people with strong memories to help me ;-) Situation: DEC3000/400 "Sandpiper" doing a BOOTP netboot: >>> boot ez0 INIT-S-CPU... INIT-S-RESET_TC... INIT-S-ASIC... INIT-S-MEM... INIT-S-NVR... INIT-S-SCC... INIT-S-NI... INIT-S-SCSI... INIT-S-ISDN... INIT-S-TC1... AUDIT_BOOT_STARTS ... AUDIT_BOOT_REQ Host server IP address is 192.168.200.1 AUDIT_BSERVER_FOUND AUDIT_LOAD_BEGINS AUDIT_LOAD_DONE Console: SRM firmware console VMS PAL rev: 0x100010530 OSF PAL rev: 0x20123 Switch to OSF PAL code succeeded. FreeBSD/alpha SRM net boot, Revision 0.1 (root@alpine.iaf.nl, Mon Jul 12 05:13:52 CEST 1999) Memory: 65536 k netbbinfo valid: force = 0, ea = 08:00:2b:3c:61:45 boot: boot device name does not contain ethernet address. boot: using hard-coded ethernet address. boot: ethernet address: 08:00:2b:3c:61:45 prom_init: open failed: 7 Boot device name was: "BOOTP 0 7 0 0 0 2 CORE-IO" Your firmware may be too old to network-boot NetBSD/Alpha, or you might have to hard-code an ethernet address into your network boot block with setnetbootinfo(8). ?05 HLT INSTR PC= 00000000.2000003C PSL= 00000000.00000007 >>> The first thing I had to do is port (well, quick hack) NetBSD's setnetbootinfo for use on FreeBSD as it is missing from the source tree. This was needed because the Sandpiper's SRM did not send the MAC address as part of the boot device name. But a hardcoded MAC address did not solve the issue, the boot device name string returned "BOOTP 0 7 0 0 0 2 CORE-IO" is one field short from what netboot expects. The last field is the device to boot from. I *guess* it needs to be EZ0 but I could be wrong. As for a different SRM version: the latest (V7.0) is not doing BOOTP correctly at all so it looks that one is out. Are there people on this list that have successfully booted a DEC3000 using netboot? If so, which SRM version did you use (assuming there is a working one, which I doubt) or did you hack netboot to make this happen? Wilko -- | / o / / _ Arnhem, The Netherlands - Powered by FreeBSD - |/|/ / / /( (_) Bulte WWW : http://www.tcja.nl http://www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message