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: ~~~~ USB Human Interface Device (HID) Configuration General HID Configuration There are two options for using a USB mouse or a USB keyboard - the standalone Boot Protocol (HIDBP) way and the full featured HID driver way. The Boot Protocol way is generally inferior, and this document describes the full featured way. The Boot Protocol way may be appropriate for embedded systems and other systems with resource constraints and no real need for the full keyboard and mouse capabilities. It is important to remember that the HID driver handles those devices (or actually those interfaces on each device) that claim to comply with the Human Interface Device (HID) specification. However the HID specification doesn't say anything about what the HID driver should do with information received from a HID device, or where the information that is sent to a device comes from, since this is obviously dependent on what the device is supposed to be doing, and what the operating system is. Linux (at the operating system kernel level) supports four interfaces to a HID device - keyboard, mouse, joystick and a generic interface, known as the event interface. These are implemented by the Input device level. HID Mouse Configuration In the kernel configuration stage, you need to turn on USB Human Interface Device (HID) support in the USB support and Mouse Support in the Input core support. You don't need to worry about the screen resolution entries for a normal mouse - these are for mouse-like devices such as a graphics tablet. Do not turn on USB HIDBP Mouse support. Perform the normal kernel rebuild and installation steps. If you are installing as modules, you need to load the input.o, hid.o and mousedev.o modules. ~~~~ there is no input.o or even input.ko in the mouse or usb source tree let alone module library tree. Ruben
-- kr -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-- http://www.mrbrklyn.com - Interesting Stuff http://www.nylxs.com - Leadership Development in Free Software So many immigrant groups have swept through our town that Brooklyn, like Atlantis, reaches mythological proportions in the mind of the world - RI Safir 1998 http://fairuse.nylxs.com DRM is THEFT - We are the STAKEHOLDERS - RI Safir 2002 "Yeah - I write Free Software...so SUE ME" "The tremendous problem we face is that we are becoming sharecroppers to our own cultural heritage -- we need the ability to participate in our own society." "> I'm an engineer. I choose the best tool for the job, politics be damned.< You must be a stupid engineer then, because politcs and technology have been attached at the hip since the 1st dynasty in Ancient Egypt. I guess you missed that one." © Copyright for the Digital Millennium -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org