Interesting: it wasn't working for me.
The link will need to be kernel-specific of course.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1004239
Title:
lirc installation error in Ubuntu 12.04
To
Mythbuntu 12.04 64-bit, fresh install updated to 3.2.0-25 kernel . I
don't have:
/lib/modules/3.2.0-25-generic/kernel/drivers/staging/lirc
but I do have:
/lib/modules/3.2.0-25-generic/kernel/drivers/staging/media/lirc
So workaround is to:
sudo ln -s
There is a simpler solution (no compilation required...) described here:
http://ubuntuforums.org/showthread.php?t=1214795
--
cyberlink Remote isn't available as an option
https://bugs.launchpad.net/bugs/305321
You received this bug notification because you are a member of Ubuntu
Bugs, which is
I agree with both the immediately previous comments: whilst I don't use
JACK etc. I'd suggest that the risk to other apps from the adoption of
the solution from #30 has to be greater than the pure Pulseaudio
workaround (#52/53 or whatever you want to call it).
For me that fix has been completely
I can confirm that #52/53 fixes analog playback/record also S/PDIF
playback: I can't confirm S/PDIF record because I've never put much
effort into trying to get it going...
--
Pulseaudio fails to initialize ICE1712 chipsets
https://bugs.launchpad.net/bugs/178442
You received this bug
Well, I'm a home user, I'm affected - and the issue is a right PITA...
Karmic's inability to mount NFS drives at boot is a major regression.
So if the mechanism for solving the problem is an SRU then I vote for
that solution too please.
--
retry remote devices when parent is ready after
If outputs 1 2 are OK then probably all you need to do is modify the
via-ice1712.conf (or whatever you called it) file. Take a look at the
Pulseaudio bug linked-to in #35 - there are files attached there for a
multi-output card that you should be able to modify to get yourself up
and going.
--
Franky - even if it's the same chipset the parameters you need may not be the
same as in #84. Take a look at the output of lspci -nnv - you should be able
to confirm that the card does use an ICE1712 chipset and also confirm the
parameters. You need to know:
vendor
device
subsystem_vendor
What does lspci -nnv tell you about the card?
--
Pulseaudio fails to initialize ICE1712 chipsets
https://bugs.launchpad.net/bugs/178442
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
OK - for /lib/udev/rules.d/90-pulseaudio.rules you could try:
SUBSYSTEMS==pci, ATTRS{vendor}==0x1412, ATTRS{device}==0x1712,
ATTRS{subsystem_vendor}==0x153b, ATTRS{subsystem_device}==0x1138,
ENV{PULSE_PROFILE_SET}=via-ice1712.conf
Depending on what you've called the file in
DMX6Fire - subsystem device id could be 0x1138?
(from http://envy24.svobodno.com/)
--
Pulseaudio fails to initialize ICE1712 chipsets
https://bugs.launchpad.net/bugs/178442
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
Paulo - in /lib/udev/rules.d/90-pulseaudio.rules try:
SUBSYSTEMS==pci, ATTRS{vendor}==0x1412, ATTRS{device}==0xd633,
ENV{PULSE_PROFILE_SET}=via-ice1712.conf
rather than the string above.
--
Pulseaudio fails to initialize ICE1712 chipsets
https://bugs.launchpad.net/bugs/178442
You received this
er - and when that doesn't work (as it probably won't) you could try:
SUBSYSTEMS==pci, ATTRS{vendor}==0x1412, ATTRS{device}==0x1712,
ATTRS{subsystem_vendor}==0x1412, ATTRS{subsystem_device}==0xd630,
ENV{PULSE_PROFILE_SET}=via-ice1712.conf
The trick is to correctly identify the parameters to
Ah - so much for google this time! My card's a M2496 so I couldn't check
directly.
Thanks for the /etc/udev/rules.d tip - the file does get overwritten
when it's in the the other folder.
--
Pulseaudio fails to initialize ICE1712 chipsets
https://bugs.launchpad.net/bugs/178442
You received this
Florian - the (partial) solution from #35 is still working for me - with
the restriction that Pulseaudio updates usually overwrite
/lib/udev/rules.d/90-pulseaudio.rules with a plain vanilla version so
that I have to re-edit it to get things going again.
In general (looking at the Pulseaudio bug)
David - take a look at the Pulseaudio ticket (#35 above) - it has the
udev policy info.
--
Pulseaudio fails to initialize ICE1712 chipsets
https://bugs.launchpad.net/bugs/178442
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
David - take a look at the Pulseaudio ticket (#35 above) - it has the
udev policy info.
--
Pulseaudio fails to initialize ICE1712 chipsets
https://bugs.launchpad.net/bugs/178442
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
I've been following this from upstream:
http://www.pulseaudio.org/ticket/624
Profile configuration isn't yet perfect, but for me it's a major step
forward in terms of mapping (I don't have the problem with glitch-free).
** Bug watch added: PulseAudio sound server #624
I have the same problem (Perfection 2580).
The kernel bug referenced above is marked as resolved - if this is the
cause of the problem will the fix make it into Feisty soon?
Thanks
Ian
--
scanner doesn't work with ubuntu 7.04
https://bugs.launchpad.net/bugs/94226
You received this bug
I have a similar setup and the same problem (the attached file contains
responses to commands per Bananabob's list).
** Attachment added: typescript
http://launchpadlibrarian.net/8081130/typescript
--
Unable to adjust sound levels when recording in feisty
20 matches
Mail list logo
