From: Thomas Davis <tadavis@lbl.gov>
To: gene.heskett@verizon.net
Cc: Burton Windle <bwindle@fint.org>, lkml <linux-kernel@vger.kernel.org>
Subject: Re: Can't boot a 2.6 kernel..
Date: Thu, 29 Jan 2004 13:39:31 -0800 [thread overview]
Message-ID: <40197D93.40104@lbl.gov> (raw)
In-Reply-To: <200401291632.15712.gene.heskett@verizon.net>
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/
>
>
next prev parent reply other threads:[~2004-01-29 21:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-29 19:18 Can't boot a 2.6 kernel Thomas Davis
2004-01-29 19:32 ` Erik Mouw
2004-01-29 19:33 ` Thomas Davis
2004-01-29 19:36 ` Thomas Davis
[not found] ` <Pine.LNX.4.58.0401291527180.1094@morpheus>
2004-01-29 20:53 ` Thomas Davis
2004-01-29 21:32 ` Gene Heskett
2004-01-29 21:39 ` Thomas Davis [this message]
2004-01-31 15:02 ` Adrian Bunk
-- strict thread matches above, loose matches on Subject: below --
2004-01-30 7:34 Tolentino, Matthew E
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=40197D93.40104@lbl.gov \
--to=tadavis@lbl.gov \
--cc=bwindle@fint.org \
--cc=gene.heskett@verizon.net \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox