2.6.25 has produced unbootable machines for me on both amd64 sid boxes I've tried. In both cases, the solution involved changing "MODULES=most" to "MODULES=dep" in /etc/initramfs-tools/initramfs.conf (and rerunning update-initramfs -u -k 2.6.25-2-amd64 or similar) but it didn't work out of the box. I didn't really investigate the details, but it took me a bit of googling to find that solution... It appeared to be unable to boot the initial ramdisk because it was too big, and perhaps it's an issue that both machines use the nvidia driver module, which is kinda huge (and doesn't need to be on the initramfs) but it's still pretty painful for people who expect lenny to be moderately stable. I wouldn't want it in lenny until some remedy or improved sanity checking is included.
- M On Thu, Jun 12, 2008 at 12:16 PM, Karl Schmidt <[EMAIL PROTECTED]> wrote: > Lennart Sorensen wrote: > >> >> 2.6.25 is a stable kernel, just as 2.6.24 was and 2.6.26 will be. The >> old 'odd number development' stuff would have meant development would be >> in 2.7.x kernels, but that hasn't been used for years. > > OK, I understand I had the odd even part mixed up. > > But what I still don't understand is why 2.6.25 isn't in lenny yet if it is > stable? > > I'm thinking of pulling in 2.6.25 from unstable, but don't want to create > other problems. > > How can I find the ETA of 2.6.25 entering lenny? (I think some of lenny is > already frozen - would that include the kernel?) > > I would think that they would fix the 2.6.24 4G bug if that is what they > will release with? > > > > > ---------------------------------------------------------------- > Karl Schmidt EMail [EMAIL PROTECTED] > Transtronics, Inc. WEB http://xtronics.com > 3209 West 9th Street Ph (785) 841-3089 > Lawrence, KS 66049 FAX (785) 841-0434 > > True wisdom is knowing what we don't know; > True maturity is being comfortable with the idea of not knowing. -KPS > > ---------------------------------------------------------------- > > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact > [EMAIL PROTECTED] > > -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
