[CentOS] Probing EDD (edd=off to disable)

Fri Jan 9 11:37:31 UTC 2015
Ned Slider <ned at unixmail.co.uk>

On 08/01/15 18:51, Fred Smith wrote:
> Hi all!
> Running Centos-6.latest on an AMD six-core Vishera processor. It's
> been running for a year on that hardware.
> today I swapped out the video card (from Nvidia 9800GT to Nvidia 460 GTX)
> hoping to get a little more horsepower, and the ability to run the
> Folding At Home GPUclient.
> I know that's an old card, it's a hand-me-down from my son who just
> replaced it with a new 970 GTX card.
> So, I got the hardware installed, close up the case, connect all the
> cables, boot it up and booting stops with this message on the screen
> in plain text mode:
> 	Probing EDD (edd=off to disable)
> I can reboot and edit the kernel commandline to add "edd=off" at the
> end then it comes up all the way.
> I haven't made any changes in the Nvidia drivers, because nvidia's
> web site tells me it uses the same driver as the 9800GT card did.
> I'm using the RPMs from elrepo, so it uses akmod to do a rebuild when
> a new kernel is installed. But I didn't install a new kernel, so it
> didn't get rebuilt, and I'm wondering if that's the cause of the
> problem... different card works with the same driver version but may
> need recompiling due to the different hardware ?????
> If so, I don't think I know how to force akmod to do the rebuild.
> Thoughts/or actual knowledge on this would be appreciated.

No, the elrepo packages are kABI-tracking kmod packages that are
compatible with the RHEL kernels stable ABI. These drivers work across
all RHEL kernel releases, no rebuilding takes place. This is unique to
Enterprise Linux (RHEL and it's clones) and different to how things may
happen on other distros or when using the NVIDIA installer.

Your card is supported by the latest elrepo driver release, so just make
sure you are yum updated to the latest release (currently

yum --enablerepo=elrepo update kmod-nvidia

Reboot if the driver gets updated and you should be good to go.

> Also, among the googling I did, I found one posting that said that message
> means an unexpected (DOS??) interrupt occurred, but it did't  help me
> any with how to resolve it.
> Your suggestions will be welcomed, thanks in advance!
> Fred