home.social

#mrmazda — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #mrmazda, aggregated by home.social.

  1. New 3.3.37 goes out the door. Includes last minute workaround for 32 bit intel gen2 gpu eglinfo hang found. Probably a regression in i915 driver. And the big monitor scaling feature.
    Full changelog here:
    codeberg.org/smxi/inxi/src/bra

    This is the longest between releases in quite a while so nice to get some nifty enhancements and fixes in.

    This also introduces the improved option syntax for -b -e, which gets rid of a peeve of -F being impossible to explain.

  2. Just released new (next ) has first draft of working monitor scaling support. The higher physical screen resolutions get, the more scaling is used. had off and on mentioned this as nice to have feature.

    Not easy to figure out data sources but seems to work with and wayland-info now.

    I realized I could do scaling on my with which made dev a lot easier. Plus a good data file of scaled 3 monitor setup.

    Updated graphics docs with new res section.

  3. Just released new #pinxi (next #inxi ) has first draft of working monitor scaling support. The higher physical screen resolutions get, the more scaling is used. #mrmazda had off and on mentioned this as nice to have feature.

    Not easy to figure out data sources but seems to work with #xrandr and wayland-info now.

    I realized I could do scaling on my #xfce with #x11 which made dev a lot easier. Plus a good data file of #wayland scaled 3 monitor setup.

    Updated graphics docs with new res section.

  4. Just released new #pinxi (next #inxi ) has first draft of working monitor scaling support. The higher physical screen resolutions get, the more scaling is used. #mrmazda had off and on mentioned this as nice to have feature.

    Not easy to figure out data sources but seems to work with #xrandr and wayland-info now.

    I realized I could do scaling on my #xfce with #x11 which made dev a lot easier. Plus a good data file of #wayland scaled 3 monitor setup.

    Updated graphics docs with new res section.

  5. Just released new #pinxi (next #inxi ) has first draft of working monitor scaling support. The higher physical screen resolutions get, the more scaling is used. #mrmazda had off and on mentioned this as nice to have feature.

    Not easy to figure out data sources but seems to work with #xrandr and wayland-info now.

    I realized I could do scaling on my #xfce with #x11 which made dev a lot easier. Plus a good data file of #wayland scaled 3 monitor setup.

    Updated graphics docs with new res section.

  6. I should probably get off my butt and release next . There haven't been any real issues for a while now. Though had an advanced display resolution enhancement request but it takes work and thinking to do. And testing.

  7. found a last minute issue, wrong gpu ID match in nvidia section, which then reminded me that I'd forgotten to update the gpu ids for amd, intel, and nvidia. Added some more, and maybe fixed, or broke, some others. Note tracking cpu and gpu microarch data is really difficult, and time consuming. I wish someone who is passionate about those would step up and help. It gets old tracking that info and researching latest specs.

  8. For anyone into / linux graphics arcana, ongoing updates.

    docs.kernel.org/gpu/vga-switch

    As I suspected real data comes krom kernel docs. Unfortunately switcheroo state data lives in /sys/kernel/debug which is root read only. But helped define the problem. switcherooctl also has a tiny bit of info with list option but it only shows gpus available.

    found great set of hardware, same boards, intel igpu. One with nvidia card. Gpu class id switched depending on w/wo dgpu! ID dynamic!

    5/

  9. Found issues in repo report for some software sorced repo lists.: 's , , . 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 . Thanks for noticing.

    Then noticed the package count failed for mageia. Turns out they are using different version of rpm, missing some options so no results. Will add workaround.

  10. Found issues in #inxi repo report for some software sorced repo lists.: #mageia's #urpmq, #pisi, #solus #eopkg. 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 #pinxi. Thanks #mrmazda for noticing.

    Then noticed the #rpm package count failed for mageia. Turns out they are using different version of rpm, missing some options so no results. Will add workaround.

  11. Found issues in #inxi repo report for some software sorced repo lists.: #mageia's #urpmq, #pisi, #solus #eopkg. 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 #pinxi. Thanks #mrmazda for noticing.

    Then noticed the #rpm package count failed for mageia. Turns out they are using different version of rpm, missing some options so no results. Will add workaround.

  12. @getajobmike 's solution to contributing to was becoming a / packager, which is a thankless task, which is why I try to thank him now and then.

    of / 's solution was to create that kernel project and run it for over decade.

    Others run distros like , and support them. has supported desktop users for ages.

    I use specific names because supporting free software is the work of individuals dedicated to it.

  13. The slow motion tidal wave of core (next ) refactors continues unabated. Thanks to ongoing testers at and particularly to who has been helping find failures by the best way possible: running and doing things I don't. Just found bug that made fallback startx/xinit detections always fail. That was the new logic. Also found more failures caused by fixes to version tests, they were relying on bug behavior to work. Always a risk when fixing bugs.

    All going well.

  14. Also verified distro ID for / newer releases of / releases.

    I don't do these upgrades that often, the original idea was that distros would actually care and spend the time to help, but that plan never materialized on the earthly plane, so it basically just happens when I get bored and feel like doing it.

    That issue stands alone and lonely, year after year.

    Also some huge documentation dumps for Audio from gave a lot of systems and data.

  15. Two small bugs were exposed by pure chance after 3.3.31 was released, one was a small error I made in the release, and one has always been around since /sys based temp feature was added. The second has never appeared before and showed literally by pure chance, typed -vs instead of --vs, which tripped sensors on one system that has this issue.

    Because this was 1 extra line to fix, and fixing a second, I did a 3.3.31-2 tagged version to make sure the fixed version is master

  16. @ChristosArgyrop @mjgardner I have vms of and , and run on an old system, which helps me catch little oversights that slip in now and then. Some other people who test, in particular, runs a lot of old systems, so he catches stuff sometimes too. And I run current Debian testing so I'm also current on reasonable new as well.