SCIENTIFIC-LINUX-USERS Archives

October 2006

SCIENTIFIC-LINUX-USERS@LISTSERV.FNAL.GOV

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Miles O'Neal <[log in to unmask]>
Reply To:
Miles O'Neal <[log in to unmask]>
Date:
Mon, 16 Oct 2006 17:41:48 -0500
Content-Type:
text/plain
Parts/Attachments:
text/plain (25 lines)
We upgraded some of our SL304 systems to
SL305, but still get erroneous SM_UNMON request
messages in the logs, and occasional refusals
to mount via NFS and the automounter.

We thought the SL304 SDR kernel was built
exactly like the SL304 kernel, but apparently
not as on a certain set of systems it refuses
to see the builtin ethernet, whereas the
standard SL304 kernel sees it just fine.
(It's an nvidia onboard NIC for which we
installed a driver from the nvidia CDROM.)

We thought the patch in 304SDR kernels was
going to be in 305, but it seems not.  Does
anyone know for sure if it showed up in a
supported kernel in a later version of SL3?
Or is there a trick to making the 304SDR
kernel see the nvidia driver?  (The sections
in grub.conf are identical except for kernel
version.)

Thanks,
Miles

ATOM RSS1 RSS2