Lector de Feeds

Mageia 10 Release Notes

Wiki Mageia - 13 Enero, 2026 - 23:11

‎Compilers and tools: llvm and some separation

← Older revision Revision as of 22:11, 13 January 2026 Line 396: Line 396:     Glibc has been updated to 2.39. Glibc has been updated to 2.39.  +  GCC has been updated to 14.1, GDB to 14.2 and Valgrind to 3.20.0. GCC has been updated to 14.1, GDB to 14.2 and Valgrind to 3.20.0. −LLVM has been updated to 17.0.+   +LLVM has been updated to 20.1.     Firebird has been updated to 4.0.2 Firebird has been updated to 4.0.2 Katnatek
Categorías: Wiki de Mageia

Mageia 10 Press

Wiki Mageia - 13 Enero, 2026 - 22:58

add Spanish blog post

← Older revision Revision as of 21:58, 13 January 2026 (2 intermediate revisions by the same user not shown)Line 6: Line 6:  {{multi language banner|[[Mageia_10_Press|English]]}} {{multi language banner|[[Mageia_10_Press|English]]}}    − +<!--  == Bulgarian - български == == Bulgarian - български ==    Line 20: Line 20:  == Croatian  - Hrvatski == == Croatian  - Hrvatski ==    −#  +# -->     == English == == English == Line 26: Line 26:  # {{Press item|9to5Linux|https://9to5linux.com/first-look-at-mageia-10-alpha-release-now-available-for-public-testing|First Look at Mageia 10 – Alpha Release Now Available for Public Testing| 2026-01-10}} # {{Press item|9to5Linux|https://9to5linux.com/first-look-at-mageia-10-alpha-release-now-available-for-public-testing|First Look at Mageia 10 – Alpha Release Now Available for Public Testing| 2026-01-10}}  # {{Press item|Phoronix|https://www.phoronix.com/news/Mageia-10-Alpha|Mageia 10 Alpha Released - 32-bit ISOs Still Available| 2026-01-10}} # {{Press item|Phoronix|https://www.phoronix.com/news/Mageia-10-Alpha|Mageia 10 Alpha Released - 32-bit ISOs Still Available| 2026-01-10}}  +no time to do it neatly, please improve:  +  +https://serverhost.com/blog/exploring-mageia-10-alpha-release-now-open-for-public-testing/  +  +https://www.linuxcompatible.org/story/mageia-10-alpha-1-released/  +  +https://www.facebook.com/groups/linuxRO/posts/25766084749688350/  +  +https://lxer.com/module/newswire/view/361030/index.html  +  +https://www.youtube.com/watch?v=w1AWo7D-BJY  +  +https://www.warp2search.net/story/mageia-10-alpha-1-released/  +  +https://www.linuxquestions.org/questions/showthread.php?s=4fe993cc0fd6de98138515f8b5f81b48&p=6610226#post6610226  +  +(from a mail from marchugo, 12-01-2026, on atelier-discuss ml)  +  +and  +https://distrowatch.com/?newsid=12698 (Marc Pare, atelier-discuss, 11-01-2026)  +  +  +https://news.tuxmachines.org/n/2026/01/10/First_Look_at_Mageia_10_Alpha_Release_Now_Available_for_Public_.shtml (marchugo, atelier-discuss, 11-01-2026)     == French – Français == == French – Français ==     #   #   − +<!--  == German - Deutsch == == German - Deutsch ==    Line 74: Line 97:     #   #   − +-->  == Spanish - Español == == Spanish - Español ==     === Blog de Mageia en Español === === Blog de Mageia en Español === − +https://blog.mageia.org/es/2026/01/11/mageia-10-primera-alpha-iso-validada-por-el-consejo/  #   #   − +<!--  == Swedish - svenska == == Swedish - svenska ==    Line 92: Line 115:     #   #   − +-->  == Wikipedia == == Wikipedia ==    Marja
Categorías: Wiki de Mageia

Mageia 10 Release Notes

Wiki Mageia - 13 Enero, 2026 - 21:43

‎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
Categorías: Wiki de Mageia

Setup the graphical server

Wiki Mageia - 13 Enero, 2026 - 21:14

‎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
Categorías: Wiki de Mageia

Official pre-release testing

Wiki Mageia - 13 Enero, 2026 - 13:38

mga10 DL link fix

← Older revision Revision as of 12:38, 13 January 2026 Line 37: Line 37:  == Downloading == == Downloading ==    −Find ISOs on https://mirrors.kernel.org/mageia/iso/10/ (will redirect you automatically to a mirror), or choose your [https://mirrors.mageia.org/ favourite mirror] and find ISOs at ''<mirror url>/mageia/iso/'' for example http://mirror.accum.se/mirror/mageia/iso/).  Netinstaller can be found at ''<mirror url>/mageia/distrib/$RELEASE/$ARCH/install/images/'' (i.e http://mirror.accum.se/mirror/mageia/distrib/9/x86_64/install/images/).+Find ISOs on https://www.mageia.org/10/ (will redirect you automatically to a mirror), or choose your [https://mirrors.mageia.org/ favourite mirror] and find ISOs at ''<mirror url>/mageia/iso/'' for example http://mirror.accum.se/mirror/mageia/iso/).  Netinstaller can be found at ''<mirror url>/mageia/distrib/$RELEASE/$ARCH/install/images/'' (i.e http://mirror.accum.se/mirror/mageia/distrib/9/x86_64/install/images/).     Now all downloads are also linked from  https://www.mageia.org/en/downloads/alternative/, which also gives instructions to check the files. Now all downloads are also linked from  https://www.mageia.org/en/downloads/alternative/, which also gives instructions to check the files. Filip
Categorías: Wiki de Mageia

Persistent live systems

Wiki Mageia - 13 Enero, 2026 - 09:45

‎Swap file on ext4 persistence

← Older revision Revision as of 08:45, 13 January 2026 (One intermediate revision by the same user not shown)Line 194: Line 194:  # Reboot to that kernel. # Reboot to that kernel.  # Add 6.6 kernel in skip.list per '''(*)''' above, and uninstall kernel(s) 6.6.x, which should also remove any 6.6.*-latest package. # Add 6.6 kernel in skip.list per '''(*)''' above, and uninstall kernel(s) 6.6.x, which should also remove any 6.6.*-latest package.  +It is ''possible'' to [https://bugs.mageia.org/attachment.cgi?id=15306 install nvidia470] - and probably similar for nvidia-current, but seldom worth the work and 1GB space!  The free drivers work well.     == Custom Live ISO == == Custom Live ISO == Line 289: Line 290:     ''' See if it works ''' ''' See if it works '''  + # systemctl daemon-reload  // reloads fstab    # mount -a    // Perform mounts per /etc/fstab   # mount -a    // Perform mounts per /etc/fstab    # swapon -av  // Activate swap, verbose   # swapon -av  // Activate swap, verbose Morgano
Categorías: Wiki de Mageia

Sysadmin Tasks

Wiki Mageia - 13 Enero, 2026 - 01:51

‎Access/Identity: Sympa_Config

← Older revision Revision as of 00:51, 13 January 2026 Line 27: Line 27:  * Unlock user account * Unlock user account  * [[SOP robot credentials renewal]] * [[SOP robot credentials renewal]]  +* [[Sympa Config|Mailing list access controls]]     === Package Building === === Package Building === Danf
Categorías: Wiki de Mageia

MGASA-2026-0007 - Updated libtasn1 packages fix security vulnerability

Mageia Security - 12 Enero, 2026 - 19:42
Publication date: 12 Jan 2026
Type: security
Affected Mageia releases : 9
CVE: CVE-2025-13151 Description Stack-based buffer overflow in libtasn1 version: v4.20.0. The function fails to validate the size of input data resulting in a buffer overflow in asn1_expend_octet_string. (CVE-2025-13151) References SRPMS 9/core
  • libtasn1-4.21.0-1.mga9

MGAA-2026-0005 - Updated dkms-vhba, libmirage & cdemu-daemon packages fix bugs

Mageia Security - 12 Enero, 2026 - 19:42
Publication date: 12 Jan 2026
Type: bugfix
Affected Mageia releases : 9
Description We are planning make a backport for kernel 6.18. In the QA stage, we discovered the dkms-vhba, libmirage and cdemu-daemon packages don't work as they should. These updates fixes the reported issue. References SRPMS 9/core
  • dkms-vhba-20250329-1.mga9
  • libmirage-3.2.10-1.mga9
  • cdemu-daemon-3.2.7-1.2.mga9
Feed