[20:20] <rlameiro> ScottL: after installing the wireless drivers, networking is working :D
[20:20] <rlameiro> i will always have this problem, proprietary drivers....  other than that it works great
[20:21] <rlameiro> now i found a new bug. My edirol usb isnt working on maverick, it is detected, /proc/asound  shows the card there
[20:22] <rlameiro> but when i do aplay dhw:1 something.wav, it just doesnt output nothing
[20:22] <rlameiro> In the other way my firewire works out the box
[20:22] <rlameiro> with generic kernel :DDDDD
[20:23] <rlameiro> persia: it seems the bug I was feeling about my usb edirol, isnt related only to ARM, but also to other archs
[20:24] <crimsun> you 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] <rlameiro> crimsun: I know, but even like that, the device doesn even show up on pulse
[20:24] <rlameiro> so, something is wrong
[20:25] <rlameiro> trying to start jack with it is also impossible
[20:25] <rlameiro> so I think that maybe there is some change made to maverick on the usb sound subsystem or something
[20:26] <crimsun> there are a lot of changes to usbaudio between lucid and maverick, yes
[20:26] <rlameiro> crimsun: this also happens on ARM architecture7
[20:26] <rlameiro> well, what would devs need to debug it better?
[20:27] <rlameiro> /proc/asound ?
[20:27] <crimsun> i 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/daily
[20:27] <crimsun> however, my hardware set doesn't match yours, so take that with a grain of salt
[20:27] <rlameiro> well, but this need to be fixed before launch or not?
[20:27] <crimsun> it very probably won't be; kernel changes are much too invasive at this point.
[20:28] <rlameiro> so you say that everyone using a EDirol ua-4fx and ua 25 will be out of luck ????
[20:28] <rlameiro> they are one of the most used cards 
[20:29] <rlameiro> on the low hobbyst segment at least
[20:29] <crimsun> I'm not saying that; I'm saying that kernel developer resources won't be spent fixing it before october 10th
[20:30] <rlameiro> ok :(
[20:30] <crimsun> you could try using a mainline daily build as I implied
[20:30] <rlameiro> crimsun: where can I see a change log of the modifications made to the maverick kernel from the upstream?
[20:30] <crimsun> rlameiro: sorry?
[20:30] <rlameiro> crimsun: yes i coudl, but not most of the userss
[20:31] <rlameiro> is there some place where i can look at the changes made to the mainline kernel
[20:31] <rlameiro> for maverick, of course
[20:32] <crimsun> rlameiro: anything marked SAUCE in the git changelog
[20:32] <crimsun> kernel.ubuntu.com/git
[20:32] <crimsun> look for ubuntu-maverick.git
[20:33] <crimsun> ubuntu/ubuntu-maverick.git to be precise
[20:40] <rlameiro> thanks crimsun 
[21:13] <rlameiro> found nothing special
[21:13] <rlameiro> maybe its mainline
[21:13] <rlameiro> will check in mainline
[21:18] <ScottL> thanks rlameiro 
[21:19] <rlameiro> ScottL: great work