Comment 64 for bug 102982

Hi

Unfortunately it has not worked for me, thank you for the help, until they
find a solution we continue with version 2.6.22-14. Today the new release
is 2.6.24-19.

I hope that they find a solution that could deploy as soon as possible.

Thanks.

On Mon, Aug 18, 2008 at 3:58 PM, Brian Kemp <email address hidden> wrote:

> I have an idea on how to solve this problem. I tested it in 7.10, but it
> should work for others. I have an older Dell Machine (don't remember the
> model number off the top of my head) but I was getting this error
> message.
>
> This *should* make this module load correctly:
>
> As root, modify the /etc/modprobe.d/options file:
> > sudo nano /etc/modprobe.d/options
>
> Add this line:
> option intel_rng no_fwh_detect=1
>
> Save the file. (In nano, Ctrl-O, Enter to save. Ctrl-X to quit.)
>
> To get this to work without a reboot, remove and reinsert the module:
> sudo modprobe -r intel_rng
> sudo modprobe intel_rng
>
> Subsequent reboots should be fine.
>
> Check your system logs to make sure that the chip is detected.
>
> --
> intel_rng: FWH not detected
> https://bugs.launchpad.net/bugs/102982
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in Ubuntu: Invalid
> Status in "linux" source package in Ubuntu: Triaged
> Status in "linux-source-2.6.20" source package in Ubuntu: Won't Fix
> Status in "linux-source-2.6.22" source package in Ubuntu: Won't Fix
>
> Bug description:
> Feisty beta w/ latest updates, 'intel_rng: FWH not detected' error on
> boot, problem is coupled with extremely long delay while 'configuring
> network interfaces' 1-2 min.
> i dont know if the problems are related.
>
> Asus Z71vp, PM, intel 2915 wireless, marvell yukon
>
> ** edit **
>
> 04/27/07
> same problem persists with feisty released
>
>