More Problems [was: Re: Focusrite Saffire LE]
Chris Wenn
christopher.wenn at gmail.com
Wed Jun 4 11:24:45 BST 2008
> Yeah - voodoo ;-)
> try running jack from a commandline and start qjackctl afterwards (jackd
> is shown then as active all the ports can be managed as usual...)
>
> This helped the case for me at least...
The problem is that jack is crashing within a second of being started,
so by the time qjackctl has launched there's no session to attach to.
But I'm not even getting that far now:
Jun 4 20:18:44 zakalwe NetworkManager: <debug> [1212574724.900833]
nm_hal_device_added(): New device added (hal udi is
'/org/freedesktop/Hal/devices/ieee1394_guid_130e0100041bbc_0').
Jun 4 20:19:20 zakalwe kernel: [ 4666.599404] ieee1394: Node changed:
0-01:1023 -> 0-00:1023
Jun 4 20:19:20 zakalwe kernel: [ 4666.599419] ieee1394: Node suspended:
ID:BUS[0-00:1023] GUID[00130e0100041bbc]
Jun 4 20:19:22 zakalwe kernel: [ 4670.243392] ieee1394: Error parsing
configrom for node 0-00:1023
Jun 4 20:19:22 zakalwe kernel: [ 4670.244125] ieee1394: Node changed:
0-00:1023 -> 0-01:1023
Jun 4 20:19:24 zakalwe kernel: [ 4672.164836] doh, someone wants to
mess with state set
Jun 4 20:19:24 zakalwe kernel: [ 4672.303844] ieee1394: Node resumed:
ID:BUS[0-00:1023] GUID[00130e0100041bbc]
The device seems to crash - around the point the syslog message says
'Node suspended'...
This is really pissing me off. I don't want to have to go back to
windows after three years of linux use just because a device that is
listed as working WON'T WORK!
More information about the Ubuntu-Studio-users
mailing list