@penalvch: I've never tested an upstream kernel before so thanks for the instructions! I'm nervous about ruining my system, so please can you confirm my understanding is correct before I go ahead with this:
1) I've downloaded these files into their own folder: linux-headers-4.4.0-040400rc7_4.4.0-040400rc7.201512272230_all.deb linux-headers-4.4.0-040400rc7-generic_4.4.0-040400rc7.201512272230_amd64.deb linux-image-4.4.0-040400rc7-generic_4.4.0-040400rc7.201512272230_amd64.deb 2) If I run 'sudo dpkg -i *.deb' in that folder in a terminal I should get a new entry in my GRUB menu. 3) I can then attempt to boot into that kernel from GRUB at boot time (and run scangearmp to see if it detects the scanner). 4) If the OS fails to boot for whatever reason I can simply reboot my PC and choose my original kernel from GRUB (i.e., 3.13.0-74-generic). Is it true that my system will be unharmed so long as I don't boot into the upstream kernel? If you can't be 99-100% sure about this I'll have to buy an external drive and clone my drive to it; which will take some days... Thanks. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1529232 Title: Scanner not detected over wifi since after 3.13.0-68 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1529232/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
