From owner-freebsd-hardware Sun Sep 30 18: 6:37 2001 Delivered-To: freebsd-hardware@freebsd.org Received: from smtp.wagsky.com (wildside.wagsky.com [64.220.148.97]) by hub.freebsd.org (Postfix) with ESMTP id 675A637B405; Sun, 30 Sep 2001 18:06:28 -0700 (PDT) Received: from localhost (jeff@localhost) by smtp.wagsky.com (8.11.6/8.9.3) with ESMTP id f9116Rb91667; Sun, 30 Sep 2001 18:06:27 -0700 (PDT) (envelope-from jeff+freebsd@wagsky.com) X-Authentication-Warning: wildside.wagsky.com: jeff owned process doing -bs Date: Sun, 30 Sep 2001 18:06:27 -0700 (PDT) From: Jeff Kletsky X-Sender: jeff@wildside.wagsky.com To: freebsd-stable@freebsd.org, freebsd-hardware@freebsd.org Subject: Promise Ultra100 TX2 and FastTrack100 TX2 Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org I have tried each of these cards in two different boxes, 4.4-RELEASE as installed, and 4.4-STABLE: FreeBSD port6.pn.wagsky.com 4.4-STABLE FreeBSD 4.4-STABLE #0: Sun Sep 16 16:10:23 PDT 2001 jeff@devel.pn.wagsky.com:/usr/obj/usr/src/sys/PIIIAV.20010916 i386 and seem to be unable to get the drives to be recognized by FreeBSD. This seems to be in conflict with the release notes and HARDWARE.TXT. Reading the notes in the group, others have been experiencing similar issues with the TX2 series. Is the TX2 different that what is referred to in the notes? The symptoms are as follows: (already run sh MAKEDEV ad4 ad5 ad6 ad7 -- with no change in behavior) * One drive on card's IDE1 - BIOS recognizes and loads - boot manager sees drive - atapci1 is seen on screen and in dmesg.boot - ad4 is not seen * One drive on card's IDE2 (or both populated) - BIOS recognizes and loads - boot manager sees drive - atapci1 is (I believe) seen on screen - hangs in the boot process just before identifying disks Motherboards are Intel se440-bx2, P600 and P600E, Promise card in first or second PCI slot (from AGP card). No issues with machines otherwise. Ultra100 TX2 is PDC20268 V2.10 B23 FastTrak100 TX2 is PDC20270 V2.00 B2 From dmesg.boot: [...] chip1: port 0x7000-0x700f at device 7.3 on pci0 atapci1: port 0x1070-0x107f,0x1080-0x1083,0x1088 -0x108f,0x1084-0x1087,0x1090-0x1097 mem 0xf4000000-0xf4003fff irq 10 at device 1 4.0 on pci0 ata2: at 0x1090 on atapci1 ata3: at 0x1088 on atapci1 fxp0: port 0x1000-0x103f mem 0xf4100000-0xf41f ffff,0xf4004000-0xf4004fff irq 9 at device 16.0 on pci0 [...] ppc0: parallel port not found. ad0: 19574MB [39770/16/63] at ata0-master UDMA33 acd0: CDROM at ata1-master using PIO4 Mounting root from ufs:/dev/ad0s1a (the freezing behavious is similar, but does not proceed to ad0) Any help on this would be greatly appreciated, even if (for now) it is a notation in the notes so that others may not suffer the same fate. Thanks! Jeff To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Mon Oct 1 4:31:24 2001 Delivered-To: freebsd-hardware@freebsd.org Received: from mailgw.servicefactory.se (oden2.exmandato.se [192.71.33.33]) by hub.freebsd.org (Postfix) with ESMTP id 6AAE537B415; Mon, 1 Oct 2001 04:24:32 -0700 (PDT) Received: from ark.servicefactory.se (ark.servicefactory.se [192.71.33.5]) by mailgw.servicefactory.se (8.11.6/8.11.6) with ESMTP id f91BOUx26627; Mon, 1 Oct 2001 13:24:30 +0200 (CEST) Received: from servicefactory.se (ark.servicefactory.se [192.71.33.5]) by ark.servicefactory.se (8.11.6/8.11.6) with ESMTP id f91BOQ811891; Mon, 1 Oct 2001 13:24:26 +0200 (CEST) Message-ID: <3BB8526C.11B616B9@servicefactory.se> Date: Mon, 01 Oct 2001 13:24:29 +0200 From: jonas Organization: Service Factory X-Mailer: Mozilla 4.78 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: Jeff Kletsky Cc: freebsd-stable@FreeBSD.ORG, freebsd-hardware@FreeBSD.ORG Subject: Re: Promise Ultra100 TX2 and FastTrack100 TX2 (and TX4) References: Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Hi, I suffer the same fate! :-( I have a Promise Fasttrak 100 TX4. It is identified by FreeBSD as two TX2 controllers: I experienced the same problem as you, i.e. the computer hangs during boot. I solved that by configure an explicit IRQ on the PCI slot used by the promise controler. But a lot of problems remains. I can only use one disk on each TX2 controller if I want the computer to boot at all, i.e not hang during boot. Using two disks on one controller causes the computer to hang as you described. Using the debugger I found out that it hangs in the function ata_command: case ATA_WAIT_INTR: scp->active = ATA_WAIT_INTR; asleep((caddr_t)scp, PRIBIO, "atacmd", 10 * hz); => outb(scp->ioaddr + ATA_CMD, command); Breakpoint 17, ata_command (scp=0xc17e0b00, device=0, command=236 'ì', cylinder=0, head=0 '\000', sector=0 '\000', count=0 '\000', feature=0 '\000', flags=2) at ../../dev/ata/ata-all.c:1518 9: scp->ioaddr = 57248 8: command = 236 'ì' (gdb) s (never returns) The kernel panics if I access the ar0 device. The backtrace is: (gdb) bt #0 Debugger (msg=0xc027477b "panic") at ../../i386/i386/db_interface.c:321 #1 0xc015ff48 in panic (fmt=0xc0278737 "biodone: bp %p not busy %d") at ../../kern/kern_shutdown.c:579 #2 0xc0188576 in biodone (bp=0xc19d2000) at ../../kern/vfs_bio.c:2664 #3 0xc022e536 in ad_interrupt (request=0xc19d4f80) at ../../dev/ata/ata-disk.c:698 #4 0xc02294fb in ata_intr (data=0xc17e5d80) at ../../dev/ata/ata-all.c:1159 #5 0xc025af3f in find_idesc (maskptr=0xc104a7c0, irq=0) at ../../i386/isa/intr_machdep.c:590 Now, I have no ideas of how to solve this. :-( regards, jonas Jeff Kletsky wrote: > > I have tried each of these cards in two different boxes, 4.4-RELEASE > as installed, and 4.4-STABLE: > > FreeBSD port6.pn.wagsky.com 4.4-STABLE > FreeBSD 4.4-STABLE #0: Sun Sep 16 16:10:23 PDT 2001 > jeff@devel.pn.wagsky.com:/usr/obj/usr/src/sys/PIIIAV.20010916 i386 > > and seem to be unable to get the drives to be recognized by FreeBSD. > This seems to be in conflict with the release notes and HARDWARE.TXT. > Reading the notes in the group, others have been experiencing similar > issues with the TX2 series. Is the TX2 different that what is > referred to in the notes? > > The symptoms are as follows: > > (already run sh MAKEDEV ad4 ad5 ad6 ad7 -- with no change in behavior) > > * One drive on card's IDE1 > > - BIOS recognizes and loads > - boot manager sees drive > - atapci1 is seen on screen and in dmesg.boot > - ad4 is not seen > > * One drive on card's IDE2 (or both populated) > > - BIOS recognizes and loads > - boot manager sees drive > - atapci1 is (I believe) seen on screen > - hangs in the boot process just before identifying disks > > Motherboards are Intel se440-bx2, P600 and P600E, Promise card in > first or second PCI slot (from AGP card). No issues with machines > otherwise. > > Ultra100 TX2 is PDC20268 V2.10 B23 > FastTrak100 TX2 is PDC20270 V2.00 B2 > > >From dmesg.boot: > [...] > chip1: port 0x7000-0x700f at device > 7.3 on pci0 > atapci1: port 0x1070-0x107f,0x1080-0x1083,0x1088 > -0x108f,0x1084-0x1087,0x1090-0x1097 mem 0xf4000000-0xf4003fff irq 10 at device 1 > 4.0 on pci0 > ata2: at 0x1090 on atapci1 > ata3: at 0x1088 on atapci1 > fxp0: port 0x1000-0x103f mem 0xf4100000-0xf41f > ffff,0xf4004000-0xf4004fff irq 9 at device 16.0 on pci0 > [...] > ppc0: parallel port not found. > ad0: 19574MB [39770/16/63] at ata0-master UDMA33 > acd0: CDROM at ata1-master using PIO4 > Mounting root from ufs:/dev/ad0s1a > > (the freezing behavious is similar, but does not proceed to ad0) > > Any help on this would be greatly appreciated, even if (for now) it is > a notation in the notes so that others may not suffer the same fate. > > Thanks! > > Jeff > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" 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 Oct 1 13:17:32 2001 Delivered-To: freebsd-hardware@freebsd.org Received: from ns.altadena.net (ns.altadena.net [206.126.144.2]) by hub.freebsd.org (Postfix) with ESMTP id 08BA937B40A; Mon, 1 Oct 2001 13:17:29 -0700 (PDT) Received: (from pete@localhost) by ns.altadena.net (8.11.6/8.8.8) id f91N3xX21733; Mon, 1 Oct 2001 16:03:59 -0700 (PDT) (envelope-from pete) From: Pete Carah Message-Id: <200110012303.f91N3xX21733@ns.altadena.net> Subject: vinum on a 3-ware controller To: questions@freebsd.org, hardware@freebsd.org Date: Mon, 1 Oct 2001 16:03:59 -0700 (PDT) X-Mailer: ELM [version 2.4ME+ PL68 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=iso8859-1 Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org I'm having trouble trying to set up vinum striping over several drives attached to a 3ware raid card (in "jbod" mode). (reason for vinum is that it looks like I can't get the 3ware to raid across more than one card.) I get (on the second attempt): nntp2# vinum stripe -v /dev/twed1s4a /dev/twed2s4a /dev/twed3s4a drive vinumdrive1 device /dev/twed2s4a Can't create drive vinumdrive1, device /dev/twed2s4a: Can't initialize drive vinumdrive1 (first attempt gets the same message, but about drive0 on twed1s4a) ------------------------------------------------------------------------ -- Pete To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Mon Oct 1 19:28:11 2001 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 CE0BF37B40B; Mon, 1 Oct 2001 19:28:05 -0700 (PDT) Received: by wantadilla.lemis.com (Postfix, from userid 1004) id BF26D6A90F; Tue, 2 Oct 2001 11:58:52 +0930 (CST) Date: Tue, 2 Oct 2001 11:58:52 +0930 From: Greg Lehey To: Pete Carah Cc: questions@freebsd.org, hardware@freebsd.org Subject: Re: vinum on a 3-ware controller Message-ID: <20011002115852.J31215@wantadilla.lemis.com> References: <200110012303.f91N3xX21733@ns.altadena.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200110012303.f91N3xX21733@ns.altadena.net>; from pete@ns.altadena.net on Mon, Oct 01, 2001 at 04:03:59PM -0700 Organization: The FreeBSD Project Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-418-838-708 WWW-Home-Page: http://www.FreeBSD.org/ 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 List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Monday, 1 October 2001 at 16:03:59 -0700, Pete Carah wrote: > I'm having trouble trying to set up vinum striping over several drives > attached to a 3ware raid card (in "jbod" mode). (reason for vinum is > that it looks like I can't get the 3ware to raid across more than one card.) > > I get (on the second attempt): > > nntp2# vinum stripe -v /dev/twed1s4a /dev/twed2s4a /dev/twed3s4a > drive vinumdrive1 device /dev/twed2s4a > Can't create drive vinumdrive1, device /dev/twed2s4a: Can't initialize drive vinumdrive1 > > (first attempt gets the same message, but about drive0 on twed1s4a) This is because Vinum doesn't know about this controller. Pete followed up this message with private mail indicating that he had found how to tell Vinum, and he now has it running. This can happen with other controllers; the code in question should go away with DEVFS. In general, if you have an unusual controller and you have trouble with it, let me know. It's a trivial thing to add. Greg -- When replying to this message, please copy the original recipients. If you don't, I may ignore the reply. For more information, see http://www.lemis.com/questions.html 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 Thu Oct 4 8: 1:29 2001 Delivered-To: freebsd-hardware@freebsd.org Received: from hotmail.com (f176.pav1.hotmail.com [64.4.31.176]) by hub.freebsd.org (Postfix) with ESMTP id CBFB637B406; Thu, 4 Oct 2001 08:01:22 -0700 (PDT) Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Thu, 4 Oct 2001 08:01:22 -0700 Received: from 212.30.183.204 by pv1fd.pav1.hotmail.msn.com with HTTP; Thu, 04 Oct 2001 15:01:21 GMT X-Originating-IP: [212.30.183.204] From: "Magdalinin Kirill" To: freebsd-hardware@freebsd.org Cc: questions@freebsd.org Subject: turning off write cache on SCSI drive Date: Thu, 04 Oct 2001 19:01:21 +0400 Mime-Version: 1.0 Content-Type: text/plain; format=flowed Message-ID: X-OriginalArrivalTime: 04 Oct 2001 15:01:22.0070 (UTC) FILETIME=[6E0DBB60:01C14CE5] Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Hello, some mail posts on softupdates says that turning off write cache is prerequisite for it. How can I accomplish it on freebsd? As far as I know there is camcontrol utility, but it's usage is quite difficult for me to understand. I stuck the drive into another box and turned off write cache using raid controler bios setup, but it's uclear if this setting is still active. The other way I can think of it is turning it off under Win2K. Yet how can I check write cache status under FreeBSD? thanks, Kirill Magdalinin bsdforumen@hotmail.com _________________________________________________________________ Get your FREE download of MSN Explorer at http://explorer.msn.com/intl.asp To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Thu Oct 4 8: 6:40 2001 Delivered-To: freebsd-hardware@freebsd.org Received: from anaconda.acceleratedweb.net (anaconda.acceleratedweb.net [209.51.164.130]) by hub.freebsd.org (Postfix) with SMTP id 3264337B40A for ; Thu, 4 Oct 2001 08:06:29 -0700 (PDT) Received: (qmail 93998 invoked by uid 106); 4 Oct 2001 15:06:54 -0000 Received: from 66-65-36-21.nyc.rr.com (HELO sharky) (66.65.36.21) by anaconda.acceleratedweb.net with SMTP; 4 Oct 2001 15:06:54 -0000 From: "Simon" To: "freebsd-hardware@freebsd.org" , "Magdalinin Kirill" Cc: "questions@freebsd.org" Date: Thu, 04 Oct 2001 11:06:17 -0400 Reply-To: "Simon" X-Mailer: PMMail 2000 Professional (2.10.2010) For Windows 2000 (5.0.2195) In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Subject: Re: turning off write cache on SCSI drive Message-Id: <20011004150629.3264337B40A@hub.freebsd.org> Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org What controller are you using? most allow you to do this from their BIOS. Otherwise, as you said, you can use camcontrol. Search the mail archives for write cache off, you will find posting that give exact command. -Simon On Thu, 04 Oct 2001 19:01:21 +0400, Magdalinin Kirill wrote: >Hello, > >some mail posts on softupdates says that turning off write cache is >prerequisite for it. > >How can I accomplish it on freebsd? As far as I know >there is camcontrol utility, but it's usage is quite >difficult for me to understand. > >I stuck the drive into another box and turned off >write cache using raid controler bios setup, but >it's uclear if this setting is still active. > >The other way I can think of it is turning it off >under Win2K. Yet how can I check write cache status >under FreeBSD? > >thanks, > >Kirill Magdalinin >bsdforumen@hotmail.com > >_________________________________________________________________ >Get your FREE download of MSN Explorer at http://explorer.msn.com/intl.asp > > >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 Thu Oct 4 10: 1:39 2001 Delivered-To: freebsd-hardware@freebsd.org Received: from hpux36.dc.engr.scu.edu (hpux36.dc.engr.scu.edu [129.210.16.36]) by hub.freebsd.org (Postfix) with ESMTP id 3833937B403 for ; Thu, 4 Oct 2001 10:01:38 -0700 (PDT) Received: from localhost (dclark@localhost) by hpux36.dc.engr.scu.edu (8.10.2/8.10.2) with ESMTP id f94H1Wq19406 for ; Thu, 4 Oct 2001 10:01:32 -0700 (PDT) Date: Thu, 4 Oct 2001 10:01:32 -0700 (PDT) From: "Dorr H. Clark" To: freebsd-hardware@freebsd.org Subject: flash vs. disk IDE devices Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Does anyone know of good resources exploring the trade off between flash devices which emulate IDE disks vs. hard drives? Please cc the response as I am unsubscribed to this list. Thanks, -dhc School of Engineering Santa Clara University To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Fri Oct 5 5:44:48 2001 Delivered-To: freebsd-hardware@freebsd.org Received: from hotmail.com (f170.pav1.hotmail.com [64.4.31.170]) by hub.freebsd.org (Postfix) with ESMTP id CEA3E37B408; Fri, 5 Oct 2001 05:44:36 -0700 (PDT) Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Fri, 5 Oct 2001 05:44:36 -0700 Received: from 212.30.183.204 by pv1fd.pav1.hotmail.msn.com with HTTP; Fri, 05 Oct 2001 12:44:36 GMT X-Originating-IP: [212.30.183.204] From: "Magdalinin Kirill" To: simon@optinet.com, freebsd-hardware@freebsd.org Cc: questions@freebsd.org Subject: Re: Re: turning off write cache on SCSI drive Date: Fri, 05 Oct 2001 16:44:36 +0400 Mime-Version: 1.0 Content-Type: text/plain; format=flowed Message-ID: X-OriginalArrivalTime: 05 Oct 2001 12:44:36.0747 (UTC) FILETIME=[7DB68DB0:01C14D9B] Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org >What controller are you using? most allow you to do this >from their BIOS. It's an Adaptec SCSI BIOS v3.00 on ASUS P2B-DS Revision 1013 to which I upgraded from some older version and there is no such feature. Anyway, the drive seems to keep write cache off that I set via Mylex AcceleRAID 352 on another box, because the setting is disabled under Win2K even though Fujitsu support says it would be switched on again after restart. I did find exac command for switching cache ("camcontrol modepage daX -m 8 -e"), but it seems to be only writeable, because according to vi launched with that command both write and read cache are disabled after each restart. regards, Kirill Magdalinin, bsdforumen@hotmail.com >From: "Simon" >Reply-To: "Simon" >To: "freebsd-hardware@freebsd.org" , >"Magdalinin Kirill" >CC: "questions@freebsd.org" >Subject: Re: turning off write cache on SCSI drive >Date: Thu, 04 Oct 2001 11:06:17 -0400 > > >What controller are you using? most allow you to do this >from their BIOS. Otherwise, as you said, you can use >camcontrol. Search the mail archives for write cache off, >you will find posting that give exact command. > >-Simon > >On Thu, 04 Oct 2001 19:01:21 +0400, Magdalinin Kirill wrote: > > >Hello, > > > >some mail posts on softupdates says that turning off write cache is > >prerequisite for it. > > > >How can I accomplish it on freebsd? As far as I know > >there is camcontrol utility, but it's usage is quite > >difficult for me to understand. > > > >I stuck the drive into another box and turned off > >write cache using raid controler bios setup, but > >it's uclear if this setting is still active. > > > >The other way I can think of it is turning it off > >under Win2K. Yet how can I check write cache status > >under FreeBSD? > > > >thanks, > > > >Kirill Magdalinin > >bsdforumen@hotmail.com > > > >_________________________________________________________________ > >Get your FREE download of MSN Explorer at >http://explorer.msn.com/intl.asp > > > > > >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-questions" in the body of the message _________________________________________________________________ Get your FREE download of MSN Explorer at http://explorer.msn.com/intl.asp To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Fri Oct 5 21: 9:41 2001 Delivered-To: freebsd-hardware@freebsd.org Received: from www.tntpro.com (159-63.suscom-maine.net [207.5.159.63]) by hub.freebsd.org (Postfix) with ESMTP id 58B8537B42F for ; Fri, 5 Oct 2001 21:09:36 -0700 (PDT) Received: from celery (celery.tntpro.com [192.168.0.13]) by www.tntpro.com (8.11.6/8.11.6) with SMTP id f9649Z544019 for ; Sat, 6 Oct 2001 00:09:35 -0400 (EDT) (envelope-from tony@tntpro.com) From: "tony" To: Subject: Is a Linksys WDT11 Wireless Network PCI NIC compatible with freebsd 4.3 or 4.4? Date: Sat, 6 Oct 2001 00:09:40 -0500 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4807.1700 Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Subject says it all, moving to a house that I can't drill any holes and can't run cable... would like to use wireless between cable modem and Freebsd firewall. Thanks, Tony To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Sat Oct 6 19:56:30 2001 Delivered-To: freebsd-hardware@freebsd.org Received: from lariat.org (lariat.org [12.23.109.2]) by hub.freebsd.org (Postfix) with ESMTP id 5DBC837B401 for ; Sat, 6 Oct 2001 19:56:28 -0700 (PDT) Received: (from brett@localhost) by lariat.org (8.9.3/8.9.3) id UAA23619 for hardware@freebsd.org; Sat, 6 Oct 2001 20:56:25 -0600 (MDT) Date: Sat, 6 Oct 2001 20:56:25 -0600 (MDT) From: Brett Glass Message-Id: <200110070256.UAA23619@lariat.org> To: hardware@freebsd.org Subject: DSL modem drivers for FreeBSD? Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Does FreeBSD have support for any DSL modem that uses the DMT modulation scheme? This is a showstopper for a client.... He will (alas) go with Linux if he can't find drivers for an internal DSL modem such as the Intel 2200. --Brett Glass To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message