Opened 11 years ago

Closed 11 years ago

#1979 closed bug (fixed)

Blank processor name in About This System

Reported by: j_freeman Owned by: bga
Priority: normal Milestone: R1
Component: - General Version: R1/pre-alpha1
Keywords: Cc: anevilyak
Blocked By: Blocking:
Has a Patch: no Platform: All

Description

The processor is blank in "About This System" under VMware. It used to say something like "AMD Athlon X2".

Tested with hrev24635 on VMware Workstation. Not a problem under real hardware (Athlon XP).

Attachments (4)

nocpu.png (30.2 KB) - added by j_freeman 11 years ago.
pulse.png (2.6 KB) - added by j_freeman 11 years ago.
Screenshot of Pulse
sysinfo.txt (1.2 KB) - added by j_freeman 11 years ago.
Output of "sysinfo"
haiku_cputype_ticket1979.diff (8.3 KB) - added by v 11 years ago.
Not compiled, not tested patch that might resolve the problem

Download all attachments as: .zip

Change History (16)

Changed 11 years ago by j_freeman

Attachment: nocpu.png added

comment:1 Changed 11 years ago by j_freeman

Update: This seems to also occur on real hardware with an Athlon 64.

comment:2 Changed 11 years ago by axeld

And that only happened recently? What does "Pulse" say? And "sysinfo"? Can you give the exact model/stepping of your CPU?

comment:3 Changed 11 years ago by j_freeman

I've only noticed it once before, and that was recently (in the last week). The CPU model is "ADA4200CUBOX". It's a 2.2GHz AMD Athlon 64 X2 (dual core) Windsor.

Changed 11 years ago by j_freeman

Attachment: pulse.png added

Screenshot of Pulse

Changed 11 years ago by j_freeman

Attachment: sysinfo.txt added

Output of "sysinfo"

comment:4 Changed 11 years ago by anevilyak

Owner: changed from axeld to bga

Reassigned to BGA by request (he broke it).

comment:5 Changed 11 years ago by anevilyak

Same problem here, sysinfo:

~>sysinfo Kernel name: kernel_x86 built on: Apr 3 2008 16:12:49 version 0x1 1 (Unknown), revision 8ff0 running at 2014MHz (ID: 0x00000000 0x00000000)

CPU #0: "AMD Athlon(tm) 64 Processor 3200+"

Type 0, family 15, model 47, stepping 0, features 0x078bfbff

FPU VME DE PSE TSC MSR PAE MCE CX8 APIC SEP MTRR PGE MCA CMOV PAT PSE36 CFLUSH MMX FXSTR SSE SSE2

Extended Intel: 0x00000001

SSE3

Extended AMD: type 0, family 15, model 47, stepping 0, features 0xe3d3fbff

Inst TLB: 2M/4M-byte pages, 8 entries, fully associative Data TLB: 2M/4M-byte pages, 8 entries, fully associative Inst TLB: 4K-byte pages, 32 entries, fully associative Data TLB: 4K-byte pages, 32 entries, fully associative L1 inst cache: 64 KB, 2-way set associative, 1 lines/tag, 64 bytes/line L1 data cache: 64 KB, 2-way set associative, 1 lines/tag, 64 bytes/line L2 cache: 512 KB, 16-way set associative, 1 lines/tag, 64 bytes/line

comment:6 Changed 11 years ago by anevilyak

Cc: anevilyak added

Changed 11 years ago by v

Not compiled, not tested patch that might resolve the problem

comment:7 in reply to:  description Changed 11 years ago by v

I haven't set up a system that can compile Haiku yet, therefore the changes as described in haiku_cputype_ticket1979.diff haven't been compiled or tested yet.

comment:8 Changed 11 years ago by bga

Hey v.

Thanks for looking into this. You seem to have reached the same conclusion I did (AMDs should not use extended information for now). At first the patch looks ok. I will apply it later today and check if it works with my Core 2 Extreme. Then I will wait for Rene to check if it also works with his AMD 64. If everything seems all right, I will commit it. What is your name anyway? So I can credit you on the commit message.

comment:9 in reply to:  8 Changed 11 years ago by v

You may credit me as "Hervé W."

comment:10 Changed 11 years ago by anevilyak

Confirmed that this patch fixes it here, everything now identifies it as an Athlon64 again as it should.

Thanks!

comment:11 Changed 11 years ago by j_freeman

Tested the patch on two machines, and they're identified again. Thanks Hervé!

comment:12 Changed 11 years ago by bga

Resolution: fixed
Status: newclosed

Fixed on hrev24958.

Note: See TracTickets for help on using tickets.