From owner-freebsd-alpha Sun Jun 17 13: 0:24 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from freebie.xs4all.nl (freebie.xs4all.nl [213.84.32.253]) by hub.freebsd.org (Postfix) with ESMTP id D223237B401 for ; Sun, 17 Jun 2001 13:00:20 -0700 (PDT) (envelope-from wkb@freebie.xs4all.nl) Received: (from wkb@localhost) by freebie.xs4all.nl (8.11.3/8.11.3) id f5HK6Iu13430 for freebsd-alpha@freebsd.org; Sun, 17 Jun 2001 22:06:18 +0200 (CEST) (envelope-from wkb) Date: Sun, 17 Jun 2001 22:06:18 +0200 From: Wilko Bulte To: freebsd-alpha@freebsd.org Subject: axing 'device plip' from GENERIC? Message-ID: <20010617220618.A13414@freebie.xs4all.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i X-OS: FreeBSD 4.3-STABLE X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Anybody opposed to me axing: device plip # TCP/IP over parallel from GENERIC for the Alpha? On all alpha models I've ever put FreeBSD on I just saw an error about plip not wanting to probe/attach/whatever (forgot the exact error). W/ -- | / o / / _ Arnhem, The Netherlands email: wilko@FreeBSD.org |/|/ / / /( (_) Bulte 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 Sun Jun 17 13: 8:39 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from freebie.xs4all.nl (freebie.xs4all.nl [213.84.32.253]) by hub.freebsd.org (Postfix) with ESMTP id A27A037B401 for ; Sun, 17 Jun 2001 13:08:36 -0700 (PDT) (envelope-from wkb@freebie.xs4all.nl) Received: (from wkb@localhost) by freebie.xs4all.nl (8.11.3/8.11.3) id f5HKEWl13503 for freebsd-alpha@freebsd.org; Sun, 17 Jun 2001 22:14:32 +0200 (CEST) (envelope-from wkb) Date: Sun, 17 Jun 2001 22:14:32 +0200 From: Wilko Bulte To: freebsd-alpha@freebsd.org Subject: going nowhere Message-ID: <20010617221432.A13492@freebie.xs4all.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i X-OS: FreeBSD 4.3-STABLE X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org As I don't remember: is the 'going nowhere without my init' bug now fixed in RELENG_4? I think it is, but I'm not sure. My question was triggered by reviewing PR alpha/17642 -- | / o / / _ Arnhem, The Netherlands email: wilko@FreeBSD.org |/|/ / / /( (_) Bulte 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 Sun Jun 17 13: 9:59 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from beppo.feral.com (beppo.feral.com [192.67.166.79]) by hub.freebsd.org (Postfix) with ESMTP id 3CD5537B408 for ; Sun, 17 Jun 2001 13:09:54 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from wonky.feral.com (wonky.feral.com [192.67.166.7]) by beppo.feral.com (8.11.3/8.11.3) with ESMTP id f5HK9mg57149; Sun, 17 Jun 2001 13:09:48 -0700 (PDT) (envelope-from mjacob@feral.com) Date: Sun, 17 Jun 2001 13:09:46 -0700 (PDT) From: Matthew Jacob Reply-To: To: Wilko Bulte Cc: Subject: Re: going nowhere In-Reply-To: <20010617221432.A13492@freebie.xs4all.nl> Message-ID: <20010617130932.M6429-100000@wonky.feral.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Sun, 17 Jun 2001, Wilko Bulte wrote: > As I don't remember: is the 'going nowhere without my init' bug now > fixed in RELENG_4? I think it is, but I'm not sure. No. The boot blocks haven't been backported. > > My question was triggered by reviewing PR alpha/17642 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Sun Jun 17 14:16:34 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from tomts14-srv.bellnexxia.net (tomts14.bellnexxia.net [209.226.175.35]) by hub.freebsd.org (Postfix) with ESMTP id 7EE6837B401 for ; Sun, 17 Jun 2001 14:16:30 -0700 (PDT) (envelope-from dp@penix.org) Received: from penix.org ([64.228.106.161]) by tomts14-srv.bellnexxia.net (InterMail vM.4.01.03.16 201-229-121-116-20010115) with ESMTP id <20010617211628.IJCH2764.tomts14-srv.bellnexxia.net@penix.org>; Sun, 17 Jun 2001 17:16:28 -0400 Message-ID: <3B2D216B.AAE32EA1@penix.org> Date: Sun, 17 Jun 2001 17:30:19 -0400 From: Paul Halliday X-Mailer: Mozilla 4.76 [en] (X11; U; FreeBSD 4.3-RC i386) X-Accept-Language: en MIME-Version: 1.0 To: Wilko Bulte Cc: freebsd-alpha@FreeBSD.ORG Subject: Re: axing 'device plip' from GENERIC? References: <20010617220618.A13414@freebie.xs4all.nl> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Wilko Bulte wrote: > > Anybody opposed to me axing: > > device plip # TCP/IP over parallel > > from GENERIC for the Alpha? Nope. > > On all alpha models I've ever put FreeBSD on I just saw an error about > plip not wanting to probe/attach/whatever (forgot the exact error). > Same here. > W/ > -- > | / o / / _ Arnhem, The Netherlands email: wilko@FreeBSD.org > |/|/ / / /( (_) Bulte http://www.FreeBSD.org > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-alpha" in the body of the message -- Paul H. ___________________ http://dp.penix.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Mon Jun 18 1:53:21 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from l04.research.kpn.com (l04.research.kpn.com [139.63.192.204]) by hub.freebsd.org (Postfix) with ESMTP id 2DD9D37B405 for ; Mon, 18 Jun 2001 01:53:18 -0700 (PDT) (envelope-from K.J.Koster@kpn.com) Received: by l04.research.kpn.com with Internet Mail Service (5.5.2653.19) id ; Mon, 18 Jun 2001 10:53:17 +0100 Message-ID: <59063B5B4D98D311BC0D0001FA7E452205FD9CB8@l04.research.kpn.com> From: "Koster, K.J." To: 'Wilko Bulte' Cc: alpha@FreeBSD.ORG Subject: RE: Wit's end (AS250 installation issues) Date: Mon, 18 Jun 2001 10:53:16 +0100 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Dear Wilko, > > Seems I need to re-phrase the -alpha docs a bit to make this > clearer to the innocent ;-) > We fought over this before, remember. I love how you closed the pr that I asked you to keep open and within days someone turns up and tells us he ran into the problem. :-/ I still think there is an opportunity for /stand/sysinstall to warn users of this issue. Ik know, I know, you await my code... *sigh* so much to code, so little time. Kees Jan ================================================ You are only young once, but you can stay immature all your life. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Mon Jun 18 5:31: 1 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from fl-mia01-m.stis.com (5935supra.020.popsite.net [64.24.149.213]) by hub.freebsd.org (Postfix) with ESMTP id 937D737B401 for ; Mon, 18 Jun 2001 05:30:55 -0700 (PDT) (envelope-from IMCEAEX-_O=STIS_OU=STIS_CN=RECIPIENTS_CN=RCRESPO@STIS.com) Received: by fl-mia01-m.stis.com.10.in-addr.arpa with Internet Mail Service (5.5.2653.19) id ; Mon, 18 Jun 2001 08:31:45 -0400 Message-ID: From: "Crespo, Ramon" To: "'freebsd-alpha@freebsd.org'" Subject: alpha's reading cdr's Date: Mon, 18 Jun 2001 08:30:42 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Hello All, I've been trying to install FreeBSD-4.3-RELEASE on a nice PWS 600a (old NT machine) here ,but I don't think the CD-ROM reads cdr's .. It wouldn't boot off of it and now it won't read it after I use the boot diskettes to boot up the machine. Also it is possible to upgrade the SRM BIOS after I've installed FreeBSD right? Just download the appropriate files and then start up via the SRM console? I have 5.67 [Alpha Bios] on here and I think that 5.7 was the newest.. its a Miata GL for those who are wondering. If you can point me to any specific documentation concerning any of these matters it will be very well appreciated. Thanks Ramon Crespo To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Mon Jun 18 8:23:16 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from fl-mia01-m.stis.com (5935supra.020.popsite.net [64.24.149.213]) by hub.freebsd.org (Postfix) with ESMTP id 6931B37B401 for ; Mon, 18 Jun 2001 08:23:06 -0700 (PDT) (envelope-from IMCEAEX-_O=STIS_OU=STIS_CN=RECIPIENTS_CN=RCRESPO@STIS.com) Received: by fl-mia01-m.stis.com.10.in-addr.arpa with Internet Mail Service (5.5.2653.19) id ; Mon, 18 Jun 2001 11:23:47 -0400 Message-ID: From: "Crespo, Ramon" To: "'freebsd-alpha@freebsd.org'" Subject: X11 Settings for the MiataGL Date: Mon, 18 Jun 2001 11:22:48 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Hello All, I have successfully installed 4.3-RELEASE on my MiataGL and I was wondering if X11 works on it. I don't know if its reading the video card correctly or what because I try to use 'SuperProbe' and it core dumps. Is there any Alpha specific X11 out there? If so please point me to it. Also does anyone have any other resources besides the list (which is great) .. WebPages or something? Right now its displaying @ 320x400 which is a little ridiculous on a 19" monitor. Thanks in advance, Ramon Crespo To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Mon Jun 18 9: 7:41 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from mail.freebsd.org (ntmcn.megabytescomputers.com [216.215.166.18]) by hub.freebsd.org (Postfix) with SMTP id 4540037B401 for ; Mon, 18 Jun 2001 09:07:33 -0700 (PDT) (envelope-from Al@megabytescomputers.com) From: Megabytes@FreeBSD.ORG, Computers@FreeBSD.ORG, &@FreeBSD.ORG, Networking@FreeBSD.ORG, Inc.@FreeBSD.ORG Date: Mon, 18 Jun 2001 12:16:20 To: freebsd-alpha@freebsd.org Subject: Seamless Functionality MIME-Version: 1.0 Content-Type: text/plain;charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <20010618160733.4540037B401@hub.freebsd.org> Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org WHY MEGABYTES? Businesses today need to manage technology for optimal performance while tending to what's most important-finding and retaining customers. Megabytes offers Mega solutions and services to the small businesses and the large corporate sector. Visit our web site at: http://www.megabytescomputers.com Services Include · Personalized service with cutting edge technology · Microsoft Certified Professionals, Microsoft Certified System Engineers. · Routine maintenance/pc help desk and on site support · IT consulting · Project management · Backup system installations · System development · Novell support It only makes sense to utilize all we have to offer. We understand your business is important and will work around the clock to keep your business up and running! We've been in business for over fifteen years.! This is a one time mailing! AL Scott Marketing Director/MCSE al@megabytescomputers.com (904)880-6366 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Mon Jun 18 9:44:15 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from freebie.xs4all.nl (freebie.xs4all.nl [213.84.32.253]) by hub.freebsd.org (Postfix) with ESMTP id 1733E37B403 for ; Mon, 18 Jun 2001 09:44:13 -0700 (PDT) (envelope-from wkb@freebie.xs4all.nl) Received: (from wkb@localhost) by freebie.xs4all.nl (8.11.3/8.11.3) id f5IGi0u01056; Mon, 18 Jun 2001 18:44:00 +0200 (CEST) (envelope-from wkb) Date: Mon, 18 Jun 2001 18:44:00 +0200 From: Wilko Bulte To: "Crespo, Ramon" Cc: "'freebsd-alpha@freebsd.org'" Subject: Re: alpha's reading cdr's Message-ID: <20010618184400.A1026@freebie.xs4all.nl> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from IMCEAEX-_O=STIS_OU=STIS_CN=RECIPIENTS_CN=RCRESPO@STIS.com on Mon, Jun 18, 2001 at 08:30:42AM -0400 X-OS: FreeBSD 4.3-STABLE X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Mon, Jun 18, 2001 at 08:30:42AM -0400, Crespo, Ramon wrote: > Hello All, > > I've been trying to install FreeBSD-4.3-RELEASE on a nice PWS 600a (old NT > machine) here ,but I don't think the CD-ROM reads cdr's .. It wouldn't boot > off of it and now it won't read it after I use the boot diskettes to boot up > the machine. Also it is possible to upgrade the SRM BIOS after I've > installed FreeBSD right? Just download the appropriate files and then start > up via the SRM console? I have 5.67 [Alpha Bios] on here and I think that > 5.7 was the newest.. its a Miata GL for those who are wondering. If you can > point me to any specific documentation concerning any of these matters it > will be very well appreciated. My Miata has no problem booting CDRs. Do it all the time ;-) What type of CDROM drive does it have (RRDxx; what is xx?) -- | / o / / _ Arnhem, The Netherlands email: wilko@FreeBSD.org |/|/ / / /( (_) Bulte 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 Mon Jun 18 10:53:19 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from fl-mia01-m.stis.com (5935supra.020.popsite.net [64.24.149.213]) by hub.freebsd.org (Postfix) with ESMTP id E422C37B401 for ; Mon, 18 Jun 2001 10:53:15 -0700 (PDT) (envelope-from IMCEAEX-_O=STIS_OU=STIS_CN=RECIPIENTS_CN=RCRESPO@STIS.com) Received: by fl-mia01-m.stis.com.10.in-addr.arpa with Internet Mail Service (5.5.2653.19) id ; Mon, 18 Jun 2001 13:53:33 -0400 Message-ID: From: "Crespo, Ramon" To: 'Wilko Bulte' Cc: "'freebsd-alpha@freebsd.org'" Subject: RE: alpha's reading cdr's Date: Mon, 18 Jun 2001 13:52:37 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Hey Wilko It reads fine now .. it seem's the image wasnt burned correctly .. thanks for the concern. If any of you can help me with X on the Miata GL I would really appreciate it .. 1024x768 on this 19" monitor would be quite nice. Im going to recompile the kernel in a few and CVSup to stable and then relax for a bit. Thanks for all your help, Ramon Crespo -----Original Message----- From: Wilko Bulte [mailto:wkb@freebie.xs4all.nl] Sent: Monday, June 18, 2001 12:44 PM To: Crespo, Ramon Cc: 'freebsd-alpha@freebsd.org' Subject: Re: alpha's reading cdr's On Mon, Jun 18, 2001 at 08:30:42AM -0400, Crespo, Ramon wrote: > Hello All, > > I've been trying to install FreeBSD-4.3-RELEASE on a nice PWS 600a (old NT > machine) here ,but I don't think the CD-ROM reads cdr's .. It wouldn't boot > off of it and now it won't read it after I use the boot diskettes to boot up > the machine. Also it is possible to upgrade the SRM BIOS after I've > installed FreeBSD right? Just download the appropriate files and then start > up via the SRM console? I have 5.67 [Alpha Bios] on here and I think that > 5.7 was the newest.. its a Miata GL for those who are wondering. If you can > point me to any specific documentation concerning any of these matters it > will be very well appreciated. My Miata has no problem booting CDRs. Do it all the time ;-) What type of CDROM drive does it have (RRDxx; what is xx?) -- | / o / / _ Arnhem, The Netherlands email: wilko@FreeBSD.org |/|/ / / /( (_) Bulte 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 Mon Jun 18 11: 4:50 2001 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 D2CEC37B40A for ; Mon, 18 Jun 2001 11:04:44 -0700 (PDT) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.3/8.9.3) with ESMTP id OAA27135; Mon, 18 Jun 2001 14:04:40 -0400 (EDT) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.11.3/8.9.1) id f5II4BZ33871; Mon, 18 Jun 2001 14:04:11 -0400 (EDT) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <15150.17051.201667.856092@grasshopper.cs.duke.edu> Date: Mon, 18 Jun 2001 14:04:11 -0400 (EDT) To: "Crespo, Ramon" Cc: "'freebsd-alpha@freebsd.org'" Subject: Re: X11 Settings for the MiataGL In-Reply-To: References: X-Mailer: VM 6.75 under 21.1 (patch 12) "Channel Islands" XEmacs Lucid Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Crespo, Ramon writes: > Hello All, > > I have successfully installed 4.3-RELEASE on my MiataGL and I was wondering > if X11 works on it. I don't know if its reading the video card correctly or > what because I try to use 'SuperProbe' and it core dumps. Is there any Alpha > specific X11 out there? If so please point me to it. Also does anyone have > any other resources besides the list (which is great) .. WebPages or > something? Right now its displaying @ 320x400 which is a little ridiculous > on a 19" monitor. If you're using XFree86 3.x, note that (as David O'Brien pointed out earlier on this mailing list): The "graphical" XFree86 configuration program -- XF86Setup program *requires* the VGA16 server. This server does NOT build on the Alpha. Not just FreeBSD/alpha, but AlphaLinux and Tru86 also. The issue with using the text-only xf86config is that it does not know about moused's sysmouse. Thus you either cannot use moused, or you must hack the /etc/XF86Config file xf86config creates to specify sysmouse. So, basically you'll need to know what kind of monitor you have, what sort of resolution / refresh rate its capable of & what sort of video card you have. If I had to guess, I'd imagine you have an Elsa Gloria Synergy (3Dlabs Permedia-2 based) card. Good luck. Drew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Mon Jun 18 11:29: 0 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from tomts7-srv.bellnexxia.net (tomts7.bellnexxia.net [209.226.175.40]) by hub.freebsd.org (Postfix) with ESMTP id 8731037B401 for ; Mon, 18 Jun 2001 11:28:57 -0700 (PDT) (envelope-from dp@penix.org) Received: from penix.org ([64.228.106.161]) by tomts7-srv.bellnexxia.net (InterMail vM.4.01.03.16 201-229-121-116-20010115) with ESMTP id <20010618182856.EDFI7745.tomts7-srv.bellnexxia.net@penix.org>; Mon, 18 Jun 2001 14:28:56 -0400 Message-ID: <3B2E4BBE.6FEC26EF@penix.org> Date: Mon, 18 Jun 2001 14:43:10 -0400 From: Paul Halliday X-Mailer: Mozilla 4.76 [en] (X11; U; FreeBSD 4.3-RC i386) X-Accept-Language: en MIME-Version: 1.0 To: Andrew Gallatin Cc: "Crespo, Ramon" , "'freebsd-alpha@freebsd.org'" Subject: Re: X11 Settings for the MiataGL References: <15150.17051.201667.856092@grasshopper.cs.duke.edu> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Andrew Gallatin wrote: > > Crespo, Ramon writes: > > Hello All, > > > > I have successfully installed 4.3-RELEASE on my MiataGL and I was wondering > > if X11 works on it. I don't know if its reading the video card correctly or > > what because I try to use 'SuperProbe' and it core dumps. Is there any Alpha > > specific X11 out there? If so please point me to it. Also does anyone have > > any other resources besides the list (which is great) .. WebPages or > > something? Right now its displaying @ 320x400 which is a little ridiculous > > on a 19" monitor. > > If you're using XFree86 3.x, note that (as David O'Brien pointed out > earlier on this mailing list): > > The "graphical" XFree86 configuration program -- XF86Setup program > *requires* the VGA16 server. This server does NOT build on the > Alpha. Not just FreeBSD/alpha, but AlphaLinux and Tru86 also. > > The issue with using the text-only xf86config is that it does not > know about moused's sysmouse. Thus you either cannot use moused, > or you must hack the /etc/XF86Config file xf86config creates to > specify sysmouse. Umm.. as200 xf86config-> Now give the full device name that the device is connected to, for example /dev/tty00. Just pressing enter will use the default, /dev/mouse. Mouse device: /dev/sysmouse > > So, basically you'll need to know what kind of monitor you have, what > sort of resolution / refresh rate its capable of & what sort of video > card you have. > > If I had to guess, I'd imagine you have an Elsa Gloria Synergy (3Dlabs > Permedia-2 based) card. Is it not an S3 chipset? > > Good luck. > > Drew > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-alpha" in the body of the message -- Paul H. ___________________ http://dp.penix.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Mon Jun 18 12:30:48 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from fl-mia01-m.stis.com (5935supra.020.popsite.net [64.24.149.213]) by hub.freebsd.org (Postfix) with ESMTP id EECF937B406 for ; Mon, 18 Jun 2001 12:30:43 -0700 (PDT) (envelope-from IMCEAEX-_O=STIS_OU=STIS_CN=RECIPIENTS_CN=RCRESPO@STIS.com) Received: by fl-mia01-m.stis.com.10.in-addr.arpa with Internet Mail Service (5.5.2653.19) id ; Mon, 18 Jun 2001 15:31:35 -0400 Message-ID: From: "Crespo, Ramon" To: 'Paul Halliday' , Andrew Gallatin Cc: "'freebsd-alpha@freebsd.org'" Subject: RE: X11 Settings for the MiataGL Date: Mon, 18 Jun 2001 15:31:03 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Hello All, I am sad to report that I don't have either video card it looks like I have a CL-GD5440 derived chipset or something (i cracked open the case and saw this). It has a supervideo port as well so I find this pretty hard to believe for this little card to only come with 64k of ram and do 320x400 standard. If possible is there a list of supported video cards for X11/Alpha? Sorry to be such a bother. Thanks in advance, Ramon Crespo -----Original Message----- From: Paul Halliday [mailto:dp@penix.org] Sent: Monday, June 18, 2001 2:43 PM To: Andrew Gallatin Cc: Crespo, Ramon; 'freebsd-alpha@freebsd.org' Subject: Re: X11 Settings for the MiataGL Andrew Gallatin wrote: > > Crespo, Ramon writes: > > Hello All, > > > > I have successfully installed 4.3-RELEASE on my MiataGL and I was wondering > > if X11 works on it. I don't know if its reading the video card correctly or > > what because I try to use 'SuperProbe' and it core dumps. Is there any Alpha > > specific X11 out there? If so please point me to it. Also does anyone have > > any other resources besides the list (which is great) .. WebPages or > > something? Right now its displaying @ 320x400 which is a little ridiculous > > on a 19" monitor. > > If you're using XFree86 3.x, note that (as David O'Brien pointed out > earlier on this mailing list): > > The "graphical" XFree86 configuration program -- XF86Setup program > *requires* the VGA16 server. This server does NOT build on the > Alpha. Not just FreeBSD/alpha, but AlphaLinux and Tru86 also. > > The issue with using the text-only xf86config is that it does not > know about moused's sysmouse. Thus you either cannot use moused, > or you must hack the /etc/XF86Config file xf86config creates to > specify sysmouse. Umm.. as200 xf86config-> Now give the full device name that the device is connected to, for example /dev/tty00. Just pressing enter will use the default, /dev/mouse. Mouse device: /dev/sysmouse > > So, basically you'll need to know what kind of monitor you have, what > sort of resolution / refresh rate its capable of & what sort of video > card you have. > > If I had to guess, I'd imagine you have an Elsa Gloria Synergy (3Dlabs > Permedia-2 based) card. Is it not an S3 chipset? > > Good luck. > > Drew > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-alpha" in the body of the message -- Paul H. ___________________ http://dp.penix.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Mon Jun 18 13:26:10 2001 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 F095837B401 for ; Mon, 18 Jun 2001 13:26:07 -0700 (PDT) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.3/8.9.3) with ESMTP id QAA00612; Mon, 18 Jun 2001 16:26:06 -0400 (EDT) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.11.3/8.9.1) id f5IKPaK34076; Mon, 18 Jun 2001 16:25:36 -0400 (EDT) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <15150.25536.710116.57965@grasshopper.cs.duke.edu> Date: Mon, 18 Jun 2001 16:25:36 -0400 (EDT) To: "Crespo, Ramon" Cc: "'freebsd-alpha@freebsd.org'" Subject: RE: X11 Settings for the MiataGL In-Reply-To: References: X-Mailer: VM 6.75 under 21.1 (patch 12) "Channel Islands" XEmacs Lucid Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Crespo, Ramon writes: > Hello All, > > I am sad to report that I don't have either video card it looks like I have > a CL-GD5440 derived chipset or something (i cracked open the case and saw > this). It has a supervideo port as well so I find this pretty hard to > believe for this little card to only come with 64k of ram and do 320x400 > standard. If possible is there a list of supported video > cards for X11/Alpha? Sorry to be such a bother. > > Thanks in advance, > Ramon Crespo Hmm.. I bought a used miata about 1.5 years ago. It came with an enormous Intergraph video "card" -- It was actually 2 32-bit PCI cards bolted together and had 2 monitor ports & a S-video port, slots for RAM, etc. It had a VGA CL-GD5440, and lord knows what else. According to the label, its a PBXGI-AA/AB/AC which is either a PowerStorm 4D40, 50, or 60.. Does this sound like what you have? Anyway, at the time, XFree86 didn't know what to do with that card. I just threw it in a drawer and bought an unbranded $30 permedia-2 based card from my local office supply store. This (permedia-2) card was supported by XFree86 & has been working well ever since. I have no idea if XFree86 supports it yet. 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 Mon Jun 18 13:26:35 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from suntana.fh-konstanz.de (suntana.fh-konstanz.de [141.37.9.230]) by hub.freebsd.org (Postfix) with ESMTP id 4792437B401 for ; Mon, 18 Jun 2001 13:26:31 -0700 (PDT) (envelope-from vahe@fh-konstanz.de) Received: from vvl10 (vvl10.fh-konstanz.de [141.37.112.110]) by suntana.fh-konstanz.de (8.9.3+Sun/8.9.3) with SMTP id UAA12418 for ; Mon, 18 Jun 2001 20:45:33 +0200 (MET DST) Message-ID: <002301c0f827$7e689510$7c45fea9@vvl10> From: "Vahe Khachikyan" To: "'freebsd-alpha@freebsd.org'" References: Subject: Re: alpha's reading cdr's Date: Mon, 18 Jun 2001 20:50:06 +0200 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 5.50.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Hello , There could be two causes of your problem. Firts your CDROM drive is old one and it can't read cdr's It is not recoverable no SRM updates will help nothing will help ! Second one you have a really driver/firmware problem. Try to read any other cdrom not CDR's on your Alpha machine I think you can do at least ls from SRM. Or to be 100% sure just install your CDROM drive into other PC and try to read any CDR. Please be sure to make multiple tests cause single test can succeed. -- Vahe --- ----- Original Message ----- From: "Crespo, Ramon" To: "'freebsd-alpha@freebsd.org'" Sent: Monday, June 18, 2001 2:30 PM Subject: alpha's reading cdr's > Hello All, > > I've been trying to install FreeBSD-4.3-RELEASE on a nice PWS 600a (old NT > machine) here ,but I don't think the CD-ROM reads cdr's .. It wouldn't boot > off of it and now it won't read it after I use the boot diskettes to boot up > the machine. Also it is possible to upgrade the SRM BIOS after I've > installed FreeBSD right? Just download the appropriate files and then start > up via the SRM console? I have 5.67 [Alpha Bios] on here and I think that > 5.7 was the newest.. its a Miata GL for those who are wondering. If you can > point me to any specific documentation concerning any of these matters it > will be very well appreciated. > > Thanks > Ramon Crespo > > 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 Mon Jun 18 13:45:50 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from fl-mia01-m.stis.com (5935supra.020.popsite.net [64.24.149.213]) by hub.freebsd.org (Postfix) with ESMTP id 5EB4837B403 for ; Mon, 18 Jun 2001 13:45:46 -0700 (PDT) (envelope-from IMCEAEX-_O=STIS_OU=STIS_CN=RECIPIENTS_CN=RCRESPO@STIS.com) Received: by fl-mia01-m.stis.com.10.in-addr.arpa with Internet Mail Service (5.5.2653.19) id ; Mon, 18 Jun 2001 16:46:35 -0400 Message-ID: From: "Crespo, Ramon" To: 'Andrew Gallatin' Cc: "'freebsd-alpha@freebsd.org'" Subject: RE: X11 Settings for the MiataGL Date: Mon, 18 Jun 2001 16:46:30 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Hey Andrew, That's exactly what I have is it supported in XFree86 now? The one that ships with 4.3-RELEASE ? I'll look at the # now .. no wonder it looked like garbage even under NT. Is there a list of supported cards under XF86/Alpha? I have an old Diamond Stealth 64 with 4MB of ram that I might be able to stick in there .. S3 Vision968 Chipset If I remember correctly. on a side note. Go duke .. Im a huge fan of the basketball team. anyway I hope to get this resolved before I leave today if not tommorow Thanks for your help. Thanks in advance, Ramon Crespo -----Original Message----- From: Andrew Gallatin [mailto:gallatin@cs.duke.edu] Sent: Monday, June 18, 2001 4:26 PM To: Crespo, Ramon Cc: 'freebsd-alpha@freebsd.org' Subject: RE: X11 Settings for the MiataGL Crespo, Ramon writes: > Hello All, > > I am sad to report that I don't have either video card it looks like I have > a CL-GD5440 derived chipset or something (i cracked open the case and saw > this). It has a supervideo port as well so I find this pretty hard to > believe for this little card to only come with 64k of ram and do 320x400 > standard. If possible is there a list of supported video > cards for X11/Alpha? Sorry to be such a bother. > > Thanks in advance, > Ramon Crespo Hmm.. I bought a used miata about 1.5 years ago. It came with an enormous Intergraph video "card" -- It was actually 2 32-bit PCI cards bolted together and had 2 monitor ports & a S-video port, slots for RAM, etc. It had a VGA CL-GD5440, and lord knows what else. According to the label, its a PBXGI-AA/AB/AC which is either a PowerStorm 4D40, 50, or 60.. Does this sound like what you have? Anyway, at the time, XFree86 didn't know what to do with that card. I just threw it in a drawer and bought an unbranded $30 permedia-2 based card from my local office supply store. This (permedia-2) card was supported by XFree86 & has been working well ever since. I have no idea if XFree86 supports it yet. 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 Mon Jun 18 14:17:25 2001 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 0F28837B401 for ; Mon, 18 Jun 2001 14:17:23 -0700 (PDT) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.3/8.9.3) with ESMTP id RAA01737; Mon, 18 Jun 2001 17:17:20 -0400 (EDT) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.11.3/8.9.1) id f5ILGoT34144; Mon, 18 Jun 2001 17:16:50 -0400 (EDT) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <15150.28610.864423.75714@grasshopper.cs.duke.edu> Date: Mon, 18 Jun 2001 17:16:50 -0400 (EDT) To: "Crespo, Ramon" Cc: "'freebsd-alpha@freebsd.org'" Subject: RE: X11 Settings for the MiataGL In-Reply-To: References: X-Mailer: VM 6.75 under 21.1 (patch 12) "Channel Islands" XEmacs Lucid Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Crespo, Ramon writes: > Hey Andrew, > > That's exactly what I have is it supported in XFree86 now? The one I have no idea. I've only been using it as a paperweight in my junk drawer.. > that ships with 4.3-RELEASE ? I'll look at the # now .. no wonder it > looked like garbage even under NT. Is there a list of supported cards under > XF86/Alpha? I have an Nope. > old Diamond Stealth 64 with 4MB of ram that I might be able to stick in > there .. S3 Vision968 Chipset That might work. XFree86 is probably much more likely to understand that card. Esp. XFree86 3.x Drew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Mon Jun 18 15:10:24 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from fl-mia01-m.stis.com (5935supra.020.popsite.net [64.24.149.213]) by hub.freebsd.org (Postfix) with ESMTP id DA91837B401 for ; Mon, 18 Jun 2001 15:10:17 -0700 (PDT) (envelope-from IMCEAEX-_O=STIS_OU=STIS_CN=RECIPIENTS_CN=RCRESPO@STIS.com) Received: by fl-mia01-m.stis.com.10.in-addr.arpa with Internet Mail Service (5.5.2653.19) id ; Mon, 18 Jun 2001 18:11:05 -0400 Message-ID: From: "Crespo, Ramon" To: "'freebsd-alpha@freebsd.org'" Subject: XF86 4.x on FreeBSD/Alpha Date: Mon, 18 Jun 2001 18:10:48 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Hello All, according to this page http://www.xfree86.org/4.1.0/Status10.html#10 .. Support (accelerated) for the DEC 21030 TGA 8 plane, 24 plane and 24 plane 3D chips (on Alpha platforms) is provided by the XF86_TGA server .. I have a DEC 21052_AB in my Miata GL .. also is there any chance to compile 4.1.x from scratch out of ports or something. I'll get started on a webpage with some info as soon as I get this resolved so we can point users to it. Is there an FAQ of some sort ? I feel bad crowding everyone's mailbox with my all my little problems. Thanks for all the support, Ramon Crespo To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Mon Jun 18 15:13: 3 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from freebie.xs4all.nl (freebie.xs4all.nl [213.84.32.253]) by hub.freebsd.org (Postfix) with ESMTP id 241E537B401 for ; Mon, 18 Jun 2001 15:13:00 -0700 (PDT) (envelope-from wkb@freebie.xs4all.nl) Received: (from wkb@localhost) by freebie.xs4all.nl (8.11.3/8.11.3) id f5IMCtU02358; Tue, 19 Jun 2001 00:12:55 +0200 (CEST) (envelope-from wkb) Date: Tue, 19 Jun 2001 00:12:55 +0200 From: Wilko Bulte To: "Crespo, Ramon" Cc: "'freebsd-alpha@freebsd.org'" Subject: Re: XF86 4.x on FreeBSD/Alpha Message-ID: <20010619001254.F2135@freebie.xs4all.nl> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from IMCEAEX-_O=STIS_OU=STIS_CN=RECIPIENTS_CN=RCRESPO@STIS.com on Mon, Jun 18, 2001 at 06:10:48PM -0400 X-OS: FreeBSD 4.3-STABLE X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Mon, Jun 18, 2001 at 06:10:48PM -0400, Crespo, Ramon wrote: > Hello All, > > according to this page http://www.xfree86.org/4.1.0/Status10.html#10 .. > Support (accelerated) for the DEC 21030 TGA 8 plane, 24 plane and 24 plane > 3D chips (on Alpha platforms) is provided by the XF86_TGA server .. I have a > DEC 21052_AB in my Miata GL .. also is there any chance to compile 4.1.x > from scratch out of ports or something. I'll get started on a webpage with > some info as soon as I get this resolved so we can point users to it. Is > there an FAQ of some sort ? I feel bad crowding everyone's mailbox with my > all my little problems. Problem is that TGA cards are not yet supported as console devices so you will be driving blind (I guess) while X has not yet [been] started. -- | / o / / _ Arnhem, The Netherlands email: wilko@FreeBSD.org |/|/ / / /( (_) Bulte 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 Mon Jun 18 15:16:54 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from fl-mia01-m.stis.com (5935supra.020.popsite.net [64.24.149.213]) by hub.freebsd.org (Postfix) with ESMTP id 22FE737B401 for ; Mon, 18 Jun 2001 15:16:47 -0700 (PDT) (envelope-from IMCEAEX-_O=STIS_OU=STIS_CN=RECIPIENTS_CN=RCRESPO@STIS.com) Received: by fl-mia01-m.stis.com.10.in-addr.arpa with Internet Mail Service (5.5.2653.19) id ; Mon, 18 Jun 2001 18:17:35 -0400 Message-ID: From: "Crespo, Ramon" To: 'Wilko Bulte' Cc: "'freebsd-alpha@freebsd.org'" Subject: RE: XF86 4.x on FreeBSD/Alpha Date: Mon, 18 Jun 2001 18:16:53 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Hello Wilko, Thanks .. so basically I should get rid of this card for now and use something that works under 3.3.6? Once support for TGA devices comes abound I can put the old card back in there .. or maybe I can keep them both and just have the monitor connected to the one that works. The video card is quite large .. so I dont want to disturb it :) ... All suggestions welcome as well as cards that will work under FreeBSD/Alpha X11. Maybe we can compile a list of people who are on this list and make it an unofficial X11 FAQ of some sort. Thanks in advance, Ramon Crespo -----Original Message----- From: Wilko Bulte [mailto:wkb@freebie.xs4all.nl] Sent: Monday, June 18, 2001 6:13 PM To: Crespo, Ramon Cc: 'freebsd-alpha@freebsd.org' Subject: Re: XF86 4.x on FreeBSD/Alpha On Mon, Jun 18, 2001 at 06:10:48PM -0400, Crespo, Ramon wrote: > Hello All, > > according to this page http://www.xfree86.org/4.1.0/Status10.html#10 .. > Support (accelerated) for the DEC 21030 TGA 8 plane, 24 plane and 24 plane > 3D chips (on Alpha platforms) is provided by the XF86_TGA server .. I have a > DEC 21052_AB in my Miata GL .. also is there any chance to compile 4.1.x > from scratch out of ports or something. I'll get started on a webpage with > some info as soon as I get this resolved so we can point users to it. Is > there an FAQ of some sort ? I feel bad crowding everyone's mailbox with my > all my little problems. Problem is that TGA cards are not yet supported as console devices so you will be driving blind (I guess) while X has not yet [been] started. -- | / o / / _ Arnhem, The Netherlands email: wilko@FreeBSD.org |/|/ / / /( (_) Bulte 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 Mon Jun 18 15:18:38 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from freebie.xs4all.nl (freebie.xs4all.nl [213.84.32.253]) by hub.freebsd.org (Postfix) with ESMTP id CE74F37B443 for ; Mon, 18 Jun 2001 15:18:31 -0700 (PDT) (envelope-from wkb@freebie.xs4all.nl) Received: (from wkb@localhost) by freebie.xs4all.nl (8.11.3/8.11.3) id f5IMHue02434; Tue, 19 Jun 2001 00:17:56 +0200 (CEST) (envelope-from wkb) Date: Tue, 19 Jun 2001 00:17:56 +0200 From: Wilko Bulte To: Andrew Gallatin Cc: "Crespo, Ramon" , "'freebsd-alpha@freebsd.org'" Subject: Re: X11 Settings for the MiataGL Message-ID: <20010619001756.I2135@freebie.xs4all.nl> References: <15150.28610.864423.75714@grasshopper.cs.duke.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <15150.28610.864423.75714@grasshopper.cs.duke.edu>; from gallatin@cs.duke.edu on Mon, Jun 18, 2001 at 05:16:50PM -0400 X-OS: FreeBSD 4.3-STABLE X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Mon, Jun 18, 2001 at 05:16:50PM -0400, Andrew Gallatin wrote: > > Crespo, Ramon writes: > > Hey Andrew, > > > > That's exactly what I have is it supported in XFree86 now? The one > > I have no idea. I've only been using it as a paperweight in my junk > drawer.. Sell it. Some Tru64 user might like it ;) I'm pretty sure it has accelerated drivers for the various Powerstorms W/ -- | / o / / _ Arnhem, The Netherlands email: wilko@FreeBSD.org |/|/ / / /( (_) Bulte 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 Mon Jun 18 15:20:15 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from freebie.xs4all.nl (freebie.xs4all.nl [213.84.32.253]) by hub.freebsd.org (Postfix) with ESMTP id A893037B403 for ; Mon, 18 Jun 2001 15:20:11 -0700 (PDT) (envelope-from wkb@freebie.xs4all.nl) Received: (from wkb@localhost) by freebie.xs4all.nl (8.11.3/8.11.3) id f5IMK5N02477; Tue, 19 Jun 2001 00:20:05 +0200 (CEST) (envelope-from wkb) Date: Tue, 19 Jun 2001 00:20:05 +0200 From: "'Wilko Bulte'" To: "Crespo, Ramon" Cc: "'freebsd-alpha@freebsd.org'" Subject: Re: alpha's reading cdr's Message-ID: <20010619002004.J2135@freebie.xs4all.nl> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from IMCEAEX-_O=STIS_OU=STIS_CN=RECIPIENTS_CN=RCRESPO@STIS.com on Mon, Jun 18, 2001 at 01:52:37PM -0400 X-OS: FreeBSD 4.3-STABLE X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Mon, Jun 18, 2001 at 01:52:37PM -0400, Crespo, Ramon wrote: > Hey Wilko > > It reads fine now .. it seem's the image wasnt burned correctly .. thanks Good.. duff CDRs happen all the time. I was already a bit surprised as even the ancient single-speed RRD43 read CDRs OK for me. > for the concern. If any of you can help me with X on the Miata GL I would > really appreciate it .. 1024x768 on this 19" monitor would be quite nice. Im > going to recompile the kernel in a few and CVSup to stable and then relax > for a bit. Sorry, never ran X on either my Miata GL or MX5 > Thanks for all your help, > Ramon Crespo -- | / o / / _ Arnhem, The Netherlands email: wilko@FreeBSD.org |/|/ / / /( (_) Bulte 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 Mon Jun 18 15:40:32 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from netau1.alcanet.com.au (ntp.alcanet.com.au [203.62.196.27]) by hub.freebsd.org (Postfix) with ESMTP id 1B74D37B401 for ; Mon, 18 Jun 2001 15:40:29 -0700 (PDT) (envelope-from jeremyp@gsmx07.alcatel.com.au) Received: from mfg1.cim.alcatel.com.au (mfg1.cim.alcatel.com.au [139.188.23.1]) by netau1.alcanet.com.au (8.9.3 (PHNE_22672)/8.9.3) with ESMTP id IAA19047; Tue, 19 Jun 2001 08:39:49 +1000 (EST) Received: from gsmx07.alcatel.com.au by cim.alcatel.com.au (PMDF V5.2-32 #37645) with ESMTP id <01K4Y0Y79KSGVNZ7FW@cim.alcatel.com.au>; Tue, 19 Jun 2001 08:39:45 +1000 Received: (from jeremyp@localhost) by gsmx07.alcatel.com.au (8.11.1/8.11.1) id f5IMdin06486; Tue, 19 Jun 2001 08:39:44 +1000 (EST envelope-from jeremyp) Content-return: prohibited Date: Tue, 19 Jun 2001 08:39:43 +1000 From: Peter Jeremy Subject: Re: XF86 4.x on FreeBSD/Alpha In-reply-to: <20010619001254.F2135@freebie.xs4all.nl>; from wkb@freebie.xs4all.nl on Tue, Jun 19, 2001 at 12:12:55AM +0200 To: Wilko Bulte Cc: "Crespo, Ramon" , freebsd-alpha@FreeBSD.ORG Mail-Followup-To: Wilko Bulte , "Crespo, Ramon" , freebsd-alpha@FreeBSD.ORG Message-id: <20010619083943.E95583@gsmx07.alcatel.com.au> MIME-version: 1.0 Content-type: text/plain; charset=us-ascii Content-disposition: inline User-Agent: Mutt/1.2.5i References: <20010619001254.F2135@freebie.xs4all.nl> Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On 2001-Jun-19 00:12:55 +0200, Wilko Bulte wrote: >Problem is that TGA cards are not yet supported as console devices >so you will be driving blind (I guess) while X has not yet [been] started. A TGA console driver for FreeBSD is currently awaiting someone with commit privs to commit it. Two people offered - the first withdrew his offer due to changed circumstances and the second appears to have lost interest. Contact "Andrew M. Miklic" for a copy of the driver. Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Mon Jun 18 17:53:36 2001 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 8D43B37B403 for ; Mon, 18 Jun 2001 17:53:33 -0700 (PDT) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.3/8.9.3) with ESMTP id UAA05454; Mon, 18 Jun 2001 20:53:30 -0400 (EDT) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.11.3/8.9.1) id f5J0r0e34563; Mon, 18 Jun 2001 20:53:00 -0400 (EDT) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <15150.41580.737389.512005@grasshopper.cs.duke.edu> Date: Mon, 18 Jun 2001 20:53:00 -0400 (EDT) To: Wilko Bulte Cc: "Crespo, Ramon" , "'freebsd-alpha@freebsd.org'" Subject: Re: XF86 4.x on FreeBSD/Alpha In-Reply-To: <20010619001254.F2135@freebie.xs4all.nl> References: <20010619001254.F2135@freebie.xs4all.nl> X-Mailer: VM 6.75 under 21.1 (patch 12) "Channel Islands" XEmacs Lucid Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Wilko Bulte writes: > > DEC 21052_AB in my Miata GL .. also is there any chance to compile 4.1.x > > from scratch out of ports or something. I'll get started on a webpage with Yes. Make sure to cvsup the latest ports -- I fixed an alpha-only compile problem roughly 1 week ago. > > some info as soon as I get this resolved so we can point users to it. Is > > there an FAQ of some sort ? I feel bad crowding everyone's mailbox with my > > all my little problems. > > Problem is that TGA cards are not yet supported as console devices > so you will be driving blind (I guess) while X has not yet [been] started. No, the lack of console driver only affects the 8-plane cards. The 3d Powerstorm cards have the cirrus logic VGA chip on it, so it "just works" for a console -- he's probably using it right now. Drew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Mon Jun 18 18: 4:12 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from dragon.nuxi.com (trang.nuxi.com [206.40.252.115]) by hub.freebsd.org (Postfix) with ESMTP id 6CD2A37B406 for ; Mon, 18 Jun 2001 18:04:09 -0700 (PDT) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.11.3/8.11.1) id f5J13Tx00747; Mon, 18 Jun 2001 18:03:29 -0700 (PDT) (envelope-from obrien) Date: Mon, 18 Jun 2001 18:03:29 -0700 From: "David O'Brien" To: "Koster, K.J." Cc: "'Wilko Bulte'" , alpha@FreeBSD.ORG Subject: Re: Wit's end (AS250 installation issues) Message-ID: <20010618180329.C540@dragon.nuxi.com> Reply-To: obrien@FreeBSD.ORG References: <59063B5B4D98D311BC0D0001FA7E452205FD9CB8@l04.research.kpn.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <59063B5B4D98D311BC0D0001FA7E452205FD9CB8@l04.research.kpn.com>; from K.J.Koster@kpn.com on Mon, Jun 18, 2001 at 10:53:16AM +0100 X-Operating-System: FreeBSD 5.0-CURRENT Organization: The NUXI BSD group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Mon, Jun 18, 2001 at 10:53:16AM +0100, Koster, K.J. wrote: > into the problem. :-/ I still think there is an opportunity for > /stand/sysinstall to warn users of this issue. No. Someone with a little extra time should make it so / is always the first partion on the Alpha. Why warn rather than just make things right. -- -- David (obrien@FreeBSD.org) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Mon Jun 18 18: 5:47 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from dragon.nuxi.com (trang.nuxi.com [206.40.252.115]) by hub.freebsd.org (Postfix) with ESMTP id 1301337B401 for ; Mon, 18 Jun 2001 18:05:45 -0700 (PDT) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.11.3/8.11.1) id f5J15an00802; Mon, 18 Jun 2001 18:05:36 -0700 (PDT) (envelope-from obrien) Date: Mon, 18 Jun 2001 18:05:35 -0700 From: "David O'Brien" To: "Crespo, Ramon" Cc: "'Wilko Bulte'" , "'freebsd-alpha@freebsd.org'" Subject: Re: alpha's reading cdr's Message-ID: <20010618180535.D540@dragon.nuxi.com> Reply-To: freebsd-alpha@freebsd.org References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from IMCEAEX-_O=STIS_OU=STIS_CN=RECIPIENTS_CN=RCRESPO@STIS.com on Mon, Jun 18, 2001 at 01:52:37PM -0400 X-Operating-System: FreeBSD 5.0-CURRENT Organization: The NUXI BSD group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Mon, Jun 18, 2001 at 01:52:37PM -0400, Crespo, Ramon wrote: > for the concern. If any of you can help me with X on the Miata GL I would > really appreciate it .. 1024x768 on this 19" monitor would be quite nice. Im You have failed to tell us the graphics card you have.... gonna be hard to help you know.... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Mon Jun 18 18: 8:57 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from dragon.nuxi.com (trang.nuxi.com [206.40.252.115]) by hub.freebsd.org (Postfix) with ESMTP id 1062A37B401 for ; Mon, 18 Jun 2001 18:08:55 -0700 (PDT) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.11.3/8.11.1) id f5J184a00853; Mon, 18 Jun 2001 18:08:04 -0700 (PDT) (envelope-from obrien) Date: Mon, 18 Jun 2001 18:08:04 -0700 From: "David O'Brien" To: Paul Halliday Cc: Andrew Gallatin , "Crespo, Ramon" , "'freebsd-alpha@freebsd.org'" Subject: Re: X11 Settings for the MiataGL Message-ID: <20010618180804.E540@dragon.nuxi.com> Reply-To: freebsd-alpha@FreeBSD.ORG References: <15150.17051.201667.856092@grasshopper.cs.duke.edu> <3B2E4BBE.6FEC26EF@penix.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <3B2E4BBE.6FEC26EF@penix.org>; from dp@penix.org on Mon, Jun 18, 2001 at 02:43:10PM -0400 X-Operating-System: FreeBSD 5.0-CURRENT Organization: The NUXI BSD group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Mon, Jun 18, 2001 at 02:43:10PM -0400, Paul Halliday wrote: > > The issue with using the text-only xf86config is that it does not > > know about moused's sysmouse. Thus you either cannot use moused, > > or you must hack the /etc/XF86Config file xf86config creates to > > specify sysmouse. > > Umm.. > as200 xf86config-> > > Now give the full device name that the device is connected to, for > example /dev/tty00. Just pressing enter will use the default, > /dev/mouse. > > Mouse device: /dev/sysmouse Uh.. you have given the mouse device, but not protocol to use. X has to know both. Speaking M$ Intelmouse to /dev/sysmouse is not a productive thing. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Mon Jun 18 18:10:12 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from dragon.nuxi.com (trang.nuxi.com [206.40.252.115]) by hub.freebsd.org (Postfix) with ESMTP id B767937B407 for ; Mon, 18 Jun 2001 18:10:10 -0700 (PDT) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.11.3/8.11.1) id f5J1A7N00874; Mon, 18 Jun 2001 18:10:07 -0700 (PDT) (envelope-from obrien) Date: Mon, 18 Jun 2001 18:10:07 -0700 From: freebsd-alpha@FreeBSD.ORG To: "Crespo, Ramon" Cc: "'Andrew Gallatin'" , "'freebsd-alpha@freebsd.org'" Subject: Re: X11 Settings for the MiataGL Message-ID: <20010618181007.F540@dragon.nuxi.com> Reply-To: freebsd-alpha@FreeBSD.ORG References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from IMCEAEX-_O=STIS_OU=STIS_CN=RECIPIENTS_CN=RCRESPO@STIS.com on Mon, Jun 18, 2001 at 04:46:30PM -0400 X-Operating-System: FreeBSD 5.0-CURRENT Organization: The NUXI BSD group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Mon, Jun 18, 2001 at 04:46:30PM -0400, Crespo, Ramon wrote: > I have an > old Diamond Stealth 64 with 4MB of ram that I might be able to stick in > there .. S3 Vision968 Chipset That will work very well (just not the speadiest thing). I have used an S3 968 in an AS 250. Matrox Millieum(sp) I and II are my favorate for the PWS. -- -- David (obrien@FreeBSD.org) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Mon Jun 18 18:12: 5 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from dragon.nuxi.com (trang.nuxi.com [206.40.252.115]) by hub.freebsd.org (Postfix) with ESMTP id 9798037B403 for ; Mon, 18 Jun 2001 18:12:03 -0700 (PDT) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.11.3/8.11.1) id f5J1C1g00957; Mon, 18 Jun 2001 18:12:01 -0700 (PDT) (envelope-from obrien) Date: Mon, 18 Jun 2001 18:12:01 -0700 From: freebsd-alpha@freebsd.org To: "Crespo, Ramon" Cc: "'freebsd-alpha@freebsd.org'" Subject: Re: XF86 4.x on FreeBSD/Alpha Message-ID: <20010618181201.G540@dragon.nuxi.com> Reply-To: freebsd-alpha@freebsd.org References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from IMCEAEX-_O=STIS_OU=STIS_CN=RECIPIENTS_CN=RCRESPO@STIS.com on Mon, Jun 18, 2001 at 06:10:48PM -0400 X-Operating-System: FreeBSD 5.0-CURRENT Organization: The NUXI BSD group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Mon, Jun 18, 2001 at 06:10:48PM -0400, Crespo, Ramon wrote: > .. also is there any chance to compile 4.1.x > from scratch out of ports or something. Yes. But why not just install the Port? ftp://ftp.freebsd.org/pub/FreeBSD/ports/alpha/packages-4.3-release/All/ -- -- David (obrien@FreeBSD.org) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Mon Jun 18 18:13:45 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from dragon.nuxi.com (trang.nuxi.com [206.40.252.115]) by hub.freebsd.org (Postfix) with ESMTP id 2E8FA37B407 for ; Mon, 18 Jun 2001 18:13:43 -0700 (PDT) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.11.3/8.11.1) id f5J1DTZ00970; Mon, 18 Jun 2001 18:13:29 -0700 (PDT) (envelope-from obrien) Date: Mon, 18 Jun 2001 18:13:28 -0700 From: "David O'Brien" To: Peter Jeremy Cc: Wilko Bulte , "Crespo, Ramon" , freebsd-alpha@FreeBSD.ORG Subject: Re: XF86 4.x on FreeBSD/Alpha Message-ID: <20010618181328.H540@dragon.nuxi.com> Reply-To: obrien@FreeBSD.ORG References: <20010619001254.F2135@freebie.xs4all.nl> <20010619083943.E95583@gsmx07.alcatel.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010619083943.E95583@gsmx07.alcatel.com.au>; from peter.jeremy@alcatel.com.au on Tue, Jun 19, 2001 at 08:39:43AM +1000 X-Operating-System: FreeBSD 5.0-CURRENT Organization: The NUXI BSD group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Tue, Jun 19, 2001 at 08:39:43AM +1000, Peter Jeremy wrote: > On 2001-Jun-19 00:12:55 +0200, Wilko Bulte wrote: > >Problem is that TGA cards are not yet supported as console devices > >so you will be driving blind (I guess) while X has not yet [been] started. > > A TGA console driver for FreeBSD is currently awaiting someone with > commit privs to commit it. Two people offered - the first withdrew > his offer due to changed circumstances and the second appears to have > lost interest. No, he is waiting until -current Alpha is solid enough so that if I have a panic I know if it is the driver, ufs, or VM code. Unfortetnly your driver has become ready to commit at a bad time for the -current Alpha. Please no one commit this driver. I *am* still working on it. -- -- David (obrien@FreeBSD.org) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Mon Jun 18 18:14:25 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from dragon.nuxi.com (trang.nuxi.com [206.40.252.115]) by hub.freebsd.org (Postfix) with ESMTP id 032E937B401 for ; Mon, 18 Jun 2001 18:14:23 -0700 (PDT) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.11.3/8.11.1) id f5J1EIH00981; Mon, 18 Jun 2001 18:14:18 -0700 (PDT) (envelope-from obrien) Date: Mon, 18 Jun 2001 18:14:18 -0700 From: "David O'Brien" To: "Crespo, Ramon" Cc: "'Wilko Bulte'" , "'freebsd-alpha@freebsd.org'" Subject: Re: XF86 4.x on FreeBSD/Alpha Message-ID: <20010618181418.I540@dragon.nuxi.com> Reply-To: obrien@FreeBSD.ORG References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from IMCEAEX-_O=STIS_OU=STIS_CN=RECIPIENTS_CN=RCRESPO@STIS.com on Mon, Jun 18, 2001 at 06:16:53PM -0400 X-Operating-System: FreeBSD 5.0-CURRENT Organization: The NUXI BSD group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Mon, Jun 18, 2001 at 06:16:53PM -0400, Crespo, Ramon wrote: > Once support for TGA devices comes abound > I can put the old card back in there .. or maybe I can keep them both and > just have the monitor connected to the one that works. The video card is Just use a serial console, and start xdm on boot up. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Mon Jun 18 18:16:16 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from dragon.nuxi.com (trang.nuxi.com [206.40.252.115]) by hub.freebsd.org (Postfix) with ESMTP id 4460737B401 for ; Mon, 18 Jun 2001 18:16:14 -0700 (PDT) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.11.3/8.11.1) id f5J1GBf01038; Mon, 18 Jun 2001 18:16:11 -0700 (PDT) (envelope-from obrien) Date: Mon, 18 Jun 2001 18:16:11 -0700 From: "David O'Brien" To: Wilko Bulte Cc: freebsd-alpha@freebsd.org Subject: Re: going nowhere Message-ID: <20010618181611.J540@dragon.nuxi.com> Reply-To: obrien@freebsd.org References: <20010617221432.A13492@freebie.xs4all.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010617221432.A13492@freebie.xs4all.nl>; from wkb@freebie.xs4all.nl on Sun, Jun 17, 2001 at 10:14:32PM +0200 X-Operating-System: FreeBSD 5.0-CURRENT Organization: The NUXI BSD group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Sun, Jun 17, 2001 at 10:14:32PM +0200, Wilko Bulte wrote: > As I don't remember: is the 'going nowhere without my init' bug now > fixed in RELENG_4? I think it is, but I'm not sure. It has been glossed over. libdisk will no longer err() (==> exit()). Rather it will just return to the caller. We still need to figure out why libdisk is getting pissy about some disk labels. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Mon Jun 18 18:19:49 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from dragon.nuxi.com (trang.nuxi.com [206.40.252.115]) by hub.freebsd.org (Postfix) with ESMTP id 4015537B401 for ; Mon, 18 Jun 2001 18:19:47 -0700 (PDT) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.11.3/8.11.1) id f5J1JiD01058; Mon, 18 Jun 2001 18:19:44 -0700 (PDT) (envelope-from obrien) Date: Mon, 18 Jun 2001 18:19:44 -0700 From: "David O'Brien" To: Wilko Bulte Cc: freebsd-alpha@freebsd.org Subject: Re: axing 'device plip' from GENERIC? Message-ID: <20010618181944.K540@dragon.nuxi.com> Reply-To: obrien@freebsd.org References: <20010617220618.A13414@freebie.xs4all.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010617220618.A13414@freebie.xs4all.nl>; from wkb@freebie.xs4all.nl on Sun, Jun 17, 2001 at 10:06:18PM +0200 X-Operating-System: FreeBSD 5.0-CURRENT Organization: The NUXI BSD group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Sun, Jun 17, 2001 at 10:06:18PM +0200, Wilko Bulte wrote: > Anybody opposed to me axing: > > device plip # TCP/IP over parallel > > from GENERIC for the Alpha? I don't see any reason to do so. It is already out of the install floppy. But there is no harm in it staying in GENERIC. > On all alpha models I've ever put FreeBSD on I just saw an error about > plip not wanting to probe/attach/whatever (forgot the exact error). If we take it out, it will never work again -- it will bitrot. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Mon Jun 18 18:50:54 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from tomts14-srv.bellnexxia.net (tomts14.bellnexxia.net [209.226.175.35]) by hub.freebsd.org (Postfix) with ESMTP id C1B2237B401 for ; Mon, 18 Jun 2001 18:50:51 -0700 (PDT) (envelope-from dp@penix.org) Received: from penix.org ([64.228.106.161]) by tomts14-srv.bellnexxia.net (InterMail vM.4.01.03.16 201-229-121-116-20010115) with ESMTP id <20010619015050.YZHN2764.tomts14-srv.bellnexxia.net@penix.org>; Mon, 18 Jun 2001 21:50:50 -0400 Message-ID: <3B2EB34C.253019C8@penix.org> Date: Mon, 18 Jun 2001 22:05:00 -0400 From: Paul Halliday X-Mailer: Mozilla 4.76 [en] (X11; U; FreeBSD 4.3-RC i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-alpha@FreeBSD.ORG Cc: Andrew Gallatin , "Crespo, Ramon" Subject: Re: X11 Settings for the MiataGL References: <15150.17051.201667.856092@grasshopper.cs.duke.edu> <3B2E4BBE.6FEC26EF@penix.org> <20010618180804.E540@dragon.nuxi.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org David O'Brien wrote: > > On Mon, Jun 18, 2001 at 02:43:10PM -0400, Paul Halliday wrote: > > > The issue with using the text-only xf86config is that it does not > > > know about moused's sysmouse. Thus you either cannot use moused, > > > or you must hack the /etc/XF86Config file xf86config creates to > > > specify sysmouse. > > > > Umm.. > > as200 xf86config-> > > > > Now give the full device name that the device is connected to, for > > example /dev/tty00. Just pressing enter will use the default, > > /dev/mouse. > > > > Mouse device: /dev/sysmouse > > Uh.. you have given the mouse device, but not protocol to use. X has to > know both. Speaking M$ Intelmouse to /dev/sysmouse is not a productive > thing. I was merely stating that their is no need to edit XF86Config by hand. Unless you fuck something up when you first run it. -- Paul H. ___________________ http://dp.penix.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Mon Jun 18 22:50:14 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from freebie.xs4all.nl (freebie.xs4all.nl [213.84.32.253]) by hub.freebsd.org (Postfix) with ESMTP id 310F837B403 for ; Mon, 18 Jun 2001 22:50:11 -0700 (PDT) (envelope-from wkb@freebie.xs4all.nl) Received: (from wkb@localhost) by freebie.xs4all.nl (8.11.3/8.11.3) id f5J5o9104407; Tue, 19 Jun 2001 07:50:09 +0200 (CEST) (envelope-from wkb) Date: Tue, 19 Jun 2001 07:50:09 +0200 From: Wilko Bulte To: freebsd-alpha@FreeBSD.ORG Cc: "Crespo, Ramon" , "'Andrew Gallatin'" Subject: Re: X11 Settings for the MiataGL Message-ID: <20010619075009.A4260@freebie.xs4all.nl> References: <20010618181007.F540@dragon.nuxi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010618181007.F540@dragon.nuxi.com>; from freebsd-alpha@FreeBSD.ORG on Mon, Jun 18, 2001 at 06:10:07PM -0700 X-OS: FreeBSD 4.3-STABLE X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Mon, Jun 18, 2001 at 06:10:07PM -0700, freebsd-alpha@FreeBSD.ORG wrote: > On Mon, Jun 18, 2001 at 04:46:30PM -0400, Crespo, Ramon wrote: > > I have an > > old Diamond Stealth 64 with 4MB of ram that I might be able to stick in > > there .. S3 Vision968 Chipset > > That will work very well (just not the speadiest thing). > I have used an S3 968 in an AS 250. > > Matrox Millieum(sp) I and II are my favorate for the PWS. Millenium -- | / o / / _ Arnhem, The Netherlands email: wilko@FreeBSD.org |/|/ / / /( (_) Bulte 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 Mon Jun 18 22:53:44 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from freebie.xs4all.nl (freebie.xs4all.nl [213.84.32.253]) by hub.freebsd.org (Postfix) with ESMTP id EF43A37B401; Mon, 18 Jun 2001 22:53:40 -0700 (PDT) (envelope-from wkb@freebie.xs4all.nl) Received: (from wkb@localhost) by freebie.xs4all.nl (8.11.3/8.11.3) id f5J5reL04472; Tue, 19 Jun 2001 07:53:40 +0200 (CEST) (envelope-from wkb) Date: Tue, 19 Jun 2001 07:53:40 +0200 From: Wilko Bulte To: "David O'Brien" Cc: freebsd-alpha@freebsd.org Subject: Re: axing 'device plip' from GENERIC? Message-ID: <20010619075340.A4458@freebie.xs4all.nl> References: <20010617220618.A13414@freebie.xs4all.nl> <20010618181944.K540@dragon.nuxi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010618181944.K540@dragon.nuxi.com>; from obrien@freebsd.org on Mon, Jun 18, 2001 at 06:19:44PM -0700 X-OS: FreeBSD 4.3-STABLE X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Mon, Jun 18, 2001 at 06:19:44PM -0700, David O'Brien wrote: > On Sun, Jun 17, 2001 at 10:06:18PM +0200, Wilko Bulte wrote: > > Anybody opposed to me axing: > > > > device plip # TCP/IP over parallel > > > > from GENERIC for the Alpha? > > I don't see any reason to do so. It is already out of the install > floppy. But there is no harm in it staying in GENERIC. And no use either. I could comment it out and mark it 'currently broken on Alpha'? > > On all alpha models I've ever put FreeBSD on I just saw an error about > > plip not wanting to probe/attach/whatever (forgot the exact error). > > If we take it out, it will never work again -- it will bitrot. Considering that has not worked on alpha that I can remember I would be surprised if anybody 'unrotted' it. Wilko -- | / o / / _ Arnhem, The Netherlands email: wilko@FreeBSD.org |/|/ / / /( (_) Bulte http://www.FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Tue Jun 19 10:15:45 2001 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 D65E337B403 for ; Tue, 19 Jun 2001 10:15:42 -0700 (PDT) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.3/8.9.3) with ESMTP id NAA20128; Tue, 19 Jun 2001 13:15:39 -0400 (EDT) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.11.3/8.9.1) id f5JHF9k36396; Tue, 19 Jun 2001 13:15:09 -0400 (EDT) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <15151.34973.411972.726083@grasshopper.cs.duke.edu> Date: Tue, 19 Jun 2001 13:15:09 -0400 (EDT) To: "Crespo, Ramon" Cc: freebsd-alpha@freebsd.org Subject: RE: XF86 4.x on FreeBSD/Alpha In-Reply-To: References: X-Mailer: VM 6.75 under 21.1 (patch 12) "Channel Islands" XEmacs Lucid Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Crespo, Ramon writes: > pcib1@pci0:11:0: class=0x060400 card=0x00000000 chip=0x00211011 > rev=0x01 hdr=0x01 > pcib2@pci0:20:0: class=0x060400 card=0x00000000 chip=0x00241011 > rev=0x02 hdr=0x01 > none0@pci1:4:0: class=0x030000 card=0x00000000 chip=0x00a01013 rev=0x47 > hdr=0x00 > none1@pci1:5:0: class=0x038000 card=0x00000000 chip=0x00eb1091 rev=0x40 > hdr=0x00 > OK, so this (0x00eb1091) is the "good" half of your graphics card. Apparently, this is an Intergraph card (0x1091), device 0x00eb. However, XFree86 apparently doesn't know diddly-squat about it (at least from a grep for 0x1091). Its TGA driver is looking for a DEC chip, not an intergraph one. So, it looks like this card will be a waste of time for you. Try your old S3 based card.. Sorry.. Drew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Tue Jun 19 11: 5:32 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from mail.gmx.net (pop.gmx.net [194.221.183.20]) by hub.freebsd.org (Postfix) with SMTP id 41CF337B407 for ; Tue, 19 Jun 2001 11:05:30 -0700 (PDT) (envelope-from K_Berbach@gmx.de) Received: (qmail 1779 invoked by uid 0); 19 Jun 2001 18:05:28 -0000 Received: from unknown (HELO nazgul) (62.16.151.38) by mail.gmx.net (mp003-rz3) with SMTP; 19 Jun 2001 18:05:28 -0000 From: "Klaus Berbach" To: "freebsd-alpha@freebsd.org" Date: Tue, 19 Jun 2001 20:05:41 +0200 Reply-To: "Klaus Berbach" X-Mailer: PMMail 2000 Professional (2.20.2360) For Windows 2000 (5.0.2195;2) In-Reply-To: <15150.28610.864423.75714@grasshopper.cs.duke.edu> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Subject: RE: X11 Settings for the MiataGL Message-Id: <20010619180530.41CF337B407@hub.freebsd.org> Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org The Powerstorm Cards (TGA2) are neither supported by XFRee3 nor 4. I have one of those (4D40T) lying around here, too. Impressive Design, but .... If you have the chance to get an Elsa Gloria Synergy (Permedia 2) it=B4s a fine choice, especially if you plan to spend 100 Bucks onTru64 someday as second OS on alpha. One of the few cards that run with both (above 640x480x16) - of course not 3D accelerated. Don=B4t know wether this is tru for other Pernedia2 based cards, too. I think the Matrox Millenuim is supported by Tru64, too - but not sure. Hopefulkly this wasn=B4t too Off Topic. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Tue Jun 19 11: 9:39 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from freebie.xs4all.nl (freebie.xs4all.nl [213.84.32.253]) by hub.freebsd.org (Postfix) with ESMTP id A1D6637B401 for ; Tue, 19 Jun 2001 11:09:36 -0700 (PDT) (envelope-from wkb@freebie.xs4all.nl) Received: (from wkb@localhost) by freebie.xs4all.nl (8.11.3/8.11.3) id f5JI9YR00962; Tue, 19 Jun 2001 20:09:34 +0200 (CEST) (envelope-from wkb) Date: Tue, 19 Jun 2001 20:09:34 +0200 From: Wilko Bulte To: Klaus Berbach Cc: "freebsd-alpha@freebsd.org" Subject: Re: X11 Settings for the MiataGL Message-ID: <20010619200934.A948@freebie.xs4all.nl> References: <15150.28610.864423.75714@grasshopper.cs.duke.edu> <20010619180530.41CF337B407@hub.freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit User-Agent: Mutt/1.2.5i In-Reply-To: <20010619180530.41CF337B407@hub.freebsd.org>; from K_Berbach@gmx.de on Tue, Jun 19, 2001 at 08:05:41PM +0200 X-OS: FreeBSD 4.3-STABLE X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Tue, Jun 19, 2001 at 08:05:41PM +0200, Klaus Berbach wrote: > The Powerstorm Cards (TGA2) are neither supported by > XFRee3 nor 4. I have one of those (4D40T) lying around > here, too. Impressive Design, but .... > If you have the chance to get an Elsa Gloria Synergy > (Permedia 2) it´s a fine choice, especially if you plan > to spend 100 Bucks onTru64 someday as second OS on > alpha. One of the few cards that run with both (above > 640x480x16) - of course not 3D accelerated. Don´t know > wether this is tru for other Pernedia2 based cards, > too. > I think the Matrox Millenuim is supported by Tru64, too > - but not sure. Hmm. I don't think so. The list of supported cards for X on T64 tends to be rather short. W/ -- | / o / / _ Arnhem, The Netherlands email: wilko@FreeBSD.org |/|/ / / /( (_) Bulte http://www.FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Tue Jun 19 12:26:24 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from meow.osd.bsdi.com (meow.osd.bsdi.com [204.216.28.88]) by hub.freebsd.org (Postfix) with ESMTP id C1D1037B406 for ; Tue, 19 Jun 2001 12:26:19 -0700 (PDT) (envelope-from jhb@FreeBSD.org) Received: from laptop.baldwin.cx (john@jhb-laptop.osd.bsdi.com [204.216.28.241]) by meow.osd.bsdi.com (8.11.3/8.11.2) with ESMTP id f5JJQC114206; Tue, 19 Jun 2001 12:26:12 -0700 (PDT) (envelope-from jhb@FreeBSD.org) 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 In-Reply-To: <20010618180804.E540@dragon.nuxi.com> Date: Tue, 19 Jun 2001 11:44:43 -0700 (PDT) From: John Baldwin To: "David O'Brien" Subject: Re: X11 Settings for the MiataGL Cc: "Crespo, Ramon" Cc: "Crespo, Ramon" , Andrew Gallatin , Paul Halliday Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On 19-Jun-01 David O'Brien wrote: > On Mon, Jun 18, 2001 at 02:43:10PM -0400, Paul Halliday wrote: >> > The issue with using the text-only xf86config is that it does not >> > know about moused's sysmouse. Thus you either cannot use moused, >> > or you must hack the /etc/XF86Config file xf86config creates to >> > specify sysmouse. >> >> Umm.. >> as200 xf86config-> >> >> Now give the full device name that the device is connected to, for >> example /dev/tty00. Just pressing enter will use the default, >> /dev/mouse. >> >> Mouse device: /dev/sysmouse > > Uh.. you have given the mouse device, but not protocol to use. X has to > know both. Speaking M$ Intelmouse to /dev/sysmouse is not a productive > thing. X 4 can autodetect the sysmouse protocol. You don't have to set it explicitly to "sysmouse". -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Tue Jun 19 15:37: 4 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from meow.osd.bsdi.com (meow.osd.bsdi.com [204.216.28.88]) by hub.freebsd.org (Postfix) with ESMTP id AC3E137B403 for ; Tue, 19 Jun 2001 15:36:58 -0700 (PDT) (envelope-from jhb@FreeBSD.org) Received: from laptop.baldwin.cx (john@jhb-laptop.osd.bsdi.com [204.216.28.241]) by meow.osd.bsdi.com (8.11.3/8.11.2) with ESMTP id f5JMao116818 for ; Tue, 19 Jun 2001 15:36:50 -0700 (PDT) (envelope-from jhb@FreeBSD.org) 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: Tue, 19 Jun 2001 15:15:16 -0700 (PDT) From: John Baldwin To: alpha@FreeBSD.org Subject: SRM Help Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Does anyone know how to examine the registers of other CPU's from SRM? I've discovered that one can arbitrarily halt processors from SRM using 'stop'. I'd like to examine the RA of teh other CPU if possible however to see where it was. I think I'm about ready to figure out how to walk back the stack via just examining memory in SRM so I can get tracebacks, too. (Sure would be nice if gdb could talk to SRM over a serial console some day.. ) -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Tue Jun 19 15:54:27 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from tomts14-srv.bellnexxia.net (tomts14.bellnexxia.net [209.226.175.35]) by hub.freebsd.org (Postfix) with ESMTP id 010B537B401; Tue, 19 Jun 2001 15:54:25 -0700 (PDT) (envelope-from dp@penix.org) Received: from penix.org ([64.228.103.184]) by tomts14-srv.bellnexxia.net (InterMail vM.4.01.03.16 201-229-121-116-20010115) with ESMTP id <20010619225423.MESE2764.tomts14-srv.bellnexxia.net@penix.org>; Tue, 19 Jun 2001 18:54:23 -0400 Message-ID: <3B2FDB73.AA21BD43@penix.org> Date: Tue, 19 Jun 2001 19:08:35 -0400 From: Paul Halliday X-Mailer: Mozilla 4.76 [en] (X11; U; FreeBSD 4.3-RC i386) X-Accept-Language: en MIME-Version: 1.0 To: John Baldwin Cc: alpha@FreeBSD.ORG Subject: Re: SRM Help References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org John Baldwin wrote: > > Does anyone know how to examine the registers of other CPU's from SRM? > > I've discovered that one can arbitrarily halt processors from SRM using 'stop'. > I'd like to examine the RA of teh other CPU if possible however to see where it > was. I think I'm about ready to figure out how to walk back the stack via just > examining memory in SRM so I can get tracebacks, too. (Sure would be nice if > gdb could talk to SRM over a serial console some day.. ) > > -- > > John Baldwin -- http://www.FreeBSD.org/~jhb/ > PGP Key: http://www.baldwin.cx/~john/pgpkey.asc > "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-alpha" in the body of the message Do you mean like >>>examine -ipr ? -- Paul H. ___________________ http://dp.penix.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Tue Jun 19 16:15:17 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from technokratis.com (modemcable052.174-202-24.mtl.mc.videotron.ca [24.202.174.52]) by hub.freebsd.org (Postfix) with ESMTP id 9117337B403 for ; Tue, 19 Jun 2001 16:15:14 -0700 (PDT) (envelope-from bmilekic@technokratis.com) Received: (from bmilekic@localhost) by technokratis.com (8.11.3/8.11.3) id f5JNG2428602 for freebsd-alpha@freebsd.org; Tue, 19 Jun 2001 19:16:02 -0400 (EDT) (envelope-from bmilekic) Date: Tue, 19 Jun 2001 19:16:02 -0400 From: Bosko Milekic To: freebsd-alpha@freebsd.org Subject: vx, lge, nge, dc, rl, sf, sis, sk, vr, wb users please TEST Message-ID: <20010619191602.A28591@technokratis.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Hi Guys, I know I've been bothering you a lot lately, but there's one more thing that I need some (or one) of you to test out, if you're using one (or more) of the following: - if_vx - if_lge - if_nge - if_dc - if_rl - if_sf - if_sis - if_sk - if_vr - if_wb and -CURRENT to test out: http://people.freebsd.org/~bmilekic/code/mdevget.patch as soon as possible. Thanks, -- Bosko Milekic bmilekic@technokratis.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Tue Jun 19 16:15:52 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from tomts6-srv.bellnexxia.net (tomts6.bellnexxia.net [209.226.175.26]) by hub.freebsd.org (Postfix) with ESMTP id 8636F37B403 for ; Tue, 19 Jun 2001 16:15:50 -0700 (PDT) (envelope-from dp@penix.org) Received: from penix.org ([64.228.103.184]) by tomts6-srv.bellnexxia.net (InterMail vM.4.01.03.16 201-229-121-116-20010115) with ESMTP id <20010619231549.NHTG29618.tomts6-srv.bellnexxia.net@penix.org> for ; Tue, 19 Jun 2001 19:15:49 -0400 Message-ID: <3B2FE078.F84CD6B6@penix.org> Date: Tue, 19 Jun 2001 19:30:00 -0400 From: Paul Halliday X-Mailer: Mozilla 4.76 [en] (X11; U; FreeBSD 4.3-RC i386) X-Accept-Language: en MIME-Version: 1.0 To: alpha@freebsd.org Subject: da1 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org I find the following a little strange from a machine that was shut-down properly.. (da1:sym0:0:1:0): WRITE(06). CDB: a 1a 0 1e 20 (da1:sym0:0:1:0): MEDIUM ERROR info:1a001e asc:3,0 (da1:sym0:0:1:0): Peripheral device write fault Cycles with three different values for CDB. drops me into single user. any ideas? -- Paul H. ___________________ http://dp.penix.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Tue Jun 19 16:18:55 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from meow.osd.bsdi.com (meow.osd.bsdi.com [204.216.28.88]) by hub.freebsd.org (Postfix) with ESMTP id 60CE637B401 for ; Tue, 19 Jun 2001 16:18:52 -0700 (PDT) (envelope-from jhb@FreeBSD.org) Received: from laptop.baldwin.cx (john@jhb-laptop.osd.bsdi.com [204.216.28.241]) by meow.osd.bsdi.com (8.11.3/8.11.2) with ESMTP id f5JNIg117380; Tue, 19 Jun 2001 16:18:42 -0700 (PDT) (envelope-from jhb@FreeBSD.org) 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 In-Reply-To: <3B2FDB73.AA21BD43@penix.org> Date: Tue, 19 Jun 2001 16:00:31 -0700 (PDT) From: John Baldwin To: Paul Halliday Subject: Re: SRM Help Cc: alpha@FreeBSD.org Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On 19-Jun-01 Paul Halliday wrote: > John Baldwin wrote: >> >> Does anyone know how to examine the registers of other CPU's from SRM? >> >> I've discovered that one can arbitrarily halt processors from SRM using >> 'stop'. >> I'd like to examine the RA of teh other CPU if possible however to see where >> it >> was. I think I'm about ready to figure out how to walk back the stack via >> just >> examining memory in SRM so I can get tracebacks, too. (Sure would be nice >> if >> gdb could talk to SRM over a serial console some day.. ) >> >> -- >> >> John Baldwin -- http://www.FreeBSD.org/~jhb/ >> PGP Key: http://www.baldwin.cx/~john/pgpkey.asc >> "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ >> >> To Unsubscribe: send mail to majordomo@FreeBSD.org >> with "unsubscribe freebsd-alpha" in the body of the message > > Do you mean like >>>examine -ipr ? Doh, I've already rebooted the machine. Basically, I want to do the equivalent of 'e -gpr ra' for a secondary CPU. Hmm, seems -ipr is either a subset or superset of -gpr. (If anyone has real, nice detailed information on SRM commands in general that would also be nice.) -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Tue Jun 19 16:19:32 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from mass.dis.org (mass.dis.org [216.240.45.41]) by hub.freebsd.org (Postfix) with ESMTP id 66F8A37B403 for ; Tue, 19 Jun 2001 16:19:26 -0700 (PDT) (envelope-from msmith@mass.dis.org) Received: from mass.dis.org (localhost [127.0.0.1]) by mass.dis.org (8.11.3/8.11.3) with ESMTP id f5JNUlY01679; Tue, 19 Jun 2001 16:30:47 -0700 (PDT) (envelope-from msmith@mass.dis.org) Message-Id: <200106192330.f5JNUlY01679@mass.dis.org> X-Mailer: exmh version 2.1.1 10/15/1999 To: Paul Halliday Cc: alpha@freebsd.org Subject: Re: da1 In-reply-to: Your message of "Tue, 19 Jun 2001 19:30:00 EDT." <3B2FE078.F84CD6B6@penix.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 19 Jun 2001 16:30:47 -0700 From: Mike Smith Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org The disk is dead, or at least dying. Check the camcontrol manpage for instructions on enabling AWRE, and if it's enabled and this still happens, throw the disk out/RMA it/etc. > I find the following a little strange from a machine that was shut-down > properly.. > (da1:sym0:0:1:0): WRITE(06). CDB: a 1a 0 1e 20 > (da1:sym0:0:1:0): MEDIUM ERROR info:1a001e asc:3,0 > (da1:sym0:0:1:0): Peripheral device write fault > > Cycles with three different values for CDB. > drops me into single user. > > any ideas? > > -- > Paul H. > ___________________ > http://dp.penix.org > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-alpha" in the body of the message -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Tue Jun 19 16:31:39 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from tomts7-srv.bellnexxia.net (tomts7.bellnexxia.net [209.226.175.40]) by hub.freebsd.org (Postfix) with ESMTP id 1425937B401; Tue, 19 Jun 2001 16:31:37 -0700 (PDT) (envelope-from dp@penix.org) Received: from penix.org ([64.228.103.184]) by tomts7-srv.bellnexxia.net (InterMail vM.4.01.03.16 201-229-121-116-20010115) with ESMTP id <20010619233135.WDXU7745.tomts7-srv.bellnexxia.net@penix.org>; Tue, 19 Jun 2001 19:31:35 -0400 Message-ID: <3B2FE42B.3438062C@penix.org> Date: Tue, 19 Jun 2001 19:45:47 -0400 From: Paul Halliday X-Mailer: Mozilla 4.76 [en] (X11; U; FreeBSD 4.3-RC i386) X-Accept-Language: en MIME-Version: 1.0 To: John Baldwin Cc: alpha@FreeBSD.org Subject: Re: SRM Help References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org John Baldwin wrote: > > Doh, I've already rebooted the machine. Basically, I want to do the equivalent > of 'e -gpr ra' for a secondary CPU. Hmm, seems -ipr is either a subset or > superset of -gpr. (If anyone has real, nice detailed information on SRM > commands in general that would also be nice.) Define _detailed_. The manual for an alphastation 200 contains a thorough explanation for all of the console commands. If this is all you require I could hook you up. -- Paul H. ___________________ http://dp.penix.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Tue Jun 19 17:43:41 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from meow.osd.bsdi.com (meow.osd.bsdi.com [204.216.28.88]) by hub.freebsd.org (Postfix) with ESMTP id 3D5D337B401 for ; Tue, 19 Jun 2001 17:43:35 -0700 (PDT) (envelope-from jhb@FreeBSD.org) Received: from laptop.baldwin.cx (john@jhb-laptop.osd.bsdi.com [204.216.28.241]) by meow.osd.bsdi.com (8.11.3/8.11.2) with ESMTP id f5K0gi118423; Tue, 19 Jun 2001 17:42:44 -0700 (PDT) (envelope-from jhb@FreeBSD.org) 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 In-Reply-To: <3B2FE42B.3438062C@penix.org> Date: Tue, 19 Jun 2001 17:29:48 -0700 (PDT) From: John Baldwin To: Paul Halliday Subject: Re: SRM Help Cc: alpha@FreeBSD.org Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On 19-Jun-01 Paul Halliday wrote: > John Baldwin wrote: > >> >> Doh, I've already rebooted the machine. Basically, I want to do the >> equivalent >> of 'e -gpr ra' for a secondary CPU. Hmm, seems -ipr is either a subset or >> superset of -gpr. (If anyone has real, nice detailed information on SRM >> commands in general that would also be nice.) > > Define _detailed_. The manual for an alphastation 200 contains > a thorough explanation for all of the console commands. If this is all > you require > I could hook you up. One that would explain what the device address for another CPU is for the examine command, for example. The help command in SRM itself is rather limited in that it assumes you already know what all the switches to the various commands mean, etc. In other words, explain what each switch to each command is, what all the commands are, etc. -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Tue Jun 19 17:55: 9 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from netau1.alcanet.com.au (ntp.alcanet.com.au [203.62.196.27]) by hub.freebsd.org (Postfix) with ESMTP id 4C0F537B406; Tue, 19 Jun 2001 17:55:02 -0700 (PDT) (envelope-from jeremyp@gsmx07.alcatel.com.au) Received: from mfg1.cim.alcatel.com.au (mfg1.cim.alcatel.com.au [139.188.23.1]) by netau1.alcanet.com.au (8.9.3 (PHNE_22672)/8.9.3) with ESMTP id KAA24695; Wed, 20 Jun 2001 10:54:58 +1000 (EST) Received: from gsmx07.alcatel.com.au by cim.alcatel.com.au (PMDF V5.2-32 #37645) with ESMTP id <01K4ZJY4WNTCVNZA9N@cim.alcatel.com.au>; Wed, 20 Jun 2001 10:54:54 +1000 Received: (from jeremyp@localhost) by gsmx07.alcatel.com.au (8.11.1/8.11.1) id f5K0stm18465; Wed, 20 Jun 2001 10:54:55 +1000 (EST envelope-from jeremyp) Content-return: prohibited Date: Wed, 20 Jun 2001 10:54:54 +1000 From: Peter Jeremy Subject: Re: SRM Help In-reply-to: ; from jhb@FreeBSD.ORG on Tue, Jun 19, 2001 at 04:00:31PM -0700 To: John Baldwin Cc: Paul Halliday , alpha@FreeBSD.ORG Mail-Followup-To: John Baldwin , Paul Halliday , alpha@FreeBSD.ORG Message-id: <20010620105454.U95583@gsmx07.alcatel.com.au> MIME-version: 1.0 Content-type: text/plain; charset=us-ascii Content-disposition: inline User-Agent: Mutt/1.2.5i References: <3B2FDB73.AA21BD43@penix.org> Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On 2001-Jun-19 16:00:31 -0700, John Baldwin wrote: > Basically, I want to do the >equivalent of 'e -gpr ra' for a secondary CPU. I've looked through the manuals for both 4100 and ES40's and it's not clear how deposit and examine handle per-cpu resources (registers) when there are multiple CPUs (the ES40 manuals side-step the issue by not documenting the deposit or examine commands). It would seem reasonable that if you stop only 1 CPU then examine refers to that CPU, but this doesn't scale if you have more than 1 CPU stopped. > Hmm, seems -ipr is either a subset or superset of -gpr. The 4100 manuals document the following address spaces for deposit/examine: fpr Floating-point registers F0-F31 gpr General register R0-R31 ipr Internal processor register pt PALtemp register PT0-PT31 pmem physical memory vmem virtual memory Based on my reading of a 21066 (LCA) datasheet (the only one I have handy): fpr, gpr and ipr are disjoint, with pt a subset of ipr. The LCA HW_MFPR and HW_MTPR instructions support PALtemp, load-store unit (LSU) and instruction decode unit (IDU) register sets. My past experimenting on a Multia suggests that the ipr space is discontiguous (and attempting to reference an illegal register triggers an SRM exception), which makes it difficult to identify all the ipr's without knowing them in advance. > (If anyone has real, nice detailed information on SRM commands in >general that would also be nice.) I'll have a look and see what I have soft-copies of. Whilst I'm at it, does anyone have information on the XDELTA debugger? (The thing that produces prompts like "0012FF08! BPT" when you've really stuffed things up). Just being able to reliably get back to SRM from it would be nice... Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Tue Jun 19 18:11:39 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from cs.Technion.AC.IL (csa.cs.technion.ac.il [132.68.32.1]) by hub.freebsd.org (Postfix) with ESMTP id 198FB37B408; Tue, 19 Jun 2001 18:11:36 -0700 (PDT) (envelope-from nadav@cs.technion.ac.il) Received: from csd.cs.technion.ac.il (csd.cs.technion.ac.il [132.68.32.8]) by cs.Technion.AC.IL (8.9.3+Sun/8.9.0) with ESMTP id EAA09751; Wed, 20 Jun 2001 04:12:59 +0300 (IDT) Received: from localhost (nadav@localhost) by csd.cs.technion.ac.il (8.9.3+Sun/8.9.0) with SMTP id EAA28522; Wed, 20 Jun 2001 04:12:57 +0300 (IDT) X-Authentication-Warning: csd.cs.technion.ac.il: nadav owned process doing -bs Date: Wed, 20 Jun 2001 04:12:57 +0300 (IDT) From: Nadav Eiron X-Sender: nadav@csd To: Peter Jeremy Cc: John Baldwin , Paul Halliday , alpha@freebsd.org Subject: Re: SRM Help In-Reply-To: <20010620105454.U95583@gsmx07.alcatel.com.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org > > (If anyone has real, nice detailed information on SRM commands in > >general that would also be nice.) > > I'll have a look and see whatI have soft-copies of. Whilst I'm at > it, does anyone have information on the XDELTA debugger? (The thing > that produces prompts like "0012FF08! BPT" when you've really stuffed > things up). Just being able to reliably get back to SRM from it would > benice... > > Peter XDELTA is the OpenVMS priviliged code debugger. I don't know if it's the same as the thing you refer to, but the docs are where all the OpenVMS docs are: http://www.openvms.compaq.com:8000/index.html Hope this helps, Nadav To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Tue Jun 19 18:42: 0 2001 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 0949537B407; Tue, 19 Jun 2001 18:41:58 -0700 (PDT) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.3/8.9.3) with ESMTP id VAA29725; Tue, 19 Jun 2001 21:41:56 -0400 (EDT) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.11.3/8.9.1) id f5K1fQL37319; Tue, 19 Jun 2001 21:41:26 -0400 (EDT) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <15151.65350.791410.529186@grasshopper.cs.duke.edu> Date: Tue, 19 Jun 2001 21:41:26 -0400 (EDT) To: John Baldwin Cc: alpha@FreeBSD.ORG Subject: Re: SRM Help In-Reply-To: References: X-Mailer: VM 6.75 under 21.1 (patch 12) "Channel Islands" XEmacs Lucid Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org John Baldwin writes: > Does anyone know how to examine the registers of other CPU's from SRM? > > I've discovered that one can arbitrarily halt processors from SRM using 'stop'. > I'd like to examine the RA of teh other CPU if possible however to see where it > was. I think I'm about ready to figure out how to walk back the stack via just > examining memory in SRM so I can get tracebacks, too. (Sure would be nice if For SRM questions, I generally point people at: http://www.support.compaq.com/alpha-tools/documentation/archive/sdk/ec-qk8df-te_srm_cons_mb_users_gde.pdf But it's probably not MP aware... Drew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Tue Jun 19 19:56:28 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from smtp01.primenet.com (smtp01.primenet.com [64.211.219.50]) by hub.freebsd.org (Postfix) with ESMTP id 92B8237B409 for ; Tue, 19 Jun 2001 19:56:21 -0700 (PDT) (envelope-from tlambert@usr05.primenet.com) Received: (from daemon@localhost) by smtp01.primenet.com (8.9.3/8.9.3) id TAA20923; Tue, 19 Jun 2001 19:56:10 -0700 (MST) Received: from usr05.primenet.com(206.165.6.205) via SMTP by smtp01.primenet.com, id smtpdAAAFhaigz; Tue Jun 19 19:21:57 2001 Received: (from tlambert@localhost) by usr05.primenet.com (8.8.5/8.8.5) id TAA24251; Tue, 19 Jun 2001 19:24:02 -0700 (MST) From: Terry Lambert Message-Id: <200106200224.TAA24251@usr05.primenet.com> Subject: Re: vx, lge, nge, dc, rl, sf, sis, sk, vr, wb users please TEST To: bmilekic@technokratis.com (Bosko Milekic) Date: Wed, 20 Jun 2001 02:24:02 +0000 (GMT) Cc: freebsd-alpha@FreeBSD.ORG In-Reply-To: <20010619191602.A28591@technokratis.com> from "Bosko Milekic" at Jun 19, 2001 07:16:02 PM X-Mailer: ELM [version 2.5 PL2] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org > Hi Guys, > > I know I've been bothering you a lot lately, but there's one more > thing that I need some (or one) of you to test out, if you're using one > (or more) of the following: > > - if_vx > - if_lge > - if_nge > - if_dc > - if_rl > - if_sf > - if_sis > - if_sk > - if_vr > - if_wb > > and -CURRENT > to test out: > > http://people.freebsd.org/~bmilekic/code/mdevget.patch > > as soon as possible. Please run this past Bill Paul. The reason for the pre-adjustment of the m_devget is to ensure that the structure in the IP header is aligned, given the fact that there is a 14 byte ethernet header in front of it. An alignment of 16 should work on the Alpha and IA64, without needing modification. The m_devget basically copies the data to force it to be aligned (ugly, but necessary on brain damaged hardware). Are these changes really necessary for the Alpha to work? Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Tue Jun 19 20:25:59 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from technokratis.com (modemcable052.174-202-24.mtl.mc.videotron.ca [24.202.174.52]) by hub.freebsd.org (Postfix) with ESMTP id 489D437B406 for ; Tue, 19 Jun 2001 20:25:33 -0700 (PDT) (envelope-from bmilekic@technokratis.com) Received: (from bmilekic@localhost) by technokratis.com (8.11.3/8.11.3) id f5K3QO129943; Tue, 19 Jun 2001 23:26:24 -0400 (EDT) (envelope-from bmilekic) Date: Tue, 19 Jun 2001 23:26:24 -0400 From: Bosko Milekic To: Terry Lambert Cc: freebsd-alpha@FreeBSD.ORG Subject: Re: vx, lge, nge, dc, rl, sf, sis, sk, vr, wb users please TEST Message-ID: <20010619232624.A29829@technokratis.com> References: <20010619191602.A28591@technokratis.com> <200106200224.TAA24251@usr05.primenet.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200106200224.TAA24251@usr05.primenet.com>; from tlambert@primenet.com on Wed, Jun 20, 2001 at 02:24:02AM +0000 Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Wed, Jun 20, 2001 at 02:24:02AM +0000, Terry Lambert wrote: > > http://people.freebsd.org/~bmilekic/code/mdevget.patch > > Please run this past Bill Paul. I already did this. :-) > The reason for the pre-adjustment of the m_devget is to ensure > that the structure in the IP header is aligned, given the fact > that there is a 14 byte ethernet header in front of it. I know. The problem is that the way the alignment issue is presently handeled is wrong. See, to trick m_devget() into writing the start of the data offset two bytes into the target mbuf chain's first mbuf's data region (to make the alignment OK), what was done was to pass for the `source buffer address' argument to m_devget(), the actual address of the source buffer MINUS ETHER_ALIGN (2 bytes). This had the effect of copying the end of the previous cluster or the end of the mbuf header (depending on where the source buffer is stored) to the first two bytes of the target mbuf. Admittedly, this is a cute trick, but it's wrong. What can happen (and will likely happen w/ mb_alloc b/c mb_alloc keeps separate maps for clusters and mbufs, to make address space limitations easier to maintain) is that the "previous cluster" sits on another page which just so happens to not be allocated yet, which will generate a page fault during the bcopy() in m_devget(). > An alignment of 16 should work on the Alpha and IA64, without > needing modification. As Jonathan Lemon kindly explained to me, the 2 byte alignment at the start of the data region makes things ok as the ethernet header is 14 bytes so the data following it will be properly aligned. This makes the Alpha happy and the x86 faster. > The m_devget basically copies the data to force it to be aligned > (ugly, but necessary on brain damaged hardware). Again, I know. What the change does, if you just glance over at it, is change the `offset from source buffer' argument of m_devget() which came with the initial import of m_devget() [and which is coincidentally not used ANYWHERE in our code, and is thus useless] to now mean `offset into the data region of the first mbuf of the target mbuf chain before copying the source buffer data.' I hope this clarifies things. > Are these changes really necessary for the Alpha to work? Absolutely. To test whether or not they are correct, it would be nice if the people with the hardware gave it a whirl. By the way, the patch is for -CURRENT but once it is committed, I'll mark it "MFC in 2 weeks," as this applies to -STABLE as well (even though -STABLE is not seeing mb_alloc, the trickery used to fool m_devget() is still technically wrong). > Terry Lambert > terry@lambert.org > --- > Any opinions in this posting are my own and not those of my present > or previous employers. K? Cheerio, -- Bosko Milekic bmilekic@technokratis.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Wed Jun 20 0: 3:40 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from hawk.mail.pas.earthlink.net (hawk.mail.pas.earthlink.net [207.217.120.22]) by hub.freebsd.org (Postfix) with ESMTP id 11B6637B403 for ; Wed, 20 Jun 2001 00:03:37 -0700 (PDT) (envelope-from tlambert2@mindspring.com) Received: from mindspring.com (dialup-209.247.138.115.Dial1.SanJose1.Level3.net [209.247.138.115]) by hawk.mail.pas.earthlink.net (EL-8_9_3_3/8.9.3) with ESMTP id AAA12064; Wed, 20 Jun 2001 00:03:27 -0700 (PDT) Message-ID: <3B304ADF.C5131399@mindspring.com> Date: Wed, 20 Jun 2001 00:03:59 -0700 From: Terry Lambert Reply-To: tlambert2@mindspring.com X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony} (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Bosko Milekic Cc: Terry Lambert , freebsd-alpha@FreeBSD.ORG Subject: Re: vx, lge, nge, dc, rl, sf, sis, sk, vr, wb users please TEST References: <20010619191602.A28591@technokratis.com> <200106200224.TAA24251@usr05.primenet.com> <20010619232624.A29829@technokratis.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Bosko Milekic wrote: > > On Wed, Jun 20, 2001 at 02:24:02AM +0000, Terry Lambert wrote: > > > http://people.freebsd.org/~bmilekic/code/mdevget.patch > > > > Please run this past Bill Paul. > > I already did this. :-) If he approves, I approve. Like that really matters, if he approves... Bill is the Driver God. 8-) > I know. The problem is that the way the alignment > issue is presently handeled is wrong. See, to trick m_devget() > into writing the start of the data offset two bytes into the > target mbuf chain's first mbuf's data region (to make the > alignment OK), what was done was to pass for the `source buffer > address' argument to m_devget(), the actual address of the > source buffer MINUS ETHER_ALIGN (2 bytes). This had the effect > of copying the end of the previous cluster or the end of the > mbuf header (depending on where the source buffer is stored) > to the first two bytes of the target mbuf. Admittedly, this is > a cute trick, but it's wrong. What can happen (and will likely > happen w/ mb_alloc b/c mb_alloc keeps separate maps for clusters > and mbufs, to make address space limitations easier to maintain) > is that the "previous cluster" sits on another page which just > so happens to not be allocated yet, which will generate a page > fault during the bcopy() in m_devget(). Ah. I never see this, the way I allocate and back mbufs. The change makes much more sense now. I wondered why you cared about the potential for "leaking" two bytes of information, when the "leak" only occurred to other things already in kernel space, which could just look at anything they wanted to, anyway. > > Are these changes really necessary for the Alpha to work? > > Absolutely. I wouldn't exactly say "absolutely", unless you are actually measuring significant faulting as a result; I would say that they are harmless. I was just a bit nervous, since I had a long conversation with Bill on this and other nasty topics (e.g. I want to add a new function to the list of externally accessible functions exported by all ethernet drivers; more on that later, after the code is happy). -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Wed Jun 20 2: 8:45 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from postino.fi.infn.it (postino.fi.infn.it [192.84.145.9]) by hub.freebsd.org (Postfix) with ESMTP id 476E337B401 for ; Wed, 20 Jun 2001 02:08:42 -0700 (PDT) (envelope-from Riccardo.Veraldi@fi.infn.it) Received: from nikita.fi.infn.it (nikita.fi.infn.it [192.84.146.189]) by postino.fi.infn.it (8.11.1/8.11.1) with ESMTP id f5K98Zm52506 for ; Wed, 20 Jun 2001 11:08:35 +0200 (CEST) From: Riccardo.Veraldi@fi.infn.it Received: by nikita.fi.infn.it (Postfix, from userid 1001) id 192FA18CE9; Wed, 20 Jun 2001 11:08:34 +0200 (CEST) Received: from localhost (localhost [127.0.0.1]) by nikita.fi.infn.it (Postfix) with ESMTP id DA4D115902 for ; Wed, 20 Jun 2001 11:08:34 +0200 (CEST) Date: Wed, 20 Jun 2001 11:08:34 +0200 (CEST) X-X-Sender: To: Subject: problem I Cannot solve Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Dear friends, I cannot solve this problem. I am unable to build xemacs21 un alpha the port seems not working ??? here are the errors which follows. The strange thing is that copying and pasting the conftest program and compiling it it works, so I do not know why configure stopts with a core: configure:4098: cc -o conftest -O -pipe -mcpu=ev56 -I/usr/local/include -L/usr/local/lib -Xlinker -R/usr/local/lib:/usr/libexec conftest.c -lutil -lxpg4 -lgcc -lc -lgcc /usr/lib/crtend.o 1>&5 Segmentation fault - core dumped configure: failed program was: #line 4087 "configure" #include "confdefs.h" #include main() { FILE *f=fopen("conftestval", "w"); if (!f) exit(1); fprintf(f, "%d\n", sizeof(short)); exit(0); } thanks Rick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Wed Jun 20 5:56:31 2001 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 4677037B406; Wed, 20 Jun 2001 05:56:28 -0700 (PDT) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.3/8.9.3) with ESMTP id IAA07996; Wed, 20 Jun 2001 08:56:27 -0400 (EDT) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.11.3/8.9.1) id f5KCtv038541; Wed, 20 Jun 2001 08:55:57 -0400 (EDT) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <15152.40285.692168.905556@grasshopper.cs.duke.edu> Date: Wed, 20 Jun 2001 08:55:57 -0400 (EDT) To: Riccardo.Veraldi@fi.infn.it Cc: , obrien@FreeBSD.ORG Subject: Re: problem I Cannot solve In-Reply-To: References: X-Mailer: VM 6.75 under 21.1 (patch 12) "Channel Islands" XEmacs Lucid Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Did you even _read_ the email I sent you about this when you first asked about it?? I've appended that email. I'm still waiting to hear back from David O'Brien as to what changed in the toolchain & when it changed. I have no idea what the right "ports" way to really fix this is. The problem here is that xemacs21's patch-aj is setting up a special case for alpha which omits /usr/lib/crti.o and /usr/lib/crtn.o. I don't pay much attention to such things. I assume these files did not exist on the alpha at some point in the past, but the toolchain changed sometime prior to 4.3-RELEASE so these files now exist on the alpha. When did that change occur? Is it far enough in the past so that it is safe to simply cvs rm that patch? Drew >>Date: Wed, 30 May 2001 13:05:24 -0400 (EDT) >>To: Riccardo.Veraldi@fi.infn.it >>Cc: >>Subject: Re: GCC problem ?? >>In-Reply-To: >>References: >>X-Mailer: VM 6.75 under 21.1 (patch 12) "Channel Islands" XEmacs Lucid >> >>More like a gnu-configure-being-to-smart-for-its-own-damned-good problem. >>The following appears to work: >> >>rm files/patch-aj >> >>Drew >> To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Wed Jun 20 7:13:14 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from dragon.nuxi.com (trang.nuxi.com [206.40.252.115]) by hub.freebsd.org (Postfix) with ESMTP id D325E37B401 for ; Wed, 20 Jun 2001 07:13:11 -0700 (PDT) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.11.3/8.11.1) id f5KECgR90105; Wed, 20 Jun 2001 07:12:42 -0700 (PDT) (envelope-from obrien) Date: Wed, 20 Jun 2001 07:12:42 -0700 From: "David O'Brien" To: Riccardo.Veraldi@fi.infn.it, freebsd-alpha@FreeBSD.ORG Subject: Re: problem I Cannot solve Message-ID: <20010620071242.B90008@dragon.nuxi.com> Reply-To: obrien@FreeBSD.ORG References: <15152.40285.692168.905556@grasshopper.cs.duke.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <15152.40285.692168.905556@grasshopper.cs.duke.edu>; from gallatin@cs.duke.edu on Wed, Jun 20, 2001 at 08:55:57AM -0400 X-Operating-System: FreeBSD 5.0-CURRENT Organization: The NUXI BSD group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Wed, Jun 20, 2001 at 08:55:57AM -0400, Andrew Gallatin wrote: > I'm still waiting to hear back from David O'Brien as to what changed > in the toolchain & when it changed. Don't remember when, but we switched to using GCC's csu code. When we did that, the Alpha started using the "standard ELF" crt files. > The problem here is that xemacs21's > patch-aj is setting up a special case for alpha which omits > /usr/lib/crti.o and /usr/lib/crtn.o. I don't use *emacs :-) , and don't have time to play with it. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Wed Jun 20 7:39:56 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from dragon.nuxi.com (trang.nuxi.com [206.40.252.115]) by hub.freebsd.org (Postfix) with ESMTP id 74A1537B401 for ; Wed, 20 Jun 2001 07:39:48 -0700 (PDT) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.11.3/8.11.1) id f5KEasT90415; Wed, 20 Jun 2001 07:36:54 -0700 (PDT) (envelope-from obrien) Date: Wed, 20 Jun 2001 07:36:54 -0700 From: "David O'Brien" To: Paul Halliday Cc: freebsd-alpha@FreeBSD.ORG, Andrew Gallatin , "Crespo, Ramon" Subject: Re: X11 Settings for the MiataGL Message-ID: <20010620073654.C90008@dragon.nuxi.com> Reply-To: obrien@FreeBSD.ORG References: <15150.17051.201667.856092@grasshopper.cs.duke.edu> <3B2E4BBE.6FEC26EF@penix.org> <20010618180804.E540@dragon.nuxi.com> <3B2EB34C.253019C8@penix.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <3B2EB34C.253019C8@penix.org>; from dp@penix.org on Mon, Jun 18, 2001 at 10:05:00PM -0400 X-Operating-System: FreeBSD 5.0-CURRENT Organization: The NUXI BSD group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Mon, Jun 18, 2001 at 10:05:00PM -0400, Paul Halliday wrote: > > > as200 xf86config-> > > > > > > Now give the full device name that the device is connected to, for > > > example /dev/tty00. Just pressing enter will use the default, > > > /dev/mouse. > > > > > > Mouse device: /dev/sysmouse > > > > Uh.. you have given the mouse device, but not protocol to use. X has to > > know both. Speaking M$ Intelmouse to /dev/sysmouse is not a productive > > thing. > > I was merely stating that their is no need to edit XF86Config by hand. > Unless you fuck something up when > you first run it. Well not clearly. Your instructions should also point out which protocol to manually pick. Otherwise someone might choose PS/2 protocol (since that is what their mouse is) and /dev/sysmouse. This will not work well. Since someone might use your email as recipe to get their X setup, it would be best to tell the complete story. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Wed Jun 20 7:40: 4 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from dragon.nuxi.com (trang.nuxi.com [206.40.252.115]) by hub.freebsd.org (Postfix) with ESMTP id 3CEA237B409; Wed, 20 Jun 2001 07:39:59 -0700 (PDT) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.11.3/8.11.1) id f5KEdwo90450; Wed, 20 Jun 2001 07:39:58 -0700 (PDT) (envelope-from obrien) Date: Wed, 20 Jun 2001 07:39:58 -0700 From: "David O'Brien" To: John Baldwin Cc: "David O'Brien" , "Crespo, Ramon" , Andrew Gallatin , Paul Halliday Subject: Re: X11 Settings for the MiataGL Message-ID: <20010620073958.D90008@dragon.nuxi.com> Reply-To: freebsd-alpha@FreeBSD.org References: <20010618180804.E540@dragon.nuxi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from jhb@FreeBSD.org on Tue, Jun 19, 2001 at 11:44:43AM -0700 X-Operating-System: FreeBSD 5.0-CURRENT Organization: The NUXI BSD group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Tue, Jun 19, 2001 at 11:44:43AM -0700, John Baldwin wrote: > > Uh.. you have given the mouse device, but not protocol to use. X has to > > know both. Speaking M$ Intelmouse to /dev/sysmouse is not a productive > > thing. > > X 4 can autodetect the sysmouse protocol. You don't have to set it > explicitly to "sysmouse". This thread was explicitly about XFree86 3.3.6. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Wed Jun 20 9:29:27 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from technokratis.com (modemcable052.174-202-24.mtl.mc.videotron.ca [24.202.174.52]) by hub.freebsd.org (Postfix) with ESMTP id 6302937B409 for ; Wed, 20 Jun 2001 09:29:24 -0700 (PDT) (envelope-from bmilekic@technokratis.com) Received: (from bmilekic@localhost) by technokratis.com (8.11.3/8.11.3) id f5KGUTg34577; Wed, 20 Jun 2001 12:30:29 -0400 (EDT) (envelope-from bmilekic) Date: Wed, 20 Jun 2001 12:30:29 -0400 From: Bosko Milekic To: Terry Lambert Cc: Terry Lambert , freebsd-alpha@FreeBSD.ORG Subject: Re: vx, lge, nge, dc, rl, sf, sis, sk, vr, wb users please TEST Message-ID: <20010620123029.A34452@technokratis.com> References: <20010619191602.A28591@technokratis.com> <200106200224.TAA24251@usr05.primenet.com> <20010619232624.A29829@technokratis.com> <3B304ADF.C5131399@mindspring.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <3B304ADF.C5131399@mindspring.com>; from tlambert2@mindspring.com on Wed, Jun 20, 2001 at 12:03:59AM -0700 Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Wed, Jun 20, 2001 at 12:03:59AM -0700, Terry Lambert wrote: [...] > > > Are these changes really necessary for the Alpha to work? > > > > Absolutely. > > I wouldn't exactly say "absolutely", unless you are actually > measuring significant faulting as a result; I would say that > they are harmless. Oh, I think I wasn't too clear above. When I said "page fault" I meant "fatal page fault" (i.e. the address space isn't even mapped, it may even sit in another submap of kmem_map). It's not a problem right now because the mbuf allocator allocates "sequentially" from the base of mb_map. So let's say we have a cluster in a page X, where X > mb_map_base. Then, we're guaranteed that all Y, where X > Y > mb_map_base consists of already wired-down pages, so we're safe. Actually, now that I think about it, if we just so happen to hit the mbuf on the first page in mb_map and the space before that is not mapped, then we may see this too - but it's very unlikely. As I mentionned previously, instead of just having `mb_map' where clusters and mbufs are allocated from, in the new allocator I have a `mbuf_map' and a `clust_map.' So, when the data being bcopy()'d comes from the first cluster of clust_map, and the previous space is unmapped, the fault is a sure thing and we'll end up crashing. > I was just a bit nervous, since I had a long conversation > with Bill on this and other nasty topics (e.g. I want to Yeah, hehe. As you mentionned above, Bill *is* the "network driver God." :-) > add a new function to the list of externally accessible > functions exported by all ethernet drivers; more on that > later, after the code is happy). Cool. > -- Terry Later, -- Bosko Milekic bmilekic@technokratis.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Wed Jun 20 10:11:14 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from swan.mail.pas.earthlink.net (swan.mail.pas.earthlink.net [207.217.120.123]) by hub.freebsd.org (Postfix) with ESMTP id 010FA37B401 for ; Wed, 20 Jun 2001 10:11:10 -0700 (PDT) (envelope-from tlambert2@mindspring.com) Received: from mindspring.com (dialup-209.244.104.7.Dial1.SanJose1.Level3.net [209.244.104.7]) by swan.mail.pas.earthlink.net (EL-8_9_3_3/8.9.3) with ESMTP id KAA27671; Wed, 20 Jun 2001 10:10:58 -0700 (PDT) Message-ID: <3B30D941.6AE93443@mindspring.com> Date: Wed, 20 Jun 2001 10:11:29 -0700 From: Terry Lambert Reply-To: tlambert2@mindspring.com X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony} (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Bosko Milekic Cc: Terry Lambert , freebsd-alpha@FreeBSD.ORG Subject: Re: vx, lge, nge, dc, rl, sf, sis, sk, vr, wb users please TEST References: <20010619191602.A28591@technokratis.com> <200106200224.TAA24251@usr05.primenet.com> <20010619232624.A29829@technokratis.com> <3B304ADF.C5131399@mindspring.com> <20010620123029.A34452@technokratis.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Bosko Milekic wrote: > > I wouldn't exactly say "absolutely", unless you are actually > > measuring significant faulting as a result; I would say that > > they are harmless. > > Oh, I think I wasn't too clear above. When I said > "page fault" I meant "fatal page fault" (i.e. the address > space isn't even mapped, it may even sit in another submap > of kmem_map). It's not a problem right now because the mbuf > allocator allocates "sequentially" from the base of mb_map. VALLOC() is a lot of protection, given the base of mb_map. /sys/i386/i386/machdep.c protects you pretty well, no problem. > So let's say we have a cluster in a page X, where X > > mb_map_base. Then, we're guaranteed that all Y, where > X > Y > mb_map_base consists of already wired-down pages, > so we're safe. Actually, now that I think about it, if > we just so happen to hit the mbuf on the first page in > mb_map and the space before that is not > mapped, then we may see this too - but it's very unlikely. > As I mentionned previously, instead of just having `mb_map' > where clusters and mbufs are allocated from, in the new > allocator I have a `mbuf_map' and a `clust_map.' So, when > the data being bcopy()'d comes from the first cluster of > clust_map, and the previous space is unmapped, the > fault is a sure thing and we'll end up crashing. I can see where that would be a problem with the new allocator. May I offer a suggestion? The purpose of having the clusters be a fixed size, given a much larger number of mbufs has never really been clear to me, given that mbufs are allocated to act as cluster headers, to make things a tiny bit (but not substantially) easier, when it comes to freing chains, etc.. It seems to me that what you really want to do is allocate _different sizes_ of mbufs, and have the deallocator sort them out on free. This could result in a substantial space savings, as the majority of the mbuf used for the cluster header is not used for anything useful. Do you have any interest in generalizing your allocator? Eventually, you will probably want to do allocations of things other than mbufs. Also, the buckets should probably be permitted to be some multiple of the page size, in order to permit the allocation of odd-sized structures, and allow them to span page boundaries, if you went ahead with a more general approach. I guess the next thing to think about after that would be allocation at interrupt time. I think this can be done using the ziniti() approach; but you would then reserve the KVA space for use by the allocator at page fault time, instead. I have some other methods of getting around faulting, when you have sufficient backing store. Now that there are systems that have the capability of having as much RAM as the KVA space (e.g. the KVA space is really no longer sparse), there are a number of optimizations that become pretty obvious. That's not true for the Alpha, yet, but the Intel KVA space is definitely matured to the point where physical RAM equals the possible KVA + user space addressable memory. NB: The windowed access to more than 4G (e.g. the AMD 16G processor that uses "megasegments" to access the extra memory) has nevery struck me as being useful, unless you can partition you working set data enough to deal with the window flipping overhead issue that would result, so I'm not too concerned about trying to support them -- they seem more useful for VMWare type applications, where you context switch at a very low level in order to run multiple instances of a kernel, or similar pig tricks. The IA64 and AMD "Sledgehammer" will make us think about these things again, as soon as someone comes up with a MB/Memory sticks that beat the 4G limit without melting down. -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Wed Jun 20 10:42:22 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from rylos.atmos.colostate.edu (rylos.atmos.colostate.edu [129.82.48.47]) by hub.freebsd.org (Postfix) with ESMTP id 8065737B401 for ; Wed, 20 Jun 2001 10:42:20 -0700 (PDT) (envelope-from tarcieri@rylos.atmos.colostate.edu) Received: from localhost (tarcieri@localhost) by rylos.atmos.colostate.edu (8.11.3/8.11.3) with ESMTP id f5KHjx277939 for ; Wed, 20 Jun 2001 11:46:00 -0600 (MDT) (envelope-from tarcieri@rylos.atmos.colostate.edu) Date: Wed, 20 Jun 2001 11:45:59 -0600 (MDT) From: Tony Arcieri To: Subject: IRQ problems with PCI NIC in Multia Message-ID: <20010620114122.U77931-100000@rylos.atmos.colostate.edu> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org I'm attempting to use a dual port ThunderLAN NIC in a Multia with FreeBSD 4.3. For whatever reason, it doesn't seem to get assigned any resources whatsoever: tl0: irq 0 at device 0.0 on pci1 tl0: couldn't map ports/memory device_probe_and_attach: tl0 attach returned 6 tl0: irq 0 at device 1.0 on pci1 tl0: couldn't map ports/memory device_probe_and_attach: tl0 attach returned 6 Any ideas? Tony Arcieri To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Wed Jun 20 10:58:42 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from technokratis.com (modemcable052.174-202-24.mtl.mc.videotron.ca [24.202.174.52]) by hub.freebsd.org (Postfix) with ESMTP id 82F3037B407 for ; Wed, 20 Jun 2001 10:58:33 -0700 (PDT) (envelope-from bmilekic@technokratis.com) Received: (from bmilekic@localhost) by technokratis.com (8.11.3/8.11.3) id f5KHxdS35058; Wed, 20 Jun 2001 13:59:39 -0400 (EDT) (envelope-from bmilekic) Date: Wed, 20 Jun 2001 13:59:39 -0400 From: Bosko Milekic To: Terry Lambert Cc: Terry Lambert , freebsd-alpha@FreeBSD.ORG Subject: Re: vx, lge, nge, dc, rl, sf, sis, sk, vr, wb users please TEST Message-ID: <20010620135939.A34888@technokratis.com> References: <20010619191602.A28591@technokratis.com> <200106200224.TAA24251@usr05.primenet.com> <20010619232624.A29829@technokratis.com> <3B304ADF.C5131399@mindspring.com> <20010620123029.A34452@technokratis.com> <3B30D941.6AE93443@mindspring.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <3B30D941.6AE93443@mindspring.com>; from tlambert2@mindspring.com on Wed, Jun 20, 2001 at 10:11:29AM -0700 Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Before I go into this [the topic seems to have diverged a little], has anybody gotten around to testing (or has the hardware to do the testing required?) - if some of you guys are stuck with the fact that you have the hardware but don't run -CURRENT, please let me know - I could generate an equivalent patch for -STABLE, with a little work. On Wed, Jun 20, 2001 at 10:11:29AM -0700, Terry Lambert wrote: > I can see where that would be a problem with the new > allocator. > > May I offer a suggestion? The purpose of having the > clusters be a fixed size, given a much larger number > of mbufs has never really been clear to me, given that > mbufs are allocated to act as cluster headers, to make > things a tiny bit (but not substantially) easier, when > it comes to freing chains, etc.. The reason is that clusters are not used everywhere, but mbufs are (even when the storage type is not a cluster). > It seems to me that what you really want to do is > allocate _different sizes_ of mbufs, and have the > deallocator sort them out on free. Believe me, I've thought about this. Alfred Perlstein has been pushing me to do something like this for a while now. There are several problems with the suggestion, but it's something to consider in the future. I'd rather allow mb_alloc to stabilize a little more after committing it, work at lockifying net*/, unwind Giant, and then continue to deal with issues such as this. > This could result in a substantial space savings, as > the majority of the mbuf used for the cluster header > is not used for anything useful. Yeah. > Do you have any interest in generalizing your allocator? Well, not really. See, the allocator is a specialization of a general allocator. One of the main design goals of the allocator is performance. I tried very hard to give the new allocator the advantages required for scalability and the "infrastructure" required to reclaim memory while keeping approximately the same allocation/deallocation standards of the present allocator. One important performance advantage of the present allocator relative to say the NetBSD or OpenBSD mbuf allocations/deallocations is that we *never* have to free pages back to the map from m_free() (an expensive procedure). This is precisely why I'd like to have freeing eventually implemented from a kproc, when it can be handled only when really needed without affecting network performance. General purpose allocations should probably be handled differently. > Eventually, you will probably want to do allocations of > things other than mbufs. There *is* a general version of an allocator such as mb_alloc. In fact, as is mentionned in the introductory comments in subr_mbuf.c, mb_alloc is in part based on Alfred's "memcache" allocator. Although a little outdated, the source is: http://people.freebsd.org/~alfred/memcache/ All it needs is a little bit of cleaning up/fixing up and it's ready to fly for general purpose allocations. Keep in mind, though, that these types of allocators have a wastage factor that becomes significant as the size of the objects being allocated approaches (falls to) the size of a pointer. The reason is that the free list is implemented with an allocated pointer array [it's done this way for very specific reasons which i'll keep out of this Email] and if you're allocating a page worth of ptr-size objects, youre spending a whole other page for the pointers for a one page worth freelist for these objects. The whole reason I wrote mb_alloc separately from memcache altogether is to allow for the different type of freeing to occur, and to allow for future very mbuf-specific alloc. optimizations to occur, and to allow us to inline the code in the mbuf allocation functions, and ... (some other less worthy reasons) [glancing over subr_mbuf.c a few times should make these things obvious]. > Also, the buckets should probably be permitted to be > some multiple of the page size, in order to permit the > allocation of odd-sized structures, and allow them to > span page boundaries, if you went ahead with a more > general approach. This is done in memcache, actually. > I guess the next thing to think about after that would > be allocation at interrupt time. I think this can be > done using the ziniti() approach; but you would then > reserve the KVA space for use by the allocator at page > fault time, instead. This is for the general allocator, right? Yeah, memcache can be made to optionally reserve KVA space for interrupt-time allocations; mind you, it would only serve as an optimization. As I previously mentionned for mb_alloc, the KVA space needed is already reserved. > I have some other methods of getting around faulting, > when you have sufficient backing store. Now that there > are systems that have the capability of having as much > RAM as the KVA space (e.g. the KVA space is really no > longer sparse), there are a number of optimizations > that become pretty obvious. Cool. Do share. Had my trip to Usenix this year not been cancelled due to the fact that I'm going to see family in Yugoslavia this Saturday, I would have gathered you and Alfred together, and listened over a few beers. > That's not true for the Alpha, yet, but the Intel KVA > space is definitely matured to the point where physical > RAM equals the possible KVA + user space addressable > memory. > > NB: The windowed access to more than 4G (e.g. the AMD > 16G processor that uses "megasegments" to access the > extra memory) has nevery struck me as being useful, > unless you can partition you working set data enough > to deal with the window flipping overhead issue that > would result, so I'm not too concerned about trying > to support them -- they seem more useful for VMWare > type applications, where you context switch at a very > low level in order to run multiple instances of a > kernel, or similar pig tricks. The IA64 and AMD > "Sledgehammer" will make us think about these things > again, as soon as someone comes up with a MB/Memory > sticks that beat the 4G limit without melting down. > > -- Terry Regards, -- Bosko Milekic bmilekic@technokratis.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Wed Jun 20 11:10:40 2001 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 D87F237B403 for ; Wed, 20 Jun 2001 11:10:37 -0700 (PDT) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.3/8.9.3) with ESMTP id OAA14656; Wed, 20 Jun 2001 14:10:33 -0400 (EDT) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.11.3/8.9.1) id f5KIA3Z40780; Wed, 20 Jun 2001 14:10:03 -0400 (EDT) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <15152.59131.711800.873825@grasshopper.cs.duke.edu> Date: Wed, 20 Jun 2001 14:10:03 -0400 (EDT) To: Bosko Milekic Cc: Terry Lambert , freebsd-alpha@FreeBSD.ORG Subject: Re: vx, lge, nge, dc, rl, sf, sis, sk, vr, wb users please TEST In-Reply-To: <20010620135939.A34888@technokratis.com> References: <20010619191602.A28591@technokratis.com> <200106200224.TAA24251@usr05.primenet.com> <20010619232624.A29829@technokratis.com> <3B304ADF.C5131399@mindspring.com> <20010620123029.A34452@technokratis.com> <3B30D941.6AE93443@mindspring.com> <20010620135939.A34888@technokratis.com> X-Mailer: VM 6.75 under 21.1 (patch 12) "Channel Islands" XEmacs Lucid Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Bosko Milekic writes: > > Before I go into this [the topic seems to have diverged a little], has > anybody gotten around to testing (or has the hardware to do the testing > required?) - if some of you guys are stuck with the fact that you have the > hardware but don't run -CURRENT, please let me know - I could generate an > equivalent patch for -STABLE, with a little work. I assume you're just looking for an unaligned access panic on the first bit of IP traffic? Drew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Wed Jun 20 11:18:11 2001 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 82BE537B401 for ; Wed, 20 Jun 2001 11:18:08 -0700 (PDT) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.3/8.9.3) with ESMTP id OAA14814; Wed, 20 Jun 2001 14:18:07 -0400 (EDT) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.11.3/8.9.1) id f5KIHcb40793; Wed, 20 Jun 2001 14:17:38 -0400 (EDT) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <15152.59586.75593.625132@grasshopper.cs.duke.edu> Date: Wed, 20 Jun 2001 14:17:38 -0400 (EDT) To: Tony Arcieri Cc: Subject: Re: IRQ problems with PCI NIC in Multia In-Reply-To: <20010620114122.U77931-100000@rylos.atmos.colostate.edu> References: <20010620114122.U77931-100000@rylos.atmos.colostate.edu> X-Mailer: VM 6.75 under 21.1 (patch 12) "Channel Islands" XEmacs Lucid Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Tony Arcieri writes: > I'm attempting to use a dual port ThunderLAN NIC in a Multia with FreeBSD > 4.3. For whatever reason, it doesn't seem to get assigned any resources > whatsoever: > > tl0: irq 0 at device 0.0 on pci1 > tl0: couldn't map ports/memory > device_probe_and_attach: tl0 attach returned 6 > tl0: irq 0 at device 1.0 on pci1 > tl0: couldn't map ports/memory > device_probe_and_attach: tl0 attach returned 6 > > Any ideas? I suspect that the SRM console firmware (the alpha's equivalent of a BIOS) never setup the card. It may be that it doesn't look behind ppb's on the Multia. Anyway, I'm not sure if this failure to setup the card is a platform (Multia) thing, or if other versions of the SRM on different types of alphas would ignore the card. FWIW, you really don't want to be running a dual-port nic on a multia. If you're after bandwidth, the multia doesn't have sufficient memory bandwidth to drive a single 100Mb nic, much less two. If you're after failover, then, well, the Multia is the weakest link here.. Sorry.. Drew ------------------------------------------------------------------------------ Andrew Gallatin, Sr Systems Programmer http://www.cs.duke.edu/~gallatin Duke University Email: gallatin@cs.duke.edu Department of Computer Science Phone: (919) 660-6590 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Wed Jun 20 11:33:26 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from technokratis.com (modemcable052.174-202-24.mtl.mc.videotron.ca [24.202.174.52]) by hub.freebsd.org (Postfix) with ESMTP id 8E8C337B401 for ; Wed, 20 Jun 2001 11:33:23 -0700 (PDT) (envelope-from bmilekic@technokratis.com) Received: (from bmilekic@localhost) by technokratis.com (8.11.3/8.11.3) id f5KIYUb35318; Wed, 20 Jun 2001 14:34:30 -0400 (EDT) (envelope-from bmilekic) Date: Wed, 20 Jun 2001 14:34:30 -0400 From: Bosko Milekic To: Andrew Gallatin Cc: Terry Lambert , freebsd-alpha@FreeBSD.ORG Subject: Re: vx, lge, nge, dc, rl, sf, sis, sk, vr, wb users please TEST Message-ID: <20010620143430.A35299@technokratis.com> References: <20010619191602.A28591@technokratis.com> <200106200224.TAA24251@usr05.primenet.com> <20010619232624.A29829@technokratis.com> <3B304ADF.C5131399@mindspring.com> <20010620123029.A34452@technokratis.com> <3B30D941.6AE93443@mindspring.com> <20010620135939.A34888@technokratis.com> <15152.59131.711800.873825@grasshopper.cs.duke.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <15152.59131.711800.873825@grasshopper.cs.duke.edu>; from gallatin@cs.duke.edu on Wed, Jun 20, 2001 at 02:10:03PM -0400 Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Wed, Jun 20, 2001 at 02:10:03PM -0400, Andrew Gallatin wrote: > > Bosko Milekic writes: > > > > Before I go into this [the topic seems to have diverged a little], has > > anybody gotten around to testing (or has the hardware to do the testing > > required?) - if some of you guys are stuck with the fact that you have the > > hardware but don't run -CURRENT, please let me know - I could generate an > > equivalent patch for -STABLE, with a little work. > > I assume you're just looking for an unaligned access panic on the > first bit of IP traffic? Yup. Well, I'm not looking for it, but if you catch it, it'll be a sign that something's wrong. > Drew -- Bosko Milekic bmilekic@technokratis.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Wed Jun 20 12:34:52 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from smtp3.xs4all.nl (smtp3.xs4all.nl [194.109.127.132]) by hub.freebsd.org (Postfix) with ESMTP id 7E4A837B403 for ; Wed, 20 Jun 2001 12:34:49 -0700 (PDT) (envelope-from wkb@freebie.xs4all.nl) Received: from freebie.xs4all.nl (freebie.xs4all.nl [213.84.32.253]) by smtp3.xs4all.nl (8.9.3/8.9.3) with ESMTP id VAA17183; Wed, 20 Jun 2001 21:34:46 +0200 (CEST) Received: (from wkb@localhost) by freebie.xs4all.nl (8.11.3/8.11.3) id f5KJYkx56609; Wed, 20 Jun 2001 21:34:46 +0200 (CEST) (envelope-from wkb) Date: Wed, 20 Jun 2001 21:34:46 +0200 From: Wilko Bulte To: Andrew Gallatin Cc: Tony Arcieri , freebsd-alpha@FreeBSD.ORG Subject: Re: IRQ problems with PCI NIC in Multia Message-ID: <20010620213446.A56591@freebie.xs4all.nl> References: <20010620114122.U77931-100000@rylos.atmos.colostate.edu> <15152.59586.75593.625132@grasshopper.cs.duke.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <15152.59586.75593.625132@grasshopper.cs.duke.edu>; from gallatin@cs.duke.edu on Wed, Jun 20, 2001 at 02:17:38PM -0400 X-OS: FreeBSD 4.3-STABLE X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Wed, Jun 20, 2001 at 02:17:38PM -0400, Andrew Gallatin wrote: > > Tony Arcieri writes: > > I'm attempting to use a dual port ThunderLAN NIC in a Multia with FreeBSD > > 4.3. For whatever reason, it doesn't seem to get assigned any resources > > whatsoever: > > > > tl0: irq 0 at device 0.0 on pci1 > > tl0: couldn't map ports/memory > > device_probe_and_attach: tl0 attach returned 6 > > tl0: irq 0 at device 1.0 on pci1 > > tl0: couldn't map ports/memory > > device_probe_and_attach: tl0 attach returned 6 > > > > Any ideas? > > I suspect that the SRM console firmware (the alpha's equivalent of a > BIOS) never setup the card. It may be that it doesn't look behind > ppb's on the Multia. Quite possible. > Anyway, I'm not sure if this failure to setup the card is a platform > (Multia) thing, or if other versions of the SRM on different types of > alphas would ignore the card. FWIW: the Netelligent dual port works fine on a x86 box, I have one in my firewall. > FWIW, you really don't want to be running a dual-port nic on a > multia. If you're after bandwidth, the multia doesn't have sufficient > memory bandwidth to drive a single 100Mb nic, much less two. If > you're after failover, then, well, the Multia is the weakest link > here.. Hehe ;-) -- | / o / / _ Arnhem, The Netherlands email: wilko@FreeBSD.org |/|/ / / /( (_) Bulte http://www.FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Wed Jun 20 13:37: 4 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from finch-post-11.mail.demon.net (finch-post-11.mail.demon.net [194.217.242.39]) by hub.freebsd.org (Postfix) with ESMTP id 44EF637B401; Wed, 20 Jun 2001 13:37:01 -0700 (PDT) (envelope-from dfr@nlsystems.com) Received: from [62.49.251.130] (helo=herring.nlsystems.com) by finch-post-11.mail.demon.net with esmtp (Exim 2.12 #1) id 15Coii-0007oS-0B; Wed, 20 Jun 2001 20:37:00 +0000 Received: from herring (herring [10.0.0.2]) by herring.nlsystems.com (8.11.2/8.11.2) with ESMTP id f5KKZi764832; Wed, 20 Jun 2001 21:35:44 +0100 (BST) (envelope-from dfr@nlsystems.com) Date: Wed, 20 Jun 2001 21:35:44 +0100 (BST) From: Doug Rabson To: John Baldwin Cc: Subject: Re: SRM Help In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Tue, 19 Jun 2001, John Baldwin wrote: > Does anyone know how to examine the registers of other CPU's from SRM? > > I've discovered that one can arbitrarily halt processors from SRM using 'stop'. > I'd like to examine the RA of teh other CPU if possible however to see where it > was. I think I'm about ready to figure out how to walk back the stack via just > examining memory in SRM so I can get tracebacks, too. (Sure would be nice if > gdb could talk to SRM over a serial console some day.. ) If the other cpu has halted, you can examine some of its state by looking at the PCB in the per-cpu structure for that processor. -- Doug Rabson Mail: dfr@nlsystems.com Phone: +44 20 8348 6160 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Wed Jun 20 14: 2:19 2001 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 C2EE337B401 for ; Wed, 20 Jun 2001 14:02:13 -0700 (PDT) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.3/8.9.3) with ESMTP id RAA18665; Wed, 20 Jun 2001 17:02:11 -0400 (EDT) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.11.3/8.9.1) id f5KL1gq41163; Wed, 20 Jun 2001 17:01:42 -0400 (EDT) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <15153.3893.891927.381941@grasshopper.cs.duke.edu> Date: Wed, 20 Jun 2001 17:01:41 -0400 (EDT) To: Bosko Milekic Cc: Terry Lambert , freebsd-alpha@FreeBSD.ORG Subject: Re: vx, lge, nge, dc, rl, sf, sis, sk, vr, wb users please TEST In-Reply-To: <20010620143430.A35299@technokratis.com> References: <20010619191602.A28591@technokratis.com> <200106200224.TAA24251@usr05.primenet.com> <20010619232624.A29829@technokratis.com> <3B304ADF.C5131399@mindspring.com> <20010620123029.A34452@technokratis.com> <3B30D941.6AE93443@mindspring.com> <20010620135939.A34888@technokratis.com> <15152.59131.711800.873825@grasshopper.cs.duke.edu> <20010620143430.A35299@technokratis.com> X-Mailer: VM 6.75 under 21.1 (patch 12) "Channel Islands" XEmacs Lucid Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Bosko Milekic writes: > > On Wed, Jun 20, 2001 at 02:10:03PM -0400, Andrew Gallatin wrote: > > > > Bosko Milekic writes: > > > > > > Before I go into this [the topic seems to have diverged a little], has > > > anybody gotten around to testing (or has the hardware to do the testing > > > required?) - if some of you guys are stuck with the fact that you have the > > > hardware but don't run -CURRENT, please let me know - I could generate an > > > equivalent patch for -STABLE, with a little work. > > > > I assume you're just looking for an unaligned access panic on the > > first bit of IP traffic? > > Yup. Well, I'm not looking for it, but if you catch it, it'll be a > sign that something's wrong. if_dc appears to work fine with your patch. BTW, it would be great if you posted your patches as CVS diffs... messing with patch -pX is something of a pain.. Cheers, Drew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Thu Jun 21 0: 9:17 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from mail.high-tech-communications.com (mail.high-tech-communications.com [216.133.228.90]) by hub.freebsd.org (Postfix) with ESMTP id D48FC37B415 for ; Thu, 21 Jun 2001 00:09:12 -0700 (PDT) (envelope-from content-management@mail.high-tech-communications.com) Received: (from content-management@localhost) by mail.high-tech-communications.com (8.11.2/8.11.2) id f5L7HXJ02527; Thu, 21 Jun 2001 00:17:33 -0700 Date: Thu, 21 Jun 2001 00:17:33 -0700 Message-Id: <200106210717.f5L7HXJ02527@mail.high-tech-communications.com> To: freebsd-alpha@FreeBSD.org From: Victor Black Subject: New web utility Content-Type: text/html; charset=iso-8859-1 Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org

I noticed your email address on a list serve related to technology and web development.  With your permission, we
would like to send you information regarding new web tools and utilities based on your interests.  Please click the
following link and opt-in to our product updates and e-newsletter, click here: http://216.133.228.90/

Cordially,

Victor Black
High-Tech-Communications.com

If you would like to be removed from our database, please click here: http://216.133.228.90/remove.cgi

 

To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Thu Jun 21 1:49: 0 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from gull.mail.pas.earthlink.net (gull.mail.pas.earthlink.net [207.217.121.85]) by hub.freebsd.org (Postfix) with ESMTP id 3A43737B40A for ; Thu, 21 Jun 2001 01:48:52 -0700 (PDT) (envelope-from tlambert2@mindspring.com) Received: from mindspring.com (dialup-209.247.140.53.Dial1.SanJose1.Level3.net [209.247.140.53]) by gull.mail.pas.earthlink.net (EL-8_9_3_3/8.9.3) with ESMTP id BAA00580; Thu, 21 Jun 2001 01:48:29 -0700 (PDT) Message-ID: <3B31B4F9.FA2D43F1@mindspring.com> Date: Thu, 21 Jun 2001 01:48:57 -0700 From: Terry Lambert Reply-To: tlambert2@mindspring.com X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony} (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Bosko Milekic Cc: Terry Lambert , freebsd-alpha@FreeBSD.ORG Subject: Re: vx, lge, nge, dc, rl, sf, sis, sk, vr, wb users please TEST References: <20010619191602.A28591@technokratis.com> <200106200224.TAA24251@usr05.primenet.com> <20010619232624.A29829@technokratis.com> <3B304ADF.C5131399@mindspring.com> <20010620123029.A34452@technokratis.com> <3B30D941.6AE93443@mindspring.com> <20010620135939.A34888@technokratis.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Bosko Milekic wrote: > > Before I go into this [the topic seems to have diverged a > little], has anybody gotten around to testing (or has the > hardware to do the testing required?) - if some of you guys > are stuck with the fact that you have the hardware but don't > run -CURRENT, please let me know - I could generate an > equivalent patch for -STABLE, with a little work. It hasn't wandered too far: your motivation was to make life easier for your allocator. I patched 4.3-RELEASE and tried with a borrowed Intel Gigabit card in an Intel based box, but then let the owner of the box reboot to our standard kernel after one FTP down. It seemed to work. Our standard kernel statically allocates mbufs out of physical RAM using VALLOC() at boot time, so we pay zero cost for the pool allocation, and O(1) cost for all allocations and deallocations, with zero wasted bytes, and are in no danger from the 2 byte underflow on copy. I think you now see why I'm a bit more interested in a generalized version of the allocator, and thing this change is benign enough that, if Bill Paul approves, it is OK with me. -- > > May I offer a suggestion? The purpose of having the > > clusters be a fixed size, given a much larger number > > of mbufs has never really been clear to me, given that > > mbufs are allocated to act as cluster headers, to make > > things a tiny bit (but not substantially) easier, when > > it comes to freing chains, etc.. > > The reason is that clusters are not used everywhere, > but mbufs are (even when the storage type is not a cluster). Yes, I know: tcptmpl, ring buffers for ethernet cards, cluster headers, and mbufs. > > It seems to me that what you really want to do is > > allocate _different sizes_ of mbufs, and have the > > deallocator sort them out on free. > > Believe me, I've thought about this. Alfred Perlstein > has been pushing me to do something like this for a while now. > There are several problems with the suggestion, but it's > something to consider in the future. I'd rather allow mb_alloc > to stabilize a little more after committing it, work at > lockifying net*/, unwind Giant, and then continue to deal with > issues such as this. I think that you should change the code to explicitly relinquish Giant on entry, and reacquire it on exit; that would be a better test of whether or not the data structures were sufficiently protected in the absence of Giant, without needing to debug everything on the unroll. You could put this in INVARIANTS or DEBUG_MB_ALLOC, or whatever. > > Do you have any interest in generalizing your allocator? > > Well, not really. See, the allocator is a specialization > of a general allocator. One of the main design goals of the > allocator is performance. I tried very hard to give the new > allocator the advantages required for scalability and the > "infrastructure" required to reclaim memory while keeping > approximately the same allocation/deallocation standards of > the present allocator. One important performance advantage > of the present allocator relative to say the NetBSD or OpenBSD > mbuf allocations/deallocations is that > we *never* have to free pages back to the map from m_free() > (an expensive procedure). This is precisely why I'd like to > have freeing eventually implemented from a kproc, when it can > be handled only when really needed without affecting network > performance. General purpose allocations should probably be > handled differently. Turning the mbufs type-stable didn't seem to affect the performance postively to any significant extent; this might have just been balancing of the lock overhead, but I have a hard time believing that it could be that balanced; the spiking seen in the without/with comparison occurred on both, so that probably wasn't it. I also have a minor concern with the deallocation back to the bucket locking things up; maybe a kproc per CPU now would let you queue deallocations that were non-local, and get rid of many of those locks (substituting locks that only IPI two CPUs instead of all of them to do a queue content exchange). If you have a general version of the allocator, it would be better to show it now, rather than a cut-down version. My guess is that it would not have an effect on John Lemon's or your benchmarks, one way or the other. Obviously, I'm a bit biased, given that I don't really allocate mbufs any more, I only pull them off or put them on a freelist. > > Eventually, you will probably want to do allocations of > > things other than mbufs. > > There *is* a general version of an allocator such > as mb_alloc. In fact, as is mentionned in the introductory > comments in subr_mbuf.c, mb_alloc is in part based on Alfred's > "memcache" allocator. Although a little outdated, the source is: > > http://people.freebsd.org/~alfred/memcache/ > > All it needs is a little bit of cleaning up/fixing up > and it's ready to fly for general purpose allocations. Keep > in mind, though, that these types of allocators have a wastage > factor that becomes significant as the size of the objects > being allocated approaches (falls to) the size of a pointer. > The reason is that the free list is implemented with an > allocated pointer array [it's done this way for very specific > reasons which i'll keep out of this Email] and if you're > allocating a page worth of ptr-size objects, youre spending > a whole other page for the pointers for a one page worth > freelist for these objects. I'm aware of Alfred's allocator; the overhead could be significantly reduced, but, as you say, not a topic for this thread. > The whole reason I wrote mb_alloc separately from > memcache altogether is to allow for the different type of > freeing to occur, I think it should be a flag in the object description, it would add a single compare, but the code would be much more general. > and to allow for future very mbuf-specific alloc. > optimizations to occur, Since mbuf's are 1/16th page sized objects (1/32nd on Alpha), there's not really a lot you have to do about that to make it work. There's actually a general trick you could do using the paging subsystem. > and to allow us to inline the code in the mbuf allocation > functions, This is not really a very good reason; a tiny compiler change would end up doing a much better job for this. > and ... (some other less worthy reasons) [glancing over > subr_mbuf.c a few times should make these things obvious]. Yes. > > Also, the buckets should probably be permitted to be > > some multiple of the page size, in order to permit the > > allocation of odd-sized structures, and allow them to > > span page boundaries, if you went ahead with a more > > general approach. > > This is done in memcache, actually. Actually, that's broken, or what I would consider to be broken, the same way the zone allocator is... > > I guess the next thing to think about after that would > > be allocation at interrupt time. I think this can be > > done using the ziniti() approach; but you would then > > reserve the KVA space for use by the allocator at page > > fault time, instead. > > This is for the general allocator, right? Yeah, > memcache can be made to optionally reserve KVA space for > interrupt-time allocations; mind you, it would only serve > as an optimization. As I previously mentionned for mb_alloc, > the KVA space needed is already reserved. This is really a pessimization, when it isn't needed. KVA space is at an ungodly premium. That's true of the current stuff without your code, too... 8-(. > > I have some other methods of getting around faulting, > > when you have sufficient backing store. Now that there > > are systems that have the capability of having as much > > RAM as the KVA space (e.g. the KVA space is really no > > longer sparse), there are a number of optimizations > > that become pretty obvious. > > Cool. Do share. Had my trip to Usenix this year not > been cancelled due to the fact that I'm going to see family > in Yugoslavia this Saturday, I would have gathered you and > Alfred together, and listened over a few beers. Boston and SF are not that close together. 8-). Basically, you do evil things with the paging code, which end up being a bit complicated, but really, really fast. -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Thu Jun 21 7:27:48 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from relay.tecc.co.uk (luggage.tecc.co.uk [193.128.6.129]) by hub.freebsd.org (Postfix) with SMTP id C6FB137B403; Thu, 21 Jun 2001 07:27:43 -0700 (PDT) (envelope-from andy@tecc.co.uk) Received: from southampton [195.217.37.155] by relay.tecc.co.uk with smtp (Exim 1.70 #1) id 15D5Qs-0007MA-00; Thu, 21 Jun 2001 15:27:42 +0100 From: "Andy" To: Cc: Subject: kvm problem on Alpha Date: Thu, 21 Jun 2001 15:27:42 +0100 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Hi All I have a friend in Germany who's using the Alpha, aka, uname -a :- FreeBSD m380.vpl.bauwesen.tu-muenchen.de / 4.3-RELEASE FreeBSD / 4.3-RELEASE #0: Thu Jun 7 16: / 19:49 CEST 2001 xxx.de:/usr/src/sys/compile/FGV2 alpha At securelevel=1 when running "netstat -rn" he gets the following error:- netstat: kvm not available Routing tables rt_tables: symbol not in namelist I'm running i386 and not able to reproduce the error. Anyone know anything on this? Regards Andy To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Thu Jun 21 8:55:32 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from beppo.feral.com (beppo.feral.com [192.67.166.79]) by hub.freebsd.org (Postfix) with ESMTP id E3A8A37B401; Thu, 21 Jun 2001 08:55:26 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from wonky.feral.com (wonky.feral.com [192.67.166.7]) by beppo.feral.com (8.11.3/8.11.3) with ESMTP id f5LFtOg71881; Thu, 21 Jun 2001 08:55:24 -0700 (PDT) (envelope-from mjacob@feral.com) Date: Thu, 21 Jun 2001 08:55:21 -0700 (PDT) From: Matthew Jacob Reply-To: To: John Baldwin , Andrew Gallatin Cc: Subject: more panics, with some traceback info.... Message-ID: <20010621081950.Q18589-100000@wonky.feral.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org panic: blockable sleep lock (sleep mutex) Giant @ ../../vm/vm_fault.c:213 cpuid = 0; panic db> t Debugger() at Debugger+0x34 panic() at panic+0x178 witness_lock() at witness_lock+0x240 vm_fault() at vm_fault+0x108 trap() at trap+0xf78 XentMM() at XentMM+0x2c --- memory management fault (from ipl 7) --- hardclock() at hardclock+0x308 handleclock() at handleclock+0x22c alpha_clock_interrupt() at alpha_clock_interrupt+0x68 interrupt() at interrupt+0xb8 XentInt() at XentInt+0x28 --- interrupt (from ipl 0) --- witness_unlock() at witness_unlock+0x50 zalloc() at zalloc+0x28c get_pv_entry() at get_pv_entry+0x70 pmap_insert_entry() at pmap_insert_entry+0x34 pmap_enter_quick() at pmap_enter_quick+0x214 pmap_object_init_pt() at pmap_object_init_pt+0x1b8 vm_map_insert() at vm_map_insert+0x37c elf_load_section() at elf_load_section+0x33c exec_elf_imgact() at exec_elf_imgact+0x528 execve() at execve+0x274 syscall() at syscall+0x708 XentSys() at XentSys+0x64 --- syscall (59, FreeBSD ELF, execve) --- --- user mode --- db> show locks exclusive (sleep mutex) zone (0xfffffc000083d5c0) locked @ ../../vm/vm_zone.c:373 exclusive (sleep mutex) vm (0xfffffc000084b180) locked @ ../../kern/imgact_elf.c:236 exclusive (sleep mutex) Giant (0xfffffc000084be18) locked @ ../../vm/vm_fault.c:213 exclusive (spin mutex) callout (0xfffffc0000845238) locked @ ../../kern/kern_clock.c:213 A minor amount of sleuthing yields: if (TAILQ_FIRST(&callwheel[ticks & callwheelmask]) != NULL) { as nearest the likely faulting line. A little sleuthing around about the value of ticks && callwheelmask led me to believe that I should check the contents of callwheel... so, callwheelmask was 4095, and masking that with ticks, I went to check into that offset via DDB, and the system froze- I probably got the offset wrong. The assembler lines are: hardclock+0x2e0: addq t0,#0x1,t0 hardclock+0x2e4: stl t0,0(t1) ticks++; /* leaving ticks in t0 */ hardclock+0x2e8: ldq t1,0xffffffffffffbe68(gp) hardclock+0x2ec: ldl t1,0(t1) hardclock+0x2f0: and t0,t1,t0 Fetch callwheelmask, mask against ticks hardclock+0x2f4: addl t0,zero,t0 hardclock+0x2f8: ldq t1,0xffffffffffff89e8(gp) hardclock+0x2fc: ldq t1,0(t1) Fetch callwheel (?) hardclock+0x300: sll t0,#0x4,t0 Turn masked ticks into an index hardclock+0x304: addq t0,t1,t0 Form address to fetch hardclock+0x308: ldq t0,0(t0) Fetch callwheel[ticks & callwheelmask] -matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Thu Jun 21 11:56:28 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from technokratis.com (modemcable052.174-202-24.mtl.mc.videotron.ca [24.202.174.52]) by hub.freebsd.org (Postfix) with ESMTP id B3CD137B401 for ; Thu, 21 Jun 2001 11:56:22 -0700 (PDT) (envelope-from bmilekic@technokratis.com) Received: (from bmilekic@localhost) by technokratis.com (8.11.3/8.11.3) id f5LIui701030; Thu, 21 Jun 2001 14:56:44 -0400 (EDT) (envelope-from bmilekic) Date: Thu, 21 Jun 2001 14:56:44 -0400 From: Bosko Milekic To: Terry Lambert Cc: Terry Lambert , freebsd-alpha@FreeBSD.ORG Subject: Re: vx, lge, nge, dc, rl, sf, sis, sk, vr, wb users please TEST Message-ID: <20010621145644.A923@technokratis.com> References: <20010619191602.A28591@technokratis.com> <200106200224.TAA24251@usr05.primenet.com> <20010619232624.A29829@technokratis.com> <3B304ADF.C5131399@mindspring.com> <20010620123029.A34452@technokratis.com> <3B30D941.6AE93443@mindspring.com> <20010620135939.A34888@technokratis.com> <3B31B4F9.FA2D43F1@mindspring.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <3B31B4F9.FA2D43F1@mindspring.com>; from tlambert2@mindspring.com on Thu, Jun 21, 2001 at 01:48:57AM -0700 Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Thu, Jun 21, 2001 at 01:48:57AM -0700, Terry Lambert wrote: > I think you now see why I'm a bit more interested in a > generalized version of the allocator, and thing this > change is benign enough that, if Bill Paul approves, it > is OK with me. The change regarding m_devget() is not that closely tied with mb_alloc. I merely happened to discover the problem while testing mb_alloc, that's all. [...] > You could put this in INVARIANTS or DEBUG_MB_ALLOC, or whatever. Will do, (already done locally). > > > Do you have any interest in generalizing your allocator? > > > > Well, not really. See, the allocator is a specialization > > of a general allocator. One of the main design goals of the > > allocator is performance. I tried very hard to give the new > > allocator the advantages required for scalability and the > > "infrastructure" required to reclaim memory while keeping > > approximately the same allocation/deallocation standards of > > the present allocator. One important performance advantage > > of the present allocator relative to say the NetBSD or OpenBSD > > mbuf allocations/deallocations is that > > we *never* have to free pages back to the map from m_free() > > (an expensive procedure). This is precisely why I'd like to > > have freeing eventually implemented from a kproc, when it can > > be handled only when really needed without affecting network > > performance. General purpose allocations should probably be > > handled differently. > > Turning the mbufs type-stable didn't seem to affect the > performance postively to any significant extent; this Not having to perform calls to the VM code made things quite a bit faster. I speak from experience: some time ago, I implemented full-blown freeing to the map from the (old) "free an mbuf" function. Freeing pages directly from m_free() is significantly expensive. I struggled quite a bit and at one point had a discussion with Poul-Henning via Email. He offered some interesting suggestions that involved the actions of a kproc. I saved all the Emails and some of those ideas are found in mb_alloc. > might have just been balancing of the lock overhead, but > I have a hard time believing that it could be that balanced; > the spiking seen in the without/with comparison occurred on > both, so that probably wasn't it. > > I also have a minor concern with the deallocation back > to the bucket locking things up; maybe a kproc per CPU > now would let you queue deallocations that were non-local, > and get rid of many of those locks (substituting locks > that only IPI two CPUs instead of all of them to do a queue > content exchange). Yes and no. I just think that optimizing a case that is not supposed to occur often is a waste of resources (not to mention energy). One looks to optimize the most common case, as for the others, well, we hope to avoid them. I plan to commit the mb_alloc code today. When things in the net code play out eventually, we may want to test cases like the one you mention and see if they really offer an overall performance boost. > If you have a general version of the allocator, it would be > better to show it now, rather than a cut-down version. My > guess is that it would not have an effect on John Lemon's > or your benchmarks, one way or the other. > > Obviously, I'm a bit biased, given that I don't really > allocate mbufs any more, I only pull them off or put them > on a freelist. Well, that's nice. But, unfortunately, not everyone has the physical memory to give away [permanently] to the expense of the mbuf subsystem. The problem is obvious: you have unused wired-down pages dispersed across a free list. > > The whole reason I wrote mb_alloc separately from > > memcache altogether is to allow for the different type of > > freeing to occur, > > I think it should be a flag in the object description, it > would add a single compare, but the code would be much more > general. Perhaps. Ideally, we may want to look at allocating network related things from mb_alloc and have them all optionally freed from a kproc. I'd like to stay away from the possibility of dealing with freeing back to the map from the mbuf free code. > -- Terry Later, -- Bosko Milekic bmilekic@technokratis.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Thu Jun 21 14: 1:19 2001 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 B55B537B407; Thu, 21 Jun 2001 14:01:16 -0700 (PDT) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.3/8.9.3) with ESMTP id RAA12613; Thu, 21 Jun 2001 17:01:15 -0400 (EDT) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.11.3/8.9.1) id f5LL0jb43827; Thu, 21 Jun 2001 17:00:45 -0400 (EDT) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <15154.24701.724278.688574@grasshopper.cs.duke.edu> Date: Thu, 21 Jun 2001 17:00:45 -0400 (EDT) To: Cc: John Baldwin , Subject: Re: more panics, with some traceback info.... In-Reply-To: <20010621081950.Q18589-100000@wonky.feral.com> References: <20010621081950.Q18589-100000@wonky.feral.com> X-Mailer: VM 6.75 under 21.1 (patch 12) "Channel Islands" XEmacs Lucid Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org This looks very similar to other pmap corruption panics that have been posted in the past.. Is this at boot, or does it take a while for it to panic? Can somebody re-review my pmap_emulate_reference() hacks? Drew Matthew Jacob writes: > > > panic: blockable sleep lock (sleep mutex) Giant @ ../../vm/vm_fault.c:213 > cpuid = 0; panic > db> t > Debugger() at Debugger+0x34 > panic() at panic+0x178 > witness_lock() at witness_lock+0x240 > vm_fault() at vm_fault+0x108 > trap() at trap+0xf78 > XentMM() at XentMM+0x2c > --- memory management fault (from ipl 7) --- > hardclock() at hardclock+0x308 > handleclock() at handleclock+0x22c > alpha_clock_interrupt() at alpha_clock_interrupt+0x68 > interrupt() at interrupt+0xb8 > XentInt() at XentInt+0x28 > --- interrupt (from ipl 0) --- > witness_unlock() at witness_unlock+0x50 > zalloc() at zalloc+0x28c > get_pv_entry() at get_pv_entry+0x70 > pmap_insert_entry() at pmap_insert_entry+0x34 > pmap_enter_quick() at pmap_enter_quick+0x214 > pmap_object_init_pt() at pmap_object_init_pt+0x1b8 > vm_map_insert() at vm_map_insert+0x37c > elf_load_section() at elf_load_section+0x33c > exec_elf_imgact() at exec_elf_imgact+0x528 > execve() at execve+0x274 > syscall() at syscall+0x708 > XentSys() at XentSys+0x64 > --- syscall (59, FreeBSD ELF, execve) --- > --- user mode --- > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Thu Jun 21 14: 6:21 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from meow.osd.bsdi.com (meow.osd.bsdi.com [204.216.28.88]) by hub.freebsd.org (Postfix) with ESMTP id BF7C237B401 for ; Thu, 21 Jun 2001 14:06:19 -0700 (PDT) (envelope-from jhb@FreeBSD.org) Received: from laptop.baldwin.cx (john@jhb-laptop.osd.bsdi.com [204.216.28.241]) by meow.osd.bsdi.com (8.11.3/8.11.2) with ESMTP id f5LL5dI51864; Thu, 21 Jun 2001 14:05:39 -0700 (PDT) (envelope-from jhb@FreeBSD.org) 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 In-Reply-To: <15154.24701.724278.688574@grasshopper.cs.duke.edu> Date: Thu, 21 Jun 2001 16:01:11 -0700 (PDT) From: John Baldwin To: Andrew Gallatin Subject: Re: more panics, with some traceback info.... Cc: alpha@FreeBSD.org, mjacob@feral.com Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On 21-Jun-01 Andrew Gallatin wrote: > > This looks very similar to other pmap corruption panics that have been > posted in the past.. > > Is this at boot, or does it take a while for it to panic? > > Can somebody re-review my pmap_emulate_reference() hacks? I have already. I have them completely locked by vm_mtx now, but that results in some fun lock order reversals. I'm still having problems though. I'm also seeing vm_page corruption on the x86. My patches ar efull of debugging cruft right now though, but I'll try to put up what I have so far tomorrow. Unfortunately, I have meetings until then. :-/ I also have a new KTR tracepoint for trap's that should make things slightly easier for panics like this where we fault in a fault handler. -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - 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 Jun 21 14:14:14 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from beppo.feral.com (beppo.feral.com [192.67.166.79]) by hub.freebsd.org (Postfix) with ESMTP id B88E437B407; Thu, 21 Jun 2001 14:14:12 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from wonky.feral.com (wonky.feral.com [192.67.166.7]) by beppo.feral.com (8.11.3/8.11.3) with ESMTP id f5LLE9g72460; Thu, 21 Jun 2001 14:14:09 -0700 (PDT) (envelope-from mjacob@feral.com) Date: Thu, 21 Jun 2001 14:14:06 -0700 (PDT) From: Matthew Jacob Reply-To: To: Andrew Gallatin Cc: John Baldwin , Subject: Re: more panics, with some traceback info.... In-Reply-To: <15154.24701.724278.688574@grasshopper.cs.duke.edu> Message-ID: <20010621141214.V19145-100000@wonky.feral.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Thu, 21 Jun 2001, Andrew Gallatin wrote: > > This looks very similar to other pmap corruption panics that have been > posted in the past.. > > Is this at boot, or does it take a while for it to panic? This was a while into things. I'm a bit confused- the pmap corruption must be corrupting random kernel mapped items. I read this situation as having taken something allocated very early (callout wheel table) and taking some of it away. > Can somebody re-review my pmap_emulate_reference() hacks? I missed those, but it's not my area of strengths either. -matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Fri Jun 22 6:57:52 2001 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 DB56837B403; Fri, 22 Jun 2001 06:57:49 -0700 (PDT) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.3/8.9.3) with ESMTP id JAA01192; Fri, 22 Jun 2001 09:57:48 -0400 (EDT) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.11.3/8.9.1) id f5MDvJl45466; Fri, 22 Jun 2001 09:57:19 -0400 (EDT) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <15155.20159.22045.932429@grasshopper.cs.duke.edu> Date: Fri, 22 Jun 2001 09:57:19 -0400 (EDT) To: John Baldwin Cc: alpha@FreeBSD.org, mjacob@feral.com Subject: Re: more panics, with some traceback info.... In-Reply-To: References: <15154.24701.724278.688574@grasshopper.cs.duke.edu> X-Mailer: VM 6.75 under 21.1 (patch 12) "Channel Islands" XEmacs Lucid Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org John Baldwin writes: > > On 21-Jun-01 Andrew Gallatin wrote: > > > > This looks very similar to other pmap corruption panics that have been > > posted in the past.. > > > > Is this at boot, or does it take a while for it to panic? > > > > Can somebody re-review my pmap_emulate_reference() hacks? > > I have already. I have them completely locked by vm_mtx now, but that results > in some fun lock order reversals. I'm still having problems though. I'm also Heh ;) > seeing vm_page corruption on the x86. My patches ar efull of debugging cruft Well, that makes me a feel a lot better. > right now though, but I'll try to put up what I have so far tomorrow. > I also have a new KTR tracepoint for trap's that should make things slightly > easier for panics like this where we fault in a fault handler. Cool.. Drew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Fri Jun 22 12:16:11 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from mail2in.giga.net.tw (mail2in.giga.net.tw [203.133.1.16]) by hub.freebsd.org (Postfix) with ESMTP id A52E537B40B for ; Fri, 22 Jun 2001 12:15:03 -0700 (PDT) (envelope-from e10233@ms60.url.com.tw) Received: from enter (u182-136.u203-203.giga.net.tw [203.203.182.136]) by mail2in.giga.net.tw (Postfix) with SMTP id B957251808 for ; Sat, 23 Jun 2001 03:15:01 +0800 (CST) To: e10233@ms60.url.com.tw From: e10233@ms60.url.com.tw Subject: ¶W¸£¤O¤ß´¼¬ì§Þ Date: Sat, 23 Jun 2001 03:12:31 +0800 Message-Id: <37065.133700347221700.2393233@localhost> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary=jjchljbcfmksfqmu Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org --jjchljbcfmksfqmu Content-Type: text/plain; charset=big5 Content-Transfer-Encoding: 8bit ¿Ë·RªºªB¤Í; ¦b¦¹´£¨Ñ2001¦~³Ì·s¸£¤O¶}µo§Þ³N «e¨¥: ®Ú¾Ú¬ì¾Ç¬ã¨sÅã¥Ü¡A§Ú­Ì¤HÃþ¤j¸£¥i§l¦¬°O¾Ð2000¸U¥»¹Ï®Ñ¤j·§10­Ó¹Ï®ÑÀ] ¤§¶q¡A¥u­n²ß±o¥¿½Tªº°O¾Ð¤èªk¡A¥²¯à±N§Ú­Ì¤j¸£µo´§²OºvºÉ­P¡A¹ï¤H¡A¨Æ ¡Aª«¥t¦³¤@µf¤£¦P¨¤«×¨£¸Ñ¡AÂǦ¹½Òµ{¦@¦P±´¯Á¤j¸£¤F¯«©_¡C ¡·"§Ú­Ìªº±M·~ §Ú­Ì¨ã¦³¥¿²Îªº­^°êMind Maps¤ß´¼Ã¸¹Ïªkªº±Â½ÒÃҮѡA±Ð±z¾Ç²ß­±¹ï21¥@¬ö ªºÄvª§¥²³Æªº§Þ¥©¡B±´¯ÁÁA¸Ñ§Ú­Ì¯«©_ªº¤j¸£¡A½Õ¾ã¾Ç²ßªº¹LÂo¾¹"¶W±j°O¾Ð" ¾Ç²ß¤ß´¼¹Ïªº³W«h¤Î¦p¦ó¹B¥Î¤ß´¼Ã¸¹Ï Mind Maps ªº¤èªk¥´³y¤@Áûª÷ÀY¸£¥Hªï±µ21¥@¬öªº¬D¾Ô¡B°l¨D¥þ¤è¦ì¦¨¥\ªº¤H¥Í¡C ¡·"§Ú­Ìªº¥Øªº ¬°±Ð¾É¥¿½Tªº¾Ç²ß°O¾Ð¤è¦¡¡A¨Ï©ÒŪªº¬ì¥Ø¥i§¹¥þªº°O¦í¤Î¹B¥Î¡A´î¤Ö¾Ç²ß¤§ ®À§é·P¡A¨Ã´£°ª§A¾Ç²ßªº¿³½ì¡C ¤HÃþªº¤j¸£¥u¥Î¨ì3%~6%©|¦³94%¥H¤W³£¨S°V½m¶}µo¨Ï¥Î¡C §Ú­Ì¹B¥Î¤@®M«e±Mªù°V½m±¡³ø¤H­ûªº¤èªk¡A²×¥Í¨ü¥ÎµL½a¡A¦p°O¡G ©m¦W¡B¹q¸Ü¡(«P¶i¤H»ÚÃö«Y¡^¡B­I³æ¦r¡B¾Ç»y¨¥¡B°O¤½¦¡¡B¾ú¥v¡B¦a²z µ¥.... ·Ó§Ú­Ì±Ð§Aªº¤èªk¡A¥u»Ý30%ªº®É¶¡¡A¹F¦¨¦Ê¤À¤§¦Êªº¥\®Ä¡A¥u­n¦³¤ß¦¨ªø¡A ±q10·³¡ã75·³¬Ò «OÃÒ¼W¥[2~15­¿¥H¤Wªº°O¾Ð¤O(°ò¦°V½m)¡C §A·Q¾Ö¦³¶W±j¹L¤Hªº°O¾Ð¶Ü¡H ¹B¥Î¶W±j°O¾Ð°V½m¡B¤ß´¼ ¹Ï°V½m¤ÎÀu¶Õ¸£ªi°V½m¡A ¥i¥HÅý§Aªº°O¾Ð¤O¥ß¨è´£¤É2~15­¿¡C§AÁÙ¦b¬Ý¶Ü¡H§OµS¿Ý»°§Ö¦æ°Ê.... Åwªï¦³§Ó°l¨D¥þ¤è¦ì¦¨¥\¤§¦U¬ÉªB¤ÍÄâ®a(ªB)±a²²(¤Í)°Ñ¥[ª÷ÀY¸£°ò¦°V½m ½Òµ{¡A¸Ô²Ó±¡§Î½Ð¤Wºô¬d¸ß: http://98.to/super2100 ©ÎÀH«Hªþ¥ó µ¹¦Û¤v·Q¤@­Ó¨Ó¤W½Òªº²z¥Ñ: ¥Î³}®Ñ§½ªº®É¶¡¤Î¶R¤@¥»®Ñªº¿ú¡A°Ñ¥[§Ú­ÌÁ|¿ìªº°ò¦½Òµ{¡A «OÃÒ±z°O¾Ð¤O´£¤É2-15­¿¡A(±z¦h¤[¨S¤W®Ñ§½¶R®Ñ¤F©O?)µ´¹ïÅý±zª«¶W©Ò­È¡C ¡@ §Ú­Ì±N¤£©w´Á¦b¥x¥_¡A®ç¶é ¡A·s¦Ë¡A­]®ß¡A¥x¤¤¡A°ª¶¯Á|¿ì¥Ü½d½Òµ{,Åwªï¨Ó¹q¹w¬ù °ª¶¯:7¤ë¥÷¶}½Ò¤é´Á¤À§O¬°:7/4¬P´Á¤T¡A7/13¬P´Á¤­¡A7/26¬P´Á¥| ¥x¤¤Á`¤½¥qTEL¡G04-23165310 FAX:04-23165315 ¬¢ÂŤp©j °ª¶¯¤À¤½¥qTEL¡G07-3861373 0955045803 ¬¢ÂÅ¥ý¥Í ¥þ¬Ù¨ä¥L¦a°Ï ½Ð¬¢ 0965-129085 ¥»°T®§¬O©e°Uµo°e¡A½Ð¤£­nª½±µ¦^ÂÐ¥»«H¡A¦pªG±z¤£·Q¦A±µ¦¬ ¥»°T®§¡A½Ð¦^«H¦Ü¥H¤U«H½cE-mail«H½c¡G:kaohsiung807@edirect168.com:: ¦p¦³¥´ÂZ±z¤§³B¡A½Ð¦h¦h¥]²[¡AÁÂÁ¡I¡I --jjchljbcfmksfqmu Content-Type: text/html; name="¤W½Òµý.htm" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="¤W½Òµý.htm" PGh0bWw+DQoNCjxoZWFkPg0KPG1ldGEgaHR0cC1lcXVpdj0iQ29udGVudC1UeXBl IiBjb250ZW50PSJ0ZXh0L2h0bWw7IGNoYXJzZXQ9YmlnNSI+DQo8dGl0bGU+t3O6 9K22OTwvdGl0bGU+DQo8bWV0YSBuYW1lPSJHRU5FUkFUT1IiIGNvbnRlbnQ9Ik1p Y3Jvc29mdCBGcm9udFBhZ2UgNC4wIj4NCjxtZXRhIG5hbWU9IlByb2dJZCIgY29u dGVudD0iRnJvbnRQYWdlLkVkaXRvci5Eb2N1bWVudCI+DQo8bWV0YSBuYW1lPSJN aWNyb3NvZnQgVGhlbWUiIGNvbnRlbnQ9Im5vbmUsIGRlZmF1bHQiPg0KPG1ldGEg bmFtZT0iTWljcm9zb2Z0IEJvcmRlciIgY29udGVudD0ibm9uZSwgZGVmYXVsdCI+ DQo8L2hlYWQ+DQoNCjxib2R5Pg0KDQo8cD690LFOprmq7a7mpkOmTCYjMjI2MjU7 vGer4bbHr3Wm3DA0LTIzMTY1MzE1pXikpMFgpL2lcbl3rPkspbukvaVxsU6md7HG pM6naaq+sPLCpr3StXuuybahqu27UKZVv6Slq6RXvdKmYcJJLLtQsXqxtayiqkGw yC7BwsHCIQ0KDQo8cD6hQA0KDQo8dGFibGUgYm9yZGVyPSIxIiB3aWR0aD0iMTAw JSIgaGVpZ2h0PSIyODAiPg0KICA8dHI+DQogICAgPHRkIHdpZHRoPSIzNCUiIGNv bHNwYW49IjIiIGhlaWdodD0iNDUiPjxzcGFuIHN0eWxlPSJGT05ULUZBTUlMWTog t3Oy06n6xek7IG1zby1hc2NpaS1mb250LWZhbWlseTogJ1RpbWVzIE5ldyBSb21h biciPqfarW6w0aVbpmHCSTogDQogICAgICA8L3NwYW4+PC90ZD4NCiAgICA8dGQg d2lkdGg9IjM5JSIgY29sc3Bhbj0iMiIgaGVpZ2h0PSI0NSI+PHNwYW4gc3R5bGU9 IkZPTlQtRkFNSUxZOiC3c7LTqfrF6SI+PGlucHV0IHR5cGU9ImNoZWNrYm94IiB2 YWx1ZT0iT04iIG5hbWU9IkMxIj48L3NwYW4+PGZvbnQgc2l6ZT0iMyI+PHNwYW4g c3R5bGU9IkZPTlQtRkFNSUxZOiC3c7LTqfrF6TsgbXNvLWFzY2lpLWZvbnQtZmFt aWx5OiAnVGltZXMgTmV3IFJvbWFuJyI+Jm5ic3A7pWu4ozwvc3Bhbj48L2ZvbnQ+ PGZvbnQgc2l6ZT0iMyI+PHNwYW4gc3R5bGU9IkxFVFRFUi1TUEFDSU5HOiAycHgi Pq7Er+CwVr1tPC9zcGFuPjxzcGFuIHN0eWxlPSJGT05ULUZBTUlMWTogt3Oy06n6 xek7IG1zby1hc2NpaS1mb250LWZhbWlseTogJ1RpbWVzIE5ldyBSb21hbiciPrDy wqa90rV7PC9zcGFuPjwvZm9udD6hQDwvdGQ+DQogICAgPHRkIHdpZHRoPSIyNyUi IHJvd3NwYW49IjYiIGhlaWdodD0iMjc0Ij4mbmJzcDsmbmJzcDsmbmJzcDsmbmJz cDsmbmJzcDsmbmJzcDsgIA0KICAgICAgPGZvbnQgc2l6ZT0iNSIgZmFjZT0itles 479Bssq2wiI+PGI+sKq2r7r0r7g8L2I+PC9mb250Pg0KICAgICAgPHA+PGZvbnQg Y29sb3I9IiNmZjAwMDAiPjxzcGFuIHN0eWxlPSJGT05ULUZBTUlMWTogt3Oy06n6 xek7IG1zby1iaWRpLWZvbnQtc2l6ZTogMTIuMHB0OyBtc28tYXNjaWktZm9udC1m YW1pbHk6IFRpbWVzIE5ldyBSb21hbiI+PGZvbnQgc2l6ZT0iMiI+pXilX6FBt3Om y6FBrue26aFBpXikpDwvZm9udD48L3NwYW4+PC9mb250PjxzcGFuIHN0eWxlPSJG T05ULUZBTUlMWTogt3Oy06n6xek7IG1zby1iaWRpLWZvbnQtc2l6ZTogMTIuMHB0 OyBtc28tYXNjaWktZm9udC1mYW1pbHk6IFRpbWVzIE5ldyBSb21hbiI+PGZvbnQg c2l6ZT0iMiI+PGZvbnQgY29sb3I9IiNmZjAwMDAiPqFBsKq2rzwvZm9udD6oQ7P1 PGZvbnQgY29sb3I9IiNmZjAwMDAiPq2tpEekUTwvZm9udD6kSKFBqEOsULTBpXW2 fTxmb250IGNvbG9yPSIjZmYwMDAwIj6kQKa4PC9mb250PqFBvdC0o6tluXes+aFB wcLBwqFJPC9mb250Pjwvc3Bhbj6hQDwvcD4NCiAgICA8L3RkPg0KICA8L3RyPg0K ICA8dHI+DQogICAgPHRkIHdpZHRoPSIzNCUiIGNvbHNwYW49IjIiIHJvd3NwYW49 IjIiIGhlaWdodD0iNDEiPjxzcGFuIHN0eWxlPSJGT05ULUZBTUlMWTogt3Oy06n6 xek7IG1zby1hc2NpaS1mb250LWZhbWlseTogJ1RpbWVzIE5ldyBSb21hbiciPqlt plc7PC9zcGFuPjwvdGQ+DQogICAgPHRkIHdpZHRoPSIxMyUiIGhlaWdodD0iMzUi IHJvd3NwYW49IjIiPjxzcGFuIHN0eWxlPSJGT05ULUZBTUlMWTogt3Oy06n6xek7 IG1zby1hc2NpaS1mb250LWZhbWlseTogJ1RpbWVzIE5ldyBSb21hbiciPsFwtbi5 cbjcOjwvc3Bhbj6hQKFAPC90ZD4NCiAgICA8dGQgd2lkdGg9IjI2JSIgaGVpZ2h0 PSIxNyI+oUA8L3RkPg0KICA8L3RyPg0KICA8dHI+DQogICAgPHRkIHdpZHRoPSIy NiUiIGhlaWdodD0iMTgiPqFAPC90ZD4NCiAgPC90cj4NCiAgPHRyPg0KICAgIDx0 ZCB3aWR0aD0iNzMlIiBjb2xzcGFuPSI0IiBoZWlnaHQ9IjUxIj48c3BhbiBzdHls ZT0iRk9OVC1GQU1JTFk6ILdzstOp+sXpOyBtc28tYXNjaWktZm9udC1mYW1pbHk6 ICdUaW1lcyBOZXcgUm9tYW4nIj6m7ad9Ozwvc3Bhbj48L3RkPg0KICA8L3RyPg0K ICA8dHI+DQogICAgPHRkIHdpZHRoPSIxMSUiIHJvd3NwYW49IjIiIGhlaWdodD0i MTE5Ij48c3BhbiBzdHlsZT0iRk9OVC1GQU1JTFk6ILdzstOp+sXpOyBtc28tYXNj aWktZm9udC1mYW1pbHk6ICdUaW1lcyBOZXcgUm9tYW4nIj6kdadAqcq96Dwvc3Bh bj48L3RkPg0KICAgIDx0ZCB3aWR0aD0iMjMlIiBoZWlnaHQ9IjExMyIgcm93c3Bh bj0iMiI+PHNwYW4gc3R5bGU9IkZPTlQtRkFNSUxZOiC3c7LTqfrF6SI+PGlucHV0 IHR5cGU9ImNoZWNrYm94IiB2YWx1ZT0iT04iIG5hbWU9IkMxIj6+x6XNPGlucHV0 IHR5cGU9ImNoZWNrYm94IiB2YWx1ZT0iT04iIG5hbWU9IkMxIj6kvTxpbnB1dCB0 eXBlPSJjaGVja2JveCIgdmFsdWU9Ik9OIiBuYW1lPSJDMSI+PC9zcGFuPrDToUAN CiAgICAgIDxwPjxpbnB1dCB0eXBlPSJjaGVja2JveCIgdmFsdWU9Ik9OIiBuYW1l PSJDMSI+pHU8aW5wdXQgdHlwZT0iY2hlY2tib3giIHZhbHVlPSJPTiIgbmFtZT0i QzEiPjxpbnB1dCB0eXBlPSJjaGVja2JveCIgdmFsdWU9Ik9OIiBuYW1lPSJDMSI+ qkGwyLd+oUA8L3A+DQogICAgPC90ZD4NCiAgICA8dGQgd2lkdGg9IjEzJSIgaGVp Z2h0PSI1MiI+PHNwYW4gc3R5bGU9IkZPTlQtRkFNSUxZOiC3c7LTqfrF6TsgbXNv LWFzY2lpLWZvbnQtZmFtaWx5OiAnVGltZXMgTmV3IFJvbWFuJyI+pn7E1jo8L3Nw YW4+oUA8L3RkPg0KICAgIDx0ZCB3aWR0aD0iMjYlIiBoZWlnaHQ9IjUyIj48c3Bh biBzdHlsZT0iRk9OVC1GQU1JTFk6ILdzstOp+sXpOyBtc28tYXNjaWktZm9udC1m YW1pbHk6ICdUaW1lcyBOZXcgUm9tYW4nIj6zxrX5PC9zcGFuPjxzcGFuIHN0eWxl PSJmb250LWZhbWlseTogt3Oy06n6xek7IG1zby1hc2NpaS1mb250LWZhbWlseTog VGltZXMgTmV3IFJvbWFuIj6hRzwvc3Bhbj6hQDwvdGQ+DQogIDwvdHI+DQogIDx0 cj4NCiAgICA8dGQgd2lkdGg9IjM5JSIgaGVpZ2h0PSI2MSIgY29sc3Bhbj0iMiI+ oUA8Zm9udCBzaXplPSI1Ij7AdbRmvXO4uaFHPGZvbnQgY29sb3I9IiNGRjAwMDAi PjAwPGI+NTYwMzAzPC9iPjwvZm9udD48L2ZvbnQ+oUA8L3RkPg0KICA8L3RyPg0K PC90YWJsZT4NCg0KPHA+PGZvbnQgY29sb3I9IiNGRjAwMDAiPiAgICAgDQoxLr7M prmkV73Stf3DuqXmMzUwpLjBv7hxtk+hQbP1pmG2TyAgIDIutUykV73Stf2qzKRX vdKrZbvdw7ql5jE1MDCkuKzjst+2TzwvZm9udD48L3A+ICANCjxkaXYgYWxpZ249 ImNlbnRlciI+DQogIDxjZW50ZXI+IA0KICA8dGFibGU+IA0KICAgIDx0cj4gDQog DQo8Zm9udCBmYWNlPSK3c7LTqfrF6SI+IA0KICAgICAgPHRkIHdpZHRoPSIxMDAl Ij6leKSkwWCkvaVxVEVMoUcwNC0yMzE2NTMxMCZuYnNwOyBGQVg6MDQtMjMxNjUz MTUgICAgICANCiAgICAgICAgrKI8Zm9udCBjb2xvcj0iIzAwMDBmZiI+wsWkcKlq PC9mb250PjwvdGQ+IA0KPC9mb250PiANCg0KICAgIDwvdHI+IA0KICAgIDx0cj4g DQogDQo8Zm9udCBmYWNlPSK3c7LTqfrF6SI+IA0KICAgICAgPHRkIHdpZHRoPSIx MDAlIj6wqravpMCkvaVxVEVMoUcwNy0zODYxMzczJm5ic3A7Jm5ic3A7Jm5ic3A7 ICAgICAgDQogICAgICAgIDA5NTUwNDU4MDMmbmJzcDsmbmJzcDsmbmJzcDsmbmJz cDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsgICAgICANCiAg ICAgICAgrKI8Zm9udCBjb2xvcj0iIzAwMDBmZiI+wsWl/aXNPC9mb250PjwvdGQ+ IA0KPC9mb250PiANCg0KICAgIDwvdHI+IA0KICAgIDx0cj4gDQogDQo8Zm9udCBm YWNlPSK3c7LTqfrF6SI+IA0KICAgICAgPHRkIHdpZHRoPSIxMDAlIj48Zm9udCBj b2xvcj0iIzAwMDBmZiI+pf6s2ajkpUymYbDPvdCsoiZuYnNwOyA8L2ZvbnQ+PGI+ PGZvbnQgY29sb3I9IiNmZjk5MDAiIGZhY2U9IkFyaWFsIiBjbGFzcz0iZm9udDE2 cHgiIHNpemU9IjMiPjA5NjUtMTI5MDg1PC9mb250PjwvYj4gIA0KPGZvbnQgY29s b3I9IiMwMDAwZmYiPsLFpf2lzSZuYnNwOyZuYnNwOyA8L2ZvbnQ+PGEgaHJlZj0i bWFpbHRvOnN1cGVyXzIxMDBAc2luYW1haWwuY29tIj48Zm9udCBjb2xvcj0iI0ZG MDAwMCI+qc6o06tIPC9mb250PjwvYT4gIA0KPC9mb250PiANCg0KICAgICAgPC90 ZD4gDQogICAgPC90cj4NCiAgPC90YWJsZT4NCiAgPC9jZW50ZXI+DQo8L2Rpdj4N Cg0KPC9ib2R5Pg0KDQo8L2h0bWw+DQo= --jjchljbcfmksfqmu-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Sat Jun 23 12:50:48 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from web14805.mail.yahoo.com (web14805.mail.yahoo.com [216.136.224.221]) by hub.freebsd.org (Postfix) with SMTP id 5902837B401 for ; Sat, 23 Jun 2001 12:50:46 -0700 (PDT) (envelope-from a_trans2001@yahoo.com) Message-ID: <20010623195046.34844.qmail@web14805.mail.yahoo.com> Received: from [24.248.85.196] by web14805.mail.yahoo.com; Sat, 23 Jun 2001 12:50:46 PDT Date: Sat, 23 Jun 2001 12:50:46 -0700 (PDT) From: La Place Subject: compilation errors on DS20 To: freebsd-alpha@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org I got an AlphaServer DS20 and is tracking -CURRENT. Whenever I try to compile the kernel, it complains: #/usr/sbin/config TEST ../../conf/files: coda/coda_fbsd.c must be optional, mandatory or standard Your version of config(8) is out of sync with your kernel source. so I try to update config(8) via cvs..cvs co src/usr.sbin/config..and attempt to make depend && make && make install..it complains #pwd /usr/src/usr.sbin/config #make depend && make && make install ..... a bunch of compilation msg... ..... /usr/src/usr.sbin/config/mkoptions.c: In function `options': /usr/src/usr.sbin/config/mkoptions.c:105: warning: passing arg 3 of `strncmp' with different width due to prototype cc -O -pipe -mcpu=ev4 -I. -I/usr/src/usr.sbin/config -W -Wall -ansi -pedantic -Wbad-function-cast -Wcast-align -Wcast-qual -Wchar-subscripts -Wconversion -Winline -Wmissing-prototypes -Wnested-externs -Wpointer-arith -Wredundant-decls -Wshadow -Wstrict-prototypes -Wwrite-strings -o config config.o main.o lang.o mkmakefile.o mkheaders.o mkoptions.o -ll make: don't know how to make config.1. Stop # how do i fix this? in addition to that, i noticed that the GENERIC conf file defines CPU_TYPE as ev4 or ev5..according to my dmesg(8), the proc is type EV6..do i just add an extra line for ev6?? __________________________________________________ Do You Yahoo!? Get personalized email addresses from Yahoo! Mail - only $35 a year! http://personal.mail.yahoo.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message