Bug 1413056
Summary: | PulseAudio doesn't recognize modem's sound interface [Sierra MC7304] | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 7 | Reporter: | Deepu K S <dkochuka> |
Component: | pulseaudio | Assignee: | Wim Taymans <wtaymans> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | Desktop QE <desktop-qa-list> |
Severity: | high | Docs Contact: | |
Priority: | unspecified | ||
Version: | 7.3 | CC: | cww, dkochuka, tpelka, wtaymans |
Target Milestone: | rc | Keywords: | OtherQA |
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2017-08-28 15:35:25 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | |||
Bug Blocks: | 1420851, 1472339 | ||
Attachments: |
Description
Deepu K S
2017-01-13 14:01:50 UTC
Created attachment 1240352 [details]
pulseaudio logs with "ExecStart=/bin/pulseaudio --system --daemonize --disallow-exit --disable-shm --exit-idle-time=-1 -v --log-target=newfile:/tmp/pulseverbose.log --log-time=1"
Moving out ~/.config/pulse folder and # mkdir ~/pulse-bkp # mv ~/.config/pulse/* ~/pulse-bkp Adding 'autospawn = no' in /etc/pulse/client.conf Tried above, but didn't help. To Note, We noticed that if we fully shutdown the server and boot it again, the sound card interface is visible without a modem reset. So there's a difference between a shutdown&boot and a reboot. Maybe the following bug report helps, especially comment #5: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1191898/ Some more information; During further testing we realized that the problem persists when PulseAudio runs in user mode, so the problem isn't restricted to PulseAudio in system mode. And a question: How likely it is that this problem is related to the modem's firmware instead of PulseAudio? Thanks (In reply to Deepu K S from comment #6) > And a question: How likely it is that this problem is related to the modem's > firmware instead of PulseAudio? Quite likely, especially when you need to reset the modem to make it work. That suggests that the default state of the modem is not initialized properly at the driver level. There are also these lines in the pulseaudio code for the source and sinks: if (pa_alsa_pcm_is_modem(u->pcm_handle)) { pa_log_notice("Device %s is modem, refusing further initialization.", u->device_name); goto fail; } But since you don't see those notices and things eventually work, _is_modem likely returns FALSE.. |