SlackwareThis Forum is for the discussion of Slackware Linux.
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.
Hi all,
In my Slack 9.0 system, X works fine (including antialiasing, DRI, GLX and so on). But at boot time, I get a HUGE number of messages saying that insmod i810_tco and insmod i810-rng failed : no such device etc etc.
What's the problem ? At least, how can I disable these errors from showing up ? (I tried removing /lib/modules/......./i810_tco.gz and so on, but
the next time it complained that these files can't be found).
Which script loads these modules anyway ?
I have the same promble with 845 chips and the computer will auto reboot in one or two minutes after login,if I say "yes" to hotplug support when install slackware 9.0.
If I say "no" to hotplug,the promble will disappear,but the system will not auto detect pci cards,I cann't use my sound card.
I donn't konw what can I do,yet.
Distribution: Slack/Ubuntu & OpenBSD (not a linux distro)
Posts: 56
Rep:
Re: insmod errors in intel 815 chipset
Quote:
Originally posted by rajorshi Hi all,
In my Slack 9.0 system, X works fine (including antialiasing, DRI, GLX and so on). But at boot time, I get a HUGE number of messages saying that insmod i810_tco and insmod i810-rng failed : no such device etc etc.
What's the problem ? At least, how can I disable these errors from showing up ? (I tried removing /lib/modules/......./i810_tco.gz and so on, but
the next time it complained that these files can't be found).
Which script loads these modules anyway ?
Thanks in advance!
you need to add
i810_tco
i810-rng
to your /etc/hotplug/blacklist & reboot, if you still the error reboot twice.
it suppose to create a device in /dev/hwrandom then feed the cpu's data there and basically analyze it.
I could not get the driver work but when I create the device file by hand
daemon dont start upon reboot...
prolly the best for u would be to remove it's modules..
insmod errors mentioned above are still present in Slackware 9.1 also. But the solutions mentioned above have not worked for me. Any suggestions to prevent these errors?
The problem I've had with my 845GL chipset was sound related and not video related as this thread seems to be about. I did however have all the same i810 something or the other bootup error messages. I got both my sound running and the messages to go away by compilling a 2.6.x kernel.
From the intel website
"AC'97 audio for Intel motherboards using ICH4 (82801DB) requires kernel 2.5.11 or later."
This might not even be related with the problem you guys are having but never know I guess...
This message looks as though it is coming up because hotplug is mistakenly trying to install devices that don't exist (this happens most often when hotplug can't distinguish between two slightly different devices and just tries to install both; then one works and the other gives an error). If this is the case, the solution is to add the module names to the hotplug blacklist as Anibal suggested. If you think you added these module names to the blacklist, but you still get these messages, then it is most likely due to a typgraphical error (or the equivalent) in your blacklist entries. These messages will not appear if these modules are properly blacklisted in hotplug. Of course the messages don't actually hurt anything, so it's not something to lose much sleep over.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.