compiling and booting 2.6.34
Sune Mølgaard
sune at molgaard.org
Mon May 31 17:49:08 UTC 2010
Lucio Crusca wrote:
> Stefan Bader wrote:
>
>> Try to boot with acpi_osi="!Windows 2009" as a kernel argument and see
>> whether this does not revive the fn+f8 combination.
>
> Unfortunately it does not, neither with 2.6.32 lucid nor 2.6.34 mainline.
>
>> And as your goal
>> is only to have a vanilla 2.6.34 kernel to check, why not safe the effort
>> of finding out what went wrong and burning more compile time.
>
> of course I followed the suggestion. However I'm quite puzzled, I've been
> able to configure and build a working Debian kernel since 2.4 times until
> 2.6.25 or so (I compiled a working 2.6.34 kernel just a few days ago but for
> a different hardware)... now I wonder what can have changed so much that
> pervents me to build a working-customly-configured kernel despite several
> trials on my dell precision m4400... it's just a need of knowledge.
>
>
>
For some odd reason, the step involving building the initramfs fails to
include a SATA module. For me, the quick and dirty fix was to compile
SATA_AHCI into the kernel, although it would be better to fix the
initramfs generation (heads up here, others)...
/Sune
--
The most overlooked advantage of owning a computer is that if they foul
up there's no law against whacking them around a bit.
More information about the kernel-team
mailing list