On Sun, Dec 18, 2016 at 5:05 AM, Elena ``of Valhalla'' < [email protected]> wrote:
> > Other hardware that may be problematic of course is new hardware which > requires a new kernel, and if you're not already using testing (as > mentioned in the other email), usually there is always one in backports. > This has not been my experience. My experience has been that if your drivers are not in stable, dont bother with testing, or sid. My last experience with this was when I had a new Core 2 Duo( E6300 CPU) system that would not work 100%. As I recall no matter what I did, the SATA controller would not work. Which was because the chipset was not fully recognized by Debian. With that said, the hardware at that time would not work with any distro. However, I'm of the opinion now days that you buy the hardware for your software. e.g. You buy hardware you know that works good for your given OS. There also comes the point that sure, maybe I've a lot of experience with Debian, and can figure out most problem related to it. But often, especially the older I get. I just want whatever it is I'm using to work. So if I need a desktop, for a system that may serve as a personal system, or a workstation. I may just opt for something that "just works" "out of the box". -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/CALHSORoBUNw9OpTiHAhxL0DxnMGPd3NWO9cjsRNhc1tCnkwVHQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
