Got it to build and even attempt to boot--no undefineds! The thing listed a lot of oops codes, many involving the journaling, so I panicked and stopped it.
Additionally, there were items like: BUG: Using SMP with preemptive .... (or something like that.) (I do not have multiple processors but the default kernels are SMP. I could set that option to "n". I saw somewhere that a scheduler option needs to be set to CPQ--I believe I have this Anticipatory now--could this be the problem?) The one ominous thing in the build is this item: Building modules, stage 2. MODPOST WARNING: drivers/acpi/processor.o - Section mismatch: reference to .init.data: from .text between 'acpi_processor_power_init' (at offset 0x1055) and 'acpi_safe_halt' WARNING: drivers/atm/he.o - Section mismatch: reference to .init.text: from .text between 'he_start' (at offset 0x1f5d) and 'he_service_tbrq' WARNING: modpost: module vzwdog.ko uses symbol 'next_online_pgdat' marked UNUSED WARNING: modpost: module vzwdog.ko uses symbol 'first_online_pgdat' marked UNUSED WARNING: "next_online_pgdat" [kernel/ve/vzwdog.ko] has no CRC! WARNING: "first_online_pgdat" [kernel/ve/vzwdog.ko] has no CRC! I do not know whether the "mismatches" are related to openvz or is in other builds as well. If I do not notice it and nothing bawks... I do not have acpi working so might be using apm instead. Both are cited. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
