gathering infos on CPU, Mainboard etc. via commandline

good day dear community

how can i find out which CPU runs on my machine - how to gather some information on the system?

mainboard
cpu
etx etc

i love to get those datas via terminal

any chance to do that?

cat /proc/cpuinfo
cat /proc/meminfo

hi there - good evening henk

many many thanks

Passwort: 
linux-vi17:/home/martin # cat /proc/cpuinfo
processor       : 0
vendor_id       : AuthenticAMD
cpu family      : 6
model           : 8
model name      : AMD Athlon(tm) XP 2000+
stepping        : 1
cpu MHz         : 1666.801
cache size      : 256 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 up
bogomips        : 3333.60
clflush size    : 32
cache_alignment : 32
address sizes   : 34 bits physical, 32 bits virtual
power management: ts

linux-vi17:/home/martin # cat /proc/meminfo
MemTotal:        1543240 kB
MemFree:           63640 kB
Buffers:          170420 kB
Cached:           550648 kB
SwapCached:            0 kB
Active:           592904 kB
Inactive:         770484 kB
Active(anon):     362348 kB
Inactive(anon):   282548 kB
Active(file):     230556 kB
Inactive(file):   487936 kB
Unevictable:           0 kB
Mlocked:               0 kB
HighTotal:        663496 kB
HighFree:           3968 kB
LowTotal:         879744 kB
LowFree:           59672 kB
SwapTotal:       1068284 kB
SwapFree:        1068284 kB
Dirty:               128 kB
Writeback:             0 kB
AnonPages:        642320 kB
Mapped:           153780 kB
Shmem:              2576 kB
Slab:              69160 kB
SReclaimable:      52236 kB
SUnreclaim:        16924 kB
KernelStack:        3272 kB
PageTables:         7628 kB
NFS_Unstable:          0 kB
Bounce:                0 kB
WritebackTmp:          0 kB
CommitLimit:     1839904 kB
Committed_AS:    2321628 kB
VmallocTotal:     122880 kB
VmallocUsed:       30172 kB
VmallocChunk:      79968 kB
HardwareCorrupted:     0 kB
HugePages_Total:       0
HugePages_Free:        0
HugePages_Rsvd:        0
HugePages_Surp:        0
Hugepagesize:       4096 kB
DirectMap4k:       49144 kB
DirectMap4M:      860160 kB
linux-vi17:/home/martin # 

thx - greetings
well i see _ in this machine the 1-5 GB are quite enough - but i guess that the CPU does its part very very well.

Note - i have another machine that runs and ASROCK K 7S41GX with 1000 Mhz CPU and 2 GB memory - this is much slower that the above mentioned machine. I guess that the cpu just is important - with a 1000mhz cpu you have a weak performance - dont you ??

well i try to get a faster cpu - than this 1000mhz cpu. And then i put this on the ASROCK K 7S41GX . What do ou tink

love to hear from you - whats your idea here.

dilbert

As well as the procfs there are a variety of commands (many of which just gather info from procfs):

dmidecode - will normally provide details such as MB model, CPU model, DIMMS etc by extracting them from the SMBIOS.

lspci - list PCI devices
lscpu - slist cpu
lsscsi - list SCSI/SATA devices

While CPU will have a big impact on performance, you also need to assess the workload versus other resources as well. For example, you mentioned 2GB, that sounds fine, but it might not be if you’re doing a lot. Perhaps see if you’re using much swap space (free command), if you are, then adding RAM will probably make things snapper. Now that RAM is cheap, I generally add enough RAM so that swap usage is normally zero.