Hi

I own slack 10 (2.4.27k) on MSI6178 (intel810) with celeron 800, 2x NIC.
In my syslog I can see that "hw_random.o: insmod hw_random failed".
How can I fix it? What is the cause of that error?

Than you!

LOG:

Sep 26 20:23:10 linux kernel: Sep 26 20:23:10 linux insmod:
/lib/modules/2.4.27/kernel/drivers/char/hw_random.o: init_module: Device or
resource busy
Sep 26 20:23:10 linux insmod:
/lib/modules/2.4.27/kernel/drivers/char/hw_random.o: Hint: insmod errors can
be caused by incorrect module parameters, including invalid IO or IRQ
parameters. You may find more information in syslog or the output from
dmesg
Sep 26 20:23:10 linux insmod:
/lib/modules/2.4.27/kernel/drivers/char/hw_random.o: insmod hw_random failed
Sep 26 20:23:10 linux kernel: hw_random: misc device register failed
Sep 26 20:23:10 linux insmod:
/lib/modules/2.4.27/kernel/drivers/char/hw_random.o: init_module: Device or
resource busy
Sep 26 20:23:10 linux insmod:
/lib/modules/2.4.27/kernel/drivers/char/hw_random.o: Hint: insmod errors can
be caused by incorrect module parameters, including invalid IO or IRQ
parameters. You may find more information in syslog or the output from
dmesg
Sep 26 20:23:10 linux insmod:
/lib/modules/2.4.27/kernel/drivers/char/hw_random.o: insmod hw_random failed
Sep 26 20:23:10 linux kernel: hw_random: misc device register failed
Sep 26 20:23:10 linux insmod:
/lib/modules/2.4.27/kernel/drivers/char/hw_random.o: init_module: Device or
resource busy
Sep 26 20:23:10 linux insmod:
/lib/modules/2.4.27/kernel/drivers/char/hw_random.o: Hint: insmod errors can
be caused by incorrect module parameters, including invalid IO or IRQ
parameters. You may find more information in syslog or the output from
dmesg
Sep 26 20:23:10 linux insmod:
/lib/modules/2.4.27/kernel/drivers/char/hw_random.o: insmod hw_random failed
Sep 26 20:23:10 linux kernel: hw_random: misc device register failed
Sep 26 20:23:10 linux insmod:
/lib/modules/2.4.27/kernel/drivers/char/hw_random.o: init_module: Device or
resource busy
Sep 26 20:23:10 linux insmod:
/lib/modules/2.4.27/kernel/drivers/char/hw_random.o: Hint: insmod errors can
be caused by incorrect module parameters, including invalid IO or IRQ
parameters. You may find more information in syslog or the output from
dmesg
Sep 26 20:23:10 linux insmod:
/lib/modules/2.4.27/kernel/drivers/char/hw_random.o: insmod hw_random failed
Sep 26 20:23:11 linux kernel: hw_random: misc device register failed
Sep 26 20:23:11 linux insmod:
/lib/modules/2.4.27/kernel/drivers/char/hw_random.o: init_module: Device or
resource busy
Sep 26 20:23:11 linux insmod:
/lib/modules/2.4.27/kernel/drivers/char/hw_random.o: Hint: insmod errors can
be caused by incorrect module parameters, including invalid IO or IRQ
parameters. You may find more information in syslog or the output from
dmesg
Sep 26 20:23:11 linux insmod:
/lib/modules/2.4.27/kernel/drivers/char/hw_random.o: insmod hw_random failed
Sep 26 20:23:11 linux kernel: hw_random: misc device register failed
Sep 26 20:23:11 linux insmod:
/lib/modules/2.4.27/kernel/drivers/char/hw_random.o: init_module: Device or
resource busy
Sep 26 20:23:11 linux insmod:
/lib/modules/2.4.27/kernel/drivers/char/hw_random.o: Hint: insmod errors can
be caused by incorrect module parameters, including invalid IO or IRQ
parameters. You may find more information in syslog or the output from
dmesg
Sep 26 20:23:11 linux insmod:
/lib/modules/2.4.27/kernel/drivers/char/hw_random.o: insmod hw_random failed
Sep 26 20:23:11 linux kernel: hw_random: misc device register failed
Sep 26 20:23:11 linux insmod:
/lib/modules/2.4.27/kernel/drivers/char/hw_random.o: init_module: Device or
resource busy
Sep 26 20:23:11 linux insmod:
/lib/modules/2.4.27/kernel/drivers/char/hw_random.o: Hint: insmod errors can
be caused by incorrect module parameters, including invalid IO or IRQ
parameters. You may find more information in syslog or the output from

"Krzys-iek" <root.a.krionix.ten<-> wrote:

> Hi
>
> I own slack 10 (2.4.27k) on MSI6178 (intel810) with celeron 800, 2x NIC.
> In my syslog I can see that "hw_random.o: insmod hw_random failed".
> How can I fix it? What is the cause of that error?

most likely you don't have that hardware. add hw_random
to /etc/hotplug/blacklist

> most likely you don't have that hardware. add hw_random
> to /etc/hotplug/blacklist

Hmm, what does hw_random do actually? Maybe stupid question but hw_random is
a little weird name for me :-)

thx

On Mon, 27 Sep 2004 17:23:42 +0200, Krzys-iek wrote:

>
>> most likely you don't have that hardware. add hw_random
>> to /etc/hotplug/blacklist
>
> Hmm, what does hw_random do actually? Maybe stupid question but hw_random is
> a little weird name for me :-)
>
> thx

I would imagine from the name - it uses the hardware random number
generator built into some systems, e.g. mini-itx with Nehemiah core.

Le 27.09.2004 17:23, Krzys-iek <root.a.krionix.ten a écrit :
>>most likely you don't have that hardware. add hw_random
>>to /etc/hotplug/blacklist
>
>
> Hmm, what does hw_random do actually? Maybe stupid question but hw_random is
> a little weird name for me :-)
>
> thx
>

it's a function of some motherboard's chipset that can generate a random
number. So it's not a weird name ;-)
hw = hardware
random = random !

> it's a function of some motherboard's chipset that can generate a
> random number.
>So it's not a weird name ;-)

now It is obvios, I didn't know that chipset can provide functions like that
:-)! If intel810 does not support that then the problem is gone, but if it
does ...

> hw = hardware
> random = random !

clear! :-)

Thank you, Krzysiek

Le 27.09.2004 21:29, Krzys-iek <root.a.krionix.ten a écrit :
> now It is obvios, I didn't know that chipset can provide functions like that
> :-)! If intel810 does not support that then the problem is gone, but if it
> does ...

AFAIK, the i810 and up support that, but some (all?) motherboard's
manufacturer haven't enable it. some pins of the chipset must be connect
and they don't.
My motherboard has this problem too. i've blacklisted this in
/etc/hotplug/blacklist
i810-tco
hw_random
Also read the comment in this file :
# This module causes many Intel motherboards to crash and reboot.