[02:38] <thraxil> trying to get an m-audio firewire solo working on maverick
[02:38] <thraxil> it was working under lucid
[02:39] <thraxil> i plug it in and dmesg says "firewire_core: phy config: card 0, new root=ffc1, gap_count=5"
[02:39] <thraxil> "firewire_core: created device fw1: GUID 000d6c0b00e2e0cf, S400, 1 config ROM retries"
[02:40] <thraxil> but i'm not seeing a /dev/raw1394
[02:40] <ailo> thraxil: put this in /etc/udev/rules.d/ http://git.debian.org/?p=pkg-multimedia/ffado.git;a=blob_plain;f=debian/60-ffado.rules
[02:41] <ailo> Don't have a device myself, so I can't check. We discussed this a couple of days ago.
[02:41] <thraxil> ok
[02:41] <ailo> And reboot to load the rules
[02:42] <thraxil> alright. i'll try that out
[02:42] <ailo> or the file should be /etc/udev/rules.d/60-ffado.rules of course
[02:42] <thraxil> jackd -d firewire is also telling me "no such driver firewire"
[02:42] <thraxil> not sure if that's the same problem
[02:43] <thraxil> but i'll try this first
[02:43] <holstein> thraxil: as a trouble shooting step
[02:43] <holstein> i like to run
[02:43] <holstein> sudo qjackctl
[02:43] <holstein> and see if JACK starts
[02:44] <holstein> can narrow down the search
[02:44] <thraxil> nope
[02:44] <thraxil> no luck with sudo qjackctl
[02:44] <holstein> thraxil: go to setup
[02:45] <holstein> sample rate 44100
[02:45] <holstein> frames/period 512
[02:45] <holstein> periods/buffer 3
[02:45] <holstein> double check that you have the firewire driver selected
[02:45] <thraxil> yep
[02:45] <thraxil> can't start jackd
[02:46] <holstein> who said start JACK ;)
[02:46] <thraxil> unknown driver "firewire"
[02:46] <thraxil> in the messages window from qjackctl
[02:46] <holstein> thraxil: go ahead and spit out what you got
[02:46] <holstein> in that message window
[02:47] <holstein> in a paster
[02:47] <holstein> ailo: this would temporarily get aroudn that file right?
[02:48] <holstein> maybe its the kernel... i had to get a RT kernel for mine to work
[02:48] <holstein> and i dont remember what the errors were....
[02:48] <thraxil> http://dpaste.com/294741/
[02:49] <ailo> right, it's also depending on the kernel. I've already forgotten most of what we did :)
[02:49] <thraxil> i've got: 2.6.35-24-generic #42-Ubuntu SMP Thu Dec 2 02:41:37 UTC 2010 x86_64 GNU/Linux
[02:50] <holstein> thraxil: you mind trying a different kernel?
[02:50] <ailo> The easy solution is to keep Lucid and wait with upgrading until Natty
[02:50] <holstein> i needed it with my firewire device
[02:50] <thraxil> well, it's already upgraded to maverick and i mostly use this machine as my desktop, so i don't really want to go back to lucid
[02:50] <holstein> http://jackschnippes.freeunix.net/index.php/2010/11/04/lowlatency-kernel-and-realtime-kernel-for-ubuntu-10-10-maverick
[02:51] <thraxil> i'm hesitant to switch to an rt kernel because i use the nvidia drivers for dual monitor stuff
[02:51] <holstein> AH
[02:51] <holstein> well, i couldnt get any joy without it
[02:51] <holstein> and neither could another FW user
[02:51] <holstein> the other day
[02:52] <holstein> thraxil: let me get a bug for you to add yourself to if you dont mind...
[02:54] <holstein> https://bugs.launchpad.net/ubuntustudio/+bug/695893
[02:54] <ubottu> Ubuntu bug 695893 in Ubuntu Studio "JACK wont start with presonus firepod and generic kernel" [Undecided,Confirmed]
[02:58] <thraxil> ok. i'm going to try the udev change first
[03:00] <holstein> right
[03:00] <holstein> and you shoud
[03:00] <holstein> should*
[03:00] <holstein> BUT im afraid sudo would get around that
[03:00] <holstein> let us know though
[03:17] <thraxil> no luck with the udev stuff
[03:18] <thraxil> it's still not creating that /dev/raw1394
[03:18] <thraxil> and jackd still won't start. firewire or no
[03:18] <thraxil> sudo or not, i mean
[03:20] <ailo> Here's a good page. https://help.ubuntu.com/community/FireWire
[03:20] <thraxil> that's what i've been following
[03:21] <ailo> ok
[03:21] <thraxil> it pretty much starts with "ls -al /dev/raw1394"
[03:21] <thraxil> and i get ls: cannot access /dev/raw1394: No such file or directory
[03:23] <holstein> thraxil: check lspci
[03:23] <holstein> maybe your FW is not there
[03:23] <holstein> or unsupported/blacklisted
[03:23] <ailo> How about this command?        lsmod | grep 'firewire\|1394'
[03:23] <thraxil> ieee1394               95219  1 sbp2
[03:23] <thraxil> firewire_ohci          24615  0
[03:23] <thraxil> firewire_core          54327  1 firewire_ohci
[03:23] <thraxil> crc_itu_t               1739  1 firewire_core
[03:24] <thraxil> and it was working with Lucid (and Karmic, and Hardy)
[03:24] <holstein> thraxil: what chipset?
[03:24] <holstein> not that that should make this error happen...
[03:24] <thraxil> so i'd be a bit surprised if it suddenly became blacklisted
[03:24] <ailo> thraxil: according to the page, you should not be using /dev/raw1394, so that's fine
[03:25] <ailo> Check out the chapter: Driver Confusion: FireWire stacks explained
[03:27] <ailo> I can only confirm from Natty, that raw1394 is blacklisted
[03:27] <ailo> because we want to use the new stack instead
[03:27] <ailo> The blacklist file is /etc/modprobe.d/blacklist-firewire.conf
[03:28] <thraxil> grep 'firewire\|1394' /proc/interrupts
[03:28] <thraxil> says that firewire_ohci is in charge
[03:29] <thraxil> i unloaded sbp2 and ieee1394
[03:29] <ailo> so, according to that page you can switch between the new stack and the old one.
[03:29] <thraxil> so now it's just firewire_ohci, firewire_core, and crc_itu_t
[03:30] <ailo> Again, I have no way of testing this stuff myself..
[03:30] <thraxil> ie, new stack exactly as it says there
[03:30] <ailo> I think it's the new stack that may be giving you problems on that kernel.
[03:31] <thraxil> ok
[03:31] <ailo> How about trying to switch? Just follow the instructions at "Switching bewteen stacks".
[03:31] <thraxil> yep
[03:31] <thraxil> ok. /dev/raw1394 shows up now
[03:32] <thraxil> audio group, which i'm in
[03:32] <thraxil> crw-rw---- 1 root audio 171, 0 2011-01-05 22:31 /dev/raw1394
[03:32] <ailo> And jack?
[03:32] <thraxil> jackd -dfirewire is still saying: Unknown driver "firewire"
[03:33] <ailo> How about sudo qjackctl?
[03:33] <thraxil> same
[03:34] <holstein> im not ugrading to anything on my production box
[03:34] <holstein> maybe 12.04
[03:36] <ailo> thraxil: you sure that the other stack is unloaded now?
[03:36] <thraxil> $ lsmod | grep 'firewire\|1394'
[03:36] <thraxil> raw1394                25814  0
[03:36] <thraxil> ohci1394               30338  0
[03:36] <thraxil> ieee1394               95219  2 raw1394,ohci1394
[03:38] <thraxil> jackd doesn't want to run with any backend
[03:38] <thraxil> not even alsa or pulseaudio
[03:38] <ailo> That's strange.
[03:39] <thraxil> just "Unknown driver "alsa"" or whatever
[03:39] <ailo> Do have a browser open with loaded flashplayer or something
[03:39] <thraxil> nope
[03:39] <ailo> Something maby be occupying th card
[03:39] <ailo> Jack from the standard repo?
[03:40] <thraxil> i assume
[03:41] <holstein> hmmm
[03:41] <holstein> interesting
[03:41] <thraxil> i did the "basics" apt-get from https://help.ubuntu.com/community/UbuntuStudioPreparation
[03:41] <holstein> thraxil: dummy?
[03:41] <holstein> thast telling
[03:41] <holstein> thats*
[03:41] <holstein> i still think you'll want an RT kernel
[03:41] <thraxil> runs with dummy
[03:41] <holstein> BUT thats telling
[03:42] <holstein> WTH
[03:43] <thraxil> could there be old backend libraries on the system somewhere that it's finding first and that don't work with this version of jack?
[03:44] <ailo> holstein: you have a 10.10, right. Did you ever try with the generic kernel?
[03:44] <holstein> thraxil: you did an upgrade?
[03:44] <thraxil> yeah, i've upgraded this machine since... probably gutsy
[03:44] <holstein> hmmm
[03:44] <holstein> thraxil: good for you
[03:46] <holstein> ailo: let me try it
[03:48] <ailo> thraxil: so you don't even have desktop audio?
[03:48] <thraxil> yeah
[03:48] <thraxil> desktop audio works great
[03:49] <thraxil> just can't jackd to talk to my external firewire interface
[03:49] <ailo> And not to your alsa card either?
[03:49] <thraxil> my alsa card doesn't have XLR inputs
[03:50] <thraxil> and, yeah, jackd doesn't seem to want to talk to anything right now
[03:50] <holstein> ailo: no good
[03:50] <holstein> fairly modest JACK settings
[03:51] <holstein> im going to reboot into the RT kernel
[03:51] <ailo> holstein: but you can get alsa running at least, right?
[03:51] <holstein> without changing anything
[03:51] <holstein> and i'll go back
[03:51] <thraxil> alsa on its own is fine
[03:51] <thraxil> but jackd with the alsa backend fails
[03:51] <ailo> I mean from jack :)
[03:51] <holstein> its a strage issue too
[03:51] <holstein> its like it wants to start
[03:52] <holstein> and i have a light that turns blue
[03:52] <holstein> that turns blue
[03:52] <holstein> jack hesitates for a while
[03:52] <holstein> at least 6 seconds
[03:52] <holstein> then just POW
[03:53] <holstein> but its runnning fine with RT
[03:53] <ailo> thraxil: how about /etc/security/limits.conf ? Do you have settings for the audio group there?
[03:53] <ailo> Cause if you have, those should be removed.
[03:54] <thraxil> nope
[03:54] <holstein> let me check natty
[03:54] <thraxil> just in limits.d/audio.conf
[03:54] <holstein> while im here
[03:55] <ailo> Well, ff on Maverick is tough, but jack/alsa is mystic. I would like to solve that first.
[03:57] <ailo> thraxil: So, you have a builtin card on your desktop? Can you get jackd started from the command line by doing: jackd -d alsa
[03:57] <thraxil> Unknown driver "alsa"
[03:58] <ailo> right
[03:58] <holstein> natty is not happy
[03:58] <holstein> something glitchy with apt going on
[03:59] <ailo> natty is buggy
[04:00] <holstein> its been over 2 weeks since i updated too
[04:00] <holstein> im going to try and force some update
[04:02] <ailo> thraxil: perhaps you could discuss the jack/alsa problem on #jack. I'm googling a bit, but not finding anything useful yet.
[04:03] <thraxil> k. thanks.
[04:03] <thraxil> i think i've had about enough for tonight :)
[04:04] <ailo> Well, as for firewire, I'm still to hear of someone getting it working on the generic kernel But jack/alsa should of course work.
[04:46] <holstein> tanders12: not you again ;)
[04:46] <holstein> ailo: no luck on natty
[04:46] <tanders12> holstein: hehehe
[04:46] <tanders12> only good news this time
[04:46] <holstein> AH
[04:46] <holstein> good
[04:47] <tanders12> got everything working a couple days ago. Haven't messed with it for while now actually
[04:47] <ailo> tanders12: I seem to remeber I had something I was supposed to tell you, but can't remember what it was :(
[04:47] <tanders12> trying to decide whether to work on that or android right now
[04:47] <holstein> tanders12: congrats
[04:47] <tanders12> ailo: If you're like me you'll remember as soon as I'm gone ;)
[04:49] <ailo> holstein: according to asmo on the -dev list he didn't do any fixes to get firewire working.
[04:49] <ailo> But, he's getting back on that
[04:49] <holstein> cool
[04:49] <holstein> i added to my bug
[04:50] <ailo> holstein: so did you do all the other usual stuff, audio groups etc..
[04:50] <holstein> i just tried sudo qjackctl
[04:50] <holstein> first thing
[04:50] <ailo> ok
[04:50] <holstein> then it was kinda stuck
[04:50] <holstein> i couldnt seem to kill jack
[04:50] <holstein> without restarting
[04:50] <holstein> and i gave up on it
[04:50] <tanders12> seems like I ran into that a couple times
[04:50] <ailo> And it's aboganis kernel?
[04:50] <tanders12> if i recall
[04:50] <holstein> i'll see if alsa starts
[04:51] <holstein> ailo: no, just generic
[04:51] <ailo> Ok
[04:51] <holstein> i'll try alsa and the other kernel soon
[04:51] <ailo> Cause in the generic there's the cgroup problem
[04:51] <holstein> might be next week
[04:51] <ailo> You should be able to start jackd with alsa, but not getting rt rights
[04:51] <ailo> So, for now, only aboganis kernel should be used for rt
[04:52] <ailo> On aboganis the cgroups are turned off
[04:54] <ailo> holstein: I'm assuming udev rules will still be needed, though
[04:57] <holstein> we'll see
[04:57] <holstein> i just might make some noise about it
[04:57] <holstein> so FW users can use ubuntustudio
[04:57] <holstein> after doing a few work arounds at least
[04:58] <ailo> The cgroup stuff is discussed between the audio community and the kernel people, and they're discussing how to solve it
[04:58] <tanders12> there just aren't enough ppl doing high-end audio on linux :/
[04:59] <tanders12> just a few dedicated devs keeping things running
[15:43] <virtu> hi... =)
[15:43] <virtu> finally everything is nice here with my mom´s computer
[16:01] <holstein> virtu: o/
[16:01] <holstein> good to hear
[16:04] <virtu> holstein: changed the video card and it worked liked a charm, so my mom decided to give her computer to a placed that cares old people (dont know the name in english)
[16:04] <virtu> then, for a few bucks she got a new one...
[16:06] <virtu> yesterday I got this new one and installed some software... she loves it and the place where she gave her old desktop are very happy because now they can do admin task with a computer