From owner-freebsd-alpha Sun Dec 12 8:57:18 1999 Delivered-To: freebsd-alpha@freebsd.org Received: from smtp-out2.bellatlantic.net (smtp-out2.bellatlantic.net [199.45.39.157]) by hub.freebsd.org (Postfix) with ESMTP id 1E51314F9B for ; Sun, 12 Dec 1999 08:57:15 -0800 (PST) (envelope-from shsrms@bellatlantic.net) Received: from bellatlantic.net (adsl-138-88-33-106.bellatlantic.net [138.88.33.106]) by smtp-out2.bellatlantic.net (8.9.1/8.9.1) with ESMTP id MAA02738 for ; Sun, 12 Dec 1999 12:03:02 -0500 (EST) Message-ID: <3853D418.E9D31DFA@bellatlantic.net> Date: Sun, 12 Dec 1999 11:58:00 -0500 From: shsrms/aka/shsrms Reply-To: shsrms@bellatlantic.net X-Mailer: Mozilla 4.5 [en]C-CCK-MCD BA45DSL (WinNT; U) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-alpha@freebsd.org Subject: Potential Newbie Question Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi, I have been using NetBSD on my Vaxen for a few years. I have gotten interested in FreeBSD and am considering setting up my newest alpha to run FreeBSD. I have a couple of questions that relate to my new PC164. Looking in the various FreeBSD resources on the net, I do find refs to jkh running SCSI drives on a PC164, so, does FreeBSD support IDE drives on this beast? What are the supported/recommended video cards? Now one, might be really dumb question, but that is ok.. What is the best way to install FreeBSD on the alpha - I can acquire a CD, I can do the floppies, I could do the FTP across the net- ??? I have looked into it a little, figuring on setting up a PC with Free on it, just to play before I tackle the alpha, but I have been a little frustrated, coming from the Netbsd environment where I can just download the tarball and go at it, Free does not seem to do it that way. Am I off base here? I have been wrong before, I have missed stuff, so If I am missing something now, please feel free to give me a clue!! thanks bob To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Sun Dec 12 11:33:55 1999 Delivered-To: freebsd-alpha@freebsd.org Received: from mach.unseen.org (mach.unseen.org [194.159.240.178]) by hub.freebsd.org (Postfix) with ESMTP id ED9D414D1C for ; Sun, 12 Dec 1999 11:33:53 -0800 (PST) (envelope-from kevin@unseen.org) Received: from kevin (helo=localhost) by mach.unseen.org with local-smtp (Exim 3.03 #1) id 11xEkj-0003SZ-00 for freebsd-alpha@FreeBSD.org; Sun, 12 Dec 1999 19:33:53 +0000 Date: Sun, 12 Dec 1999 19:33:53 +0000 (GMT) From: Kevin Walton To: freebsd-alpha@FreeBSD.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 subscribe -- Kevin Walton Fax: +44 (0)870 1640411 UnSeen.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Sun Dec 12 14: 0:49 1999 Delivered-To: freebsd-alpha@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id 734F114E21 for ; Sun, 12 Dec 1999 14:00:44 -0800 (PST) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.3/8.9.3) with ESMTP id OAA19381 for ; Sun, 12 Dec 1999 14:00:43 -0800 (PST) (envelope-from jdp@polstra.com) Received: (from jdp@localhost) by vashon.polstra.com (8.9.3/8.9.1) id OAA03299 for alpha@freebsd.org; Sun, 12 Dec 1999 14:00:43 -0800 (PST) (envelope-from jdp@polstra.com) 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: Sun, 12 Dec 1999 14:00:42 -0800 (PST) Organization: Polstra & Co., Inc. From: John Polstra To: alpha@freebsd.org Subject: Alpha multiboot: is it possible? Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I have an Alpha with one disk and two root filesystems. The root filesystems are on da0a and da0f. I want to be able to boot either one, but I can't seem to find the magic recipe to boot from da0f. From man loader, I would expect this to work at the loader prompt: unload set currdev=disk0f set rootdev=disk0f load /kernel boot That loads the correct kernel (the one on da0f) but the kernel still thinks its root filesystem is da0a. I tried adding set boot_askname and (next try) set boot_askname=true in an attempt to get the kernel to let me tell it which root filesystem to use. That had no effect. I also tried adding "-a" to the boot command, again with no effect. Is this just broken, or am I doing something wrong? John --- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "No matter how cynical I get, I just can't keep up." -- Nora Ephron To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Sun Dec 12 16:29: 2 1999 Delivered-To: freebsd-alpha@freebsd.org Received: from mass.cdrom.com (castles552.castles.com [208.214.165.116]) by hub.freebsd.org (Postfix) with ESMTP id C854714EA1 for ; Sun, 12 Dec 1999 16:28:59 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id QAA04415; Sun, 12 Dec 1999 16:31:31 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <199912130031.QAA04415@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: John Polstra Cc: alpha@freebsd.org Subject: Re: Alpha multiboot: is it possible? In-reply-to: Your message of "Sun, 12 Dec 1999 14:00:42 PST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 12 Dec 1999 16:31:30 -0800 From: Mike Smith Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > I have an Alpha with one disk and two root filesystems. The root > filesystems are on da0a and da0f. I want to be able to boot either > one, but I can't seem to find the magic recipe to boot from da0f. > >From man loader, I would expect this to work at the loader prompt: > > unload > set currdev=disk0f > set rootdev=disk0f > load /kernel > boot > > That loads the correct kernel (the one on da0f) but the kernel still > thinks its root filesystem is da0a. I tried adding > > set boot_askname > > and (next try) > > set boot_askname=true > > in an attempt to get the kernel to let me tell it which root > filesystem to use. That had no effect. I also tried adding "-a" to > the boot command, again with no effect. > > Is this just broken, or am I doing something wrong? I just got a report that $rootdev doesn't parse correctly without a trailing ':', and indeed the original design was for the trailing colon to be mandatory. Under -current you shouldn't have to set $rootdev at all, as the loader should pick up the contents of /etc/fstab. -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Sun Dec 12 16:40:14 1999 Delivered-To: freebsd-alpha@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id 0763614EF3; Sun, 12 Dec 1999 16:40:13 -0800 (PST) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.3/8.9.3) with ESMTP id QAA19876; Sun, 12 Dec 1999 16:40:12 -0800 (PST) (envelope-from jdp@polstra.com) From: John Polstra Received: (from jdp@localhost) by vashon.polstra.com (8.9.3/8.9.1) id QAA04009; Sun, 12 Dec 1999 16:40:11 -0800 (PST) (envelope-from jdp@polstra.com) Date: Sun, 12 Dec 1999 16:40:11 -0800 (PST) Message-Id: <199912130040.QAA04009@vashon.polstra.com> To: msmith@freebsd.org Subject: Re: Alpha multiboot: is it possible? In-Reply-To: <199912130031.QAA04415@mass.cdrom.com> References: <199912130031.QAA04415@mass.cdrom.com> Organization: Polstra & Co., Seattle, WA Cc: alpha@freebsd.org Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In article <199912130031.QAA04415@mass.cdrom.com>, Mike Smith wrote: > > I just got a report that $rootdev doesn't parse correctly without a > trailing ':', and indeed the original design was for the trailing colon > to be mandatory. I tried it with the trailing colon too, but that didn't make any difference. My setup is a bit complicated, so let me fill in the details. On da0a I have -current. On da0f I have -stable. I suppose the /boot/loader that's being used is coming from da0a, so maybe that causes problems for booting a -stable kernel. I even tried configuring the -stable kernel with an explicit "config kernel root on da0f" in the config file, but it still gives me da0a as the root filesystem when I boot it. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "No matter how cynical I get, I just can't keep up." -- Nora Ephron To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Sun Dec 12 19:21:39 1999 Delivered-To: freebsd-alpha@freebsd.org Received: from mass.cdrom.com (castles516.castles.com [208.214.165.80]) by hub.freebsd.org (Postfix) with ESMTP id 1DFAD14DD2 for ; Sun, 12 Dec 1999 19:21:36 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id TAA04953; Sun, 12 Dec 1999 19:24:14 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <199912130324.TAA04953@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: John Polstra Cc: alpha@freebsd.org Subject: Re: Alpha multiboot: is it possible? In-reply-to: Your message of "Sun, 12 Dec 1999 16:40:11 PST." <199912130040.QAA04009@vashon.polstra.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 12 Dec 1999 19:24:13 -0800 From: Mike Smith Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > In article <199912130031.QAA04415@mass.cdrom.com>, > Mike Smith wrote: > > > > I just got a report that $rootdev doesn't parse correctly without a > > trailing ':', and indeed the original design was for the trailing colon > > to be mandatory. > > I tried it with the trailing colon too, but that didn't make any > difference. > > My setup is a bit complicated, so let me fill in the details. On da0a > I have -current. On da0f I have -stable. I suppose the /boot/loader > that's being used is coming from da0a, so maybe that causes problems > for booting a -stable kernel. > > I even tried configuring the -stable kernel with an explicit "config > kernel root on da0f" in the config file, but it still gives me da0a as > the root filesystem when I boot it. I don't think -stable on the alpha will work with / anywhere but on da0a. You might try swapping the two systems around, since -current _should_ work properly like that. -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Sun Dec 12 19:32: 2 1999 Delivered-To: freebsd-alpha@freebsd.org Received: from mass.cdrom.com (castles516.castles.com [208.214.165.80]) by hub.freebsd.org (Postfix) with ESMTP id D29F214D48 for ; Sun, 12 Dec 1999 19:31:59 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id TAA04994; Sun, 12 Dec 1999 19:33:03 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <199912130333.TAA04994@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: shsrms@bellatlantic.net Cc: freebsd-alpha@freebsd.org Subject: Re: Potential Newbie Question In-reply-to: Your message of "Sun, 12 Dec 1999 11:58:00 EST." <3853D418.E9D31DFA@bellatlantic.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 12 Dec 1999 19:33:03 -0800 From: Mike Smith Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > Hi, > I have been using NetBSD on my Vaxen for a few years. > I have gotten interested in FreeBSD and am considering > setting up my newest alpha to run FreeBSD. > > I have a couple of questions that relate to my new > PC164. > > Looking in the various FreeBSD resources on the net, I do find > refs to jkh running SCSI drives on a PC164, so, does FreeBSD support > IDE drives on this beast? They should work, but you can't boot from them (only the PC164SX supports that AFAIK). > What are the supported/recommended video cards? Same as for the x86 - note that we don't support the TGA cards. In reality your prospects are a little more limited - eg. I have had no luck with TNT-based cards on the Alpha. I've had good results with #9 and Matrox cards though. > Now one, might be really dumb question, but that is ok.. > What is the best way to install FreeBSD on the alpha - > I can acquire a CD, I can do the floppies, I could do the FTP across the > net- FTP installs work well. We're still a bit early on with the Alpha CD distributions, and floppy installs are _agonising_. > I have looked into it a little, figuring on setting up a PC with Free on > it, just to play before I tackle the alpha, but I have been a little > frustrated, coming from the Netbsd environment where I can just download > the tarball and go at it, Free does not seem to do it that way. Am I off > base here? Just looking at things from a different angle. I'm not sure what you mean by "just download the tarball and go at it" - you still have to bootstrap the system and suck the tarball in. With FreeBSD all you download are the floppy images; it'll do all the rest itself. > I have been wrong before, I have missed stuff, so If I am missing > something now, please feel free to give me a clue!! Sounds like you're headed in about the right direction; if you want to tinker I'd recommend going to ftp.freebsd.org/pub/FreeBSD/snapshots/alpha, grab the kern.flp and mfsroot.flp images out of the floppies directory in the most recent snapshot there, cut them onto floppies and boot the kern.flp image. Just about everything from there should be pretty self-explanatory (but feel free to ask). Don't forget the point about booting from IDE drives though. -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Sun Dec 12 20:28:44 1999 Delivered-To: freebsd-alpha@freebsd.org Received: from gw.one.com.au (gw.one.com.au [203.18.85.1]) by hub.freebsd.org (Postfix) with ESMTP id 98F4614FEC for ; Sun, 12 Dec 1999 20:28:36 -0800 (PST) (envelope-from MAX@one.com.au) Received: from one.com.au (pxx.local [10.18.85.1]) by gw.one.com.au (8.9.2/8.9.2) with SMTP id OAA28690 for alpha@freebsd.org; Mon, 13 Dec 1999 14:27:55 +1000 (EST) (envelope-from MAX@one.com.au) Date: Mon, 13 Dec 1999 14:27:55 +1000 (EST) From: MAX@one.com.au Message-Id: <199912130427.OAA28690@gw.one.com.au> Subject: /usr/libexec/ld-elf.so.1: Shared object "libncurses.so.5" not found Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi all, I was wondering what went wrong when I install the tcsh shell. The installation process did not give me any error. But I have error on the execution. Is there any other shared files required to run this shell? Thanks. max To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Mon Dec 13 9:42:21 1999 Delivered-To: freebsd-alpha@freebsd.org Received: from egsner.cirr.com (egsner.cirr.com [192.67.63.1]) by hub.freebsd.org (Postfix) with ESMTP id EBD07154AE; Mon, 13 Dec 1999 09:42:15 -0800 (PST) (envelope-from eric@cirr.com) Received: from cirr.com (IDENT:eric@egsner.cirr.com [192.67.63.1]) by egsner.cirr.com (8.9.0/8.9.1) with ESMTP id LAA16003; Mon, 13 Dec 1999 11:42:12 -0600 (CST) Message-Id: <199912131742.LAA16003@egsner.cirr.com> From: eric@cirr.com (Eric Schnoebelen) To: Mike Smith Cc: shsrms@bellatlantic.net, freebsd-alpha@FreeBSD.ORG Subject: Re: Potential Newbie Question In-reply-to: Your message of "Sun, 12 Dec 1999 19:33:03 PST." <199912130333.TAA04994@mass.cdrom.com> Date: Mon, 13 Dec 1999 11:42:11 -0600 Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Mike Smith writes: - > Looking in the various FreeBSD resources on the net, I do find - > refs to jkh running SCSI drives on a PC164, so, does FreeBSD support - > IDE drives on this beast? - - They should work, but you can't boot from them (only the PC164SX supports - that AFAIK). Please don't tell my PC164 that it can't boot from an IDE drive! :-) Seriously, with a late model SRM, the PC164 MB can boot from an IDE drive without any problems. Note: I'm currently running NetBSD on that system, and haven't tried to boot FreeBSD off of the IDE drive, so there may be issues in FreeBSD with it. However, SRM understands and can boot from the IDE drive. -- Eric Schnoebelen eric@cirr.com http://www.cirr.com The law of gravity says no fair jumping up without coming back down. -- 5th grader's description. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Mon Dec 13 17: 5:33 1999 Delivered-To: freebsd-alpha@freebsd.org Received: from smtp-out2.bellatlantic.net (smtp-out2.bellatlantic.net [199.45.39.157]) by hub.freebsd.org (Postfix) with ESMTP id 70FB015252; Mon, 13 Dec 1999 17:05:29 -0800 (PST) (envelope-from shsrms@bellatlantic.net) Received: from bellatlantic.net (adsl-138-88-35-233.bellatlantic.net [138.88.35.233]) by smtp-out2.bellatlantic.net (8.9.1/8.9.1) with ESMTP id UAA16197; Mon, 13 Dec 1999 20:11:15 -0500 (EST) Message-ID: <38559809.67C00E24@bellatlantic.net> Date: Mon, 13 Dec 1999 20:06:17 -0500 From: shsrms/aka/shsrms Reply-To: shsrms@bellatlantic.net X-Mailer: Mozilla 4.5 [en]C-CCK-MCD BA45DSL (WinNT; U) X-Accept-Language: en MIME-Version: 1.0 To: Mike Smith Cc: freebsd-alpha@freebsd.org Subject: Re: Potential Newbie Question References: <199912130333.TAA04994@mass.cdrom.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Thanks Mike! That was a great bit of info!! bob To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Mon Dec 13 17: 9:53 1999 Delivered-To: freebsd-alpha@freebsd.org Received: from mass.cdrom.com (mass.cdrom.com [204.216.28.184]) by hub.freebsd.org (Postfix) with ESMTP id 90BE015450 for ; Mon, 13 Dec 1999 17:09:46 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id RAA01699; Mon, 13 Dec 1999 17:10:31 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <199912140110.RAA01699@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: eric@cirr.com (Eric Schnoebelen) Cc: shsrms@bellatlantic.net, freebsd-alpha@FreeBSD.ORG Subject: Re: Potential Newbie Question In-reply-to: Your message of "Mon, 13 Dec 1999 11:42:11 CST." <199912131742.LAA16003@egsner.cirr.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 13 Dec 1999 17:10:31 -0800 From: Mike Smith Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > Mike Smith writes: > - > Looking in the various FreeBSD resources on the net, I do find > - > refs to jkh running SCSI drives on a PC164, so, does FreeBSD support > - > IDE drives on this beast? > - > - They should work, but you can't boot from them (only the PC164SX supports > - that AFAIK). > > Please don't tell my PC164 that it can't boot from an IDE > drive! :-) > > Seriously, with a late model SRM, the PC164 MB can boot > from an IDE drive without any problems. > > Note: I'm currently running NetBSD on that system, and > haven't tried to boot FreeBSD off of the IDE drive, so there may > be issues in FreeBSD with it. However, SRM understands and can > boot from the IDE drive. Cool. Now I have to go pull the box and see if it works here. Just to be sure, this is a PC164 you're talking about, not a PC164LX, PC164UX or PC164SX, right? Thanks for the heads-up! -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Mon Dec 13 17:34:44 1999 Delivered-To: freebsd-alpha@freebsd.org Received: from opus.cirr.com (opus.cirr.com [192.67.63.6]) by hub.freebsd.org (Postfix) with ESMTP id 38D9D14A0A; Mon, 13 Dec 1999 17:34:28 -0800 (PST) (envelope-from eric@cirr.com) Received: from cirr.com (IDENT:eric@egsner.cirr.com [192.67.63.1]) by opus.cirr.com (8.9.0/8.9.0) with ESMTP id TAA20952; Mon, 13 Dec 1999 19:34:04 -0600 (CST) Message-Id: <199912140134.TAA20952@opus.cirr.com> From: eric@cirr.com (Eric Schnoebelen) To: Mike Smith Cc: shsrms@bellatlantic.net, freebsd-alpha@FreeBSD.ORG Subject: Re: Potential Newbie Question In-reply-to: Your message of "Mon, 13 Dec 1999 17:10:31 PST." <199912140110.RAA01699@mass.cdrom.com> Date: Mon, 13 Dec 1999 19:34:02 -0600 Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Mike Smith writes: - > Mike Smith writes: - > - > Looking in the various FreeBSD resources on the net, I do find - > - > refs to jkh running SCSI drives on a PC164, so, does FreeBSD support - > - > IDE drives on this beast? - > - - > - They should work, but you can't boot from them (only the PC164SX supports - > - that AFAIK). - > - > Please don't tell my PC164 that it can't boot from an IDE - > drive! :-) - > - > Seriously, with a late model SRM, the PC164 MB can boot - > from an IDE drive without any problems. - > - > Note: I'm currently running NetBSD on that system, and - > haven't tried to boot FreeBSD off of the IDE drive, so there may - > be issues in FreeBSD with it. However, SRM understands and can - > boot from the IDE drive. - - Cool. Now I have to go pull the box and see if it works here. Just to - be sure, this is a PC164 you're talking about, not a PC164LX, PC164UX or - PC164SX, right? Yup, it's a MBD-PC164-500, if that means anything. dmesg says: Copyright (c) 1996, 1997, 1998, 1999 The NetBSD Foundation, Inc. All rights reserved. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. NetBSD 1.4.1 (MILO) #1: Sun Nov 21 20:24:18 PST 1999 eric@milo:/home/milo/eric/work/syssrc/sys/arch/alpha/compile/MILO Digital AlphaPC 164 500 MHz 8192 byte page size, 1 processor. real mem = 67108864 (2531328 reserved for PROM, 64577536 used by NetBSD) avail mem = 53477376 using 788 buffers containing 6455296 bytes of memory mainbus0 (root) cpu0 at mainbus0: ID 0 (primary), 21164A-2 (pass 2) cia0 at mainbus0: DECchip 2117x Core Logic Chipset (ALCOR/ALCOR2), pass 3 cia0: extended capabilities: 21 cia0: using BWX for PCI config access pci0 at cia0 bus 0 pci0: i/o enabled, memory enabled ncr0 at pci0 dev 5 function 0: ncr 53c815 fast10 scsi ncr0: interrupting at eb164 irq 2 ncr0: minsync=25, maxsync=206, maxoffs=8, 16 dwords burst, normal dma fifo ncr0: single-ended, open drain IRQ driver ncr0: restart (scsi reset). scsibus0 at ncr0: 8 targets, 8 luns per target sio0 at pci0 dev 8 function 0: Intel 82378ZB System I/O (SIO) (rev. 0x43) de0 at pci0 dev 9 function 0 de0: interrupting at eb164 irq 3 de0: Cogent 21040 [10Mb/s] pass 2.4 de0: address 00:00:92:91:41:60 pciide0 at pci0 dev 11 function 0: CMD Technology PCI0646 pciide0: bus-master DMA support present pciide0: primary channel wired to compatibility mode wd0 at pciide0 channel 0 drive 0: wd0: drive supports 16-sector pio transfers, lba addressing wd0: 2014MB, 4092 cyl, 16 head, 63 sec, 512 bytes/sect x 4124736 sectors wd0: 32-bits data port wd0: drive supports PIO mode 4, DMA mode 2 pciide0: secondary channel wired to compatibility mode pciide0: disabling secondary channel (no drives) wd0(pciide0:0:0): using PIO mode 4, DMA mode 2 (using DMA data transfers) isa0 at sio0 com0 at isa0 port 0x3f8-0x3ff irq 4: ns16550a, working fifo com0: console com1 at isa0 port 0x2f8-0x2ff irq 3: ns16550a, working fifo lpt0 at isa0 port 0x3bc-0x3bf irq 7 pckbc0 at isa0 port 0x60-0x64 pcppi0 at isa0 port 0x61 spkr0 at pcppi0 isabeep0 at pcppi0 fdc0 at isa0 port 0x3f0-0x3f7 irq 6 drq 2 fd0 at fdc0 drive 0: 1.44MB, 80 cyl, 2 head, 18 sec mcclock0 at isa0 port 0x70-0x71: mc146818 or compatible root on wd0a dumps on wd0b root file system type: ffs de0: enabling 10baseT port -- Eric Schnoebelen eric@cirr.com http://www.cirr.com Windows has detected that a gnat has farted near your computer. Press any key to reboot. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Mon Dec 13 21:38:40 1999 Delivered-To: freebsd-alpha@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id 7132E1531E; Mon, 13 Dec 1999 21:38:38 -0800 (PST) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.3/8.9.3) with ESMTP id VAA27300; Mon, 13 Dec 1999 21:38:37 -0800 (PST) (envelope-from jdp@polstra.com) Received: (from jdp@localhost) by vashon.polstra.com (8.9.3/8.9.1) id VAA00443; Mon, 13 Dec 1999 21:38:37 -0800 (PST) (envelope-from jdp@polstra.com) 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: Mon, 13 Dec 1999 21:38:37 -0800 (PST) Organization: Polstra & Co., Inc. From: John Polstra To: alpha@freebsd.org Subject: Alpha Makefile is broken for config -g in -stable Cc: dfr@freebsd.org Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On -stable Alpha systems, if you do a "config -g" and then try to build a kernel, the build stops with "make: don't know how to make kernel.debug. Stop". I am pretty sure the breakage was introduced in revision 1.16.2.3 of Makefile.alpha. It looks like some -currentisms were introduced without the corresponding changes in "config". N.B., -stable i386 systems don't even try to do the kernel.debug thing -- that's -current only. If any of you have time to try to fix this before the release, it would be a Very Good Thing. I don't think I'm going to have time to work on it between now and then. John --- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "No matter how cynical I get, I just can't keep up." -- Nora Ephron To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Tue Dec 14 0:59:59 1999 Delivered-To: freebsd-alpha@freebsd.org Received: from gallions-reach.inpharmatica.co.uk (gallions-reach.inpharmatica.co.uk [193.115.214.5]) by hub.freebsd.org (Postfix) with ESMTP id C10F915336; Tue, 14 Dec 1999 00:59:56 -0800 (PST) (envelope-from m.seaman@inpharmatica.co.uk) Received: from kings-cross.inpharmatica.co.uk (euston.inpharmatica.co.uk [193.115.214.6]) by gallions-reach.inpharmatica.co.uk (8.8.8/8.8.8) with ESMTP id IAA06594; Tue, 14 Dec 1999 08:59:41 GMT (envelope-from m.seaman@inpharmatica.co.uk) Received: from paddington.inpharmatica.co.uk (IDENT:root@paddington.inpharmatica.co.uk [192.168.122.1]) by kings-cross.inpharmatica.co.uk (8.9.3/8.9.3) with ESMTP id IAA06417; Tue, 14 Dec 1999 08:59:40 GMT Received: from inpharmatica.co.uk (IDENT:matthew@localhost [127.0.0.1]) by paddington.inpharmatica.co.uk (8.9.3/8.9.3) with ESMTP id IAA02359; Tue, 14 Dec 1999 08:59:40 GMT Message-ID: <385606FC.899355FF@inpharmatica.co.uk> Date: Tue, 14 Dec 1999 08:59:40 +0000 From: Matthew Seaman X-Mailer: Mozilla 4.61 [en] (X11; I; Linux 2.2.4 i586) X-Accept-Language: en-GB, en MIME-Version: 1.0 To: John Polstra Cc: alpha@FreeBSD.ORG, dfr@FreeBSD.ORG Subject: Re: Alpha Makefile is broken for config -g in -stable References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org John Polstra wrote: > > On -stable Alpha systems, if you do a "config -g" and then try to > build a kernel, the build stops with "make: don't know how to make > kernel.debug. Stop". I am pretty sure the breakage was introduced in > revision 1.16.2.3 of Makefile.alpha. It looks like some -currentisms > were introduced without the corresponding changes in "config". N.B., > -stable i386 systems don't even try to do the kernel.debug thing -- > that's -current only. That's been around for a while --- since 3.2 at least: PR conf/12832 Matthew -- Certe, Toto, sentio nos in Kansate non iam adesse. Dr. Matthew Seaman, Inpharmatica Ltd, 60 Charlotte St, London, W1P 2AX Tel: +44 171 631 4644 x229 Fax: +44 171 631 4844 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Tue Dec 14 2: 2:18 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 1493614A09; Tue, 14 Dec 1999 02:02:10 -0800 (PST) (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 KAA35935; Tue, 14 Dec 1999 10:11:31 GMT (envelope-from dfr@nlsystems.com) Date: Tue, 14 Dec 1999 10:11:31 +0000 (GMT) From: Doug Rabson To: John Polstra Cc: alpha@freebsd.org, dfr@freebsd.org Subject: Re: Alpha Makefile is broken for config -g in -stable 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 Mon, 13 Dec 1999, John Polstra wrote: > On -stable Alpha systems, if you do a "config -g" and then try to > build a kernel, the build stops with "make: don't know how to make > kernel.debug. Stop". I am pretty sure the breakage was introduced in > revision 1.16.2.3 of Makefile.alpha. It looks like some -currentisms > were introduced without the corresponding changes in "config". N.B., > -stable i386 systems don't even try to do the kernel.debug thing -- > that's -current only. > > If any of you have time to try to fix this before the release, it > would be a Very Good Thing. I don't think I'm going to have time to > work on it between now and then. I don't have a stable machine to test with right now but this patch might fix it (on the other hand, it might make things worse): Index: Makefile.alpha =================================================================== RCS file: /home/ncvs/src/sys/alpha/conf/Makefile.alpha,v retrieving revision 1.16.2.6 diff -u -r1.16.2.6 Makefile.alpha --- Makefile.alpha 1999/08/29 15:56:41 1.16.2.6 +++ Makefile.alpha 1999/12/14 10:07:53 @@ -98,12 +98,26 @@ %MFILES -%LOAD - %CLEAN +all: ${KERNEL} + +.if !defined(DEBUG) +FULLKERNEL= ${KERNEL} +.else +FULLKERNEL= ${KERNEL}.debug +${KERNEL}: ${FULLKERNEL} + objcopy --strip-debug ${FULLKERNEL} ${KERNEL} +.endif + +${FULLKERNEL}: ${BEFORE_DEPEND} ${SYSTEM_DEP} vers.o + @rm -f ${.TARGET} + @echo linking ${.TARGET} + ${SYSTEM_LD} + ${SYSTEM_LD_TAIL} + .if !exists(.depend) -${SYSTEM_OBJS}: ${BEFORE_DEPEND:M*.h} +${SYSTEM_OBJS}: vnode_if.h ${BEFORE_DEPEND:M*.h} .endif clean: -- 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 Dec 14 8:57:55 1999 Delivered-To: freebsd-alpha@freebsd.org Received: from metzelkueche.tabu.uni-bonn.de (metzelkueche.tabu.uni-bonn.de [131.220.159.242]) by hub.freebsd.org (Postfix) with ESMTP id 09EC1152DA for ; Tue, 14 Dec 1999 08:57:53 -0800 (PST) (envelope-from armin@metzelkueche.tabu.uni-bonn.de) Received: from localhost (localhost [127.0.0.1]) by metzelkueche.tabu.uni-bonn.de (8.9.3/8.9.3) with ESMTP id RAA12388 for ; Tue, 14 Dec 1999 17:57:24 +0100 Date: Tue, 14 Dec 1999 17:57:24 +0100 (MET) From: Armin Ollig X-Sender: armin@metzelkueche.tabu.uni-bonn.de To: alpha@freebsd.org Subject: make world 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 Hi, i did a make buildworld -DNOGAMES -DNOSHARE on yesterdays -current. While doing make installworld the make crashed on signal 12. After that i was not able to start any programm (not even 'more' to check the make.log when the error occured). However the shell was still functional. When rebooting (old or new kernel) the login promt does not come up, because getty cannot start correctly. Is it a good idea to boot from floppy and copy the /usr/obj stuff by hand and hope things come back ? Or should i go back to the snapshot i started with ? Thanks in advance, -Armin PS: I will do disaster discovery this night, maybe i can give additional info after that... -- "To save energy the light at the end of the tunnel will temporarily be switched off." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Tue Dec 14 9:22:56 1999 Delivered-To: freebsd-alpha@freebsd.org Received: from mail.scc.nl (node1374.a2000.nl [62.108.19.116]) by hub.freebsd.org (Postfix) with ESMTP id 607CB14CE7 for ; Tue, 14 Dec 1999 09:22:52 -0800 (PST) (envelope-from freebsd-alpha@scc.nl) Received: (from daemon@localhost) by mail.scc.nl (8.9.3/8.9.3) id SAA75719 for alpha@FreeBSD.org; Tue, 14 Dec 1999 18:13:53 +0100 (CET) (envelope-from freebsd-alpha@scc.nl) Received: from GATEWAY by dwarf.hq.scc.nl with netnews for alpha@FreeBSD.org (alpha@FreeBSD.org) To: alpha@FreeBSD.org Date: Tue, 14 Dec 1999 18:13:46 +0100 From: Marcel Moolenaar Message-ID: <38567ACA.75E6593@scc.nl> Organization: SCC vof Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit References: Subject: Re: make world broken ? Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Armin Ollig wrote: > i did a make buildworld -DNOGAMES -DNOSHARE on yesterdays -current. > While doing make installworld the make crashed on signal 12. How old was the snapshot you came from? I guess it's one before the sigset_t change... > Is it a good idea to boot from floppy and copy the /usr/obj stuff by hand > and hope things come back ? > Or should i go back to the snapshot i started with ? Installing a new kernel should solve your problems. -- Marcel Moolenaar mailto:marcel@scc.nl SCC Internetworking & Databases http://www.scc.nl/ The FreeBSD project mailto:marcel@FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Tue Dec 14 13: 5:17 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 E37A0152E5 for ; Tue, 14 Dec 1999 13:05:13 -0800 (PST) (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 VAA18428 for freebsd-alpha@freebsd.org; Tue, 14 Dec 1999 21:04:21 +0100 (MET) Received: (from wilko@localhost) by yedi.iaf.nl (8.9.3/8.9.3) id VAA35173 for freebsd-alpha@freebsd.org; Tue, 14 Dec 1999 21:39:15 +0100 (CET) (envelope-from wilko) Date: Tue, 14 Dec 1999 21:39:15 +0100 From: Wilko Bulte To: FreeBSD-alpha mailing list Subject: use of -mcpu=21164a Message-ID: <19991214213915.A35163@yedi.iaf.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i X-OS: FreeBSD yedi.iaf.nl 3.3-STABLE FreeBSD 3.3-STABLE X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Will adding -mcpu=21164a to CFLAGS in /etc/make.conf result in code not running on EV4/21064 CPUs? -- Wilko Bulte Arnhem, The Netherlands - The FreeBSD Project 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 From owner-freebsd-alpha Tue Dec 14 13: 9:55 1999 Delivered-To: freebsd-alpha@freebsd.org Received: from lestat.nas.nasa.gov (lestat.nas.nasa.gov [129.99.33.127]) by hub.freebsd.org (Postfix) with ESMTP id 879A314E6C for ; Tue, 14 Dec 1999 13:09:53 -0800 (PST) (envelope-from thorpej@lestat.nas.nasa.gov) Received: from lestat (localhost [127.0.0.1]) by lestat.nas.nasa.gov (8.8.8/8.6.12) with ESMTP id NAA29906; Tue, 14 Dec 1999 13:09:40 -0800 (PST) Message-Id: <199912142109.NAA29906@lestat.nas.nasa.gov> To: Wilko Bulte Cc: FreeBSD-alpha mailing list Subject: Re: use of -mcpu=21164a Reply-To: Jason Thorpe From: Jason Thorpe Date: Tue, 14 Dec 1999 13:09:39 -0800 Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Tue, 14 Dec 1999 21:39:15 +0100 Wilko Bulte wrote: > Will adding -mcpu=21164a to CFLAGS in /etc/make.conf > result in code not running on EV4/21064 CPUs? The Alpha Architecture specifies that user programs can expect the kernel to emulate BWX, so it should work, albeit a bit more slowly in the event that BWX is actually used. Also, your assembler has to do the right thing; gas will treat the BWX instructions are macros and open-code the equivalent in EV4 instructions unless it is explicitly in EV56 (or greater) mode. If your compiler is targeted correctly, the assembler will behave properly. If not, you'll have to pass additional flags. -- Jason R. Thorpe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Tue Dec 14 13:35:24 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 B851F15378 for ; Tue, 14 Dec 1999 13:35:18 -0800 (PST) (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 VAA19934 for freebsd-alpha@freebsd.org; Tue, 14 Dec 1999 21:35:03 +0100 (MET) Received: (from wilko@localhost) by yedi.iaf.nl (8.9.3/8.9.3) id VAA35549 for freebsd-alpha@freebsd.org; Tue, 14 Dec 1999 21:56:44 +0100 (CET) (envelope-from wilko) Date: Tue, 14 Dec 1999 21:56:44 +0100 From: Wilko Bulte To: FreeBSD-alpha mailing list Subject: netboot on alpha Message-ID: <19991214215644.A35183@yedi.iaf.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i X-OS: FreeBSD yedi.iaf.nl 3.3-STABLE FreeBSD 3.3-STABLE X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Has anybody recently tested the netboot functionality of FreeBSD/alpha? Reason for asking is that an older netboot exec seems to work: FreeBSD/alpha SRM net boot, Revision 0.1 (root@alpine.iaf.nl, Tue Oct 19 18:47:13 CEST 1999) Memory: 98304 k but the one in -current does not appear to.. -- Wilko Bulte Arnhem, The Netherlands - The FreeBSD Project 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 From owner-freebsd-alpha Tue Dec 14 14: 5:22 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 6B5BC15409 for ; Tue, 14 Dec 1999 14:05:15 -0800 (PST) (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 WAA21790; Tue, 14 Dec 1999 22:09:58 +0100 (MET) Received: (from wilko@localhost) by yedi.iaf.nl (8.9.3/8.9.3) id WAA36193; Tue, 14 Dec 1999 22:47:35 +0100 (CET) (envelope-from wilko) Date: Tue, 14 Dec 1999 22:47:29 +0100 From: Wilko Bulte To: Jason Thorpe Cc: FreeBSD-alpha mailing list Subject: Re: use of -mcpu=21164a Message-ID: <19991214224728.A36085@yedi.iaf.nl> References: <199912142109.NAA29906@lestat.nas.nasa.gov> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <199912142109.NAA29906@lestat.nas.nasa.gov>; from thorpej@nas.nasa.gov on Tue, Dec 14, 1999 at 01:09:39PM -0800 X-OS: FreeBSD yedi.iaf.nl 3.3-STABLE FreeBSD 3.3-STABLE X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Tue, Dec 14, 1999 at 01:09:39PM -0800, Jason Thorpe wrote: > On Tue, 14 Dec 1999 21:39:15 +0100 > Wilko Bulte wrote: > > > Will adding -mcpu=21164a to CFLAGS in /etc/make.conf > > result in code not running on EV4/21064 CPUs? > > The Alpha Architecture specifies that user programs can expect the kernel > to emulate BWX, so it should work, albeit a bit more slowly in the event > that BWX is actually used. OK. > Also, your assembler has to do the right thing; gas will treat the BWX > instructions are macros and open-code the equivalent in EV4 instructions > unless it is explicitly in EV56 (or greater) mode. So, in case of -mcpu=21164a gas will generate BWX and if -mcpu=21164a is omitted it will open-code in EV4 instructions? > If your compiler is targeted correctly, the assembler will behave properly. > If not, you'll have to pass additional flags. Time to explain where I'm coming from: what if I generate 'netboot' on a Miata with mcpu=m21164a and want to use the generated netboot on a Sandpiper (EV4)? There is no kernel (yet) to emulate BWX so I lose, right? Thanks, -- Wilko Bulte Arnhem, The Netherlands - The FreeBSD Project 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 From owner-freebsd-alpha Tue Dec 14 14:14:59 1999 Delivered-To: freebsd-alpha@freebsd.org Received: from lestat.nas.nasa.gov (lestat.nas.nasa.gov [129.99.33.127]) by hub.freebsd.org (Postfix) with ESMTP id 20C6614CC3 for ; Tue, 14 Dec 1999 14:14:55 -0800 (PST) (envelope-from thorpej@lestat.nas.nasa.gov) Received: from lestat (localhost [127.0.0.1]) by lestat.nas.nasa.gov (8.8.8/8.6.12) with ESMTP id OAA00903; Tue, 14 Dec 1999 14:14:45 -0800 (PST) Message-Id: <199912142214.OAA00903@lestat.nas.nasa.gov> To: Wilko Bulte Cc: FreeBSD-alpha mailing list Subject: Re: use of -mcpu=21164a Reply-To: Jason Thorpe From: Jason Thorpe Date: Tue, 14 Dec 1999 14:14:45 -0800 Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Tue, 14 Dec 1999 22:47:29 +0100 Wilko Bulte wrote: > > Also, your assembler has to do the right thing; gas will treat the BWX > > instructions are macros and open-code the equivalent in EV4 instructions > > unless it is explicitly in EV56 (or greater) mode. > > So, in case of -mcpu=21164a gas will generate BWX and if -mcpu=21164a > is omitted it will open-code in EV4 instructions? Yes. (Of course, I'd rather it emitted an error, or a warning, at least...) > what if I generate 'netboot' on a Miata with mcpu=m21164a and want to > use the generated netboot on a Sandpiper (EV4)? There is no kernel (yet) > to emulate BWX so I lose, right? Right, if the compiler/assembler emitted BWX, you lose. -- Jason R. Thorpe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Tue Dec 14 15:20:29 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 128AA152F9 for ; Tue, 14 Dec 1999 15:20:26 -0800 (PST) (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 XAA26446; Tue, 14 Dec 1999 23:31:31 +0100 (MET) Received: (from wilko@localhost) by yedi.iaf.nl (8.9.3/8.9.3) id AAA77553; Wed, 15 Dec 1999 00:00:00 +0100 (CET) (envelope-from wilko) Date: Wed, 15 Dec 1999 00:00:00 +0100 From: Wilko Bulte To: Jason Thorpe Cc: FreeBSD-alpha mailing list Subject: Re: use of -mcpu=21164a Message-ID: <19991215000000.B77327@yedi.iaf.nl> References: <199912142214.OAA00903@lestat.nas.nasa.gov> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <199912142214.OAA00903@lestat.nas.nasa.gov>; from thorpej@nas.nasa.gov on Tue, Dec 14, 1999 at 02:14:45PM -0800 X-OS: FreeBSD yedi.iaf.nl 3.3-STABLE FreeBSD 3.3-STABLE X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Tue, Dec 14, 1999 at 02:14:45PM -0800, Jason Thorpe wrote: > On Tue, 14 Dec 1999 22:47:29 +0100 > Wilko Bulte wrote: > > > > Also, your assembler has to do the right thing; gas will treat the BWX > > > instructions are macros and open-code the equivalent in EV4 instructions > > > unless it is explicitly in EV56 (or greater) mode. > > > > So, in case of -mcpu=21164a gas will generate BWX and if -mcpu=21164a > > is omitted it will open-code in EV4 instructions? > > Yes. (Of course, I'd rather it emitted an error, or a warning, at least...) > > > what if I generate 'netboot' on a Miata with mcpu=m21164a and want to > > use the generated netboot on a Sandpiper (EV4)? There is no kernel (yet) > > to emulate BWX so I lose, right? > > Right, if the compiler/assembler emitted BWX, you lose. This is definitely a nice pitfall. The only obvious way to avoid it (that I see right now) is to have the build environment of the standalone parts of the system set their own cpu-independent flags (read: the least-common denominator cpu). The standalone bits then also include the kernel itself (or can it emulate missing BWX while they are being used inside the kernel? I doubt it.) W/ -- Wilko Bulte Arnhem, The Netherlands - The FreeBSD Project 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 From owner-freebsd-alpha Wed Dec 15 2:26:31 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 5B46E14D60 for ; Wed, 15 Dec 1999 02:26:29 -0800 (PST) (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 KAA50031; Wed, 15 Dec 1999 10:35:56 GMT (envelope-from dfr@nlsystems.com) Date: Wed, 15 Dec 1999 10:35:56 +0000 (GMT) From: Doug Rabson To: Wilko Bulte Cc: Jason Thorpe , FreeBSD-alpha mailing list Subject: Re: use of -mcpu=21164a In-Reply-To: <19991214224728.A36085@yedi.iaf.nl> 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, 14 Dec 1999, Wilko Bulte wrote: > On Tue, Dec 14, 1999 at 01:09:39PM -0800, Jason Thorpe wrote: > > On Tue, 14 Dec 1999 21:39:15 +0100 > > Wilko Bulte wrote: > > > > > Will adding -mcpu=21164a to CFLAGS in /etc/make.conf > > > result in code not running on EV4/21064 CPUs? > > > > The Alpha Architecture specifies that user programs can expect the kernel > > to emulate BWX, so it should work, albeit a bit more slowly in the event > > that BWX is actually used. > > OK. We don't yet emulate the BWX instructions for 21064 (although we should). -- 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 Dec 15 2:27:30 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 B5B2B15244 for ; Wed, 15 Dec 1999 02:27:27 -0800 (PST) (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 KAA50344; Wed, 15 Dec 1999 10:37:03 GMT (envelope-from dfr@nlsystems.com) Date: Wed, 15 Dec 1999 10:37:03 +0000 (GMT) From: Doug Rabson To: Wilko Bulte Cc: FreeBSD-alpha mailing list Subject: Re: netboot on alpha In-Reply-To: <19991214215644.A35183@yedi.iaf.nl> 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, 14 Dec 1999, Wilko Bulte wrote: > Has anybody recently tested the netboot functionality of FreeBSD/alpha? > > Reason for asking is that an older netboot exec seems to work: > > FreeBSD/alpha SRM net boot, Revision 0.1 > (root@alpine.iaf.nl, Tue Oct 19 18:47:13 CEST 1999) > Memory: 98304 k > > but the one in -current does not appear to. I haven't tested it for a couple of months. -- 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 Dec 15 6:54:36 1999 Delivered-To: freebsd-alpha@freebsd.org Received: from comet.connix.com (comet.connix.com [198.69.10.4]) by hub.freebsd.org (Postfix) with ESMTP id 5D55615124 for ; Wed, 15 Dec 1999 06:54:32 -0800 (PST) (envelope-from booga@comet.connix.com) Received: from localhost (booga@localhost) by comet.connix.com (8.9.3/8.9.3) with ESMTP id JAA04097 for ; Wed, 15 Dec 1999 09:54:30 -0500 (EST) Date: Wed, 15 Dec 1999 09:54:28 -0500 (EST) From: Shawn Kelly O Shea Reply-To: sko@eth0.net To: FreeBSD-alpha mailing list Subject: Re: netboot on alpha 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 Last time I played with this code, I was having the "old firmware doesnt send the enet addr so you need to hard code it into the boot image or upgrade your firmware" problem. (AStation200 4/100). Unfortunately after flashing the firmware from ARC, arc was ok, but upon switching to SRM, SRM just spews out all kinds of hex dumps and the machine reboots. I've since heard about the jumper that is supposed to let you boot off of floppy, but i'm not sure what jumper it is on this box (AServer300 is J2, but I tried this on the 200 and it never talks to the floppy drive I added) Anyhoo, if somebody has any ideas on how I can fix my 200, I'd be more than happy to try and netboot the thing =) -Shawn On Wed, 15 Dec 1999, Doug Rabson wrote: > On Tue, 14 Dec 1999, Wilko Bulte wrote: > > > Has anybody recently tested the netboot functionality of FreeBSD/alpha? > > > > Reason for asking is that an older netboot exec seems to work: > > > > FreeBSD/alpha SRM net boot, Revision 0.1 > > (root@alpine.iaf.nl, Tue Oct 19 18:47:13 CEST 1999) > > Memory: 98304 k > > > > but the one in -current does not appear to. > > I haven't tested it for a couple of months. > > -- > 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 > -------------------------------------------------------------- # ifconfig eth0.net "Shawn O'Shea" netmask 255.255.255.0 up # route add -net smtp shawn@eth0.net # route add -net http http://eth0.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Wed Dec 15 10:53: 1 1999 Delivered-To: freebsd-alpha@freebsd.org Received: from mail.scc.nl (node1374.a2000.nl [62.108.19.116]) by hub.freebsd.org (Postfix) with ESMTP id D2B4F153DD for ; Wed, 15 Dec 1999 10:52:56 -0800 (PST) (envelope-from freebsd-alpha@scc.nl) Received: (from daemon@localhost) by mail.scc.nl (8.9.3/8.9.3) id TAA43715 for alpha@FreeBSD.org; Wed, 15 Dec 1999 19:27:25 +0100 (CET) (envelope-from freebsd-alpha@scc.nl) Received: from GATEWAY by dwarf.hq.scc.nl with netnews for alpha@FreeBSD.org (alpha@FreeBSD.org) To: alpha@FreeBSD.org Date: Wed, 15 Dec 1999 19:27:22 +0100 From: Marcel Moolenaar Message-ID: <3857DD8A.FA67F18A@scc.nl> Organization: SCC vof Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Subject: What is special about /sys/boot/common/gensetdefs.c Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi, Why is the boot code using a special version of gensetdefs.c? Is there something special about it that /usr/bin/gensetdefs can't be used? I have the appropriate patches so that /usr/bin/gensetdefs is used, which enables us to cross-built the boot code. I just want to make sure I'm not overlooking something. -- Marcel Moolenaar mailto:marcel@scc.nl SCC Internetworking & Databases http://www.scc.nl/ The FreeBSD project mailto:marcel@FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Wed Dec 15 11:20:40 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 05DB614C09 for ; Wed, 15 Dec 1999 11:20:32 -0800 (PST) (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 TAA26087; Wed, 15 Dec 1999 19:20:11 +0100 (MET) Received: (from wilko@localhost) by yedi.iaf.nl (8.9.3/8.9.3) id UAA01302; Wed, 15 Dec 1999 20:08:53 +0100 (CET) (envelope-from wilko) Date: Wed, 15 Dec 1999 20:08:53 +0100 From: Wilko Bulte To: Doug Rabson Cc: FreeBSD-alpha mailing list Subject: Re: netboot on alpha Message-ID: <19991215200853.I447@yedi.iaf.nl> References: <19991214215644.A35183@yedi.iaf.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: ; from dfr@nlsystems.com on Wed, Dec 15, 1999 at 10:37:03AM +0000 X-OS: FreeBSD yedi.iaf.nl 3.3-STABLE FreeBSD 3.3-STABLE X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Wed, Dec 15, 1999 at 10:37:03AM +0000, Doug Rabson wrote: > On Tue, 14 Dec 1999, Wilko Bulte wrote: > > > Has anybody recently tested the netboot functionality of FreeBSD/alpha? > > > > Reason for asking is that an older netboot exec seems to work: > > > > FreeBSD/alpha SRM net boot, Revision 0.1 > > (root@alpine.iaf.nl, Tue Oct 19 18:47:13 CEST 1999) > > Memory: 98304 k > > > > but the one in -current does not appear to. > > I haven't tested it for a couple of months. Any chance you could give it a quick try? -- Wilko Bulte Arnhem, The Netherlands - The FreeBSD Project 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 From owner-freebsd-alpha Wed Dec 15 13:36: 3 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 A1D3B155FF for ; Wed, 15 Dec 1999 13:35:58 -0800 (PST) (envelope-from rharris@nimbus.skycache.com) Received: from localhost (rharris@localhost) by nimbus.skycache.com (8.9.3/8.9.3) with SMTP id QAA05717 for ; Wed, 15 Dec 1999 16:35:57 -0500 (EST) Date: Wed, 15 Dec 1999 16:35:57 -0500 (EST) From: Rob Harris To: freebsd-alpha@freebsd.org Subject: snmp 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 Has anyone been able to get ANY snmp daemons running under 4.0 snap? I REALLY dont want to have to try to hand hack it, but I need it BAD for a production system I'm using. Thx. --Rob ____________________________________________________________________________ Rob Harris 8037 Laurel Lakes Blvd. ph: 301.598.0500 SkyCache, Inc. Laurel, MD x2236 rharris@skycache.com rharris-page@skycache.com 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 Dec 15 14: 5:29 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 705BA155D4 for ; Wed, 15 Dec 1999 14:05:22 -0800 (PST) (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 WAA02520; Wed, 15 Dec 1999 22:05:42 +0100 (MET) Received: (from wilko@localhost) by yedi.iaf.nl (8.9.3/8.9.3) id WAA03887; Wed, 15 Dec 1999 22:48:45 +0100 (CET) (envelope-from wilko) Date: Wed, 15 Dec 1999 22:48:45 +0100 From: Wilko Bulte To: Doug Rabson Cc: FreeBSD-alpha mailing list Subject: Re: netboot on alpha Message-ID: <19991215224845.B3729@yedi.iaf.nl> References: <19991214215644.A35183@yedi.iaf.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: ; from dfr@nlsystems.com on Wed, Dec 15, 1999 at 10:37:03AM +0000 X-OS: FreeBSD yedi.iaf.nl 3.3-STABLE FreeBSD 3.3-STABLE X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Wed, Dec 15, 1999 at 10:37:03AM +0000, Doug Rabson wrote: > On Tue, 14 Dec 1999, Wilko Bulte wrote: > > > Has anybody recently tested the netboot functionality of FreeBSD/alpha? > > > > Reason for asking is that an older netboot exec seems to work: > > > > FreeBSD/alpha SRM net boot, Revision 0.1 > > (root@alpine.iaf.nl, Tue Oct 19 18:47:13 CEST 1999) > > Memory: 98304 k > > > > but the one in -current does not appear to. > > I haven't tested it for a couple of months. I did a bit more experimenting: using a freshly built 'netboot' out of the 'old' sources gives me: >>> boot ez0 -fi "kernel" INIT-S-CPU... AUDIT_BOOT_STARTS ... AUDIT_BOOT_REQ kernel Host server IP address is 192.168.200.22 AUDIT_BSERVER_FOUND AUDIT_LOAD_BEGINS AUDIT_LOAD_DONE ?02 KSP INVAL PC= 00000000.00000000 PSL= 00000000.00001F00 >>> ----- The older netboot excutable (built in october) gives: >>> boot ez0 -fi "kernel" INIT-S-CPU... AUDIT_BOOT_STARTS ... AUDIT_BOOT_REQ kernel Host server IP address is 192.168.200.22 AUDIT_BSERVER_FOUND AUDIT_LOAD_BEGINS AUDIT_LOAD_DONE Console: SRM firmware console VMS PAL rev: 0x100010538 OSF PAL rev: 0x2012d Switch to OSF PAL code succeeded. FreeBSD/alpha SRM net boot, Revision 0.1 (root@alpine.iaf.nl, Tue Oct 19 18:47:13 CEST 1999) Memory: 98304 k boot: ethernet address: 08:00:2b:3c:61:45 net_open: server addr: 192.168.200.22 net_open: server path: /usr/sandpiper boot: ethernet address: 08:00:2b:3c:61:45 net_open: server addr: 192.168.200.22 net_open: server path: /usr/sandpiper boot: ethernet address: 08:00:2b:3c:61:45 net_open: server addr: 192.168.200.22 net_open: server path: /usr/sandpiper Hit [Enter] to boot immediately, or any other key for command prompt. Booting [kernel] in 5 seconds... Type '?' for a list of commands, 'help' for more detailed help. net0:> net0:> [etc] In looking at the cvs logs I don't see a reason why it should have stopped working. Far fetched: the change in compiler? W/ -- Wilko Bulte Arnhem, The Netherlands - The FreeBSD Project 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 From owner-freebsd-alpha Wed Dec 15 14:24:42 1999 Delivered-To: freebsd-alpha@freebsd.org Received: from mass.cdrom.com (mass.cdrom.com [204.216.28.184]) by hub.freebsd.org (Postfix) with ESMTP id BD45814EE3 for ; Wed, 15 Dec 1999 14:24:40 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id OAA01526; Wed, 15 Dec 1999 14:27:19 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <199912152227.OAA01526@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Marcel Moolenaar Cc: alpha@FreeBSD.org Subject: Re: What is special about /sys/boot/common/gensetdefs.c In-reply-to: Your message of "Wed, 15 Dec 1999 19:27:22 +0100." <3857DD8A.FA67F18A@scc.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 15 Dec 1999 14:27:19 -0800 From: Mike Smith Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org The i386 loader, at least, uses a completely different technique for generating linker sets from the kernel. I'm not sure that it's applicable to the kernel/KLDs, but it doesn't require the gensetdefs crap at all. The alpha code should probably be using it as well. > Why is the boot code using a special version of gensetdefs.c? > Is there something special about it that /usr/bin/gensetdefs can't be > used? > > I have the appropriate patches so that /usr/bin/gensetdefs is used, > which enables us to cross-built the boot code. I just want to make sure > I'm not overlooking something. > > -- > Marcel Moolenaar mailto:marcel@scc.nl > SCC Internetworking & Databases http://www.scc.nl/ > The FreeBSD project mailto:marcel@FreeBSD.org > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-alpha" in the body of the message > -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Wed Dec 15 14:56:32 1999 Delivered-To: freebsd-alpha@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 608) id C228114E7F; Wed, 15 Dec 1999 14:56:31 -0800 (PST) From: "Jonathan M. Bresler" To: rharris@skycache.com Cc: freebsd-alpha@freebsd.org In-reply-to: (message from Rob Harris on Wed, 15 Dec 1999 16:35:57 -0500 (EST)) Subject: Re: snmp Message-Id: <19991215225631.C228114E7F@hub.freebsd.org> Date: Wed, 15 Dec 1999 14:56:31 -0800 (PST) Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > Has anyone been able to get ANY snmp daemons running under 4.0 snap? I > REALLY dont want to have to try to hand hack it, but I need it BAD for a > production system I'm using. yes, i have patches to get some of the HOST_RESOURCES mib added back to ucdavis' snmpd from the ports tree. i'll send them to you. you can reach me at 410-320-7108. we are physically close to each other as well. i live in silver spring md (i-495 and rt 29) and work in annapolis. jmb To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Wed Dec 15 15:25:59 1999 Delivered-To: freebsd-alpha@freebsd.org Received: from lh2.rdc1.sdca.home.com (ha2.rdc1.sdca.home.com [24.0.3.67]) by hub.freebsd.org (Postfix) with ESMTP id 2CD1A155B7 for ; Wed, 15 Dec 1999 15:25:57 -0800 (PST) (envelope-from craig-burgess@home.com) Received: from home.com ([24.0.178.21]) by lh2.rdc1.sdca.home.com (InterMail v4.01.01.00 201-229-111) with ESMTP id <19991215232556.VRZD1336.lh2.rdc1.sdca.home.com@home.com> for ; Wed, 15 Dec 1999 15:25:56 -0800 Message-ID: <385823A0.FD07A212@home.com> Date: Wed, 15 Dec 1999 15:26:24 -0800 From: Craig Burgess X-Mailer: Mozilla 4.7 [en] (WinNT; U) X-Accept-Language: en MIME-Version: 1.0 To: FreeBSD-alpha mailing list Subject: ports path query Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org The database and language applications which I would like to install are not yet ported or are dependant on other things which haven't yet been ported to Alpha. Nowhere have I found Alpha-specific information regarding ports. Is there ports information somewhere? Craig Burgess To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Wed Dec 15 17:54:35 1999 Delivered-To: freebsd-alpha@freebsd.org Received: from mass.cdrom.com (mass.cdrom.com [204.216.28.184]) by hub.freebsd.org (Postfix) with ESMTP id E62E614A10 for ; Wed, 15 Dec 1999 17:54:30 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id RAA04577; Wed, 15 Dec 1999 17:57:45 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <199912160157.RAA04577@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: alpha@freebsd.org Cc: port-alpha@netbsd.org Subject: Alpha Processor Inc. UP2000 system Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 15 Dec 1999 17:57:45 -0800 From: Mike Smith Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Just to clarify from the earlier discussion; the UP2000 system that Alpha Processor Inc just delivered to FreeBSD Labs is indeed a DP264. It runs FreeBSD just fine (on one CPU only, obviously), and should run NetBSD just as well. My apologies for any inadvertent confusion caused. -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Thu Dec 16 2:23:47 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 A5390155C9 for ; Thu, 16 Dec 1999 02:23:44 -0800 (PST) (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 KAA83185; Thu, 16 Dec 1999 10:33:34 GMT (envelope-from dfr@nlsystems.com) Date: Thu, 16 Dec 1999 10:33:34 +0000 (GMT) From: Doug Rabson To: Wilko Bulte Cc: FreeBSD-alpha mailing list Subject: Re: netboot on alpha In-Reply-To: <19991215200853.I447@yedi.iaf.nl> 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, 15 Dec 1999, Wilko Bulte wrote: > On Wed, Dec 15, 1999 at 10:37:03AM +0000, Doug Rabson wrote: > > On Tue, 14 Dec 1999, Wilko Bulte wrote: > > > > > Has anybody recently tested the netboot functionality of FreeBSD/alpha? > > > > > > Reason for asking is that an older netboot exec seems to work: > > > > > > FreeBSD/alpha SRM net boot, Revision 0.1 > > > (root@alpine.iaf.nl, Tue Oct 19 18:47:13 CEST 1999) > > > Memory: 98304 k > > > > > > but the one in -current does not appear to. > > > > I haven't tested it for a couple of months. > > Any chance you could give it a quick try? I'll give it a try but it might not be until the weekend. -- 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 Dec 16 2:30: 0 1999 Delivered-To: freebsd-alpha@freebsd.org Received: from post.mail.nl.demon.net (post-11.mail.nl.demon.net [194.159.73.21]) by hub.freebsd.org (Postfix) with ESMTP id 439E6155CE; Thu, 16 Dec 1999 02:29:58 -0800 (PST) (envelope-from marcel@scc.nl) Received: from [212.238.132.94] (helo=scones.sup.scc.nl) by post.mail.nl.demon.net with esmtp (Exim 2.12 #1) id 11yYAA-000B4R-00; Thu, 16 Dec 1999 10:29:34 +0000 Received: from scc.nl (scones.sup.scc.nl [192.168.2.4]) by scones.sup.scc.nl (8.9.3/8.9.3) with ESMTP id LAA61658; Thu, 16 Dec 1999 11:29:54 +0100 (CET) (envelope-from marcel@scc.nl) Message-ID: <3858BF22.AD6A5B65@scc.nl> Date: Thu, 16 Dec 1999 11:29:54 +0100 From: Marcel Moolenaar Organization: SCC vof X-Mailer: Mozilla 4.7 [en] (X11; I; Linux 2.2.5 i386) X-Accept-Language: en MIME-Version: 1.0 To: Mike Smith Cc: alpha@FreeBSD.org Subject: Re: What is special about /sys/boot/common/gensetdefs.c References: <199912152227.OAA01526@mass.cdrom.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Mike Smith wrote: > > The i386 loader, at least, uses a completely different technique for > generating linker sets from the kernel. I'm not sure that it's > applicable to the kernel/KLDs, but it doesn't require the gensetdefs crap > at all. The alpha code should probably be using it as well. Either that or /usr/bin/gensetdefs. I go with /usr/bin/gensetdefs, because that leads me to cross-building much faster. I already cross-built Alpha on i386 at home (no kernel), so it's basicly just a matter of reviewing and committing... -- Marcel Moolenaar mailto:marcel@scc.nl SCC Internetworking & Databases http://www.scc.nl/ The FreeBSD project mailto:marcel@FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Thu Dec 16 4:56:53 1999 Delivered-To: freebsd-alpha@freebsd.org Received: from mail.scc.nl (node1374.a2000.nl [62.108.19.116]) by hub.freebsd.org (Postfix) with ESMTP id AE6AA150B0 for ; Thu, 16 Dec 1999 04:56:49 -0800 (PST) (envelope-from freebsd-alpha@scc.nl) Received: (from daemon@localhost) by mail.scc.nl (8.9.3/8.9.3) id NAA07220 for alpha@FreeBSD.org; Thu, 16 Dec 1999 13:30:51 +0100 (CET) (envelope-from freebsd-alpha@scc.nl) Received: from GATEWAY by dwarf.hq.scc.nl with netnews for alpha@FreeBSD.org (alpha@FreeBSD.org) To: alpha@FreeBSD.org Date: Thu, 16 Dec 1999 13:30:42 +0100 From: Marcel Moolenaar Message-ID: <3858DB72.14B2E766@scc.nl> Organization: SCC vof Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Subject: pcvt and libkeycap on Alpha Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi, On Alpha, src/usr.sbin/pcvt is not built but src/usr.sbin/pcvt/keycap is! src/usr.bin/pcvt/keycap is built by the 'libraries' target in src/Makefile.inc1. But since src/usr.sbin/pcvt is itself not built, not object directory is created. This means that src/usr.sbin/pcvt/keycap is always built in the source tree. The question (at last :-): Should src/usr.sbin/pcvt be enabled or should we exclude src/usr.sbin/pcvt/keycap from the libraries target on Alpha? -- Marcel Moolenaar mailto:marcel@scc.nl SCC Internetworking & Databases http://www.scc.nl/ The FreeBSD project mailto:marcel@FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Sun Dec 19 9:42: 8 1999 Delivered-To: freebsd-alpha@freebsd.org Received: from m2.dj.net.tw (m2.dj.net.tw [203.135.250.50]) by hub.freebsd.org (Postfix) with SMTP id EF76E14C43 for ; Sun, 19 Dec 1999 09:41:53 -0800 (PST) (envelope-from maiowoo@m2.dj.net.tw) Received: from [203.135.240.3] by m2.dj.net.tw (NTMail 3.03.0018/1.aewb) with ESMTP id ea302488 for ; Mon, 20 Dec 1999 01:41:39 +0800 From: maiowoo@m2.dj.net.tw (MaioWoo(Âù³½¿ß)) To: freebsd-alpha@FreeBSD.org Subject: Date: Mon, 20 Dec 1999 01:43:01 +0800 Message-ID: <385f1922.10218343@m2.dj.net.tw> X-Mailer: Forte Agent 1.5/32.452 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 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Sun Dec 19 15: 2:20 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 DD42E14F53 for ; Sun, 19 Dec 1999 15:02:18 -0800 (PST) (envelope-from mjacob@feral.com) Received: from semuta.feral.com (semuta [192.67.166.70]) by feral.com (8.9.3/8.9.3) with ESMTP id PAA09931; Sun, 19 Dec 1999 15:04:11 -0800 Date: Sun, 19 Dec 1999 15:04:11 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: freebsd-alpha@freebsd.org Cc: Andrew Gallatin Subject: kern/9018: Qlogic ISP driver no longer works on AlphaServer 8200 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 interested, take a moment to look at this NetBSD PR- this applies to Alphas too, and may in fact have been (at one time) a major factor for Drew's problems. -matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Sun Dec 19 23:20:13 1999 Delivered-To: freebsd-alpha@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id 8337414C18; Sun, 19 Dec 1999 23:20:11 -0800 (PST) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.3/8.9.3) with ESMTP id XAA04644; Sun, 19 Dec 1999 23:20:09 -0800 (PST) (envelope-from jdp@polstra.com) From: John Polstra Received: (from jdp@localhost) by vashon.polstra.com (8.9.3/8.9.1) id XAA31056; Sun, 19 Dec 1999 23:20:09 -0800 (PST) (envelope-from jdp@polstra.com) Date: Sun, 19 Dec 1999 23:20:09 -0800 (PST) Message-Id: <199912200720.XAA31056@vashon.polstra.com> To: msmith@freebsd.org Subject: Re: Alpha multiboot: is it possible? In-Reply-To: <199912130324.TAA04953@mass.cdrom.com> References: <199912130324.TAA04953@mass.cdrom.com> Organization: Polstra & Co., Seattle, WA Cc: alpha@freebsd.org Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In article <199912130324.TAA04953@mass.cdrom.com>, Mike Smith wrote: > I don't think -stable on the alpha will work with / anywhere but on da0a. > > You might try swapping the two systems around, since -current _should_ > work properly like that. That seems to work. Thanks. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "No matter how cynical I get, I just can't keep up." -- Nora Ephron To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Mon Dec 20 23:12:40 1999 Delivered-To: freebsd-alpha@freebsd.org Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id 833FD14D0B for ; Mon, 20 Dec 1999 23:12:35 -0800 (PST) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (root@d60-025.leach.ucdavis.edu [169.237.60.25]) by relay.nuxi.com (8.9.3/8.9.3) with ESMTP id XAA72707 for ; Mon, 20 Dec 1999 23:12:35 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.9.3/8.9.1) id XAA37907 for freebsd-alpha@freebsd.org; Mon, 20 Dec 1999 23:12:35 -0800 (PST) (envelope-from obrien) Date: Mon, 20 Dec 1999 23:12:34 -0800 From: "David O'Brien" To: freebsd-alpha@freebsd.org Subject: Tekram SCSI controlers supported by SRM? Message-ID: <19991220231234.A37893@dragon.nuxi.com> Reply-To: obrien@NUXI.com Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i X-Operating-System: FreeBSD 4.0-CURRENT Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Does anybody have any experience using a Tekram DC-390U2W (LVD) or DC-390U2B (Ultra-wide) on a SRM based Alpha? PC164SX specifically. -- -- David (obrien@NUXI.com) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Mon Dec 20 23:25:40 1999 Delivered-To: freebsd-alpha@freebsd.org Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id EF17B14BE3 for ; Mon, 20 Dec 1999 23:25:38 -0800 (PST) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (root@d60-025.leach.ucdavis.edu [169.237.60.25]) by relay.nuxi.com (8.9.3/8.9.3) with ESMTP id XAA72765 for ; Mon, 20 Dec 1999 23:25:38 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.9.3/8.9.1) id XAA37963 for freebsd-alpha@freebsd.org; Mon, 20 Dec 1999 23:25:38 -0800 (PST) (envelope-from obrien) Date: Mon, 20 Dec 1999 23:25:38 -0800 From: "David O'Brien" To: freebsd-alpha@freebsd.org Subject: Re: Tekram SCSI controlers supported by SRM? Message-ID: <19991220232538.O28348@dragon.nuxi.com> Reply-To: obrien@NUXI.com References: <19991220231234.A37893@dragon.nuxi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <19991220231234.A37893@dragon.nuxi.com>; from obrien@NUXI.com on Mon, Dec 20, 1999 at 11:12:34PM -0800 X-Operating-System: FreeBSD 4.0-CURRENT Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > Does anybody have any experience using a Tekram DC-390U2W (LVD) or > DC-390U2B (Ultra-wide) on a SRM based Alpha? PC164SX specifically. Please add the DC-390F to the inquiry list. -- -- David (obrien@NUXI.com) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Thu Dec 23 13: 9:19 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 36B1A14E41 for ; Thu, 23 Dec 1999 13:09:10 -0800 (PST) (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 VAA10691 for freebsd-alpha@freebsd.org; Thu, 23 Dec 1999 21:13:14 +0100 (MET) Received: (from wilko@localhost) by yedi.iaf.nl (8.9.3/8.9.3) id WAA11560 for freebsd-alpha@freebsd.org; Thu, 23 Dec 1999 22:04:32 +0100 (CET) (envelope-from wilko) Date: Thu, 23 Dec 1999 22:04:32 +0100 From: Wilko Bulte To: FreeBSD-alpha mailing list Subject: diskless boot on Alpha Message-ID: <19991223220432.A11438@yedi.iaf.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i X-OS: FreeBSD yedi.iaf.nl 3.4-STABLE FreeBSD 3.4-STABLE X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I'm probably overlooking something too obvious. As can be seen below the Alpha (DEC3000/400 Sandpiper) tries to mount its root device using ufs. Does not work too well with an nfs root. Previously there was a 'root on clause in the kernel config file. But this is depreciated (right?). Question remains: how do I convince the kernel to use the nfs root? Wilko The kernel config file says: # SANDpiper machine alpha cpu EV4 ident SAND maxusers 32 #makeoptions DEBUG=-g #Build kernel with gdb(1) debug symbols # Platforms supported options DEC_3000_500 # DEC3000/[4-9]00 Flamingo/Sandpiper fa mily options INET #InterNETworking # options NFS #Network Filesystem options NFS_ROOT #NFS usable as root device options BOOTP # Use BOOTP to obtain IP address/hostname options BOOTP_NFSROOT # NFS mount root filesystem using BOOTP info options BOOTP_COMPAT # Workaround for broken bootp daemons. options BOOTP_WIRED_TO=le0 # Use interface le0 for BOOTP # options CD9660 #ISO 9660 Filesystem options PROCFS #Process filesystem options COMPAT_43 #Compatible with BSD 4.3 [KEEP THIS!] options SCSI_DELAY=5000 #Be pessimistic about Joe SCSI device # SCSI Controllers # A single entry for any of these controllers (ahb, ahc, amd, ncr, etc...) is # sufficient for any number of installed devices. #controller esp0 # SCSI peripherals # Only one of each of these is needed, they are dynamically allocated. #controller scbus0 # SCSI bus (required) #device da0 # Direct Access (disks) #device sa0 # Sequential Access (tape etc) #device cd0 # CD #device pass0 # Passthrough device (direct SCSI access) # real time clock device mcclock0 # Ethernet device le0 # Lance # Pseudo devices - the number indicates how many units to allocated. pseudo-device loop # Network loopback pseudo-device ether # Ethernet support pseudo-device pty # Pseudo-ttys (telnet etc) === Try unionizing the nu_nickname and nu_flag fields Timecounter "alpha" frequency 133000000 Hz le0 XXX: driver didn't set ifq_maxlen Mounting root from ufs:192.168.200.22:/usr/sandpiper Can't allocate root mount for filesystem 'ufs': 19 Root mount failed: 19 Manual root filesystem specification: : Mount using filesystem eg. ufs:/dev/da0s1a ? List valid disk boot devices Abort manual input >>> -- Wilko Bulte Arnhem, The Netherlands - The FreeBSD Project 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 From owner-freebsd-alpha Thu Dec 23 18: 7: 6 1999 Delivered-To: freebsd-alpha@freebsd.org Received: from mass.cdrom.com (mass.cdrom.com [204.216.28.184]) by hub.freebsd.org (Postfix) with ESMTP id 517F714E9C for ; Thu, 23 Dec 1999 18:07:02 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id SAA06908; Thu, 23 Dec 1999 18:10:56 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <199912240210.SAA06908@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Wilko Bulte Cc: FreeBSD-alpha mailing list Subject: Re: diskless boot on Alpha In-reply-to: Your message of "Thu, 23 Dec 1999 22:04:32 +0100." <19991223220432.A11438@yedi.iaf.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 23 Dec 1999 18:10:56 -0800 From: Mike Smith Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > I'm probably overlooking something too obvious. As can be seen > below the Alpha (DEC3000/400 Sandpiper) tries to mount its root > device using ufs. Does not work too well with an nfs root. > > Previously there was a 'root on clause in the kernel config file. > But this is depreciated (right?). > > Question remains: how do I convince the kernel to use the nfs root? Are you booting the loader, or the kernel directly? Try booting with '-a' and specify nfs:... I'd be guessing that the code in the alpha autoconf isn't correctly picking up that / is meant to be nfs-mounted. 8( > Wilko > > > The kernel config file says: > > # SANDpiper > > machine alpha > cpu EV4 > ident SAND > maxusers 32 > > #makeoptions DEBUG=-g #Build kernel with gdb(1) debug > symbols > > # Platforms supported > options DEC_3000_500 # DEC3000/[4-9]00 Flamingo/Sandpiper > fa > mily > > options INET #InterNETworking > # > options NFS #Network Filesystem > options NFS_ROOT #NFS usable as root device > options BOOTP # Use BOOTP to obtain IP address/hostname > options BOOTP_NFSROOT # NFS mount root filesystem using BOOTP info > options BOOTP_COMPAT # Workaround for broken bootp daemons. > options BOOTP_WIRED_TO=le0 # Use interface le0 for BOOTP > > # > options CD9660 #ISO 9660 Filesystem > options PROCFS #Process filesystem > options COMPAT_43 #Compatible with BSD 4.3 [KEEP > THIS!] > options SCSI_DELAY=5000 #Be pessimistic about Joe SCSI device > > # SCSI Controllers > # A single entry for any of these controllers (ahb, ahc, amd, ncr, etc...) > is > # sufficient for any number of installed devices. > #controller esp0 > > # SCSI peripherals > # Only one of each of these is needed, they are dynamically allocated. > #controller scbus0 # SCSI bus (required) > #device da0 # Direct Access (disks) > #device sa0 # Sequential Access (tape etc) > #device cd0 # CD > #device pass0 # Passthrough device (direct SCSI access) > > # real time clock > device mcclock0 > > # Ethernet > device le0 # Lance > > # Pseudo devices - the number indicates how many units to allocated. > pseudo-device loop # Network loopback > pseudo-device ether # Ethernet support > pseudo-device pty # Pseudo-ttys (telnet etc) > > === > > Try unionizing the nu_nickname and nu_flag fields > Timecounter "alpha" frequency 133000000 Hz > le0 XXX: driver didn't set ifq_maxlen > Mounting root from ufs:192.168.200.22:/usr/sandpiper > Can't allocate root mount for filesystem 'ufs': 19 > Root mount failed: 19 > > Manual root filesystem specification: > : Mount using filesystem > eg. ufs:/dev/da0s1a > ? List valid disk boot devices > Abort manual input > > >>> > > > > -- > Wilko Bulte Arnhem, The Netherlands - The FreeBSD Project > 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 > -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Fri Dec 24 8:47:58 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 B7A3E14F15; Fri, 24 Dec 1999 08:47:53 -0800 (PST) (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 RAA32047; Fri, 24 Dec 1999 17:44:10 +0100 (MET) Received: (from wilko@localhost) by yedi.iaf.nl (8.9.3/8.9.3) id RAA63622; Fri, 24 Dec 1999 17:47:08 +0100 (CET) (envelope-from wilko) Date: Fri, 24 Dec 1999 17:47:08 +0100 From: Wilko Bulte To: Mike Smith Cc: FreeBSD-alpha mailing list Subject: Re: diskless boot on Alpha Message-ID: <19991224174708.A63398@yedi.iaf.nl> References: <19991223220432.A11438@yedi.iaf.nl> <199912240210.SAA06908@mass.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <199912240210.SAA06908@mass.cdrom.com>; from msmith@freebsd.org on Thu, Dec 23, 1999 at 06:10:56PM -0800 X-OS: FreeBSD yedi.iaf.nl 3.4-STABLE FreeBSD 3.4-STABLE X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Thu, Dec 23, 1999 at 06:10:56PM -0800, Mike Smith wrote: Hello Mike, I appreciate your help in this. Be warned: long mail follows.. > > I'm probably overlooking something too obvious. As can be seen > > below the Alpha (DEC3000/400 Sandpiper) tries to mount its root > > device using ufs. Does not work too well with an nfs root. > > > > Previously there was a 'root on clause in the kernel config file. > > But this is depreciated (right?). > > > > Question remains: how do I convince the kernel to use the nfs root? > > Are you booting the loader, or the kernel directly? I'm doing: >>> boot ez0 INIT-S-CPU... AUDIT_BOOT_STARTS ... AUDIT_BOOT_REQ Host server IP address is 192.168.200.22 AUDIT_BSERVER_FOUND AUDIT_LOAD_BEGINS AUDIT_LOAD_DONE Console: SRM firmware console VMS PAL rev: 0x100010538 OSF PAL rev: 0x2012d Switch to OSF PAL code succeeded. FreeBSD/alpha SRM net boot, Revision 0.1 (root@miata.iaf.nl, Tue Dec 21 18:31:30 CET 1999) Memory: 98304 k boot: ethernet address: 08:00:2b:3c:61:45 net_open: server addr: 192.168.200.22 net_open: server path: /usr/sandpiper Hit [Enter] to boot immediately, or any other key for command prompt. Booting [kernel]... /kernel data=0x189908+0x1b168 syms=[0x8+0x237c0+0x8+0x1a681] Entering kernel at 0xfffffc000031f760... > Try booting with '-a' and specify nfs:... > I'd be guessing that the code in the alpha autoconf isn't correctly > picking up that / is meant to be nfs-mounted. 8( The relevant code (I think) is: * Do legacy root filesystem discovery. This isn't really * needed on the Alpha, which has always used the loader. */ void cpu_rootconf() { int order = 0; printf(">>## in cpu_rootconf\n"); /* #if defined(NFS) && defined(NFS_ROOT) #if !defined(BOOTP_NFSROOT) if (nfs_diskless_valid) #endif */ rootdevnames[order++] = "nfs:"; printf (">>## nfsroot before ufs\n"); /* #endif */ #if defined(FFS) && defined(FFS_ROOT) rootdevnames[order++] = "ufs:da0a"; #endif } SYSINIT(cpu_rootconf, SI_SUB_ROOT_CONF, SI_ORDER_FIRST, cpu_rootconf, NULL) from autoconf.c (the printfs etc are mine) First interesting observation is that 'options NFS' and 'options NFS_ROOT' in the kernel config file do not result in the nfs bit being compiled in: (using original autoconf.c): miata#make cc -c -O -pipe -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi -nostdinc -I- -I. -I../.. -I../../../include -DKERNEL -include opt_global.h -D_KERNEL -mno-fp-regs -Wa,-mev56 ../../alpha/alpha/autoconf.c ../../alpha/alpha/autoconf.c: In function `cpu_rootconf': ../../alpha/alpha/autoconf.c:214: warning: unused variable `order' In other words, the compiler only sees the declaration of 'order' and no code that uses it. I admit not to understand why this is the case. My theory right now is that the compile of autoconf.c should include opt_nfs.h in addition to opt_nfsroot.h. The latter is already present. I base this on: miata#grep NFS * config.c:___options NFS #Network Filesystem\n\ config.c:___options NFS_ROOT #NFS usable as root device\n\ Binary file kernel matches kernfs.h:#define NKERNFS 0 Binary file nfs_bio.o matches Binary file nfs_node.o matches Binary file nfs_nqlease.o matches Binary file nfs_socket.o matches Binary file nfs_srvcache.o matches Binary file nfs_subs.o matches Binary file nfs_syscalls.o matches Binary file nfs_vfsops.o matches Binary file nfs_vnops.o matches opt_nfs.h:#define NFS 1 opt_nfsroot.h:#define NFS_ROOT 1 Binary file ufs_vnops.o matches miata#pwd /sys/compile/SAND miata# When I add opt_nfs.h to the include files in autoconf.c thing compile like expected. Can somebody please verify this for me? When I boot a kernel built with the above patch I get: >>## nfsroot before ufs Mounting root from ufs:192.168.200.22:/usr/sandpiper Can't allocate root mount for filesystem 'ufs': 19 Root mount failed: 19 Manual root filesystem specification: : Mount using filesystem eg. ufs:/dev/da0s1a ? List valid disk boot devices Abort manual input Which I don't understand because vfs_mountroot() should try nfs before ufs because that is the order in which cpu_rootconf sets up the rootdevnames ? And in my case the kernel is compiled without FFS and FFS_ROOT so it should only do NFS. I'm puzzled.. NB as the code tells me to use 'loader', how do I set that up on Alpha? I still need to bootp netboot right? Wilko Bulte Arnhem, The Netherlands - The FreeBSD Project 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 From owner-freebsd-alpha Fri Dec 24 10:13:48 1999 Delivered-To: freebsd-alpha@freebsd.org Received: from mta2.rcsntx.swbell.net (mta2.rcsntx.swbell.net [151.164.30.26]) by hub.freebsd.org (Postfix) with ESMTP id CD03914C08; Fri, 24 Dec 1999 10:13:32 -0800 (PST) (envelope-from chris@holly.dyndns.org) Received: from holly.dyndns.org ([216.62.157.60]) by mta2.rcsntx.swbell.net (Sun Internet Mail Server sims.3.5.1999.09.16.21.57.p8) with ESMTP id <0FN900H1CBYBOE@mta2.rcsntx.swbell.net>; Fri, 24 Dec 1999 12:13:24 -0600 (CST) Received: (from chris@localhost) by holly.dyndns.org (8.9.3/8.9.3) id MAA03742; Fri, 24 Dec 1999 12:15:48 -0600 (CST envelope-from chris) X-URL: http://www.FreeBSD.org/~chris/ Date: Fri, 24 Dec 1999 12:15:47 -0600 From: Chris Costello Subject: Alpha "minimum hardware requirements"? To: alpha@FreeBSD.org, doc@FreeBSD.org Reply-To: chris@calldei.com Message-id: <19991224121547.I70195@holly.calldei.com> MIME-version: 1.0 Content-type: text/plain; charset=us-ascii User-Agent: Mutt/0.96.4i Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Since I'm rewriting the FAQ for 3.X, I'd like to include information about Alpha systems. Unfortunately, I can't find anything relating to the minimum requirements of hardware in any documentation. So can anyone point me in the right direction, or explain the 'least possible' system? -- |Chris Costello |EOOPS: We're sorry, our bad `---------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Fri Dec 24 10:23: 8 1999 Delivered-To: freebsd-alpha@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id 8222714EEB for ; Fri, 24 Dec 1999 10:22:56 -0800 (PST) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.3/8.9.3) with ESMTP id KAA03247 for ; Fri, 24 Dec 1999 10:22:49 -0800 (PST) (envelope-from jdp@polstra.com) Received: (from jdp@localhost) by vashon.polstra.com (8.9.3/8.9.1) id KAA71870 for alpha@freebsd.org; Fri, 24 Dec 1999 10:22:48 -0800 (PST) (envelope-from jdp@polstra.com) 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: Fri, 24 Dec 1999 10:22:48 -0800 (PST) Organization: Polstra & Co., Inc. From: John Polstra To: alpha@freebsd.org Subject: Is 3.4-RELEASE for i386 only? Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I have a feeling I may have missed an announcement due to sheer lack of attention. I see that there are no Alpha bits for 3.4-RELEASE on the FTP sites. Are there going to be any, or have we more or less abandoned the Alpha on that branch? John To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Fri Dec 24 10:28:32 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 D340614E1C for ; Fri, 24 Dec 1999 10:28:24 -0800 (PST) (envelope-from don@calis.blacksun.org) Received: by calis.blacksun.org (Postfix, from userid 1000) id A36F374; Fri, 24 Dec 1999 13:31:14 -0500 (EST) Received: from localhost (localhost [127.0.0.1]) by calis.blacksun.org (Postfix) with ESMTP id 954C349E6; Fri, 24 Dec 1999 13:31:14 -0500 (EST) Date: Fri, 24 Dec 1999 13:31:14 -0500 (EST) From: Don To: John Polstra Cc: alpha@freebsd.org Subject: Re: Is 3.4-RELEASE for i386 only? 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 > I have a feeling I may have missed an announcement due to sheer lack > of attention. I see that there are no Alpha bits for 3.4-RELEASE on > the FTP sites. Are there going to be any, or have we more or less > abandoned the Alpha on that branch? I was going to ask the same question. I was pretty sure that Jordan had said the 3.4-RELEASE would be available for the alpha on the FTP site shortly after the i386 release but I am wondering how much later. Oh well, time to search the archives. -don To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Fri Dec 24 10:33:28 1999 Delivered-To: freebsd-alpha@freebsd.org Received: from cara.sonn.com (cara.sonn.com [206.79.239.6]) by hub.freebsd.org (Postfix) with ESMTP id BF56615234 for ; Fri, 24 Dec 1999 10:32:45 -0800 (PST) (envelope-from snoble@cara.sonn.com) Received: (from snoble@localhost) by cara.sonn.com (8.9.3/8.9.3) id KAA08274; Fri, 24 Dec 1999 10:23:06 -0800 (PST) Date: Fri, 24 Dec 1999 10:23:06 -0800 From: Steve Noble To: John Polstra Cc: alpha@FreeBSD.ORG Subject: Re: Is 3.4-RELEASE for i386 only? Message-ID: <19991224102306.U5414@sonn.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95i In-Reply-To: ; from John Polstra on Fri, Dec 24, 1999 at 10:22:48AM -0800 Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I've successfully cvs'd and built 3.4 ... FreeBSD alpha.sonn.com 3.4-STABLE FreeBSD 3.4-STABLE #2: Fri Dec 24 03:19:35 EST 1999 jimmie@alpha.sonn.com:/usr/src/sys/compile/ALPHA alpha Seems to be working fine.. On Fri, Dec 24, 1999 at 10:22:48AM -0800, John Polstra wrote: > I have a feeling I may have missed an announcement due to sheer lack > of attention. I see that there are no Alpha bits for 3.4-RELEASE on > the FTP sites. Are there going to be any, or have we more or less > abandoned the Alpha on that branch? -- ------------------------------------------------------------------------------- : Steven Noble / Network Janitor / Be free my soul and leave this world alone : : My views = My views != The views of any of my past or present employers : ------------------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Fri Dec 24 10:35:42 1999 Delivered-To: freebsd-alpha@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id B6888150AE for ; Fri, 24 Dec 1999 10:35:40 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id KAA16733; Fri, 24 Dec 1999 10:35:36 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) To: John Polstra Cc: alpha@FreeBSD.ORG Subject: Re: Is 3.4-RELEASE for i386 only? In-reply-to: Your message of "Fri, 24 Dec 1999 10:22:48 PST." Date: Fri, 24 Dec 1999 10:35:36 -0800 Message-ID: <16729.946060536@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > I have a feeling I may have missed an announcement due to sheer lack > of attention. I see that there are no Alpha bits for 3.4-RELEASE on > the FTP sites. Are there going to be any, or have we more or less > abandoned the Alpha on that branch? The alpha release got a bit delayed due to some kernel-trimming being necessary just to get the alpha installation bits back onto two floppies again. Now that FreeBSD 3.4/i386 is out of our hair, I should be able to get back to this today and hopefully have the 3.4/alpha release out before the New Millenium*! :-) - Jordan * Purposely spelled with only one `n' and a year early, just to piss off the pedants. :-) - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Fri Dec 24 10:36: 8 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 761421518D for ; Fri, 24 Dec 1999 10:36:04 -0800 (PST) (envelope-from don@calis.blacksun.org) Received: by calis.blacksun.org (Postfix, from userid 1000) id DD2D174; Fri, 24 Dec 1999 13:38:58 -0500 (EST) Received: from localhost (localhost [127.0.0.1]) by calis.blacksun.org (Postfix) with ESMTP id D889649E6; Fri, 24 Dec 1999 13:38:58 -0500 (EST) Date: Fri, 24 Dec 1999 13:38:58 -0500 (EST) From: Don To: Steve Noble Cc: John Polstra , alpha@FreeBSD.ORG Subject: Re: Is 3.4-RELEASE for i386 only? In-Reply-To: <19991224102306.U5414@sonn.com> 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've successfully cvs'd and built 3.4 ... We are not talking about 3.4-STABLE but 3.4_RELEASE. Both John and myself are wondering the ftp installable distribution is for 3.4 for the Alpha. -don To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Fri Dec 24 11:54:44 1999 Delivered-To: freebsd-alpha@freebsd.org Received: from mass.cdrom.com (castles551.castles.com [208.214.165.115]) by hub.freebsd.org (Postfix) with ESMTP id AA62615116 for ; Fri, 24 Dec 1999 11:54:42 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id LAA10609; Fri, 24 Dec 1999 11:59:03 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <199912241959.LAA10609@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: John Polstra Cc: alpha@freebsd.org Subject: Re: Is 3.4-RELEASE for i386 only? In-reply-to: Your message of "Fri, 24 Dec 1999 10:22:48 PST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 24 Dec 1999 11:59:03 -0800 From: Mike Smith Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > I have a feeling I may have missed an announcement due to sheer lack > of attention. I see that there are no Alpha bits for 3.4-RELEASE on > the FTP sites. Are there going to be any, or have we more or less > abandoned the Alpha on that branch? The rush to get the i386 release out before the end of the year forced us to back-burner the alpha product. When I left the office yesterday evening, jkh was just getting the build underway. We already have a package collection ready to roll for it, so I'd look for something before the new year. -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Fri Dec 24 12: 9:59 1999 Delivered-To: freebsd-alpha@freebsd.org Received: from mass.cdrom.com (castles551.castles.com [208.214.165.115]) by hub.freebsd.org (Postfix) with ESMTP id 5936614F94; Fri, 24 Dec 1999 12:09:57 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id MAA10876; Fri, 24 Dec 1999 12:14:16 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <199912242014.MAA10876@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Wilko Bulte Cc: Mike Smith , FreeBSD-alpha mailing list Subject: Re: diskless boot on Alpha In-reply-to: Your message of "Fri, 24 Dec 1999 17:47:08 +0100." <19991224174708.A63398@yedi.iaf.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 24 Dec 1999 12:14:16 -0800 From: Mike Smith Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > I admit not to understand why this is the case. My theory right now is > that the compile of autoconf.c should include opt_nfs.h in addition to > opt_nfsroot.h. The latter is already present. ... > When I add opt_nfs.h to the include files in autoconf.c thing compile like > expected. Can somebody please verify this for me? Sounds about right to me. > When I boot a kernel built with the above patch I get: > > >>## nfsroot before ufs > Mounting root from ufs:192.168.200.22:/usr/sandpiper > Can't allocate root mount for filesystem 'ufs': 19 > Root mount failed: 19 Ugh. > Manual root filesystem specification: > : Mount using filesystem > eg. ufs:/dev/da0s1a > ? List valid disk boot devices > Abort manual input Did you try entering nfs:192.168.200.22:/usr/sandpiper here? > Which I don't understand because vfs_mountroot() should try nfs before > ufs because that is the order in which cpu_rootconf sets up the > rootdevnames ? And in my case the kernel is compiled without > FFS and FFS_ROOT so it should only do NFS. I don't think that it's even getting down to the paths in rootdevnames[], I think it's trying to boot the path from the vfs.root.mountfrom variable which is set by the loader. I'm puzzled as to why it doesn't then move on to the fallbacks. Can you add some debugging to to sys/kern/vfs_conf.c:vfs_mountroot() and see exactly what's going on there? Thanks... > I'm puzzled.. > > NB as the code tells me to use 'loader', how do I set > that up on Alpha? I still need to bootp netboot right? netboot is the loader, it just has the wrong name. One of these days they'll all coalesce back into a single binary. -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Fri Dec 24 14:18: 3 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 905C614D64; Fri, 24 Dec 1999 14:17:54 -0800 (PST) (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 XAA11748; Fri, 24 Dec 1999 23:10:20 +0100 (MET) Received: (from wilko@localhost) by yedi.iaf.nl (8.9.3/8.9.3) id XAA68176; Fri, 24 Dec 1999 23:02:57 +0100 (CET) (envelope-from wilko) Date: Fri, 24 Dec 1999 23:02:57 +0100 From: Wilko Bulte To: Mike Smith Cc: FreeBSD-alpha mailing list Subject: Re: diskless boot on Alpha Message-ID: <19991224230257.A67738@yedi.iaf.nl> References: <19991224174708.A63398@yedi.iaf.nl> <199912242014.MAA10876@mass.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <199912242014.MAA10876@mass.cdrom.com>; from msmith@freebsd.org on Fri, Dec 24, 1999 at 12:14:16PM -0800 X-OS: FreeBSD yedi.iaf.nl 3.4-STABLE FreeBSD 3.4-STABLE X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Fri, Dec 24, 1999 at 12:14:16PM -0800, Mike Smith wrote: > > that the compile of autoconf.c should include opt_nfs.h in addition to > > opt_nfsroot.h. The latter is already present. > ... > > When I add opt_nfs.h to the include files in autoconf.c thing compile like > > expected. Can somebody please verify this for me? > > Sounds about right to me. OK. Do you want a wrap-up send-pr for this (i.e. as soon as I can get it to mount it's root (assuming I can .. :-) ? > Did you try entering > > nfs:192.168.200.22:/usr/sandpiper > > here? Yes, I did. Forgot to include the results. These are: >>## in cpu_rootconf >>## nfsroot before ufs Mounting root from ufs:192.168.200.22:/usr/sandpiper Can't allocate root mount for filesystem 'ufs': 19 Root mount failed: 19 Manual root filesystem specification: : Mount using filesystem eg. ufs:/dev/da0s1a ? List valid disk boot devices Abort manual input >>> nfs:192.168.200.22:/usr/sandpiper Mounting root from nfs:192.168.200.22:/usr/sandpiper no such device 'sandpiper' setrootbyname failed panic: nfs_mountroot: socreate(0000): 43 Which stems from: nfs/nfs_vfsops.c: /* * Do enough of ifconfig(8) so that the critical net interface can * talk to the server. */ error = socreate(nd->myif.ifra_addr.sa_family, &so, SOCK_DGRAM, 0, p); if (error) panic("nfs_mountroot: socreate(%04x): %d", nd->myif.ifra_addr.sa_family, error); I discovered this can be fixed by adding 'options BOOTP_NFSROOT' to the netbooted kernel. > > Which I don't understand because vfs_mountroot() should try nfs before > > ufs because that is the order in which cpu_rootconf sets up the > > rootdevnames ? And in my case the kernel is compiled without > > FFS and FFS_ROOT so it should only do NFS. > > I don't think that it's even getting down to the paths in rootdevnames[], > I think it's trying to boot the path from the vfs.root.mountfrom variable > which is set by the loader. I'm puzzled as to why it doesn't then move > on to the fallbacks. > > Can you add some debugging to to sys/kern/vfs_conf.c:vfs_mountroot() and > see exactly what's going on there? Thanks... Like: le0 XXX: driver didn't set ifq_maxlen >>## in cpu_rootconf >>## nfsroot before ufs >>## vfs_mountroot: getenv(mountfrom) = ufs:192.168.200.22:/usr/sandpiper Mounting root from ufs:192.168.200.22:/usr/sandpiper Can't allocate root mount for filesystem 'ufs': 19 Root mount failed: 19 >>## vfs_mountroot: trying legacy 0 Mounting root from nfs: bootpc_init: using network interface 'le0' Bootpc testing starting bootpc hw address is 8:0:2b:3c:61:45 BOOTP timeout for server 0xffffffff BOOTP timeout for server 0xffffffff [... etc] It gets this far after adding "options BOOTP_NFSROOT" to the kernel config file. You were right with the mountfrom variable. It got a hybrid of ufs and nfs which did not work too well. The fallback to legacy 0 gives it nfs to try and it gets a bit further. I'm not too sure why the BOOTP timeouts keep occuring but that is another matter. Guessing mode: the netboot/loader code probably does a kind of setenv which subsequently get getenv-ed by the booted kernel. If yes, where does that value reside, and how is it foud/read back by the kernel? In new SRM versions you can set do "set foo bar" to create a variable and give it a value. The old SRM (like the Sandpiper has) this is not possible. Long shot, but could this be the culprit? -- Wilko Bulte Arnhem, The Netherlands - The FreeBSD Project 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 From owner-freebsd-alpha Fri Dec 24 19:35:50 1999 Delivered-To: freebsd-alpha@freebsd.org Received: from news-ma.rhein-neckar.de (news-ma.rhein-neckar.de [193.197.90.3]) by hub.freebsd.org (Postfix) with ESMTP id 2A42C151F9 for ; Fri, 24 Dec 1999 19:35:47 -0800 (PST) (envelope-from daemon@bigeye.rhein-neckar.de) Received: from bigeye.rhein-neckar.de (uucp@localhost) by news-ma.rhein-neckar.de (8.8.8/8.8.8) with bsmtp id EAA23684 for freebsd-alpha@freebsd.org; Sat, 25 Dec 1999 04:35:45 +0100 (CET) (envelope-from daemon@bigeye.rhein-neckar.de) Received: (from daemon@localhost) by bigeye.rhein-neckar.de (8.9.3/8.9.3) id DAA62978 for freebsd-alpha@freebsd.org; Sat, 25 Dec 1999 03:37:29 +0100 (CET) (envelope-from daemon) From: naddy@mips.rhein-neckar.de (Christian Weisgerber) Subject: OSF/1 emulation: ksh93? Date: 25 Dec 1999 03:37:28 +0100 Message-ID: <841al8$1tfo$1@bigeye.rhein-neckar.de> To: freebsd-alpha@freebsd.org Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I gather FreeBSD/alpha has grown an OSF/1 emulation. (?) I maintain the ksh93 port, which alas has to use pre-compiled executables provided by AT&T. On i386, statically linked BSD/OS binaries work fine. AT&T also offers OSF/1 binaries. Since I don't have access to FreeBSD on alpha, I need to enlist somebody else's assistance to check these out. Go to , follow the link "Non-Commercial License Agreement and Available Software [ Binary ]", choose ast-base-97 and ast-base-99 with operating system "UNIX: Dec Alpha OSF/1" for download. Questions: Can the ksh93 executables be made to work on FreeBSD? Are they statically or dynamically linked? Special kernel options and/or Tru64 shared libs required? -- Christian "naddy" Weisgerber naddy@mips.rhein-neckar.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Sat Dec 25 6:33:16 1999 Delivered-To: freebsd-alpha@freebsd.org Received: from cicely9.cicely.de (cicely.de [194.231.9.142]) by hub.freebsd.org (Postfix) with ESMTP id E780314D7D for ; Sat, 25 Dec 1999 06:33:12 -0800 (PST) (envelope-from ticso@cicely9.cicely.de) Received: (from root@localhost) by cicely9.cicely.de (8.9.3/8.9.3) id PAA25865 for freebsd-alpha@freebsd.org; Sat, 25 Dec 1999 15:33:03 +0100 (CET) (envelope-from ticso) Date: Sat, 25 Dec 1999 15:33:02 +0100 From: Bernd Walter To: freebsd-alpha@freebsd.org Subject: NFS append race @2000:119 Message-ID: <19991225153301.A15915@cicely9.cicely.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org From time to time I get the following messages with current from 18th Dec 1999: NFS append race @2000:119 NFS append race @2000:96 The system is a PC164 using amd with NFSV3/TCP. NFS-Servers are i386 current from july to november - I don't know with which of them these errors happen. The servers are all used in a similar configuration from older i386-current clients without these errors. -- B.Walter COSMO-Project http://www.cosmo-project.de ticso@cicely.de Usergroup info@cosmo-project.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message