2008/5/14 Alan McKinnon <[EMAIL PROTECTED]>: > On Wednesday 14 May 2008, Marko Kocić wrote: > > Is it a known issue with 2.6.26-rc1 kernel? How could I painlessly > > migrate configuration from old 2.6.25 kernel to 2.6.26 without need > > for complete reconfiguration? > > make menuconfig always keeped current config before, did it change > > recently? > > It didn't change that I know of, but one can never tell. I suppose step > 1 is to check what changed. So, either: > > run make oldconfig > or > run make menuconfig and rapidly flip through all the screens looking for > entries that end with [NEW]
Did that, but I probably missed to reenable something ;) It was a long time since the last time I had to configure kernel from scratch, so it is hard to remember everything. > If that doesn't sort stuff out, then you will probably have to inspect > the area where you have missing modules more closely and read the help > pages. What are these missing modules? Often it's a case of a > replacement has a different name, like the b43legacy for Broadcom > wireless now has an entirely new b43 intended to replace b43legacy It might be the case. I don't currently have access to my home laptop, but there were lots of modules that are missing. Alsa and iptables failed to start after reboot and I ended up in console screen which is small and in the center of the screen. Thanks, Marko
