On Monday 04 April 2005 12:32, Christopher Hotchkiss wrote:
> On Apr 4, 2005 11:01 AM, Mario Lombardo <mario@alienscience.com> wrote:
> > On Monday 04 April 2005 00:37, Christopher Hotchkiss wrote:
> > > On Apr 4, 2005 12:27 AM, Mario Lombardo <mario@alienscience.com> wrote:
> > > > On Monday 04 April 2005 00:18, Max F Lang wrote:
> > > > > On Apr 3, 2005, at 11:02 PM, Mario Lombardo wrote:
> > > > > > On Sunday 03 April 2005 22:40, Christopher Hotchkiss wrote:
> > > > > >> On Apr 3, 2005 10:20 PM, Mario Lombardo <mario@alienscience.com>
> > > > > >>
> > > > > >> wrote:
> > > > > >>> Whenever I rebooted my box, I would lose my video driver:
> > > > > >>> I noticed no 'nvidia" module with lsmod, so I did the
> > > > > >>> following: modprobe nvidia and I got this as a result:
> > > > > >>
> > > > > >> Okay this is what I have in my /etc/modules.conf for nvidia:
> > > > > >> alias char-major-195 nvidia
> > > > > >> alias /dev/nvidiactl char-major-195
> > > > >
> > > > > We've had this discussion on other lists, like the JaxLug and LEAP
> > > > > lists, and seen this same problem stated elsewhere. For some dang
> > > > > reason, the module just doesn't load. My modules.conf agrees
> > > > > exactly with someone's whose nvidia modules loads just fine. And
> > > > > still it doesn't load for me.
> > > > >
> > > > > I finally gave up trying to figure it out, and just put the
> > > > > modprobe line into /etc/rc.d/rc.local (for Fedora), with an echo
> > > > > statement saying the module loaded. The only issue I face is when
> > > > > yum to pull updates which includes a new kernel, since now the new
> > > > > /lib/modules/<kernel-version> won't have the nvidia module. Just
> >
> > copy
> >
> > > > > it from its old location to its new, and modprobe. All will be
> >
> > well...
> >
> > > > > Max.
> > > >
> > > > So you're just adding
> > > >
> > > > modprobe nvidia
> > > >
> > > > to your /etc/rc.d/rc.local Yes? Too bad about modprobe.conf. I wonder
> > > > what the deal is. If I find anything on Nvidia, I'll be sure to pass
> >
> > it
> >
> > > > along.
> > > >
> > > > /mario
> > >
> > > Well upon further reflection there could be a couple issues:
> > > Are you using devfsd or udev?
> > > What distro are you using? (They might use a different file)
> > > I know mine, Gentoo, autogenerates my modules.conf from a different
> > > directory at bootup. It will clobber the modules.conf without warning.
> >
> > I know I'm using udev since I see it start up at boot time. I'm using
> > Fedora
> > Core 3.
> >
> > [user@baglady ~]$ ps ax | grep udev
> > 1404 ? S<s 0:00 udevd
> >
> > /mario
>
> grrr... I have never had a problem with udev in regards to this (devfsd is
> a different story). Does anyone have any other ideas? I'm not sure about
> Fedora internals.
I could just
modprobe nvidia
in rc.local, but I think that's clunky. I figure there's a better, cleaner
way.
/mario
-----------------------------------------------------------------------
This list is provided as an unmoderated internet service by Networked
Knowledge Systems (NKS). Views and opinions expressed in messages
posted are those of the author and do not necessarily reflect the
official policy or position of NKS or any of its employees.
This archive was generated by hypermail 2.1.3 : Fri Aug 01 2014 - 17:18:31 EDT