From owner-freebsd-hardware@FreeBSD.ORG Mon Mar 1 18:47:08 2010 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8B16A1065677 for ; Mon, 1 Mar 2010 18:47:08 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from cyrus.watson.org (cyrus.watson.org [65.122.17.42]) by mx1.freebsd.org (Postfix) with ESMTP id 5C50D8FC1C for ; Mon, 1 Mar 2010 18:47:08 +0000 (UTC) Received: from bigwig.baldwin.cx (66.111.2.69.static.nyinternet.net [66.111.2.69]) by cyrus.watson.org (Postfix) with ESMTPSA id 0D42D46B49; Mon, 1 Mar 2010 13:47:08 -0500 (EST) Received: from jhbbsd.localnet (smtp.hudson-trading.com [209.249.190.9]) by bigwig.baldwin.cx (Postfix) with ESMTPA id 42DF08A021; Mon, 1 Mar 2010 13:47:06 -0500 (EST) From: John Baldwin To: agh@coolrhaug.com Date: Mon, 1 Mar 2010 11:54:00 -0500 User-Agent: KMail/1.12.1 (FreeBSD/7.3-CBSD-20100217; KDE/4.3.1; amd64; ; ) References: <201002212231.12018.agh@coolrhaug.com> <201002261129.13746.jhb@freebsd.org> <201002271530.05185.agh@coolrhaug.com> In-Reply-To: <201002271530.05185.agh@coolrhaug.com> MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-15" Content-Transfer-Encoding: 7bit Message-Id: <201003011154.00827.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0.1 (bigwig.baldwin.cx); Mon, 01 Mar 2010 13:47:06 -0500 (EST) X-Virus-Scanned: clamav-milter 0.95.1 at bigwig.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-1.4 required=4.2 tests=AWL,BAYES_00 autolearn=ham version=3.2.5 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on bigwig.baldwin.cx Cc: kochetkov.andrew@gmail.com, Randy Chou , freebsd-hardware@freebsd.org Subject: Re: Intel DP45SG motherboard problem (amd64) X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 01 Mar 2010 18:47:08 -0000 On Saturday 27 February 2010 2:30:05 am Alastair Hogge wrote: > On Sat February 27 2010 00:29:13 John Baldwin wrote: > > On Friday 26 February 2010 6:15:28 am Alastair Hogge wrote: > > > On Thu February 25 2010 21:02:58 John Baldwin wrote: > > > > On Wednesday 24 February 2010 6:32:21 pm Alastair Hogge wrote: > > > > > On Wed February 24 2010 22:46:29 John Baldwin wrote: > > > > > > On Tuesday 23 February 2010 5:40:31 pm Alastair Hogge wrote: > > > > > > > On Wed February 24 2010 00:14:00 John Baldwin wrote: > > > > > > > > On Tuesday 23 February 2010 8:51:04 am Alastair Hogge wrote: > > > > > > > > > > > Hello John, > > > > > > > > > > > > > > > > > > > > > > In regards to an old email thread: > > > > > > > > > > > http://lists.freebsd.org/pipermail/freebsd- hardware/2009- > > > > > > > > > > > > > > > > > > > > June/thread.html#5887 > > > > > > > > > > > > > > > > > > > > > I've attached the i386 dmesg & "mptable device" from a > > > > > > > > > > > 9.0-CURRENT -r204168 system which still fails on booting > > > > > > > > > > > an amd64 CD. > > > > > > > > > > > > > > > > > > > > You need to build a custom amd64 kernel which includes > > > > > > > > > > "device > > > > > > > > > > > > mptable" > > > > > > > > > > > > > > > > and use that. You may need to set 'hint.acpi.0.disabled=1' > > > > > > > > > > as well to force ACPI to be disabled. > > > > > > > > > > > > > > > > > > OK, I've cross built an amd64 system and installed it on a > > > > > > > > > spare HDD. Once it booted I ran "mptable -verbose -dmesg > > > > > > > > > -grope" Here is the > > > > > > > > > > > > output: > > > > > > > > It appears that the new kernel works, yes? > > > > > > > > > > > > > > Yes > > > > > > > > > > > > > > > That should at least get you a > > > > > > > > working system now. > > > > > > > > > > > > > > Pretty exciting, however, it looks like that booting from an > > > > > > > installation CD is still problematic. > > > > > > > > > > > > Yes, but it is really odd that you do not have any ACPI tables. > > > > > > All 64-bit machines should have ACPI. > > > > > > > > > > > > > > I have no idea why the system does not provide ACPI > > > > > > > > tables. Is there a BIOS option to enable/disable ACPI perhaps? > > > > > > > > > > > > > > I can't find anything . > > > > > > > > > > > > Can you save the output of 'acpidump -d -t' to a file and post the > > > > URL? > > > > > > > > If the output is very short, you can just paste it inline into a > > > > > > reply. > > > > > > > > > > # acpidump -d -t > > > > > /* > > > > > RSD PTR: OEM=INTEL, ACPI_Rev=2.0x (2) > > > > > XSDT=0xcfd62e18, length=36, cksum=1 > > > > > */ > > > > > acpidump: XSDT is corrupted > > > > > > > > Hmm, the checksum for the XSDT is bad. You can try hacking > > > > src/usr.sbin/acpi/acpidump/acpi.c to disable the checksum check for the > > > > XSDT. Just look for the 'XSDT is corrupted' string in that source file > > > > and > > > > > > comment out the call to acpi_checksum(). Something like this: > > > > > > > > rsdp = (ACPI_TABLE_HEADER *)acpi_map_sdt(rp- > >XsdtPhysicalAddress); > > > > if (memcmp(rsdp->Signature, "XSDT", 4) != 0 /* || > > > > acpi_checksum(rsdp, rsdp->Length) != 0 */) > > > > errx(1, "XSDT is corrupted"); > > > > addr_size = sizeof(uint64_t); > > > > > > > > Then see if acpidump -d -t gets any further. > > > > > > Pleas see http://pastebin.ca/1811641 > > > You might noticed a different XSDT in the lastest dump. This is because I > > > moved the amd64 hdd to the other system and booted it from there. Both > > > > systems > > > > > are identical except for the video cards. > > > > > > > I would also look for a BIOS > > > > update perhaps, > > > > > > I've updated the BIOS, but still no luck. > > > > > > > and/or complain to your motherboard vendor that their BIOS > > > > is broken. > > > > > > Complaining has begun. > > > > Hmm, it looks like it is a common problem with this board actually. Try > > editing src/contrib/dev/acpica/include/acconfig.h and changing > > ACPI_CHECKSUM_ABORT to 0 instead of FALSE. > acpidump output doesn't change & the system still fails to boot with ACPI > enabled. This would not change acpidump output, just the kernel. Are you able to capture the boot messages with this kernel? Specifically, do you get any error messages from ACPI? Also, what happens if you find the code that uses ACPI_CHECKSUM_ABORT (I think in sys/contrib/acpica/tables/tbutils.c) and put #if 0 around that block? -- John Baldwin From owner-freebsd-hardware@FreeBSD.ORG Tue Mar 2 16:40:37 2010 Return-Path: Delivered-To: hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 15E12106566C for ; Tue, 2 Mar 2010 16:40:37 +0000 (UTC) (envelope-from ray@dlink.ua) Received: from dlink.ua (smtp.dlink.ua [193.138.187.146]) by mx1.freebsd.org (Postfix) with ESMTP id C7FC18FC18 for ; Tue, 2 Mar 2010 16:40:36 +0000 (UTC) Received: from gw ([192.168.10.10] helo=terran) by dlink.ua with esmtpsa (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.63) (envelope-from ) id 1NmUVp-0002T3-0U for hardware@freebsd.org; Tue, 02 Mar 2010 17:59:57 +0200 Date: Tue, 2 Mar 2010 18:02:42 +0200 From: Alexandr Rybalko To: hardware@freebsd.org Message-Id: <20100302180242.824f4726.ray@dlink.ua> Organization: D-Link X-Mailer: Sylpheed 2.7.1 (GTK+ 2.16.6; i386-portbld-freebsd8.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: Subject: Pseudo PHY and fake PHY ID X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 02 Mar 2010 16:40:37 -0000 Hi, I making correct driver for SoC switch which is Pseudo PHY on bfe interface. Someone can point me correct way to fake PHY ID for make it possible auto attach bfeswitch pseudo PHY driver? -- Alexandr Rybalko aka Alex RAY From owner-freebsd-hardware@FreeBSD.ORG Tue Mar 2 21:39:39 2010 Return-Path: Delivered-To: hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id BA4E1106566B for ; Tue, 2 Mar 2010 21:39:39 +0000 (UTC) (envelope-from ticso@cicely7.cicely.de) Received: from raven.bwct.de (raven.bwct.de [85.159.14.73]) by mx1.freebsd.org (Postfix) with ESMTP id A97A88FC14 for ; Tue, 2 Mar 2010 21:39:38 +0000 (UTC) Received: from mail.cicely.de ([10.1.1.37]) by raven.bwct.de (8.13.4/8.13.4) with ESMTP id o22LHEb5076068 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Tue, 2 Mar 2010 22:17:15 +0100 (CET) (envelope-from ticso@cicely7.cicely.de) Received: from cicely7.cicely.de (cicely7.cicely.de [10.1.1.9]) by mail.cicely.de (8.14.3/8.14.3) with ESMTP id o22LHCNU066614 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 2 Mar 2010 22:17:12 +0100 (CET) (envelope-from ticso@cicely7.cicely.de) Received: from cicely7.cicely.de (localhost [127.0.0.1]) by cicely7.cicely.de (8.14.2/8.14.2) with ESMTP id o22LHBV7078867; Tue, 2 Mar 2010 22:17:11 +0100 (CET) (envelope-from ticso@cicely7.cicely.de) Received: (from ticso@localhost) by cicely7.cicely.de (8.14.2/8.14.2/Submit) id o22LH3pq078866; Tue, 2 Mar 2010 22:17:03 +0100 (CET) (envelope-from ticso) Date: Tue, 2 Mar 2010 22:17:03 +0100 From: Bernd Walter To: Alexandr Rybalko Message-ID: <20100302211703.GP58319@cicely7.cicely.de> References: <20100302180242.824f4726.ray@dlink.ua> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20100302180242.824f4726.ray@dlink.ua> X-Operating-System: FreeBSD cicely7.cicely.de 7.0-STABLE i386 User-Agent: Mutt/1.5.11 X-Spam-Status: No, score=-4.4 required=5.0 tests=ALL_TRUSTED=-1.8, AWL=0.000, BAYES_00=-2.599 autolearn=ham version=3.2.5 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on spamd.cicely.de Cc: hardware@freebsd.org Subject: Re: Pseudo PHY and fake PHY ID X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: ticso@cicely.de List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 02 Mar 2010 21:39:39 -0000 On Tue, Mar 02, 2010 at 06:02:42PM +0200, Alexandr Rybalko wrote: > Hi, > > I making correct driver for SoC switch which is Pseudo PHY on bfe interface. > Someone can point me correct way to fake PHY ID for make it possible auto attach bfeswitch pseudo PHY driver? Has the switch an MDIO connection? I wrote the rtlswitch pseudo PHY driver for the RTL8305SC , which AFAIK still is the only one. The switch identifies without problem via identifiers, but it occupies multiple addresses and to avoid other drivers to claim the other IDs the rtlswitch driver claims all, but only attaches one time. ate0: mem 0xdffbc000-0xdffbffff irq 24 on atmelarm0 miibus0: on ate0 rlswitch0: PHY 0 on miibus0 rlswitch0: 100baseTX-FDX rlswitch1: PHY 1 on miibus0 rlswitch1: ignoring this PHY, non-zero instance device_attach: rlswitch1 attach returned 6 rlswitch2: PHY 2 on miibus0 rlswitch2: ignoring this PHY, non-zero instance device_attach: rlswitch2 attach returned 6 rlswitch3: PHY 3 on miibus0 rlswitch3: ignoring this PHY, non-zero instance device_attach: rlswitch3 attach returned 6 rlswitch4: PHY 4 on miibus0 rlswitch4: ignoring this PHY, non-zero instance device_attach: rlswitch4 attach returned 6 rlswitch5: PHY 5 on miibus0 rlswitch5: ignoring this PHY, non-zero instance device_attach: rlswitch5 attach returned 6 Beside from loocking strange it works fine this way. -- B.Walter http://www.bwct.de Modbus/TCP Ethernet I/O Baugruppen, ARM basierte FreeBSD Rechner uvm. From owner-freebsd-hardware@FreeBSD.ORG Wed Mar 3 10:25:45 2010 Return-Path: Delivered-To: hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id AC2E7106566C for ; Wed, 3 Mar 2010 10:25:45 +0000 (UTC) (envelope-from ray@dlink.ua) Received: from dlink.ua (smtp.dlink.ua [193.138.187.146]) by mx1.freebsd.org (Postfix) with ESMTP id 329888FC13 for ; Wed, 3 Mar 2010 10:25:44 +0000 (UTC) Received: from gw ([192.168.10.10] helo=terran) by dlink.ua with esmtpsa (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.63) (envelope-from ) id 1NmljV-00043t-Jk; Wed, 03 Mar 2010 12:23:13 +0200 Date: Wed, 3 Mar 2010 12:26:04 +0200 From: Alexandr Rybalko To: ticso@cicely.de Message-Id: <20100303122604.b8835c32.ray@dlink.ua> In-Reply-To: <20100302211703.GP58319@cicely7.cicely.de> References: <20100302180242.824f4726.ray@dlink.ua> <20100302211703.GP58319@cicely7.cicely.de> Organization: D-Link X-Mailer: Sylpheed 2.7.1 (GTK+ 2.16.6; i386-portbld-freebsd8.0) Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Cc: Bernd Walter , hardware@freebsd.org Subject: Re: Pseudo PHY and fake PHY ID X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 03 Mar 2010 10:25:45 -0000 On Tue, 2 Mar 2010 22:17:03 +0100 Bernd Walter wrote: >> On Tue, Mar 02, 2010 at 06:02:42PM +0200, Alexandr Rybalko wrote: >> > Hi, >> > >> > I making correct driver for SoC switch which is Pseudo PHY on bfe interface. >> > Someone can point me correct way to fake PHY ID for make it possible auto attach bfeswitch pseudo PHY driver? >> >> Has the switch an MDIO connection? Yes. >> I wrote the rtlswitch pseudo PHY driver for the RTL8305SC , which AFAIK still >> is the only one. >> The switch identifies without problem via identifiers, but it occupies multiple >> addresses and to avoid other drivers to claim the other IDs the rtlswitch >> driver claims all, but only attaches one time. My problem different, switch use one PHY address, but they (as I know) don`t provide identification. And I have to devices one on BCM5354 they have one bfe and one switch second on BCM5350 they have two bfe and one switch So I can`t only set hardcoded link bfe to bfeswitch. I need way for keeping auto probe and to know how fake switch id depend on outer info. >> >> ate0: mem 0xdffbc000-0xdffbffff irq 24 on atmelarm0 >> miibus0: on ate0 >> rlswitch0: PHY 0 on miibus0 >> rlswitch0: 100baseTX-FDX >> rlswitch1: PHY 1 on miibus0 >> rlswitch1: ignoring this PHY, non-zero instance >> device_attach: rlswitch1 attach returned 6 >> rlswitch2: PHY 2 on miibus0 >> rlswitch2: ignoring this PHY, non-zero instance >> device_attach: rlswitch2 attach returned 6 >> rlswitch3: PHY 3 on miibus0 >> rlswitch3: ignoring this PHY, non-zero instance >> device_attach: rlswitch3 attach returned 6 >> rlswitch4: PHY 4 on miibus0 >> rlswitch4: ignoring this PHY, non-zero instance >> device_attach: rlswitch4 attach returned 6 >> rlswitch5: PHY 5 on miibus0 >> rlswitch5: ignoring this PHY, non-zero instance >> device_attach: rlswitch5 attach returned 6 >> >> Beside from loocking strange it works fine this way. >> >> -- >> B.Walter http://www.bwct.de >> Modbus/TCP Ethernet I/O Baugruppen, ARM basierte FreeBSD Rechner uvm. -- Рыбалко Александр Консультант D-Link Украина From owner-freebsd-hardware@FreeBSD.ORG Wed Mar 3 12:05:55 2010 Return-Path: Delivered-To: hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id ECCB2106564A for ; Wed, 3 Mar 2010 12:05:55 +0000 (UTC) (envelope-from ticso@cicely7.cicely.de) Received: from raven.bwct.de (raven.bwct.de [85.159.14.73]) by mx1.freebsd.org (Postfix) with ESMTP id 59A718FC08 for ; Wed, 3 Mar 2010 12:05:54 +0000 (UTC) Received: from mail.cicely.de ([10.1.1.37]) by raven.bwct.de (8.13.4/8.13.4) with ESMTP id o23C5bJr034840 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Wed, 3 Mar 2010 13:05:37 +0100 (CET) (envelope-from ticso@cicely7.cicely.de) Received: from cicely7.cicely.de (cicely7.cicely.de [10.1.1.9]) by mail.cicely.de (8.14.3/8.14.3) with ESMTP id o23C5YJD001969 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 3 Mar 2010 13:05:34 +0100 (CET) (envelope-from ticso@cicely7.cicely.de) Received: from cicely7.cicely.de (localhost [127.0.0.1]) by cicely7.cicely.de (8.14.2/8.14.2) with ESMTP id o23C5Yub083264; Wed, 3 Mar 2010 13:05:34 +0100 (CET) (envelope-from ticso@cicely7.cicely.de) Received: (from ticso@localhost) by cicely7.cicely.de (8.14.2/8.14.2/Submit) id o23C5Xxt083263; Wed, 3 Mar 2010 13:05:33 +0100 (CET) (envelope-from ticso) Date: Wed, 3 Mar 2010 13:05:33 +0100 From: Bernd Walter To: Alexandr Rybalko Message-ID: <20100303120533.GV58319@cicely7.cicely.de> References: <20100302180242.824f4726.ray@dlink.ua> <20100302211703.GP58319@cicely7.cicely.de> <20100303122604.b8835c32.ray@dlink.ua> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20100303122604.b8835c32.ray@dlink.ua> X-Operating-System: FreeBSD cicely7.cicely.de 7.0-STABLE i386 User-Agent: Mutt/1.5.11 X-Spam-Status: No, score=-4.4 required=5.0 tests=ALL_TRUSTED=-1.8, AWL=0.000, BAYES_00=-2.599 autolearn=ham version=3.2.5 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on spamd.cicely.de Cc: Bernd Walter , ticso@cicely.de, hardware@freebsd.org Subject: Re: Pseudo PHY and fake PHY ID X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: ticso@cicely.de List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 03 Mar 2010 12:05:56 -0000 On Wed, Mar 03, 2010 at 12:26:04PM +0200, Alexandr Rybalko wrote: > On Tue, 2 Mar 2010 22:17:03 +0100 > Bernd Walter wrote: > > >> On Tue, Mar 02, 2010 at 06:02:42PM +0200, Alexandr Rybalko wrote: > >> > Hi, > >> > > >> > I making correct driver for SoC switch which is Pseudo PHY on bfe interface. > >> > Someone can point me correct way to fake PHY ID for make it possible auto attach bfeswitch pseudo PHY driver? > >> > >> Has the switch an MDIO connection? > > Yes. > > >> I wrote the rtlswitch pseudo PHY driver for the RTL8305SC , which AFAIK still > >> is the only one. > >> The switch identifies without problem via identifiers, but it occupies multiple > >> addresses and to avoid other drivers to claim the other IDs the rtlswitch > >> driver claims all, but only attaches one time. > > My problem different, switch use one PHY address, but they (as I know) don`t provide identification. > And I have to devices > one on BCM5354 they have one bfe and one switch > second on BCM5350 they have two bfe and one switch > So I can`t only set hardcoded link bfe to bfeswitch. > I need way for keeping auto probe and to know how fake switch id depend on outer info. I don't know details since there doesn't seem to be a public accessible datasheet, but it looks like it is a fixed combo, so I would suggest to take a look into the rl/rlphy implementation, which had to solve a similar problem. The RTL8201 PHY family exists in two different styles. One are discrete chips and others are embedded with MAC. The RTL8139 for example include an RTL8201, but unlike the discrete versions the intenal PHY won't identify. -- B.Walter http://www.bwct.de Modbus/TCP Ethernet I/O Baugruppen, ARM basierte FreeBSD Rechner uvm. From owner-freebsd-hardware@FreeBSD.ORG Thu Mar 4 09:14:28 2010 Return-Path: Delivered-To: hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C2C091065670 for ; Thu, 4 Mar 2010 09:14:28 +0000 (UTC) (envelope-from ray@dlink.ua) Received: from dlink.ua (smtp.dlink.ua [193.138.187.146]) by mx1.freebsd.org (Postfix) with ESMTP id 7D1A78FC25 for ; Thu, 4 Mar 2010 09:14:28 +0000 (UTC) Received: from gw ([192.168.10.10] helo=terran) by dlink.ua with esmtpsa (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.63) (envelope-from ) id 1Nn763-00025Z-In; Thu, 04 Mar 2010 11:11:55 +0200 Date: Thu, 4 Mar 2010 11:14:25 +0200 From: Alexandr Rybalko To: ticso@cicely.de Message-Id: <20100304111425.4e3c9e19.ray@dlink.ua> In-Reply-To: <20100303120533.GV58319@cicely7.cicely.de> References: <20100302180242.824f4726.ray@dlink.ua> <20100302211703.GP58319@cicely7.cicely.de> <20100303122604.b8835c32.ray@dlink.ua> <20100303120533.GV58319@cicely7.cicely.de> Organization: D-Link X-Mailer: Sylpheed 2.7.1 (GTK+ 2.16.6; i386-portbld-freebsd8.0) Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Cc: Bernd Walter , hardware@freebsd.org Subject: Re: Pseudo PHY and fake PHY ID X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 04 Mar 2010 09:14:28 -0000 On Wed, 3 Mar 2010 13:05:33 +0100 Bernd Walter wrote: >> On Wed, Mar 03, 2010 at 12:26:04PM +0200, Alexandr Rybalko wrote: >> > On Tue, 2 Mar 2010 22:17:03 +0100 >> > Bernd Walter wrote: >> > >> > >> On Tue, Mar 02, 2010 at 06:02:42PM +0200, Alexandr Rybalko wrote: >> > >> > Hi, >> > >> > >> > >> > I making correct driver for SoC switch which is Pseudo PHY on bfe interface. >> > >> > Someone can point me correct way to fake PHY ID for make it possible auto attach bfeswitch pseudo PHY driver? >> > >> >> > >> Has the switch an MDIO connection? >> > >> > Yes. >> > >> > >> I wrote the rtlswitch pseudo PHY driver for the RTL8305SC , which AFAIK still >> > >> is the only one. >> > >> The switch identifies without problem via identifiers, but it occupies multiple >> > >> addresses and to avoid other drivers to claim the other IDs the rtlswitch >> > >> driver claims all, but only attaches one time. >> > >> > My problem different, switch use one PHY address, but they (as I know) don`t provide identification. >> > And I have to devices >> > one on BCM5354 they have one bfe and one switch >> > second on BCM5350 they have two bfe and one switch >> > So I can`t only set hardcoded link bfe to bfeswitch. >> > I need way for keeping auto probe and to know how fake switch id depend on outer info. >> >> I don't know details since there doesn't seem to be a public accessible >> datasheet, but it looks like it is a fixed combo, so I would suggest to >> take a look into the rl/rlphy implementation, which had to solve a >> similar problem. >> The RTL8201 PHY family exists in two different styles. >> One are discrete chips and others are embedded with MAC. >> The RTL8139 for example include an RTL8201, but unlike the discrete >> versions the intenal PHY won't identify. >> >> -- >> B.Walter http://www.bwct.de >> Modbus/TCP Ethernet I/O Baugruppen, ARM basierte FreeBSD Rechner uvm. Not the same problem, but near. Thanks! -- Рыбалко Александр Консультант D-Link Украина From owner-freebsd-hardware@FreeBSD.ORG Sat Mar 6 15:08:33 2010 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 167431065670 for ; Sat, 6 Mar 2010 15:08:33 +0000 (UTC) (envelope-from ml@netfence.it) Received: from cp-out7.libero.it (cp-out7.libero.it [212.52.84.107]) by mx1.freebsd.org (Postfix) with ESMTP id CDCCB8FC16 for ; Sat, 6 Mar 2010 15:08:32 +0000 (UTC) Received: from soth.ventu (151.51.46.88) by cp-out7.libero.it (8.5.107) id 4B8FAAE300280CCB for freebsd-hardware@freebsd.org; Sat, 6 Mar 2010 15:57:12 +0100 Received: from alamar.ventu (alamar.ventu [10.1.2.18]) by soth.ventu (8.14.4/8.14.3) with ESMTP id o26Ev8Gu068518 for ; Sat, 6 Mar 2010 15:57:08 +0100 (CET) (envelope-from ml@netfence.it) Message-ID: <4B926D44.2050500@netfence.it> Date: Sat, 06 Mar 2010 15:57:08 +0100 From: Andrea Venturoli User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; it-IT; rv:1.9.1.8) Gecko/20100303 Thunderbird/3.0.3 MIME-Version: 1.0 To: freebsd-hardware@freebsd.org Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Subject: SATA regression with 7.2 X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 06 Mar 2010 15:08:33 -0000 Hello. I've got a box with a VIA VT8251 chipset and a single SATA HD, running 6.3/i386. I'm trying to upgrade it to 7.2, but, when booting with the new kernel, it won't detect any HD. In my BIOS I can set the controller to SATA, RAID or AHCI, but that doesn't matter. Here's what I see when booting 6.3: atapci0: port 0xe880-0xe887,0xe800-0xe803,0xe480-0xe487,0xe400-0xe403,0xe080-0xe08f mem 0xfebfec00-0xfebfefff irq 21 at device 15.0 on pci0 atapci0: AHCI Version 01.00 controller with 4 ports detected ata2: on atapci0 ata3: on atapci0 ata4: on atapci0 ata5: on atapci0 atapci1: port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xfc00-0xfc0f at device 15.1 on pci0 ata0: on atapci1 ata1: on atapci1 ... ad4: 152627MB at ata2-master SATA300 Trying to mount root from ufs:/dev/ad4s1a On 7.2 the output is roughly the same (I couldn't save it), but it won't find ad4 and prompt me for a boot device (with none available). Here's an extract from "pciconf -lv": atapci0@pci0:15:0: class=0x010601 card=0x33491106 chip=0x33491106 rev=0x00 hdr=0x00 vendor = 'VIA Technologies Inc' device = 'VT8251 VIA VT8251 AHCI RAID Controller' class = mass storage atapci1@pci0:15:1: class=0x01018a card=0x05711106 chip=0x05711106 rev=0x07 hdr=0x00 vendor = 'VIA Technologies Inc' device = 'VT82C586A/B/VT82C686/A/B/VT823x/A/C Bus Master IDE Controller' class = mass storage subclass = ATA Please help. bye & Thanks av. From owner-freebsd-hardware@FreeBSD.ORG Sat Mar 6 19:43:12 2010 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B8D84106566B for ; Sat, 6 Mar 2010 19:43:12 +0000 (UTC) (envelope-from mavbsd@gmail.com) Received: from mail-fx0-f223.google.com (mail-fx0-f223.google.com [209.85.220.223]) by mx1.freebsd.org (Postfix) with ESMTP id 416438FC1E for ; Sat, 6 Mar 2010 19:43:11 +0000 (UTC) Received: by fxm23 with SMTP id 23so3659805fxm.3 for ; Sat, 06 Mar 2010 11:43:08 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:sender:message-id:date:from :user-agent:mime-version:to:cc:subject:references:in-reply-to :content-type:content-transfer-encoding; bh=2YzJmGEdFafAjt8BjCdGHGINVu8TBfMGHQA+CfxgRFY=; b=cvFw0dWjjHTAXgboeCzVaZ3eU7LBll/9YiRekRkV3vk5acGwzOIXerRa5j9xgL8Me4 5vQBml99E5dRwS1qZphTeQrNAuvPe0hPhsAiOxzOc912r2ZgH7JNMGLeJXZUsqDWnCH4 WdVk3c2aGws0wA5X/yDLs5rq57tzXoUeKd0Gk= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=sender:message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; b=fkM1buevMr9a7aa8PHvE5jMEe683xHof6zY/GWhfgjTAXPSKtF6/BQ9nVYLx3VQTSz UhjN0LWQAeUcgpix4NT4o8rIRvDvhisE65xeXH4u652yIwrfNbONceS/fm289KNDZFzg 4cz0lT4O84eTX30G+/dNjOVCIGVGayuwnj6wc= Received: by 10.87.63.22 with SMTP id q22mr4323028fgk.2.1267904588286; Sat, 06 Mar 2010 11:43:08 -0800 (PST) Received: from mavbook.mavhome.dp.ua (pc.mavhome.dp.ua [212.86.226.226]) by mx.google.com with ESMTPS id 15sm2004090fxm.8.2010.03.06.11.43.07 (version=SSLv3 cipher=RC4-MD5); Sat, 06 Mar 2010 11:43:07 -0800 (PST) Sender: Alexander Motin Message-ID: <4B92B048.1030805@FreeBSD.org> Date: Sat, 06 Mar 2010 21:43:04 +0200 From: Alexander Motin User-Agent: Thunderbird 2.0.0.23 (X11/20091212) MIME-Version: 1.0 To: Andrea Venturoli References: <1267899785.00226614.1267888204@10.7.7.3> In-Reply-To: <1267899785.00226614.1267888204@10.7.7.3> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Cc: freebsd-hardware@freebsd.org Subject: Re: SATA regression with 7.2 X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 06 Mar 2010 19:43:12 -0000 Andrea Venturoli wrote: > I've got a box with a VIA VT8251 chipset and a single SATA HD, running > 6.3/i386. > I'm trying to upgrade it to 7.2, but, when booting with the new kernel, > it won't detect any HD. > In my BIOS I can set the controller to SATA, RAID or AHCI, but that > doesn't matter. > > Here's what I see when booting 6.3: > > atapci0: port > 0xe880-0xe887,0xe800-0xe803,0xe480-0xe487,0xe400-0xe403,0xe080-0xe08f > mem 0xfebfec00-0xfebfefff irq 21 at device 15.0 on pci0 > atapci0: AHCI Version 01.00 controller with 4 ports detected > ata2: on atapci0 > ata3: on atapci0 > ata4: on atapci0 > ata5: on atapci0 > atapci1: port > 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xfc00-0xfc0f at device 15.1 on pci0 > ata0: on atapci1 > ata1: on atapci1 > ... > ad4: 152627MB at ata2-master SATA300 > Trying to mount root from ufs:/dev/ad4s1a > > On 7.2 the output is roughly the same (I couldn't save it), but it won't > find ad4 and prompt me for a boot device (with none available). To get more info you may try to boot with verbose kernel messages enabled. Also as soon as you are updating, I would suggest you to try new 7.3, or even better 8-STABLE. 8-STABLE includes significant changes in ATA subsystem, including completely new AHCI driver ahci(4). -- Alexander Motin