Linux - GeneralThis Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then this is the place.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Hello all
since recompiling my 2.4.2 kernel, I get an annoying message at boot time. Just as the machine enters non interactive start up, and begins starting services, I get...
Modprobe failed to locate module CHAR MAJOR 10-135
I have no idea what this is, and the system seems to work fine.
Can anyone tell me what it is, and how to get rid of the error?
Regards
Jim
I'm not so sure that your problem is not having the entry in /dev - have you changed /etc/modules.conf at all? It sounds more like modprobe is trying to find a module called CHAR MAJOR 10-135 which ain't gonna exist, rather than attemptig to load a module that fails becuase it can't find CHAR MAJOR 10-135 if you see what I'm getting at.
AFAIK it shouldn't make any difference wether you put code in as a module or in the kernel proper, if the entry it expects in /dev/ ain't there then you'll have problems, although you won't get the error message through modprobe. Having said that as rshaw has mentioned putting stuff in the kernel does sometimes seem to get around the hassle associated with some modules...
Actually - just thought... if you had this code in the kernel before and it was giving you errors you might not have reliased if it wasn't something that was logged, however the same code being loaded by modprobe might produce an error that is then reported back by modprobe... uhm... that does sound a little unlikely though.
HTH however having read it back to myself it seems a little odd.
Hmmmm
I too am a little confused by this! I don't recall anything about rtc in the xconfig setup screens, and I compiled just about everything I wanted directly into the kernel. I would have thought rtc should be an automatic part of the system.
Will tinker when I get back to my RH machine.
Jim
this is just a note, but if you upgraded from a 2.2.x kernel to the 2.4, then you need to get the updated modutils. the 2.2 kernel uses a different module... architecture or something. i'm not perfectly sure what it is, but the two kernels identify modules differently, and the old modutils (lsmod, insmod, ect...) will bring up error messages, but the system will still work in most cases. i had this same type of problem until i updated my modutils, but it worked perfectly after that, and no annoying messages.
Hi
I updated the modutils as per the changes doc, so hopefully that's not it. Not got back to this yet: Girlfriend moving into new flat, work etc! System works, so i guess there's no massive hurry.
Jim
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.