Error Inserting Hw_random Ubuntu
Start here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the company Business Learn more about hiring developers or posting ads with us Server Fault Questions Tags Users Badges Unanswered Ask Question _ Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute: Sign up Here's how it works: Anybody can ask a question Anybody can answer The best answers are voted up and rise to the top modprobe amd-rng fails, No such device up vote 1 down vote favorite When trying to install hw_random to a 2.6 kernel, modprobe returns a FATAL error "No such device" on both CentOS 5.7 and Fedora 15. Both are using the latest kernel, respectively. The .ko file exists, and config- contains CONFIG_RTC=y and CONFIG_CRYPTO_RNG=m Both servers are x86_64 AMD processors. The only google results are very old, often reference the kernel module 'hw_random' (which has been replaced with processor specific modules and don't offer much help. Has anyone been able to install hw_random? Am I missing a step while installing the module? Edit: Fedora 15 /lib/modules/2.6.40.6-0.fc15.x86_64/kernel/drivers/char/hw_random/amd-rng.ko # uname -r 2.6.40.6-0.fc15.x86_64 # modprobe -v amd-rng insmod /lib/modules/2.6.40.6-0.fc15.x86_64/kernel/drivers/char/hw_random/amd-rng.ko FATAL: Error inserting amd_rng (/lib/modules/2.6.40.6-0.fc15.x86_64/kernel/drivers/char/hw_random/amd-rng.ko): No such device CentOS 5.7 /lib/modules/2.6.18-274.7.1.el5/kernel/drivers/char/hw_random/amd-rng.ko # uname -r 2.6.18-274.7.1.el5 # modprobe -v amd-rng insmod /lib/modules/2.6.18-274.7.1.el5/kernel/drivers/char/hw_random/amd-rng.ko FATAL: Error inserting amd_rng (/lib/modules/2.6.18-274.7.1.el5/kernel/drivers/char/hw_random/amd-rng.ko): No such device central-processing-unit modprobe random-number-generator share|improve this question edited Mar 7 '13 at 17:10 voretaq7♦ 68.8k1397179 asked Nov 16 '11 at 1:30 CrackerJack9 1046 Where is the .ko file located? What is the output of modprobe -v ...? Also post the un
hwclock Hanging on Startup and Shutdown About Ubuntu Linux DELL Dimension 4700 Details Ubuntu Installer Cannot Detect the Video Card When the Ubuntu installer attempts to detect the video card you will be greeted with a dialogue box that has selected by default the "VESA" option. These machines have an i915 video card that is not supported by any of the drivers available in the "Warty" release of Ubuntu (Note: This video driver is apparantly fully http://serverfault.com/questions/331339/modprobe-amd-rng-fails-no-such-device supported in the "Hoary" release of Ubuntu, due in April 2005). The "VESA" driver works quite well but 3D support is not available, at least until "Hoary" is released anyway. Hotplug Errors on Boot after Installation When you reboot after a successfull install you will notice the following five lines: modprobe: FATAL: Error inserting pciehp https://mcwhirter.com.au/craige/blog/2005/Issues-Installing-Ubuntu-4-10-Warty-on-a-Dell-Dimension-4700/ (/lib/modules/2.6.8.1-4-686/kernel/drivers/hotplug/pciehp.ko) Operation not permitted modprobe: FATAL: Error inserting shpchp (/lib/modules/2.6.8.1-4-686/kernel/drivers/hotplug/shpchp.ko) Operation not permitted modprobe: FATAL: Error inserting pciehp (/lib/modules/2.6.8.1-4-686/kernel/drivers/hotplug/pciehp.ko) Operation not permitted modprobe: FATAL: Error inserting shpchp (/lib/modules/2.6.8.1-4-686/kernel/drivers/hotplug/shpchp.ko) Operation not permitted modprobe: FATAL: Error inserting hw_random (/lib/modules/2.6.8.1-4-686/kernel/drivers/char/hw_random.ko) No such device Fear not! There is nothing fatal about this at all. To stop hotplug trying to load drivers it has no business trying to load (on this system, anyway) add the following three lines to the bottom of /etc/hotplug/blacklist # Not loading on boot. Removed from sight :) pciehp shpchp hw_random Next time you boot you'll notice those annoying messages are now gone. I'd rather know why they won't load but haven't had time to work that out yet so removing them from sight will do for now. hwclock Hanging on Startup and Shutdown The DELL 4700's are hanging on startup (worked around with good 'ol [ctl]+[c]) and locking up completely on shutdown. The hanging and lockups occur with on the following messages: On Startup:
[--noopt] nbits ipsec rsasigkey [--verbose] [--configdir nssdbdir] [--password nsspassword] [--hostname hostname] [--noopt] [--oldkey filename] DESCRIPTION Rsasigkey generates an RSA public/private key pair, suitable http://manpages.ubuntu.com/manpages/precise/man8/ipsec_rsasigkey.8.html for digital signatures, of (exactly) nbits bits (that is, two primes each of exactly nbits/2 bits, and related numbers) and emits it on standard http://osdir.com/ml/ubuntu-users/2005-01/msg02760.html output as ASCII (mostly hex) data. nbits must be a multiple of 16. The public exponent is forced to the value 3, which has error inserting important speed advantages for signature checking. Beware that the resulting keys have known weaknesses as encryption keys and should not be used for that purpose. The --verbose option makesrsasigkey give a running commentary on standard error. By default, it works in silence until it is ready to generate output. error inserting hw_random The --random option specifies a source for random bits. The default is /dev/random (see random(4)). Normally, rsasigkey reads exactly nbits random bits from the source; in extremely-rare circumstances it may need more. Under Linux with hardware random support, the special device /dev/hw_random is created. However, the driver does not guarantee FIPS compliant random, and some hardware is so broken that it return extremely non-random data. Therefor /dev/hw_random should never be used with the --random option. Instead, one should run the rngd(8) daemon to funnel randomness from /dev/hw_random into /dev/random. The --rounds option specifies the number of rounds to be done by the pz_probab_prime_p probabilistic primality checker. The default, 30, is fairly rigorous and should not normally have to be overridden. The --configdir option specifies the nss configuration directory to use. This is the directory where the NSS certificate, key and security modules databases reside. Th
> On Thu, 27 Jan 2005 13:46:00 +0100 (CET), Brian > > Durant > >