Re: Identifying CPU
Hi Guys, Please, can I get something like the 'Extended brand string' from cpuid to identify a cpu using C language? Of course, not using system(cpuid) :) Something more cross-platform. Cheers, Beco -- Dr Beco A.I. researcher Sometimes the heart sees what is invisible to the eye. (H. Jackson Brown Jr.) -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/CALuYw2yWStyu-OCbmAb9Fyyk8_yGUrqw9ewOOZJ=scqlicx...@mail.gmail.com
Re: Identifying CPU
On Wed, Sep 18, 2013 at 11:53:03AM -0300, Beco wrote: Hi Guys, Please, can I get something like the 'Extended brand string' from cpuid to identify a cpu using C language? Of course, not using system(cpuid) :) Something more cross-platform. Is x86 enough for you? If so, http://libcpuid.sourceforge.net/ If you need to check across architectures, you probably need to go all the way to autoconf for maximum flexibility. -dsr- -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20130918155117.gp4...@randomstring.org
Re: Identifying CPU
On 18 September 2013 12:51, Dan Ritter d...@randomstring.org wrote: Is x86 enough for you? If so, http://libcpuid.sourceforge.net/ If you need to check across architectures, you probably need to go all the way to autoconf for maximum flexibility. -dsr- Nice lib, Dan. Thanks! --Beco -- Dr Beco A.I. researcher Sometimes the heart sees what is invisible to the eye. (H. Jackson Brown Jr.) -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/CALuYw2ypd=QmmZE+Hk0t64AZKtW4P8zTsFJ0XuHvBSyWWuSW=g...@mail.gmail.com
Re: Identifying CPU
On Sat, Sep 07, 2013 at 02:17:36AM +0530, shirish शिरीष wrote: cpuid is the best if you are looking for any sort of detailed info. See http://forums.debian.net/viewtopic.php?f=10t=106956 for details. -- Looks cool :) anyway thanks. -- software engineer Rajagiri school of engineering and technology. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20130907180808.ga5...@debian.jeff
Re: Identifying CPU
Now, if only people would notice Intel processors are actually identified by the signature (cpuid(1).EAX) *and* the platform id bits in MSR 17 (the pf or processor flags)... -- One disk to rule them all, One disk to find them. One disk to bring them all and in the darkness grind them. In the Land of Redmond where the shadows lie. -- The Silicon Valley Tarot Henrique Holschuh -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20130907215900.gd23...@khazad-dum.debian.net
Re: Identifying CPU
at bottom :- On 9/8/13, Henrique de Moraes Holschuh h...@debian.org wrote: Now, if only people would notice Intel processors are actually identified by the signature (cpuid(1).EAX) *and* the platform id bits in MSR 17 (the pf or processor flags)... I had spent quite sometime on the output generated by CPUID yesterday as well as today but was unable to glean the info. that you are telling me. Maybe, just maybe I'm just dumb enough not to get it. -- One disk to rule them all, One disk to find them. One disk to bring them all and in the darkness grind them. In the Land of Redmond where the shadows lie. -- The Silicon Valley Tarot Henrique Holschuh -- Regards, Shirish Agarwal शिरीष अग्रवाल My quotes in this email licensed under CC 3.0 http://creativecommons.org/licenses/by-nc/3.0/ http://flossexperiences.wordpress.com 065C 6D79 A68C E7EA 52B3 8D70 950D 53FB 729A 8B17 -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/cadddzrkw3sgtadxjybe0bm1v1-dabwiyeb9mtt6toez1gyu...@mail.gmail.com
Re: Identifying CPU
On Sun, 08 Sep 2013, shirish शिरीष wrote: On 9/8/13, Henrique de Moraes Holschuh h...@debian.org wrote: Now, if only people would notice Intel processors are actually identified by the signature (cpuid(1).EAX) *and* the platform id bits in MSR 17 (the pf or processor flags)... I had spent quite sometime on the output generated by CPUID yesterday as well as today but was unable to glean the info. that you are telling me. Maybe, just maybe I'm just dumb enough not to get it. I did mean people as in people writing CPU identification programs... The fact is that the processor flags field of MSR #17 is a little known detail which you will only know about if you look at the microcode update system. It isn't even cited in the how to identify the processor sections of Intel manuals as far as I know. And it is Intel-specific, AMD processors work differently. -- One disk to rule them all, One disk to find them. One disk to bring them all and in the darkness grind them. In the Land of Redmond where the shadows lie. -- The Silicon Valley Tarot Henrique Holschuh -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20130907233147.gb25...@khazad-dum.debian.net
Re: Identifying CPU
great tool! On Fri, Sep 6, 2013 at 5:47 PM, shirish शिरीष shirisha...@gmail.com wrote: cpuid is the best if you are looking for any sort of detailed info. See http://forums.debian.net/viewtopic.php?f=10t=106956 for details. -- Regards, Shirish Agarwal शिरीष अग्रवाल My quotes in this email licensed under CC 3.0 http://creativecommons.org/licenses/by-nc/3.0/ http://flossexperiences.wordpress.com 065C 6D79 A68C E7EA 52B3 8D70 950D 53FB 729A 8B17 -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/cadddzrmho5qg2dow+9f9p6ewj2zfk8o9ebnmrnapy2cg+0...@mail.gmail.com -- Danilo Sampaio Skype: danilosampa Msn: danilosa...@hotmail.com Dyad Associados 40084711
Re: Resolved - was [Re: Identifying CPU]
On 9/1/2013 9:44 PM, Joel Rees wrote: On Mon, Sep 2, 2013 at 7:18 AM, Pascal Hambourg pas...@plouf.fr.eu.org wrote: Richard Owlett a écrit : Stan Hoeppner wrote: So I fail to see why your knowing the CPU bus width is relevant to anything. If I understand correctly some processors can run 32 bit OSes but not any 64 bit OS. This has nothing to do with bus width. Not an entirely separate issue from the address bus width, however. While it's possible to back track a CPU's ISA from knowing the address line width, there are far more practical and fool proof methods to determining the ISA. Just for fun, I looked at what this box tells me with lscpu and cat-ting /proc/cpuinfo. The relevant lines in the reply are, for lscpu, CPU op-mode(s):32-bit which tells me that it can run OSses in 32-bit mode, I think. You're making this harder than need be. Look at the 'flags' data in /proc/cpuinfo. If you see 'lm' it's a 64 bit ISA CPU and can run a 64 bit OS. If 'lm' is not present it's a 32 bit only CPU. 'lm' represents Long Mode which is the operating mode of x86-64 processors that enables execution of 64 bit instructions. -- Stan -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/52244145.6000...@hardwarefreak.com
Re: Resolved - was [Re: Identifying CPU]
Stan Hoeppner wrote: On 9/1/2013 8:09 AM, Richard Owlett wrote: Stan Hoeppner wrote: On 8/31/2013 10:00 AM, Richard Owlett wrote: Especially as I explicitly emphasized wanting to know bus width. [snip] You're confusing register width with data bus width. Register width dictates which binary instruction sets can be executed. I wasn't confused. But I evidently confused others. Personally, and for my purposes, the only meaningful widths (address or data) are those on chip. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/52246cc5.4010...@cloud85.net
Re: Resolved - was [Re: Identifying CPU]
On Mon, Sep 2, 2013 at 4:41 PM, Stan Hoeppner s...@hardwarefreak.com wrote: On 9/1/2013 9:44 PM, Joel Rees wrote: On Mon, Sep 2, 2013 at 7:18 AM, Pascal Hambourg pas...@plouf.fr.eu.org wrote: Richard Owlett a écrit : Stan Hoeppner wrote: So I fail to see why your knowing the CPU bus width is relevant to anything. If I understand correctly some processors can run 32 bit OSes but not any 64 bit OS. This has nothing to do with bus width. Not an entirely separate issue from the address bus width, however. While it's possible to back track a CPU's ISA from knowing the address line width, there are far more practical and fool proof methods to determining the ISA. Really? I mean, for the un-initiate? Just for fun, I looked at what this box tells me with lscpu and cat-ting /proc/cpuinfo. The relevant lines in the reply are, for lscpu, CPU op-mode(s):32-bit which tells me that it can run OSses in 32-bit mode, I think. You're making this harder than need be. Look at the 'flags' data in /proc/cpuinfo. If you see 'lm' it's a 64 bit ISA CPU and can run a 64 bit OS. If 'lm' is not present it's a 32 bit only CPU. 'lm' represents Long Mode which is the operating mode of x86-64 processors that enables execution of 64 bit instructions. -- Stan Which is great if you happen to know that lm iin the flags means long mode and that long in this case means the ability to use and calculate long=64 bit addresses at a pace useful enough to run the 64 bit (addressing) OS. (And it's not just us old fogies. There are still a lot of contexts in which long still means 32 bit addresses. Just because Intel is trying to forget its roots doesn't mean the rest of the world is on their bandwagon.) -- Joel Rees -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/CAAr43iPhxR1DmbKEb=td3i_6bkgpnmt18jutvx5gojfsbhx...@mail.gmail.com
Re: Resolved - was [Re: Identifying CPU]
On 9/2/2013 6:11 PM, Joel Rees wrote: On Mon, Sep 2, 2013 at 4:41 PM, Stan Hoeppner s...@hardwarefreak.com wrote: On 9/1/2013 9:44 PM, Joel Rees wrote: On Mon, Sep 2, 2013 at 7:18 AM, Pascal Hambourg pas...@plouf.fr.eu.org wrote: Richard Owlett a écrit : Stan Hoeppner wrote: So I fail to see why your knowing the CPU bus width is relevant to anything. If I understand correctly some processors can run 32 bit OSes but not any 64 bit OS. This has nothing to do with bus width. Not an entirely separate issue from the address bus width, however. While it's possible to back track a CPU's ISA from knowing the address line width, there are far more practical and fool proof methods to determining the ISA. Really? I mean, for the un-initiate? The un-initiate isn't going to care. Just for fun, I looked at what this box tells me with lscpu and cat-ting /proc/cpuinfo. The relevant lines in the reply are, for lscpu, CPU op-mode(s):32-bit which tells me that it can run OSses in 32-bit mode, I think. You're making this harder than need be. Look at the 'flags' data in /proc/cpuinfo. If you see 'lm' it's a 64 bit ISA CPU and can run a 64 bit OS. If 'lm' is not present it's a 32 bit only CPU. 'lm' represents Long Mode which is the operating mode of x86-64 processors that enables execution of 64 bit instructions. Which is great if you happen to know that lm iin the flags means long mode You know now. and that long in this case means the ability to use and calculate long=64 bit addresses at a pace useful enough to run the You seem to be intentionally taking a single word out of context to build an invalid argument below. It's long mode, and yes, context matters, always. 64 bit (addressing) OS. And note there is no such thing as 64 bit addressing. There has not been, nor will there be in the near future, a 64 bit CPU that has 64 bits of either physical or virtual address space. CPUs with 46 bit physical and 48 bit virtual addressing exist today, yielding 64TB physical and 256TB virtual address spaces. 64 bits yields a 16 exabyte address space. 50 bits is 1 petabyte, and it will likely be many years before we see CPUs with 50 bits of physical or virtual addressing. SGI is the only vendor that could make use of a 50 bit address space. But it doesn't appear to they plan to offer the 4096 socket 64 cabinet machine required to hold 1PB of DRAM. Interestingly enough they did build a translation mechanism into the NUMALink 5 router ASIC to support a 50 bit physical address space regardless of the Xeon CPU limitations. They've been stuck at 256 sockets for two generations of Altix UV. I guess it's good to have the capability in the event the US Govt asks for a 4096 socket machine out of the blue. NSA may have already purchased one and we'd never know. And NSA has the prime workload, pattern matching of very large datasets, that require massive main memory. (And it's not just us old fogies. There are still a lot of contexts in which long still means 32 bit addresses. I'm sorry, but long != long mode, no matter your old fogie status. Just because Intel is trying to forget its roots doesn't mean the rest of the world is on their bandwagon.) AMD, not Intel, invented the x86-64® architecture (now AMD64®) of which long mode is a component. Intel reverse engineered and copied it a few years later, and calls it Intel 64®. Your venom is misplaced. -- Stan -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/52256569.5080...@hardwarefreak.com
Re: Resolved - was [Re: Identifying CPU]
On 8/31/2013 10:00 AM, Richard Owlett wrote: Especially as I explicitly emphasized wanting to know bus width. I find it curious Richard that you emphasize this, given that the CPU bus width in isolation is meaningless. Every x86 CPU since the original Pentium that shipped in 1993, up to the Opteron which shipped in 2003, had a 64 bit wide data bus, clocked from 66 to 266MHz, including double/quad pumped buses. Throughput has varied from the first to the last model from 528MB/s to 8.5GB/s. In the post Opteron era the memory buses are decoupled from the system interconnect, the latter no longer being a bus but a apir of bidirectional point-point serial links. Modern CPUs have 2 to 4x 64bit wide memory buses clocked at up to 1600 MHz, for a combined DRAM bandwidth of 25.6 to 51.2GB/s. The system interconnect links, HyperTransport in the case of AMD CPUs, provide from 3.2GB/s to 12.8GB/s one way. On CPUs shipped since 2003 in the case of AMD, later for Intel, there is no singular bus width. There are 2, 3, or 4 memory buses, and a system interconnect, all clocked at different speeds on different vendor models. So I fail to see why your knowing the CPU bus width is relevant to anything. -- Stan -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/52231789.3040...@hardwarefreak.com
Re: Resolved - was [Re: Identifying CPU]
Stan Hoeppner wrote: On 8/31/2013 10:00 AM, Richard Owlett wrote: Especially as I explicitly emphasized wanting to know bus width. I find it curious Richard that you emphasize this, given that the CPU bus width in isolation is meaningless. Every x86 CPU since the original Pentium that shipped in 1993, up to the Opteron which shipped in 2003, had a 64 bit wide data bus, clocked from 66 to 266MHz, including double/quad pumped buses. Throughput has varied from the first to the last model from 528MB/s to 8.5GB/s. In the post Opteron era the memory buses are decoupled from the system interconnect, the latter no longer being a bus but a apir of bidirectional point-point serial links. Modern CPUs have 2 to 4x 64bit wide memory buses clocked at up to 1600 MHz, for a combined DRAM bandwidth of 25.6 to 51.2GB/s. The system interconnect links, HyperTransport in the case of AMD CPUs, provide from 3.2GB/s to 12.8GB/s one way. On CPUs shipped since 2003 in the case of AMD, later for Intel, there is no singular bus width. There are 2, 3, or 4 memory buses, and a system interconnect, all clocked at different speeds on different vendor models. So I fail to see why your knowing the CPU bus width is relevant to anything. 'Cause I'm so old I remember introduction of 8085 and a Z80A was considered a speed demon at 2 MHz ;/ If I understand correctly some processors can run 32 bit OSes but not any 64 bit OS. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/52233c86.4080...@cloud85.net
Re: Resolved - was [Re: Identifying CPU]
Richard Owlett a écrit : Stan Hoeppner wrote: So I fail to see why your knowing the CPU bus width is relevant to anything. If I understand correctly some processors can run 32 bit OSes but not any 64 bit OS. This has nothing to do with bus width. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/5223bd3e.3000...@plouf.fr.eu.org
Re: Resolved - was [Re: Identifying CPU]
On Mon, Sep 2, 2013 at 7:18 AM, Pascal Hambourg pas...@plouf.fr.eu.org wrote: Richard Owlett a écrit : Stan Hoeppner wrote: So I fail to see why your knowing the CPU bus width is relevant to anything. If I understand correctly some processors can run 32 bit OSes but not any 64 bit OS. This has nothing to do with bus width. Not an entirely separate issue from the address bus width, however. :-P Just for fun, I looked at what this box tells me with lscpu and cat-ting /proc/cpuinfo. The relevant lines in the reply are, for lscpu, CPU op-mode(s):32-bit which tells me that it can run OSses in 32-bit mode, I think. (We could talk about data and address register width, but it's more to the point to talk about OSses running in 32-bit mode.) and, for cat /proc/info address sizes : 34 bits physical, 32 bits virtual which tells me I should be able to run PAE. (I am running PAE.) And, if the motherboard had enough address lines, I should be able to put in more than 2G of RAM, but the manual says just 2G. So, maybe not. Some things in there that might be worth a try if I had the time. -- Joel Rees -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/CAAr43iNeMHDikOC1k4o9oU=od05qyq62xkq0kx_a3aurpv3...@mail.gmail.com
Re: Resolved - was [Re: Identifying CPU]
On 9/1/2013 8:09 AM, Richard Owlett wrote: Stan Hoeppner wrote: On 8/31/2013 10:00 AM, Richard Owlett wrote: Especially as I explicitly emphasized wanting to know bus width. I find it curious Richard that you emphasize this, given that the CPU bus width in isolation is meaningless. Every x86 CPU since the original Pentium that shipped in 1993, up to the Opteron which shipped in 2003, had a 64 bit wide data bus, clocked from 66 to 266MHz, including double/quad pumped buses. Throughput has varied from the first to the last model from 528MB/s to 8.5GB/s. In the post Opteron era the memory buses are decoupled from the system interconnect, the latter no longer being a bus but a apir of bidirectional point-point serial links. Modern CPUs have 2 to 4x 64bit wide memory buses clocked at up to 1600 MHz, for a combined DRAM bandwidth of 25.6 to 51.2GB/s. The system interconnect links, HyperTransport in the case of AMD CPUs, provide from 3.2GB/s to 12.8GB/s one way. On CPUs shipped since 2003 in the case of AMD, later for Intel, there is no singular bus width. There are 2, 3, or 4 memory buses, and a system interconnect, all clocked at different speeds on different vendor models. So I fail to see why your knowing the CPU bus width is relevant to anything. 'Cause I'm so old I remember introduction of 8085 and a Z80A was considered a speed demon at 2 MHz ;/ If I understand correctly some processors can run 32 bit OSes but not any 64 bit OS. You're confusing register width with data bus width. Register width dictates which binary instruction sets can be executed. The width of the data bus(es) simply dictates how much data you can move per unit time to DRAM and peripherals. There is no correlation between register width and data bus width. Using examples from an era that you're more familiar with, the Intel 8086 had a 16 bit register width and a 16 bit data bus to the system. Intel shortly thereafter released the 8088 which ditched the 16 bit data bus for an 8 bit bus. This was done to reduce the cost of the system, and as a result reduced IO performance by 50%. Intel did this again with the 80386sx, taking the 80386 CPU with a 32 bit register width and a 32 bit data bus, and reducing the data bus to 16 bits, again to reduce system costs. -- Stan -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/5224091c.30...@hardwarefreak.com
Re: Identifying CPU
Richard Owlett wrote, on 08/29/2013 15:25: I'll be installing Debian 7.1 on two unrelated sets of machines. I have no record of the cpu in any of the machines. Is there a utility to identify the processors, particularly bus width. All machines originally ran various 32 bit MS Windows incarnations. Three personal machines: 1. A Lenovo desktop currently running WinXP Pro SP3 2. An IBM/Lenovo T43 Thinkpad laptop running WinXP Pro SP3 3. A Lenovo R61 Thinkpad laptop currently running various configurations of Squeeze. There were stickers on it when I purchased it saying Intel Core2 Duo and Windows Vista Basic. Windows was completely removed when I installed Squeeze. A collection of donated machines at church being used for a outreach program for the neighborhood K-6 children. OS include Win98 and later. For the time being all Debian installs will be 32 bit. In a year or so, capable machines will be migrated to 64 bit. There are non-technical constraints precluding immediate migration to 64 bit. Suggestions/comments? TIA Why not try a Debian Live install image (http://www.debian.org/CD/live/) on CD, DVD, or USB stick? Then, with a running Linux-system a command like cat /proc/cpuinfo shows capabilites of the cpu. Regards, jvp -- -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/5221b461.1060...@web.de
Resolved - was [Re: Identifying CPU]
Richard Owlett wrote: I'll be installing Debian 7.1 on two unrelated sets of machines. I have no record of the cpu in any of the machines. Is there a utility to identify the processors, particularly bus width. All machines originally ran various 32 bit MS Windows incarnations. [snip] The best answer was /usr/bin/lscpu Especially as I explicitly emphasized wanting to know bus width. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/52220523.5010...@cloud85.net
Re: Identifying CPU
On Thursday 29 August 2013 14:25:35 Richard Owlett wrote: K-6 children What are K-6 children?? Lisi -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/201308301619.39505.lisi.re...@gmail.com
Re: Identifying CPU
How about Children in Kindergarten through 6th Grade. John Graves On 8/30/2013 11:19 AM, Lisi Reisz wrote: On Thursday 29 August 2013 14:25:35 Richard Owlett wrote: K-6 children What are K-6 children?? Lisi -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/5220b8ee.1090...@verizon.net
Re: Identifying CPU
On Friday 30 August 2013 16:23:26 John wrote: How about Children in Kindergarten through 6th Grade. John Graves On 8/30/2013 11:19 AM, Lisi Reisz wrote: On Thursday 29 August 2013 14:25:35 Richard Owlett wrote: K-6 children What are K-6 children?? This is an international list. Your use of the word through suggests that you are American. It is not obvious to someone not familiar with the United States education systmem what K-6 means. Here is the result of googling: https://www.google.co.uk/#q=k-6 Lisi -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/201308301634.52432.lisi.re...@gmail.com
Re: Identifying CPU
On Thu, Aug 29, 2013 at 08:25:35AM -0500, Richard Owlett wrote: I'll be installing Debian 7.1 on two unrelated sets of machines. I have no record of the cpu in any of the machines. Is there a utility to identify the processors, particularly bus width. All machines originally ran various 32 bit MS Windows incarnations. Three personal machines: 1. A Lenovo desktop currently running WinXP Pro SP3 2. An IBM/Lenovo T43 Thinkpad laptop running WinXP Pro SP3 3. A Lenovo R61 Thinkpad laptop currently running various configurations of Squeeze. There were stickers on it when I purchased it saying Intel Core2 Duo and Windows Vista Basic. Windows was completely removed when I installed Squeeze. A collection of donated machines at church being used for a outreach program for the neighborhood K-6 children. OS include Win98 and later. For the time being all Debian installs will be 32 bit. In a year or so, capable machines will be migrated to 64 bit. There are non-technical constraints precluding immediate migration to 64 bit. Suggestions/comments? TIA cat /proc/cpuinfo and Google will do the job. -- staticsafe O ascii ribbon campaign - stop html mail - www.asciiribbon.org Please don't top post. Please don't CC! I'm subscribed to whatever list I just posted on. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20130829135841.gd31...@uriel.asininetech.com
Re: Identifying CPU
On Thursday 29 August 2013 07:28 PM, staticsafe wrote: On Thu, Aug 29, 2013 at 08:25:35AM -0500, Richard Owlett wrote: I'll be installing Debian 7.1 on two unrelated sets of machines. I have no record of the cpu in any of the machines. Is there a utility to identify the processors, particularly bus width. All machines originally ran various 32 bit MS Windows incarnations. Three personal machines: 1. A Lenovo desktop currently running WinXP Pro SP3 2. An IBM/Lenovo T43 Thinkpad laptop running WinXP Pro SP3 3. A Lenovo R61 Thinkpad laptop currently running various configurations of Squeeze. There were stickers on it when I purchased it saying Intel Core2 Duo and Windows Vista Basic. Windows was completely removed when I installed Squeeze. A collection of donated machines at church being used for a outreach program for the neighborhood K-6 children. OS include Win98 and later. For the time being all Debian installs will be 32 bit. In a year or so, capable machines will be migrated to 64 bit. There are non-technical constraints precluding immediate migration to 64 bit. Suggestions/comments? TIA cat /proc/cpuinfo and Google will do the job. Hi Richard, A few weeks ago we had an interesting thread discussing the performance advantage of 64bit vs 32bit kernels and the outcome was that except for server loads where a couple of % points make a difference, you may not really need to go for 64bit. So, unless there's a reason like huge amounts of RAM, you're better off with the 32bit kernel. 2 cents, Kailash -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/521f55df.2010...@gmail.com
Re: Identifying CPU
Le 29/08/2013 15:25, Richard Owlett a écrit : I'll be installing Debian 7.1 on two unrelated sets of machines. I have no record of the cpu in any of the machines. Is there a utility to identify the processors, particularly bus width. All machines originally ran various 32 bit MS Windows incarnations. $ apt-file search lscpu manpages-fr-extra: /usr/share/man/fr/man1/lscpu.1.gz manpages-pl: /usr/share/man/pl/man1/lscpu.1.gz util-linux: /usr/bin/lscpu util-linux: /usr/share/man/man1/lscpu.1.gz My 2 cents, rudu -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/521f87bd.50...@cegetel.net
