Re: [Alsa-user] M-Audio keystudio usb midi keyboard works on Ubuntu Studio 12.04, not on 13.10, now what ?
On Sun, Nov 3, 2013 at 11:47 PM, Robert M. Riches Jr. wrote: > Very long shot: Does it still work under 13.10 if everything is > powered off and then booted directly to 13.10? This is based on Yes, altough I only powered the keyboard down for couple of seconds. I was also thinkin that maybe 12.04 managed to install firmware, altough I do not know whether this particular keyboard requires one or not. > Another long shot: Might it be flaky physical connectors? Well, keyboard is brand new, as is the cable. Then again, stranger things have happened. Another thing... As I said the keyboard is no visible at lsusb and also in Jack and also in amidi -l (or something like that). However, Jack is unable to connect it. So is there a easy way to verify that Alsa layer is working correctly ? Some kind of midi monitor directly on top of Alsa or similar ? There are currently too many moving parts in this equation :( - Jyrki -- Android is increasing in popularity, but the open development platform that developers love is also attractive to malware creators. Download this white paper to learn more about secure code signing practices that can help keep Android apps secure. http://pubads.g.doubleclick.net/gampad/clk?id=65839951&iu=/4140/ostg.clktrk ___ Alsa-user mailing list Alsa-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/alsa-user
[Alsa-user] XMOS multichannel ref. design board - Any success stories?
Hello to all, i would like to ask you for any experience with snd-usb-audio module and this board: http://www.xmos.com/products/reference-designs/multichannel Friends had some issues, basically can't set hw params and initiate playback, with this interface and i would like to help them. So before i'll get my hands on it to do further debugging, i'd like to ask other potential users. I know, there are quite few compatible products and DIY designs based on LS-1 chip, but only with stereo SPDIF and I2S I/Os with slightly different base firmware by XMOS, but except of one thread on XMOS forum i didn't find any information about compatibility with recent snd-usb-audio driver. Thank you very much Michal -- Android is increasing in popularity, but the open development platform that developers love is also attractive to malware creators. Download this white paper to learn more about secure code signing practices that can help keep Android apps secure. http://pubads.g.doubleclick.net/gampad/clk?id=65839951&iu=/4140/ostg.clktrk ___ Alsa-user mailing list Alsa-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/alsa-user
Re: [Alsa-user] M-Audio keystudio usb midi keyboard works on Ubuntu Studio 12.04, not on 13.10, now what ?
> Date: Sun, 3 Nov 2013 20:47:23 +0200 > From: Jyrki Saarela > To: Daniel Mack > Cc: alsa-user@lists.sourceforge.net > > On Sun, Nov 3, 2013 at 12:31 PM, Daniel Mack wrote: > > Ok, then we have a good test setup to investigate on. > > Seems so, except (see below) > > > Please provide the output of 'lsusb -v' as well as a full dmesg output > > of that machine then, with the keyboard connected of course, for both > > Ubuntu versions. > > on 12.04 keyboard was listed, as expected > > > Also, what kernel does 12.04 (and 13.10, respectively) ship with again? > > Check with 'uname -a'. > > and after reboot to 13.10, it is listed there also. Nothing was > changed, now it just works. I really don't know what to say... > > Well, now there is another problem :) Neither qjackctl or Patchage can > connect the keyboard anywhere. Not to midi trough nor to qsynth. > > dmesg outputs not attached, seems that message gets too large... > > - Jyrki Very long shot: Does it still work under 13.10 if everything is powered off and then booted directly to 13.10? This is based on a wild guess that there might be firmware that gets downloaded to the device that enables 13.10 to see it. (I have a USB-attached TV tuner that enumerates as one USB device, installs firmware, disconnects as a USB device, then re-enumerates as a different USB device once it has its firmware.) Another long shot: Might it be flaky physical connectors? HTH Robert Riches (just another lurker) -- Android is increasing in popularity, but the open development platform that developers love is also attractive to malware creators. Download this white paper to learn more about secure code signing practices that can help keep Android apps secure. http://pubads.g.doubleclick.net/gampad/clk?id=65839951&iu=/4140/ostg.clktrk ___ Alsa-user mailing list Alsa-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/alsa-user
Re: [Alsa-user] M-Audio keystudio usb midi keyboard works on Ubuntu Studio 12.04, not on 13.10, now what ?
On Sun, Nov 3, 2013 at 12:31 PM, Daniel Mack wrote: > Ok, then we have a good test setup to investigate on. Seems so, except (see below) > Please provide the output of 'lsusb -v' as well as a full dmesg output > of that machine then, with the keyboard connected of course, for both > Ubuntu versions. on 12.04 keyboard was listed, as expected > Also, what kernel does 12.04 (and 13.10, respectively) ship with again? > Check with 'uname -a'. and after reboot to 13.10, it is listed there also. Nothing was changed, now it just works. I really don't know what to say... Well, now there is another problem :) Neither qjackctl or Patchage can connect the keyboard anywhere. Not to midi trough nor to qsynth. dmesg outputs not attached, seems that message gets too large... - Jyrki -- Android is increasing in popularity, but the open development platform that developers love is also attractive to malware creators. Download this white paper to learn more about secure code signing practices that can help keep Android apps secure. http://pubads.g.doubleclick.net/gampad/clk?id=65839951&iu=/4140/ostg.clktrk ___ Alsa-user mailing list Alsa-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/alsa-user
Re: [Alsa-user] M-Audio keystudio usb midi keyboard works on Ubuntu Studio 12.04, not on 13.10, now what ?
On 11/03/2013 11:05 AM, Jyrki Saarela wrote: > On Sun, Nov 3, 2013 at 11:34 AM, Daniel Mack wrote: >> If it's not listen in lsusb, it's not an ALSA problem. Are you >> completely sure about that? Can you double-check with another machine maybe? >> >> Are there any dmesg messages added when the device is plugged in? > > > Well, it works with this machine with ubuntu 12.04 :) Ok, then we have a good test setup to investigate on. Please provide the output of 'lsusb -v' as well as a full dmesg output of that machine then, with the keyboard connected of course, for both Ubuntu versions. Also, what kernel does 12.04 (and 13.10, respectively) ship with again? Check with 'uname -a'. Thanks, Daniel -- Android is increasing in popularity, but the open development platform that developers love is also attractive to malware creators. Download this white paper to learn more about secure code signing practices that can help keep Android apps secure. http://pubads.g.doubleclick.net/gampad/clk?id=65839951&iu=/4140/ostg.clktrk ___ Alsa-user mailing list Alsa-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/alsa-user
Re: [Alsa-user] M-Audio keystudio usb midi keyboard works on Ubuntu Studio 12.04, not on 13.10, now what ?
On Sun, Nov 3, 2013 at 11:34 AM, Daniel Mack wrote: > If it's not listen in lsusb, it's not an ALSA problem. Are you > completely sure about that? Can you double-check with another machine maybe? > > Are there any dmesg messages added when the device is plugged in? Well, it works with this machine with ubuntu 12.04 :) I do have a spare laptop, but it does not boot from cd (broken) nor from usb stick (too old machine...) :) Anyway, jsaarela@Paranoid:~$ dmesg | tail; lsusb [ 15.309813] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready [ 18.152299] wlan0: authenticate with ac:22:0b:ba:44:e8 [ 18.167515] wlan0: send auth to ac:22:0b:ba:44:e8 (try 1/3) [ 18.169063] wlan0: authenticated [ 18.171753] wlan0: associate with ac:22:0b:ba:44:e8 (try 1/3) [ 18.175848] wlan0: RX AssocResp from ac:22:0b:ba:44:e8 (capab=0x411 status=0 aid=2) [ 18.176020] wlan0: associated [ 18.176075] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready [ 18.254434] init: plymouth-stop pre-start process (1446) terminated with status 1 [ 19.810168] init: cups-browsed main process ended, respawning Bus 002 Device 002: ID 064e:e263 Suyin Corp. Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 002: ID 046d:c52f Logitech, Inc. Unifying Receiver Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub plug in the keyboard: jsaarela@Paranoid:~$ dmesg | tail; lsusb [ 15.309813] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready [ 18.152299] wlan0: authenticate with ac:22:0b:ba:44:e8 [ 18.167515] wlan0: send auth to ac:22:0b:ba:44:e8 (try 1/3) [ 18.169063] wlan0: authenticated [ 18.171753] wlan0: associate with ac:22:0b:ba:44:e8 (try 1/3) [ 18.175848] wlan0: RX AssocResp from ac:22:0b:ba:44:e8 (capab=0x411 status=0 aid=2) [ 18.176020] wlan0: associated [ 18.176075] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready [ 18.254434] init: plymouth-stop pre-start process (1446) terminated with status 1 [ 19.810168] init: cups-browsed main process ended, respawning Bus 002 Device 002: ID 064e:e263 Suyin Corp. Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 002: ID 046d:c52f Logitech, Inc. Unifying Receiver Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub jsaarela@Paranoid:~$ Modprobing snd-usb-audio manually does not help either. Nor plugging kbd in and turning it on after plugging, or leaving kbd on and just plugging it in. Plugging a usb memory stick to same port produces expected results, stick is visible at dmesg and lsusb, and it can be mounted, so the port itself should be quite ok. So something is clearly broken somewhere, but as I don't have slightest idea how the current usb subsystem should work I really don't know where to start looking. - Jyrki -- Android is increasing in popularity, but the open development platform that developers love is also attractive to malware creators. Download this white paper to learn more about secure code signing practices that can help keep Android apps secure. http://pubads.g.doubleclick.net/gampad/clk?id=65839951&iu=/4140/ostg.clktrk ___ Alsa-user mailing list Alsa-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/alsa-user
[Alsa-user] ALC668: no sound through speakers (except once, don't know what I did)
Hello! I bought a new laptop, Asus n550jv. For some reason, I don't have sound through the speakers. Except once, in which I don't know what happened for the sound to start to work. I've uploaded ALSA script information to http://www.alsa-project.org/db/?f=f0529130fd9a0539dfbe370ca4704c584c6545d3 . I've tried snd_hda_intel model=generic and model=asus-mode4 . speakers_test -c6 -twav doesn't output any sound through the speakers (except the one time they worked). The kernel hasn't changed. Does anyone know what can I try to get it to work? Thanks in Advance, -- Pedro -- Android is increasing in popularity, but the open development platform that developers love is also attractive to malware creators. Download this white paper to learn more about secure code signing practices that can help keep Android apps secure. http://pubads.g.doubleclick.net/gampad/clk?id=65839951&iu=/4140/ostg.clktrk ___ Alsa-user mailing list Alsa-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/alsa-user
Re: [Alsa-user] M-Audio keystudio usb midi keyboard works on Ubuntu Studio 12.04, not on 13.10, now what ?
On 11/03/2013 10:06 AM, Jyrki Saarela wrote: > Title pretty much says it all. On 12.04 it just works, on 13.10 it is > not even listed at lsusb. If it's not listen in lsusb, it's not an ALSA problem. Are you completely sure about that? Can you double-check with another machine maybe? Are there any dmesg messages added when the device is plugged in? Daniel -- Android is increasing in popularity, but the open development platform that developers love is also attractive to malware creators. Download this white paper to learn more about secure code signing practices that can help keep Android apps secure. http://pubads.g.doubleclick.net/gampad/clk?id=65839951&iu=/4140/ostg.clktrk ___ Alsa-user mailing list Alsa-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/alsa-user
[Alsa-user] M-Audio keystudio usb midi keyboard works on Ubuntu Studio 12.04, not on 13.10, now what ?
Title pretty much says it all. On 12.04 it just works, on 13.10 it is not even listed at lsusb. Tried googling without much help. So where do I start debugging this ? Or should I ask this at -devel -list instead ? - Jyrki -- Android is increasing in popularity, but the open development platform that developers love is also attractive to malware creators. Download this white paper to learn more about secure code signing practices that can help keep Android apps secure. http://pubads.g.doubleclick.net/gampad/clk?id=65839951&iu=/4140/ostg.clktrk___ Alsa-user mailing list Alsa-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/alsa-user
Re: [Alsa-user] [alsa-devel] hdmi sound rerouted?
> - Original Message - > From: Deucher, Alexander > Sent: 10/19/13 03:59 PM > To: Dagg Stompler, Takashi Iwai > Subject: RE: [alsa-devel] [Alsa-user] hdmi sound rerouted? > > > -Original Message- > > > From: Dagg Stompler [mailto:da...@gmx.com] > > > Sent: Saturday, October 19, 2013 5:49 AM > > > To: Takashi Iwai; Deucher, Alexander > > > Cc: Clemens Ladisch; alsa-user@lists.sourceforge.net; alsa-devel@alsa- > > > project.org > > > Subject: Re: [alsa-devel] [Alsa-user] hdmi sound rerouted? > > > > > > > - Original Message - > > > > From: Takashi Iwai > > > > Sent: 10/08/13 10:49 AM > > > > To: Deucher, Alexander > > > > Subject: Re: [alsa-devel] [Alsa-user] hdmi sound rerouted? > > > > > > > > At Mon, 7 Oct 2013 13:36:24 +, > > > > Deucher, Alexander wrote: > > > > > > > > > > > -Original Message- > > > > > > From: Takashi Iwai [mailto:ti...@suse.de] > > > > > > Sent: Monday, September 30, 2013 5:18 AM > > > > > > To: Deucher, Alexander > > > > > > Cc: Clemens Ladisch; Dagg Stompler; alsa-user@lists.sourceforge.net; > > > alsa- > > > > > > de...@alsa-project.org > > > > > > Subject: Re: [alsa-devel] [Alsa-user] hdmi sound rerouted? > > > > > > > > > > > > At Mon, 30 Sep 2013 02:23:22 +, > > > > > > Deucher, Alexander wrote: > > > > > > > > > > > > > > > -Original Message- > > > > > > > > From: Clemens Ladisch [mailto:cladi...@googlemail.com] > > > > > > > > Sent: Saturday, September 28, 2013 6:33 PM > > > > > > > > To: Dagg Stompler > > > > > > > > Cc: alsa-user@lists.sourceforge.net; Deucher, Alexander; alsa- > > > > > > devel@alsa- > > > > > > > > project.org > > > > > > > > Subject: Re: [Alsa-user] [alsa-devel] hdmi sound rerouted? > > > > > > > > > > > > > > > > Dagg Stompler wrote: > > > > > > > > >> da...@gmx.com wrote: > > > > > > > > >>> card 0: PCH [HDA Intel PCH], device 3: HDMI 0 [HDMI 0] > > > > > > > > >>> card 1: Generic [HD-Audio Generic], device 3: HDMI 0 [HDMI 0] > > > > > > > > >>> card 2: HDMI [HDA ATI HDMI], device 3: HDMI 0 [HDMI 0] > > > > > > > > >> > > > > > > > > >> The second one is called "Generic" because your kernel does not > > > (yet) > > > > > > > > >> know the hardware. > > > > > > > > >> > > > > > > > > >>> 01:00.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] > > > Cedar > > > > > > > > HDMI Audio [Radeon HD 5400/6300 Series] > > > > > > > > >>> 06:00.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] > > > RV635 > > > > > > > > HDMI Audio [Radeon HD 3600 Series] > > > > > > > > >> > > > > > > > > >> These are the HDMI outputs of *two* graphics cards. The first > > > one's > > > > > > > > >> model is so new that the driver doesn't know it. > > > > > > > > > > > > > > > > > > the 3600 doesn't have hdmi socket so I think it is irrelevant > > > > > > > > for my > > > issue. > > > > > > > > > > > > > > > > The RV635 chip does support HDMI outputs (even if none are > > > actually > > > > > > > > connected), so the corresponding PCI device shows up here. > > > > > > > > > > > > > > > > >>> If you update the kernel, you will get two devices named "HDA > > > ATI > > > > > > > > HDMI". > > > > > > > > > > > > > > > > > > upgrade to where? > > > > > > > > > > > > > > > > Oops. Even the latest driver lacks the PCI IDs of many HDMI HDA > > > devices > > > > > > > > (aa50/aa58/aa60/aa68/aa80/aa88/aa90/aa98: > > > > > > > > Cypress/Juniper/Redwood/Cedar/ > > > > > > > > Cayman+Antilles/Barts/Turks/Caicos). > > > > > > > > > > > > > > > > Alex, are these devices that require disabling snooping? > > > > > > > > > > > > > > Sorry what does snooping mean in this context? > > > > > > > > > > > > Most of HD-audio controller have a snoop control, but the recent AMD > > > > > > HDMI audio controller don't have the feature, thus the driver must use > > > > > > the non-cached pages. At least, PCI ID 1002:aaa0, aaa8 and aab0 are > > > > > > known to require such. > > > > > > > > > > > > Now the question is whether all new chips above (aa50,...) require the > > > > > > same workaround, too. Could you check this or forward the inquiry to > > > > > > someone in AMD? > > > > > > > > > > According to our internal teams, disabling snooping is only required on > > > the audio parts included in Evergreen and Northern Islands GPUs. Older chips > > > like R7xx (aa48) and newer chips like Southern Islands (aaa0) are able to > > use > > > snooping. I'm not real familiar with the audio portions of the GPUs so if > > you > > > need further clarification, let me know. > > > > > > > > Thanks for the information. > > > > > > > > Though, it's strange that the information doesn't match with what I've > > > > heard (and also with what I've tested with a laptop). I've heard that > > > > it's Southern Island HDMI that needs the snoop-disablement. > > > > > > > > Could you ask again whether it's really Evergreen / Nothern Islands? > > > > > > > > > >
