If it works in the mainline/upstream kernel, then it should have worked in Ubuntu at some point, since Ubuntu is rebased to mainline during development. We just need to find the last Ubuntu kernel that did work, then we can figure out which Ubuntu specific patch is causing this.
From the first page, you select the version by clicking the versions link. On the following page, you click the link for your architecture, which is under the "Builds" section. On the final page, you can download the linux-image and linux-image-extra .deb packages.
If it works in the mainline/upstream kernel, then it should have worked in Ubuntu at some point, since Ubuntu is rebased to mainline during development. We just need to find the last Ubuntu kernel that did work, then we can figure out which Ubuntu specific patch is causing this.
Can you test an earlier kernel, one that was based on upstream 3.10: /launchpad. net/ubuntu/ +source/ linux/3. 10.0-3. 12
https:/
If your interested, all of the previous Ubuntu kernels for Saucy are available at: /launchpad. net/ubuntu/ saucy/+ source/ linux
https:/
From the first page, you select the version by clicking the versions link. On the following page, you click the link for your architecture, which is under the "Builds" section. On the final page, you can download the linux-image and linux-image-extra .deb packages.