The major-minor thing works this way:
- each device node had a internal number/code the kernel uses. If you type "ls -l /dev" you'll see all kinds of numbers.
- note there are 2 kind of devices: block devices; for example, /dev/hd.. and character devices; for example, /dev/tty.. Their codes are completely independent from each other.
if a device file is accessed, the kernel will use it's code to determine what device is being accessed. If a driver hasn't been loaded for it, the kernel will try to load it. (with modprobe off course)
The kernel knows about a lot of module names referring to the devices, but if it doesn't, it will try to load a "
type-major-
majornumber-
minornumber" module. In /etc/modules.conf, you can set an alias for this file. This is my modules.conf, it could be helpfull. After modifying modules.conf, you need to run
depmod -a
Code:
### APM
alias char-major-10-134 apm
### webcam (I use mod_quickcam instead)
alias quickcam off
### DRI (graphics accelerator)
alias char-major-226 fglrx
# Somehow detected :-s
alias char-major-178 off
alias sound-slot-1 off
alias sound-service-1-0 off
The "alias char-major-226 fglrx" line tells modprobe that it should load fglrx (the ati driver) for the device no 226. The "alias .. off" disables the loading of a certain module.
I've been looking in
/usr/src/linux/Documentation/devices.txt, and the char-10-135 seams to correspond to "/dev/rtc"; the real time clock!
Have you been compiling your kernel without rtc support? Linux uses a software based clock, because it's more accurate, and stores the time into the real time clock at shutdown.
and there is another thing: what other programs are you running..? I've noticed that smartd for example, scans all possible ide devices when it's started. (until the S.M.A.R.T. capable devices are specified in it's configuration file)
use the information from
/usr/src/linux/Documentation/devices.txt to find out what devices are being probed.
How can I translate what a modprobe error means?
)
