- This topic has 1,421 replies, 37 voices, and was last updated May 12-10:07 am by Brian Masinick.
-
Posts
-
Brian Masinick
pinxi -b System: Host: antix21 Kernel: 4.9.0-294-antix.1-amd64-smp arch: x86_64 bits: 64 Desktop: IceWM v: 2.9.9 Distro: antiX-21-runit_x64-base Grup Yorum 30 October 2021 Machine: Type: Laptop System: Dell product: Inspiron 5558 v: 01 serial: <superuser required> Mobo: Dell model: 086DKN v: A00 serial: <superuser required> UEFI: Dell v: A04 date: 08/06/2015 Battery: ID-1: BAT0 charge: 30.1 Wh (100.0%) condition: 30.1/41.4 Wh (72.6%) CPU: Info: dual core Intel Core i7-5500U [MT MCP] speed (MHz): avg: 675 min/max: 500/2401 Graphics: Device-1: Intel HD Graphics 5500 driver: i915 v: kernel Device-2: NVIDIA GK208BM [GeForce 920M] driver: N/A Device-3: Suyin Integrated_Webcam_HD type: USB driver: uvcvideo Display: x11 server: X.Org v: 1.20.11 driver: X: loaded: modesetting unloaded: fbdev,vesa dri: swrast gpu: i915 resolution: 1366x768~60Hz OpenGL: renderer: llvmpipe (LLVM 11.0.1 256 bits) v: 4.5 Mesa 20.3.5 Network: Device-1: Intel Wireless 3160 driver: iwlwifi Device-2: Realtek RTL810xE PCI Express Fast Ethernet driver: r8169 Device-3: Intel Bluetooth wireless interface type: USB driver: btusb Drives: Local Storage: total: 447.13 GiB used: 27.87 GiB (6.2%) Info: Processes: 199 Uptime: 44m Memory: 7.77 GiB used: 1.31 GiB (16.8%) Shell: Bash pinxi: 3.3.21-14--
Brian Masinickh2
No, all those sites are mine. Documentation is tedious and I don’t go through it all routinely to update it, the stuff I am working on at the moment is what I update. I don’t even bother updating the doc version/release date often, though the new docs are working better than the old ones. I almost never update most of the docs on smxi.org except for the manual/options/changelog html versions, which are automatically generated now as well, so those tend to track quite well with current inxi.
The more docs there are, the more docs there are to maintain, and docs are boring to maintain, so I tend to only update intermittently something outside of those core files, and the configuration html which I usually also update when I add a config option/value otherwise I’ll forget.
In order of docs least to most likely to be updated [these all overlap each other, the order is only a rough guess]:
- github binxi readme page. This will never get updated.
- smxi.org [the green and black pages]
- github inxi single wiki page, which only points to real resource pages. This one is updated so rarely that I almost forget it even exists.
- smxi.org [the black and white pages]
- github readme pages for inxi master and inxi-perl branches.
- inxi-perl/docs files
- smxi.org [black and white options, man, and changelog pages, now automated]
- pinxi -h and pinxi man and pinxi changelog [these last 3 are usually now updated in real time as I do the feature, unless I forget, but I try to do help/man/changelog as I do the fix or bug, which is why sometimes the changelog is not quite right, I might change stuff a lot as I find issues, and forget to update the changelog].
docs are a pain, and since almost nobody reads them, and certainly nobody helps, they are always exactly what they are, no more, no less.
With this said, the new modularized docs in inxi-perl/docs are a big upgrade, and make the docs quite a bit more usable, for me anyway.
There’s a common misperception in free software that there is a ‘they’ that does this stuff, but there isn’t. rsync’s man page, for example, has been a mess for years, and sorely needs reorganization. I know the guy who redid that page last time, he actually helped do the inxi man page too a while back, but he doesn’t do the stuff ongoing, it’s a one time thing.
There are probably other docs I’m forgetting about, which means I’ve forgotten about them… oh, right, like the totally out of date techpatterns.com inxi forum posts.
- This reply was modified 8 months ago by h2.
- This reply was modified 8 months ago by h2.
- This reply was modified 8 months ago by h2.
inxi system information script (install info) :: inxi git
Brian Masinick
Good to know; in any case I know the guy behind this stuff and the code is good; if there are any defects you notice them long before I catch them at this stage.
Thanks for sharing and thanks for responding to the conversation here; it’s helpful to me and to several people who have been asking good questions.
--
Brian MasinickIn terms of the code, this is roughly who is finding bugs.
- me, I spot many just randomly looking at inxi outputs online, best case is when they paste int he actual perl error, which helps narrow it down, next best is when I have a good idea why the feature is wrong. Those users, by the way, virtually never file issue or bug reports, they don’t even look at the inxi output they posted. I also spot a lot just doing random testing on various systems, but that has certain limits defined by what systems I have access to, and how similar they are to each other.
- Right now, mrmazda has been finding a lot of issues and things that could be better with inxi, a big chunk of -G is now based on his requests and observations, but also other items to a lesser extent.
- For specific advanced new upgrades, like -C, package data, -G, etc, somewhat ongoing, the guys at lq slackware forums. Their interests tend more towards the heavy lifting parts of inxi, hardware, servers, etc, which is great.
- github issues, which are random
- someone contacting me via forum pm, which is usually not a great idea because it assumes I viist distro forums routinely.
- irc, sometimes, now and then. This and the previous are roughly equally un/likely.
This all varies, around jan and ongoing 2021, stan from linux.org did a huge amount of behind the scenes work, and I mean a lot – oddly enough, for freebsd and openbsd, which once again proved to me that the only generally active supporters of the bsds and inxi are linux users testing the bsds, which is… odd. I take this reality into account now increasingly heavily when deciding where and when to allocate my finite time and energy. I believe I can count on one hand, with 5 fingers left over, the number of quality, debugger data supplied, promptly answered, BSD sourced issues reported in the past 3 years. Though the OpenBSD guys at daemon forums if they find the issue interesting have helped if I ask for it now and then, but OpenBSD kinds of stands in a class by itself when it comes to the BSDs, so that’s not surprising.
Not mentioning specific distros, there has been a significant dropoff over the past 3 years however in distro active support and interest. I put this down to the new linux generation, who are raised with people doing everything for them, like smartphones and their apps, and the ongoing rapidly declining unix graybeards, who were generally good at problem solving, and liked it.
This to me is the single biggest danger to inxi’s future in my view, this new passive generation of non-contributing ‘open source’ _consumers_, who I think tend to think of open source as something to be used to bootstrap your startup before you do your hoped for IPO and then moving on to the next project, not as free software made to promote freedom. Open Source was always a toxic concept to me for this reason.
- This reply was modified 8 months ago by h2.
- This reply was modified 8 months ago by h2.
- This reply was modified 8 months ago by h2.
inxi system information script (install info) :: inxi git
Brian Masinick
Yeah I hear you! I’m one of those guys, ‘When I get older, losing my hair…’ — I’m 66 so I, like Paul, Ringo, and the deceased members of the once famous band from Liverpool that we all eventually age.
I was once a big multiple systems user, putting 10-12, occasionally more systems than that at times on my hardware plus occasionally using a virtual machine or a live instance to run even more systems.
In the past I’ve had BSD, VMware, Windows and Linux software on the same physical hardware so I have stretched the capabilities of the boot loader and I used to be a GRUB legacy expert.
I used to build GNU software from source code so when the early Linux systems arrived they were no problem to build; the biggest problem in those days was finding halfway decent graphics display drivers. I remember that my first Slackware build was an old system from a book that lacked current display drivers so I had 8 color 640×480 display until I could dig up the right graphics drivers, ‘sneaker net’ them onto my system from a fast UNIX server I had access to and finally install them.
Though I had to go through a few of those early pains, the 90s software was super fast.
antiX is a bit like this because it sometimes uses software conceived from that era, small, lean, and fast. I still appreciate such things.
Software like Gentoo Linux and LFS, Linux From Scratch acts like and claims to be fast and efficient. If it is, I was never able to discern any significant difference; in fact the time and effort to put such systems together wasn’t worth it; instead I occasionally build a rare application or user interface myself, but even that is mostly in the past.
I recently wrote several small clock applications in as many languages as I could, sometimes getting code or code ideas from other people and reworking them to fine tune the appearance, just to remember a bit of code that has been gradually slipping out of my head.
I’ve always been more of a systems engineer, project manager and administrator than a crack development engineer. I understand code and I can envision ideas but many people are far superior development engineers than me, I’m better at integrating components and specifying requirements according to what common people SAY they want.
--
Brian MasinickBrian Masinick
I had a very fast, efficient medical test this morning: 10 minutes to complete the test!
Very happy with the great facilities in our area!
Haven’t used any of my computer systems yet but I have a Pixel 4A 5G that works well for sending quick notes like this!
--
Brian MasinickBrian Masinick
I did a bit of exploratory work on the antiX 5.10 kernel, because 5.10.137 WORKS on my Acer Aspire 5 Model A515-55, but NOT on my Dell Inspiron 5558 laptop, which until recently had worked with ANY antiX kernel!
So here’s what I tried on the Dell today in the 5.10 series:
1) linux-image-5.10.104-antix.1-amd64-smp — works on the Dell!
2) linux-image-5.10.137-antix.1-amd64-smp — does NOT work on the Dell; kernel dumps.
3) linux-image-5.10.137-antix.1-686-smp-pae — does NOT work on the Dell; kernel dumps.I’ve previously used the older 5.10.88 image and that works fine too, but that was not in today’s test.
inxi -xz CPU: dual core Intel Core i7-5500U (-MT MCP-) speed/min/max: 2463/500/2401 MHz Kernel: 5.10.104-antix.1-amd64-smp x86_64 Up: 1h 18m Mem: 514.9/7868.6 MiB (6.5%) Storage: 447.13 GiB (6.2% used) Procs: 174 Shell: Bash 5.1.4 inxi: 3.3.21--
Brian MasinickBrian Masinick
I did a bit of exploratory work on the antiX 5.10 kernel, because 5.10.137 WORKS on my Acer Aspire 5 Model A515-55, but NOT on my Dell Inspiron 5558 laptop, which until recently had worked with ANY antiX kernel!
So here’s what I tried on the Dell today in the 5.10 series:
1) linux-image-5.10.104-antix.1-amd64-smp — works on the Dell!
2) linux-image-5.10.137-antix.1-amd64-smp — does NOT work on the Dell; kernel dumps.
3) linux-image-5.10.137-antix.1-686-smp-pae — does NOT work on the Dell; kernel dumps.I’ve previously used the older 5.10.88 image and that works fine too, but that was not in today’s test.
inxi -xz CPU: dual core Intel Core i7-5500U (-MT MCP-) speed/min/max: 2463/500/2401 MHz Kernel: 5.10.104-antix.1-amd64-smp x86_64 Up: 1h 18m Mem: 514.9/7868.6 MiB (6.5%) Storage: 447.13 GiB (6.2% used) Procs: 174 Shell: Bash 5.1.4 inxi: 3.3.21Apparently I have more “work” to do; I put two 5.10 kernels on the Dell, and then neither of them worked. I’ll revisit that again the next time I’m on that system.
Meanwhile I’m back on the Acer Aspire 5 Model A515-55 and I DO have a 5.10 kernel working here:
./pinxi -N Network: Device-1: Intel Killer Wi-Fi 6 AX1650i 160MHz Wireless Network Adapter driver: iwlwifi Device-2: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet driver: r8169 [antixMas]:/home/masinick/bin> ./pinxi -Nb System: Host: antixMas Kernel: 5.10.137-antix.1-amd64-smp arch: x86_64 bits: 64 Desktop: IceWM v: 2.9.9 Distro: antiX-21-runit_x64-full Grup Yorum 30 October 2021 Machine: Type: Laptop System: Acer product: Aspire A515-55 v: V1.12 serial: <superuser required> Mobo: IL model: Doc_IL v: V1.12 serial: <superuser required> UEFI: Insyde v: 1.12 date: 09/07/2020 Battery: ID-1: BAT1 charge: 47.8 Wh (100.0%) condition: 47.8/47.8 Wh (100.0%) CPU: Info: dual core Intel Core i3-1005G1 [MT MCP] speed (MHz): avg: 3387 min/max: 400/3400 Graphics: Device-1: Intel Iris Plus Graphics G1 driver: i915 v: kernel Device-2: Quanta HD User Facing type: USB driver: uvcvideo Display: x11 server: X.Org v: 1.20.11 driver: X: loaded: modesetting unloaded: fbdev,vesa dri: iris gpu: i915 resolution: 1920x1080~60Hz OpenGL: renderer: Mesa Intel UHD Graphics (ICL GT1) v: 4.6 Mesa 20.3.5 Network: Device-1: Intel Killer Wi-Fi 6 AX1650i 160MHz Wireless Network Adapter driver: iwlwifi Device-2: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet driver: r8169 Drives: Local Storage: total: 119.24 GiB used: 12.3 GiB (10.3%) Info: Processes: 173 Uptime: 8m Memory: 3.62 GiB used: 593.4 MiB (16.0%) Shell: Bash pinxi: 3.3.21-14--
Brian MasinickBrian Masinick
Graphics and basic output for the Acer Aspire 5 A515-55:
bin/pinxi -Gxxx Graphics: Device-1: Intel Iris Plus Graphics G1 vendor: Acer Incorporated ALI driver: i915 v: kernel arch: Gen-11 ports: active: eDP-1 empty: HDMI-A-1 bus-ID: 00:02.0 chip-ID: 8086:8a56 class-ID: 0300 Device-2: Quanta HD User Facing type: USB driver: uvcvideo bus-ID: 1-5:3 chip-ID: 0408:a061 class-ID: 0e02 Display: x11 server: X.Org v: 1.20.11 driver: X: loaded: modesetting unloaded: fbdev,vesa dri: iris gpu: i915 display-ID: :0.0 screens: 1 Screen-1: 0 s-res: 1920x1080 s-dpi: 96 s-size: 508x285mm (20.00x11.22") s-diag: 582mm (22.93") Monitor-1: eDP-1 model: ChiMei InnoLux 0x15e7 res: 1920x1080 hz: 60 dpi: 142 size: 344x193mm (13.54x7.6") diag: 394mm (15.5") modes: 1920x1080 OpenGL: renderer: Mesa Intel UHD Graphics (ICL GT1) v: 4.6 Mesa 20.3.5 direct render: Yes [antixMas]:/home/masinick> bin/pinxi -b System: Host: antixMas Kernel: 5.19.0-8.2-liquorix-amd64 arch: x86_64 bits: 64 Desktop: IceWM v: 2.9.9 Distro: antiX-21-runit_x64-full Grup Yorum 30 October 2021 Machine: Type: Laptop System: Acer product: Aspire A515-55 v: V1.12 serial: <superuser required> Mobo: IL model: Doc_IL v: V1.12 serial: <superuser required> UEFI: Insyde v: 1.12 date: 09/07/2020 Battery: ID-1: BAT1 charge: 47.8 Wh (100.0%) condition: 47.8/47.8 Wh (100.0%) CPU: Info: dual core Intel Core i3-1005G1 [MT MCP] speed (MHz): avg: 1145 min/max: 400/1201 Graphics: Device-1: Intel Iris Plus Graphics G1 driver: i915 v: kernel Device-2: Quanta HD User Facing type: USB driver: uvcvideo Display: x11 server: X.Org v: 1.20.11 driver: X: loaded: modesetting unloaded: fbdev,vesa dri: iris gpu: i915 resolution: 1920x1080~60Hz OpenGL: renderer: Mesa Intel UHD Graphics (ICL GT1) v: 4.6 Mesa 20.3.5 Network: Device-1: Intel Killer Wi-Fi 6 AX1650i 160MHz Wireless Network Adapter driver: iwlwifi Device-2: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet driver: r8169 Drives: Local Storage: total: 119.24 GiB used: 12.91 GiB (10.8%) Info: Processes: 179 Uptime: 3m Memory: 3.62 GiB used: 592.5 MiB (16.0%) Shell: Bash pinxi: 3.3.21-14--
Brian MasinickBrian Masinick
Interesting! The Acer ALSO uses the i915 graphics, but I can usually get the 5.10 kernels working here!
--
Brian MasinickBrian Masinick
The Dell has i915 too plus nvidia…
Machine: Type: Laptop System: Dell product: Inspiron 5558 v: 01 serial: <superuser required> Mobo: Dell model: 086DKN v: A00 serial: <superuser required> UEFI: Dell v: A04 date: 08/06/2015 Battery: ID-1: BAT0 charge: 30.1 Wh (100.0%) condition: 30.1/41.4 Wh (72.6%) CPU: Info: dual core Intel Core i7-5500U [MT MCP] speed (MHz): avg: 675 min/max: 500/2401 Graphics: Device-1: Intel HD Graphics 5500 driver: i915 v: kernel Device-2: NVIDIA GK208BM [GeForce 920M] driver: N/A Device-3: Suyin Integrated_Webcam_HD type: USB driver: uvcvideo Display: x11 server: X.Org v: 1.20.11 driver: X: loaded: modesetting unloaded: fbdev,vesa dri: swrast gpu: i915 resolution: 1366x768~60Hz OpenGL: renderer: llvmpipe (LLVM 11.0.1 256 bits) v: 4.5 Mesa 20.3.5--
Brian MasinickBrian Masinick
techore
This is my new home theater PC which @Moddit and others on the forum helped me fix alsa. Further testing needs to be done but I am hopeful the audio oddities experienced using pulseaudio are gone.
sudo inxi -bz System: Kernel: 5.10.137-antix.1-amd64-smp arch: x86_64 bits: 64 Desktop: dwm v: 6.3 Distro: antiX-21-runit_x64-core Grup Yorum 31 October 2021 Machine: Type: Desktop System: Gigabyte product: H87-D3H v: N/A serial: N/A Mobo: Gigabyte model: H87-D3H-CF v: x.x serial: N/A UEFI: American Megatrends v: F10 date: 08/18/2015 CPU: Info: quad core Intel Xeon E3-1230 v3 [MT MCP] speed (MHz): avg: 3686 min/max: 800/3700 Graphics: Device-1: NVIDIA TU116 [GeForce GTX 1650 SUPER] driver: nvidia v: 470.129.06 Display: server: X.Org v: 1.20.11 driver: X: loaded: nvidia unloaded: fbdev,modesetting,nouveau,vesa gpu: nvidia resolution: 3840x2160~60Hz OpenGL: renderer: NVIDIA GeForce GTX 1650 SUPER/PCIe/SSE2 v: 4.6.0 NVIDIA 470.129.06 Network: Device-1: Intel Ethernet I217-V driver: e1000e Drives: Local Storage: total: 727.9 GiB used: 12.48 GiB (1.7%) Info: Processes: 223 Uptime: 1h 1m Memory: 31.31 GiB used: 1.51 GiB (4.8%) Shell: fish inxi: 3.3.19Brian Masinick
Note to self to verify 5.10.142-2 kernel
I’ve yet to “see” the 5.10.142 kernel (either version) on the repo I have (“Conexco, or something like that). 137 is the latest 5.10 kernel I’ve seen there, as of Sunday, 10:30 AM EDT.
--
Brian MasinickBrian Masinick
- You must be logged in to reply to this topic.
