- 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: 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: 3372 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: 10.83 GiB (9.1%) Info: Processes: 182 Uptime: 1m Memory: 3.62 GiB used: 555.5 MiB (15.0%) Shell: Bash pinxi: 3.3.21-11--
Brian MasinickBrian Masinick
Forum Email responses were not working properly; I hadn’t received any since July 2, once I looked closely.
Our Website admin took care of the problem and it appears to be working once again.--
Brian MasinickBrian Masinick
Forum Email is now flowing freely thanks to peregrine, our antiX Forum software administrator.
With that, here’s another Perl development system information tool (the development version is called pinxi; the released version is simply inxi):
pinxi -v3 System: Host: antixMas Kernel: 5.10.137-antix.1-amd64-smp arch: x86_64 bits: 64 compiler: gcc v: 10.2.1 Desktop: IceWM v: 2.9.9 Distro: antiX-21-runit_x64-full Grup Yorum 30 October 2021 base: Debian GNU/Linux 11 (bullseye) 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%) volts: 12.3 min: 11.2 model: LGC AP18C8K status: full CPU: Info: dual core model: Intel Core i3-1005G1 bits: 64 type: MT MCP arch: Ice Lake rev: 5 cache: L1: 160 KiB L2: 1024 KiB L3: 4 MiB Speed (MHz): avg: 3194 high: 3404 min/max: 400/3400 cores: 1: 2909 2: 3404 3: 3400 4: 3065 bogomips: 9523 Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx Graphics: Device-1: Intel Iris Plus Graphics G1 vendor: Acer Incorporated ALI driver: i915 v: kernel arch: Gen-11 bus-ID: 00:02.0 Device-2: Quanta HD User Facing type: USB driver: uvcvideo bus-ID: 1-5:3 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 direct render: Yes Network: Device-1: Intel Killer Wi-Fi 6 AX1650i 160MHz Wireless Network Adapter driver: iwlwifi v: kernel bus-ID: 00:14.3 IF: wlan0 state: up mac: 8c:8d:28:33:ec:3a Device-2: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet vendor: Acer Incorporated ALI driver: r8169 v: kernel port: 3000 bus-ID: 01:00.0 IF: eth0 state: down mac: b4:a9:fc:db:69:5e Drives: Local Storage: total: 119.24 GiB used: 10.86 GiB (9.1%) Info: Processes: 173 Uptime: 0m Memory: 3.62 GiB used: 531.8 MiB (14.3%) Init: runit runlevel: 2 Compilers: gcc: 10.2.1 Packages: 1624 Shell: Bash v: 5.1.4 pinxi: 3.3.21-11- This reply was modified 8 months, 1 week ago by Brian Masinick.
--
Brian MasinickBrian Masinick
Here’s a more verbose pinxi listing – verbosity 4 from a short while ago:
pinxi -v4 System: Host: antixMas Kernel: 5.10.137-antix.1-amd64-smp arch: x86_64 bits: 64 compiler: gcc v: 10.2.1 Desktop: IceWM v: 2.9.9 Distro: antiX-21-runit_x64-full Grup Yorum 30 October 2021 base: Debian GNU/Linux 11 (bullseye) 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%) volts: 12.3 min: 11.2 model: LGC AP18C8K status: full CPU: Info: dual core model: Intel Core i3-1005G1 bits: 64 type: MT MCP arch: Ice Lake rev: 5 cache: L1: 160 KiB L2: 1024 KiB L3: 4 MiB Speed (MHz): avg: 2501 high: 3397 min/max: 400/3400 cores: 1: 2783 2: 1187 3: 2638 4: 3397 bogomips: 9523 Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx Graphics: Device-1: Intel Iris Plus Graphics G1 vendor: Acer Incorporated ALI driver: i915 v: kernel arch: Gen-11 bus-ID: 00:02.0 Device-2: Quanta HD User Facing type: USB driver: uvcvideo bus-ID: 1-5:4 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 direct render: Yes Network: Device-1: Intel Killer Wi-Fi 6 AX1650i 160MHz Wireless Network Adapter driver: iwlwifi v: kernel bus-ID: 00:14.3 IF: wlan0 state: up mac: 8c:8d:28:33:ec:3a Device-2: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet vendor: Acer Incorporated ALI driver: r8169 v: kernel port: 3000 bus-ID: 01:00.0 IF: eth0 state: down mac: b4:a9:fc:db:69:5e Drives: Local Storage: total: 119.24 GiB used: 11.14 GiB (9.3%) ID-1: /dev/nvme0n1 vendor: Samsung model: MZVLQ128HBHQ-00000 size: 119.24 GiB temp: 14.8 C Partition: ID-1: / size: 28.67 GiB used: 11.14 GiB (38.9%) fs: ext4 dev: /dev/nvme0n1p5 ID-2: swap-1 size: 3.91 GiB used: 0 KiB (0.0%) fs: swap dev: /dev/nvme0n1p2 Info: Processes: 174 Uptime: 25m Memory: 3.62 GiB used: 556.6 MiB (15.0%) Init: runit runlevel: 2 Compilers: gcc: 10.2.1 Packages: 1625 Shell: Bash v: 5.1.4 pinxi: 3.3.21-12--
Brian MasinickBrian Masinick
Added the Liquorix kernel to my Acer 5 Aspire instance of antiX 21 runit. Here’s the basic output of the developmental information tool:
pinxi -b System: Host: antixMas Kernel: 5.19.0-6.1-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: 1116 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: 11.57 GiB (9.7%) Info: Processes: 169 Uptime: 1m Memory: 3.62 GiB used: 539.1 MiB (14.5%) Shell: Bash pinxi: 3.3.21-12--
Brian MasinickBrian Masinick
I’m using a Liquorix kernel here again today, and this kernel is regularly updated. Our antiX kernels are very good, and are particularly well suited to aging computers. What Liquorix kernels provide is a versatile kernel well suited to interactive use, and for the gamers (I’m NOT among them), you may find the Liquorix kernel to be particularly useful too. In any case, I’ve found these kernels to be good for many years now.
pinxi -b System: Host: antixMas Kernel: 5.19.0-7.1-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: 1201 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.19 GiB (10.2%) Info: Processes: 169 Uptime: 0m Memory: 3.62 GiB used: 529.7 MiB (14.3%) Shell: Bash pinxi: 3.3.21-12--
Brian MasinickBrian Masinick
My development copy of inxi, pinxi, receives regular updates, so here’s a fairly verbose copy of today’s system information report on my antiX configuration:
pinxi -v4 System: Host: antixMas Kernel: 5.19.0-7.1-liquorix-amd64 arch: x86_64 bits: 64 compiler: gcc v: 10.2.1 Desktop: IceWM v: 2.9.9 Distro: antiX-21-runit_x64-full Grup Yorum 30 October 2021 base: Debian GNU/Linux 11 (bullseye) 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%) volts: 12.2 min: 11.2 model: LGC AP18C8K status: full CPU: Info: dual core model: Intel Core i3-1005G1 bits: 64 type: MT MCP arch: Ice Lake rev: 5 cache: L1: 160 KiB L2: 1024 KiB L3: 4 MiB Speed (MHz): avg: 1179 high: 1201 min/max: 400/1201 boost: enabled cores: 1: 1114 2: 1201 3: 1201 4: 1201 bogomips: 9523 Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx Graphics: Device-1: Intel Iris Plus Graphics G1 vendor: Acer Incorporated ALI driver: i915 v: kernel arch: Gen-11 bus-ID: 00:02.0 Device-2: Quanta HD User Facing type: USB driver: uvcvideo bus-ID: 1-5:4 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 direct render: Yes Network: Device-1: Intel Killer Wi-Fi 6 AX1650i 160MHz Wireless Network Adapter driver: iwlwifi v: kernel bus-ID: 00:14.3 IF: wlan0 state: up mac: 8c:8d:28:33:ec:3a Device-2: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet vendor: Acer Incorporated ALI driver: r8169 v: kernel port: 3000 bus-ID: 01:00.0 IF: eth0 state: down mac: b4:a9:fc:db:69:5e Drives: Local Storage: total: 119.24 GiB used: 12.22 GiB (10.2%) ID-1: /dev/nvme0n1 vendor: Samsung model: MZVLQ128HBHQ-00000 size: 119.24 GiB temp: 15.8 C Partition: ID-1: / size: 28.67 GiB used: 12.22 GiB (42.6%) fs: ext4 dev: /dev/nvme0n1p5 ID-2: swap-1 size: 3.91 GiB used: 0 KiB (0.0%) fs: swap dev: /dev/nvme0n1p2 Info: Processes: 157 Uptime: 5m Memory: 3.62 GiB used: 549.3 MiB (14.8%) Init: runit runlevel: 2 Compilers: gcc: 10.2.1 Packages: 1633 Shell: Bash v: 5.1.4 pinxi: 3.3.21-14--
Brian MasinickBrian Masinick
Woo hoo! I picked up an inexpensive tp-link AC600 high gain wireless dual band USB adapter, and now this adapter is recognized when booting from the previously created image that I used to install antiX-21-runit_x64-full Grup Yorum on my Dell Inspiron 5558 laptop; now I can run it on my Acer Aspire 5 Model A515-55 too!
inxi -b System: Host: antix1 Kernel: 5.10.57-antix.1-amd64-smp arch: x86_64 bits: 64 Desktop: IceWM v: 2.8.0 Distro: antiX-21-runit_x64-full Grup Yorum 30 October 2021 Machine: Type: Laptop System: Acer product: Aspire A515-55 v: V1.12 serial: NA Mobo: IL model: Doc_IL v: V1.12 serial: NA 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: 3014 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 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 Device-3: TP-Link 802.11ac WLAN Adapter type: USB driver: N/A Drives: Local Storage: total: 148.54 GiB used: 4 MiB (0.0%) Info: Processes: 166 Uptime: 5m Memory: 3.62 GiB used: 1.04 GiB (28.6%) Shell: Bash inxi: 3.3.20When I reported this, I did not realize that when I booted the antiX 21 image, by default the 4.9 kernel was coming up. While I could detect the USB and load it, unless I selected a 5.* kernel, in this case the 5.10 kernel, it wouldn’t work with Wifi, with or without the USB dongle antenna, but with the 5.10 image, I didn’t actually need the antenna, as it turns out; it was the 5.10 or later kernel I needed in order for Wifi to work, whereas on the Dell Inspiron 5558, it’s the exact opposite; the 4 series kernels work and the 5.10 kernel experiences some of the same issues that others have reported, though curiously enough, other 5 series kernels work fine on that hardware too.
Either way, for me, I’ve found working antiX kernels for all of my different systems now and I’ve been really happy, because that means I can use antiX on all of my systems where Linux can be installed.
--
Brian Masinick
techore
@masinick, nice. Tell me more about pinxi?
System: Kernel: 5.10.104-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: Laptop System: ASUSTeK product: UX330UAK v: 1.0 serial: <filter> Mobo: ASUSTeK model: UX330UAK v: 1.0 serial: <filter> UEFI: American Megatrends v: UX330UAK.305 date: 05/02/2017 Battery: ID-1: BAT0 charge: 8.4 Wh (21.6%) condition: 38.8/57.1 Wh (68.0%) volts: 11.6 min: 11.6 CPU: Info: dual core Intel Core i5-7200U [MT MCP] speed (MHz): avg: 3100 min/max: 400/3100 Graphics: Device-1: Intel HD Graphics 620 driver: i915 v: kernel Device-2: Realtek USB2.0 HD UVC WebCam type: USB driver: uvcvideo Display: server: X.Org v: 1.20.11 driver: X: loaded: modesetting unloaded: fbdev,vesa gpu: i915 resolution: 1920x1080~60Hz OpenGL: renderer: Mesa Intel HD Graphics 620 (KBL GT2) v: 4.6 Mesa 20.3.5 Network: Device-1: Intel Wireless 8260 driver: iwlwifi Device-2: Intel Bluetooth wireless interface type: USB driver: btusb Drives: Local Storage: total: 238.47 GiB used: 4.45 GiB (1.9%) Info: Processes: 162 Uptime: 43m Memory: 7.66 GiB used: 1.27 GiB (16.6%) Shell: fish inxi: 3.3.19- This reply was modified 8 months, 1 week ago by Brian Masinick.
Brian Masinick
https://smxi.org/docs/inxi.htm is the inxi site. It describes “inxi :: a full featured system information script”.
https://github.com/smxi/inxi – “inxi-perl is the dev branch, the others are rarely if ever used. inxi itself has
the built in feature to be able to update itself from anywhere, including these
branches, which is very useful for development and debugging on various user
systems.”“PACKAGERS: inxi has one and only one ‘release’, and that is the current
commit/version in the master branch (plus pinxi inxi-perl branch, of course, but
those should never be packaged). ”Here is where you can actually obtain pinxi:
——————————————————————————–
DEVELOPMENT BRANCH
——————————————————————————–All active development is now done on the inxi-perl branch (pinxi):
git clone https://github.com/smxi/inxi --branch inxi-perl --single-branchOR direct fast and easy install:
wget -O pinxi https://github.com/smxi/inxi/raw/inxi-perl/pinxiOR easy to remember shortcut (which redirects to github):
wget -O pinxi https://smxi.org/pinxi wget -O pinxi smxi.org/pinxiOnce new features have been debugged, tested, and are reasonably stable, pinxi
is copied to inxi in the master branch.--
Brian MasinickBrian Masinick
By the way, my longtime development friend h2 is the developer of both inxi and pinxi, the development branch of inxi.
He may stop by here from time to time; in fact, if you look through our forum history, I think he explained these things a while ago too.--
Brian Masinickh2
I don’t think I’d put it that way, re my developing both pinxi and inxi, pinxi becomes next inxi, it rolls along that way endlessly. Whenever the features being worked on actively in pinxi are stable and working and have been tested hopefully (though this is often optimistic) enough, pinxi is literally copied over to inxi, pinxi.1 man file is copied to inxi.1 man file, and pinxi.changelog is copied over to inxi.changelog, and then we have a new inxi.
In other words, I don’t develop inxi at all, I only develop pinxi, pinxi.1, and pinxi.changelog, which once stable are copied to the master branch as inxi bits, and committed, but I technically almost never work on inxi itself, unless I’m fixing a typo, but with my new release.pl tool, I actually now almost never touch inxi at all, quite literally it’s not touched, the release.pl does all the updates etc, and then I commit that once it’s passed the release.pl pre-release tests. I used to work on inxi a tiny bit, like copying pinxi to it manually, and maybe editing a typo, but now I don’t do any of that anymore, it’s much easier to release and correct issues, it’s always pinxi > inxi now. So technically I work on pinxi, period, and I release inxi, but don’t work on it, if that makes sense.
Because of the increasing complexity of some features, I recently did a suite of release and pre-release perl tools, which live in inxi-perl/tools/, and also I did and do more releases of the core inxi data which is required to make it work and debug it etc, which now live in inxi-perl/data/, which both are also reflected in inxi-perl/docs/ which is more granular now. pinxi > inxi is getting a lot more complicated to work on, though the code is easier by the year as I do upgrades, but the overall conceptual complexity is getting to be a lot more… daunting… but all the recent tools, data releases, etc, were all designed to make it less daunting and less error prone, those seem to be working roughly as intended.
Barring tiny edits right at release, this is the only update inxi ever sees. Part of this comes from my detesting how git treats branches, and the horror of ‘merging’ branches, so I skip all of that, and literally copy pinxi to inxi, then commit that change to git master branch. This also results in my being always able to in real time test pinxi against inxi to confirm that I didn’t break something. I used this feature a lot during this pinxi cycle since I was working on some bugs and oddities and had to keep comparing pinxi output to inxi 3.3.21 output to make sure I hadn’t broken anything and that the fix had actually fixed the issue, not broken it worse.
I personally honestly do not even understand how people work on git branch based stuff when the changes get really massive, which pinxi changes almost always do, sometimes one single next inxi might change 10-20% of the entire codebase.
pinxi -GCSaz --vs pinxi 3.3.21-14 (2022-09-05) System: Kernel: 5.18.0-15.1-liquorix-amd64 arch: x86_64 bits: 64 compiler: gcc v: 11.3.0 parameters: audit=0 intel_pstate=disable hpet=disable rcupdate.rcu_expedited=1 BOOT_IMAGE=/boot/vmlinuz-5.18.0-15.1-liquorix-amd64 root=UUID=4f6b4acd-fa5c-400e-8b48-364b1f44dd17 ro quiet Desktop: Xfce v: 4.16.0 tk: Gtk v: 3.24.24 info: xfce4-panel wm: xfwm v: 4.16.1 vt: 7 dm: LightDM v: 1.26.0 Distro: Debian GNU/Linux bookworm/sid CPU: Info: model: AMD Ryzen 5 2600 bits: 64 type: MT MCP arch: Zen+ gen: 2 level: v3 note: check built: 2018-21 process: GF 12nm family: 0x17 (23) model-id: 8 stepping: 2 microcode: 0x800820D Topology: cpus: 1x cores: 6 tpc: 2 threads: 12 smt: enabled cache: L1: 576 KiB desc: d-6x32 KiB; i-6x64 KiB L2: 3 MiB desc: 6x512 KiB L3: 16 MiB desc: 2x8 MiB Speed (MHz): avg: 2551 high: 3892 min/max: 1550/3400 boost: enabled scaling: driver: acpi-cpufreq governor: ondemand cores: 1: 1793 2: 3613 3: 2270 4: 2940 5: 1482 6: 1474 7: 3319 8: 3349 9: 3892 10: 2812 11: 2235 12: 1443 bogomips: 81598 Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm Vulnerabilities: Type: itlb_multihit status: Not affected Type: l1tf status: Not affected Type: mds status: Not affected Type: meltdown status: Not affected Type: mmio_stale_data status: Not affected Type: retbleed mitigation: untrained return thunk; SMT vulnerable Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via prctl Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization Type: spectre_v2 mitigation: Retpolines, IBPB: conditional, STIBP: disabled, RSB filling Type: srbds status: Not affected Type: tsx_async_abort status: Not affected Graphics: Device-1: AMD Cedar [Radeon HD 5000/6000/7350/8350 Series] vendor: XFX Pine driver: radeon v: kernel alternate: amdgpu arch: TeraScale-2 code: Evergreen process: TSMC 32-40nm built: 2009-15 pcie: gen: 1 speed: 2.5 GT/s lanes: 16 link-max: gen: 2 speed: 5 GT/s ports: active: DVI-I-1,VGA-1 empty: HDMI-A-1 bus-ID: 0a:00.0 chip-ID: 1002:68f9 class-ID: 0300 temp: 64.0 C Display: x11 server: X.Org v: 1.21.1.3 with: Xwayland v: 22.1.3 compositor: xfwm v: 4.16.1 driver: X: loaded: modesetting dri: r600 gpu: radeon display-ID: :0.0 screens: 1 Screen-1: 0 s-res: 2560x1024 s-dpi: 96 s-size: 677x270mm (26.65x10.63") s-diag: 729mm (28.7") Monitor-1: DVI-I-1 pos: primary,left model: Samsung SyncMaster serial: <filter> built: 2004 res: 1280x1024 hz: 60 dpi: 96 gamma: 1.2 size: 338x270mm (13.31x10.63") diag: 433mm (17") ratio: 5:4 modes: max: 1280x1024 min: 720x400 Monitor-2: VGA-1 pos: right model: Dell 1908FP serial: <filter> built: 2008 res: 1280x1024 hz: 60 dpi: 86 gamma: 1.4 size: 376x301mm (14.8x11.85") diag: 482mm (19") ratio: 5:4 modes: max: 1280x1024 min: 720x400 OpenGL: renderer: AMD CEDAR (DRM 2.50.0 / 5.18.0-15.1-liquorix-amd64 LLVM 14.0.4) v: 3.3 Mesa 22.0.5 compat-v: 3.1 direct render: Yes- This reply was modified 8 months, 1 week ago by h2.
inxi system information script (install info) :: inxi git
Brian Masinick
Thanks for sharing h2!
I had a good feeling that you would clarify and correct any inaccurate information 😃👍
Always good to hear from you and read your words of wisdom!
--
Brian Masinicktechore
@h2, nice box! and thank you, both, for the pixni and ixni information. I understand the relationship between the two now.
ixni is awesome possum.
Brian Masinick
BTW, h2, some of that information that I put in that post earlier was directly copied from the sites cited in what I posted. I *thought* it was the official site; if I’m wrong, then that explains the discrepancies; if it is the correct site though, it’s either out of context or now well out of date; it might be worth checking on it; if it’s someone else’s site, THEY should fix their inaccuracies. As far as the DEFINITIVE source, I definitely know that is YOU, so thank you for your thorough and complete explanation; I knew I could count on you and I appreciate your attention to accuracy and detail.
--
Brian Masinick
- You must be logged in to reply to this topic.
