From owner-freebsd-hardware Sun Oct 24 23:52:16 1999 Delivered-To: freebsd-hardware@freebsd.org Received: from polaris.we.lc.ehu.es (polaris.we.lc.ehu.es [158.227.6.43]) by hub.freebsd.org (Postfix) with ESMTP id D400D151D1 for ; Sun, 24 Oct 1999 23:52:00 -0700 (PDT) (envelope-from jose@we.lc.ehu.es) Received: from we.lc.ehu.es (lxpxay.lx.ehu.es [158.227.99.124]) by polaris.we.lc.ehu.es (8.9.1/8.9.1) with ESMTP id VAA02957; Sat, 23 Oct 1999 21:01:44 +0200 (MET DST) Message-ID: <38120617.CA2EA948@we.lc.ehu.es> Date: Sat, 23 Oct 1999 21:01:43 +0200 From: "Jose M. Alcaide" Organization: Universidad del =?iso-8859-1?Q?Pa=EDs?= Vasco - Dept. de Electricidad y =?iso-8859-1?Q?Electr=F3nica?= X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 3.3-RELEASE i386) X-Accept-Language: es-ES, es, en-US, en MIME-Version: 1.0 To: freebsd-hardware@FreeBSD.org Cc: yokota@zodiac.mech.utsunomiya-u.ac.jp Subject: a desirable fetaure: syscons reset utility Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hello, I think that many of us have experienced Xserver crashes that leave the console (display, keyboard, or both) in a unusable state. Then, we log into the system from a serial terminal or another networked host and... now what? There is no way for resetting the console, turning it usable again (or there is?). A small utility capable of resetting the console would be very useful. What do you think about this idea, Mr Yokota? :-) -- JMA ----------------------------------------------------------------------- José Mª Alcaide | mailto:jose@we.lc.ehu.es Universidad del País Vasco | mailto:jmas@FreeBSD.ORG Dpto. de Electricidad y Electrónica | http://www.we.lc.ehu.es/~jose Facultad de Ciencias - Campus de Lejona | Tel.: +34-946012479 48940 Lejona (Vizcaya) - SPAIN | Fax: +34-946013071 ----------------------------------------------------------------------- "Beware of Programmers who carry screwdrivers" -- Leonard Brandwein To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Sun Oct 24 23:56:35 1999 Delivered-To: freebsd-hardware@freebsd.org Received: from dingo.cdrom.com (castles546.castles.com [208.214.165.110]) by hub.freebsd.org (Postfix) with ESMTP id 7151E15085 for ; Sun, 24 Oct 1999 23:56:32 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.3/8.8.8) with ESMTP id XAA16702; Sun, 24 Oct 1999 23:47:56 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199910250647.XAA16702@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: "Jose M. Alcaide" Cc: freebsd-hardware@FreeBSD.org, yokota@zodiac.mech.utsunomiya-u.ac.jp Subject: Re: a desirable fetaure: syscons reset utility In-reply-to: Your message of "Sat, 23 Oct 1999 21:01:43 +0200." <38120617.CA2EA948@we.lc.ehu.es> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Date: Sun, 24 Oct 1999 23:47:56 -0700 From: Mike Smith Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > I think that many of us have experienced Xserver crashes that > leave the console (display, keyboard, or both) in a unusable state. > Then, we log into the system from a serial terminal or another > networked host and... now what? There is no way for resetting the > console, turning it usable again (or there is?). A small utility capabl= e > of resetting the console would be very useful. What do you think > about this idea, Mr Yokota? :-) We've discussed this before. The end result: forget it. -- = \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Mon Oct 25 0:31:25 1999 Delivered-To: freebsd-hardware@freebsd.org Received: from outmail.utsunomiya-u.ac.jp (outmail.utsunomiya-u.ac.jp [160.12.196.3]) by hub.freebsd.org (Postfix) with ESMTP id 26FFD15089 for ; Mon, 25 Oct 1999 00:31:15 -0700 (PDT) (envelope-from yokota@zodiac.mech.utsunomiya-u.ac.jp) Received: from zodiac.mech.utsunomiya-u.ac.jp (IDENT:PCRBcG0Z7n7UDplxznqcGuKel5JoqDY+@zodiac.mech.utsunomiya-u.ac.jp [160.12.42.1]) by outmail.utsunomiya-u.ac.jp (8.9.3/3.7Wpl2) with ESMTP id QAA15190; Mon, 25 Oct 1999 16:30:48 +0900 (JST) Received: from zodiac.mech.utsunomiya-u.ac.jp (zodiac.mech.utsunomiya-u.ac.jp [160.12.42.1]) by zodiac.mech.utsunomiya-u.ac.jp (8.7.6+2.6Wbeta7/3.4W/zodiac-May96) with ESMTP id QAA11861; Mon, 25 Oct 1999 16:35:18 +0900 (JST) Message-Id: <199910250735.QAA11861@zodiac.mech.utsunomiya-u.ac.jp> To: "Jose M. Alcaide" Cc: freebsd-hardware@freebsd.org, yokota@zodiac.mech.utsunomiya-u.ac.jp Subject: Re: a desirable fetaure: syscons reset utility In-reply-to: Your message of "Sat, 23 Oct 1999 21:01:43 +0200." <38120617.CA2EA948@we.lc.ehu.es> References: <38120617.CA2EA948@we.lc.ehu.es> Date: Mon, 25 Oct 1999 16:35:17 +0900 From: Kazutaka YOKOTA Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >I think that many of us have experienced Xserver crashes that >leave the console (display, keyboard, or both) in a unusable state. >Then, we log into the system from a serial terminal or another >networked host and... now what? There is no way for resetting the >console, turning it usable again (or there is?). A small utility capable >of resetting the console would be very useful. What do you think >about this idea, Mr Yokota? :-) Try running the following sequence of commands. vidcontrol -s 0 < /dev/ttyv0 vidcontrol 80x25 < /dev/ttyv0 kbd_mode -a < /dev/ttyv0 The above sequence MIGHT work. But, sadly, it won't, in general. There isn't a reliable way of `resetting' video hardware once the X server has messed up with it. Kazu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Mon Oct 25 1:44: 1 1999 Delivered-To: freebsd-hardware@freebsd.org Received: from polaris.we.lc.ehu.es (polaris.we.lc.ehu.es [158.227.6.43]) by hub.freebsd.org (Postfix) with ESMTP id 47B6214BEA for ; Mon, 25 Oct 1999 01:43:11 -0700 (PDT) (envelope-from jose@we.lc.ehu.es) Received: from we.lc.ehu.es (garatu [158.227.6.222]) by polaris.we.lc.ehu.es (8.9.1/8.9.1) with ESMTP id KAA05855; Mon, 25 Oct 1999 10:42:32 +0200 (MET DST) Message-ID: <381417F8.1BFEB34B@we.lc.ehu.es> Date: Mon, 25 Oct 1999 10:42:32 +0200 From: "Jose M. Alcaide" Organization: Universidad del =?iso-8859-1?Q?Pa=EDs?= Vasco - Dpto. de Electricidad y =?iso-8859-1?Q?Electr=F3nica?= X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 3.3-RELEASE i386) X-Accept-Language: es-ES, es, en-US, en MIME-Version: 1.0 To: Kazutaka YOKOTA Cc: freebsd-hardware@freebsd.org Subject: Re: a desirable fetaure: syscons reset utility References: <38120617.CA2EA948@we.lc.ehu.es> <199910250735.QAA11861@zodiac.mech.utsunomiya-u.ac.jp> Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Kazutaka YOKOTA wrote: > > >I think that many of us have experienced Xserver crashes that > >leave the console (display, keyboard, or both) in a unusable state. > >Then, we log into the system from a serial terminal or another > >networked host and... now what? There is no way for resetting the > >console, turning it usable again (or there is?). A small utility capable > >of resetting the console would be very useful. What do you think > >about this idea, Mr Yokota? :-) > > Try running the following sequence of commands. > > vidcontrol -s 0 < /dev/ttyv0 > vidcontrol 80x25 < /dev/ttyv0 > kbd_mode -a < /dev/ttyv0 > > The above sequence MIGHT work. But, sadly, it won't, in general. > There isn't a reliable way of `resetting' video hardware once the X > server has messed up with it. > Oh, bad news. I tried that sequence of commands several times, without any luck. Well, we will have to live with this problem. Fortunately, my Xserver does not crash very often ;-) . Thanks, -- JMA ----------------------------------------------------------------------- José Mª Alcaide | mailto:jose@we.lc.ehu.es Universidad del País Vasco | mailto:jmas@FreeBSD.org Dpto. de Electricidad y Electrónica | http://www.we.lc.ehu.es/~jose Facultad de Ciencias - Campus de Lejona | Tel.: +34-946012479 48940 Lejona (Vizcaya) - SPAIN | Fax: +34-946013071 ----------------------------------------------------------------------- "Beware of Programmers who carry screwdrivers" -- Leonard Brandwein To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Mon Oct 25 3:40:49 1999 Delivered-To: freebsd-hardware@freebsd.org Received: from omnix.net (omnix.net [195.154.168.66]) by hub.freebsd.org (Postfix) with SMTP id 29C881516B for ; Mon, 25 Oct 1999 03:40:35 -0700 (PDT) (envelope-from didier@omnix.net) Received: (qmail 23164 invoked by uid 200); 25 Oct 1999 10:40:34 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 25 Oct 1999 10:40:34 -0000 Date: Mon, 25 Oct 1999 10:40:34 +0000 (GMT) From: Didier Derny To: freebsd-hardware@freebsd.org Subject: performance problem with scsi disk (3.3-RELEASE) Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org hi, I've a performance problem with a quantum fireball ST disk (4.3Gb) it runs fine with winblows95 and Beos4.5 but it's hell with FreeBSD the read speed is normal but the write speed usually at 4.5Mb/s (iozone 2.1) is reduce to less that 1.2Mb do you have any clue ? Thanks for your help -- didier@omnix.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Mon Oct 25 9: 7:35 1999 Delivered-To: freebsd-hardware@freebsd.org Received: from panzer.kdm.org (panzer.kdm.org [216.160.178.169]) by hub.freebsd.org (Postfix) with ESMTP id 82870151E0 for ; Mon, 25 Oct 1999 09:07:20 -0700 (PDT) (envelope-from ken@panzer.kdm.org) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id KAA18836; Mon, 25 Oct 1999 10:07:03 -0600 (MDT) (envelope-from ken) Message-Id: <199910251607.KAA18836@panzer.kdm.org> Subject: Re: performance problem with scsi disk (3.3-RELEASE) In-Reply-To: from Didier Derny at "Oct 25, 1999 10:40:34 am" To: didier@omnix.net (Didier Derny) Date: Mon, 25 Oct 1999 10:07:03 -0600 (MDT) Cc: freebsd-hardware@FreeBSD.ORG From: "Kenneth D. Merry" X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Didier Derny wrote... > > hi, > > I've a performance problem with a quantum fireball ST disk (4.3Gb) > it runs fine with winblows95 and Beos4.5 but it's hell with FreeBSD > the read speed is normal but the write speed usually at 4.5Mb/s (iozone > 2.1) is reduce to less that 1.2Mb It's generally better to send SCSI problems to the freebsd-scsi list. In any case, try disabling tagged queueing on the disk. You can do it like this (assuming the disk is da0): camcontrol negotiate da0 -v -T disable Ken -- Kenneth Merry ken@kdm.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Mon Oct 25 22:52:47 1999 Delivered-To: freebsd-hardware@freebsd.org Received: from jason.argos.org (a13b146.neo.rr.com [204.210.197.146]) by hub.freebsd.org (Postfix) with ESMTP id 29D1D1530D for ; Mon, 25 Oct 1999 22:52:45 -0700 (PDT) (envelope-from mike@argos.org) Received: from localhost (mike@localhost) by jason.argos.org (8.9.1/8.9.1) with ESMTP id BAA30970; Tue, 26 Oct 1999 01:52:02 -0400 Date: Tue, 26 Oct 1999 01:52:02 -0400 (EDT) From: Mike Nowlin To: "Jose M. Alcaide" Cc: Kazutaka YOKOTA , freebsd-hardware@FreeBSD.ORG Subject: Re: a desirable fetaure: syscons reset utility In-Reply-To: <381417F8.1BFEB34B@we.lc.ehu.es> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > The above sequence MIGHT work. But, sadly, it won't, in general. > > There isn't a reliable way of `resetting' video hardware once the X > > server has messed up with it. > > > > Oh, bad news. I tried that sequence of commands several times, without > any luck. Well, we will have to live with this problem. Fortunately, > my Xserver does not crash very often ;-) . I ran into this problem on some Linux boxes - somewhere, I found a program that saved the video card registers when it was in a "usable" mode (80x25 text) to a file, and let you restore them later... Basically, if the X server crashed, telnet into the dead machine, kill X, and use this program to restore the video card settings. Worked about 90% of the time, I'd guess. Is something like this available on FreeBSD (or need to be written?) mike To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Tue Oct 26 0:46:19 1999 Delivered-To: freebsd-hardware@freebsd.org Received: from outmail.utsunomiya-u.ac.jp (outmail.utsunomiya-u.ac.jp [160.12.196.3]) by hub.freebsd.org (Postfix) with ESMTP id 4F69714E7B for ; Tue, 26 Oct 1999 00:46:16 -0700 (PDT) (envelope-from yokota@zodiac.mech.utsunomiya-u.ac.jp) Received: from zodiac.mech.utsunomiya-u.ac.jp (IDENT:IHOk4mkBNP/DIBD26zCgFqY86URjXXe4@zodiac.mech.utsunomiya-u.ac.jp [160.12.42.1]) by outmail.utsunomiya-u.ac.jp (8.9.3/3.7Wpl2) with ESMTP id QAA23195; Tue, 26 Oct 1999 16:44:23 +0900 (JST) Received: from zodiac.mech.utsunomiya-u.ac.jp (zodiac.mech.utsunomiya-u.ac.jp [160.12.42.1]) by zodiac.mech.utsunomiya-u.ac.jp (8.7.6+2.6Wbeta7/3.4W/zodiac-May96) with ESMTP id QAA15139; Tue, 26 Oct 1999 16:48:53 +0900 (JST) Message-Id: <199910260748.QAA15139@zodiac.mech.utsunomiya-u.ac.jp> To: Mike Nowlin Cc: "Jose M. Alcaide" , freebsd-hardware@freebsd.org, yokota@zodiac.mech.utsunomiya-u.ac.jp Subject: Re: a desirable fetaure: syscons reset utility In-reply-to: Your message of "Tue, 26 Oct 1999 01:52:02 -0400." References: Date: Tue, 26 Oct 1999 16:48:52 +0900 From: Kazutaka YOKOTA Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >> > The above sequence MIGHT work. But, sadly, it won't, in general. >> > There isn't a reliable way of `resetting' video hardware once the X >> > server has messed up with it. >> > >> >> Oh, bad news. I tried that sequence of commands several times, without >> any luck. Well, we will have to live with this problem. Fortunately, >> my Xserver does not crash very often ;-) . > >I ran into this problem on some Linux boxes - somewhere, I found a program >that saved the video card registers when it was in a "usable" mode (80x25 >text) to a file, and let you restore them later... Basically, if the X >server crashed, telnet into the dead machine, kill X, and use this program >to restore the video card settings. Worked about 90% of the time, I'd >guess. Is something like this available on FreeBSD (or need to be >written?) This won't reliably work, if the said program is saving/restoring only the standard VGA registers. Because the X server touches various extra registers which are not present in the standard VGA, you need to save these registers as well as the standard VGA registers. Restoring only the standard VGA registers is not enough to bring the video card back to known state. When vidcontrol issues the ioctl command to switch the video mode, the vga video driver will set the standard VGA registers to the values listed in the card's BIOS ROM (or use the VESA BIOS to set up the VESA video mode). If the video BIOS cannot set up the card, then, what can we do? Does this Linux utility have some knowledge about extra registers and is able to save and restore them? Kazu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Tue Oct 26 2:53: 0 1999 Delivered-To: freebsd-hardware@freebsd.org Received: from polaris.we.lc.ehu.es (polaris.we.lc.ehu.es [158.227.6.43]) by hub.freebsd.org (Postfix) with ESMTP id 94BEA14BE4 for ; Tue, 26 Oct 1999 02:52:48 -0700 (PDT) (envelope-from jose@we.lc.ehu.es) Received: from we.lc.ehu.es (garatu [158.227.6.222]) by polaris.we.lc.ehu.es (8.9.1/8.9.1) with ESMTP id LAA11389; Tue, 26 Oct 1999 11:31:44 +0200 (MET DST) Message-ID: <381574FF.57884B79@we.lc.ehu.es> Date: Tue, 26 Oct 1999 11:31:43 +0200 From: "Jose M. Alcaide" Organization: Universidad del =?iso-8859-1?Q?Pa=EDs?= Vasco - Dpto. de Electricidad y =?iso-8859-1?Q?Electr=F3nica?= X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 3.3-RELEASE i386) X-Accept-Language: es-ES, es, en-US, en MIME-Version: 1.0 To: Richard Foulk Cc: Mike Nowlin , Kazutaka YOKOTA , freebsd-hardware@FreeBSD.ORG Subject: Re: a desirable fetaure: syscons reset utility References: <199910260712.VAA28371@pegasus.com> Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Richard Foulk wrote: > > That's pretty easy ... > > Save: stty -g > /tmp/save_flags > > Restore: stty `cat /tmp/save_flags` > > Or just restart X, it knows what settings it needs. > Uh? stty(1) only deals which the UNIX tty driver, which has nothing to do with the [S]VGA registers. Restart and quit X... sometimes work, but usually it does not. -- ----------------------------------------------------------------------- José Mª Alcaide | mailto:jose@we.lc.ehu.es Universidad del País Vasco | mailto:jmas@FreeBSD.org Dpto. de Electricidad y Electrónica | http://www.we.lc.ehu.es/~jose Facultad de Ciencias - Campus de Lejona | Tel.: +34-946012479 48940 Lejona (Vizcaya) - SPAIN | Fax: +34-946013071 ----------------------------------------------------------------------- "Beware of Programmers who carry screwdrivers" -- Leonard Brandwein To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Tue Oct 26 6:52:32 1999 Delivered-To: freebsd-hardware@freebsd.org Received: from polaris.we.lc.ehu.es (polaris.we.lc.ehu.es [158.227.6.43]) by hub.freebsd.org (Postfix) with ESMTP id 3881F14CB7 for ; Tue, 26 Oct 1999 06:50:50 -0700 (PDT) (envelope-from jose@we.lc.ehu.es) Received: from we.lc.ehu.es (garatu [158.227.6.222]) by polaris.we.lc.ehu.es (8.9.1/8.9.1) with ESMTP id PAA14744; Tue, 26 Oct 1999 15:42:38 +0200 (MET DST) Message-ID: <3815AFCE.DB4ECE98@we.lc.ehu.es> Date: Tue, 26 Oct 1999 15:42:38 +0200 From: "Jose M. Alcaide" Organization: Universidad del =?iso-8859-1?Q?Pa=EDs?= Vasco - Dpto. de Electricidad y =?iso-8859-1?Q?Electr=F3nica?= X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 3.3-RELEASE i386) X-Accept-Language: es-ES, es, en-US, en MIME-Version: 1.0 To: Kazutaka YOKOTA Cc: Mike Nowlin , freebsd-hardware@FreeBSD.ORG Subject: Re: a desirable fetaure: syscons reset utility References: <199910260748.QAA15139@zodiac.mech.utsunomiya-u.ac.jp> Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Kazutaka YOKOTA wrote: > > This won't reliably work, if the said program is saving/restoring only > the standard VGA registers. Because the X server touches various > extra registers which are not present in the standard VGA, you need to > save these registers as well as the standard VGA registers. Restoring > only the standard VGA registers is not enough to bring the video card > back to known state. > > When vidcontrol issues the ioctl command to switch the video mode, the > vga video driver will set the standard VGA registers to the values > listed in the card's BIOS ROM (or use the VESA BIOS to set up the > VESA video mode). If the video BIOS cannot set up the card, then, > what can we do? > This is very interesting. Then, the conclusion is that this problem should be redirected to the XFree86 people: perhaps, they could write a utility (probably adapted to each Xserver) that restores the [S]VGA registers. BTW, when the Xserver crashes, sometimes the keyboard is also left in an unusable state and "kbd_mode -a" does not solve the problem. Perhaps a new "reset" option for kbdcontrol could be useful and easy to implement 8) -- JMA ----------------------------------------------------------------------- José Mª Alcaide | mailto:jose@we.lc.ehu.es Universidad del País Vasco | mailto:jmas@FreeBSD.org Dpto. de Electricidad y Electrónica | http://www.we.lc.ehu.es/~jose Facultad de Ciencias - Campus de Lejona | Tel.: +34-946012479 48940 Lejona (Vizcaya) - SPAIN | Fax: +34-946013071 ----------------------------------------------------------------------- "Beware of Programmers who carry screwdrivers" -- Leonard Brandwein To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Tue Oct 26 9: 7:42 1999 Delivered-To: freebsd-hardware@freebsd.org Received: from dingo.cdrom.com (castles522.castles.com [208.214.165.86]) by hub.freebsd.org (Postfix) with ESMTP id 4DD5614BED for ; Tue, 26 Oct 1999 09:07:39 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.3/8.8.8) with ESMTP id IAA04237; Tue, 26 Oct 1999 08:56:05 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199910261556.IAA04237@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: "Jose M. Alcaide" Cc: Kazutaka YOKOTA , Mike Nowlin , freebsd-hardware@FreeBSD.ORG Subject: Re: a desirable fetaure: syscons reset utility In-reply-to: Your message of "Tue, 26 Oct 1999 15:42:38 +0200." <3815AFCE.DB4ECE98@we.lc.ehu.es> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Date: Tue, 26 Oct 1999 08:56:05 -0700 From: Mike Smith Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > This is very interesting. Then, the conclusion is that this problem > should be redirected to the XFree86 people: perhaps, they could write > a utility (probably adapted to each Xserver) that restores the [S]VGA > registers. Perhaps it would be better for the XFree86 people to concentrate on not = having their servers crash at all? Your proposal seems like such a = waste of time. 8( (It's also still clear that you don't understand the situation; please = stop irritating those of us that do and take our word for it - what you = want is simply not achievable.) -- = \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Tue Oct 26 10:59:49 1999 Delivered-To: freebsd-hardware@freebsd.org Received: from polaris.we.lc.ehu.es (polaris.we.lc.ehu.es [158.227.6.43]) by hub.freebsd.org (Postfix) with ESMTP id 3467C14F20 for ; Tue, 26 Oct 1999 10:59:26 -0700 (PDT) (envelope-from jose@we.lc.ehu.es) Received: from we.lc.ehu.es (garatu [158.227.6.222]) by polaris.we.lc.ehu.es (8.9.1/8.9.1) with ESMTP id TAA16813; Tue, 26 Oct 1999 19:59:06 +0200 (MET DST) Message-ID: <3815EBEA.77EE6A52@we.lc.ehu.es> Date: Tue, 26 Oct 1999 19:59:06 +0200 From: "Jose M. Alcaide" Organization: Universidad del =?iso-8859-1?Q?Pa=EDs?= Vasco - Dpto. de Electricidad y =?iso-8859-1?Q?Electr=F3nica?= X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 3.3-RELEASE i386) X-Accept-Language: es-ES, es, en-US, en MIME-Version: 1.0 To: Mike Smith Cc: freebsd-hardware@FreeBSD.ORG Subject: Re: a desirable fetaure: syscons reset utility References: <199910261556.IAA04237@dingo.cdrom.com> Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Mike Smith wrote: > > > This is very interesting. Then, the conclusion is that this problem > > should be redirected to the XFree86 people: perhaps, they could write > > a utility (probably adapted to each Xserver) that restores the [S]VGA > > registers. > > Perhaps it would be better for the XFree86 people to concentrate on not > having their servers crash at all? Your proposal seems like such a > waste of time. 8( Xservers are *very* complex. Sure, it would be better to have Perfect Xservers thar never crash. Maybe, this goal will be achieved. I don't think so, because new graphic cards will be always appearing, having an initial unstable support by the XFree86 servers. While waiting for that Happy Day of the Perfect Xservers, these will be crashing. > > (It's also still clear that you don't understand the situation; please > stop irritating those of us that do and take our word for it - what you > want is simply not achievable.) > I *understand* the situation: I *understand* that you have a natural tendency towards irritation. And I *understand* (after the clear explanation of the VGA register trouble by Kazu) that this problem cannot be solved in the syscons/vga driver, so I DON'T WANT THAT, OK? I only asked for that type of solution in my _first_ message. Please, the next time that you want to suggest (or affirm) that someone is an ignorant or even an idiot, read the messages from that person again and think about it twice. Thanks. -- JMA ----------------------------------------------------------------------- José Mª Alcaide | mailto:jose@we.lc.ehu.es Universidad del País Vasco | mailto:jmas@FreeBSD.org Dpto. de Electricidad y Electrónica | http://www.we.lc.ehu.es/~jose Facultad de Ciencias - Campus de Lejona | Tel.: +34-946012479 48940 Lejona (Vizcaya) - SPAIN | Fax: +34-946013071 ----------------------------------------------------------------------- "Beware of Programmers who carry screwdrivers" -- Leonard Brandwein To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Tue Oct 26 17:51: 7 1999 Delivered-To: freebsd-hardware@freebsd.org Received: from mx.emailqueue.net (mx0.emailqueue.net [209.240.140.250]) by hub.freebsd.org (Postfix) with ESMTP id 1908314BCC for ; Tue, 26 Oct 1999 17:50:42 -0700 (PDT) (envelope-from bs@cyalchemy.com) Received: from mx0.emailqueue.net (209.75.4.19) by mx.emailqueue.net (8.9.3/8.9.3) with ESMTP id RAA12363 for ; Tue, 26 Oct 1999 17:50:41 -0700 (PDT) (envelope-from bs@cyalchemy.com) Received: from ben ([63.70.222.240]) by mx0.emailqueue.net (8.9.3/8.9.3) with ESMTP id RAA97287 for ; Tue, 26 Oct 1999 17:50:41 -0700 (PDT) Message-Id: <4.2.0.58.19991026182732.00989a80@mail.cyalchemy.com> X-Sender: bs@mail.cyalchemy.com (Unverified) X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58 Date: Tue, 26 Oct 1999 18:48:56 -0600 To: freebsd-hardware@FreeBSD.org From: Ben Schumacher Subject: FreeBSD Server Hardware Configuration Question. Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hello- I am working on a project in my company where we will need to be able to handle large amounts of traffic on a web server we are setting up. Basically, we estimate about 75,000 visitors a day with roughly five 20k page views each, which makes roughly 7.5GB of data a day. Most of the pages we'll be offering on this site are static, but access to the site will be need to be verified through a database of say 750,000 customers. What I need is an idea of a good hardware configuration of (most likely) 2 machines that would be able to handle this much potential traffic. I've had a lot of experience with FreeBSD and think that it would be the best solution for this, running a combination of Apace and MySQL, but I need to know what I can do on the hardware side to support it. I guess what I really need is a good idea of what is necessary to make these machines powerful and responsive. I think the best solution for the web server would be a powerful P3 Xeon server, using a hardware RAID system with at least 1GB of RAM. The database server, on the other hand, I'm a little more unsure about. I haven't had enough experience with MySQL to know what keeps to running fast and smooth. I figure that it probably relies heavily on drive speed and RAM, but how important are issues like having a large L2 cache on the processor? One last thing. We're looking at getting the server equipment from one of the big vendors (Dell, Micron, etc), but while searching the archives that Del''s PERC RAID controller is not support (or was not) by FreeBSD, any world on when/if it will be? I know that Micron's is support (since Walnut Creek uses it). What are some other hardware RAID solutions available and from which vendors could I get them from? I would really appreciate any information you could provide me. - Ben Schumacher To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Tue Oct 26 19: 5:58 1999 Delivered-To: freebsd-hardware@freebsd.org Received: from rz5.rz.fh-wilhelmshaven.de (rz5.rz.fh-wilhelmshaven.de [139.13.57.132]) by hub.freebsd.org (Postfix) with ESMTP id BA19F152CC for ; Tue, 26 Oct 1999 19:05:50 -0700 (PDT) (envelope-from ohoyer@fbwi.fh-wilhelmshaven.de) Received: from fettesau.stuwo.fh-wilhelmshaven.de (stuwopc5.stuwo.fh-wilhelmshaven.de [139.13.209.5]) by rz5.rz.fh-wilhelmshaven.de (8.8.7/8.8.5) with SMTP id EAA20291; Wed, 27 Oct 1999 04:05:33 +0200 Message-Id: <4.1.19991027034125.00bbad80@mailserv.rz.fh-wilhelmshaven.de> X-Sender: ohoyer@mailserv.rz.fh-wilhelmshaven.de X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1 Date: Wed, 27 Oct 1999 03:59:22 +0200 To: Ben Schumacher From: Olaf Hoyer Subject: Re: FreeBSD Server Hardware Configuration Question. Cc: freebsd-hardware@FreeBSD.ORG In-Reply-To: <4.2.0.58.19991026182732.00989a80@mail.cyalchemy.com> Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >What I need is an idea of a good hardware configuration of (most likely) 2= =20 >machines that would be able to handle this much potential traffic. I've=20 >had a lot of experience with FreeBSD and think that it would be the best=20 >solution for this, running a combination of Apace and MySQL, but I need to= =20 >know what I can do on the hardware side to support it. > >I guess what I really need is a good idea of what is necessary to make=20 >these machines powerful and responsive. I think the best solution for the= =20 >web server would be a powerful P3 Xeon server, using a hardware RAID system= =20 >with at least 1GB of RAM. The database server, on the other hand, I'm a=20 >little more unsure about. I haven't had enough experience with MySQL to=20 >know what keeps to running fast and smooth. I figure that it probably=20 >relies heavily on drive speed and RAM, but how important are issues like=20 >having a large L2 cache on the processor? Hi! Well, I've discussed those server topics on another list already, and we agreed there to the following statements, after also having discussed the famous mindcraft bench Win NT vs Linux. German mag c't also did its own implementation of the test, using practical parameters for it, and did those accordingly to the real load statistic of their own web server. (www.heise.de has approx 100 hits/sec in peak times, on a SUN Enterprise= 450) There is also a link with an english translation, with some nice graphics, doing the same tests with different numbers of CPUs... General statements were (Based on Intel architecture (They had a quad Siemens Primergy) The more static the content is, the less numbers of CPUs are needed You need lots of RAM, because you have numerous handles to deal with. HUge L2 caches are not that bad, also. Only question is, does the added value (price) due to more 2nd level cache corresponds with the performance gain. 1 or 2 ethernet cards are enough (at least under Linux with its TCP/IP stack and SMP handling), they shall be enough. (For fault tolerance or load-balancing, ok- they are cheap nowadays...=20 (That was NTs advantage- to blast enough content out to saturate 4 NICs) Put the journals (database access, logs, transaction files, everything you need to write to another partition/HDD/RAID than that where you have to distribute your contents from. Look at: http://www.heise.de/ct/english/99/13/186-1/ for the comparison between NT/Linux, where some very interesting aspects were evaluated There is no english online version available for their former stress test of their own web-server. IN short, their own Enterprise 450 Dual CPU stands at Xlink in a server farm, and has AFAIR only 1 NIC actually used. They put it into service in March this year, using Solaris 2.6 on it, having 100 hits/sec in peak times. Regards Olaf Hoyer - - - - - - - -=20 Olaf Hoyer ICQ: 22838075 mailto: Olaf.Hoyer@nightfire.de home: www.nightfire.de (The home of the burning CPU) Wer mit Ungeheuern k=E4mpft, mag zusehn,=20 da=DF er nicht dabei zum Ungeheuer wird. Und wenn du lange in einen Abgrund blickst, blickt der Abgrund=20 auch in dich hinein. (Friedrich Nietzsche, Jenseits von Gut und B=F6se) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Tue Oct 26 22: 1:19 1999 Delivered-To: freebsd-hardware@freebsd.org Received: from hera.webcom.com (hera.webcom.com [209.1.28.42]) by hub.freebsd.org (Postfix) with ESMTP id 3860714FD8 for ; Tue, 26 Oct 1999 22:01:13 -0700 (PDT) (envelope-from graeme@echidna.com) Received: from kigal.webcom.com (kigal.webcom.com [209.1.28.57]) by hera.webcom.com (8.9.1/8.9.1) with SMTP id WAA01767; Tue, 26 Oct 1999 22:01:05 -0700 Received: from [204.143.69.31] by inanna.webcom.com (WebCom SMTP 1.2.1) with SMTP id 46123635; Tue Oct 26 21:55 PDT 1999 Message-Id: <3816B124.32D2@echidna.com> Date: Wed, 27 Oct 1999 01:00:36 -0700 From: Graeme Tait Organization: Echidna X-Mailer: Mozilla 2.02 (Win16; I) Mime-Version: 1.0 To: Ben Schumacher Cc: freebsd-hardware@freebsd.org Subject: Re: FreeBSD Server Hardware Configuration Question. References: <4.2.0.58.19991026182732.00989a80@mail.cyalchemy.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Ben Schumacher wrote: > > Hello- > > I am working on a project in my company where we will need to be able to > handle large amounts of traffic on a web server we are setting > up. Basically, we estimate about 75,000 visitors a day with roughly five > 20k page views each, which makes roughly 7.5GB of data a day. Most of the > pages we'll be offering on this site are static, but access to the site > will be need to be verified through a database of say 750,000 customers. Maybe isp or questions is a better forum for this? Leaving aside the database/access verification, I run a site with comparable access parameters (average of 10 hits/second, 7kB/hit, 6GB/day). A PII-400 with 256MB RAM running FreeBSD/Apache does this with both hands tied behind its back (well, at least one hand per daemon). In addition it supports a fair cgi load, runs Glimpse searches of a 130MB file, processes about 15% of hits as SSI, reverse-resolves all accessing IP's on the fly, and processes web logs. With our traffic patterns (worldwide accesses, but dominated by the US), Apache very rarely exceeds 200 children. Memory usage is such that the 130MB file mentioned above is normally cached in RAM - with a bit more RAM, I would expect this to always be the case. (BTW, web server benchmarks that fail to simulate slow client connections are virtually meaningless in relation to typical Internet conditions, especially regarding memory usage.) The network connection is 10Mb ethernet - it rarely saturates for any sustained interval (more than seconds). The web files occupy about 3GB and all reside on one 4.5GB SCSI disk (Seagate Cheetah). Most of the rest of the system, including log files is on a second 4.5GB disk. 85% of accesses involve a small number of images that would be therefore memory-cached. The remaining 15% are to a fairly random selection of files drawn from the 3GB repertoire, so will mostly have to be read from disk. Your disk load would depend a lot on what fraction of accesses could be to cached files. So I don't think your web serving requirements per se are very onerous. A Xeon/Raid for this would probably be overkill. You don't explain what the access verification entails. If it could be implemented by using db-based Apache access controls, I would imagine the above configuration could readily cope with that too. The DB files would probably end up memory-cached, greatly helping performance. > What I need is an idea of a good hardware configuration of (most likely) 2 > machines that would be able to handle this much potential traffic. I've > had a lot of experience with FreeBSD and think that it would be the best > solution for this, running a combination of Apace and MySQL, but I need to > know what I can do on the hardware side to support it. > > I guess what I really need is a good idea of what is necessary to make > these machines powerful and responsive. I think the best solution for the > web server would be a powerful P3 Xeon server, using a hardware RAID system > with at least 1GB of RAM. The database server, on the other hand, I'm a > little more unsure about. I haven't had enough experience with MySQL to > know what keeps to running fast and smooth. I figure that it probably > relies heavily on drive speed and RAM, but how important are issues like > having a large L2 cache on the processor? > > One last thing. We're looking at getting the server equipment from one of > the big vendors (Dell, Micron, etc), but while searching the archives that > Del''s PERC RAID controller is not support (or was not) by FreeBSD, any > world on when/if it will be? I know that Micron's is support (since Walnut > Creek uses it). What are some other hardware RAID solutions available and > from which vendors could I get them from? > > I would really appreciate any information you could provide me. > > - Ben Schumacher > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hardware" in the body of the message -- Graeme Tait - Echidna To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Tue Oct 26 23:12:30 1999 Delivered-To: freebsd-hardware@freebsd.org Received: from dingo.cdrom.com (castles520.castles.com [208.214.165.84]) by hub.freebsd.org (Postfix) with ESMTP id 127AB14CEB for ; Tue, 26 Oct 1999 23:12:24 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.3/8.8.8) with ESMTP id XAA00634; Tue, 26 Oct 1999 23:04:03 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199910270604.XAA00634@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Ben Schumacher Cc: freebsd-hardware@FreeBSD.org Subject: Re: FreeBSD Server Hardware Configuration Question. In-reply-to: Your message of "Tue, 26 Oct 1999 18:48:56 MDT." <4.2.0.58.19991026182732.00989a80@mail.cyalchemy.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 26 Oct 1999 23:04:03 -0700 From: Mike Smith Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > I am working on a project in my company where we will need to be able to > handle large amounts of traffic on a web server we are setting > up. Basically, we estimate about 75,000 visitors a day with roughly five > 20k page views each, which makes roughly 7.5GB of data a day. Most of the > pages we'll be offering on this site are static, but access to the site > will be need to be verified through a database of say 750,000 customers. This is not "large amounts of traffic"; you should be able to do all of this on a single, fairly small system. > I guess what I really need is a good idea of what is necessary to make > these machines powerful and responsive. I think the best solution for the > web server would be a powerful P3 Xeon server, using a hardware RAID system > with at least 1GB of RAM. This would be outrageous overkill. A mid-sized P-II system with a moderate amount of memory (128-256M) should be able to cover all of your page-serving requirements. You should obviously benchmark your implementation, and you'll want to design for peak capacity so you will need to know the likely access patterns for your userbase. But even so, you're talking about less than 0.5M hits a day, which is really loafing. Figure that 75,000 visitors a day averages out to about one every second or so. If they all visit you inside a two-hour period, you'll have to authenticate about ten a second; that's probably a reasonable peak performace figure. You'll want to design your database carefully to keep its performance requirements down; it's not that this is a difficult task, but it's very easy to get database design wrong. You might want to design a custom authentication application for this purpose; do the math for a moment. Assume you allow 16 characters for the username, and 16 more for the authentication token. 32 * 750,000 is a mere 24M to hold the entire database in memory. If you index it aggressively, you'd still be hard-pressed to use more than 32M for the entire process. > The database server, on the other hand, I'm a > little more unsure about. I haven't had enough experience with MySQL to > know what keeps to running fast and smooth. I figure that it probably > relies heavily on drive speed and RAM, but how important are issues like > having a large L2 cache on the processor? For this application; more or less irrelevant. > One last thing. We're looking at getting the server equipment from one of > the big vendors (Dell, Micron, etc), but while searching the archives that > Del''s PERC RAID controller is not support (or was not) by FreeBSD, any > world on when/if it will be? I know that Micron's is support (since Walnut > Creek uses it). What are some other hardware RAID solutions available and > from which vendors could I get them from? Actually, WCarchive uses a Mylex SCSI:SCSI controller (as far as I can tell, Micron don't actually make RAID controllers). I've been working on drivers for a number of the PCI:SCSI RAID controllers (including the PERC and PERC 2/SC), but they're not really ready for general usage yet. Without meaning to rain on your parade here however, it doesn't look like you actually need a "big vendor" solution, nor RAID, nor a 1GB Xeon, nor even two machines to more than admirably handle your application. Buy an economical, compact PII or PIII box from someone nice like Telenet, put a 9GB IBM SCSI drive in it, and make the occasional backup so that if the drive dies (unlikely) you can bring it back up. If you're really paranoid, build two machines and have the second mirror the first. You could even splurge on something like Polyserve's product and run a 2-node redundant cluster and _still_ save money. The cardinal rule, as always, for systems design at this stage: know your requirements, and specify the hardware accordingly. Don't go shopping for what you want to need; you'll either screw yourself by trying too hard to save money, or screw yourself by wasting your money on hardware you'll never need or use. -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Wed Oct 27 0:59:20 1999 Delivered-To: freebsd-hardware@freebsd.org Received: from gwsmtp.thomson-csf.com (gwsmtp.thomson-csf.com [195.101.39.226]) by hub.freebsd.org (Postfix) with ESMTP id 3F29015321; Wed, 27 Oct 1999 00:59:17 -0700 (PDT) (envelope-from jean-philipe.boisseau@sextant.thomson-csf.com) X-Internal-ID: 381462DB00014029 Received: from thomplex.thomson-csf.com (200.3.2.2) by gwsmtp.thomson-csf.com (NPlex 2.0.123); Wed, 27 Oct 1999 10:03:44 +0200 X-Internal-ID: 3815AE2000008FA2 Received: from thomplex.thomson-csf.com (200.3.2.2) by thomplex.thomson-csf.com (NPlex 2.0.124); Wed, 27 Oct 1999 10:01:44 +0200 Received: from 128.1.6.5 by thomplex.thomson-csf.com (InterScan E-Mail VirusWall NT); Wed, 27 Oct 1999 10:01:43 +0200 (Paris, Madrid (heure d'été)) X-Internal-ID: 38142D1F00002855 Received: from sms1.val (128.1.9.254) by vpsms001.sextant.thomson-csf.com (NPlex 2.0.123); Wed, 27 Oct 1999 09:50:33 +0200 Received: from sextant.thomson-csf.com (yussol03.vly) by sms1.val with ESMTP (1.40.112.12/16.2) id AA011251455; Wed, 27 Oct 1999 10:04:15 +0200 Message-Id: <3816B0BB.388315AB@sextant.thomson-csf.com> Date: Wed, 27 Oct 1999 09:58:51 +0200 From: BOISSEAU Jean-Philippe Organization: sextant X-Mailer: Mozilla 4.03 [en] (X11; I; SunOS 5.5.1 sun4u) Mime-Version: 1.0 To: freebsd-hardware@freebsd.org Cc: nsouch@freebsd.org Subject: Tekram DC 395 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi. I'd like to know if there is a work in progress for Tekram DC 395 SCSI card. Thanks Jean-Philippe Boisseau To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Wed Oct 27 19:26:56 1999 Delivered-To: freebsd-hardware@freebsd.org Received: from panzer.kdm.org (panzer.kdm.org [216.160.178.169]) by hub.freebsd.org (Postfix) with ESMTP id 055E514C3B; Wed, 27 Oct 1999 19:26:52 -0700 (PDT) (envelope-from ken@panzer.kdm.org) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id UAA12960; Wed, 27 Oct 1999 20:26:49 -0600 (MDT) (envelope-from ken) Message-Id: <199910280226.UAA12960@panzer.kdm.org> Subject: Re: Tekram DC 395 In-Reply-To: <3816B0BB.388315AB@sextant.thomson-csf.com> from BOISSEAU Jean-Philippe at "Oct 27, 1999 09:58:51 am" To: jean-philipe.boisseau@sextant.thomson-csf.com (BOISSEAU Jean-Philippe) Date: Wed, 27 Oct 1999 20:26:49 -0600 (MDT) Cc: freebsd-hardware@FreeBSD.ORG, nsouch@FreeBSD.ORG, freebsd-scsi@FreeBSD.ORG From: "Kenneth D. Merry" X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org [ CCed to -scsi, as people there might be interested ] BOISSEAU Jean-Philippe wrote... > Hi. > I'd like to know if there is a work in progress for Tekram DC 395 SCSI > card. Actually, Tekram has written a driver for the card. I don't know much about the card or driver, but the driver is available at ftp.tekram.com. I have a slightly newer version (1.06, the version on the ftp site is 1.05) that Erich Chen sent me in early September, but I haven't had a chance to do much with it. In any case, I'd suggest that you first contact Erich Chen , as he is likely to have the latest version of their driver for the TRM-S1040 chip that's on their 395 and 315 boards. If that fails, I can just give you a copy of the driver he sent me. Tekram is to be commended for putting forth the effort to support FreeBSD. They have actually written three different FreeBSD/CAM drivers -- one for their AMD 53c974 boards (the amd driver in the tree is based on that driver), one for their NCR/Symbios boards, and now one for their own SCSI chips. Ken -- Kenneth Merry ken@kdm.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Wed Oct 27 20:43:43 1999 Delivered-To: freebsd-hardware@freebsd.org Received: from alpha.ces.cwru.edu (alpha.CES.CWRU.Edu [129.22.16.10]) by hub.freebsd.org (Postfix) with ESMTP id 5461A15252 for ; Wed, 27 Oct 1999 20:43:30 -0700 (PDT) (envelope-from djc6@eecs.cwru.edu) Received: from akasha (akasha [129.22.16.70]) by alpha.ces.cwru.edu (8.9.1/8.9.1) with ESMTP id XAA02466 for ; Wed, 27 Oct 1999 23:43:27 -0400 (EDT) Date: Wed, 27 Oct 1999 23:43:26 -0400 (EDT) From: David Carlin X-Sender: djc6@akasha.ces.cwru.edu To: freebsd-hardware@freebsd.org Subject: Cyclades driver problem Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hello, I ran into a small problem while getting my Cyclom Ye-16/DB25 to work. In the file /usr/src/sys/i386/isa/cy.c I had to add the line "#define USE_COMLOCK" in order to make my new kernel (FreeBSD 3.3-RELEASE) work. Otherwise, it wouldn't compile - saying that COM_LOCK and COM_UNLOCK were undefine. Is this normal? The board works fine, but it took me a while to figure out. Also, what is this "PollMode" mentioned in cy.c? Should it be enabled for the Ye? Thanks! -David -- David Carlin -- djc6@po.cwru.edu | Unix Administrator, EECS Dept. | Case Western Reserve University | Office: Olin 414 10900 Euclid Ave | Phone: (216) 368-0355 Cleveland, OH 44106-7071 | Fax: (216) 368-6888 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Wed Oct 27 22:15:32 1999 Delivered-To: freebsd-hardware@freebsd.org Received: from jason.argos.org (a13b146.neo.rr.com [204.210.197.146]) by hub.freebsd.org (Postfix) with ESMTP id C317514EC1 for ; Wed, 27 Oct 1999 22:15:24 -0700 (PDT) (envelope-from mike@argos.org) Received: from localhost (mike@localhost) by jason.argos.org (8.9.1/8.9.1) with ESMTP id BAA31838; Thu, 28 Oct 1999 01:15:06 -0400 Date: Thu, 28 Oct 1999 01:15:06 -0400 (EDT) From: Mike Nowlin To: Mike Smith Cc: freebsd-hardware@FreeBSD.ORG Subject: Re: FreeBSD Server Hardware Configuration Question. In-Reply-To: <199910270604.XAA00634@dingo.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > I guess what I really need is a good idea of what is necessary to make > > these machines powerful and responsive. I think the best solution for the > > web server would be a powerful P3 Xeon server, using a hardware RAID system > > with at least 1GB of RAM. > > This would be outrageous overkill. A mid-sized P-II system with a Agreed.... I have a P-II/400 with 256 megs of RAM handling more traffic than this, and it's doing both the HTTP and DB aspects of it. You aren't used to using NT, are you? :) > > The database server, on the other hand, I'm a > > little more unsure about. I haven't had enough experience with MySQL to > > know what keeps to running fast and smooth. I figure that it probably > > relies heavily on drive speed and RAM, but how important are issues like > > having a large L2 cache on the processor? > > For this application; more or less irrelevant. A boatload of memory usually helps... It's amazing the performance increase you get by going from 64 to 96 megs even on a light-to-medium load DB server. I've played around with tweaking both Postgres and MySQL on -stable in different configurations, and (especially on Postgres) adding memory always made a significant improvement -- doing large table sorts and SELECT..WHERE commands can take up large chunks of RAM for very short periods of time -- without it, "may the swapping commence." Unless you're dealing with a 486/25, your best bet is to concentrate on the I/O bandwidth of the drives, and memory. Even a Pentium/200 can be a wonderful DB server if you set it up right. mike To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Thu Oct 28 9:33:19 1999 Delivered-To: freebsd-hardware@freebsd.org Received: from mail.wolves.k12.mo.us (mail.wolves.k12.mo.us [207.160.214.1]) by hub.freebsd.org (Postfix) with ESMTP id 1DEAB14C99; Thu, 28 Oct 1999 09:33:11 -0700 (PDT) (envelope-from cdillon@wolves.k12.mo.us) Received: from mail.wolves.k12.mo.us (cdillon@mail.wolves.k12.mo.us [207.160.214.1]) by mail.wolves.k12.mo.us (8.9.3/8.9.3) with ESMTP id LAA64895; Thu, 28 Oct 1999 11:32:59 -0500 (CDT) (envelope-from cdillon@wolves.k12.mo.us) Date: Thu, 28 Oct 1999 11:32:59 -0500 (CDT) From: Chris Dillon To: "Kenneth D. Merry" Cc: BOISSEAU Jean-Philippe , freebsd-hardware@FreeBSD.ORG, nsouch@FreeBSD.ORG, freebsd-scsi@FreeBSD.ORG Subject: Re: Tekram DC 395 In-Reply-To: <199910280226.UAA12960@panzer.kdm.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Wed, 27 Oct 1999, Kenneth D. Merry wrote: > Tekram is to be commended for putting forth the effort to support FreeBSD. > They have actually written three different FreeBSD/CAM drivers -- one for > their AMD 53c974 boards (the amd driver in the tree is based on that > driver), one for their NCR/Symbios boards, and now one for their own SCSI > chips. I've always been happy with my Tekram DC-390F, which is based on the NCR/Symbios 53c875. I've also got a bunch of Compaq servers with integrated 53c875's which work flawlessly with FreeBSD as well. How do these new chips apparently made by Tekram compare to the Symbios and even Adaptec chips as far as performance and reliability go? If they're at least as good, or better, I'll probably invest in another Tekram card when I decide to get some U2 devices. -- Chris Dillon - cdillon@wolves.k12.mo.us - cdillon@inter-linc.net FreeBSD: The fastest and most stable server OS on the planet. For Intel x86 and Alpha architectures (SPARC under development). ( http://www.freebsd.org ) "One should admire Windows users. It takes a great deal of courage to trust Windows with your data." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Thu Oct 28 10:17:35 1999 Delivered-To: freebsd-hardware@freebsd.org Received: from panzer.kdm.org (panzer.kdm.org [216.160.178.169]) by hub.freebsd.org (Postfix) with ESMTP id 0ADBD14C34; Thu, 28 Oct 1999 10:17:25 -0700 (PDT) (envelope-from ken@panzer.kdm.org) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id LAA17567; Thu, 28 Oct 1999 11:17:18 -0600 (MDT) (envelope-from ken) Message-Id: <199910281717.LAA17567@panzer.kdm.org> Subject: Re: Tekram DC 395 In-Reply-To: from Chris Dillon at "Oct 28, 1999 11:32:59 am" To: cdillon@wolves.k12.mo.us (Chris Dillon) Date: Thu, 28 Oct 1999 11:17:18 -0600 (MDT) Cc: jean-philipe.boisseau@sextant.thomson-csf.com (BOISSEAU Jean-Philippe), freebsd-hardware@FreeBSD.ORG, nsouch@FreeBSD.ORG, freebsd-scsi@FreeBSD.ORG From: "Kenneth D. Merry" X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Chris Dillon wrote... > On Wed, 27 Oct 1999, Kenneth D. Merry wrote: > > > Tekram is to be commended for putting forth the effort to support FreeBSD. > > They have actually written three different FreeBSD/CAM drivers -- one for > > their AMD 53c974 boards (the amd driver in the tree is based on that > > driver), one for their NCR/Symbios boards, and now one for their own SCSI > > chips. > > I've always been happy with my Tekram DC-390F, which is based on the > NCR/Symbios 53c875. I've also got a bunch of Compaq servers with > integrated 53c875's which work flawlessly with FreeBSD as well. How > do these new chips apparently made by Tekram compare to the Symbios > and even Adaptec chips as far as performance and reliability go? If > they're at least as good, or better, I'll probably invest in another > Tekram card when I decide to get some U2 devices. Well, I have no idea how the chips or driver perform. One thing to keep in mind, though, is that either the chip doesn't have a SCSI phase engine, or the driver isn't written to take advantage of it. It does all of its own phase transitions, like the AMD 53c974 and Adaptec 6360 drivers. (They have to.) In any case, their TRM-S1040 chip only does ultra-wide, not Ultra 2. So if you want to do Ultra 2 with a Tekram board, you'll need to get the DC-390U2, and I would recommend using Gerard's sym driver instead of the stock NCR driver. Ken -- Kenneth Merry ken@kdm.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Thu Oct 28 12:58:47 1999 Delivered-To: freebsd-hardware@freebsd.org Received: from front6m.grolier.fr (front6m.grolier.fr [195.36.216.56]) by hub.freebsd.org (Postfix) with ESMTP id 9DC0B14C1F; Thu, 28 Oct 1999 12:58:32 -0700 (PDT) (envelope-from groudier@club-internet.fr) Received: from localhost (ppp-116-190.villette.club-internet.fr [194.158.116.190]) by front6m.grolier.fr (8.9.3/No_Relay+No_Spam_MGC990224) with SMTP id VAA24274; Thu, 28 Oct 1999 21:58:22 +0200 (MET DST) Date: Thu, 28 Oct 1999 22:21:15 +0200 (MET DST) From: Gerard Roudier X-Sender: groudier@localhost To: "Kenneth D. Merry" Cc: BOISSEAU Jean-Philippe , freebsd-hardware@FreeBSD.ORG, nsouch@FreeBSD.ORG, freebsd-scsi@FreeBSD.ORG Subject: Re: Tekram DC 395 In-Reply-To: <199910280226.UAA12960@panzer.kdm.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=ISO-8859-1 Content-Transfer-Encoding: QUOTED-PRINTABLE Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org You must be aware of the following when deciding to buy such a controller: The S1040 has no phase engine, unlike the aic7xxx and the sym53c8xx chips, for example. The means that all phase changes must be handled by the C code. Result is at least 5 (more?) interrupts + some (much?) programmed IOs from the C code for the execution of a each SCSI IO (the chip does DMA for the data).= =20 Basically the design of this chip is similar to the amd53c974. I suggest people to prefer the Tekram Boards based on SYM53C8XX chips that are excellent products for a quite reasonnable price. (DC-390-U/F/U2B/U2W etc ...) G=E9rard. On Wed, 27 Oct 1999, Kenneth D. Merry wrote: > [ CCed to -scsi, as people there might be interested ] >=20 > BOISSEAU Jean-Philippe wrote... > > Hi. > > I'd like to know if there is a work in progress for Tekram DC 395 SCSI > > card. >=20 > Actually, Tekram has written a driver for the card. I don't know much > about the card or driver, but the driver is available at ftp.tekram.com. >=20 > I have a slightly newer version (1.06, the version on the ftp site is 1.0= 5) > that Erich Chen sent me in early September, but I haven't had a chance to > do much with it. >=20 > In any case, I'd suggest that you first contact Erich Chen > , as he is likely to have the latest version of thei= r > driver for the TRM-S1040 chip that's on their 395 and 315 boards. If tha= t > fails, I can just give you a copy of the driver he sent me. >=20 > Tekram is to be commended for putting forth the effort to support FreeBSD= =2E > They have actually written three different FreeBSD/CAM drivers -- one for > their AMD 53c974 boards (the amd driver in the tree is based on that > driver), one for their NCR/Symbios boards, and now one for their own SCSI > chips. >=20 > Ken > --=20 > Kenneth Merry > ken@kdm.org >=20 >=20 > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-scsi" in the body of the message >=20 >=20 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Thu Oct 28 20:56:40 1999 Delivered-To: freebsd-hardware@freebsd.org Received: from mailman.zeta.org.au (mailman.zeta.org.au [203.26.10.16]) by hub.freebsd.org (Postfix) with ESMTP id 7FEE915509 for ; Thu, 28 Oct 1999 20:56:34 -0700 (PDT) (envelope-from bde@zeta.org.au) Received: from p54-ts5.syd2.zeta.org.au (beefcake.zeta.org.au [203.26.10.12]) by mailman.zeta.org.au (8.8.7/8.8.7) with ESMTP id OAA28420; Fri, 29 Oct 1999 14:00:47 +1000 Date: Fri, 29 Oct 1999 13:56:12 +1000 (EST) From: Bruce Evans X-Sender: bde@alphplex.bde.org To: David Carlin Cc: freebsd-hardware@FreeBSD.ORG Subject: Re: Cyclades driver problem In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Wed, 27 Oct 1999, David Carlin wrote: > Hello, > I ran into a small problem while getting my Cyclom Ye-16/DB25 to > work. In the file /usr/src/sys/i386/isa/cy.c I had to add the line > "#define USE_COMLOCK" in order to make my new kernel (FreeBSD 3.3-RELEASE) > work. Otherwise, it wouldn't compile - saying that COM_LOCK and > COM_UNLOCK were undefine. Is this normal? The board works fine, but it > took me a while to figure out. No, this isn't normal. USE_COMLOCK is an internal SMP definition. It is normally set appropriately in . > Also, what is this "PollMode" mentioned in cy.c? Should it be enabled for > the Ye? As mentioned in cy.c, it is for so-called polled mode which is required for all cards that don't connect the cd1400's hardware svcack lines, in particular for all Cyclades cards except for some old ones. It is enabled by default for all cards. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Fri Oct 29 6:31:12 1999 Delivered-To: freebsd-hardware@freebsd.org Received: from news-ma.rhein-neckar.de (news-ma.rhein-neckar.de [193.197.90.3]) by hub.freebsd.org (Postfix) with ESMTP id 83369155A5 for ; Fri, 29 Oct 1999 06:31:09 -0700 (PDT) (envelope-from daemon@bigeye.rhein-neckar.de) Received: from bigeye.rhein-neckar.de (uucp@localhost) by news-ma.rhein-neckar.de (8.8.8/8.8.8) with bsmtp id PAA02820 for freebsd-hardware@freebsd.org; Fri, 29 Oct 1999 15:31:09 +0200 (CEST) (envelope-from daemon@bigeye.rhein-neckar.de) Received: (from daemon@localhost) by bigeye.rhein-neckar.de (8.9.3/8.9.3) id NAA28937 for freebsd-hardware@freebsd.org; Fri, 29 Oct 1999 13:20:43 +0200 (CEST) (envelope-from daemon) From: naddy@mips.rhein-neckar.de (Christian Weisgerber) Subject: IDT WinChip? Date: 29 Oct 1999 13:20:42 +0200 Message-ID: <7vbvua$s7r$1@bigeye.rhein-neckar.de> To: freebsd-hardware@freebsd.org Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Is anybody successfully running an IDT WinChip in an old Pentium board? Configuration: CPU: IDT "WinChip" W2A-233 Board: Asus P55TP4N, BIOS rev. 0302 (latest) OS: FreeBSD 4.0-CURRENT (Oct 26), "cpu I586_CPU" Problem: The system crashes very quickly on its way to multi-user or soon thereafter. "Page fault while in kernel mode". Crashes seem to relate to disk activity, and occur typically in file system related calls such as open(). No overheating. The same system is solid with a Intel Pentium-100 CPU. -- Christian "naddy" Weisgerber naddy@mips.rhein-neckar.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Fri Oct 29 7:33:44 1999 Delivered-To: freebsd-hardware@freebsd.org Received: from rz5.rz.fh-wilhelmshaven.de (rz5.rz.fh-wilhelmshaven.de [139.13.57.132]) by hub.freebsd.org (Postfix) with ESMTP id DEA97150C8 for ; Fri, 29 Oct 1999 07:33:35 -0700 (PDT) (envelope-from ohoyer@fbwi.fh-wilhelmshaven.de) Received: from fettesau.stuwo.fh-wilhelmshaven.de (stuwopc5.stuwo.fh-wilhelmshaven.de [139.13.209.5]) by rz5.rz.fh-wilhelmshaven.de (8.8.7/8.8.5) with SMTP id QAA29321; Fri, 29 Oct 1999 16:33:23 +0200 Message-Id: <4.1.19991029162608.00bcab70@mailserv.rz.fh-wilhelmshaven.de> X-Sender: ohoyer@mailserv.rz.fh-wilhelmshaven.de X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1 Date: Fri, 29 Oct 1999 16:32:33 +0200 To: naddy@mips.rhein-neckar.de (Christian Weisgerber) From: Olaf Hoyer Subject: Re: IDT WinChip? Cc: freebsd-hardware@FreeBSD.ORG In-Reply-To: <7vbvua$s7r$1@bigeye.rhein-neckar.de> Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org At 13:20 29.10.99 +0200, you wrote: >Is anybody successfully running an IDT WinChip in an old Pentium board? > >Configuration: >CPU: IDT "WinChip" W2A-233 >Board: Asus P55TP4N, BIOS rev. 0302 (latest) >OS: FreeBSD 4.0-CURRENT (Oct 26), "cpu I586_CPU" > >Problem: >The system crashes very quickly on its way to multi-user or soon >thereafter. "Page fault while in kernel mode". Crashes seem to >relate to disk activity, and occur typically in file system related >calls such as open(). No overheating. The same system is solid with >a Intel Pentium-100 CPU. > HI! Well, I ran the old version of the C6 with 180 Mhz in an crappy PCChips-Board 3 months under Windoze NTwithout any probs The chips should have been certified also under several Unices for operation. Also the Asus board is know for some stability, I also put together some boxes with that board. Thermal issues are non-important (at least the old Winchip was able to run 2*50 MHZ=3D100 MHz) without any cooler without probs... It is imaginable that some power-saving code in -current does not work properly with the IDTs Or that the bus speed is too high and out of spec. (some series needed to do 75*3, like Cyrix) Possibly other problem could be the 1st level cache, which is a bit bigger and different organized than that from a Intel chip. Regards Olaf Hoyer P.S. Private Mail in german welcome... - - - - - - - -=20 Olaf Hoyer ICQ: 22838075 mailto: Olaf.Hoyer@nightfire.de home: www.nightfire.de (The home of the burning CPU) Wer mit Ungeheuern k=E4mpft, mag zusehn,=20 da=DF er nicht dabei zum Ungeheuer wird. Und wenn du lange in einen Abgrund blickst, blickt der Abgrund=20 auch in dich hinein. (Friedrich Nietzsche, Jenseits von Gut und B=F6se) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Fri Oct 29 16: 0:22 1999 Delivered-To: freebsd-hardware@freebsd.org Received: from schooner.svjava.com (schooner.svjava.com [204.75.228.3]) by hub.freebsd.org (Postfix) with ESMTP id 166161510C for ; Fri, 29 Oct 1999 16:00:17 -0700 (PDT) (envelope-from kozowski@svjava.com) Received: (from kozowski@localhost) by schooner.svjava.com (8.9.1a/svjava.com) id QAA19407; Fri, 29 Oct 1999 16:00:13 -0700 (PDT) Date: Fri, 29 Oct 1999 16:00:13 -0700 From: Eric Kozowski To: Olaf Hoyer Cc: freebsd-hardware@FreeBSD.ORG Subject: Re: problems installing 3.3 Message-ID: <19991029160013.A19360@schooner.svjava.com> References: <19991021231842.D25786@schooner.svjava.com> <4.1.19991022095543.00baf850@mailserv.rz.fh-wilhelmshaven.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.7i In-Reply-To: <4.1.19991022095543.00baf850@mailserv.rz.fh-wilhelmshaven.de> Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Fri, Oct 22, 1999 at 09:59:06AM +0200, Olaf Hoyer wrote: > At 23:18 21.10.99 -0700, you wrote: > > > >i'm having difficulty installing 3.3 on the following system: > > > >amptron 3100B motherboard > > Amptron is another name for PCCHips mainboards, like Alton, Eurone, Hsing > Tech... > > IMO, based on some bitter experiences, they range from cheap to crap. > In field service, seen lots of them making stress... > Well, just a theory. will be happy seeing other guys pointing other solution. replacing the mb w/ a tyan tsunami fixed the problem. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Fri Oct 29 16:12:21 1999 Delivered-To: freebsd-hardware@freebsd.org Received: from schooner.svjava.com (schooner.svjava.com [204.75.228.3]) by hub.freebsd.org (Postfix) with ESMTP id EB50415549 for ; Fri, 29 Oct 1999 16:12:15 -0700 (PDT) (envelope-from kozowski@svjava.com) Received: (from kozowski@localhost) by schooner.svjava.com (8.9.1a/svjava.com) id QAA19530 for freebsd-hardware@FreeBSD.ORG; Fri, 29 Oct 1999 16:12:15 -0700 (PDT) Date: Fri, 29 Oct 1999 16:12:15 -0700 From: Eric Kozowski To: freebsd-hardware@FreeBSD.ORG Subject: problems getting pcm0 to work Message-ID: <19991029161215.A19492@schooner.svjava.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.7i Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org i'm having problems getting pcm0 to find my sb 64 awe in freebsd 3.3. i have the following in my kernel config: device pcm0 at isa? port ? tty irq ? drq 1 flags 0x15 pnpinfo has the following to say: Card assigned CSN #1 Vendor ID CTL00e4 (0xe4008c0e), Serial Number 0x0029071c PnP Version 1.0, Vendor Version 16 Device Description: Creative SB AWE64 PnP *** Small Vendor Tag Detected Logical Device ID: CTL0045 0x45008c0e #0 Device Description: Audio TAG Start DF Good Configuration IRQ: 5 - only one type (true/edge) DMA: channel(s) 1 8-bit, not a bus master, count by byte, , Compatibility mode DMA: channel(s) 5 16-bit, not a bus master, , count by word, Compatibility mode I/O Range 0x220 .. 0x220, alignment 0x1, len 0x10 [16-bit addr] I/O Range 0x330 .. 0x330, alignment 0x1, len 0x2 [16-bit addr] I/O Range 0x388 .. 0x388, alignment 0x1, len 0x4 [16-bit addr] Logical Device ID: CTL0022 0x22008c0e #2 Device Description: WaveTable TAG Start DF Good Configuration I/O Range 0x620 .. 0x620, alignment 0x1, len 0x4 [16-bit addr] TAG Start DF Acceptable Configuration I/O Range 0x620 .. 0x680, alignment 0x20, len 0x4 [16-bit addr] TAG End DF *** Small Vendor Tag Detected End Tag Successfully got 69 resources, 3 logical fdevs -- card select # 0x0001 CSN CTL00e4 (0xe4008c0e), Serial Number 0x0029071c Logical device #0 IO: 0x0000 0x0000 0x0000 0x0000 0x0000 0x0000 0x0000 0x0000 IRQ 0 0 DMA 4 4 IO range check 0x00 activate 0x00 Logical device #1 IO: 0x0000 0x0000 0x0000 0x0000 0x0000 0x0000 0x0000 0x0000 IRQ 0 0 DMA 4 4 IO range check 0x00 activate 0x00 Logical device #2 IO: 0x0000 0x0000 0x0000 0x0000 0x0000 0x0000 0x0000 0x0000 IRQ 0 0 DMA 4 4 IO range check 0x00 activate 0x00 bootup shows: Probing for PnP devices: CSN 1 Vendor ID: CTL00e4 [0xe4008c0e] Serial 0x0029071c Comp ID: PNPb02f [0x2fb0d041] This is a SB16 PnP, but LDN 0 is disabled pcm0 not found anyone have any ideas? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Sat Oct 30 6: 9:31 1999 Delivered-To: freebsd-hardware@freebsd.org Received: from polaris.we.lc.ehu.es (polaris.we.lc.ehu.es [158.227.6.43]) by hub.freebsd.org (Postfix) with ESMTP id ED2AD14C8C for ; Sat, 30 Oct 1999 06:09:20 -0700 (PDT) (envelope-from jose@we.lc.ehu.es) Received: from we.lc.ehu.es (lxpx83.lx.ehu.es [158.227.99.83]) by polaris.we.lc.ehu.es (8.9.1/8.9.1) with ESMTP id PAA20399; Sat, 30 Oct 1999 15:09:07 +0200 (MET DST) Message-ID: <381AEDF2.1A57E202@we.lc.ehu.es> Date: Sat, 30 Oct 1999 15:09:06 +0200 From: "Jose M. Alcaide" Organization: Universidad del =?iso-8859-1?Q?Pa=EDs?= Vasco - Dept. de Electricidad y =?iso-8859-1?Q?Electr=F3nica?= X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 3.3-RELEASE i386) X-Accept-Language: es-ES, es, en-US, en MIME-Version: 1.0 To: Eric Kozowski Cc: freebsd-hardware@FreeBSD.ORG Subject: Re: problems getting pcm0 to work References: <19991029161215.A19492@schooner.svjava.com> Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Eric Kozowski wrote: > > i'm having problems getting pcm0 to find my sb 64 awe in freebsd 3.3. > > i have the following in my kernel config: > > device pcm0 at isa? port ? tty irq ? drq 1 flags 0x15 > > [SNIP] > > bootup shows: > > Probing for PnP devices: > CSN 1 Vendor ID: CTL00e4 [0xe4008c0e] Serial 0x0029071c Comp ID: PNPb02f [0x2fb0d041] > This is a SB16 PnP, but LDN 0 is disabled > > pcm0 not found > Your machine's BIOS does not initalize the PnP sound card. This is a well known problem with some BIOSes, and there is an easy solution: 1. reboot your system passing the "-c" option to the kernel, in order to enter the kernel configuration mode. 2. type this command: pnp 1 0 os enable port0 0x220 port1 0x330 port2 0x388 irq0 5 drq0 1 drq1 5 3. quit confifuration mode, and check whether your card is now detected. If it is, create a file "/boot/kernel.conf" containing the pnp command shown above, and create another file named "/boot/loader.conf" containing the line userconfig_script_load="YES" In this way, your PnP sound card will be automagically configured every time you boot your system up. Hoping this helps, -- JMA ----------------------------------------------------------------------- José Mª Alcaide | mailto:jose@we.lc.ehu.es Universidad del País Vasco | mailto:jmas@FreeBSD.ORG Dpto. de Electricidad y Electrónica | http://www.we.lc.ehu.es/~jose Facultad de Ciencias - Campus de Lejona | Tel.: +34-946012479 48940 Lejona (Vizcaya) - SPAIN | Fax: +34-946013071 ----------------------------------------------------------------------- "Beware of Programmers who carry screwdrivers" -- Leonard Brandwein To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Sat Oct 30 10:39:42 1999 Delivered-To: freebsd-hardware@freebsd.org Received: from rz5.rz.fh-wilhelmshaven.de (rz5.rz.fh-wilhelmshaven.de [139.13.57.132]) by hub.freebsd.org (Postfix) with ESMTP id E858714D8C for ; Sat, 30 Oct 1999 10:39:38 -0700 (PDT) (envelope-from ohoyer@fbwi.fh-wilhelmshaven.de) Received: from fettesau.stuwo.fh-wilhelmshaven.de (stuwopc5.stuwo.fh-wilhelmshaven.de [139.13.209.5]) by rz5.rz.fh-wilhelmshaven.de (8.8.7/8.8.5) with SMTP id TAA28490 for ; Sat, 30 Oct 1999 19:39:33 +0200 Message-Id: <4.1.19991030193252.00bc6310@mailserv.rz.fh-wilhelmshaven.de> X-Sender: ohoyer@mailserv.rz.fh-wilhelmshaven.de X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1 Date: Sat, 30 Oct 1999 19:37:24 +0200 To: freebsd-hardware@FreeBSD.ORG From: Olaf Hoyer Subject: Re: problems getting pcm0 to work In-Reply-To: <19991029161215.A19492@schooner.svjava.com> Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org At 16:12 29.10.99 -0700, you wrote: > >i'm having problems getting pcm0 to find my sb 64 awe in freebsd 3.3. > >i have the following in my kernel config: > >device pcm0 at isa? port ? tty irq ? drq 1 flags 0x15 > >bootup shows: > >Probing for PnP devices: >CSN 1 Vendor ID: CTL00e4 [0xe4008c0e] Serial 0x0029071c Comp ID: PNPb02f=20 >[0x2fb0d041] >This is a SB16 PnP, but LDN 0 is disabled Hi! Well, the SB 64 has a structure which is a bit different to that of the "old" cards like SB16 and SB16 pnp. Even under Windoze 95, there are certain problems on several mobos So I suspect that the driver simply has its difficulties. Make sure that in BIOS the IRQs are routed correctly. Also, as there should be some Intel ICU utility (on CD ), you should be able to set the card in a "jumperless mode" and make configs by hand from a DOS boot disk, then enter the values manually. Regards Olaf Hoyer - - - - - - - -=20 Olaf Hoyer ICQ: 22838075 mailto: Olaf.Hoyer@nightfire.de home: www.nightfire.de (The home of the burning CPU) Wer mit Ungeheuern k=E4mpft, mag zusehn,=20 da=DF er nicht dabei zum Ungeheuer wird. Und wenn du lange in einen Abgrund blickst, blickt der Abgrund=20 auch in dich hinein. (Friedrich Nietzsche, Jenseits von Gut und B=F6se) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Sat Oct 30 15:43:58 1999 Delivered-To: freebsd-hardware@freebsd.org Received: from dialup124.zpr.uni-koeln.de (1-198.K.dial.o-tel-o.net [212.144.1.198]) by hub.freebsd.org (Postfix) with ESMTP id 4AE8D14D7D; Sat, 30 Oct 1999 15:43:45 -0700 (PDT) (envelope-from se@zpr.uni-koeln.de) Received: by dialup124.zpr.uni-koeln.de (Postfix, from userid 200) id 24667D8A; Sun, 31 Oct 1999 00:35:04 +0200 (CEST) Date: Sun, 31 Oct 1999 00:35:04 +0200 From: Stefan Esser To: Christian Weisgerber Cc: freebsd-hardware@FreeBSD.ORG, Stefan Esser Subject: Re: IDT WinChip? Message-ID: <19991031003504.C978@dialup124.zpr.uni-koeln.de> Reply-To: se@freebsd.org References: <7vbvua$s7r$1@bigeye.rhein-neckar.de> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Mailer: Mutt 0.95.6i In-Reply-To: <7vbvua$s7r$1@bigeye.rhein-neckar.de>; from Christian Weisgerber on Fri, Oct 29, 1999 at 01:20:42PM +0200 Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On 1999-10-29 13:20 +0200, Christian Weisgerber wrote: > Is anybody successfully running an IDT WinChip in an old Pentium board? > > Configuration: > CPU: IDT "WinChip" W2A-233 > Board: Asus P55TP4N, BIOS rev. 0302 (latest) > OS: FreeBSD 4.0-CURRENT (Oct 26), "cpu I586_CPU" > > Problem: > The system crashes very quickly on its way to multi-user or soon > thereafter. "Page fault while in kernel mode". Crashes seem to > relate to disk activity, and occur typically in file system related > calls such as open(). No overheating. The same system is solid with > a Intel Pentium-100 CPU. Yes, I have some 10 old systems (original IBM which came with P5/75s) and they run just fine with W2/240s for one year already. The voltage regulator on your ASUS board should be able to supply the current needed by the W2A, so that shouldn't be the problem ... FreeBSD definitely runs well on Winchip CPUs. I have used my boxes to saturate large ATM backbone switches during load tests ;-) Gruß, STefan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Sat Oct 30 20:28:28 1999 Delivered-To: freebsd-hardware@freebsd.org Received: from schooner.svjava.com (schooner.svjava.com [204.75.228.3]) by hub.freebsd.org (Postfix) with ESMTP id 771A114CC2 for ; Sat, 30 Oct 1999 20:28:24 -0700 (PDT) (envelope-from kozowski@svjava.com) Received: (from kozowski@localhost) by schooner.svjava.com (8.9.1a/svjava.com) id UAA29077; Sat, 30 Oct 1999 20:28:20 -0700 (PDT) Date: Sat, 30 Oct 1999 20:28:20 -0700 From: Eric Kozowski To: "Jose M. Alcaide" Cc: freebsd-hardware@FreeBSD.ORG Subject: Re: problems getting pcm0 to work Message-ID: <19991030202820.A29047@schooner.svjava.com> References: <19991029161215.A19492@schooner.svjava.com> <381AEDF2.1A57E202@we.lc.ehu.es> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.7i In-Reply-To: <381AEDF2.1A57E202@we.lc.ehu.es> Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Sat, Oct 30, 1999 at 03:09:06PM +0200, Jose M. Alcaide wrote: > Your machine's BIOS does not initalize the PnP sound card. This is > a well known problem with some BIOSes, and there is an easy solution: > > 1. reboot your system passing the "-c" option to the kernel, in order to > enter the kernel configuration mode. > > 2. type this command: > > pnp 1 0 os enable port0 0x220 port1 0x330 port2 0x388 irq0 5 drq0 1 drq1 5 > > 3. quit confifuration mode, and check whether your card is now detected. > > If it is, create a file "/boot/kernel.conf" containing the pnp command > shown above, and create another file named "/boot/loader.conf" containing > the line > userconfig_script_load="YES" > > In this way, your PnP sound card will be automagically configured > every time you boot your system up. > that did the trick! thanks! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message