Beta testers for new Perl inxi requested

If none of the more specific forums is the right place to ask

Beta testers for new Perl inxi requested

Postby h2 » 2018-03-17 21:57

Hi Debian users, I'm the developer of inxi, and would like to get as many issues and bugs resolved before I release the brand new inxi, rewritten in Perl, finally, a real programming language! We've already been beta testing it for 2 weeks, and have found most bugs, but some still crop up, particularly on fringe hardware/system setups.

I'm working on the new 3.0.0 release of inxi. The development branch is called pinxi, so you can run pinxi and inxi together to compare etc. Once all the bugs and issues that are going to be found are found, the pinxi branch will move to inxi master and become inxi 3.0.0. Pinxi is a full rewrite, in Perl5, of inxi. Since this new Perl based inxi will enter Debian sid probably sometime next week, assuming no further issues or bugs, it would be nice to have it released with as few bugs as possible.

Git branch: https://github.com/smxi/inxi/tree/inxi-perl

To test, install/download, as root/sudo:

Code: Select all
wget -O /usr/local/bin/pinxi https://github.com/smxi/inxi/raw/inxi-perl/pinxi
chmod +x /usr/local/bin/pinxi


Once installed, updating works the same as with inxi:

Code: Select all
pinxi -U


I want to release version 3.0.0 of inxi with no real bugs, at least as few as possible, and as many improvements over inxi 2.3.56 as possible.

I"m probably now in my final days of beta testing (unless new bugs show up), but I'd like if other distros would give it a spin and see if there are any errors, bugs, issues, glitches, etc.

Once there are no active issues or bugs, pinxi will move to inxi 2.9.01, as the first official Perl inxi release. After a few weeks, this will become inxi 3.0.0, again assuming, all bugs fixed etc.

Of particular interest to me is ARM testing, zfs or mdraid software RAID, and weird old systems, or weird new systems, that might expose unfound bugs.

All short form args for normal options are the same, only now there are also long form args for everything as well, which means any tools that use inxi should see few changes, though you want to check that to make sure. See --help for new options.

There's an enhanced debugger as well, called with --debug 21 (leaves tar.gz data file on your system) or --debug 22 (removes all debugging data after automatic upload), which is helping a lot with debugging issues.

The most useful testing command is: pinxi -zv8

-zv8 is basically everything it can do, so any bugs will show there if they exist, plus the -z output filter.

Note that the new inxi features a few core new things, like exporting it's data to json/xml, which might be of interest to other developers. That's a feature that was long ago requested, but which was impossible to achieve with the previous mutant language combination that inxi had. Also on the burner is language pack support, for different language keys and messages etc, but that's a feature that will probably added only if there is active interest and help by non english speakers.

Thanks for any bugs, glitches, or issues you can find.
smxi/sgfxi site (manuals, how-to's, faqs) :: script forums :: Check out inxi sys info script!
h2
 
Posts: 120
Joined: 2006-10-29 20:00
Location: USA

Re: Beta testers for new Perl inxi requested

Postby dcihon » 2018-03-17 22:51

No Bugs. Looks good on my system.
I'll try it on some other ones I have.
Code: Select all
cihonm@cihonm:~$ sudo pinxi -zv8
System:    Host: cihonm Kernel: 4.14.0-3-amd64 x86_64 bits: 64 compiler: gcc v: 7.3.0 Console: tty 0
           dm: lightdm 1.18.3 Distro: Debian GNU/Linux buster/sid
Machine:   Type: Desktop System: Dell product: Inspiron 3650 v: X00 serial: <filter> Chassis: type: 3
           serial: <filter>
           Mobo: Dell model: 0C2XKD v: A01 serial: <filter> UEFI [Legacy]: Dell v: 3.4.1 date: 06/20/2017
Memory:    Array-1: capacity: 16 GB slots: 2 EC: None max module size: N/A
           Device-1: DIMM1 size: 8 GB speed: 1600 MT/s type: DDR3 detail: synchronous bus width: 64 bits
           total: 64 bits manufacturer: Micron part-nu: 16KTF1G64AZ-1G6P1 serial: 20422310
           Device-2: DIMM2 size: 8 GB speed: 1600 MT/s type: DDR3 detail: synchronous bus width: 64 bits
           total: 64 bits manufacturer: Micron part-nu: 16KTF1G64AZ-1G6P1 serial: 20422396
PCI Slots: Slot: 0 type: x16 PCI Express PCIE status: In Use length: Long
           Slot: 1 type: x1 PCI Express J6B1 status: In Use length: Short
CPU:       Topology: Quad Core model: Intel Core i7-6700 type: MT MCP arch: Skylake-S rev: 3 L2 cache: 8192 KB
           flags: lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 54528
           Speed: 900 MHz min/max: 800/4000 MHz Core speeds: 1: 863 2: 846 3: 849 4: 853 5: 871 6: 853 7: 851
           8: 854
Graphics:  Card-1: Advanced Micro Devices [AMD/ATI] Tobago PRO [Radeon R7 360 / R9 360 OEM] driver: radeon
           v: kernel bus ID: 01:00.0 chip ID: 1002:665f
           Display Server: X.Org 1.19.6 driver: radeon,ati unloaded: fbdev,vesa,modesetting
           resolution: 1920x1080~60Hz, 1920x1080~60Hz
           OpenGL: renderer: AMD BONAIRE (DRM 2.50.0 / 4.14.0-3-amd64 LLVM 5.0.1) version: 4.5 Mesa 17.3.6
           compat-v: 3.0 direct render: Yes
Audio:     Card-1: Intel Sunrise Point-H HD Audio driver: snd_hda_intel v: kernel bus ID: 00:1f.3
           chip ID: 8086:a170
           Card-2: Advanced Micro Devices [AMD/ATI] Tobago HDMI Audio [Radeon R7 360 / R9 360 OEM]
           driver: snd_hda_intel v: kernel bus ID: 01:00.1 chip ID: 1002:aac0
           Card-3: Logitech Webcam C270 driver: USB Audio bus ID: 1:5 chip ID: 046d:0825
           Sound Server: ALSA v: k4.14.0-3-amd64
Network:   Card-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller driver: r8169
           v: 2.3LK-NAPI port: d000 bus ID: 02:00 chip ID: 10ec:8168
           IF: enp2s0 state: down mac: <filter>
           Card-2: Qualcomm Atheros QCA9565 / AR9565 Wireless Network Adapter driver: ath9k v: kernel
           bus ID: 03:00 chip ID: 168c:0036
           IF: wlp3s0 state: up mac: <filter>
           IP v4: <filter> type: dynamic noprefixroute wlp3s0 scope: global broadcast: <filter>
           Card-3: Atheros driver: USB Network bus ID: 1:17 chip ID: 0cf3:e005
           WAN IP: <filter>
Drives:    HDD Total Size: 1.88 TB used: 270.48 GB (14.1%)
           ID-1: /dev/sda model: ST2000DM001-1ER1 size: 1.82 TB serial: <filter> rev: CC27 temp: 36 C
           ID-2: /dev/sdb type: USB model: Flash_Disk size: 58.59 GB serial: <filter> rev: 8.07
           Optical-1: /dev/sr0 vendor: HL-DT-ST model: DVD+-RW GU90N rev: A1C1 dev-links: cdrom,cdrw,dvd,dvdrw
           Features: speed: 24 multisession: yes audio: yes dvd: yes rw: cd-r,cd-rw,dvd-r,dvd-ram
           state: running
RAID:      Message: No RAID data was found.
Partition: ID-1: / size: 39.25 GB used: 20.15 GB (51.3%) fs: ext4 dev: /dev/sda6 label: N/A
           uuid: d8863e48-11dd-46d2-a293-08f3ab55d6b9
           ID-2: /snap/acestreamplayer/7 size: 193.1 MB used: 193.1 MB (100.0%) fs: squashfs dev: /dev/loop2
           label: N/A uuid: N/A
           ID-3: /snap/core/4110 size: 81.6 MB used: 81.6 MB (100.0%) fs: squashfs dev: /dev/loop3 label: N/A
           uuid: N/A
           ID-4: /snap/core/4017 size: 81.8 MB used: 81.8 MB (100.0%) fs: squashfs dev: /dev/loop0 label: N/A
           uuid: N/A
           ID-5: /home size: 867.99 GB used: 208.08 GB (24.0%) fs: ext4 dev: /dev/sda11 label: N/A
           uuid: 1ee2b8d8-ab62-4a09-870a-0c37e5308d5b
           ID-6: /snap/core/4206 size: 81.8 MB used: 81.8 MB (100.0%) fs: squashfs dev: /dev/loop4 label: N/A
           uuid: N/A
           ID-7: /media/cihonm/30D6-616B size: 58.58 GB used: 41.82 GB (71.4%) fs: vfat dev: /dev/sdb
           label: N/A uuid: 30D6-616B
           ID-8: swap-1 size: 16.00 GB used: 0 KB (0.0%) fs: swap dev: /dev/sda5 label: N/A
           uuid: 42e5932b-d210-427f-aef0-28aac6826539
Unmounted: ID-1: /dev/sda1 size: 101.9 MB fs: N/A label: DellUtility uuid: 5450-4444
           ID-2: /dev/sda10 size: 78.91 GB fs: ext4 label: N/A uuid: 26473ad7-3383-4b94-a1c2-104144704019
           ID-3: /dev/sda2 size: 13.73 GB fs: NTFS label: RECOVERY uuid: 7682188882184F4D
           ID-4: /dev/sda3 size: 465.76 GB fs: NTFS label: OS uuid: 58AE1AC7AE1A9E16
           ID-5: /dev/sda7 size: 60.00 GB fs: ext4 label: Solydk uuid: 601546b5-883b-46ac-9331-e094f0349bb8
           ID-6: /dev/sda8 size: 284.94 GB fs: ext4 label: SolydK EE 9 64-b
           uuid: c31ee348-fb82-4059-a00b-1b94c5c0c5e7
           ID-7: /dev/sda9 size: 20.72 GB fs: ext4 label: N/A uuid: d52c07ce-d022-41c4-9e4c-62b358469408
USB:       Hub: 1:1 usb: 2.00 type: Full speed (or root) hub chip ID: 1d6b:0002
           Device-1: Logitech Unifying Receiver bus ID: 1:2 usb: 2.00 type: Keyboard chip ID: 046d:c52b
           Device-2: Realtek RTS5129 Card Reader Controller bus ID: 1:4 usb: 2.00 type: Vendor Specific Class
           chip ID: 0bda:0129
           Device-3: Logitech Webcam C270 bus ID: 1:5 usb: 2.00 type: Video chip ID: 046d:0825
           Hub: 1:6 usb: 2.00 type: D-Link DUB-H7 7-port USB 2.0 hub chip ID: 2001:f103
           Device-4: Alcor Micro Flash Drive bus ID: 1:15 usb: 2.00 type: Mass Storage chip ID: 058f:6387
           Device-5: Atheros bus ID: 1:17 usb: 1.10 type: Bluetooth chip ID: 0cf3:e005
           Hub: 2:1 usb: 3.00 type: Full speed (or root) hub chip ID: 1d6b:0003
Sensors:   System Temperatures: cpu: 51.0 C mobo: 29.8 C gpu: radeon temp: 51 C
           Fan Speeds (in RPM): cpu: 827 fan-2: 853
Repos:     Active apt sources in: /etc/apt/sources.list
           1: deb http://httpredir.debian.org/debian/ testing main non-free contrib
           2: deb http://security.debian.org/debian-security/ testing/updates main contrib non-free
           3: deb http://httpredir.debian.org/debian/ buster-updates main contrib
           Active apt sources in: /etc/apt/sources.list.d/compiz-reloaded.list
           1: deb http://download.opensuse.org/repositories/home:/stevenpusser:/compiz-reloaded/Debian_9.0/ /
           No apt repos found in: /etc/apt/sources.list.d/liquorix.list
           No apt repos found in: /etc/apt/sources.list.d/mdm.list
           Active apt sources in: /etc/apt/sources.list.d/qbittorrent.list
           1: deb https://download.opensuse.org/repositories/home:/stevenpusser:/qbittorrent/Debian_9.0/ /
Processes: CPU  % used - Command - pid - Memory: MB / % used - top: 5
           1: cpu: 4.4% command: virtualbox pid: 25325 mem: 1821.4MB (11.3%)
           2: cpu: 3.8% command: xorg pid: 1411 mem: 143.6MB (0.8%)
           3: cpu: 2.6% command: palemoon pid: 2853 mem: 1108.5MB (6.9%)
           4: cpu: 1.0% command: compiz pid: 2811 mem: 85.9MB (0.5%)
           5: cpu: 0.4% command: vboxsvc pid: 14339 mem: 27.7MB (0.1%)
           Memory MB/% used - Command - pid - CPU: % used - top: 5
           1: mem: 1821.4 MB (4.4%) command: virtualbox pid: 25325 cpu: 11.3%
           2: mem: 1108.5 MB (2.6%) command: palemoon pid: 2853 cpu: 6.9%
           3: mem: 143.6 MB (3.8%) command: xorg pid: 1411 cpu: 0.8%
           4: mem: 120.7 MB (0.1%) command: virtualbox pid: 14308 cpu: 0.7%
           5: mem: 119.4 MB (0.1%) command: caja pid: 2787 cpu: 0.7%
Info:      Processes: 235 Uptime: 4 days Memory: 15.61 GB used: 3.99 GB (25.5%) Init: systemd v: 238
           runlevel: 5 default: 2 Compilers: gcc: 7.3.0 alt: 6/7 Shell: mksh running in: mate-terminal
           pinxi: 2.9.00-440-p
dcihon
 
Posts: 233
Joined: 2012-09-23 16:18

Re: Beta testers for new Perl inxi requested

Postby sunrat » 2018-03-17 23:12

This is a 10 year old desktop running siduction. Only issue I can see is wireless driver is reported as USB Network where it is actually ath9k_htc .

Code: Select all
# pinxi -zv8
System:    Host: siduction-brain2 Kernel: 4.15.7-towo.1-siduction-amd64 x86_64 bits: 64 compiler: gcc v: 7.3.0
           Desktop: KDE Plasma 5.12.2 dm: sddm Distro: siduction 17.1.0 Patience - kde - (201703051755)
Machine:   Type: Desktop Mobo: Gigabyte model: EP45-UD3R v: x.x serial: N/A BIOS: Award v: F3 date: 09/18/2008
Memory:    Array-1: capacity: 8 GB note: est slots: 4 EC: None max module size: 2 GB note: est
           Device-1: A0 size: 2 GB info: single-bank speed: 800 MT/s type: Unknown detail: none
           bus width: 64 bits total: 64 bits manufacturer: N/A part-nu: N/A serial: N/A
           Device-2: A1 size: No Module Installed
           Device-3: A2 size: 2 GB info: single-bank speed: 800 MT/s type: Unknown detail: none
           bus width: 64 bits total: 64 bits manufacturer: N/A part-nu: N/A serial: N/A
           Device-4: A3 size: No Module Installed
PCI Slots: Slot: 0 type: 32-bit PCI PCI status: Available length: Long
           Slot: 1 type: 32-bit PCI PCI status: Available length: Long
CPU:       Topology: Dual Core model: Intel Core2 Duo E8500 type: MCP arch: Penryn rev: 10 L2 cache: 6144 KB
           flags: lm nx pae sse sse2 sse3 sse4_1 ssse3 vmx bogomips: 12665
           Speed: 2000 MHz min/max: 2000/3166 MHz Core speeds: 1: 2000 2: 2000
Graphics:  Card-1: NVIDIA GF114 [GeForce GTX 560 Ti] driver: nouveau v: kernel bus ID: 01:00.0
           chip ID: 10de:1200
           Display Server: x11 (X.Org 1.19.6) driver: nouveau unloaded: nv,modesetting,vesa,fbdev
           resolution: 1920x1080~60Hz
           OpenGL: renderer: NVCE version: 4.3 Mesa 17.3.6 compat-v: 3.0 direct render: Yes
Audio:     Card-1: Intel 82801JI (ICH10 Family) HD Audio Controller driver: snd_hda_intel v: kernel
           bus ID: 00:1b.0 chip ID: 8086:3a3e
           Card-2: NVIDIA GF114 HDMI Audio Controller driver: snd_hda_intel v: kernel bus ID: 01:00.1
           chip ID: 10de:0e0c
           Sound Server: ALSA v: k4.15.7-towo.1-siduction-amd64
Network:   Message: No PCI card data found.
           Card-1: TP-Link TL-WN821N v3 / TL-WN822N v2 802.11n [Atheros AR7010+AR9287] driver: USB Network
           bus ID: 7:2 chip ID: 0cf3:7015
           IF-ID-1: wlan0 state: up speed: N/A duplex: N/A mac: <filter>
           IP v4: <filter> type: dynamic noprefixroute wlan0 scope: global broadcast: <filter>
           IP v6: <filter> virtual: noprefixroute scope: link
           WAN IP: <filter>
Drives:    HDD Total Size: 1.92 TB used: 932.24 GB (47.3%)
           ID-1: /dev/sda model: OCZ-VERTEX2_3.5 size: 107.13 GB serial: <filter> rev: 1.29 temp: 30 C
           ID-2: /dev/sdb model: WDC_WD1001FALS-0 size: 931.51 GB serial: <filter> rev: 0K05 temp: 47 C
           ID-3: /dev/sdc model: WDC_WD1001FALS-0 size: 931.51 GB serial: <filter> rev: 0K05 temp: 45 C
           Optical-1: /dev/sr0 vendor: HL-DT-ST model: DVDRAM GH20NS10 rev: EL00
           dev-links: cdrom,cdrw,dvd,dvdrw
           Features: speed: 48 multisession: yes audio: yes dvd: yes rw: cd-r,cd-rw,dvd-r,dvd-ram
           state: running
RAID:      Message: No RAID data was found.
Partition: ID-1: / size: 20.47 GB used: 12.47 GB (60.9%) fs: ext4 dev: /dev/sda2 label: N/A
           uuid: 45a5cc41-596c-4783-b066-8609f04c28a6
           ID-2: /mnt/stash size: 406.03 GB used: 288.40 GB (71.0%) fs: ext4 dev: /dev/sdb3 label: stash
           uuid: 11c68f17-0fc7-4413-92e5-99a5021197bf
           ID-3: /mnt/music size: 820.26 GB used: 631.38 GB (77.0%) fs: ext3 dev: /dev/sdc1 label: music
           uuid: 7605433f-5c96-4d6c-bb11-a1818eda16d4
           ID-4: swap-1 size: 2.29 GB used: 0 KB (0.0%) fs: swap dev: /dev/sda3 label: N/A
           uuid: ee8c3db0-ccee-40ef-93b1-1a244e7ecb19
Unmounted: ID-1: /dev/sda1 size: 40.30 GB fs: NTFS label: WIN7 uuid: 677EE28C54F5FC0F
           ID-2: /dev/sda5 size: 17.62 GB fs: N/A label: rootMX17 uuid: ce68b629-ebef-4a65-9641-f2a47f44c725
           ID-3: /dev/sda6 size: 25.99 GB fs: N/A label: N/A uuid: 73db6bc2-7ceb-4a53-9103-e7eb6c3f8f88
           ID-4: /dev/sdb1 size: 119.23 GB fs: NTFS label: win-stash uuid: 4E25F0444084DA77
           ID-5: /dev/sdb2 size: 399.64 GB fs: NTFS label: win-progs uuid: 69B1A5EF6A01E52F
           ID-6: /dev/sdc3 size: 98.05 GB fs: ext3 label: N/A uuid: e6e1d8eb-1cc9-46d8-998c-d88c83fe3bc9
USB:       Hub: 1:1 usb: 1.10 type: Full speed (or root) hub chip ID: 1d6b:0001
           Hub: 2:1 usb: 1.10 type: Full speed (or root) hub chip ID: 1d6b:0001
           Hub: 3:1 usb: 1.10 type: Full speed (or root) hub chip ID: 1d6b:0001
           Hub: 4:1 usb: 1.10 type: Full speed (or root) hub chip ID: 1d6b:0001
           Hub: 5:1 usb: 1.10 type: Full speed (or root) hub chip ID: 1d6b:0001
           Hub: 6:1 usb: 1.10 type: Full speed (or root) hub chip ID: 1d6b:0001
           Hub: 7:1 usb: 2.00 type: Full speed (or root) hub chip ID: 1d6b:0002
           Device-1: TP-Link TL-WN821N v3 / TL-WN822N v2 802.11n [Atheros AR7010+AR9287] bus ID: 7:2 usb: 2.00
           type: Vendor Specific Class chip ID: 0cf3:7015
           Hub: 8:1 usb: 2.00 type: Full speed (or root) hub chip ID: 1d6b:0002
Sensors:   System Temperatures: cpu: 37.0 C mobo: N/A gpu: nouveau temp: 37 C
           Fan Speeds (in RPM): cpu: 1320 gpu: nouveau fan: 1320
Repos:     No apt repos found in: /etc/apt/sources.list
           Active apt sources in: /etc/apt/sources.list.d/debian.list
           1: deb http://ftp.monash.edu.au/pub/linux/debian/ unstable main contrib non-free
           Active apt sources in: /etc/apt/sources.list.d/extra.list
           1: deb https://packages.siduction.org/extra unstable main
           Active apt sources in: /etc/apt/sources.list.d/fixes.list
           1: deb https://packages.siduction.org/fixes unstable main contrib non-free
           Active apt sources in: /etc/apt/sources.list.d/google-chrome.list
           1: deb [arch=amd64] http://dl.google.com/linux/chrome/deb/ stable main
           Active apt sources in: /etc/apt/sources.list.d/qupzilla.list
           1: deb http://download.opensuse.org/repositories/home:/stevenpusser:/qupzilla/Debian_9.0/ /
Processes: CPU  % used - Command - pid - Memory: MB / % used - top: 5
           1: cpu: 2.4% command: firefox pid: 4004 mem: 507.1MB (12.8%)
           2: cpu: 2.1% command: thunderbird pid: 2747 mem: 226.7MB (5.7%)
           3: cpu: 1.7% command: deadbeef pid: 13741 mem: 50.0MB (1.2%)
           4: cpu: 1.1% command: firefox pid: 4593 mem: 187.9MB (4.7%)
           5: cpu: 0.8% command: pulseaudio pid: 1930 mem: 12.8MB (0.3%)
           Memory MB/% used - Command - pid - CPU: % used - top: 5
           1: mem: 507.1 MB (2.4%) command: firefox pid: 4004 cpu: 12.8%
           2: mem: 231.8 MB (0.4%) command: firefox pid: 4132 cpu: 5.8%
           3: mem: 228.9 MB (0.2%) command: plasmashell pid: 1896 cpu: 5.7%
           4: mem: 226.7 MB (2.1%) command: thunderbird pid: 2747 cpu: 5.7%
           5: mem: 224.3 MB (0.1%) command: firefox pid: 4554 cpu: 5.6%
Info:      Processes: 181 Uptime: 8:13 Memory: 3.86 GB used: 1.80 GB (46.8%) Init: systemd v: 237 runlevel: 5
           Compilers: gcc: 7.3.0 alt: 6/7 Shell: bash 4.4.18 running in: konsole pinxi: 2.9.00-440-p


There is a small speed advantage for pinxi over inxi:
Code: Select all
# time pinxi -F
...
real    0m1.257s
user    0m0.485s
sys     0m0.120s

Code: Select all
# time inxi -F
...
real    0m1.415s
user    0m0.597s
sys     0m0.350s
“ computer users can be divided into 2 categories:
Those who have lost data
...and those who have not lost data YET ”
Remember to BACKUP!
User avatar
sunrat
 
Posts: 2425
Joined: 2006-08-29 09:12
Location: Melbourne, Australia

Re: Beta testers for new Perl inxi requested

Postby h2 » 2018-03-17 23:15

looks good except for: mksh

That shell is not handled in pinxi yet, is there a command that gives version output, like:

Code: Select all
mksh --version 2>/dev/null
# or:
mksh --version


I put in the 2>/dev/null in case it sends version information to stderr, not stdout. If the first is empty, and the second, not, it's doing that.

If that has output, post it here and I'll add that information into the version handler. That would be a good example of a fringe thing that isn't handled, heh.

and I'm curious about the /snap stuff in partitions, are those actual partitions, given they are squashfs? That also looks like something that isn't handled.

Thanks for checking.
smxi/sgfxi site (manuals, how-to's, faqs) :: script forums :: Check out inxi sys info script!
h2
 
Posts: 120
Joined: 2006-10-29 20:00
Location: USA

Re: Beta testers for new Perl inxi requested

Postby h2 » 2018-03-17 23:30

sunrat, the wireless usb network driver issue might be a bug, not sure. Normally I can't get usb driver data out of these types of devices, but that doesn't mean it's not possible, which is why it defaults to USB <driver>

If you want to do the upload of the --debug 22 (cleans up all debugger data, 21 leaves gz file if you want to look at it, 20 does not upload, if you want to look first) I can probably tell you if the information is detectable or not, since I would have to look inside of /sys data pretty deeply to determine if it's there or not.

I'd certainly like to get rid of the generic USB <driver> item for the driver: for USB devices, although actually I notice a weakness there as well, because if I could find the drive, that would get rid of the only indication that it's a USB device, so I think I should add type: USB in any case to audio/network usb devices, that's an oversight on my part.
smxi/sgfxi site (manuals, how-to's, faqs) :: script forums :: Check out inxi sys info script!
h2
 
Posts: 120
Joined: 2006-10-29 20:00
Location: USA

Re: Beta testers for new Perl inxi requested

Postby sunrat » 2018-03-17 23:49

Sent you the debug file. Lotsa luck! The only simple way I know of displaying the driver is lshw -c network but I'd guess you don't want to call and parse that from pinxi.
“ computer users can be divided into 2 categories:
Those who have lost data
...and those who have not lost data YET ”
Remember to BACKUP!
User avatar
sunrat
 
Posts: 2425
Joined: 2006-08-29 09:12
Location: Melbourne, Australia

Re: Beta testers for new Perl inxi requested

Postby Head_on_a_Stick » 2018-03-17 23:53

h2 wrote:looks good except for: mksh

That shell is not handled in pinxi yet, is there a command that gives version output, like:

Code: Select all
mksh --version 2>/dev/null
# or:
mksh --version

Code: Select all
empty@Xanadu:~ $ echo $KSH_VERSION
@(#)MIRBSD KSH R56 2018/03/09
empty@Xanadu:~ $
ESTRAGON: We always find something, eh, Didi, to give us the impression we exist?
VLADIMIR (impatiently): Yes, yes, we're magicians.
User avatar
Head_on_a_Stick
 
Posts: 7893
Joined: 2014-06-01 17:46
Location: /dev/chair

Re: Beta testers for new Perl inxi requested

Postby h2 » 2018-03-18 00:18

Head_on_a_Stick, that's good to know. I'm not sure that will be available in Perl, I've noticed not all environmental variables are present when pinxi runs, most are, like $HOME, but not all. I can add tests for that one though.

sunrat, the information is in /sys, I had to really dig around in a bunch of differently parsed /sys debuggers from another user with network wifi.

I still can't figure out how to get the path, because /sys is filled with a combination of nice clean shortcuts to things, and the full actual non symbolic link paths, which are really difficult to guess at dynamically.

So you're absolutely right, there can be a driver connected to the usb device, but sadly, there is no file to read directly that is nice enough to tell me that, well, there is one, but I'm still not able to figure out it's predictable path, but the other one is a symbolic link to a usb driver file, which itself then is the answer, that is, you have to get the link TARGET file, not the contents of a file, to get that data, the target file name itself is the driver name, which is weird, I can see why I never realized that situation existed, almost always there's a file to read. So it is in there, and there is a uevent file, which are sort of summary files for certain sections, that contains that data, but the problem is, it's 1 level in further than my tools can read without generating massive file sizes, so I can't find the direct path to it. I'll keep poking around though. Certainly a valid issue, something I was not aware of.
smxi/sgfxi site (manuals, how-to's, faqs) :: script forums :: Check out inxi sys info script!
h2
 
Posts: 120
Joined: 2006-10-29 20:00
Location: USA

Re: Beta testers for new Perl inxi requested

Postby sunrat » 2018-03-18 00:44

Not sure if this is helpful but it shows a folder - /sys/class/net/wlan0/device/driver/module/drivers/usb:ath9k_htc/
Obviously it would need to know the interface name to find that.
“ computer users can be divided into 2 categories:
Those who have lost data
...and those who have not lost data YET ”
Remember to BACKUP!
User avatar
sunrat
 
Posts: 2425
Joined: 2006-08-29 09:12
Location: Melbourne, Australia

Re: Beta testers for new Perl inxi requested

Postby h2 » 2018-03-18 00:54

Code: Select all
/sys/class/net/wlan0/device/driver/module/drivers/usb:ath9k_htc/


That would a nice one, except that pinxi doesn't learn about the IF name until after it makes this line, but it's the right idea.

the data is in there, I've seen it, and can be found using just the usb bus id numbers. There's a couple of ways of finding that, but it's all tricky. But now that I know that the data exists, I'll see if I can find anything in your dataset, which looks pretty similar to the one I got from another guy re that specific driver I believe.

pinxi 2.9.00-0431-p

corrects the following glitches seen so far:

1. the showing of /slap packages in partitions. this is now corrected
2. possible version ID (if the value of KSH_VERSION is visible to Perl), also, I improved the handling for ksh, now it will just kick back null if the KSH_VERSION test doesn't work. Note that I could only find the mksh version given here, and a sample from KSH I found online, in both the version number occurred in the 3rd space separated column, so that's what I'm using, the 3rd. This may not always work, or the variable may simply not be visible inside of Perl (that's my strong suspicion), but a quick test will see. If nothing, there's nothing practical I can do with the ksh variants, I looked a bit at some articles on how to detect them, and they are very convoluted. I'd rather see users file issue reports with the ksh variants asking for a simple solution to a simple problem, code in a --version option, but aside from that fix, there's not much I can do about the ksh variants if this solution doesn't work.
3. Updated audio and network to add type: USB to usb device lines, like disks has already, so that will match well. That was just an oversight on my part.

I'll look into the usb version.
smxi/sgfxi site (manuals, how-to's, faqs) :: script forums :: Check out inxi sys info script!
h2
 
Posts: 120
Joined: 2006-10-29 20:00
Location: USA

Re: Beta testers for new Perl inxi requested

Postby Head_on_a_Stick » 2018-03-18 01:02

h2 wrote:the value of KSH_VERSION

Be aware that there are two implementations of the KornShell programming language available in Debian:
Code: Select all
$ echo $KSH_VERSION
Version ABIJ 93v- 2014-12-24
$

^ That's the new Meson Build version of ksh93 but the one in the repositories uses a similar nomenclature:

https://packages.debian.org/stretch/ksh

ksh93 is quite popular with Unix sysadmins so it may be worth covering (or maybe not, it's better for scripting than for interactive use).

I will test your script on my boxen tomorrow, thanks for your efforts!
ESTRAGON: We always find something, eh, Didi, to give us the impression we exist?
VLADIMIR (impatiently): Yes, yes, we're magicians.
User avatar
Head_on_a_Stick
 
Posts: 7893
Joined: 2014-06-01 17:46
Location: /dev/chair

Re: Beta testers for new Perl inxi requested

Postby h2 » 2018-03-18 01:25

Code: Select all
Version ABIJ 93v- 2014-12-24
Version JM 93t+ 2010--03-05
@(#)MIRBSD KSH R56 2018/03/09


There's a couple of tests I can do once it's confirmed that Perl is even seeing this variable. If it is seeing it, you would be seeing the 3rd white space separated term for any ksh type shell in pinxi -Ix output. Or pinxi [with no args], currently shows the version if present, that's actually kind of a small bug but I'm leaving it in place for the time being.

For example, on this string, what is the actual version number?
I'm currently picking the thing that looks most like a version number, 93v-

The date is obvious, I could include that very easily since it appears to always be at the end of the string, so that's trivial to add on.

The tests are not very expensive since I've already determined that it's lksh/mksh/pdksh/ksh before starting the test, and then I only run further tests on it if the variable is not null, so I could do a fair amount assuming the data ist here, for example, if the string starts with: Version I can use the 2nd and 3rd items, let me know: A: what part of that string is most important to know re output, and B: if there is version data showing at all in the Shell: line now. That requires the -x switch to see, so: pinxi -Ixx would show most of the data there in shell.

If you're familiar with this shell and its users, you could best tell me what should be shown assuming something can be grabbed. This is a nice little feature enhancement since in the past inxi just gave up if it was ksh, and didn't know about the other variants at all.

This is however precisely the kind of corner case adjustments and fine tunings I was hoping to get at this stage of beta testing, so thanks.
smxi/sgfxi site (manuals, how-to's, faqs) :: script forums :: Check out inxi sys info script!
h2
 
Posts: 120
Joined: 2006-10-29 20:00
Location: USA

Re: Beta testers for new Perl inxi requested

Postby dilberts_left_nut » 2018-03-18 01:51

h2 wrote:and I'm curious about the /snap stuff in partitions, are those actual partitions, given they are squashfs? That also looks like something that isn't handled.
https://docs.snapcraft.io/snaps/intro
It's a mechanism by which any given distro can be made as insecure as windows, by continuing to use vulnerable dependencies long after the security team has patched the issues ... ;)
AdrianTM wrote:There's no hacker in my grandma...
User avatar
dilberts_left_nut
 
Posts: 4866
Joined: 2009-10-05 07:54
Location: enzed

Re: Beta testers for new Perl inxi requested

Postby h2 » 2018-03-18 02:05

dilbert, I'm glad you said it, heh. That's now filtered out however since those aren't real partitions.
smxi/sgfxi site (manuals, how-to's, faqs) :: script forums :: Check out inxi sys info script!
h2
 
Posts: 120
Joined: 2006-10-29 20:00
Location: USA

Re: Beta testers for new Perl inxi requested

Postby h2 » 2018-03-18 04:12

Code: Select all
readlink  /sys/bus/usb/devices/usb7/7-1/7-1.1.0/driver


Sunrat, does that show something like: ../../../../../../bus/usb/drivers/ath9k_htc

This path is predictable, that is: bus ID: 7:2 translates to usb7/7-1 [the second device on 7, starts at 0]/7-1.1.0 [I believe the first part of the usb device, which is what we want]/driver is the symbolic link to the relevant file.

This is a pretty easy path to guess at, since it's just 7 then the id minus 1, then put into that format.

Looking at your data: usb7/7-0:1.0/uevent:["DEVTYPE=usb_interface", "DRIVER=hub",

so that's the hub the device is connected to. usb7/7-1/7-1:1.0/drive is then the link to the drive. I believe this may work, but please confirm that the above readlink returns that path, if so, it's solvable.

You'll note that this does not require knowing the interface name.

note: I checked this on a more complicated usb data set, and it doesn't work, the usb id dosn't translate as expected when it's a larger number. Not sure what's up there.

Here's an example of another way it can be:

Code: Select all
readlink /sys/bus/usb/devices/usb4/4-1/4-1.1/4-1.1:1.0/driver
../../../../../../../bus/usb/drivers/snd-usb-audio

readlink /sys/bus/usb/devices/usb4/4-1/4-1.1/4-1.1:1.1/driver
../../../../../../../bus/usb/drivers/snd-usb-audio

readlink /sys/bus/usb/devices/usb4/4-1/4-1.1/4-1.1:1.2/driver
../../../../../../../bus/usb/drivers/snd-usb-audio

readlink /sys/bus/usb/devices/usb4/4-1/4-1.1/4-1.1:1.3/driver
../../../../../../../bus/usb/drivers/cm109


That's a usb sound card driver, you'll notice it's one level further in, and it's also either one of the first 3, or the last one, 1.3, probably the last one, but hard to say.
smxi/sgfxi site (manuals, how-to's, faqs) :: script forums :: Check out inxi sys info script!
h2
 
Posts: 120
Joined: 2006-10-29 20:00
Location: USA

Next

Return to General Questions

Who is online

Users browsing this forum: CwF and 9 guests

fashionable