From owner-freebsd-questions@FreeBSD.ORG Sat Oct 24 23:29:53 2009 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id CBEF3106566B for ; Sat, 24 Oct 2009 23:29:53 +0000 (UTC) (envelope-from kalin@el.net) Received: from mail.el.net (mail.el.net [74.1.12.120]) by mx1.freebsd.org (Postfix) with ESMTP id 27B628FC08 for ; Sat, 24 Oct 2009 23:29:52 +0000 (UTC) Received: (qmail 32296 invoked by uid 1008); 25 Oct 2009 00:43:43 -0000 Received: from unknown (HELO kalins-macbook-pro.local) (kalin@el.net@24.193.246.51) by mail.el.net with ESMTPA; 25 Oct 2009 00:43:43 -0000 Message-ID: <4AE38D5B.3080903@el.net> Date: Sat, 24 Oct 2009 19:27:23 -0400 From: kalin m User-Agent: Thunderbird 2.0.0.23 (Macintosh/20090812) MIME-Version: 1.0 To: Kevin Kinsey References: <4AE250BF.8010902@el.net> <6201873e0910231846j4386baa9g3bd3eab21fed1727@mail.gmail.com> <4AE26337.8030001@el.net> <20091024054227.e3a4a3bb.freebsd@edvax.de> <4AE27939.20303@el.net> <4AE336F3.9040107@daleco.biz> In-Reply-To: <4AE336F3.9040107@daleco.biz> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Adam Vande More , Polytropon , freebsd-questions Subject: Re: freebsd forgets root password X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 24 Oct 2009 23:29:53 -0000 Kevin Kinsey wrote: > kalin m wrote: >> """ >> does anybody here know if freebsd has a driver for Marvell 88E8057 >> nic chip? >> >> according to the kernel list of drivers (7.2) marvell chips are >> driven by the msk driver. but it doesn't show up in pciconf, dmesg or >> sysinstall.... >> strangely enough 88E8057 is not in the list in man msk. although >> 88E8056 and 88E8058 are. is this just bad luck?! >> """ > > No, as I mentioned earlier, it appears the driver author didn't have > or wasn't aware of this chipset. It's quite possible, based on the > cursory glance I gave to the headers of the file, that it didn't exist > at the time it was written. There are obviously some issues with > licensing or disclosure or what-not. > > See /usr/src/dev/msk/if_msk.c, down about line 210-220 where > these are defined. You can, I think, very carefully, attempt > to add this device to that file and rebuild your kernel, I think, > and then see if it works. I'm thinking OOTOMH the trick would be getting > the right DEVICEID string in there. > > Barring that, you might speak very sweetly to the author of the driver, > perhaps offering $BEVERAGE and detailed information about the chip, and > see if he/she would attempt to conjure up the right code to make it work. thanks kevin... i did get an email from (i believe ) the author of the driver. so i'll be hopefully trying his patch on monday. and i have to get some files from HEAD. but it was very nice that he contacted me. i had to look up OOTOMH thought... thanks... > > HTH, > > Kevin Kinsey