On Sun, 2003-07-06 at 01:31, Duncan wrote: > That's what I thought I said.. However, I attribute it to something else.. > the binary only bit of the nvidia module, as I had to force > recompile/reinstall of the nvidia module after compiling and switching to > 2.4.21, as the nvidia installer otherwise gave me a warning/error about me > using a different compiler to compile the module than I had to compile the > kernel, tho it was the same one, and I'd just finished compiling the kernel. > The only reasonable explanation for that is that the nvidia binary-only > component was compiled with a different compiler, which would be expected > since I rather doubt they could be using the latest Cooker gcc, when I > believe this release (the latest, but..) was out b4 the latest gcc! > > Thus, I think the problem is the stupid binary-only core, which of necessity > HAS to be compiled with something older than the newest gcc, rather than > devfsd or some other such thing. I expect the reason it won't load by > default now has to do with the compiler differences, tho it will still load > if specifically loaded, as it is when loaded from modules or manually.
No, that's not it. It didn't stop working with a kernel version change for me; it was working with a kernel then stopped working with the same kernel when something else changed. It's not the gcc version. -- adamw
