Comment 103 for bug 85488

I've had to conclude that the developers won't be fixing this one - they are not going to change the kernel build options for anything other than security issues, which this isn't. The time to fix this was during feisty development, by responding to this bug report. Instead the decision was taken to allow some of the best-supported scanners under linux to become broken, balancing that against the benefit elsewhere. Hopefully it was worth it - some kind of response to all these hundreds of bug reports would be nice!

I now have Feisty running, with the latest Nvidia drivers, Beryl, all my hardware (INCLUDING my LIDE-20!) working properly.

How? By enabling edy security repository, installing the 2.6.17-11 kernel, removing the ubuntu Nvidia stuff, adding all the build-essential gcc and so on, then installing the Nvidia drivers (and compiling the kernel modules after stopping kdm), editing xorg.conf. I've had to do all this sort of thing before, but this kind of thing is what I moved to Ubuntu to avoid - certainly not working-out-of-the-box! Oh well, next release will be THE one, I'm sure.