- As mentioned my old 2.6.24 was working with hard while the hardy kernel didn't work
So I tried 2.6.24.4 with my 2.6.24 config, which worked. Then I tried it with config-2.6.24-14-generic what didn't work... Most of the time the system did not even boot (the same as with the official 2.6.24-14-generic kernel). The place where it stopped booting was always the same (have a look at my second-last message).
At the end I found out why my old 2.6.24 config did work and the new didn't: Using config-2.6.24-14 and changing CONFIG_M586 to CONFIG_MPENTIUMM (in Menuconfig what changes in fact a few other values, see at the full diff later).
So I think that this is not a ubuntu specific bug as the Gutsy-CONFIG_M586.kernel was working on the same machine without any problems... Even though I think that this is an important bug as my Samsung notebook uses the same components as many other centrino notebooks and I doubt that only a few machines are affected...
A few more observations:
- As mentioned my old 2.6.24 was working with hard while the hardy kernel didn't work
So I tried 2.6.24.4 with my 2.6.24 config, which worked. Then I tried it with config- 2.6.24- 14-generic what didn't work... Most of the time the system did not even boot (the same as with the official 2.6.24-14-generic kernel). The place where it stopped booting was always the same (have a look at my second-last message).
At the end I found out why my old 2.6.24 config did work and the new didn't: Using config-2.6.24-14 and changing CONFIG_M586 to CONFIG_MPENTIUMM (in Menuconfig what changes in fact a few other values, see at the full diff later).
So I think that this is not a ubuntu specific bug as the Gutsy-CONFIG_ M586.kernel was working on the same machine without any problems... Even though I think that this is an important bug as my Samsung notebook uses the same components as many other centrino notebooks and I doubt that only a few machines are affected...