this post was submitted on 17 Jun 2023
18 points (100.0% liked)

Pop!_OS (Linux)

5126 readers
34 users here now

Pop!_OS is an operating system developed by System76 for STEM and creative professionals who use their computer as a tool to discover and create. Unleash your potential on secure, reliable open source software. Based on your exceptional curiosity, we sense you have a lot of it.

Unleash your potential

Whether this is your first experience with Linux, or your latest adventure, all are welcome to discuss and ask questions about Pop!_OS and COSMIC. Keep the discussions friendly though, and remember to assume good intentions whenever you reply. We're all here because we have a shared love for Linux and open source software.

System76 Logo

Support us by buying System76 hardware for you or your company! Or by donating on the Pop!_OS website through the "Support Pop" button. Pop!_OS and COSMIC are fully funded by System76 hardware sales. All systems are assembled in the USA. With your support, we'll work to push the Linux desktop forward with COSMIC.

Links

Guides

Hardware

Recommended

Community Rules

Follow the Code of Conduct

All posts on pop_os must adhere to the Pop!_OS community Code of Conduct. https://github.com/pop-os/code-of-conduct

Be helpful

Posts to pop_os must be helpful. When responding to a user asking for help, do not provide tongue-in-cheek responses like "RTM" or links to LMGTFY. Linking to direct sources that answer the asker's question is fine, but it's advised to provide some explanation as to how you got to that source.

Critique should be constructive

We within the Pop!_OS community welcome helpful criticism or ideas on ways to improve. However, basic "It's bad" or other simple negative comments don't help anyone fix anything. When voicing a complaint about something, try to point out ways the complaint could be improved or worked around, so that we can make a better product for it.

This rule applies to both Pop!_OS and its projects as well as other products available from third-parties.

Don't post malicious "advice"

It can be funny to joke about malicious commands, however this is not the venue for it. Do not advise users to run commands which will lock up their systems, steal their data, or erase their drive. Examples of this include (but are not limited to) fork bombs, rm, etc.

Posts violating this rule will be removed, even if the post is clearly in jest. Repeated offences may lead to a ban. You may understand that the command isn't serious, but a new user might not.

No personal attacks

Posts making a personal attack on any user will not be tolerated.

No hate speech

Hate speech of any kind will not be tolerated. Any violations will be removed, and are grounds for a ban.

founded 1 year ago
MODERATORS
 

I am kinda new to Linux, but have been using Pop OS for over a year.

This issue has always been the case for me. Since I was on the 20.10 build till now. First some context.

Current version. 22.04lts Intel Celeron N4100 Mesa Intel 600UHD Graphics Connected Via HDMI to TV

How the issue presents-

Upon boot, everything works fine. But after a while, I lose audio. and the only way to get it back would be to open the settings app> sound > then toggle the audio device back to HDMI.

Sometimes it takes multiple (2-3) attempts to get this sorted.

But the kicker is, the second I click on the settings icon, the screen goes blank. And this stays blank for about 2-3mins then comes back on.

This blank screen thing also happens at times when I install or update certain apps eg. Plex. The screen just goes blank, then comes back on after a few minutes.

Oh, and I can prevent this from happening, if upon boot up, the first thing I do is open the settings app, and just leave it minimized in my dock. No (or at least hardly any) audio cutouts and no more blank screens. In this case, updating apps like Plex still causes the blank screen though.

Again, I am a Linux noob, so please, to anyone willing and capable of helping, anything you suggest I do or ask me to do, that requires the use of the terminal, kindly also provide instructions.

you are viewing a single comment's thread
view the rest of the comments
[–] mmstick@lemmy.world 2 points 1 year ago (2 children)

Are there any errors emitted when this happens if you have journalctl -fk running in a terminal in the background?

[–] 1ntrinsic@lemmy.world 2 points 1 year ago* (last edited 1 year ago) (1 children)

It happened again... ran journal thing...

Got this...

Jun 17 21:45:16 pop-os kernel: snd_hda_codec_realtek hdaudioC0D0: Unable to sync register 0x2b8000. -5

Jun 17 21:45:16 pop-os kernel: snd_hda_codec_realtek hdaudioC0D0: Unable to sync register 0x2b8000. -5

Jun 17 21:45:18 pop-os kernel: snd_hda_codec_realtek hdaudioC0D0: Unable to sync register 0x2b8000. -5

Jun 17 21:45:18 pop-os kernel: snd_hda_codec_realtek hdaudioC0D0: Unable to sync register 0x2b8000. -5

Jun 17 21:46:51 pop-os kernel: azx_single_wait_for_response: 738 callbacks suppressed

Jun 17 21:46:51 pop-os kernel: snd_hda_codec_realtek hdaudioC0D0: Unable to sync register 0x2b8000. -5

Jun 17 21:46:51 pop-os kernel: snd_hda_codec_realtek hdaudioC0D0: Unable to sync register 0x2b8000. -5

Jun 17 22:54:35 pop-os kernel: azx_single_wait_for_response: 362 callbacks suppressed

Jun 17 22:54:35 pop-os kernel: snd_hda_codec_realtek hdaudioC0D0: Unable to sync register 0x2b8000. -5

Jun 17 22:54:35 pop-os kernel: snd_hda_codec_realtek hdaudioC0D0: Unable to sync register 0x2b8000. -5

and then this when I did the journal thing for the past hour. Just copied the part that was red.

Jun 17 22:54:35 pop-os kernel: azx_single_wait_for_response: 362 callbacks suppressed

Jun 17 22:54:35 pop-os kernel: snd_hda_codec_realtek hdaudioC0D0: Unable to sync register 0x2b8000. -5

Jun 17 22:54:35 pop-os kernel: snd_hda_codec_realtek hdaudioC0D0: Unable to sync register 0x2b8000. -5

Jun 17 22:54:35 pop-os gsd-media-keys[3235]: Unable to get default source

Jun 17 22:55:20 pop-os gsd-media-keys[3235]: Unable to get default source

[–] mmstick@lemmy.world 2 points 1 year ago

Then the issue is in the kernel and it may be fixed in a future kernel update. It might be caused by a power state. You can add intel_idle.max_cstate=1 to your kernel options by running sudo kernelstub -a intel_idle.max_cstate=1 to limit the max cstate, at the cost of higher energy consumption.

[–] 1ntrinsic@lemmy.world 1 points 1 year ago

haven't tried that, leaving that open in the terminal now and waiting for it to happen again.