[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <b38b5947482a5ca4b55e0ddb908c2f34@tuxedo.de>
Date: Wed, 02 Oct 2024 10:21:22 +0200
From: Christoffer Sandberg <cs@...edo.de>
To: Takashi Iwai <tiwai@...e.de>
Cc: Jerry Luo <jerryluo225@...il.com>, christian@...sel.eu,
linux-kernel@...r.kernel.org, linux-sound@...r.kernel.org, perex@...ex.cz,
regressions@...ts.linux.dev, wse@...edocomputers.com
Subject: Re: [REGRESSION][BISECTED] Audio volume issues since 4178d78cd7a8
On 30.9.2024 09:44, Takashi Iwai wrote:
> On Mon, 23 Sep 2024 21:37:42 +0200,
> Jerry Luo wrote:
>>
>>
>> Hi Takashi,
>>
>> On Mon, 16 Sep 2024 19:22:05 +0200,
>>
>> Takashi Iwai wrote:
>>
>> Could you give alsa-info.sh output from both working and
>> non-working
>> cases? Run the script with --no-upload option and attach the
>> outputs.
>>
>> thanks,
>>
>> Takashi
>>
>> Issue now reappear, output from alsa-info.sh are attached. If they are
>> still
>> needed.
>
> Thanks. The obvious difference seems to be the assignment of two DACs
> 0x10 and 0x11 for headphone and speaker outputs.
>
> Christoffer, how are those on your machines?
I attached alsa-info from the Sirius Gen2 device.
Comparing the working/nonworking of Jerry, yeah, the assignment of 0x10
and 0x11 looks switched around. I don't see what difference this would
make. Also, node 0x22 has "bass speaker" controls in the non-working
version.
Comparing the Sirius Gen2 alsa-info with Jerrys, to me it looks like the
non-working version corresponds to our working version.
I would expect the non-working version to happen all the time though
with regards to the "bass speaker" controls. Why would this only happen
sometimes?
Christoffer
View attachment "alsa-info-sirius-gen2.txt" of type "text/plain" (63557 bytes)
Powered by blists - more mailing lists