| View previous topic :: View next topic |
| Author |
Message |
Joe
n00b
Joined: 01 Jul 2002
Posts: 70
Location: Europe
|
 Posted: Tue Jul 15, 2003 10:42 pm Post subject: |
 |
|
| mrsteven wrote: | | I really wonder when this bug gets fixed. Is anyone able to say when the new devfsd is released? |
I am still encountering that problem. Its very annoying. Cause I use a monolith kernel on some machines, it appears more like a farce... system is trying all the time to insert modules, but they arent even supported by kernel.
Maybe someone could post some infos how to modify /etc/ configfiles to workaround this problem. I simply want to disable that modprobe feature completely.
Regards,
Joe |
|
| Back to top |
|
 |
josh
Guru
Joined: 05 Feb 2003
Posts: 473
Location: Milky Way: Solar System: Earth: North America: USA: NY: Buffalo
|
| Posted: Wed Jul 16, 2003 2:35 am Post subject: |
|
|
I had a wierd problem concerning this:
I did a system update recently (emerge -u world), and after that, when I started my computer, I would get about 4:
| Code: | | modprobe: can't load module /dev/*rtc |
Then about 53 other "can't load /dev/* and /dev/snd/*
Then, it wouldn't be able to bring up eth0, netmount, klogd, vcron and other vital stuff. As well it couldn't find alsactl. eth0 could be brought up manually, but the rest could not. If I rebooted, I got all the warnings, but everything seemed to come up ok. So, if I turned the machine off for a few seconds (or more), I got all these problems, but when I'd reboot, it was ok (?????) After reading through these posts, I downgraded devfsd but it made no difference. Next I decided to enable RTC in the kernel. I didn't think it would work, but it was worth a shot. I enabled it as <Module> and entered it into /etc/modules.autoload . After I restarted, I didn't get the first four /dev/*rtc warnings, but I got the rest, and everything worked fine, without rebooting.
Just thought I'd post that, cuz I saw that a couple of people were having kind of similar problems. Er at least, more problems than JUST the warnings.
_________________
-Josh |
|
| Back to top |
|
|
mpsii
l33t
Joined: 11 Mar 2003
Posts: 658
Location: Jackson, TN
|
| Posted: Wed Jul 16, 2003 2:50 am Post subject: |
|
|
Not sure if this is a help or not...
But, those messages all went away after I
ran | Code: | | # rc-update add sshd default |
and rebooted...
Not sure why, just glad to see error messages gone!
_________________
-----------------------------------------
Michael |
|
| Back to top |
|
|
josh
Guru
Joined: 05 Feb 2003
Posts: 473
Location: Milky Way: Solar System: Earth: North America: USA: NY: Buffalo
|
| Posted: Wed Jul 16, 2003 3:08 am Post subject: |
|
|
mpsii: That didn't work for me. But I'm just glad it's only error messages for me now and not errors. This is a wierd problem, because everyone has a similar yet different problem with it...whatever it is.
_________________
-Josh |
|
| Back to top |
|
|
mpsii
l33t
Joined: 11 Mar 2003
Posts: 658
Location: Jackson, TN
|
| Posted: Wed Jul 16, 2003 1:11 pm Post subject: |
|
|
Ok... I am now getting it again...
IIRC, /dev/rtc is the real time clock, mostly used with SMP systems to sync the processors, correct?
Since I did not compile SMP support in my kernel and did not select /dev/rtc support, why are these apparently common error messages appearing?
_________________
-----------------------------------------
Michael |
|
| Back to top |
|
|
josh
Guru
Joined: 05 Feb 2003
Posts: 473
Location: Milky Way: Solar System: Earth: North America: USA: NY: Buffalo
|
| Posted: Wed Jul 16, 2003 7:50 pm Post subject: |
|
|
Yeah, I'm pretty sure you're right. At least... that's the gist of what I got when reading the <help> under it in make menuconfig. I enabled it (as module) anyway because it didn't sound like any real harm could be done by it (even though my comp is only a single processor) and it got rid of the /dev/rtc errors, but I still get others.
_________________
-Josh |
|
| Back to top |
|
|
b0fh
Guru
Joined: 16 Jun 2003
Posts: 426
|
| Posted: Wed Jul 16, 2003 7:59 pm Post subject: |
|
|
Well, but I think you should avoid creating modules you really don't need.
By the way: You don't need real time clock support only for smp, but for other programs which use certain timers... |
|
| Back to top |
|
|
mpsii
l33t
Joined: 11 Mar 2003
Posts: 658
Location: Jackson, TN
|
| Posted: Wed Jul 16, 2003 8:36 pm Post subject: |
|
|
/dev/rtc is used when you want low latency scheduling... so... if you use gentoo-sources, gaming-sources, etc with the low latency scheduling patches, that is where this node comes into play.
When I let sysctl control the low latency scheduling in my kernel config under "Processor type and features," the error messages go away.
_________________
-----------------------------------------
Michael |
|
| Back to top |
|
|
Inte
Veteran
Joined: 15 Jul 2003
Posts: 1387
Location: Mannheim, GER
|
| Posted: Fri Jul 18, 2003 9:10 am Post subject: |
|
|
| mpsii wrote: | /dev/rtc is the real time clock, mostly used with SMP systems to sync the processors, correct?
Since I did not compile SMP support in my kernel and did not select /dev/rtc support, why are these apparently common error messages appearing? |
I'd nearly the same problem. I need to compile SMP support otherwhise I get a Kernel panic. Strange! 
I tried to compile the RTC support (module) in my kernel, to avoid these /modprope/*rtc messages. It fixed the problem. 
Offtopic: Do anybody know why I need to compile the SMB support in my kernel (2.4.20-r5)? I've a Thinkpad R40 and I'm sure it has a single processor. 
-=Inte=-
_________________
Gentoo Linux - Die Metadistribution |
|
| Back to top |
|
|
dank
n00b
Joined: 06 Jun 2003
Posts: 15
|
| Posted: Sun Jul 20, 2003 3:35 pm Post subject: |
|
|
| Quote: | Posted by: Lord_Orion
I found a solution to kill this error message...
downgrade baselayout to version 1.8.5.9
after an etc-update that's it... |
i know i'm a newb, wut do i know... but upon installing a fresh rc4 i had the same modprobe /dev/rtc issue (fixed by adding rtc support in kernel), and a bunch of modprobe errors that would pop up upon login which was fixed by downgrading to baselayout 1.8.5.9
thanks guys 
-dank |
|
| Back to top |
|
|
wastaz
n00b
Joined: 19 Jan 2003
Posts: 9
Location: Sweden, land of the few ddr machines
|
| Posted: Tue Aug 05, 2003 6:55 pm Post subject: |
|
|
This error is back.
It would probably be a baselayout error seeing as I updated my baselayout yesterday, but not devfsd. Im using baselayout-1.8.6.8-r1 and I'm going to downgrade to 1.8.6.7 now and see if it solves the problem.
-edit-
Downgrade to 1.8.6.7 didnt solve any problems (more like created some due to other stuff being upgraded..) so Im back on 1.8.6.8-r1 now again.
Might be something else, but Im not sure what.
I tried compiling in low latency scheduling via sysconf instead in the kernel as someone talked about earlier, but this hasnt solved any problems for me either. |
|
| Back to top |
|
|
Giorgio
Tux's lil' helper
Joined: 18 Jan 2003
Posts: 77
Location: Milano, Italy
|
| Posted: Mon Aug 25, 2003 5:16 pm Post subject: |
|
|
| georgm wrote: | Hm, I had no crash...
Can I see anywhere what I've emerged yesterday? |
emerge app-portage/genlop
_________________
app-portage/genlop
A nice emerge.log parser |
|
| Back to top |
|
|
caslca
Tux's lil' helper
Joined: 24 Aug 2003
Posts: 85
|
| Posted: Sun Sep 21, 2003 6:27 pm Post subject: |
|
|
***POSSIBLE_FIX***
the grprnam error from pam is happening because pam is trying to find info on a group (from /etc/group) on the group "cdwriter"
fix: groupadd cdwriter
the multiple modprobe errors i fixed weirdly enough by:
rc-update add metalog boot
on the next boot, the errors were gone...(i still can't figure why)
oh and i have RTC compiled as a module (it still gets loaded though, so someone needs it) |
|
| Back to top |
|
|
teknik0s
n00b
Joined: 26 May 2003
Posts: 72
Location: Texas
|
| Posted: Thu Apr 22, 2004 12:48 pm Post subject: |
|
|
| i get the /dev/rtc error too, gaming-sources-2.4.20rc10 i think. So i just need to compile RTC in and it will go away? |
|
| Back to top |
|
|
kabz
n00b
Joined: 02 Feb 2005
Posts: 12
|
| Posted: Fri Feb 04, 2005 6:14 am Post subject: |
|
|
Have you tried rebuilding your kernel with support for the real time clock.
Mplayer is running, but really slowly, and complaining about no /dev/rtc. And lo, it's not there. And it's not there because I didn't set the option in my kernel.
DOH !!!
P.S. 2.6.10-gentoo-r6 is running great for me !!!! |
|
| Back to top |
|
|
|
Other Things Gentoo
