I think your CPU is perfectly suported by 2.6.8 smp kernel.

So, it is possible that the boot problem is caused by any other problem (i.e. 
your 2.6.8 smp kernel has not built in support for your root filesystem).

For example, if your root filesystem is ext3 and your kernel has compiled ext3 
support in a MODULE (or NO ext3 support)  you will not be able to load the 
ext3 kernel support (the ext3 MODULE) and, of course, you will NOT be able to 
boot.

Many other reasons are possible.

But, without the exact error messages is difficult to troubleshoot.

Regards

On Sunday 05 August 2007 18:44, you wrote:
> Thank you for your reply.
> I'm sorry that the machine is really far from my reach.
> And I asked someone who was not familiar with linux restart my server
> and choose my original kernel for me.
> I wonder if the 686 kernel of 2.6.18 is the right one for me.
> Thanks again for your reply.
>
> 2007/8/6, srgqwerty <[EMAIL PROTECTED]>:
> > And what error messages had you got when the system failed to boot with
> > 2.6.8 smp kernel?
> > They are important in order to determine the boot failed reason.
> >
> > Regards
> >
> > On Sunday 05 August 2007 17:40, Kun Niu wrote:
> > > Dear all,
> > > The following is the cat message from /proc/cpuinfo
> > > processor       : 0
> > > vendor_id       : GenuineIntel
> > > cpu family      : 15
> > > model           : 4
> > > model name      : Intel(R) Xeon(TM) CPU 3.00GHz
> > > stepping        : 3
> > > cpu MHz         : 2800.220
> > > cache size      : 16 KB
> > > My present kernel is 2.4.27 on 386 system.
> > > I've ever tried 2.6.8 smp kernel but the system fails to boot.
> > > I wonder if the cpu is supported by etch and which kernel I should
> > > choose to use if it is supported.
> > >
> > > Thanks for any help in advance.
> > >
> > > Regards.
> >
> > --
> > To UNSUBSCRIBE, email to [EMAIL PROTECTED]
> > with a subject of "unsubscribe". Trouble? Contact
> > [EMAIL PROTECTED]


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to