From owner-freebsd-alpha Sun Feb 14 07:49:19 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA06872 for freebsd-alpha-outgoing; Sun, 14 Feb 1999 07:49:19 -0800 (PST) (envelope-from owner-freebsd-alpha@FreeBSD.ORG) Received: from set.spradley.tmi.net (set.spradley.tmi.net [207.170.107.99]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA06865 for ; Sun, 14 Feb 1999 07:49:02 -0800 (PST) (envelope-from tsprad@set.spradley.tmi.net) Received: from set.spradley.tmi.net (localhost [127.0.0.1]) by set.spradley.tmi.net (8.8.8/8.8.8) with ESMTP id JAA01133; Sun, 14 Feb 1999 09:48:36 -0600 (CST) (envelope-from tsprad@set.spradley.tmi.net) Message-Id: <199902141548.JAA01133@set.spradley.tmi.net> X-Mailer: exmh version 2.0.2 2/24/98 To: Hans Huebner cc: Simon Shapiro , freebsd-alpha@FreeBSD.ORG, Doug Rabson Subject: Re: X11 - Again... In-reply-to: Your message of "Sat, 13 Feb 1999 09:48:17 +0100." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 14 Feb 1999 09:48:35 -0600 From: Ted Spradley Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > it is as simple as that: The patches work with XFree-3.3.3.1 without > any problem. They will not (not!) work with older versions. To use > them, you need the current x11/XFree86 port. Please make sure that > your Makefile is: > > # $Id: Makefile,v 1.52 1999/01/27 18:32:15 fenner Exp $ > > If all this is given, patch --index-first will give no errors whatsoever, > the build will run completely fine and you'll get a useable SVGA server. Thanks! This was the clue I needed. It turns out that there was something messed up in my mirror of the CVS repository and my cvsup cron job was aborting. Since ports/x11 is at the very end, it wasn't updated even though everything else I use was just fine. > > Note that the server starts up in 8 bpp mode unless you explicitly tell > it to use 16 bits on the command line. 8 bit mode is broken, as mentioned > on the web page. > > -Hans > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Tue Feb 16 18:36:18 1999 Delivered-To: freebsd-alpha@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id 6B5711114E for ; Tue, 16 Feb 1999 18:34:29 -0800 (PST) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.1/8.9.1) with ESMTP id SAA09241 for ; Tue, 16 Feb 1999 18:34:29 -0800 (PST) (envelope-from jdp@polstra.com) Received: (from jdp@localhost) by vashon.polstra.com (8.9.2/8.9.1) id SAA97257 for alpha@freebsd.org; Tue, 16 Feb 1999 18:34:29 -0800 (PST) (envelope-from jdp@polstra.com) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Date: Tue, 16 Feb 1999 18:34:29 -0800 (PST) Organization: Polstra & Co., Inc. From: John Polstra To: alpha@freebsd.org Subject: CVSup-16.0 for FreeBSD/Alpha Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I've created FreeBSD/Alpha binaries for CVSup-16.0. You'll find them here: http://www.freebsd.org/~jdp/cvsup-alpha/ These are just like the i386 binary releases, except the executables are for the Alpha. John --- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Nobody ever went broke underestimating the taste of the American public." -- H. L. Mencken To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Wed Feb 17 12:59:58 1999 Delivered-To: freebsd-alpha@freebsd.org Received: from mailc.telia.com (mailc.telia.com [194.22.190.4]) by hub.freebsd.org (Postfix) with ESMTP id 5FF551120E for ; Wed, 17 Feb 1999 12:59:47 -0800 (PST) (envelope-from khaled@mailbox.telia.net) Received: from mailbox.telia.net (khaled@mailbox.telia.net [194.237.170.234]) by mailc.telia.com (8.8.8/8.8.8) with ESMTP id VAA09166 for ; Wed, 17 Feb 1999 21:59:42 +0100 (CET) Received: from localhost (khaled@localhost) by mailbox.telia.net (8.9.1/8.8.5) with SMTP id VAA01218 for ; Wed, 17 Feb 1999 21:59:44 +0100 (CET) Date: Wed, 17 Feb 1999 21:59:44 +0100 (CET) From: Khaled Daham To: freebsd-alpha@freebsd.org Subject: Problems with booting kern.flp Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hello! I have a problem with the kern.flp from the 3.1-REL on my alpha164LX , when I try to boot from the dd'ed kern.flp floppy the SRM gives me this (boot dva0.0.0.0.0 -flags 0) block 0 of dva0.0.0.0 is not a valid boot block bootstrap failure however I found a kern.flp(boot.flp) from www.freebsd.orf/~msmith which worked, but it is abit old (Oct 23).Isnt the kern.flp in 3.1-REL supposed to be bootable on an alpha system ? or is there some special trick to get it to work ?I run SRM v5.3-3. /Khaled, Telia Network Services Mail: khaled@telia.net Cell: 070-6785492 Work: 08-4567281 :hacker: /n./ [originally, someone who makes furniture with an axe] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Thu Feb 18 1:49:49 1999 Delivered-To: freebsd-alpha@freebsd.org Received: from herring.nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (Postfix) with ESMTP id 6BD2C112D5 for ; Thu, 18 Feb 1999 01:49:01 -0800 (PST) (envelope-from dfr@nlsystems.com) Received: from localhost (dfr@localhost) by herring.nlsystems.com (8.9.2/8.8.8) with ESMTP id JAA63698; Thu, 18 Feb 1999 09:48:36 GMT (envelope-from dfr@nlsystems.com) Date: Thu, 18 Feb 1999 09:48:36 +0000 (GMT) From: Doug Rabson To: Khaled Daham Cc: freebsd-alpha@freebsd.org Subject: Re: Problems with booting kern.flp In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Wed, 17 Feb 1999, Khaled Daham wrote: > Hello! > > I have a problem with the kern.flp from the 3.1-REL on my alpha164LX , > when I try to boot from the dd'ed kern.flp floppy the SRM gives me > this > > (boot dva0.0.0.0.0 -flags 0) > block 0 of dva0.0.0.0 is not a valid boot block > bootstrap failure > > however I found a kern.flp(boot.flp) from www.freebsd.orf/~msmith which > worked, but it is abit old (Oct 23).Isnt the kern.flp in 3.1-REL supposed > to be bootable on an alpha system ? or is there some special trick to get > it to work ?I run SRM v5.3-3. > > /Khaled, Telia Network Services > > Mail: khaled@telia.net > Cell: 070-6785492 > Work: 08-4567281 > > :hacker: /n./ [originally, someone who makes furniture with an axe] I thought the 3.1-RELEASE directory contained only the i386 release (shouldn't this be x.x-RELEASE/i386 or something). You should consider trying a 3.x snapshot from ftp://ftp.cdrom.com/pub/FreeBSD/releases/snapshots/alpha. -- 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 Feb 18 14:32: 2 1999 Delivered-To: freebsd-alpha@freebsd.org Received: from set.spradley.tmi.net (set.spradley.tmi.net [207.170.107.99]) by hub.freebsd.org (Postfix) with ESMTP id 1395711780 for ; Thu, 18 Feb 1999 14:31:58 -0800 (PST) (envelope-from tsprad@set.spradley.tmi.net) Received: from set.spradley.tmi.net (localhost [127.0.0.1]) by set.spradley.tmi.net (8.8.8/8.8.8) with ESMTP id QAA11232 for ; Thu, 18 Feb 1999 16:31:57 -0600 (CST) (envelope-from tsprad@set.spradley.tmi.net) Message-Id: <199902182231.QAA11232@set.spradley.tmi.net> X-Mailer: exmh version 2.0.2 2/24/98 To: freebsd-alpha@FreeBSD.ORG Subject: xdm doesn't work Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 18 Feb 1999 16:31:57 -0600 From: Ted Spradley Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Has anyone got xdm working? If I run startx from a root shell the X server comes up just fine, with working xterms, but when I run xdm the screen switches modes, draws the background, then goes blank and then back to the vty. The xdm process is still there, but no X server process, and no clue in the xdm-errors file. This is 4.0 current as of last week, with XFree86 built from the port with Doug Rabson's patch, running on an AS200-4/233 with a Diamond S3 Trio64 board and the XF86_S3 server. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Thu Feb 18 15: 7: 2 1999 Delivered-To: freebsd-alpha@freebsd.org Received: from herring.nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (Postfix) with ESMTP id D304311A64 for ; Thu, 18 Feb 1999 15:06:51 -0800 (PST) (envelope-from dfr@nlsystems.com) Received: from localhost (dfr@localhost) by herring.nlsystems.com (8.9.2/8.8.8) with ESMTP id XAA65808; Thu, 18 Feb 1999 23:06:55 GMT (envelope-from dfr@nlsystems.com) Date: Thu, 18 Feb 1999 23:06:54 +0000 (GMT) From: Doug Rabson To: Ted Spradley Cc: freebsd-alpha@freebsd.org Subject: Re: xdm doesn't work In-Reply-To: <199902182231.QAA11232@set.spradley.tmi.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 Thu, 18 Feb 1999, Ted Spradley wrote: > Has anyone got xdm working? If I run startx from a root shell the X > server comes up just fine, with working xterms, but when I run xdm the > screen switches modes, draws the background, then goes blank and then > back to the vty. The xdm process is still there, but no X server > process, and no clue in the xdm-errors file. > > This is 4.0 current as of last week, with XFree86 built from the port > with Doug Rabson's patch, running on an AS200-4/233 with a Diamond S3 > Trio64 board and the XF86_S3 server. I haven't tried it to be honest. I tried kdm once which put up a login dialog but refused to start a session. I never managed to find the time to debug it though. I suggest recompiling xdm with debug information and digging in with gdb :-) -- 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 Feb 18 15:11:48 1999 Delivered-To: freebsd-alpha@freebsd.org Received: from sun-sparc1.infoglobe.com (mail.infoglobe.com [38.216.162.162]) by hub.freebsd.org (Postfix) with ESMTP id E865B11AD7 for ; Thu, 18 Feb 1999 15:10:06 -0800 (PST) (envelope-from jhermes@infoglobe.com) Received: from kenny ([38.216.162.189]) by sun-sparc1.infoglobe.com (Post.Office MTA v3.1 release PO203a ID# 560-34435U100L100S0) with SMTP id AAA26682 for ; Thu, 18 Feb 1999 18:09:16 -0500 Message-ID: <001201be5b93$8828fbe0$bda2d826@kenny.infoglobe.com> From: "John S. Hermes" To: Subject: Post install questions Date: Thu, 18 Feb 1999 18:08:01 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.2106.4 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.2106.4 Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hello, I installed 3.0-19990114-SNAP/alpha on my DEC PW433au today after failing twice with 4.0-19990206-SNAP/alpha (cp, ls et al gave wierd parser errors when invoked). Anyway, I notice that the 3.0 SNAP install ignored my partition sizes and made my / (root) 31Mb, instead of the 150Mb that I wanted. Needless to say, that makes that particular partition 96% full (ouch). I'll install to da1 and boot there manually until I can relabel and format da0. Does the install program have hard-coded partition sizes? The install program also did not detect my IDE CD-ROM (I hope the reason is IDE CD-ROM support is not in GENERIC kernel), so I had to do a network install (anybody need a custom burned SNAP CD?). Will the ATAPI option in the kernel conf work for Alpha like it does for Intel? Anybody with a tuned kernel config for a DEC PW433au, I sure would appreciate a copy! Thanks! John Hermes jhermes@infoglobe.com Infoglobe, Inc. (937) 225-9999 x317 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Thu Feb 18 16:42:44 1999 Delivered-To: freebsd-alpha@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 717C111C0C; Thu, 18 Feb 1999 16:42:18 -0800 (PST) (envelope-from mjacob@feral.com) Received: from localhost (mjacob@localhost) by feral.com (8.8.7/8.8.7) with ESMTP id QAA24996; Thu, 18 Feb 1999 16:42:06 -0800 Date: Thu, 18 Feb 1999 16:42:06 -0800 (PST) From: Matthew Jacob X-Sender: mjacob@feral-gw Reply-To: mjacob@feral.com To: satoshi@freebsd.org Cc: alpha@freebsd.org Subject: where should changes to patches go that we find for the alpha platform? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org If we find and fix patches for ports that are for alpha, where should they be sent? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Sat Feb 20 8:29: 9 1999 Delivered-To: freebsd-alpha@freebsd.org Received: from callisto.fortean.com (callisto.fortean.com [209.42.229.241]) by hub.freebsd.org (Postfix) with ESMTP id AA41411553 for ; Sat, 20 Feb 1999 08:29:04 -0800 (PST) (envelope-from walter@fortean.com) Received: from localhost (walter@localhost) by callisto.fortean.com (8.8.8/8.8.5) with SMTP id LAA13402 for ; Sat, 20 Feb 1999 11:27:03 -0500 (EST) X-Authentication-Warning: callisto.fortean.com: walter owned process doing -bs Date: Sat, 20 Feb 1999 11:27:02 -0500 (EST) From: "Bruce M. Walter" To: freebsd-alpha@freebsd.org Subject: 3.1/4.0, the alpha, and a dog named blue... Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hello all, I've been running FreeBSD on several alpha's now for about two months. I'm elated that I no longer have to kiss the arse of the Linux god to get useful CPU cycles out of these machines. Thanks all for the hard work and a hearty job well-done the the alpha porters. I realized I may get flamed for asking something like this, but since I honestly don't know, I'm gonna ask: Where should a person looking to get relatively stable (read -stable ;) performance from an alpha be? I know the answer may still be 'not on FreeBSD' at this point, but I've been very impressed with the stability of the last few snaps. I'm really wondering whether new bug-fixes/enhancements/functionality in the alpha stuff is finding it's way back into the -stable branch, as all of the latest snap's are from -current which has had some ffs/vm related problems of late. If it's just a matter of taking the last 3.x alpha snap and tracking -stable via CVS that's fine, it's just not apparent that that's the "Right Thing to Do" (tm). Cheers all and thanks for the guidance! - Bruce ______________________ Bruce M. Walter, Principal NIXdesign Group Inc. 426 S. Dawson Street Raleigh NC 27601 USA 919.829.4901 Tel 919.829.4993 Fax http://www.nixdesign.com Visual communications | concept + code To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Sat Feb 20 8:48:25 1999 Delivered-To: freebsd-alpha@freebsd.org Received: from callisto.fortean.com (callisto.fortean.com [209.42.229.241]) by hub.freebsd.org (Postfix) with ESMTP id D468710E5B for ; Sat, 20 Feb 1999 08:48:21 -0800 (PST) (envelope-from walter@fortean.com) Received: from localhost (walter@localhost) by callisto.fortean.com (8.8.8/8.8.5) with SMTP id LAA13442; Sat, 20 Feb 1999 11:46:18 -0500 (EST) X-Authentication-Warning: callisto.fortean.com: walter owned process doing -bs Date: Sat, 20 Feb 1999 11:46:17 -0500 (EST) From: "Bruce M. Walter" To: Adam Furman Cc: freebsd-alpha@freebsd.org Subject: Re: 3.1/4.0, the alpha, and a dog named blue... In-Reply-To: <19990220113401.A7335@delsol.sunfire.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 > I want to know how stable is FreeBSD on the Alpha platform. I have an > AlphaStation 200 which I want to place FreeBSD on and get RID of RedHat > Linux. I'm not a linux fan and love the FreeBSD platform. Adam, I've not personally had experience with the AlphaStation 200, so I've copied the list on your question. I've got access to Multia's and a Personal Workstation 533au. YMMV, but aside from getting used to tracking down 'converting pointer to integer of differing size' compiler warnings, I've not noticed any real show stoppers in the last month. My machines exhibit almost all of the stability and functionality of the x86 releases. I am currently running 4.0-19990206-SNAP on everything. My ideal setup would be to track -current on the Multia's and -stable on the 533au, using it as an internal samba/nfs/cvs/web server. Things seem real solid under testing, but I've been reluctant to put the 533au into production. Hope this helps somewhat. - Bruce ______________________ Bruce M. Walter, Principal NIXdesign Group Inc. 426 S. Dawson Street Raleigh NC 27601 USA 919.829.4901 Tel 919.829.4993 Fax http://www.nixdesign.com Visual communications | concept + code To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Sat Feb 20 9:47:35 1999 Delivered-To: freebsd-alpha@freebsd.org Received: from herring.nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (Postfix) with ESMTP id 9CC01111D2 for ; Sat, 20 Feb 1999 09:47:29 -0800 (PST) (envelope-from dfr@nlsystems.com) Received: from localhost (dfr@localhost) by herring.nlsystems.com (8.9.3/8.8.8) with ESMTP id RAA53678; Sat, 20 Feb 1999 17:47:26 GMT (envelope-from dfr@nlsystems.com) Date: Sat, 20 Feb 1999 17:47:26 +0000 (GMT) From: Doug Rabson To: "Bruce M. Walter" Cc: freebsd-alpha@freebsd.org Subject: Re: 3.1/4.0, the alpha, and a dog named blue... 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 Sat, 20 Feb 1999, Bruce M. Walter wrote: > Hello all, > > I've been running FreeBSD on several alpha's now for about two months. > I'm elated that I no longer have to kiss the arse of the Linux god to get > useful CPU cycles out of these machines. Thanks all for the hard work and > a hearty job well-done the the alpha porters. > > I realized I may get flamed for asking something like this, but since I > honestly don't know, I'm gonna ask: Where should a person looking to > get relatively stable (read -stable ;) performance from an alpha be? > > I know the answer may still be 'not on FreeBSD' at this point, but I've > been very impressed with the stability of the last few snaps. I'm really > wondering whether new bug-fixes/enhancements/functionality in the alpha > stuff is finding it's way back into the -stable branch, as all of the > latest snap's are from -current which has had some ffs/vm related problems > of late. > > If it's just a matter of taking the last 3.x alpha snap and tracking > -stable via CVS that's fine, it's just not apparent that that's the "Right > Thing to Do" (tm). > > Cheers all and thanks for the guidance! I think you ought to be fine on the stable branch. Relavent changes to current are being merged across all the time and the alpha specific parts will be no different. In fact there should be very little difference between 3.1 and 4.0 for the alpha specific code (4.0 uses the new syscons and I expect to merge that into 3.1 in due course). -- 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