- This topic has 1,420 replies, 37 voices, and was last updated May 12-4:56 am by Trashthrasher.
-
Posts
-
Brian Masinick
Wednesday, February 15, 2023 – using antiX 22 with the 6.1.11-antix.1-amd64-smp Kernel
pinxi -abc System: Host: brian-antix-hp-14fq1025nr Kernel: 6.1.11-antix.1-amd64-smp arch: x86_64 bits: 64 compiler: gcc v: 10.2.1 parameters: BOOT_IMAGE=/boot/vmlinuz-6.1.11-antix.1-amd64-smp root=UUID=e1d85e10-a42a-4ed5-a98e-c860607e6910 ro quiet selinux=0 Desktop: IceWM v: 3.3.1 vt: 4 dm: slimski v: 1.5.0 Distro: antiX-21-runit_x64-full Grup Yorum 30 October 2021 base: Debian GNU/Linux 11 (bullseye) Machine: Type: Laptop System: HP product: HP Laptop 14-fq1xxx v: N/A serial: <superuser required> Chassis: type: 10 serial: <superuser required> Mobo: HP model: 887C v: 59.11 serial: <superuser required> UEFI: AMI v: F.18 date: 11/26/2021 Battery: ID-1: BAT0 charge: 40.6 Wh (99.8%) condition: 40.7/40.7 Wh (100.0%) volts: 12.8 min: 11.3 model: HP Primary type: Li-ion serial: SerialNumber status: not charging CPU: Info: 6-core AMD Ryzen 5 5500U with Radeon Graphics [MT MCP] arch: Zen 2 speed (MHz): avg: 1457 min/max: 1400/4056 Graphics: Device-1: AMD Lucienne vendor: Hewlett-Packard driver: amdgpu v: kernel arch: GCN-5 code: Vega process: GF 14nm built: 2017-20 pcie: gen: 3 speed: 8 GT/s lanes: 16 link-max: gen: 4 speed: 16 GT/s ports: active: eDP-1 empty: HDMI-A-1 bus-ID: 03:00.0 chip-ID: 1002:164c class-ID: 0300 temp: 40.0 C Device-2: Chicony HP TrueVision HD Camera type: USB driver: uvcvideo bus-ID: 1-3:2 chip-ID: 04f2:b6f1 class-ID: 0e02 serial: 0001 Display: x11 server: X.Org v: 1.20.11 driver: X: loaded: amdgpu unloaded: fbdev,modesetting,vesa dri: radeonsi gpu: amdgpu resolution: 1920x1080~60Hz API: OpenGL v: 4.6 Mesa 20.3.5 renderer: AMD RENOIR (DRM 3.49.0 6.1.11-antix.1-amd64-smp LLVM 11.0.1) direct-render: Yes Network: Device-1: Realtek vendor: Hewlett-Packard driver: rtw89_8852ae v: kernel pcie: gen: 1 speed: 2.5 GT/s lanes: 1 port: f000 bus-ID: 01:00.0 chip-ID: 10ec:a85a class-ID: 0280 Drives: Local Storage: total: 238.47 GiB used: 29.22 GiB (12.3%) Info: Processes: 233 Uptime: 6m wakeups: 74 Memory: 7.11 GiB used: 593.2 MiB (8.2%) Init: runit v: N/A runlevel: 2 tool: service Compilers: gcc: 10.2.1 alt: 10 Packages: pm: dpkg pkgs: 1859 libs: 849 tools: apt,apt-get,nala,synaptic Shell: Bash v: 5.1.4 running-in: roxterm pinxi: 3.3.25-1--
Brian MasinickBrian Masinick
Thursday, February 16, 2023 – using antiX 22 with the Kernel: 6.1.12-x64v3-xanmod1 arch: x86_64.
xanmod1 and Liquorix were, until recently, the only Version 6 kernels I could use. Debian finally added several Version 6 kernels, but last I looked, they were at least a rev behind, so I’ve ignored those. Now that antiX has a couple of Version 6.1 kernels, I do anticipate using them a LOT more often, particularly once they are included in our software builds. I will say, however, that my recent testing has shown xanmod1, Liquorix, and the new antiX kernels to be VERY CLOSE in overall capabilities. The xanmod1 kernels are known for low latency, useful for those interested in “gaming”, and the Liquorix kernels have been around a long time, providing the newest kernels aimed at interactive use. Now that antiX also has Version 6 kernels, I’ll be using them more and more, but I will say this – they’re all very good, it simply depends on what you’re going to do. Also, the antiX 6.1.11 kernel DOES NOT have memory leaks, and neither do these other two kernels; I’ve checked and all three of them are superb at releasing unused memory, but they are large – they’re built that way to provide lots of in memory cache for excellent interactive performance.
inxi -abc System: Host: brian-antix-hp-14fq1025nr Kernel: 6.1.12-x64v3-xanmod1 arch: x86_64 bits: 64 compiler: gcc v: 12.2.0 parameters: BOOT_IMAGE=/boot/vmlinuz-6.1.12-x64v3-xanmod1 root=UUID=e1d85e10-a42a-4ed5-a98e-c860607e6910 ro quiet selinux=0 Desktop: IceWM v: 3.3.1 wm: motif vt: 4 dm: slimski v: 1.5.0 Distro: antiX-21-runit_x64-full Grup Yorum 30 October 2021 base: Debian GNU/Linux 11 (bullseye) Machine: Type: Laptop System: HP product: HP Laptop 14-fq1xxx v: N/A serial: <superuser required> Chassis: type: 10 serial: <superuser required> Mobo: HP model: 887C v: 59.11 serial: <superuser required> UEFI: AMI v: F.18 date: 11/26/2021 Battery: ID-1: BAT0 charge: 40.6 Wh (99.8%) condition: 40.7/40.7 Wh (100.0%) volts: 12.8 min: 11.3 model: HP Primary type: Li-ion serial: SerialNumber status: not charging CPU: Info: 6-core AMD Ryzen 5 5500U with Radeon Graphics [MT MCP] arch: Zen 2 speed (MHz): avg: 1876 min/max: 1400/4056 Graphics: Device-1: AMD Lucienne vendor: Hewlett-Packard driver: amdgpu v: kernel arch: GCN-5 code: Vega process: GF 14nm built: 2017-20 pcie: gen: 3 speed: 8 GT/s lanes: 16 link-max: gen: 4 speed: 16 GT/s ports: active: eDP-1 empty: HDMI-A-1 bus-ID: 03:00.0 chip-ID: 1002:164c class-ID: 0300 temp: 47.0 C Device-2: Chicony HP TrueVision HD Camera type: USB driver: uvcvideo bus-ID: 1-3:2 chip-ID: 04f2:b6f1 class-ID: 0e02 serial: 0001 Display: x11 server: X.Org v: 1.20.11 driver: X: loaded: amdgpu unloaded: fbdev,modesetting,vesa dri: radeonsi gpu: amdgpu resolution: 1920x1080~60Hz API: OpenGL v: 4.6 Mesa 20.3.5 renderer: AMD RENOIR (DRM 3.49.0 6.1.12-x64v3-xanmod1 LLVM 11.0.1) direct-render: Yes Network: Device-1: Realtek vendor: Hewlett-Packard driver: rtw89_8852ae v: kernel pcie: gen: 1 speed: 2.5 GT/s lanes: 1 port: f000 bus-ID: 01:00.0 chip-ID: 10ec:a85a class-ID: 0280 Drives: Local Storage: total: 238.47 GiB used: 29.41 GiB (12.3%) Info: Processes: 284 Uptime: 2h 46m wakeups: 11183 Memory: 7.11 GiB used: 1.43 GiB (20.1%) Init: runit v: N/A runlevel: 2 tool: service Compilers: gcc: 10.2.1 alt: 10 Packages: pm: dpkg pkgs: 1865 libs: 852 tools: apt,apt-get,nala,synaptic Shell: Bash v: 5.1.4 running-in: roxterm inxi: 3.3.25--
Brian MasinickBrian Masinick
sudo ps_mem.py Private + Shared = RAM used Program 92.0 KiB + 12.5 KiB = 104.5 KiB runit 100.0 KiB + 16.5 KiB = 116.5 KiB runsvdir 128.0 KiB + 17.5 KiB = 145.5 KiB svlogd 192.0 KiB + 25.5 KiB = 217.5 KiB gpm 208.0 KiB + 24.5 KiB = 232.5 KiB atd 260.0 KiB + 48.5 KiB = 308.5 KiB rtkit-daemon 288.0 KiB + 28.5 KiB = 316.5 KiB acpid 360.0 KiB + 101.5 KiB = 461.5 KiB icewm-session 396.0 KiB + 81.5 KiB = 477.5 KiB dbus-launch 396.0 KiB + 137.5 KiB = 533.5 KiB udevil 480.0 KiB + 199.5 KiB = 679.5 KiB rpcbind 544.0 KiB + 292.0 KiB = 836.0 KiB getty (4) 424.0 KiB + 428.0 KiB = 852.0 KiB avahi-daemon (2) 792.0 KiB + 169.5 KiB = 961.5 KiB gconfd-2 620.0 KiB + 371.5 KiB = 991.5 KiB devmon 768.0 KiB + 264.5 KiB = 1.0 MiB saned 736.0 KiB + 356.5 KiB = 1.1 MiB dconf-service 832.0 KiB + 452.5 KiB = 1.3 MiB desktop-session 836.0 KiB + 537.5 KiB = 1.3 MiB at-spi-bus-launcher 904.0 KiB + 473.5 KiB = 1.3 MiB at-spi2-registryd 1.7 MiB + 72.5 KiB = 1.8 MiB elogind 1.4 MiB + 480.5 KiB = 1.8 MiB dbus-daemon (3) 1.4 MiB + 420.5 KiB = 1.8 MiB sudo 1.6 MiB + 240.5 KiB = 1.9 MiB udevd 1.5 MiB + 397.5 KiB = 1.9 MiB ntpd 1.6 MiB + 395.5 KiB = 2.0 MiB runsv (25) 1.9 MiB + 235.5 KiB = 2.1 MiB bluetoothd 2.3 MiB + 44.5 KiB = 2.3 MiB rsyslogd 1.9 MiB + 502.5 KiB = 2.4 MiB bash 3.2 MiB + 24.5 KiB = 3.2 MiB haveged 2.6 MiB + 744.5 KiB = 3.3 MiB dhclient 3.6 MiB + 208.5 KiB = 3.8 MiB connmand 3.6 MiB + 862.5 KiB = 4.4 MiB conky 4.4 MiB + 789.5 KiB = 5.2 MiB slimski 4.5 MiB + 770.5 KiB = 5.3 MiB wpa_supplicant 5.7 MiB + 1.4 MiB = 7.1 MiB icewm 4.0 MiB + 3.0 MiB = 7.1 MiB volumeicon 11.0 MiB + 4.2 MiB = 15.2 MiB roxterm 41.1 MiB + 22.1 MiB = 63.2 MiB Xorg 783.5 MiB + 124.7 MiB = 908.3 MiB firefox-bin (13) --------------------------------- 1.0 GiB =================================--
Brian MasinickBrian Masinick
Closing a second tab on my browser, look how much memory usage IMMEDIATELY decreases:
sudo ps_mem.py Private + Shared = RAM used Program 92.0 KiB + 12.5 KiB = 104.5 KiB runit 100.0 KiB + 17.5 KiB = 117.5 KiB runsvdir 128.0 KiB + 17.5 KiB = 145.5 KiB svlogd 192.0 KiB + 25.5 KiB = 217.5 KiB gpm 208.0 KiB + 24.5 KiB = 232.5 KiB atd 260.0 KiB + 50.5 KiB = 310.5 KiB rtkit-daemon 292.0 KiB + 27.5 KiB = 319.5 KiB acpid 360.0 KiB + 111.5 KiB = 471.5 KiB icewm-session 396.0 KiB + 83.5 KiB = 479.5 KiB dbus-launch 396.0 KiB + 143.5 KiB = 539.5 KiB udevil 480.0 KiB + 200.5 KiB = 680.5 KiB rpcbind 536.0 KiB + 294.0 KiB = 830.0 KiB getty (4) 424.0 KiB + 431.0 KiB = 855.0 KiB avahi-daemon (2) 792.0 KiB + 182.5 KiB = 974.5 KiB gconfd-2 620.0 KiB + 373.5 KiB = 993.5 KiB devmon 768.0 KiB + 295.5 KiB = 1.0 MiB saned 736.0 KiB + 363.5 KiB = 1.1 MiB dconf-service 832.0 KiB + 455.5 KiB = 1.3 MiB desktop-session 832.0 KiB + 550.5 KiB = 1.4 MiB at-spi-bus-launcher 904.0 KiB + 487.5 KiB = 1.4 MiB at-spi2-registryd 1.7 MiB + 73.5 KiB = 1.8 MiB elogind 1.4 MiB + 491.5 KiB = 1.8 MiB dbus-daemon (3) 1.6 MiB + 242.5 KiB = 1.9 MiB udevd 1.5 MiB + 440.5 KiB = 1.9 MiB sudo 1.5 MiB + 400.5 KiB = 1.9 MiB ntpd 1.6 MiB + 402.5 KiB = 2.0 MiB runsv (25) 1.9 MiB + 245.5 KiB = 2.1 MiB bluetoothd 2.3 MiB + 47.5 KiB = 2.3 MiB rsyslogd 1.9 MiB + 505.5 KiB = 2.4 MiB bash 3.2 MiB + 25.5 KiB = 3.2 MiB haveged 2.6 MiB + 745.5 KiB = 3.3 MiB dhclient 3.6 MiB + 213.5 KiB = 3.8 MiB connmand 3.6 MiB + 917.5 KiB = 4.5 MiB conky 4.4 MiB + 838.5 KiB = 5.2 MiB slimski 4.5 MiB + 774.5 KiB = 5.3 MiB wpa_supplicant 4.0 MiB + 3.1 MiB = 7.1 MiB volumeicon 5.7 MiB + 1.5 MiB = 7.2 MiB icewm 11.0 MiB + 4.4 MiB = 15.4 MiB roxterm 41.1 MiB + 22.1 MiB = 63.2 MiB Xorg 657.5 MiB + 116.9 MiB = 774.3 MiB firefox-bin (11) --------------------------------- 923.9 MiB =================================--
Brian MasinickBrian Masinick
Closed the browser briefly, and look how nicely the system trimmed down the memory usage—
sudo ps_mem.py Private + Shared = RAM used Program 92.0 KiB + 15.5 KiB = 107.5 KiB runit 100.0 KiB + 20.5 KiB = 120.5 KiB runsvdir 128.0 KiB + 20.5 KiB = 148.5 KiB svlogd 192.0 KiB + 31.5 KiB = 223.5 KiB gpm 208.0 KiB + 28.5 KiB = 236.5 KiB atd 292.0 KiB + 32.5 KiB = 324.5 KiB acpid 260.0 KiB + 67.5 KiB = 327.5 KiB rtkit-daemon 396.0 KiB + 116.5 KiB = 512.5 KiB dbus-launch 396.0 KiB + 210.5 KiB = 606.5 KiB udevil 364.0 KiB + 262.5 KiB = 626.5 KiB icewm-session 480.0 KiB + 210.5 KiB = 690.5 KiB rpcbind 536.0 KiB + 326.0 KiB = 862.0 KiB getty (4) 424.0 KiB + 456.0 KiB = 880.0 KiB avahi-daemon (2) 620.0 KiB + 399.5 KiB = 1.0 MiB devmon 792.0 KiB + 373.5 KiB = 1.1 MiB gconfd-2 768.0 KiB + 509.5 KiB = 1.2 MiB saned 736.0 KiB + 564.5 KiB = 1.3 MiB dconf-service 832.0 KiB + 480.5 KiB = 1.3 MiB desktop-session 1.0 MiB + 719.5 KiB = 1.7 MiB at-spi-bus-launcher 1.0 MiB + 738.5 KiB = 1.8 MiB at-spi2-registryd 1.7 MiB + 85.5 KiB = 1.8 MiB elogind 1.6 MiB + 261.5 KiB = 1.9 MiB udevd 1.4 MiB + 572.5 KiB = 1.9 MiB dbus-daemon (3) 1.5 MiB + 500.5 KiB = 2.0 MiB sudo 1.5 MiB + 466.5 KiB = 2.0 MiB ntpd 1.6 MiB + 469.5 KiB = 2.1 MiB runsv (25) 1.9 MiB + 460.5 KiB = 2.3 MiB bluetoothd 2.3 MiB + 71.5 KiB = 2.4 MiB rsyslogd 1.9 MiB + 525.5 KiB = 2.4 MiB bash 3.2 MiB + 30.5 KiB = 3.2 MiB haveged 2.6 MiB + 754.5 KiB = 3.3 MiB dhclient 3.6 MiB + 278.5 KiB = 3.8 MiB connmand 3.6 MiB + 1.2 MiB = 4.8 MiB conky 4.6 MiB + 809.5 KiB = 5.3 MiB wpa_supplicant 4.5 MiB + 1.3 MiB = 5.8 MiB slimski 5.9 MiB + 2.7 MiB = 8.6 MiB icewm 4.4 MiB + 4.2 MiB = 8.6 MiB volumeicon 11.5 MiB + 6.0 MiB = 17.4 MiB roxterm 84.2 MiB + 1.4 MiB = 85.7 MiB Xorg --------------------------------- 180.3 MiB =================================--
Brian MasinickBrian Masinick
Today, those results are with the xanmod1 kernel. I did the exact same test recently with our new 6.1.11 antiX kernel and got very similar results, so both of them are very good; the only thing that xanmod1 *might* be more specifically tuned for (unless our kernel is set up in a similar fashion) is optimized low latency; otherwise they’re very similar for most routine interactive workloads. I’m not a gamer, I only found xanmod1 because I wanted to get an early start with Version 6 kernel testing and xanmod1 got there before Liquorix by a day or two; now it’s nice to have a choice – I have three very good V6.1 kernel options I can use with my HP-14 and antiX – our own new kernel, xanmod1, and Liquorix.
On other distributions, several of them are now up to 6.1.11 or 6.1.12 – I know that Endeavour OS, for example, has a brand new kernel. That’s a good distribution; it DOESN’T operate as a super light, lean distribution, but it’s a cutting edge distribution that, for me anyway, “tames” the behavior of Arch Linux a bit, so it’s been the first RELIABLE Arch derivative I’ve been happy with. Manjaro looked good for a while, until it wasn’t; it messed up the installation so badly that it was no longer usable. Arch, when you’re using stable code, is usually solid. When you use “AUR”, that’s their way to get the absolute newest stuff. What Endeavour OS has provided to me has been a safety bridge; 1) I haven’t had to put much AUR software in place, but when I do, it’s been pretty safe stuff like the latest browsers. If those don’t work, I can easily ignore them, update them with a fix, or remove them. When critically important packages fail, however, that’s a deal breaker.
As we know with our own distribution, there are VERY FEW cases where we have “deal breakers” in our core software. Most of our “deal breakers” are that a system is eventually “too old” with certain versions or “too new” – like my HP-14, which I had to manually hack to bring in the appropriate wireless firmware, newer kernel and all modules associated with those two things, a non trivial exercise, but I was able to benefit from the MX Linux “AHS” (Advanced Hardware Support) build to snag what I needed, and since I put multiple distributions on several of my computers, I’m able to do such things and that’s how I currently have an HP-14 laptop working here; otherwise I’d be waiting for an upcoming version of antiX; now I can work WITH our current versions here and test the upcoming release on my Dell until we get newer (2021) systems supported. Anyway, working with many distributions helps me figure some of this stuff out; that, and my “geek mind” keeps me working with and checking out various different systems.
--
Brian Masinickh2
Just to double check, is there any way to get the runit version, like runit –version, -v, -version, etc?
My info says no, but since antix is using these in production maybe your info is more up to date. If so, what is the command, and what is the output?
I was quite pleased in recent test to discover that my dinit version stuff works, which I can never be sure of with these non systemd init systems.
inxi system information script (install info) :: inxi git
Brian Masinick
I don’t know how to obtain the details, but if there IS a way, perhaps something in the site documentation will spell it out.
http://smarden.org/runit/ is the site where runit is documented; hopefully that will help; if someone knows more, please let h2 know; thanks!--
Brian MasinickBrian Masinick
According to http://smarden.org/runit/upgrade.html 2.1.2 is the current release.
--
Brian MasinickBrian Masinick
Note inxi sadly can’t look up on github or forums what a version number of an installed bit of software is, looks like in this case runit left out –version type option, which means I didn’t miss anything when researching it in the past. Most of these you can deduce by reading their online man page, with one or two exceptions, most notably, the s6 author, who seems to feel such things are not required, which is weird.
I’ve always been surprised a bit why projects would forget/neglect/refuse to add a simple version switch, since it helps in debugging to ask users what version they are running. Seems like a fairly silly way to try to save a few lines of code. Even sysvinit never had that, inxi has to use strings to try to get it from the binary, which works on some distros, not on others. But that’s not a real solution.
Just seeing if I had missed anything. Note that in particular with init systems or tools, it’s very risky to query for a –version type option that may not exist because some init systems willl interpret that as a start command, or other things like that, so you can never add a test hoping it will be there in the future, or if it did not have it then added it later. But I also suspect that in the case of init systems, and sometimes window managers, if it’s not built to accept any command line options, the results often are not good if you try using one.
But still to me odd, just seems like a barrier against getting good valid issues etc, but it may be in some cases that the thing is simply absolutely not interactive in any way, so there is no way to make it ‘listen’ for a command line option, I suspect that’s the case with some init systems. Still seems like an odd oversight to me.
Note that I try to make the inxi init stuff as complete as possible, with the minimal objective being to in that small way supporting non systemd init systems, it’s actually surprising how many are being used now, not large scale, but it’s significant.
- This reply was modified 2 months, 3 weeks ago by h2.
- This reply was modified 2 months, 3 weeks ago by h2.
inxi system information script (install info) :: inxi git
Brian Masinick
Runit is a very efficient init system.
I’ve found it to be very solid but I can also tell you that it took the team members a while to get the tools for management of runit in good shape.While I have never had a stability issue with runit, until the team got the right tools in place to manage the runit services, that aspect was challenging. The way antiX has it set up now is as good, in fact, better (for me) than anyone else’s implementation that I found and tried. That doesn’t mean that the others are lacking. I suspect by now they are also improved. With the improvements runit is much better than systemd. That method and runit both improve parallel task management over sysvinit but systemd puts way too many other features into what originally was ONLY an init system – the huge argument between the alternative init systems.
All that said I’ve still seen very good distributions with each approach but I do prefer runit for the classic one feature one tool, like the much smaller systems of old and that’s a major reason why antiX is able to work across a pretty wide age range of equipment.
Nevertheless I still believe in choice and people are free to choose a lean approach, a feature rich approach, a user friendly approach and even a proprietary approach. I happen to appreciate lean, efficient approaches myself and yet I defend the right of each person to choose for themselves what best suits their own needs.
--
Brian MasinickBrian Masinick
Today is Friday, February 17, 2023. Here is what I am running early this morning –
inxi -bc System: Host: antix23 Kernel: 6.1.10-antix.1-amd64-smp arch: x86_64 bits: 64 Desktop: IceWM v: 3.3.1 Distro: antiX-23-runit_x64-full Grup Yorum 3 February 2023 Machine: Type: Laptop System: Dell product: Inspiron 5558 v: N/A serial: <superuser required> Mobo: Dell model: 086DKN v: A00 serial: <superuser required> UEFI: Dell v: A18 date: 12/30/2019 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: 721 min/max: 500/3000 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: server: X.Org v: 1.21.1.7 driver: X: loaded: modesetting unloaded: fbdev,vesa dri: iris gpu: i915 resolution: 1366x768~60Hz API: OpenGL v: 4.6 Mesa 22.3.3 renderer: Mesa Intel HD Graphics 5500 (BDW GT2) 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: 504.44 GiB used: 11.91 GiB (2.4%) Info: Processes: 181 Uptime: 34m Memory: 7.69 GiB used: 1.62 GiB (21.0%) Shell: Bash inxi: 3.3.25--
Brian MasinickBrian Masinick
As you can see above, I have now been successful installing antiX kernel 6.1.10 on my Alpha 1 testing instance of antiX 23.
--
Brian MasinickBrian Masinick
Back on my HP-14 with the antiX 6.1.11 kernel –
pinxi -bc System: Host: brian-antix-hp-14fq1025nr Kernel: 6.1.11-antix.1-amd64-smp arch: x86_64 bits: 64 Desktop: IceWM v: 3.3.1 Distro: antiX-21-runit_x64-full Grup Yorum 30 October 2021 Machine: Type: Laptop System: HP product: HP Laptop 14-fq1xxx v: N/A serial: <superuser required> Mobo: HP model: 887C v: 59.11 serial: <superuser required> UEFI: AMI v: F.18 date: 11/26/2021 Battery: ID-1: BAT0 charge: 40.6 Wh (99.8%) condition: 40.7/40.7 Wh (100.0%) CPU: Info: 6-core AMD Ryzen 5 5500U with Radeon Graphics [MT MCP] speed (MHz): avg: 1516 min/max: 1400/4056 Graphics: Device-1: AMD Lucienne driver: amdgpu v: kernel Device-2: Chicony HP TrueVision HD Camera type: USB driver: uvcvideo Display: x11 server: X.Org v: 1.20.11 driver: X: loaded: amdgpu unloaded: fbdev,modesetting,vesa dri: radeonsi gpu: amdgpu resolution: 1920x1080~60Hz API: OpenGL v: 4.6 Mesa 20.3.5 renderer: AMD RENOIR (DRM 3.49.0 6.1.11-antix.1-amd64-smp LLVM 11.0.1) Network: Device-1: Realtek driver: rtw89_8852ae Drives: Local Storage: total: 238.47 GiB used: 29.1 GiB (12.2%) Info: Processes: 271 Uptime: 2m Memory: 7.11 GiB used: 620.2 MiB (8.5%) Shell: Bash pinxi: 3.3.25-2--
Brian Masinick
- You must be logged in to reply to this topic.
