jegunn <jeg@...> writes: > > Some more info on the sequencing: On the C7 machine, the results are not > consistent. There seems no way to be sure it will work; usually > (re-)booting with both the computer and the QB9 powered up and connected > works, but not always. Interestingly, it seems to be most reliable when > one shuts down with something playing, so as soon as the state file is > read on startup, playback resumes. Plugging in the USB from the QB9 with > it powered sometimes works. Clearly some weird timing problem. It may be > interesting that the failure mode is different on the two machines; on the > C7, I do not get ANY error message when I plug in the powered-up QB9, the > dashes appear on the screen, but nothing will play. Thought it might have > something to do with the timing of loading/registering snd-usb-audio, but > does not help to load it before connecting. > > My QB9 is brand-new, and I gather from other posts that, in agreement with > Nick, the early models with the USB2 interface just worked; there must > have been some change.
Dear Jim, Muchas gratias. The day before yesterday, doing an exercise of 'updating the kernel' which at that moment I thought was useless has now proven to be very valuable. I was running kernel 2.6.32 and I've updated to 2.6.38.5. In the older kernel setting the switch to class 2 did not work at all (probably a too old alsa driver). However, at your suggestion setting it to class 2 with the new kernel works beautifully. I have not experienced any of the remaining problems you described (yet). In response your last remark. My QB9 is from the first batch with the updated USB2 interface arriving in the Netherlands and I have this problem too, soo that can't be it. However, assuming Nick is the same Nick from computeraudiophile.com I noticed the following in the dmesg output: [ 9175.194164] usb 6-2: SerialNumber: (C) 2010 XMOS/Wavelength Audio Mine on the other hand says: [ 783.249135] usb 3-2: SerialNumber: Streamlength(tm) The same goes for Frank. Now I think this is related to a difference in firmware and perhaps an indicator of problems to come. Would you guys mind checking which serialnumber is displayed in dmesg and post it back? Kind regards, Maarten ps. I'm not running Voyage but Debian. But since we're all experiencing the same problem . . . ps. I hope this message doesn't show up twice but there seems to be an issue with my message actually arriving at this group. _______________________________________________ Voyage-linux mailing list [email protected] http://list.voyage.hk/mailman/listinfo/voyage-linux
