After the upgrade of my R5D1 combined frontend & backend to R5E50 I am getting some errors at boot. The system will still boot eventually but it takes about 3 minutes to get past the first two errors.

My Myth box specs are in my sig below. I am connected to a non-HD 36" TV via s-video out of the FX5200.

The first error is "You passed an undefined mode number" and then I can either press return and select a mode or space to continue. After 30 seconds or so it moved on a continues booting. How do I pass the correct mode?

The second error is "intel_rng: FWH not detected" It hangs on this for over a minute and then runs through some ata2 errors quickly. After this it boots quickly. I Googled the intel error but didn't find anything that I understand.

Any suggestions?

Thanks,
Britney

At the very top of your /etc/lilo.conf there is an entry that says vga=[something].

Mine says:

vga=791

You can just comment out that line and it shouldn't complain about that one.

then, at the command prompt (as root) type "lilo" to rerun lilo just as the instructions at the top of /etc/lilo.conf inidcate.


- Not sure about your intel message though. Maybe someone else can help there...

The Ether..

_________________
Knoppmyth 7.02 Kernel 2.6.39-LINHES
[MBE] SilverStone LC-10 HTPC Case, Asus M2NPV-VM, AMD X2 4200+, 1G RAM, Nvidia 9500 PCIe, PVR500 and a HD-PVR - Rockin VDPAU

For the first thing, I generally use "vga=normal" there. YMMV.

The second thing is a kernel/hardware problem. If I'm following the stuff in the Kernel mailing list correctly, they're trying to map out the BIOS so they can get at the firmware address space to detect a hardware Random Number Generator. Since this is a dangerous thing to do from a security standpoint, many BIOSes will lock themselves into the memory map to prevent it. There was a discussion of some boot options to skip that, but it wasn't clear to me if they required a kernel patch to use or not.

Thanks! vga=normal fixed the first error. What is the reason for vga=normal not being the default? Just curious.

So the second issue has to do with the newer kernel used in R5E50? I take it that most other people are not seeing this error and that it is specific to my config?

Thanks for the quick responses!

Britney

No, we are just ignoring it as it is not important.

Did you happen to enable boot splash? That would probably do it.

Ok. I was just curious because of the delay in booting. Thanks for confirming that it is nothing for me to be concerned about.


I didn't enable the boot splash during the upgrade. In R5D1 I had the boot splash enabled for a while but it garbled the console screen for me so I disabled.

Britney

I know it's a little after the fact but my system is displaying that intel error message as well. Thanks for the heads up to just ignore it.