Re: modprobe: Cannot locate module char-major-10
"Jeroen N. Witmond" <[EMAIL PROTECTED]> writes: > I have searched the mailing list archives for this problem, and I > understand it can be solved by aliasing module char-major-10 to off, but > I would like to understand what is going on. (It is not really a > problem, because in spite of the message everything seems to work.) [snip] > In human language: The Debian 2.0.34 configured the serial support as a > module, whereas I included it into the 2.0.36 kernel itself. It seems > that, even when the serial support is included into the kernel, > 'somebody' still wants to access it as a module, but I can't find who, > where and why. Serial ports are on char-major-4; see "ls -l /dev/ttyS0": crw-rw 1 root dialout4, 64 Feb 10 1998 /dev/ttyS0 major ^ ^^ minor char-major-10 is misc devices such as psaux, watchdog, apm and nvram - "cat /proc/misc" should list the ones you're using. Presumably something is trying to access one of the misc devices. You might be able to get some idea of what's happening with: $ cd /dev $ ls -ltur [...] crw-rw 1 uucp dialout4, 65 Jan 3 10:32 ttyS1 crw--- 1 root sys 10, 1 Jan 3 11:53 psaux prw-r--r-- 1 root root0 Jan 3 11:55 xconsole| [...] crw-rw-rw- 1 root root 2, 1 Jan 3 11:58 ptyp1 crw--w 1 careytty3, 1 Jan 3 11:58 ttyp1 crw--w--w- 1 root root 4, 7 Jan 3 11:58 tty7 $ -- Carey Evans http://home.clear.net.nz/pages/c.evans/ Larry froze. Was the bag a trap? He could see the way in, but the other end appeared to be sealed.
Re: modprobe: Cannot locate module char-major-10
"Jeroen N. Witmond" <[EMAIL PROTECTED]> writes: > The problem appeared on my box when I upgraded from the Debian hamm > kernel 2.0.34 to a 2.0.36 kernel straight from linux. The only > relevent difference in the configuration of these kernels seems to > be: > > diff -u /boot/config-2.0.34 /usr/src/linux-2.0.36/.config > # > # Character devices > # > -CONFIG_SERIAL=m > +CONFIG_SERIAL=y > > In human language: The Debian 2.0.34 configured the serial support > as a module, whereas I included it into the 2.0.36 kernel itself. > It seems that, even when the serial support is included into the > kernel, 'somebody' still wants to access it as a module, but I can't > find who, where and why. > > Can somebody explain what is going on? Thanks in advance. Please check the contents of your /etc/modules file (the comments at the begin should explain its purpose). Torsten -- Homepage: http://www.in-berlin.de/User/myrkr
modprobe: Cannot locate module char-major-10
I have searched the mailing list archives for this problem, and I understand it can be solved by aliasing module char-major-10 to off, but I would like to understand what is going on. (It is not really a problem, because in spite of the message everything seems to work.) The problem appeared on my box when I upgraded from the Debian hamm kernel 2.0.34 to a 2.0.36 kernel straight from linux. The only relevent difference in the configuration of these kernels seems to be: diff -u /boot/config-2.0.34 /usr/src/linux-2.0.36/.config # # Character devices # -CONFIG_SERIAL=m +CONFIG_SERIAL=y In human language: The Debian 2.0.34 configured the serial support as a module, whereas I included it into the 2.0.36 kernel itself. It seems that, even when the serial support is included into the kernel, 'somebody' still wants to access it as a module, but I can't find who, where and why. Can somebody explain what is going on? Thanks in advance. -- Jeroen N. Witmond ( mailto:[EMAIL PROTECTED] http://www.xs4all.nl/~jnw/ ) This message was composed in a Micro$oft-free environment.
