From owner-freebsd-hardware Mon Apr 24 13: 9:55 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from lmail.actcom.co.il (lmail.actcom.co.il [192.114.47.13]) by hub.freebsd.org (Postfix) with ESMTP id CE25337BBA2 for ; Mon, 24 Apr 2000 13:09:45 -0700 (PDT) (envelope-from tale@cybertel.co.il) Received: from tale (i0-13.haifa4.actcom.co.il [192.114.80.202]) by lmail.actcom.co.il (8.9.3/8.9.1) with SMTP id XAA25978 for ; Mon, 24 Apr 2000 23:10:12 +0300 From: "Tal S Eilon" To: Subject: Slow Dell PowerEdge 1300 with FreeBSD 3.4 Date: Mon, 24 Apr 2000 23:07:40 +0200 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="windows-1255" 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) X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Importance: Normal Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi all I Just installed my Dell PowerEdge 1300 P-III/500 + 512MB RAM + 8Gb UW-SCSI Drive but I experienced several problems: 1. The system did not detect my Adaptec SCSI Card which I use for my backup tape, so I had to remove it or it would not boot at all 2. After booting and intalling the system, it did not recognize my 512MB but only 64MB + it is working extremly SLOW. I tried recompiling the kernel with MAXMEM of 512MB but with no success since the system is too slow to compile. So now I am very confused about what I should do next? any ideas would be very welcome... Tal S. Eilon Unix System Administrator Cybertel Ltd. -- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Tue Apr 25 2:51:25 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from mail.surf1.de (mail.Surf1.de [194.25.165.21]) by hub.freebsd.org (Postfix) with ESMTP id 39A2A37BC70 for ; Tue, 25 Apr 2000 02:51:21 -0700 (PDT) (envelope-from alex@cichlids.com) Received: from cichlids.com (p3E9C1137.dip0.t-ipconnect.de [62.156.17.55]) by mail.surf1.de (8.9.3/8.9.3) with ESMTP id KAA31578; Tue, 25 Apr 2000 10:49:51 +0200 Received: from cichlids.cichlids.com (cichlids.cichlids.com [192.168.0.10]) by cichlids.com (Postfix) with ESMTP id 55A38AC2C; Tue, 25 Apr 2000 11:54:04 +0200 (CEST) Received: (from alex@localhost) by cichlids.cichlids.com (8.9.3/8.9.3) id LAA02032; Tue, 25 Apr 2000 11:50:07 +0200 (CEST) (envelope-from alex) Date: Tue, 25 Apr 2000 11:50:07 +0200 From: Alexander Langer To: Tal S Eilon Cc: freebsd-hardware@FreeBSD.ORG Subject: Re: Slow Dell PowerEdge 1300 with FreeBSD 3.4 Message-ID: <20000425115007.A1952@cichlids.cichlids.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: ; from tale@cybertel.co.il on Mon, Apr 24, 2000 at 11:07:40PM +0200 X-PGP-Fingerprint: 44 28 CA 4C 46 5B D3 A8 A8 E3 BA F3 4E 60 7D 7F X-Verwirrung: Dieser Header dient der allgemeinen Verwirrung. Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Thus spake Tal S Eilon (tale@cybertel.co.il): > 1. The system did not detect my Adaptec SCSI Card which I use for my > backup tape, so I had to remove it or it would not boot at all ^^^^^^^^^^^^^^^^^^^^^^ Why? > with MAXMEM of 512MB but with no success since the system is too slow to > compile. Too slow to compile? That is a joke. Try it again. > So now I am very confused about what I should do next? any ideas would be > very welcome... compile the kernel with MAXMEM. Alex -- I need a new ~/.sig. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Tue Apr 25 4:40:14 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from lmail.actcom.co.il (lmail.actcom.co.il [192.114.47.13]) by hub.freebsd.org (Postfix) with ESMTP id 9DCE437BD19 for ; Tue, 25 Apr 2000 04:40:10 -0700 (PDT) (envelope-from tale@cybertel.co.il) Received: from tale (i1-7.haifa6.actcom.co.il [192.114.82.187]) by lmail.actcom.co.il (8.9.3/8.9.1) with SMTP id OAA21308; Tue, 25 Apr 2000 14:40:21 +0300 From: "Tal S Eilon" To: "Alexander Langer" Cc: Subject: RE: Slow Dell PowerEdge 1300 with FreeBSD 3.4 Date: Tue, 25 Apr 2000 14:37:33 +0200 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) X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Importance: Normal In-Reply-To: <20000425115007.A1952@cichlids.cichlids.com> Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I compiled it as you said and it took 13 hours to recompile the new kernel. Now it does recognize 512MB of RAM but still processing everything dead slow. It took me close to 25min to compile tcsh-6.09.00, this is not a joke! Maybe this can help? -- Copyright (c) 1992-1999 FreeBSD Inc. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 3.4-RELEASE #0: Tue Apr 25 02:23:41 GMT 2000 root@bell.superbanner.net:/usr/src/sys/compile/BELL Timecounter "i8254" frequency 1193182 Hz CPU: Pentium III (498.48-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x673 Stepping = 3 Features=0x383fbff> real memory = 536870912 (524288K bytes) avail memory = 519454720 (507280K bytes) -- --Tal -----Original Message----- From: owner-freebsd-hardware@FreeBSD.ORG [mailto:owner-freebsd-hardware@FreeBSD.ORG]On Behalf Of Alexander Langer Sent: Tuesday, April 25, 2000 11:50 AM To: Tal S Eilon Cc: freebsd-hardware@FreeBSD.ORG Subject: Re: Slow Dell PowerEdge 1300 with FreeBSD 3.4 Thus spake Tal S Eilon (tale@cybertel.co.il): > 1. The system did not detect my Adaptec SCSI Card which I use for my > backup tape, so I had to remove it or it would not boot at all ^^^^^^^^^^^^^^^^^^^^^^ Why? > with MAXMEM of 512MB but with no success since the system is too slow to > compile. Too slow to compile? That is a joke. Try it again. > So now I am very confused about what I should do next? any ideas would be > very welcome... compile the kernel with MAXMEM. Alex -- I need a new ~/.sig. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Tue Apr 25 5:13: 2 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from mail.surf1.de (mail.Surf1.de [194.25.165.21]) by hub.freebsd.org (Postfix) with ESMTP id E16FB37B6DD for ; Tue, 25 Apr 2000 05:12:48 -0700 (PDT) (envelope-from alex@cichlids.com) Received: from cichlids.com (p3E9C1137.dip0.t-ipconnect.de [62.156.17.55]) by mail.surf1.de (8.9.3/8.9.3) with ESMTP id NAA29764; Tue, 25 Apr 2000 13:11:26 +0200 Received: from cichlids.cichlids.com (cichlids.cichlids.com [192.168.0.10]) by cichlids.com (Postfix) with ESMTP id 087A8AC2C; Tue, 25 Apr 2000 14:15:58 +0200 (CEST) Received: (from alex@localhost) by cichlids.cichlids.com (8.9.3/8.9.3) id OAA07812; Tue, 25 Apr 2000 14:12:10 +0200 (CEST) (envelope-from alex) Date: Tue, 25 Apr 2000 14:12:10 +0200 From: Alexander Langer To: Tal S Eilon Cc: freebsd-hardware@FreeBSD.ORG Subject: Re: Slow Dell PowerEdge 1300 with FreeBSD 3.4 Message-ID: <20000425141210.A7779@cichlids.cichlids.com> References: <20000425115007.A1952@cichlids.cichlids.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: ; from tale@cybertel.co.il on Tue, Apr 25, 2000 at 02:37:33PM +0200 X-PGP-Fingerprint: 44 28 CA 4C 46 5B D3 A8 A8 E3 BA F3 4E 60 7D 7F X-Verwirrung: Dieser Header dient der allgemeinen Verwirrung. Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Thus spake Tal S Eilon (tale@cybertel.co.il): > It took me close to 25min to compile tcsh-6.09.00, this is not a joke! Uh. Bad. > Maybe this can help? Hmm. Is it that slow only for FreeBSD or also for Windows? I remember that I have once modified my BIOS settings somehow and then everything was completely fucked up, i.e. damn slow, as your one is. could that be? Alex -- I need a new ~/.sig. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Tue Apr 25 5:40:56 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from lmail.actcom.co.il (lmail.actcom.co.il [192.114.47.13]) by hub.freebsd.org (Postfix) with ESMTP id 9951837B851 for ; Tue, 25 Apr 2000 05:40:52 -0700 (PDT) (envelope-from tale@cybertel.co.il) Received: from tale (i1-7.haifa6.actcom.co.il [192.114.82.187]) by lmail.actcom.co.il (8.9.3/8.9.1) with SMTP id PAA27560; Tue, 25 Apr 2000 15:41:13 +0300 From: "Tal S Eilon" To: "Alexander Langer" Cc: Subject: RE: Slow Dell PowerEdge 1300 with FreeBSD 3.4 Date: Tue, 25 Apr 2000 15:38:21 +0200 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) X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Importance: Normal In-Reply-To: <20000425141210.A7779@cichlids.cichlids.com> Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Changes in system bios CPU Speed from "Automatic" to "500Mhz" and... IT WORKS!! THANKS!!!!!! the system is blazing fast now! --Tal -----Original Message----- From: owner-freebsd-hardware@FreeBSD.ORG [mailto:owner-freebsd-hardware@FreeBSD.ORG]On Behalf Of Alexander Langer Sent: Tuesday, April 25, 2000 2:12 PM To: Tal S Eilon Cc: freebsd-hardware@FreeBSD.ORG Subject: Re: Slow Dell PowerEdge 1300 with FreeBSD 3.4 Thus spake Tal S Eilon (tale@cybertel.co.il): > It took me close to 25min to compile tcsh-6.09.00, this is not a joke! Uh. Bad. > Maybe this can help? Hmm. Is it that slow only for FreeBSD or also for Windows? I remember that I have once modified my BIOS settings somehow and then everything was completely fucked up, i.e. damn slow, as your one is. could that be? Alex -- I need a new ~/.sig. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Tue Apr 25 6:39:10 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from mail.cytag.nl (node08dc.a2000.nl [62.108.8.220]) by hub.freebsd.org (Postfix) with ESMTP id 7A41737B5A1 for ; Tue, 25 Apr 2000 06:39:07 -0700 (PDT) (envelope-from aristide@lionking.org) Received: from vjr [200.23.87.221] by mail.cytag.nl with ESMTP (SMTPD32-5.05) id AF59ACAB0146; Tue, 25 Apr 2000 15:36:25 +0200 Message-ID: <014501bfaeba$3eaf7720$100000c0@lionking.org> From: "Aristide Aragon" To: Subject: Future Domain 850 MEX card Date: Tue, 25 Apr 2000 08:29:05 -0500 X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2919.6600 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600 Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hello I have a Future domain 850 SCSI controller that I want to use with a scanner (Mikrotek ScanMaker II). The handbook says this card was supported by the old interface and that it's not by the new one. I downloaded the 2.2.8 and 2.2.7 floppies to install them, but at the kernel configuration screen I get after booting I can't find it, it's not there. Does somebody know what version of FreeBSD supports this controller? Thanks in advance Aristide Aragon PS.- Is there an explanation for a mailserver returning my mails to FreeBSD.ORG and not to freebsd.org? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Tue Apr 25 12:31: 6 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from postfix3.free.fr (postfix3.free.fr [212.27.32.22]) by hub.freebsd.org (Postfix) with ESMTP id C1D2A37BDA9; Tue, 25 Apr 2000 12:31:02 -0700 (PDT) (envelope-from stephane@libertysurf.fr) Received: from sequoia.mondomaineamoi.megalo (unknown [213.228.8.149]) by postfix3.free.fr (Postfix) with ESMTP id 46E6386CF0; Tue, 25 Apr 2000 21:30:58 +0200 (CEST) Received: (from stephane@localhost) by sequoia.mondomaineamoi.megalo (8.9.3/8.9.3) id VAA04238; Tue, 25 Apr 2000 21:28:31 +0200 (CEST) (envelope-from stephane) From: Stephane Legrand MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14597.61918.896873.20089@sequoia.mondomaineamoi.megalo> Date: Tue, 25 Apr 2000 21:28:30 +0200 (CEST) To: Mike Smith Cc: Stephane Legrand , freebsd-hardware@freebsd.org Subject: Re: Boot problem with AcceleRAID 150 (was VALinux FullOn 2x2 with FreeBSD) In-Reply-To: <200004212119.OAA00572@mass.cdrom.com> References: <14592.47374.389569.324252@sequoia.mondomaineamoi.megalo> <200004212119.OAA00572@mass.cdrom.com> X-Mailer: VM 6.72 under 21.1 (patch 9) "Canyonlands" XEmacs Lucid Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Mike Smith writes: > > > Four slices on the first logical disk (one for /, one for swap, one > > for /usr and one for /var). Obviously, no slices and no partitions on > > the second logical disk of ~ 20 Gb. > > Ah. I think that explains why there are four entries in the boot > selector - you do realise that you only need to create _one_ slice, and > then divvy it up using partitions later? > Yes :) > > > > We finally received these servers and tried to install a 4.0-release > > > > (CD-Rom version) on one. The installation was really flawless but > > > > FreeBSD can't boot. The boot stops at the boot manager prompt with > > > > something like this : > > > > > > > > F1 FreeBSD > > > > F2 FreeBSD > > > > F3 FreeBSD > > > > F4 FreeBSD > > > > F5 other disk > > > > > > > > None function key works, there is only a "beep" and that's all. I also > > > > tried to boot on cd and load the kernel on the disk with a command > > > > like "boot mlxd(0,a)kernel" with no success. > > Ok. The 'beep' is almost certainly indicative of a geometry mixup > between the disk layout and the BIOS. Try the other BIOS translation > mode - just flip the option and reboot. If things come up OK, tell me > which mode it was in when you installed (ie. before you change it) and > I'll go see if I've stuffed something up. > You were right. My boss has changed the translation mode from "8 GB mode" to "2 GB mode" in the Mylex BIOS and now FreeBSD boots without problem. Thank you very much for your invaluable help. Stephane Legrand. -- Stephane.Legrand@bigfoot.com FreeBSD Francophone : http://www.freebsd-fr.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Wed Apr 26 1:36:34 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from maciek.gv.edu.pl (netserv.gv.edu.pl [195.117.86.8]) by hub.freebsd.org (Postfix) with ESMTP id 655BB37B54B for ; Wed, 26 Apr 2000 01:36:19 -0700 (PDT) (envelope-from ans2@gv.edu.pl) Received: from gv.edu.pl (z-TPNETu2.complex.com.pl [195.116.223.130]) by maciek.gv.edu.pl (8.9.3/8.9.1) with ESMTP id KAA05927 for ; Wed, 26 Apr 2000 10:47:03 +0200 (CEST) (envelope-from ans2@gv.edu.pl) Message-ID: <3906A9EF.2C4C47E@gv.edu.pl> Date: Wed, 26 Apr 2000 10:33:51 +0200 From: Andrzej Szydlo X-Mailer: Mozilla 4.7 [en] (WinNT; I) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-hardware@freebsd.org Subject: Satellite DVB cards drivers for FreeBSD? Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi, Does anyone know of any drivers avialable (or any work in progress) for FreeBSD for any satellite DVB cards? There are some cards with linux drivers available, but I couldn't find any for the FreeBSD. TIA Andrzej To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Wed Apr 26 8:50:12 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from mailgate.fore.com (mailgate.fore.com [169.144.68.6]) by hub.freebsd.org (Postfix) with ESMTP id 7B60137BE38 for ; Wed, 26 Apr 2000 08:50:06 -0700 (PDT) (envelope-from eho@fore.com) Received: from mailman.fore.com (mailman.fore.com [169.144.2.12]) by mailgate.fore.com (8.9.3/8.9.3) with ESMTP id LAA12112; Wed, 26 Apr 2000 11:50:02 -0400 (EDT) Received: from eholaptop (compuserve-45-17.fore.com [169.144.45.17]) by mailman.fore.com (8.9.3/8.9.3) with SMTP id LAA29941; Wed, 26 Apr 2000 11:49:47 -0400 (EDT) From: "Eric Ho" To: "Tal S Eilon" , "Alexander Langer" Cc: Subject: RE: Slow Dell PowerEdge 1300 with FreeBSD 3.4 Date: Wed, 26 Apr 2000 23:49:50 +0800 Message-ID: <000e01bfaf97$0e5ef590$0300000a@home.local> 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 8.5, Build 4.71.2377.0 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600 In-Reply-To: Importance: Normal Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > I compiled it as you said and it took 13 hours to recompile the > new kernel. > Now it does recognize 512MB of RAM but still processing everything dead > slow. > It took me close to 25min to compile tcsh-6.09.00, this is not a joke! This doesn't sound right even on an i486?! > > Maybe this can help? > > -- > Copyright (c) 1992-1999 FreeBSD Inc. > Copyright (c) 1982, 1986, 1989, 1991, 1993 > The Regents of the University of California. All rights reserved. > FreeBSD 3.4-RELEASE #0: Tue Apr 25 02:23:41 GMT 2000 > root@bell.superbanner.net:/usr/src/sys/compile/BELL > Timecounter "i8254" frequency 1193182 Hz > CPU: Pentium III (498.48-MHz 686-class CPU) > Origin = "GenuineIntel" Id = 0x673 Stepping = 3 > > Features=0x383fbff R,PGE,MCA, > CMOV,PAT,PSE36,MMX,FXSR,> > real memory = 536870912 (524288K bytes) > avail memory = 519454720 (507280K bytes) > -- > > --Tal > > > > > -----Original Message----- > From: owner-freebsd-hardware@FreeBSD.ORG > [mailto:owner-freebsd-hardware@FreeBSD.ORG]On Behalf Of Alexander Langer > Sent: Tuesday, April 25, 2000 11:50 AM > To: Tal S Eilon > Cc: freebsd-hardware@FreeBSD.ORG > Subject: Re: Slow Dell PowerEdge 1300 with FreeBSD 3.4 > > > Thus spake Tal S Eilon (tale@cybertel.co.il): > > > 1. The system did not detect my Adaptec SCSI Card which I use for my > > backup tape, so I had to remove it or it would not boot at all > ^^^^^^^^^^^^^^^^^^^^^^ > Why? > > > with MAXMEM of 512MB but with no success since the system is too slow > to > > compile. > > Too slow to compile? That is a joke. > Try it again. > > > So now I am very confused about what I should do next? any > ideas would be > > very welcome... > > compile the kernel with MAXMEM. > > Alex > > -- > I need a new ~/.sig. > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hardware" in the body of the message > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hardware" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Wed Apr 26 23:35:45 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from mega.nu (douzzer.ne.mediaone.net [24.147.236.53]) by hub.freebsd.org (Postfix) with ESMTP id 598C537B80D for ; Wed, 26 Apr 2000 23:35:32 -0700 (PDT) (envelope-from douzzer@mega.nu) Received: (from douzzer@localhost) by mega.nu (8.10.0.Beta6/8.10.0.Beta6) id e3R6ZRM06120; Thu, 27 Apr 2000 02:35:27 -0400 (EDT) Date: Thu, 27 Apr 2000 02:35:27 -0400 (EDT) Message-Id: <200004270635.e3R6ZRM06120@mega.nu> From: Daniel Pouzzner To: freebsd-hardware@freebsd.org Subject: PCI bus activity causes Soundblaster Live glitches Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Whenever my NIC or SCSI controller generates PCI bus traffic, I hear crackle-pop type glitches from the sound card. I believe the problem is with the sound card (Usenet is rife with frustrated reports of SB Live specific crackling, popping, etc., using Creative's own drivers and the very ordinary mass market hardware and software the card was intended for), so I should be glad I'm well within the 14 day return window I suppose. By the way, when it's not glitching, the SB Live has good sound quality, despite all data being digitally resampled to 48khz before it reaches the DAC. A persistent problem I've seen is that I cannot sample with the card. cat and sox invariably exit immediately with a "device busy" error. Seems like this might be something awry in the driver? For when I've given up on the SB Live, does anyone have a sound card recommendation for me? I want S/PDIF I/O, but if I could just have good quality glitch free analog I/O (preferably over PCI) I'd be satisfied. I'm planning on getting an RME Hammerfall for digital I/O anyway. So about this glitching: what I'm hoping for, obviously, is some magic incantation that will make the card stop glitching. My hopes are not high but I figured it was at least worth giving the question an audience. Machine description: CPU: Athlon 750 mainboard: Epox 7KXA BIOS: Award for 7KXA, version of 2000-Apr-25 memory: Kingston PC133, clocked at 133MHz NIC: 3com 3C905B SCSI: Adaptec 39160 sound card: Creative Soundblaster Live! mp3 display: Matrox G400-TV OS: FreeBSD 4.0-RELEASE sound card driver: emu10k1 of 2000-Apr-18, grabbed from 5.0-CURRENT The sound card has its IRQ (5) all to itself, though it doesn't in fact make any difference whether it shares an IRQ or not (experimentally determined). Display activity causes no glitches. The G400 runs over the AGP port a.k.a. pci1, while the main peripheral bus is pci0, so this is unsurprising. Chipset onboard ATA/66 interface activity does not cause glitches, even though the controller is internally on pci0. Activity over low speed devices on the ISA bus - specifically, keyboard and mouse - do not generate glitches, even though the ISA bridge hangs off pci0. In other words, glitches occur only when other outboard cards on the pci0 backplane generate traffic, and then, occur sporadically but fairly predictably. In particular, an ifconfig probe of the NIC always produces a substantial glitch. In the earliest BIOS version of my mainboard, there was a known bug that caused outboard sound cards to have noise and glitches. In early March Epox released a BIOS version that purported to fix the sound problem ("Fixed cracking sound problem when an additional sound card is installed."). I am now running a BIOS that is several generations on from that original fixed version. On a slightly related issue, I have never been able to get onboard sound on the Epox to actually make any sound, though I imagine I'm not missing much. Thanks in advance for any advice, -Daniel Pouzzner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Thu Apr 27 0:20:58 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from Wheel.TSR.Ru (wheel.tsr.ru [195.208.67.7]) by hub.freebsd.org (Postfix) with ESMTP id AAE9E37B650 for ; Thu, 27 Apr 2000 00:19:24 -0700 (PDT) (envelope-from matrix@chat.ru) Received: from wp1 (VG-1-15.dialup.tsr.ru [195.208.67.113]) by Wheel.TSR.Ru (8.10.1may/TELECORE-1.1) with SMTP id e3R7J8f13081 for ; Thu, 27 Apr 2000 11:19:10 +0400 (MSD) envelope from matrix@chat.ru Message-ID: <003301bfb018$e8406060$0c00a8c0@ipform.ru> From: "Artem Koutchine" To: Subject: What's you server harware config? Date: Thu, 27 Apr 2000 11:19:14 +0400 Organization: IP Form MIME-Version: 1.0 Content-Type: text/plain; charset="koi8-r" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2615.200 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200 Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I still need more input on server hardware wich works perfectly with FreeBSD 3.4. Tell me your Motherboard/CPU/Memory/SCSI/LAN/HDDs Admit it, it is always enjoyable to tell another one how smart you were to setup such a flowless machine. Regards, Artem Koutchine To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Thu Apr 27 5:33:49 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from mail.rz.fh-wilhelmshaven.de (mail.rz.fh-wilhelmshaven.de [139.13.25.134]) by hub.freebsd.org (Postfix) with ESMTP id 0936A37B623 for ; Thu, 27 Apr 2000 05:33:36 -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 mail.rz.fh-wilhelmshaven.de (8.9.3/8.9.3) with SMTP id OAA29248; Thu, 27 Apr 2000 14:33:03 +0200 (MET DST) Message-Id: <4.1.20000427142107.0096d8e0@mail.rz.fh-wilhelmshaven.de> X-Sender: ohoyer@mail.rz.fh-wilhelmshaven.de X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1 Date: Thu, 27 Apr 2000 14:26:51 +0200 To: Daniel Pouzzner From: Olaf Hoyer Subject: Re: PCI bus activity causes Soundblaster Live glitches Cc: freebsd-hardware@FreeBSD.ORG In-Reply-To: <200004270635.e3R6ZRM06120@mega.nu> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org At 02:35 27.04.00 -0400, you wrote: >Whenever my NIC or SCSI controller generates PCI bus traffic, I hear >crackle-pop type glitches from the sound card. I believe the problem >is with the sound card (Usenet is rife with frustrated reports of SB >Live specific crackling, popping, etc., using Creative's own drivers >and the very ordinary mass market hardware and software the card was >intended for), so I should be glad I'm well within the 14 day return >window I suppose. Hi! Well, I suspect some DMA problem. IIRC the mentioned devices also use heavy transfer time on PCI bus, so (depending on the driver state/PCI driver/scheduler for PCI transfers), the SB Live's datastream may be interrupted sometimes. COuld be a simple priority issue, or a sign of alck of support for the new VIA chipsets. (Or some flaws not yet ironed out). The Epox mainboard is also rumored on other mailinglists not to be the first choice. (Asus rulez) > >Machine description: > >CPU: Athlon 750 >mainboard: Epox 7KXA >BIOS: Award for 7KXA, version of 2000-Apr-25 >memory: Kingston PC133, clocked at 133MHz >NIC: 3com 3C905B >SCSI: Adaptec 39160 >sound card: Creative Soundblaster Live! mp3 >display: Matrox G400-TV > >OS: FreeBSD 4.0-RELEASE >sound card driver: emu10k1 of 2000-Apr-18, grabbed from 5.0-CURRENT > > >The sound card has its IRQ (5) all to itself, though it doesn't in >fact make any difference whether it shares an IRQ or not >(experimentally determined). The IRQ 5 is normally (this means, Windoze 9x) used for SB16/ISA compatibility for old apps. Regards OIaf Hoyer -------- Olaf Hoyer www.nightfire.de mailto:Olaf.Hoyer@nightfire.de FreeBSD- Turning PC's into workstations ICQ:22838075 Liebe und Hass sind nicht blind, aber geblendet vom Feuer, dass sie selber mit sich tragen. (Nietzsche) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Fri Apr 28 0: 1:29 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from phoenix.volant.org (phoenix.volant.org [205.179.79.193]) by hub.freebsd.org (Postfix) with ESMTP id AE78B37B659 for ; Fri, 28 Apr 2000 00:01:26 -0700 (PDT) (envelope-from patl@phoenix.volant.org) Received: from asimov.phoenix.volant.org ([205.179.79.65]) by phoenix.volant.org with esmtp (Exim 1.92 #8) for hardware@freebsd.org id 12l4mD-0001Wp-00; Fri, 28 Apr 2000 00:01:25 -0700 Received: from localhost (localhost [127.0.0.1]) by asimov.phoenix.volant.org (8.9.1b+Sun/8.9.1) with SMTP id AAA22043 for ; Fri, 28 Apr 2000 00:01:22 -0700 (PDT) Date: Fri, 28 Apr 2000 00:01:22 -0700 (PDT) From: patl@phoenix.volant.org Reply-To: patl@phoenix.volant.org Subject: dc0: couldn't map ports/memory To: hardware@freebsd.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 I've just installed FreeBSD 4.0R on an Hitachi VisionBook Pro 7590. During the boot, when the probe checks the builtin NIC, it reports: dc0: irq 11 at device 11.0 on pci0 dc0: couldn't map ports/memory device_probe_and_attach: dc0 attach returned 6 Windows98 lists this device as: Class: Network adapters Device: PCI Fast Ethernet DEC 21143 Based Adapter Resources: IRQ: 11 I/O: 1080h-10FFh MEM: 09043000h-090433FFh What do I need to do to get FreeBSD to correctly handle this device? Thanks, -Pat To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Fri Apr 28 4: 5:56 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from guard.polynet.lviv.ua (Guard.PolyNet.Lviv.UA [209.58.62.194]) by hub.freebsd.org (Postfix) with SMTP id B765437B7CF for ; Fri, 28 Apr 2000 04:05:34 -0700 (PDT) (envelope-from akorud@polynet.lviv.ua) Received: (qmail 68289 invoked from network); 28 Apr 2000 11:05:27 -0000 Received: from unknown (HELO postoffice.polynet.lviv.ua) (unknown) by unknown with SMTP; 28 Apr 2000 11:05:27 -0000 Received: (qmail 60038 invoked from network); 28 Apr 2000 11:05:26 -0000 Received: (ofmipd unknown); 28 Apr 2000 11:05:04 -0000 Date: 28 Apr 2000 14:05:42 +0300 Message-ID: From: "Andriy Korud" To: hardware@freebsd.org Subject: FreeBSD & RAID MIME-Version: 1.0 Content-Type: text/plain; charset="koi8-r" 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.50.4029.2901 Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi Can somebody answer me two questins: - Is Mylex AccelRaid 250 supported in FreeBSD 4_STABLE? - Which cheap (ala Mylex) RAID controller is best supported under FreeBSD 4_STABLE? Thanks in advance, Andriy Korud, Lviv, Ukraine To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Fri Apr 28 8:44: 3 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from sirius.stella-net.fr (sirius.stella-net.fr [195.154.71.2]) by hub.freebsd.org (Postfix) with ESMTP id 2C75E37BF31 for ; Fri, 28 Apr 2000 08:43:58 -0700 (PDT) (envelope-from garry@stella-net.fr) Received: from stella-net.fr ([193.48.73.34]) by sirius.stella-net.fr (8.9.3/8.9.3) with ESMTP id RAA06393 for ; Fri, 28 Apr 2000 17:43:40 +0200 Message-ID: <3909B215.CAC1563D@stella-net.fr> Date: Fri, 28 Apr 2000 17:45:25 +0200 From: Philippe Charron Organization: Alcatel Space Industries X-Mailer: Mozilla 4.72 [en] (X11; I; FreeBSD 4.0-RELEASE i386) X-Accept-Language: fr-FR, en MIME-Version: 1.0 To: hardware@FreeBSD.ORG Subject: someone has an idea ? Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hello, Im a trying to do a FreeBSD box without any keyboard (this machine will be a Squid, HTTP and FTP serveur for non specialist person that can't handle with a Unix system). As the user can't shutdown properly the computer, he has to press the power button to switch off the box. This leads to problems with fsck and inode lost in the system. Does anyone have an idea to solve this problem ? Thanx in avance Philippe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Fri Apr 28 10: 3:44 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from mail.rz.fh-wilhelmshaven.de (mail.rz.fh-wilhelmshaven.de [139.13.25.134]) by hub.freebsd.org (Postfix) with ESMTP id EFBD837BF7D for ; Fri, 28 Apr 2000 10:03:34 -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 mail.rz.fh-wilhelmshaven.de (8.9.3/8.9.3) with SMTP id TAA21411; Fri, 28 Apr 2000 19:03:22 +0200 (MET DST) Message-Id: <4.1.20000428184009.00cac4b0@mail.rz.fh-wilhelmshaven.de> X-Sender: ohoyer@mail.rz.fh-wilhelmshaven.de X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1 Date: Fri, 28 Apr 2000 18:48:47 +0200 To: Philippe Charron From: Olaf Hoyer Subject: Re: someone has an idea ? Cc: freebsd-hardware@freebsd.org In-Reply-To: <3909B215.CAC1563D@stella-net.fr> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org At 17:45 28.04.00 +0200, you wrote: >Hello, > >Im a trying to do a FreeBSD box without any keyboard (this machine will >be a Squid, HTTP and FTP serveur for non specialist person that can't >handle with a Unix system). > >As the user can't shutdown properly the computer, he has to press the >power button to switch off the box. >This leads to problems with fsck and inode lost in the system. > Hi! Well, there are several possibilities: If there are any other machines running on the local network (preferrably under Windoze), what about remote shutdown? Simply write a little script there, that logs onto the FBSD machine, and issues a "halt". There also shall be some little freeware/shareware programs available for that. Then create a shortcut on the desktop of that machine, and voila- Remote shutdown with a simple mouseclick. (Or place a crappy old 386 with some kind of win3.1 beneath the BSD box... Like a terminal) Or, if the shutdown is on a regular basis, do it with a cron job. Other thought: Is there any possibility that FBSD may read on actual boards those SMI power saving switch status? On newer boards you have that switch to set the system to a standby mode. What against making FBSD reading out that status of the switch, and instead standby-mode, a ordinary shutdown -h is issued? Best thing also would be a big big screen displayed after halt: It is now safe to turn the computer off ... ;-)) Regards Olaf Hoyer -------- Olaf Hoyer www.nightfire.de mailto:Olaf.Hoyer@nightfire.de FreeBSD- Turning PC's into workstations ICQ:22838075 Liebe und Hass sind nicht blind, aber geblendet vom Feuer, dass sie selber mit sich tragen. (Nietzsche) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Fri Apr 28 10: 5:59 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from mail.surf1.de (mail.Surf1.de [194.25.165.21]) by hub.freebsd.org (Postfix) with ESMTP id 5231837B804 for ; Fri, 28 Apr 2000 10:05:43 -0700 (PDT) (envelope-from alex@cichlids.com) Received: from cichlids.com (p3E9C112E.dip0.t-ipconnect.de [62.156.17.46]) by mail.surf1.de (8.9.3/8.9.3) with ESMTP id SAA19327; Fri, 28 Apr 2000 18:04:40 +0200 Received: from cichlids.cichlids.com (cichlids.cichlids.com [192.168.0.10]) by cichlids.com (Postfix) with ESMTP id B62E4AC2C; Fri, 28 Apr 2000 18:08:59 +0200 (CEST) Received: (from alex@localhost) by cichlids.cichlids.com (8.9.3/8.9.3) id SAA21752; Fri, 28 Apr 2000 18:04:49 +0200 (CEST) (envelope-from alex) Date: Fri, 28 Apr 2000 18:04:49 +0200 From: Alexander Langer To: Philippe Charron Cc: hardware@FreeBSD.ORG Subject: Re: someone has an idea ? Message-ID: <20000428180449.A21702@cichlids.cichlids.com> References: <3909B215.CAC1563D@stella-net.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <3909B215.CAC1563D@stella-net.fr>; from garry@stella-net.fr on Fri, Apr 28, 2000 at 05:45:25PM +0200 X-PGP-Fingerprint: 44 28 CA 4C 46 5B D3 A8 A8 E3 BA F3 4E 60 7D 7F X-Verwirrung: Dieser Header dient der allgemeinen Verwirrung. Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Thus spake Philippe Charron (garry@stella-net.fr): > This leads to problems with fsck and inode lost in the system. > Does anyone have an idea to solve this problem ? remote boot it (ssh). Or, if you have some hardware/programming knowledge, you create a switch, that you connec to a serial/parallel interface and then, when you press it, a kernel module shutdowns the computer. Alex -- I need a new ~/.sig. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Fri Apr 28 10:42:10 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from ren.sasknow.com (ren.sasknow.com [207.195.92.131]) by hub.freebsd.org (Postfix) with ESMTP id ECB8737B822 for ; Fri, 28 Apr 2000 10:42:03 -0700 (PDT) (envelope-from ryan@sasknow.com) Received: from localhost (ryan@localhost) by ren.sasknow.com (8.9.3/8.9.3) with ESMTP id LAA61554; Fri, 28 Apr 2000 11:42:44 -0600 (CST) (envelope-from ryan@sasknow.com) Date: Fri, 28 Apr 2000 11:42:44 -0600 (CST) From: Ryan Thompson To: Philippe Charron Cc: hardware@FreeBSD.ORG Subject: Re: someone has an idea ? In-Reply-To: <3909B215.CAC1563D@stella-net.fr> Message-ID: Organization: SaskNow Technologies [www.sasknow.com] MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Philippe Charron wrote to hardware@FreeBSD.ORG: > Hello, > > Im a trying to do a FreeBSD box without any keyboard (this machine will > be a Squid, HTTP and FTP serveur for non specialist person that can't > handle with a Unix system). > > As the user can't shutdown properly the computer, he has to press the > power button to switch off the box. > This leads to problems with fsck and inode lost in the system. > > Does anyone have an idea to solve this problem ? Assuming the user isn't experienced enough to handle a full root login, what about the following: create another user with uid '0', gid '0', different password, name = halt, shell = /sbin/halt. Be sure to add /sbin/halt to /etc/shells and remake the password database if you don't use vipw. Note I haven't actually 'tried' this. :-) Then, all that must be done is--with an ssh client and root logins enabled--put a login icon on their desktop. At the prompts, they have to remember 'halt' and a password. Not rocket science. Of course, this is kind of a kludge. You could accomplish the same with a cgi web form (if Apache is running) that inputs a password for the 'halt' user. Then, that password is passed along to a cgi script (probably using expect(1)) that runs 'su halt -c /sbin/halt'... and make sure that you added /sbin/halt to /etc/shells! Then, rebooting the system is as easy as clicking on a hyperlink and entering a password. OR... The other option that I see is the following. Create a root run shell script that can be detached (&) that sleep(1)s for 20 or 30 seconds and looks for a flagfile. The flag file directory can be owned by a normal user (say, with ftp access) and when halt.flag is created, reboot the system. Below is a shell script that we use for things like restarting daemons, etc. I've modified it for you so that it will halt a system when /var/db/sysflags/halt is created. #!/bin/sh # # $Id: sysflagd,v 1.1 2000/01/18 17:33:11 ryan Exp ryan $ # # Synopsis: # Monitors for the existence of predetermined flag files and executes # commands as root. # # (C)2000 SaskNow Technologies # All Rights Reserved if [ ! -e /var/log/sysflagd.log ] ; then touch /var/log/sysflagd.log logger -i -p local0.info New log started fi logger -i -p local0.info Started on `date`, `hostname` while true ; do if [ -f /var/db/sysflags/halt ] ; then logger -ip local0.info System shutdown initiated rm /var/db/sysflags/halt /sbin/halt fi # Default sleep interval of 30 seconds sleep 30 done simply run the 'sysflagd' shell script as root like: # ./sysflagd & or add a script to /usr/local/etc/rc.d/ to start it at bootup. Then, creating that flagfile is as simple as creating the directory, chmod 755 to a regular user of choice, and make a batch file in windows that invokes microsoft's stock ``ftp'' program with a name and password and uploads that file. Create a shortcut to that, and anyone with that batch file can remote shutdown the machine. :-) You will probably want to tweak /etc/login.access to allow logins only from a specific host for the user. -- Ryan Thompson Systems Administrator, Accounts Phone: +1 (306) 664-1161 SaskNow Technologies http://www.sasknow.com #106-380 3120 8th St E Saskatoon, SK S7H 0W2 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Fri Apr 28 11: 0:49 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from intra.daemontech.net (intra.daemontech.net [208.138.46.11]) by hub.freebsd.org (Postfix) with SMTP id 1287437B60C for ; Fri, 28 Apr 2000 11:00:47 -0700 (PDT) (envelope-from nicole@unixgirl.com) Received: (qmail 41206 invoked by uid 200); 28 Apr 2000 18:00:46 -0000 Received: from xwin.nmhtech.com (208.138.46.10) by intra.daemontech.net with SMTP; 28 Apr 2000 18:00:46 -0000 Content-Length: 1785 Message-ID: X-Mailer: XFMail 1.3.1 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <3909B215.CAC1563D@stella-net.fr> Date: Fri, 28 Apr 2000 11:00:46 -0700 (PDT) From: "Nicole Harrington." To: Philippe Charron Subject: RE: someone has an idea ? Cc: hardware@FreeBSD.ORG Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On 28-Apr-00 Philippe Charron wrote: > Hello, > > Im a trying to do a FreeBSD box without any keyboard (this machine will > be a Squid, HTTP and FTP serveur for non specialist person that can't > handle with a Unix system). > > As the user can't shutdown properly the computer, he has to press the > power button to switch off the box. > This leads to problems with fsck and inode lost in the system. > > Does anyone have an idea to solve this problem ? > > Thanx in avance > Philippe > In a similiar situation I partially solved it in a somewhat lame way by setting fsck in /etc/rc to fsck -f -y (by memory) This way on every reboot it would perform a full fsck with a yes to repair. Also be sure to use soft updates on any partiton that would likely have active writes when switched off. Hope this helps Nicole > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hardware" in the body of the message nicole@unixgirl.com |\ __ /| (`\ http://www.unixgirl.com/ webmistress@dangermouse.org | o_o |__ ) ) http://www.dangermouse.org/ // \\ ---------------------------(((---(((----------------------------------------- -- Powered by Coka-Cola and FreeBSD -- -- Stong enough for a man - But made for a Woman -- -- Microsoft: What bug would you like today? -- ------------------------------------------------------------------------------- -- As a computing professional, I believe it would be unethical for me to advise, recommend, or support the use (save possibly for personal amusement) of any product that is or depends on any Microsoft product. -- OWNED? MS: Who's Been In Your Computer Today? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Fri Apr 28 12:41:44 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from cs.rice.edu (cs.rice.edu [128.42.1.30]) by hub.freebsd.org (Postfix) with ESMTP id 82E0337B60C for ; Fri, 28 Apr 2000 12:41:42 -0700 (PDT) (envelope-from rjf@cs.rice.edu) Received: from cs.rice.edu (zot.cs.rice.edu [128.42.3.141]) by cs.rice.edu (8.9.0/8.9.0) with ESMTP id OAA06833 for ; Fri, 28 Apr 2000 14:41:39 -0500 (CDT) Message-ID: <3909E972.429276D2@cs.rice.edu> Date: Fri, 28 Apr 2000 14:41:38 -0500 From: Rob Fowler X-Mailer: Mozilla 4.72 [en] (WinNT; U) X-Accept-Language: en MIME-Version: 1.0 To: hardware@freebsd.org Subject: [Fwd: someone has an idea ?] Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org It's easy if the operator can come in over the net, but if you want a "front-panel shutdown" function on a box without keyboard or other obvious I/O devices, you'll have to make do with what your hardware has. If there is a button or switch you can use as a sensor, then all you need is a demon monitoring that function. This may require hardware and/or software hacking. A couple of years ago we were running a small keyboard-less cluster that was usually FreeBSD, but occasionally had to be brought up under Linux. The solution was to use the presence absence of a LILO floppy as the control for bringing the system up. The drill was to put LILO floppies in all the drives (or remove them) and force reboots over the net through a script. Sleazy, but effective. If the floppy drive is not being used, you might try the inverse of the floppy trick. Write a script that tries to open a file called on the floppy and halts if successful. Run it under cron with an appropriate interval, or just wrap it in sleep loop and start the script when the system boots. Tell the operator to stick the bright red floppy in the drive and wait xx seconds before powering down. The tricky thing may be signalling the operator when it really is OK to power down. If the box is new enough to shut itself off on a halt, then you're done. Otherwise, you may have to have the kernel beep a couple of times after it's done sync'ing. -- Rob > > On 28-Apr-00 Philippe Charron wrote: > > Hello, > > > > Im a trying to do a FreeBSD box without any keyboard (this machine will > > be a Squid, HTTP and FTP serveur for non specialist person that can't > > handle with a Unix system). > > > > As the user can't shutdown properly the computer, he has to press the > > power button to switch off the box. > > This leads to problems with fsck and inode lost in the system. > > > > Does anyone have an idea to solve this problem ? > > > > Thanx in avance > > Philippe > >> > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Sat Apr 29 10:52:40 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from mail-out.visi.com (kauket.visi.com [209.98.98.22]) by hub.freebsd.org (Postfix) with ESMTP id C84C437B947 for ; Sat, 29 Apr 2000 10:52:37 -0700 (PDT) (envelope-from sdk@visi.com) Received: from isis.visi.com (isis.visi.com [209.98.98.8]) by mail-out.visi.com (Postfix) with ESMTP id CBD8F3918; Sat, 29 Apr 2000 12:52:30 -0500 (CDT) Received: (from sdk@localhost) by isis.visi.com (8.8.8/8.8.8) id MAA02413; Sat, 29 Apr 2000 12:52:30 -0500 (CDT) Date: Sat, 29 Apr 2000 12:52:30 -0500 From: Stephen To: freebsd-hardware@FreeBSD.ORG Subject: IRQ question Message-ID: <20000429125230.A406@visi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii User-Agent: Mutt/0.96.1i Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I have a Intel Seattle (SE440BX) mainboard running 3.4-S with the following bootup messages: Apr 21 22:20:37 io /kernel: fxp0: rev 0x08 int a irq 11 on pci0.13.0 Apr 21 22:20:37 io /kernel: fxp0: Ethernet address 00:90:27:ad:44:4a Apr 21 22:20:37 io /kernel: fxp1: rev 0x08 int a irq 11 on pci0.14.0 Apr 21 22:20:37 io /kernel: fxp1: Ethernet address 00:90:27:ad:44:c6 Apr 21 22:20:37 io /kernel: Probing for devices on PCI bus 1: Apr 21 22:20:37 io /kernel: vga0: rev 0x00 int a irq 11 on pci1.0.0 Having just built another PC I learned that it's not optimal to have pci devices sharing IRQ's. So, not knowing about how FreeBSD interfaces with the hardware, I'm wondering if I'm sacrificing performance by having 3 devices using IRQ 11. Should I move cards/reconfig the BIOS to use unassigned IRQ's? Thanks, Steve -- sdk@yuck.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Sat Apr 29 13:11:11 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from mass.cdrom.com (adsl-63-202-176-65.dsl.snfc21.pacbell.net [63.202.176.65]) by hub.freebsd.org (Postfix) with ESMTP id C2A5737B51B for ; Sat, 29 Apr 2000 13:11:07 -0700 (PDT) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id NAA01057; Sat, 29 Apr 2000 13:19:06 -0700 (PDT) (envelope-from msmith@mass.cdrom.com) Message-Id: <200004292019.NAA01057@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: "Andriy Korud" Cc: hardware@freebsd.org Subject: Re: FreeBSD & RAID In-reply-to: Your message of "28 Apr 2000 14:05:42 +0300." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 29 Apr 2000 13:19:06 -0700 From: Mike Smith Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > Hi > Can somebody answer me two questins: > - Is Mylex AccelRaid 250 supported in FreeBSD 4_STABLE? Yes. > - Which cheap (ala Mylex) RAID controller is best supported under FreeBSD > 4_STABLE? All of the "cheap" PCI Mylex and AMI controllers are supported. Right now, Mylex support is better. -- \\ 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 Sat Apr 29 18:43:44 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from vail.net (vail.net [199.45.148.10]) by hub.freebsd.org (Postfix) with ESMTP id 5C56737B67A for ; Sat, 29 Apr 2000 18:43:41 -0700 (PDT) (envelope-from ivanfetch@technologist.com) Received: from gatekeeper.cfcc.com (cfcc.com [204.144.216.251]) by vail.net (/) with ESMTP id e3U1abc14015 for ; Sat, 29 Apr 2000 19:36:37 -0600 (MDT) Received: from oak.ivanfetch.tzo.com (130.253.6.20 [130.253.6.20]) by gatekeeper.cfcc.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.1960.3) id JSC692GL; Sat, 29 Apr 2000 19:51:07 -0600 Date: Sat, 29 Apr 2000 18:41:11 -0700 (MST) From: Ivan Fetch X-Sender: ifetch@oak.ivanfetch.tzo.com To: freebsd-hardware@freebsd.org Subject: Please Help: CD-ROM no longer works with 4.0R vs. 3.4R! 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, can someone please give me some help with the following - I would really appreciate it. I posted this to freebsd-questions and got nothing... Attempting to install FreeBSD 4.0-Release to a Compaq prosario yields the following message (while the kernel is detecting devices). The CD-ROM in this machine workked fine under FreeBSD 3.4 - Can anyone help me out as to why it no longer does? ata1-master: cdrom device - no driver! Thank you very much - Ivan. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message