From owner-freebsd-hardware Sun Apr 16 19:33:19 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from orion.ac.hmc.edu (Orion.AC.HMC.Edu [134.173.32.20]) by hub.freebsd.org (Postfix) with ESMTP id E200337B80B for ; Sun, 16 Apr 2000 19:33:14 -0700 (PDT) (envelope-from brdavis@orion.ac.hmc.edu) Received: (from brdavis@localhost) by orion.ac.hmc.edu (8.8.8/8.8.8) id TAA22304; Sun, 16 Apr 2000 19:33:05 -0700 (PDT) Date: Sun, 16 Apr 2000 19:33:05 -0700 From: Brooks Davis To: Barney Wolff Cc: freebsd-hardware@FreeBSD.ORG Subject: Re: thermal grease? Message-ID: <20000416193305.A16979@orion.ac.hmc.edu> References: <38f8b28a0.3ca7@databus.databus.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre4i In-Reply-To: <38f8b28a0.3ca7@databus.databus.com>; from barney@databus.com on Sat, Apr 15, 2000 at 02:15:00PM -0400 Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Sat, Apr 15, 2000 at 02:15:00PM -0400, Barney Wolff wrote: > Would some kind soul give me a hint on where to acquire the thermal > grease that everybody says must be placed between the cpu and its > heat-sink/fan? The cheap parts places I deal with don't seem to > carry it, nor does my local CompUSA, nor Radio Shack, nor computer store. > All of them seem to just clip the fan to the chip and hope for the best. Lots of places should have it, but you can get small quantaties (though far more then you need) from PC Power and Cooling at http://www.pcpowercooling.com/ -- Brooks -- Any statement of the form "X is the one, true Y" is FALSE. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Sun Apr 16 21:29:35 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from anchor-post-32.mail.demon.net (anchor-post-32.mail.demon.net [194.217.242.90]) by hub.freebsd.org (Postfix) with ESMTP id EB52C37B589 for ; Sun, 16 Apr 2000 21:29:30 -0700 (PDT) (envelope-from freebsd-lists@i-zone.demon.co.uk) Received: from i-zone.demon.co.uk ([158.152.227.78]) by anchor-post-32.mail.demon.net with esmtp (Exim 2.12 #1) id 12h3A8-0003VP-0W for freebsd-hardware@freebsd.org; Mon, 17 Apr 2000 05:29:29 +0100 Message-ID: Date: Mon, 17 Apr 2000 05:28:07 +0100 To: freebsd-hardware@freebsd.org From: John Subject: zoom webcam (ISA) and freebsd 4.0 MIME-Version: 1.0 X-Mailer: Turnpike Integrated Version 5.00 U Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hello people I was wondering if there is anyone out there with a success story regarding zoomcam isa and freebsd 4.0., if so can they please post it here and mail it to me at the address below as well the spec of the zoomcam & description can be found at http://www.zoom.com/datasheets/isacam.shtml Thanks -- John To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Mon Apr 17 2: 6:51 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from linux.ssc.nsu.ru (linux.ssc.nsu.ru [193.124.219.91]) by hub.freebsd.org (Postfix) with SMTP id D07D537BAE8 for ; Mon, 17 Apr 2000 02:03:38 -0700 (PDT) (envelope-from danfe@inet.ssc.nsu.ru) Received: (qmail 6217 invoked from network); 17 Apr 2000 09:03:32 -0000 Received: from inet.ssc.nsu.ru (62.76.110.12) by hub.freebsd.org with SMTP; 17 Apr 2000 09:03:32 -0000 Received: from localhost (danfe@localhost) by inet.ssc.nsu.ru (8.9.3/8.9.3) with ESMTP id QAA00706; Mon, 17 Apr 2000 16:02:32 +0700 Date: Mon, 17 Apr 2000 16:02:32 +0700 (NOVST) From: "Alexey N. Dokuchaev" To: freebsd-hackers@freebsd.org Cc: freebsd-hardware@freebsd.org Subject: NEC 260 CDROM detection under FreeBSD 4.0-RELESE/STABLE 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've been using FreeBSD 3.4 for quite a while, and my CDROM, being quite old and weird (NEC 260 model) was detected by both BIOS and FreeBSD. Recently, I've decided to upgrade to FreeBSD 4.0, and also changed my motherboad, now it is ASUS TXP4, was latest version of award bios, and now it doesn't find my CDROM (I have two harddrives, both partitioned in dedicated mode, one (bootable for FreeBSD) is master with CDROM being slave on first contoller, another is singe/master on the second; I've tried moving them around, but it didn't help). I've even tried attaching CDROM on my sound card's IDE conntector, still unsuccessfully). The reason why I am writing this, because when I boot Linux (from boot/rescue diskettes, for instance), it definitely does find my CDROM! Computer specs: genuine intel Pentium 200 MMX, 64M RAM, FreeBSD 4.0, NE2000-compatible non-PnP ISA NIC on irq 5, MM ISP 16 sound card (ISA non-PnP) on irq 11, USB IRQ 12, 2 coms, 1 lpt, s3 virge dx/gx on irq 10, two floppy frives on irq 6. I know most of this is useless, but still, maybe someone will notice some conflicts; I still doubt though. Here's parts of both dmesg's: FreeBSD: --------------------------------------------------- atapci0: port 0xe000-0xe00f at device 1.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 ... ad0: 3079MB [6256/16/63] at ata0-master using UDMA33 ad1: 4111MB [8354/16/63] at ata1-master using UDMA33 Mounting root from ufs:/dev/ad1s1a --------------------------------------------------- Linux: --------------------------------------------------- ide: i82371 PIIX (Triton) on PCI bus 0 function 9 ide0: BM-DMA at 0xe000-0xe007 ide1: BM-DMA at 0xe008-0xe00f hda: QUANTUM FIREBALL SE3.2A, 3079MB w/80kB Cache, CHS=702/128/63, UDMA hdb: NEC CD-ROM DRIVE:260, ATAPI cdrom or floppy?, assuming CDROM drive hdc: ST34310A, 4111MB w/512kB Cache, CHS=8354/16/63, UDMA ide0 at 0x1f0-0x1f7,0x3f6 on irq 14 ide1 at 0x170-0x177,0x376 on irq 15 --------------------------------------------------- My thoughts would be, maybe FreeBSD relies on BIOS here, which doesn't detect CDROM, while Linux detects it without BIOS. So, maybe there is a way to say explicitly to FreeBSD that I have CDROM with exact parameters? Any help regarding this subject will be greatly appreciated. P.S. Sorry for cross-posting, and please reply directly, since I am not the member of the maillists. Cheers, /* Alexey N. Dokuchaev, more commonly | */ /* known as DAN Fe | mailto:danfe@inet.ssc.nsu.ru */ /* | ICQ UIN: 38934845 */ /* Novosibirsk State University | http://inet.ssc.nsu.ru/~danfe/ */ /* Scientific Study Center Computer Lab | */ [Team Assembler] [Team BSD] [Team DooM] [Team Quake] -----BEGIN GEEK CODE BLOCK----- Version: 3.12 GCS d-@ s+: a--- C++(+++) UBL++++$ P++>$ L+ E-- W++ N++ o? K? w-- O- M V- PS PE Y+ PGP+ t+ 5+ X+ R- !tv b++ DI+ D+++ G++ e h !r !y+ ------END GEEK CODE BLOCK------ Microsoft: Where do you want to go today? Linux: Where do you want to go tomorrow? FreeBSD: Are you guys coming or what? Microsoft: What are we going to rip off today and claim as our own? Microsoft: Where do you want to be taken today? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Mon Apr 17 2:45:32 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from paprika.michvhf.com (paprika.michvhf.com [209.103.136.12]) by hub.freebsd.org (Postfix) with SMTP id A636737B83D for ; Mon, 17 Apr 2000 02:45:29 -0700 (PDT) (envelope-from vev@michvhf.com) Received: (qmail 4815 invoked by uid 1001); 17 Apr 2000 09:45:32 -0000 Date: Mon, 17 Apr 2000 05:45:32 -0400 (EDT) From: Vince Vielhaber To: Barney Wolff Cc: freebsd-hardware@FreeBSD.ORG Subject: Re: thermal grease? In-Reply-To: <20000416193305.A16979@orion.ac.hmc.edu> 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 Sat, Apr 15, 2000 at 02:15:00PM -0400, Barney Wolff wrote: > Would some kind soul give me a hint on where to acquire the thermal > grease that everybody says must be placed between the cpu and its > heat-sink/fan? The cheap parts places I deal with don't seem to > carry it, nor does my local CompUSA, nor Radio Shack, nor computer store. > All of them seem to just clip the fan to the chip and hope for the best. Here's the radio shack part number: 901-0237 You can order it right off their website for about $5.00. Vince. -- ========================================================================== Vince Vielhaber -- KA8CSH email: vev@michvhf.com http://www.pop4.net 128K ISDN from $22.00/mo - 56K Dialup from $16.00/mo at Pop4 Networking Online Campground Directory http://www.camping-usa.com Online Giftshop Superstore http://www.cloudninegifts.com ========================================================================== To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Mon Apr 17 4:44:19 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from fanta.modeemi.cs.tut.fi (fanta.modeemi.cs.tut.fi [130.230.11.247]) by hub.freebsd.org (Postfix) with ESMTP id C910237B5E6 for ; Mon, 17 Apr 2000 04:44:07 -0700 (PDT) (envelope-from tuomov@fanta.modeemi.cs.tut.fi) Received: by fanta.modeemi.cs.tut.fi id OAA0000011384; Mon, 17 Apr 2000 14:43:12 +0300 (EET DST) Date: Mon, 17 Apr 2000 14:43:12 +0300 From: Valkonen Tuomo To: "Alexey N. Dokuchaev" Cc: freebsd-hardware@freebsd.org Subject: Re: NEC 260 CDROM detection under FreeBSD 4.0-RELESE/STABLE Message-ID: <20000417144312.A11777@fanta.modeemi.cs.tut.fi> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: ; from danfe@inet.ssc.nsu.ru on Mon, Apr 17, 2000 at 04:02:32PM +0700 Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Mon, Apr 17, 2000 at 04:02:32PM +0700, Alexey N. Dokuchaev wrote: > Recently, I've decided to upgrade to FreeBSD 4.0, and also changed my > motherboad, now it is ASUS TXP4, was latest version of award bios, and now > it doesn't find my CDROM (I have two harddrives, both partitioned in FreeBSD 4.0 could not detect my cd either (it is detected under linux) but I could make it do so with a little patch (it still does not work, though). See for more. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Mon Apr 17 5:36:41 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 5A3B137B739 for ; Mon, 17 Apr 2000 05:36:37 -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 OAA10277 for ; Mon, 17 Apr 2000 14:36:31 +0200 (MET DST) Message-Id: <4.1.19990224133006.022808f0@mail.rz.fh-wilhelmshaven.de> X-Sender: ohoyer@mail.rz.fh-wilhelmshaven.de X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1 Date: Wed, 24 Feb 1999 13:32:41 +0100 To: freebsd-hardware@FreeBSD.ORG From: Olaf Hoyer Subject: Re: NEC 260 CDROM detection under FreeBSD 4.0-RELESE/STABLE In-Reply-To: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org At 16:02 17.04.00 +0700, you wrote: >Hello! > >I've been using FreeBSD 3.4 for quite a while, and my CDROM, being quite >old and weird (NEC 260 model) was detected by both BIOS and FreeBSD. > >Recently, I've decided to upgrade to FreeBSD 4.0, and also changed my >motherboad, now it is ASUS TXP4, was latest version of award bios, and now >it doesn't find my CDROM (I have two harddrives, both partitioned in >dedicated mode, one (bootable for FreeBSD) is master with CDROM being >slave on first contoller, another is singe/master on the second; I've >tried moving them around, but it didn't help). I've even tried attaching >CDROM on my sound card's IDE conntector, still unsuccessfully). > >The reason why I am writing this, because when I boot Linux (from >boot/rescue diskettes, for instance), it definitely does find my CDROM! > >Computer specs: genuine intel Pentium 200 MMX, 64M RAM, FreeBSD 4.0, >NE2000-compatible non-PnP ISA NIC on irq 5, MM ISP 16 sound card (ISA >non-PnP) on irq 11, USB IRQ 12, 2 coms, 1 lpt, s3 virge dx/gx on irq >10, two floppy frives on irq 6. I know most of this is useless, but >still, maybe someone will notice some conflicts; I still doubt though. > Hi! Well, could also be a problem with the UDMA modes. lots of non-UDMA capable CD-ROM do not like being on the same port with a HDD that does UDMA and have the mobo drive it with UDMA... Also could be that the electronic is somwhat really weird (they were the first, as ATAPI was quite a fresh thing) and may not behave standard way... Some other SCSI Nec CD-ROMS also did not behaved well (3x-6x) 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 Mon Apr 17 9:16: 5 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from exmta2.rjf.com (exmta2.rjf.com [170.12.31.84]) by hub.freebsd.org (Postfix) with ESMTP id 671E037B79A for ; Mon, 17 Apr 2000 09:16:01 -0700 (PDT) (envelope-from ICartwright@IT.RJF.com) Received: by exmta2.rjf.com with Internet Mail Service (5.5.2448.0) id <2R5PGH36>; Mon, 17 Apr 2000 12:15:56 -0400 Message-ID: <6D5097D4B56AD31190D50008C7B1579B670205@EXLAN5> From: Ian Cartwright To: "'Viren R.Shah'" , "Matthew N. Dodd" Cc: Jonathan Lemon , "FreeBSD Hardware (E-mail)" Subject: RE: cvs commit: src/sys/dev/ida ida_eisa.c Date: Mon, 17 Apr 2000 12:15:48 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2448.0) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org The ida driver now detects the SMART controller and the logical drives on it correctly. However, now I get a page fault immediately after the ida detection. It looks like maybe it's detecting the next eisa card or something though. I'm not sure. Can someone take a look at the output and maybe point me in the right direction? Output: ida0: at 0x7c88-0x7c9e, irq 10 (level) ida0: on eisa0 slot 7 ida0: drives=2 firm_rev=2.26 idad0: 4091MB (8380320 sectors), blocksize=512 idad1: 2000MB (4096320 sectors), blocksize=512 e Fatal trap 12: page fault while in kernel mode fault virtual address = 0xff00015d fault code = supervisor read, page not present instruction pointer = 0x8:0xc0170aa7 stack pointer = 0x10:0xc0602d94 frame pointer = 0x10:0xc0602da0 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, def 32 1, gran 1 processor flags = interrupt enabled, resume, IOPL = 0 current process = 0 (swapper) interrupt mask = net tty bio cam trap number = 12 panic: page fault Uptime: 0s Ian Cartwright Senior Engineer Raymond James Associates icartwright@it.rjf.com -----Original Message----- From: Viren R.Shah [mailto:viren@rstcorp.com] Sent: Sunday, April 16, 2000 9:31 AM To: Matthew N. Dodd Cc: Jonathan Lemon; Ian Cartwright Subject: Re: cvs commit: src/sys/dev/ida ida_eisa.c >>>>> "Matt" == Matthew N Dodd writes: Matt> Ok, I see whats happening. Matt> The EISA IDA boards don't use the lower registers but the register Matt> definitions are defined as offsets from the lower iobase. Matt> Thankfully the IDA drivers is very well written so that the register Matt> access is all contained within the bus front end code. Matt> Jonathan, please review the attached patch before I commit it. You have already committed this patch right (I cvsup every morning at 4am EDT)? I compiled a kernel after today morning's cvsup, and it booted and found the ida controller and sysinstall again found the exising slices on the RAID array (4 1G drives RAID'ed into a 3G partition *grin*). After I backup everything I need from the Compaq box, I'll go further and reinstall from a new snap (whenever one is available). Matt> Viren, thanks alot for your good debuging and shedding light on the Matt> problem. No problem, it has already given me a slightly better understanding of the device driver framework. Thanks, both of you, for getting the driver working. Ian, does it work for you? Viren -- Viren R. Shah Man's Greatest Asset is... ...an unsettled mind To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Mon Apr 17 12: 4:56 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id CE9C937B824; Mon, 17 Apr 2000 12:04:54 -0700 (PDT) (envelope-from kris@FreeBSD.org) Received: from localhost (kris@localhost) by freefall.freebsd.org (8.9.3/8.9.2) with ESMTP id MAA51665; Mon, 17 Apr 2000 12:04:54 -0700 (PDT) (envelope-from kris@FreeBSD.org) X-Authentication-Warning: freefall.freebsd.org: kris owned process doing -bs Date: Mon, 17 Apr 2000 12:04:54 -0700 (PDT) From: Kris Kennaway To: "Alexey N. Dokuchaev" Cc: freebsd-hardware@freebsd.org Subject: Re: NEC 260 CDROM detection under FreeBSD 4.0-RELESE/STABLE 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 Mon, 17 Apr 2000, Alexey N. Dokuchaev wrote: > Hello! > > I've been using FreeBSD 3.4 for quite a while, and my CDROM, being quite > old and weird (NEC 260 model) was detected by both BIOS and FreeBSD. You didn't post your kernel config file..do you have "device atapicd" there? Kris ---- In God we Trust -- all others must submit an X.509 certificate. -- Charles Forsythe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Mon Apr 17 15:57:46 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 BC84F37BC6E for ; Mon, 17 Apr 2000 15:57:41 -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 AAA28822 for ; Tue, 18 Apr 2000 00:57:36 +0200 (MET DST) Message-Id: <4.1.19990224233855.0227e690@mail.rz.fh-wilhelmshaven.de> X-Sender: ohoyer@mail.rz.fh-wilhelmshaven.de X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1 Date: Wed, 24 Feb 1999 23:45:27 +0100 To: freebsd-hardware@freebsd.org From: Olaf Hoyer Subject: RE: thermal grease? In-Reply-To: <8070C3A4E99ED211A63200105A19B99B31763E@mail.edifecs.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org At 14:17 17.04.00 -0700, you wrote: >> Well, not that odd... Most of that part is used to put >> between transistors >> and their heatsink befor they are screwed together... So any >> electronic >> shop should carry that... >> CPU is not that wide application field. >> >> But, unless you are running a very stressed CPU (24h/7day server use, >> overclocked thingie or highest-end one like Athlon 1 GHz) >> then in normal >> cases you can leave out the thermal grease. Most coolers >> nowadays have some >> plastiv sheet under them that also helps in distributing the >> energy from >> CPU to cooler, and also prevents direct metal contact, which >> is helpful in >> case of power spikes... >> >> For real hard-core overclockers, there is special silver grease... > >I disagree. You should ALWAYS use thermal grease. It will result in a >better, more reliable heat transfer area. Overclocking or not. > >You can buy it off the web from just about anywhere that sells CPUs or heat >sinks. You can also get it at Radio Shack. Maybe yours was out of stock. Hi! Well, of course it runs better with thermal grease applied, no question. Of course it is more reliable, no doubt about that. But it is common practice to leave that out in most low-end-user PCs, that will only see some M$ OS and small stuff... (so no real stress) The heatsinks placed on that machines suffice in most cases, having far more heat dissipating capacity than the CPU is able to produce, so in most cases it is sufficient. Of course, if you use a real OS, that is really been used, one should care about overall reliability of all parts... ;-) 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 Mon Apr 17 19:17:30 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from linux.ssc.nsu.ru (linux.ssc.nsu.ru [193.124.219.91]) by hub.freebsd.org (Postfix) with SMTP id 11CE237B64F for ; Mon, 17 Apr 2000 19:16:48 -0700 (PDT) (envelope-from danfe@inet.ssc.nsu.ru) Received: (qmail 7579 invoked from network); 18 Apr 2000 02:16:24 -0000 Received: from inet.ssc.nsu.ru (62.76.110.12) by hub.freebsd.org with SMTP; 18 Apr 2000 02:16:24 -0000 Received: from localhost (danfe@localhost) by inet.ssc.nsu.ru (8.9.3/8.9.3) with ESMTP id JAA04949; Tue, 18 Apr 2000 09:15:23 +0700 Date: Tue, 18 Apr 2000 09:15:23 +0700 (NOVST) From: "Alexey N. Dokuchaev" To: Kris Kennaway Cc: freebsd-hardware@FreeBSD.org Subject: Re: NEC 260 CDROM detection under FreeBSD 4.0-RELESE/STABLE 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 Mon, 17 Apr 2000, Kris Kennaway wrote: > On Mon, 17 Apr 2000, Alexey N. Dokuchaev wrote: > > > Hello! > > > > I've been using FreeBSD 3.4 for quite a while, and my CDROM, being quite > > old and weird (NEC 260 model) was detected by both BIOS and FreeBSD. > > You didn't post your kernel config file..do you have "device > atapicd" there? > Sure I do. I have "device ata\ndevice atadisk\ndevice atapicd". Cheers, /* Alexey N. Dokuchaev, more commonly | */ /* known as DAN Fe | mailto:danfe@inet.ssc.nsu.ru */ /* | ICQ UIN: 38934845 */ /* Novosibirsk State University | http://inet.ssc.nsu.ru/~danfe/ */ /* Scientific Study Center Computer Lab | */ [Team Assembler] [Team BSD] [Team DooM] [Team Quake] -----BEGIN GEEK CODE BLOCK----- Version: 3.12 GCS d-@ s+: a--- C++(+++) UBL++++$ P++>$ L+ E-- W++ N++ o? K? w-- O- M V- PS PE Y+ PGP+ t+ 5+ X+ R- !tv b++ DI+ D+++ G++ e h !r !y+ ------END GEEK CODE BLOCK------ Microsoft: Where do you want to go today? Linux: Where do you want to go tomorrow? FreeBSD: Are you guys coming or what? Microsoft: What are we going to rip off today and claim as our own? Microsoft: Where do you want to be taken today? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Tue Apr 18 11:34: 8 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from sammy.tibco.com (sammy.tibco.com [192.216.111.146]) by hub.freebsd.org (Postfix) with ESMTP id EEC2937BB00 for ; Tue, 18 Apr 2000 11:33:55 -0700 (PDT) (envelope-from aram@tibco.com) Received: from osgood.tibco.com (osgood.tibco.com [160.101.240.42]) by sammy.tibco.com (8.9.3/8.9.3) with ESMTP id LAA04230 for ; Tue, 18 Apr 2000 11:33:47 -0700 (PDT) Received: from venus.tibco.com (venus.tibco.com [160.101.240.40]) by osgood.tibco.com (8.9.3/8.9.3) with ESMTP id LAA11199 for ; Tue, 18 Apr 2000 11:36:17 -0700 (PDT) Received: from tibco.com ([160.101.22.192]) by venus.tibco.com (Netscape Messaging Server 3.6) with ESMTP id AAA555C; Tue, 18 Apr 2000 11:25:03 -0700 Message-ID: <38FCA917.6E75ADDD@tibco.com> Date: Tue, 18 Apr 2000 11:27:35 -0700 From: "Aram Compeau" X-Mailer: Mozilla 4.72 [en] (WinNT; U) X-Accept-Language: en MIME-Version: 1.0 To: Brandon DeYoung Cc: FreeBSDHW Subject: Re: RAID & FreeBSD References: <00e601bfa399$a6f8a4e0$0101a8c0@austin.rr.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org You always have the choice of using SCSI-SCSI RAID as well... A great thing, but somewhat pricey. Aram Brandon DeYoung wrote: > Is there a "best" RAID solution for Free BSD? > I just set up two new database servers and like a true coward installed > Linux on them (RedHat 6.1 using software RAID). I did this because it > appears that the only hardware controllers supported by Free BSD are DPT's > SmartRAID I-IV which, though available, don't appear to be manufactured any > longer. Is there a software RAID option for FreeBSD that I was unable to > find? > Any and all suggestions and experiences anyone is willing to share would > be greatly appreciated. > > ~Brandon > > 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 18 18:21:39 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 DEBE137B668 for ; Tue, 18 Apr 2000 18:21:36 -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 TAA19421 for ; Tue, 18 Apr 2000 19:22:23 -0600 (CST) (envelope-from ryan@sasknow.com) Date: Tue, 18 Apr 2000 19:22:23 -0600 (CST) From: Ryan Thompson To: freebsd-hardware@freebsd.org Subject: FPGA solutions? 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 Hi all, Has anyone had any experiences (good or bad) with any FPGA boards under FreeBSD? I want to cheaply implement a circuit of about 15,000 gates, but don't know what hardware is available, and what interfaces are supported under FreeBSD, if any work has been done in this area. CAD software that runs under FreeBSD would be nice as well :-) I've scoured the mailing lists for obvious keywords, but didn't turn up very much. If anyone has any information on the availability (and approximate pricing) of the hardware, I would appreciate any information! I hail from Western Canada, but, if necessary, I can ship from the US. Thanks - Ryan -- 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 Wed Apr 19 7:19:18 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from unicap.br (email.unicap.br [200.133.2.209]) by hub.freebsd.org (Postfix) with ESMTP id 0BA1C37B58D for ; Wed, 19 Apr 2000 07:19:12 -0700 (PDT) (envelope-from luciano@unicap.br) Received: from unicap.br (sirimole.unicap.br [200.133.2.220]) by unicap.br (AIX4.3/UCB 8.8.8/1) with ESMTP id LAA10436 for ; Wed, 19 Apr 2000 11:18:49 -0300 Message-ID: <38FDCCFF.19111882@unicap.br> Date: Wed, 19 Apr 2000 12:13:03 -0300 From: Luciano de Oliveira X-Mailer: Mozilla 4.6 [en] (X11; I; AIX 4.2) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-hardware@freebsd.org Subject: drivers hp scsi Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi everybody, Do you know if there's any support do drivers AIC7870, and AIC7830. These are adaptec drivers? if there's linux support for the server, it can be supported on freebsd? the model of the server is lc2000r. Tks to all. -- ********************************************************** _/ _/ _/ _/ _/ _/_/_/_/ _/_/_/_/ _/_/_/_/ _/ _/ _/_/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/_/ _/ _/ _/_/_/_/ _/_/_/_/ _/_/_/_/ _/ _/ _/ _/_/_/_/ _/ _/ _/ Universidade Catolica de Pernambuco Nucleo de Informatica e Computacao Luciano de Oliveira Eng. Eletronico Especialista em Tecnologia da Informacao luciano@unicap.br 55-081-2164272/2164139 ********************************************************** To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Wed Apr 19 9:55:38 2000 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 0BC8237BCD7 for ; Wed, 19 Apr 2000 09:55:33 -0700 (PDT) (envelope-from ken@panzer.kdm.org) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id KAA06825; Wed, 19 Apr 2000 10:54:12 -0600 (MDT) (envelope-from ken) Date: Wed, 19 Apr 2000 10:54:12 -0600 From: "Kenneth D. Merry" To: Luciano de Oliveira Cc: freebsd-hardware@FreeBSD.ORG Subject: Re: drivers hp scsi Message-ID: <20000419105412.A6809@panzer.kdm.org> References: <38FDCCFF.19111882@unicap.br> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <38FDCCFF.19111882@unicap.br>; from luciano@unicap.br on Wed, Apr 19, 2000 at 12:13:03PM -0300 Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Wed, Apr 19, 2000 at 12:13:03 -0300, Luciano de Oliveira wrote: > Hi everybody, > Do you know if there's any support do drivers AIC7870, > and AIC7830. These are adaptec drivers? if there's linux > support for the server, it can be supported on freebsd? > the model of the server is lc2000r. The AIC 7870 and 7880 are supported by the ahc driver. There is no such thing as an AIC 7830. 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 Apr 19 13:14:30 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from queeg.ludd.luth.se (queeg.ludd.luth.se [130.240.16.109]) by hub.freebsd.org (Postfix) with ESMTP id 3B8A337BD26 for ; Wed, 19 Apr 2000 13:14:27 -0700 (PDT) (envelope-from max@ludd.luth.se) Received: from speedy.ludd.luth.se (root@speedy.ludd.luth.se [130.240.16.164]) by queeg.ludd.luth.se (8.9.3/8.9.3) with ESMTP id WAA03725; Wed, 19 Apr 2000 22:14:06 +0200 (CEST) Received: (max@localhost) by speedy.ludd.luth.se (8.8.8/8.6.11) id WAA28040; Wed, 19 Apr 2000 22:14:06 +0200 (CEST) Date: Wed, 19 Apr 2000 22:14:06 +0200 From: Max Nilsson To: Ryan Thompson , freebsd-hardware@FreeBSD.ORG Cc: freebsd-hardware@FreeBSD.ORG Subject: Re: FPGA solutions? Message-ID: <20000419221406.A27809@ludd.luth.se> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0us In-Reply-To: ; from ryan@sasknow.com on Tue, Apr 18, 2000 at 07:22:23PM -0600 Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hello. FreeBSD-current (maybe also FreeBSD4.0 and older ?) has support for the HOT1 FPGA-card from VCC (http://www.vcc.com). The board uses a Xilinx 6200 FPGA. The device name is 'xrpu' in LINT. You can find some free CAD software in /usr/ports/cad/ /Max On Tue, Apr 18, 2000 at 07:22:23PM -0600, Ryan Thompson wrote: > > Hi all, > > Has anyone had any experiences (good or bad) with any FPGA boards under > FreeBSD? I want to cheaply implement a circuit of about 15,000 gates, but > don't know what hardware is available, and what interfaces are supported > under FreeBSD, if any work has been done in this area. CAD software that > runs under FreeBSD would be nice as well :-) > > I've scoured the mailing lists for obvious keywords, but didn't turn up > very much. > > If anyone has any information on the availability (and approximate > pricing) of the hardware, I would appreciate any information! I hail from > Western Canada, but, if necessary, I can ship from the US. > > Thanks > > - Ryan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Wed Apr 19 23:15:21 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from ns1.networkiowa.com (ns1.networkiowa.com [209.234.64.192]) by hub.freebsd.org (Postfix) with ESMTP id 17A3F37BDC9 for ; Wed, 19 Apr 2000 23:15:16 -0700 (PDT) (envelope-from johnl@raccoon.com) Received: from raccoon.com (dsl.72.145.networkiowa.com [209.234.72.145]) by ns1.networkiowa.com (8.9.3/8.9.3) with ESMTP id BAA20216 for ; Thu, 20 Apr 2000 01:18:38 -0500 Message-ID: <38FEA079.7D69CF34@raccoon.com> Date: Thu, 20 Apr 2000 01:15:22 -0500 From: John Lengeling X-Mailer: Mozilla 4.7 [en] (Win98; I) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-hardware@freebsd.org Subject: Support for PCI parallel port cards? Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org i have a generic PCI PNP parallel port card which I would like to setup as lpt1 for a printer. Does FreeBSD 4.0-RELEASE support pnp PCI parallel port cards? Any one working on support for one? johnl To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Thu Apr 20 4:30:41 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 46EC837BC92; Thu, 20 Apr 2000 04:30:36 -0700 (PDT) (envelope-from matrix@chat.ru) Received: from wp1 (IRM-1-01.dialup.tsr.ru [195.208.67.129]) by Wheel.TSR.Ru (8.10.1may/TELECORE-1.1) with SMTP id e3KBU5f10408; Thu, 20 Apr 2000 15:30:05 +0400 (MSD) envelope from matrix@chat.ru Message-ID: <002e01bfaabb$d4629520$0c00a8c0@ipform.ru> From: "Artem Koutchine" To: Cc: Subject: IDE RAID (Adaptec one) Date: Thu, 20 Apr 2000 15:24:15 +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 Adaptec now offers a IDE RAID 5 controller and i just was wondering if it works fine with freebsd and will it outperform a single big SCSI drive ( i mean speed, not capacity). Artem To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Thu Apr 20 4:30:51 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 CF1F437B6E8; Thu, 20 Apr 2000 04:30:35 -0700 (PDT) (envelope-from matrix@chat.ru) Received: from wp1 (IRM-1-01.dialup.tsr.ru [195.208.67.129]) by Wheel.TSR.Ru (8.10.1may/TELECORE-1.1) with SMTP id e3KBU7f10417; Thu, 20 Apr 2000 15:30:08 +0400 (MSD) envelope from matrix@chat.ru Message-ID: <002f01bfaabb$d5e31aa0$0c00a8c0@ipform.ru> From: "Artem Koutchine" To: Cc: Subject: Ultra 160 AHA controller on 3.4? Date: Thu, 20 Apr 2000 15:24:21 +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 Does anybody use one of those on 3.4? Does 3.4 even support any Ultra 160 controller? Artem To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Thu Apr 20 4:30:54 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 F110437BD76; Thu, 20 Apr 2000 04:30:40 -0700 (PDT) (envelope-from matrix@chat.ru) Received: from wp1 (IRM-1-01.dialup.tsr.ru [195.208.67.129]) by Wheel.TSR.Ru (8.10.1may/TELECORE-1.1) with SMTP id e3KBU3f10375; Thu, 20 Apr 2000 15:30:03 +0400 (MSD) envelope from matrix@chat.ru Message-ID: <002d01bfaabb$d3453e40$0c00a8c0@ipform.ru> From: "Artem Koutchine" To: Cc: Subject: Motherborad/Memory/CPU for web hosting system Date: Thu, 20 Apr 2000 15:24:06 +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 Hi! I am trying to pick a hardware config for a server which must hosts dozens of web server. It is going to be a commercial hosting and i picked FreeBSD as OS because of many personal reasons:) Now i must pick some x86 compat platform hardware. What I am thinking about right now is : Asus P2B-LS motherboard, Pentium III above 500, 512MB ram, 1 SCSI 10GB, 1 SCSI 30GB, 1 UDMA IDE AS BIG AS IT CAN BE for backup. The main problem is the motherboard. I just don't see any alternative and that;s bad. I'd like to have a choice. It seems like the newer i820 bases motherboards from Asus have SCSI contrller Ultra160 which is not supported by 3.4 ( i'd rather no go with 4.0). But on the other hand BX is kind old now. If you have some experience with hosting a lot of web servers, please, share the hardware config with me. Artem To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Thu Apr 20 4:44:37 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id 36E8537B564; Thu, 20 Apr 2000 04:44:21 -0700 (PDT) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id NAA96256; Thu, 20 Apr 2000 13:42:12 +0200 (CEST) (envelope-from sos) From: Soren Schmidt Message-Id: <200004201142.NAA96256@freebsd.dk> Subject: Re: NEC 260 CDROM detection under FreeBSD 4.0-RELESE/STABLE In-Reply-To: from "Alexey N. Dokuchaev" at "Apr 17, 2000 04:02:32 pm" To: danfe@inet.ssc.nsu.ru (Alexey N. Dokuchaev) Date: Thu, 20 Apr 2000 13:42:12 +0200 (CEST) Cc: freebsd-hackers@FreeBSD.ORG, freebsd-hardware@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org It seems Alexey N. Dokuchaev wrote: > Hello! > > I've been using FreeBSD 3.4 for quite a while, and my CDROM, being quite > old and weird (NEC 260 model) was detected by both BIOS and FreeBSD. Judging on the output it seems the NEC is one of the old devices that doesn't say its a CDROM... Try this patch: Index: atapi-all.c =================================================================== RCS file: /home/ncvs/src/sys/dev/ata/atapi-all.c,v retrieving revision 1.51 diff -u -r1.51 atapi-all.c --- atapi-all.c 2000/04/18 15:15:02 1.51 +++ atapi-all.c 2000/04/20 09:41:58 @@ -93,6 +93,7 @@ switch (ATP_PARAM->device_type) { #if NATAPICD > 0 case ATAPI_TYPE_CDROM: +try_cdrom: if (acdattach(atp)) goto notfound; break; @@ -100,7 +101,12 @@ #if NATAPIFD > 0 case ATAPI_TYPE_DIRECT: if (afdattach(atp)) +#if NATAPICD > 0 + ATP_PARAM->device_type = ATAPI_TYPE_CDROM; + goto try_cdrom; +#else goto notfound; +#endif break; #endif #if NATAPIST > 0 -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Thu Apr 20 5:59:58 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 E97EB37BDD7 for ; Thu, 20 Apr 2000 05:59:54 -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 OAA17646; Thu, 20 Apr 2000 14:56:20 +0200 (MET DST) Message-Id: <4.1.20000420143901.00a516d0@mail.rz.fh-wilhelmshaven.de> X-Sender: ohoyer@mail.rz.fh-wilhelmshaven.de X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1 Date: Thu, 20 Apr 2000 14:53:03 +0200 To: "Artem Koutchine" From: Olaf Hoyer Subject: Re: Motherborad/Memory/CPU for web hosting system Cc: freebsd-hardware@freebsd.org In-Reply-To: <002d01bfaabb$d3453e40$0c00a8c0@ipform.ru> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org At 15:24 20.04.00 +0400, you wrote: >Hi! > >I am trying to pick a hardware config for a server which must hosts >dozens of web server. It is going to be a commercial hosting and >i picked FreeBSD as OS because of many personal reasons:) Now >i must pick some x86 compat platform hardware. > >What I am thinking about right now is : Asus P2B-LS motherboard, >Pentium III above 500, 512MB ram, 1 SCSI 10GB, 1 SCSI 30GB, >1 UDMA IDE AS BIG AS IT CAN BE for backup. The main problem >is the motherboard. I just don't see any alternative and that;s bad. I'd >like >to have a choice. It seems like the newer i820 bases motherboards from Asus >have SCSI contrller Ultra160 which is not supported by 3.4 ( i'd rather no >go with 4.0). But on the other hand BX is kind old now. Hi! Well, I don't know which brands are available in your area, but there is plenty of stuff available. I'd prefer for servers the BX and Gx chipsets, because they are stable, and proven. They have their edges ironed out, and have proven under stress. Forget any Intel 8xx chipset right now, they are troublemakers. Asus is one of the best brands, but there shall be Intel (their server boards are fine), Tyan, Gigabyte. Those boards also shall be available. The dual boards from Tyan and Gigabyte also ship with U2W SCSI controllers, I also heard rumors that in near future a 160 controller will be onboard. Also SMP should be regarded when dealing with multiple requests, also multiple NICs shall be taken into account, for load balancingm issues. So the CPUs can distribute some of the load. Also a RAID (as option with an adapter on those boards) can enhance performance and overall stability. Big IDE for backup is IMO not that good idea. In case of hardware crash (power spike or so) you also lose that disc. For backups use only removable media, such as streamer, MO-drives (the newer ones hold also more than 2 GB) etc. Or you go for a hot-swap capable HDD (means SCSI) in a removable frame for backup use. Store your backups at another location than your server. I also heard reports (a sysadmin at Springer Verlag in Berlin) that the P2B-LS is not that fast, because they mapped the (whether LAN or SCSI) on the last PCI if I remember correctly. Therefore performance wasn't that good. If you want, I may pick up some model numbers from Gigabyte and TYan and send it via PM. 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 Thu Apr 20 9:20:30 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from Ilsa.StevesCafe.com (Ilsa.StevesCafe.com [206.168.13.65]) by hub.freebsd.org (Postfix) with ESMTP id D11E837B8FE for ; Thu, 20 Apr 2000 09:20:27 -0700 (PDT) (envelope-from fbsd@Ilsa.StevesCafe.com) Received: from Ilsa.StevesCafe.com (localhost [127.0.0.1]) by Ilsa.StevesCafe.com (8.9.3/8.9.3) with ESMTP id KAA75266; Thu, 20 Apr 2000 10:18:26 -0600 (MDT) (envelope-from fbsd@Ilsa.StevesCafe.com) Message-Id: <200004201618.KAA75266@Ilsa.StevesCafe.com> X-Mailer: exmh version 2.0.2 2/24/98 From: Steve Passe To: Olaf Hoyer Cc: "Artem Koutchine" , freebsd-hardware@FreeBSD.ORG Subject: Re: Motherborad/Memory/CPU for web hosting system In-reply-to: Your message of "Thu, 20 Apr 2000 14:53:03 +0200." <4.1.20000420143901.00a516d0@mail.rz.fh-wilhelmshaven.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 20 Apr 2000 10:18:26 -0600 Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi, There is a SEVERE shortage of 100MHz fsb cpus in the channel right now. When buying a motherboard of the BX/GX class, be sure that you can get a cpu for it. We've had to send 133MHz fsb cpus back several times now as dealers are either clueless about the differences, or are hoping to get away with it... -- Steve Passe | powered by smp@csn.net | Symmetric MultiProcessor FreeBSD To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Thu Apr 20 9:28:51 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from sasami.jurai.net (sasami.jurai.net [63.67.141.99]) by hub.freebsd.org (Postfix) with ESMTP id 3CC0A37B702 for ; Thu, 20 Apr 2000 09:28:47 -0700 (PDT) (envelope-from winter@jurai.net) Received: from localhost (winter@localhost) by sasami.jurai.net (8.9.3/8.8.7) with ESMTP id MAA90877; Thu, 20 Apr 2000 12:28:42 -0400 (EDT) Date: Thu, 20 Apr 2000 12:28:42 -0400 (EDT) From: "Matthew N. Dodd" To: "Viren R.Shah" Cc: Jonathan Lemon , Ian Cartwright , freebsd-hardware@freebsd.org Subject: Re: ida driver (Re: cvs commit: src/sys/dev/ida ida_eisa.c) In-Reply-To: <14591.5517.454232.897127@jabberwock.rstcorp.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've got a patch for problem #2. You can get it at: ftp://ftp.jurai.net/users/winter/tmp/idad.patch On Thu, 20 Apr 2000, Viren R.Shah wrote: > Just a report on the ida driver: > > I installed a recent (0418) -current SNAP on my Compaq ProLiant box, > and it worked just fine, except for 2 issues: > > 1. I did what I usually do, and customized the kernel to remove all > the devices that were not present, and that new kernel would not > boot -- paniced right after detecting ida0. I'm currently trying to > resolve that issue by gradually removing devices and booting to > find out which devices it needs that I thought it didn't. > > 2. The loader won't boot from the idad0s1a device. Here's the boot > log: > > ida0: ignoring completion 1000 > no devsw (majdev=0 bootdev=0xa0200000) > Mounting root from ufs:/dev/idad0s1a > no such device 'idad' > setrootbyname failed > ffs_mountroot: can't find rootvp > Root mount failed: 6 > > Manual root filesystem specification: > : Mount using filesystem > eg. ufs:/dev/da0s1a > ? List valid disk boot devices > Abort manual input > > mountroot> ufs:/dev/id0s1a > Mounting root from ufs:/dev/id0s1a > > > > The weird thing is that the id0s1a device isn't even present in the > /dev directory. > The ida devices present in /dev are (ls -la /dev/id* ): > > > > crw-r----- 1 root operator 109, 0x00010002 Apr 19 09:17 /dev/idad0 > crw-r----- 1 root operator 109, 0 Apr 19 09:17 /dev/idad0a > crw-r----- 1 root operator 109, 1 Apr 19 09:17 /dev/idad0b > crw-r----- 1 root operator 109, 2 Apr 19 09:17 /dev/idad0c > crw-r----- 1 root operator 109, 3 Apr 19 09:17 /dev/idad0d > crw-r----- 1 root operator 109, 4 Apr 19 09:17 /dev/idad0e > crw-r----- 1 root operator 109, 5 Apr 19 09:17 /dev/idad0f > crw-r----- 1 root operator 109, 6 Apr 19 09:17 /dev/idad0g > crw-r----- 1 root operator 109, 7 Apr 19 09:17 /dev/idad0h > crw-r----- 1 root operator 109, 0x00020002 Apr 20 09:36 /dev/idad0s1 > crw-r----- 1 root operator 109, 0x00020000 Apr 20 09:36 /dev/idad0s1a > crw-r----- 1 root operator 109, 0x00020001 Apr 20 09:36 /dev/idad0s1b > crw-r----- 1 root operator 109, 0x00020002 Apr 20 09:36 /dev/idad0s1c > crw-r----- 1 root operator 109, 0x00020003 Apr 20 09:36 /dev/idad0s1d > crw-r----- 1 root operator 109, 0x00020004 Apr 20 09:36 /dev/idad0s1e > crw-r----- 1 root operator 109, 0x00020005 Apr 20 09:36 /dev/idad0s1f > crw-r----- 1 root operator 109, 0x00020006 Apr 20 09:36 /dev/idad0s1g > crw-r----- 1 root operator 109, 0x00020007 Apr 20 09:36 /dev/idad0s1h > crw-r----- 1 root operator 109, 0x00030002 Apr 19 09:17 /dev/idad0s2 > crw-r----- 1 root operator 109, 0x00030000 Apr 18 15:35 /dev/idad0s2a > crw-r----- 1 root operator 109, 0x00030001 Apr 18 15:35 /dev/idad0s2b > crw-r----- 1 root operator 109, 0x00030002 Apr 18 15:35 /dev/idad0s2c > crw-r----- 1 root operator 109, 0x00030003 Apr 18 15:35 /dev/idad0s2d > crw-r----- 1 root operator 109, 0x00030004 Apr 18 15:35 /dev/idad0s2e > crw-r----- 1 root operator 109, 0x00030005 Apr 18 15:35 /dev/idad0s2f > crw-r----- 1 root operator 109, 0x00030006 Apr 18 15:35 /dev/idad0s2g > crw-r----- 1 root operator 109, 0x00030007 Apr 18 15:35 /dev/idad0s2h > crw-r----- 1 root operator 109, 0x00040002 Apr 19 09:17 /dev/idad0s3 > crw-r----- 1 root operator 109, 0x00050002 Apr 19 09:17 /dev/idad0s4 > > > Viren > -- | Matthew N. Dodd | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD | | winter@jurai.net | 2 x '84 Volvo 245DL | ix86,sparc,pmax | | http://www.jurai.net/~winter | This Space For Rent | ISO8802.5 4ever | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Thu Apr 20 10:44:46 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from mass.cdrom.com (adsl-63-202-177-62.dsl.snfc21.pacbell.net [63.202.177.62]) by hub.freebsd.org (Postfix) with ESMTP id 109A837B660; Thu, 20 Apr 2000 10:44:42 -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 KAA00784; Thu, 20 Apr 2000 10:50:19 -0700 (PDT) (envelope-from msmith@mass.cdrom.com) Message-Id: <200004201750.KAA00784@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: "Artem Koutchine" Cc: questions@freebsd.org, hardware@freebsd.org Subject: Re: IDE RAID (Adaptec one) In-reply-to: Your message of "Thu, 20 Apr 2000 15:24:15 +0400." <002e01bfaabb$d4629520$0c00a8c0@ipform.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 20 Apr 2000 10:50:18 -0700 From: Mike Smith Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > Adaptec now offers a IDE RAID 5 controller and i just was wondering if > it works fine with freebsd and will it outperform a single big SCSI drive > ( i mean speed, not capacity). It's impossible to tell, but I would expect that, being another product of Adaptec's RAID division, documentation is going to be impossible to obtain, and thus there will be no driver support. If anyone has any more data, I'd love to hear about it, but right now I'm not very optomistic. -- \\ 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 Thu Apr 20 11:14:47 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from mass.cdrom.com (adsl-63-202-177-62.dsl.snfc21.pacbell.net [63.202.177.62]) by hub.freebsd.org (Postfix) with ESMTP id 77ED537BE9F for ; Thu, 20 Apr 2000 11:14:44 -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 LAA00941; Thu, 20 Apr 2000 11:21:36 -0700 (PDT) (envelope-from msmith@mass.cdrom.com) Message-Id: <200004201821.LAA00941@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: John Lengeling Cc: freebsd-hardware@freebsd.org Subject: Re: Support for PCI parallel port cards? In-reply-to: Your message of "Thu, 20 Apr 2000 01:15:22 CDT." <38FEA079.7D69CF34@raccoon.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 20 Apr 2000 11:21:36 -0700 From: Mike Smith Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > i have a generic PCI PNP parallel port card which I would like to setup > as lpt1 for a printer. Does FreeBSD 4.0-RELEASE support pnp PCI > parallel port cards? Any one working on support for one? I don't know of anyone doing this, no. You'd probably be better off just getting a USB:Parallel cable at this point in time. -- \\ 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 Thu Apr 20 11:17:20 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from portnoy.lbl.gov (portnoy.lbl.gov [131.243.2.11]) by hub.freebsd.org (Postfix) with ESMTP id 1F3B237BE23; Thu, 20 Apr 2000 11:17:15 -0700 (PDT) (envelope-from jin@portnoy.lbl.gov) Received: (from jin@localhost) by george.lbl.gov () id LAA01940; Thu, 20 Apr 2000 11:17:14 -0700 (PDT) Date: Thu, 20 Apr 2000 11:17:14 -0700 (PDT) From: Jin Guojun (FTG staff) Message-Id: <200004201817.LAA01940@george.lbl.gov> To: matrix@chat.ru, msmith@FreeBSD.ORG Subject: Re: IDE RAID (Adaptec one) Cc: hardware@FreeBSD.ORG, questions@FreeBSD.ORG Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > Adaptec now offers a IDE RAID 5 controller and i just was wondering if > > it works fine with freebsd and will it outperform a single big SCSI drive > > ( i mean speed, not capacity). > > It's impossible to tell, but I would expect that, being another product > of Adaptec's RAID division, documentation is going to be impossible to > obtain, and thus there will be no driver support. > > If anyone has any more data, I'd love to hear about it, but right now I'm > not very optomistic. I do not know Adaptec one, but I know 3ware has something similar. We asked them for an evaluation board (retail is about $270) and come with linux driver source. It works quite well under linux. It can be configured as 2x2 stripe, 1x4 stripe (RAID1), and mirror (RAID0). The 2x2 stripe can have 32MBps I/O rate which is not bad at all. Four 45GB WDC IDE drives are $1000, plus a $270 IDE controller, you can get total 180GB with 32MBps I/O at $1300 which is half price of the same configuration for SCSI. The driver code is about 16K, but requires many linux header files. I do not have time to poke Linux syuff at this moment. If some one is interested in it, driver source can be download from www.3ware.com. -Jin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Thu Apr 20 11:23:16 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from mass.cdrom.com (adsl-63-202-177-62.dsl.snfc21.pacbell.net [63.202.177.62]) by hub.freebsd.org (Postfix) with ESMTP id 8EA1037B660; Thu, 20 Apr 2000 11:23:12 -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 LAA01011; Thu, 20 Apr 2000 11:30:07 -0700 (PDT) (envelope-from msmith@mass.cdrom.com) Message-Id: <200004201830.LAA01011@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Jin Guojun (FTG staff) Cc: hardware@FreeBSD.ORG, questions@FreeBSD.ORG Subject: Re: IDE RAID (Adaptec one) In-reply-to: Your message of "Thu, 20 Apr 2000 11:17:14 PDT." <200004201817.LAA01940@george.lbl.gov> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 20 Apr 2000 11:30:07 -0700 From: Mike Smith Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > I do not know Adaptec one, but I know 3ware has something similar. > We asked them for an evaluation board (retail is about $270) and come with > linux driver source. It works quite well under linux. It can be configured > as 2x2 stripe, 1x4 stripe (RAID1), and mirror (RAID0). The 2x2 stripe can > have 32MBps I/O rate which is not bad at all. > Four 45GB WDC IDE drives are $1000, plus a $270 IDE controller, you can > get total 180GB with 32MBps I/O at $1300 which is half price of the same > configuration for SCSI. Note that this controller doesn't support RAID 5 or hotswap. > The driver code is about 16K, but requires many linux header files. > I do not have time to poke Linux syuff at this moment. If some one is > interested in it, driver source can be download from www.3ware.com. I have one in the lab, and am working on a driver. It's next in the queue behind the ICP Vortex cards at the moment. -- \\ 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 Thu Apr 20 11:49:20 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from vcnet.com (mail.vcnet.com [209.239.239.15]) by hub.freebsd.org (Postfix) with SMTP id 671CA37B70C for ; Thu, 20 Apr 2000 11:49:15 -0700 (PDT) (envelope-from jpr@vcnet.com) Received: (qmail 28211 invoked from network); 20 Apr 2000 18:49:15 -0000 Received: from joff.vc.net (HELO ?209.239.239.22?) (209.239.239.22) by mail.vcnet.com with SMTP; 20 Apr 2000 18:49:15 -0000 Mime-Version: 1.0 Message-Id: In-Reply-To: <002d01bfaabb$d3453e40$0c00a8c0@ipform.ru> References: <002d01bfaabb$d3453e40$0c00a8c0@ipform.ru> Date: Thu, 20 Apr 2000 11:49:17 -0700 To: "Artem Koutchine" , From: Jon Rust Subject: Re: Motherborad/Memory/CPU for web hosting system Cc: Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Get a dual if you can. The SMP code works very well, and you'll be happy you did when the server starts getting busy (especially with DB lookups if you do them). I wouldn't be afriad of 4.0. The FreeBSD development team kicks butt, and they've had quite a while to work the bugs out. Is it bug free? No. For my purposes, 4.0-S appears to be as bug free as 3.4-S. Just my 2 cents... jon At 3:24 PM +0400 4/20/00, Artem Koutchine wrote: >Hi! > >I am trying to pick a hardware config for a server which must hosts >dozens of web server. It is going to be a commercial hosting and >i picked FreeBSD as OS because of many personal reasons:) Now >i must pick some x86 compat platform hardware. > >What I am thinking about right now is : Asus P2B-LS motherboard, >Pentium III above 500, 512MB ram, 1 SCSI 10GB, 1 SCSI 30GB, >1 UDMA IDE AS BIG AS IT CAN BE for backup. The main problem >is the motherboard. I just don't see any alternative and that;s bad. I'd >like >to have a choice. It seems like the newer i820 bases motherboards from Asus >have SCSI contrller Ultra160 which is not supported by 3.4 ( i'd rather no >go with 4.0). But on the other hand BX is kind old now. > >If you have some experience with hosting a lot of web servers, please, share >the hardware config with me. > >Artem To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Thu Apr 20 12: 1:40 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from exmta2.rjf.com (exmta2.rjf.com [170.12.31.84]) by hub.freebsd.org (Postfix) with ESMTP id 44D8837B81E for ; Thu, 20 Apr 2000 12:01:32 -0700 (PDT) (envelope-from ICartwright@IT.RJF.com) Received: by exmta2.rjf.com with Internet Mail Service (5.5.2448.0) id <2R5PHQV6>; Thu, 20 Apr 2000 15:01:30 -0400 Message-ID: <6D5097D4B56AD31190D50008C7B1579B670246@EXLAN5> From: Ian Cartwright To: "'viren@rstcorp.com'" , "Matthew N. Dodd" Cc: Jonathan Lemon , Ian Cartwright , freebsd-hardware@freebsd.org Subject: RE: ida driver (Re: cvs commit: src/sys/dev/ida ida_eisa.c) Date: Thu, 20 Apr 2000 15:01:24 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2448.0) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I had both of those problem too. Matt Dodd's newest patch has fixed #2 for me. And recompiling the kernel with 04/19 snapshot (or later) has solved problem #1 for me. I think it was choking on finding the NCR 5c710 SCSI controller... Not sure why though. Ian Cartwright Senior Engineer Raymond James Associates icartwright@it.rjf.com -----Original Message----- From: Viren R.Shah [mailto:viren@rstcorp.com] Sent: Thursday, April 20, 2000 10:35 AM To: Matthew N. Dodd Cc: Jonathan Lemon; Ian Cartwright; freebsd-hardware@freebsd.org Subject: ida driver (Re: cvs commit: src/sys/dev/ida ida_eisa.c) Just a report on the ida driver: I installed a recent (0418) -current SNAP on my Compaq ProLiant box, and it worked just fine, except for 2 issues: 1. I did what I usually do, and customized the kernel to remove all the devices that were not present, and that new kernel would not boot -- paniced right after detecting ida0. I'm currently trying to resolve that issue by gradually removing devices and booting to find out which devices it needs that I thought it didn't. 2. The loader won't boot from the idad0s1a device. Here's the boot log: ida0: ignoring completion 1000 no devsw (majdev=0 bootdev=0xa0200000) Mounting root from ufs:/dev/idad0s1a no such device 'idad' setrootbyname failed ffs_mountroot: can't find rootvp Root mount failed: 6 Manual root filesystem specification: : Mount using filesystem eg. ufs:/dev/da0s1a ? List valid disk boot devices Abort manual input mountroot> ufs:/dev/id0s1a Mounting root from ufs:/dev/id0s1a The weird thing is that the id0s1a device isn't even present in the /dev directory. The ida devices present in /dev are (ls -la /dev/id* ): crw-r----- 1 root operator 109, 0x00010002 Apr 19 09:17 /dev/idad0 crw-r----- 1 root operator 109, 0 Apr 19 09:17 /dev/idad0a crw-r----- 1 root operator 109, 1 Apr 19 09:17 /dev/idad0b crw-r----- 1 root operator 109, 2 Apr 19 09:17 /dev/idad0c crw-r----- 1 root operator 109, 3 Apr 19 09:17 /dev/idad0d crw-r----- 1 root operator 109, 4 Apr 19 09:17 /dev/idad0e crw-r----- 1 root operator 109, 5 Apr 19 09:17 /dev/idad0f crw-r----- 1 root operator 109, 6 Apr 19 09:17 /dev/idad0g crw-r----- 1 root operator 109, 7 Apr 19 09:17 /dev/idad0h crw-r----- 1 root operator 109, 0x00020002 Apr 20 09:36 /dev/idad0s1 crw-r----- 1 root operator 109, 0x00020000 Apr 20 09:36 /dev/idad0s1a crw-r----- 1 root operator 109, 0x00020001 Apr 20 09:36 /dev/idad0s1b crw-r----- 1 root operator 109, 0x00020002 Apr 20 09:36 /dev/idad0s1c crw-r----- 1 root operator 109, 0x00020003 Apr 20 09:36 /dev/idad0s1d crw-r----- 1 root operator 109, 0x00020004 Apr 20 09:36 /dev/idad0s1e crw-r----- 1 root operator 109, 0x00020005 Apr 20 09:36 /dev/idad0s1f crw-r----- 1 root operator 109, 0x00020006 Apr 20 09:36 /dev/idad0s1g crw-r----- 1 root operator 109, 0x00020007 Apr 20 09:36 /dev/idad0s1h crw-r----- 1 root operator 109, 0x00030002 Apr 19 09:17 /dev/idad0s2 crw-r----- 1 root operator 109, 0x00030000 Apr 18 15:35 /dev/idad0s2a crw-r----- 1 root operator 109, 0x00030001 Apr 18 15:35 /dev/idad0s2b crw-r----- 1 root operator 109, 0x00030002 Apr 18 15:35 /dev/idad0s2c crw-r----- 1 root operator 109, 0x00030003 Apr 18 15:35 /dev/idad0s2d crw-r----- 1 root operator 109, 0x00030004 Apr 18 15:35 /dev/idad0s2e crw-r----- 1 root operator 109, 0x00030005 Apr 18 15:35 /dev/idad0s2f crw-r----- 1 root operator 109, 0x00030006 Apr 18 15:35 /dev/idad0s2g crw-r----- 1 root operator 109, 0x00030007 Apr 18 15:35 /dev/idad0s2h crw-r----- 1 root operator 109, 0x00040002 Apr 19 09:17 /dev/idad0s3 crw-r----- 1 root operator 109, 0x00050002 Apr 19 09:17 /dev/idad0s4 Viren -- Viren Shah | "Every time a file is committed, viren@rstcorp.com | a fairy gets its wings." viren@viren.org | -- TJ Walls To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Thu Apr 20 12:11:23 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from assurance.rstcorp.com (rstcorp2.daf.concentric.net [216.112.242.2]) by hub.freebsd.org (Postfix) with ESMTP id 7701A37B6AC for ; Thu, 20 Apr 2000 12:11:15 -0700 (PDT) (envelope-from vshah@rstcorp.com) Received: (from uucp@localhost) by assurance.rstcorp.com (8.9.3/8.9.3) id JAA26242; Thu, 20 Apr 2000 09:38:20 -0400 Received: from sandbox.rstcorp.com(10.1.30.2) by assurance.rstcorp.com via smap (V2.0) id xma026229; Thu, 20 Apr 00 13:37:29 GMT Received: from jabberwock.rstcorp.com (jabberwock.rstcorp.com [10.1.100.5]) by sandbox.rstcorp.com (8.9.3/8.9.3) with ESMTP id KAA19217; Thu, 20 Apr 2000 10:28:16 -0400 (EDT) Received: by jabberwock.rstcorp.com (Postfix, from userid 93) id A6A305B1C; Thu, 20 Apr 2000 10:34:53 -0400 (EDT) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14591.5517.454232.897127@jabberwock.rstcorp.com> Date: Thu, 20 Apr 2000 10:34:53 -0400 (EDT) From: "Viren R.Shah" To: "Matthew N. Dodd" Cc: Jonathan Lemon , Ian Cartwright , freebsd-hardware@freebsd.org Subject: ida driver (Re: cvs commit: src/sys/dev/ida ida_eisa.c) In-Reply-To: References: <14584.47894.130306.880624@jabberwock.rstcorp.com> X-Mailer: VM 6.72 under 19.16 "Lille" XEmacs Lucid Reply-To: viren@rstcorp.com X-Face: )~y+U*K:yzjz{q<5lzpI_SVef'U.])9g[C9`1N@]u3,MHY7f*l7C)[_NjM4y4K8$uIUh|\u (K&&HS6,M!61&GMTk'mqmB/Qg]]X}"?TzsFl]"2v!bl8']dma.:^IY^a[lbOI>U:b<~FyK3q-p{HmZ mn~g.`~BE!5{2D:}Yi+\_KkWe?XaHj9$ko1k8iKLYv5*_2c8"G=?Up[}hn+7RNM(bzBZ_wWk6!Pf&B ?3Tcm7M7B~W%K/I0aX3]*=jP?aM]H6HBPT`oLk+0n^_;N\2\%|Rhy;p}34Q.jEsM\qtnxcm;ag%Nq Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Just a report on the ida driver: I installed a recent (0418) -current SNAP on my Compaq ProLiant box, and it worked just fine, except for 2 issues: 1. I did what I usually do, and customized the kernel to remove all the devices that were not present, and that new kernel would not boot -- paniced right after detecting ida0. I'm currently trying to resolve that issue by gradually removing devices and booting to find out which devices it needs that I thought it didn't. 2. The loader won't boot from the idad0s1a device. Here's the boot log: ida0: ignoring completion 1000 no devsw (majdev=0 bootdev=0xa0200000) Mounting root from ufs:/dev/idad0s1a no such device 'idad' setrootbyname failed ffs_mountroot: can't find rootvp Root mount failed: 6 Manual root filesystem specification: : Mount using filesystem eg. ufs:/dev/da0s1a ? List valid disk boot devices Abort manual input mountroot> ufs:/dev/id0s1a Mounting root from ufs:/dev/id0s1a The weird thing is that the id0s1a device isn't even present in the /dev directory. The ida devices present in /dev are (ls -la /dev/id* ): crw-r----- 1 root operator 109, 0x00010002 Apr 19 09:17 /dev/idad0 crw-r----- 1 root operator 109, 0 Apr 19 09:17 /dev/idad0a crw-r----- 1 root operator 109, 1 Apr 19 09:17 /dev/idad0b crw-r----- 1 root operator 109, 2 Apr 19 09:17 /dev/idad0c crw-r----- 1 root operator 109, 3 Apr 19 09:17 /dev/idad0d crw-r----- 1 root operator 109, 4 Apr 19 09:17 /dev/idad0e crw-r----- 1 root operator 109, 5 Apr 19 09:17 /dev/idad0f crw-r----- 1 root operator 109, 6 Apr 19 09:17 /dev/idad0g crw-r----- 1 root operator 109, 7 Apr 19 09:17 /dev/idad0h crw-r----- 1 root operator 109, 0x00020002 Apr 20 09:36 /dev/idad0s1 crw-r----- 1 root operator 109, 0x00020000 Apr 20 09:36 /dev/idad0s1a crw-r----- 1 root operator 109, 0x00020001 Apr 20 09:36 /dev/idad0s1b crw-r----- 1 root operator 109, 0x00020002 Apr 20 09:36 /dev/idad0s1c crw-r----- 1 root operator 109, 0x00020003 Apr 20 09:36 /dev/idad0s1d crw-r----- 1 root operator 109, 0x00020004 Apr 20 09:36 /dev/idad0s1e crw-r----- 1 root operator 109, 0x00020005 Apr 20 09:36 /dev/idad0s1f crw-r----- 1 root operator 109, 0x00020006 Apr 20 09:36 /dev/idad0s1g crw-r----- 1 root operator 109, 0x00020007 Apr 20 09:36 /dev/idad0s1h crw-r----- 1 root operator 109, 0x00030002 Apr 19 09:17 /dev/idad0s2 crw-r----- 1 root operator 109, 0x00030000 Apr 18 15:35 /dev/idad0s2a crw-r----- 1 root operator 109, 0x00030001 Apr 18 15:35 /dev/idad0s2b crw-r----- 1 root operator 109, 0x00030002 Apr 18 15:35 /dev/idad0s2c crw-r----- 1 root operator 109, 0x00030003 Apr 18 15:35 /dev/idad0s2d crw-r----- 1 root operator 109, 0x00030004 Apr 18 15:35 /dev/idad0s2e crw-r----- 1 root operator 109, 0x00030005 Apr 18 15:35 /dev/idad0s2f crw-r----- 1 root operator 109, 0x00030006 Apr 18 15:35 /dev/idad0s2g crw-r----- 1 root operator 109, 0x00030007 Apr 18 15:35 /dev/idad0s2h crw-r----- 1 root operator 109, 0x00040002 Apr 19 09:17 /dev/idad0s3 crw-r----- 1 root operator 109, 0x00050002 Apr 19 09:17 /dev/idad0s4 Viren -- Viren Shah | "Every time a file is committed, viren@rstcorp.com | a fairy gets its wings." viren@viren.org | -- TJ Walls To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Thu Apr 20 12:13:21 2000 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 3A03037B510; Thu, 20 Apr 2000 12:13:14 -0700 (PDT) (envelope-from ken@panzer.kdm.org) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id KAA15408; Thu, 20 Apr 2000 10:42:30 -0600 (MDT) (envelope-from ken) Date: Thu, 20 Apr 2000 10:42:30 -0600 From: "Kenneth D. Merry" To: Artem Koutchine Cc: questions@freebsd.org, hardware@freebsd.org Subject: Re: Ultra 160 AHA controller on 3.4? Message-ID: <20000420104230.A15370@panzer.kdm.org> References: <002f01bfaabb$d5e31aa0$0c00a8c0@ipform.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <002f01bfaabb$d5e31aa0$0c00a8c0@ipform.ru>; from matrix@chat.ru on Thu, Apr 20, 2000 at 03:24:21PM +0400 Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Thu, Apr 20, 2000 at 15:24:21 +0400, Artem Koutchine wrote: > Does anybody use one of those on 3.4? Does 3.4 > even support any Ultra 160 controller? The Adaptec Ultra160 controllers are only supported in 4.0 (and -current). You can probably use a Symbios/LSI Ultra160 controller with 3.4 if you download Gerard Roudier's sym driver from here: ftp://ftp.tux.org/tux/roudier/drivers/freebsd If you've got questions about that driver, send mail to groudier@FreeBSD.ORG. 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 Apr 20 13:15:12 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id 2417D37BE7F for ; Thu, 20 Apr 2000 13:15:10 -0700 (PDT) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.3/8.9.3) with ESMTP id NAA19780 for ; Thu, 20 Apr 2000 13:15:09 -0700 (PDT) (envelope-from jdp@polstra.com) Received: (from jdp@localhost) by vashon.polstra.com (8.9.3/8.9.1) id NAA04677 for hardware@freebsd.org; Thu, 20 Apr 2000 13:15:08 -0700 (PDT) (envelope-from jdp@polstra.com) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Date: Thu, 20 Apr 2000 13:15:08 -0700 (PDT) Organization: Polstra & Co., Inc. From: John Polstra To: hardware@freebsd.org Subject: Booting from Mylex RAID Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Is it possible to boot a FreeBSD system from a Mylex RAID controller? John To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Thu Apr 20 13:52:47 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from watson.grauel.com (watson.grauel.com [199.233.104.36]) by hub.freebsd.org (Postfix) with ESMTP id 62A4137B746 for ; Thu, 20 Apr 2000 13:52:44 -0700 (PDT) (envelope-from jjr@sparcmill.grauel.com) Received: from sparcmill.grauel.com (sparcmill.grauel.com [199.233.104.34]) by watson.grauel.com (8.8.7/8.8.7) with SMTP id PAA11144 for ; Thu, 20 Apr 2000 15:52:44 -0500 (EST) (envelope-from jjr@sparcmill.grauel.com) Received: by sparcmill.grauel.com (SMI-8.6/SMI-SVR4) id PAA03895; Thu, 20 Apr 2000 15:50:18 -0500 Date: Thu, 20 Apr 2000 15:50:18 -0500 Message-Id: <200004202050.PAA03895@sparcmill.grauel.com> From: John J Rieser MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: hardware@FreeBSD.ORG Subject: VScom PCI Multiport cards X-Mailer: VM 6.34 under 20.3 "Vatican City" XEmacs Lucid Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I've just loaded FreeBSD 4.0 on a HP Brio 200 (PCI bus for peripherals only). I'd love to get this AST-style ports card configured to run modems and terminals. My experience is limited to the isa version of this card, so I'm in the dark as to what the kernel needs in order to find the card/ports. SIO man page claims: device sio ## is the only thing needed in the kernel. This is supposed to be a plug and pray card..so far I'm only praying! What I've done so far... 1) Turned off appropriate things in BIOS. 2) Made new kernel including pci controller and sio device without setting ports, irqs or the like. 3) Rebooted and searched for pci~anything in dmesg. * this is all I get: ======== pcib0: on motherboard pci0: on pcib0 pci0: at 1.0 irq 10 pcib1: at device 30.0 on pci0 pci1: on pcib1 pci1: (vendor=0x14d2, dev=0xa003) at 14.0 irq 10 pci1: (vendor=0x14d2, dev=0xa000) at 14.1 irq 10 isab0: at device 31.0 on pci0 atapci0: port 0x1800-0x180f at device 31.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 pci0: at 31.2 irq 11 pci0: (vendor=0x8086, dev=0x2423) at 31.3 irq 9 chip1: port 0x1840-0x187f,0x2000-0x20ff irq 9 at device 31.5 on pci0 ========= Any help in this would be greatly appreciated! John J. Rieser jjr@grauel.com PO Box 6249 Tel: (765)477-6000 \ 100 Sawmill Road x327 Lafayette, IN 47903 (800)489-4891 / To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Thu Apr 20 15: 0:48 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from postfix1.free.fr (postfix1.free.fr [212.27.32.21]) by hub.freebsd.org (Postfix) with ESMTP id 54E1A37B74A; Thu, 20 Apr 2000 15:00:45 -0700 (PDT) (envelope-from stephane@libertysurf.fr) Received: from sequoia.mondomaineamoi.megalo (unknown [213.228.19.159]) by postfix1.free.fr (Postfix) with ESMTP id 0D1082870D; Fri, 21 Apr 2000 00:00:41 +0200 (MEST) Received: (from stephane@localhost) by sequoia.mondomaineamoi.megalo (8.9.3/8.9.3) id XAA04711; Thu, 20 Apr 2000 23:56:45 +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: <14591.32028.804492.576621@sequoia.mondomaineamoi.megalo> Date: Thu, 20 Apr 2000 23:56:44 +0200 (CEST) To: freebsd-hardware@freebsd.org Cc: Mike Smith , Stephane Legrand Subject: Boot problem with AcceleRAID 150 (was VALinux FullOn 2x2 with FreeBSD) In-Reply-To: <14545.17741.355237.821095@sequoia.mondomaineamoi.megalo> References: <20000315113405.E74343@PacHell.TelcoSucks.org> <200003152050.MAA01297@mass.cdrom.com> <20000315153036.F74343@PacHell.TelcoSucks.org> <14545.17741.355237.821095@sequoia.mondomaineamoi.megalo> 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 Hello, 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. So, is there a "trick" to boot FreeBSD with this RAID controller ? Does the 4.0-release supports this controller also for boot or do we have to upgrade the system to 4.0-stable ? Do we have to try without the boot manager ? Thank you. Stephane Legrand. Stephane Legrand writes: > Ulf Zimmermann writes: > > On Wed, Mar 15, 2000 at 12:50:14PM -0800, Mike Smith wrote: > > > > > Does anyone know if the server VALinux FullOn 2x2 ("good" version : > > > > > http://www.valinux.com/systems/productinfo.html?product=16#raid) can > > > > > run with FreeBSD ? Every components of this server seem ok except for > > > > > the RAID controler which is a Mylex AcceleRAID 150. On this web page > > > > > (http://www.posi.net/freebsd/drivers/driver-info.phtml?ID=9), i read > > > > > that this card should be supported on FreeBSD 4.x but also that it has > > > > > never been tested with this special card. > > > > > > > > The Mylex AcceleRaid 150/250 is supported as bootable device since > > > > a few weeks. I am running a 250 currently and I am very happy with it. > > > > > > AFAIK, the 150 is the same as the 250, but with a slower processor. I > > > don't have one here in the lab, but I would be quite surprised if it > > > didn't work as expected. > > > > Differences are: > > > > 33 MHz against 66 MHz cpu > > Software Xor chip against hardware ASIC > > > > Thank you very much for your answers. I'll keep inform the list if > FreeBSD actually runs well with this server. > > 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 Thu Apr 20 15: 8:35 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from mass.cdrom.com (mass.cdrom.com [204.216.28.184]) by hub.freebsd.org (Postfix) with ESMTP id 0EBB437B652 for ; Thu, 20 Apr 2000 15:08:31 -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 PAA09048; Thu, 20 Apr 2000 15:15:19 -0700 (PDT) (envelope-from msmith@mass.cdrom.com) Message-Id: <200004202215.PAA09048@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Stephane Legrand Cc: freebsd-hardware@freebsd.org Subject: Re: Boot problem with AcceleRAID 150 (was VALinux FullOn 2x2 with FreeBSD) In-reply-to: Your message of "Thu, 20 Apr 2000 23:56:44 +0200." <14591.32028.804492.576621@sequoia.mondomaineamoi.megalo> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 20 Apr 2000 15:15:19 -0700 From: Mike Smith Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org It sounds like you've done something _really_ weird here. Did you initialise the array before installing to it? Which geometry mode is it in? Which disk did you actually install to? How many partitions did you create while you were installing? > 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. > > So, is there a "trick" to boot FreeBSD with this RAID controller ? > Does the 4.0-release supports this controller also for boot or do we > have to upgrade the system to 4.0-stable ? Do we have to try without > the boot manager ? > > > Thank you. > Stephane Legrand. > > > Stephane Legrand writes: > > Ulf Zimmermann writes: > > > On Wed, Mar 15, 2000 at 12:50:14PM -0800, Mike Smith wrote: > > > > > > Does anyone know if the server VALinux FullOn 2x2 ("good" version : > > > > > > http://www.valinux.com/systems/productinfo.html?product=16#raid) can > > > > > > run with FreeBSD ? Every components of this server seem ok except for > > > > > > the RAID controler which is a Mylex AcceleRAID 150. On this web page > > > > > > (http://www.posi.net/freebsd/drivers/driver-info.phtml?ID=9), i read > > > > > > that this card should be supported on FreeBSD 4.x but also that it has > > > > > > never been tested with this special card. > > > > > > > > > > The Mylex AcceleRaid 150/250 is supported as bootable device since > > > > > a few weeks. I am running a 250 currently and I am very happy with it. > > > > > > > > AFAIK, the 150 is the same as the 250, but with a slower processor. I > > > > don't have one here in the lab, but I would be quite surprised if it > > > > didn't work as expected. > > > > > > Differences are: > > > > > > 33 MHz against 66 MHz cpu > > > Software Xor chip against hardware ASIC > > > > > > > Thank you very much for your answers. I'll keep inform the list if > > FreeBSD actually runs well with this server. > > > > Stephane Legrand. > > > > > -- > Stephane.Legrand@bigfoot.com > FreeBSD Francophone : http://www.freebsd-fr.org/ > -- \\ 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 Thu Apr 20 17: 8:23 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from europa.engg.ksu.edu (Europa.engg.ksu.edu [129.130.81.112]) by hub.freebsd.org (Postfix) with ESMTP id 8FE8037B55A for ; Thu, 20 Apr 2000 17:08:16 -0700 (PDT) (envelope-from dave@europa.engg.ksu.edu) Received: from phobos.engg.ksu.edu (phobos.engg.ksu.edu [129.130.81.133]) by europa.engg.ksu.edu (8.9.3/8.9.3) with ESMTP id TAA12020 for ; Thu, 20 Apr 2000 19:08:13 -0500 (CDT) Received: from phobos.engg.ksu.edu (phobos.engg.ksu.edu [129.130.81.133]) by phobos.engg.ksu.edu (8.9.3+Sun/8.9.1) with SMTP id TAA16405 for ; Thu, 20 Apr 2000 19:16:24 -0500 (CDT) Message-Id: <200004210016.TAA16405@phobos.engg.ksu.edu> Date: Thu, 20 Apr 2000 19:16:24 -0500 (CDT) From: Dave Haney Reply-To: Dave Haney Subject: IDE problems with as200 To: freebsd-hardware@freebsd.org MIME-Version: 1.0 Content-Type: TEXT/plain; charset=us-ascii Content-MD5: H/QP14Hb0Wm+oi3iINbKcg== X-Mailer: dtmail 1.3.0 CDE Version 1.3 SunOS 5.7 sun4m sparc Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hello, I have an AlphaStation 200 4/233 running FreeBSD 4.0-stable which I am overall very pleased with, howhever I have purchaced an "Ultra66" ATA/66 Promise controller to replace an ISA EIDEMAXII Promise controller I had in the system. When I placed the PCI ATA/66 card in the system, and booted it the system crashed midway through the boot: [snip] sio1: reserved for low-level i/o unexpected machine check: mces = 0x1 vector = 0x660 param = 0xfffffc0000006000 pc = 0xfffffc00004a9c60 ra = 0xfffffc00004a9c34 curproc = 0xfffffc0000567090 pid = 0, comm = swapper panic: machine check uptime: 0s [snip] The problem is perfectly reproducable. I've tried: * updating the SRM console firmware * updating the BIOS/Firmware/whatever on the ATA/66 card * removing the ata drivers from the kernel * booting generic kernel * disconnecting hard disk from card * placing the ATA/66 card in other slots * removing other cards which might cause conflicts Nothing seems to help. Does anyone have any suggestions? Thanks in advance, --Dave Dave Haney College of Engineering Computer Systems Analyst Kansas State University dave@engg.ksu.edu 785.532.4643 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Thu Apr 20 21:48:13 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from guy.asimware.com (guy.asimware.com [199.185.255.10]) by hub.freebsd.org (Postfix) with ESMTP id 07AF537B8E7; Thu, 20 Apr 2000 21:48:05 -0700 (PDT) (envelope-from gscott@guy.asimware.com) Received: from localhost (gscott@localhost) by guy.asimware.com (8.8.7/8.8.7) with SMTP id JAA23173; Thu, 20 Apr 2000 09:24:08 -0400 Date: Thu, 20 Apr 2000 09:24:08 -0400 (EDT) From: Greg Scott To: Artem Koutchine Cc: questions@FreeBSD.ORG, hardware@FreeBSD.ORG Subject: Re: Motherborad/Memory/CPU for web hosting system In-Reply-To: <002d01bfaabb$d3453e40$0c00a8c0@ipform.ru> 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 > What I am thinking about right now is : Asus P2B-LS motherboard, > Pentium III above 500, 512MB ram, 1 SCSI 10GB, 1 SCSI 30GB, > 1 UDMA IDE AS BIG AS IT CAN BE for backup. The main problem > is the motherboard. I just don't see any alternative and that;s bad. I'd > like > to have a choice. It seems like the newer i820 bases motherboards from Asus > have SCSI contrller Ultra160 which is not supported by 3.4 ( i'd rather no > go with 4.0). But on the other hand BX is kind old now. > > If you have some experience with hosting a lot of web servers, please, share > the hardware config with me. We just recently put together a machine with the following: SuperMicro P6DGU Dual Slot1 440BX Board with AIC-7890 SCSI PentiumIII 600 512M of ECC RAM DPT RAID Card 3 x 9.1G AtlasV SCA Drives Seagate 12G DAT Drive Intel Pro Server Ethernet Card Elan Vital S30 Rackmount case with HotSwap Kit It's a very nice box that will be doing mostly transactions. Because of the RAID card I can only run FreeBSD 3.2 on it, but it's pretty sweet. The only other problem is the Coppermine processors will not work in Dual mode at this time.. regardless of the Slocket adapter you try. BX may be kind of old now, but it works and there is lots of support for it in the OS. You could also look at Tyan motherboards. I've used them in a number of different systems for different things. They make good stuff. If you are looking for a fault tollerant solution, go with the RAID setup.. it can really save your ass when it comes to downtime. ************************************************************** ** Greg Scott, ** Asimware Innovations Inc. ** ** Website Co-Ordinator ** 600 Upper Wellington Unit D ** ** Network Administrator ** Hamilton, Ontario Canada ** ** gscott@asimware.com ** L9A 3P9 ** ************************************************************** PGP Key http://www.asimware.com/pubkey_gscott.asc To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Fri Apr 21 1:55:22 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from hermes.research.kpn.com (hermes.research.kpn.com [139.63.192.8]) by hub.freebsd.org (Postfix) with ESMTP id 0D81A37B6EF for ; Fri, 21 Apr 2000 01:55:19 -0700 (PDT) (envelope-from K.J.Koster@kpn.com) Received: from l04.research.kpn.com (l04.research.kpn.com [139.63.192.204]) by research.kpn.com (PMDF V5.2-31 #35196) with ESMTP id <01JOHU2105B6001879@research.kpn.com> for hardware@FreeBSD.ORG; Fri, 21 Apr 2000 10:53:03 +0200 Received: by l04.research.kpn.com with Internet Mail Service (5.5.2650.21) id ; Fri, 21 Apr 2000 10:53:02 +0100 Content-return: allowed Date: Fri, 21 Apr 2000 10:53:00 +0100 From: "Koster, K.J." Subject: RE: Motherborad/Memory/CPU for web hosting system To: 'Artem Koutchine' Cc: hardware@FreeBSD.ORG Message-id: <59063B5B4D98D311BC0D0001FA7E452201313AEB@l04.research.kpn.com> MIME-version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-type: text/plain; charset="koi8-r" Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > But on the other hand BX is kind old now. > Perhaps. I read some stuff on Tom's hardware pages that shows that the BX chipset with PC133 SDRAM will kick the newer chipsets pretty little asses. I have to admit Tom had to overclock it for that, which is not what you'd do on a server. http://www.tomshardware.com/mainboard/00q1/000308/fsb-133-2-19.html Even if you're not going for to scrape the bottom of the can for performance, the BX chipset is a proven one, as someone pointed out earlier. Kees Jan ============================================== You are only young once, but you can stay immature all your life To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Fri Apr 21 9:27: 9 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id 7B1FA37B9E2 for ; Fri, 21 Apr 2000 09:27:07 -0700 (PDT) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.3/8.9.3) with ESMTP id JAA24705 for ; Fri, 21 Apr 2000 09:27:06 -0700 (PDT) (envelope-from jdp@polstra.com) From: John Polstra Received: (from jdp@localhost) by vashon.polstra.com (8.9.3/8.9.1) id JAA11295; Fri, 21 Apr 2000 09:27:05 -0700 (PDT) (envelope-from jdp@polstra.com) Date: Fri, 21 Apr 2000 09:27:05 -0700 (PDT) Message-Id: <200004211627.JAA11295@vashon.polstra.com> To: hardware@freebsd.org Subject: Re: Booting from Mylex RAID In-Reply-To: References: Organization: Polstra & Co., Seattle, WA Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In article , John Polstra wrote: > Is it possible to boot a FreeBSD system from a Mylex RAID > controller? For the archives: Mike Smith says the answer is yes. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Disappointment is a good sign of basic intelligence." -- Chögyam Trungpa To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Fri Apr 21 13:27: 2 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from postfix1.free.fr (postfix1.free.fr [212.27.32.21]) by hub.freebsd.org (Postfix) with ESMTP id 33B6E37B975; Fri, 21 Apr 2000 13:26:59 -0700 (PDT) (envelope-from stephane@libertysurf.fr) Received: from sequoia.mondomaineamoi.megalo (paris11-nas1-20-6.dial.proxad.net [213.228.20.6]) by postfix1.free.fr (Postfix) with ESMTP id EAC9D280E9; Fri, 21 Apr 2000 22:26:54 +0200 (MEST) Received: (from stephane@localhost) by sequoia.mondomaineamoi.megalo (8.9.3/8.9.3) id WAA03819; Fri, 21 Apr 2000 22:24:47 +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: <14592.47374.389569.324252@sequoia.mondomaineamoi.megalo> Date: Fri, 21 Apr 2000 22:24:46 +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: <200004202215.PAA09048@mass.cdrom.com> References: <14591.32028.804492.576621@sequoia.mondomaineamoi.megalo> <200004202215.PAA09048@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: > > It sounds like you've done something _really_ weird here. Did you > initialise the array before installing to it? If you mean initialisation with the Mylex BIOS, yes and i remember clearly because it take a looonnng time. > Which geometry mode is it > in? Frankly, i can't remember and i can't be in front of the server until next week so i can't even take a look. I just can say that the number of blocks viewed by the FreeBSD installation program seemed correct with the disks sizes. > Which disk did you actually install to? There are 4 disks of 9Gbytes each. We chose "RAID 5" in the Mylex BIOS during the initialisation. We have created 2 logical disks with the Mylex BIOS : - one of ~ 5.5 Gb for the system. This logical disk was recognized by the FreeBSD installation program as "mlxd0" if i remember well. We installed FreeBSD on this logical disk. - one other of may be ~ 20 Gb. This logical disk was recognized by the FreeBSD installation program as "mlxd1" if i remember well. The FreeBSD installation program didn't modified this logical disk (we didn't even format this disk). > How many partitions did you > create while you were installing? > 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. > > 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. > > > > So, is there a "trick" to boot FreeBSD with this RAID controller ? > > Does the 4.0-release supports this controller also for boot or do we > > have to upgrade the system to 4.0-stable ? Do we have to try without > > the boot manager ? > > > > > > Thank you. > > Stephane Legrand. > > > > > > Stephane Legrand writes: > > > Ulf Zimmermann writes: > > > > On Wed, Mar 15, 2000 at 12:50:14PM -0800, Mike Smith wrote: > > > > > > > Does anyone know if the server VALinux FullOn 2x2 ("good" version : > > > > > > > http://www.valinux.com/systems/productinfo.html?product=16#raid) can > > > > > > > run with FreeBSD ? Every components of this server seem ok except for > > > > > > > the RAID controler which is a Mylex AcceleRAID 150. On this web page > > > > > > > (http://www.posi.net/freebsd/drivers/driver-info.phtml?ID=9), i read > > > > > > > that this card should be supported on FreeBSD 4.x but also that it has > > > > > > > never been tested with this special card. > > > > > > > > > > > > The Mylex AcceleRaid 150/250 is supported as bootable device since > > > > > > a few weeks. I am running a 250 currently and I am very happy with it. > > > > > > > > > > AFAIK, the 150 is the same as the 250, but with a slower processor. I > > > > > don't have one here in the lab, but I would be quite surprised if it > > > > > didn't work as expected. > > > > > > > > Differences are: > > > > > > > > 33 MHz against 66 MHz cpu > > > > Software Xor chip against hardware ASIC > > > > > > > > > > Thank you very much for your answers. I'll keep inform the list if > > > FreeBSD actually runs well with this server. > > > > > > 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 Fri Apr 21 14:12:51 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from mass.cdrom.com (mass.cdrom.com [204.216.28.184]) by hub.freebsd.org (Postfix) with ESMTP id C34B737B8ED; Fri, 21 Apr 2000 14:12:47 -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 OAA00572; Fri, 21 Apr 2000 14:19:50 -0700 (PDT) (envelope-from msmith@mass.cdrom.com) Message-Id: <200004212119.OAA00572@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Stephane Legrand Cc: Mike Smith , freebsd-hardware@freebsd.org Subject: Re: Boot problem with AcceleRAID 150 (was VALinux FullOn 2x2 with FreeBSD) In-reply-to: Your message of "Fri, 21 Apr 2000 22:24:46 +0200." <14592.47374.389569.324252@sequoia.mondomaineamoi.megalo> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 21 Apr 2000 14:19:50 -0700 From: Mike Smith Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > Which geometry mode is it > > in? > > Frankly, i can't remember and i can't be in front of the server until > next week so i can't even take a look. I just can say that the number > of blocks viewed by the FreeBSD installation program seemed correct > with the disks sizes. Ok. That doesn't help though if you've set the geometry oddly. I typically use the 2GB mode, so I may have missed an issue here. > 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? > > > 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. -- \\ 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 Fri Apr 21 19:12:51 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from whitey.org (cc188085-c.chmbl1.ga.home.com [24.4.239.166]) by hub.freebsd.org (Postfix) with ESMTP id C34AD37BDAB for ; Fri, 21 Apr 2000 19:12:48 -0700 (PDT) (envelope-from smoked@whitey.org) Received: from localhost (smoked@localhost) by whitey.org (8.9.3/8.9.3) with ESMTP id KAA00364 for ; Sat, 22 Apr 2000 10:10:51 -0400 (EDT) (envelope-from smoked@whitey.org) Date: Sat, 22 Apr 2000 10:10:51 -0400 (EDT) From: AG To: freebsd-hardware@freebsd.org Subject: Write errors on UDMA drives 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 ---------- Forwarded message ---------- Date: Sat, 22 Apr 2000 05:13:10 -0400 (EDT) From: AG To: freebsd-questions@freebsd.org Subject: Write errors on UDMA drives Hello, I am running FreeBSD 4.0 with two UDMA drives. One is a 8 gig Maxtor running at UDMA/33 and the other is a 40 gig Maxtor running at UDMA/66. When I try to do large writes to either drive, gunzip'ing a large file, sorting a large file, or any other type of intensive writing to the drive, I get the following errors repeatedly: Apr 22 05:02:40 37 /kernel: ad0: UDMA ICRC WRITE ERROR blk# 13597744 retrying On the 8 gig drive, this will continue without any real effects, but on the 40 gig drive, it will go so far as to halt/reboot my machine. The blk# changes, and it appears to be a worse condition on the 40 gig, rather then the 8 gig. I have checked dmesg, and there doesn't appear to be any IRQ conflicts. Has anyone else run across this, or possibly know what is going on? Any help will be appreciated. Thanks, AG p.s. I am also getting this error occasionaly: Apr 22 10:05:55 37 /kernel: invalid state: 0x1 Apr 22 10:05:56 37 /kernel: invalid state: 0x1 I'm not sure this relates, but I thought I would just include it anyways. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Fri Apr 21 21:51:50 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from web107.yahoomail.com (web107.yahoomail.com [205.180.60.74]) by hub.freebsd.org (Postfix) with SMTP id B785337B8F0 for ; Fri, 21 Apr 2000 21:51:38 -0700 (PDT) (envelope-from eaglez69@yahoo.com) Received: (qmail 14861 invoked by uid 60001); 22 Apr 2000 04:51:38 -0000 Message-ID: <20000422045138.14860.qmail@web107.yahoomail.com> Received: from [130.65.210.24] by web107.yahoomail.com; Fri, 21 Apr 2000 21:51:38 PDT Date: Fri, 21 Apr 2000 21:51:38 -0700 (PDT) From: Eaglez Subject: Re: Write errors on UDMA drives To: AG Cc: freebsd-hardware@FreeBSD.ORG MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org No offense, but I think that's because they're >Maxtor< drives. Those are notoriously stupid. They even tried to sell a bootloader with some of their old ones, that would put a new format on the disk, and make it so nothing could read it. I think this is something like how a lot of 100baseTX cards can't really do full 100baseTX. Like maybe not enough buffer. I couldn't say for sure. The point is, Maxtor is somewhat low-end (they're cheep for a reason), and if you're going to be doing massive reads/writes, i'd advise saving up for something slightly better. (I've had NO problems with IBM drives...) -Jesse --- AG wrote: > > > ---------- Forwarded message ---------- > Date: Sat, 22 Apr 2000 05:13:10 -0400 (EDT) > From: AG > To: freebsd-questions@freebsd.org > Subject: Write errors on UDMA drives > > Hello, > > I am running FreeBSD 4.0 with two UDMA drives. One > is a 8 gig Maxtor > running at UDMA/33 and the other is a 40 gig Maxtor > running at > UDMA/66. When I try to do large writes to either > drive, gunzip'ing a large > file, sorting a large file, or any other type of > intensive writing to the > drive, I get the following errors repeatedly: > > Apr 22 05:02:40 37 /kernel: ad0: UDMA ICRC WRITE > ERROR blk# 13597744 > retrying > > On the 8 gig drive, this will continue without any > real effects, but on > the 40 gig drive, it will go so far as to > halt/reboot my machine. The > blk# changes, and it appears to be a worse condition > on the 40 gig, > rather then the 8 gig. I have checked dmesg, and > there doesn't appear to > be any IRQ conflicts. Has anyone else run across > this, or possibly know > what is going on? Any help will be appreciated. > > Thanks, > > AG > > p.s. I am also getting this error occasionaly: > > Apr 22 10:05:55 37 /kernel: invalid state: 0x1 > Apr 22 10:05:56 37 /kernel: invalid state: 0x1 > > I'm not sure this relates, but I thought I would > just include it anyways. > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hardware" in the body of > the message > __________________________________________________ Do You Yahoo!? Send online invitations with Yahoo! Invites. http://invites.yahoo.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 22 23: 6:47 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from celery.dragondata.com (celery.dragondata.com [205.253.12.6]) by hub.freebsd.org (Postfix) with ESMTP id C957837B795 for ; Sat, 22 Apr 2000 23:06:31 -0700 (PDT) (envelope-from toasty@celery.dragondata.com) Received: (from toasty@localhost) by celery.dragondata.com (8.9.3/8.9.3) id BAA42439 for hardware@freebsd.org; Sun, 23 Apr 2000 01:06:21 -0500 (CDT) (envelope-from toasty) From: Kevin Day Message-Id: <200004230606.BAA42439@celery.dragondata.com> Subject: TESTERS WANTED: OPTi 82C621 ATA support To: hardware@freebsd.org Date: Sun, 23 Apr 2000 01:06:21 -0500 (CDT) X-Mailer: ELM [version 2.5 PL1] 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 I've completed the first pass of support for the OPTi 82C621 IDE controller, for modes up to PIO4. I've seen a considerable speed boost on my system after doing this, and it seems stable, however, it's all very untested code. If anyone has one of these chips in their system and could assist in testing it, I would really appreciate it. DON'T attempt this without backing up everything you have. It's completely possible(but not too likely) this could destroy any data you have on your disk. Here's a quick measurement of speed gained, with iozone: iozone -N -s 12m -f /tmp/iozone.tmp Microseconds/op Mode. Output is in microseconds per operation. random random bkwd record stride KB reclen write rewrite read reread read write read rewrite read fwrite frewrite fread freread OPTi PIO4 12288 4 871 771 234 233 286 8333 244 164 254 775 769 317 316 OPTi PIO0 12288 4 874 1021 634 341 299 8291 266 163 301 822 998 684 622 GENERIC 12288 4 887 3115 1992 876 414 8000 381 161 536 908 1834 990 1025 The "GENERIC" was a standard GENERIC kernel with whatever the BIOS happened to set the chip's timings to. So, it seems that this can make a significant speed increase, if you have a disk that can handle PIO4. Note that this is using a nasty slow 2.5" IDE drive, which probably explains the poor write performance. This is what you should see during bootup: ata0-master: success setting up PIO4 mode on OPTi621 chip ata0-slave: success setting up PIO3 mode on OPTi621 chip ata0: OPTi621 addressing mode set at PIO3 ad0: ATA-4 disk at ata0 as master ad0: 2067MB (4233600 sectors), 4200 cyls, 16 heads, 63 S/T, 512 B/S ad0: 16 secs/int, 1 depth queue, PIO4 ad0: piomode=4 dmamode=2 udmamode=-1 cblid=0 Creating DISK ad0 Creating DISK wd0 ata0-slave: piomode=3 dmamode=-1 udmamode=-1 dmaflag=0 acd0: CDROM drive at ata0 as slave acd0: read 689KB/s (689KB/s), 128KB buffer, PIO3 acd0: Reads: acd0: Audio: play, 256 volume levels acd0: Mechanism: ejectable tray acd0: Medium: no/blank disc inside, unlocked Because of a quirk in how the chip handles addressing speed, your 'address mode speed' will be set to whatever the SLOWEST device is on that cable. If you've got a nice fast PIO4 drive and a slow PIO0 cd-rom on the same cable, the chip will use address timings for PIO0. For maximum speed, don't do this. :) Here's the patch. Yes, it probably could be cleaned up quite a bit, but it appears to work here. Please please please give some feedback if you can try it. :) This diff is against 4.0-RELEASE, although I could probably make it work on a different version if necessary. diff --exclude=*compile* -r -u /usr/src/sys-orig/conf/options /usr/src/sys/conf/options --- /usr/src/sys-orig/conf/options Wed Feb 23 14:10:53 2000 +++ /usr/src/sys/conf/options Sun Apr 23 00:15:13 2000 @@ -219,6 +219,7 @@ # Options used in the 'ata' ATA/ATAPI driver ATA_STATIC_ID opt_ata.h ATA_ENABLE_ATAPI_DMA opt_ata.h +ATA_OPTI_PIO opt_ata.h # Resource limits. DFLDSIZ opt_rlimit.h diff --exclude=*compile* -r -u /usr/src/sys-orig/dev/ata/ata-all.c /usr/src/sys/dev/ata/ata-all.c --- /usr/src/sys-orig/dev/ata/ata-all.c Sat Mar 18 16:26:28 2000 +++ /usr/src/sys/dev/ata/ata-all.c Sun Apr 23 00:22:21 2000 @@ -294,6 +294,9 @@ case 0x00041103: return "HighPoint HPT366 ATA66 controller"; + case 0xc6211045: + return "OPTi/Cirrus Logic 82C621 ATA controller"; + /* unsupported but known chipsets, generic DMA only */ case 0x10001042: case 0x10011042: @@ -1012,11 +1015,125 @@ return 0; } +#ifdef ATA_OPTI_PIO +#define opti_pcic_unlock() inw(scp->ioaddr + 1); inw(scp->ioaddr + 1) + +static void +opti_reg_write(struct ata_softc *scp, unsigned char reg, unsigned char value) +{ + + opti_pcic_unlock(); + outb(scp->ioaddr + 2, 0x03); + outb(scp->ioaddr + reg, value); + outb(scp->ioaddr + 2, 0x83); + +} + +static void +opti621_timing(struct ata_softc *scp, int32_t bestmode) +{ + int i, data, recovery, addr; + + /* Calculate the address timing for the entire controller */ + + switch (inw(scp->ioaddr + 5) & 1) { + case 1: /* 25/50Mhz */ + switch (bestmode) { + case ATA_PIO0: addr = 2; break; + case ATA_PIO1: addr = 2; break; + case ATA_PIO2: addr = 1; break; + case ATA_PIO3: addr = 1; break; + case ATA_PIO4: addr = 1; break; + default: addr = 2; break; + } + break; + default: + case 0: /* 33/66MHz */ + switch (bestmode) { + case ATA_PIO0: addr = 3; break; + case ATA_PIO1: addr = 2; break; + case ATA_PIO2: addr = 2; break; + case ATA_PIO3: addr = 1; break; + case ATA_PIO4: addr = 1; break; + default: addr = 3; break; + } + break; + } + + /* + * The Linux driver seems to be violating the spec for the + * chip if I do what they did. If you have problems, try + * turning this on + * + */ +#if 0 + outb(scp->ioaddr + 3, 0x81); /* access B register */ +#endif + /* + * The Linux driver does this too, without understanding why. + * If I don't do it, the chip hangs. Undocumented completely. + * + */ + outb(scp->ioaddr + 5, 0xff); /* huh? */ + + for (i=0;i<2;i++) { /* Once per drive */ + + switch (inw(scp->ioaddr + 5) & 1) { + case 1: /* 25/50Mhz */ + switch (scp->mode[i]) { + case ATA_PIO0: data = 5; recovery = 8; break; + case ATA_PIO1: data = 4; recovery = 4; break; + case ATA_PIO2: data = 3; recovery = 2; break; + case ATA_PIO3: data = 2; recovery = 2; break; + case ATA_PIO4: data = 2; recovery = 1; break; + default: data = 8; recovery = 8; break; + } + break; + default: + case 0: /* 33/66MHz */ + switch (scp->mode[i]) { + case ATA_PIO0: data = 6; recovery = 11; break; + case ATA_PIO1: data = 5; recovery = 6; break; + case ATA_PIO2: data = 4; recovery = 2; break; + case ATA_PIO3: data = 3; recovery = 2; break; + case ATA_PIO4: data = 3; recovery = 1; break; + default: data = 8; recovery = 10; break; + } + break; + } + + opti_reg_write(scp, 6, i); /* Select proper drive */ + /* Write the read timing and the write timing */ + opti_reg_write(scp, 0, recovery | (data << 4)); + opti_reg_write(scp, 1, recovery | (data << 4)); + + } + + /* + * Disable prefetching (doesn't work right) + * Set address select timing + * Default DRDY timing (2 LCLKS) + * + */ + opti_reg_write(scp, 6, addr << 4); + + /* Enable the changes we made, overriding strapping options */ + outb(scp->ioaddr + 3, 0x85); + +} + +#endif /* ATA_OPTI_PIO */ + static void ata_boot_attach(void) { struct ata_softc *scp; int32_t ctlr; +#ifdef ATA_OPTI_PIO + int32_t bestmode, error, apiomode; +#endif /* * run through all ata devices and look for real ATA & ATAPI devices @@ -1040,6 +1157,62 @@ scp->devices &= ~ATA_ATAPI_MASTER; } +#ifdef ATA_OPTI_PIO + /* + * In the case of the OPTi 621, we have to work around the fact that + * it's rather brain damaged. While it supports up to PIO4, both the + * master and the slave device have to be the same mode for address + * timing. If you've got a PIO4 drive and a PIO1 CD-ROM, you're stuck + * with PIO1's address speed. Really. Data/recovery speeds do match the + * true drive's speed, though. + * + * So, we have to be at a point where we can look at both devices on + * the channel before we can setup the timing, but before we've + * actually done the attach. The only place I can see for this is here + * + */ + for (ctlr=0; ctlrchiptype != 0xc6211045) + continue; + + bestmode = 255; + if (scp->devices & (ATA_ATA_MASTER | ATA_ATAPI_MASTER)) { + apiomode = ata_pmode(ATA_PARAM(scp,ATA_MASTER)); + bestmode = min(bestmode, apiomode); + scp->mode[0] = ata_pio2mode(apiomode); + error = ata_command(scp, ATA_MASTER, ATA_C_SETFEATURES, 0, 0, 0, + ata_pio2mode(apiomode), + ATA_C_F_SETXFER, ATA_WAIT_READY); + if (bootverbose) + ata_printf(scp, ATA_MASTER, + "%s setting up PIO%d mode on OPTi621 chip\n", + (error) ? "failed" : "success", + (apiomode >= 0) ? apiomode : 0); + } + if (scp->devices & (ATA_ATA_SLAVE | ATA_ATAPI_SLAVE)) { + apiomode = ata_pmode(ATA_PARAM(scp,ATA_SLAVE)); + bestmode = min(bestmode, apiomode); + scp->mode[1] = ata_pio2mode(apiomode); + error = ata_command(scp, ATA_SLAVE, ATA_C_SETFEATURES, 0, 0, 0, + ata_pio2mode(apiomode), + ATA_C_F_SETXFER, ATA_WAIT_READY); + if (bootverbose) + ata_printf(scp, ATA_SLAVE, + "%s setting up PIO%d mode on OPTi621 chip\n", + (error) ? "failed" : "success", + (apiomode >= 0) ? apiomode : 0); + } + + if (bestmode == 255) + continue; + ata_printf(scp, -1, "OPTi621 addressing mode set at PIO%d\n", + bestmode); + opti621_timing(scp, bestmode); + } +#endif + #if NATADISK > 0 /* now we know whats there, do the real attach, first the ATA disks */ for (ctlr=0; ctlrunit << 1) + ATA_DEV(device); int32_t error; +#ifdef ATA_OPTI_PIO + /* + * If we're using the OPTi chip, this will be done later, when + * we're attaching the disks. (We need to know what speed both + * disks are on the channel to configure the controller) + * + */ + if (scp->chiptype == 0xc6211045) + return; +#endif + /* set our most pessimistic default mode */ scp->mode[ATA_DEV(device)] = ATA_PIO; To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message