12-30-2008
Jack,
You just listed the HW. How about the Linux distro you are using?. And kindly tell us what was the changes after this things happens. Thanks.
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
I am trying to Install RHEL AS 4 on x86 pc, through VNC and got the below error, Am not pretty sure as how to resolve this. Can some one guide me through the process, or what might be missing....
Have Installed RHEL, many a times but cudnt find this out...
Wud appreciate an early reply ......... (0 Replies)
Discussion started by: Crazy_murli
0 Replies
2. Linux
ok so I just installed fedora core 6 on my dell inspiron 700m and I go to boot into linux and I get this error. Has anyone seen this before?
I also had XP Pro and Vista installed on this pc prior to putting fedora core 6 on the machine. I'm trying to setup a triple boot system.
Please Help... (2 Replies)
Discussion started by: dave043
2 Replies
3. UNIX for Advanced & Expert Users
HI,
My Machine is running on RHEL3, Its not booting. When I try to boot in rescue mode.Its giving the following err:
" Kernel panic : Fatal exception "
Can any one tel me how to get rid of this error? (3 Replies)
Discussion started by: praveen_b744
3 Replies
4. UNIX for Advanced & Expert Users
We had written an application in which we create worker thread.
So the main thread will create the worker thread. After some time
the child thread(Worker thread) will call pthread_exit().
This function was written in try{} and there occured an Exception
and is handled in catch(...)... (0 Replies)
Discussion started by: platso
0 Replies
5. Solaris
HI friends
can any body tell me what is the difference between server panic and fatal error. (1 Reply)
Discussion started by: tv.praveenkumar
1 Replies
6. UNIX for Advanced & Expert Users
Hi, all:
How should I obtain the reason of kernel panic?
How should I debug the program which result in a kernel panic?
What can I get from the panic information?
li, kunlun (3 Replies)
Discussion started by: liklstar
3 Replies
7. Ubuntu
I installed a new kernel 3.0.22 on ubuntu server 11.04 32 bit.
when I select the kenel from boot loader it stops when
Code:
loading initial ramdisk...
I added all_generic_ide at the end of linux line and also added dev/sda1 to linux line: root=UUID=dev/sda1
now it says that
... (12 Replies)
Discussion started by: dr_mabuse
12 Replies
8. Slackware
Hi,
first of all I'm 110% newbie, sorry for any mistake if I made it.
In my country there are no normal or active linux forums, so i found this forum.
Ok, that's for begining, but not for may real problem.
---------------------------------------------------
I am system administrator... (4 Replies)
Discussion started by: ElvijsL
4 Replies
9. Red Hat
HI All,
server stopped here, we are suspecting server crash, need install new OS.
Any suggestions on this. kindly help to us.
Thanks
Rajesh (0 Replies)
Discussion started by: Rajesh_Apple
0 Replies
10. Red Hat
dear experts linux
i am using RHEL 5.5 run on a physical server.
i am front of a big trouble, the Rhel can't run correctly , it show me this error message in black screen:
reading all physical volumes. this my take a while ..
found volume group "VolGroup00" using metadata type lvm2
9... (1 Reply)
Discussion started by: wassimpb
1 Replies
LEARN ABOUT DEBIAN
zita-j2a
ZITA-REV1(1) General Commands Manual ZITA-REV1(1)
NAME
zita-j2a - Use ALSA capture device as a Jack client, with resampling.
SYNOPSIS
zita-j2a [options]
DESCRIPTION
This tool allows to use an ALSA device as a Jack client, to provide additional capture channels. Functionally it is equivalent to alsa_out
that comes with Jack, but provides much better audio quality.
The resampling ratio will typically be stable within 1 PPM and change only very smoothly. Delay will be stable as well even under worse
case conditions, e.g. the Jack client running near the end of the cycle.
The alsa device should be a 'hw:' one, i.e. direct access to a soundcard and not an ALSA 'plug' device. A well-working Jack system is
assumed, running in real-time mode.
The sample rate can be the same as Jack's one, or different. Minimum delay is obtained by running the alsa device at a lower period size
than Jack. This can be done safely as the alsa thread will run at a higher priority, and apart from copying to/from an internal buffer no
work is done there. There are no restrictions on the product of period_size and number_of_periods as there are for alsa_in and alsa_out.
zita-j2a will optionally print some information four times per second. The first number is the average loop error over the last quarter
second, in samples. It should be reduced to small randowm values close to zero after 15 seconds or so. The second is the dynamic correction
factor of the nominal resampling ratio. This should converge to a value close to one and not move much.
You may observe small variations in these numbers when Jack apps are started or stopped. This is normal. Anything else isn't - please
report.
When starting, and in case of major trouble, you will see the
'Starting synchronisation' message. This can happen if there is a timeout on the Jack server, e.g. a client crashed or terminated in a
dirty way. Jack1 will skip one or more cycles when new apps are started, or when a large number of port connections is done in a short
time. his may interrupt the audio signal, but should otherwise not have any ill consequences nor require a restart.
zita-a2j and zita-j2a will suspend operation while Jack is in
'freewheeling' mode.
OPTIONS
-h Display this text
-d <device>
ALSA playback device [none]
-r <rate>
Sample rate [48000]
-p <period>
Period size [256]
-n <nfrags>
Number of fragments [2]
-c <nchannels>
Number of channels [2]
-Q <quality>
Resampling quality [48]
-v Print tracing information [off]
Use '-h' to see all options.
SEE ALSO
A quick guide is available at <http://kokkinizita.linuxaudio.org/linuxaudio/zita-rev1-doc/quickguide.html>
AUTHOR
zita-ajbridge was written by Fons Adriaensen <fons@linuxaudio.org>.
This manual page was written by Robin Gareus <robin@gareus.org> for the Debian project (but may be used by others). It is based on the
original README and announce message by Fons Adriaensen.
March 2012 ZITA-REV1(1)