From owner-freebsd-hardware Sun Sep 24 1:27:58 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from fepB.post.tele.dk (postB.tele.dk [195.41.46.146]) by hub.freebsd.org (Postfix) with ESMTP id 6FC1E37B424 for ; Sun, 24 Sep 2000 01:27:52 -0700 (PDT) Received: from anne ([195.249.35.247]) by fepB.post.tele.dk (InterMail vM.4.01.03.00 201-229-121) with SMTP id <20000924082750.YSGV21052.fepB.post.tele.dk@anne>; Sun, 24 Sep 2000 10:27:50 +0200 Message-ID: <003301c02600$ea74ea00$0401a8c0@spellweaver.dk> From: "Kristian Hansen" To: "Archibald Hive" Cc: References: Subject: Re: Disk/Tape Controller Date: Sun, 24 Sep 2000 10:23:49 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2919.6600 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600 Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi, This problem seems to date back to FreeBSD 3.1, see following link: http://www.freebsd.org/cgi/query-pr.cgi?pr=10563 I'm reproducing the problem on FreeBSD 4.0 using a Colorado QIC-40 drive, that I've previously used with FreeBSD 2.2.8. Regards Kristian Hansen, ----- Original Message ----- From: "Archibald Hive" To: Cc: Sent: 14. september 2000 13:44 Subject: Disk/Tape Controller > > > Hello, I've tried everything that I could find on the freebsd site about > floppy tape's. I guess this is my last ditch effort attempt to find out > if the conner model CTT800I-F QIC-80 (drive connects via fdd > connection) is in any way, shape or form accessible under fbsd. > > I've tried adding in the following lines to the kernels config, but no > luckage with it: > > controller fdc0 at isa? port "IO_FD1" bio irq 6 drq 2 flags 0x1 vector fdintr > *and* > device ft0 at fdc0 drive 2 > > at which time i get the response back during the configuration of the > kernel i recieve: > > config: line 42: syntax error > config: line 43: fdc 0 not defined > config: line 44: fdc 0 not defined > config: line 45: fdc 0 not defined > > Warning: device "ft" is unknown > > at which time I then remodified the kernel to remove the quatations with > the same results. > > figure, okay, no problem, just keep marching on right... > > # make depend -- no problems > # make --------- appears to have no problems > # make install - does install just fine > > # shutdown -r now > > # cd /dev > # ./MAKEDEV ft0 > ft0 - no such device name > > # > > I'm wondering if there is a way to work around this, maybe using a scsi > fdd controller and build that into the kernel, do you think that would > work? > > At wit's end, appreciate the time and help > > root@e-u-a.net > > > > > > > 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 Sun Sep 24 8:34:58 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from gc7.generalconcepts.com (24.65.54.138.on.wave.home.com [24.65.54.138]) by hub.freebsd.org (Postfix) with ESMTP id 5BE1D37B424 for ; Sun, 24 Sep 2000 08:34:51 -0700 (PDT) Received: (from jsellens@localhost) by gc7.generalconcepts.com (8.9.3/8.9.3) id LAA67325 for freebsd-hardware@FreeBSD.ORG; Sun, 24 Sep 2000 11:34:50 -0400 (EDT) (envelope-from jsellens) Date: Sun, 24 Sep 2000 11:34:50 -0400 (EDT) From: John Sellens Message-Id: <200009241534.LAA67325@gc7.generalconcepts.com> To: freebsd-hardware@FreeBSD.ORG Subject: maxtor IDE disk parks heads too quickly Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I'm running 4.0-RELEASE with a Cyrix processor and AMI BIOS. I have a Maxtor 18GB IDE disk as a second disk installed as the slave on the second IDE controller, though I saw similar behaviour when it was secondary on the primary IDE controller. The disk seems to park its heads after 15 seconds of idle time (there's an audible click) and then takes 3 or 4 seconds to ready itself when the next access is requested, which I find quite annoying. I've looked at the Maxtor docs and can't find anything that looks like it would help. The BIOS has disk power management disabled, I can't see any other BIOS settings that look relevant. Potentially relevant bits from dmesg: atapci0: port 0x4000-0x400f,0xe08000-0xe08003,0x40154000-0x40154007,0x20090140-0x20090143,0x30f0400-0x30f0407 irq 0 at device 1.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 ad0: 6187MB [13410/15/63] at ata0-master using UDMA33 ad3: 17418MB [35390/16/63] at ata1-slave using UDMA33 acd0: CD-RW at ata1-master using PIO4 Any suggestions on how to extend or disable the head park time? Or is this just a Maxtor feature or something? Thanks very much John jsellens@generalconcepts.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Sun Sep 24 11:22:35 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from rip.psg.com (rip.psg.com [147.28.0.39]) by hub.freebsd.org (Postfix) with ESMTP id 55EFA37B424 for ; Sun, 24 Sep 2000 11:22:33 -0700 (PDT) Received: from randy by rip.psg.com with local (Exim 3.16 #1) id 13dGQ4-0008Ii-00 for freebsd-hardware@freebsd.org; Sun, 24 Sep 2000 11:22:32 -0700 From: Randy Bush MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: FreeBSD Hardware Subject: asus recommendation Message-Id: Date: Sun, 24 Sep 2000 11:22:32 -0700 Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org i have used asus for a long time, so am a bit partial. this is for a desktop, not the rack. so what is a good high-perf asus that's compatible this season o atx o takes decent speed processor(a) o screaming scsi on board (like the aic7890/91 on the p2b-ds) o agp optional o smd optional but kinda like it o 10/100 onboard optional o video that XFree likes optional randy To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Sun Sep 24 21: 0:28 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from merlin.prod.itd.earthlink.net (merlin.prod.itd.earthlink.net [207.217.120.156]) by hub.freebsd.org (Postfix) with ESMTP id AA91537B422 for ; Sun, 24 Sep 2000 21:00:24 -0700 (PDT) Received: from earthlink.net (1Cust208.tnt4.everett2.wa.da.uu.net [63.22.5.208]) by merlin.prod.itd.earthlink.net (8.9.3-EL_1_3/8.9.3) with ESMTP id VAA12171; Sun, 24 Sep 2000 21:00:22 -0700 (PDT) Received: (from odyseus2000@localhost) by earthlink.net (8.9.3/8.9.3) id UAA01823; Sun, 24 Sep 2000 20:57:23 -0700 (PDT) (envelope-from odyseus2000) Date: Sun, 24 Sep 2000 20:57:22 -0700 From: David Burton To: Randy Bush Cc: freebsd-hardware@FreeBSD.org Subject: Re: asus recommendation Message-ID: <20000924205722.B269@slick.earthlink.net> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.4i In-Reply-To: ; from randy@psg.com on Sun, Sep 24, 2000 at 11:22:32AM -0700 Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I think your request is much too general. why dont you surf on over to the www.asus.com website, poke around a little while, see what looks like it would meet your needs. takes decent processor speed?? (a)?? I am sure there are some that might argue a Pent 133 is all the power you need :-0 a for athlon? agp 1x? 2x? 4x? Pro? smd ??? do you mean SMBus or SIMD, perhaps I am missing something. perhaps some specs about its use? and so on? sincerely, David On Sun, Sep 24, 2000 at 11:22:32AM -0700, Randy Bush wrote: > i have used asus for a long time, so am a bit partial. this is for a > desktop, not the rack. > > so what is a good high-perf asus that's compatible this season > o atx > o takes decent speed processor(a) > o screaming scsi on board (like the aic7890/91 on the p2b-ds) > o agp > > optional > o smd optional but kinda like it > o 10/100 onboard optional > o video that XFree likes optional > > randy > > > 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 Sun Sep 24 22: 0:10 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from rip.psg.com (rip.psg.com [147.28.0.39]) by hub.freebsd.org (Postfix) with ESMTP id 806E437B507 for ; Sun, 24 Sep 2000 21:59:52 -0700 (PDT) Received: from randy by rip.psg.com with local (Exim 3.16 #1) id 13dQMp-000Bm4-00; Sun, 24 Sep 2000 21:59:51 -0700 From: Randy Bush MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: David Burton Cc: freebsd-hardware@FreeBSD.org Subject: Re: asus recommendation References: <20000924205722.B269@slick.earthlink.net> Message-Id: Date: Sun, 24 Sep 2000 21:59:51 -0700 Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > why dont you surf on over to the www.asus.com website, poke around a > little while, see what looks like it would meet your needs. did that. and they use all sorts of terms which folk who have not kept up with mbs and chip sets don't understand, FSB, ServerWorks, AGPset, i820, RDRAM, ... which it is not clear freebsd (4.1-stable) supports. e.g. the p3c-ls (or -s) look close to my needs if i don't want anything faster than 733mhz, but does freebsd support the i820, the aic7892 (the handbook says 789x, but i am cautious), ...? > smd ? sorry. smp. with 700+ cpu, i can live without smp. i have a dual-300 on my desk now, and it it getting soggy and hard to light. >> i have used asus for a long time, so am a bit partial. this is for a >> desktop, not the rack. >> >> so what is a good high-perf asus that's compatible this season >> o atx >> o takes decent speed processor(a) >> o screaming scsi on board (like the aic7890/91 on the p2b-ds) >> o agp >> >> optional >> o smd optional but kinda like it >> o 10/100 onboard optional >> o video that XFree likes optional basically, i am a semi-competent net.geek and sysadmin of a decade or two, etc., but have never had the time to keep up with all the latest hardwhere gadgets. so when it's time to upgrade a limping box, i whine for help. randy To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Mon Sep 25 3:21: 0 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from cage.tse-online.de (cage.tse-online.de [194.97.69.170]) by hub.freebsd.org (Postfix) with SMTP id 947AB37B422 for ; Mon, 25 Sep 2000 03:20:55 -0700 (PDT) Received: (qmail 46363 invoked by uid 1000); 25 Sep 2000 10:27:43 -0000 Date: Mon, 25 Sep 2000 12:27:43 +0200 From: Andreas Braukmann To: Darryl Okahata Cc: freebsd-hardware@FreeBSD.ORG Subject: Re: Lucent Wavelan vs. wi-driver Message-ID: <20000925122742.E45877@cage.tse-online.de> References: <20000924004338.B37311@cage.tse-online.de> <200009240243.TAA16209@mina.soco.agilent.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <200009240243.TAA16209@mina.soco.agilent.com>; from darrylo@soco.agilent.com on Sat, Sep 23, 2000 at 07:43:38PM -0700 Organization: TSE GmbH - Neue Medien Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi, sorry for coming back to you that late. But I didn't have any chance to work on the problem the last two days. On Sat, Sep 23, 2000 at 07:43:38PM -0700, Darryl Okahata wrote: > Andreas Braukmann wrote: [ ... problems with vaio 505 and wi driver ... ] > I'd guess that the problem is related to the PCMCIA chipset used in > the Vaio, as the bug report talks about a Vaio, too (although a > different model). Well, than I'll check, if they use the same PCMCIA chipset. > It probably won't help, but you could post a verbose dmesg, As soon as I get my fingers on my notebook again (my partner grabbed it right from my desk for using it on a local trade show :( ), I'll dig a little deeper. > as well as the bootup console messages (many of which are NOT > placed into dmesg or /var/log/messages). Capturing the console > messages can be tricky, That should be solvable. I don't fear patching rc scripts ... Thanks, Andreas -- : Anti-Spam Petition: http://www.politik-digital.de/spam/ : : PGP-Key: http://www.tse-online.de/~ab/public-key : : Key fingerprint: 12 13 EF BC 22 DD F4 B6 3C 25 C9 06 DC D3 45 9B : To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Mon Sep 25 4:13:59 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from sun262.hai.iec.co.il (sun262.hai.iec.co.il [138.134.2.62]) by hub.freebsd.org (Postfix) with ESMTP id 228CB37B424 for ; Mon, 25 Sep 2000 04:13:56 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by sun262.hai.iec.co.il (Postfix) with ESMTP id 064BD7070 for ; Mon, 25 Sep 2000 14:10:42 +0200 (IST) Date: Mon, 25 Sep 2000 14:10:42 +0200 (IST) From: Roman Shterenzon X-Sender: roman@sun262.hai.iec.co.il To: freebsd-hardware@freebsd.org Subject: PCI modem Message-ID: Organization: Xpert UNIX Systems Ltd. MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi, Could anyone recommend a PCI modem that works under FreeBSD (i.e. hardware modem). Some specific brand/model. It has to be PCI, since the computer it'll be used in doesn't have ISA slots and serial ports are already in use. I only found some USrobotics model which I cannot find in stores :( Thank you in advance, --Roman Shterenzon, UNIX System Administrator and Consultant [ Xpert UNIX Systems Ltd., Herzlia, Israel. Tel: +972-9-9522361 ] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Mon Sep 25 7:19:10 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from etsfw1.emrsn.net (etsfw1.customer.dbn.net [216.178.212.94]) by hub.freebsd.org (Postfix) with ESMTP id C61EC37B422 for ; Mon, 25 Sep 2000 07:19:03 -0700 (PDT) Received: (from smap@localhost) by etsfw1.emrsn.net (8.9.3/8.9.3) id OAA27655 for ; Mon, 25 Sep 2000 14:22:36 GMT From: Gerardo.Galvan@emotors.com Message-Id: <200009251422.OAA27655@etsfw1.emrsn.net> X-Authentication-Warning: etsfw1.emrsn.net: smap set sender to using -f Received: from emrsvr1(209.251.176.16) by etsfw1.emrsn.net via smap (V2.1) id xma027616; Mon, 25 Sep 00 14:22:17 GMT Received: from 128.53.1.56 by ets-srvr1.emrsn.net (InterScan E-Mail VirusWall NT); Mon, 25 Sep 2000 09:18:42 -0500 (Central Daylight Time) Received: by MXSEMRCN2 with Internet Mail Service (5.5.2650.21) id ; Mon, 25 Sep 2000 09:16:20 -0500 To: freebsd-hardware@FreeBSD.ORG Subject: Are "Winmodems" supported? Date: Mon, 25 Sep 2000 09:28:22 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-Type: multipart/mixed; boundary="----_=_NextPart_000_01C026FC.DB7EACA0" Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. ------_=_NextPart_000_01C026FC.DB7EACA0 Content-Type: text/plain Hi all, Does anybody know if the so called "Winmodems" are supported under FreeBSD 4.1? If so, Which chipsets are proven to work? Thanks for your answers, Gerardo. ------_=_NextPart_000_01C026FC.DB7EACA0 Content-Type: application/ms-tnef Content-Transfer-Encoding: base64 eJ8+IhUOAQaQCAAEAAAAAAABAAEAAQeQBgAIAAAA5AQAAAAAAADoAAEIgAcAGAAAAElQTS5NaWNy b3NvZnQgTWFpbC5Ob3RlADEIAQSAAQAbAAAAQXJlICJXaW5tb2RlbXMiIHN1cHBvcnRlZD8AdAkB CYABACEAAAAwNzVBRjg5QkI0OTJENDExQjgwNTAwQjBEMDRCM0E4RAAcBwEggAMADgAAANAHCQAZ AAkAEAATAAEAJgEBBYADAA4AAADQBwkAGQAJABwAFgABADUBAQ2ABAACAAAAAgACAAEDkAYAdAQA AB4AAAADAC4AAAAAAEAAOQCgrH7b/CbAAR4AcAABAAAAFAAAAGhhcmR3YXJlIHN1cHBvcnRlZD8A AgFxAAEAAAAbAAAAAcAl5ruYWAx6HZHLEdSyUAAIx7EeSQBFc7NBAAIBCRABAAAAIwEAAB8BAACn AQAATFpGdcyB5zcDAAoAcmNwZzEyNf4yAP8CBgKkA+QF6wKDAFATA1QCAGNoCsBzZXR+MgYABsMC gw5QBFUCAHBwcnExIAhVB7ICgH1/CoAIzwnZAoAKgQ5xC2BucQ4QMDMzCvsTsQvyYyEOoCBIaSAH QGwsZwqFCoUbMERvB5EAcHmBBuBkeSBrbm8H4AEGkCB0aGUgc2+MIGMaIQmAICJXC4BxBGJtcyIa EBZgHOB1THBwFgEdYXVuBIEgAkYJ0UJTRCA0LjAxPyBJHJAc8CwgtFdoDeBoHRAg4HASsecbkR5h FGBvdgnwHKAdAFJ3BbBrPxpsVBKAbu5rBCACEAXAeQhhG6ED4DUEkHMaVkcEkAsRby4LGmwVgQAn YAADAP0/UgMAAB4AQhABAAAAIwAAADwzOUNEOUEwNy5EMkI2NTBCQUB1YXMuYWxhc2thLmVkdT4A AAMAJgAAAAAAAwA2AAAAAAAeADFAAQAAABAAAABHQUxWQU5HOTIxRDkwQzUAAwAaQAAAAAAeADBA AQAAABAAAABHQUxWQU5HOTIxRDkwQzUAAwAZQAAAAAACAfk/AQAAAF4AAAAAAAAA3KdAyMBCEBq0 uQgAKy/hggEAAAAGAAAAL089RU1SL09VPUJCLUVNUi1TVEwtVVMtMDEvQ049TVNNQUlMIFVTRVJT KFBDKS9DTj1HQUxWQU5HOTIxRDkwQzUAAAAeAPg/AQAAABoAAABHYWx2YW4sIEdlcmFyZG8gW0VN Qy9NTU1dAAAAHgA4QAEAAAAQAAAAR0FMVkFORzkyMUQ5MEM1AAIB+z8BAAAAXgAAAAAAAADcp0DI wEIQGrS5CAArL+GCAQAAAAYAAAAvTz1FTVIvT1U9QkItRU1SLVNUTC1VUy0wMS9DTj1NU01BSUwg VVNFUlMoUEMpL0NOPUdBTFZBTkc5MjFEOTBDNQAAAB4A+j8BAAAAGgAAAEdhbHZhbiwgR2VyYXJk byBbRU1DL01NTV0AAAAeADlAAQAAABAAAABHQUxWQU5HOTIxRDkwQzUAQAAHMOCQZYr8JsABQAAI MOKMmSz7JsABHgA9AAEAAAABAAAAAAAAAB4AHQ4BAAAAGwAAAEFyZSAiV2lubW9kZW1zIiBzdXBw b3J0ZWQ/AAALACkAAAAAAAsAIwAAAAAAAwAGEOpXkB0DAAcQhgAAAAMAEBAAAAAAAwAREAEAAAAe AAgQAQAAAGUAAABISUFMTCxET0VTQU5ZQk9EWUtOT1dJRlRIRVNPQ0FMTEVEIldJTk1PREVNUyJB UkVTVVBQT1JURURVTkRFUkZSRUVCU0Q0MT9JRlNPLFdISUNIQ0hJUFNFVFNBUkVQUk9WRU5UAAAA AEkI ------_=_NextPart_000_01C026FC.DB7EACA0-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Mon Sep 25 9:10:10 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from bbnrel4.net.external.hp.com (bbnrel4.net.external.hp.com [155.208.254.68]) by hub.freebsd.org (Postfix) with ESMTP id 9534E37B50F for ; Mon, 25 Sep 2000 09:09:46 -0700 (PDT) Received: from hpcpbla.bri.hp.com (hpcpbla.bri.hp.com [15.144.112.65]) by bbnrel4.net.external.hp.com (Postfix) with ESMTP id E25CC186B5; Mon, 25 Sep 2000 18:09:25 +0200 (METDST) Received: from sse0691.bri.hp.com (sse0691.bri.hp.com [15.144.0.53]) by hpcpbla.bri.hp.com (8.9.3 (PHNE_18979)/8.9.3 SMKit7.0) with ESMTP id RAA19479; Mon, 25 Sep 2000 17:09:24 +0100 (BST) Received: (from steve@localhost) by sse0691.bri.hp.com (8.9.3/8.9.3) id RAA64912; Mon, 25 Sep 2000 17:12:40 +0100 (BST) (envelope-from steve) Date: Mon, 25 Sep 2000 17:12:40 +0100 From: Steve Roome To: kafeend Cc: hardware@freebsd.org Subject: Re: UDMA write error Message-ID: <20000925171240.F8111@moose.bri.hp.com> References: <3.0.6.32.20000923164403.00795b10@pop.crosswinds.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.4i In-Reply-To: <3.0.6.32.20000923164403.00795b10@pop.crosswinds.net>; from jimmychonga@pop1.crosswinds.net on Sat, Sep 23, 2000 at 04:44:03PM -0700 Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Sat, Sep 23, 2000 at 04:44:03PM -0700, kafeend wrote: > I came across your answer to Nader's problem. And i have the same it > seems like all VIA chipsets have this problem :). I wanted to know > how to make it not start up in ata mode. the output of sysctl > hw.atamodes is "hw.atamodes:pio,pio,"...but it still gives me that > error the UDMA write error on boot. How can i fix it so that this > won't happen anymore. Also i don't have an /etc/sysctl.conf file > :(. Thanks kafeend Firstly you really need to get your mail client to wrap lines at 72 chars or thereabouts.. I saw another post, possibly from you recently on -stable and I almost replied but it was a right mess because it wasn't wrapped the way I (and a lot of others) like. Secondly, I've cc:d this to freebsd-hardware because it seems relevant, and hopefully someone will either find my comments useful and perhaps even get back to me with corrections or explanations for where I've got things wrong. Finally, in response, the problem, UDMA devices dying horribly... I have a 82c686 as well, (mine is the onboard one on an FIC SD-11, which is not really the best of motherboards, but does the job and works OKAY being one of the earliest boards to support athlons). I also have a 34Gb IBM disk, UDMA66 (and apparenly UDMA 100) compatible. Originally I had my disk setup in UDMA 66 mode, and it went all pear shaped and died with lots of bad blocks while writing or reading #. The disk actually then reported itself as dead to Windows as well, and I got as far as sending it back to the manufacturors to get a replacement. However, it turns out I was one of the first to get bit by this problem, and all that had happened is that the IDE driver had toasted the disk due to some sort of corruption. I finally wiped the disk with a util from IBM for ... wiping your disks! The same disk now works, and I have moved it so that it is better cooled and rechecked all the cabling. I think that your problem, and a lot of other problems people have been having with this are due to UDMA going wrong because a disk has overheated, I think *guessing* that writing to a device with UDMA which is just in the process of dying due to overheating can cause problems with the blocks on the disk. Not just in the drivers.. Note that after my problem I couldn't even get the IBM DOS disk utils to properly identify and check the disk until after a complete low level wipe. Interestingly my problem occurred about 10GB into the FreeBSD partition of the disk, yet it rendered the Windows partition corrupt as well. Now, as a solution you can turn off UDMA, (I've put it here because I think you should read the bit above anyway!) but I don't beleive there is as much wrong with the driver as people are making out, and I'm not going to advocate that solution as it's probably solvable (soluble?!) by simply checking the cabling and cooling of the disk. Others will tell you to switch to PIO mode, but since moving my disk I've hammered it hard! I've got an Athlon 500, and after two or three succesive make -j buildworlds I've come to the conclusion that although it looked like UDMA driver crapness it was just UDMA driver stressed hardware better than I'd installed it! Since then I've also repartitioned the disk much more cleanly and I move some very large files about and do TV captures etc. The only other possible culprit for data corruption might be using the UDMA driver to write more than 2Gb to a Windows (FAT32) filesystem. I've remember something about this, I think it might even cause a panic if you try that, but I'mm not willing to test it any further because I don't fancy wiping my disk again. I'll leave that as an excersice for someone on the hardware list who feels like having a bad week =) In summary though, you probably do actually have bad blocks on this disk now, I know that after my problem I did have blocks marked as bad on the disk. It killed two filesystems (about 15Gb apart!) and I had to wipe the disk to get rid of them. But I've never actually changed to PIO mode, and I don't think I or you need to! Of course, as always, your mileage may vary, Steve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Mon Sep 25 10: 6:36 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from ipamzlx.physik.uni-mainz.de (ipamzlx.Physik.Uni-Mainz.DE [134.93.180.54]) by hub.freebsd.org (Postfix) with ESMTP id 362DC37B43F for ; Mon, 25 Sep 2000 10:06:30 -0700 (PDT) Received: from ipamzlx.Physik.Uni-Mainz.DE (ipamzlx.Physik.Uni-Mainz.DE [134.93.180.54]) by ipamzlx.physik.uni-mainz.de (8.11.0/8.9.3) with ESMTP id e8PH7fp87658 for ; Mon, 25 Sep 2000 19:07:42 +0200 (CEST) (envelope-from ohartman@ipamzlx.physik.uni-mainz.de) Date: Mon, 25 Sep 2000 19:07:41 +0200 (CEST) From: "O. Hartmann" To: freebsd-hardware@freebsd.org Subject: What kind of CPU-type when using AMD-K6 2? 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 Dear Sirs. Some of our boxes running FreeBSD are based on AMD's K6-2 CPUs. My question is: Is AMD K6-2 CPU CPU type i586 or i686? At this time, I use in kernel the option CPU type i586 but I want to ask for that here not to give away performance by using a wrong type of CPU. Thanks for your comments, Gruss O. Hartmann ------------------------------------------------------------------- ohartman@ipamzlx.physik.uni-mainz.de Klimadatenserver des IPA, Universitaet Mainz Netzwerk- und Systembetreuung To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Mon Sep 25 10:14:41 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from ipamzlx.physik.uni-mainz.de (ipamzlx.Physik.Uni-Mainz.DE [134.93.180.54]) by hub.freebsd.org (Postfix) with ESMTP id 1E74137B424; Mon, 25 Sep 2000 10:14:37 -0700 (PDT) Received: from ipamzlx.Physik.Uni-Mainz.DE (ipamzlx.Physik.Uni-Mainz.DE [134.93.180.54]) by ipamzlx.physik.uni-mainz.de (8.11.0/8.9.3) with ESMTP id e8PHFnp93386; Mon, 25 Sep 2000 19:15:49 +0200 (CEST) (envelope-from ohartman@ipamzlx.physik.uni-mainz.de) Date: Mon, 25 Sep 2000 19:15:49 +0200 (CEST) From: "O. Hartmann" To: freebsd-smp@freebsd.org Cc: freebsd-hardware@freebsd.org Subject: TYAN Thunder 2500/MP Table Error 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 Dear Sirs. I run successfully a TYAN Thunder 2500 mainboard with FreeBSD 4.1-STABLE, BIOS Beta 1.03/896 for the LSI 53C896 based SCSI controler. When booting, I obtain a lot of SMP messages from the kernel, but at one stage, I receive this error: APIC_IO: Testing 8254 interrupt delivery APIC_IO: Broken MP table detected: 8254 is not connected to IOAPIC #0 intpin 2 APIC_IO: routing 8254 via 8259 and IOAPIC #0 intpin 0 SMP works fine, but it seems that there is something wron with the MP table. Is this a serious error message or is it simply a warning? What kind of performance penalty does it results in? And: hopefully, is there a chance to get rid of it with a new BIOS update in the future? Thanks in advance, Gruss O. Hartmann ------------------------------------------------------------------- ohartman@ipamzlx.physik.uni-mainz.de Klimadatenserver des IPA, Universitaet Mainz Netzwerk- und Systembetreuung To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Mon Sep 25 10:28:50 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from mail.wolves.k12.mo.us (mail.wolves.k12.mo.us [207.160.214.1]) by hub.freebsd.org (Postfix) with ESMTP id 39A3237B424 for ; Mon, 25 Sep 2000 10:28:42 -0700 (PDT) Received: from mail.wolves.k12.mo.us (cdillon@mail.wolves.k12.mo.us [207.160.214.1]) by mail.wolves.k12.mo.us (8.9.3/8.9.3) with ESMTP id MAA80812; Mon, 25 Sep 2000 12:28:31 -0500 (CDT) (envelope-from cdillon@wolves.k12.mo.us) Date: Mon, 25 Sep 2000 12:28:30 -0500 (CDT) From: Chris Dillon To: Randy Bush Cc: David Burton , freebsd-hardware@FreeBSD.ORG Subject: Re: asus recommendation 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 Sun, 24 Sep 2000, Randy Bush wrote: > > why dont you surf on over to the www.asus.com website, poke around a > > little while, see what looks like it would meet your needs. > > did that. and they use all sorts of terms which folk who have not kept up > with mbs and chip sets don't understand, FSB, ServerWorks, AGPset, i820, > RDRAM, ... which it is not clear freebsd (4.1-stable) supports. > > e.g. the p3c-ls (or -s) look close to my needs if i don't want anything > faster than 733mhz, but does freebsd support the i820, the aic7892 (the > handbook says 789x, but i am cautious), ...? This should help you out with general narrowing-down of what you want: 1) Stay away from the RDRAM chipsets. This includes the Intel i820 and i840. RDRAM is not only very, very expensive memory, its actual performance advantage is questionable, and it is being backed by a very questionable company (as in the underhanded Microsoft-type questionable -- Rambus, Inc.). I don't envision RAMBUS DRAM lasting very long in the server/workstation/desktop market due to its many disadvantages, but instead in the embedded market where it actually has some good advantages over SDRAM. 2) If you want to use a PIII processor, this leaves you with several choices: The good old i440BX chipset, the i810, the i815, and the ServerWorks stuff. I don't recommend the i810, as it is pretty low-end. The i440BX is over a couple of years old, but it is a very mature chipset that has proven itself as reliable. All of the other chipsets available for Slot1/Socket370 processors (such as from VIA, SiS, ALI, etc.) are crap, IMHO. Since the i815 is also pretty low-end and not suitable for servers, I'd have to go with one of the ServerWorks solutions (ASUS, Tyan, and SuperMicro, among others, make boards with these chipsets). 3) If you want to use an AMD Athlon processor of some type, you should wait a bit. The motherboards based on AMD's new 760 chipset are just now in the beta phase (the chipset is done, now its up to the mobo manufacturers to do something with it). The only other options are the AMD 750 chipset which is now quite dated and would hinder the performance of any modern Athlon you stick on it, and then there are the VIA chipsets. Most of the boards based on the VIA stuff are not very reliable. A few manufacturers have managed to create reliable boards out of them, but you'll have to do extra research to find out which boards they are. -- Chris Dillon - cdillon@wolves.k12.mo.us - cdillon@inter-linc.net FreeBSD: The fastest and most stable server OS on the planet. For Intel x86 and Alpha architectures. ( http://www.freebsd.org ) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Mon Sep 25 11:13:18 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from asterix.icon.net.mx (ns1.icon.net.mx [209.104.24.45]) by hub.freebsd.org (Postfix) with ESMTP id 7D19437B620; Mon, 25 Sep 2000 11:11:53 -0700 (PDT) Received: from localhost (antonio@localhost) by asterix.icon.net.mx (8.9.3/8.9.1) with ESMTP id LAA65164; Mon, 25 Sep 2000 11:11:51 -0700 (MST) Date: Mon, 25 Sep 2000 11:11:51 -0700 (MST) From: Antonio Varela Lizardi To: mobile@freebsd.org Cc: hardware@freebsd.org Subject: Help with WaveLAN Card 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 Apollogies in advance for the crossposting, but my deadline related to this matter it's very close. I have a Lucent WaveLAN Silver 11Mbps PCMCIA Card, a Texas Instrument (chipset recognized as 1225) PCMCIA-PCI Cardbus bridge (sold by lucent), a regular Desktop PC and FreeBSD 4.1-STABLE. I just cannot get the card to work. It's recognized sucessfully by pccardd, but I'm having an error: "tx buffer allocation failed" with any network operation over the card. Diggin out more, I've found that wi_seek( ) it's failing with a WI_TIMEOUT, when wi_alloc_nicmem( ) calls to alloc the tx buffer, when wi_init ( ) tries to initialize the card. The allocation of the management buffer suceeeds, and that sounds strange. The wi driver talks straight to the Hermes Controller, not using the card's firmware. I wonder if in this new product, the hardware has changed. In the wi manpage it's written about supporting 6Mbps cards, but never mentions 11Mbps cards. In the PAO FAQ found something about configuring the card with the MSDOS utility, but I just can't find it, neither CDROM/Website. Folks, you're my only hope, otherwise I'll have to install Linux. Any hint or bad news (the 11mbps card is supported?) will be welcome. Please help. I'm not subscribed to this lists, only to questions@freebsd.org. Please respond to my email too. Best regards, Antonio ----------- Antonio Varela Lizardi Ingenieria Computacional del Noroeste http://www.icon.net.mx To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Mon Sep 25 11:16:33 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from schooner.svjava.com (schooner.svjava.com [204.75.228.3]) by hub.freebsd.org (Postfix) with ESMTP id D823237B424; Mon, 25 Sep 2000 11:16:12 -0700 (PDT) Received: (from kozowski@localhost) by schooner.svjava.com (8.9.1a/svjava.com) id LAA12513; Mon, 25 Sep 2000 11:16:07 -0700 (PDT) Date: Mon, 25 Sep 2000 11:16:07 -0700 From: Eric Kozowski To: Antonio Varela Lizardi Cc: mobile@FreeBSD.ORG, hardware@FreeBSD.ORG Subject: Re: Help with WaveLAN Card Message-ID: <20000925111607.Q10523@schooner.svjava.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.2i In-Reply-To: ; from antonio@icon.net.mx on Mon, Sep 25, 2000 at 11:11:51AM -0700 Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Mon, Sep 25, 2000 at 11:11:51AM -0700, Antonio Varela Lizardi wrote: > > Apollogies in advance for the crossposting, but my deadline related to this > matter it's very close. > > I have a Lucent WaveLAN Silver 11Mbps PCMCIA Card, a Texas Instrument > (chipset recognized as 1225) PCMCIA-PCI Cardbus bridge (sold by lucent), a > regular Desktop PC and FreeBSD 4.1-STABLE. I just cannot get the card to > work. It's recognized sucessfully by pccardd, but I'm having an error: "tx > buffer allocation failed" with any network operation over the card. Diggin > out more, I've found that wi_seek( ) it's failing with a WI_TIMEOUT, when > wi_alloc_nicmem( ) calls to alloc the tx buffer, when wi_init ( ) tries to > initialize the card. The allocation of the management buffer suceeeds, and > that sounds strange. The wi driver talks straight to the Hermes Controller, > not using the card's firmware. I wonder if in this new product, the hardware > has changed. In the wi manpage it's written about supporting 6Mbps cards, > but never mentions 11Mbps cards. In the PAO FAQ found something about > configuring the card with the MSDOS utility, but I just can't find it, > neither CDROM/Website. Folks, you're my only hope, otherwise I'll have to > install Linux. Any hint or bad news (the 11mbps card is supported?) will be > welcome. Please help. as per the many discussions, as are available in the archives, the pci based bridge from lucent does not currently work. > I'm not subscribed to this lists, only to questions@freebsd.org. Please > respond to my email too. if you're going to ask the question on a list, you should be subscribed to that list. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Mon Sep 25 11:30:26 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from emu.prod.itd.earthlink.net (emu.prod.itd.earthlink.net [207.217.121.31]) by hub.freebsd.org (Postfix) with ESMTP id 4F09C37B42C for ; Mon, 25 Sep 2000 11:30:23 -0700 (PDT) Received: from earthlink.net (1Cust132.tnt8.everett2.wa.da.uu.net [63.24.202.132]) by emu.prod.itd.earthlink.net (8.9.3-EL_1_3/8.9.3) with ESMTP id LAA00874 for ; Mon, 25 Sep 2000 11:30:21 -0700 (PDT) Received: (from odyseus2000@localhost) by earthlink.net (8.9.3/8.9.3) id LAA03993 for freebsd-hardware@FreeBSD.org; Mon, 25 Sep 2000 11:29:49 -0700 (PDT) (envelope-from odyseus2000) Date: Mon, 25 Sep 2000 11:29:48 -0700 From: David Burton To: freebsd-hardware@FreeBSD.org Subject: Re: asus recommendation Message-ID: <20000925112948.F269@slick.earthlink.net> References: <20000924205722.B269@slick.earthlink.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.4i In-Reply-To: ; from randy@psg.com on Sun, Sep 24, 2000 at 09:59:51PM -0700 Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org You forgot to mention that the AMD 760 will support DDR SDRAM memory. On Sun, Sep 24, 2000 at 09:59:51PM -0700, Randy Bush wrote: > > why dont you surf on over to the www.asus.com website, poke around a > > little while, see what looks like it would meet your needs. > > did that. and they use all sorts of terms which folk who have not kept up > with mbs and chip sets don't understand, FSB, ServerWorks, AGPset, i820, > RDRAM, ... which it is not clear freebsd (4.1-stable) supports. > > e.g. the p3c-ls (or -s) look close to my needs if i don't want anything > faster than 733mhz, but does freebsd support the i820, the aic7892 (the > handbook says 789x, but i am cautious), ...? > > > smd ? > > sorry. smp. with 700+ cpu, i can live without smp. i have a dual-300 on > my desk now, and it it getting soggy and hard to light. > > >> i have used asus for a long time, so am a bit partial. this is for a > >> desktop, not the rack. > >> > >> so what is a good high-perf asus that's compatible this season > >> o atx > >> o takes decent speed processor(a) > >> o screaming scsi on board (like the aic7890/91 on the p2b-ds) > >> o agp > >> > >> optional > >> o smd optional but kinda like it > >> o 10/100 onboard optional > >> o video that XFree likes optional > > basically, i am a semi-competent net.geek and sysadmin of a decade or two, > etc., but have never had the time to keep up with all the latest hardwhere > gadgets. so when it's time to upgrade a limping box, i whine for help. > > randy > > > 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 Mon Sep 25 12: 0:31 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from mail.wolves.k12.mo.us (mail.wolves.k12.mo.us [207.160.214.1]) by hub.freebsd.org (Postfix) with ESMTP id B388A37B422 for ; Mon, 25 Sep 2000 12:00:28 -0700 (PDT) Received: from mail.wolves.k12.mo.us (cdillon@mail.wolves.k12.mo.us [207.160.214.1]) by mail.wolves.k12.mo.us (8.9.3/8.9.3) with ESMTP id OAA82382; Mon, 25 Sep 2000 14:00:20 -0500 (CDT) (envelope-from cdillon@wolves.k12.mo.us) Date: Mon, 25 Sep 2000 14:00:19 -0500 (CDT) From: Chris Dillon To: Lanny Baron Cc: Randy Bush , David Burton , freebsd-hardware@FreeBSD.ORG Subject: Re: asus recommendation 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, 25 Sep 2000, Lanny Baron wrote: > Hello, > In my HO, the INTEL (TM) D815EEAL which comes with onboard Intel > Pro100 as as desktop machine, works extremely well and fast. Uses > 133 MHZ bus for both ram and cpu and is inexpensive. Thats just fine for a desktop machine, but I wouldn't use one for a server. > IMHO, Asus, SUCKS big time. My pII400 is exactly 1/2 the speed of my PII > 266 with ASUS boards. Comparing it (Asus vs Intel D815)to a home/office > system I just built it was a joke to see the increase in perfomance. Thats funny, since ASUS consistently outperforms every other motherboard manufacturer in just about every benchmark anywhere that I've seen. Some of those benchmarks suck and are meaningless, but some are good and attempt to be as "real-world" as possible, and the fact that they take the top of nearly every benchmark (for consumer boards) that people have thrown at them should tell you something. Even ASUS has made a bad line of boards, though, so it might just be the particular model you have, or it could be a misconfiguration on your part. -- Chris Dillon - cdillon@wolves.k12.mo.us - cdillon@inter-linc.net FreeBSD: The fastest and most stable server OS on the planet. For Intel x86 and Alpha architectures. ( http://www.freebsd.org ) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Mon Sep 25 12:20:11 2000 Delivered-To: freebsd-hardware@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 618) id 3F3E037B43C; Mon, 25 Sep 2000 12:20:01 -0700 (PDT) Subject: Re: Help with WaveLAN Card In-Reply-To: <20000925111607.Q10523@schooner.svjava.com> from Eric Kozowski at "Sep 25, 2000 11:16:07 am" To: eric@svjava.com (Eric Kozowski) Date: Mon, 25 Sep 2000 12:20:01 -0700 (PDT) Cc: antonio@icon.net.mx, mobile@FreeBSD.ORG, hardware@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Message-Id: <20000925192001.3F3E037B43C@hub.freebsd.org> From: wpaul@FreeBSD.ORG (Bill Paul) Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > On Mon, Sep 25, 2000 at 11:11:51AM -0700, Antonio Varela Lizardi wrote: > > > > Apollogies in advance for the crossposting, but my deadline related to this > > matter it's very close. > > > > I have a Lucent WaveLAN Silver 11Mbps PCMCIA Card, a Texas Instrument > > (chipset recognized as 1225) PCMCIA-PCI Cardbus bridge (sold by lucent), a > > regular Desktop PC and FreeBSD 4.1-STABLE. I just cannot get the card to > > work. It's recognized sucessfully by pccardd, but I'm having an error: "tx > > buffer allocation failed" with any network operation over the card. Diggin > > out more, I've found that wi_seek( ) it's failing with a WI_TIMEOUT, when > > wi_alloc_nicmem( ) calls to alloc the tx buffer, when wi_init ( ) tries to > > initialize the card. The allocation of the management buffer suceeeds, and > > that sounds strange. The wi driver talks straight to the Hermes Controller, > > not using the card's firmware. I wonder if in this new product, the hardware > > has changed. In the wi manpage it's written about supporting 6Mbps cards, > > but never mentions 11Mbps cards. In the PAO FAQ found something about > > configuring the card with the MSDOS utility, but I just can't find it, > > neither CDROM/Website. Folks, you're my only hope, otherwise I'll have to > > install Linux. Any hint or bad news (the 11mbps card is supported?) will be > > welcome. Please help. Actually, the wi driver does not talk directly to the controller: it talks to the firmware. But it talks to the firmware directly rather than using the HCF (hardware control functions) library that Lucent normally uses. The libhcf library hides most of the hardware details from you. I chose not to use it because a) the original version of it that I got from Lucent was contaminated by the GPL, and b) the code is pretty yucky in my opinion. That said, the firmware interface is virtually identical for all of the cards, which includes the 2mbps, 6mbps and 11mbps ones. We're using the 11mbps gold cards in the office. The Orinoco cards should just be the same WaveLAN cards with a different name on them. > as per the many discussions, as are available in the archives, the pci > based bridge from lucent does not currently work. That may be, but he's not what he said. Read closer: he has a laptop with a particular cardbus bridge chipset, *not* a PCI card. I've heard of this problem before, but I don't know if it's directly related to the wi driver itself. The WaveLAN cards I have work with the laptops that I've tried here, as well as with the ISA-PCMCIA bridge adapter cards that came with the Webgear cards. If I can get my hands on a laptop with that particular chipset, I'll see if I can debug the problem. The 11mbps cards are supposed to work though. -Bill To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Mon Sep 25 12:32: 9 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from mass.osd.bsdi.com (adsl-63-206-89-203.dsl.snfc21.pacbell.net [63.206.89.203]) by hub.freebsd.org (Postfix) with ESMTP id 1FC8737B50C; Mon, 25 Sep 2000 12:31:54 -0700 (PDT) Received: from mass.osd.bsdi.com (localhost [127.0.0.1]) by mass.osd.bsdi.com (8.11.0/8.9.3) with ESMTP id e8PJVKA13966; Mon, 25 Sep 2000 12:31:21 -0700 (PDT) (envelope-from msmith@mass.osd.bsdi.com) Message-Id: <200009251931.e8PJVKA13966@mass.osd.bsdi.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: "O. Hartmann" Cc: freebsd-smp@freebsd.org, freebsd-hardware@freebsd.org Subject: Re: TYAN Thunder 2500/MP Table Error In-reply-to: Your message of "Mon, 25 Sep 2000 19:15:49 +0200." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 25 Sep 2000 12:31:20 -0700 From: Mike Smith Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org This is an informational message only, and you should ignore it. > Dear Sirs. > I run successfully a TYAN Thunder 2500 mainboard with FreeBSD 4.1-STABLE, BIOS Beta > 1.03/896 for the LSI 53C896 based SCSI controler. When booting, I obtain a lot of > SMP messages from the kernel, but at one stage, I receive this error: > > APIC_IO: Testing 8254 interrupt delivery > APIC_IO: Broken MP table detected: 8254 is not connected to IOAPIC #0 intpin 2 > APIC_IO: routing 8254 via 8259 and IOAPIC #0 intpin 0 > > SMP works fine, but it seems that there is something wron with the MP table. > Is this a serious error message or is it simply a warning? What kind of performance penalty does > it results in? And: hopefully, is there a chance to get rid of it with a new > BIOS update in the future? > > Thanks in advance, > > Gruss O. Hartmann > ------------------------------------------------------------------- > ohartman@ipamzlx.physik.uni-mainz.de > > Klimadatenserver des IPA, Universitaet Mainz > Netzwerk- und Systembetreuung > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-smp" in the body of the message > -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Mon Sep 25 12:40:42 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from eagle.prod.itd.earthlink.net (eagle.prod.itd.earthlink.net [207.217.120.24]) by hub.freebsd.org (Postfix) with ESMTP id B0EFA37B422 for ; Mon, 25 Sep 2000 12:40:23 -0700 (PDT) Received: from earthlink.net (1Cust132.tnt8.everett2.wa.da.uu.net [63.24.202.132]) by eagle.prod.itd.earthlink.net (8.9.3-EL_1_3/8.9.3) with ESMTP id MAA02772; Mon, 25 Sep 2000 12:40:21 -0700 (PDT) Received: (from odyseus2000@localhost) by earthlink.net (8.9.3/8.9.3) id MAA04170; Mon, 25 Sep 2000 12:37:01 -0700 (PDT) (envelope-from odyseus2000) Date: Mon, 25 Sep 2000 12:37:00 -0700 From: David Burton To: Chris Dillon Cc: freebsd-hardware@FreeBSD.org Subject: Re: asus recommendation Message-ID: <20000925123700.B4086@slick.earthlink.net> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.4i In-Reply-To: ; from cdillon@wolves.k12.mo.us on Mon, Sep 25, 2000 at 02:00:19PM -0500 Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org My first impression with an ASUS board (CUV4X) was good except for one nagging factor. They were either too lazy or too cheap to integrate the second com ports right beside the first on the atx edge. But rather put as a header on the board and mounted it on a bracket to take up an expansion slot. Looking at some other models I saw that they had put both coms on the atx edge(what ever the proper name for it is). IMHO that really sucks. On Mon, Sep 25, 2000 at 02:00:19PM -0500, Chris Dillon wrote: > On Mon, 25 Sep 2000, Lanny Baron wrote: > > > Hello, > > In my HO, the INTEL (TM) D815EEAL which comes with onboard Intel > > Pro100 as as desktop machine, works extremely well and fast. Uses > > 133 MHZ bus for both ram and cpu and is inexpensive. > > Thats just fine for a desktop machine, but I wouldn't use one for a > server. > > > IMHO, Asus, SUCKS big time. My pII400 is exactly 1/2 the speed of my PII > > 266 with ASUS boards. Comparing it (Asus vs Intel D815)to a home/office > > system I just built it was a joke to see the increase in perfomance. > > Thats funny, since ASUS consistently outperforms every other > motherboard manufacturer in just about every benchmark anywhere that > I've seen. Some of those benchmarks suck and are meaningless, but > some are good and attempt to be as "real-world" as possible, and the > fact that they take the top of nearly every benchmark (for consumer > boards) that people have thrown at them should tell you something. > Even ASUS has made a bad line of boards, though, so it might just be > the particular model you have, or it could be a misconfiguration on > your part. > > > -- Chris Dillon - cdillon@wolves.k12.mo.us - cdillon@inter-linc.net > FreeBSD: The fastest and most stable server OS on the planet. > For Intel x86 and Alpha architectures. ( http://www.freebsd.org ) > > > > > 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 Mon Sep 25 12:55: 0 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from mail.wolves.k12.mo.us (mail.wolves.k12.mo.us [207.160.214.1]) by hub.freebsd.org (Postfix) with ESMTP id 1091A37B422 for ; Mon, 25 Sep 2000 12:54:53 -0700 (PDT) Received: from mail.wolves.k12.mo.us (cdillon@mail.wolves.k12.mo.us [207.160.214.1]) by mail.wolves.k12.mo.us (8.9.3/8.9.3) with ESMTP id OAA83523; Mon, 25 Sep 2000 14:54:49 -0500 (CDT) (envelope-from cdillon@wolves.k12.mo.us) Date: Mon, 25 Sep 2000 14:54:49 -0500 (CDT) From: Chris Dillon To: David Burton Cc: freebsd-hardware@FreeBSD.org Subject: Re: asus recommendation In-Reply-To: <20000925123700.B4086@slick.earthlink.net> 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, 25 Sep 2000, David Burton wrote: > My first impression with an ASUS board (CUV4X) was good except for > one nagging factor. They were either too lazy or too cheap to > integrate the second com ports right beside the first on the atx > edge. But rather put as a header on the board and mounted it on a > bracket to take up an expansion slot. Looking at some other models > I saw that they had put both coms on the atx edge(what ever the > proper name for it is). IMHO that really sucks. I'm sure it wasn't out of lazyness, since the header, cable, and bracket would cost them more money and more engineering time than just putting the second COM port on the ATX backplane. Was on-board video an option on that board? If so, thats where the video connector would have gone. -- Chris Dillon - cdillon@wolves.k12.mo.us - cdillon@inter-linc.net FreeBSD: The fastest and most stable server OS on the planet. For Intel x86 and Alpha architectures. ( http://www.freebsd.org ) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Mon Sep 25 13: 6:52 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from ipamzlx.physik.uni-mainz.de (ipamzlx.Physik.Uni-Mainz.DE [134.93.180.54]) by hub.freebsd.org (Postfix) with ESMTP id AC42D37B424 for ; Mon, 25 Sep 2000 13:06:47 -0700 (PDT) Received: from ipamzlx.Physik.Uni-Mainz.DE (ipamzlx.Physik.Uni-Mainz.DE [134.93.180.54]) by ipamzlx.physik.uni-mainz.de (8.11.0/8.9.3) with ESMTP id e8PK80N36797 for ; Mon, 25 Sep 2000 22:08:00 +0200 (CEST) (envelope-from ohartman@ipamzlx.physik.uni-mainz.de) Date: Mon, 25 Sep 2000 22:08:00 +0200 (CEST) From: "O. Hartmann" To: freebsd-hardware@freebsd.org Subject: Oboard ES1373 sound chip 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 have a mainboard with onboard sound chip ES1373 (as a PCI device). I use device pcm0 in kernel and I got response while booting: pcm0: port 0xfcc0-0xfcff irq 17 at device 2.0 on pci0 But I can not run any kind of amp, x11amp or othe sound-based software, I cannot do /dev/MAKEDEV /dev/pcm0. Is 1373 chip not yet supported or is anything wrong in my doing? Sorry about this silly question, but sound is just a luxury, not a necessity. Gruss O. Hartmann ------------------------------------------------------------------- ohartman@ipamzlx.physik.uni-mainz.de Klimadatenserver des IPA, Universitaet Mainz Netzwerk- und Systembetreuung To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Mon Sep 25 13:30:31 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from penguin.prod.itd.earthlink.net (penguin.prod.itd.earthlink.net [207.217.120.134]) by hub.freebsd.org (Postfix) with ESMTP id C694B37B42C for ; Mon, 25 Sep 2000 13:30:25 -0700 (PDT) Received: from earthlink.net (1Cust132.tnt8.everett2.wa.da.uu.net [63.24.202.132]) by penguin.prod.itd.earthlink.net (8.9.3-EL_1_3/8.9.3) with ESMTP id NAA07413; Mon, 25 Sep 2000 13:30:22 -0700 (PDT) Received: (from odyseus2000@localhost) by earthlink.net (8.9.3/8.9.3) id NAA04266; Mon, 25 Sep 2000 13:27:17 -0700 (PDT) (envelope-from odyseus2000) Date: Mon, 25 Sep 2000 13:27:17 -0700 From: David Burton To: Chris Dillon Cc: freebsd-hardware@FreeBSD.org Subject: Re: asus recommendation Message-ID: <20000925132717.C4086@slick.earthlink.net> References: <20000925123700.B4086@slick.earthlink.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.4i In-Reply-To: ; from cdillon@wolves.k12.mo.us on Mon, Sep 25, 2000 at 02:54:49PM -0500 Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org no onboard video. It does have on board sound which was above it. I thought this perhaps percluded them. However I was at a computer store that had different mboards laying out(still in the ESD sack) so you could look at them i.e. on display. I was looking at some of the asus ones and noted another model that had the on board audio but implemented both com ports beneath it on the first row, so it was definately because they couldnt do it. though perhaps with that chipset maybe had problems routing the traces from the chip to the connector, so they just made it into a header instead. Other than that just laziness is the only other reason. Or perhaps I am remember it wrong and that second connector wasnt a com port but rather a video port, but even if that is the case I would think they could put a com port in that real estate. I like my Tyan but the traces are too close to the mounting screw hole and such that they recommend using plastic stanoffs and only one screw and the installed cards to hold it in place. sound like a jurry-rig. so I havent fired that one up yet because I was putting it in an old full tower AT case I had and cannot do it as they recommend. I am pretty sure the metal standoffs are not on any traces. I pray :-). And of course no issues with my Intel Seattle BX-2. On Mon, Sep 25, 2000 at 02:54:49PM -0500, Chris Dillon wrote: > On Mon, 25 Sep 2000, David Burton wrote: > > > My first impression with an ASUS board (CUV4X) was good except for > > one nagging factor. They were either too lazy or too cheap to > > integrate the second com ports right beside the first on the atx > > edge. But rather put as a header on the board and mounted it on a > > bracket to take up an expansion slot. Looking at some other models > > I saw that they had put both coms on the atx edge(what ever the > > proper name for it is). IMHO that really sucks. > > I'm sure it wasn't out of lazyness, since the header, cable, and > bracket would cost them more money and more engineering time than just > putting the second COM port on the ATX backplane. Was on-board video > an option on that board? If so, thats where the video connector would > have gone. > > > -- Chris Dillon - cdillon@wolves.k12.mo.us - cdillon@inter-linc.net > FreeBSD: The fastest and most stable server OS on the planet. > For Intel x86 and Alpha architectures. ( http://www.freebsd.org ) > > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Mon Sep 25 14: 0:55 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from msgbas1tx.cos.agilent.com (msgbas1tx.cos.agilent.com [192.6.9.34]) by hub.freebsd.org (Postfix) with ESMTP id 5118C37B43E; Mon, 25 Sep 2000 14:00:48 -0700 (PDT) Received: from andom1.an.hp.com (andom1.an.hp.com [15.4.128.104]) by msgbas1tx.cos.agilent.com (Postfix) with ESMTP id D3985456; Mon, 25 Sep 2000 15:00:43 -0600 (MDT) Received: from mina.soco.agilent.com (mina.soco.agilent.com [141.121.54.157]) by andom1.an.hp.com (Postfix) with ESMTP id 0569D126; Mon, 25 Sep 2000 17:00:42 -0400 (EDT) Received: from mina.soco.agilent.com (darrylo@localhost [127.0.0.1]) by mina.soco.agilent.com (8.9.3 (PHNE_18979)/8.9.3 SMKit7.0) with ESMTP id OAA18978; Mon, 25 Sep 2000 14:00:39 -0700 (PDT) Message-Id: <200009252100.OAA18978@mina.soco.agilent.com> To: wpaul@FreeBSD.ORG (Bill Paul) Cc: eric@svjava.com (Eric Kozowski), mobile@FreeBSD.ORG, hardware@FreeBSD.ORG Subject: Re: Help with WaveLAN Card Reply-To: Darryl Okahata In-Reply-To: Your message of "Mon, 25 Sep 2000 12:20:01 PDT." <20000925192001.3F3E037B43C@hub.freebsd.org> Mime-Version: 1.0 (generated by tm-edit 1.6) Content-Type: text/plain; charset=US-ASCII Date: Mon, 25 Sep 2000 14:00:38 -0700 From: Darryl Okahata Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org wpaul@FreeBSD.ORG (Bill Paul) wrote: > > as per the many discussions, as are available in the archives, the pci > > based bridge from lucent does not currently work. > > That may be, but he's not what he said. Read closer: he has a laptop > with a particular cardbus bridge chipset, *not* a PCI card. I've heard Huh? Which poster are you talking about? The original poster, to which Eric was replying, has a *DESKTOP*; here's a (reformatted) quote: ... I have a Lucent WaveLAN Silver 11Mbps PCMCIA Card, a Texas Instrument (chipset recognized as 1225) PCMCIA-PCI Cardbus bridge (sold by lucent), a regular Desktop PC and FreeBSD 4.1-STABLE. ... He never said that he has a laptop. As Eric said, this poster is probably running into the TI1225 PCI-PCMCIA issue, which Warner has not yet had the time to investigate/fix (I believe). Now, there was a different poster (Andreas Braukmann ), who does have a problematic laptop (a Sony Vaio). Perhaps you're getting the two posters confused? Interestingly enough, the symptoms of the two problems appear to be the same. I can't help but wonder if the cause isn't, also. -- Darryl Okahata darrylo@soco.agilent.com DISCLAIMER: this message is the author's personal opinion and does not constitute the support, opinion, or policy of Agilent Technologies, or of the little green men that have been following him all day. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Mon Sep 25 14:23:13 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from ipamzlx.physik.uni-mainz.de (ipamzlx.Physik.Uni-Mainz.DE [134.93.180.54]) by hub.freebsd.org (Postfix) with ESMTP id 2EFFC37B422; Mon, 25 Sep 2000 14:23:07 -0700 (PDT) Received: from ipamzlx.Physik.Uni-Mainz.DE (ipamzlx.Physik.Uni-Mainz.DE [134.93.180.54]) by ipamzlx.physik.uni-mainz.de (8.11.0/8.9.3) with ESMTP id e8PLOJN41917; Mon, 25 Sep 2000 23:24:20 +0200 (CEST) (envelope-from ohartman@ipamzlx.physik.uni-mainz.de) Date: Mon, 25 Sep 2000 23:24:19 +0200 (CEST) From: "O. Hartmann" To: freebsd-hardware@freebsd.org Cc: freebsd-questions@freebsd.org Subject: Fortran 90/95 problems ... 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 Dear Sirs. A few weeks ago, I installed sucessfully Lahey/Fujitsu Fortran95 compiler on our FreeBSD/SMP box running FreeBSD 4.1-STABLE. I compiled a testbed (a simulation model of particel's collision) under this compiler an it worked well, I could compile this program and run it. Several days ago, some kernel patches were made, and I remember some Linux code was updated (Lahey/Fujitsu Fortran 95 compiler is to be run under Linux emulation!). Since then Lahey/Fujitsu F95 compiler does strange things. It compiles code three time and loose some options. When starting "lf95 -tpp ddscat" or compile some application we developed here and compiled them successfully three weeks ago, lf95 starts compiling, but the it compiles the stuff a second and third time and whenever it starts an additional, unnecessary round, it outputs some error messages about the unknown option "pp", it loose obviously the preceding t. But why? This phenomenon occurs on two machine, one SMP server and one UP system (K6-2). I wiped out completely my linux-emulation packages and installed them again. Nothing happened in another way. This seems to me to be some breakages in the code donated these days to the stable kernel ... Gruss O. Hartmann ------------------------------------------------------------------- ohartman@ipamzlx.physik.uni-mainz.de Klimadatenserver des IPA, Universitaet Mainz Netzwerk- und Systembetreuung To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Mon Sep 25 14:39:59 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 7FC3C37B424; Mon, 25 Sep 2000 14:39:54 -0700 (PDT) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id PAA04097; Mon, 25 Sep 2000 15:39:48 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id PAA07209; Mon, 25 Sep 2000 15:39:48 -0600 (MDT) Message-Id: <200009252139.PAA07209@harmony.village.org> To: Darryl Okahata Subject: Re: Help with WaveLAN Card Cc: wpaul@FreeBSD.ORG (Bill Paul), eric@svjava.com (Eric Kozowski), mobile@FreeBSD.ORG, hardware@FreeBSD.ORG In-reply-to: Your message of "Mon, 25 Sep 2000 14:00:38 PDT." <200009252100.OAA18978@mina.soco.agilent.com> References: <200009252100.OAA18978@mina.soco.agilent.com> Date: Mon, 25 Sep 2000 15:39:48 -0600 From: Warner Losh Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In message <200009252100.OAA18978@mina.soco.agilent.com> Darryl Okahata writes: : ... I have a Lucent WaveLAN Silver 11Mbps PCMCIA Card, a Texas : Instrument (chipset recognized as 1225) PCMCIA-PCI Cardbus : bridge (sold by lucent), a regular Desktop PC and FreeBSD : 4.1-STABLE. ... This conifguration isn't supported until we can do pci routing of interrupts. In laptops the cardbus bridge is connected directly to the south bridge so can ise the ISA interrupts. On the PCI bus this isn't the case. These cards come up w/o interrupts assigned to them. Most of thenm are wired to have two interrupts (INTA and INTB), but we need more work to properly route the interrupts over the INTA and INTB pins as well as setting thngs up so we know which IRQ fires when these signals on the PCI bus are asserted. Yamamoto-san has some code to do this, but I haven't had the time to look into adding this functionality. It is fairly x86 based, and I'd like at least an interface that could be supported on the Alpha. Of course pcibios is fairly x86 centric, iirc. : He never said that he has a laptop. As Eric said, this poster is : probably running into the TI1225 PCI-PCMCIA issue, which Warner has not : yet had the time to investigate/fix (I believe). Fix, no. Investigate yes. It is as above :-(. : Now, there was a different poster (Andreas Braukmann : ), who does have a problematic laptop (a Sony : Vaio). Perhaps you're getting the two posters confused? The VAIO problem is almost certainly a IRQ conflict problem, but I've not had the time to help out on that one. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Mon Sep 25 14:42:11 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id B593B37B422; Mon, 25 Sep 2000 14:42:06 -0700 (PDT) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id PAA04133; Mon, 25 Sep 2000 15:42:03 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id PAA07276; Mon, 25 Sep 2000 15:42:03 -0600 (MDT) Message-Id: <200009252142.PAA07276@harmony.village.org> To: wpaul@FreeBSD.ORG (Bill Paul) Subject: Re: Help with WaveLAN Card Cc: eric@svjava.com (Eric Kozowski), antonio@icon.net.mx, mobile@FreeBSD.ORG, hardware@FreeBSD.ORG In-reply-to: Your message of "Mon, 25 Sep 2000 12:20:01 PDT." <20000925192001.3F3E037B43C@hub.freebsd.org> References: <20000925192001.3F3E037B43C@hub.freebsd.org> Date: Mon, 25 Sep 2000 15:42:03 -0600 From: Warner Losh Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I've used a wavelan gold card as well as a silver card on my Sony VAIO 505TS at the Usenix security conference in Denver. So if others are having a problem with it, I think it is an IRQ problem. It smells that way to me. It isn't a wi driver problem as far as I can tell. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Mon Sep 25 15:26:20 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from schooner.svjava.com (schooner.svjava.com [204.75.228.3]) by hub.freebsd.org (Postfix) with ESMTP id 96B0537B43C; Mon, 25 Sep 2000 15:26:17 -0700 (PDT) Received: (from kozowski@localhost) by schooner.svjava.com (8.9.1a/svjava.com) id PAA14825; Mon, 25 Sep 2000 15:26:13 -0700 (PDT) Date: Mon, 25 Sep 2000 15:26:13 -0700 From: Eric Kozowski To: Warner Losh Cc: Bill Paul , antonio@icon.net.mx, mobile@FreeBSD.ORG, hardware@FreeBSD.ORG Subject: Re: Help with WaveLAN Card Message-ID: <20000925152612.B10523@schooner.svjava.com> References: <20000925192001.3F3E037B43C@hub.freebsd.org> <200009252142.PAA07276@harmony.village.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.2i In-Reply-To: <200009252142.PAA07276@harmony.village.org>; from imp@village.org on Mon, Sep 25, 2000 at 03:42:03PM -0600 Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Mon, Sep 25, 2000 at 03:42:03PM -0600, Warner Losh wrote: > I've used a wavelan gold card as well as a silver card on my Sony VAIO > 505TS at the Usenix security conference in Denver. So if others are > having a problem with it, I think it is an IRQ problem. It smells > that way to me. It isn't a wi driver problem as far as I can tell. > > Warner they work in my 505s, too. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Mon Sep 25 16: 3:49 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from cage.tse-online.de (cage.tse-online.de [194.97.69.170]) by hub.freebsd.org (Postfix) with SMTP id 955F837B422 for ; Mon, 25 Sep 2000 16:03:45 -0700 (PDT) Received: (qmail 51182 invoked by uid 1000); 25 Sep 2000 23:10:39 -0000 Date: Tue, 26 Sep 2000 01:10:39 +0200 From: Andreas Braukmann To: hardware@FreeBSD.ORG Subject: Re: Help with WaveLAN Card Message-ID: <20000926011039.A51104@cage.tse-online.de> References: <200009252100.OAA18978@mina.soco.agilent.com> <200009252139.PAA07209@harmony.village.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <200009252139.PAA07209@harmony.village.org>; from imp@village.org on Mon, Sep 25, 2000 at 03:39:48PM -0600 Organization: TSE GmbH - Neue Medien Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi Warner, On Mon, Sep 25, 2000 at 03:39:48PM -0600, Warner Losh wrote: > : Now, there was a different poster (Andreas Braukmann > : ), Hey, ... that' me ;) > : who does have a problematic laptop (a Sony > : Vaio). Perhaps you're getting the two posters confused? It's a Sony Vaio 505X. > The VAIO problem is almost certainly a IRQ conflict problem, but I've > not had the time to help out on that one. I'm nearly sure, that it's not an irq conflict. The pcic0 probes on IRQ 10. The wi-driver gets IRQ 5. It seems that there are no other devices on these interrupts. I'll keep the rest of this discussion on the thread I posted my problem originally to. I might be able to supply you with a ssh-account on the Vaio. I have only *one* not so small problem. Since the Vaio has only one pcmcia-slot, ... (you get the picture ...) -Andreas P.S.: I'll try to get a freebsd supported usb ethernet card, if anybody would like to take a closer look on the wi-/pcmcia problem. -- : Anti-Spam Petition: http://www.politik-digital.de/spam/ : : PGP-Key: http://www.tse-online.de/~ab/public-key : : Key fingerprint: 12 13 EF BC 22 DD F4 B6 3C 25 C9 06 DC D3 45 9B : To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Mon Sep 25 16:16:59 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from cage.tse-online.de (cage.tse-online.de [194.97.69.170]) by hub.freebsd.org (Postfix) with SMTP id 4C91537B422 for ; Mon, 25 Sep 2000 16:16:10 -0700 (PDT) Received: (qmail 51213 invoked by uid 1000); 25 Sep 2000 23:23:04 -0000 Date: Tue, 26 Sep 2000 01:23:04 +0200 From: Andreas Braukmann To: Darryl Okahata Cc: freebsd-hardware@FreeBSD.ORG Subject: Re: Lucent Wavelan vs. wi-driver Message-ID: <20000926012304.B51104@cage.tse-online.de> References: <20000924004338.B37311@cage.tse-online.de> <200009240243.TAA16209@mina.soco.agilent.com> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="bp/iNruPH9dso1Pn" Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <200009240243.TAA16209@mina.soco.agilent.com>; from darrylo@soco.agilent.com on Sat, Sep 23, 2000 at 07:43:38PM -0700 Organization: TSE GmbH - Neue Medien Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org --bp/iNruPH9dso1Pn Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Hi Darryl, hi Warner, ... hi there, I grabbed a few pieces of further information. On Sat, Sep 23, 2000 at 07:43:38PM -0700, Darryl Okahata wrote: > Andreas Braukmann wrote: > > > The pccardd recognizes the wavelan card and binds it (as expected) > > to the the wi driver. > [ ... ] > > Bringing up the interface with ifconfig results in > > "wi0: tx buffer allocation failed" messages. > > If you're seeing this, the driver initialization is failing. > It probably won't help, but you could post a verbose dmesg, It's attached to this message. > as well as the bootup console messages (many of which are NOT > placed into dmesg or /var/log/messages). It didn't look like as there were any additional messages. The rc.pccard redirects all output (stdout and stderr) to /var/log/pccard.debug. This file stays empty. This message should have 3 attachements. 1. 'theDmesg' - the verbose boot messages 2. 'theMessages' - the syslog messages generated by pccardd. I killed the pccardd and restarted it with the -d Flag. Doing an'ifconfig' results in the mentioned error messages. 3. 'pccard.dumpcis' - the output of an 'pccardc dumpcis' with the lucent card inserted. I'd appreciate all help I could get and would gladfully help out with an ssh-account (for really interested folks) on the vaio. TIA, Andreas -- : Anti-Spam Petition: http://www.politik-digital.de/spam/ : : PGP-Key: http://www.tse-online.de/~ab/public-key : : Key fingerprint: 12 13 EF BC 22 DD F4 B6 3C 25 C9 06 DC D3 45 9B : --bp/iNruPH9dso1Pn Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename=theDmesg Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 4.1-RELEASE #2: Mon Sep 25 23:19:48 CEST 2000 toor@troubadour.intern.tse:/usr/src/sys/compile/VAIO Calibrating clock(s) ... TSC clock: 331581429 Hz, i8254 clock: 1193190 Hz CLK_USE_I8254_CALIBRATION not specified - using default frequency Timecounter "i8254" frequency 1193182 Hz CLK_USE_TSC_CALIBRATION not specified - using old calibration method CPU: Pentium II/Pentium II Xeon/Celeron (331.58-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x66a Stepping = 10 Features=0x183f9ff real memory = 67043328 (65472K bytes) Physical memory chunk(s): 0x00001000 - 0x0009efff, 647168 bytes (158 pages) 0x00381000 - 0x03fdbfff, 63287296 bytes (15451 pages) avail memory = 61509632 (60068K bytes) bios32: Found BIOS32 Service Directory header at 0xc00f6d80 bios32: Entry = 0xfd8a0 (c00fd8a0) Rev = 0 Len = 1 pcibios: PCI BIOS entry at 0x11e pnpbios: Found PnP BIOS data at 0xc00f6db0 pnpbios: Entry = f0000:b358 Rev = 1.0 pnpbios: Event flag at 400 Other BIOS signatures found: ACPI: 000f6d20 Preloaded elf kernel "kernel" at 0xc0368000. Preloaded userconfig_script "/boot/kernel.conf" at 0xc03680a8. Pentium Pro MTRR support enabled md0: Malloc disk Creating DISK md0 Math emulator present pci_open(1): mode 1 addr port (0x0cf8) is 0x80003904 pci_open(1a): mode1res=0x80000000 (0x80000000) pci_cfgcheck: device 0 [class=060000] [hdr=00] is there (id=71928086) npx0: on motherboard npx0: INT 16 interface pci_open(1): mode 1 addr port (0x0cf8) is 0x00000000 pci_open(1a): mode1res=0x80000000 (0x80000000) pci_cfgcheck: device 0 [class=060000] [hdr=00] is there (id=71928086) pcib0: on motherboard found-> vendor=0x8086, dev=0x7192, revid=0x03 class=06-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 map[10]: type 1, range 32, base 00000000, size 26 found-> vendor=0x8086, dev=0x7110, revid=0x02 class=06-01-00, hdrtype=0x00, mfdev=1 subordinatebus=0 secondarybus=0 found-> vendor=0x8086, dev=0x7111, revid=0x01 class=01-01-80, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 map[20]: type 1, range 32, base 0000fc90, size 4 found-> vendor=0x8086, dev=0x7112, revid=0x01 class=0c-03-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=d, irq=9 map[20]: type 1, range 32, base 0000fca0, size 5 found-> vendor=0x8086, dev=0x7113, revid=0x03 class=06-80-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 map[90]: type 1, range 32, base 00001040, size 4 found-> vendor=0x104d, dev=0x8039, revid=0x02 class=0c-00-10, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=a, irq=9 map[10]: type 1, range 32, base fedf7000, size 11 map[14]: type 1, range 32, base fedf7c00, size 9 found-> vendor=0x1073, dev=0x0010, revid=0x02 class=04-01-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=a, irq=9 map[10]: type 1, range 32, base fedf8000, size 15 map[14]: type 1, range 32, base 0000fcc0, size 6 map[18]: type 3, range 32, base 0000fc8c, size 2 found-> vendor=0x10c8, dev=0x0005, revid=0x20 class=03-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=a, irq=3 map[10]: type 1, range 32, base fd000000, size 24 map[14]: type 1, range 32, base fe800000, size 22 map[18]: type 1, range 32, base fec00000, size 20 found-> vendor=0x1180, dev=0x0475, revid=0x80 class=06-07-00, hdrtype=0x02, mfdev=0 subordinatebus=0 secondarybus=0 intpin=a, irq=255 pci0: on pcib0 isab0: at device 7.0 on pci0 isa0: on isab0 atapci0: port 0xfc90-0xfc9f at device 7.1 on pci0 ata0: iobase=0x01f0 altiobase=0x03f6 bmaddr=0xfc90 ata0: mask=03 status0=50 status1=00 ata0: mask=03 status0=50 status1=00 ata0: devices = 0x1 ata0: at 0x1f0 irq 14 on atapci0 ata1: iobase=0x0170 altiobase=0x0376 bmaddr=0xfc98 ata1: mask=00 status0=a5 status1=a5 ata1: probe allocation failed uhci0: port 0xfca0-0xfcbf irq 9 at device 7.2 on pci0 usb0: on uhci0 usb0: USB revision 1.0 uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered uhub0: port 1 power on failed, IOERROR uhub0: port 2 power on failed, IOERROR chip1: port 0x1040-0x104f at device 7.3 on pci0 pci0: (vendor=0x104d, dev=0x8039) at 8.0 irq 9 pci0: (vendor=0x1073, dev=0x0010) at 9.0 irq 9 pci0: (vendor=0x10c8, dev=0x0005) at 10.0 irq 3 pcic-pci0: at device 12.0 on pci0 pcic-pci0: Legacy address set to 0x3e0 PCI Config space: 00: 04751180 02100007 06070080 00020000 10: 00000000 020000dc 00000000 00000000 20: 00000000 00000000 00000000 00000000 30: 00000000 00000000 00000000 078001ff 40: 8061104d 000003e1 00000000 00000000 50: 00000000 00000000 00000000 00000000 60: 00000000 00000000 00000000 00000000 70: 00000000 00000000 00000000 00000000 80: 00a20001 00000000 04630463 30000000 90: 00000000 00000000 00000000 00000000 Cardbus Socket registers: 00: f000ff53: f000ff53: f000e2c3: f000ff53: 10: f000ff53: f000ff54: f000a0c7: f000ff53: ExCa registers: 00: eb 88 d5 43 30 d2 66 f7 f3 88 d7 5a 66 3d ff 03 10: 00 00 fb 77 44 86 c4 c0 c8 02 08 e8 40 91 88 fe 20: 28 e0 8a 66 02 38 e0 72 02 88 e0 bf 05 00 c4 5e 30: 04 50 b4 02 cd 13 5b 73 0a 4f 74 1c 30 e4 cd 13 Trying Read_Port at 203 Trying Read_Port at 243 Trying Read_Port at 283 Trying Read_Port at 2c3 Trying Read_Port at 303 Trying Read_Port at 343 Trying Read_Port at 383 Trying Read_Port at 3c3 ata-: ata0 exists, using next available unit number ata-: ata1 exists, using next available unit number isa_probe_children: disabling PnP devices isa_probe_children: probing non-PnP devices fdc0: direction bit not set fdc0: cmd 3 failed at out byte 1 of 3 ata3: iobase=0x0170 altiobase=0x0376 bmaddr=0x0000 ata3: mask=00 status0=a5 status1=a5 ata3: probe allocation failed aha0: not probed (disabled) aic0: not probed (disabled) atkbdc0: at port 0x60,0x64 on isa0 atkbd0: flags 0x1 irq 1 on atkbdc0 atkbd: the current kbd controller command byte 0047 atkbd: keyboard ID 0x41ab (2) kbdc: RESET_KBD return code:00fa kbdc: RESET_KBD status:00aa kbd0 at atkbd0 kbd0: atkbd0, AT 101/102 (2), config:0x1, flags:0x3d0000 psm0: current command byte:0047 kbdc: TEST_AUX_PORT status:0000 kbdc: RESET_AUX return code:00fa kbdc: RESET_AUX status:00aa kbdc: RESET_AUX ID:0000 psm: status 00 02 64 psm: status 00 00 64 psm: status 00 03 64 psm: status 00 03 64 psm: data 08 00 00 psm: status 53 02 14 psm: data 08 00 00 psm: status 00 02 64 psm0: irq 12 on atkbdc0 psm0: model GlidePoint, device ID 0-00, 2 buttons psm0: config:00000000, flags:00000000, packet size:3 psm0: syncmask:c0, syncbits:00 vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 fb0: vga0, vga, type:VGA (5), flags:0x7007f fb0: port:0x3c0-0x3df, crtc:0x3d4, mem:0xa0000 0x20000 fb0: init mode:24, bios mode:3, current mode:24 fb0: window:0xc00b8000 size:32k gran:32k, buf:0 size:32k VGA parameters upon power-up 50 18 10 00 00 00 03 00 02 67 5f 4f 50 82 55 81 bf 1f 00 4f 0d 0e 00 00 07 80 9c 8e 8f 28 1f 96 b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff VGA parameters in BIOS for mode 24 50 18 10 00 10 00 03 00 02 67 5f 4f 50 82 55 81 bf 1f 00 4f 0d 0e 00 00 00 00 9c 8e 8f 28 1f 96 b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff EGA/VGA parameters to be used for mode 24 50 18 10 00 10 00 03 00 02 67 5f 4f 50 82 55 81 bf 1f 00 4f 0d 0e 00 00 00 00 9c 8e 8f 28 1f 96 b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> sc0: fb0, kbd0, terminal emulator: sc (syscons terminal) pcic0: at port 0x3e0 iomem 0xd0000 irq 10 on isa0 pcic0: management irq 10 pccard0: on pcic0 pcic1: not probed (disabled) sio0: irq maps: 0x1 0x11 0x1 0x1 sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio1: configured irq 3 not in bitmap of probed irqs 0 sio1: irq maps: 0x1 0x1 0x1 0x1 sio1: probe failed test(s): 0 1 2 4 6 7 9 sio2: not probed (disabled) sio3: not probed (disabled) ppc0: parallel port found at 0x378 ppc0: using extended I/O port range ppc0: SPP ppc0: at port 0x378-0x37f irq 7 on isa0 ppc0: Generic chipset (NIBBLE-only) in COMPATIBLE mode ppi0: on ppbus0 lpt0: on ppbus0 lpt0: Interrupt-driven port plip0: on ppbus0 bpf: lp0 attached ed0: not probed (disabled) isa_probe_children: probing PnP devices BIOS Geometries: 0:0313fe3f 0..787=788 cylinders, 0..254=255 heads, 1..63=63 sectors 0 accounted for Device configuration finished. bpf: sl0 attached bpf: ppp0 attached new masks: bio 684200, tty 631092, net 671092 bpf: lo0 attached bpf: gif0 attached bpf: gif1 attached bpf: gif2 attached bpf: gif3 attached bpf: faith0 attached ata0-master: success setting up UDMA2 mode on PIIX4 chip ad0: ATA-4 disk at ata0 as master ad0: 6194MB (12685680 sectors), 13424 cyls, 15 heads, 63 S/T, 512 B/S ad0: 16 secs/int, 1 depth queue, UDMA33 ad0: piomode=4 dmamode=2 udmamode=2 cblid=0 Creating DISK ad0 Creating DISK wd0 Mounting root from ufs:/dev/ad0s2a ad0s1: type 0xb, start 63, end = 4032314, size 4032252 : OK ad0s2: type 0xa5, start 4032315, end = 12209399, size 8177085 : OK start_init: trying /sbin/init Linux-ELF exec handler installed splash: image decoder found: green_saver --bp/iNruPH9dso1Pn Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename=theMessages Sep 25 23:46:24 troubadour pccardd[246]: pccardd started Sep 25 23:46:50 troubadour /kernel: pccard: card inserted, slot 0 Sep 25 23:46:56 troubadour pccardd[246]: Card "Lucent Technologies"("WaveLAN/IEEE") [Version 01.01] [] matched "Lucent Technologies" ("WaveLAN/IEEE") [(null)] [(null)] Sep 25 23:47:02 troubadour /kernel: pcic: I/O win 0 flags 15 240-27f Sep 25 23:47:02 troubadour /kernel: pcic: I/O win 0 flags 5 240-27f Sep 25 23:47:02 troubadour /kernel: wi0: at port 0x240-0x27f irq 5 slot 0 on pccard0 Sep 25 23:47:02 troubadour /kernel: pcic: I/O win 0 flags 15 240-27f Sep 25 23:47:02 troubadour /kernel: wi0: Ethernet address: 00:02:2d:0d:9f:0b Sep 25 23:47:02 troubadour /kernel: bpf: wi0 attached Sep 25 23:47:02 troubadour pccardd[246]: wi0: Lucent Technologies (WaveLAN/IEEE) inserted. [ ... and now the ifconfig ... ] Sep 25 23:50:50 troubadour /kernel: wi0: tx buffer allocation failed Sep 25 23:50:51 troubadour /kernel: wi0: xmit failed Sep 25 23:50:56 troubadour /kernel: wi0: device timeout Sep 25 23:50:56 troubadour /kernel: wi0: tx buffer allocation failed Sep 25 23:50:59 troubadour /kernel: wi0: xmit failed Sep 25 23:51:04 troubadour /kernel: wi0: device timeout Sep 25 23:51:04 troubadour /kernel: wi0: tx buffer allocation failed --bp/iNruPH9dso1Pn Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="pccardc.dumpcis" Configuration data for card in slot 0 Tuple #1, code = 0x1 (Common memory descriptor), length = 3 000: 00 00 ff Common memory device information: Device number 1, type No device, WPS = OFF Speed = No speed, Memory block size = 512b, 1 units Tuple #2, code = 0x17 (Attribute memory descriptor), length = 4 000: 67 5a 08 ff Attribute memory device information: Device number 1, type SRAM, WPS = OFF Speed = 5.0 x 100 ns, Memory block size = reserved, 32 units Device number 2, type No device, WPS = OFF Speed = No speed, Memory block size = 512b, 1 units Tuple #3, code = 0x1d (Other conditions for attribute memory), length = 5 000: 01 67 5a 08 ff (MWAIT) Tuple #4, code = 0x15 (Version 1 info), length = 80 000: 05 00 4c 75 63 65 6e 74 20 54 65 63 68 6e 6f 6c 010: 6f 67 69 65 73 00 57 61 76 65 4c 41 4e 2f 49 45 020: 45 45 00 56 65 72 73 69 6f 6e 20 30 31 2e 30 31 030: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 040: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ff Version = 5.0, Manuf = [Lucent Technologies], card vers = [WaveLAN/IEEE] Addit. info = [Version 01.01],[] Tuple #5, code = 0x20 (Manufacturer ID), length = 4 000: 56 01 02 00 PCMCIA ID = 0x156, OEM ID = 0x2 Tuple #6, code = 0x21 (Functional ID), length = 2 000: 06 00 Network/LAN adapter Tuple #7, code = 0x22 (Functional EXT), length = 2 000: 01 07 Network technology: Wireless Tuple #8, code = 0x22 (Functional EXT), length = 5 000: 02 40 42 0f 00 Network speed: 1 Mb/sec Tuple #9, code = 0x22 (Functional EXT), length = 5 000: 02 80 84 1e 00 Network speed: 2 Mb/sec Tuple #10, code = 0x22 (Functional EXT), length = 5 000: 02 60 ec 53 00 Network speed: 5 Mb/sec Tuple #11, code = 0x22 (Functional EXT), length = 5 000: 02 c0 d8 a7 00 Network speed: 11 Mb/sec Tuple #12, code = 0x22 (Functional EXT), length = 2 000: 03 07 Network media: 2.4 GHz Tuple #13, code = 0x22 (Functional EXT), length = 8 000: 04 06 00 02 2d 0d 9f 0b Network node ID: 00 02 2d 0d 9f 0b Tuple #14, code = 0x22 (Functional EXT), length = 2 000: 05 01 Network connector: closed connector standard Tuple #15, code = 0x1a (Configuration map), length = 7 000: 03 01 e0 03 00 00 01 Reg len = 4, config register addr = 0x3e0, last config = 0x1 Registers: X------- Tuple #16, code = 0x1b (Configuration entry), length = 15 000: c1 01 19 76 c5 4b d5 19 36 36 05 46 7f ff ff Config index = 0x1(default) Interface byte = 0x1 (I/O) Vcc pwr: Minimum operating supply voltage: 4 x 1V, ext = 0x4b Maximum operating supply voltage: 5 x 1V, ext = 0x19 Max current average over 1 second: 3 x 100mA Max current average over 10 ms: 3 x 100mA Power down supply current: 1 x 10mA Card decodes 6 address lines, limited 8/16 Bit I/O IRQ modes: Level, Pulse IRQs: NMI IOCK BERR VEND 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 Tuple #17, code = 0xff (Terminator), length = 0 1 slots found --bp/iNruPH9dso1Pn-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Mon Sep 25 16:50:20 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from cage.tse-online.de (cage.tse-online.de [194.97.69.170]) by hub.freebsd.org (Postfix) with SMTP id EF08737B424 for ; Mon, 25 Sep 2000 16:50:05 -0700 (PDT) Received: (qmail 51429 invoked by uid 1000); 25 Sep 2000 23:56:59 -0000 Date: Tue, 26 Sep 2000 01:56:59 +0200 From: Andreas Braukmann To: Warner Losh Cc: Darryl Okahata , Bill Paul , Eric Kozowski , mobile@FreeBSD.ORG, hardware@FreeBSD.ORG Subject: Re: Help with WaveLAN Card Message-ID: <20000926015659.A51222@cage.tse-online.de> References: <200009252100.OAA18978@mina.soco.agilent.com> <200009252139.PAA07209@harmony.village.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <200009252139.PAA07209@harmony.village.org>; from imp@village.org on Mon, Sep 25, 2000 at 03:39:48PM -0600 Organization: TSE GmbH - Neue Medien Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi there, I don't trim the cc-Header to keep you informed. On Mon, Sep 25, 2000 at 03:39:48PM -0600, Warner Losh wrote: > : Now, there was a different poster (Andreas Braukmann > : ), who does have a problematic laptop (a Sony > : Vaio). Perhaps you're getting the two posters confused? > The VAIO problem is almost certainly a IRQ conflict problem, but I've > not had the time to help out on that one. Although I denied the possibility of an interrupt conflict (problem), I took the hint and did a little test. I changed my pccardd from using irq 5 to using irq 15. And what should I say? - I stand corrected. The lucent card runs without a hitch now. :) That's nice. But I really don't know why. Actually no other device was (is) sitting on the former used IRQ 5 and my other pcmcia network cards (Farallon 10baseT, 3COM 374TX) are running fine on IRQ 5. Many thanks for your attention and friendly assistance, Andreas -- : Anti-Spam Petition: http://www.politik-digital.de/spam/ : : PGP-Key: http://www.tse-online.de/~ab/public-key : : Key fingerprint: 12 13 EF BC 22 DD F4 B6 3C 25 C9 06 DC D3 45 9B : To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Mon Sep 25 16:50:39 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from cage.tse-online.de (cage.tse-online.de [194.97.69.170]) by hub.freebsd.org (Postfix) with SMTP id ED89937B43C for ; Mon, 25 Sep 2000 16:50:33 -0700 (PDT) Received: (qmail 51441 invoked by uid 1000); 25 Sep 2000 23:57:27 -0000 Date: Tue, 26 Sep 2000 01:57:26 +0200 From: Andreas Braukmann To: freebsd-hardware@FreeBSD.ORG Subject: Re: Lucent Wavelan vs. wi-driver Message-ID: <20000926015726.B51222@cage.tse-online.de> References: <20000924004338.B37311@cage.tse-online.de> <200009240243.TAA16209@mina.soco.agilent.com> <20000926012304.B51104@cage.tse-online.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <20000926012304.B51104@cage.tse-online.de>; from braukmann@tse-online.de on Tue, Sep 26, 2000 at 01:23:04AM +0200 Organization: TSE GmbH - Neue Medien Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi Darryl, Warner and still interested readers, ... On Tue, Sep 26, 2000 at 01:23:04AM +0200, Andreas Braukmann wrote: > > > The pccardd recognizes the wavelan card and binds it (as expected) > > > to the the wi driver. > > [ ... ] > > > Bringing up the interface with ifconfig results in > > > "wi0: tx buffer allocation failed" messages. ... the problem is *solved*. Warner,. ... I stand corrected. It seems, that it was an interrupt problem in fact. I'm avoiding the word 'conflict' intentionelly. Why? My 3COM 374TX 100baseT runs fine on IRQ 5. My Farralon 10baseT card runs fine on IRQ 5. Both are doing fine on IRQ 5 under Windows, too. No other device probes on IRQ 5. Despite of this, many many thanks for the crucial hint on the interrupts. Thanks, Andreas -- : Anti-Spam Petition: http://www.politik-digital.de/spam/ : : PGP-Key: http://www.tse-online.de/~ab/public-key : : Key fingerprint: 12 13 EF BC 22 DD F4 B6 3C 25 C9 06 DC D3 45 9B : To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Mon Sep 25 17: 9:35 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from wantadilla.lemis.com (wantadilla.lemis.com [192.109.197.80]) by hub.freebsd.org (Postfix) with ESMTP id 42DB737B422 for ; Mon, 25 Sep 2000 17:09:31 -0700 (PDT) Received: (from grog@localhost) by wantadilla.lemis.com (8.11.0/8.9.3) id e8Q06m038922; Tue, 26 Sep 2000 09:36:48 +0930 (CST) (envelope-from grog) Date: Tue, 26 Sep 2000 09:36:48 +0930 From: Greg Lehey To: "O. Hartmann" Cc: freebsd-hardware@FreeBSD.ORG Subject: Re: What kind of CPU-type when using AMD-K6 2? Message-ID: <20000926093648.A36385@wantadilla.lemis.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: ; from ohartman@ipamzlx.physik.uni-mainz.de on Mon, Sep 25, 2000 at 07:07:41PM +0200 Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-418-838-708 WWW-Home-Page: http://www.lemis.com/~grog X-PGP-Fingerprint: 6B 7B C3 8C 61 CD 54 AF 13 24 52 F8 6D A4 95 EF Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Monday, 25 September 2000 at 19:07:41 +0200, O. Hartmann wrote: > Dear Sirs. > > Some of our boxes running FreeBSD are based on AMD's K6-2 CPUs. My question is: > > Is AMD K6-2 CPU CPU type i586 or i686? At this time, I use in kernel > the option CPU type i586 but I want to ask for that here not to give > away performance by using a wrong type of CPU. Thanks for your > comments, That's correct. You can confirm this yourself with dmesg: CPU: AMD-K6tm w/ multimedia extensions (233.86-MHz 586-class CPU) Origin = "AuthenticAMD" Id = 0x562 Stepping = 2 Features=0x8001bf AMD Features=0x400<> Greg -- Finger grog@lemis.com for PGP public key See complete headers for address and phone numbers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Mon Sep 25 22:35:54 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from fremont.bolingbroke.com (adsl-216-102-90-210.dsl.snfc21.pacbell.net [216.102.90.210]) by hub.freebsd.org (Postfix) with ESMTP id BACF137B424; Mon, 25 Sep 2000 22:35:51 -0700 (PDT) Received: from fremont.bolingbroke.com (fremont.bolingbroke.com [216.102.90.210]) by fremont.bolingbroke.com (Pro-8.9.3/Pro-8.9.3) with ESMTP id WAA05750; Mon, 25 Sep 2000 22:35:51 -0700 (PDT) Date: Mon, 25 Sep 2000 22:35:51 -0700 (PDT) From: Ken Bolingbroke To: questions@FreeBSD.ORG Cc: freebsd-hardware@FreeBSD.ORG Subject: Kodak DC280, read as a disk via USB? In-Reply-To: <4.3.2.7.2.20000921091215.01f14e88@mail.ideal.net.au> 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 Is it possible to transfer images from a Kodak DC280 digital camera via USB to FreeBSD? The archives mention using ophoto, from http://www.fromme.com/ophoto/ , but that website appears to be dead. I'm currently using gphoto, but it only uses the serial port and is painfully slow (a transfer is in progress right now). I'd be quite happy with merely the ability to copy the images straight from the camera to disk over USB, if such is possible? Ken To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Mon Sep 25 23:17:53 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from jason.argos.org (a1-3a105.neo.rr.com [24.93.180.105]) by hub.freebsd.org (Postfix) with ESMTP id 5F16937B43C; Mon, 25 Sep 2000 23:17:40 -0700 (PDT) Received: from localhost (mike@localhost) by jason.argos.org (8.10.1/8.10.1) with ESMTP id e8Q6CEG17534; Tue, 26 Sep 2000 02:12:14 -0400 Date: Tue, 26 Sep 2000 02:12:14 -0400 (EDT) From: Mike Nowlin To: Ken Bolingbroke Cc: questions@FreeBSD.ORG, freebsd-hardware@FreeBSD.ORG Subject: Re: Kodak DC280, read as a disk via USB? 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 > Is it possible to transfer images from a Kodak DC280 digital camera via > USB to FreeBSD? The archives mention using ophoto, from > http://www.fromme.com/ophoto/ , but that website appears to be dead. I'm > currently using gphoto, but it only uses the serial port and is painfully > slow (a transfer is in progress right now). > > I'd be quite happy with merely the ability to copy the images straight > from the camera to disk over USB, if such is possible? Haven't tried it on FBSD, but I use USB from my DC240 (same protocol as DC280, I believe) to my Linux box using gphoto. Linux has a USB driver for the DC2xx series of cameras - I'd imagine it's just a matter of figuring out the "goofy stuff" in that driver and porting that over to the FBSD USB framework, if it's not already done somewhere. Fortunately, Kodak has been quite helpful in getting their stuff to run with operating systems that actually work... :) mike To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Mon Sep 25 23:18:43 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from iclub.nsu.ru (iclub.nsu.ru [193.124.222.66]) by hub.freebsd.org (Postfix) with ESMTP id 87D9837B424 for ; Mon, 25 Sep 2000 23:18:34 -0700 (PDT) Received: from localhost (fjoe@localhost) by iclub.nsu.ru (8.9.3/8.9.3) with ESMTP id NAA31917; Tue, 26 Sep 2000 13:16:39 +0700 (NSS) (envelope-from fjoe@iclub.nsu.ru) Date: Tue, 26 Sep 2000 13:16:39 +0700 (NSS) From: Max Khon To: "O. Hartmann" Cc: freebsd-hardware@FreeBSD.ORG Subject: Re: Oboard ES1373 sound chip 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 hi, there! On Mon, 25 Sep 2000, O. Hartmann wrote: > I have a mainboard with onboard sound chip ES1373 (as a PCI device). > I use device pcm0 in kernel and I got response while booting: > > pcm0: port 0xfcc0-0xfcff irq 17 at device 2.0 on pci0 > > But I can not run any kind of amp, x11amp or othe sound-based software, > I cannot do /dev/MAKEDEV /dev/pcm0. Is 1373 chip not yet supported or is > anything wrong in my doing? work here like a charm on 4.1-STABLE. which FreeBSD version do you use? how do amp, x11amp etc. complain? Are you sure you have maked all the devices? (cd /dev; sh MAKEDEV snd0) /fjoe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Tue Sep 26 4: 0: 9 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from ipamzlx.physik.uni-mainz.de (ipamzlx.Physik.Uni-Mainz.DE [134.93.180.54]) by hub.freebsd.org (Postfix) with ESMTP id B529D37B43C for ; Tue, 26 Sep 2000 04:00:04 -0700 (PDT) Received: from ipamzlx.Physik.Uni-Mainz.DE (ipamzlx.Physik.Uni-Mainz.DE [134.93.180.54]) by ipamzlx.physik.uni-mainz.de (8.11.0/8.9.3) with ESMTP id e8QAwWh04631; Tue, 26 Sep 2000 12:58:33 +0200 (CEST) (envelope-from ohartman@ipamzlx.physik.uni-mainz.de) Date: Tue, 26 Sep 2000 12:58:32 +0200 (CEST) From: "O. Hartmann" To: Max Khon Cc: freebsd-hardware@FreeBSD.ORG Subject: Re: Oboard ES1373 sound chip 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 Tue, 26 Sep 2000, Max Khon wrote: Well, I stupid boy forgot that things are never quite the way they seem ... /dev/MAKEDEV snd0 did the task and now I can hera some music :-) Oliver :>hi, there! :> :>On Mon, 25 Sep 2000, O. Hartmann wrote: :> :>> I have a mainboard with onboard sound chip ES1373 (as a PCI device). :>> I use device pcm0 in kernel and I got response while booting: :>> :>> pcm0: port 0xfcc0-0xfcff irq 17 at device 2.0 on pci0 :>> :>> But I can not run any kind of amp, x11amp or othe sound-based software, :>> I cannot do /dev/MAKEDEV /dev/pcm0. Is 1373 chip not yet supported or is :>> anything wrong in my doing? :> :>work here like a charm on 4.1-STABLE. which FreeBSD version do you use? :>how do amp, x11amp etc. complain? Are you sure you have maked all the :>devices? (cd /dev; sh MAKEDEV snd0) :> :>/fjoe :> :> Gruss O. Hartmann ------------------------------------------------------------------- ohartman@ipamzlx.physik.uni-mainz.de Klimadatenserver des IPA, Universitaet Mainz Netzwerk- und Systembetreuung To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Tue Sep 26 12:47: 8 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from tdnet.com.br (lince.tdnet.com.br [200.236.148.6]) by hub.freebsd.org (Postfix) with ESMTP id 6B2A437B422 for ; Tue, 26 Sep 2000 12:46:50 -0700 (PDT) Received: from tdnet.com.br [200.236.148.135] by tdnet.com.br with ESMTP (SMTPD32-5.05) id AD08A460178; Tue, 26 Sep 2000 16:46:16 -0300 Message-ID: <39D0D344.1612CE80@tdnet.com.br> Date: Tue, 26 Sep 2000 16:48:04 +0000 From: Gustavo Vieira Goncalves Coelho Rios X-Mailer: Mozilla 4.72 [en] (X11; I; FreeBSD 4.1-STABLE i386) X-Accept-Language: en MIME-Version: 1.0 To: hardware@freebsd.org Subject: tired of bad qulaity hardware Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I folks! I am tired of buying low quality hardware or ones that does not run well with FreeBSD! Since than, i would appreciate any help from this list suggesting me high quality ones (and remenber, money is not the problem). 0) Motherboards, 1) Memories, 2) SCSI Controllers, 3) NIC, 2) Hard Disks. Is there any good url that shows me tips of witch criterias should i analise ? Thanks a lot for your time and cooperation. best regards! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Tue Sep 26 20:11: 9 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from femail2.sdc1.sfba.home.com (femail2.sdc1.sfba.home.com [24.0.95.82]) by hub.freebsd.org (Postfix) with ESMTP id 17DE537B43C for ; Tue, 26 Sep 2000 20:11:08 -0700 (PDT) Received: from home.com ([24.3.185.85]) by femail2.sdc1.sfba.home.com (InterMail vM.4.01.03.00 201-229-121) with ESMTP id <20000927031057.MWEC27630.femail2.sdc1.sfba.home.com@home.com>; Tue, 26 Sep 2000 20:10:57 -0700 Message-ID: <39D16525.75080821@home.com> Date: Tue, 26 Sep 2000 23:10:29 -0400 From: "Gary T. Corcoran" X-Mailer: Mozilla 4.7 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Gustavo Vieira Goncalves Coelho Rios Cc: hardware@FreeBSD.ORG Subject: Re: tired of bad qulaity hardware References: <39D0D344.1612CE80@tdnet.com.br> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Gustavo Vieira Goncalves Coelho Rios wrote: > > I am tired of buying low quality hardware or ones that does not run well > with FreeBSD! > > Since than, i would appreciate any help from this list suggesting me > high quality ones (and remenber, money is not the problem). ... > 2) Hard Disks. For my money, I'll only buy IBM hard disks now. They're quiet, run relatively cool, and in my experience so far, have been reliable. Gary To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Tue Sep 26 20:46:42 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from gabriel.schoolpeople.net (gabriel.schoolpeople.net [216.34.170.167]) by hub.freebsd.org (Postfix) with ESMTP id A553F37B424 for ; Tue, 26 Sep 2000 20:46:39 -0700 (PDT) Received: from dopey (cs9347-126.austin.rr.com [24.93.47.126]) by gabriel.schoolpeople.net (8.9.3/8.9.3) with SMTP id WAA32384; Tue, 26 Sep 2000 22:46:24 -0500 (CDT) (envelope-from brandon@schoolpeople.net) Message-ID: <005c01c02835$96aa6120$7e2f5d18@austin.rr.com> From: "Brandon DeYoung" To: "Gustavo Vieira Goncalves Coelho Rios" , References: <39D0D344.1612CE80@tdnet.com.br> Subject: Re: tired of bad qulaity hardware Date: Tue, 26 Sep 2000 22:46:58 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 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 > 0) Motherboards, Gotta go with Asus A7V as long as you don't need more than 1.5 GB RAM. > 1) Memories, Get the "Athlon tested" PC133 from www.mushkin.com > 2) SCSI Controllers, Adaptec AHA-2940U2W or any of the 2940 line have always been solid. > 3) NIC, Intel Pro/100 line > 2) Hard Disks. For SCSI, IBM or Seagate. For IDE I've become a big fan of Maxtor recently, but IBM is good as well. I've had very bad luck with Western Digital lately. Just my favorites, ~Brandon ----- Original Message ----- From: Gustavo Vieira Goncalves Coelho Rios To: Sent: Tuesday, September 26, 2000 11:48 AM Subject: tired of bad qulaity hardware > I folks! > > I am tired of buying low quality hardware or ones that does not run well > with FreeBSD! > > Since than, i would appreciate any help from this list suggesting me > high quality ones (and remenber, money is not the problem). > > 0) Motherboards, > 1) Memories, > 2) SCSI Controllers, > 3) NIC, > 2) Hard Disks. > > Is there any good url that shows me tips of witch criterias should i > analise ? > > Thanks a lot for your time and cooperation. > > best regards! > > > 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 Sep 26 21: 1:25 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from gabriel.schoolpeople.net (gabriel.schoolpeople.net [216.34.170.167]) by hub.freebsd.org (Postfix) with ESMTP id F30F637B424 for ; Tue, 26 Sep 2000 21:01:23 -0700 (PDT) Received: from dopey (cs9347-126.austin.rr.com [24.93.47.126]) by gabriel.schoolpeople.net (8.9.3/8.9.3) with SMTP id XAA32424 for ; Tue, 26 Sep 2000 23:01:23 -0500 (CDT) (envelope-from brandon@schoolpeople.net) Message-ID: <007f01c02837$ae28ddc0$7e2f5d18@austin.rr.com> From: "Brandon DeYoung" To: Subject: Asus CUR-DLS/Serverworks ServerSet III LE chipset Date: Tue, 26 Sep 2000 23:01:57 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2615.200 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200 Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I'll be building some pretty heavy-duty servers in about a month and am considering the Asus CUR-DLS. I'm concerned about this chipset (Serverworks ServerSet III LE) and FreeBSD compatibility. Does anyone have any experience (good or bad) with it? If anyone feels like recommending another board on this level I'm all ears. Requirements are: supports 4GB RAM, SMP, integrated video and NIC. Thanks in advance, ~Brandon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Tue Sep 26 21:22:12 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from mass.osd.bsdi.com (adsl-63-206-90-224.dsl.snfc21.pacbell.net [63.206.90.224]) by hub.freebsd.org (Postfix) with ESMTP id 7969537B43C for ; Tue, 26 Sep 2000 21:21:57 -0700 (PDT) Received: from mass.osd.bsdi.com (localhost [127.0.0.1]) by mass.osd.bsdi.com (8.11.0/8.9.3) with ESMTP id e8R4N9A02902; Tue, 26 Sep 2000 21:23:12 -0700 (PDT) (envelope-from msmith@mass.osd.bsdi.com) Message-Id: <200009270423.e8R4N9A02902@mass.osd.bsdi.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: "Brandon DeYoung" Cc: freebsd-hardware@FreeBSD.ORG Subject: Re: Asus CUR-DLS/Serverworks ServerSet III LE chipset In-reply-to: Your message of "Tue, 26 Sep 2000 23:01:57 CDT." <007f01c02837$ae28ddc0$7e2f5d18@austin.rr.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 26 Sep 2000 21:23:09 -0700 From: Mike Smith Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org As I've posted to this list at least once in the last couple of weeks, we (FreeBSD Labs) certified this board for 4.1 a little while back. It should serve you well. Note that 4GB is going to cost you about US$6k to put into that board (1GB DIMMs being what they are). You might want to consider the Tyan S2500, which has 8 DIMM sockets. Whilst the board is larger and more expensive, it's somewhat offset by the ~$1200 saving in memory cost. > I'll be building some pretty heavy-duty servers in about a month and am > considering the Asus CUR-DLS. I'm concerned about this chipset (Serverworks > ServerSet III LE) and FreeBSD compatibility. Does anyone have any experience > (good or bad) with it? > If anyone feels like recommending another board on this level I'm all > ears. Requirements are: supports 4GB RAM, SMP, integrated video and NIC. > > Thanks in advance, > ~Brandon > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hardware" in the body of the message > -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Wed Sep 27 4:33: 1 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from ipamzlx.physik.uni-mainz.de (ipamzlx.Physik.Uni-Mainz.DE [134.93.180.54]) by hub.freebsd.org (Postfix) with ESMTP id 6B9EC37B424; Wed, 27 Sep 2000 04:32:49 -0700 (PDT) Received: from ipamzlx.Physik.Uni-Mainz.DE (ipamzlx.Physik.Uni-Mainz.DE [134.93.180.54]) by ipamzlx.physik.uni-mainz.de (8.11.0/8.9.3) with ESMTP id e8RBY2510574; Wed, 27 Sep 2000 13:34:03 +0200 (CEST) (envelope-from ohartman@ipamzlx.physik.uni-mainz.de) Date: Wed, 27 Sep 2000 13:34:02 +0200 (CEST) From: "O. Hartmann" To: freebsd-stable@freebsd.org Cc: freebsd-hardware@freebsd.org Subject: max. amount of physical memory in FBSD 4.1? 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 Dear Sirs. Every step done under Linux is well documented by the press, especially here in Germany! When Microsoft found a bug in AMD's Athlon CPUs which causes Win2k to crash, the 4GB physical memory limit came into play again. Some discussions were made about PAE addressing modell and so on and although the discussion started on a M$ <-> AMD problem, the migration towards Linux's memory modell was done smoothly. Well, we now know, Linux has recently a 4GB physical memory limitation due its PAE address space model. And what is about FreeBSD 4.1? We use now TYAN's Thunder 2500 maonboard which is capable to hold two CPUs and get equipted with max. 8GB main memory. This is a nice option because we plan to solve some memory intensive environtmental research calculations. So, my question seems to be stupid for those who understand reading kernel code, but for me, a kind of "normalo", please tell me: how much memory and how many CPUs is FreeBSD 4.1.1-STABLE capable to work with in a stable fashion? Many thanks, Gruss O. Hartmann ------------------------------------------------------------------- ohartman@ipamzlx.physik.uni-mainz.de Klimadatenserver des IPA, Universitaet Mainz Netzwerk- und Systembetreuung To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Wed Sep 27 5:18:12 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from lucifer.ninth-circle.org (lucifer.bart.nl [194.158.168.74]) by hub.freebsd.org (Postfix) with ESMTP id BD9D837B424; Wed, 27 Sep 2000 05:18:00 -0700 (PDT) Received: (from asmodai@localhost) by lucifer.ninth-circle.org (8.11.0/8.9.3) id e8RCFpe14721; Wed, 27 Sep 2000 14:15:51 +0200 (CEST) (envelope-from asmodai) Date: Wed, 27 Sep 2000 14:15:48 +0200 From: Jeroen Ruigrok van der Werven To: "O. Hartmann" Cc: freebsd-stable@FreeBSD.ORG, freebsd-hardware@FreeBSD.ORG Subject: Re: max. amount of physical memory in FBSD 4.1? Message-ID: <20000927141547.J10657@lucifer.bart.nl> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from ohartman@ipamzlx.physik.uni-mainz.de on Wed, Sep 27, 2000 at 01:34:02PM +0200 Organisation: VIA Net.Works The Netherlands Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Guten tag, -On [20000927 13:35], O. Hartmann (ohartman@ipamzlx.physik.uni-mainz.de) wrote: [snip] >And what is about FreeBSD 4.1? We use now TYAN's Thunder 2500 maonboard >which is capable to hold two CPUs and get equipted with max. 8GB main >memory. This is a nice option because we plan to solve some memory >intensive environtmental research calculations. So, my question seems >to be stupid for those who understand reading kernel code, but for me, >a kind of "normalo", please tell me: how much memory and how many CPUs >is FreeBSD 4.1.1-STABLE capable to work with in a stable fashion? I have been running FreeBSD 4-STABLE and higher on SMP boxes reliable. Those were 2 CPU boxen. For more CPU's see LINT's options: # Mandatory: options SMP # Symmetric MultiProcessor Kernel options APIC_IO # Symmetric (APIC) I/O # Optional, these are the defaults plus 1: options NCPU=5 # number of CPUs options NBUS=5 # number of busses options NAPIC=2 # number of IO APICs options NINTR=25 # number of INTs 4 Gigabyte is currently the limit. Peter Wemm [peter@freebsd.org] is current working on getting 8 Gigabyte supported and working. -- Jeroen Ruigrok van der Werven Network- and systemadministrator VIA Net.Works The Netherlands BSD: Technical excellence at its best http://www.via-net-works.nl Grant me the serenity to accept the things I cannot change, courage to change the things I can, and wisdom to know the difference... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Wed Sep 27 7:22:32 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from rush.telenordia.se (mail.telenordia.se [194.213.64.42]) by hub.freebsd.org (Postfix) with SMTP id EB55F37B424 for ; Wed, 27 Sep 2000 07:22:20 -0700 (PDT) Received: (qmail 5331 invoked from network); 27 Sep 2000 16:22:19 +0200 Received: from du138-148.ppp.algonet.se (HELO 128136) (195.100.148.138) by mail.telenordia.se with SMTP; 27 Sep 2000 16:22:19 +0200 Received: (qmail 72687 invoked by uid 1004); 27 Sep 2000 13:51:07 -0000 Date: Wed, 27 Sep 2000 15:51:07 +0200 From: Andreas Persson To: "O. Hartmann" Cc: freebsd-stable@freebsd.org, freebsd-hardware@freebsd.org Subject: Re: max. amount of physical memory in FBSD 4.1? Message-ID: <20000927155106.C72327@sophocles> Mail-Followup-To: "O. Hartmann" , freebsd-stable@freebsd.org, freebsd-hardware@freebsd.org References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: ; from ohartman@ipamzlx.physik.uni-mainz.de on Wed, Sep 27, 2000 at 01:34:02PM +0200 Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Wed, Sep 27, 2000 at 01:34:02PM +0200, "O. Hartmann" wrote: >Dear Sirs. > >Every step done under Linux is well documented by the press, especially here >in Germany! When Microsoft found a bug in AMD's Athlon CPUs which causes >Win2k to crash, the 4GB physical memory limit came into play again. Some >discussions were made about PAE addressing modell and so on and although the >discussion started on a M$ <-> AMD problem, the migration towards Linux's >memory modell was done smoothly. Well, we now know, Linux has recently a >4GB physical memory limitation due its PAE address space model. And what is >about FreeBSD 4.1? We use now TYAN's Thunder 2500 maonboard which is capable >to hold two CPUs and get equipted with max. 8GB main memory. This is a nice >option because we plan to solve some memory intensive environtmental >research calculations. So, my question seems to be stupid for those who >understand reading kernel code, but for me, a kind of "normalo", please >tell me: how much memory and how many CPUs is FreeBSD 4.1.1-STABLE capable to >work with in a stable fashion? There are some fairly complex issues that need to be resolved before FreeBSD can support more than 4GB of physical memory (splitting vm_offset/vm_size into virtual and physical parts like netbsd, cleanups, drivers that do dma..). But 4GB works just fine. As for processors, IIRC, it supports any amount that the hardware can handle, but it won't scale very well with many due to the big lock. >Many thanks, > >Gruss O. Hartmann >------------------------------------------------------------------- >ohartman@ipamzlx.physik.uni-mainz.de > >Klimadatenserver des IPA, Universitaet Mainz >Netzwerk- und Systembetreuung -- Andreas Persson pap@garen.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Wed Sep 27 7:25:45 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from osiris.ipform.ru (osiris.ipform.ru [212.158.165.98]) by hub.freebsd.org (Postfix) with ESMTP id D05A837B422; Wed, 27 Sep 2000 07:25:16 -0700 (PDT) Received: from wp2 (wp2 [192.168.0.12]) by osiris.ipform.ru (8.11.0/8.11.0) with SMTP id e8REOvR04178; Wed, 27 Sep 2000 18:24:58 +0400 (MSD) (envelope-from matrix@ipform.ru) Message-ID: <011a01c0288e$b7a53ae0$0c00a8c0@ipform.ru> From: "Artem Koutchine" To: Cc: Subject: DVB driver Date: Wed, 27 Sep 2000 18:24:34 +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.2919.6600 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600 Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Is there a DVB (digital video broadcat cards) driver for FreeBSD? I know, that SkyStar1 works on Linux. Help! Artem To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Wed Sep 27 7:53: 9 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from averroe.polito.it (averroe.polito.it [130.192.4.32]) by hub.freebsd.org (Postfix) with SMTP id D7D0037B43C for ; Wed, 27 Sep 2000 07:53:06 -0700 (PDT) Received: (qmail 31635 invoked by uid 10003); 27 Sep 2000 14:52:54 -0000 Received: from demostene.polito.it (130.192.4.73) by averroe.polito.it with SMTP; 27 Sep 2000 14:52:54 -0000 Message-Id: <5.0.0.25.0.20000927165230.00a8c5f0@averroe.polito.it> X-Sender: tealdi@averroe.polito.it X-Mailer: QUALCOMM Windows Eudora Version 5.0 Date: Wed, 27 Sep 2000 16:52:54 +0200 To: freebsd-hardware@freebsd.org From: Paolo Tealdi Subject: Proliant LM370 Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Ing. Paolo Tealdi Library & News System Administrator Politecnico Torino Phone : +39-11-5646714 , FAX : +39-11-5646799 C.so D. degli Abruzzi, 24 - 10129 Torino - ITALY Email: tealdi@sb.polito.it To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Wed Sep 27 8: 3:48 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from averroe.polito.it (averroe.polito.it [130.192.4.32]) by hub.freebsd.org (Postfix) with SMTP id 430E137B42C for ; Wed, 27 Sep 2000 08:03:45 -0700 (PDT) Received: (qmail 31709 invoked by uid 10003); 27 Sep 2000 15:03:42 -0000 Received: from demostene.polito.it (130.192.4.73) by averroe.polito.it with SMTP; 27 Sep 2000 15:03:42 -0000 Message-Id: <5.0.0.25.0.20000927165317.00a8a400@averroe.polito.it> X-Sender: tealdi@averroe.polito.it X-Mailer: QUALCOMM Windows Eudora Version 5.0 Date: Wed, 27 Sep 2000 17:03:42 +0200 To: freebsd-hardware@freebsd.org From: Paolo Tealdi Subject: Proliant ML370 architecture Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In a few days we will buy a Compaq Proliant ML370. I searched for information on the architecture and on FreeBSD support for its hardware but i couldn't find anything of certain. Our vendor told us that its NIC chipset is an Intel 82559 (compaq calls it NC3163) and its controller chipset SCSI is a "Symbios Logic 53C1510". This is right ? FreeBSD 4.1 (4.1.1 ) supports these cards ? In general anybody has tested FreeBSD in a Compaq Proliant ML370 environment (with two processors) ? I know that compaq is not the top for compatibility but ... Best regards, Paolo Tealdi P.S. Sorry for the first mail .... i found a new Eudora feature "Ctrl-E : Send Immediately" Ing. Paolo Tealdi Library & News System Administrator Politecnico Torino Phone : +39-11-5646714 , FAX : +39-11-5646799 C.so D. degli Abruzzi, 24 - 10129 Torino - ITALY Email: tealdi@sb.polito.it To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Wed Sep 27 8:27:21 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from mail.dcnv.com (mail.dcnv.com [216.33.117.136]) by hub.freebsd.org (Postfix) with ESMTP id DF12437B423; Wed, 27 Sep 2000 08:27:18 -0700 (PDT) Received: from digitalconvergence.com (dallas [207.158.100.67]) by mail.dcnv.com (8.9.3/8.9.3) with ESMTP id KAA72057; Wed, 27 Sep 2000 10:23:06 -0500 (CDT) (envelope-from aedmonds@digitalconvergence.com) Message-ID: <39D211D0.5BEFDB17@digitalconvergence.com> Date: Wed, 27 Sep 2000 10:27:12 -0500 From: Alan Edmonds X-Mailer: Mozilla 4.75 [en] (WinNT; U) X-Accept-Language: en MIME-Version: 1.0 To: Mike Smith Cc: Brandon DeYoung , freebsd-hardware@FreeBSD.ORG Subject: Re: Asus CUR-DLS/Serverworks ServerSet III LE chipset References: <200009270423.e8R4N9A02902@mass.osd.bsdi.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Just as an aside, 4.1-RELEASE will boot in 4GB but 4.1-STABLE panics trying to boot in 4GB. At least on my Compaq DL360 machines. I haven't filled out a PR yet since I haven't captured the panic. I think it is related to the pmap changes that went in just after 4.1-RELEASE. -- Alan Edmonds Director of International Technology Digital:Convergence aedmonds@digitalconvergence.com Phone: +1-214-292-6040 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Wed Sep 27 10:21:48 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.hcvlny.cv.net (mx1.hcvlny.cv.net [167.206.112.76]) by hub.freebsd.org (Postfix) with ESMTP id ABBBE37B423 for ; Wed, 27 Sep 2000 10:21:37 -0700 (PDT) Received: from s1.optonline.net (s1.optonline.net [167.206.112.6]) by mx1.hcvlny.cv.net (8.10.2/8.10.2) with ESMTP id e8RHLao17206 for ; Wed, 27 Sep 2000 13:21:36 -0400 (EDT) Received: from steinyv (d133-151.jcsnnj.optonline.net [24.189.133.151]) by s1.optonline.net (8.10.2/8.10.2) with ESMTP id e8RHLao27643 for ; Wed, 27 Sep 2000 13:21:36 -0400 (EDT) Message-Id: <4.2.0.58.20000927131552.009d5440@mail-hub.optonline.net> X-Sender: mvanberk@mail-hub.optonline.net X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58 Date: Wed, 27 Sep 2000 13:16:43 -0400 To: freebsd-hardware@freebsd.org From: Bigwillie Subject: Adaptec 1520 Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I know its an old card, but Im running 4.1S and the led doesn't light up. I went through the archive and came across something similar with symbios 875 based scsi cards. I haven't been able to come up with a fix. Is it in the archive, or am I out of luck? Thanks _________________________________________ Steiny's Studio Pachyderm Productions http://steiny.hypermart.net mailto:info@steiny.hypermart.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Wed Sep 27 11:42:14 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from mass.osd.bsdi.com (adsl-63-206-90-224.dsl.snfc21.pacbell.net [63.206.90.224]) by hub.freebsd.org (Postfix) with ESMTP id A2C8A37B424 for ; Wed, 27 Sep 2000 11:41:52 -0700 (PDT) Received: from mass.osd.bsdi.com (localhost [127.0.0.1]) by mass.osd.bsdi.com (8.11.0/8.9.3) with ESMTP id e8RIh5A05474; Wed, 27 Sep 2000 11:43:06 -0700 (PDT) (envelope-from msmith@mass.osd.bsdi.com) Message-Id: <200009271843.e8RIh5A05474@mass.osd.bsdi.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Paolo Tealdi Cc: freebsd-hardware@freebsd.org Subject: Re: Proliant ML370 architecture In-reply-to: Your message of "Wed, 27 Sep 2000 17:03:42 +0200." <5.0.0.25.0.20000927165317.00a8a400@averroe.polito.it> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 27 Sep 2000 11:43:05 -0700 From: Mike Smith Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > In a few days we will buy a Compaq Proliant ML370. > I searched for information on the architecture and on FreeBSD support for > its hardware but i couldn't find anything of certain. I haven't heard of anyone running one of these systems yet. > Our vendor told us that its NIC chipset is an Intel 82559 (compaq calls it > NC3163) and its controller chipset SCSI is a "Symbios Logic 53C1510". > > This is right ? > FreeBSD 4.1 (4.1.1 ) supports these cards ? Yes, they should work. > In general anybody has tested FreeBSD in a Compaq Proliant ML370 > environment (with two processors) ? No. Note that the DL360 is known to have problems, while the DL380 is known to work fine. You may have issues with the DL370, in which case you should yell at Compaq. -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Wed Sep 27 11:57: 8 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from mail.dcnv.com (mail.dcnv.com [216.33.117.136]) by hub.freebsd.org (Postfix) with ESMTP id A5F6137B422; Wed, 27 Sep 2000 11:57:01 -0700 (PDT) Received: from digitalconvergence.com (dallas [207.158.100.67]) by mail.dcnv.com (8.9.3/8.9.3) with ESMTP id NAA02310; Wed, 27 Sep 2000 13:52:54 -0500 (CDT) (envelope-from aedmonds@digitalconvergence.com) Message-ID: <39D242FC.FC110A4E@digitalconvergence.com> Date: Wed, 27 Sep 2000 13:57:00 -0500 From: Alan Edmonds X-Mailer: Mozilla 4.75 [en] (WinNT; U) X-Accept-Language: en MIME-Version: 1.0 To: Mike Smith Cc: Paolo Tealdi , freebsd-hardware@freebsd.org Subject: Re: Proliant ML370 architecture References: <200009271843.e8RIh5A05474@mass.osd.bsdi.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Mike Smith wrote: > > > In a few days we will buy a Compaq Proliant ML370. > > I searched for information on the architecture and on FreeBSD support for > > its hardware but i couldn't find anything of certain. > > I haven't heard of anyone running one of these systems yet. > > > Our vendor told us that its NIC chipset is an Intel 82559 (compaq calls it > > NC3163) and its controller chipset SCSI is a "Symbios Logic 53C1510". > > > > This is right ? > > FreeBSD 4.1 (4.1.1 ) supports these cards ? > > Yes, they should work. > > > In general anybody has tested FreeBSD in a Compaq Proliant ML370 > > environment (with two processors) ? > > No. Note that the DL360 is known to have problems, while the DL380 is > known to work fine. You may have issues with the DL370, in which case > you should yell at Compaq. Interesting. I'm running 4.1-RELEASE on DL360s. Works fine. I did have problems with 4GB of RAM and 4.1-STABLE. I'll send in a pr today on that. What are the issues with the DL360? -- Alan Edmonds Director of International Technology Digital:Convergence aedmonds@digitalconvergence.com Phone: +1-214-292-6040 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Wed Sep 27 12: 2:18 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from mass.osd.bsdi.com (adsl-63-206-90-224.dsl.snfc21.pacbell.net [63.206.90.224]) by hub.freebsd.org (Postfix) with ESMTP id 7665C37B424 for ; Wed, 27 Sep 2000 12:02:16 -0700 (PDT) Received: from mass.osd.bsdi.com (localhost [127.0.0.1]) by mass.osd.bsdi.com (8.11.0/8.9.3) with ESMTP id e8RJ3QA05558; Wed, 27 Sep 2000 12:03:31 -0700 (PDT) (envelope-from msmith@mass.osd.bsdi.com) Message-Id: <200009271903.e8RJ3QA05558@mass.osd.bsdi.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Alan Edmonds Cc: freebsd-hardware@freebsd.org Subject: Re: Proliant ML370 architecture In-reply-to: Your message of "Wed, 27 Sep 2000 13:57:00 CDT." <39D242FC.FC110A4E@digitalconvergence.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 27 Sep 2000 12:03:26 -0700 From: Mike Smith Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > No. Note that the DL360 is known to have problems, while the DL380 is > > known to work fine. You may have issues with the DL370, in which case > > you should yell at Compaq. > > Interesting. I'm running 4.1-RELEASE on DL360s. Works fine. > I did have problems with 4GB of RAM and 4.1-STABLE. > I'll send in a pr today on that. Ack. I saw your post on that today. 8( > What are the issues with the DL360? We have numerous reports of them not working in SMP mode. -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Wed Sep 27 12: 6:11 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from mail.dcnv.com (mail.dcnv.com [216.33.117.136]) by hub.freebsd.org (Postfix) with ESMTP id 0713F37B42C; Wed, 27 Sep 2000 12:06:09 -0700 (PDT) Received: from digitalconvergence.com (dallas [207.158.100.67]) by mail.dcnv.com (8.9.3/8.9.3) with ESMTP id OAA03677; Wed, 27 Sep 2000 14:02:01 -0500 (CDT) (envelope-from aedmonds@digitalconvergence.com) Message-ID: <39D2451F.512DAC90@digitalconvergence.com> Date: Wed, 27 Sep 2000 14:06:07 -0500 From: Alan Edmonds X-Mailer: Mozilla 4.75 [en] (WinNT; U) X-Accept-Language: en MIME-Version: 1.0 To: Mike Smith Cc: freebsd-hardware@freebsd.org Subject: Re: Proliant ML370 architecture References: <200009271903.e8RJ3QA05558@mass.osd.bsdi.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Mike Smith wrote: > > > > No. Note that the DL360 is known to have problems, while the DL380 is > > > known to work fine. You may have issues with the DL370, in which case > > > you should yell at Compaq. > > > > Interesting. I'm running 4.1-RELEASE on DL360s. Works fine. > > I did have problems with 4GB of RAM and 4.1-STABLE. > > I'll send in a pr today on that. > > Ack. I saw your post on that today. 8( > > > What are the issues with the DL360? > > We have numerous reports of them not working in SMP mode. I haven't tried them in SMP mode; I only have single processor systems. I just got an update that should allow me to enable PXE mode for the onboard NICs. That's something I've been waiting for. -- Alan Edmonds Director of International Technology Digital:Convergence aedmonds@digitalconvergence.com Phone: +1-214-292-6040 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Wed Sep 27 12: 8:30 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from mass.osd.bsdi.com (adsl-63-206-90-224.dsl.snfc21.pacbell.net [63.206.90.224]) by hub.freebsd.org (Postfix) with ESMTP id 69C3537B423 for ; Wed, 27 Sep 2000 12:08:28 -0700 (PDT) Received: from mass.osd.bsdi.com (localhost [127.0.0.1]) by mass.osd.bsdi.com (8.11.0/8.9.3) with ESMTP id e8RJ9iA05594; Wed, 27 Sep 2000 12:09:44 -0700 (PDT) (envelope-from msmith@mass.osd.bsdi.com) Message-Id: <200009271909.e8RJ9iA05594@mass.osd.bsdi.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Alan Edmonds Cc: freebsd-hardware@freebsd.org Subject: Re: Proliant ML370 architecture In-reply-to: Your message of "Wed, 27 Sep 2000 14:06:07 CDT." <39D2451F.512DAC90@digitalconvergence.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 27 Sep 2000 12:09:44 -0700 From: Mike Smith Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > > What are the issues with the DL360? > > > > We have numerous reports of them not working in SMP mode. > > I haven't tried them in SMP mode; I only have single processor systems. > > I just got an update that should allow me to enable PXE mode for > the onboard NICs. That's something I've been waiting for. What's the build number? (It will print this as it initialises) Chances are that it's a buggy one (eg. 078). You want 082 (assuming they aren't hiding the Intel build numbers). There are significant bugs in older builds, which Intel are aware of. -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Wed Sep 27 12:33:13 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from mail.dcnv.com (mail.dcnv.com [216.33.117.136]) by hub.freebsd.org (Postfix) with ESMTP id 43BF837B424; Wed, 27 Sep 2000 12:33:10 -0700 (PDT) Received: from digitalconvergence.com (dallas [207.158.100.67]) by mail.dcnv.com (8.9.3/8.9.3) with ESMTP id OAA07594; Wed, 27 Sep 2000 14:29:02 -0500 (CDT) (envelope-from aedmonds@digitalconvergence.com) Message-ID: <39D24B74.4955AF5D@digitalconvergence.com> Date: Wed, 27 Sep 2000 14:33:08 -0500 From: Alan Edmonds X-Mailer: Mozilla 4.75 [en] (WinNT; U) X-Accept-Language: en MIME-Version: 1.0 To: Mike Smith Cc: freebsd-hardware@freebsd.org Subject: Re: Proliant ML370 architecture References: <200009271909.e8RJ9iA05594@mass.osd.bsdi.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Mike Smith wrote: > > I just got an update that should allow me to enable PXE mode for > > the onboard NICs. That's something I've been waiting for. > > What's the build number? (It will print this as it initialises) Chances > are that it's a buggy one (eg. 078). You want 082 (assuming they aren't > hiding the Intel build numbers). There are significant bugs in older > builds, which Intel are aware of. I'm not sure yet. I'm using 082 on some add on NICs currently. The date on the ROMPaq is early Sept so I hope it isn't 078.... -- Alan Edmonds Director of International Technology Digital:Convergence aedmonds@digitalconvergence.com Phone: +1-214-292-6040 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Wed Sep 27 19:18:52 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from heorot.1nova.com (sub24-23.member.dsl-only.net [63.105.24.23]) by hub.freebsd.org (Postfix) with ESMTP id D272837B424 for ; Wed, 27 Sep 2000 19:18:50 -0700 (PDT) Received: by heorot.1nova.com (Postfix, from userid 1000) id 62A3F328D; Tue, 26 Sep 2000 18:42:33 +0000 (GMT) Received: from localhost (localhost [127.0.0.1]) by heorot.1nova.com (Postfix) with ESMTP id 4202C328C; Tue, 26 Sep 2000 18:42:33 +0000 (GMT) Date: Tue, 26 Sep 2000 18:42:33 +0000 (GMT) From: Rick Hamell To: Bigwillie Cc: freebsd-hardware@freebsd.org Subject: Re: Adaptec 1520 In-Reply-To: <4.2.0.58.20000927131552.009d5440@mail-hub.optonline.net> 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 know its an old card, but Im running 4.1S and the led doesn't light > up. I went through the archive and came across something similar with > symbios 875 based scsi cards. I haven't been able to come up with a > fix. Is it in the archive, or am I out of luck? > Thanks It's been my experience that if the card dosen't light up, it's dead... but then I've not played with one since 486 days.... Rick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Wed Sep 27 19:40:29 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.hcvlny.cv.net (mx1.hcvlny.cv.net [167.206.112.76]) by hub.freebsd.org (Postfix) with ESMTP id A69E537B422 for ; Wed, 27 Sep 2000 19:40:18 -0700 (PDT) Received: from s1.optonline.net (s1.optonline.net [167.206.112.6]) by mx1.hcvlny.cv.net (8.10.2/8.10.2) with ESMTP id e8S2eHo04831; Wed, 27 Sep 2000 22:40:17 -0400 (EDT) Received: from steinyv (d133-151.jcsnnj.optonline.net [24.189.133.151]) by s1.optonline.net (8.10.2/8.10.2) with ESMTP id e8S2eGo10741; Wed, 27 Sep 2000 22:40:16 -0400 (EDT) Message-Id: <4.2.0.58.20000927222757.009d9b80@mail-hub.optonline.net> X-Sender: mvanberk@mail-hub.optonline.net X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58 Date: Wed, 27 Sep 2000 22:35:21 -0400 To: Rick Hamell From: Bigwillie Subject: Re: Adaptec 1520 Cc: freebsd-hardware@freebsd.org In-Reply-To: References: <4.2.0.58.20000927131552.009d5440@mail-hub.optonline.net> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Well this one works. I had it on a win 98 box and the led worked. On the FBSD box it works up to where you have to hit enter to boot the kernel. After that the led is a dodo. At 02:42 PM 9/26/00 , you wrote: > > I know its an old card, but Im running 4.1S and the led doesn't light > > up. I went through the archive and came across something similar with > > symbios 875 based scsi cards. I haven't been able to come up with a > > fix. Is it in the archive, or am I out of luck? > > Thanks > > It's been my experience that if the card dosen't light up, it's >dead... but then I've not played with one since 486 days.... > > > Rick _________________________________________ Steiny's Studio Pachyderm Productions http://steiny.hypermart.net mailto:info@steiny.hypermart.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Wed Sep 27 19:47:19 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from heorot.1nova.com (sub24-23.member.dsl-only.net [63.105.24.23]) by hub.freebsd.org (Postfix) with ESMTP id 24F9737B42C for ; Wed, 27 Sep 2000 19:47:00 -0700 (PDT) Received: by heorot.1nova.com (Postfix, from userid 1000) id 017C6328D; Tue, 26 Sep 2000 19:10:59 +0000 (GMT) Received: from localhost (localhost [127.0.0.1]) by heorot.1nova.com (Postfix) with ESMTP id E2AB4328C; Tue, 26 Sep 2000 19:10:59 +0000 (GMT) Date: Tue, 26 Sep 2000 19:10:59 +0000 (GMT) From: Rick Hamell To: Bigwillie Cc: freebsd-hardware@freebsd.org Subject: Re: Adaptec 1520 In-Reply-To: <4.2.0.58.20000927222757.009d9b80@mail-hub.optonline.net> 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 > Well this one works. I had it on a win 98 box and the led worked. On the > FBSD box it works up to where you have to hit enter to boot the > kernel. After that the led is a dodo. Ahh... that's part of the info we're missing... have you tried changing the IRQ settings upon bootup, both in PNP options in the BIOS, AND in the visual config tool when installing FreeBSD to match what the card is set too? Have you turned the IRQ (Usually 11 or 12) on that card in the BIOS to ISA/Legacy/Yes? Rick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Wed Sep 27 21:31:57 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.hcvlny.cv.net (mx1.hcvlny.cv.net [167.206.112.76]) by hub.freebsd.org (Postfix) with ESMTP id 8BCE137B423 for ; Wed, 27 Sep 2000 21:31:54 -0700 (PDT) Received: from s1.optonline.net (s1.optonline.net [167.206.112.6]) by mx1.hcvlny.cv.net (8.10.2/8.10.2) with ESMTP id e8S4Vro16392; Thu, 28 Sep 2000 00:31:53 -0400 (EDT) Received: from steinyv (d133-151.jcsnnj.optonline.net [24.189.133.151]) by s1.optonline.net (8.10.2/8.10.2) with ESMTP id e8S4Vqo23304; Thu, 28 Sep 2000 00:31:52 -0400 (EDT) Message-Id: <4.2.0.58.20000928002046.009d97b0@mail-hub.optonline.net> X-Sender: mvanberk@mail-hub.optonline.net X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58 Date: Thu, 28 Sep 2000 00:26:57 -0400 To: Rick Hamell From: Bigwillie Subject: Re: Adaptec 1520 Cc: freebsd-hardware@freebsd.org In-Reply-To: References: <4.2.0.58.20000927222757.009d9b80@mail-hub.optonline.net> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Ahhh, interesting..... It'll take some time to check what's going on with my system and Ill report back. At 03:10 PM 9/26/00 , you wrote: > > Well this one works. I had it on a win 98 box and the led worked. On the > > FBSD box it works up to where you have to hit enter to boot the > > kernel. After that the led is a dodo. > > Ahh... that's part of the info we're missing... have you tried >changing the IRQ settings upon bootup, both in PNP options in the BIOS, >AND in the visual config tool when installing FreeBSD to match what the >card is set too? Have you turned the IRQ (Usually 11 or 12) on that card >in the BIOS to ISA/Legacy/Yes? > > Rick > > > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-hardware" in the body of the message _________________________________________ Steiny's Studio Pachyderm Productions http://steiny.hypermart.net mailto:info@steiny.hypermart.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Thu Sep 28 16:32:43 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from rip.psg.com (rip.psg.com [147.28.0.39]) by hub.freebsd.org (Postfix) with ESMTP id A7D9D37B422; Thu, 28 Sep 2000 16:32:38 -0700 (PDT) Received: from randy by rip.psg.com with local (Exim 3.16 #1) id 13enAH-0005t2-00; Thu, 28 Sep 2000 16:32:33 -0700 From: Randy Bush MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Mike Smith Cc: freebsd-hardware@FreeBSD.ORG Subject: Re: Asus CUR-DLS/Serverworks ServerSet III LE chipset References: <007f01c02837$ae28ddc0$7e2f5d18@austin.rr.com> <200009270423.e8R4N9A02902@mass.osd.bsdi.com> Message-Id: Date: Thu, 28 Sep 2000 16:32:33 -0700 Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > As I've posted to this list at least once in the last couple of weeks, we > (FreeBSD Labs) certified this board for 4.1 a little while back. It > should serve you well. i am hoping so, as i just ordered it. gossip appreciated muchly. but i did not really understand why there are two scsi chipsets shown on i suspect both are on board and i plug my ibm 36LZX u160s into the 68-pin 1010-66. and does anyone have the /etc/XF86Config for the on-board ATI Rage-XL PCI? VGA? randy To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Thu Sep 28 16:40:24 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from mass.osd.bsdi.com (adsl-63-202-176-106.dsl.snfc21.pacbell.net [63.202.176.106]) by hub.freebsd.org (Postfix) with ESMTP id 69E8537B424; Thu, 28 Sep 2000 16:40:21 -0700 (PDT) Received: from mass.osd.bsdi.com (localhost [127.0.0.1]) by mass.osd.bsdi.com (8.11.0/8.9.3) with ESMTP id e8SNfjA02641; Thu, 28 Sep 2000 16:41:46 -0700 (PDT) (envelope-from msmith@mass.osd.bsdi.com) Message-Id: <200009282341.e8SNfjA02641@mass.osd.bsdi.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Randy Bush Cc: Mike Smith , freebsd-hardware@freebsd.org Subject: Re: Asus CUR-DLS/Serverworks ServerSet III LE chipset In-reply-to: Your message of "Thu, 28 Sep 2000 16:32:33 PDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 28 Sep 2000 16:41:45 -0700 From: Mike Smith Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > As I've posted to this list at least once in the last couple of weeks, we > > (FreeBSD Labs) certified this board for 4.1 a little while back. It > > should serve you well. > > i am hoping so, as i just ordered it. gossip appreciated muchly. > > but i did not really understand why there are two scsi chipsets shown on > > i suspect both are on board and i plug my ibm 36LZX u160s into the 68-pin > 1010-66. No. You can order the board with either the 896 OR the 1010 chipset. The former is U2W, the latter U160. > and does anyone have the /etc/XF86Config for the on-board ATI Rage-XL PCI? > VGA? Install XF86 4.0.1 and say 'X -configure'. End of story. 8) -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Thu Sep 28 18:28:28 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from ligarius-fe0.ultra.net (ligarius-fe0.ultra.net [146.115.8.189]) by hub.freebsd.org (Postfix) with ESMTP id 7821D37B423 for ; Thu, 28 Sep 2000 18:28:26 -0700 (PDT) Received: from ma.ultranet.com (d190.dial-1.cmb.ma.ultra.net [209.6.64.190]) by ligarius-fe0.ultra.net (8.8.8/ult/n26500/mtc.v2) with ESMTP id VAA26870 for ; Thu, 28 Sep 2000 21:27:08 -0400 (EDT) Message-ID: <39D3FDAD.C1875A6@ma.ultranet.com> Date: Thu, 28 Sep 2000 21:25:49 -0500 From: "Gregory D. Moncreaff" Reply-To: moncrg@ma.ultranet.com X-Mailer: Mozilla 4.75 [en] (X11; U; FreeBSD 4.1.1-STABLE i386) X-Accept-Language: en MIME-Version: 1.0 To: FreeBSD-Hardware@FreeBSD.org Subject: Has anyone run FreeBSD on a Saintsong Pocket PC Espresso? Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org or why would one not even want to? some reference URLs: http://www.saintsong.com.tw/it/english/prod/espresso.htm http://slashdot.org/articles/00/04/18/2326253.shtml http://www.ibuypower.com/product-pc/pocket-epc.htm http://arstechnica.com/reviews/2q00/espresso/espresso-1.html -- Greg Moncreaff moncrg@ma.ultranet.com Marlborough, MA; USA To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Fri Sep 29 7:39: 3 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from mail3.freesurf.fr (bastille.freesurf.fr [212.43.206.2]) by hub.freebsd.org (Postfix) with ESMTP id 73D2737B424; Fri, 29 Sep 2000 07:39:00 -0700 (PDT) Received: from mail.freesurf.fr (mail.freesurf.fr [212.43.206.50]) by mail3.freesurf.fr (Postfix) with ESMTP id A8B3319056; Fri, 29 Sep 2000 16:38:58 +0200 (CEST) Received: by mail.freesurf.fr (Postfix, from userid 5000) id 910CF3838A; Fri, 29 Sep 2000 16:38:58 +0200 (CEST) From: fpassera@freesurf.fr To: freebsd-hardware@freebsd.org, freebsd-questions@FreeBSD.ORG Subject: PCI Modems and FreeBSD ??? Date: Fri, 29 Sep 2000 14:38:58 GMT Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Sender: fpassera@freesurf.fr Message-Id: <20000929143858.910CF3838A@mail.freesurf.fr> Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I see a lot of people looking for drivers of PCI modems. I also have a PCI modem and cannot find any driver for FreeBSD. Can someone give a status of the support of PCI modems ? Thanks. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Fri Sep 29 9:23:36 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from mx-a.qnet.com (mx-a.qnet.com [209.221.198.11]) by hub.freebsd.org (Postfix) with ESMTP id BBAD737B422; Fri, 29 Sep 2000 09:23:33 -0700 (PDT) Received: from cello.qnet.com (stork@cello.qnet.com [209.221.198.10]) by mx-a.qnet.com (8.9.1a/8.9.3) with ESMTP id JAA13243; Fri, 29 Sep 2000 09:23:30 -0700 (PDT) Received: from localhost (stork@localhost) by cello.qnet.com (8.9.0/8.9.1) with ESMTP id JAA02415; Fri, 29 Sep 2000 09:22:55 -0700 (PDT) X-Authentication-Warning: cello.qnet.com: stork owned process doing -bs Date: Fri, 29 Sep 2000 09:22:55 -0700 (PDT) From: Heredity Choice To: fpassera@freesurf.fr Cc: freebsd-hardware@FreeBSD.ORG, freebsd-questions@FreeBSD.ORG Subject: Re: PCI Modems and FreeBSD ??? In-Reply-To: <20000929143858.910CF3838A@mail.freesurf.fr> 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 My ISP technical support tell me that the modem should be either an ISA modem with jumper settings for the port and interrupt or any external modem. Has anybody ever successfully used any other kind of modem under FreeBSD? Has anybody used, with or without success, a USB external modem? Paul Smith stork@qnet.com On Fri, 29 Sep 2000 fpassera@freesurf.fr wrote: > > I see a lot of people looking for drivers of PCI modems. I also have a PCI > modem and cannot find any driver for FreeBSD. Can someone give a status of > the support of PCI modems ? > > Thanks. > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-questions" 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 Fri Sep 29 10: 3: 6 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from calcaphon.demon.co.uk (calcaphon.demon.co.uk [193.237.19.5]) by hub.freebsd.org (Postfix) with ESMTP id DA4BA37B423 for ; Fri, 29 Sep 2000 10:03:01 -0700 (PDT) Received: from henny.qubesoft.com (henny.qubesoft.com [192.168.1.5]) by calcaphon.demon.co.uk (8.9.3/8.9.1) with ESMTP id SAA89664; Fri, 29 Sep 2000 18:02:31 +0100 (BST) (envelope-from n_hibma@qubesoft.com) Received: from localhost (localhost [127.0.0.1]) by henny.webweaving.org (8.9.3/8.9.3) with ESMTP id QAA25121; Fri, 29 Sep 2000 16:57:03 +0100 (BST) (envelope-from n_hibma@qubesoft.com) Date: Fri, 29 Sep 2000 16:57:03 +0100 (BST) From: Nick Hibma Reply-To: Nick Hibma To: rob Cc: "freebsd-hardware@FreeBSD.ORG" Subject: Re: Imation USB In-Reply-To: <39C914F1.6FDE19DD@home.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 Nope, a driver is not yet available. Nick On Wed, 20 Sep 2000, rob wrote: > Has a driver been developed for this super-floppy drive? I saw on some > archives that there had been some work done, but it was old > information. Rob. > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hardware" in the body of the message > -- Qube Software, Ltd. Private: n_hibma@qubesoft.com n_hibma@webweaving.org n_hibma@freebsd.org http://www.qubesoft.com/ http://www.etla.net/~n_hibma/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Fri Sep 29 12:24:46 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from home.rest.ru (home.rest.ru [195.58.8.205]) by hub.freebsd.org (Postfix) with ESMTP id 8FCBA37B63A for ; Fri, 29 Sep 2000 12:24:32 -0700 (PDT) Received: from zal (almaz.rest.ru [195.58.8.140]) by home.rest.ru (8.9.1/8.9.1) with SMTP id BAA00991 for ; Sat, 30 Sep 2000 01:24:26 +0600 (ESS) Message-ID: <004801c02a4a$de9ef600$0a01a8c0@zal.ping.ru> From: "Aleksey Zvyagin" To: Subject: Help me please! FreeBSD 3.4 & HDD 13Gb Date: Sat, 30 Sep 2000 01:24:17 +0600 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.3612.1700 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3612.1700 Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hello! Help me please! I have the problem. The version of FreeBSD is 3.4-RELEASE. The problem the following: i get the error messages to console of the HDD IDE (~13 Gb). I have the two equality HDD on secondary IDE controller and a FreeBSD 3.4 curses to both HDDes. I have attached below the dmesg message of FreeBSD and error logs. The problen occurs when i try run a bad144 utility (bad144 -v /dev/rwd2c for example) or i run /stand/sysinstall and try to execute a fdisk (to mark a bad block scan bit of slice and write command /W/). Please help me what is problem? Sep 29 21:24:04 ping /kernel: Timecounter "i8254" frequency 1193182 Hz Sep 29 21:24:04 ping /kernel: CPU: AMD Athlon(tm) Processor (700.03-MHz 686-class CPU) Sep 29 21:24:04 ping /kernel: Origin = "AuthenticAMD" Id = 0x622 Stepping = 2 Sep 29 21:24:04 ping /kernel: Features=0x183f9ff Sep 29 21:24:04 ping /kernel: AMD Features=0xc0400000<,,3DNow!> Sep 29 21:24:04 ping /kernel: real memory = 268435456 (262144K bytes) Sep 29 21:24:04 ping /kernel: avail memory = 258707456 (252644K bytes) Sep 29 21:24:04 ping /kernel: Preloaded elf kernel "kernel" at 0xc0255000. Sep 29 21:24:04 ping /kernel: Pentium Pro MTRR support enabled Sep 29 21:24:04 ping /kernel: Probing for devices on PCI bus 0: Sep 29 21:24:04 ping /kernel: chip0: rev 0x02 on pci0.0.0 Sep 29 21:24:04 ping /kernel: chip1: rev 0x00 on pci0.1.0 Sep 29 21:24:04 ping /kernel: chip2: rev 0x21 on pci0.4.0 Sep 29 21:24:04 ping /kernel: ide_pci0: rev 0x10 on pci0.4.1 Sep 29 21:24:04 ping /kernel: chip3: rev 0x30 on pci0.4.4 Sep 29 21:24:04 ping /kernel: vga0: rev 0x02 on pci0.11.0 Sep 29 21:24:04 ping /kernel: Probing for devices on PCI bus 1: Sep 29 21:24:04 ping /kernel: Probing for PnP devices: Sep 29 21:24:04 ping /kernel: Probing for devices on the ISA bus: Sep 29 21:24:04 ping /kernel: sc0 on isa Sep 29 21:24:04 ping /kernel: sc0: VGA color <16 virtual consoles, flags=0x0> Sep 29 21:24:04 ping /kernel: atkbdc0 at 0x60-0x6f on motherboard Sep 29 21:24:04 ping /kernel: atkbd0 irq 1 on isa Sep 29 21:24:04 ping /kernel: psm0 irq 12 on isa Sep 29 21:24:04 ping /kernel: psm0: model NetMouse, device ID 0 Sep 29 21:24:04 ping /kernel: sio0: configured irq 4 not in bitmap of probed irqs 0 Sep 29 21:24:04 ping /kernel: sio0 at 0x3f8-0x3ff irq 4 flags 0x10 on isa Sep 29 21:24:04 ping /kernel: sio0: type 8250 Sep 29 21:24:04 ping /kernel: sio1: configured irq 3 not in bitmap of probed irqs 0 Sep 29 21:24:04 ping /kernel: sio1 not found at 0x2f8 Sep 29 21:24:04 ping /kernel: fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa Sep 29 21:24:04 ping /kernel: fdc0: FIFO enabled, 8 bytes threshold Sep 29 21:24:04 ping /kernel: fd0: 1.44MB 3.5in Sep 29 21:24:04 ping /kernel: wdc0 at 0x1f0-0x1f7 irq 14 on isa Sep 29 21:24:04 ping /kernel: wdc0: unit 0 (wd0): Sep 29 21:24:04 ping /kernel: wd0: 8223MB (16841664 sectors), 16708 cyls, 16 heads, 63 S/T, 512 B/S Sep 29 21:24:04 ping /kernel: wdc0: unit 1 (wd1): Sep 29 21:24:04 ping /kernel: wd1: 8223MB (16841664 sectors), 16708 cyls, 16 heads, 63 S/T, 512 B/S Sep 29 21:24:04 ping /kernel: wdc1 at 0x170-0x177 irq 15 on isa Sep 29 21:24:04 ping /kernel: wdc1: unit 0 (wd2): Sep 29 21:24:04 ping /kernel: wd2: 13027MB (26679688 sectors), 26467 cyls, 16 heads, 63 S/T, 512 B/S Sep 29 21:24:04 ping /kernel: wdc1: unit 1 (wd3): Sep 29 21:24:04 ping /kernel: wd3: 13027MB (26679688 sectors), 26467 cyls, 16 heads, 63 S/T, 512 B/S Sep 29 21:24:04 ping /kernel: ppc0 not found Sep 29 21:24:04 ping /kernel: vga0 at 0x3b0-0x3df maddr 0xa0000 msize 131072 on isa Sep 29 21:24:04 ping /kernel: npx0 on motherboard Sep 29 21:24:04 ping /kernel: npx0: INT 16 interface Sep 29 21:24:04 ping /kernel: changing root device to wd0s1a -------------------------------- I have run the bad144 -v /dev/rwd2c and have gotten the following errors: Sep 29 21:31:35 ping /kernel: wd2s1h: hard error writing fsbn 16644487 (wd2s1 bn 26679687; cn 20273 tn 59 sn 6) (status 51 error 10) Sep 29 21:33:55 ping /kernel: wd2c: hard error reading fsbn 26679681 (wd2 bn 26679681; cn 20273 tn 59 sn 0) (status 59 error 10) Sep 29 21:33:55 ping /kernel: wd2c: hard error reading fsbn 26679683 (wd2 bn 26679683; cn 20273 tn 59 sn 2) (status 59 error 10) Sep 29 21:33:55 ping /kernel: wd2c: hard error reading fsbn 26679685 (wd2 bn 26679685; cn 20273 tn 59 sn 4) (status 59 error 10) Sep 29 21:33:55 ping /kernel: wd2c: hard error reading fsbn 26679687 (wd2 bn 26679687; cn 20273 tn 59 sn 6) (status 59 error 10) Sep 29 21:34:50 ping /kernel: wd2c: hard error reading fsbn 26679681 (wd2 bn 26679681; cn 20273 tn 59 sn 0) (status 59 error 10) Sep 29 21:34:50 ping /kernel: wd2c: hard error reading fsbn 26679683 (wd2 bn 26679683; cn 20273 tn 59 sn 2) (status 59 error 10) Sep 29 21:34:50 ping /kernel: wd2c: hard error reading fsbn 26679685 (wd2 bn 26679685; cn 20273 tn 59 sn 4) (status 59 error 10) Sep 29 21:34:51 ping /kernel: wd2c: hard error reading fsbn 26679687 (wd2 bn 26679687; cn 20273 tn 59 sn 6) (status 59 error 10) I have run the bad144 -v /dev/rwd3c and have gotten the following errors: Sep 29 21:35:03 ping /kernel: wd3c: hard error reading fsbn 26679625 (wd3 bn 26679625; cn 1660 tn 186 sn 7) (status 59 error 10) Sep 29 21:35:03 ping /kernel: wd3c: hard error reading fsbn 26679627 (wd3 bn 26679627; cn 1660 tn 186 sn 9) (status 59 error 10) Sep 29 21:35:03 ping /kernel: wd3c: hard error reading fsbn 26679629 (wd3 bn 26679629; cn 1660 tn 186 sn 11) (status 59 error 10) Sep 29 21:35:04 ping /kernel: wd3c: hard error reading fsbn 26679631 (wd3 bn 26679631; cn 1660 tn 186 sn 13) (status 59 error 10) Sep 29 21:35:04 ping /kernel: wd3c: hard error reading fsbn 26679633 (wd3 bn 26679633; cn 1660 tn 186 sn 15) (status 59 error 10) Sep 29 21:38:17 ping /kernel: wd3c: hard error reading fsbn 26679625 (wd3 bn 26679625; cn 1660 tn 186 sn 7) (status 59 error 10) Sep 29 21:38:17 ping /kernel: wd3c: hard error reading fsbn 26679627 (wd3 bn 26679627; cn 1660 tn 186 sn 9) (status 59 error 10) --- Best regards, Aleksey Zvyagin, zal@zal.pp.ru To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Fri Sep 29 17:31:29 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from whistle.com (s205m131.whistle.com [207.76.205.131]) by hub.freebsd.org (Postfix) with ESMTP id DE69B37B66D; Fri, 29 Sep 2000 17:31:26 -0700 (PDT) Received: (from smap@localhost) by whistle.com (8.10.0/8.10.0) id e8U0VQv16780; Fri, 29 Sep 2000 17:31:26 -0700 (PDT) Received: from bubba.whistle.com( 207.76.205.7) by whistle.com via smap (V2.0) id xma016777; Fri, 29 Sep 2000 17:31:18 -0700 Received: (from archie@localhost) by bubba.whistle.com (8.9.3/8.9.3) id RAA54873; Fri, 29 Sep 2000 17:31:18 -0700 (PDT) (envelope-from archie) From: Archie Cobbs Message-Id: <200009300031.RAA54873@bubba.whistle.com> Subject: Driver for Intel 82801AA (ICH) SMBus controller To: freebsd-hardware@freebsd.org, freebsd-hackers@freebsd.org Date: Fri, 29 Sep 2000 17:31:18 -0700 (PDT) X-Mailer: ELM [version 2.4ME+ PL82 (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org For anyone interested, I've written a first draft of a driver for the SMBus controller in the Intel 82801AA (ICH) chip. Not sure if or how well it works yet, but anyone wanting to play around with it is welcome to do so.. some hacking may be required. ftp://ftp.whistle.com/pub/archie/misc/ichsmb-driver.tgz This is for FreeBSD 4.1 but should work with more recent sources. Also compatible with the 82801AB (ICH0) chip. -Archie ___________________________________________________________________________ Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Sat Sep 30 14:33: 8 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from adsl-63-192-211-186.dsl.snfc21.pacbell.net (adsl-63-192-211-186.dsl.snfc21.pacbell.net [63.192.211.186]) by hub.freebsd.org (Postfix) with ESMTP id 1A46F37B502 for ; Sat, 30 Sep 2000 14:33:06 -0700 (PDT) Received: from localhost.minions.com (bifrost@localhost.minions.com [127.0.0.1]) by adsl-63-192-211-186.dsl.snfc21.pacbell.net (8.9.3/8.9.3) with ESMTP id OAA72716 for ; Sat, 30 Sep 2000 14:33:05 -0700 (PDT) Date: Sat, 30 Sep 2000 14:33:05 -0700 (PDT) From: Tom To: freebsd-hardware@freebsd.org Subject: ISO PIII Superworkstation Board 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 been poking around through my favorite manufacturer's websites to find that nobody seems to make what I want. I've used some of the Tyan stuff before, but I wasn't particularly happy with them, although quality and support improves all the time with any given manufacturer and FreeBSD. What I'm looking for: I would really like Dual FCPGA PIII DIMM Memory (No RIMM) 4x or 2x AGP resonable PCI slots Fit in a regular ATX case Prefer onboard SCSI and Ethernet (but not required) Looks like a Serverworks Chipset is all thats really available Obviously working with FreeBSD is a given requirement :) Anyone got any reccomendations? --- Tom bifrost@minions.com "Where am I and why am I in this handbasket?" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message