On ср, 2006-07-19 at 22:18 +0700, Dave Patterson wrote: > * [EMAIL PROTECTED] <[EMAIL PROTECTED]> [2006-07-19 22:54:31 +0800]: > > > > As I recall, this broke for me in going from 2.6.15 to 2.6.16. > > > > Clayton > > > Yup, it did - my solution was to install a stock kernel, and used it's > .config as the basis for my custom kernel's config, then remove the stock > kernel. It saved a little heartache looking through the new directory > structure, and was faster, too. >
Thank you all for the hints. What I did was actually go back to kernel 2.6.15 where my oldconfig worked. Then from 2.6.15 I upgraded to 2.6.16 and this time it didn't break. And finally the step form 2.6.16 to 2.6.17 was successful. It took me all night to compile kernels and test! This was my toughest ever update of my Debian box! A few days ago I migrated from XFree86 to Xorg, it was painful too. Debian used to be the easiest to upgrade Operating System, now I find it very frustrating... I didn't realise that my omitting several kernel releases would break things. By means of oldconfig I some time ago upgraded from 2.4.27 to 2.6.8 kernel without any problems! This is ridiculous. What if I were running Debian Stable and decided to give Unstable a go (which is a very common scenario)? The migration from 2.6.8 to 2.6.17 would definitely break! I know this is what Unstable is all about. Don't get me wrong - I am not complaining much. But I am sure there are users that will not have the patience to solve their problems and my current post's aim is to ask if there is a way of avoiding such major omissions. Best regards and enjoy our favourite distro Chavdar Videff -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
