doxa
Newbie
 Offline
Posts: 7
|
 |
« on: May 04, 2012, 02:48:10 PM » |
|
When I type this:
: cat /proc/asound/cards
into the terminal, I get this:
0 [NVidia ]: HDA-Intel - HDA NVidia
HDA NVidia at 0xfe024000 irq 22
I've read all the jack paperwork tutorials and manual entry stuff.
I can't get my head around any of it.
I also get this when I try to configure Jack:
Jackd[3816]: Segfault at 91d8000 ip b7582486 sp bfd66f38 error 4 in libc-2.13.50 [b750e000+153000]
I'm on a Compaq Presario 3200+
NVidia GeForce 6150 le or ls?
DDR2 533
I have the most updated version of AV Linux
and I'm on the 3.0 realtime kernel.
What do I need to do in order to get Jack up and running?
|
|
|
|
|
Logged
|
|
|
|
|
varpa
|
|
« Reply #1 on: May 04, 2012, 04:03:53 PM » |
|
How are you starting Jack? It looks like your soundcard is hw:0 so you could try this:
/usr/bin/jackd -P80 -t2000 -dalsa -dhw:0 -r44100 -p1024 -n2 -o2
What is the output of "aplay -l"
|
|
|
|
|
Logged
|
|
|
|
doxa
Newbie
Offline
Posts: 7
|
|
« Reply #2 on: May 04, 2012, 05:49:46 PM » |
|
before:
doxa@gloria:~$ aplay -l
**** List of PLAYBACK Hardware Devices ****
card 0: NVidia [HDA NVidia], device 0: ALC888 Analog [ALC888 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
after:
doxa@gloria:~$ aplay -l
**** List of PLAYBACK Hardware Devices ****
card 0: NVidia [HDA NVidia], device 0: ALC888 Analog [ALC888 Analog]
Subdevices: 0/1
Subdevice #0: subdevice #0
doxa@gloria:~$
Here is the output from doing what you said:
root@gloria:/home/doxa# /usr/bin/jackd -p80 -t2000 -dalsa -dhw:0 -r44100 -p1024 -n2 -o2
jackd 0.121.3
Copyright 2001-2009 Paul Davis, Stephane Letz, Jack O'Quinn, Torben Hohn and others.
jackd comes with ABSOLUTELY NO WARRANTY
This is free software, and you are welcome to redistribute it
under certain conditions; see the file COPYING for details
JACK compiled with System V SHM support.
loading driver ..
apparent rate = 44100
creating alsa driver ... hw:0|hw:0|1024|2|44100|0|2|nomon|swmeter|-|32bit
control device hw:0
configuring for 44100Hz, period = 1024 frames (23.2 ms), buffer = 2 periods
ALSA: final selected sample format for capture: 32bit integer little-endian
ALSA: use 2 periods for capture
ALSA: final selected sample format for playback: 32bit integer little-endian
ALSA: use 2 periods for playback
|
|
|
|
« Last Edit: May 04, 2012, 06:03:57 PM by doxa »
|
Logged
|
|
|
|
doxa
Newbie
Offline
Posts: 7
|
|
« Reply #3 on: May 04, 2012, 06:53:48 PM » |
|
Here's something else I encountered and I wonder if it has something to do with Jack's lack of configuration:
MP BIOS bug 8254 timer not connected to IO-APIC
|
|
|
|
|
Logged
|
|
|
|
|
GMaq
|
|
« Reply #4 on: May 04, 2012, 07:05:52 PM » |
|
Hi,
If that output from the jack command is complete then it looks to me like JACK is running properly, usually there would be an error message after 'ALSA: use 2 periods for playback' if something was going wrong.
When you say you are having trouble configuring JACK do you mean that Qjackctl won't run or that it segfaults while you are doing the settings? Also I'm curious why you are not using the stock AV Linux kernel, where did you obtain the 'Realtime 3.0' kernel you mentioned, or perhaps I just misunderstood ?
|
|
|
|
« Last Edit: May 04, 2012, 07:14:35 PM by GMaq »
|
Logged
|
|
|
|
doxa
Newbie
Offline
Posts: 7
|
|
« Reply #5 on: May 04, 2012, 08:47:30 PM » |
|
My kernel:
doxa@gloria:~$ uname -a
Linux gloria 3.0.16-avl-7 #22 SMP PREEMPT Fri Jan 6 23:46:34 EST 2012 i686 GNU/Linux
doxa@gloria:~$
This is what the kernel changed to after I installed the NVIDIA proprietary drivers.
Jack segfaults.
Any option I type in after jackd in the terminal comes up with unknown option character.
Am I doing something wrong here?
The first time I uploaded Jack it worked, but I didn't have speakers connected...so I had to restart.
I went through dmesg and I fixed all the issues that made boot up start slow.
All I'm trying to do is what is so easy to do in the manual and connect the onboard MIDI keyboard to QSynth.
It is not happening.
|
|
|
|
« Last Edit: May 04, 2012, 10:13:31 PM by doxa »
|
Logged
|
|
|
|
|
GMaq
|
|
« Reply #6 on: May 05, 2012, 09:30:41 AM » |
|
OK, to clarify,
The kernel is good and that's what it should be, the kernel was not changed by the nVidia driver install only the video driver itself. I don't think the issue is that you are doing something wrong, it would appear that your nVidia HDA sound chip may not be supported by ALSA fully, 99% of HDA chips are supported but there are a few that aren't. Unfortunately the nVidia video driver doesn't also support the sound chip.
Occasionally some of these chipsets give trouble if the capture input is not enabled, you can select this in the Gnome ALSA Mixer if it is not enabled, you can also try selecting playback only in the Qjackctl Setup and see if it works that way, this will tell us if the hardware is supported completely or if it is a duplex issue.
|
|
|
|
|
Logged
|
|
|
|
|
wyeth
|
|
« Reply #7 on: May 06, 2012, 03:00:27 AM » |
|
Here's something else I encountered and I wonder if it has something to do with Jack's lack of configuration:
MP BIOS bug 8254 timer not connected to IO-APIC
I have that same message for 5 years, recording and playback are unaffected. Many error messages you can cut/paste to google for more info, makes for an interesting read sometimes. I always find others who have the exact same errors. Cheers |
|
|
|
|
Logged
|
|
|
|
|
trulan
|
|
« Reply #8 on: May 07, 2012, 07:33:27 PM » |
|
From what you posted in post #3, it looks like you are trying to run Jack as root. Do not run Jack as root, it needs to be run as your user. Otherwise many programs will have trouble using Jack.
Please run the Jack command varpa posted again, this time as your username, and post the output it gives.
|
|
|
|
|
Logged
|
|
|
|
|
