Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 24 Oct 2009 12:18:43 -0500
From:      Kevin Kinsey <kdk@daleco.biz>
To:        kalin m <kalin@el.net>
Cc:        Adam Vande More <amvandemore@gmail.com>, Polytropon <freebsd@edvax.de>, freebsd-questions <freebsd-questions@freebsd.org>
Subject:   Re: freebsd forgets root password
Message-ID:  <4AE336F3.9040107@daleco.biz>
In-Reply-To: <4AE27939.20303@el.net>
References:  <4AE250BF.8010902@el.net>	<6201873e0910231846j4386baa9g3bd3eab21fed1727@mail.gmail.com>	<4AE26337.8030001@el.net>	<20091024054227.e3a4a3bb.freebsd@edvax.de> <4AE27939.20303@el.net>

next in thread | previous in thread | raw e-mail | index | archive | help
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.

HTH,

Kevin Kinsey



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4AE336F3.9040107>