From owner-freebsd-stable@FreeBSD.ORG Mon Jul 8 02:36:34 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 098E3E11 for ; Mon, 8 Jul 2013 02:36:34 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: from mail-pd0-x229.google.com (mail-pd0-x229.google.com [IPv6:2607:f8b0:400e:c02::229]) by mx1.freebsd.org (Postfix) with ESMTP id D56B71189 for ; Mon, 8 Jul 2013 02:36:33 +0000 (UTC) Received: by mail-pd0-f169.google.com with SMTP id y10so3602951pdj.14 for ; Sun, 07 Jul 2013 19:36:33 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:date:to:cc:subject:message-id:reply-to:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; bh=tU+2LNC4Hr2eWnbxN2H3p39aGf2pA8ZyRXDIzTmPK4M=; b=t1KSOOTUNWHPvzhd0sc0v+J9i2o2zeBfAK2Kop6G7fArtlhtDrk2eeJEMMcfFbGR4C SbGkOHmH9oN2KCl1skqaU6Oyxy0wczgQ5f0dpqBCF70k3082gvQ0KftgsWo+yECiRl4t 0Dnh1DJg7743wJyQEmS5PH4QjV1ZkYjqelNKyaWucVlICKpwOHPZ3pwLlZqZobZk0nmv puxzcXCALBQaf4+zl+oWQ0JDjVwX+37CU4ZcE+wN+SQeTri6IO6Pe27cLrYajrhV6MZo XDkpvx4iCi6CkFz/RK3H5m7b54kyjWv1pd9SgZIjcKCZ9qlAt/3dXreIKyHqOJ+4j+3G VGBA== X-Received: by 10.66.142.5 with SMTP id rs5mr13462732pab.168.1373250993492; Sun, 07 Jul 2013 19:36:33 -0700 (PDT) Received: from pyunyh@gmail.com (lpe4.p59-icn.cdngp.net. [114.111.62.249]) by mx.google.com with ESMTPSA id kc8sm19595699pbc.18.2013.07.07.19.36.29 for (version=TLSv1 cipher=RC4-SHA bits=128/128); Sun, 07 Jul 2013 19:36:32 -0700 (PDT) Received: by pyunyh@gmail.com (sSMTP sendmail emulation); Mon, 08 Jul 2013 11:36:28 +0900 From: Yonghyeon PYUN Date: Mon, 8 Jul 2013 11:36:27 +0900 To: Doug Hardie Subject: Re: Sanity Check on Mac Mini Message-ID: <20130708023627.GA4258@michelle.cdnetworks.com> References: <51CB1227-3A5F-4688-B48D-4D0E47A17572@lafn.org> <5138A742.3090200@wintek.com> <97F9BA96-A328-4EF9-8E39-A8160AF9EB7A@lafn.org> <71F173FA-CB9C-43B4-A702-ABA82268EA83@lafn.org> <428C87E0-7CF4-4664-9EF2-8CD582927AAB@lafn.org> <7F72BB49-8810-42A4-AC4F-9B6D3E61C6EB@lafn.org> <28915479-B712-4ED0-A041-B75F2F59FECA@lafn.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <28915479-B712-4ED0-A041-B75F2F59FECA@lafn.org> User-Agent: Mutt/1.4.2.3i Cc: "freebsd-stable@freebsd.org List" X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: pyunyh@gmail.com List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 08 Jul 2013 02:36:34 -0000 On Sun, Jul 07, 2013 at 05:56:09PM -0700, Doug Hardie wrote: > As I previously indicated, I have tested a couple more Minis and updated the instructions with what I learned. Here is the revised version: > [...] > 2.12.3 Rebuilding the kernel to support the Ethernet Interface > > Once the system has been rebooted, you will notice that ifconfig may not show the ethernet interface. There are at least two different chips being used for that interface. Some of the units work right out of the box. Others do not. I have two units and the only visible difference is the Part No. Part Nu. MC815LL/A appears to be the older unit and the bge interface worked on install. Part No MD387LL/A is newer and has the newer chips that require the driver update. > > If the bge interface does not show, then the bge driver needs to be updated to recognize the NIC. Mount the second memstick with the files retrieved earlier and move them into the kernel source. I used the following commands: > > cp -p brgphy.c /usr/src/sys/dev/mii > cp -p if_bgereg.h /usr/src/sys/dev/bge > cp -p if_bge.c /usr/src/sys/dev/bge > > then rebuild the kernel. Note the instructions here are for GENERIC, but you can use KERNCONF to specify a custom kernel. > > cd /usr/src > make buildkernel > make installkernel > > Reboot the server as before. Now ifconfig will show bge0 and it will work. The mini is now running a useable version of 9.1-Release. There are still some items remaining to be resolved: Updating the kernel with the recent security patches, Disabling Bluetooth and Wireless to save power, and unattended rebooting. These issues are still being addressed. > I'm not sure whether this bge(4) controller is sitting behind TB(Apple Thunderbolt) bridge. The Apple TB bridge has known performance issue and some BCM controllers have a work-around to mitigate it. The work-around is not enabled by default so I'm interested in bge(4) performance numbers on your box. If you can't get more than 920 ~ 930Mbps(950Mbps or higher with jumbo frame) please let me know. I didn't enable the work-around yet since it will hurt other BCM controllers when TB bridge is absent.