Dear Marcus,
this was not, as it turned out, strictly a "bug"
in Launchpad terms. In fact, as I and my Watcher Raymond discovered from
inspired research by a guy whose name I have forgotten, it started life
as a deliberate "System Restriction" approved and adopted in the
Hello Raymond,
thank you for staying with me on this.
Thanks in particular for the astonishing,
one-line -- one-fact information in this e-mail from yourself.
So surprising in fact, that it is taking me
a while
Hi Raymond,
1) as I think I mentioned, I am (obviously) not as
well up on this stuff as you. Hence my question as to where exactly I
should specify
try specify radeon.audio=1
In a moment of madness, probably due to lack of
sleep,
Hi Raymond,
1) Where is it exactly that you suggest that I
specify radeon.audio=1 ?
2) If I follow your reasoning now, you ARE
supposing that the existence of, and Jack Detection of HDMI connection
by Pulse Audio ( a subprogram of the Alsa Driver --
Public bug reported:
As the summary mentions , this is a continuation ofBug#1231730.
In order to collect all the neccessary diagnostics, with a
different hardware configuration:- that is with the original computer ( AMD
2-core ) actually CONNECTED via HDMI to the Sharp
Hello Raymond,
Confusion.Apologies.
After a pause for reflection (and to work on my car
for MOT) , It seems to me that the thrust of your remarks and questions MIGHT
be that the display of the HDMI sound option might in some way be
Public bug reported:
I have 2 computers; 1) this with Asus M2A-VMHDMI motherboard, 2core AMD CPU
and ATI HD 6000 series graphic card where I do not actually use the HDMI output
; 2) the second with Asus M4A 72 PRO
motherboard, 4core Phenom and ATI HD
This is my first bug report. I apologise for the scrambled format, presumably
due to the limitations of the editor, in a small window.
It is the bug reporting software that has labelled this as a
fault with the alsa driver. It may or may not be.
My bug initially is a
8 matches
Mail list logo
