I've an unknown cpu (athlon xp) in my machine. What data do I need to
collect so the kernel knows what it is?
# cat /proc/cpuinfo
processor : 0
vendor_id : AuthenticAMD
cpu family : 6
model : 10
model name : Unknown CPU Type
stepping : 0
cpu MHz : 1837.618
cache size : 512 KB
fdiv_bug : no
hlt_bug : no
f00f_bug : no
coma_bug : no
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 mmx fxsr sse syscall mmxext 3dnowext 3dnow
bogomips : 3629.05
On Fri, Jan 16, 2004 at 02:42:14PM -0500, David Ford wrote:
> I've an unknown cpu (athlon xp) in my machine. What data do I need to
> collect so the kernel knows what it is?
>
> # cat /proc/cpuinfo
> processor : 0
> vendor_id : AuthenticAMD
> cpu family : 6
> model : 10
> model name : Unknown CPU Type
That string gets read from the CPU directly, after the BIOS programs it.
Try and get an updated BIOS.
Dave
It's clearly a barton, what kernel are you running?
joelja
On Fri, 16 Jan 2004, David Ford wrote:
> I've an unknown cpu (athlon xp) in my machine. What data do I need to
> collect so the kernel knows what it is?
>
> # cat /proc/cpuinfo
> processor : 0
> vendor_id : AuthenticAMD
> cpu family : 6
> model : 10
> model name : Unknown CPU Type
> stepping : 0
> cpu MHz : 1837.618
> cache size : 512 KB
> fdiv_bug : no
> hlt_bug : no
> f00f_bug : no
> coma_bug : no
> 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 mmx fxsr sse syscall mmxext 3dnowext 3dnow
> bogomips : 3629.05
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to [email protected]
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
--
--------------------------------------------------------------------------
Joel Jaeggli Unix Consulting [email protected]
GPG Key Fingerprint: 5C6E 0104 BAF0 40B0 5BD3 C38B F000 35AB B67F 56B2
Since the mid 2.5 kernels, I'm now on 2.6.1
Joel Jaeggli wrote:
>It's clearly a barton, what kernel are you running?
>
>joelja
>
>
>
I know on my ASUS A7N8X, the CPU type when the CPU is detected is shown
as Unknown unless the correct clock rates etc are used. As soon as they
are set correctly.. it says Athlon 2600+. Before I got them correct, it
had some unknown string (sorry Icant tell you what it was...) and I dont
know what Linux reported then because I at that time all was new in this
PC and hard drive was blank.
Are you over or underclocking?
Craig
On Fri, 2004-01-16 at 21:58, David Ford wrote:
> Since the mid 2.5 kernels, I'm now on 2.6.1
>
> Joel Jaeggli wrote:
>
> >It's clearly a barton, what kernel are you running?
> >
> >joelja
> >
> >
> >
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to [email protected]
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
Nope, the CPU is clocked per spec. I have an issue with this
motherboard since I got it, half the time when I reboot it blurps and
simply won't boot with a high-low warble. I have to turn the machine
off for about 30 minutes or drain the cmos and reset everything.
I'm actually running the RAM a little slow.
David
Craig Bradney wrote:
>I know on my ASUS A7N8X, the CPU type when the CPU is detected is shown
>as Unknown unless the correct clock rates etc are used. As soon as they
>are set correctly.. it says Athlon 2600+. Before I got them correct, it
>had some unknown string (sorry Icant tell you what it was...) and I dont
>know what Linux reported then because I at that time all was new in this
>PC and hard drive was blank.
>
>Are you over or underclocking?
>
>Craig
>
>On Fri, 2004-01-16 at 21:58, David Ford wrote:
>
>
>>Since the mid 2.5 kernels, I'm now on 2.6.1
>>
>>Joel Jaeggli wrote:
>>
>>
>>
>>>It's clearly a barton, what kernel are you running?
>>>
>>>joelja
>>>
>>>
>>>
>>>
>>>
>>-
>>To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
>>the body of a message to [email protected]
>>More majordomo info at http://vger.kernel.org/majordomo-info.html
>>Please read the FAQ at http://www.tux.org/lkml/
>>
>>
>
>
>
What BIOS version are you running?
On my ASUS A7N8X it would list unknown at boot up for an Athlon 2500+ until I got the lastest BIOS version.
--
James Lamanna
Applied Minds, Inc.
1209 Grand Central Ave.
Glendale, CA 91201
(818) 332-5214
On Sat, 2004-01-17 at 00:37, James Lamanna wrote:
> What BIOS version are you running?
> On my ASUS A7N8X it would list unknown at boot up for an Athlon 2500+ until I got the lastest BIOS version.
1007, the latest for the Deluxe.
Hi,
You have the same CPU like me.
I have the EPox mobo and I had this issue.
If your bios ver is not 10/17/2003 then update it from the net.
David Ford wrote:
> I've an unknown cpu (athlon xp) in my machine. What data do I need to
> collect so the kernel knows what it is?
>
> # cat /proc/cpuinfo
> processor : 0
> vendor_id : AuthenticAMD
> cpu family : 6
> model : 10
> model name : Unknown CPU Type
> stepping : 0
> cpu MHz : 1837.618
> cache size : 512 KB
> fdiv_bug : no
> hlt_bug : no
> f00f_bug : no
> coma_bug : no
> 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 mmx fxsr sse syscall mmxext 3dnowext 3dnow
> bogomips : 3629.05
>
> -
> To unsubscribe from this list: send the line "unsubscribe
> linux-kernel" in
> the body of a message to [email protected]
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
David Ford wrote:
> Nope, the CPU is clocked per spec.??I?have?an?issue?with?this
> motherboard since I got it, half the time when I reboot it blurps and
> simply won't boot with a high-low warble.??I?have?to?turn?the?machine
> off for about 30 minutes or drain the cmos and reset everything.
>
I had this no-boot problem with one of the Epox mb's (nForce2). It just
hanged at POST and booted only after many tries. The solution was to
disable showing Health Information (those fan RPMs and temperatures) at
BIOS POST.
Strange, but works this way.
Maybe helps somebody.
Lenar