Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.user > #167592
| From | David Wright <deblis@lionunicorn.co.uk> |
|---|---|
| Newsgroups | linux.debian.user |
| Subject | Re: libpepflashplayer.so |
| Date | 2016-05-09 01:00 +0200 |
| Message-ID | <rwFQ5-7xe-1@gated-at.bofh.it> (permalink) |
| References | (1 earlier) <rwvnI-6dm-11@gated-at.bofh.it> <rwvH4-6K0-15@gated-at.bofh.it> <rww0p-6Zl-5@gated-at.bofh.it> <rwD1T-4Ci-5@gated-at.bofh.it> <rwF3I-73q-7@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
On Sun 08 May 2016 at 19:00:29 (-0300), Henrique de Moraes Holschuh wrote:
> On Sun, 08 May 2016, Teemu Likonen wrote:
> > Lisi Reisz [2016-05-08 13:25:46+01] wrote:
> > > Or perhaps check the model - it is an old Dell, but the crucial
> > > question is what chip that model had, so which exact model.
> >
> > For 64 bit CPUs "lscpu" command prints:
> >
> > CPU op-mode(s): 32-bit, 64-bit
>
> The output of "cat /proc/cpuinfo", as well as that of "dmidecode" is usually
> a lot more useful for diagnostics. The dmidecode output might have serial
> numbers and UUIDs, which you should not post to the list, so feel free to
> XXXXX them out beforehand.
This is all rather ambiguous.
If dmidecode says:
Handle 0x0400, DMI type 4, 40 bytes
Processor Information
Socket Designation: Microprocessor
Type: Central Processor
Family: Pentium M
Manufacturer: Intel
ID: [...]
Signature: Type 0, Family 6, Model 15, Stepping 2
Flags:
FPU (Floating-point unit on-chip)
[...]
Part Number: Not Specified
Core Count: 2
Core Enabled: 2
Thread Count: 2
Characteristics:
64-bit capable
and the machine is only running a 32-bit Debian system and kernel,
would cpuinfo still say "CPU op-mode(s): 32-bit, 64-bit"?
Or does cpuinfo only mention "CPU op-mode(s): 32-bit, 64-bit"
when the OS actually running has those two modes available to it now?
Cheers,
David.
Back to linux.debian.user | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
libpepflashplayer.so Lisi Reisz <lisi.reisz@gmail.com> - 2016-05-07 11:40 +0200
Re: libpepflashplayer.so Curt <curty@free.fr> - 2016-05-07 18:30 +0200
Re: libpepflashplayer.so Sven Hartge <sven@svenhartge.de> - 2016-05-07 19:40 +0200
Re: libpepflashplayer.so Curt <curty@free.fr> - 2016-05-07 20:10 +0200
Re: libpepflashplayer.so Lisi Reisz <lisi.reisz@gmail.com> - 2016-05-07 23:50 +0200
Re: libpepflashplayer.so Lisi Reisz <lisi.reisz@gmail.com> - 2016-05-07 23:50 +0200
Re: libpepflashplayer.so Sven Hartge <sven@svenhartge.de> - 2016-05-08 00:30 +0200
Re: libpepflashplayer.so Lisi Reisz <lisi.reisz@gmail.com> - 2016-05-08 13:50 +0200
Re: libpepflashplayer.so Sven Hartge <sven@svenhartge.de> - 2016-05-08 14:10 +0200
Re: libpepflashplayer.so Lisi Reisz <lisi.reisz@gmail.com> - 2016-05-08 14:30 +0200
Re: libpepflashplayer.so Sven Hartge <sven@svenhartge.de> - 2016-05-08 15:20 +0200
Re: libpepflashplayer.so Teemu Likonen <tlikonen@iki.fi> - 2016-05-08 22:00 +0200
Re: libpepflashplayer.so Henrique de Moraes Holschuh <hmh@debian.org> - 2016-05-09 00:10 +0200
Re: libpepflashplayer.so David Wright <deblis@lionunicorn.co.uk> - 2016-05-09 01:00 +0200
Re: libpepflashplayer.so Henrique de Moraes Holschuh <hmh@debian.org> - 2016-05-09 02:40 +0200
Re: libpepflashplayer.so Sven Hartge <sven@svenhartge.de> - 2016-05-09 03:10 +0200
Re: libpepflashplayer.so Lisi Reisz <lisi.reisz@gmail.com> - 2016-05-09 10:10 +0200
Re: libpepflashplayer.so Sven Hartge <sven@svenhartge.de> - 2016-05-09 15:10 +0200
Re: libpepflashplayer.so David Wright <deblis@lionunicorn.co.uk> - 2016-05-09 03:20 +0200
Re: libpepflashplayer.so Henrique de Moraes Holschuh <hmh@debian.org> - 2016-05-08 18:20 +0200
Re: libpepflashplayer.so Sven Hartge <sven@svenhartge.de> - 2016-05-08 19:30 +0200
csiph-web