Lector de Feeds

‎Programming languages: rust

← Older revision Revision as of 20:43, 13 January 2026 Line 441: Line 441:  Ruby has been updated to 3.1.5. Ruby has been updated to 3.1.5.    −Rust is at version 1.91.0 It will be updated during Mageia 10's support life to follow new developments.+Rust is at version 1.92.0 It will be updated during Mageia 10's support life to follow new developments.     PHP has been updated to 8.4 / 8.5 (to determine which will be the main version). PHP has been updated to 8.4 / 8.5 (to determine which will be the main version). Katnatek

‎nouveau problems

← Older revision Revision as of 20:14, 13 January 2026 (4 intermediate revisions by the same user not shown)Line 56: Line 56:  == The modesetting driver == == The modesetting driver ==    −The modesetting X11 driver is hardware-agnostic, works with Nvidia, Intel and AMD kernel drivers.  The nouveau X11 driver only works with the nouveau kernel driver.+The modesetting X11 driver is hardware-agnostic, works with '''Nvidia, Intel and AMD''' kernel drivers.  The nouveau X11 driver only works with the nouveau kernel driver.     "modesetting" with Nvidia cards, though more stable, uses internally kernel's nouveau module too for 3D. "nouveau" in Xorg uses nouveau Xorg DDX driver plus kernel's nouveau module. For many recent NV cards the nouveau DDX can't even be used because they are unsupported (e.g. for NV RTX 3xxx and beyond, etc.). "modesetting" with Nvidia cards, though more stable, uses internally kernel's nouveau module too for 3D. "nouveau" in Xorg uses nouveau Xorg DDX driver plus kernel's nouveau module. For many recent NV cards the nouveau DDX can't even be used because they are unsupported (e.g. for NV RTX 3xxx and beyond, etc.). Line 63: Line 63:     == nouveau problems == == nouveau problems ==  +  +* nouveau can not load if you have installed [[#Loading_driver_in_initramfs|nvidia driver in initramfs]] - remove it.  +  +* Raster on portions of tty(s) when using multiple displays of unequal resolutions: upstream bug [https://gitlab.freedesktop.org/drm/nouveau/-/issues/214 #214], applicable when plymouth is disabled, and a valid video= parameter is not included on the linux or linuxefi lines in bootloader stanzas.     === Missing firmware === === Missing firmware === Line 74: Line 78:     {{fixme|81}} ''Someone try on Mageia and document it here.'' {{fixme|81}} ''Someone try on Mageia and document it here.'' −  −===Raster on portions of tty(s) when using multiple displays of unequal resolutions===  −  −This is upstream bug [https://gitlab.freedesktop.org/drm/nouveau/-/issues/214 #214], applicable when plymouth is disabled, and a valid video= parameter is not included on the linux or linuxefi lines in bootloader stanzas.      <br> <br> Line 145: Line 145:  ''News January 2025:'' <!--https://bugs.mageia.org/show_bug.cgi?id=31841#c42--> ''News January 2025:'' <!--https://bugs.mageia.org/show_bug.cgi?id=31841#c42-->  Now we provide initramfs packages for the three supported nvidia branches: nvidia-{470,current,newfeature}-initramfs. Now we provide initramfs packages for the three supported nvidia branches: nvidia-{470,current,newfeature}-initramfs. −'''Installing''' this package puts the related nvidia-current.ko and related sub-modules into the initramfs boot image for the running kernel by automatically also executing dracut.  To do it for all installed kernels, manually execute "dracut --regenerate-all" - but you may first want to see if current kernel boots nicely first.     −''This early loading of the driver might help in situations which else have slow loading or when there are concurrent racing with nouveau. It may help with Wayland issues.''+'''Advantages'''<br>  +This early loading of the driver might help in situations which else have slow loading or when there are concurrent racing issues with nouveau. It may help with Wayland or sddm issues in case they start too quicker than nvidia else loads.    −'''Note:''' You must first have used drakx11 to set your graphics driver to nvidia proprietary of same version.+'''Installing'''<br>  +This package puts the related nvidia-current.ko and related sub-modules into the initramfs boot image for the running kernel by automatically also executing dracut.  To do it for all installed kernels, manually execute "dracut --regenerate-all" - but you may first want to see if current kernel boots nicely first.    −'''Possible issues:''' when you switch from proprietary to free driver without uninstalling nvidia drivers, or in some rare particular situation of upgrading kernel and driver versions in same transaction.+'''Notes'''  +* You must first have used drakx11 to set your graphics driver to nvidia proprietary of same version.  +* There may later come problems in some rare particular situation of upgrading kernel and driver versions in same transaction.  +* drakx11 do not handle the -initramfs package  +*:...so if you want to switch to free driver, you *must* manually uninstall nvidia initramfs, or else it will block the free driver!    −'''To uninstall:''' just uninstall the -initramfs package, and dracut gets called to generate a new boot image of running kernel. To remove it from all kernels images, execute "dracut --regenerate-all".+'''To uninstall'''  +* uninstall the -initramfs package, and dracut gets called to generate a new boot image of running kernel.  +*:And then remove it from all kernels images: execute "dracut --regenerate-all".     <br> <br> Line 174: Line 181:  <br> <br>    −=== Known Nvidia issues ===+=== Known Nvidia issues and mitigations ===     '''{{Bug|32352}}''' - drakx11 do not for nvidia check whether kernel-devel is installed, nvidia-newfeature exist, nor if nvidia module really got built. '''Implication:  If you install a nvidia card''' and switch to nvidia proprietry driver, you must install the corresponding kernel-devel package for the running kernel before using MCC to configure the driver ( = executing drakx11 ), so the nvidia kernel module can get built.  And also make sure the -devel packages are installed for other installed kernels, so drivers can get automatically built when booting them. '''{{Bug|32352}}''' - drakx11 do not for nvidia check whether kernel-devel is installed, nvidia-newfeature exist, nor if nvidia module really got built. '''Implication:  If you install a nvidia card''' and switch to nvidia proprietry driver, you must install the corresponding kernel-devel package for the running kernel before using MCC to configure the driver ( = executing drakx11 ), so the nvidia kernel module can get built.  And also make sure the -devel packages are installed for other installed kernels, so drivers can get automatically built when booting them.    −'''{{Bug|33452}}''' - '''drakx11 in text mode crash''' on "too small screen" (in reality 4K) after preparing kernel module '''when installing Nvidia proprietary driver.'''  This may make root filesystem unmountable and/or fail graphics mode.  You may need to boot another system to work on it (one example see bug).  When it boots but do not reach graphical login, switch to a text terminal (i.e Ctrl+Alt+F4) log in as root, run drakx11 and select nouveau or modesetting driver.+'''{{Bug|33452}}''' - '''drakx11 in text mode crash''' on "too small screen" (in reality 4K) after preparing kernel module '''when installing Nvidia proprietary driver.'''  This may make root filesystem unmountable and/or fail graphics mode.  You may need to boot another system to work on it (one example see bug).  When it boots but do not reach graphical login, switch to a text terminal (i.e Ctrl+Alt+F4) log in as root, run drakx11 and select nouveau or modesetting driver. (also uninstall [[#Loading_driver_in_initramfs|initramfs nvidia]] if installed]]  +   +'''Kernel module build log''' If system fail to make the kernel module, like if you in journal during booting see a line containing "dkms-autorebuild.sh" and "Build failed.", then for details see the build log /var/lib/dkms/<broadcom?>/<version>.mga9.nonfree/build/make.log  +   +'''Kernel command line parameters'''  +* To prevent nouveau from loading you can either set "nouveau.modeset=0" or "module_blacklist=nouveau" on the boot command line, if this solves problem about loading nvidia proprietary driver, you might consider instead to load nvidia early [[#Loading_driver_in_initramfs|in initramfs]].  +* The nokmsboot option has no effect anymore since its support has been removed in kernel since kernel-6.2.1, during mga9 dev cycle. (But it is still written by some of our tool.)     <br> <br> Line 190: Line 203:     '''Possible Workaround''' Make sure to set a well supported resolution in the kernel command line, i.e avoid the red numbers in [https://en.wikipedia.org/wiki/VESA_BIOS_Extensions#Linux_video_mode_numbers this] table.  To see what got set on the kernel line on your system in last boot, issue {{cmd|<nowiki>journalctl -b|grep 'command line:'</nowiki>}} and look at the number after "vga=".  Look it up in the table what resolution it means. ''Note there is no wide standard for resolutions above 1280x1024.''  - To change it using {{prog|Mageia Control Center}}, Select {{menu|Boot > Set up boot system > Next > Advanced > Video mode: 1280x1024 16bpp}}, which will result in "vga=794", working on most computers. (If your screen have lower resolution, select that or next lower.) '''Possible Workaround''' Make sure to set a well supported resolution in the kernel command line, i.e avoid the red numbers in [https://en.wikipedia.org/wiki/VESA_BIOS_Extensions#Linux_video_mode_numbers this] table.  To see what got set on the kernel line on your system in last boot, issue {{cmd|<nowiki>journalctl -b|grep 'command line:'</nowiki>}} and look at the number after "vga=".  Look it up in the table what resolution it means. ''Note there is no wide standard for resolutions above 1280x1024.''  - To change it using {{prog|Mageia Control Center}}, Select {{menu|Boot > Set up boot system > Next > Advanced > Video mode: 1280x1024 16bpp}}, which will result in "vga=794", working on most computers. (If your screen have lower resolution, select that or next lower.) −  −<br>  −  −==== Problems resuming ====  −  −''I have a system *) which depending on nvidia driver version have problems after suspend-resume. Some works perfectly, some versions system may hang hard, some can be brought down using [[Troubleshooting_section_for_the_manual#Magics_keys|REISUB]], sometimes it is just that the screen only wakes up briefly with a message no signal and go back to sleep - but computer is running - for this case it may be enough to Power off/on the screen or disconnect/connect the cable so try that first, before REISUB, or I could get around this problem by using HDMI instead but that gives bad colours on sharp lines on this monitor. Workarounds: 1) Try another connection to monitor.  2) Try another nvidia driver (i.e for my system nvidia-current-550.90.07-1 have problem but not our two previous versions, and not nvidia470-470.256.02-1 released at the same time, but both versions from mga9 release do. 3) Use a free driver instead such as modesetting (slower) or nouveau (even slower here). 4) Using non-official kernels helped more or less in some cases, {{Bug|33316}}. 5) Hibernating works, so to hibernate instead of suspend may also be a workaround. '''*) System''': Mageia 9, Nvidia GTX 750 Ti, ASRock P55 Pro, Philips 436M6 screen on DisplayPort. /Morgano''      <br> <br> Morgano

Introduction

Hi there, blog readers! For the last week or so I've been poking into AI code review tools. Yes, this is partly because of the Red Hat "you must do AI things!" policy. But also, to be honest, because they seem to be...actually good now. I set up AI reviews for pull requests to our openQA test repo as an experiment. But especially over the last couple of months, they've got to the point where well over half of the review notes are actually useful, and the writing style isn't so awful I want to stab myself in the eyeballs. So I'd quite like to keep doing them, but in a more open source-y way. So far I've simply been cloning the pull requests to a GitHub mirror of the repo that exists solely to get AI reviews done. That repo has Gemini Code Assist enabled so the PRs are reviewed by Gemini automatically, e.g. here. It's very simple, but entirely closed source, there's no control over it, and Google could take it away at any time.

We're in the middle of migrating Fedora projects from Pagure to our new Forgejo instance, so I decided to try and get some sort of AI review system integrated with Forgejo. And I kinda succeeded! I wrote a Forgejo integration for ai-code-review, a tool I found that was written by another Red Hatter, and managed to set up a proof-of-concept Forgejo Actions workflow using it on a repo I own that's hosted at Codeberg (since Codeberg has public Forgejo Actions runners available; we don't have Actions entirely set up in the Fedora instance yet). Right now it's using Gemini as the model provider just because that was the easiest thing to set up for a PoC, but ai-code-review's design makes the LLM provider easily pluggable, so it's trivial to swap it out. Long term I hope we'll get a Fedora LLM provider set up, serving open source models, and we can make it use that. There's an Ollama backend, and adding an OpenAI API backend should be pretty easy.

Before going any further with that, though, I decided to look around and see if there are other tools out there, and if so, which might be the best one. I poked around a bit and found a few, and wrote up a very half-assed comparative assessment. I figured this might interest others, so I've prettied it up a tiny bit and put it below. I make no claims that this is comprehensive, accurate or fair, please send all complaints to the happyassassin.net HR department! The takeaway is that I'll probably keep working on the ai-code-review approach and also experiment with forking Qodo's archived open-source pr-agent project and see if I can add Forgejo support to it, to compare it against ai-code-review.

If anyone knows of any I missed, please let me know! I briefly looked at RhodeCode but discounted it because it's a whole-ass forge, not just a review tool. ReviewBoard doesn't seem to have any LLM integration as best as I could tell.

The Contenders ai-code-review

• Repo: https://gitlab.com/redhat/edge/ci-cd/ai-code-review
• Author: Juanje Ojeda (Red Hat)
• Language: Python (typed)
• Architecture: Modular
• Tests: Yes, LLM-generated, fairly comprehensive unit tests, very limited integration tests
• Begun: August 2025
• Status: Active
• Forges: GitLab, GitHub, local changes (Forgejo supported submitted)
• Model providers: Gemini, Anthropic, Ollama
• Output: Console or PR/MR comment
• Deployment: Local execution, GitLab CI, GitHub Actions (one-shot deployment via container image in CI job)
• Prompts: Here

ai-codereview

• Repo: Red Hat internal
• Author: Tuvya Korol (Red Hat)
• Language: Python (untyped)
• Architecture: Monolithic
• Tests: No
• Begun: June 2025
• Status: Active
• Forges: GitLab, local changes
• Model providers: RH-internal Claude, Gemini, Granite
• Output: Console or MR comment
• Deployment: Local execution, GitLab CI (ad hoc deployment via curl/pip in CI job)
• Prompts: Red Hat internal

kodus-ai

• Repo: https://github.com/kodustech/kodus-ai
• Author: Kodus
• Language: Typescript
• Architecture: Modular
• Tests: Yes, handwritten, unit and integration, not sure of coverage
• Begun: April 2025
• Status: Active
• Forges: GitHub, GitLab, BitBucket
• Model providers: OpenAI, Gemini, Anthropic, Novita, OpenRouter, any OpenAI-compatible
• Output: MR/PR comment and/or review (seems to depend on configuration)
• Deployment: Local via yarn (indicated as for development only), as containerized webapp (for prod) with own installer - looks complex
• Prompts: Here

pr-agent

• Repo: https://github.com/qodo-ai/pr-agent
• Author: Qodo (formerly Codium)
• Language: Python (untyped)
• Architecture: Modular
• Tests: Yes, handwritten, unit and integration, somewhat primitive, many commented out, 24% coverage (per codecov)
• Begun: July 2023
• Status: Archived (Nov 2025)
• Forges: GitHub, GitLab, Gitea, Gerrit, BitBucket, AWS CodeCommit, Azure DevOps, local changes
• Model providers: Any OpenAI-compatible (looks like some special handling for Azure), LiteLLM
• Output: MR/PR comment and/or review, has interactive features
• Deployment: Local execution or Forge CI. There's a custom GitHub action but it may be abandoned. Installable via pip, should be trivial to containerize for simple one-shot CI job deployment
• Prompts: Here

ai-pr-reviewer

• Repo: https://github.com/coderabbitai/ai-pr-reviewer
• Author: CodeRabbit
• Language: Typescript
• Architecture: Modular
• Tests: Barely any
• Begun: Feb 2023
• Status: Archived (Nov 2023)
• Forges: GitHub
• Model providers: OpenAI
• Output: PR review/comment
• Deployment: GitHub Action (no longer maintained). No generic or local deployment documented
• Prompts: Here

Conclusions

ai-code-review (Juanje) and pr-agent (Qodo/Codium) seem the best options.

Of the RH-developed, greenfield projects, ai-code-review is more featureful and better architected than ai-codereview, and not tied to an RH-internal model provider.

Of the existing public projects, ai-pr-reviewer (CodeRabbit) was very tied to GitHub, has no documented standalone deployment ability, and was archived fairly early in development. Plus it's in TypeScript. Kodus is actively developed, but similarly is in TypeScript, deployment looks complex, and from what I've seen I don't love its review style. Hard to say why but the project overall gives me a sloppy vibe. pr-agent (Qodo) had the longest development history and seems the most mature and capable at the point where it was abandoned (well, they actually seem to have done a heel turn and gone closed source / SaaS). It has a documented standalone deployment process which looks relatively simple and subject to integration into generic CI workflows.

In Mageia/9/x86_64: Mesa is an OpenGL 4.6 compatible 3D graphics library.

In Mageia/9/aarch64: Mesa is an OpenGL 4.6 compatible 3D graphics library.

In Mageia/9/armv7hl: Mesa is an OpenGL 4.6 compatible 3D graphics library.

In Mageia/9/i586: Mesa is an OpenGL 4.6 compatible 3D graphics library.

In Mageia/cauldron/x86_64: Rachota is a portable application for timetracking different projects. It runs everywhere. It displays time data in diagram form, creates customized reports and invoices or analyses measured data and suggests hints to improve user's time usage. The totally portable yet personal timetracker.

In Mageia/cauldron/i586: Rachota is a portable application for timetracking different projects. It runs everywhere. It displays time data in diagram form, creates customized reports and invoices or analyses measured data and suggests hints to improve user's time usage. The totally portable yet personal timetracker.

In Mageia/cauldron/i586: A program to convert images from PPM format into the control language for the Alps Micro-Dry printers, at various times sold by Citizen, Alps and Okidata. This program drives the Alps Micro-Dry series of printers, including the Citizen Printiva series, Alps MD series, and Oki DP series (but not yet the DP-7000). In the current release, the program drives the standard mode fairly well; the dye sublimation mode very well; and the VPhoto mode reasonably well. It supports all the colours available up to the DP-5000, including the foil colours.

In Mageia/cauldron/x86_64: A program to convert images from PPM format into the control language for the Alps Micro-Dry printers, at various times sold by Citizen, Alps and Okidata. This program drives the Alps Micro-Dry series of printers, including the Citizen Printiva series, Alps MD series, and Oki DP series (but not yet the DP-7000). In the current release, the program drives the standard mode fairly well; the dye sublimation mode very well; and the VPhoto mode reasonably well. It supports all the colours available up to the DP-5000, including the foil colours.

In Mageia/cauldron/x86_64: This tool tries to recover JFIF (JPEG) pictures and MOV movies (using recovermov) from a peripheral. This may be useful if you mistakenly overwrite a partition or if a device such as a digital camera memory card is bogus.

In Mageia/cauldron/i586: This tool tries to recover JFIF (JPEG) pictures and MOV movies (using recovermov) from a peripheral. This may be useful if you mistakenly overwrite a partition or if a device such as a digital camera memory card is bogus.

In Mageia/cauldron/x86_64: Rdfind is a program that finds duplicate files. It is useful for compressing backup directories or just finding duplicate files. It compares files based on their content, NOT on their file names.

In Mageia/cauldron/i586: Rdfind is a program that finds duplicate files. It is useful for compressing backup directories or just finding duplicate files. It compares files based on their content, NOT on their file names.

In Mageia/cauldron/x86_64: Unifont is a Unicode font with a glyph for every visible Unicode Basic Multilingual Plane code point and more, with supporting utilities to modify the font. This package contains tools and glyph descriptions.

In Mageia/cauldron/i586: Unifont is a Unicode font with a glyph for every visible Unicode Basic Multilingual Plane code point and more, with supporting utilities to modify the font. This package contains tools and glyph descriptions.

In Mageia/cauldron/i586: RANCID monitors a router's (or more generally a device's) configuration, including software and hardware (cards, serial numbers, etc) and uses CVS (Concurrent Version System) or Subversion to maintain history of changes. RANCID does this by the very simple process summarized here: * login to each device in the router table (router.db), * run various commands to get the information that will be saved, * cook the output; re-format, remove oscillating or incrementing data, * email any differences (sample) from the previous collection to a mail list, * and finally commit those changes to the revision control system RANCID also includes looking glass software. It is based on Ed Kern's looking glass which was once used for http://nitrous.digex.net/, for the old-school folks who remember it. Our version has added functions, supports Cisco, Juniper, and Foundry and uses the login scripts that come with rancid; so it can use telnet or ssh to connect to your devices(s). Rancid currently supports Cisco routers, Juniper routers, Catalyst switches, Foundry switches, Redback NASs, ADC EZT3 muxes, MRTd (and thus likely IRRd), Alteon switches, and HP Procurve switches and a host of others. Rancid is known to be used at: AOL, Global Crossing, MFN, NTT America, Certainty Solutions Inc.

In Mageia/cauldron/x86_64: RANCID monitors a router's (or more generally a device's) configuration, including software and hardware (cards, serial numbers, etc) and uses CVS (Concurrent Version System) or Subversion to maintain history of changes. RANCID does this by the very simple process summarized here: * login to each device in the router table (router.db), * run various commands to get the information that will be saved, * cook the output; re-format, remove oscillating or incrementing data, * email any differences (sample) from the previous collection to a mail list, * and finally commit those changes to the revision control system RANCID also includes looking glass software. It is based on Ed Kern's looking glass which was once used for http://nitrous.digex.net/, for the old-school folks who remember it. Our version has added functions, supports Cisco, Juniper, and Foundry and uses the login scripts that come with rancid; so it can use telnet or ssh to connect to your devices(s). Rancid currently supports Cisco routers, Juniper routers, Catalyst switches, Foundry switches, Redback NASs, ADC EZT3 muxes, MRTd (and thus likely IRRd), Alteon switches, and HP Procurve switches and a host of others. Rancid is known to be used at: AOL, Global Crossing, MFN, NTT America, Certainty Solutions Inc.

In Mageia/cauldron/x86_64: Redis is an advanced key-value store. It is often referred to as a data structure server since keys can contain strings, hashes, lists, sets and sorted sets. You can run atomic operations on these types, like appending to a string; incrementing the value in a hash; pushing to a list; computing set intersection, union and difference; or getting the member with highest ranking in a sorted set. In order to achieve its outstanding performance, Redis works with an in-memory dataset. Depending on your use case, you can persist it either by dumping the dataset to disk every once in a while, or by appending each command to a log. Redis also supports trivial-to-setup master-slave replication, with very fast non-blocking first synchronization, auto-reconnection on net split and so forth. Other features include Transactions, Pub/Sub, Lua scripting, Keys with a limited time-to-live, and configuration settings to make Redis behave like a cache. You can use Redis from most programming languages also.