From owner-freebsd-hardware@FreeBSD.ORG Sun Jan 18 10:35:25 2004 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5649616A4CE for ; Sun, 18 Jan 2004 10:35:25 -0800 (PST) Received: from imf19aec.mail.bellsouth.net (imf19aec.mail.bellsouth.net [205.152.59.67]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8049143D2D for ; Sun, 18 Jan 2004 10:35:23 -0800 (PST) (envelope-from cbonzo@bellsouth.net) Received: from desktop ([65.82.174.218]) by imf19aec.mail.bellsouth.net (InterMail vM.5.01.06.05 201-253-122-130-105-20030824) with ESMTP id <20040118183522.QMKD1950.imf19aec.mail.bellsouth.net@desktop> for ; Sun, 18 Jan 2004 13:35:22 -0500 To: freebsd-hardware@freebsd.org From: Chris Bendzel Content-Type: text/plain; format=flowed; charset=iso-8859-15 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Date: Sun, 18 Jan 2004 12:35:28 -0600 Message-ID: User-Agent: Opera7.23/Win32 M2 build 3227 Subject: Sound card issue X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 18 Jan 2004 18:35:25 -0000 Hi I have recently installed FreeBSD 5.1 on a Compaq with onboard sound. WinXP identifies the card as an "ESS Allegro PCI". Compiling the kernel with the "pcm" option did not load the driver or show up in the "dmesg" output. I chose the load all sound drivers in the /boot/loader.conf file. It loaded the "maestro3" driver. This is the output of my "dmesg" file: CHRIS >}> dmesg | grep snd Preloaded elf module "/boot/kernel/snd_maestro3.ko" at 0xc04470cc. CHRIS >}> dmesg | grep pcm pcm0: port 0x1000-0x10ff irq 5 at device 5.0 on pci1 pcm0: failed to enable memory mapping! pcm0: The problem I am having is that after about 30 seconds, the sound card hangs on one note and the only way to stop it is to load another sound application. If anyone has had this problem before, Please Help. Thank you for your time in this matter. -- Using M2, Opera's revolutionary e-mail client: http://www.opera.com/m2/ From owner-freebsd-hardware@FreeBSD.ORG Mon Jan 19 03:49:37 2004 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CDBE716A4CE for ; Mon, 19 Jan 2004 03:49:37 -0800 (PST) Received: from mps3.plala.or.jp (c146240.vh.plala.or.jp [210.150.146.240]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7E26943D2F for ; Mon, 19 Jan 2004 03:49:35 -0800 (PST) (envelope-from e-kamo@trio.plala.or.jp) Received: from msvc1.plala.or.jp ([172.23.8.209]) by mps3.plala.or.jp with SMTP id <20040119114933.VZAM29247.mps3.plala.or.jp@msvc1.plala.or.jp> for ; Mon, 19 Jan 2004 20:49:33 +0900 Received: ( 23836 invoked from network); 19 Jan 2004 20:49:32 +0900 X-SVCK: Received: from unknown (HELO mpb2.plala.or.jp) (172.23.8.17) by msvc1 with SMTP; 19 Jan 2004 20:49:32 +0900 Received: from trio.plala.or.jp ([219.25.148.126]) by mpb2.plala.or.jp with ESMTP id <20040119114932.IJLW5188.mpb2.plala.or.jp@trio.plala.or.jp> for ; Mon, 19 Jan 2004 20:49:32 +0900 Message-ID: <400BC44E.5000507@trio.plala.or.jp> Date: Mon, 19 Jan 2004 20:49:34 +0900 From: Eitarou Kamo User-Agent: Mozilla/5.0 (Windows; U; Win98; ja-JP; rv:1.0.2) Gecko/20030208 Netscape/7.02 X-Accept-Language: ja MIME-Version: 1.0 To: freebsd-hardware@freebsd.org X-Enigmail-Version: 0.75.1.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=ISO-2022-JP Content-Transfer-Encoding: 7bit Subject: Tyan Tiger mpx PCI slot X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 19 Jan 2004 11:49:37 -0000 Hi, all I'm new to this list. I have some questions about Tiger MPX mother board. I would appreciate any help. Tyan Tiger MPX have 2x 64bit PCI slots and 4x 32bit PCI slots. I would like to configure a fasttrak card and 4 Giga bit Ether card on it. Is it possible physically? I'm afraid of conflict or Bus Master issue. And Is there anyone who tried it? Thanks in advance. Eitarou -- *********************** Eitarou Kamo Tel. +81 75 7035997 Fax +81 75 7035997 VoIP 050 10585997 e$B!>(Bmail e-kamo@trio.plala.or.jp PayPal e-kamo@trio.plala.or.jp GPG FingerPrint: CD46 37A9 35BF F417 0B95 03D4 24D9 3C2D FFF4 2E3A ************************************************************************ From owner-freebsd-hardware@FreeBSD.ORG Tue Jan 20 04:08:19 2004 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0812D16A4CE for ; Tue, 20 Jan 2004 04:08:19 -0800 (PST) Received: from imf20aec.mail.bellsouth.net (imf20aec.mail.bellsouth.net [205.152.59.68]) by mx1.FreeBSD.org (Postfix) with ESMTP id CA12443D31 for ; Tue, 20 Jan 2004 04:08:17 -0800 (PST) (envelope-from gilrain@lunarpolicy.net) Received: from lunarpolicy.net ([68.217.183.166]) by imf20aec.mail.bellsouth.netESMTP <20040120120817.SSCF18522.imf20aec.mail.bellsouth.net@lunarpolicy.net> for ; Tue, 20 Jan 2004 07:08:17 -0500 Message-ID: <400D1A53.1010504@lunarpolicy.net> Date: Tue, 20 Jan 2004 06:08:51 -0600 From: gilrain User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.6b) Gecko/20040119 Thunderbird/0.4 X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-hardware@freebsd.org Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Subject: Generic sound? X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 20 Jan 2004 12:08:19 -0000 Hi all, Just got my 5.2-RELEASE installation up and running. My sound card (Realtek onboard sound: ALC650) isn't supported, and from searching Google it looks like there aren't any drivers. I was wondering (hoping!) that I could still get basic functionality with some kind of generic driver. Like how my Radeon 9800Pro isn't supported, but I can still get the basics by using the "vesa" driver. Is there something like that for soundcards? Thanks, John Thile http://lunarpolicy.net From owner-freebsd-hardware@FreeBSD.ORG Tue Jan 20 04:18:24 2004 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D21EC16A4CE; Tue, 20 Jan 2004 04:18:24 -0800 (PST) Received: from jawa.at (jawa.at [213.229.17.146]) by mx1.FreeBSD.org (Postfix) with ESMTP id 684D343D39; Tue, 20 Jan 2004 04:18:23 -0800 (PST) (envelope-from michael.hollmann@jawa.at) Received: from jawa.at (holly.jawa.at [192.168.200.62]) by jawa.at (8.12.9p2/8.12.8) with ESMTP id i0KCILcj055353; Tue, 20 Jan 2004 13:18:21 +0100 (CET) (envelope-from michael.hollmann@jawa.at) Message-ID: <400D1CA7.8050304@jawa.at> Date: Tue, 20 Jan 2004 13:18:47 +0100 From: Michael Hollmann User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; de-DE; rv:1.0.2) Gecko/20030208 Netscape/7.02 X-Accept-Language: de-de, de MIME-Version: 1.0 To: mobile@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit X-Virus-Scanned: by amavisd-new cc: hardware@freebsd.org Subject: cardbus activation failed X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 20 Jan 2004 12:18:25 -0000 hi i am running FreeBSD 5.2 Release #0 on my laptop. my wlan card is "netgear WG512 Cardbus 32bit". i have no troubles to run this card under windows 2000 prof. but on FreeBSD 5.2 i get "cardbus activation failed". should this be fixed now ??? any ideas? thank´s michael From owner-freebsd-hardware@FreeBSD.ORG Tue Jan 20 08:16:33 2004 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3272C16A4CE; Tue, 20 Jan 2004 08:16:33 -0800 (PST) Received: from panzer.kdm.org (panzer.kdm.org [216.160.178.169]) by mx1.FreeBSD.org (Postfix) with ESMTP id A997E43D64; Tue, 20 Jan 2004 08:16:31 -0800 (PST) (envelope-from ken@panzer.kdm.org) Received: from panzer.kdm.org (localhost [127.0.0.1]) by panzer.kdm.org (8.12.9/8.12.5) with ESMTP id i0KGGV64013210; Tue, 20 Jan 2004 09:16:31 -0700 (MST) (envelope-from ken@panzer.kdm.org) Received: (from ken@localhost) by panzer.kdm.org (8.12.9/8.12.5/Submit) id i0KGGUiE013206; Tue, 20 Jan 2004 09:16:30 -0700 (MST) (envelope-from ken) Date: Tue, 20 Jan 2004 09:16:30 -0700 From: "Kenneth D. Merry" To: Michael Hollmann Message-ID: <20040120161630.GA13178@panzer.kdm.org> References: <400D1CA7.8050304@jawa.at> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <400D1CA7.8050304@jawa.at> User-Agent: Mutt/1.4.1i cc: mobile@freebsd.org cc: hardware@freebsd.org Subject: Re: cardbus activation failed X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 20 Jan 2004 16:16:33 -0000 On Tue, Jan 20, 2004 at 13:18:47 +0100, Michael Hollmann wrote: > hi > > > i am running FreeBSD 5.2 Release #0 on my laptop. my wlan card is > "netgear WG512 Cardbus 32bit". i have no troubles to run this card under > windows 2000 prof. but on FreeBSD 5.2 i get "cardbus activation failed". > > should this be fixed now ??? You haven't mentioned what kind of laptop you have. With my Dell Inspiron 8500, I can get things to work if I pull the card out and re-insert it. It's just that the onboard ethernet then blows up if it is enabled. Ken -- Kenneth Merry ken@kdm.org From owner-freebsd-hardware@FreeBSD.ORG Tue Jan 20 08:22:44 2004 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CABFB16A4CE; Tue, 20 Jan 2004 08:22:44 -0800 (PST) Received: from otter3.centtech.com (moat3.centtech.com [207.200.51.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id F31A543D76; Tue, 20 Jan 2004 08:22:23 -0800 (PST) (envelope-from anderson@centtech.com) Received: from centtech.com (neutrino.centtech.com [10.177.171.220]) by otter3.centtech.com (8.12.3/8.12.3) with ESMTP id i0KGMN6T008310; Tue, 20 Jan 2004 10:22:23 -0600 (CST) (envelope-from anderson@centtech.com) Message-ID: <400D55A5.4040804@centtech.com> Date: Tue, 20 Jan 2004 10:21:57 -0600 From: Eric Anderson User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4) Gecko/20030624 Netscape/7.1 X-Accept-Language: en-us, en MIME-Version: 1.0 To: "Kenneth D. Merry" References: <400D1CA7.8050304@jawa.at> <20040120161630.GA13178@panzer.kdm.org> In-Reply-To: <20040120161630.GA13178@panzer.kdm.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit cc: Michael Hollmann cc: mobile@freebsd.org cc: hardware@freebsd.org Subject: Re: cardbus activation failed X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 20 Jan 2004 16:22:44 -0000 Kenneth D. Merry wrote: >On Tue, Jan 20, 2004 at 13:18:47 +0100, Michael Hollmann wrote: > > >>hi >> >> >>i am running FreeBSD 5.2 Release #0 on my laptop. my wlan card is >>"netgear WG512 Cardbus 32bit". i have no troubles to run this card under >>windows 2000 prof. but on FreeBSD 5.2 i get "cardbus activation failed". >> >>should this be fixed now ??? >> >> > >You haven't mentioned what kind of laptop you have. > >With my Dell Inspiron 8500, I can get things to work if I pull the card out >and re-insert it. > >It's just that the onboard ethernet then blows up if it is enabled. > > Same here with a Latitude D600 - I have a bge (broadcom) gig-e onboard. Any cardbus card inserted hoses it all up, and FreeBSD thinks I have two bge cards installed, and things go downhill from there. I think M. Warner Losh said he had some patches for this, but was waiting to commit or was waiting for time at least.. Eric -- ------------------------------------------------------------------ Eric Anderson Systems Administrator Centaur Technology All generalizations are false, including this one. ------------------------------------------------------------------ From owner-freebsd-hardware@FreeBSD.ORG Tue Jan 20 08:30:09 2004 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E2E8016A4CE; Tue, 20 Jan 2004 08:30:09 -0800 (PST) Received: from jawa.at (jawa.at [213.229.17.146]) by mx1.FreeBSD.org (Postfix) with ESMTP id 00E2B43D5C; Tue, 20 Jan 2004 08:30:08 -0800 (PST) (envelope-from michael.hollmann@jawa.at) Received: from jawa.at (holly.jawa.at [192.168.200.62]) by jawa.at (8.12.9p2/8.12.8) with ESMTP id i0KGU3cj074490; Tue, 20 Jan 2004 17:30:03 +0100 (CET) (envelope-from michael.hollmann@jawa.at) Message-ID: <400D57A4.5060805@jawa.at> Date: Tue, 20 Jan 2004 17:30:28 +0100 From: Michael Hollmann User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; de-DE; rv:1.0.2) Gecko/20030208 Netscape/7.02 X-Accept-Language: de-de, de MIME-Version: 1.0 To: Eric Anderson References: <400D1CA7.8050304@jawa.at> <20040120161630.GA13178@panzer.kdm.org> <400D55A5.4040804@centtech.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit X-Virus-Scanned: by amavisd-new cc: mobile@freebsd.org cc: hardware@freebsd.org Subject: Re: cardbus activation failed X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 20 Jan 2004 16:30:10 -0000 thanks, my laptop is a toshiba satellite-z20, i did run freebsd from 5.0 to 5.2 now. i have not any troubles until now, only my wlan card. i think i try to change the card to "WG511T" if it is possible. thank´s for your help michael Eric Anderson schrieb: > Kenneth D. Merry wrote: > >> On Tue, Jan 20, 2004 at 13:18:47 +0100, Michael Hollmann wrote: >> >> >>> hi >>> >>> >>> i am running FreeBSD 5.2 Release #0 on my laptop. my wlan card is >>> "netgear WG512 Cardbus 32bit". i have no troubles to run this card >>> under windows 2000 prof. but on FreeBSD 5.2 i get "cardbus activation >>> failed". >>> >>> should this be fixed now ??? >>> >> >> >> You haven't mentioned what kind of laptop you have. >> >> With my Dell Inspiron 8500, I can get things to work if I pull the >> card out >> and re-insert it. >> >> It's just that the onboard ethernet then blows up if it is enabled. >> >> > Same here with a Latitude D600 - I have a bge (broadcom) gig-e onboard. > Any cardbus card inserted hoses it all up, and FreeBSD thinks I have two > bge cards installed, and things go downhill from there. I think M. > Warner Losh said he had some patches for this, but was waiting to commit > or was waiting for time at least.. > > Eric > > -- Mit freundlichen Grüßen Michael Hollmann JAWA Management Software GmbH A-8041 Graz, Liebenauer Hauptstraße 200 Tel: ++43 (0)316 403274-13 Fax: ++43 (0)316 403274-10 GSM: ++43 (0)676 4101431 E-Mail: michael.hollmann@jawa.at Web: http://www.jawa.at/ News: http://www.jawa.at/news.php/ "Web-Framework für B2B-Applikationen" From owner-freebsd-hardware@FreeBSD.ORG Tue Jan 20 08:47:15 2004 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0B66116A4CE for ; Tue, 20 Jan 2004 08:47:15 -0800 (PST) Received: from mxfep01.bredband.com (mxfep01.bredband.com [195.54.107.70]) by mx1.FreeBSD.org (Postfix) with ESMTP id F055643D91 for ; Tue, 20 Jan 2004 08:46:15 -0800 (PST) (envelope-from mathias.nospam@haas.se) Received: from haas.se ([213.114.148.49] [213.114.148.49]) by mxfep01.bredband.com with SMTP id <20040120164606.CEDX9038.mxfep01.bredband.com@haas.se> for ; Tue, 20 Jan 2004 17:46:06 +0100 Received: (qmail 45369 invoked from network); 20 Jan 2004 16:49:32 -0000 Received: from mathias.nospam@haas.se by p3-550.haas.se by uid 82 with qmail-scanner-1.20 (spamassassin: 2.61. Clear:RC:1(127.0.0.1):. Processed: 49:32 -0000 Received: from localhost.haas.se (HELO mail.haas.se) (127.0.0.1) by: 49:32 -0000 Received: from 193.14.163.194 (SquirrelMail authenticated user mathias@haas.se) by mail.haas.se with HTTP; Tue,: 49:32 +0100 (CET) Message-ID: <50999.193.14.163.194.1074617372.squirrel@mail.haas.se> Date: Tue, 20 Jan 2004 17:49:32 +0100 (CET) From: mathias.nospam@haas.se To: hardware@freebsd.org User-Agent: SquirrelMail/1.4.2 MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 Importance: Normal Subject: Urgent: Problems with 3ware RAID controller X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 20 Jan 2004 16:47:15 -0000 Hello! Short version: We're having problems with a 3ware 8506-4 RAID controller and having rather severe problems. Has anyone tried the FreeBSD 4.8 drivers from 3ware on FreeBSD 5.2? 3ware say on their website that they "may or may not work"... Long version: We're running the controller under FreeBSD 5.2 (Release) on an ASUS P4S8X motherboard. We're having two different problems: 1) When booting BSD hangs when initilizing the 3Ware controller driver. Previously it almost never happend, now it hangs almost every time. These are the last two lines before it freezes: 3ware 7000 series Storage Controller. Driver version 1.50.00.000> port 0x8400-0x840f mem 0xe4000000-0xe47fffff,0xe4800000-0xe480000f irq 10 at device 9.0 on pci0 We have not installed any other drivers than the ones supplied with FreeBSD 5.2. I noticed that it says "7000-series" - Is this really as it should be? 2) At shutdown, the OS complains about not being able to delete the device 0 and then hangs. Sometimes (maybe every second time) it reboots or shutdowns okay. Have you seen any of these errors before? We're just taking this server into production so we are a bit worried that it will fail miserably and die on us... I'd be very grateful for all answers! Kind regards, Mathias Haas From owner-freebsd-hardware@FreeBSD.ORG Tue Jan 20 11:15:10 2004 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8AD2B16A4CF for ; Tue, 20 Jan 2004 11:15:10 -0800 (PST) Received: from ns1.microbsd.net (rrcs-se-24-227-64-10.biz.rr.com [24.227.64.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5A95943D58 for ; Tue, 20 Jan 2004 11:15:06 -0800 (PST) (envelope-from dingo@microbsd.net) Received: from webmail.isosweb.com (localhost.isosweb.com [127.0.0.1]) by ns1.microbsd.net (Postfix) with SMTP id D8A1835D4A6; Tue, 20 Jan 2004 14:14:46 -0500 (EST) Received: from 12.6.138.178 (SquirrelMail authenticated user dingo@microbsd.net) by webmail.isosweb.com with HTTP; Tue, 20 Jan 2004 14:14:46 -0500 (EST) Message-ID: <62824.12.6.138.178.1074626086.squirrel@webmail.isosweb.com> In-Reply-To: <400D57A4.5060805@jawa.at> References: <400D1CA7.8050304@jawa.at> <20040120161630.GA13178@panzer.kdm.org><400D55A5.4040804@centtech.com> <400D57A4.5060805@jawa.at> Date: Tue, 20 Jan 2004 14:14:46 -0500 (EST) From: dingo@microbsd.net To: "Michael Hollmann" User-Agent: SquirrelMail/1.4.2 MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 Importance: Normal cc: Eric Anderson cc: hardware@freebsd.org Subject: Re: cardbus activation failed X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 20 Jan 2004 19:15:10 -0000 Okay i will re-iterate what i said a week or so ago, as of 5.2-RELEASEit seems there have been alot of cardbus issues, i myself have a Sony VAIO PCG-GRX560 that never had issues with wireless devices or cardbus util i upgraded to FreeBSD 5.2 Release. then all pcmcia items stopped functioning. Ive downgraded to a 5.2-current cvs snapshot dated January8, 2004 and all works fine again. It seems something changed for cardbus between January 8th and January 15th. It is most likely a pcmcia carddevice having the issue, it seems to be directly related to the FreeBSD code dated after January 9-10th 2004. My cardbus works with the January 8th current cvs snpshot. > thanks, > > my laptop is a toshiba satellite-z20, i did run freebsd from 5.0 to 5.2 > now. i have not any troubles until now, only my wlan card. > > i think i try to change the card to "WG511T" if it is possible. > > thank´s for your help > > michael From owner-freebsd-hardware@FreeBSD.ORG Tue Jan 20 12:24:40 2004 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 215B616A4EC for ; Tue, 20 Jan 2004 12:24:40 -0800 (PST) Received: from rdsnet.ro (smtp.rdsnet.ro [62.231.74.130]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6BAFC43D64 for ; Tue, 20 Jan 2004 12:24:37 -0800 (PST) (envelope-from itetcu@apropo.ro) Received: (qmail 19113 invoked from network); 20 Jan 2004 20:24:35 -0000 Received: from unknown (HELO it.buh.cameradicommercio.ro) (81.196.25.19) by mail.rdsnet.ro with SMTP; 20 Jan 2004 20:24:35 -0000 Date: Tue, 20 Jan 2004 22:26:02 +0200 From: Ion-Mihai Tetcu To: gilrain Message-Id: <20040120222602.04ee8560@it.buh.cameradicommercio.ro> In-Reply-To: <400D1A53.1010504@lunarpolicy.net> References: <400D1A53.1010504@lunarpolicy.net> X-Mailer: Sylpheed version 0.9.8claws (GTK+ 1.2.10; i386-portbld-freebsd5.2) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit cc: freebsd-hardware@freebsd.org Subject: Re: Generic sound? X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 20 Jan 2004 20:24:40 -0000 On Tue, 20 Jan 2004 06:08:51 -0600 gilrain wrote: > Hi all, > > Just got my 5.2-RELEASE installation up and running. My sound card > (Realtek onboard sound: ALC650) isn't supported, and from searching > Google it looks like there aren't any drivers. > > I was wondering (hoping!) that I could still get basic functionality > with some kind of generic driver. Like how my Radeon 9800Pro isn't > supported, but I can still get the basics by using the "vesa" driver. Is > there something like that for soundcards? Well, what cipset does your card have ? I have a Gigabyte GA-7VT600L KT600/8237 with ALC655 and I'm using: itetcu@it> /root/bin [22:17:25] 0 # kldstat | grep snd 2 1 0xc09e0000 5d2c snd_via8233.ko 3 2 0xc09e6000 1e58c snd_pcm.ko which work usually ok without vchans at least for playback (I haven't tried anything else). itetcu@it> /root/bin [22:17:52] 1 # sysctl hw.snd hw.snd.targetirqrate: 32 hw.snd.report_soft_formats: 1 hw.snd.verbose: 1 hw.snd.unit: 0 hw.snd.maxautovchans: 0 hw.snd.pcm0.buffersize: 4096 hw.snd.pcm0.vchans: 0 hw.snd.pcm0.spdif_enabled: 0 itetcu@it> /root/bin [22:18:53] 1 # pciconf -vl | grep -A4 pcm pcm0@pci0:17:5: class=0x040100 card=0xa0021458 chip=0x30591106 rev=0x60 hdr=0x00 vendor = 'VIA Technologies Inc' device = 'VT8233/33A AC97 Enhanced Audio Controller' class = multimedia subclass = audio itetcu@it> /root/bin [22:24:10] 0 # cat /dev/sndstat FreeBSD Audio Driver (newpcm) Installed devices: pcm0: at io 0xe400 irq 22 (5p/1r/0v channels duplex default) -- IOnut Unregistered ;) FreeBSD user From owner-freebsd-hardware@FreeBSD.ORG Tue Jan 20 12:42:20 2004 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AB2D816A4D8 for ; Tue, 20 Jan 2004 12:42:20 -0800 (PST) Received: from imf16aec.mail.bellsouth.net (imf16aec.mail.bellsouth.net [205.152.59.64]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8FB2C43D94 for ; Tue, 20 Jan 2004 12:41:56 -0800 (PST) (envelope-from gilrain@lunarpolicy.net) Received: from lunarpolicy.net ([68.217.183.166]) by imf16aec.mail.bellsouth.netESMTP <20040120204156.CESW1899.imf16aec.mail.bellsouth.net@lunarpolicy.net>; Tue, 20 Jan 2004 15:41:56 -0500 Message-ID: <400D92B3.7070208@lunarpolicy.net> Date: Tue, 20 Jan 2004 14:42:27 -0600 From: gilrain User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.6b) Gecko/20040119 Thunderbird/0.4 X-Accept-Language: en-us, en MIME-Version: 1.0 To: David Raistrick References: <400D1A53.1010504@lunarpolicy.net> In-Reply-To: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-hardware@freebsd.org Subject: Re: Generic sound? X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 20 Jan 2004 20:42:20 -0000 Hello, David Raistrick wrote: > To load /all/ sound drivers in a running system (to may need to cd > /usr/src/sys/modules/sound/pcm and make install to install the > modules...my 5.2-rc2 install didn't appear to install any kld modules but > I might have missed something.) just: > > kldload snd_driver > > and that'll load /all/ of the sound modules, and should find yours. You're a life saver! That worked perfectly, and now I'm happily listening to my music library in XMMS. Thanks a bunch, John Thile From owner-freebsd-hardware@FreeBSD.ORG Tue Jan 20 20:42:25 2004 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2C42616A4CE for ; Tue, 20 Jan 2004 20:42:25 -0800 (PST) Received: from dexter.starfire.mn.org (starfire.skypoint.net [199.199.159.71]) by mx1.FreeBSD.org (Postfix) with ESMTP id 13C8443D41 for ; Tue, 20 Jan 2004 20:42:14 -0800 (PST) (envelope-from john@dexter.starfire.mn.org) Received: (from john@localhost) by dexter.starfire.mn.org (8.11.3/8.11.3) id i0L4fwU35061 for freebsd-hardware@freebsd.org; Tue, 20 Jan 2004 22:41:58 -0600 (CST) (envelope-from john) Date: Tue, 20 Jan 2004 22:41:58 -0600 From: John To: freebsd-hardware@freebsd.org Message-ID: <20040120224158.C34876@starfire.mn.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i Subject: RealTek 8139D chipset, the re(4) driver, and FreeBSD 4.9 X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 21 Jan 2004 04:42:25 -0000 This is going to be a bit convoluted. I was shopping for an efficient, fast 100baseTX PCI controller, and inexpensive would be really nice, too! I came across the re(4) driver for certain RealTek chipsets. It specified RealTek 8139C+ (among others). This is in contrast to the 8139 (no suffix, A, or B) chipsets handled by the rl(4) driver, which sounds like the chips are real dogs. Anyway, the re(4) driver made cards based on these chips sound GREAT! Here's the first catch - THE WEB PAGE FOOTER SAYS "FreeBSD 4.9!" I came to the conclusion, which I thought was reasonable, that even though it said the driver first appeared in FreeBSD 5.2, that it was also available under 4.9.... I didn't feel like I was making a dangerous assumption, but now it looks otherwise. So, when I found a card with 8139D chips for $9.95, I took a chance. Afterall, I got an 8-port N-WAY auto-sensing switch with automatic MDI/MDIX sensing for $19.95 from the same place, so, the price seemed plausible, and I bought it! Now it's time to generate a 4.9-STABLE kernel - but there's no "device re" in GENERIC or LINT.... so I looked up the 4.9 hardware release notes from the web site - and it's not there! So - I'm afraid that the page I was looking at was formatted with the wrong macros, and there is no such thing as a "re" driver for 4.9-STABLE. If that's the case - I'd like to respectfully suggest that the page be reformatted with the correct macros lest someone else, like myself, get to it via a search rather than flat links and come to the wrong conclusion... Speaking of wrong conclusions, I thought of simply loading the "rl" driver and seeing if it recognized the card, thinking that would mean it was the "wrong" chipset, but then I thought that since the model numbers are so similar, it may simply mean that the functionality that was broken in the earlier chipsets may simply be fixed now, and that the "rl" driver might recognize and use the card, though with the mbuf copies that are what I was trying to avoid in the first place, and lead me to an incorrect decision on the card. It might be that the "re" driver needs to look for the card first, to recognize higher-function chipsets... So - how much of a chore is it to port ethernet drivers from 5.2 to 4.9??? Any guides or best practices for this? I mean, it sounds like a GREAT chipset, and I'd hate for everyone who will stay with 4.x for awhile to not be able to use it. I know there's a lot in here - how to interpret descriptions of chipsets, formatting of manual pages, porting of drivers, but I hope someone can help me sort this all out. Help? -- John Lind john@starfire.MN.ORG From owner-freebsd-hardware@FreeBSD.ORG Wed Jan 21 07:11:05 2004 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A4B1916A4CE for ; Wed, 21 Jan 2004 07:11:05 -0800 (PST) Received: from shellma.zin.lublin.pl (shellma.zin.lublin.pl [212.182.126.68]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2646843D69 for ; Wed, 21 Jan 2004 07:10:52 -0800 (PST) (envelope-from pawmal-posting@freebsd.lublin.pl) Received: by shellma.zin.lublin.pl (Postfix, from userid 1018) id D1A985F103; Wed, 21 Jan 2004 16:11:16 +0100 (CET) Date: Wed, 21 Jan 2004 16:11:16 +0100 From: Pawel Malachowski To: freebsd-hardware@freebsd.org Message-ID: <20040121151116.GE62180@shellma.zin.lublin.pl> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-2 Content-Disposition: inline Content-Transfer-Encoding: 8bit User-Agent: Mutt/1.4.1i Subject: SuperMicro i875 P4SCE-O question X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 21 Jan 2004 15:11:05 -0000 Hello, I'm looking for someone who is using FreeBSD 4.x (not 5.x) on Super Micro i875P P4SCE-O motherboard [1]. I'm especially interested in stability of driver for dual-gigabit NIC (because I heared that more-than-one modern gigabit onboard NICs can cause problems with some drivers), hardware monitoring (CPU temp. and cooler r.p.m. via helathd, mbmon or similar). Less intersted in SATA, I have external PCI SCSI Controller). [1] http://www.supermicro.com/PRODUCT/MotherBoards/875/P4SCE.htm cheers, -- Pawe³ Ma³achowski From owner-freebsd-hardware@FreeBSD.ORG Wed Jan 21 08:11:33 2004 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2F44B16A4D0; Wed, 21 Jan 2004 08:11:33 -0800 (PST) Received: from TheWorld.com (pcls4-e.std.com [192.74.137.144]) by mx1.FreeBSD.org (Postfix) with ESMTP id 256D143D2F; Wed, 21 Jan 2004 08:11:32 -0800 (PST) (envelope-from kwc@shell.TheWorld.com) Received: from shell.TheWorld.com (pip1-5.std.com [192.74.137.185]) by TheWorld.com (8.12.8p1/8.12.8) with ESMTP id i0LGBUiW000912; Wed, 21 Jan 2004 11:11:30 -0500 Received: (from kwc@localhost) by shell.TheWorld.com (8.9.3/8.9.3) id LAA16954677; Wed, 21 Jan 2004 11:11:25 -0500 (EST) Date: Wed, 21 Jan 2004 11:11:25 -0500 (EST) From: Kenneth W Cochran Message-Id: <200401211611.LAA16954677@shell.TheWorld.com> To: freebsd-hardware@freebsd.org, freebsd-net@freebsd.org Subject: Troubleshooting network card/link X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 21 Jan 2004 16:11:33 -0000 Hello: Is there anything for FreeBSD that's analogous to Linux's "mii-diag" program? I'm (still) trying to troubleshoot a card's (mis)communication with a router. For background, see http://docs.freebsd.org/cgi/mid.cgi?200401120237.VAA15119655 Thanks, -kc From owner-freebsd-hardware@FreeBSD.ORG Wed Jan 21 09:28:14 2004 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A9F1F16A4CE for ; Wed, 21 Jan 2004 09:28:14 -0800 (PST) Received: from fed1mtao07.cox.net (fed1mtao07.cox.net [68.6.19.124]) by mx1.FreeBSD.org (Postfix) with ESMTP id E9A0743D39 for ; Wed, 21 Jan 2004 09:28:12 -0800 (PST) (envelope-from av730@osfn.org) Received: from osfn.org ([68.0.145.83]) by fed1mtao07.cox.net (InterMail vM.5.01.06.05 201-253-122-130-105-20030824) with ESMTP id <20040121172810.LNY17405.fed1mtao07.cox.net@osfn.org> for ; Wed, 21 Jan 2004 12:28:10 -0500 From: Cretog Vesuvius To: freebsd-hardware@freebsd.org Date: Wed, 21 Jan 2004 10:27:16 -0700 User-Agent: KMail/1.5.2 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200401211027.16498.av730@osfn.org> Subject: ICS PHY driver? X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 21 Jan 2004 17:28:14 -0000 Hello, I was wondering if there are any plans to add the mii/icsphy driver to FreeBSD. My motherboard has a builtin ICS1893 and i'd like to use it, rather than this PCI card that's giving me a lot of trouble. The driver seems to exist in NetBSD and OpenBSD. Thanks! From owner-freebsd-hardware@FreeBSD.ORG Wed Jan 21 18:55:05 2004 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C4D3416A4CE for ; Wed, 21 Jan 2004 18:55:05 -0800 (PST) Received: from smtp015.mail.yahoo.com (smtp015.mail.yahoo.com [216.136.173.59]) by mx1.FreeBSD.org (Postfix) with SMTP id F28F543D1D for ; Wed, 21 Jan 2004 18:55:04 -0800 (PST) (envelope-from q_dolan@yahoo.com.au) Received: from unknown (HELO ?172.22.1.10?) (q?dolan@203.10.89.16 with plain) by smtp015.mail.yahoo.com with SMTP; 22 Jan 2004 02:55:04 -0000 From: Q To: Cretog Vesuvius In-Reply-To: <200401211027.16498.av730@osfn.org> References: <200401211027.16498.av730@osfn.org> Content-Type: text/plain Message-Id: <1074740089.40910.6.camel@boxster> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.5 Date: Thu, 22 Jan 2004 12:54:49 +1000 Content-Transfer-Encoding: 7bit cc: freebsd-hardware@freebsd.org Subject: Re: ICS PHY driver? X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 22 Jan 2004 02:55:05 -0000 On Thu, 2004-01-22 at 03:27, Cretog Vesuvius wrote: > Hello, > I was wondering if there are any plans to add the mii/icsphy > driver to FreeBSD. My motherboard has a builtin ICS1893 > and i'd like to use it, rather than this PCI card that's giving > me a lot of trouble. The driver seems to exist in NetBSD and > OpenBSD. Thanks! What motherboard is it exactly? -- Seeya...Q -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- _____ / Quinton Dolan q_dolan@yahoo.com.au __ __/ / / __/ / / / __ / _/ / / Gold Coast, QLD, Australia __/ __/ __/ ____/ / - / Ph: +61 419 729 806 _______ / _\ From owner-freebsd-hardware@FreeBSD.ORG Thu Jan 22 09:41:18 2004 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 618) id AE3D016A4CF; Thu, 22 Jan 2004 09:41:18 -0800 (PST) In-Reply-To: <200401211027.16498.av730@osfn.org> from Cretog Vesuvius at "Jan 21, 2004 10:27:16 am" To: av730@osfn.org (Cretog Vesuvius) Date: Thu, 22 Jan 2004 09:41:18 -0800 (PST) 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: <20040122174118.AE3D016A4CF@hub.freebsd.org> From: wpaul@FreeBSD.ORG (Bill Paul) cc: freebsd-hardware@freebsd.org Subject: Re: ICS PHY driver? X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 22 Jan 2004 17:41:18 -0000 > Hello, > I was wondering if there are any plans to add the mii/icsphy > driver to FreeBSD. My motherboard has a builtin ICS1893 > and i'd like to use it, rather than this PCI card that's giving > me a lot of trouble. The driver seems to exist in NetBSD and > OpenBSD. Thanks! > You have come to the erroneous conclusion that a PHY chip is equivalent to an ethernet card. The PHY is just one component. The important part is the MAC chip. However you have failed to tell us just what motherboard you have, so lacking further information, there's no way anyone can help you. -Bill -- ============================================================================= -Bill Paul (510) 749-2329 | Senior Engineer, Master of Unix-Fu wpaul@windriver.com | Wind River Systems ============================================================================= you're just BEGGING to face the moose ============================================================================= From owner-freebsd-hardware@FreeBSD.ORG Thu Jan 22 10:31:21 2004 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 618) id 6A09016A4CF; Thu, 22 Jan 2004 10:31:21 -0800 (PST) In-Reply-To: <20040120224158.C34876@starfire.mn.org> from John at "Jan 20, 2004 10:41:58 pm" To: john@starfire.mn.org (John) Date: Thu, 22 Jan 2004 10:31:21 -0800 (PST) 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: <20040122183121.6A09016A4CF@hub.freebsd.org> From: wpaul@FreeBSD.ORG (Bill Paul) cc: freebsd-hardware@freebsd.org Subject: Re: RealTek 8139D chipset, the re(4) driver, and FreeBSD 4.9 X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 22 Jan 2004 18:31:21 -0000 > This is going to be a bit convoluted. [...] This is _not_ going to be convoluted. The man page for the re(4) driver says it supports the 8139C+ chip. Not the 8139. Not the 8139A. Not the 8139B. Not the 8139C. And not the 8139D either. You have come to the erroneous conclusion that the 8139D has the same features as the 8139C+ just because it looks like it's a newer chip rev. The manual page tells you _EXACTLY_ what chips it supports: - The 8139C+ 10/100 chip - The 8169 10/100/1000 chip (MAC only, obsoleted by 8169S) - The 8169S 10/100/1000 chip (MAC + PHY, single chip) - The 8110S 10/100/1000 chip (MAC + PHY, single chip, Lan On Motherboard) That's ALL. Do you see "8139D" anywhere in that list? No, you don't. The 8139C+ is the _ONLY_ special RealTek 10/100 chip. The 8139D came out later, but it's still yet another rehash of the older 8139 design. I repeat: _ONLY_ the C+ revision is special. All the other 10/100 chips in RealTek's product line are equally sucky. Got it now? The 8139D card you bought is just as brain damaged as all its earlier bretheren. It will work with the rl(4) driver in 4.9. (As a matter of fact, the 8139C+ will work with the rl(4) driver too, since it's backward compatible. But it will perform just like the older chips then.) You are not going to find an 8139C+ NIC anywhere in the U.S. market, except built into some higher end Compaq laptops. None of the ethernet card makers bought the 8139C+ chip, because it costs about a dollar more than all of the other 8139 parts. Why wouldn't they spend the extra buck for all those added featuers and performance? Because they know that cheap bastard consumers like you wouldn't buy it. Everyone makes such grand claims about how they want to buy only quality hardware, but then you go to the local computer store and what do you buy? The cheapest thing you can find. The board makers know this, so they cater to your idiotic whims by selling you the cheapest thing _they_ can find. And RealTek decided to corner the market by making the cheapest chip possible so they'd always be the board makers' first choice. If the board makers had bought the 8139C+ chip and C+ NICs had turned up on the shelves for $15 next to the other 8139-based boards selling for $10, would you have bought the 8139C+ card? No. You would have looked at the price tags first, and convinced yourself that since they both say "8139" on them, it should be ok to buy the cheaper one, just like you tried to convince yourself that the 8139D was as good as the 8139C+. Because RealTek had already saturated the 10/100 market with the 8139, they didn't bother to push the 8139C+ very hard when they noticed the board makers weren't interested in it. Instead, they're going to try to do to the 10/100/1000 market what they did to the 10/100 market, by pushing the 8169S and 8110S gigE chips. These chips are vastly less sucky than the older 8139 chips (they have one drawback: jumbo frame support is very bad) so for once they may not be shafting consumers quite so badly. I have not seem them turning up in too many places yet though. There are some Asus motherboards that have the 8110S gigE chip. RealTek stated to me that they wanted to see gigE cards on the market selling for $15. I'm still waiting to see if this happens. Anyway. The reason the re(4) driver isn't in FreeBSD 4.9 is that I didn't finish working on it until after 4.9 had gone into code freeze, and unlike some developers, I believe in following the rule that says that "code freeze" means "feature-complete". I did, however, port the re(4) driver to 4-stable. You can get it here: http://www.freebsd.org/~wpaul/RealTek/4-stable/re.tar.gz As for the manual page: the HISTORY section says the driver first appeared in FreeBSD 5.x. It's telling you the truth. The fact that the page was formatted on a 4.9 box before being displayed to you is unfortunate, but all you had to do to figure out whether the driver was in 4.9 or not was to read the release notes. If it wasn't mentioned, it wasn't there. -Bill -- ============================================================================= -Bill Paul (510) 749-2329 | Senior Engineer, Master of Unix-Fu wpaul@windriver.com | Wind River Systems ============================================================================= you're just BEGGING to face the moose ============================================================================= From owner-freebsd-hardware@FreeBSD.ORG Thu Jan 22 12:30:33 2004 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E370916A4CE; Thu, 22 Jan 2004 12:30:33 -0800 (PST) Received: from fed1mtao03.cox.net (fed1mtao03.cox.net [68.6.19.242]) by mx1.FreeBSD.org (Postfix) with ESMTP id 09B1343D2F; Thu, 22 Jan 2004 12:30:32 -0800 (PST) (envelope-from av730@osfn.org) Received: from ip68-0-151-124.tc.ph.cox.net ([68.0.151.124]) by fed1mtao03.cox.netESMTP <20040122203023.YCYU28419.fed1mtao03.cox.net@ip68-0-151-124.tc.ph.cox.net>; Thu, 22 Jan 2004 15:30:23 -0500 From: Sean O'Neill To: wpaul@freebsd.org (Bill Paul) Date: Thu, 22 Jan 2004 13:25:33 -0700 User-Agent: KMail/1.5.2 References: <20040122174118.AE3D016A4CF@hub.freebsd.org> In-Reply-To: <20040122174118.AE3D016A4CF@hub.freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200401221325.33444.av730@osfn.org> cc: freebsd-hardware@freebsd.org Subject: Re: ICS PHY driver? X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 22 Jan 2004 20:30:34 -0000 On Thursday 22 January 2004 10:41, Bill Paul wrote: > > Hello, > > I was wondering if there are any plans to add the mii/icsphy > > driver to FreeBSD. My motherboard has a builtin ICS1893 > > and i'd like to use it, rather than this PCI card that's giving > > me a lot of trouble. The driver seems to exist in NetBSD and > > OpenBSD. Thanks! > > You have come to the erroneous conclusion that a PHY chip is > equivalent to an ethernet card. The PHY is just one component. > The important part is the MAC chip. However you have failed to > tell us just what motherboard you have, so lacking further > information, there's no way anyone can help you. > > -Bill > I have an MSI K7n2-Delta board with the nForce2 chipset, and finally last night I learned about the nvnet package- now it's working fine, sorry about that. From owner-freebsd-hardware@FreeBSD.ORG Fri Jan 23 09:35:57 2004 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2A58E16A4CE for ; Fri, 23 Jan 2004 09:35:57 -0800 (PST) Received: from vir1.relay.fluke.com (vir1.relay.fluke.com [129.196.184.25]) by mx1.FreeBSD.org (Postfix) with ESMTP id E1FAF43D3F for ; Fri, 23 Jan 2004 09:35:55 -0800 (PST) (envelope-from paul.lutt@fluke.com) Received: from sarguy.tc.fluke.com ([129.196.165.251] RDNS failed) by vir1.relay.fluke.com with Microsoft SMTPSVC(5.0.2195.5329); Fri, 23 Jan 2004 09:35:49 -0800 Received: from paul (helo=localhost) by sarguy.tc.fluke.com with local-esmtp (Exim 3.36 #1 (Debian)) id 1Ak5Dh-0000t1-00; Fri, 23 Jan 2004 09:35:49 -0800 Date: Fri, 23 Jan 2004 09:35:49 -0800 (PST) From: Paul Lutt X-X-Sender: paul@sarguy.na.flukecorp.com To: freebsd-hardware@freebsd.org Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-OriginalArrivalTime: 23 Jan 2004 17:35:49.0567 (UTC) FILETIME=[57514CF0:01C3E1D7] Subject: HP DL360 G3 Hangs on Disk Removal X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 23 Jan 2004 17:35:57 -0000 I have been evaluating FreeBSD Release-5.2 on an HP DL360 G3 for possible deployment on several new servers. Everything was looking good until I tried pulling a disk drive from the RAID 1 pair while the system was running. I wanted to verify that it would continue on gracefully. What I got was a system that wasn't totally locked up, but it could not perform any disk access. I had a shell open on the console. Pressing enter would bring up a new prompt. Trying to do anything that required reading the disk would cause the shell to hang. I could go to another console window and get a login prompt, but as soon as I entered the login name, the login process would hang. If I power cycle the server, it comes back up OK and notes the failed disk. If I insert the disk while the system is running, it hangs in the same manner as when I removed the disk. If I reboot, the system rebuilds the disk and everything is OK. I tried this test a couple of times and got the same results. Sometimes the CISS driver would note the changes in syslog, but the system would still hang. I tried installing FreeBSD Release-4.9 and got identical results. I have a Dell server with PERC RAID running FreeBSD Release-5.1. I tried the same test on it and it performed flawlessly, logging the removal of the disk and the re-insertion without a single hiccup. Unfortunately, I need to get this to work on the HP Proliant hardware. Does anyone have any suggestions on how to get this to work reliably? If not, I will have to abandon FreeBSD and install some flavor of Linux on the servers instead. Thanks in advance. Paul Lutt Fluke Corporation paul.lutt@fluke.com From owner-freebsd-hardware@FreeBSD.ORG Fri Jan 23 12:24:45 2004 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4CBDB16A4D2 for ; Fri, 23 Jan 2004 12:24:45 -0800 (PST) Received: from wonkity.com (wonkity.com [65.173.111.5]) by mx1.FreeBSD.org (Postfix) with ESMTP id E8AFB43D45 for ; Fri, 23 Jan 2004 12:24:43 -0800 (PST) (envelope-from wblock@wonkity.com) Received: from wonkity.com (localhost [127.0.0.1]) by wonkity.com (8.12.10/8.12.10) with ESMTP id i0NKOg1m098167 for ; Fri, 23 Jan 2004 13:24:43 -0700 (MST) (envelope-from wblock@wonkity.com) Received: from localhost (wblock@localhost) by wonkity.com (8.12.10/8.12.10/Submit) with ESMTP id i0NKOgZJ098164 for ; Fri, 23 Jan 2004 13:24:42 -0700 (MST) (envelope-from wblock@wonkity.com) Date: Fri, 23 Jan 2004 13:24:42 -0700 (MST) From: Warren Block To: hardware@freebsd.org Message-ID: <20040123131935.K98150@wonkity.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Subject: XF86Config for ProSavage (MSI KM4ML) X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 23 Jan 2004 20:24:45 -0000 FreeBSD runs great on the Microstar/MSI KM4M motherboard, an integrated MicroATX board with on-board network (VIA Rhine), sound (works with pcm), and video (ProSavage). However, getting X to work with the integrated video requires a trick that I wanted to document for the archives. The "NoUseBIOS" option must be included in the Device settings. Otherwise, the monitor just goes dark when X is started. Section "Device" ### Available Driver options are:- ### Values: : integer, : float, : "True"/"False", ### : "String", : " Hz/kHz/MHz" ### [arg]: arg optional #Option "NoAccel" # [] #Option "HWCursor" # [] #Option "SWCursor" # [] #Option "ShadowFB" # [] #Option "Rotate" # [] #Option "UseBIOS" # [] #Option "LCDClock" # #Option "ShadowStatus" # [] #Option "CrtOnly" # [] #Option "TvOn" # [] #Option "PAL" # [] #Option "ForceInit" # [] Option "NoUseBIOS" # WB: needed! Identifier "Card0" Driver "savage" VendorName "S3 Inc." BoardName "[ProSavageDDR]" BusID "PCI:1:0:0" EndSection -Warren Block * Rapid City, South Dakota USA From owner-freebsd-hardware@FreeBSD.ORG Fri Jan 23 13:11:48 2004 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1B4DC16A4CE; Fri, 23 Jan 2004 13:11:48 -0800 (PST) Received: from www.gotbrains.org (www2.gotbrains.org [206.180.149.129]) by mx1.FreeBSD.org (Postfix) with ESMTP id 01C8343D58; Fri, 23 Jan 2004 13:10:47 -0800 (PST) (envelope-from clists@gotbrains.org) Received: from igor.gotbrains.org (eagle.spinneret.com [206.180.139.69]) by www.gotbrains.org (8.12.9p2/8.12.9) with SMTP id i0NL7q5p059525; Fri, 23 Jan 2004 15:07:52 -0600 (CST) (envelope-from clists@gotbrains.org) Date: Fri, 23 Jan 2004 15:06:48 -0600 From: "Stephen P. Cravey" To: freebsd-questions@freebsd.org Message-Id: <20040123150648.64dbb023.clists@gotbrains.org> X-Mailer: Sylpheed version 0.9.8a (GTK+ 1.2.10; i386-portbld-freebsd5.1) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit cc: freebsd-hardware@freebsd.org Subject: Hot Swap hardware on FreeBSD? X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 23 Jan 2004 21:11:48 -0000 I'm trying to locate a good resource for creating hot swap capable servers with FreeBSD and Vinum. Specifically, I'm trying to find out several things: Are there resources somewhere that document this type of thing? Please? Do I need controllers for SATA/SCSI that will handle the plugging/unplugging of drives, or do I just need to do a bus rescan (or the like) after the change and notify vinum? i.e. do i need something like an adaptec 2200S or will a 39320 work? Is there anything in particular I should look for when buying hot swap chassis? Other than SCA for SCSI? What about Hot swap with Fibre Channel? What about using FreeBSD in a SAN where it's both serving drives and acting as a client? Where can I find (recent) performance numbers for raid 0,1,5 comparisons? What else should I know about this before attempting it? Thank you. -Stephen From owner-freebsd-hardware@FreeBSD.ORG Fri Jan 23 13:31:33 2004 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 66C5016A4CE for ; Fri, 23 Jan 2004 13:31:33 -0800 (PST) Received: from vir2.relay.fluke.com (vir2.relay.fluke.com [129.196.184.26]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2686543D3F for ; Fri, 23 Jan 2004 13:31:32 -0800 (PST) (envelope-from paul.lutt@fluke.com) Received: from sarguy.tc.fluke.com ([129.196.165.251] RDNS failed) by vir2.relay.fluke.com with Microsoft SMTPSVC(5.0.2195.5329); Fri, 23 Jan 2004 13:31:27 -0800 Received: from paul (helo=localhost) by sarguy.tc.fluke.com with local-esmtp (Exim 3.36 #1 (Debian)) id 1Ak8ti-0000xD-00; Fri, 23 Jan 2004 13:31:26 -0800 Date: Fri, 23 Jan 2004 13:31:26 -0800 (PST) From: Paul Lutt X-X-Sender: paul@sarguy.na.flukecorp.com To: "Jackie S. McCracken" In-Reply-To: <2E6D639430377992@jacktel.com> Message-ID: References: <2E6D639430377992@jacktel.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-OriginalArrivalTime: 23 Jan 2004 21:31:27.0033 (UTC) FILETIME=[41E76A90:01C3E1F8] cc: paul.lutt@fluke.com cc: freebsd-hardware@freebsd.org Subject: Re:HP DL360 G3 Hangs on Disk Removal X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 23 Jan 2004 21:31:33 -0000 I feel your pain. I so much want to use FreeBSD. We've used Red Hat Linux for years, but I have 20 odd servers that are running 7.2 which is no longer supported by Red Hat. The cheapest I could get support for would be $150/server if I install Enterprise Desktop. I was going to go with Debian, but I'm having a devil of a time with the Broadcomm ethernet versus Woody, the "stable" Debian release. I'm in the midst of building a custom kernel to see if I can get it up and running. I really like the FreeBSD model, having used SunOS for years. But having the RAID controller unreliable makes this a non-starter. It is especially frustrating to see how well the PERC raid driver works. It behaves exactly the way you would expect. Hope you have better luck in the future. Paul Lutt Fluke Corporation paul.lutt@fluke.com From owner-freebsd-hardware@FreeBSD.ORG Sat Jan 24 02:43:20 2004 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D501216A4CE for ; Sat, 24 Jan 2004 02:43:20 -0800 (PST) Received: from sasami.jurai.net (sasami.jurai.net [66.92.160.223]) by mx1.FreeBSD.org (Postfix) with ESMTP id F0B6743D6D for ; Sat, 24 Jan 2004 02:43:15 -0800 (PST) (envelope-from mdodd@FreeBSD.ORG) Received: from sasami.jurai.net (winter@sasami.jurai.net [66.92.160.223]) by sasami.jurai.net (8.12.9/8.12.9) with ESMTP id i0OAhDdi070899; Sat, 24 Jan 2004 05:43:14 -0500 (EST) (envelope-from mdodd@FreeBSD.ORG) Date: Sat, 24 Jan 2004 05:43:13 -0500 (EST) From: "Matthew N. Dodd" X-X-Sender: winter@sasami.jurai.net To: Paul Lutt In-Reply-To: Message-ID: <20040124054046.W57327@sasami.jurai.net> References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-hardware@FreeBSD.ORG Subject: Re: HP DL360 G3 Hangs on Disk Removal X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 24 Jan 2004 10:43:21 -0000 On Fri, 23 Jan 2004, Paul Lutt wrote: > What I got was a system that wasn't totally locked up, but it could not > perform any disk access. I had a shell open on the console. Pressing > enter would bring up a new prompt. Trying to do anything that required > reading the disk would cause the shell to hang. I've seen this with the ida(4) driver as well, though only on re-insertion of a hotswap disk. Failure was the same. With the system cracked open and the status LEDs on the controller available for viewing you could see when the controller locked up. After going over the driver and instrumenting the interrupt handler and installing a watchdog timeout routine I see no way that this condition could be caused by the driver, unless we're supposed to be doing something that we don't know about. What model CISS card do you have? -- 10 40 80 C0 00 FF FF FF FF C0 00 00 00 00 10 AA AA 03 00 00 00 08 00 From owner-freebsd-hardware@FreeBSD.ORG Sat Jan 24 08:47:07 2004 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id ACFBC16A4CF; Sat, 24 Jan 2004 08:47:07 -0800 (PST) Received: from vir2.relay.fluke.com (vir2.relay.fluke.com [129.196.184.26]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1380D43D67; Sat, 24 Jan 2004 08:47:03 -0800 (PST) (envelope-from paul@fluke.com) Received: from [192.168.0.106] ([129.196.191.160] unverified) by vir2.relay.fluke.com with Microsoft SMTPSVC(5.0.2195.5329); Sat, 24 Jan 2004 08:47:00 -0800 Date: Sat, 24 Jan 2004 08:46:57 -0800 (PST) From: Paul Lutt X-X-Sender: paul@myst.wavecable.com To: "Matthew N. Dodd" In-Reply-To: <20040124054046.W57327@sasami.jurai.net> Message-ID: References: <20040124054046.W57327@sasami.jurai.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-OriginalArrivalTime: 24 Jan 2004 16:47:00.0153 (UTC) FILETIME=[AFA9F290:01C3E299] cc: Paul Lutt cc: freebsd-hardware@FreeBSD.ORG Subject: Re: HP DL360 G3 Hangs on Disk Removal X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 24 Jan 2004 16:47:07 -0000 On Sat, 24 Jan 2004, Matthew N. Dodd wrote: > On Fri, 23 Jan 2004, Paul Lutt wrote: > > What I got was a system that wasn't totally locked up, but it could not > > perform any disk access. I had a shell open on the console. Pressing > > enter would bring up a new prompt. Trying to do anything that required > > reading the disk would cause the shell to hang. > > I've seen this with the ida(4) driver as well, though only on re-insertion > of a hotswap disk. Failure was the same. With the system cracked open > and the status LEDs on the controller available for viewing you could see > when the controller locked up. > > After going over the driver and instrumenting the interrupt handler and > installing a watchdog timeout routine I see no way that this condition > could be caused by the driver, unless we're supposed to be doing something > that we don't know about. > > What model CISS card do you have? > > -- > 10 40 80 C0 00 FF FF FF FF C0 00 00 00 00 10 AA AA 03 00 00 00 08 00 > lspci shows the following (Yes, I've installed Debian in the interim) 00:04.0 RAID bus controller: Compaq Computer Corporation Smart Array 5i/532 (rev 01) This is all a bit frustrating because I have several Linux based Proliant servers with the CISS hardware and they behave properly when the disk is removed and re-inserted. We also have LOTS of Windows based servers that behave properly given the same test. Makes me suspect some sort of driver issue. Paul Lutt Fluke Corporation From owner-freebsd-hardware@FreeBSD.ORG Sat Jan 24 17:26:46 2004 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3A19816A4CE; Sat, 24 Jan 2004 17:26:46 -0800 (PST) Received: from fep03-mail.bloor.is.net.cable.rogers.com (fep03-mail.bloor.is.net.cable.rogers.com [66.185.86.73]) by mx1.FreeBSD.org (Postfix) with ESMTP id CCCBE43D2D; Sat, 24 Jan 2004 17:26:42 -0800 (PST) (envelope-from mikej@rogers.com) Received: from win2000 ([63.139.3.63]) by fep03-mail.bloor.is.net.cable.rogers.comESMTP <20040125012602.XMOS163351.fep03-mail.bloor.is.net.cable.rogers.com@win2000>; Sat, 24 Jan 2004 20:26:02 -0500 From: "Mike Jakubik" To: , Date: Sat, 24 Jan 2004 20:27:16 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook, Build 11.0.5510 Thread-Index: AcPi4l4+1mWMZw9YR+2i3YuRGjdB1A== X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 X-Authentication-Info: Submitted using SMTP AUTH LOGIN at fep03-mail.bloor.is.net.cable.rogers.com from [63.139.3.63] using ID at Sat, 24 Jan 2004 20:26:02 -0500 Message-Id: <20040125012602.XMOS163351.fep03-mail.bloor.is.net.cable.rogers.com@win2000> Subject: LSI MegaRAID SCSI 320-0 support X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 25 Jan 2004 01:26:46 -0000 Does anyone know if the LSI Logic MegaRAID SCSI 320-0 Zero-channel (ZCR) Ultra320 SCSI RAID card is supported? I know the amr man page doesn't list the ZCR card specifically, but im hoping someone forgot to list it :) Thanks. From owner-freebsd-hardware@FreeBSD.ORG Sat Jan 24 19:49:00 2004 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 618) id 1570F16A4CF; Sat, 24 Jan 2004 19:49:00 -0800 (PST) To: freebsd-current@freebsd.org, freebsd-hardware@freebsd.org Date: Sat, 24 Jan 2004 19:49:00 -0800 (PST) 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: <20040125034900.1570F16A4CF@hub.freebsd.org> From: wpaul@FreeBSD.ORG (Bill Paul) Subject: Project Evil: The Evil Continues X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 25 Jan 2004 03:49:00 -0000 Previously, I had asked for help getting the Intel Centrino wireless cards to work with Project Evil, and thanks to various wonderful people, a couple of Centrino cards and a miniPCI-to-PCI adapter turned up on Project Evil Labs' doorstep. The Centrino NDIS driver now works correctly. (The problem turned out to be that I wasn't initializing some special flags in ndis_packet structures). Now I'm trying to get a handle on getting support done for all the remaining unsupported 802.11 chipsets out there. There are a couple that I know don't work, and a few which might work, but I don't know for sure since I don't have them. Right now, it looks like all of the Broadcom-based cards should be supported, as well as the Centrino cards. There are various ethernet cards that I've tested which work as well. I am looking for success or failure reports concerning the following devices: - nVidia MCP ethernet, integrated into the nVidia nForce2 chipset. This driver should work using the nvenet.sys driver for Windows which is available from nVidia's web site. Note: recent versions of the driver consist of just two files: the nvenet.sys binary module, and its accompanying .inf file. However some of the older driver distributions included a couple of additional firmware/microcode files that nvenet.sys would try to load at runtime. If you have one of these older drivers, put the firmware/microcode files in /compat/ndis, and the driver should load them correctly. - RealTek RTL8180 wireless LAN chipset. I have been unable to find a card with this chip in any of my local computer stores. The RealTek driver for this chip _should_ work. I'm pretty sure all of the routines it calls are implemented. - ADMtek 8211 wireless LAN chipset. This one should also work, but I can't find any cards with this chipset in my local computer stores. - Intel PRO/5000 wirless card. This is apparently an Atheros 5210 chipset. I have been told the wl50nd5.sys driver for this card crashes when you call its reset method, but again I don't have one of these so I can't confirm this or figure out what the problem is. - AMD Am1771/Am1772 wireless LAN chipset. This one probably won't work: the supplied AMD driver calls lots of functions in ntoskrnl.exe which I haven't implemented yet. This chipset is present on the SMC 2602w version 3 card. I repeat: that's the SMC 2602w VERSION THREE. The version 1 card is a Prism chipset. I don't know what the v2 card is. - Texas Instruments ax100 chipset. I'm not sure if this one works or not. This chipset has been reverse-engineered and there is a native FreeBSD driver available, but I'm still curious to see if it works with the NDISulator. - Atheros chipsets. Of course, we have the ath(4) driver to support these, but it would be nice to know which ones work (or do not work) with the NDISulator. - Any other PCI or cardbus NIC that I've overlooked which isn't currently supported by an existing native driver. If you have a system with one of these chipsets, please give the NDISulator a try. Note: you do NOT have to recompile your kernel to test it. Find the .sys and .inf files from your Windows driver media and do the following: # cp foo.sys foo.inf /sys/modules/if_ndis # cd /sys/modules/ndis # make; make load # cd /sys/modules/if_ndis # ndiscvt -i foo.inf -s foo.sys -o ndis_driver_data.h # make; make load You don't even have to reboot. Well, not unless the driver causes a panic. :/ If the NIC works, that's great! Drop me a line letting me know, so I can cross it off the list. If it doesn't work, please do the following: - Describe the failure to me _in_ _detail_. DON'T LOAD THE DRIVER WITH X RUNNING. (I hate it when people do that. If for some reason there's a panic, you'll never see it unless you're watching the console. If X is running, it will just look like the system froze, and you won't be able to tell what happened.) If you see messages of the form "No match for " on the console, then the driver is trying to call some functions that I haven't implemented yet. In very rare cases, the driver may still work, but don't bet on it. Make a note of all console messages that appear when you try to load the driver module. And send them to me, along with a description of what card you have and whar Windows driver module you used. - Tell me where you got your card so I can try to get one too. As with the Centrino, it's not always possible to debug these problems without actual hardware. - If you're feeling really generous, loan me your card for a while so I can coerce^Wcoax it into working. (This doesn't apply to NICs that are integrated into your system.) Again, we at Project Evil appreciate your assistance in our efforts to dominate^Wimprove the world. If you decide to loan us your hardware, please send it do: Attn: Bill Paul Wind River Systems 500 Wind River Way Alameda, CA. 94102 USA Project Evil: when it absolutely, positively has to be evil overnight. -Bill -- ============================================================================= -Bill Paul (510) 749-2329 | Senior Engineer, Master of Unix-Fu wpaul@windriver.com | Wind River Systems ============================================================================= you're just BEGGING to face the moose ============================================================================= From owner-freebsd-hardware@FreeBSD.ORG Sat Jan 24 19:52:52 2004 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 618) id 62AD716A4CF; Sat, 24 Jan 2004 19:52:52 -0800 (PST) To: freebsd-current@freebsd.org, freebsd-hardware@freebsd.org Date: Sat, 24 Jan 2004 19:52:52 -0800 (PST) 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: <20040125035252.62AD716A4CF@hub.freebsd.org> From: wpaul@FreeBSD.ORG (Bill Paul) Subject: Re: Project Evil: The Evil Continues X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 25 Jan 2004 03:52:52 -0000 Whoops... I botched the zip code in the address in my previous message. The correct address is: Attn: Bill Paul Wind River Systems 500 Wind River Way Alameda, CA. 94501 USA (I typed 94102 by mistake -- that's my home zip code, not Wind River's.) -Bill -- ============================================================================= -Bill Paul (510) 749-2329 | Senior Engineer, Master of Unix-Fu wpaul@windriver.com | Wind River Systems ============================================================================= you're just BEGGING to face the moose ============================================================================= From owner-freebsd-hardware@FreeBSD.ORG Sat Jan 24 19:59:34 2004 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2F2C616A4CE; Sat, 24 Jan 2004 19:59:34 -0800 (PST) Received: from mout.perfora.net (mout.perfora.net [217.160.230.40]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6B5A243D60; Sat, 24 Jan 2004 19:59:03 -0800 (PST) (envelope-from dark@perfora.net) Received: from [217.160.230.50] (helo=smtp.perfora.net) by mout.perfora.net with esmtp (Exim 3.35 #1) id 1AkbQM-0000mL-00; Sat, 24 Jan 2004 22:59:02 -0500 Received: from [24.169.60.91] (helo=mxus.perfora.net) by smtp.perfora.net with asmtp (Exim 3.35 #1) id 1AkbQM-0005el-00; Sat, 24 Jan 2004 22:59:02 -0500 Received: by mxus.perfora.net (Postfix, from userid 1001) id 74A3B5EDD; Sat, 24 Jan 2004 22:58:58 -0500 (EST) Date: Sat, 24 Jan 2004 22:58:58 -0500 From: Dev Tugnait To: Bill Paul Message-ID: <20040125035858.GB82300@daemon.unixdaemon.org> References: <20040125034900.1570F16A4CF@hub.freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20040125034900.1570F16A4CF@hub.freebsd.org> X-Editor: Vim http://www.vim.org/ X-Info: http://unixdaemon.org X-Operating-System: Unix/5.2-RELEASE (i386) X-Uptime: 10:58PM up 1 day, 9:26, 16 users, load averages: 0.05, 0.18, 0.20 User-Agent: Mutt/1.5.5.1i cc: freebsd-current@freebsd.org cc: freebsd-hardware@freebsd.org Subject: Re: Project Evil: The Evil Continues X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 25 Jan 2004 03:59:34 -0000 What in the world is Project Evil? * Bill Paul (wpaul@FreeBSD.ORG) wrote: > > Previously, I had asked for help getting the Intel Centrino wireless > cards to work with Project Evil, and thanks to various wonderful people, > a couple of Centrino cards and a miniPCI-to-PCI adapter turned up on > Project Evil Labs' doorstep. The Centrino NDIS driver now works > correctly. (The problem turned out to be that I wasn't initializing > some special flags in ndis_packet structures). > > Now I'm trying to get a handle on getting support done for all > the remaining unsupported 802.11 chipsets out there. There are a > couple that I know don't work, and a few which might work, but I > don't know for sure since I don't have them. > > Right now, it looks like all of the Broadcom-based cards should be > supported, as well as the Centrino cards. There are various ethernet > cards that I've tested which work as well. I am looking for success > or failure reports concerning the following devices: > > - nVidia MCP ethernet, integrated into the nVidia nForce2 chipset. > This driver should work using the nvenet.sys driver for Windows > which is available from nVidia's web site. Note: recent versions > of the driver consist of just two files: the nvenet.sys binary > module, and its accompanying .inf file. However some of the older > driver distributions included a couple of additional firmware/microcode > files that nvenet.sys would try to load at runtime. If you have one > of these older drivers, put the firmware/microcode files in > /compat/ndis, and the driver should load them correctly. > > - RealTek RTL8180 wireless LAN chipset. I have been unable to find > a card with this chip in any of my local computer stores. The > RealTek driver for this chip _should_ work. I'm pretty sure all > of the routines it calls are implemented. > > - ADMtek 8211 wireless LAN chipset. This one should also work, but I > can't find any cards with this chipset in my local computer stores. > > - Intel PRO/5000 wirless card. This is apparently an Atheros 5210 > chipset. I have been told the wl50nd5.sys driver for this card > crashes when you call its reset method, but again I don't have one of > these so I can't confirm this or figure out what the problem is. > > - AMD Am1771/Am1772 wireless LAN chipset. This one probably won't > work: the supplied AMD driver calls lots of functions in ntoskrnl.exe > which I haven't implemented yet. This chipset is present on the > SMC 2602w version 3 card. I repeat: that's the SMC 2602w VERSION THREE. > The version 1 card is a Prism chipset. I don't know what the v2 card is. > > - Texas Instruments ax100 chipset. I'm not sure if this one works or > not. This chipset has been reverse-engineered and there is a native > FreeBSD driver available, but I'm still curious to see if it works > with the NDISulator. > > - Atheros chipsets. Of course, we have the ath(4) driver to support > these, but it would be nice to know which ones work (or do not work) > with the NDISulator. > > - Any other PCI or cardbus NIC that I've overlooked which isn't currently > supported by an existing native driver. > > If you have a system with one of these chipsets, please give the > NDISulator a try. Note: you do NOT have to recompile your kernel to > test it. Find the .sys and .inf files from your Windows driver media > and do the following: > > # cp foo.sys foo.inf /sys/modules/if_ndis > # cd /sys/modules/ndis > # make; make load > # cd /sys/modules/if_ndis > # ndiscvt -i foo.inf -s foo.sys -o ndis_driver_data.h > # make; make load > > You don't even have to reboot. Well, not unless the driver causes > a panic. :/ > > If the NIC works, that's great! Drop me a line letting me know, so I > can cross it off the list. If it doesn't work, please do the > following: > > - Describe the failure to me _in_ _detail_. DON'T LOAD THE DRIVER > WITH X RUNNING. (I hate it when people do that. If for some reason > there's a panic, you'll never see it unless you're watching the > console. If X is running, it will just look like the system froze, > and you won't be able to tell what happened.) If you see messages > of the form "No match for " on the > console, then the driver is trying to call some functions that I > haven't implemented yet. In very rare cases, the driver may still > work, but don't bet on it. Make a note of all console messages that > appear when you try to load the driver module. And send them to me, > along with a description of what card you have and whar Windows driver > module you used. > > - Tell me where you got your card so I can try to get one too. As with > the Centrino, it's not always possible to debug these problems without > actual hardware. > > - If you're feeling really generous, loan me your card for a while so > I can coerce^Wcoax it into working. (This doesn't apply to NICs > that are integrated into your system.) > > Again, we at Project Evil appreciate your assistance in our efforts > to dominate^Wimprove the world. If you decide to loan us your hardware, > please send it do: > > Attn: Bill Paul > Wind River Systems > 500 Wind River Way > Alameda, CA. 94102 > USA > > Project Evil: when it absolutely, positively has to be evil overnight. > > -Bill > > -- > ============================================================================= > -Bill Paul (510) 749-2329 | Senior Engineer, Master of Unix-Fu > wpaul@windriver.com | Wind River Systems > ============================================================================= > you're just BEGGING to face the moose > ============================================================================= > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" ---++--- ---------GnuPGPVer 1.2.3-------------------------------------------------- pub 1024D/B9046473 2003-11-21 Dev Tugnait (Freebsd) Key fingerprint = F690 6725 1930 6FBE C05A FE4D 6CB1 34C1 B904 6473 sub 1024g/F8F019DF 2003-11-21 -------------------------------------------------------------------------- From owner-freebsd-hardware@FreeBSD.ORG Sat Jan 24 20:47:15 2004 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 793DB16A4CE for ; Sat, 24 Jan 2004 20:47:15 -0800 (PST) Received: from kiwi-computer.com (megan.kiwi-computer.com [63.224.10.3]) by mx1.FreeBSD.org (Postfix) with SMTP id EF26943D41 for ; Sat, 24 Jan 2004 20:47:13 -0800 (PST) (envelope-from rick@kiwi-computer.com) Received: (qmail 21068 invoked by uid 2001); 25 Jan 2004 04:47:12 -0000 Date: Sat, 24 Jan 2004 22:47:12 -0600 From: "Rick C. Petty" To: freebsd-hardware@freebsd.org Message-ID: <20040125044712.GA20903@megan.kiwi-computer.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.1i Subject: Conexant HCF 56k PCI modem help X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 25 Jan 2004 04:47:15 -0000 For a project, our customer wants to use these 56k PCI modems from Creative. Although not my first choice, I did some research and discovered that the modems use a Conexant Systems, Inc. (vendor id 0x14F1) SmartHCF 56k chip (device id 0x1059). It is not a "winmodem"; the HCF family is "Controllerless" vs. the HSF "software" chipsets. Under a vanilla 5.2-RELEASE, pciconf showed: none9@pci1:7:0: class=0x078000 card=0x1059 chip=0x105914F1 rev=0x08 hdr=0x00 vendor = 'Conexant Systems, Inc.' device = 'HCF 56k Data/Fax/Voice Modem (Worldwide)' class = simple comms I started by adding the following entry to the top of src/dev/puc/pucdata.c: { "HCF 56k Data/Fax/Voice Modem (Worldwide)", NULL, { 0x14F1, 0x1059, 0x148D, 0x1059 }, { 0xFFFF, 0xFFFF, 0xFFFF, 0xFFFF }, { { PUC_PORT_TYPE_UART, 0x10, 0x00, 0, 0 }, }, }, and the kernel detected the device (puc0) an bootup, but was unable to attach because it "could not get resource". That last line in the struct was pure guesswork, based on many other entries. I tried it with PUC_PORT_TYPE_COM and had the same error. Digging through puc.c I tried adding PUC_FLAGS_ALTRES to the flags and it found the device, although sometimes would hang on boot [I guessed various numbers for the "bar" parameter with varying levels of bootability], so I tried another approach.. Further internet investigation revealed a linux driver from linuxant: http://www.linuxant.com/drivers/hcf/downloads-license.php They provide two versions of their drivers-- one binary-only "full" version (at a "modest price") and a free (limited) version with source code. The code generates a few [linux] kernel modules via some shims to access the binary-only modules. I am hoping someone else of more kernel/driver/puc(4) experience has the time to help get this ported... please let me know ASAP. Alternatively, if someone could suggest a better solution (PCI-only) for not much more than US$25/ea. that works well in FreeBSD 5.x I would be quite grateful! Thanks in advance, -- Rick C. Petty Senior Software Engineer KIWI Computer From owner-freebsd-hardware@FreeBSD.ORG Sat Jan 24 20:51:17 2004 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 618) id BA32B16A4CF; Sat, 24 Jan 2004 20:51:17 -0800 (PST) In-Reply-To: <20040125035858.GB82300@daemon.unixdaemon.org> from Dev Tugnait at "Jan 24, 2004 10:58:58 pm" To: dev@unixdaemon.org (Dev Tugnait) Date: Sat, 24 Jan 2004 20:51:17 -0800 (PST) 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: <20040125045117.BA32B16A4CF@hub.freebsd.org> From: wpaul@FreeBSD.ORG (Bill Paul) cc: freebsd-current@freebsd.org cc: freebsd-hardware@freebsd.org Subject: Re: Project Evil: The Evil Continues X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 25 Jan 2004 04:51:17 -0000 > What in the world is Project Evil? Project Evil (aka the NDISulator) is a special binary compatibility layer for the FreeBSD kernel that lets you use Windows NDIS drivers for network adapters with FreeBSD/ia32. What does Project Evil do: - Provides a small Windows PE file relocator/dynamic linker to allow Windows .sys files to be interfaced with the native code. - Provides a utility to parse Windows .inf files to extract device identification data and registry keys. - Emulates large chunks of NDIS.SYS, HAL.dll and ntoskrnl.exe with native FreeBSD kernel routines. - Interfaces the NDIS packet/buffer model with the BSD ifnet/mbuf model, making an NDIS driver look like an ifnet interface to the FreeBSD kernel. - Supports PCI and cardbus devices (and PCMCIA too, eventually). What doesn't Project Evil do: - Provide support for USB network devices (this would require emulating portions of USBD.SYS and portitions of the Windows I/O model outside of the NDIS API). - Support Winows modem drivers (this would mean duplicating big parts of ntoskrnl.exe). -Bill -- ============================================================================= -Bill Paul (510) 749-2329 | Senior Engineer, Master of Unix-Fu wpaul@windriver.com | Wind River Systems ============================================================================= you're just BEGGING to face the moose ============================================================================= From owner-freebsd-hardware@FreeBSD.ORG Sat Jan 24 22:26:56 2004 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 75F3716A4CE for ; Sat, 24 Jan 2004 22:26:56 -0800 (PST) Received: from sccrmhc12.comcast.net (sccrmhc12.comcast.net [204.127.202.56]) by mx1.FreeBSD.org (Postfix) with ESMTP id CB24B43D2F for ; Sat, 24 Jan 2004 22:26:54 -0800 (PST) (envelope-from garycor@comcast.net) Received: from comcast.net (pcp04278597pcs.union01.nj.comcast.net[68.39.97.186]) by comcast.net (sccrmhc12) with SMTP id <200401250626530120027p3le> (Authid: garycor); Sun, 25 Jan 2004 06:26:53 +0000 Message-ID: <40136254.7000708@comcast.net> Date: Sun, 25 Jan 2004 01:29:40 -0500 From: Gary Corcoran User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.5) Gecko/20031007 X-Accept-Language: en-us, en MIME-Version: 1.0 To: "Rick C. Petty" References: <20040125044712.GA20903@megan.kiwi-computer.com> In-Reply-To: <20040125044712.GA20903@megan.kiwi-computer.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-hardware@freebsd.org Subject: Re: Conexant HCF 56k PCI modem help X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 25 Jan 2004 06:26:56 -0000 Rick, > For a project, our customer wants to use these 56k PCI modems from > Creative. Although not my first choice, I did some research and discovered > that the modems use a Conexant Systems, Inc. (vendor id 0x14F1) SmartHCF > 56k chip (device id 0x1059). It is not a "winmodem"; the HCF family is > "Controllerless" vs. the HSF "software" chipsets. I can't help you directly with your problem, but perhaps a clarification might help you or someone else understand the problem better. If the modem you have is "controllerless", then it *IS* a "winmodem". It needs a "windows" (or equivalent) driver to emulate the missing controller. If it's both controllerless *and* DSP-less, then it's a "softmodem". That is, a softmodem is one that does *everything* (except the actual Analog-to-Digital and Digital -to-Analog conversions) in software. So a softmodem needs realtime Digital Signal Processing code (as well as the controller emulation code) that runs on your host CPU. Gary > Under a vanilla 5.2-RELEASE, pciconf showed: > > none9@pci1:7:0: class=0x078000 card=0x1059 chip=0x105914F1 rev=0x08 hdr=0x00 > vendor = 'Conexant Systems, Inc.' > device = 'HCF 56k Data/Fax/Voice Modem (Worldwide)' > class = simple comms > > I started by adding the following entry to the top of src/dev/puc/pucdata.c: > > { "HCF 56k Data/Fax/Voice Modem (Worldwide)", > NULL, > { 0x14F1, 0x1059, 0x148D, 0x1059 }, > { 0xFFFF, 0xFFFF, 0xFFFF, 0xFFFF }, > { > { PUC_PORT_TYPE_UART, 0x10, 0x00, 0, 0 }, > }, > }, > > and the kernel detected the device (puc0) an bootup, but was unable to > attach because it "could not get resource". That last line in the struct > was pure guesswork, based on many other entries. I tried it with > PUC_PORT_TYPE_COM and had the same error. Digging through puc.c I tried > adding PUC_FLAGS_ALTRES to the flags and it found the device, although > sometimes would hang on boot [I guessed various numbers for the "bar" > parameter with varying levels of bootability], so I tried another > approach.. > > Further internet investigation revealed a linux driver from linuxant: > http://www.linuxant.com/drivers/hcf/downloads-license.php > > They provide two versions of their drivers-- one binary-only "full" version > (at a "modest price") and a free (limited) version with source code. The > code generates a few [linux] kernel modules via some shims to access the > binary-only modules. I am hoping someone else of more kernel/driver/puc(4) > experience has the time to help get this ported... please let me know > ASAP. > > Alternatively, if someone could suggest a better solution (PCI-only) for > not much more than US$25/ea. that works well in FreeBSD 5.x I would be > quite grateful! Thanks in advance, > > -- Rick C. Petty > Senior Software Engineer > KIWI Computer