Awhile back I reported a show-stopper bug with the 220.127.116.11 kernel:
I never bothered to get that one sorted out with the kernel developers, as I thought that 18.104.22.168 was the end of the line for that series.
However, recently Paul Gortman released 22.214.171.124, as apparently Intel are still using that kernel in one of their computers. 2.6.34.x is now re-classified as a "long term" supported kernel.
So, I contacted Paul and explained the problem that I had on one of my PCs. We are going to try and sort it out. To get the ball rolling, I built Wary Puppy with 126.96.36.199, and sent a preliminary report to Paul, various log files that show the bug.
Right now I am recompiling 188.8.131.52 with my "special patch" that "fixes" the bug, and I will send a report on that to Paul also.
Comments:Posted on 14 Jan 2011, 19:41 by Terryphi
Go 2.6.34.x !
Glad to see you are working on kernel 184.108.40.206 and that 2.6.34.x is now re-classified as LTS. Wary 070 with kernel 220.127.116.11 worked very well on my PC and laptop.
Posted on 15 Jan 2011, 5:54 by dionicio
one edible puppy
Posted on 15 Jan 2011, 8:56 by ozsouth
2.6.34.x LTS = good
Glad this is LTS - it seems to have balance between functionality & safety, unlike some later efforts.
Posted on 19 Jan 2011, 11:41 by q5sys
2.6.34 as a long term is a good choice. Any chance you could release the patched source for 2.6.37 since its the most recent stable, so I (and potentially others) can tinker around with it? The Latest Intel graphics drivers require it.
Posted on 21 Jan 2011, 8:28 by BarryK
user: p#up#py pass: l#in#ux
18.104.22.168 is no good, see my blog.