Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

si.system() does not return raspberry on Raspberry Pi 4 #881

Open
KristjanESPERANTO opened this issue Jan 14, 2024 · 6 comments
Open

si.system() does not return raspberry on Raspberry Pi 4 #881

KristjanESPERANTO opened this issue Jan 14, 2024 · 6 comments

Comments

@KristjanESPERANTO
Copy link

Thanks for this great library! I have the following issue: si.system() does not return raspberry on Raspberry Pi 4

Steps to reproduce the behavior

  1. used function: si.system()
  2. code snippet
    const si = require("systeminformation");
    async function logSystemInformation () {
    try {
    	const staticData = await si.system();
    	console.info(staticData);
        } catch (e) {
    	console.error(e);
        }
    }
    logSystemInformation()
  3. start app / code: node test.js
  4. See output/error
    {
      manufacturer: '',
      model: '',
      version: 'd03114',
      serial: '10000000XXXXXXXX',
      uuid: '',
      sku: '-',
      virtual: false
    }

Expected behavior

    {
      manufacturer: '',
      model: '',
      version: 'd03114',
      serial: '10000000XXXXXXXX',
      uuid: '',
      raspberry: 'Raspberry Pi 4 Model B Rev 1.4',
      sku: '-',
      virtual: false
    }

Environment

$ npx systeminformation info
┌─────────────────────────────────────────────────────────────────────────────────────────┐
│  SYSTEMINFORMATION                                                     Version: 5.21.22 │
└─────────────────────────────────────────────────────────────────────────────────────────┘

Operating System:
──────────────────────────────────────────────────────────────────────────────────────────
Platform         : linux
Distro           : Debian GNU/Linux
Release          : 12
Codename         : bookworm
Kernel           : 6.1.0-rpi7-rpi-v8
Arch             : arm64
Hostname         : raspberrypi
Codepage         : UTF-8
Build            : 

System:
──────────────────────────────────────────────────────────────────────────────────────────
Manufacturer     : 
Model            : 
Version          : d03114
Virtual          : 

CPU:
──────────────────────────────────────────────────────────────────────────────────────────
Manufacturer     : Sony UK
Brand            : BCM2711
Family           : Cortex-A72
Model            : 3
Stepping         : r0p3
Speed            : 1.8
Cores            : 4
PhysicalCores    : 4
PerformanceCores : 4
EfficiencyCores  : 
Processors       : 1
Socket           : SOC

Additional context

When I run cat /proc/cpuinfo, I get this:

processor	: 0
BogoMIPS	: 108.00
Features	: fp asimd evtstrm crc32 cpuid
CPU implementer	: 0x41
CPU architecture: 8
CPU variant	: 0x0
CPU part	: 0xd08
CPU revision	: 3

processor	: 1
BogoMIPS	: 108.00
Features	: fp asimd evtstrm crc32 cpuid
CPU implementer	: 0x41
CPU architecture: 8
CPU variant	: 0x0
CPU part	: 0xd08
CPU revision	: 3

processor	: 2
BogoMIPS	: 108.00
Features	: fp asimd evtstrm crc32 cpuid
CPU implementer	: 0x41
CPU architecture: 8
CPU variant	: 0x0
CPU part	: 0xd08
CPU revision	: 3

processor	: 3
BogoMIPS	: 108.00
Features	: fp asimd evtstrm crc32 cpuid
CPU implementer	: 0x41
CPU architecture: 8
CPU variant	: 0x0
CPU part	: 0xd08
CPU revision	: 3

Revision	: d03114
Serial		: 10000000XXXXXXXX
Model		: Raspberry Pi 4 Model B Rev 1.4
@sebhildebrandt
Copy link
Owner

@KristjanESPERANTO thank you! I will have a look at it. As I am currently not in my office, I can check it in apron 1 week the earliest. I am pretty sure to find the reason and to provide a fix. Once again, thank you for your report and all provided information.

@markmiro
Copy link

Having the same issue with a Raspberry Pi 5 with bookworm. It can't detect that it's a pi.

const { raspberry } = await systeminfo.system();
console.log(raspberry); // returns undefined
$ cat /etc/os-release
PRETTY_NAME="Debian GNU/Linux 12 (bookworm)"
NAME="Debian GNU/Linux"
VERSION_ID="12"
VERSION="12 (bookworm)"
VERSION_CODENAME=bookworm
ID=debian
# ...
$ cat /proc/cpuinfo
# ...
CPU part        : 0xd0b
CPU revision    : 1

Revision        : c04170
Serial          : fd2263ad97a4f1e2
Model           : Raspberry Pi 5 Model B Rev 1.0

@SquirrelCorporation
Copy link

SquirrelCorporation commented Apr 5, 2024

Same issue here, additionnally, not sending anything too with Rpi5

pi@raspberrypi-5:~ $ cat /proc/cpuinfo
processor	: 0
BogoMIPS	: 108.00
Features	: fp asimd evtstrm aes pmull sha1 sha2 crc32 atomics fphp asimdhp cpuid asimdrdm lrcpc dcpop asimddp
CPU implementer	: 0x41
CPU architecture: 8
CPU variant	: 0x4
CPU part	: 0xd0b
CPU revision	: 1

processor	: 1
BogoMIPS	: 108.00
Features	: fp asimd evtstrm aes pmull sha1 sha2 crc32 atomics fphp asimdhp cpuid asimdrdm lrcpc dcpop asimddp
CPU implementer	: 0x41
CPU architecture: 8
CPU variant	: 0x4
CPU part	: 0xd0b
CPU revision	: 1

processor	: 2
BogoMIPS	: 108.00
Features	: fp asimd evtstrm aes pmull sha1 sha2 crc32 atomics fphp asimdhp cpuid asimdrdm lrcpc dcpop asimddp
CPU implementer	: 0x41
CPU architecture: 8
CPU variant	: 0x4
CPU part	: 0xd0b
CPU revision	: 1

processor	: 3
BogoMIPS	: 108.00
Features	: fp asimd evtstrm aes pmull sha1 sha2 crc32 atomics fphp asimdhp cpuid asimdrdm lrcpc dcpop asimddp
CPU implementer	: 0x41
CPU architecture: 8
CPU variant	: 0x4
CPU part	: 0xd0b
CPU revision	: 1

Revision	: d04170
Serial		: 9c69a2344e20a994
Model		: Raspberry Pi 5 Model B Rev 1.0
pi@raspberrypi-5:~ $ cat /etc/os-release
PRETTY_NAME="Debian GNU/Linux 12 (bookworm)"
NAME="Debian GNU/Linux"
VERSION_ID="12"
VERSION="12 (bookworm)"
VERSION_CODENAME=bookworm
ID=debian
HOME_URL="https://www.debian.org/"
SUPPORT_URL="https://www.debian.org/support"
BUG_REPORT_URL="https://bugs.debian.org/"

pi@raspberrypi:/opt/squirrelserversmanager $ cat /proc/cpuinfo
processor	: 0
BogoMIPS	: 38.40
Features	: fp asimd evtstrm crc32 cpuid
CPU implementer	: 0x41
CPU architecture: 8
CPU variant	: 0x0
CPU part	: 0xd03
CPU revision	: 4

processor	: 1
BogoMIPS	: 38.40
Features	: fp asimd evtstrm crc32 cpuid
CPU implementer	: 0x41
CPU architecture: 8
CPU variant	: 0x0
CPU part	: 0xd03
CPU revision	: 4

processor	: 2
BogoMIPS	: 38.40
Features	: fp asimd evtstrm crc32 cpuid
CPU implementer	: 0x41
CPU architecture: 8
CPU variant	: 0x0
CPU part	: 0xd03
CPU revision	: 4

processor	: 3
BogoMIPS	: 38.40
Features	: fp asimd evtstrm crc32 cpuid
CPU implementer	: 0x41
CPU architecture: 8
CPU variant	: 0x0
CPU part	: 0xd03
CPU revision	: 4

Revision	: a020d3
Serial		: 0000000090f37455
Model		: Raspberry Pi 3 Model B Plus Rev 1.3
pi@raspberrypi:/opt/squirrelserversmanager $ cat /etc/os-release
PRETTY_NAME="Debian GNU/Linux 12 (bookworm)"
NAME="Debian GNU/Linux"
VERSION_ID="12"
VERSION="12 (bookworm)"
VERSION_CODENAME=bookworm
ID=debian
HOME_URL="https://www.debian.org/"
SUPPORT_URL="https://www.debian.org/support"
BUG_REPORT_URL="https://bugs.debian.org/"

@Erwin40
Copy link

Erwin40 commented Dec 3, 2024

Toll, mal wieder auf ein totes Package gesetzt. :-(
Entwickler scheint keine Lust mehr zu haben, hier was weiterzuentwickeln..
Sehr schade...

@KristjanESPERANTO
Copy link
Author

Toll, mal wieder auf ein totes Package gesetzt. :-( Entwickler scheint keine Lust mehr zu haben, hier was weiterzuentwickeln.. Sehr schade...

It's Open Source, you are free to fix this in your own fork 🤷 And please read the CODE_OF_CONDUCT before you comment again.

@Erwin40
Copy link

Erwin40 commented Dec 3, 2024

Naja, bei 122 offenen Issues kann man schon mal die Tatsachen beim Namen nennen.
Ich weiß das ich das selber fixen könnte. Aber dann hätte ich wohl kaum das hier eingesetzt und mir gleich die Informationen zusammen gesucht, mit Boardmitteln, soweit möglich.
Ich habe das hier auch geschrieben, weil ein an und für sich gut dokumentiertes und umfangreiches Tool nicht weiterentwickelt wird.
Und das ist genau das verhängnisvolle an Open Source. Ist leider kein Einzelfall. Besonders dann wenn nur eine Person verantwortlich ist.
Sollte wirklich nicht persöhnlich gegen den freiwilligen Entwickler gehen!
Sondern eher meine Entäuschung wiederspiegeln.
Und bei einem unwichtigen Tool hätte ich sowieso nix geschrieben ;-)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants