Planet Ubuntu  -
1 days and 22 hours ago
img class=face src=http://planet.ubuntu.com/heads/lucas.png alt= pI#8217;m getting increasingly
annoyed by the state of some aspects of hardware support in Linux./p pMy laptop (old Dell Latitude
D610, Intel-based with ATI graphics) used to suspend/resume correctly with Linux 2.6.24 (ie, 95%
success rate). Later changes made the success rate drop significantly, and added a problem with
kacpid taking 100% CPU because of an interrupt storm. And now, with 2.6.28-rc6, it#8217;s
completely broken. (partially documented in a
href=http://bugzilla.kernel.org/show_bug.cgi?id=11563bug 11563/a, but I admit I gave up on this
bug, because I#8217;m going to change my laptop soon)./p pMy desktop used to wake-on-lan correctly
with 2.6.24 (but required some hacks, because it wouldn#8217;t wake up if the NIC was DOWNed before
shutdown), but changes in the r8169 driver broke it. (documented in a
href=http://bugzilla.kernel.org/show_bug.cgi?id=9512bug 9512/a)./p pAs a result, I#8217;m forced to
run old kernel versions on the two systems I have at home. I can understand that those issues
aren#8217;t considered high priority (not everybody use WoL), but the fact that in both cases, they
are regressions, worries me a bit./p pHow many things are routinely broken during each kernel
release cycle? Hardware support is difficult, of course, but are we really doing everything we
could to make it suck less? Some things I really would like to see:/p ul libDistro packages for
development kernel versions./b For Debian, there#8217;s a
href=http://kernel-archive.buildserver.net/debian-kernel/pool/main/l/linux-2.6/this repository/a,
but it doesn#8217;t always contain the latest kernel versions. Maybe that#8217;s something that
should be moved to a kernel.org umbrella and generalized to all distributions, to provide
beta-testers with easy-to-install packages. igit bisect/i isn#8217;t that user-friendly./li
libFunding for driver developers/b to buy specific hardware. Many drivers cover a wide range of
chips/cards, and developers often only have on a small subset of them, making it difficult to debug
issues specific to one chip./li libBetter/updated bugzilla on kernel.org/b. Many bug logs are
totally confusing, and cover different issues. They could maybe benefit from new or specifically
developed bugzilla features (and more bug triagers, of course)./li /ul
 |
Recommandations
)
and reject those that you are not interested in
(
)
