Welcome!
Important information
-- Spectre and Meltdown vulnerabilities
-- Change in MX sources

News
-- MX Linux on social media: here
-- Mepis support still here

Current releases
-- MX-17.1 Final release info here
-- antiX-17 release info here

New users
-- Please read this first, and don't forget to add system and hardware information to posts!
-- Here are the Forum Rules

inxi / pinxi 2.9.00 beta testers!

Message
Author
User avatar
rokytnji.1
Forum Regular
Forum Regular
Posts: 752
Joined: Sun Apr 13, 2014 9:06 pm

Re: inxi / pinxi 2.9.00 beta testers!

#111 Post by rokytnji.1 » Fri Mar 09, 2018 7:08 pm

Ooops. My bad being punch drunk at dawn. Sorry. I'll blame it on muscle memory. Yeah, that's the ticket. :pint:

Code: Select all

arry@biker:~
$ pinxi -Fxxx
System:
  Host: biker Kernel: 4.15.5-antix.1-amd64-smp x86_64 bits: 64 compiler: gcc v: 6.3.0 
  Desktop: IceWM 1.4.2 dm: slim 
  Distro: antiX-17_x64-full Heather Heyer 24 October 2017 
Machine:
  Type: Desktop System: Google product: Parrot v: 1.0 serial: N/A Chassis: type: 3 
  serial: N/A 
  Mobo: Google model: Parrot v: 1.0 serial: N/A BIOS: coreboot 
  v: 4.0-6588-g4acd8ea-dirty date: 09/04/2014 
Battery:
  BAT-X: charge: 31.3 Wh condition: 31.3/37.0 Wh (85%) volts: 17.3/14.8 
  model: SANYO AL12B32 type: Li-ion serial: 0000000000001D0F status: Full 
CPU:
  Topology: Dual Core model: Intel Celeron 1007U type: MCP arch: Ivy Bridge rev: 9 
  L2 cache: 2048 KB 
  flags: lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 5986 
  Speed: 1093 MHz min/max: 800/1500 MHz Core speeds: 1: 798 2: 798 
Graphics:
  Card-1: Intel 3rd Gen Core processor Graphics Controller driver: i915 v: kernel 
  bus ID: 00:02.0 chip ID: 8086:0156 
  Display Server: X.Org 1.19.2 driver: modesetting unloaded: vesa,fbdev 
  resolution: 1366x768~60Hz 
  OpenGL: renderer: Mesa DRI Intel Ivybridge Mobile version: 3.3 Mesa 13.0.6 
  compat-v: 3.0 direct render: Yes 
Audio:
  Card-1: Intel 7 Series/C216 Family High Definition Audio Controller 
  driver: snd_hda_intel v: kernel bus ID: 00:1b.0 chip ID: 8086:1e20 
  Sound Server: ALSA v: k4.15.5-antix.1-amd64-smp 
Network:
  Card-1: Qualcomm Atheros AR9462 Wireless Network Adapter driver: ath9k v: kernel 
  bus ID: 01:00 chip ID: 168c:0034 
  IF: wlan0 state: up mac: 3c:77:e6:26:f5:b5 
  Card-2: Broadcom Limited NetLink BCM57785 Gigabit Ethernet PCIe driver: tg3 v: 3.137 
  port: N/A bus ID: 02:00 chip ID: 14e4:16b5 
  IF: eth0 state: down mac: 20:1a:06:14:09:d9 
Drives:
  HDD Total Size: 14.91 GB used: 25.54 GB (171.2%) 
  ID-1: /dev/mmcblk0 model: N/A size: 29.72 GB serial: 0x61881eb6 
  ID-2: /dev/sda model: SanDisk_SSD_U100 size: 14.91 GB serial: 132553400495 rev: 6.14 
Partition:
  ID-1: / size: 14.62 GB used: 4.40 GB (30.1%) fs: ext4 dev: /dev/sda1 
Sensors:
  System Temperatures: cpu: 45.0 C mobo: N/A 
  Fan Speeds (in RPM): N/A 
Info:
  Processes: 132 Uptime: 3:22 Memory: 2.81 GB used: 738.9 MB (25.7%) Init: SysVinit 
  v: 2.88 runlevel: 5 default: 5 Compilers: gcc: 6.3.0 alt: 6 Shell: bash 4.4.12 
  running in: lxterminal pinxi: 2.9.00-380-p 
 

jbMacAZ
Forum Novice
Forum  Novice
Posts: 39
Joined: Tue Aug 22, 2017 2:08 am

Re: inxi / pinxi 2.9.00 beta testers!

#112 Post by jbMacAZ » Fri Mar 09, 2018 7:29 pm

h2-1 wrote:jbMacAZ, 382 will fix that 'usb' glitch
384 looks clean, Thanks a lot! I like the partition detail supporting mmcblk, this will help me debug some installer issues on the T100CHI
MX-17.1 on Asus T100CHI (z3775, 64 bit quad core Intel atom baytrail) mixed-mode 32 bit UEFI, 64 bit OS

User avatar
h2-1
Forum Regular
Forum Regular
Posts: 429
Joined: Sat Nov 15, 2008 3:16 pm

Re: inxi / pinxi 2.9.00 beta testers!

#113 Post by h2-1 » Fri Mar 09, 2018 8:28 pm

ok, I've gotten most of the toughest bugs solved. 0386 has all the main bugs I know about as handled as they can be given the available data.

the cpu die issue I thought I could do in a certain way, but it turns out I can't, /proc/cpuinfo can't be used to detect > 1 cpu die, so I have to run other tests for ARM, that do appear to be reliable so far, and for ryzen, which is also reliable according to the docs I read. Basically ryzen is split into blocks of 8 cores, so the die count is rounded up core count / 8. Basic.

The missing networking stuff is resolved I believe, now all missing networking IF will show under the main CARD report with IF-ID-1: for example, incrementing. I found long lists of IFs on say, big arm servers, hard to read, so I made the line starter more obvious.

I don't know if I've missed anything else, let me know, I think this largely covers it, barring more undefined data errors, which I'm still getting now and then from various user systems, but fewer by far.

debugging and logging is enhanced a lot, which makes debugging failures a lot easier.
smxi/sgfxi site (manuals, how-to's, faqs) :: script forums :: Check out inxi sys info script!

User avatar
h2-1
Forum Regular
Forum Regular
Posts: 429
Joined: Sat Nov 15, 2008 3:16 pm

Re: inxi / pinxi 2.9.00 beta testers!

#114 Post by h2-1 » Fri Mar 09, 2018 8:30 pm

jbMacAZ, I looked in the data to see if I could get more mmcblk data, like the device name, but I couldn't find that anywhere, if you find a way to discover that, let me know. I'll take a look in /dev/disk/... to see if there's anything there.

biker, yours looks solid, that's a relief, lol. I'm very impressed by the amount of failures and glitches everyone found, on all 10 of my test systems, when I announced beta testing, I was getting no errors, or of course I wouldn't have announced it ready to test, so the range of hardware/os has really been great to expose a lot of untested and trusted as not null data. More pops up all the time, but the flow is slowing to a trickle now.

I still technically have two features to complete, raid, and bsd hard disks, but I'm waiting for the bugs to finish to get those done, I already discovered a wrong assumption with zfs raid reports that will require redoing the raid logic a bit to handle that.

So it's maybe 1 week from final release, but ALL errors, glitches, bugs, small oversights, whatever, are show stoppers as far as I'm concerned, and I won't release pinxi as inxi 3.0.0 until nobody can find anything wrong or glitchy with it.
smxi/sgfxi site (manuals, how-to's, faqs) :: script forums :: Check out inxi sys info script!

User avatar
h2-1
Forum Regular
Forum Regular
Posts: 429
Joined: Sat Nov 15, 2008 3:16 pm

Re: inxi / pinxi 2.9.00 beta testers!

#115 Post by h2-1 » Fri Mar 09, 2018 8:56 pm

jbMacAZ, I looked again, and realized I had to explicitly add the mmblk type to the advanced disk data collector.

0387 should now show model name and serial and maybe also firmware rev
smxi/sgfxi site (manuals, how-to's, faqs) :: script forums :: Check out inxi sys info script!

jbMacAZ
Forum Novice
Forum  Novice
Posts: 39
Joined: Tue Aug 22, 2017 2:08 am

Re: inxi / pinxi 2.9.00 beta testers!

#116 Post by jbMacAZ » Sat Mar 10, 2018 2:24 am

387 does show the mmcblk model name now. Looking forward to the 3.0 release
Last edited by jbMacAZ on Sun Mar 11, 2018 12:56 pm, edited 1 time in total.
MX-17.1 on Asus T100CHI (z3775, 64 bit quad core Intel atom baytrail) mixed-mode 32 bit UEFI, 64 bit OS

User avatar
h2-1
Forum Regular
Forum Regular
Posts: 429
Joined: Sat Nov 15, 2008 3:16 pm

Re: inxi / pinxi 2.9.00 beta testers!

#117 Post by h2-1 » Sat Mar 10, 2018 2:31 am

Good news. that was a subtle issue I'd half noticed, but your dataset showed me that there was in fact a solution, that was pretty easy to do.

I still have some core stuff to do, RAID, which doesn't impact most users, but it's not complete, and has some issues, and BSD drives, also which won't impact most users, but I'd like to have those done before I do 3.0.0 since I want pinxi to be feature complete in all areas relative to inxi, and better in many, before I do 3.0.0. Could be next week, depends on if I get more difficult to resolve issues or not, which is to say, I want the issues if they exist of course.

The raid is just a solid day or so, plus testing it a bit, the bsd disks I have to sort of just hope it works because i don't have a freebsd system with that data, I have some, but not with that.
smxi/sgfxi site (manuals, how-to's, faqs) :: script forums :: Check out inxi sys info script!

User avatar
h2-1
Forum Regular
Forum Regular
Posts: 429
Joined: Sat Nov 15, 2008 3:16 pm

Re: inxi / pinxi 2.9.00 beta testers!

#118 Post by h2-1 » Mon Mar 19, 2018 5:35 pm

Just a heads up, as of 2.9.00-0452-p there's only one outstanding issue which most people aren't even noticing.

There's some issues re version data being wrong in places, but unless I get requested user datasets or feedback, I'm not going to worry about those, since I can't fix stuff I don't get data on. Not you guys, you found probably 50% of the bugs so far, heh.

But I'm looking at release in the next few days, though due to the number and seriousness of some bugs, I am opting for the iniitial 2.9.01 release rather than the bug free goal I'd had for 3.0.0.

A few of the major upgrades were: usb audio and network device gets the real drivers, not the fake strings early versions, and inxi, were providing. That was a nifty addition. ARM devices now will try to show machine data, which I discovered is sometimes in /proc/cpuinfo along with the cpu data. I discovered this while working on an arm cpu bug, I'd noticed it before but never thought about at as an actual data source.

There's still some glitches, but as noted, unless I get user datasets, I can't fix those. not you guys, you were great about supplying that stuff.

There's one remaining bug I'm going to try to fix today, related to how usb network devices actually are id'ed internally, that's an old bug, was in inxi too. Note that almost all bugs I've fixed in the past days are inxi bugs, except for some recent bugs I created while finishing up features.

Thanks for all the help
smxi/sgfxi site (manuals, how-to's, faqs) :: script forums :: Check out inxi sys info script!

User avatar
h2-1
Forum Regular
Forum Regular
Posts: 429
Joined: Sat Nov 15, 2008 3:16 pm

Re: inxi / pinxi 2.9.00 beta testers!

#119 Post by h2-1 » Tue Mar 20, 2018 12:03 am

2.9.00-0456-p fixes the last bug I know about that's significant, failure to actually get the real IF of the usb nic device. If anyone has a usb networkingi device, and could post, from this version: pinxi -zixxx that would be appreciated so I can close this last issue, and release tomorrow.
smxi/sgfxi site (manuals, how-to's, faqs) :: script forums :: Check out inxi sys info script!

caprea
Forum Regular
Forum Regular
Posts: 118
Joined: Sat Aug 23, 2014 7:01 am

Re: inxi / pinxi 2.9.00 beta testers!

#120 Post by caprea » Tue Mar 20, 2018 2:33 pm

It's a live-session of MX17.1

Code: Select all

demo@mx1:~
$ pinxi -zixxx 
Network:   Card-1: Intel 82567V-2 Gigabit Network Connection driver: e1000e v: 3.2.6-k 
           port: a000 bus ID: 00:19 chip ID: 8086:10ce 
           IF: eth0 state: down mac: <filter> 
           Card-2: ASUSTek WL-167G v2 802.11g Adapter [Ralink RT2571W] type: USB driver: rt73usb 
           bus ID: 4:2 chip ID: 0b05:1723 
           IF: wlan0 state: up mac: <filter> 
           IP v4: <filter> type: dynamic wlan0 scope: global broadcast: <filter> 
           IP v6: <filter> type: noprefixroute dynamic scope: global 
           IP v6: <filter> scope: link 
           WAN IP: <filter> 

Code: Select all

demo@mx1:~
$ pinxi -zv7
System:    Host: mx1 Kernel: 4.15.0-1-amd64 x86_64 bits: 64 compiler: gcc v: 6.3.0 
           Desktop: Xfce 4.12.3 (Gtk 2.24.31) info: xfce4-panel dm: lightdm 1.18.3 
           Distro: MX-17.1-RC1_x64 Horizon March 6, 2018 
Machine:   Type: Desktop System: IPMTB-GS product: IPMTB-GS v: N/A serial: N/A 
           Chassis: PEGATRON CORPORATION type: 3 serial: N/A 
           Mobo: PEGATRON model: IPMTB-GS v: 1.00 serial: N/A BIOS: American Megatrends v: 3.00 
           date: 04/03/2009 
Memory:    RAM Report: permissions: Unable to run dmidecode. Are you root? 
CPU:       Topology: Quad Core model: Intel Core i7 920 type: MT MCP arch: Nehalem rev: 5 
           L2 cache: 8192 KB 
           flags: lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 42672 
           Speed: 2667 MHz min/max: N/A Core speeds: 1: 2667 2: 2666 3: 2667 4: 2667 5: 2667 
           6: 2667 7: 2667 8: 2666 
Graphics:  Card-1: NVIDIA GT200b [GeForce GTX 275] driver: nouveau v: kernel bus ID: 08:00.0 
           chip ID: 10de:05e6 
           Display Server: x11 (X.Org 1.19.2) driver: nouveau 
           unloaded: modesetting,vesa,nv,fbdev resolution: 1024x768~60Hz 
           OpenGL: renderer: Gallium 0.4 on NVA0 version: 3.3 Mesa 13.0.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 
           Sound Server: ALSA v: k4.15.0-1-amd64 
Network:   Card-1: Intel 82567V-2 Gigabit Network Connection driver: e1000e v: 3.2.6-k 
           port: a000 bus ID: 00:19 chip ID: 8086:10ce 
           IF: eth0 state: down mac: <filter> 
           Card-2: ASUSTek WL-167G v2 802.11g Adapter [Ralink RT2571W] type: USB driver: rt73usb 
           bus ID: 4:2 chip ID: 0b05:1723 
           IF: wlan0 state: up mac: <filter> 
           IP v4: <filter> type: dynamic wlan0 scope: global broadcast: <filter> 
           IP v6: <filter> type: noprefixroute dynamic scope: global 
           IP v6: <filter> scope: link 
           WAN IP: <filter> 
Drives:    HDD Total Size: 705.91 GB used: 1.25 GB (0.2%) 
           ID-1: /dev/sda model: WDC_WD7500AAVS-0 size: 698.64 GB serial: <filter> rev: 1A01 
           temp: 21 C 
           ID-2: /dev/sdb type: USB model: Basic_Line size: 7.28 GB serial: <filter> rev: 8.07 
           Optical-1: /dev/sr0 vendor: TSSTcorp model: CDDVDW SH-S223B rev: SB00 
           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: /live/boot-dev size: 7.17 GB used: 1.25 GB (17.4%) fs: ext4 dev: /dev/sdb1 
           label: MX-Live-usb uuid: 832fc0c4-e4e5-4ab1-8d47-ee9b1524507d 
           ID-2: / size: 3.03 GB used: 258.4 MB (8.3%) fs: overlay dev: ERR-102 label: N/A 
           uuid: N/A 
Unmounted: ID-1: /dev/sda1 size: 698.64 GB fs: NTFS label: System uuid: 2AFE4176FE413B79 
           ID-2: /dev/sdb2 size: 50.0 MB fs: root required label: MX-uefi uuid: 74D7-3F03 
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: 2.00 type: Full speed (or root) hub chip ID: 1d6b:0002 
           Hub: 4:1 usb: 2.00 type: Full speed (or root) hub chip ID: 1d6b:0002 
           Device-1: ASUSTek WL-167G v2 802.11g Adapter [Ralink RT2571W] bus ID: 4:2 usb: 2.00 
           type: Vendor Specific Protocol chip ID: 0b05:1723 
           Device-2: Alcor Micro Flash Drive bus ID: 4:3 usb: 2.00 type: Mass Storage 
           chip ID: 058f:6387 
           Hub: 5:1 usb: 2.00 type: Full speed (or root) hub chip ID: 1d6b:0002 
           Hub: 6:1 usb: 1.10 type: Full speed (or root) hub chip ID: 1d6b:0001 
           Hub: 7:1 usb: 1.10 type: Full speed (or root) hub chip ID: 1d6b:0001 
           Hub: 8:1 usb: 1.10 type: Full speed (or root) hub chip ID: 1d6b:0001 
           Device-3: Chicony Ltd KBR-0108 bus ID: 8:2 usb: 1.10 type: Keyboard 
           chip ID: 04f2:0200 
           Hub: 9:1 usb: 1.10 type: Full speed (or root) hub chip ID: 1d6b:0001 
           Hub: 10:1 usb: 1.10 type: Full speed (or root) hub chip ID: 1d6b:0001 
           Hub: 11:1 usb: 1.10 type: Full speed (or root) hub chip ID: 1d6b:0001 
Sensors:   System Temperatures: cpu: 42.2 C mobo: N/A 
           Fan Speeds (in RPM): cpu: 1427 fan-2: 0 fan-3: 0 
Info:      Processes: 228 Uptime: 7 min Memory: 3.85 GB used: 861.0 MB (21.9%) Init: SysVinit 
           v: 2.88 runlevel: 5 default: 5 Compilers: gcc: 6.3.0 alt: 6 Shell: bash 4.4.12 
           running in: xfce4-terminal pinxi: 2.9.00-457-p 

Post Reply

Return to “antiX”