Mailinglist Archive: opensuse (3221 mails)

["K.R. Foley" <kr@xxxxxxxxxx>]

Ruben Safir wrote:
> On Fri, Nov 23, 2007 at 04:00:17PM -0600, K.R. Foley wrote:
> > Ruben Safir wrote:
> > > On Fri, Nov 23, 2007 at 01:03:35PM -0600, K.R. Foley wrote:
> > > > Ruben Safir wrote:
> > > > > Hello
> > > > >
> > > > > I've update my kernel to get it to function with new hardware and the 
> > > > > modules for my eepro100
> > > > > and USB mouse aren't working now.  Where is the scripts that initiate 
> > > > > these things so that I
> > > > > fix this.  It doesn't seem to be in the /etc/rc.d/ directory, or at least 
> > > > > I can't seem to find it with
> > > > > Grep.
> > > > >
> > > > > Ruben
> > > > What version of the kernel?
> > > >
> > > > I believe the problem that you are having is probably the difference in
> > > > the way devices are detected and initialized (ie. udev). I had similar
> > > > problems after going past a certain kernel version (maybe 2.6.18) on
> > > > 9.3. I was able to work around this problem by adding the device drivers
> > > > for the devices to the MODULES_LOADED_ON_BOOT="capability raw1394
> > > > video1394 sis900" in /etc/sysconfig/kernel.
> > >
> > > I added eepro100 which is a working module into the initrd line of the 
> > > kernel file, but the system still isn't initializing the
> > > ethernet card prior to me running modprobe on the command line.  I looked 
> > > into the config files under network and still find no 
> > > place where it does a probe for the card and loads modules.
> > >
> > > Any further thoughts?
> > Did you just add it to the INITRD line or did you add it to the
> > MODULES_LOADED_ON_BOOT line like I suggested above. If you add it to
> > that line there is no need to do a modprobe because the module gets
> > loaded every time. The script you are looking for is
> > /etc/init.d/network, but it doesn't do a modprobe. Udev is SUPPOSED to
> > cause the module to load when the hardware scan happens, but in newer
> > kernels things have changed.
>
> Thanks.  Your right.  The only thing is that currently that line is a blank
> string which means until now that system wasn't depending on that in order to
> run.  It's been loading the module from elsewhere.  I'm going to change that
> line for the network card.  The USB mouse, however, looks like a more
> complicated problem.  I found on the web the following howto instruction:

I understand that the line may have been blank before. However, there is
an incompatibility between the initialization on 9.3 and the newer
kernel. There is no easy fix for that.

As for the mouse, I have never had to specifically load a USB mouse
driver on my 9.3 system running newer kernels. You do however have to
have the kernel properly configured. How did you configure the kernel?
Did you start with your existing kernel config as a baseline? You can do
that by copying /boot/config-`uname -r` to srcdir/config and then do
'make oldconfig'.


-- 
        kr
-- 
To unsubscribe, e-mail: opensuse+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse+help@xxxxxxxxxxxx