[aklug] Re: Compiling a kernel for Ubuntu Dapper

Dee McKinney wrote:
> _____
> From: Damien Hull [mailto:dhull@digitaloverload.net]
> To: Dee McKinney [mailto:deem@wdmfam.com]
> Cc: aklug@aklug.org
> Sent: Wed, 16 Jan 2008 12:15:58 -0900
> Subject: Re: [aklug] Re: Compiling a kernel for Ubuntu Dapper
>
> Dee McKinney wrote:
> > _____
> > From: Damien Hull [mailto:dhull@digitaloverload.net]
> > To: Dee McKinney [mailto:deem@wdmfam.com]
> > Cc: aklug@aklug.org
> > Sent: Tue, 15 Jan 2008 15:46:26 -0900
> > Subject: Re: [aklug] Re: Compiling a kernel for Ubuntu Dapper
> >
> > Dee McKinney wrote:
> > > _____
> > > From: Damien Hull [mailto:dhull@digitaloverload.net]
> > > To: aklug [mailto:aklug@aklug.org]
> > > Sent: Mon, 14 Jan 2008 13:58:31 -0900
> > > Subject: [aklug] Compiling a kernel for Ubuntu Dapper
> > >
> > > I need to compile a new kernel for Dapper. Why? Well, I have software
> > > that requires Dapper so I can't upgrade to Gutsy etc... The system has
> > > an Intel Core 2 Duo 6300. The Dapper kernel only sees one core. It
> > > should show me two cores or two processors.
> > >
> > > Before I rush out and download the latest kernel I thought It would be
> > > best to ask for help.
> > >
> > > * How do I compile a kernel the Debian way?
> > > o never don it the Debian way
> > > * How do I make sure I get the settings for the current working kernel?
> > > o Thinking "oldconfig" etc...
> > > * How do I make sure I get all the drivers / modules compiled?
> > > o My hardware needs to work after the kernel boots
> > >
> > > Just so you know /proc/cpuinfo in Gutsy Gibbon (7.10) shows me two
> > > processors.
> > > ---------
> > > To unsubscribe, send email to <aklug-request@aklug.org>
> > > with 'unsubscribe' in the message body.
> > > Dapper supports SMP.
> > > There is no longer a need to install a separate kernel.
> > >
> > > -Dee
> > >
> > >
> > >
> >
> > I tried two different SMP kernels. No luck. /proc/cpuinfo only shows 1
> > cpu. In Gutsy Gibbon I see two cpu's.
> > Very odd then, as all my servers run on Ubuntu and they are Core 2 Duo servers.
> > -Dee
> >
> >
> > ---------
> > To unsubscribe, send email to <aklug-request@aklug.org>
> > with 'unsubscribe' in the message body.
> >
> >
>
> * What processor are you using? I have the 6300
> * What kernel version?
> * What does /proc/cpuinfo say?
>
>
> Here is one of my AMD servers:
>
> # cat cpuinfo
> processor : 0
> vendor_id : AuthenticAMD
> cpu family : 15
> model : 35
> model name : Dual Core AMD Opteron(tm) Processor 170
> stepping : 2
> cpu MHz : 1995.064
> cache size : 1024 KB
> physical id : 0
> siblings : 2
> core id : 0
> cpu cores : 2
> fpu : yes
> fpu_exception : yes
> cpuid level : 1
> wp : yes
> flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt lm 3dnowext 3dnow pni lahf_lm cmp_legacy
> bogomips : 3996.40
> TLB size : 1024 4K pages
> clflush size : 64
> cache_alignment : 64
> address sizes : 40 bits physical, 48 bits virtual
> power management: ts fid vid ttp
>
> processor : 1
> vendor_id : AuthenticAMD
> cpu family : 15
> model : 35
> model name : Dual Core AMD Opteron(tm) Processor 170
> stepping : 2
> cpu MHz : 1995.064
> cache size : 1024 KB
> physical id : 0
> siblings : 2
> core id : 1
> cpu cores : 2
> fpu : yes
> fpu_exception : yes
> cpuid level : 1
> wp : yes
> flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt lm 3dnowext 3dnow pni lahf_lm cmp_legacy
> bogomips : 3990.31
> TLB size : 1024 4K pages
> clflush size : 64
> cache_alignment : 64
> address sizes : 40 bits physical, 48 bits virtual
> power management: ts fid vid ttp
> ---------
> To unsubscribe, send email to <aklug-request@aklug.org>
> with 'unsubscribe' in the message body.
>
>
I manage a dual Xeon server running Dapper. It shows 4 processors. I'm
not sure why Dapper doesn't like the core 2. I need to find someone
running dapper on a core 2.
---------
To unsubscribe, send email to <aklug-request@aklug.org>
with 'unsubscribe' in the message body.
Received on Wed Jan 16 18:12:26 2008