inxi / pinxi 2.9.00 beta testers!

[h2-1]

richb, I'm hoping for a truly seamless update to inxi 3.0.0, where users simply go, wow, this is way better, cool. Faster, stronger, more flexible. There will be no need for example to touch the existing configuration files, they will work natively, and continue to work.

You can unleash most features with -v 7 fyi.

[richb]

-v 7 fyi results in

Code: Select all

Error 21: Unsupported option: fyi

[kmathern]

kmathern, does the issue show when you run: pinxi -Fxxx

I don't see the 'Argument "" isn't numeric...' message running pinxi -Fxxx as a regular user, I do see it if I run it with sudo, or su -c 'pinxi -Fxxx '.

But I hardly ever run inxi using sudo or su -c, though I did earlier to run the -U update command to update pinxi.

[timkb4cq]

Don't know if this is a bug or not. One of my machines gets a memory manufacturer of N/A, on this one I get <BAD INDEX>
binxi gets N/A on both.

Code: Select all

$ sudo pinxi -v7
System:    Host: Woody2 Kernel: 4.2.0-0.bpo.1-amd64 x86_64 bits: 64 compiler: gcc v: 4.9.2 
           Desktop: Xfce 4.12.2 (Gtk 2.24.25) info: xfce4-panel dm: lightdm 1.10.3 
           Distro: MX-15_x64 Fusion 24 December 2015 
Machine:   Type: Desktop Mobo: ECS model: KBN-I v: 1.0 serial: N/A BIOS: American Megatrends v: 4.6.5 
           date: 01/03/2014 
Memory:    Array-1: capacity: 4 GB slots: 2 EC: None max module size: N/A 
           Device-1: DIMM 0 size: 2 GB speed: 533 MHz type: DDR3 detail: synchronous unbuffered (unregistered) 
           bus width: 64 bits total: 64 bits manufacturer: <BAD INDEX> part-nu: Team-Elite-1066 serial: N/A 
           Device-2: DIMM 1 size: 2 GB speed: 533 MHz type: DDR3 detail: synchronous unbuffered (unregistered) 
           bus width: 64 bits total: 64 bits manufacturer: <BAD INDEX> part-nu: Team-Elite-1066 serial: N/A 
CPU:       Topology: Dual Core model: AMD E1-2100 APU with Radeon HD Graphics type: MCP arch: Jaguar rev: 1 
           L2 cache: 1024 KB 
           flags: lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm bogomips: 3992 
           Speed: 1000 MHz min/max: 800/1000 MHz Core speeds: 1: 1000 2: 1000 
Graphics:  Card-1: Advanced Micro Devices [AMD/ATI] Kabini [Radeon HD 8210] driver: N/A bus ID: 00:01.0 
           chip ID: 1002:9834 
           Display Server: X.Org 1.16.4 driver: modesetting,ati,fbdev,radeon,vesa resolution: 1920x1080~60Hz 
           OpenGL: renderer: N/A version: N/A direct render: N/A 
Audio:     Card-1: Advanced Micro Devices [AMD/ATI] Kabini HDMI/DP Audio driver: snd_hda_intel v: kernel 
           bus ID: 00:01.1 chip ID: 1002:9840 
           Card-2: Advanced Micro Devices [AMD] FCH Azalia Controller driver: snd_hda_intel v: kernel 
           bus ID: 00:14.2 chip ID: 1022:780d 
           Sound Server: ALSA v: k4.2.0-0.bpo.1-amd64 
Network:   Card-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller driver: r8169 
           v: 2.3LK-NAPI port: e000 bus ID: 01:00 chip ID: 10ec:8168 
           IF: eth0 state: up speed: 100 Mbps duplex: full mac: c0:3f:d5:ff:91:71 
           IP v4: 192.168.1.111/24 type: dynamic eth0 scope: global broadcast: 192.168.1.255 
           IP v6: fe80::c23f:d5ff:feff:9171/64 scope: link 
           WAN IP: 65.35.72.33 
Drives:    HDD Total Size: 1.82 TB used: 545.08 GB (29.3%) 
           ID-1: /dev/sda model: WDC_WD2003FYPS size: 1.82 TB serial: WD-WCAVY5671943 rev: 5G11 temp: 38 C 
           Message: No Optical or Floppy data was found. 
Partition: ID-1: / size: 31.37 GB used: 6.38 GB (20.3%) fs: ext4 dev: /dev/sda1 label: MX-15-64 
           uuid: b0b70542-012d-4d34-b874-61ffe269d847 
           ID-2: /home size: 1007.81 GB used: 538.68 GB (53.5%) fs: ext4 dev: /dev/sda3 label: home 
           uuid: 10804f8c-662a-4baf-8f96-91d95d99bb77 
           ID-3: /sys/fs/cgroup size: 12 KB used: 0 KB (0.0%) fs: tmpfs dev: /dev/ label: N/A uuid: N/A 
           ID-4: swap-1 size: 8.00 GB used: 32.4 MB (0.4%) fs: swap dev: /dev/sda2 label: MXswap 
           uuid: e4c1eb5c-5fcc-4cb5-864a-1db5906fee9c 
RAID:      Message: No RAID data was found. 
Unmounted: Message: No unmounted partitions found. 
USB Info:  Hub: 1:1 usb: 2.00 type: Full speed (or root) hub chip ID: 1d6b:0002 
           Hub: 2:1 usb: 2.00 type: Full speed (or root) hub chip ID: 1d6b:0002 
           Device-1: Brother Industries Ltd MFC-7220 Printer bus ID: 2:2 usb: 1.00 type: Bidirectional 
           chip ID: 04f9:0185 
           Hub: 3:1 usb: 3.00 type: Full speed (or root) hub chip ID: 1d6b:0003 
           Hub: 4:1 usb: 2.00 type: Full speed (or root) hub chip ID: 1d6b:0002 
           Hub: 5:1 usb: 1.10 type: Full speed (or root) hub chip ID: 1d6b:0001 
           Device-2: Logitech Unifying Receiver bus ID: 5:2 usb: 2.00 type: Keyboard chip ID: 046d:c52b 
           Hub: 6:1 usb: 1.10 type: Full speed (or root) hub chip ID: 1d6b:0001 
Sensors:   System Temperatures: cpu: 50.1 C mobo: N/A 
           Fan Speeds (in RPM): N/A 
Info:      Processes: 339 Uptime: 22 days Memory: 3.33 GB used: 583.4 MB (17.1%) Init: SysVinit v: 2.88 
           runlevel: 5 default: 5 Compilers: gcc: 4.9.2 alt: 4.9 Shell: sudo ersion running in: bash 
           pinxi: 2.9.00-342-p

[h2-1]

kmathern, great, something I also have not tested much. It's possible that -0343-p fixes the issue.

If it does not, you can edit the following two lines:
12,639: #print "shell pre: $shell\n"; # uncomment
12,650: #print "shell post: $shell\n"; # uncomment

then just run pinxi as root and it should show what was happening. I believe though I'm not certain that an action I expected to return a program name was returning the path, which made some tests fail, which sent the request to the wrong place, and that request had bugs in it as well, lol.

I can't log this error unfortunately because i believe it happens before logging kicks in.

But so far a nice haul of bugs, better than I hoped.

[h2-1]

timkb4cq, yes, it's a bug, thanks. That's a filter problem, missing that item.

[timkb4cq]

This discrepancy is an error. It might have to do with AMD specifying that the A6-4400 APU has 2 cores in one physical module.

Code: Select all

$ pinxi
CPU: Single Core AMD A6-4400M APU with Radeon HD Graphics (-MT-)
speed/min/max: 937/1400/2700 MHz Kernel: 4.13.0-0.bpo.1-amd64 x86_64 Up: 7 min 
Mem: 592.8/7435.7 MB (8.0%) HDD: 232.89 GB (5.0% used) Procs: 154 Shell: bash 4.4.12
pinxi: 2.9.00-343-p 

Code: Select all

$ inxi
CPU~Dual core AMD A6-4400M APU with Radeon HD Graphics (-MCP-) speed/max~2695/2700 MHz Kernel~4.13.0-0.bpo.1-amd64 x86_64 Up~7 min Mem~584.6/7435.7MB HDD~250.1GB(6.6% used) Procs~156 Client~Shell inxi~2.3.53

Note however that extended info shows the speed of each core of the "Single core" APU

Code: Select all

CPU:       Topology: Single Core model: AMD A6-4400M APU with Radeon HD Graphics type: MT 
           arch: Piledriver rev: 1 L2 cache: 1024 KB 
           flags: lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm bogomips: 10780 
           Speed: 1112 MHz min/max: 1400/2700 MHz Core speeds: 1: 1112 2: 982

[h2-1]

kmathern, your issue should be resolved in -0345-p

The problem was that I literally never use sudo, and didn't realize that when you start pinxi with sudo, the parent is then sudo, not shell, and that broke all that stuff.

that break exposed a bug in the parameters I used in the fallback case, and also exposed that sudo was not handled at all.

inxi never actually handled this, and pinxi now has this handled, it now checks to see if parent is shell, and if so, it gets the next level up, which is the parent of sudo, the shell. Then it gets the parent of that, for example, xfce-terminal

I may have now broken konversation slightly re version numbers with this fix, not sure yet.

I have to check this fix more to make sure it works in irc stuff.

timkb4cq, filters should be fixed for ram data. I was trying to avoid excessive cleaner actions internally on dmidecode, but I clearly went too far.

I've restored the filters basically verbatim from inxi for some items now, though not all since they aren't needed in all cases, I think.

[h2-1]

timkb4cq, I'd have to see /proc/cpuinfo
or just generate the debugger data: pinxi --debug 21
and I should be able to get that fixed, the logic for cpus is very complicated now in pinxi because it's much more clever re what it can detect. So this is probably just a small logic glitch.

But so far outstanding bugs!!

kmathern's was the more core technically speaking, because it was a total failure on 3 levels.

[h2-1]

timkb4cq, just as an aside, the issue is probably that amd cpu is not reporting itself correctly, however, I'll learn what's up as soon as I see the data. The core speeds come from a different place by default, and have no real connection to the raw cpu data, unless pinxi had to fall back to the cpuinfo speeds.

If I were to guess, I'd guess that amd is reporting physical id 0, then core 0, then repeating physical id 0, and core 0, in the data, that would account for that error, inxi had a very 'dumb' processor counter, which is why it worked in this case, pinxi has a far more complicated cpu handler, for example, it can detect when the cpu has 2 dies in one body, ryzen does that, intel is starting to do that, some arm chips also do that now, which is why I had to add that support in.

this is almost certainly a case of slightly off cpuinfo structure that has to be handled.