From owner-freebsd-hardware Sun Sep 16 4: 1:49 2001 Delivered-To: freebsd-hardware@freebsd.org Received: from kirov.i.eunet.no (kirov.i.eunet.no [193.71.2.3]) by hub.freebsd.org (Postfix) with ESMTP id AFD2237B409 for ; Sun, 16 Sep 2001 04:01:40 -0700 (PDT) Received: from mastahr.kpnqwest.no (mastahr.i.eunet.no [193.71.2.85] (may be forged)) by kirov.i.eunet.no (8.9.3/8.9.3/GN) with ESMTP id NAA12575; Sun, 16 Sep 2001 13:00:42 +0200 (MET DST) Message-Id: <5.1.0.14.2.20010916125135.00a82380@kirov.eunet.no> X-Sender: awand@kirov.eunet.no X-Mailer: QUALCOMM Windows Eudora Version 5.1 Date: Sun, 16 Sep 2001 13:03:09 +0200 To: Mike Tancsa , jus@security.za.net (Justin Stanford) From: Andreas Wideroe Andersen Subject: Re: Gigabyte 1U GS-SR101 Server and Onboard Intel NIC trouble.. anyone? Cc: freebsd-hardware@FreeBSD.ORG In-Reply-To: <3jj7qt43t49sbnpn1kice63r5b9m9v7ikg@4ax.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1"; format=flowed Content-Transfer-Encoding: quoted-printable 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 At 17:59 15.09.01 -0400, Mike Tancsa wrote: >On 15 Sep 2001 10:47:38 -0400, in sentex.lists.freebsd.hardware you wrote: > > > > >Has anyone else experienced this trouble? I hesitate to think that it is= a > >faulty NIC, but that's all I can think of right now.. is there a known > >problem with FreeBSD and this hardware? GNATS and a search of the= mailling > >lists doesn't seem to reveal anything. > > > > >Is this board based on the Intel 815e chipset by chance ? The Intel NICs on >those boards need 4.4Release (or 4.3 STABLE from late August) to work >properly. I've got an Aopen MX3S motherboard with Intel 815e chipset and an onboard=20 Intel NIC. I'm having problems with timouts. Whenever I'm updating ports or= =20 when there is massive traffic going through the NIC I get: fxp0: Device timout or fxp0: scb timeout I just got 4.3 RELEASE installed after trying 30 times, now I want to=20 upgrade to STABLE, but am unable to retrieve the latest distributions. I've been reading about this problem on websites and in mailinglists and it= =20 seems to be a bug in the driver. Is this bug fixed in the 4.4 version of=20 FreeBSD? Thanks for any help! /Andreas --- Mvh/Rgds, Andreas Wider=F8e Andersen KPNQwest Norway AS Phone: +47 22 09 78 31 Mobile: +47 90 92 61 21 Fax: +47 22 09 29 01 http://www.kpnqwest.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Sun Sep 16 9: 4:46 2001 Delivered-To: freebsd-hardware@freebsd.org Received: from cage.simianscience.com (cage.simianscience.com [64.7.134.1]) by hub.freebsd.org (Postfix) with ESMTP id F3B4037B406 for ; Sun, 16 Sep 2001 09:04:40 -0700 (PDT) Received: from chimp.sentex.net (fcage [192.168.0.2]) by cage.simianscience.com (8.11.6/8.11.6) with ESMTP id f8GG4U947119; Sun, 16 Sep 2001 12:04:31 -0400 (EDT) (envelope-from mike@sentex.net) Message-Id: <5.1.0.14.0.20010916115740.048925c0@192.168.0.12> X-Sender: mdtancsa@192.168.0.12 X-Mailer: QUALCOMM Windows Eudora Version 5.1 Date: Sun, 16 Sep 2001 12:04:29 -0400 To: Andreas Wideroe Andersen From: Mike Tancsa Subject: Re: Gigabyte 1U GS-SR101 Server and Onboard Intel NIC trouble.. anyone? Cc: freebsd-hardware@FreeBSD.ORG In-Reply-To: <5.1.0.14.2.20010916125135.00a82380@kirov.eunet.no> References: <3jj7qt43t49sbnpn1kice63r5b9m9v7ikg@4ax.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed 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 At 01:03 PM 9/16/2001 +0200, Andreas Wideroe Andersen wrote: >At 17:59 15.09.01 -0400, Mike Tancsa wrote: >>On 15 Sep 2001 10:47:38 -0400, in sentex.lists.freebsd.hardware you wrote: >> >> > >> >Has anyone else experienced this trouble? I hesitate to think that it is a >> >faulty NIC, but that's all I can think of right now.. is there a known >> >problem with FreeBSD and this hardware? GNATS and a search of the mailling >> >lists doesn't seem to reveal anything. >> > >> >> >>Is this board based on the Intel 815e chipset by chance ? The Intel NICs on >>those boards need 4.4Release (or 4.3 STABLE from late August) to work >>properly. > > >I've got an Aopen MX3S motherboard with Intel 815e chipset and an onboard >Intel NIC. I'm having problems with timouts. Whenever I'm updating ports >or when there is massive traffic going through the NIC I get: > >fxp0: Device timout or fxp0: scb timeout > >I just got 4.3 RELEASE installed after trying 30 times, now I want to >upgrade to STABLE, but am unable to retrieve the latest distributions. > >I've been reading about this problem on websites and in mailinglists and >it seems to be a bug in the driver. Is this bug fixed in the 4.4 version >of FreeBSD? Yes, there is a bug in this particular version of the Intel chip from what I understand. A work around to it was committed to the FreeBSD tree Aug 30th. I have several of these boards and they work great with this version of the driver. This fix corrects the problem for both the ET and EM version of the NIC e.g. fxp1: port 0xc400-0xc43f mem 0xd5101000-0xd5101fff irq 11 at device 8.0 on pci1 fxp1: Ethernet address 00:01:80:05:d2:67 inphy1: on miibus1 inphy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto In the intrim, it *might* be possible to grabb the miibus and fxp KLDs from 4.4R and load them that way. Not sure if it will work or not, but it might. Or grab a 4.4R kernel.GENERIC. That *might* work long enough for you to cvsup. Also, the bug seems to happen less if you are in 100BaseTX instead of 10baseT. ---Mike -------------------------------------------------------------------- Mike Tancsa, tel +1 519 651 3400 Sentex Communications, mike@sentex.net Providing Internet since 1994 www.sentex.net Cambridge, Ontario Canada www.sentex.net/mike To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Sun Sep 16 10: 1:10 2001 Delivered-To: freebsd-hardware@freebsd.org Received: from berkano.pair.com (berkano.pair.com [209.68.1.182]) by hub.freebsd.org (Postfix) with SMTP id 66D4437B409 for ; Sun, 16 Sep 2001 10:01:04 -0700 (PDT) Received: (qmail 58759 invoked by uid 3258); 16 Sep 2001 17:01:03 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 16 Sep 2001 17:01:03 -0000 Date: Sun, 16 Sep 2001 13:01:02 -0400 (EDT) From: Bryan Taylor To: Justin Stanford Cc: , Subject: Re: Gigabyte 1U GS-SR101 Server and Onboard Intel NIC trouble.. anyone? In-Reply-To: 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 had the same kind of problem few months back. Was never able to find a solution for it (No help from Gigabyte). It wasted 3 weeks of my time. Finally I decided to dump the Gigabyte 1U GS-SR101 server and bought a 1U server based on ServerWork LE chipset. The Gigabyte 1U GS-SR101 was nothing but problems. Bryan Tyalor P-Network On Sat, 15 Sep 2001, Justin Stanford wrote: > [Apologies for cross-post] > > Hi, > > I'm working with one of these 1U GS-SR101 Gigabyte rackmount servers, with > twin onboard Intel Pro NIC's, running FreeBSD 4.3-RELEASE. It has a > pentium III 1GHz CPU, and 512mb RAM. > > When booting GENERIC, it get fxp0, and fxp1, as expected. However, upon > assigning correct IP's, and other network parameters, and extensive > testing between both cisco routers and other miscellaneous servers, I can > *only* get pings or other traffic flowing on fxp0, and not fxp1, not > matter what I seem to do. fxp1 appears to be up in all respects, but it > just doesn't seem to be working, whereas fxp0 works fine. > > However, I can ping fxp1 via fxp0, so the interface is up on the system, > but I can't get anything via fxp1. > > Has anyone else experienced this trouble? I hesitate to think that it is a > faulty NIC, but that's all I can think of right now.. is there a known > problem with FreeBSD and this hardware? GNATS and a search of the mailling > lists doesn't seem to reveal anything. > > Thanks in anticipation, > Justin > > (Kindly CC me any answers as I am not subscribed, thank you.) > > -- > Justin Stanford > Internet/Network Security & Solutions Consultant > 4D Digital Security > http://www.4dds.co.za > Cell: (082) 7402741 > E-Mail: jus@security.za.net > PGP Key: http://www.security.za.net/jus-pgp-key.txt > > > > 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 16 16:44:50 2001 Delivered-To: freebsd-hardware@freebsd.org Received: from bunrab.catwhisker.org (adsl-63-193-123-122.dsl.snfc21.pacbell.net [63.193.123.122]) by hub.freebsd.org (Postfix) with ESMTP id 96FD537B40B for ; Sun, 16 Sep 2001 16:44:43 -0700 (PDT) Received: (from david@localhost) by bunrab.catwhisker.org (8.11.6/8.11.6) id f8GNieg75347 for hardware@freebsd.org; Sun, 16 Sep 2001 16:44:40 -0700 (PDT) (envelope-from david) Date: Sun, 16 Sep 2001 16:44:40 -0700 (PDT) From: David Wolfskill Message-Id: <200109162344.f8GNieg75347@bunrab.catwhisker.org> To: hardware@freebsd.org Subject: Getting old PC to boot from new(er) IDE disk??!? 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 Somewhat over 2 years ago, I bought a used PC for use as a firewall system, in anticipation of the DSL connection. Since this was shortly after the 1999 USENIX, I used the 3.2-RELEASE CD that I got there. All in all, it has (generally) served me well, despite a disk drive failure. (The failed drive was replaced with a 0.5G drive which has run since that time, after restoring the data from backups.) I also used the same CD to put together a machine to provide various services. Earlier this year, I bought a laptop, which I used as an excuse to experiment with using multiple boot slices. (I run both -STABLE and -CURRENT on the laptop, depending on circumstances.) More recently, I put together a "build machine", where I repeated the "multiple boot slices" approach. (Again, I track, build & run both -STABLE & -CURRENT on it.) With the build machine in place, I picked up a new disk drive, and built up a new drive for the above-mentioned server. (Side note on this below.) About 3 weeks ago, I deployed that new drive; the system was then running FreeBSD 4.3-STABLE. Last weekend, I used the "other bootable slice" to "clone" the running one, then upgraded that to 4.4-RC (after having tracked -STABLE daily on the build machine & my laptop). All this is going well: I expect to be upgrading it about every other week (while continuing to track -STABLE daily on my laptop & the build machine). Fortified by this success, I decided to use the old disk drive from the server as the new drive for the firewall. Accordingly, I carved it into slices, and set up, then populated the file systems. One of the bootable slices was a copy of the exitsing 3.2-R; the other was 4.4-STABLE. I took the (firewall) machine down, replaced the disk drive, re-booted, and... ...nothing. The machine recognizes that there's a drive -- the only drive on any IDE controller, and it's primary. It even sees that there are a couple of bootable slices, but hitting any of F1, F2, or Enter just results in a beep. It won't boot. I tried putting the "new" drive back on the build machine, and went through the sequence (F5/F1 & F5/F2) to boot from the new drive. (Single user mode, to be sure -- but at least it recognized the possibility & booted.) Oh: that "side note" -- I actually had tried upgrading the firewall machine first, but it wouldn't boot from that new drive -- same symptoms as above. So at this point, I think I would be fairly described as "exasperated". What resources exist to help me figure out what is going on here? I really don't like having the firewall machine down; that impairs connectivity. :-( In case it isn't obvious, I'm not real familiar with PCs; nearly all my experience with them has been in the last 3.5 years, and that is just running FreeBSD. Help? Thanks, david -- David H. Wolfskill david@catwhisker.org Help? Thanks, david -- As a computing professional, I believe it would be unethical for me to advise, recommend, or support the use (save possibly for personal amusement) of any product that is or depends on any Microsoft product. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Mon Sep 17 21:16:47 2001 Delivered-To: freebsd-hardware@freebsd.org Received: from posgate.acis.com.au (posgate.acis.com.au [203.14.230.14]) by hub.freebsd.org (Postfix) with ESMTP id 4FD0637B409 for ; Mon, 17 Sep 2001 21:16:39 -0700 (PDT) Received: from bullseye.apana.org.au (dialup-5.aaa.net.au [203.14.230.70]) by posgate.acis.com.au (8.11.3/8.11.3) with ESMTP id f8I4GUJ25011; Tue, 18 Sep 2001 14:16:30 +1000 Received: from bullseye.apana.org.au (central-f.apana.org.au [203.9.107.235]) by bullseye.apana.org.au (8.8.8/8.8.8) with ESMTP id JAA16490; Tue, 18 Sep 2001 09:35:49 +1000 (EST) (envelope-from andymac@bullseye.apana.org.au) Date: Tue, 18 Sep 2001 09:23:59 +1000 (EST) From: Andrew MacIntyre To: David Wolfskill Cc: Subject: Re: Getting old PC to boot from new(er) IDE disk??!? In-Reply-To: <200109162344.f8GNieg75347@bunrab.catwhisker.org> Message-ID: X-X-Sender: andymac@bullseye.apana.org.au 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 On Sun, 16 Sep 2001, David Wolfskill wrote: {...} > In case it isn't obvious, I'm not real familiar with PCs; nearly all my > experience with them has been in the last 3.5 years, and that is just > running FreeBSD. You don't give a lot of detail about the machines (age, CPU) or the size of the unbootable drive, but if your firewall system is sufficiently elderly the BIOS may not be able to handle some of the contents of the MBR. I can think of two alternatives for this situation:- - create a boot partition < 500M (you might need to fiddle with CHS values in the BIOS to get it to work right), with another partition containing the rest of the disk; - use a dangerously dedicated MBR (last resort, as various people want DD to disappear) HTH -- Andrew I MacIntyre "These thoughts are mine alone..." E-mail: andymac@bullseye.apana.org.au | Snail: PO Box 370 andymac@pcug.org.au | Belconnen ACT 2616 Web: http://www.andymac.org/ | Australia To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Mon Sep 17 22:45:27 2001 Delivered-To: freebsd-hardware@freebsd.org Received: from athena.za.net (athena.za.net [196.30.167.200]) by hub.freebsd.org (Postfix) with ESMTP id 1BF3F37B416; Mon, 17 Sep 2001 22:45:11 -0700 (PDT) Received: from jus (helo=localhost) by athena.za.net with local-esmtp (Exim 3.13 #1) id 15jDgc-0007oQ-00; Tue, 18 Sep 2001 07:44:46 +0200 Date: Tue, 18 Sep 2001 07:44:46 +0200 (SAST) From: Justin Stanford X-Sender: jus@athena.za.net To: Bryan Taylor Cc: freebsd-questions@freebsd.org, freebsd-hardware@freebsd.org Subject: Re: Gigabyte 1U GS-SR101 Server and Onboard Intel NIC trouble.. anyone? In-Reply-To: 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'm happy to say that the problem was fixed with the latest version of 4.4 FreeBSD. Many thanks for all the help, Justin -- Justin Stanford Internet/Network Security & Solutions Consultant 4D Digital Security http://www.4dds.co.za Cell: (082) 7402741 E-Mail: jus@security.za.net PGP Key: http://www.security.za.net/jus-pgp-key.txt On Sun, 16 Sep 2001, Bryan Taylor wrote: > > I had the same kind of problem few months back. Was never able to find a > solution for it (No help from Gigabyte). It wasted 3 weeks of my time. > Finally I decided to dump the Gigabyte 1U GS-SR101 server and bought a 1U > server based on ServerWork LE chipset. The Gigabyte 1U GS-SR101 was nothing > but problems. > > Bryan Tyalor > P-Network > > On Sat, 15 Sep 2001, Justin Stanford wrote: > > > [Apologies for cross-post] > > > > Hi, > > > > I'm working with one of these 1U GS-SR101 Gigabyte rackmount servers, with > > twin onboard Intel Pro NIC's, running FreeBSD 4.3-RELEASE. It has a > > pentium III 1GHz CPU, and 512mb RAM. > > > > When booting GENERIC, it get fxp0, and fxp1, as expected. However, upon > > assigning correct IP's, and other network parameters, and extensive > > testing between both cisco routers and other miscellaneous servers, I can > > *only* get pings or other traffic flowing on fxp0, and not fxp1, not > > matter what I seem to do. fxp1 appears to be up in all respects, but it > > just doesn't seem to be working, whereas fxp0 works fine. > > > > However, I can ping fxp1 via fxp0, so the interface is up on the system, > > but I can't get anything via fxp1. > > > > Has anyone else experienced this trouble? I hesitate to think that it is a > > faulty NIC, but that's all I can think of right now.. is there a known > > problem with FreeBSD and this hardware? GNATS and a search of the mailling > > lists doesn't seem to reveal anything. > > > > Thanks in anticipation, > > Justin > > > > (Kindly CC me any answers as I am not subscribed, thank you.) > > > > -- > > Justin Stanford > > Internet/Network Security & Solutions Consultant > > 4D Digital Security > > http://www.4dds.co.za > > Cell: (082) 7402741 > > E-Mail: jus@security.za.net > > PGP Key: http://www.security.za.net/jus-pgp-key.txt > > > > > > > > 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 18 4:50: 9 2001 Delivered-To: freebsd-hardware@freebsd.org Received: from blake.arcadia.spb.ru (ns.arcadia.spb.ru [212.119.177.2]) by hub.freebsd.org (Postfix) with ESMTP id 8502A37B408 for ; Tue, 18 Sep 2001 04:50:04 -0700 (PDT) Received: from anti.arcadia.spb.ru (anti.arcadia.spb.ru [212.119.177.3] (may be forged)) by blake.arcadia.spb.ru (8.9.2/8.8.6) with SMTP id PAA93356 for ; Tue, 18 Sep 2001 15:50:59 +0400 (MSD) Received: from LEV ([172.16.16.85]:1413) (HELO dhcp85.arcadia.intranet) by anti.arcadia.spb.ru ([212.119.177.3]:25) (F-Secure Anti-Virus for Internet Mail 5.0.53 Release) with SMTP; Tue, 18 Sep 2001 11:48:17 -0000 Date: Tue, 18 Sep 2001 15:46:53 +0400 From: Lev Serebryakov X-Mailer: The Bat! (v1.52f) Personal Reply-To: Lev Serebryakov Organization: Arcadia, Inc. X-Priority: 3 (Normal) Message-ID: <469319420.20010918154653@arcadia.spb.ru> To: freebsd-hardware@FreeBSD.ORG Subject: Is 3COM OfficeConnect/USB modem supported by FreeBSD? MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii 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 Hello freebsd-hardware, Is modem "3COM OfficeConnect/USB model no 3294" supportet by FreeBSD? It could be attached via COM, but I have not free COM ports on server. How much such modems do I connect to computer with FreeBSD? -- Best regards, Lev mailto:Lev.Serebryakov@arcadia.spb.ru To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Tue Sep 18 14:10: 1 2001 Delivered-To: freebsd-hardware@freebsd.org Received: from pop3.psconsult.nl (ps226.psconsult.nl [193.67.147.226]) by hub.freebsd.org (Postfix) with ESMTP id 1342937B40B for ; Tue, 18 Sep 2001 14:09:53 -0700 (PDT) Received: (from paul@localhost) by pop3.psconsult.nl (8.9.2/8.9.2) id XAA16243; Tue, 18 Sep 2001 23:09:43 +0200 (CEST) (envelope-from paul) Date: Tue, 18 Sep 2001 23:09:43 +0200 From: Paul Schenkeveld To: Ian West Cc: freebsd-hardware@FreeBSD.ORG Subject: Re: Dual PCI SIO card Message-ID: <20010918230942.A16162@psconsult.nl> References: <20010505133007.Y1899@rose.niw.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <20010505133007.Y1899@rose.niw.com.au>; from ian@apdata.com.au on Sat, May 05, 2001 at 01:30:07PM +0930 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 all, On Sat, May 05, 2001 at 01:30:07PM +0930, Ian West wrote: > Hi, I have a Sunix SUN1889 based dual serial card. I have it working by > modifying the sio driver to scale divisors by 8, and manually > configuring 2 isa sio ports in a kernel config (along with > COM_MULTIPORT). This is not ideal as it changes if the config of the > machine is altered. (PCI allocations change). I would like to get > 'proper' support working. Is there a way within the sio driver to spawn > two seperate devices from one pci probe ? Is a better solution to treat > the device as a pci bridge and spawn to child sio ports from this ? Can > anyone point me at the right doco, or a driver which already implements > something like this ? I also urgently need extra serial ports on two new machines and have only PCI slots to put them in. I found a 4 port serial card from PC COM but it's not recognized at all by FreeBSD 4.3. I'm willing to spend a couple of days trying to get them to work if there's any chance getting it to work reliably. But I have never played with drivers for PCI cards. I've read the serial port source thoroughly some 8 years ago or so and have done many C programming projects over the last 17 years but I've no clue where to start getting this serial port to work. There is source for a Linux driver available however. Regards, Paul Schenkeveld To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Wed Sep 19 5:33: 1 2001 Delivered-To: freebsd-hardware@freebsd.org Received: from scan.ji-net.com (scan.ji-net.com [203.130.156.4]) by hub.freebsd.org (Postfix) with ESMTP id 3FD8137B403 for ; Wed, 19 Sep 2001 05:32:58 -0700 (PDT) Received: from 4090xdvd ([203.148.244.235]) by scan.ji-net.com (8.11.2/8.11.2) with SMTP id f8JCWsA28410 for ; Wed, 19 Sep 2001 19:32:55 +0700 From: "Raymond Pert" To: Subject: HP USB cd-writer Date: Wed, 19 Sep 2001 19:35:24 +0700 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="windows-874" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0) Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2479.0006 X-Virus-Scanned: by AMaViS-perl11-milter (http://amavis.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 Where do I start? I am really new at this and just recently got X to run on my Toshiba notebook. Thanx To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Wed Sep 19 16:31:34 2001 Delivered-To: freebsd-hardware@freebsd.org Received: from c001.snv.cp.net (c001-h018.c001.snv.cp.net [209.228.32.132]) by hub.freebsd.org (Postfix) with SMTP id 06AD737B41A for ; Wed, 19 Sep 2001 16:31:18 -0700 (PDT) Received: (cpmta 29263 invoked from network); 19 Sep 2001 16:31:10 -0700 Date: 19 Sep 2001 16:31:10 -0700 Message-ID: <20010919233110.29262.cpmta@c001.snv.cp.net> X-Sent: 19 Sep 2001 23:31:10 GMT Received: from [24.48.64.135] by mail.sawilson.com with HTTP; 19 Sep 2001 16:31:10 PDT Content-Type: text/plain Content-Disposition: inline Mime-Version: 1.0 To: rpert@ji-net.com From: sawilson@sawilson.com Cc: freebsd-hardware@freebsd.org X-Mailer: Web Mail 3.9.3.5 Subject: Re: HP USB cd-writer X-Sent-From: sawilson@sawilson.com 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 Wed, 19 September 2001, "Raymond Pert" wrote: > > Where do I start? > > I am really new at this and just recently got X to run on my Toshiba > notebook. First you'll have to make sure that you have USB in your kernel. You'll probably have to recompile your kernel. You can find information on how to do that here: http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/kernelconfig.html After that, it's a matter of knowing how to use the burner. You can find information on that here: http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/creating-cds.html I found the answers to this using the google search engine: http://www.google.com I put in the keywords: usb cd burner freebsd I can't recommend using google first before asking questions enough. I hope you get your burner working perfectly the first time. -- Best Regards, S.A.Wilson To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Thu Sep 20 5:46:32 2001 Delivered-To: freebsd-hardware@freebsd.org Received: from alpha.dante.org.uk (alpha.dante.org.uk [193.63.211.19]) by hub.freebsd.org (Postfix) with ESMTP id BABE437B407; Thu, 20 Sep 2001 05:46:26 -0700 (PDT) Received: from pi.dante.org.uk ([193.63.211.70] helo=dante.org.uk) by alpha.dante.org.uk with esmtp (Exim 3.12 #4) id 15k3Dl-0000iC-00; Thu, 20 Sep 2001 13:46:25 +0100 Message-ID: <3BA9E51E.5155D58A@dante.org.uk> Date: Thu, 20 Sep 2001 13:46:22 +0100 From: Konstantin Chuguev Organization: Delivery of Advanced Network Technology to Europe Ltd. X-Mailer: Mozilla 4.78 [en] (X11; U; SunOS 5.8 sun4u) X-Accept-Language: ru, en MIME-Version: 1.0 To: freebsd-hardware@freebsd.org, freebsd-current@freebsd.org Subject: USB Multimedia Card (MMC) readers supported? Content-Type: text/plain; charset=us-ascii 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 Hello, Are USB MMC Card Readers (such as SanDisk ImageMate) supported in CURRENT? I suppose they can be treated as generic SCSI-over-USB drives, just want to be sure... Thanks, Konstantin. -- * * Konstantin Chuguev Francis House * * Application Engineer 112 Hills Road * Tel: +44 1223 302992 Cambridge CB2 1PQ D A N T E WWW: http://www.dante.net United Kingdom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Thu Sep 20 7:19: 6 2001 Delivered-To: freebsd-hardware@freebsd.org Received: from smtp013.mail.yahoo.com (smtp013.mail.yahoo.com [216.136.173.57]) by hub.freebsd.org (Postfix) with SMTP id E98C537B405 for ; Thu, 20 Sep 2001 07:19:00 -0700 (PDT) Received: from mkc-65-31-219-45.kc.rr.com (HELO yahoo.com) (65.31.219.45) by smtp.mail.vip.sc5.yahoo.com with SMTP; 20 Sep 2001 14:19:00 -0000 X-Apparently-From: Message-ID: <3BA9FAD3.10502@yahoo.com> Date: Thu, 20 Sep 2001 09:18:59 -0500 From: Jim Bryant Reply-To: kc5vdj@yahoo.com User-Agent: Mozilla/5.0 (X11; U; Linux i386; en-US; rv:0.9.2) Gecko/20010726 Netscape6/6.1 X-Accept-Language: en-us MIME-Version: 1.0 To: Konstantin Chuguev Cc: freebsd-hardware@freebsd.org, freebsd-current@freebsd.org Subject: Re: USB Multimedia Card (MMC) readers supported? References: <3BA9E51E.5155D58A@dante.org.uk> Content-Type: text/plain; charset=us-ascii; format=flowed 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 believe at least one version of the SanDisk one is supported, and I recently helped test and get committed the Microtech CameraMate.... I personally recommend the CameraMate, as it has support for all known CompactFlash devices, including IBM Microdrives, as well as the fact that it also reads SmartMedia cards. Konstantin Chuguev wrote: > Hello, > > Are USB MMC Card Readers (such as SanDisk ImageMate) supported in > CURRENT? > I suppose they can be treated as generic SCSI-over-USB drives, just > want to be sure... > > Thanks, jim -- ET has one helluva sense of humor! He's always anal-probing right-wing schizos! ----------------------------------------------------- POWER TO THE PEOPLE! ----------------------------------------------------- "Religious fundamentalism is the biggest threat to international security that exists today." United Nations Secretary General B.B.Ghali _________________________________________________________ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Thu Sep 20 11:28:16 2001 Delivered-To: freebsd-hardware@freebsd.org Received: from paperboy.sixforty.co.uk (paperboy.sixforty.co.uk [195.10.242.11]) by hub.freebsd.org (Postfix) with ESMTP id E4F4E37B414 for ; Thu, 20 Sep 2001 11:28:12 -0700 (PDT) Received: (from root@localhost) by paperboy.sixforty.co.uk (8.11.1/8.11.1) id f8KISBa25842 for freebsd-hardware@freebsd.org; Thu, 20 Sep 2001 19:28:11 +0100 (BST) (envelope-from freebsd-hw@sixforty.co.uk) Delivered-To: Received: from lfarr (daisy.int.epcdirect.co.uk [192.168.6.200]) by paperboy.sixforty.co.uk (8.11.1/8.11.1av) with ESMTP id f8KIS8S25834 for ; Thu, 20 Sep 2001 19:28:09 +0100 (BST) (envelope-from freebsd-hw@sixforty.co.uk) From: "Lawrence Farr" To: Subject: Temperature Monitoring Date: Thu, 20 Sep 2001 19:28:40 +0100 Message-ID: <007a01c14202$121d1c30$c806a8c0@lfarr> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.2627 Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2462.0000 X-Virus-Scanned: by AMaViS perl-10 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 Has anyone got temperature monitoring to work on an Intel ISP2150 (PIIX4) or an Asus A7V? I'm getting the relevant lines for smb on the A7v: pcf0: at port 0x320-0x321 irq 5 on isa0 iicbus0: on pcf0 addr 0xaa iicsmb0: on iicbus0 smbus0: on iicsmb0 smb0: on smbus0 iic0: on iicbus0 And on the PIIX4 based one: intpm0: port 0x1040-0x104f irq 9 at device 18.3 on pci0 intpm0: I/O mapped 1040 intpm0: intr IRQ 9 enabled revision 0 smbus0: on intsmb0 smb0: on smbus0 intpm0: PM I/O mapped c00 pcf0: at port 0x320-0x321 irq 5 on isa0 iicbus0: on pcf0 addr 0xaa iicsmb0: on iicbus0 smbus1: on iicsmb0 smb1: on smbus1 iic0: on iicbus0 But healthd and lmmon give me junk readings. Any help appreciated! Lawrence Farr EPC Direct Limited mailto:lawrence@epcdirect.co.uk T:01179666123 F:01179666111 M:07970780901 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Thu Sep 20 14: 4:45 2001 Delivered-To: freebsd-hardware@freebsd.org Received: from pt-quorum.com (pt-quorum.com [209.10.167.210]) by hub.freebsd.org (Postfix) with ESMTP id 37A2337B40C for ; Thu, 20 Sep 2001 14:04:35 -0700 (PDT) Received: from gateway.bogus (unknown [213.30.47.84]) by pt-quorum.com (Postfix) with ESMTP id 3397FEC7F for ; Thu, 20 Sep 2001 22:06:10 +0100 (WEST) Received: by gateway.bogus (Postfix, from userid 1000) id 95B915D6B; Thu, 20 Sep 2001 22:04:52 +0100 (WEST) Date: Thu, 20 Sep 2001 22:04:52 +0100 From: Nuno Teixeira To: freebsd-hardware@freebsd.org Subject: hw.ata.wc && hw.ata.tags && softupdates short question Message-ID: <20010920220452.F7820@gateway.bogus> Mail-Followup-To: Nuno Teixeira , freebsd-hardware@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit User-Agent: Mutt/1.2.5i X-Operating-System: FreeBSD 4.4-STABLE 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 to all, I have searched for the experimental hw.ata.tags that work on IDE IBM DTLA and DPLA disks. For what I heard, I concluded that we shouldn't use softupdates with write cache turned on. The first time that I tried this I loose a lot of work due to a power failure. Since then I'm using softupdates with hw.ata.wc="0". Since I have a IBM DTLA disk that supports hw.ata.tags, I want to make the following questions: 1. Can I use softupdates with hw.ata.wc="1" and hw.ata.tags="1" safely? 2. Does hw.ata.tags="1" "allows write caching to be safely turned on really? Thanks very much, -- -- Nuno Teixeira Dir. Técnico pt-quorum.com -- PGP Public Key: http://www.pt-quorum.com/pgp/nunoteixeira.asc Key fingerprint: 8C2C B364 D4DC 0C92 56F5 CE6F 8F07 720A 63A0 4FC7 -- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Thu Sep 20 20:17: 5 2001 Delivered-To: freebsd-hardware@freebsd.org Received: from rover.village.org (rover.bsdimp.com [204.144.255.66]) by hub.freebsd.org (Postfix) with ESMTP id D0BDB37B406; Thu, 20 Sep 2001 20:17:00 -0700 (PDT) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.11.3/8.11.3) with ESMTP id f8L3Gxu20808; Thu, 20 Sep 2001 21:16:59 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost [127.0.0.1]) by harmony.village.org (8.11.6/8.11.6) with ESMTP id f8L3Gw713606; Thu, 20 Sep 2001 21:16:58 -0600 (MDT) (envelope-from imp@harmony.village.org) Message-Id: <200109210316.f8L3Gw713606@harmony.village.org> To: Konstantin Chuguev Subject: Re: USB Multimedia Card (MMC) readers supported? Cc: freebsd-hardware@FreeBSD.ORG, freebsd-current@FreeBSD.ORG In-reply-to: Your message of "Thu, 20 Sep 2001 13:46:22 BST." <3BA9E51E.5155D58A@dante.org.uk> References: <3BA9E51E.5155D58A@dante.org.uk> Date: Thu, 20 Sep 2001 21:16:58 -0600 From: Warner Losh 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 In message <3BA9E51E.5155D58A@dante.org.uk> Konstantin Chuguev writes: : Are USB MMC Card Readers (such as SanDisk ImageMate) supported in : CURRENT? Some are, some aren't. The one I have that works identifies itself as: SanDisk ImageMate II 1.30 and except for lying about the geometry of the devices, it works great. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Fri Sep 21 5:16:17 2001 Delivered-To: freebsd-hardware@freebsd.org Received: from squid.tznet.com (squid.tznet.com [206.31.5.7]) by hub.freebsd.org (Postfix) with ESMTP id 00AE237B40E; Fri, 21 Sep 2001 05:16:15 -0700 (PDT) Received: from localhost (tech@localhost) by squid.tznet.com (8.11.2/8.11.2) with ESMTP id f8LCIwO12656; Fri, 21 Sep 2001 07:18:58 -0500 (CDT) Date: Fri, 21 Sep 2001 07:18:58 -0500 (CDT) From: Scott Pilz To: freebsd-questions@freebsd.org Cc: freebsd-hardware@freebsd.org Subject: Hardware/Problem? 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 Got this on a Dell PowerEdge 2550 early this morning, any ideas? This box is 4.3. kernel log messages: > A33 controller> port 0x8b0-0x8bf at device 15.1 on pci0 Nothing has been added/changed for ages. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Sat Sep 22 17: 6:27 2001 Delivered-To: freebsd-hardware@freebsd.org Received: from femail39.sdc1.sfba.home.com (femail39.sdc1.sfba.home.com [24.254.60.33]) by hub.freebsd.org (Postfix) with ESMTP id A712F37B428; Sat, 22 Sep 2001 17:06:19 -0700 (PDT) Received: from cx543097a ([65.13.57.165]) by femail39.sdc1.sfba.home.com (InterMail vM.4.01.03.20 201-229-121-120-20010223) with SMTP id <20010920001651.KCHK29420.femail39.sdc1.sfba.home.com@cx543097a>; Wed, 19 Sep 2001 17:16:51 -0700 From: "Ian Cartwright" To: "FreeBSD Mobile" , "FreeBSD Questions" , "FreeBSD Hardware" Subject: FW: Problems with netgear MA401 Date: Wed, 19 Sep 2001 17:16:52 -0700 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.2911.0) X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 Importance: Normal 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 Repost because it's been about 24 hours and my post hasn't shown up... > -----Original Message----- > From: Ian Cartwright [mailto:ian351c@home.com] > Sent: Tuesday, September 18, 2001 4:10 PM > To: freebsd-mobile@freebsd.org; FreeBSD Questions; FreeBSD Hardware > Subject: Problems with netgear MA401 > > > Hello eveybody, > > I've posted a couple timed before with no replies. But now that > 4.4-R is out maybe there is time for someone to take alook at this... > > I have a Netgear MA-401 that I have been unable to get woring > under FreeBSD. > The card works fine under Windows 2000. The card works great in FreeBSD > without WEP. When I enable WEP I lose my connection. I have scoured the > archives, which resulted in: update to a recent -STABLE > (9/14/01), addition > of a flag to pccard.conf to allow "Prism2 mode" for my card > (which fixed an > issue with wicontrol reporting WEP off even though ifconfig said > it was on), > and not much else, and moving my configuration commands from > pccard.conf to start_if.wi0. I have also tried configuring > straight from ifconfig with no change in results. > > Here is some info about my current setup: > > - The card works with WEP disabled > - My WEP key is entered in hex > - I am trying to attach to a Netgear MA-102 Access Point which > only supports > 40 bit hex keys > - wicontrol looks like it is doing everything properly (correct > keys, ssid, > etc.) > - ifconfig looks OK too, except "authmode" is NONE and I cannot > change it to > anything else > > Here is a copy of my start_if.wi0 > > #!/bin/sh > /usr/sbin/wicontrol -i wi0 -t 11 > /usr/sbin/wicontrol -i wi0 -n IansWireless > /usr/sbin/wicontrol -i wi0 -c 0 -p 0 > /usr/sbin/wicontrol -i wi0 -k 0x1111111111 -v 1 > /usr/sbin/wicontrol -i wi0 -T 1 > /usr/sbin/wicontrol -i wi0 -e 1 > > Also, I have noticed some strange behavior when setting keys. If > I set the 40 bit WEP key to all 3's then do a wicontrol -i wi0 to > report the keys, it will show the key as '33333' (as in a text > string instead of hex). But that may or may not be part of this. > > Cheers, > > Ian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Sat Sep 22 19:17:56 2001 Delivered-To: freebsd-hardware@freebsd.org Received: from femail27.sdc1.sfba.home.com (femail27.sdc1.sfba.home.com [24.254.60.17]) by hub.freebsd.org (Postfix) with ESMTP id 2361D37B41D; Sat, 22 Sep 2001 19:17:44 -0700 (PDT) Received: from cx543097a ([65.13.57.165]) by femail27.sdc1.sfba.home.com (InterMail vM.4.01.03.20 201-229-121-120-20010223) with SMTP id <20010918230932.ZEWO559.femail27.sdc1.sfba.home.com@cx543097a>; Tue, 18 Sep 2001 16:09:32 -0700 From: "Ian Cartwright" To: , "FreeBSD Questions" , "FreeBSD Hardware" Subject: Problems with netgear MA401 Date: Tue, 18 Sep 2001 16:09:32 -0700 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.2911.0) X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 Importance: Normal 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 eveybody, I've posted a couple timed before with no replies. But now that 4.4-R is out maybe there is time for someone to take alook at this... I have a Netgear MA-401 that I have been unable to get woring under FreeBSD. The card works fine under Windows 2000. The card works great in FreeBSD without WEP. When I enable WEP I lose my connection. I have scoured the archives, which resulted in: update to a recent -STABLE (9/14/01), addition of a flag to pccard.conf to allow "Prism2 mode" for my card (which fixed an issue with wicontrol reporting WEP off even though ifconfig said it was on), and not much else, and moving my configuration commands from pccard.conf to start_if.wi0. I have also tried configuring straight from ifconfig with no change in results. Here is some info about my current setup: - The card works with WEP disabled - My WEP key is entered in hex - I am trying to attach to a Netgear MA-102 Access Point which only supports 40 bit hex keys - wicontrol looks like it is doing everything properly (correct keys, ssid, etc.) - ifconfig looks OK too, except "authmode" is NONE and I cannot change it to anything else Here is a copy of my start_if.wi0 #!/bin/sh /usr/sbin/wicontrol -i wi0 -t 11 /usr/sbin/wicontrol -i wi0 -n IansWireless /usr/sbin/wicontrol -i wi0 -c 0 -p 0 /usr/sbin/wicontrol -i wi0 -k 0x1111111111 -v 1 /usr/sbin/wicontrol -i wi0 -T 1 /usr/sbin/wicontrol -i wi0 -e 1 Also, I have noticed some strange behavior when setting keys. If I set the 40 bit WEP key to all 3's then do a wicontrol -i wi0 to report the keys, it will show the key as '33333' (as in a text string instead of hex). But that may or may not be part of this. Cheers, Ian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message