From owner-freebsd-hardware@FreeBSD.ORG Sun Dec 19 10:47: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 A221316A4CE; Sun, 19 Dec 2004 10:47:05 +0000 (GMT) Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.126.173]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2F5B243D48; Sun, 19 Dec 2004 10:47:05 +0000 (GMT) (envelope-from craig.freebsd@online.de) Received: from [212.227.126.205] (helo=mrelayng.kundenserver.de) by moutng.kundenserver.de with esmtp (Exim 3.35 #1) id 1Cfyae-0004cK-00; Sun, 19 Dec 2004 11:47:04 +0100 Received: from [217.231.72.99] (helo=[192.168.0.103]) by mrelayng.kundenserver.de with asmtp (Exim 3.35 #1) id 1Cfyad-0008PT-00; Sun, 19 Dec 2004 11:47:03 +0100 Message-ID: <41C55C22.9020101@online.de> Date: Sun, 19 Dec 2004 11:46:58 +0100 From: craig Organization: small-pla.net User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206) X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-questions@freebsd.org, freebsd-hardware@freebsd.org, diavul@bsd.krakow.pl Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Provags-ID: kundenserver.de abuse@kundenserver.de auth:13d873e74d14c1363715808660186da0 Subject: Marvell 88E8001 on sk0 and RELENG_5_3 - big problems X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: craig.freebsd@online.de List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 19 Dec 2004 10:47:05 -0000 > Here's the fix: > http://www.openbsd.org/cgi-bin/cvsweb/src/sys/dev/pci/if_sk.c.diff?r1=1.51&r2=1.52 > > -- > Michal Belczyk do to severe incompatibility problems with my previous motherboard's IDE and fbsd5.3, i recently purchased a new gigabyte 865PE, complete with onboard marvell nic. :( from dmesg (after applying identifying patch) ---- skc0: port 0xac00-0xacff mem 0xfb000000-0xfb003fff irq 20 at device 9.0 on pci2 skc0: Yukon Gigabit Ethernet 10/100/1000Base-T Adapter skc0: PN: Yukon 88E8001 skc0: EC: Rev. 1.3 skc0: MN: Marvell skc0: SN: AbCdEfG5ca025 sk0: on skc0 sk0: Ethernet address: 00:0f:ea:5c:a0:25 miibus0: on sk0 ---- unfortuantely, this motherboard too has severe problems. although the nic is recognised at install/boot, it simply *refuses* to come up. dhclient just draws a blank. i have tried to ifconfig sk0 up and down a few times, but makes no difference. i tried to apply Michal's above patch off an absolute fresh install. ie. the *very* first thing i did sadly, only 1 of the 2 chunks succeeded. from if_sk.c.rej *************** *** 2425,2431 **** /* serial mode register */ DPRINTFN(6, ("sk_init_yukon: 9\n")); SK_YU_WRITE_2(sc_if, YUKON_SMR, YU_SMR_DATA_BLIND(0x1c) | - YU_SMR_MFL_VLAN | YU_SMR_IPG_DATA(0x1e)); DPRINTFN(6, ("sk_init_yukon: 10\n")); /* Setup Yukon's address */--- 2425,2432 ---- /* serial mode register */ DPRINTFN(6, ("sk_init_yukon: 9\n")); SK_YU_WRITE_2(sc_if, YUKON_SMR, YU_SMR_DATA_BLIND(0x1c) | + YU_SMR_MFL_VLAN | YU_SMR_MFL_JUMBO | + YU_SMR_IPG_DATA(0x1e)); DPRINTFN(6, ("sk_init_yukon: 10\n")); /* Setup Yukon's address */ --- note, i cannot cvsup to latest RLEENG_5, because i have no network! :( any ideas on what to do from here? although the patch did not work automatically, i could manually insert the code, but i am well aware of the problems that may cause! if anyone (in europe) is able to help me solve this issue, i will gladly send them my old ASRock PE ProHT motherboard! its in perfect condition and works fine with freebsd4.10 - tragically, 5.3 refuses to work with the onboard sis IDE controller... much thanks, --- craig.freebsd at online.de From owner-freebsd-hardware@FreeBSD.ORG Sun Dec 19 20:17:01 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 32F0A16A4CE for ; Sun, 19 Dec 2004 20:17:01 +0000 (GMT) Received: from mail.terralink.de (mail.tlink.de [217.9.16.16]) by mx1.FreeBSD.org (Postfix) with ESMTP id DB55B43D31 for ; Sun, 19 Dec 2004 20:17:00 +0000 (GMT) (envelope-from me@daniel.stefan.haischt.name) Received: from smtp.abyssworld.de (daniel-s-haischt.biz [84.252.66.2]) by mail.terralink.de (Postfix) with ESMTP id DB40BBD622 for ; Sun, 19 Dec 2004 21:16:59 +0100 (CET) Received: from localhost (smtp.abyssworld.de [192.168.0.7]) by smtp.abyssworld.de (Postfix) with ESMTP id 4615C18B84 for ; Sun, 19 Dec 2004 21:16:59 +0100 (CET) Received: from smtp.abyssworld.de ([127.0.0.1])port 10024) with ESMTP id 00232-02 for ; Sun, 19 Dec 2004 21:16:58 +0100 (CET) Received-SPF: none (smtp.abyssworld.de: 192.168.0.7 is neither permitted nor denied by domain of daniel.stefan.haischt.name) client-ip=192.168.0.7; envelope-from=me@daniel.stefan.haischt.name; helo=[192.168.120.239]; Received: from [192.168.120.239] (smtp.abyssworld.de [192.168.0.7]) by smtp.abyssworld.de (Postfix) with ESMTP id BEE7817532 for ; Sun, 19 Dec 2004 21:16:58 +0100 (CET) Message-ID: <41C5E1B8.2090805@daniel.stefan.haischt.name> Date: Sun, 19 Dec 2004 21:16:56 +0100 From: "Daniel S. Haischt" User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206) X-Accept-Language: de-DE, de, en-us, en MIME-Version: 1.0 To: freebsd-hardware@freebsd.org X-Enigmail-Version: 0.89.5.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=ISO-8859-15; format=flowed Content-Transfer-Encoding: 7bit X-Comment-1: GNU's Not Unix! X-Comment-2: Support FSF! X-Virus-Scanned: amavisd-new at abyssworld.de Subject: [QUESTION] Promise PDC20269 problems with FreeBSD 5.3 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, 19 Dec 2004 20:17:01 -0000 Hello, recently I updated one of my FreeBSD boxes to v 5.3. This box got a builtin Promise PDC20269 UDMA133 controller. Actually it's a controller with two IDE channels. So far if using the GENERIC kernel that comes with FreeBSD, I do not experience any problems. If using my own customized kernel I am getting the following error message while booting the system: ----8<--------8<--------8<-------8<-----8<----- Interrupt storm detected on "irq10: atapci1"; throtteling interrupt source: ---->8-------->8-------->8------->8----->8----- After some trail-and-error based investigations, I did figure out that if I don't plugin any device into IDE channel two, the just described error does not occur. So it has something to do with IDE channel two. As an additional note - The controller works under Linux, FreeBSD 5.3 (GENERIC) and FreeBSD 5.2.1 (custom kernel). Any hints on how to solve this issue would be greatly appreciated. -- Mit freundlichen Gruessen / With kind regards Daniel S. Haischt | phone: +49 -7032-992909 Grabenstrasse 11 | +49 -700-DHAISCHT | fax: +49 -7032-992910 D-71083 Herrenberg | fax2mail: +49 -7032-7999738 GERMANY | cell: +49 -172-7668936 SIP: sip:haischt@daniel-s-haischt.biz:5060 email: me@daniel.stefan.haischt.name web: http://www.daniel.stefan.haischt.name/ From owner-freebsd-hardware@FreeBSD.ORG Sun Dec 19 20:40:27 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 19B2416A4CE for ; Sun, 19 Dec 2004 20:40:27 +0000 (GMT) Received: from gaff.hhhr.ision.net (gaff.hhhr.ision.net [195.180.9.213]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6066243D39 for ; Sun, 19 Dec 2004 20:40:25 +0000 (GMT) (envelope-from ohoyer@ohoyer.de) Received: from gaff.hhhr.ision.net (localhost [127.0.0.1]) by gaff.hhhr.ision.net (8.12.11/8.12.11) with ESMTP id iBJKeUIQ051129; Sun, 19 Dec 2004 21:40:30 +0100 (CET) (envelope-from ohoyer@ohoyer.de) Received: from localhost (ohoyer@localhost)iBJKeTZU051126; Sun, 19 Dec 2004 21:40:30 +0100 (CET) (envelope-from ohoyer@ohoyer.de) X-Authentication-Warning: gaff.hhhr.ision.net: ohoyer owned process doing -bs Date: Sun, 19 Dec 2004 21:40:29 +0100 (CET) From: Olaf Hoyer Sender: ohoyer@gaff.hhhr.ision.net To: KC Somaratne In-Reply-To: Message-ID: <20041219213641.M50992@gaff.hhhr.ision.net> References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed cc: freebsd-hardware@freebsd.org Subject: Re: HP NC7170 Dual Port PCI-X 1000T Gigabit Server Adapter 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, 19 Dec 2004 20:40:27 -0000 On Thu, 16 Dec 2004, KC Somaratne wrote: > Hi, > > Is there going to be any support for the above HP EtherNet > card in FreeBSD 5.3-RELEASE? > > Most of the HP cards listed in the hardware notes for this > relase seem to be end-of-life by HP..! > Hi! Well, IIRC the 7170 is a dual-Port Intel-GigE-card, should be supported by the em(4) driver. I had some time ago the opportunity to play a short time with a Sun V65x, with 2 of those cards (I think because Sun could/would not supply us with additional NICs we bought 7170 from a HP supplier) equipped, and FBSD 5.2.1 worked. Are you just curious if they will work in a machnine that you want to buy, or do you have real trouble in an existing setup? HTH Olaf -- Olaf Hoyer ohoyer@ohoyer.de Fuerchterliche Erlebniss geben zu raten, ob der, welcher sie erlebt, nicht etwas Fuerchterliches ist. (Nietzsche, Jenseits von Gut und Boese) From owner-freebsd-hardware@FreeBSD.ORG Sun Dec 19 22:39: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 CBE2116A4CE for ; Sun, 19 Dec 2004 22:39:33 +0000 (GMT) Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.199]) by mx1.FreeBSD.org (Postfix) with ESMTP id 61C3343D48 for ; Sun, 19 Dec 2004 22:39:33 +0000 (GMT) (envelope-from daniel.hyde@gmail.com) Received: by wproxy.gmail.com with SMTP id 55so60967wri for ; Sun, 19 Dec 2004 14:39:33 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:references; b=F4ddg1nDlBLbkNKUK6GD69k4hjW3P+e02ZsDFy4N6qCktrFrlnIwa1q4T65LRBLUALo8mxxWM7mTjJXA1sPy3BhL4f8zUrUHzGC8VYIasImx1hySYTrSZ4K6RuhxsopTWyxfS7TmYqDcDvGWaOtO08d6iP1HW4WT4YSPSyApg7M= Received: by 10.54.6.57 with SMTP id 57mr13278wrf; Sun, 19 Dec 2004 14:39:32 -0800 (PST) Received: by 10.54.39.25 with HTTP; Sun, 19 Dec 2004 14:39:32 -0800 (PST) Message-ID: Date: Mon, 20 Dec 2004 09:39:32 +1100 From: Daniel Hyde To: craig.freebsd@online.de In-Reply-To: <41C55C22.9020101@online.de> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit References: <41C55C22.9020101@online.de> cc: freebsd-hardware@freebsd.org Subject: Re: Marvell 88E8001 on sk0 and RELENG_5_3 - big problems X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Daniel Hyde List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 19 Dec 2004 22:39:34 -0000 I've got a gigabyte's GA-8IPE775-PRO motherboard which I believe has the same onboard ethernet card. I too had zero luck obtaining an IP address with dhcp (dhclient); however the card works fine if you forget dhcp and assign it an IP address statically using ifconfig. If you know the range of IPs your DHCP server reserves for its own use (or if, like, me, it's your local router that's assigning you an IP in a private range), just make freebsd claim an IP of its own that's within the same subnet, but not within DHCP's range, so that it doesn't clash with other DHCP clients. For example, my LAN uses 192.168.1.n as its private IP space. The gateway/router is 192.168.1.1, and it assigns IPs 100-253 via DHCP. So, I just told ifconfig to grab 192.168.1.90, and it's fine. Couldn't give you the exact configuration steps now, as I'm at work and thus on a different machine. But if you want them, give me a holler and I'll see if I can remember what I did when I get home. :) Daniel On Sun, 19 Dec 2004 11:46:58 +0100, craig wrote: > > Here's the fix: > > http://www.openbsd.org/cgi-bin/cvsweb/src/sys/dev/pci/if_sk.c.diff?r1=1.51&r2=1.52 > > > > -- > > Michal Belczyk > > do to severe incompatibility problems with my previous motherboard's IDE and fbsd5.3, i recently purchased > a new gigabyte 865PE, complete with onboard marvell nic. :( > > from dmesg (after applying identifying patch) > ---- > skc0: port 0xac00-0xacff mem 0xfb000000-0xfb003fff irq 20 at device 9.0 on pci2 > skc0: Yukon Gigabit Ethernet 10/100/1000Base-T Adapter > skc0: PN: Yukon 88E8001 > skc0: EC: Rev. 1.3 > skc0: MN: Marvell > skc0: SN: AbCdEfG5ca025 > sk0: on skc0 > sk0: Ethernet address: 00:0f:ea:5c:a0:25 > miibus0: on sk0 > ---- > > unfortuantely, this motherboard too has severe problems. > although the nic is recognised at install/boot, it simply *refuses* to come up. dhclient just draws a blank. > i have tried to ifconfig sk0 up and down a few times, but makes no difference. > > i tried to apply Michal's above patch off an absolute fresh install. ie. the *very* first thing i did > sadly, only 1 of the 2 chunks succeeded. > > from if_sk.c.rej > *************** > *** 2425,2431 **** > /* serial mode register */ > DPRINTFN(6, ("sk_init_yukon: 9\n")); > SK_YU_WRITE_2(sc_if, YUKON_SMR, YU_SMR_DATA_BLIND(0x1c) | > - YU_SMR_MFL_VLAN | YU_SMR_IPG_DATA(0x1e)); > > DPRINTFN(6, ("sk_init_yukon: 10\n")); > /* Setup Yukon's address */--- 2425,2432 ---- > /* serial mode register */ > DPRINTFN(6, ("sk_init_yukon: 9\n")); > SK_YU_WRITE_2(sc_if, YUKON_SMR, YU_SMR_DATA_BLIND(0x1c) | > + YU_SMR_MFL_VLAN | YU_SMR_MFL_JUMBO | > + YU_SMR_IPG_DATA(0x1e)); > > DPRINTFN(6, ("sk_init_yukon: 10\n")); > /* Setup Yukon's address */ > > --- > > note, i cannot cvsup to latest RLEENG_5, because i have no network! :( > any ideas on what to do from here? > although the patch did not work automatically, i could manually insert the code, > but i am well aware of the problems that may cause! > > if anyone (in europe) is able to help me solve this issue, i will gladly send them my old ASRock PE ProHT motherboard! > its in perfect condition and works fine with freebsd4.10 - tragically, 5.3 refuses to work with the > onboard sis IDE controller... > > much thanks, > > --- > craig.freebsd at online.de > > _______________________________________________ > freebsd-hardware@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-hardware > To unsubscribe, send any mail to "freebsd-hardware-unsubscribe@freebsd.org" > From owner-freebsd-hardware@FreeBSD.ORG Tue Dec 21 13:04: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 2A3D716A4CE for ; Tue, 21 Dec 2004 13:04:19 +0000 (GMT) Received: from szamoca.krvarr.bc.ca (s142-179-111-232.bc.hsia.telus.net [142.179.111.232]) by mx1.FreeBSD.org (Postfix) with ESMTP id AF4C143D1D for ; Tue, 21 Dec 2004 13:04:16 +0000 (GMT) (envelope-from sandy@krvarr.bc.ca) Received: from szamoca.krvarr.bc.ca (localhost [127.0.0.1]) by szamoca.krvarr.bc.ca (8.13.1/8.12.11) with ESMTP id iBLD4GYs008212 for ; Tue, 21 Dec 2004 05:04:16 -0800 (PST) (envelope-from sandy@szamoca.krvarr.bc.ca) Received: (from sandy@localhost) by szamoca.krvarr.bc.ca (8.13.1/8.12.11/Submit) id iBLD4Fr8008209; Tue, 21 Dec 2004 05:04:15 -0800 (PST) (envelope-from sandy) From: Sandy Rutherford MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <16840.8015.621763.784113@szamoca.krvarr.bc.ca> Date: Tue, 21 Dec 2004 05:04:15 -0800 To: freebsd-hardware@freebsd.org X-Mailer: VM 7.07 under Emacs 21.3.1 Subject: ZX348 or ZX346 NIC with 5.3 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, 21 Dec 2004 13:04:19 -0000 Does anyone have any experience with using either the Znyx ZX348 dual channel or ZX346 quad NIC in FreeBSD 5.3? I am currently using a ZX348 under FreeBSD 4.10. However, it had high packet loss rates with the de (4) driver, which is the recommended driver. This was solved by switching to Znyx's znb driver. According to Znyx's web page their driver is only for FreeBSD 4.x, so I am hoping that the 5.3 de (4) driver works with these cards. Does anybody have any experience with this? Thanks, Sandy From owner-freebsd-hardware@FreeBSD.ORG Wed Dec 22 08:30:42 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 ED55A16A4CE for ; Wed, 22 Dec 2004 08:30:42 +0000 (GMT) Received: from user123.c2.studioproteus.si (user123.c2.studioproteus.si [213.253.97.123]) by mx1.FreeBSD.org (Postfix) with ESMTP id E3ADF43D4C for ; Wed, 22 Dec 2004 08:30:41 +0000 (GMT) (envelope-from mte@bomango.net) Received: from [192.168.1.2] (BSN-95-249-115.dsl.siol.net [193.95.249.115]) iBM8V4XV002313 for ; Wed, 22 Dec 2004 09:31:05 +0100 Message-ID: <41C930AC.4030301@bomango.net> Date: Wed, 22 Dec 2004 09:30:36 +0100 From: Matej User-Agent: Mozilla Thunderbird 1.0 (X11/20041220) X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-hardware@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: atapi burning problems 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, 22 Dec 2004 08:30:43 -0000 Hello, I've tried to burn a dao audio cd using burncd but the system hanged. No combination of keys worked. Several times. Then I tried to burn a tao audio cd. The process seemed to be without errors but the result was very scratchy cd with some kind of distorsion in there. I thought it was something wrong with .cdr files so I converted one back to .wav and it was ok. Then I tried to burn a data cd, but the result was an I/O error when trying to mount it. So the burning doesn't work. I have the NEC 3500 dvd writer. Is my only chance to try scsi emulation with atacom or is there anything else to do? Thanks very much, Matej From owner-freebsd-hardware@FreeBSD.ORG Wed Dec 22 08:58: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 CAB3916A4CE for ; Wed, 22 Dec 2004 08:58:33 +0000 (GMT) Received: from fidel.freesurf.fr (fidel.freesurf.fr [212.43.206.16]) by mx1.FreeBSD.org (Postfix) with ESMTP id 01BBC43D31 for ; Wed, 22 Dec 2004 08:58:33 +0000 (GMT) (envelope-from olivier@gautherot.net) Received: from [192.168.0.2] (du-209-203.nat.adsl.claranet.fr [212.43.209.203]) by fidel.freesurf.fr (Postfix) with ESMTP id 697352A538F; Wed, 22 Dec 2004 09:58:31 +0100 (CET) Message-ID: <41C9373F.3050707@gautherot.net> Date: Wed, 22 Dec 2004 09:58:39 +0100 From: Olivier User-Agent: Mozilla Thunderbird 1.0 (X11/20041215) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Matej References: <41C930AC.4030301@bomango.net> In-Reply-To: <41C930AC.4030301@bomango.net> Content-Type: multipart/mixed; boundary="------------050908000308010205030504" X-Content-Filtered-By: Mailman/MimeDel 2.1.1 cc: freebsd-hardware@freebsd.org Subject: Re: atapi burning problems 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, 22 Dec 2004 08:58:33 -0000 This is a multi-part message in MIME format. --------------050908000308010205030504 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Hi Matej! > Hello, > I've tried to burn a dao audio cd using burncd but the system hanged. > No combination of keys worked. Several times. Then I tried to burn a > tao audio cd. The process seemed to be without errors but the result > was very scratchy cd with some kind of distorsion in there. I thought > it was something wrong with .cdr files so I converted one back to .wav > and it was ok. Then I tried to burn a data cd, but the result was an > I/O error when trying to mount it. > So the burning doesn't work. I have the NEC 3500 dvd writer. > Is my only chance to try scsi emulation with atacom or is there > anything else to do? > Thanks very much, > Matej Did you recompile your kernel with the following option? options atapicam I seem to remember a similar problem that was solved with this. Hope it helps Olivier --------------050908000308010205030504-- From owner-freebsd-hardware@FreeBSD.ORG Wed Dec 22 15:09:35 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 1A16B16A4CE for ; Wed, 22 Dec 2004 15:09:35 +0000 (GMT) Received: from user123.c2.studioproteus.si (user123.c2.studioproteus.si [213.253.97.123]) by mx1.FreeBSD.org (Postfix) with ESMTP id A6CC543D48 for ; Wed, 22 Dec 2004 15:09:33 +0000 (GMT) (envelope-from mte@bomango.net) Received: from [192.168.1.2] (BSN-95-249-115.dsl.siol.net [193.95.249.115]) iBMF9tXV009723 for ; Wed, 22 Dec 2004 16:09:57 +0100 Message-ID: <41C98E24.6070504@bomango.net> Date: Wed, 22 Dec 2004 16:09:24 +0100 From: Matej User-Agent: Mozilla Thunderbird 1.0 (X11/20041220) X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-hardware@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: atapi burning problems 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, 22 Dec 2004 15:09:35 -0000 Hi, Olivier: as I understand correctly, i have to rebuild kernel with atapicam only if i want to use scsi emulation. I have to enable this if I want to use cdrecord or cdrdao, but burncd is for atapi cd-r drives so this doesn't apply here. Dalius: yeah making an iso applies to data cds, but not to audio cds. I think so at least.. So have I missed something? Shouldn't it work without recompiling kernel? Or is enabling scsi emulation the only way to go? thanks, Matej From owner-freebsd-hardware@FreeBSD.ORG Wed Dec 22 16:09: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 CDD8716A528 for ; Wed, 22 Dec 2004 16:09:46 +0000 (GMT) Received: from S3.cableone.net (smtp3.cableone.net [24.116.0.229]) by mx1.FreeBSD.org (Postfix) with ESMTP id 79E8743D54 for ; Wed, 22 Dec 2004 16:09:46 +0000 (GMT) (envelope-from v.velox@vvelox.net) Received: from vixen42.24-119-122-191.cpe.cableone.net (unverified [24.119.123.89]) by S3.cableone.net (CableOne SMTP Service S3) with ESMTP id 5150404 for multiple; Wed, 22 Dec 2004 09:21:58 -0700 Date: Wed, 22 Dec 2004 10:08:49 -0600 From: Vulpes Velox To: Matej Message-ID: <20041222100849.3cc680a9@vixen42.24-119-122-191.cpe.cableone.net> In-Reply-To: <41C930AC.4030301@bomango.net> References: <41C930AC.4030301@bomango.net> X-Mailer: Sylpheed-Claws 0.9.13 (GTK+ 1.2.10; i386-portbld-freebsd5.3) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Abuse-Info: Send abuse complaints to abuse@cableone.net cc: freebsd-hardware@freebsd.org Subject: Re: atapi burning problems 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, 22 Dec 2004 16:09:47 -0000 On Wed, 22 Dec 2004 09:30:36 +0100 Matej wrote: > Hello, > I've tried to burn a dao audio cd using burncd but the system > hanged. No combination of keys worked. Several times. Then I tried > to burn a tao audio cd. The process seemed to be without errors but > the result was very scratchy cd with some kind of distorsion in > there. I thought it was something wrong with .cdr files so I > converted one back to .wav and it was ok. Then I tried to burn a > data cd, but the result was an I/O error when trying to mount it. > So the burning doesn't work. I have the NEC 3500 dvd writer. > Is my only chance to try scsi emulation with atacom or is there > anything else to do? What commands you using for it? Also check if the sysctl hw.ata.atapi_dma is set to 1. I have had the occasional problem caused by this with one drive I have. From owner-freebsd-hardware@FreeBSD.ORG Thu Dec 23 07:17:53 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 4972D16A4CE for ; Thu, 23 Dec 2004 07:17:53 +0000 (GMT) Received: from smtp1.bahnhof.se (smtp1.bahnhof.se [213.80.101.25]) by mx1.FreeBSD.org (Postfix) with ESMTP id E65F143D31 for ; Thu, 23 Dec 2004 07:17:52 +0000 (GMT) (envelope-from mark.rowlands@mypost.se) Received: from mfilter1.bahnhof.se (mail.bahnhof.se [213.136.33.1]) by smtp1.bahnhof.se (Postfix) with ESMTP id 841C61F7346 for ; Thu, 23 Dec 2004 07:45:00 +0100 (CET) Received: from localhost (localhost.localdomain [127.0.0.1]) by re-injector1.bahnhof.se (Postfix) with ESMTP id 3470C129152 for ; Thu, 23 Dec 2004 07:44:59 +0100 (CET) Received: from smtp4.bahnhof.se ([213.136.33.1]) by localhost (mfilter1.bahnhof.se [10.0.1.21]) (amavisd-new, port 10024) with ESMTP id 14232-06 for ; Thu, 23 Dec 2004 07:44:58 +0100 (CET) Received: from pcmarpxy.mine.nu (81-170-150-191.bahnhofbredband.net [81.170.150.191]) by smtp4.bahnhof.se (Postfix) with ESMTP id B79E112E390 for ; Thu, 23 Dec 2004 07:44:57 +0100 (CET) Received: from localhost (localhost.mwrwin2k.se [127.0.0.1]) by pcmarpxy.mine.nu (Postfix) with ESMTP id A04C31060D for ; Thu, 23 Dec 2004 07:44:58 +0100 (CET) Received: from pcmarpxy.mine.nu ([127.0.0.1]) by localhost (pcmarpxy.mine.nu [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 87095-08 for ; Thu, 23 Dec 2004 07:44:55 +0100 (CET) Received: from exchsrv1.mwrwin2k.se (kalendar.mine.nu [192.168.0.4]) by pcmarpxy.mine.nu (Postfix) with ESMTP id 2B8F710517 for ; Wed, 22 Dec 2004 23:57:05 +0100 (CET) MIME-Version: 1.0 Date: Wed, 22 Dec 2004 23:57:04 +0100 Content-class: urn:content-classes:message X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Lacie Firewire 800 pci Thread-Index: AcToeY1A+37O4ZvlTHqOWLjtUTFqgQ== From: "Mark Rowlands" To: X-Virus-Scanned: by amavisd-new at bahnhof.se Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.1 Subject: Lacie Firewire 800 pci 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, 23 Dec 2004 07:17:53 -0000 I'd just like to say that I just got one of these with a 250gb d2 = external disk shoved it in me 4.10 box recompiled kernel with firewire and it worked a treat..... now can someone tell me who to contact so it gets documented as working...because I found no docs anywhere suggesting that it would = work. =20 =20 From owner-freebsd-hardware@FreeBSD.ORG Thu Dec 23 13:47:38 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 95B6D16A4CE for ; Thu, 23 Dec 2004 13:47:38 +0000 (GMT) Received: from web50002.mail.yahoo.com (web50002.mail.yahoo.com [206.190.38.17]) by mx1.FreeBSD.org (Postfix) with SMTP id 2655F43D2F for ; Thu, 23 Dec 2004 13:47:38 +0000 (GMT) (envelope-from vkapya_2000@yahoo.com) Received: (qmail 65069 invoked by uid 60001); 23 Dec 2004 13:47:37 -0000 Comment: DomainKeys? See http://antispam.yahoo.com/domainkeys DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; b=XKnke3hdbrHYG/4kTYgwNtmug78OKd0Spl4R7/0aGv7dP3rCpGZ/xnU7D2UAxiATVJ/pUYrTM5mE3utry0rX5uDAC5/nlrG6u2EyUsZSu+3XCWpXex6hu21Qr6zopkCwvNVxdTBugenFGdWGF9CHssG6wBrXAbx3BV43I52kKVo= ; Message-ID: <20041223134737.65067.qmail@web50002.mail.yahoo.com> Received: from [193.220.82.125] by web50002.mail.yahoo.com via HTTP; Thu, 23 Dec 2004 05:47:37 PST Date: Thu, 23 Dec 2004 05:47:37 -0800 (PST) From: VICTOR KAPYA To: freebsd-hardware@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Subject: onboard intel pro 100 ve problems 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, 23 Dec 2004 13:47:38 -0000 Hi I have installed Windows XP IN Compaq Machine , Now I have a problem with the Network card ,it fails to update driver from my computer as well on Windows XP CD . Giving me a message "The device can not start (code 10) Note : The Driver version is 6.1.3.10 What should I do to resolve this problem. Regards Victor __________________________________ Do you Yahoo!? Yahoo! Mail - You care about security. So do we. http://promotions.yahoo.com/new_mail From owner-freebsd-hardware@FreeBSD.ORG Thu Dec 23 21:05:30 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 DD73E16A4CE for ; Thu, 23 Dec 2004 21:05:30 +0000 (GMT) Received: from smtp7.wanadoo.fr (smtp7.wanadoo.fr [193.252.22.24]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4C41543D3F for ; Thu, 23 Dec 2004 21:05:30 +0000 (GMT) (envelope-from cbaud@laposte.net) Received: from me-wanadoo.net (localhost [127.0.0.1]) by mwinf0712.wanadoo.fr (SMTP Server) with SMTP id 084471C000CA for ; Thu, 23 Dec 2004 22:05:29 +0100 (CET) Received: from libra.baudcl-liber.fr (AAmiens-151-1-32-141.w83-192.abo.wanadoo.fr [83.192.178.141]) by mwinf0712.wanadoo.fr (SMTP Server) with ESMTP id A148E1C000C7 for ; Thu, 23 Dec 2004 22:05:28 +0100 (CET) From: "Claude B." To: freebsd-hardware@freebsd.org Content-Type: text/plain; charset=iso-8859-15 Message-Id: <1103839588.5783.12.camel@libra.baudcl-liber.fr> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.4-8mdk Date: Thu, 23 Dec 2004 22:06:28 +0000 Content-Transfer-Encoding: 8bit Subject: RAID1 and ASUS PSCH-L motherboard 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, 23 Dec 2004 21:05:31 -0000 Hello, I intalled FreeBSD 5.3 without problem on my ASUS PSCH-L server motherboard. I setup a RAID 1 array in the BIOS of the Promise PDC20319 controller and I boot on the RAID array: "Hard Disk Drives:[FT TX Ary 1]". FreeBSD 5.3 supports perfectly this controller in view of the atacontrol commands and all seem ok: # atacontrol list ATA channel 0: Master: acd0 ATA/ATAPI revision 4 Slave: no device present ATA channel 1: Master: no device present Slave: no device present ATA channel 2: Master: no device present Slave: no device present ATA channel 3: Master: ad6 Slave: no device present ATA channel 4: Master: no device present Slave: no device present ATA channel 5: Master: ad10 Slave: no device present # atacontrol status ar0 ar0: ATA RAID1 subdisks: ad6 ad10 status: READY # I have a question: How to do to check the RAID 1 is operational without all to break? Is there tools to check? Here the ships of my board: Thank in anticipation, claude -- Clé publique: http://pgp.mit.edu From owner-freebsd-hardware@FreeBSD.ORG Thu Dec 23 22:57:29 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 DBEAA16A4CE for ; Thu, 23 Dec 2004 22:57:29 +0000 (GMT) Received: from web61202.mail.yahoo.com (web61202.mail.yahoo.com [216.155.196.126]) by mx1.FreeBSD.org (Postfix) with SMTP id 788F043D2D for ; Thu, 23 Dec 2004 22:57:29 +0000 (GMT) (envelope-from mcd_advisory@yahoo.com) Received: (qmail 8634 invoked by uid 60001); 23 Dec 2004 22:57:29 -0000 Comment: DomainKeys? See http://antispam.yahoo.com/domainkeys DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; b=uhVUGB6UTa8bxUzsdRVZ8HjzIx1usc4Jq/xSQ4LhJPUzOO3ulz/IdSK+ZKfsoVGPMSmU+xr7ZlX9uAf82TqSaihpU1c2oWEnvSSa7VmuPnbLlD5dzZhQmVE3vqXJS3KrWiCwq7xPERJDfPCQBoRt3KWRzs9B+5eibtiwE0f8e9o= ; Message-ID: <20041223225729.8632.qmail@web61202.mail.yahoo.com> Received: from [67.28.117.82] by web61202.mail.yahoo.com via HTTP; Thu, 23 Dec 2004 14:57:28 PST Date: Thu, 23 Dec 2004 14:57:28 -0800 (PST) From: Mervin McDougall To: freebsd-hardware@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Subject: Poor Console resolution on Compaq 2103US 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, 23 Dec 2004 22:57:30 -0000 I have one experience to share as a newbie, that of trying to get a proper console resolution on my laptop. I chose to stick with FreeBSD over Slackware for my laptop for the simplicity in its init system and fewer init levels, its ports and packages system which reduces the stress of looking for a file and all its dependencies and getting it downloaded, compiled and using on my laptop and basically its speed of booting- in 2/3 the time it takes slackware linux to boot, bsd is at the loging prompt.However,getting the proper console resolution was a pain as I favour console over X. I tried recompiling the kernel including support for Vesa by including options VESA and SC_PIXEL_MODE and that didn't work.I tried compiling the kernel with suppor for VGA_90WIDTH and that still did not provide me with adequate space on my screen to get anything else done. My console only the center of my screen and only occupied a 1/3 rd of the entire screen. I was very stressed until I cam across a website of someone who had successfully installed FreeBSD 5.2.1 on a similar laptop. I contacted him and he explained that he had similar problem but got over the issue by making use of a patch which allowed me to achieve screen resolutions of 1024x768. I have gotten over the problem happily but there are still some issues that the patch created in making use of it as slower performance in switching from console to X and the printing of error information when the kernel is initiating vidcontrol but I get to use console more often thankfully. I wish that the freebsd team would look into fixing any errors in vidcontrol to get the problem with screen resolutions on laptops fixed. I was able to do this with ease using linux framebuffer settings with slackware but had so much difficulty getting that done under freebsd 5.3. I could have chosen to give up and simply use linux but I like the way freebsd performs something about it is just magically and wouldn't want to miss out on using it. I just wish somethng could be done to better the performance of the system as is and get rid of some of those escape errors. or gett a better patch from the freebsd team. If anyone has a similar laptop and wants to get some specifics about what works and what doesn't feel free to visit http://demira.shopkeeper.de/~sascha/nx9005/ its pretty informative. Some details .. The Video Card is an ATI IGP 320M (Mobility 1) Mervin McDougall __________________________________ Do you Yahoo!? Send holiday email and support a worthy cause. Do good. http://celebrity.mail.yahoo.com From owner-freebsd-hardware@FreeBSD.ORG Fri Dec 24 06:55:30 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 4407F16A4CE for ; Fri, 24 Dec 2004 06:55:30 +0000 (GMT) Received: from mx1.mail.ru (mx1.mail.ru [194.67.23.121]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7530C43D39 for ; Fri, 24 Dec 2004 06:55:29 +0000 (GMT) (envelope-from pvtrifonov@mail.ru) Received: from [195.209.229.106] (port=2913 helo=tank) by mx1.mail.ru with esmtp id 1ChjME-000IRG-00 for freebsd-hardware@freebsd.org; Fri, 24 Dec 2004 09:55:26 +0300 From: "Peter Trifonov" To: Date: Fri, 24 Dec 2004 09:59:15 +0300 MIME-Version: 1.0 Content-Type: text/plain; charset="koi8-r" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook, Build 11.0.5510 Thread-Index: AcTphhRTR+bblnS7TMq3Tas6ldEB1A== X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 Message-Id: X-Spam: Not detected Subject: fxp device timeout 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, 24 Dec 2004 06:55:30 -0000 Hello all, I have already posted this message to freebsd-stable, but there was no reply up to now. I have a 2*PentiumPro200 PC with FreeBSD 5.3 acting as a firewall in a department network. The PC has both IDE and SCSI hard drives. (Quite strange system for a firewall, isn't it? However, it was the most suitable box I was able to find). It has 3 NICs xl0,fxp0 and fxp1. >From time to time both fxp's SIMULTANEOUSLY stop working and produce messages fxp*: device timeout. After doing ifconfig fxp* down&up it said Dec 22 19:22:13 firewall kernel: fxp1: SCB timeout: 0x70 0x0 0x50 0x0 Dec 22 19:22:13 firewall kernel: fxp1: SCB timeout: 0x20 0x0 0x50 0x0 Dec 22 19:22:23 firewall last message repeated 53 times Dec 22 19:22:23 firewall kernel: fxp0: SCB timeout: 0x70 0x0 0x50 0x0 Dec 22 19:22:23 firewall kernel: fxp1: SCB timeout: 0x20 0x0 0x50 0x0 The system resumes normal operation only after reboot. xl0 does not experience any problems. Does anybody know how to avoid this? Many thanks in advance. Here is the output of pciconf -l -v ******************************************** isab0@pci0:0:0: class=0x000000 card=0x00000000 chip=0x04848086 rev=0x88 hdr=0x00 vendor = 'Intel Corporation' device = '82378ZB/IB,82379AB PCI to ISA Bridge, System I/O' class = old subclass = non-VGA display device atapci0@pci0:1:0: class=0x01018a card=0x00000000 chip=0x06461095 rev=0x01 hdr=0x00 vendor = 'Silicon Image Inc (Was: CMD Technology Inc)' device = 'PCI-0646 EIDE Adapter (Single FIFO)' class = mass storage subclass = ATA ahc0@pci0:2:0: class=0x010000 card=0x00000000 chip=0x80789004 rev=0x00 hdr=0x00 vendor = 'Adaptec Inc' device = 'AIC-7880P Ultra/Ultra Wide SCSI Chipset' class = mass storage subclass = SCSI none0@pci0:11:0: class=0x030000 card=0x00000000 chip=0x0519102b rev=0x01 hdr=0x00 vendor = 'Matrox Electronic Systems Ltd.' device = 'MGA-2064W Storm (Millennium board)' class = display subclass = VGA xl0@pci0:12:0: class=0x020000 card=0x100010b7 chip=0x920010b7 rev=0x6c hdr=0x00 vendor = '3COM Corp, Networking Division' device = '3C905C-TX Fast EtherLink for PC Management NIC' class = network subclass = ethernet fxp0@pci0:13:0: class=0x020000 card=0x1200103c chip=0x12298086 rev=0x02 hdr=0x00 vendor = 'Intel Corporation' device = '82550/1/7/8/9 EtherExpress PRO/100(B) Ethernet Adapter' class = network subclass = ethernet fxp1@pci0:14:0: class=0x020000 card=0x1200103c chip=0x12298086 rev=0x02 hdr=0x00 vendor = 'Intel Corporation' device = '82550/1/7/8/9 EtherExpress PRO/100(B) Ethernet Adapter' class = network subclass = ethernet none1@pci0:20:0: class=0x050000 card=0x00000000 chip=0x84c58086 rev=0x04 hdr=0x00 vendor = 'Intel Corporation' device = '82453KX/GX 450KX/GX Memory Controller (Orion)' class = memory subclass = RAM hostb0@pci0:25:0: class=0x060000 card=0x00000000 chip=0x84c48086 rev=0x04 hdr=0x00 vendor = 'Intel Corporation' device = '82454KX/GX 450KX/GX Orion System Controller' class = bridge subclass = HOST-PCI ***************************************************** Here is the output of dmesg -a: ****************************************************** FreeBSD 5.3-RELEASE #0: Sat Dec 18 11:45:40 MSK 2004 bugman@firewall.xj.dcn:/usr/src/sys/i386/compile/FIREWALL Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: Pentium Pro (199.74-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x619 Stepping = 9 Features=0xfbff real memory = 100663296 (96 MB) avail memory = 88842240 (84 MB) MPTable: FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs cpu0 (BSP): APIC ID: 1 cpu1 (AP): APIC ID: 0 ioapic0: Changing APIC ID to 16 ioapic0: Assuming intbase of 0 MPTable: Ignoring global interrupt entry for pin 1 MPTable: Ignoring global interrupt entry for pin 2 MPTable: Ignoring global interrupt entry for pin 3 MPTable: Ignoring global interrupt entry for pin 4 MPTable: Ignoring global interrupt entry for pin 5 MPTable: Ignoring global interrupt entry for pin 6 MPTable: Ignoring global interrupt entry for pin 7 MPTable: Ignoring global interrupt entry for pin 8 MPTable: Ignoring global interrupt entry for pin 9 MPTable: Ignoring global interrupt entry for pin 10 MPTable: Ignoring global interrupt entry for pin 11 MPTable: Ignoring global interrupt entry for pin 12 MPTable: Ignoring global interrupt entry for pin 13 MPTable: Ignoring global interrupt entry for pin 14 MPTable: Ignoring global interrupt entry for pin 15 ioapic0 irqs 0-15 on motherboard npx0: [FAST] npx0: on motherboard npx0: INT 16 interface pcib0: pcibus 0 on motherboard pci0: on pcib0 isab0: at device 0.0 on pci0 isa0: on isab0 atapci0: port 0xfc00-0xfc0f,0x376,0x170-0x177,0x3f6,0x1f0-0x1f7 irq 14 at device 1.0 on pci0 ata0: channel #0 on atapci0 ata1: channel #1 on atapci0 ahc0: port 0xf800-0xf8ff mem 0xffbfc000-0xffbfcfff irq 9 at device 2.0 on pci0 ahc0: Using left over BIOS settings ahc0: [GIANT-LOCKED] aic7880: Ultra Single Channel A, SCSI Id=7, 16/253 SCBs pci0: at device 11.0 (no driver attached) xl0: <3Com 3c905C-TX Fast Etherlink XL> port 0xf400-0xf47f mem 0xffbec000-0xffbec07f irq 10 at device 12.0 on pci0 miibus0: on xl0 xlphy0: <3c905C 10/100 internal PHY> on miibus0 xlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto xl0: Ethernet address: 00:50:da:39:91:99 fxp0: port 0xf000-0xf01f mem 0xffa00000-0xffafffff,0xffbdc000-0xffbdcfff irq 11 at device 13.0 on pci0 miibus1: on fxp0 inphy0: on miibus1 inphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto fxp0: Ethernet address: 00:60:b0:67:21:6f fxp1: port 0xec00-0xec1f mem 0xff900000-0xff9fffff,0xffbcc000-0xffbccfff irq 11 at device 14.0 on pci0 miibus2: on fxp1 inphy1: on miibus2 inphy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto fxp1: Ethernet address: 00:60:b0:67:31:ec pci0: at device 20.0 (no driver attached) cpu0 on motherboard cpu1 on motherboard orm0: at iomem 0xc8000-0xcc7ff,0xc0000-0xc7fff on isa0 pmtimer0 on isa0 atkbdc0: at port 0x64,0x60 on isa0 atkbd0: irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] fdc0: at port 0x3f0-0x3f5 irq 6 drq 2 on isa0 fdc0: [FAST] fd0: <1440-KB 3.5" drive> on fdc0 drive 0 ppc0: at port 0x378-0x37f irq 7 on isa0 ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/8 bytes threshold ppbus0: on ppc0 plip0: on ppbus0 lpt0: on ppbus0 lpt0: Interrupt-driven port ppi0: on ppbus0 sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 unknown: can't assign resources (port) unknown: can't assign resources (port) unknown: can't assign resources (port) unknown: can't assign resources (port) unknown: can't assign resources (port) Timecounters tick every 10.000 msec ipfw2 initialized, divert enabled, rule-based forwarding disabled, default to deny, logging limited to 100 packets/entry by default ad2: 2441MB [4960/16/63] at ata1-master WDMA2 acd0: CDROM at ata1-slave PIO3 Waiting 15 seconds for SCSI devices to settle da0 at ahc0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-2 device da0: 3.300MB/s transfers, Tagged Queueing Enabled da0: 2033MB (4165272 512 byte sectors: 64H 32S/T 2033C) da1 at ahc0 bus 0 target 1 lun 0 da1: Fixed Direct Access SCSI-2 device da1: 3.300MB/s transfers, Tagged Queueing Enabled da1: 2033MB (4165272 512 byte sectors: 64H 32S/T 2033C) da2 at ahc0 bus 0 target 2 lun 0 da2: Fixed Direct Access SCSI-2 device da2: 3.300MB/s transfers, Tagged Queueing Enabled da2: 2033MB (4165272 512 byte sectors: 64H 32S/T 2033C) da3 at ahc0 bus 0 target 3 lun 0 da3: Fixed Direct Access SCSI-2 device da3: 3.300MB/s transfers, Tagged Queueing Enabled da3: 2033MB (4165272 512 byte sectors: 64H 32S/T 2033C) da4 at ahc0 bus 0 target 4 lun 0 da4: Fixed Direct Access SCSI-2 device da4: 3.300MB/s transfers, Tagged Queueing Enabled da4: 2033MB (4165272 512 byte sectors: 64H 32S/T 2033C) da5 at ahc0 bus 0 target 5 lun 0 da5: Fixed Direct Access SCSI-2 device da5: 3.300MB/s transfers, Tagged Queueing Enabled da5: 2033MB (4165272 512 byte sectors: 64H 32S/T 2033C) da6 at ahc0 bus 0 target 6 lun 0 da6: Fixed Direct Access SCSI-2 device da6: 10.000MB/s transfers (10.000MHz, offset 15), Tagged Queueing Enabled da6: 2033MB (4165272 512 byte sectors: 64H 32S/T 2033C) SMP: AP CPU #1 Launched! Mounting root from ufs:/dev/ad2s1a Pre-seeding PRNG: kickstart . Loading configuration files. Entropy harvesting: interrupts ethernet point_to_point kickstart . swapon: adding /dev/ad2s1b as swap device Starting file system checks: /dev/ad2s1a: FILE SYSTEM CLEAN; SKIPPING CHECKS /dev/ad2s1a: clean, 81944 free (1528 frags, 10052 blocks, 1.2% fragmentation) /dev/ad2s1e: FILE SYSTEM CLEAN; SKIPPING CHECKS /dev/ad2s1e: clean, 126835 free (35 frags, 15850 blocks, 0.0% fragmentation) /dev/da6s1d: FILE SYSTEM CLEAN; SKIPPING CHECKS /dev/da6s1d: clean, 1005324 free (28 frags, 125662 blocks, 0.0% fragmentation) /dev/ad2s1f: FILE SYSTEM CLEAN; SKIPPING CHECKS /dev/ad2s1f: clean, 369161 free (1201 frags, 45995 blocks, 0.2% fragmentation) /dev/ad2s1d: FILE SYSTEM CLEAN; SKIPPING CHECKS /dev/ad2s1d: clean, 122503 free (87 frags, 15302 blocks, 0.1% fragmentation) Setting hostname: firewall.xj.dcn. xl0: flags=8843 mtu 1500 options=9 inet 10.0.103.3 netmask 0xffffff00 broadcast 10.0.103.255 inet xxx.xxx.xxx.xxx netmask 0xfffffff0 broadcast xxx.xxx.xxx.xxx ether 00:50:da:39:91:99 media: Ethernet autoselect (100baseTX ) status: active fxp0: flags=8843 mtu 1500 options=8 inet xxx.xxx.xxx.xxx netmask 0xffffffc0 broadcast xxx.xxx.xxx.xxx ether 00:60:b0:67:21:6f media: Ethernet autoselect (100baseTX ) status: active fxp1: flags=8843 mtu 1500 options=8 inet xxx.xxx.xxx.xxx netmask 0xfffffffc broadcast xxx.xxx.xxx.xxx ether 00:60:b0:67:31:ec media: Ethernet autoselect (10baseT/UTP) status: active lo0: flags=8049 mtu 16384 inet 127.0.0.1 netmask 0xff000000 *********************************************************** Here is my kernel configuration *********************************************************** machine i386 #cpu I486_CPU #cpu I586_CPU cpu I686_CPU ident FIREWALL #custom options by P. Trifonov options SMP options IPFIREWALL options CPU_DISABLE_SSE options IPDIVERT #divert sockets options TCP_DROP_SYNFIN # drop TCP packets with SYN+FIN options IPFIREWALL_VERBOSE # print information about dropped packets options IPFIREWALL_VERBOSE_LIMIT=100 # limit verbosity # To statically compile in device wiring instead of /boot/device.hints #hints "GENERIC.hints" # Default places to look for devices. options SCHED_4BSD # 4BSD scheduler #options SCHED_ULE # Trifonov: use SMP scheduler options INET # InterNETworking #options INET6 # IPv6 communications protocols options FFS # Berkeley Fast Filesystem options SOFTUPDATES # Enable FFS soft updates support options UFS_ACL # Support for access control lists options UFS_DIRHASH # Improve performance on big directories options MD_ROOT # MD is a potential root device #options NFSCLIENT # Network Filesystem Client #options NFSSERVER # Network Filesystem Server #options NFS_ROOT # NFS usable as /, requires NFSCLIENT options MSDOSFS # MSDOS Filesystem options CD9660 # ISO 9660 Filesystem options PROCFS # Process filesystem (requires PSEUDOFS) options PSEUDOFS # Pseudo-filesystem framework options GEOM_GPT # GUID Partition Tables. options COMPAT_43 # Compatible with BSD 4.3 [KEEP THIS!] options COMPAT_FREEBSD4 # Compatible with FreeBSD4 options SCSI_DELAY=15000 # Delay (in ms) before probing SCSI options KTRACE # ktrace(1) support options SYSVSHM # SYSV-style shared memory options SYSVMSG # SYSV-style message queues options SYSVSEM # SYSV-style semaphores options _KPOSIX_PRIORITY_SCHEDULING # POSIX P1003_1B real-time extensions options KBD_INSTALL_CDEV # install a CDEV entry in /dev options AHC_REG_PRETTY_PRINT # Print register bitfields in debug # output. Adds ~128k to driver. options AHD_REG_PRETTY_PRINT # Print register bitfields in debug # output. Adds ~215k to driver. options ADAPTIVE_GIANT # Giant mutex is adaptive. device apic # I/O APIC # Bus support. Do not remove isa, even if you have no isa slots device isa device eisa device pci # Floppy drives device fdc # ATA and ATAPI devices device ata device atadisk # ATA disk drives device ataraid # ATA RAID drives device atapicd # ATAPI CDROM drives device atapifd # ATAPI floppy drives device atapist # ATAPI tape drives options ATA_STATIC_ID # Static device numbering # SCSI Controllers device ahb # EISA AHA1742 family device ahc # AHA2940 and onboard AIC7xxx devices device ahd # AHA39320/29320 and onboard AIC79xx devices device amd # AMD 53C974 (Tekram DC-390(T)) device isp # Qlogic family device mpt # LSI-Logic MPT-Fusion #device ncr # NCR/Symbios Logic device sym # NCR/Symbios Logic (newer chipsets + those of `ncr') device trm # Tekram DC395U/UW/F DC315U adapters device adv # Advansys SCSI adapters device adw # Advansys wide SCSI adapters device aha # Adaptec 154x SCSI adapters device aic # Adaptec 15[012]x SCSI adapters, AIC-6[23]60. device bt # Buslogic/Mylex MultiMaster SCSI adapters device ncv # NCR 53C500 device nsp # Workbit Ninja SCSI-3 device stg # TMC 18C30/18C50 # SCSI peripherals device scbus # SCSI bus (required for SCSI) device ch # SCSI media changers device da # Direct Access (disks) device sa # Sequential Access (tape etc) device cd # CD device pass # Passthrough device (direct SCSI access) device ses # SCSI Environmental Services (and SAF-TE) # RAID controllers interfaced to the SCSI subsystem device amr # AMI MegaRAID device asr # DPT SmartRAID V, VI and Adaptec SCSI RAID device ciss # Compaq Smart RAID 5* device dpt # DPT Smartcache III, IV - See NOTES for options device hptmv # Highpoint RocketRAID 182x device iir # Intel Integrated RAID device ips # IBM (Adaptec) ServeRAID device mly # Mylex AcceleRAID/eXtremeRAID device twa # 3ware 9000 series PATA/SATA RAID # RAID controllers device aac # Adaptec FSA RAID device aacp # SCSI passthrough for aac (requires CAM) device ida # Compaq Smart RAID device mlx # Mylex DAC960 family device pst # Promise Supertrak SX6000 device twe # 3ware ATA RAID # atkbdc0 controls both the keyboard and the PS/2 mouse device atkbdc # AT keyboard controller device atkbd # AT keyboard device psm # PS/2 mouse device vga # VGA video card driver device splash # Splash screen and screen saver support # syscons is the default console driver, resembling an SCO console device sc # Enable this for the pcvt (VT220 compatible) console driver #device vt #options XSERVER # support for X server on a vt console #options FAT_CURSOR # start with block cursor device agp # support several AGP chipsets # Floating point support - do not disable. device npx # Power management support (see NOTES for more options) #device apm # Add suspend/resume support for the i8254. device pmtimer # PCCARD (PCMCIA) support # PCMCIA and cardbus bridge support device cbb # cardbus (yenta) bridge device pccard # PC Card (16-bit) bus device cardbus # CardBus (32-bit) bus # Serial (COM) ports device sio # 8250, 16[45]50 based serial ports # Parallel port device ppc device ppbus # Parallel port bus (required) device lpt # Printer device plip # TCP/IP over parallel device ppi # Parallel port interface device #device vpo # Requires scbus and da # If you've got a "dumb" serial or parallel PCI card that is # supported by the puc(4) glue driver, uncomment the following # line to enable it (connects to the sio and/or ppc drivers): #device puc # PCI Ethernet NICs. device de # DEC/Intel DC21x4x (``Tulip'') device em # Intel PRO/1000 adapter Gigabit Ethernet Card device ixgb # Intel PRO/10GbE Ethernet Card device txp # 3Com 3cR990 (``Typhoon'') device vx # 3Com 3c590, 3c595 (``Vortex'') # PCI Ethernet NICs that use the common MII bus controller code. # NOTE: Be sure to keep the 'device miibus' line in order to use these NICs! device miibus # MII bus support device bfe # Broadcom BCM440x 10/100 Ethernet device bge # Broadcom BCM570xx Gigabit Ethernet device dc # DEC/Intel 21143 and various workalikes device fxp # Intel EtherExpress PRO/100B (82557, 82558) device lge # Level 1 LXT1001 gigabit ethernet device nge # NatSemi DP83820 gigabit ethernet device pcn # AMD Am79C97x PCI 10/100 (precedence over 'lnc') device re # RealTek 8139C+/8169/8169S/8110S device rl # RealTek 8129/8139 device sf # Adaptec AIC-6915 (``Starfire'') device sis # Silicon Integrated Systems SiS 900/SiS 7016 device sk # SysKonnect SK-984x & SK-982x gigabit Ethernet device ste # Sundance ST201 (D-Link DFE-550TX) device ti # Alteon Networks Tigon I/II gigabit Ethernet device tl # Texas Instruments ThunderLAN device tx # SMC EtherPower II (83c170 ``EPIC'') device vge # VIA VT612x gigabit ethernet device vr # VIA Rhine, Rhine II device wb # Winbond W89C840F device xl # 3Com 3c90x (``Boomerang'', ``Cyclone'') # ISA Ethernet NICs. pccard NICs included. device cs # Crystal Semiconductor CS89x0 NIC # 'device ed' requires 'device miibus' device ed # NE[12]000, SMC Ultra, 3c503, DS8390 cards device ex # Intel EtherExpress Pro/10 and Pro/10+ device ep # Etherlink III based cards device fe # Fujitsu MB8696x based cards device ie # EtherExpress 8/16, 3C507, StarLAN 10 etc. device lnc # NE2100, NE32-VL Lance Ethernet cards device sn # SMC's 9000 series of Ethernet chips device xe # Xircom pccard Ethernet # ISA devices that use the old ISA shims #device le # Wireless NIC cards #device wlan # 802.11 support #device an # Aironet 4500/4800 802.11 wireless NICs. #device awi # BayStack 660 and others #device wi # WaveLAN/Intersil/Symbol 802.11 wireless NICs. #device wl # Older non 802.11 Wavelan wireless NIC. # Pseudo devices. device loop # Network loopback device mem # Memory and kernel memory devices device io # I/O device device random # Entropy device device ether # Ethernet support device sl # Kernel SLIP device ppp # Kernel PPP device tun # Packet tunnel. device pty # Pseudo-ttys (telnet etc) device md # Memory "disks" device gif # IPv6 and IPv4 tunneling device faith # IPv6-to-IPv4 relaying (translation) # The `bpf' device enables the Berkeley Packet Filter. # Be aware of the administrative consequences of enabling this! device bpf # Berkeley packet filter # USB support device uhci # UHCI PCI->USB interface device ohci # OHCI PCI->USB interface device usb # USB Bus (required) #device udbp # USB Double Bulk Pipe devices device ugen # Generic device uhid # "Human Interface Devices" device ukbd # Keyboard device ulpt # Printer device umass # Disks/Mass storage - Requires scbus and da device ums # Mouse device urio # Diamond Rio 500 MP3 player device uscanner # Scanners # USB Ethernet, requires mii device aue # ADMtek USB Ethernet device axe # ASIX Electronics USB Ethernet device cue # CATC USB Ethernet device kue # Kawasaki LSI USB Ethernet device rue # RealTek RTL8150 USB Ethernet # FireWire support device firewire # FireWire bus code device sbp # SCSI over FireWire (Requires scbus and da) device fwe # Ethernet over FireWire (non-standard!) *********************************************************** With best regards, P. Trifonov