| View previous topic :: View next topic |
| Author |
Message |
bsolar
Bodhisattva
Joined: 12 Jan 2003
Posts: 2764
|
 Posted: Tue Mar 11, 2003 1:07 am Post subject: Can't locate module /dev/rtc |
 |
|
I had a system freeze and it did some damage...
At boot I got this:
| Code: | * Setting system clock to hardware clock [Local Time]... [ok]
modprobe: Can't locate module /dev/rtc [ok]
modprobe: Can't locate module /dev/misc/rtc [ok]
modprobe: Can't locate module /dev/rtc [ok]
modprobe: Can't locate module /dev/misc/rtc [ok] |
And when logging out I get LOTS of errors like that, but all referred to sound things...
I looked for that device but haven't found it.
How can I repair things (without doing a reinstall, if possible).
_________________
I may not agree with what you say, but I'll defend to the death your right to say it. |
|
| Back to top |
|
 |
scocou
Apprentice
Joined: 16 Aug 2002
Posts: 184
Location: Pacific NW, Canada
|
| Posted: Tue Mar 11, 2003 6:14 am Post subject: |
|
|
| Slow down there, no need to reinstall. It appears you're missing kernel support for your real-time-clock, or RTC. Personally I don't usually include support for it anyhow, but it's found in the character devices section of your kernel config if you need it. If that's all you have wrong, I would suggest recompiling your kernel and modules for a start. If that doesn't work report back... |
|
| Back to top |
|
|
bsolar
Bodhisattva
Joined: 12 Jan 2003
Posts: 2764
|
| Posted: Tue Mar 11, 2003 11:17 am Post subject: |
|
|
No, the kernel is the same as before the freeze. I recompiled it too and checked for that.
_________________
I may not agree with what you say, but I'll defend to the death your right to say it. |
|
| Back to top |
|
|
georgm
n00b
Joined: 10 Aug 2002
Posts: 30
Location: Germany
|
| Posted: Tue Mar 11, 2003 1:52 pm Post subject: |
|
|
I have the same problem. I startet my computer today and got lots of messages of missing modules in /dev ?!?.
Maybe a defect ebuild, but which one? I tried to emerge an older version of devfsd but no change... |
|
| Back to top |
|
|
bsolar
Bodhisattva
Joined: 12 Jan 2003
Posts: 2764
|
| Posted: Tue Mar 11, 2003 2:14 pm Post subject: |
|
|
Well I experienced this after a system freeze and I think was caused by that. I'm reinstalling now, since even if I can detect what's wrong I cannot find every possible corruption that happened with the freeze. I prefer a clean system...
If the problem is caused by a package, I'll notice since I'm going to reinstall everything.
_________________
I may not agree with what you say, but I'll defend to the death your right to say it. |
|
| Back to top |
|
|
georgm
n00b
Joined: 10 Aug 2002
Posts: 30
Location: Germany
|
| Posted: Tue Mar 11, 2003 2:24 pm Post subject: |
|
|
Hm, I had no crash...
Can I see anywhere what I've emerged yesterday? |
|
| Back to top |
|
|
bsolar
Bodhisattva
Joined: 12 Jan 2003
Posts: 2764
|
| Posted: Tue Mar 11, 2003 2:57 pm Post subject: |
|
|
| georgm wrote: | Hm, I had no crash...
Can I see anywhere what I've emerged yesterday? |
Check /var/log for the emerge log file.
_________________
I may not agree with what you say, but I'll defend to the death your right to say it. |
|
| Back to top |
|
|
georgm
n00b
Joined: 10 Aug 2002
Posts: 30
Location: Germany
|
| Posted: Tue Mar 11, 2003 3:09 pm Post subject: |
|
|
Nothing bad...
Here is an extract of my /var/log/critical/current:
| Code: |
Mar 11 15:58:28 [kde(pam_unix)] session opened for user georg by (uid=0)
Mar 11 15:58:29 [modprobe] modprobe: Can't locate module :0 which is needed for /dev/:0
Mar 11 15:58:29 [modprobe] modprobe: Can't locate module fd[0-1]* which is needed for /dev/fd[0-1]*
Mar 11 15:58:29 [modprobe] modprobe: Can't locate module * which is needed for /dev/floppy/*
Mar 11 15:58:29 [modprobe] modprobe: Can't locate module dsp* which is needed for /dev/dsp*
Mar 11 15:58:29 [modprobe] modprobe: Can't locate module dsp* which is needed for /dev/dsp*
Mar 11 15:58:29 [modprobe] modprobe: Can't locate module audio* which is needed for /dev/audio*
Mar 11 15:58:29 [modprobe] modprobe: Can't locate module mixer* which is needed for /dev/mixer*
Mar 11 15:58:29 [modprobe] modprobe: Can't locate module mixer* which is needed for /dev/mixer*
Mar 11 15:58:29 [modprobe] modprobe: Can't locate module sequencer* which is needed for /dev/sequencer*
Mar 11 15:58:29 [modprobe] modprobe: Can't locate module /dev/beep
Mar 11 15:58:29 [modprobe] modprobe: Can't locate module admm* which is needed for /dev/admm*
Mar 11 15:58:29 [modprobe] modprobe: Can't locate module adsp* which is needed for /dev/adsp*
Mar 11 15:58:29 [modprobe] modprobe: Can't locate module adsp* which is needed for /dev/adsp*
Mar 11 15:58:29 [modprobe] modprobe: Can't locate module aload* which is needed for /dev/aload*
Mar 11 15:58:29 [modprobe] modprobe: Can't locate module amidi* which is needed for /dev/amidi*
Mar 11 15:58:29 [modprobe] modprobe: Can't locate module amidi* which is needed for /dev/amidi*
Mar 11 15:58:29 [modprobe] modprobe: Can't locate module dmfm* which is needed for /dev/dmfm*
Mar 11 15:58:29 [modprobe] modprobe: Can't locate module /dev/sndstat
Mar 11 15:58:29 [modprobe] modprobe: Can't locate module /dev/sndstat
Mar 11 15:58:29 [modprobe] modprobe: Can't locate module /dev/ide/host0/bus1/target1/lun0/cd
Mar 11 15:58:29 [modprobe] modprobe: Can't locate module /dev/ide/host0/bus1/target0/lun0/cd
Mar 11 15:58:29 [modprobe] modprobe: Can't locate module /dev/ide/host0/bus0/target1/lun0/cd
Mar 11 15:58:29 [modprobe] modprobe: Can't locate module /dev/ide/host0/bus0/target0/lun0/cd
Mar 11 15:58:29 [modprobe] modprobe: Can't locate module /dev/rdvd
Mar 11 15:58:29 [modprobe] modprobe: Can't locate module * which is needed for /dev/ide/*
Mar 11 15:58:29 [modprobe] modprobe: Can't locate module /dev/pilot
Mar 11 15:58:29 [modprobe] modprobe: Can't locate module /dev/ls120
Mar 11 15:58:29 [modprobe] modprobe: Can't locate module /dev/scanner
Mar 11 15:58:29 [modprobe] modprobe: Can't locate module scanner* which is needed for /dev/usb/scanner*
Mar 11 15:58:29 [modprobe] modprobe: Can't locate module dc2xx* which is needed for /dev/usb/dc2xx*
Mar 11 15:58:29 [modprobe] modprobe: Can't locate module mdc800* which is needed for /dev/usb/mdc800*
Mar 11 15:58:29 [modprobe] modprobe: Can't locate module /dev/kbd
Mar 11 15:58:29 [modprobe] modprobe: Can't locate module js[0-9]* which is needed for /dev/js[0-9]*
Mar 11 15:58:29 [modprobe] modprobe: Can't locate module /dev/video
|
These are stupid tries, because I haven't nearly any of these devices... |
|
| Back to top |
|
|
georgm
n00b
Joined: 10 Aug 2002
Posts: 30
Location: Germany
|
| Posted: Tue Mar 11, 2003 4:33 pm Post subject: |
|
|
There are also messages like:
| Code: |
Mar 11 14:51:01 [modprobe] modprobe: Can't locate module /dev/s
Mar 11 14:51:05 [modprobe] modprobe: Safe mode parameter contains '='
Mar 11 14:51:05 [modprobe] modprobe: Safe mode parameter contains '='
Mar 11 14:51:06 [modprobe] modprobe: Can't locate module [sawfish-2.0] bash which is needed for /dev/[sawfish-2.0] bash
Mar 11 14:53:28 [modprobe] modprobe: Can't locate module [] bash which is needed for /dev/[] bash
Mar 11 14:55:28 [modprobe] modprobe: Can't locate module [] bash which is needed for /dev/[] bash
Mar 11 14:59:52 [kernel] portmap: server localhost not responding, timed out
Mar 11 14:59:52 [kernel] lockd_up: no pid, 2 users??
|
What the hell does these [] mean?
Any idea which ebuild might be guilty? |
|
| Back to top |
|
|
bsolar
Bodhisattva
Joined: 12 Jan 2003
Posts: 2764
|
| Posted: Tue Mar 11, 2003 4:35 pm Post subject: |
|
|
It might be a devfsd problem. Updated it recently?
_________________
I may not agree with what you say, but I'll defend to the death your right to say it. |
|
| Back to top |
|
|
georgm
n00b
Joined: 10 Aug 2002
Posts: 30
Location: Germany
|
| Posted: Tue Mar 11, 2003 4:39 pm Post subject: |
|
|
Yes, but there was no "etc-update"-message
And I downgraded to the last installed version without a change of the situation... |
|
| Back to top |
|
|
Mell
n00b
Joined: 16 Nov 2002
Posts: 26
Location: Germany
|
| Posted: Tue Mar 11, 2003 5:10 pm Post subject: |
|
|
I do have the same problems. I am not quite sure if it is due to an update of devfsd (1.3.25-r2) or a system crash both happened yesterday. Additional to these problems I am not able initialize the clock during boot anymore: "IOCTL not matching the device". The clock problem I could solve for now by adding "--directisa" to /etc/init.d/clock. Does anyone have another suggestion since it worked just until today without the "--directisa"-option?
Meanwhile I tried to downgrade devfsd and noticed the the package has a shutup-patch. Maybe the error messages are related to this? I am not envolved enough to see what this patch actually does...
 |
|
| Back to top |
|
|
georgm
n00b
Joined: 10 Aug 2002
Posts: 30
Location: Germany
|
| Posted: Tue Mar 11, 2003 5:15 pm Post subject: |
|
|
This patch is as far as I can see for 2.5-kernels:
| Code: |
emerge module-init-tools -p
These are the packages that I would merge, in order:
Calculating dependencies ...done!
[ebuild N ] sys-kernel/development-sources-2.5.64
[ebuild N ] sys-apps/module-init-tools-0.9.10-r3
|
|
|
| Back to top |
|
|
Mell
n00b
Joined: 16 Nov 2002
Posts: 26
Location: Germany
|
| Posted: Tue Mar 11, 2003 5:21 pm Post subject: |
|
|
That is right: Look at the devfsd-1.3.25-r2.ebuild
| Quote: | # Get modprobe from module-init-tools to shutup
epatch ${FILESDIR}/${P}-shutup-modprobe.patch
|
under the src-unpack section.
Besides there is a note in the ChangeLog:
| Quote: | *devfsd-1.3.25-r2 (10 March 2003)
10 March 2003; Martin Schlemmer <azarah@gentoo.org> devfsd-1.3.25-r2.ebuild :
Change the patch to rather send modprobe output to syslog (-s).
*devfsd-1.3.25-r1 (02 March 2003)
02 March 2003; Martin Schlemmer <azarah@gentoo.org> devfsd-1.3.25-r1.ebuild :
Call modprobe with -q to minimize errors to stderr ... many stuff comes from
/etc/*.devfs anyhow, so very possible that no module present ... |
But I unfortunately do not really understand what all this is about... |
|
| Back to top |
|
|
bsolar
Bodhisattva
Joined: 12 Jan 2003
Posts: 2764
|
| Posted: Tue Mar 11, 2003 5:34 pm Post subject: |
|
|
Then are harmless error messages? From what I undesrtood is a mere error messages redirection issue.
BTW just reinstalled and the problem is still here... 
_________________
I may not agree with what you say, but I'll defend to the death your right to say it. |
|
| Back to top |
|
|
georgm
n00b
Joined: 10 Aug 2002
Posts: 30
Location: Germany
|
| Posted: Tue Mar 11, 2003 5:47 pm Post subject: |
|
|
hm, maybe time to write a bug report...
my english isn't the best - anyone else? |
|
| Back to top |
|
|
bsolar
Bodhisattva
Joined: 12 Jan 2003
Posts: 2764
|
| Posted: Tue Mar 11, 2003 6:15 pm Post subject: |
|
|
| georgm wrote: | hm, maybe time to write a bug report...
my english isn't the best - anyone else? |
I can do that.
_________________
I may not agree with what you say, but I'll defend to the death your right to say it. |
|
| Back to top |
|
|
georgm
n00b
Joined: 10 Aug 2002
Posts: 30
Location: Germany
|
| Posted: Tue Mar 11, 2003 6:48 pm Post subject: |
|
|
| thx |
|
| Back to top |
|
|
spitzwegerich
l33t
Joined: 04 Mar 2003
Posts: 697
Location: Lower Bavaria, Central Europe
|
| Posted: Tue Mar 11, 2003 11:51 pm Post subject: |
|
|
hello!
i have the same problem. here is what i did before this happened the first time:
i copied the whole file system to another partition, then i repartitioned my linux harddisc and i copied all the data back.
now everything seems to be fine, except this /dev/rtc thing. i get also a message "Can't locate module /dev/ttyp0" when booting.
is it possible that some device files are not copied with a "cp -r /* somewhere"? has anyone an idea how i could get back these lost device files?
thanks,
~michael |
|
| Back to top |
|
|
spitzwegerich
l33t
Joined: 04 Mar 2003
Posts: 697
Location: Lower Bavaria, Central Europe
|
| Posted: Wed Mar 12, 2003 12:01 am Post subject: |
|
|
| i just remembered that the copying i described was not the only thing i did before. i did "merge -u system" and an unsuccessful "emerge xfree" (because of not enough disc space). |
|
| Back to top |
|
|
bsolar
Bodhisattva
Joined: 12 Jan 2003
Posts: 2764
|
| Posted: Wed Mar 12, 2003 1:06 am Post subject: |
|
|
| spitzwegerich wrote: | hello!
i have the same problem. here is what i did before this happened the first time:
i copied the whole file system to another partition, then i repartitioned my linux harddisc and i copied all the data back.
now everything seems to be fine, except this /dev/rtc thing. i get also a message "Can't locate module /dev/ttyp0" when booting.
is it possible that some device files are not copied with a "cp -r /* somewhere"? has anyone an idea how i could get back these lost device files?
thanks,
~michael |
I have your same problem and it persisted even after a fresh reinstall from livecd. I think is a bug somewhere (I think devfsd to blame).
I filed a bug about that.
_________________
I may not agree with what you say, but I'll defend to the death your right to say it. |
|
| Back to top |
|
|
georgm
n00b
Joined: 10 Aug 2002
Posts: 30
Location: Germany
|
| Posted: Wed Mar 12, 2003 2:07 am Post subject: |
|
|
| Emerging devfsd-1.3.25 worked for me... |
|
| Back to top |
|
|
Cappy
Tux's lil' helper
Joined: 12 Mar 2003
Posts: 98
|
| Posted: Wed Mar 12, 2003 3:20 am Post subject: |
|
|
| I had the same problem with several kernels....solved it by just choosing Enhanced Realtime Clock Support as a module in menuconfig. don't know why modprobe is calling upon it....even using the Vanilla-Sources with RTC support disabled. Like someone said, it may be a bug in devfs. |
|
| Back to top |
|
|
TecHunter
Tux's lil' helper
Joined: 15 Feb 2003
Posts: 124
|
| Posted: Wed Mar 12, 2003 8:54 am Post subject: |
|
|
i emerge the latest devfsd yesterday.and when i entered gentoo today, it took out this error.i think it is a bug of the latest devfsd ebuild
_________________
Gentoo is GREAT!!! |
|
| Back to top |
|
|
Sassur
n00b
Joined: 04 Jul 2002
Posts: 25
Location: Hägersten/Stockholm/Sweden
|
| Posted: Wed Mar 12, 2003 9:23 am Post subject: |
|
|
I vote for the new devfsd too.
I got the same errors as you and didn't understand why. But when I
read this thread I rememberd that I too hade updated devfsd.
It's time for a downgrade. 
_________________
Fredrik |
|
| Back to top |
|
|
|
Other Things Gentoo
