Gordon Messmer wrote:
Use "rpm -Vf /path/to/original/module.ko"
If rpm tells you that the checksum has been modified, then the
"original" file you've got isn't the correct file. Download the rpm
that owns that file, and use "rpm -i --replacefiles --replacepkgs
" to reinstall the kernel package
Use "rpm -Vf /path/to/original/module.ko"
If rpm tells you that the checksum has been modified, then the
"original" file you've got isn't the correct file. Download the rpm
that owns that file, and use "rpm -i --replacefiles --replacepkgs
" to reinstall the kernel package.
___
Ken Smith wrote:
Leon Fauster wrote:
Am 17.05.2017 um 12:22 schrieb Ken Smith:
{snip}
Not sure if i understand your problem. Try to regenerate the map
files with
# depmod -a
--
LF
Hi Leon, I tried that and get the same error. Its to do with the
modules being signed. But I don't see ho
Leon Fauster wrote:
Am 17.05.2017 um 12:22 schrieb Ken Smith:
{snip}
Not sure if i understand your problem. Try to regenerate the map files with
# depmod -a
--
LF
Hi Leon, I tried that and get the same error. Its to do with the modules
being signed. But I don't see how I ha
Am 17.05.2017 um 12:22 schrieb Ken Smith :
>
> As part of testing an alternative module I saved the original module and
> copied the test one in. The test was done and I put the original module back.
>
> Now the original module is not loading at startup and doing it manually I get
> the error
>
Hello,
As part of testing an alternative module I saved the original module and
copied the test one in. The test was done and I put the original module
back.
Now the original module is not loading at startup and doing it manually
I get the error
WARNING: Error inserting {Module name & path
6 matches
Mail list logo
