<html><head><style type="text/css"></style></head><body><div style="font-family:times new roman, new york, times, serif;font-size:12pt"><DIV>Mario,</DIV> <DIV> </DIV> <DIV>I'm not speaking for Ben.  The nvidia proprietary driver versions 177.13 and 177.69 are reported to work with 2.6.27. (see <A href="http://www.nvnews.net">www.nvnews.net</A> forums)</DIV> <DIV> </DIV> <DIV>Regards,</DIV> <DIV> </DIV> <DIV>Harvey</DIV> <DIV> </DIV> <DIV><BR> </DIV> <DIV style="FONT-SIZE: 12pt; FONT-FAMILY: times new roman, new york, times, serif"><BR> <DIV style="FONT-SIZE: 12pt; FONT-FAMILY: times new roman, new york, times, serif">----- Original Message ----<BR>From: Mario Limonciello <superm1@ubuntu.com><BR>To: Ben Collins <ben.collins@canonical.com><BR>Cc: ubuntu-devel@lists.ubuntu.com<BR>Sent: Thursday, August 21, 2008 10:52:39 AM<BR>Subject: Re: [RFC] Moving Intrepid to 2.6.27 kernel<BR><BR> <DIV dir=ltr>Hi Ben:<BR><BR>Not to necessarily be a deterrant from moving to 2.6.27, but do the closed drivers available in Ubuntu, the Broadcom, the NVIDIAs, and the Fglrx compile nicely against 2.6.27, or will some more modifications be needed there too?<BR><BR>Regards<BR><BR> <DIV class=gmail_quote>On Wed, Aug 20, 2008 at 15:02, Ben Collins <SPAN dir=ltr><<A href="mailto:ben.collins@canonical.com" target=_blank rel=nofollow ymailto="mailto:ben.collins@canonical.com">ben.collins@canonical.com</A>></SPAN> wrote:<BR> <BLOCKQUOTE class=gmail_quote style="PADDING-LEFT: 1ex; MARGIN: 0pt 0pt 0pt 0.8ex; BORDER-LEFT: rgb(204,204,204) 1px solid">As many of you know, we've continued a tree called ubuntu-next which is<BR>currently following 2.6.27 upstream kernel. It has been kept in sync<BR>with intrepid's 2.6.26 based kernel tree.<BR><BR>In recent weeks it has become apparent that we will need several updates<BR>to 2.6.26 in order to have a stable kernel for 8.10. These include:<BR><BR> * Updated mac80211, which will require updated wlan drivers in order<BR>  to fix major regressions with suspend/resume and wlan devices.<BR> * Updated alsa-1.0.17 drivers for new codecs<BR> * xen64 paravirt<BR> * Updated KVM<BR><BR>These are just the major things we need to do. The good thing is, all of<BR>this is already in 2.6.27, and is ready to be uploaded on a moments<BR>notice. It has been tested by myself for quite some time, and others on<BR>the team have also tested it.<BR><BR>Yesterday, we discussed the possibility of moving to 2.6.27 before<BR>feature freeze on #ubuntu-kernel during out weekly IRC meeting. In<BR>attendance were the kernel team, Steve Langasek, Chuck Short and Soren<BR>Hansen. Soren and Chuck gave particularly good reasons for moving to<BR>2.6.27, which included xen64 and updated KVM.<BR><BR>Steve had questions about the particulars of this move, and I believe we<BR>answered all of his questions satisfyingly, but we agreed to take this<BR>to a wider audience before making a commitment.<BR><BR>So fire away with any concerns or issues that this might cause. If we<BR>are going to do it, it needs to be decided by early next week.<BR><BR>Thanks<BR><FONT color=#888888><BR><BR>--<BR>ubuntu-devel mailing list<BR><A href="mailto:ubuntu-devel@lists.ubuntu.com" target=_blank rel=nofollow ymailto="mailto:ubuntu-devel@lists.ubuntu.com">ubuntu-devel@lists.ubuntu.com</A><BR>Modify settings or unsubscribe at: <A href="https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel" target=_blank rel=nofollow>https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel</A><BR></FONT></BLOCKQUOTE></DIV><BR><BR clear=all><BR>-- <BR>Mario Limonciello<BR><A href="mailto:superm1@gmail.com" target=_blank rel=nofollow ymailto="mailto:superm1@gmail.com">superm1@gmail.com</A><BR></DIV></DIV></DIV></div></body></html>