|
Error on the new Raspberry PI 400
Hey H2 long time no see. So I recently purchase the shiny new Raspberry PI 400.
I was surprised to see inxi in the repos. Very cool. Any way the script shows an error. Argument "Raspberry Pi 400 Rev 1.0" isn't numeric in sprintf at /usr/bin/inxi line 6969. The full output. :: Code :: $ inxi -F
System: Host: raspberrypi Kernel: 5.10.11-v8+ aarch64 bits: 64 Desktop: LXDE 0.10.0 Distro: Debian GNU/Linux 10 (buster) Machine: Type: ARM Device System: Raspberry Pi 400 Rev 1.0 details: BCM2835 rev: c03130 serial: 10000000db2f6389 Argument "Raspberry Pi 400 Rev 1.0" isn't numeric in sprintf at /usr/bin/inxi line 6969. CPU: Topology: Quad Core model: N/A variant: cortex-a72 bits: 64 type: MCP Speed: 1800 MHz min/max: 600/1800 MHz Core speeds (MHz): 1: 1800 2: 1800 3: 1800 4: 1800 Graphics: Device-1: bcm2711-vc5 driver: vc4_drm v: N/A Device-2: bcm2711-hdmi0 driver: N/A Device-3: bcm2711-hdmi1 driver: N/A Display: x11 server: X.Org 1.20.4 driver: N/A resolution: 1360x768~60Hz OpenGL: renderer: V3D 4.2 v: 2.1 Mesa 19.3.2 Audio: Device-1: bcm2835-audio driver: bcm2835_audio Device-2: bcm2711-hdmi0 driver: N/A Device-3: bcm2711-hdmi1 driver: N/A Sound Server: ALSA v: k5.10.11-v8+ Network: Message: No ARM data found for this feature. IF-ID-1: eth0 state: down mac: dc:a6:32:cd:41:53 IF-ID-2: proton0 state: unknown speed: 10 Mbps duplex: full mac: N/A IF-ID-3: wlan0 state: up mac: dc:a6:32:cd:41:54 Drives: Local Storage: total: 292.50 GiB used: 42.82 GiB (14.6%) ID-1: /dev/mmcblk0 model: EC2QT size: 59.62 GiB ID-2: /dev/sda type: USB vendor: SanDisk model: USB 3.2Gen1 size: 232.88 GiB Partition: ID-1: / size: 58.41 GiB used: 10.99 GiB (18.8%) fs: ext4 dev: /dev/mmcblk0p2 ID-2: /boot size: 252.0 MiB used: 29.3 MiB (11.6%) fs: vfat dev: /dev/mmcblk0p1 Sensors: System Temperatures: cpu: 37.5 C mobo: N/A Fan Speeds (RPM): N/A Info: Processes: 205 Uptime: 21h 11m Memory: 3.78 GiB used: 1.73 GiB (45.8%) gpu: 76.0 MiB Shell: bash inxi: 3.0.32 Back to top |
|
yo mr evil... long time no see too.
but you fell for the 'frozen pool inxi' issue, that particular arm error is tedious because it was fixed ages ago. /etc/inxi.conf change B_ALLOW_UPDATE=false to true, save, then sudo inxi -U and all will be hunky dory as far as I know. ARM in particular should not use the frozen inxi becuase arm devices do not follow strict rules etc, and supporting them is always an ongoing process, inxi can't predict what stuff will do the future when it comes to android/arm, sadly, so keeping legacy inxi's in the frozen repos does the users little good. Back to top |
|
Thanks all good.
Back to top |
|
Can you show: inxi -Fazy
I haven't had access to a rp4, in your initial sample, it had missed both networking devices. I know in rp3 they used a weird mmc wifi chip, which inxi doesn't know how to detect, but did it also miss the lan chip? Back to top |
|
All times are GMT - 8 Hours |