Fosstodon

0 posts0 participants0 posts today

smxiGot a good <a href="https://fosstodon.org/tags/inxi" class="mention hashtag" rel="tag">#inxi</a> <a href="https://fosstodon.org/tags/codeberg" class="mention hashtag" rel="tag">#codeberg</a> issue report. Graphics <a href="https://fosstodon.org/tags/Vulkan" class="mention hashtag" rel="tag">#Vulkan</a> API item failed to show driver. Turns out that somewhere between vulkaninfo v. 1.3.255 and 1.3.296 they dropped the device driver summary data block. It was always also in a much larger and longer block but I'd never trusted the block name to be consistent. I still don't but there's no choice.This is fixed in <a href="https://fosstodon.org/tags/pinxi" class="mention hashtag" rel="tag">#pinxi</a> but sadly just missed the 3.3.37 release by a few days. Oh well. A <a href="https://fosstodon.org/tags/Mint" class="mention hashtag" rel="tag">#Mint</a> user reported it after seeing driver: N/A always.

smxiChurning through an unexpectedly complicated series of updates in <a href="https://fosstodon.org/tags/pinxi" class="mention hashtag" rel="tag">#pinxi</a> next <a href="https://fosstodon.org/tags/inxi" class="mention hashtag" rel="tag">#inxi</a>Got the gpu monitor scaling handled which required fixing xrandr and wayland tool parsing and logic. False assumptions led to errors in output.--force options were glitchy and inconsistently used and documented. Cleaning that up exposed more glitches, like --no-man not working in inxi due to opaque hash names.It's surprising how fixing docs, help, and man exposes bugs in logic. Still polishing that up.

smxiJust released new <a href="https://fosstodon.org/tags/pinxi" class="mention hashtag" rel="tag">#pinxi</a> (next <a href="https://fosstodon.org/tags/inxi" class="mention hashtag" rel="tag">#inxi</a> ) has first draft of working monitor scaling support. The higher physical screen resolutions get, the more scaling is used. <a href="https://fosstodon.org/tags/mrmazda" class="mention hashtag" rel="tag">#mrmazda</a> had off and on mentioned this as nice to have feature.Not easy to figure out data sources but seems to work with <a href="https://fosstodon.org/tags/xrandr" class="mention hashtag" rel="tag">#xrandr</a> and wayland-info now.I realized I could do scaling on my <a href="https://fosstodon.org/tags/xfce" class="mention hashtag" rel="tag">#xfce</a> with <a href="https://fosstodon.org/tags/x11" class="mention hashtag" rel="tag">#x11</a> which made dev a lot easier. Plus a good data file of <a href="https://fosstodon.org/tags/wayland" class="mention hashtag" rel="tag">#wayland</a> scaled 3 monitor setup. Updated graphics docs with new res section.

smxiFrom a simple issue (#312) on <a href="https://fosstodon.org/tags/codeberg" class="mention hashtag" rel="tag">#codeberg</a> <a href="https://fosstodon.org/tags/pinxi" class="mention hashtag" rel="tag">#pinxi</a> (next <a href="https://fosstodon.org/tags/inxi" class="mention hashtag" rel="tag">#inxi</a>) finally dumps the legacy -F/--full option names in favor of much more accurate and easier to explain -e/--expanded. Easier because -F hasn't been full output for over 10 years, and -F now actually expands -b/--basic, so noting that -e expands basic is a lot more logical than explaining that --full is not actually full at all, not even close. -F now listed as deprecated to avoid confusion in help/man. Redid -v too, all consistent now. 1/

smxiToday was a reminder of how useful documentation is, for help, man page, and standalone docs . <a href="https://fosstodon.org/tags/pinxi" class="mention hashtag" rel="tag">#pinxi</a> (next <a href="https://fosstodon.org/tags/inxi" class="mention hashtag" rel="tag">#inxi</a>) had a lot of changes to in particular CPU logic. Editing man and options for those changes forces me to make sure I have it all right. The thing with docs is, to write them means you have to be able to put into words what the code is doing, where changes are, how new features come to be, aka, UNDERSTAND. The longer I program, the more I realize the value of having to do this.

smxiI'm going to call the <a href="https://fosstodon.org/tags/pinxi" class="mention hashtag" rel="tag">#pinxi</a> (next <a href="https://fosstodon.org/tags/inxi" class="mention hashtag" rel="tag">#inxi</a> ) CPU die/cluster/core counter refactor good. Nobody has found a failure case, but then again, no new complex topologies have appeared.The issue with GPU class IDs being translated to usable data I've given up on, unlike the kernel, FreeDesktop has bad docs as a rule, so unless someone can find clear docs about 302/380 classes that are nonambiguous, re Intel, AMD, etc use, there's no way to give correct info beyond the current ID active. Not static :(

smxiLast testing of <a href="https://fosstodon.org/tags/pinxi" class="mention hashtag" rel="tag">#pinxi</a> (next <a href="https://fosstodon.org/tags/inxi" class="mention hashtag" rel="tag">#inxi</a> ) die cluster core counter core rewrite. Pardon the pun. I can't stop myself. Fixes probably both <a href="https://fosstodon.org/tags/codeberg" class="mention hashtag" rel="tag">#codeberg</a> wrong core count issues. 307 was RISCV 2 cluster 8 core reporting as 4 core MT. This fix is a true fix, not a hack. Being tested by <a href="https://fosstodon.org/tags/slackware" class="mention hashtag" rel="tag">#slackware</a> forums now. Looks good.Also grabbed new <a href="https://fosstodon.org/tags/pop_os" class="mention hashtag" rel="tag">#pop_os</a> 24.04 <a href="https://fosstodon.org/tags/cosmic" class="mention hashtag" rel="tag">#cosmic</a> w/ <a href="https://fosstodon.org/tags/iced" class="mention hashtag" rel="tag">#iced</a> toolkit alpha iso. Hoping to add cosmic and ice tk support as well.The longest period without Issues or dev work in years in this release.

smxiI've been gathering data for the Chinese <a href="https://fosstodon.org/tags/Loongson" class="mention hashtag" rel="tag">#Loongson</a> <a href="https://fosstodon.org/tags/MIPS" class="mention hashtag" rel="tag">#MIPS</a> CPU and GPUs, almost no data on the GPUs for the GPU arch tables (need more product IDs for matches), but found a fairly complete listing of Loongson CPUs on <a href="https://en.wikichip.org/wiki/loongson/godson_2/2h" target="_blank" rel="nofollow noopener noreferrer" translate="no">https://en.wikichip.org/wiki/loongson/godson_2/2h</a> then found a collection of sample cpuinfo output files, which was enough to create a rough first CPU arch support in <a href="https://fosstodon.org/tags/pinxi" class="mention hashtag" rel="tag">#pinxi</a> (next <a href="https://fosstodon.org/tags/inxi" class="mention hashtag" rel="tag">#inxi</a>). Just debugged last bits, seems to be working. Chinese built <a href="https://fosstodon.org/tags/Deepin" class="mention hashtag" rel="tag">#Deepin</a> (<a href="https://fosstodon.org/tags/Debian" class="mention hashtag" rel="tag">#Debian</a> derived) supports <a href="https://fosstodon.org/tags/LoongArch" class="mention hashtag" rel="tag">#LoongArch</a>.

smxiNext <a href="https://fosstodon.org/tags/inxi" class="mention hashtag" rel="tag">#inxi</a> is shaping up well, all running in <a href="https://fosstodon.org/tags/pinxi" class="mention hashtag" rel="tag">#pinxi</a> now. Came across an ancient distro I'd never heard of, <a href="https://fosstodon.org/tags/TDSDE" class="mention hashtag" rel="tag">#TDSDE</a>, which apparently preceded Gentoo by a few months. Poor docs, unreliable source builds, but got everything inxi cares about working, and found some weak spots. These corner case distros often expose weak assumptions. Also locked down <a href="https://fosstodon.org/tags/rpm" class="mention hashtag" rel="tag">#rpm</a> packages, <a href="https://fosstodon.org/tags/urpm" class="mention hashtag" rel="tag">#urpm</a> <a href="https://fosstodon.org/tags/eopkg" class="mention hashtag" rel="tag">#eopkg</a> <a href="https://fosstodon.org/tags/pisi" class="mention hashtag" rel="tag">#pisi</a> repo reports, which were not great, or not working. Took a while to get enough fixes to warrant a new release.

smxiFound issues in <a href="https://fosstodon.org/tags/inxi" class="mention hashtag" rel="tag">#inxi</a> repo report for some software sorced repo lists.: <a href="https://fosstodon.org/tags/mageia" class="mention hashtag" rel="tag">#mageia</a>'s <a href="https://fosstodon.org/tags/urpmq" class="mention hashtag" rel="tag">#urpmq</a>, <a href="https://fosstodon.org/tags/pisi" class="mention hashtag" rel="tag">#pisi</a>, <a href="https://fosstodon.org/tags/solus" class="mention hashtag" rel="tag">#solus</a> <a href="https://fosstodon.org/tags/eopkg" class="mention hashtag" rel="tag">#eopkg</a>. These all are roughly similar and all had same report glitch of showing one repo data source per output line instead of source then all repos. The output was also weird. Corrected in <a href="https://fosstodon.org/tags/pinxi" class="mention hashtag" rel="tag">#pinxi</a>. Thanks <a href="https://fosstodon.org/tags/mrmazda" class="mention hashtag" rel="tag">#mrmazda</a> for noticing.Then noticed the <a href="https://fosstodon.org/tags/rpm" class="mention hashtag" rel="tag">#rpm</a> package count failed for mageia. Turns out they are using different version of rpm, missing some options so no results. Will add workaround.

smxiTo release next <a href="https://fosstodon.org/tags/inxi" class="mention hashtag" rel="tag">#inxi</a> now, or not to release and wait for more fixes/issues etc to show up? Always a tough call when there are not a huge amount of fixes, but there are real fixes that impact some people. Right now it's a little light for a new release for my taste, but it's been about 6 weeks, and the bugs/fixes I got were real issues, and should probably move from <a href="https://fosstodon.org/tags/pinxi" class="mention hashtag" rel="tag">#pinxi</a> to inxi.This makes 3.3.35, like 3.3.34, mostly corner case fixes and updates. Which suggests... stability?!

smxiAdded initial support in <a href="https://fosstodon.org/tags/pinxi" class="mention hashtag" rel="tag">#pinxi</a> (next <a href="https://fosstodon.org/tags/inxi" class="mention hashtag" rel="tag">#inxi</a>) for Loongson GPUs, but I have almost no data, so it won't be very meaningful. More important is to add in support on backend tools/gpu_raw.pl and gpu_ids.pl, which is where the GPU arch data for inxi gets generated. Support for Loongson CPUs is totally lacking, I have no data, no cpuid data, nothing, though I found a good source for at least some of the features, process nodes, etc, but no way to match to actual CPUs. And so it goes.

smxiMeanwhile, on the <a href="https://fosstodon.org/tags/inxi" class="mention hashtag" rel="tag">#inxi</a> / <a href="https://fosstodon.org/tags/pinxi" class="mention hashtag" rel="tag">#pinxi</a> front, all remains peaceful. Issues reported are resolved. It's lingering in that odd space where not quite enough updates to warrant a new release, so waiting for more to pop up.I'm calling the long refactor roughly completed with 3.3.33 a win, I'm not hitting code in general that makes me wince, hides issues, or makes logic hard to understand. This was the goal, so looks like a win.I get slightly nervous when nothing shows up, but that's old habits.

smxiA another day in the life for <a href="https://fosstodon.org/tags/inxi" class="mention hashtag" rel="tag">#inxi</a>: Issue 303 on <a href="https://social.anoxinon.de/@Codeberg" class="u-url mention">@Codeberg</a> noted <a href="https://fosstodon.org/tags/mesa" class="mention hashtag" rel="tag">#mesa</a> version in <a href="https://fosstodon.org/tags/OpenGL" class="mention hashtag" rel="tag">#OpenGL</a> was failing on one user's output.With some good sleuthing (not by me, gfxstrand the OP figured it out), turns out that when mesa is built from git, it added an extra string to end of version number string, which then broke the regex.While technically working now in <a href="https://fosstodon.org/tags/pinxi" class="mention hashtag" rel="tag">#pinxi</a>, I will probably make this pattern less picky in case other weird variants crop up.Another good cb issue. Not missing <a href="https://fosstodon.org/tags/github" class="mention hashtag" rel="tag">#github</a>.

smxiDue to an almost overwhelming popular demand (ok ok, a guy asked when I'd release), I grit my teeth, did the last horrifically tedious manual matching tables data updates last night in <a href="https://fosstodon.org/tags/pinxi" class="mention hashtag" rel="tag">#pinxi</a> (next <a href="https://fosstodon.org/tags/inxi" class="mention hashtag" rel="tag">#inxi</a>), which always means release is going to be within a day or two. So this nice collection of corner case fixes will probably go out the door today.I'm calling it: <a href="https://social.anoxinon.de/@Codeberg" class="u-url mention">@Codeberg</a> is working _exactly_ the way I hoped it would. Signal to noise ratio in issues radically higher now than on github.

smxiFixes in <a href="https://fosstodon.org/tags/pinxi" class="mention hashtag" rel="tag">#pinxi</a>, con'd * A big one in <a href="https://fosstodon.org/tags/inxi" class="mention hashtag" rel="tag">#inxi</a>, only didn't show up I think because most distros ship <a href="https://fosstodon.org/tags/Xwayland" class="mention hashtag" rel="tag">#Xwayland</a>, <a href="https://fosstodon.org/tags/Wayland" class="mention hashtag" rel="tag">#Wayland</a> ID always failed without Xwayland because it depended on $DISPLAY, which refers to <a href="https://fosstodon.org/tags/X" class="mention hashtag" rel="tag">#X</a>.org display ID, NOT wayland's. $WAYLAND_DISPLAY added, plus some other fallbacks.In a sense, this failure was the largest, but I only found it because I installed <a href="https://fosstodon.org/tags/sway" class="mention hashtag" rel="tag">#sway</a> and deliberately left off Xwayland to see what I'd really need to install to get stuff running.2/

smxi<a href="https://fosstodon.org/tags/inxi" class="mention hashtag" rel="tag">#inxi</a> update: all in <a href="https://fosstodon.org/tags/pinxi" class="mention hashtag" rel="tag">#pinxi</a> now. Nothing very exciting: * <a href="https://fosstodon.org/tags/FreeBSD" class="mention hashtag" rel="tag">#FreeBSD</a> changes exposed several block device failures, all revolving around not handling /dev/gpt/[device] syntax. Some of these failures are quite obvious, some not as much. Not a big userbase, but it was a good set of bug/issue reports, which is very unusual for the BSDs. * Adding in some more matching data, gpu vendor IDs, hyprlock, nova <a href="https://fosstodon.org/tags/rust" class="mention hashtag" rel="tag">#rust</a> <a href="https://fosstodon.org/tags/linux" class="mention hashtag" rel="tag">#linux</a> <a href="https://fosstodon.org/tags/nvidia" class="mention hashtag" rel="tag">#nvidia</a> display driver project.1/

smxi<a href="https://social.anoxinon.de/@Codeberg" class="u-url mention">@Codeberg</a> so it was with a sigh of relief that I switched all my <a href="https://fosstodon.org/tags/github" class="mention hashtag" rel="tag">#github</a> repos to Archived read only status, which has the benefit of also turning off all future pull requests, which you can't disable on gh otherwise. Soimetime in the future I'll start repo by repo removing all the code, and just leaving the README.txt as pointer to the codeberg repo.This already happened for the inxi-perl branch (<a href="https://fosstodon.org/tags/pinxi" class="mention hashtag" rel="tag">#pinxi</a>), docs, tarballs.So for all practical purposes this frees me from gh and its users.

smxiThere's going to be a quick new <a href="https://fosstodon.org/tags/inxi" class="mention hashtag" rel="tag">#inxi</a> 3.3.33 release next few days. Currently all running fine in <a href="https://fosstodon.org/tags/pinxi" class="mention hashtag" rel="tag">#pinxi</a>. Just need to check man page and docs. New feature -na will show network services/daemons running in advanced network report. Also a long standing feature request by mrmazda for better error handling of pointless option use. Added all network services I could find along with documenting each as I added them. Rushing release due to real bug found and <a href="https://fosstodon.org/tags/Ubuntu" class="mention hashtag" rel="tag">#Ubuntu</a> LTS freeze soon.

smxiAnd with that <a href="https://fosstodon.org/tags/inxi" class="mention hashtag" rel="tag">#inxi</a> 3.3.32 is released. 3 months in the making. Maybe 4k new or changed lines of code. Cleaner. Easier to maintain and add support for software based features like window managers and desktops. Refactors anywhere pain points existed. Because I had to draw a line there's already some new features coming in next inxi but I couldn't delay release any longer. So will be interesting to see how this does in the wild. <a href="https://fosstodon.org/tags/pinxi" class="mention hashtag" rel="tag">#pinxi</a> got as much testing as practical so fingers crossed.

Recent searches

Search options

Administered by:

Server stats:

#pinxi