Mathias Homann wrote:
Am Dienstag, 25. März 2003 13:54 schrieb Peter Wiersig:
But it wasn't a _version_ upgrade... just 2.4.29-74 -> 2.4.19-274? Never seen such a behaviour before...
I expect every binary-only module to break when I upgrade my kernel. Less nasty surprises on my side, I guess.
Go ask NVidia when they will supply compiled drivers for the bug-fixed kernel. And remind them that ".rpm" could contain proper dependencies, so that you will not break your system inadvertently.
Then they will tell me 'but we _have_ SuSE rpm packages for kernel version 2.4.19...'
Because of that .rpm have that "release:" number, which is now "274", as you posted. If they've tested only with "-74" they need to retest with "-274". Have you tried to reinstall the nividia-kernel package and ran "depmod" afterwards. If the interface and compile options were the same even the nvidia module should load. Another alternative is the use of the nvidia-kernel.src.rpm to build the kernel module on your machine. But you need additional software for that, which I would not install on a gaming machine. Peter