FAQ Search Today's Posts Mark Forums Read
» Video Reviews

» Linux Archive

Linux-archive is a website aiming to archive linux email lists and to make them easily accessible for linux users/developers.


» Sponsor

» Partners

» Sponsor

Go Back   Linux Archive > 64 Studio > 64 Studio User

 
 
LinkBack Thread Tools
 
Old 07-16-2008, 10:58 AM
Ralf Mardorf
 
Default Solved: Jack won't start any more

Hi again

Very strange, I deleted "/usr/bin/killall artsd &" in the server path,
so now there is only "/usr/bin/jackd" and now Jack and Jackbridge seems
to be fine again. Reaper could play. I never noticed that "RT" is
blinking in Jacks transport display, now it does.

How can it be, that Jack was fine with killall artsd before and isn't now?

Phew, I don't need to buy a Windows .

Cheers,
Ralf

> Hi
>
> I installed a SATA HDD.
> Installed Suse 11.0 on that HDD and run Suse 11.0's Jack.
> Disabled and enabled the old IDE HDD and the new SATA HDD in the BIOS.
> Copied data and 64 Studio from the old IDE HDD to the new SATA HDD by
> Suse 11.0 and Gadmin-Rsync, but I didn't change anything for 64 Studio,
> excepted the fstab for the copied version.
>
> Jack for Suse 11.0 is still fine.
> Jack for the copied 64 Studio isn't fine.
> Jack for the original 64 Studio ISN'T fine ANY MORE.
>
> Audio is fine for You Tube. No sound server or daemon like arts is running.
>
> QJackCtl's messages:
>
> "12:02:14.305 Patchbay deactivated.
>
> 12:02:14.348 Statistics reset.
>
> 12:02:14.419 ALSA connection graph change.
>
> 12:02:18.541 ALSA connection change.
>
> 12:02:30.788 Startup script...
>
> 12:02:30.789 artsshell -q terminate
>
> 12:02:31.305 Startup script terminated with exit status=256.
>
> 12:02:31.306 JACK is starting...
>
> 12:02:31.307 /usr/bin/killall artsd & /usr/bin/jackd -R -dalsa -r44100
> -p1024 -n2 -D -Chw:0 -Phw:0
>
> 12:02:31.321 JACK was started with PID=3987.
>
> R: unknown signal; killall -l lists signals.
>
> 12:02:31.324 JACK was stopped with exit status=1.
>
> 12:02:31.324 Post-shutdown script...
>
> 12:02:31.324 killall jackd
>
> jackd: no process killed
>
> 12:02:31.733 Post-shutdown script terminated with exit status=256.
>
> 12:02:33.353 Could not connect to JACK server as client. - Overall
> operation failed. - Unable to connect to server. Please check the
> messages window for more info."
>
>
> The terminal's message:
>
> "spinymouse@64studio:~$ qjackctl
> Warning: no locale found: /usr/share/locale/qjackctl_en_US.qm
> spinymouse@64studio:~$"
>
> Devices are like they where before, when Jack was fine. TerraTec hw:0,
> USB-MIDI hw:2, no other audio devices.
>
> What might be wrong now? Troubles because any interrupt might has changed?
>
> 64studio:/home/spinymouse# hwinfo --sound
> 30: PCI 306.0: 0401 Multimedia audio controller
> [Created at pci.296]
> UDI: /org/freedesktop/Hal/devices/pci_1412_1712
> Unique ID: Kaa7.J4wu6rKmng4
> Parent ID: qscc.ULOo3yhA66C
> SysFS ID: /devices/pci0000:00/0000:00:14.4/0000:03:06.0
> SysFS BusID: 0000:03:06.0
> Hardware Class: sound
> Model: "TERRATEC EWX 24/96"
> Vendor: pci 0x1412 "VIA Technologies Inc."
> Device: pci 0x1712 "ICE1712 [Envy24] PCI Multi-Channel I/O Controller"
> SubVendor: pci 0x153b "TERRATEC Electronic GmbH"
> SubDevice: pci 0x1130 "EWX 24/96"
> Revision: 0x02
> Driver: "ICE1712"
> Driver Modules: "snd_ice1712"
> I/O Ports: 0xcf00-0xcf1f (rw)
> I/O Ports: 0xce00-0xce0f (rw)
> I/O Ports: 0xcd00-0xcd0f (rw)
> I/O Ports: 0xcc00-0xcc3f (rw)
> IRQ: 21 (12038 events)
> Module Alias: "pci:v00001412d00001712sv0000153Bsd00001130bc04sc0 1i00"
> Driver Info #0:
> Driver Status: snd_ice1712 is active
> Driver Activation Cmd: "modprobe snd_ice1712"
> Config Status: cfg=new, avail=yes, need=no, active=unknown
> Attached to: #23 (PCI bridge)
> 64studio:/home/spinymouse#
>
> The IRQ for the TerraTec is still the same, that interrupt didn't change.
>
> Don't care about the patchbay, it's just because there is missing a
> snapshot like before, when Jack was fine. I got this error "Could not
> load patchbay definition file: "/home/spinymouse/New Folder/test.xml""
> before, when Jack was fine.
>
> It's not only that I didn't make any changes for 64 Studio, I also
> didn't run 64 Studio, because I was running the new Suse 11.0. Because
> You Tube's audio is fine with Iceweasel, there seems to be no troubles
> with ALSA.
>
> Why is'n Jack fine any more for 64 Studio, without making any changes,
> even without running 64 Studio? Any ideas?
>
> I thought after spending a lot of money and time for Linux and having a
> stable 64 Studio, I could make music, but now without changing 64
> Studio, it's unstable.
>
> Cheers,
> Ralf
>

_______________________________________________
64studio-users mailing list
64studio-users@64studio.com
http://lists.64studio.com/mailman/listinfo/64studio-users
 

Thread Tools




All times are GMT. The time now is 12:13 PM.

VBulletin, Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO ©2007, Crawlability, Inc.
Copyright 2007 - 2008, www.linux-archive.org