Freels, James D. wrote:
The problem I had started at kernels greater than 2.6.12.x (starting at 2.6.13.0) and was finally cleared at 2.6.15.0.
Interesting ... I am using that module with kernel 2.6.13 and have no problems. Maybe this related to the old hardware I use, maybe to the fact that the Suse-guys have patched that already (assumption: NO research done on this by me ...)
Stefan
