/srv/irclogs.ubuntu.com/2010/09/26/#ubuntustudio-devel.txt

rlameiroScottL: after installing the wireless drivers, networking is working :D20:20
rlameiroi will always have this problem, proprietary drivers....  other than that it works great20:20
rlameironow i found a new bug. My edirol usb isnt working on maverick, it is detected, /proc/asound  shows the card there20:21
rlameirobut when i do aplay dhw:1 something.wav, it just doesnt output nothing20:22
rlameiroIn the other way my firewire works out the box20:22
rlameirowith generic kernel :DDDDD20:22
rlameiropersia: it seems the bug I was feeling about my usb edirol, isnt related only to ARM, but also to other archs20:23
crimsunyou shouldn't use hw:1 unless necessary in that context; use plughw:foo where foo is the name of the device.  You'll find the name of the device from /proc/asound/cards in the brackets.20:24
rlameirocrimsun: I know, but even like that, the device doesn even show up on pulse20:24
rlameiroso, something is wrong20:24
rlameirotrying to start jack with it is also impossible20:25
rlameiroso I think that maybe there is some change made to maverick on the usb sound subsystem or something20:25
crimsunthere are a lot of changes to usbaudio between lucid and maverick, yes20:26
rlameirocrimsun: this also happens on ARM architecture720:26
rlameirowell, what would devs need to debug it better?20:26
rlameiro/proc/asound ?20:27
crimsuni don't bother to run maverick's kernel for that reason; i use the daily mainline builds of 2.6.36 from kernel.ubuntu.com/~kernel-ppa/mainline/daily20:27
crimsunhowever, my hardware set doesn't match yours, so take that with a grain of salt20:27
rlameirowell, but this need to be fixed before launch or not?20:27
crimsunit very probably won't be; kernel changes are much too invasive at this point.20:27
rlameiroso you say that everyone using a EDirol ua-4fx and ua 25 will be out of luck ????20:28
rlameirothey are one of the most used cards 20:28
rlameiroon the low hobbyst segment at least20:29
crimsunI'm not saying that; I'm saying that kernel developer resources won't be spent fixing it before october 10th20:29
rlameirook :(20:30
crimsunyou could try using a mainline daily build as I implied20:30
rlameirocrimsun: where can I see a change log of the modifications made to the maverick kernel from the upstream?20:30
crimsunrlameiro: sorry?20:30
rlameirocrimsun: yes i coudl, but not most of the userss20:30
rlameirois there some place where i can look at the changes made to the mainline kernel20:31
rlameirofor maverick, of course20:31
crimsunrlameiro: anything marked SAUCE in the git changelog20:32
crimsunkernel.ubuntu.com/git20:32
crimsunlook for ubuntu-maverick.git20:32
crimsunubuntu/ubuntu-maverick.git to be precise20:33
rlameirothanks crimsun 20:40
rlameirofound nothing special21:13
rlameiromaybe its mainline21:13
rlameirowill check in mainline21:13
ScottLthanks rlameiro 21:18
rlameiroScottL: great work21:19

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!