Re: Anyone With Problems, Please Read.
Posted: Tue May 13, 2008 9:47 am
Sorry to have to say this, but I think it was a mistake for Zero Prime to even post about upgrading your kernel. I understand that Hardy was pushed through and didn't really (IMHO) have the time needed to get all the little stuff worked out in it, this will change soon enough with regular updates. I read the posts in the Ubuntu Forums about this envy issue and read a really good post from one of the developers. Though everyone might want to read this. .....
SomeUbuntuAdminGuy wrote:A final note: at this point in time the -17 kernels are only available in the hardy-proposed repository. This is where bugfix updates to Hardy are pushed first, to recieve testing. As such, this repository is subject to the same sort of problems as an unstable release, but on a lesser scale. Everything should work in there, but it's explicitly for testing, so breakage may occur. In particular, this sort of breakage (where the kernel image is built but an associated package isn't yet built) is going to happen each time a new kernel ABI is pushed (the -17 part of the version string). You can't build the restricted modules without the new kernel, so there's an unavoidable period of time when the repository is in this state.
If you're going to run with the hardy-proposed repository enabled you should be treating it somewhat like running the development release, and be careful on updates. For most people it's better to not have hardy-proposed enabled, unless they want to test a bugfix for a specific bug they are seeing]A final note: at this point in time the -17 kernels are only available in the hardy-proposed repository. This is where bugfix updates to Hardy are pushed first, to recieve testing. As such, this repository is subject to the same sort of problems as an unstable release, but on a lesser scale. Everything should work in there, but it's explicitly for testing, so breakage may occur. In particular, this sort of breakage (where the kernel image is built but an associated package isn't yet built) is going to happen each time a new kernel ABI is pushed (the -17 part of the version string). You can't build the restricted modules without the new kernel, so there's an unavoidable period of time when the repository is in this state.
If you're going to run with the hardy-proposed repository enabled you should be treating it somewhat like running the development release, and be careful on updates. For most people it's better to not have hardy-proposed enabled, unless they want to test a bugfix for a specific bug they are seeing.