> On Wed, 25 Jun 2008, Steven Stallion wrote:
>
>> Would it be possible to obtain a version of the SUNWstc-netperf2
>> package?
>
> How did you install your test suites?
>
> There's a helper script that gets the netperf sources and builds them.
>
> I thought the latest stuff has that installed after you run it...I could
> be wrong.

I followed the instructions provided on the NICDRV page; in the
documentation it mentioned that if you are external to Sun you have to
download and build netperf yourself, which I did.

>> I've not changed anything on my end - the vast majority of my testing
>> outside of NICDRV is done against the 64-bit driver. Solaris 10 and
>> Nevada builds (up to snv_89 at least) do not have a 64-bit version of
>> dnet installed, which is what spurred my previous comment.
>
> If you don't have the 64-bit driver, you could be missing the entrie(s) in
> your prototype_i386. Do you have /kernel/drv/amd64/dnet in the package
> and/or build?

The problem isnt with onnv or my workspace - it builds both 32 and 64-bit
modules just fine. If you look at current installs of Solaris 10 versus
Solaris Nevada, the 64-bit version is missing:

# uname -a
SunOS global 5.10 Generic_137112-01 i86pc i386 i86pc
# find /kernel/drv -name 'dnet'
/kernel/drv/dnet

v.s.

# uname -a
SunOS prometheus 5.11 snv_89 i86pc i386 i86pc
# find /kernel/drv -name 'dnet'
/kernel/drv/amd64/dnet
/kernel/drv/dnet

It should also be noted that the inclusion of the 64-bit version of dnet
is relatively recent; IIRC snv_78 had it missing as well.

>> Beyond that, I will do my best to get NICDRV to play nice with the
>> non-SUNW netperf (assuming I will be unable to get my hands
>> onSUNWstc-netperf2).
>
> Have you run this wrapper to install?
>
> http://www.opensolaris.org/os/community/device_drivers/auto_nicdrv_0521.tar.bz2
>

Nope, but I will :) Hopefully this will take care of the problem.

Thanks!

Steve

_______________________________________________
driver-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/driver-discuss

Reply via email to