I have my own version of the v4l drivers compiled into one of my machines and it does not have this problem.
The other system with the stock v4l drivers (from the ubuntu-modules package) does have the problem.
Both are running 2.6.24-15. It seems as if the v4l developers have fixed the problem.
I have my own version of the v4l drivers compiled into one of my machines and it does not have this problem.
The other system with the stock v4l drivers (from the ubuntu-modules package) does have the problem.
Both are running 2.6.24-15. It seems as if the v4l developers have fixed the problem.