Hello Clemens, I thought I knew what had to be done, but apparently not.
That's what I did:
- I downloaded the kernel source 4.0.4 from kernel.org
- Then I edited the mixer_maps.c file, I found an entry like this:
static struct usbmix_name_map maya44_map[] = {
/* 1: IT line */
{ 2, "Line Playback" }, /* FU */
/* 3: IT line */
{ 4, "Line Playback" }, /* FU */
/* 5: IT pcm playback */
/* 6: MU */
{ 7, "Master Playback" }, /* FU */
/* 8: OT speaker */
/* 9: IT line */
{ 10, "Line Capture" }, /* FU */
/* 11: MU */
/* 12: OT pcm capture */
{ }
};
And I duplicated, but this time I called her "maya44p_map"
I did the same with this entry:
{
.id = USB_ID(0x0a92, 0x0091),
.map = maya44_map,
},
I duplicated it well, but additionally I changed de USB ID:
{
.id = USB_ID(0x2573, 0x0008),
.map = maya44p_map,
},
I compiled and installed the kernel, I check with "uname -a", connected the sound card, I checked the logs and no errors.
Alsamixer still telling: "This sound device does not have any capture controls".
I do not know how to continue, there is a recommendation that steps go from here?
Thanks again for your time!
Regards.
That's what I did:
- I downloaded the kernel source 4.0.4 from kernel.org
- Then I edited the mixer_maps.c file, I found an entry like this:
static struct usbmix_name_map maya44_map[] = {
/* 1: IT line */
{ 2, "Line Playback" }, /* FU */
/* 3: IT line */
{ 4, "Line Playback" }, /* FU */
/* 5: IT pcm playback */
/* 6: MU */
{ 7, "Master Playback" }, /* FU */
/* 8: OT speaker */
/* 9: IT line */
{ 10, "Line Capture" }, /* FU */
/* 11: MU */
/* 12: OT pcm capture */
{ }
};
And I duplicated, but this time I called her "maya44p_map"
I did the same with this entry:
{
.id = USB_ID(0x0a92, 0x0091),
.map = maya44_map,
},
I duplicated it well, but additionally I changed de USB ID:
{
.id = USB_ID(0x2573, 0x0008),
.map = maya44p_map,
},
I compiled and installed the kernel, I check with "uname -a", connected the sound card, I checked the logs and no errors.
Alsamixer still telling: "This sound device does not have any capture controls".
I do not know how to continue, there is a recommendation that steps go from here?
Thanks again for your time!
Regards.
2015-05-18 12:12 GMT-03:00 nightmixes <nightmixes@xxxxxxxxx>:
Thanks Clemens, I think I understand what to do. I will try to do it myself, if I have a problem, I tell you.Regards.
If I have success, I will also tell you!
Thank you very much!2015-05-18 6:12 GMT-03:00 Clemens Ladisch <cladisch@xxxxxxxxxxxxxx>:nightmixes wrote:
> I wondered if the vendor:product id that appears in lsusb may be wrong
> and makes fail the Alsa or USB system to identified the device properly.
The MAYA44 indeed indeed has a workaround to change some of its mixer
controls.
> What if the device is correctly identified some years ago because I
> had a correct ID, but later the manufacturer changed the ID, leaving
> the device as unknown or configured as generic.
Your device is not called "MAYA44 USB" but "MAYA44 USB+". I don't know
what actually changed, but this would be a reason for the different ID.
The lsusb output shows that your device uses the same mixer control IDs
as the older device, so the same workaround should work.
You need to add a new entry to the file sound/usb/mixer_maps.c in the
kernel source, and recompile the kernel. Do you know how to do this in
your distribution?
Regards,
Clemens
------------------------------------------------------------------------------ One dashboard for servers and applications across Physical-Virtual-Cloud Widest out-of-the-box monitoring support with 50+ applications Performance metrics, stats and reports that give you Actionable Insights Deep dive visibility with transaction tracing using APM Insight. http://ad.doubleclick.net/ddm/clk/290420510;117567292;y
_______________________________________________ Alsa-user mailing list Alsa-user@xxxxxxxxxxxxxxxxxxxxx https://lists.sourceforge.net/lists/listinfo/alsa-user
