Inxi / pinxi ARM (or MIPS) testers appreciated


#41

pinxi -zv8 on Odroid C2, let me know if you need any further info!

System:    Host: odroidc2 Kernel: 3.14.79-odroidc2 aarch64 bits: 64 compiler: gcc v: 5.5.0 Console: N/A dm: N/A 
           Distro: Armbian GNU/Linux 9 (stretch) 
Machine:   Type: ARM Device System: ODROID-C2 rev: 020c 
Battery:   ID-1: battery charge: N/A condition: N/A volts: 0.0/N/A model: N/A type: Li-ion serial: N/A 
           status: Charging 
Memory:    RAM: total: 1.68 GiB used: 606.0 MiB (35.3%) 
           RAM Report: missing: Required program dmidecode not available 
PCI Slots: ARM: No ARM data found for this feature. 
CPU:       Topology: Quad Core model: N/A variant: cortex-a53 bits: 64 type: MCP arch: ARMv8 family: 8 
           model-id: N/A stepping: 4 microcode: N/A bogomips: 0 
           Speed: 1536 MHz min/max: 100/1536 MHz Core speeds (MHz): 1: 1536 2: 1536 3: 1536 4: 1536 
           Features: asimd crc32 fp 
           Vulnerabilities: No CPU vulnerability/bugs data available. 
Graphics:  Device-1: amhdmitx driver: amhdmitx v: N/A bus ID: N/A chip ID: amlogic:amhdmitx 
           Device-2: mali-450 driver: mali_utgard v: N/A bus ID: N/A chip ID: arm:d00c0000 
           Device-3: odroid_hdmi driver: odroid_hdmi_snd v: N/A bus ID: N/A chip ID: sound_card:odroid_hdmi 
           Display: server: No display server data found. Headless machine? tty: 179x49 
           Message: Unable to show advanced data. Required tool glxinfo missing. 
Audio:     Device-1: amhdmitx driver: amhdmitx bus ID: N/A chip ID: amlogic:amhdmitx 
           Device-2: odroid_hdmi driver: odroid_hdmi_snd bus ID: N/A chip ID: sound_card:odroid_hdmi 
           Sound Server: ALSA v: k3.14.79-odroidc2 
Network:   Device-1: gxbb-rgmii-dwmac driver: stmmaceth v: N/A port: N/A bus ID: N/A chip ID: amlogic:c9410000 
           IF: eth0 state: up speed: 100 Mbps duplex: full mac: <filter> 
           IP v4: <filter> scope: global broadcast: <filter> 
           IP v6: <filter> type: temporary dynamic scope: global 
           IP v6: <filter> type: temporary deprecated dynamic scope: global 
           IP v6: <filter> type: temporary deprecated dynamic scope: global 
           IP v6: <filter> type: temporary deprecated dynamic scope: global 
           IP v6: <filter> type: temporary deprecated dynamic scope: global 
           IP v6: <filter> type: temporary deprecated dynamic scope: global 
           IP v6: <filter> type: temporary deprecated dynamic scope: global 
           IP v6: <filter> type: mngtmpaddr noprefixroute scope: global 
           IP v6: <filter> scope: link 
           IF-ID-1: bond0 state: down mac: <filter> 
           IF-ID-2: bonding_masters state: N/A speed: N/A duplex: N/A mac: N/A 
           WAN IP: <filter> 
Drives:    Local Storage: total: 1.85 TiB used: 111.61 GiB (5.9%) 
           ID-1: /dev/mmcblk0 model: BGND3R size: 29.12 GiB block size: physical: 512 B logical: 512 B 
           serial: <filter> scheme: MBR 
           ID-2: /dev/sda type: USB vendor: Toshiba model: DT01ACA200 size: 1.82 TiB block size: 
           physical: 512 B logical: 512 B rotation: 7200 rpm serial: <filter> scheme: MBR 
           Message: No Optical or Floppy data was found. 
RAID:      Message: No RAID data was found. 
Partition: ID-1: / raw size: 28.83 GiB size: 28.35 GiB (98.36%) used: 4.94 GiB (17.4%) fs: ext4 
           dev: /dev/mmcblk0p1 label: N/A uuid: 8cb90750-ea48-43f0-ac15-ce5eeb5a9aae 
           ID-2: /home raw size: 1.10 TiB size: 1.09 TiB (98.34%) used: 106.67 GiB (9.6%) fs: ext4 
           dev: /dev/sda2 label: USERS uuid: e3a43399-1768-420d-8958-e8434e6fd417 
Unmounted: ID-1: /dev/sda1 size: 732.42 GiB fs: ext4 label: BACKUP uuid: 3b235458-2116-4851-96e0-fbb9cd15d7b3 
USB:       Hub: 1-0:1 info: Full speed (or root) Hub ports: 1 rev: 2.0 speed: 480 Mb/s chip ID: 1d6b:0002 
           Hub: 1-1:2 info: Genesys Logic 4-port hub ports: 4 rev: 2.0 speed: 480 Mb/s chip ID: 05e3:0610 
           Device-1: 1-1.2:4 info: TrekStor & KG type: Mass Storage driver: usb-storage interfaces: 1 rev: 2.1 
           speed: 480 Mb/s chip ID: 1e68:007d serial: <filter> 
           Hub: 2-0:1 info: Full speed (or root) Hub ports: 1 rev: 2.0 speed: 480 Mb/s chip ID: 1d6b:0002 
Sensors:   System Temperatures: cpu: 41.0 C mobo: N/A 
           Fan Speeds (RPM): N/A 
Repos:     Active apt repos in: /etc/apt/sources.list 
           1: deb http://httpredir.debian.org/debian stretch main contrib non-free
           2: deb http://httpredir.debian.org/debian stretch-updates main contrib non-free
           3: deb http://httpredir.debian.org/debian stretch-backports main contrib non-free
           4: deb http://security.debian.org/ stretch/updates main contrib non-free
           Active apt repos in: /etc/apt/sources.list.d/armbian.list 
           1: deb http://apt.armbian.com stretch main stretch-utils stretch-desktop
Processes: CPU top: 5 
           1: cpu: 0.5% command: zsh pid: 20369 mem: 3.90 MiB (0.2%) 
           2: cpu: 0.4% command: mosh-server pid: 20228 mem: 3.07 MiB (0.1%) 
           3: cpu: 0.4% command: -zsh pid: 20229 mem: 3.43 MiB (0.1%) 
           4: cpu: 0.3% command: [kworker/0:2] pid: 18223 mem: 0.00 MiB (0.0%) 
           5: cpu: 0.2% command: haveged pid: 468 mem: 1.14 MiB (0.0%) 
           Memory top: 5 
           1: mem: 164.0 MiB (9.5%) command: mysqld pid: 902 cpu: 0.2% 
           2: mem: 43.5 MiB (2.5%) command: apache2 pid: 10955 cpu: 0.0% 
           3: mem: 37.8 MiB (2.2%) command: apache2 pid: 11310 cpu: 0.0% 
           4: mem: 35.3 MiB (2.0%) command: apache2 pid: 10960 cpu: 0.0% 
           5: mem: 34.9 MiB (2.0%) command: apache2 pid: 13084 cpu: 0.1% 
Info:      Processes: 124 Uptime: 19d 23h 44m Init: systemd v: 232 runlevel: 5 Compilers: gcc: 6.3.0 alt: 4.9/6 
           Shell: zsh v: 5.3.1 pinxi: 3.0.24-52

#42

Oh! It got the networking device, great!! I didn’t expect that to work, unexpected bonus from the recent updates. If I remember right, /proc/cpuinfo for the C2 doesn’t have machine data, so that missing data is not going to be available.

If you want to fire off a pinxi --debug 22 that would be good, the more datasets I have for ARM the better, just in case there are small variants in those devices I was not aware of.


#43

inxi 3.0.25 now done, with all these MIPS/ARM fixes, thanks for taking the time to debug and test.


#44

Just uploaded a dataset for a Odroid-XU4. Called pinxi-ARM-odroid-server-2018-10-27_202725-3.0.27.tar.gz.


#45

Handled via inxi github issue, but for others, Odroid XU4 is now handled, and several glitches/bugs were fixed re the 2 cpu speed handling. Also trimmed out some extra Audio Device items that should not have been there. In current pinxi, and will be in inxi 3.0.28 when it comes out.


#46

Just uploaded a debug from the new Pinebook.

File is called:
inxi-ARM-manjaro-arm-2018-11-12_205730-3.0.27.tar.gz


#47

Try the current pinxi, that includes fixes that are relevant. I’ve also added fixes for the pinebook weaknesses in that dataset, like the battery charge percent, more filters for audio devices. Note that no data is available for charge wh/ah, but I could tweak inxi battery to add in percent if nothing else is found for charge data. I was hoping to be able to find battery size, but that is also not available.

I am unable currently to understand why the voltage now/min data is not showing, it’s there in the raw data. I’ve added several debuggers to the battery section to help me see why something appears or does not appear.

I cannot yet see any clear way to get rid of those excess wifi devices listed, pinebook is using an odd way of identifying network related devices, and calls them all wifi even though clearly they are not all wifi.

pinxi already had some new filters for excessive audio devices, and I’ve added in a few more based on the dataset.


#48

Just uploaded a new one from pinxi 3.0.27-9 of the Pinebook… :slight_smile:


#49

Just did -10, but found a few things, logging the battery data helped:

  1. there is no way to identify the battery as a system battery, not a device battery, that’s why the voltage/charge percent is not showing. I’d have to check several laptop battery datasets to make sure there is never voltage now/design min data for things like wifi mice/keyboards before letting the battery in as a system battery, not a device battery.

  2. I think I found a subtle ARM device data error that was allowing some non audio devices in as audio, I didn’t reset certain variables in the loop there, not sure how I missed that, probably because nothing exposed that oversight I guess.

  3. I’d have to look more at the wifi thing, and the oddity of the ethernet calling itself wan0 or whatever it is. that part is unclear.


#50

Nice.

Thanks for working on this.
Let me know if/when/what you want more testing. :slight_smile:


#51

try pinxi 3.0.27-11, that may now catch the battery state, I checked some datasets and it appears that voltage_now and voltage_design_min only appear with system batteries, not device batteries.

Also to confirm that the capacity item actually works, try unplugging it for a while so the charge state is less than 100% to make sure that appears as intended. There’s not very much battery data available compared to normal laptops.


#52

This part could prove troublesome. I have very unstable wifi connection whenever it runs on battery and the device has no ethernet. But I will try it tomorrow.


#53

If you can’t unplug it, see if the other fixes are working. It’s possible that the wifi repeats might also be fixed if I’m lucky. Battery will just show 100%, but you can also just verify without running the debugger that pinxi -Bxxx shows the charge: 95%, if it does, it’s correct in terms of the data it’s using for that fallback data, the default is the real Wh remaining, but that data is not present in the /sys data for the battery. I also found a C issue on this same laptop for i3status tool, and they also could not get a charge in Wh using C, so I assume it’s simply not there.


#54

Latest dataset looks much much better. Battery now is working correctly, and it looks like the fallback ‘charge: 97%’ is working as expected, that’s good. The main bug for repeated devices was failure to reset the values each iteration when going through the device tree/platform items for the machine.

The wifi device repetition is also fixed, I only see one small problem, a duplicated soc item for audio, I’ll take a look at that and see if there is any way to filter out that data, or enhance the filters that prevent such things.

But much better than it was to start.


#55

Pulseaudio also see 2 cards, but tht’s probably because it has speakers and a headphone jack.


#56

I’ll have to look a bit more at the networking logic, it reversed the two, lc10000 is the wlan0 card, and lc30000 is the ethernet.

The logic there is pretty fuzzy however, and inxi doesn’t actually have proper support for mmc networking devices for ARM yet. That’s a tricky problem.


#57

The pinebook does not have an ethernet port though. :slight_smile:


#58

what’s odd is that the device data does show ethernet.

/sys/firmware/devicetree/base/soc/ethernet@1c30000

These ARM things are confusing and difficult to make sense of in a predictable way. I’m guessing that they use the same SOC as on the rock64 SBC, which I assume does have an ethernet port.


#59

It’s actually the pine64 it’s based on, and yes that does have ethernet. :slight_smile:
So I just assume the pinebook does not utilize the ethernet bus at all.


#60

That leaves the question as to why inxi reversed those items, and applied the IF to the wrong one. Certainly related to the MMC issue, which I’m aware of already in terms of ARM networking, but this is the first case where it’s shown up, but been treated wrong.