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