sound fine on 5.8.0-48-generic #54~20.04.1-Ubuntu
On 3/27/21 10:00 AM, Steph Gosling wrote:
> On a 9300 with 5.4.0-70-generic #78 (running kubuntu) it appears every
> other login I have no sound and the repeated message:
>
> [ 257.488549] snd_hda_intel :00:1f.3: DSP detected with PCI
> class
On a 9300 with 5.4.0-70-generic #78 (running kubuntu) it appears every
other login I have no sound and the repeated message:
[ 257.488549] snd_hda_intel :00:1f.3: DSP detected with PCI
class/subclass/prog-if info 0x040380
[ 257.494305] snd_hda_intel :00:1f.3: enabling device ( -> 00
In the meantime I'm on 5.4.0-51-generic #56, but it's still happening.
Google more about the error, there are some indications that it could be
a faulty/bad firmware problem:
https://www.kernel.org/doc/html/v5.4/sound/hd-audio/notes.html#codec-
probing-problem
--
You received this bug notificati
Just happened again. I mostly get the "No response from codec" messages
from above, but this actually the slightly different first line when the
errors begin:
Oct 3 11:40:45 fedell kernel: [8.819040] snd_hda_intel
:00:1f.3: azx_get_response timeout, switching to polling mode: last
cmd=0x2
Re #18:
Same here - but I can't tell whether it was working fine on 5.4.0-47-generic
since I don't have the laptop long enough and I updated straight away ...
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://
When I first installed 20.04 I had no problem at all.
I have been having this problem since 5.4.0-47-generic #51
I have to turn off or reboot 2, 3 times to get sound back.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubu
I have the same machine (Dell XPS 13 9300), came preloaded with Ubuntu
18, then upgraded to 20.04. Running Kernel 5.4.0-48-generic #52.
I have the same problem, only that nothing really helps apart from
restarting until it randomly works ...
--
You received this bug notification because you are
problem seems gone since 5.4.0-48-generic #52
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1894881
Title:
[XPS 13 9300, Realtek ALC289, Speaker, Internal] Pulseaudio fails to
d
No. Bught the laptop with Ubuntu 18,04 preloaded and moved to 20.04
Got a main PC also running Ubuntu
No Windows at home :/
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1894881
Ti
Are you dual-booting with Windows by chance?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1894881
Title:
[XPS 13 9300, Realtek ALC289, Speaker, Internal] Pulseaudio fails to
de
kern.log
** Attachment added: "kern.log.gz"
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1894881/+attachment/5409903/+files/kern.log.gz
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.l
syslog shows :
Sep 11 20:03:43 orion kernel: [ 104.062316] snd_hda_intel :00:1f.3: No
response from codec, resetting bus: last cmd=0x20570500
Sep 11 20:03:44 orion kernel: [ 105.065317] snd_hda_intel :00:1f.3: No
response from codec, resetting bus: last cmd=0x20670500
Sep 11 20:03:45 o
syslog
** Attachment added: "syslog.gz"
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1894881/+attachment/5409904/+files/syslog.gz
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchp
Just booted my machine from being off. No sound.
Messages filling kern.log and syslog.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1894881
Title:
[XPS 13 9300, Realtek ALC289, S
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: pulseaudio (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bug
I dont believe this to really be a bug. If I leave the sound keys alone
after boot and login and let the Pulse and soudcard be ready, no problem
hapoens. You just need to avoid using those keys just after login or at
login prompt.
Ok to close this ?
--
You received this bug notification because
tried to add logs but it complains about a "cant find package linux"
gf@orion:~$ apport-collect 1894881
The authorization page:
(https://launchpad.net/+authorize-token?oauth_token=sDF40cwZ5lbHvmQ5xGZp&allow_permission=DESKTOP_INTEGRATION)
should be opening in your browser. Use your browser to au
Reponse to Daniel Letzeisen (dtl131)
Yes, doing that helped
And not tounching the 3 buttons immediatly after login to let Pulse and
the sound card be "ready" also avoids the problem :)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pul
I think I found out what's happening.
When the machine boots, and the login screen is displayed
The sound is not immediatly initialized and working
If, when it's not yet ready, I press the cut volume/volume up/volume down
It puts the sound card and/or Pulse into a state where it gets stuck...
If
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1894881
Title:
[XPS 13 9300, Realtek ALC289, Speaker, Int
Boot into the BIOS and disable the onboard audio. Save the settings and
reboot. Then, go into the BIOS again and turn the audio back on (save
and reboot). Does that help?
https://www.dell.com/support/manuals/us/en/04/xps-13-9300-laptop/xps-13-9300
-service-manual/system-setup-options?guid=guid-cc1
After reboot a few times, the sound card started to work
But rebooting again, the problem came back.
I tried reboots, and turning off then on.
Sometimes, it works. Sometimes it does not.
Could be related to the initialization of the sound card
Or when the system is rebooted or turned off and som
22 matches
Mail list logo
