If you feel still adventurous, you could track it down to code changes in the kernel, by using git-bisect. I've not used it myself, but generally you would pull the Ubuntu kernel sources, and the use "git bisect" to find the particular commit, which caused this.
Thank you very much for tracking this down.
If you feel still adventurous, you could track it down to code changes in the kernel, by using git-bisect. I've not used it myself, but generally you would pull the Ubuntu kernel sources, and the use "git bisect" to find the particular commit, which caused this.
See e.g. http:// kerneltrap. org/node/ 11753 - it's just one of the results that turned up when googling for "git-bisect" though.
You can find the Git sources of the Ubuntu kernel at: http:// kernel. ubuntu. com/git? p=ubuntu/ ubuntu- hardy.git; a=summary and you can then build the kernel using e.g. binary- generic
AUTOBUILD=1 NOEXTRAS=1 fakeroot debian/rules custom-
See also https:/ /wiki.ubuntu. com/KernelTeam/ GitKernelBuild.
It would be great, if you could even track it further down, but for now it's great that you've found a workaround.