From owner-freebsd-alpha Sat Jan 1 22:48:53 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from picnic.mat.net (picnic.mat.net [206.246.122.133]) by hub.freebsd.org (Postfix) with ESMTP id BEF3E14D35 for ; Sat, 1 Jan 2000 22:48:49 -0800 (PST) (envelope-from chuckr@picnic.mat.net) Received: from localhost (chuckr@localhost [127.0.0.1]) by picnic.mat.net (8.9.3/8.9.3) with ESMTP id BAA12594 for ; Sun, 2 Jan 2000 01:48:40 -0500 (EST) (envelope-from chuckr@picnic.mat.net) Date: Sun, 2 Jan 2000 01:48:40 -0500 (EST) From: Chuck Robey To: FreeBSD-alpha@FreeBSD.org Subject: fxp0 & splimp 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 was trying to bring an Alpha with a kernel from 11/15/99 to current, and I can't seem to get kernel right. I see that there were a lot of config changes, so perhaps I don't have my config file in sync, but it looks roughly like GENERIC, so I will toss the diag information in your laps. The kernel boots, but it can't find the onboard Intel Pro-100 (it's a Intel DK440LX, integrated everything). The boot message tells me: link_elf: symbol splimp undefined This just stops the network from working, so I'm not in trouble (I have the old kernel cached away too). Seeing as I didn't find the ax0 device in GENERIC, I took it out of my config file, and this causes more confusion, because the ax0 device IS being caught on the dmesg, but the fxp0 device (which is in the new config, instead of ax0) isn't being caught. I haven't done a make world with the new kernel yet, I'm running on somewhat old userland, could that have some effect? No kld's, that can't be it. Old bootblocks? ---------------------------------------------------------------------------- Chuck Robey | Interests include C & Java programming, New Year's Resolution: I | electronics, communications, and will not sphroxify gullible| signal processing. people into looking up | I run picnic.mat.net: FreeBSD-current(i386) and fictitious words in the | jaunt.mat.net : FreeBSD-current(Alpha)| dictionary. | ---------------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Sat Jan 1 23:18:15 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from picnic.mat.net (picnic.mat.net [206.246.122.133]) by hub.freebsd.org (Postfix) with ESMTP id D3EDD14CAF for ; Sat, 1 Jan 2000 23:18:11 -0800 (PST) (envelope-from chuckr@picnic.mat.net) Received: from localhost (chuckr@localhost [127.0.0.1]) by picnic.mat.net (8.9.3/8.9.3) with ESMTP id CAA12744 for ; Sun, 2 Jan 2000 02:18:04 -0500 (EST) (envelope-from chuckr@picnic.mat.net) Date: Sun, 2 Jan 2000 02:18:03 -0500 (EST) From: Chuck Robey To: FreeBSD-alpha@FreeBSD.ORG Subject: Re: fxp0 & splimp 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 Sun, 2 Jan 2000, Chuck Robey wrote: > I was trying to bring an Alpha with a kernel from 11/15/99 to current, and > I can't seem to get kernel right. I see that there were a lot of config > changes, so perhaps I don't have my config file in sync, but it looks > roughly like GENERIC, so I will toss the diag information in your laps. > > The kernel boots, but it can't find the onboard Intel Pro-100 (it's a > Intel DK440LX, integrated everything). The boot message tells me: > > link_elf: symbol splimp undefined > > This just stops the network from working, so I'm not in trouble (I have > the old kernel cached away too). Seeing as I didn't find the ax0 device > in GENERIC, I took it out of my config file, and this causes more > confusion, because the ax0 device IS being caught on the dmesg, but the > fxp0 device (which is in the new config, instead of ax0) isn't being > caught. Followup to my own question, because I just found out that dmesg on the Alpha doesn't clear out the old boot message, and when I made real sure that I *was* reading the right dmesg, ax0 isn't showing up. Neither is fxp0, and the splimp message is still there, so most of the question still holds. I'm getting the link error on boot, and fxp0 isn't being seen on probe. > I haven't done a make world with the new kernel yet, I'm running on > somewhat old userland, could that have some effect? No kld's, that can't > be it. Old bootblocks? ---------------------------------------------------------------------------- Chuck Robey | Interests include C & Java programming, New Year's Resolution: I | electronics, communications, and will not sphroxify gullible| signal processing. people into looking up | I run picnic.mat.net: FreeBSD-current(i386) and fictitious words in the | jaunt.mat.net : FreeBSD-current(Alpha)| dictionary. | ---------------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Sun Jan 2 0: 7:48 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from mass.cdrom.com (castles512.castles.com [208.214.165.76]) by hub.freebsd.org (Postfix) with ESMTP id 554DE14E00 for ; Sun, 2 Jan 2000 00:07:44 -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 AAA09891; Sun, 2 Jan 2000 00:12:57 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <200001020812.AAA09891@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Chuck Robey Cc: FreeBSD-alpha@FreeBSD.org Subject: Re: fxp0 & splimp In-reply-to: Your message of "Sun, 02 Jan 2000 01:48:40 EST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 02 Jan 2000 00:12:57 -0800 From: Mike Smith Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > I was trying to bring an Alpha with a kernel from 11/15/99 to current, and > I can't seem to get kernel right. I see that there were a lot of config > changes, so perhaps I don't have my config file in sync, but it looks > roughly like GENERIC, so I will toss the diag information in your laps. > > The kernel boots, but it can't find the onboard Intel Pro-100 (it's a > Intel DK440LX, integrated everything). The boot message tells me: I'm not aware of any way to install an Alpha CPU on an Intel DK440LX board that doesn't involve rolling your own silicon and some neat work with small machine tools. -- \\ 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 Jan 2 5:56:42 2000 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 5498614E67 for ; Sun, 2 Jan 2000 05:56: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 NAA27869; Sun, 2 Jan 2000 13:57:28 GMT (envelope-from dfr@nlsystems.com) Date: Sun, 2 Jan 2000 13:56:10 +0000 (GMT) From: Doug Rabson To: Chuck Robey Cc: FreeBSD-alpha@freebsd.org Subject: Re: fxp0 & splimp 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 Sun, 2 Jan 2000, Chuck Robey wrote: > I was trying to bring an Alpha with a kernel from 11/15/99 to current, and > I can't seem to get kernel right. I see that there were a lot of config > changes, so perhaps I don't have my config file in sync, but it looks > roughly like GENERIC, so I will toss the diag information in your laps. > > The kernel boots, but it can't find the onboard Intel Pro-100 (it's a > Intel DK440LX, integrated everything). The boot message tells me: > > link_elf: symbol splimp undefined > > This just stops the network from working, so I'm not in trouble (I have > the old kernel cached away too). Seeing as I didn't find the ax0 device > in GENERIC, I took it out of my config file, and this causes more > confusion, because the ax0 device IS being caught on the dmesg, but the > fxp0 device (which is in the new config, instead of ax0) isn't being > caught. > > I haven't done a make world with the new kernel yet, I'm running on > somewhat old userland, could that have some effect? No kld's, that can't > be it. Old bootblocks? Are you sure there are no klds? That is an error from the kernel linker.. -- 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 Sun Jan 2 5:57:50 2000 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 B1DE014E67 for ; Sun, 2 Jan 2000 05:57: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 NAA27873; Sun, 2 Jan 2000 13:58:54 GMT (envelope-from dfr@nlsystems.com) Date: Sun, 2 Jan 2000 13:57:36 +0000 (GMT) From: Doug Rabson To: Chuck Robey Cc: FreeBSD-alpha@freebsd.org Subject: Re: fxp0 & splimp 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 Sun, 2 Jan 2000, Chuck Robey wrote: > On Sun, 2 Jan 2000, Chuck Robey wrote: > > > I was trying to bring an Alpha with a kernel from 11/15/99 to current, and > > I can't seem to get kernel right. I see that there were a lot of config > > changes, so perhaps I don't have my config file in sync, but it looks > > roughly like GENERIC, so I will toss the diag information in your laps. > > > > The kernel boots, but it can't find the onboard Intel Pro-100 (it's a > > Intel DK440LX, integrated everything). The boot message tells me: > > > > link_elf: symbol splimp undefined > > > > This just stops the network from working, so I'm not in trouble (I have > > the old kernel cached away too). Seeing as I didn't find the ax0 device > > in GENERIC, I took it out of my config file, and this causes more > > confusion, because the ax0 device IS being caught on the dmesg, but the > > fxp0 device (which is in the new config, instead of ax0) isn't being > > caught. > > Followup to my own question, because I just found out that dmesg on the > Alpha doesn't clear out the old boot message, and when I made real sure > that I *was* reading the right dmesg, ax0 isn't showing up. Neither is > fxp0, and the splimp message is still there, so most of the question still > holds. I'm getting the link error on boot, and fxp0 isn't being seen on > probe. I think the ax driver was removed since the new dc driver was committed. -- 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 Sun Jan 2 10:41: 7 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from picnic.mat.net (picnic.mat.net [206.246.122.133]) by hub.freebsd.org (Postfix) with ESMTP id 290E414E5B; Sun, 2 Jan 2000 10:41:03 -0800 (PST) (envelope-from chuckr@picnic.mat.net) Received: from localhost (chuckr@localhost [127.0.0.1]) by picnic.mat.net (8.9.3/8.9.3) with ESMTP id NAA13970; Sun, 2 Jan 2000 13:40:52 -0500 (EST) (envelope-from chuckr@picnic.mat.net) Date: Sun, 2 Jan 2000 13:40:51 -0500 (EST) From: Chuck Robey To: Mike Smith Cc: FreeBSD-alpha@FreeBSD.ORG Subject: Re: fxp0 & splimp In-Reply-To: <200001020812.AAA09891@mass.cdrom.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 On Sun, 2 Jan 2000, Mike Smith wrote: > > I was trying to bring an Alpha with a kernel from 11/15/99 to current, and > > I can't seem to get kernel right. I see that there were a lot of config > > changes, so perhaps I don't have my config file in sync, but it looks > > roughly like GENERIC, so I will toss the diag information in your laps. > > > > The kernel boots, but it can't find the onboard Intel Pro-100 (it's a > > Intel DK440LX, integrated everything). The boot message tells me: > > I'm not aware of any way to install an Alpha CPU on an Intel DK440LX board > that doesn't involve rolling your own silicon and some neat work with > small machine tools. God. Once a year I decide to party (I'm not a big drinker) and everybody's a critic :-) I better amend this with reality, hadn't I? The ethernet card's a CNet Pro100, uses the ax0 device. I still get that "link_elf: symbol splimp undefined" error during boot, and the CNet card's not recognized. The previous 11/15/99 kernel used no modules (kldstat says so), and I added nothing new to the config, just changed one "disk" to device, and took out the following lines that config complained about (and weren't in GENERIC): controller cia0 controller apecs0 controller tsunami0 controller lca0 controller tcasic0 controller tc0 controller tcds0 controller ioasic0 I'd had these in before because they were in GENERIC, now they're gone. If I'm loading a kld on startup (the boot loader says no) then I am not sure how to check further. The only problem I see with the new kernel is the splimp thing (which means no network card). While I wait for responses, I'm going to re-cvsup and build me a new kernel. ---------------------------------------------------------------------------- Chuck Robey | Interests include C & Java programming, New Year's Resolution: I | electronics, communications, and will not sphroxify gullible| signal processing. people into looking up | I run picnic.mat.net: FreeBSD-current(i386) and fictitious words in the | jaunt.mat.net : FreeBSD-current(Alpha)| dictionary. | ---------------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Sun Jan 2 12:50: 3 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id 72D201509B for ; Sun, 2 Jan 2000 12:50:01 -0800 (PST) (envelope-from gnats@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.9.3/8.9.2) id MAA63099; Sun, 2 Jan 2000 12:50:01 -0800 (PST) (envelope-from gnats@FreeBSD.org) Received: by hub.freebsd.org (Postfix, from userid 32767) id 95FA514BCC; Sun, 2 Jan 2000 12:44:59 -0800 (PST) Message-Id: <20000102204459.95FA514BCC@hub.freebsd.org> Date: Sun, 2 Jan 2000 12:44:59 -0800 (PST) From: freebsd@furka.zuo.cpqcorp.net To: freebsd-gnats-submit@freebsd.org X-Send-Pr-Version: www-1.0 Subject: alpha/15846: Alpha hangs when using ppp/tun - no error Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >Number: 15846 >Category: alpha >Synopsis: Alpha hangs when using ppp/tun - no error >Confidential: no >Severity: critical >Priority: high >Responsible: freebsd-alpha >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Sun Jan 2 12:50:00 PST 2000 >Closed-Date: >Last-Modified: >Originator: Pascal Pederiva >Release: 4.0-19991225-CURRENT >Organization: >Environment: FreeBSD 4.0-19991225-CURRENT FreeBSD 4.0-19991225 #7: Sat Jan 1 01:55:05 CET 2000 root@router.paped.com:/usr/src/sys/compile/ALPHA1 alpha - AlphaServer 400 4/233 - Alpha Station 4/266 >Description: Usermode ppp using tun and sio on either AlphaServer 400 4/233 or Alpha Station 4/266 works fine for about 5 minutes, then hangs the system completly. (no ping,no response on the console). Can be forced by transferring data (http and ftp tried). >How-To-Repeat: Setup user mode ppp, use ppp-link to transfer data via one of the builtin serial ports. Custom Kernels as well as generic kernel shows same behaviour. >Fix: - How to force a crash with FreeBSD ? - Make indicates that ev56 instructions are used .. those are ev4 Systems, could that be a problem ? Could not build kernel for ev4. >Release-Note: >Audit-Trail: >Unformatted: To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Sun Jan 2 13: 5:56 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from tccn.cs.kun.nl (tccn.cs.kun.nl [131.174.32.38]) by hub.freebsd.org (Postfix) with ESMTP id 0004014A08 for ; Sun, 2 Jan 2000 13:05:53 -0800 (PST) (envelope-from sparky@cs.kun.nl) Received: from cs.kun.nl (catv6063.extern.kun.nl [131.174.116.63]) by tccn.cs.kun.nl (8.9.2/8.9.2) with ESMTP id WAA56088 for ; Sun, 2 Jan 2000 22:05:23 +0100 (CET) (envelope-from sparky@cs.kun.nl) Message-ID: <386FBEEE.B1F7F0E7@cs.kun.nl> Date: Sun, 02 Jan 2000 22:11:10 +0100 From: Franc Grootjen X-Mailer: Mozilla 4.61 [en] (Win98; I) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-alpha@freebsd.org Subject: ncr in polling mode?! 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 just tried to run ccd on my AXPpci33 box and striped two 1Gb SCSI drives. No problems in configuring, but bonnie show _no_ performance gain at all (it got worse). So my question is: does this ncr driver use DMA or is it polling all the time? I really like to know. Please reply to sparky@cs.kun.nl, since I'm not on the list Franc To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Sun Jan 2 15:22:59 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from mail.du.gtn.com (mail.du.gtn.com [194.77.9.57]) by hub.freebsd.org (Postfix) with ESMTP id 8FE3F14EFD for ; Sun, 2 Jan 2000 15:22:53 -0800 (PST) (envelope-from ticso@cicely8.cicely.de) Received: from mail.cicely.de (cicely.de [194.231.9.142]) by mail.du.gtn.com (8.9.3/8.9.3) with ESMTP id AAA20273; Mon, 3 Jan 2000 00:22:24 +0100 (MET) Received: from cicely8.cicely.de (cicely8.cicely.de [10.1.2.10]) by mail.cicely.de (8.9.0/8.9.0) with ESMTP id AAA38304; Mon, 3 Jan 2000 00:22:54 +0100 (CET) Received: (from ticso@localhost) by cicely8.cicely.de (8.9.3/8.9.2) id AAA87739; Mon, 3 Jan 2000 00:22:28 +0100 (CET) (envelope-from ticso) Date: Mon, 3 Jan 2000 00:22:27 +0100 From: Bernd Walter To: Franc Grootjen Cc: freebsd-alpha@FreeBSD.ORG Subject: Re: ncr in polling mode?! Message-ID: <20000103002227.A87713@cicely8.cicely.de> References: <386FBEEE.B1F7F0E7@cs.kun.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre3i In-Reply-To: <386FBEEE.B1F7F0E7@cs.kun.nl> Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Sun, Jan 02, 2000 at 10:11:10PM +0100, Franc Grootjen wrote: > Hi! > I just tried to run ccd on my AXPpci33 box and striped two 1Gb SCSI > drives. No problems in configuring, but bonnie show _no_ performance > gain at all (it got worse). So my question is: does this ncr driver use > DMA or is it polling all the time? > I really like to know. Please reply to sparky@cs.kun.nl, since I'm not > on the list If your performance got much worse your stripe size is obviously to small. bonnie is using single file transaction so don't expect to be much faster than a single drive with this programm. The ncr driver is running fine - the newer sym driver seems to be slightly better but I asume that your controller is a plain 810 and not an 810A so it is not supported by the sym driver. -- 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 From owner-freebsd-alpha Mon Jan 3 9:42:38 2000 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 EE41414E3D for ; Mon, 3 Jan 2000 09:42:34 -0800 (PST) (envelope-from freebsd-alpha@scc.nl) Received: (from daemon@localhost) by mail.scc.nl (8.9.3/8.9.3) id SAA19299 for alpha@FreeBSD.org; Mon, 3 Jan 2000 18:38: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: Mon, 03 Jan 2000 18:38:18 +0100 From: Marcel Moolenaar Message-ID: <3870DE8A.24B73F07@scc.nl> Organization: SCC vof Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Subject: rshd broken on alpha? Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org donut: 4.0-CURRENT Sun Jan 2 17:30:52 CET 2000 alpha muffin: 3.3-STABLE Sat Dec 4 12:54:34 CET 1999 i386 scones: 4.0-CURRENT Sun Jan 2 13:20:10 CET 2000 i386 case 1: scones -> donut ----------------------- scones% rsh donut assword:anything_you_type_is_displayed ^C [note: no password should be required in this case] case 2: scones -> muffin ------------------------ scones% rsh muffin Last login: Mon Jan 3 18:17:36 from scones ... [note: no password required. this is normal and works ok] case 3: donut -> scones ----------------------- donut% rsh scones Password: Last login: Mon Jan 3 18:10:45 from donut ... [note: password required. works ok] cases 4-6 --------- donut -> muffin: ok muffin -> donut: broken (same as case 1) muffin -> scones: ok conclusion ---------- i386 -> alpha: broken otherwise: ok more info: ---------- o almost no local tuning in /etc on donut o telnet works ok o it worked before the upgrade Is this a known problem? Does anyone else sees this? -- 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 Jan 4 6:34:19 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by hub.freebsd.org (Postfix) with ESMTP id 3EF551523A; Tue, 4 Jan 2000 06:33:46 -0800 (PST) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.1/8.9.1) with ESMTP id JAA25702; Tue, 4 Jan 2000 09:33:35 -0500 (EST) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.9.3/8.9.1) id JAA48267; Tue, 4 Jan 2000 09:33:04 -0500 (EST) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Tue, 4 Jan 2000 09:33:04 -0500 (EST) To: Chuck Robey Cc: Mike Smith , FreeBSD-alpha@FreeBSD.ORG Subject: Re: fxp0 & splimp In-Reply-To: References: <200001020812.AAA09891@mass.cdrom.com> X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14450.832.737977.843430@grasshopper.cs.duke.edu> Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Chuck Robey writes: > I better amend this with reality, hadn't I? The ethernet card's a CNet > Pro100, uses the ax0 device. I still get that "link_elf: symbol splimp > undefined" error during boot, and the CNet card's not recognized. The > previous 11/15/99 kernel used no modules (kldstat says so), and I added > nothing new to the config, just changed one "disk" to device, and took out Chuck, The if_ax driver disappeared between Nov 15 & now (in favor of if_dc). So if_ax was built into the 11/15 GENERIC kernel but it is not built into today's GENERIC kernel. When you do an 'ifconfig ax0 foo' ifconfig will kldload /modules/if_ax.ko. This module will be from the last time you built world. Among other things, splimp() is now an in-line function so there is no way for the kld loader to resolve splimp() because there is no splimp symbol in the kernel. You should be using dc0 instead. Cheers, Drew ------------------------------------------------------------------------------ Andrew Gallatin, Sr Systems Programmer http://www.cs.duke.edu/~gallatin Duke University Email: gallatin@cs.duke.edu Department of Computer Science Phone: (919) 660-6590 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Tue Jan 4 7:58:12 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by hub.freebsd.org (Postfix) with ESMTP id 9C72F1508D for ; Tue, 4 Jan 2000 07:58:07 -0800 (PST) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.1/8.9.1) with ESMTP id KAA27100; Tue, 4 Jan 2000 10:58:00 -0500 (EST) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.9.3/8.9.1) id KAA48398; Tue, 4 Jan 2000 10:57:30 -0500 (EST) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Tue, 4 Jan 2000 10:57:29 -0500 (EST) To: Marcel Moolenaar Cc: alpha@FreeBSD.ORG Subject: Re: rshd broken on alpha? In-Reply-To: <3870DE8A.24B73F07@scc.nl> References: <3870DE8A.24B73F07@scc.nl> X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14450.6182.72917.987226@grasshopper.cs.duke.edu> Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Marcel Moolenaar writes: > donut: 4.0-CURRENT Sun Jan 2 17:30:52 CET 2000 alpha > muffin: 3.3-STABLE Sat Dec 4 12:54:34 CET 1999 i386 > scones: 4.0-CURRENT Sun Jan 2 13:20:10 CET 2000 i386 > > case 1: scones -> donut > ----------------------- > scones% rsh donut > assword:anything_you_type_is_displayed > ^C > > [note: no password should be required in this case] > Perhaps this not alpha-specific, but is related to the "Problem with rlogin and /etc/pam.conf" thread on -current? Drew ------------------------------------------------------------------------------ Andrew Gallatin, Sr Systems Programmer http://www.cs.duke.edu/~gallatin Duke University Email: gallatin@cs.duke.edu Department of Computer Science Phone: (919) 660-6590 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Tue Jan 4 8:11:51 2000 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 39DE01545E for ; Tue, 4 Jan 2000 08:11:48 -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 125WYg-000FaC-00; Tue, 4 Jan 2000 16:11:43 +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 RAA06252; Tue, 4 Jan 2000 17:11:40 +0100 (CET) (envelope-from marcel@scc.nl) Message-ID: <38721BBC.DDED502C@scc.nl> Date: Tue, 04 Jan 2000 17:11:40 +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: Andrew Gallatin Cc: alpha@FreeBSD.ORG Subject: Re: rshd broken on alpha? References: <3870DE8A.24B73F07@scc.nl> <14450.6182.72917.987226@grasshopper.cs.duke.edu> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Andrew Gallatin wrote: > > Marcel Moolenaar writes: > > donut: 4.0-CURRENT Sun Jan 2 17:30:52 CET 2000 alpha > > muffin: 3.3-STABLE Sat Dec 4 12:54:34 CET 1999 i386 > > scones: 4.0-CURRENT Sun Jan 2 13:20:10 CET 2000 i386 > > > > case 1: scones -> donut > > ----------------------- > > scones% rsh donut > > assword:anything_you_type_is_displayed > > ^C > > > > [note: no password should be required in this case] > > > > Perhaps this not alpha-specific, but is related to the "Problem with > rlogin and /etc/pam.conf" thread on -current? Yes, I happen to saw that thread. It solved the problem. Strange though, because I have updated both machines and my i386 didn't complain. That's probably why I didn't look any further and thought it was Alpha related :-/ Thanks for the reply, -- 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 Jan 4 10:10:11 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from zmamail02.zma.compaq.com (zmamail02.zma.compaq.com [161.114.64.102]) by hub.freebsd.org (Postfix) with ESMTP id 633161518D for ; Tue, 4 Jan 2000 10:10:08 -0800 (PST) (envelope-from michael.waite@compaq.com) Received: by zmamail02.zma.compaq.com (Postfix, from userid 12345) id A985125F; Tue, 4 Jan 2000 13:10:01 -0500 (EST) Received: from exctay-gh02.tay.cpqcorp.net (exctay-gh02.tay.cpqcorp.net [16.103.129.52]) by zmamail02.zma.compaq.com (Postfix) with ESMTP id A25FE257 for ; Tue, 4 Jan 2000 13:10:01 -0500 (EST) Received: by exctay-gh02.tay.cpqcorp.net with Internet Mail Service (5.5.2650.21) id ; Tue, 4 Jan 2000 13:10:01 -0500 Message-ID: <212CC57E84B8D111AD780000F84AA04906963D6B@mroexc2.tay.dec.com> From: "Waite, Michael" To: "'freebsd-alpha@freebsd.org'" Subject: Alpha XP1000a EV6.7 available Date: Tue, 4 Jan 2000 13:09:59 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-Type: text/plain Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I have just finished putting the latest Alpha 4.0 CURRENT up on the Internet for developers to use. The system that I have it running on is a brand new EV6.7 XP1000 running at 667MHZ with two gigs of ram. You can get your free shell account at http://www.testdrive.compaq.com This is not intended as an additional mail client. We have disabled most out-going connections for obvious reasons but you can ftp and telnet onto the system. I also have a DPW500au running a previous version of 4.0 CURRENT -----Mike Michael Waite Global Partnering Solutions, Marlboro Center Compaq Computer Corporation TEL: (508)467-2289 EMAIL: michael.waite@compaq.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Tue Jan 4 12:59:46 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by hub.freebsd.org (Postfix) with ESMTP id 299D214CF6 for ; Tue, 4 Jan 2000 12:59:40 -0800 (PST) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.1/8.9.1) with ESMTP id PAA01976 for ; Tue, 4 Jan 2000 15:59:39 -0500 (EST) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.9.3/8.9.1) id PAA49001; Tue, 4 Jan 2000 15:59:08 -0500 (EST) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Tue, 4 Jan 2000 15:59:08 -0500 (EST) To: freebsd-alpha@freebsd.org Subject: XFree86 3.9.17? X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14450.24156.784763.803825@grasshopper.cs.duke.edu> Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Has anybody been able to build the XF86 3.9.17 snapshot on alpha yet? Should I even expect that it will work? Thanks, Drew ------------------------------------------------------------------------------ Andrew Gallatin, Sr Systems Programmer http://www.cs.duke.edu/~gallatin Duke University Email: gallatin@cs.duke.edu Department of Computer Science Phone: (919) 660-6590 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Tue Jan 4 15:58:36 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from mail.HiWAAY.net (fly.HiWAAY.net [208.147.154.56]) by hub.freebsd.org (Postfix) with ESMTP id E328914A28 for ; Tue, 4 Jan 2000 15:58:34 -0800 (PST) (envelope-from kris@hiwaay.net) Received: from tnt6-216-180-4-219.dialup.HiWAAY.net (tnt6-216-180-4-219.dialup.HiWAAY.net [216.180.4.219]) by mail.HiWAAY.net (8.9.3/8.9.0) with ESMTP id RAA03887; Tue, 4 Jan 2000 17:58:32 -0600 (CST) Date: Tue, 4 Jan 2000 17:58:31 -0600 (CST) From: Kris Kirby X-Sender: kris@barricuda.bsd.nws.net To: Andrew Gallatin Cc: freebsd-alpha@FreeBSD.ORG Subject: Re: XFree86 3.9.17? In-Reply-To: <14450.24156.784763.803825@grasshopper.cs.duke.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Tue, 4 Jan 2000, Andrew Gallatin wrote: > > Has anybody been able to build the XF86 3.9.17 snapshot on alpha yet? > Should I even expect that it will work? Geez, I'm having enough trouble building it for i386 ;-). Seriously, if anyone would like help me, it wouldn't go unappreciated. --- Kris Kirby ------------------------------------------- TGIFreeBSD... 'Nuff said. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Tue Jan 4 16:33:39 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from FreeBSD.ORG (ppp19-besancon.isdnet.net [195.154.11.226]) by hub.freebsd.org (Postfix) with ESMTP id ECC4D15027 for ; Tue, 4 Jan 2000 16:33:34 -0800 (PST) (envelope-from jmz@FreeBSD.ORG) Received: (from jmz@localhost) by qix.jmz.org (8.9.3/8.9.3) id BAA94537; Wed, 5 Jan 2000 01:33:37 +0100 (MET) (envelope-from jmz@FreeBSD.ORG) Date: Wed, 5 Jan 2000 01:33:37 +0100 (MET) Message-Id: <200001050033.BAA94537@qix.jmz.org> From: Jean-Marc Zucconi To: kris@hiwaay.net Cc: gallatin@cs.duke.edu, freebsd-alpha@FreeBSD.ORG In-reply-to: (message from Kris Kirby on Tue, 4 Jan 2000 17:58:31 -0600 (CST)) Subject: Re: XFree86 3.9.17? X-Mailer: Emacs References: Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >>>>> Kris Kirby writes: > On Tue, 4 Jan 2000, Andrew Gallatin wrote: >> >> Has anybody been able to build the XF86 3.9.17 snapshot on alpha yet? >> Should I even expect that it will work? > Geez, I'm having enough trouble building it for i386 ;-). Seriously, if > anyone would like help me, it wouldn't go unappreciated. Foe the i386 try with the following patches (eventually apply them by hand as they are for 3.9.17 excepted the last one) --- programs/Xserver/hw/xfree86/input/joystick/Imakefile~ Fri Oct 8 01:24:05 1999 +++ programs/Xserver/hw/xfree86/input/joystick/Imakefile Fri Oct 8 14:17:12 1999 @@ -12,11 +12,11 @@ -I$(SERVERSRC)/include -I$(XINCLUDESRC) -I$(EXTINCSRC) #ifdef LinuxArchitecture - ARCH_JSTK = ../os-support/linux/lnx_jstk.o +ARCH_JSTK = ../os-support/linux/lnx_jstk.o #endif #if defined(FreeBSDArchitecture) || defined(NetBSDArchitecture) || defined(OpenBSDArchitecture) - ARCH_JSTK = ../os-support/bsd/bsd_jstk.o +ARCH_JSTK = ../os-support/bsd/bsd_jstk.o #endif #if MakeHasPosixVariableSubstitutions --- programs/Xserver/hw/xfree86/os-support/bsd/bsd_jstk.c~ Sun Aug 2 08:43:34 1998 +++ programs/Xserver/hw/xfree86/os-support/bsd/bsd_jstk.c Mon Oct 11 02:27:32 1999 @@ -97,7 +97,6 @@ *centerY = js.y; xf86Msg(X_PROBED, "Joystick: CenterY set to %d\n", *centerY); } - } return status; } --- lib/FS/Imakefile~ Sat Feb 20 15:51:05 1999 +++ lib/FS/Imakefile Mon Oct 11 02:43:58 1999 @@ -34,7 +34,7 @@ CONN_DEFINES = $(CONNECTION_FLAGS) -DFS_t -DTRANS_CLIENT #if HasBSD44Sockets -SOCK_DEFINES = -DBSD44SOCKETS +SOCK_DEFINES = -DBSD44SOCKETS -D_P1003_1B_VISIBLE #endif #include --- Imakefile~ Sun Jan 2 03:09:36 2000 +++ Imakefile Sun Jan 2 21:42:40 2000 @@ -133,3 +133,4 @@ InstallDriverSDKNonExecFile(dgaproc.h,$(DRIVERSDKINCLUDEDIR)) InstallDriverSDKNonExecFile(xvdix.h,$(DRIVERSDKINCLUDEDIR)) +CDEBUGFLAGS= And add the following at the end of xf86site.def: #define HasTk YES #define TkLibDir /usr/local/lib #define TkIncDir /usr/local/include/tk8.2 #define TkLibName tk82 #define HasTcl YES #define TclLibDir /usr/local/lib #define TclIncDir /usr/local/include/tcl8.2 #define TclLibName tcl82 #define XVirtualFramebufferServer YES #define XprtServer YES #define XF86CardDrivers mga glint nv tga s3virge sis rendition neomagic i740 tdfx cirrus tseng trident chips apm GlideDriver fbdev ati vga XF86ExtraCardDrivers #define BuildFontServer YES #define InstallFSConfig YES #define BuildFonts YES #define Build75DpiFonts YES #define Build100DpiFonts YES #define BuildSpeedoFonts YES #define BuildType1Fonts YES #define BuildCIDFonts YES #define BuildCyrillicFonts YES #define BuildLatin2Fonts YES #define XInputDrivers dynapro elo2300 elographics magellan microtouch mutouch spaceorb wacom #define JoystickSupport NO #define BuildXinerama YES #define InstallXinitConfig YES #define InstallFSConfig YES #define ForceNormalLib YES Good luck :) Jean-Marc -- Jean-Marc Zucconi PGP Key: finger jmz@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 Jan 4 21:10:36 2000 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 EB474151E4 for ; Tue, 4 Jan 2000 21:10:34 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (jkh@localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id VAA12521 for ; Tue, 4 Jan 2000 21:10:27 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) To: alpha@freebsd.org Subject: 3.4-RELEASE now on ftp.freebsd.org Date: Tue, 04 Jan 2000 21:10:27 -0800 Message-ID: <12518.947049027@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Sorry for the long delay on this vs the 3.4-RELEASE/i386 release but our build machine was a bit ill for awhile. It can be found at: ftp://ftp.freebsd.org/pub/FreeBSD/releases/alpha/3.4-RELEASE/ ... and will also be available on CDROM from Walnut Creek CDROM in the next couple of weeks. I'll also be uploading the first ISO image to ftp://ftp.freebsd.org/pub/FreeBSD/releases/alpha/ISO-IMAGES/ as soon as it has been produced. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Wed Jan 5 17:24: 1 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id 429731504C for ; Wed, 5 Jan 2000 17:23:59 -0800 (PST) (envelope-from gnats@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.9.3/8.9.2) id RAA97623; Wed, 5 Jan 2000 17:20:00 -0800 (PST) (envelope-from gnats@FreeBSD.org) Received: from bubba.whistle.com (bubba.whistle.com [207.76.205.7]) by hub.freebsd.org (Postfix) with ESMTP id 3509015517 for ; Wed, 5 Jan 2000 17:16:08 -0800 (PST) (envelope-from archie@whistle.com) Received: (from archie@localhost) by bubba.whistle.com (8.9.2/8.9.2) id RAA72721; Wed, 5 Jan 2000 17:14:14 -0800 (PST) Message-Id: <200001060114.RAA72721@bubba.whistle.com> Date: Wed, 5 Jan 2000 17:14:14 -0800 (PST) From: Archie Cobbs Reply-To: archie@whistle.com To: FreeBSD-gnats-submit@freebsd.org X-Send-Pr-Version: 3.2 Subject: alpha/15929: printf(1) truncates if it sees 000 Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >Number: 15929 >Category: alpha >Synopsis: printf(1) truncates if it sees \000 >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-alpha >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Wed Jan 5 17:20:00 PST 2000 >Closed-Date: >Last-Modified: >Originator: Archie Cobbs >Release: FreeBSD 3.4-RELEASE i386 >Organization: Whistle Communications, Inc. >Environment: FreeBSD 3.4-RELEASE i386 >Description: If '\000' is used in a printf(1) format string, the string is trunctated at that point >How-To-Repeat: $ printf 'a\000truncated\n' This outputs "a" instead of "atruncated" >Fix: >Release-Note: >Audit-Trail: >Unformatted: To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Wed Jan 5 17:36:18 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from bubba.whistle.com (bubba.whistle.com [207.76.205.7]) by hub.freebsd.org (Postfix) with ESMTP id 1900B1551B; Wed, 5 Jan 2000 17:36:10 -0800 (PST) (envelope-from archie@whistle.com) Received: (from archie@localhost) by bubba.whistle.com (8.9.2/8.9.2) id RAA72964; Wed, 5 Jan 2000 17:31:57 -0800 (PST) From: Archie Cobbs Message-Id: <200001060131.RAA72964@bubba.whistle.com> Subject: Re: alpha/15929: printf(1) truncates if it sees 000 In-Reply-To: <200001060120.RAA97619@freefall.freebsd.org> from "gnats-admin@FreeBSD.org" at "Jan 5, 2000 05:20:00 pm" To: gnats-admin@FreeBSD.org, freebsd-alpha@FreeBSD.org Date: Wed, 5 Jan 2000 17:31:57 -0800 (PST) X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org gnats-admin@FreeBSD.org writes: > Thank you very much for your problem report. > It has the internal identification `alpha/15929'. > The individual assigned to look at your > report is: freebsd-alpha. > > >Category: alpha > >Responsible: freebsd-alpha > >Synopsis: printf(1) truncates if it sees \000 > >Arrival-Date: Wed Jan 5 17:20:00 PST 2000 Oops, this should be in Category 'bin' instead of 'alpha'. Sorry about that.. (can I change it with edit-pr? will try) -Archie ___________________________________________________________________________ Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Wed Jan 5 17:37: 3 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id 8AD2815517; Wed, 5 Jan 2000 17:37:01 -0800 (PST) (envelope-from archie@FreeBSD.org) Received: (from archie@localhost) by freefall.freebsd.org (8.9.3/8.9.2) id RAA00775; Wed, 5 Jan 2000 17:33:16 -0800 (PST) (envelope-from archie@FreeBSD.org) Date: Wed, 5 Jan 2000 17:33:16 -0800 (PST) From: Message-Id: <200001060133.RAA00775@freefall.freebsd.org> To: archie@FreeBSD.org, freebsd-alpha@FreeBSD.org, freebsd-bugs@FreeBSD.org Subject: Re: alpha/15929: printf(1) truncates if it sees \000 Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Synopsis: printf(1) truncates if it sees \000 Responsible-Changed-From-To: freebsd-alpha->freebsd-bugs Responsible-Changed-By: archie Responsible-Changed-When: Wed Jan 5 17:32:35 PST 2000 Responsible-Changed-Why: Category should be 'bin' instead of 'alpha'. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Wed Jan 5 23:20: 9 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id F201C154EC for ; Wed, 5 Jan 2000 23:20:07 -0800 (PST) (envelope-from gnats@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.9.3/8.9.2) id XAA61102; Wed, 5 Jan 2000 23:20:07 -0800 (PST) (envelope-from gnats@FreeBSD.org) Date: Wed, 5 Jan 2000 23:20:07 -0800 (PST) Message-Id: <200001060720.XAA61102@freefall.freebsd.org> To: freebsd-alpha@freebsd.org Cc: From: Alexander Tretiak Subject: Re: alpha/15846: Alpha hangs when using ppp/tun - no error Reply-To: Alexander Tretiak Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org The following reply was made to PR alpha/15846; it has been noted by GNATS. From: Alexander Tretiak To: freebsd-gnats-submit@FreeBSD.org, freebsd@furka.zuo.cpqcorp.net Cc: Subject: Re: alpha/15846: Alpha hangs when using ppp/tun - no error Date: Thu, 06 Jan 2000 10:24:44 +0300 -- Best regards, Alexander Tretyak. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Thu Jan 6 2:13:27 2000 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 ED5AE14F87 for ; Thu, 6 Jan 2000 02:13:23 -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 KAA07979; Thu, 6 Jan 2000 10:15:24 GMT (envelope-from dfr@nlsystems.com) Date: Thu, 6 Jan 2000 10:13:05 +0000 (GMT) From: Doug Rabson To: Andrew Gallatin Cc: freebsd-alpha@freebsd.org Subject: Re: XFree86 3.9.17? In-Reply-To: <14450.24156.784763.803825@grasshopper.cs.duke.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Tue, 4 Jan 2000, Andrew Gallatin wrote: > > Has anybody been able to build the XF86 3.9.17 snapshot on alpha yet? > Should I even expect that it will work? I have it (or something close to it from the XFree86 cvs) nearly working. It faults on exit at the moment. -- 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 Jan 6 15: 3:59 2000 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 36D9815139 for ; Thu, 6 Jan 2000 15:03:46 -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 AAA10311 for freebsd-alpha@freebsd.org; Fri, 7 Jan 2000 00:00:18 +0100 (MET) Received: (from wilko@localhost) by yedi.iaf.nl (8.9.3/8.9.3) id XAA02740 for freebsd-alpha@freebsd.org; Thu, 6 Jan 2000 23:47:09 +0100 (CET) (envelope-from wilko) Date: Thu, 6 Jan 2000 23:47:09 +0100 From: Wilko Bulte To: FreeBSD-alpha mailing list Subject: HARDWARE.TXT specific for Alpha? Message-ID: <20000106234709.A2690@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 Hi there, How about creating a HARDWARE.TXT (or something appropriately named) specific to FreeBSD on the Alpha machines? Topics to include (e.g) - what should be considered a minimum config - what hardware definitely does [not] work - specific hardware quirks (e.g. Miata first generation mainboard) - ... If people agree this is useful to do I volunteer to maintain this file. I can, however, only comment on Alpha hardware that I'm familiar with myself [NoName, Aspen Alpine, 'Bird-series' DEC3000, Miata]. So I will definitely need help for the other stuff. Comments please? -- 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 Jan 6 15:12:55 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from iteso.mx (iteso.mx [148.201.1.4]) by hub.freebsd.org (Postfix) with ESMTP id 2AFC714EFF for ; Thu, 6 Jan 2000 15:12:39 -0800 (PST) (envelope-from eric@iteso.mx) Received: from localhost (eric@localhost) by iteso.mx (8.9.3/8.9.3) with ESMTP id RAA79157 for ; Thu, 6 Jan 2000 17:12:52 -0600 (CST) (envelope-from eric@iteso.mx) Date: Thu, 6 Jan 2000 17:12:52 -0600 (CST) From: De la Cruz Lugo Eric To: freebsd-alpha@FreeBSD.ORG Subject: Re: HARDWARE.TXT specific for Alpha? In-Reply-To: <20000106234709.A2690@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 By the way, some one have information about the memory and storage limits for FreeBSD on Alpha?, max memory, max file size, thanks in advance. Eric De La Cruz Lugo. Merida, Yucatan, Mexico, the maya land! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Fri Jan 7 0:39: 5 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from ostrich.prod.itd.earthlink.net (ostrich.prod.itd.earthlink.net [207.217.120.14]) by hub.freebsd.org (Postfix) with ESMTP id C5701154E1 for ; Fri, 7 Jan 2000 00:39:03 -0800 (PST) (envelope-from kneumann@pacbell.net) Received: from gull.prod.itd.earthlink.net (gull.prod.itd.earthlink.net [207.217.121.85]) by ostrich.prod.itd.earthlink.net (8.8.7/8.8.5) with ESMTP id RAA23212 for ; Thu, 6 Jan 2000 17:29:07 -0800 (PST) Received: from laptop (CBL117.pool002.CH001-glendale.hs.earthlink.net [209.178.103.117]) by gull.prod.itd.earthlink.net (8.9.3/8.9.3) with SMTP id RAA11299 for ; Thu, 6 Jan 2000 17:24:06 -0800 (PST) Message-ID: <002901bf58ad$d192ab60$050a0a0a@earthlink.net> From: "Kurt Neumann" To: Subject: Parallel port driver for Alpha? Date: Thu, 6 Jan 2000 17:23:35 -0800 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0024_01BF586A.C3018E60" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2314.1300 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org This is a multi-part message in MIME format. ------=_NextPart_000_0024_01BF586A.C3018E60 Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: quoted-printable I just finished an extensive install, and realized I didn't see the = parallel port driver anywhere in the kernelconfig. I am afraid to ask, = but is it really not supported? I tried adding the options from what I = saw in i386, but it had problems. Any info would be appreciated... ------=_NextPart_000_0024_01BF586A.C3018E60 Content-Type: text/html; charset="Windows-1252" Content-Transfer-Encoding: quoted-printable
I just finished an extensive install, = and realized=20 I didn't see the parallel port driver anywhere in the kernelconfig. I am = afraid=20 to ask, but is it really not supported? I tried adding the options from = what I=20 saw in i386, but it had problems. Any info would be=20 appreciated...
------=_NextPart_000_0024_01BF586A.C3018E60-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Fri Jan 7 6:16:36 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by hub.freebsd.org (Postfix) with ESMTP id 37EF215650 for ; Fri, 7 Jan 2000 06:16:33 -0800 (PST) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.1/8.9.1) with ESMTP id JAA23889; Fri, 7 Jan 2000 09:16:31 -0500 (EST) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.9.3/8.9.1) id JAA60187; Fri, 7 Jan 2000 09:16:00 -0500 (EST) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Fri, 7 Jan 2000 09:16:00 -0500 (EST) To: De la Cruz Lugo Eric Cc: freebsd-alpha@FreeBSD.ORG Subject: Re: HARDWARE.TXT specific for Alpha? In-Reply-To: References: <20000106234709.A2690@yedi.iaf.nl> X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14453.62608.509835.123219@grasshopper.cs.duke.edu> Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org De la Cruz Lugo Eric writes: > By the way, some one have information about the memory and storage limits > for FreeBSD on Alpha?, max memory, max file size, thanks in advance. Max memory currently varies by platform. On most machines it is 1GB and on newer 21264 machines it is 2GB. I'll let somebody else address max file size. I've only gone as high as a few 10s of GB myself, but I think the limits should be much higher. Drew ------------------------------------------------------------------------------ Andrew Gallatin, Sr Systems Programmer http://www.cs.duke.edu/~gallatin Duke University Email: gallatin@cs.duke.edu Department of Computer Science Phone: (919) 660-6590 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Fri Jan 7 7:32:46 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from iteso.mx (iteso.mx [148.201.1.4]) by hub.freebsd.org (Postfix) with ESMTP id 7DE1E156D7 for ; Fri, 7 Jan 2000 07:32:37 -0800 (PST) (envelope-from eric@iteso.mx) Received: from localhost (eric@localhost) by iteso.mx (8.9.3/8.9.3) with ESMTP id JAA92062 for ; Fri, 7 Jan 2000 09:32:58 -0600 (CST) (envelope-from eric@iteso.mx) Date: Fri, 7 Jan 2000 09:32:58 -0600 (CST) From: De la Cruz Lugo Eric To: freebsd-alpha@FreeBSD.ORG Subject: Re: HARDWARE.TXT specific for Alpha? In-Reply-To: <14453.62608.509835.123219@grasshopper.cs.duke.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Fri, 7 Jan 2000, Andrew Gallatin wrote: > > De la Cruz Lugo Eric writes: > > By the way, some one have information about the memory and storage limits > > for FreeBSD on Alpha?, max memory, max file size, thanks in advance. > > Max memory currently varies by platform. On most machines it is 1GB > and on newer 21264 machines it is 2GB. > > I'll let somebody else address max file size. I've only gone as high > as a few 10s of GB myself, but I think the limits should be much higher. > > Drew Thanks for the info, in X86 Architecture the RAM max size is 4 GB (check ftp.cdrom configuration :), i thinked that in Alpha should be bigger. i guess im wrong about that :) thanks for the info again! Eric De La Cruz Lugo Merida, Yucatan, Mexico, The Maya Land! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Fri Jan 7 7:42: 6 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by hub.freebsd.org (Postfix) with ESMTP id 8D97F1522B for ; Fri, 7 Jan 2000 07:41:46 -0800 (PST) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.1/8.9.1) with ESMTP id KAA25241; Fri, 7 Jan 2000 10:41:44 -0500 (EST) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.9.3/8.9.1) id KAA60317; Fri, 7 Jan 2000 10:41:14 -0500 (EST) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Fri, 7 Jan 2000 10:41:13 -0500 (EST) To: De la Cruz Lugo Eric Cc: freebsd-alpha@FreeBSD.ORG Subject: Re: HARDWARE.TXT specific for Alpha? In-Reply-To: References: <14453.62608.509835.123219@grasshopper.cs.duke.edu> X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14454.1900.901358.626546@grasshopper.cs.duke.edu> Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org De la Cruz Lugo Eric writes: > > > On Fri, 7 Jan 2000, Andrew Gallatin wrote: > > > > > Max memory currently varies by platform. On most machines it is 1GB > > and on newer 21264 machines it is 2GB. <..> > > Thanks for the info, in X86 Architecture the RAM max size is 4 GB (check > ftp.cdrom configuration :), i thinked that in Alpha should be bigger. > > i guess im wrong about that :) The problem is that we need to be able to DMA to/from any address is RAM. On most platforms, the default direct-mapped DMA window is 1GB in size, so we cannot exceed 1GB. It is possible to alter the number, size & placement of such windows so as to increase the amount of RAM one can DMA to/from. I have done this for the 21264s which is why they can have 2GB. Another solution would be to set up temporary scatter/gather dma mappings for all DMA & not just ISA DMA. This would alow memory sizes greater than 4GB. This would require changes to many device drivers and all drivers would need to support this mechanism to be able to use it. I don't see this happening any time soon. Cheers, Drew ------------------------------------------------------------------------------ Andrew Gallatin, Sr Systems Programmer http://www.cs.duke.edu/~gallatin Duke University Email: gallatin@cs.duke.edu Department of Computer Science Phone: (919) 660-6590 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Fri Jan 7 7:44:58 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from sstar.com (sstar.com [209.102.160.1]) by hub.freebsd.org (Postfix) with ESMTP id 8F535156D7 for ; Fri, 7 Jan 2000 07:44:47 -0800 (PST) (envelope-from king@sstar.com) Received: from JKING ([134.132.75.164]) by sstar.com with ESMTP (IPAD 2.52) id 3888400; Fri, 07 Jan 2000 09:44:17 -0600 Message-Id: <4.2.0.58.20000107094134.00a74c90@mail.sstar.com> X-Sender: king@mail.sstar.com X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58 Date: Fri, 07 Jan 2000 09:44:17 -0600 To: De la Cruz Lugo Eric , freebsd-alpha@FreeBSD.ORG From: Jim King Subject: Re: HARDWARE.TXT specific for Alpha? In-Reply-To: References: <14453.62608.509835.123219@grasshopper.cs.duke.edu> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org At 09:32 AM 1/7/2000 -0600, De la Cruz Lugo Eric wrote: >On Fri, 7 Jan 2000, Andrew Gallatin wrote: > > > > > De la Cruz Lugo Eric writes: > > > By the way, some one have information about the memory and storage > limits > > > for FreeBSD on Alpha?, max memory, max file size, thanks in advance. > > > > Max memory currently varies by platform. On most machines it is 1GB > > and on newer 21264 machines it is 2GB. > > > > I'll let somebody else address max file size. I've only gone as high > > as a few 10s of GB myself, but I think the limits should be much higher. > > > > Drew > >Thanks for the info, in X86 Architecture the RAM max size is 4 GB (check >ftp.cdrom configuration :), i thinked that in Alpha should be bigger. > >i guess im wrong about that :) On x86 the maximum memory is also specific to the PC model. e.g. my old Pentium won't accept more than 128 MB; my current Pentium II won't accept more than 768 MB. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Fri Jan 7 9:47: 8 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 2A48014E0B; Fri, 7 Jan 2000 09:47:05 -0800 (PST) (envelope-from mjacob@feral.com) Received: from beppo.feral.com (beppo [192.67.166.79]) by feral.com (8.9.3/8.9.3) with ESMTP id JAA22941; Fri, 7 Jan 2000 09:46:43 -0800 Date: Fri, 7 Jan 2000 09:46:41 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: Andrew Gallatin Cc: De la Cruz Lugo Eric , freebsd-alpha@FreeBSD.ORG, sos@FreeBSD.ORG Subject: Re: HARDWARE.TXT specific for Alpha? In-Reply-To: <14454.1900.901358.626546@grasshopper.cs.duke.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > The problem is that we need to be able to DMA to/from any address is > RAM. On most platforms, the default direct-mapped DMA window is 1GB > in size, so we cannot exceed 1GB. It is possible to alter the number, > size & placement of such windows so as to increase the amount of RAM > one can DMA to/from. I have done this for the 21264s which is why > they can have 2GB. > > Another solution would be to set up temporary scatter/gather dma > mappings for all DMA & not just ISA DMA. This would alow memory sizes > greater than 4GB. This would require changes to many device drivers > and all drivers would need to support this mechanism to be able to use > it. I don't see this happening any time soon. It's easy to enforce this, btw- just remove the alpha_XXX_dmamap so that drivers have to use the busdma map routines instead of the compatibility define of vtophys. This is why I mentioned this to Soren about the so-called 'new' ATA driver (for which he got unbelievingly annoying in return about). This isn't going to happen any time soon as a default- there are too many drivers even in NetBSD which is more stringent about this than FreeBSD that still depend on this. However, we'll probably do something like add an option that says "use large memory" that will force the issue. -matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Fri Jan 7 13:18:37 2000 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 0A9AE157C4 for ; Fri, 7 Jan 2000 13:18:34 -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 WAA06870 for freebsd-alpha@freebsd.org; Fri, 7 Jan 2000 22:06:36 +0100 (MET) Received: (from wilko@localhost) by yedi.iaf.nl (8.9.3/8.9.3) id UAA01167 for freebsd-alpha@freebsd.org; Fri, 7 Jan 2000 20:10:25 +0100 (CET) (envelope-from wilko) Date: Fri, 7 Jan 2000 20:10:25 +0100 From: Wilko Bulte To: FreeBSD-alpha mailing list Subject: weird interrupts? Message-ID: <20000107201025.B614@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 An excerpt from a 2 day old -current on a MiataGL: isa0: on isab0 ata-pci0: irq 238 at device 7.1 o n pci0 ata-pci0: Busmastering DMA supported ata-pci1: irq 239 at device 7.2 o n pci0 ata-pci1: Busmastering DMA not supported ohci0: irq 234 at device 7.3 on pci0 ohci0: could not allocate irq device_probe_and_attach: ohci0 attach returned 12 vga-pci0: at device 12.0 on pci0 pcib1: at device 20.0 on pci0 Aren't the IRQs a bit weird (high)? Wilko -- 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 Jan 7 13:29:34 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 2394B157FA for ; Fri, 7 Jan 2000 13:29:27 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id OAA18089; Fri, 7 Jan 2000 14:29:20 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id OAA88896; Fri, 7 Jan 2000 14:29:20 -0700 (MST) Message-Id: <200001072129.OAA88896@harmony.village.org> To: De la Cruz Lugo Eric Subject: Re: HARDWARE.TXT specific for Alpha? Cc: freebsd-alpha@FreeBSD.ORG In-reply-to: Your message of "Fri, 07 Jan 2000 09:32:58 CST." References: Date: Fri, 07 Jan 2000 14:29:20 -0700 From: Warner Losh Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In message De la Cruz Lugo Eric writes: : Thanks for the info, in X86 Architecture the RAM max size is 4 GB (check : ftp.cdrom configuration :), i thinked that in Alpha should be bigger. No. That's not right. PPro and newer support 36 bits of physical address, which leads to a max size of 64G. The biggest Mobo I've seen for x86 is 8GB (and that was second hand info about a micron server mobo). FreeBSD can't go above 4G w/o rewriting all DMA customers to use bus_dma, which are the network drivers iirc. The pmap layer would also require a fair amount of work as well. But I drift from the charter of this group now :-) Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Fri Jan 7 14: 3:17 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from iteso.mx (iteso.mx [148.201.1.4]) by hub.freebsd.org (Postfix) with ESMTP id 0BF5C158AC for ; Fri, 7 Jan 2000 14:01:38 -0800 (PST) (envelope-from eric@iteso.mx) Received: from localhost (eric@localhost) by iteso.mx (8.9.3/8.9.3) with ESMTP id QAA80124; Fri, 7 Jan 2000 16:01:47 -0600 (CST) (envelope-from eric@iteso.mx) Date: Fri, 7 Jan 2000 16:01:47 -0600 (CST) From: De la Cruz Lugo Eric To: Warner Losh Cc: freebsd-alpha@FreeBSD.ORG Subject: Re: HARDWARE.TXT specific for Alpha? In-Reply-To: <200001072129.OAA88896@harmony.village.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 Yes, in fact i was refering to FreeBSD on x86, where the known limit is 4 GB (unless of course some one think otherwise). taking this, theoretically what its the posible max RAM memory in Alpha? (repeat only in theory). thanks in advance. Eric De La Cruz Lugo Merida, Yucatan, Mexico, The Maya Land On Fri, 7 Jan 2000, Warner Losh wrote: > In message De la Cruz Lugo Eric writes: > : Thanks for the info, in X86 Architecture the RAM max size is 4 GB (check > : ftp.cdrom configuration :), i thinked that in Alpha should be bigger. > > No. That's not right. PPro and newer support 36 bits of physical > address, which leads to a max size of 64G. The biggest Mobo I've seen > for x86 is 8GB (and that was second hand info about a micron server > mobo). FreeBSD can't go above 4G w/o rewriting all DMA customers to > use bus_dma, which are the network drivers iirc. The pmap layer would > also require a fair amount of work as well. But I drift from the > charter of this group now :-) > > Warner > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-alpha" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Fri Jan 7 14: 9:44 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 43EBF158B7 for ; Fri, 7 Jan 2000 14:09:42 -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 OAA23947; Fri, 7 Jan 2000 14:09:35 -0800 Date: Fri, 7 Jan 2000 14:09:31 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: De la Cruz Lugo Eric Cc: Warner Losh , freebsd-alpha@FreeBSD.ORG Subject: Re: HARDWARE.TXT specific for 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 On Fri, 7 Jan 2000, De la Cruz Lugo Eric wrote: > Yes, in fact i was refering to FreeBSD on x86, where the known limit is 4 > GB (unless of course some one think otherwise). > > taking this, theoretically what its the posible max RAM memory in Alpha? > (repeat only in theory). It varies from implementation to implementation. Something on the order of 39 bits. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Fri Jan 7 14:10:23 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 857E2158F6 for ; Fri, 7 Jan 2000 14:10:20 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id PAA18357; Fri, 7 Jan 2000 15:10:18 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id PAA89370; Fri, 7 Jan 2000 15:10:18 -0700 (MST) Message-Id: <200001072210.PAA89370@harmony.village.org> To: De la Cruz Lugo Eric Subject: Re: HARDWARE.TXT specific for Alpha? Cc: freebsd-alpha@FreeBSD.ORG In-reply-to: Your message of "Fri, 07 Jan 2000 16:01:47 CST." References: Date: Fri, 07 Jan 2000 15:10:18 -0700 From: Warner Losh Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In message De la Cruz Lugo Eric writes: : Yes, in fact i was refering to FreeBSD on x86, where the known limit is 4 : GB (unless of course some one think otherwise). FreeBSD/i386 has a limit of 4GB, but the limit for ia32 machines is 64GB. That is, FreeBSD/i386 can run on a 8GB machine, but will only use 4GB of that. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Fri Jan 7 15:42: 0 2000 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 1B5FF14FDA; Fri, 7 Jan 2000 15:41: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 PAA03998; Fri, 7 Jan 2000 15:48:19 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <200001072348.PAA03998@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: "Justin T. Gibbs" Cc: cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org, alpha@FreeBSD.org Subject: Re: cvs commit: src/sys/pci ahc_pci.c src/sys/dev/aic7xxx 93cx6.c aic7xxx.c aic7xxx.h aic7xxx.reg aic7xxx.seq In-reply-to: Your message of "Fri, 07 Jan 2000 15:08:21 PST." <200001072308.PAA31150@freefall.freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 07 Jan 2000 15:48:19 -0800 From: Mike Smith Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > Be more paranoid in how we probe and enable external ram, fast external > ram timing and external ram parity checking. We should now work on > 20ns and 8bit SRAM parts. This incidentally fixes the Alpha Processor Inc. UP2000 board; you still can't boot from the onboard Adaptec controller, but you should be able to use it for secondary disk, and the install kernel won't die on the system anymore. (Booting is an SRM issue that seems unlikely to be fixed anytime soon.) -- \\ 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 Jan 7 21: 7:35 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from noc.nyx.net (noc.nyx.net [206.124.29.3]) by hub.freebsd.org (Postfix) with ESMTP id 8CBFC158CA for ; Fri, 7 Jan 2000 21:07:30 -0800 (PST) (envelope-from amunkres@nyx.net) Received: from nyx10.nyx.net (amunkres@nyx10.nyx.net [206.124.29.2]) by noc.nyx.net (8.9.1a+3.1W/8.9.1/esr) with ESMTP id WAA19176 for ; Fri, 7 Jan 2000 22:07:28 -0700 (MST) Received: from localhost (amunkres@localhost) by nyx10.nyx.net (8.8.8/8.8.8/esr) with SMTP id WAA12099 for ; Fri, 7 Jan 2000 22:07:27 -0700 (MST) X-Nyx-Envelope-Data: Date=Fri Jan 7 22:07:27 2000, Sender=amunkres@nyx.net, Recipient=, Valsender=amunkres@localhost Date: Fri, 7 Jan 2000 22:07:26 -0700 (MST) From: Andrew Munkres X-Sender: amunkres@nyx10 To: freebsd-alpha@freebsd.org Subject: Installing FreeBSD/Alpha on PC164LX from floppy disks 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 successfully booted FreeBSD/Alpha on my PC164LX from floppy disks with the kern.flp and mfsroot.flp images on them. I had intended to install FreeBSD from floppy disks, but when I chose this option on the installation media screen, it told me that there was no floppy drive device. Even though I don't have a FreeBSD CD, I chose the CDROM option out of curiosity, and it said that there was no CDROM drive, even though I do have a SCSI CDROM drive. It did this on both versions 3.4 and 3.3, on both Novice and Custom installation modes. The disk partitioning program recognizes the UWSCSI hard drive correctly. What could be causing the problem? Thanks in advance. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Fri Jan 7 22: 4:32 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from noc.nyx.net (noc.nyx.net [206.124.29.3]) by hub.freebsd.org (Postfix) with ESMTP id 96E1A14F0D for ; Fri, 7 Jan 2000 22:04:30 -0800 (PST) (envelope-from amunkres@nyx.net) Received: from nyx10.nyx.net (amunkres@nyx10.nyx.net [206.124.29.2]) by noc.nyx.net (8.9.1a+3.1W/8.9.1/esr) with ESMTP id XAA19519 for ; Fri, 7 Jan 2000 23:04:30 -0700 (MST) Received: from localhost (amunkres@localhost) by nyx10.nyx.net (8.8.8/8.8.8/esr) with SMTP id XAA13106 for ; Fri, 7 Jan 2000 23:04:28 -0700 (MST) X-Nyx-Envelope-Data: Date=Fri Jan 7 23:04:28 2000, Sender=amunkres@nyx.net, Recipient=, Valsender=amunkres@localhost Date: Fri, 7 Jan 2000 23:04:27 -0700 (MST) From: Andrew Munkres X-Sender: amunkres@nyx10 To: freebsd-alpha@freebsd.org Subject: Re: Installing FreeBSD/Alpha on PC164LX from floppy disks In-Reply-To: <3876D151.911BCB92@pacbell.net> 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 Fri, 7 Jan 2000, ick wrote: > > > Andrew Munkres wrote: > > > I successfully booted FreeBSD/Alpha on my PC164LX from floppy disks with > > the kern.flp and mfsroot.flp images on them. I had intended to install > > FreeBSD from floppy disks, but when I chose this option on the > > installation media screen, it told me that there was no floppy drive > > device. Even though I don't have a FreeBSD CD, I chose the CDROM option > > out of curiosity, and it said that there was no CDROM drive, even though I > > do have a SCSI CDROM drive. It did this on both versions 3.4 and 3.3, on > > both Novice and Custom installation modes. The disk partitioning program > > recognizes the UWSCSI hard drive correctly. What could be causing the > > problem? Thanks in advance. > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-alpha" in the body of the message > > What version SRM do you have? Can you see the CDROM device within the SRM > console? > I have version 5.6-2 of the SRM. (I think that this is the newest version.) The CDROM device is shown when I type show config. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Fri Jan 7 22:36:23 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from panzer.kdm.org (panzer.kdm.org [216.160.178.169]) by hub.freebsd.org (Postfix) with ESMTP id 2355314EE2 for ; Fri, 7 Jan 2000 22:36:20 -0800 (PST) (envelope-from ken@panzer.kdm.org) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id XAA51630; Fri, 7 Jan 2000 23:35:58 -0700 (MST) (envelope-from ken) Date: Fri, 7 Jan 2000 23:35:58 -0700 From: "Kenneth D. Merry" To: Andrew Munkres Cc: freebsd-alpha@FreeBSD.ORG Subject: Re: Installing FreeBSD/Alpha on PC164LX from floppy disks Message-ID: <20000107233558.A51611@panzer.kdm.org> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: ; from amunkres@nyx.net on Fri, Jan 07, 2000 at 10:07:26PM -0700 Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Fri, Jan 07, 2000 at 22:07:26 -0700, Andrew Munkres wrote: > I successfully booted FreeBSD/Alpha on my PC164LX from floppy disks with > the kern.flp and mfsroot.flp images on them. I had intended to install > FreeBSD from floppy disks, but when I chose this option on the > installation media screen, it told me that there was no floppy drive > device. Even though I don't have a FreeBSD CD, I chose the CDROM option > out of curiosity, and it said that there was no CDROM drive, even though I > do have a SCSI CDROM drive. It did this on both versions 3.4 and 3.3, on > both Novice and Custom installation modes. The disk partitioning program > recognizes the UWSCSI hard drive correctly. What could be causing the > problem? Thanks in advance. If I had to guess, it probably said you didn't have a CDROM drive because there was no CD in the drive. Ken -- Kenneth Merry ken@kdm.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Fri Jan 7 22:43:44 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from mail.cybcon.com (mail.cybcon.com [216.190.188.5]) by hub.freebsd.org (Postfix) with ESMTP id 4734515259 for ; Fri, 7 Jan 2000 22:43:43 -0800 (PST) (envelope-from freebsd@cybcon.com) Received: from laptop.cybcon.com (william@usr1-5.cybcon.com [205.147.75.6]) by mail.cybcon.com (8.9.3/8.9.3) with ESMTP id WAA11352 for ; Fri, 7 Jan 2000 22:43:39 -0800 (PST) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Date: Fri, 07 Jan 2000 22:44:59 -0800 (PST) From: William Woods To: freebsd-alpha@freebsd.org Subject: 56k external modem on an Alpha...... Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Does anyone here have a 56k modem (external) on their alpha and get decent connect speeds useing 4.0-current? I tried it a while back, about 6 months, but got sio overflows at any speed over 9600bps. ---------------------------------- E-Mail: William Woods Date: 07-Jan-00 Time: 22:43:27 FreeBSD 3.4 ---------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Fri Jan 7 23:13: 1 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from noc.nyx.net (noc.nyx.net [206.124.29.3]) by hub.freebsd.org (Postfix) with ESMTP id 0B81315887 for ; Fri, 7 Jan 2000 23:12:59 -0800 (PST) (envelope-from amunkres@nyx.net) Received: from nyx10.nyx.net (amunkres@nyx10.nyx.net [206.124.29.2]) by noc.nyx.net (8.9.1a+3.1W/8.9.1/esr) with ESMTP id AAA19889 for ; Sat, 8 Jan 2000 00:12:57 -0700 (MST) Received: from localhost (amunkres@localhost) by nyx10.nyx.net (8.8.8/8.8.8/esr) with SMTP id AAA14272 for ; Sat, 8 Jan 2000 00:12:56 -0700 (MST) X-Nyx-Envelope-Data: Date=Sat Jan 8 00:12:56 2000, Sender=amunkres@nyx.net, Recipient=, Valsender=amunkres@localhost Date: Sat, 8 Jan 2000 00:12:56 -0700 (MST) From: Andrew Munkres X-Sender: amunkres@nyx10 To: freebsd-alpha@freebsd.org Subject: Re: Installing FreeBSD/Alpha on PC164LX from floppy disks In-Reply-To: <20000107233558.A51611@panzer.kdm.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Fri, 7 Jan 2000, Kenneth D. Merry wrote: > On Fri, Jan 07, 2000 at 22:07:26 -0700, Andrew Munkres wrote: > > I successfully booted FreeBSD/Alpha on my PC164LX from floppy disks with > > the kern.flp and mfsroot.flp images on them. I had intended to install > > FreeBSD from floppy disks, but when I chose this option on the > > installation media screen, it told me that there was no floppy drive > > device. Even though I don't have a FreeBSD CD, I chose the CDROM option > > out of curiosity, and it said that there was no CDROM drive, even though I > > do have a SCSI CDROM drive. It did this on both versions 3.4 and 3.3, on > > both Novice and Custom installation modes. The disk partitioning program > > recognizes the UWSCSI hard drive correctly. What could be causing the > > problem? Thanks in advance. > > If I had to guess, it probably said you didn't have a CDROM drive because > there was no CD in the drive. Its exact words are "No CDROM devices found! Please check that your system's is correct and that the CDROM drive is of a supported type. For more information, consult the hardware guide in the Doc menu." However, I don't really care about this since I don't have a FreeBSD CD. Was the kernel in kern.flp compiled with "controller fdc0" so that it can see the floppy drive, or was this left out for some reason? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Sat Jan 8 2:36: 1 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from tccn.cs.kun.nl (tccn.cs.kun.nl [131.174.32.38]) by hub.freebsd.org (Postfix) with ESMTP id 29C0514DD8 for ; Sat, 8 Jan 2000 02:35:58 -0800 (PST) (envelope-from sparky@cs.kun.nl) Received: from cs.kun.nl (sirius.cs.kun.nl [131.174.33.213]) by tccn.cs.kun.nl (8.9.2/8.9.2) with ESMTP id LAA66129 for ; Sat, 8 Jan 2000 11:35:25 +0100 (CET) (envelope-from sparky@cs.kun.nl) Message-ID: <3877130C.EEAAE7A1@cs.kun.nl> Date: Sat, 08 Jan 2000 11:35:56 +0100 From: Franc Grootjen Organization: University of Nijmegen X-Mailer: Mozilla 4.61 [en] (X11; I; FreeBSD 3.2-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-alpha@freebsd.org Subject: Strange (random?) cc1plus hang in 4.0-current snapshot 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 installed 4.0-19991031-CURRENT on my AXPpci33 machine, and it works like a charm. I recompiled several ports, but keep getting problems when building c++ related packages like for instance kde. At totally unpredictable moments (say once in the 6 source files) the make process hangs showing no activity whatsoever. After ^C and another make the building process resumes (with the same source file) but will hang agains after 4-8 source files. Every `hang' produces a cc1plus process doing nothing. Hope someone can help me out. Please reply to sparky@cs.kun.nl, since I'm not on the list (yet!) Franc To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Sat Jan 8 12:48:56 2000 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 2691314D68 for ; Sat, 8 Jan 2000 12:48:44 -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 VAA28059 for freebsd-alpha@freebsd.org; Sat, 8 Jan 2000 21:42:04 +0100 (MET) Received: (from wilko@localhost) by yedi.iaf.nl (8.9.3/8.9.3) id VAA02156 for freebsd-alpha@freebsd.org; Sat, 8 Jan 2000 21:45:01 +0100 (CET) (envelope-from wilko) Date: Sat, 8 Jan 2000 21:45:01 +0100 From: Wilko Bulte To: FreeBSD-alpha mailing list Subject: first shot at AlphaHW.txt / please review... Message-ID: <20000108214500.A2099@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 Hi 'list', Please find below my first shot at the AlphaHW.txt file that I'm compiling. For obvious reasons I have started with systems that I am familiar with myself. Please review it for usability, paying particular attention to <> marked sections. If you are familiar with a system that is not yet listed please write up your part of the story so that I can include it in the AlphaHW.txt Cheers, Wilko ------- FreeBSD/alpha Hardware Information ================================== This file is maintained by Wilko Bulte Additions, corrections and constructive criticism are invited. Sat Jan 8 21:41:43 CET 2000 What do you need to run FreeBSD/alpha? -------------------------------------- Obviously you will need an Alpha machine that FreeBSD/alpha knows about. Alpha machines are NOT PC-architectures. There are considerable differences between the various chipsets and mainboard designs. This means that a kernel needs to know the intimate details of a particular machine before it can run on it. Throwing some odd GENERIC kernel at unknown hardware is almost guaranteed to fail miserably. For a machine even to be considered for FreeBSD use please make sure it has the SRM console firmware installed. Or at least make sure that SRM console firmware is available for this particular model. Machines with the ARC/AlphaBIOS console firmware are intended for WindowsNT, some of them have SRM firmware available in the system ROMs which you only have to select (via an ARC/AlphaBIOS menu). In other cases you will have to re-flash the ROMs with SRM code. In any case: no SRM -> no FreeBSD (or NetBSD, OpenBSD, Tru64 Unix or OpenVMS for that matter). There is another pitfall ahead: you will need a disk adapter that the SRM console recognises in order to be able to boot from your disk. For PCI SCSI this means you will need either a NCR/Symbios 810 based adapter, or a Qlogic 1020/1040 based adapter. Some machines come with a SCSI chip embedded on the mainboard. Some SRM versions (depends on the mainboard) can also boot from IDE disks. As I'm a SCSI-only guy I invite comments on 'GO/NOGO' here <> This problem might bite those who have machines that started it's life as a WinNT box. The ARC/AlphaBIOS knows about *other* adapters that it can boot from than the SRM. For example you can boot from an Adaptec 2940UW with ARC but not with SRM. Some adapters that cannot be booted from work fine for data-only disks (e.g. Adaptec 2940x boards). The differences between SRM and ARC could also get you IDE CDROMs and harddrives in some systems. You better check Alpha machines can generally be run (with SRM..) on a graphics console or on a serial console. ARC does not like serial consoles. If you want to run your Alpha without a monitor/graphics card just don't connect a keyboard/mouse to the machine. Instead hook up a serial terminal[emulator] to serial port #1. The SRM will talk 9600N81 to you. This is really practical for debugging purposes. For Alpha CPUs you will find multiple versions. The original Alpha design is the 21064. It was produced in a chip baking process called MOS4, chips made in this process are nicknamed EV4. Newer CPUs are 21164, 21264 etc. You will see designations like EV4S, EV45, EV5, EV56, EV6, EV67. The higher the EV number the more desirable (read: faster / more modern). For memory you want at least 32Mbytes. I have seen FreeBSD/alpha run on a 16Mbyte system but you will not like that. Note that the SRM steals 2Mbyte from the total system memory. For more serious use >= 64Mbyte is recommended. Model specific information -------------------------- Below is an overview of the hardware that FreeBSD/alpha is capable of running on. This list is bound to grow, a look in /sys/alpha/conf/GENERIC can be enlightening. Alpha models are often best known by their project codename, these are listed below in (). * * AXPpci33 ("NoName") * The NoName is a baby-AT mainboard based on the 21066 LCA (Low Cost Alpha) processor. It was originally designed for OEM-use. The LCA chip includes almost all of the logic to drive a PCI/AT bus. This makes for a low-priced design. Due to the limited memory interface the system is not particularly fast in case of cache misses. Features: - 21066 Alpha CPU at 166/233Mc (21068 CPUs are also possible, but are even slower. Never seen/used one) - memory bus: 64 bits - onboard cache: 0, 256k or 1Mbyte (uses DIL chips) - PS/2 mouse & keyboard port OR 5pin DIN keyboard (2 mainboard models) - memory: PS/2 style 72 pin 36bit Fast Page Mode SIMMs, 70ns or better, installed in pairs of 2, 4 SIMM sockets uses ECC - 512kB FlashROM for the console code. - 2x 16550A serial ports, 1x parallel port, floppy interface - 1x embedded IDE interface - expansion: 3 32 bit PCI slots (1 shared with ISA) 5 ISA slots (1 shared with PCI) - embedded FastSCSI using an NCR/Symbios 810 chip NoName's can either have SRM *or* ARC console firmware in their FlashROM. The FlashROM is not big enough to hold both ARC and SRM at the same time and allow software selection of alternate console code. But you need SRM only anyway. Cache for the NoNames are 15 or 20ns DIL chips. For a 256kByte cache you want to check your junked 486 mainboard. Chips for a 1Mbyte cache are a rare breed unfortunately. Getting at least a 256kByte cache is recommended performance wise. Cacheless they are really slow. The NoName comes with a power connector 3.3Volts. No need to rush out to get a new power supply. An ordinary AT-style power supply will work just fine as long as you don't use 3.3V PCI option cards. SRM presumably cannot boot from IDE disks (have never tried this myself) <> Make sure you use true 36 bit SIMMs, and only FPM (Fast Page Mode). EDO RAM or SIMMs with fake parity will not work (the board uses the 4 extra bits for ECC!). This is the #1 problem that people encounter with NoNames. The OEM manual is recommended reading. If you did not get one with your system/board send me email, I have a Postscript copy. The kernel configuration file for a NoName kernel must contain: options DEC_AXPPCI_33 * * Universal Desktop Box (UDB or "Multia") * Note: Multia can be either Intel or Alpha CPU based. We assume Alpha based Multias here for obvious reasons. Multia is a very compact 21066 based box, rougly 40cm square and 8 cm thick. It has a small 2.5" SCSI disk of 300Mbyte or so. Fortunately there is an external high density 50pin SCSI connector. It has an embedded 10Mbit Ethernet interface. There is only one PCI slot for expansion, and only for a small PCI card too. The CPU is either 166 or 233 Mc. It comes with a TGA based graphics onboard. The 3.5" floppy drive is a very compact laptop variant. Multias are somewhat notorious for dying of heat strokes. The very compact box does not really allow cooling very well. Please use the Multia on it's vertical stand, don't put it horizontally ('pizza style'). Most the discussion of the NoName applies to Multia too. The kernel configuration file for a Multia kernel must contain: options DEC_AXPPCI_33 * * Personal Workstation ("Miata") * The Miata is a small tower machine intended to be put under a desk. There are multiple Miata variants. The original Miata is the MX5 model. Because it suffers from a number of hardware design flaws an ECO was performed, yielding the MiataGL. Unfortunately the boxes are identical for both variants. An easy check if to see if the back of the machine sports two USB connectors. If yes, it is a MiataGL Features: - 21164 EV5 Alpha CPU, at 433, 500 or 600Mc [MX5] - 21164A EV56 Alpha CPU, at 433, 500 or 600Mc [MiataGL] - 2117x Core Logic ("Pyxis") chipset - onboard cache: 0, 2, 4Mbyte (uses a cache module) - memory bus: 128 bits wide, ECC protected - memory: Miata uses unbuffered SDRAMs, installed in pairs of 2 - onboard Fast Ethernet, the bulkhead can be 10/100 UTP, or 10 UTP/BNC (MX5 uses a 21142 ethernetchip, MiataGL has a 21143 chip) - 2x onboard IDE (MX5: CMD 646, MiataGL: Cypress 82C693) - 1x UltraWide SCSI Qlogic 1040 [MiataGL only] - expansion: 2 64-bit PCI slots 3 32-bit PCI slots (behind a PCI-PCI bridge chip) 3 ISA slots (physically shared with the 32 bit PCI slots, via a Intel 82378IB PCI to ISA bridge) - 2x 16550A serial port - 1x parallel port <> - PS/2 keyboard & mouse port - USB interface [MiataGL only] CPU mainboard and PCI 'riser' board: the Miata is divided into two printed circuit boards. The lower board in the bottom of the machine has the PCI and ISA slots and things like the sound chip etc. The top board has the CPU, the Pyxis chip, memory etc. Note that MX5 and the MiataGL use a different PCI riser board. This means that you cannot just upgrade to a MiataGL CPU board (with the newer Pyxis chip) but that you will also need a different riser board. Everything else (cabinet, wiring etc etc) is identical for MX5 and MiataGL. DMA bug: MX5 has problems with DMA via the 2 64-bit PCI slots when this DMA crosses a page boundary. The 32bit slots don't have this problem because the PCI-PCI bridge chip does not allow the offending transfers. The SRM code knows about the problem and refuses to start the system if there is a PCI card in one of the 64bit slots that it does not know about. Cards that are 'known good' to the SRM are allowed to be used in the 64bit slots. If you want to fool the SRM you can type "set pci_device_override 88c15333" at the >>> SRM prompt. This example assumes the PCI ID of your PCI card is 88c15333, use the right valua for your card. The kernel reports it when it sees a buggy Pyxis chip: Sep 16 18:39:43 miata /kernel: cia0: Pyxis, pass 1 Sep 16 18:39:43 miata /kernel: cia0: extended capabilities: 1 Sep 16 18:39:43 miata /kernel: cia0: WARNING: Pyxis pass 1 DMA bug; no bets... A MiataGL probes as: Jan 3 12:22:32 miata /kernel: cia0: Pyxis, pass 1 Jan 3 12:22:32 miata /kernel: cia0: extended capabilities: 1 Jan 3 12:22:32 miata /kernel: pcib0: <2117x PCI host bus adapter> on cia0 MiataGL does not have the DMA problems of the MX5. PCI cards that make the MX5 SRM choke when installed in the 64bit slots are accepted without problems by the MiataGL SRM. Sound: both MX5 and MiataGL have an onboard sound chip, an ESS1887 and an ESS1888 respectively. I have yet to see/hear it work on my MiataGL. Cache: when your Miata has an optional cache board installed make sure it is firmly seated. A slightly loose cache has been observed to cause weird crashes (not surprising obviously, but maybe not so obvious when troubleshooting). The kernel configuration file for a Miata kernel must contain: options DEC_ST550 # Personal Workstation 433, 500, 600 * * DEC3000 family (the "Bird" machines) * The DEC3000 series were among the first Alpha machines ever produced. They are based on a proprietary I/O bus, the TurboChannel (TC) bus. These machines are built like tanks (watch your back). They are quite fast (considering their age) thanks to the good memory design. DEC3000 can be subdivided in DEC3000/500-class and DEC3000/300-class. The DEC3000/500-class is the early high-end workstation/server Alpha family. Servers use serial consoles, workstations have graphics tubes. They are called 'Birds' because their internal DEC codenames were bird names: DEC3000/400 'Sandpiper' 133Mc CPU, desktop DEC3000/500 'Flamingo' 150Mc CPU, floorstanding DEC3000/600 ' ? ' 175Mc CPU, desktop DEC3000/700, DEC3000/800, DEC3000/900, DEC3000/300 'Pelican' different variations, workstation class Features: - 21064 CPU (speeds varying between 133 and 200Mc) - memory bus: 256 bit, with ECC - memory: proprietary SIMMs (DEC3000/300 has different memory SIMMs) used in sets of 8 - builtin 10Mbit ethernet based on a Lance 7990 chip - one or two SCSI buses based on a NCR53C94 chip - 2 serial ports (one usable as a serial console) - embedded ISDN interface Currently DEC3000 machines can only be used diskless on FreeBSD/alpha. The reason for this is that the SCSI drivers needed for the TC SCSI adapters were not brought into CAM that the current FreeBSD versions use. ISDN interface does not work on FreeBSD (to be honest I don't think there is any operating system, including Tru64 Unix, that can use it). Birds can be obtained from surplus sales etc. As they are not PCI based they are no longer actively maintained. TC expansion boards can be difficult to obtain these days and support for them is not too good unless you write/debug the code yourself. Be prepared to run a serial console on the Birds. For the DEC3000/[4-9]00 series machines the kernel config file must contain: options DEC_3000_500 For the DEC3000/300 ("Pelican") machines the kernel config file must contain: options DEC_3000_300 * *Evaluation Board 64plus ("EB64+"), Aspen Alpine * In it's attempts to popularise the Alpha CPU DEC produced a number of so called Evaluation Boards. The EB64+ family boards have the following feature set: - 21064 or 21064A CPU, 150 to 275Mc - memory bus: 128 bit - memory: PS/2 style 72 pin 36bit Fast Page Mode SIMMs, 70ns or better, installed in pairs of 2, 8 SIMM sockets uses parity - cache: 512 kByte, 1 Mbyte or 2 Mbyte - 21072 chipset - Intel 82378ZB PCI to ISA bridge chip ('Saturn') - dual 16550A serial ports - 53C810 FastSCSI - embedded 10Mbit Ethernet - 2 PCI slots - 3 ISA slots The SRM console code is housed in an UV-erasable EPROM. No easy flash SRM upgrades for the EB64+ Aspen Alpine is slightly different, but is close enough to the EB64+ to run an EB64+ SRM EPROM (mine does..). The Aspen Alpine does not have an embedded Ethernet, has 3 instead of 2 PCI slots. For the EB64+ class machines the kernel config file must contain: options DEC_EB64PLUS Acknowledgements ---------------- In compiling this file I used multiple information sources, but http://www.netbsd.org proved to be an invaluable source of information. If it wasn't for NetBSD/alpha there probably would not be a FreeBSD/alpha in the first place. -- 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 Sat Jan 8 19:58:57 2000 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 30E1214DCD for ; Sat, 8 Jan 2000 19:58:51 -0800 (PST) (envelope-from raymond@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 NAA09858 for freebsd-alpha@FreeBSD.ORG; Sun, 9 Jan 2000 13:58:47 +1000 (EST) (envelope-from raymond@one.com.au) Date: Sun, 9 Jan 2000 13:58:47 +1000 (EST) From: User Raymond Message-Id: <200001090358.NAA09858@gw.one.com.au> Subject: 56k external modem on an Alpha...... Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org To: freebsd-alpha@FreeBSD.ORG > Does anyone here have a 56k modem (external) on their alpha and get decent > connect speeds useing 4.0-current? I tried it a while back, about 6 months, > but got sio overflows at any speed over 9600bps. If it's one of the "smaller" alphas that dual use the COM1 as an alternate console, it's not FreeBSD, it's the hardware. We have used there things with VMS for years and COM1 is always limited. Seems all trafic goes via the SRM code as this "may" be used as a console. Basically, don't use COM1 unless you have to. Ray Newman To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message