Messages in this thread | | | Date | Thu, 29 Jan 2004 13:39:31 -0800 | From | Thomas Davis <> | Subject | Re: Can't boot a 2.6 kernel.. |
| |
I'll summarize again for everyone
getting a prebuilt kernel from http://people.redhat.com/arjanv (2.6.1-1.141smp) and installing it - will not boot.
picking athlon in 2.6.1, and 2.6.2rc2 - will not boot.
picking i386 in 2.6.1 and 2.6.2rc2, and making it brain dead - will not boot.
doing "make allmodconfig" - setting to athlon - will not boot. doing "make allyesconfig" - setting to athlon - will not boot.
thomas
Gene Heskett wrote: > On Thursday 29 January 2004 15:53, Thomas Davis wrote: > >>Not it. >> >># >># Processor type and features >># >>CONFIG_X86_PC=y >># CONFIG_X86_VOYAGER is not set >># CONFIG_X86_NUMAQ is not set >># CONFIG_X86_SUMMIT is not set >># CONFIG_X86_BIGSMP is not set >># CONFIG_X86_VISWS is not set >># CONFIG_X86_GENERICARCH is not set >># CONFIG_X86_ES7000 is not set >>CONFIG_M386=y <-- pretty old hardware??? >># CONFIG_M486 is not set >># CONFIG_M586 is not set >># CONFIG_M586TSC is not set >># CONFIG_M586MMX is not set >># CONFIG_M686 is not set >># CONFIG_MPENTIUMII is not set >># CONFIG_MPENTIUMIII is not set >># CONFIG_MPENTIUM4 is not set >># CONFIG_MK6 is not set >># CONFIG_MK7 is not set >># CONFIG_MK8 is not set >># CONFIG_MELAN is not set >># CONFIG_MCRUSOE is not set >># CONFIG_MWINCHIPC6 is not set >># CONFIG_MWINCHIP2 is not set >># CONFIG_MWINCHIP3D is not set >># CONFIG_MCYRIXIII is not set >># CONFIG_MVIAC3_2 is not set >>CONFIG_X86_GENERIC=y <--- > > I'm running on an old athlon, (MK7 above) and I do not have the above > option set. > I'm also working "stably" on 2.6.2-rc2-mm1. > >>CONFIG_X86_L1_CACHE_SHIFT=7 >>CONFIG_RWSEM_GENERIC_SPINLOCK=y >>CONFIG_X86_PPRO_FENCE=y >>CONFIG_X86_F00F_BUG=y >>CONFIG_X86_INTEL_USERCOPY=y >>CONFIG_HPET_TIMER=y >># CONFIG_HPET_EMULATE_RTC is not set >>CONFIG_SMP=y >>CONFIG_NR_CPUS=8 >>CONFIG_PREEMPT=y >>CONFIG_X86_LOCAL_APIC=y >>CONFIG_X86_IO_APIC=y >>CONFIG_X86_MCE=y >>CONFIG_X86_MCE_NONFATAL=y >>CONFIG_X86_MCE_P4THERMAL=y >>CONFIG_TOSHIBA=m >>CONFIG_I8K=m >>CONFIG_MICROCODE=m >>CONFIG_X86_MSR=m >>CONFIG_X86_CPUID=m >>CONFIG_EDD=m >>CONFIG_NOHIGHMEM=y >># CONFIG_HIGHMEM4G is not set >># CONFIG_HIGHMEM64G is not set >>CONFIG_MATH_EMULATION=y >>CONFIG_MTRR=y >>CONFIG_EFI=y >>CONFIG_BOOT_IOREMAP=y >> >>next. >> >>Burton Windle wrote: >> >>>What about CPU selection? Compiling for a P4 when you have a P2 >>>will cause the same symptom. >>> >>> >>>-- >>>Burton Windle bwindle@fint.org >>> >>>On Thu, 29 Jan 2004, Thomas Davis wrote: >>> >>>>Erik Mouw wrote: >>>> >>>>>On Thu, Jan 29, 2004 at 11:18:09AM -0800, Thomas Davis wrote: >>>>> >>>>>>Ok, I'm trying to get a 2.6 kernel to boot on my desktop here at >>>>>>work. >>>>>> >>>>>>I have tried 3 different kernels - 2.6.1, 2.6.2rc1, and arjanv's >>>>>>2.6.1 kernel. >>>>>> >>>>>>After the grub prompt, I get the grub kernel description, and >>>>>>then.. >>>>>> >>>>>>Nothing. Nada. Zip. Zilch. >>>>>> >>>>>>2.4 kernels boot and works fine; I've attached the dmesg output >>>>>>of one of it's boots. >>>>>> >>>>>>Any ideas on what to try? >>>>> >>>>>I hope you read the post-halloween document, especially the part >>>>>about "Known gotchas"? See >>>>>http://www.codemonkey.org.uk/docs/post-halloween-2.6.txt >>>> >>>>Not it. >>>> >>>>[root@lanshark linux-2.6.1]# egrep >>>>CONFIG_VGA\|CONFIG_INPUT\|CONFIG_VGA_CONSOLE\|CONFIG_VT_CONSOLE >>>>.config CONFIG_INPUT=y >>>>CONFIG_INPUT_MOUSEDEV=m >>>>CONFIG_INPUT_MOUSEDEV_PSAUX=y >>>>CONFIG_INPUT_MOUSEDEV_SCREEN_X=1024 >>>>CONFIG_INPUT_MOUSEDEV_SCREEN_Y=768 >>>>CONFIG_INPUT_JOYDEV=m >>>>CONFIG_INPUT_TSDEV=m >>>>CONFIG_INPUT_TSDEV_SCREEN_X=240 >>>>CONFIG_INPUT_TSDEV_SCREEN_Y=320 >>>>CONFIG_INPUT_EVDEV=m >>>>CONFIG_INPUT_EVBUG=m >>>>CONFIG_INPUT_KEYBOARD=y >>>>CONFIG_INPUT_MOUSE=y >>>>CONFIG_INPUT_JOYSTICK=y >>>>CONFIG_INPUT_JOYDUMP=m >>>>CONFIG_INPUT_TOUCHSCREEN=y >>>>CONFIG_INPUT_MISC=y >>>>CONFIG_INPUT_PCSPKR=m >>>>CONFIG_INPUT_UINPUT=m >>>>CONFIG_VT_CONSOLE=y >>>>CONFIG_VGA_CONSOLE=y >>>> >>>>- >>>>To unsubscribe from this list: send the line "unsubscribe >>>>linux-kernel" in the body of a message to >>>>majordomo@vger.kernel.org >>>>More majordomo info at http://vger.kernel.org/majordomo-info.html >>>>Please read the FAQ at http://www.tux.org/lkml/ >> >>- >>To unsubscribe from this list: send the line "unsubscribe >>linux-kernel" in the body of a message to majordomo@vger.kernel.org >>More majordomo info at http://vger.kernel.org/majordomo-info.html >>Please read the FAQ at http://www.tux.org/lkml/ > >
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |