Description of problem: Output IEC958 is the only output available all other output are "Unplugged unavailable". The problem occured after an update around the end of december. Mageia Cauldron kernel-desktop-5.10.4-4.mga8 - Linux Kernel for desktop use with x86_64 Pulse audio : Version : 14.0-1.mga8 pavucontrol : Version : 4.0-2.mga8 Fabricant: Advanced Micro Devices, Inc. [AMD/ATI] Description: SBx00 Azalia (Intel HDA) Module: snd_hda_intel
(In reply to Jean-Marc Sarat from comment #0) > Description of problem: > Output IEC958 is the only output available all other output are "Unplugged > unavailable". The problem occured after an update around the end of december. > This is too vague as there are many updates since. To find the culprit, the best you can do is to try a live ISO from Beta 2 before they were unavailable as we are next to release the RC one. Once booted with Live CD (Plasma, Gnome or XFCE), check if sound is available. You can also test the kernel-5.10.5 which has landed Cauldron early this week.
CC: (none) => ouaurelien
You could add here the output of $ inxi -A
Can you even be able to upgrade to latest kernel 5.10.7 in core repository by doing as root in a terminal: # urpmi --auto-update and reboot Does this device worked with earlier version of Mageia?
Reporter, could you please reply to the previous question? If you don't reply within two weeks from now, I will have to close this bug as OLD. Thank you.
Keywords: (none) => 8rc1, NEEDINFO
@Jean-Marc The latest Cauldron versions are: 5.10.12-desktop-2.mga8 pulseaudio-14.2-1.mga8 pavucontrol-4.0-2.mga8 [unchanged] Please DO report back. Normally the most recent ISOs are a snapshot of Cauldron at the time they are made, so any updated M8 system should be the same or better; but with Mageia 8 being forked off from Cauldron, version freezes etc, I am not sure. There is nothing to lose by trying a Live ISO anyway.
CC: (none) => lewyssmith
Yeah, as of today, an updated Cauldron machine is the same as if it has been installed with latest netinstall ISO. Note that currently the only medias for M8 that are publicly available are still the Beta2 medias, which are pretty outdated. But the Kernel version in Original report reminds me that the reporter uses a Cauldron system. @ Reporter, ASAP, when Mageia 8 RC official ISO will be published, can you report back about this current Bug report?
I do not think a later ISO should matter if a Cauldron/M8 system is kept up-to-date, it would mainly be for installation issues, not the latest software. > The problem occured after an update around the end of december I have not seen the mgaapplet Systray icon for some time, but doing: $ sudo urpmi --auto-update --auto is yielding updates. They are coming from (in my case; note the /8/ : http://distrib-coffee.ipsl.jussieu.fr/pub/linux/Mageia/distrib/8/x86_64/media/core/release/ etc. Must try MCC-Update System another time.
(In reply to Lewis Smith from comment #7) > I do not think a later ISO should matter if a Cauldron/M8 system is kept > up-to-date, it would mainly be for installation issues, not the latest > software. > > The problem occured after an update around the end of december > I have not seen the mgaapplet Systray icon for some time, but doing: > $ sudo urpmi --auto-update --auto > is yielding updates. They are coming from (in my case; note the /8/ : > http://distrib-coffee.ipsl.jussieu.fr/pub/linux/Mageia/distrib/8/x86_64/ > media/core/release/ > etc. > Must try MCC-Update System another time. Because mgaapplet has been set for his correct behaviour: to look only for updates in repositories marked as "update". To have GUI mgaapplet still look for updates until M8 is releajsed, use : $ drakrpm-edit-media --expert and click on checkbox to repos not marked as "update" repo. Don't forger to uncheck mater when M8 is released.
Status: NEW => NEEDINFOSeverity: major => normalVersion: Cauldron => 8Keywords: 8rc1 => (none)
Since there are insufficient details provided in this report for us to investigate the issue further, and we have not received feedback to the information we have requested above, we will assume the problem was not reproducible, or has been fixed in one of the updates we have released for the reporter's distribution. Users who have experienced this problem are encouraged to upgrade to the latest update of their distribution, and if this issue turns out to still be reproducible in the latest update, please reopen this bug with additional information. Closing as OLD.
Resolution: (none) => OLDStatus: NEEDINFO => RESOLVED