LinuxQuestions.org
Visit Jeremy's Blog.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - General
User Name
Password
Linux - General This 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


Reply
  Search this Thread
Old 07-04-2001, 11:05 AM   #1
drjimstuckinwin
Member
 
Registered: Mar 2001
Location: Manchester UK
Distribution: Mainly Fedora
Posts: 496

Rep: Reputation: 30
what is it?


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
 
Old 07-04-2001, 12:10 PM   #2
rshaw
Senior Member
 
Registered: Apr 2001
Location: Perry, Iowa
Distribution: Mepis , Debian
Posts: 2,692

Rep: Reputation: 45
it's /dev/rtc (real time clock),
 
Old 07-04-2001, 12:14 PM   #3
drjimstuckinwin
Member
 
Registered: Mar 2001
Location: Manchester UK
Distribution: Mainly Fedora
Posts: 496

Original Poster
Rep: Reputation: 30
Interesting.
Do I need to mkdev rtc or something??
 
Old 07-04-2001, 02:22 PM   #4
rshaw
Senior Member
 
Registered: Apr 2001
Location: Perry, Iowa
Distribution: Mepis , Debian
Posts: 2,692

Rep: Reputation: 45
yes, then you have to do a mknod with a major number 10 (character devices,misc) minor number 135 (real time clock)

i don't know the exact syntax of the mknod command, try mknod --help for all the options.
 
Old 07-04-2001, 02:26 PM   #5
rshaw
Senior Member
 
Registered: Apr 2001
Location: Perry, Iowa
Distribution: Mepis , Debian
Posts: 2,692

Rep: Reputation: 45
i always take the easy(cowards?) way out and recompile with a 'y' instead of a 'm' for any troublemakers.
 
Old 07-04-2001, 02:50 PM   #6
jharris
Senior Member
 
Registered: May 2001
Location: Bristol, UK
Distribution: Slackware, Fedora, RHES
Posts: 2,243

Rep: Reputation: 47
Question Just a few thoughts...

Uhm...

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.

Jamie...
 
Old 07-04-2001, 03:02 PM   #7
drjimstuckinwin
Member
 
Registered: Mar 2001
Location: Manchester UK
Distribution: Mainly Fedora
Posts: 496

Original Poster
Rep: Reputation: 30
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
 
Old 07-04-2001, 03:07 PM   #8
mcleodnine
Senior Member
 
Registered: May 2001
Location: Left Coast - Canada
Distribution: s l a c k w a r e
Posts: 2,731

Rep: Reputation: 45
Quote:
Originally posted by rshaw
i always take the easy(cowards?) way out and recompile with a 'y' instead of a 'm' for any troublemakers.
It's my dirty little secret, too. Maybe there should be a support group. Fat kernels... <sigh>.
 
Old 07-05-2001, 03:12 PM   #9
isajera
Senior Member
 
Registered: Jun 2001
Posts: 1,635

Rep: Reputation: 45
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.
 
Old 07-05-2001, 06:32 PM   #10
drjimstuckinwin
Member
 
Registered: Mar 2001
Location: Manchester UK
Distribution: Mainly Fedora
Posts: 496

Original Poster
Rep: Reputation: 30
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
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off



LinuxQuestions.org > Forums > Linux Forums > Linux - General

All times are GMT -5. The time now is 05:56 AM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration