Can't locate module /dev/rtc

pjp · Posted: Wed Mar 12, 2003 7:51 pm Post subject:

Moved from Installing Gentoo.
_________________
lolgov. 'cause where we're going, you don't have civil liberties.

In Loving Memory
1787 - 2008

azote · Guru Joined: 17 Sep 2002 Posts: 414

plate · Posted: Wed Mar 12, 2003 11:55 pm Post subject:

Martin Schlemmer is on the case. Thanks for filing that bug report, bsolar!

Just wondering why modprobe gets invoked with all these non-existent modules to begin with...

bsolar · Bodhisattva Joined: 12 Jan 2003 Posts: 2764

plate · Posted: Thu Mar 13, 2003 3:12 am Post subject:

Just you, I suppose. I've been using the same avatar since the time I joined, didn't even change it when they made me a moderator...

But seriously, does anyone know why modprobe is calling all those modules nobody wants or needs?

Azarah · Retired Dev Joined: 20 Jun 2002 Posts: 81

It is harmless (except for filling up your logs :twisted:

).

Problem though is that with devfsd-1.3.25 (not 1.3.25-r[12]) modprobe from
module-init-tools output a lot of garbage (pretty much what you get in your
logs) to console

The devfsd-1.3.25-r[12] is thus more for linux-2.5
users until I can figure out why modprobe from module-init-tools behave
like this, and modprobe from modutils do not.

So, please just downgrade to 1.3.25, or ignore the logs for now :wink:

Azarah · Retired Dev Joined: 20 Jun 2002 Posts: 81

stustill · Posted: Fri Mar 14, 2003 7:38 pm Post subject:

I am getting exactly the same error, with one MAJOR difference! I cannot even log into my machine. It reboots as soon as it reaches a log in prompt, be it an x login prompt or a console login prompt! What should I do, arghh?

Stu

plate · Posted: Sat Mar 15, 2003 12:47 am Post subject:

Stustill, it's not an error that could lead to a reboot, it's just a message from modprobe. Nothing to do with your problem, I suggest you post this elsewhere.

bsolar · Bodhisattva Joined: 12 Jan 2003 Posts: 2764

Only to inform that -r3 solves the problem (the error messages; I agree that stustill problem is another).
_________________
I may not agree with what you say, but I'll defend to the death your right to say it.

di1bert · l33t Joined: 16 May 2002 Posts: 963 Location: Oslo, Norway

I just updated world (and devfsd) and the problem was rooted out and fixed

I love it when things get fixed quickly. Got my nice little Gentoo box back

Gentoo > all

di1bert (~matt)
_________________
choff.

b0fh · Guru Joined: 16 Jun 2003 Posts: 423

luugin · n00b Joined: 10 May 2003 Posts: 69

I just did an emerge -u system, and now i also have those weird modprobe messages hehe

azambuja · Posted: Tue Jun 24, 2003 3:52 am Post subject:

exactly the same for me... whats this all about???

cheers/thanx
_________________
"Slip inside the eye of your mind, don't you know you might find, a better place to play"

Arthur Vandelay · n00b Joined: 09 Jan 2003 Posts: 55

Havn't seen anyone mention this, but I got the same problem, plus a $hitload of others after I upgraded baselayout. I was able to fix everything except the /dev/rtc stuff.

azambuja · Posted: Wed Jun 25, 2003 7:18 pm Post subject:

im using the 2.4.20-r5 kernel and i recompiled it with RTC as <module>.
i got rid of the annoying errors...

cheers
_________________
"Slip inside the eye of your mind, don't you know you might find, a better place to play"

junco · n00b Joined: 09 Jun 2003 Posts: 41

just thought i would add that i have the same problem. I get numerous errors about missing modules in /dev/ on bootup. /dev/gpmctl and /dev/usblp* and /dev/usb/lp* are most of them. I am running devfsd-1.3.25-r3 (just remerged it today). I never had these problems before so i don't know whats up. is there a solution for this yet?

azambuja · Posted: Fri Jun 27, 2003 11:20 am Post subject:

try recompiling the kernel with <module> support to /dev/usblp*, ... , etc

cheers
_________________
"Slip inside the eye of your mind, don't you know you might find, a better place to play"

plate · Posted: Fri Jun 27, 2003 12:12 pm Post subject:

What on earth for? There's nothing wrong with his (or anybody's) kernel. We're talking about suppressing misleading messages here, not missing modules. Check Bugzilla for a more complete discussion of this phenomenon, e.g. here and there and everywhere...

Lord_Orion · Posted: Sun Jun 29, 2003 7:22 pm Post subject:

It seems not to be a devfsd bug... but I think more it is a baselayout bug...

I explain :

I had an error with /dev/ttyp0 module that could not be found ( I could put it away with an etc-update) you can do it manually if you comment the last lines that speak about ttyp0

I had another error too with /dev/gpmctl (this error I'm sure is te consequence of my baselayout update) I could put it away. I have just added

need local

in /etc/init.d/gpm

the last point is to put back th rtc errors (i have compiled the rtc support in my kernel theses errors appeared again...)

Lord_Orion · Posted: Sun Jun 29, 2003 8:17 pm Post subject:

I found a solution to kill this error message...

downgrade baselayout to version 1.8.5.9 :cry:

after an etc-update that's it...

b0fh · Guru Joined: 16 Jun 2003 Posts: 423

noob-question: how do I emerge an old version?

Lord_Orion · Posted: Mon Jun 30, 2003 1:21 pm Post subject:

emerge -p /usr/portage/sys-apps/baselayout/baselayout-1.8.5.9.ebuild

to see what emerge will do ...

emerge /usr/portage/sys-apps/baselayout/baselayout-1.8.5.9.ebuild

to do it...

Treek · n00b Joined: 25 Jun 2003 Posts: 9

yep. downgrading did the trick.

mrsteven · Veteran Joined: 04 Jul 2003 Posts: 1878

I really wonder when this bug gets fixed. Is anyone able to say when the new devfsd is released?