I figured this out by adding if_myk_load=YES to /boot/loader.conf. I
don't know if this is where it's supposed to go, but it works.
Now the million-dollar question: can I do a firmware upgrade without
loosing this entry in the /boot/loader.conf? I'm confident the .ko
files I copied to /boot/kernel won't get deleted during updates, but I
want to make sure that the /boot/loader.conf doesn't get overwritten.
Otherwise, I'll have a bunch of pissed off clients and a trip to our
colocation on my next update. :)
--Bennett
Bennett Lee wrote:
OK, after many problems, like couldn't install because of no known
NICs, installing NICs in a 1U case with no riser, figuring out how
to mount, if_myk.ko requiring libmbpool.ko, etc., I finally got the
drivers installed with kldload and they appear to work.
Until I rebooted. The drivers don't reload. What to do I need to
change in order to get them to install permanently?
--Bennett
Bill Marquette wrote:
Probably easiest to load them onto a USB keyfob and mount it after
boot. Then kldload the if_myk.ko module.
--Bill
On 9/25/07, Bennett Lee [EMAIL PROTECTED] wrote:
I've got a new motherboard with quad-GB LANs that all use Marvell
8056, which isn't supported by pfSense/FreeBSD. I d/l Marvell's
Yukon
FreeBSD drivers, which supposedly support this board. Their .tgz
contains if_myk.ko, +CONTENTS, and myk.4.gz. Inside myk.4.gz is
myk.4.
How do I add these drivers to the LiveCD so I can try them out? Is
it
as easy as injecting the files into the CD into some particular
folder
and maybe adding them to a boot config file? (I hope so--haven't
done
anything in *nix since I wrote a crappy little client/server app
back
in college [many, many, many] years ago.)
--Bennett
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
