I recently had a hard disk failure on my CentOS-6.4 server. I re-intalled CentOS on a second disk, and this is working fine.
But I put together the old system - most partitions on the old disk could still be read - and made a working system. But when I re-start this system I get the above message many times.
(Also I can only login in text mode, and when I run startx I get the error "Fatal server error: no screens found." And ifconfig only gives the lo interface; it does not show eth0 and eth1, so I am unable to access the internet.)
But how can one "sign" a module? I googled for this, but all the suggestions were about signing modules while compiling them.
It seems odd too that the error message does not tell me which module it is referring to. But the error is repeated about as many times as the number of modules listed by lsmod, so I guess every module is wrongly signed.
Any enlightenment on this subject gratefully received.
On 11/17/2013 08:50 AM, Timothy Murphy wrote:
I recently had a hard disk failure on my CentOS-6.4 server. I re-intalled CentOS on a second disk, and this is working fine.
But I put together the old system - most partitions on the old disk could still be read - and made a working system. But when I re-start this system I get the above message many times.
(Also I can only login in text mode, and when I run startx I get the error "Fatal server error: no screens found." And ifconfig only gives the lo interface; it does not show eth0 and eth1, so I am unable to access the internet.)
But how can one "sign" a module? I googled for this, but all the suggestions were about signing modules while compiling them.
It seems odd too that the error message does not tell me which module it is referring to. But the error is repeated about as many times as the number of modules listed by lsmod, so I guess every module is wrongly signed.
Any enlightenment on this subject gratefully received.
my $0.02 worth - I suspect the code snippet that deals with signing is being called but possibly the keys used to verify the signed modules are missing.
Rob Kampen wrote:
But when I re-start this system I get the above message many times.
But how can one "sign" a module? I googled for this, but all the suggestions were about signing modules while compiling them.
my $0.02 worth - I suspect the code snippet that deals with signing is being called but possibly the keys used to verify the signed modules are missing.
Thanks for your response. What you suggest sounds very plausible. But what key or keys are these? Where can they be found.
I put together the old system from various pieces, including bits from old backups, so it is very likely that something is missing.
-
Rob Kampen -
Timothy Murphy