[Demudi-commits] r284 - in demudi-trac/trunk: templates wiki
Free Ekanayaka
free-guest@haydn.debian.org
Wed, 01 Dec 2004 15:06:12 -0700
Author: free-guest
Date: 2004-12-01 15:02:48 -0700 (Wed, 01 Dec 2004)
New Revision: 284
Added:
demudi-trac/trunk/wiki/DocumentsFaq
Removed:
demudi-trac/trunk/wiki/DocumentsFAQ
Modified:
demudi-trac/trunk/templates/wiki.cs
Log:
Renamed the FAQ wiki to respect naming convention
Modified: demudi-trac/trunk/templates/wiki.cs
===================================================================
--- demudi-trac/trunk/templates/wiki.cs 2004-12-01 08:49:13 UTC (rev 283)
+++ demudi-trac/trunk/templates/wiki.cs 2004-12-01 22:02:48 UTC (rev 284)
@@ -36,7 +36,7 @@
<li><a href="<?cs var:$trac.href.wiki ?>/DocumentsConcept">Concept</a></li>
<li><a href="<?cs var:$trac.href.wiki ?>/DocumentsOverview">Overview</a></li>
<li><a href="<?cs var:$trac.href.wiki ?>/DocumentsSoftware">Software</a></li>
-<li><a href="<?cs var:$trac.href.wiki ?>/DocumentsFAQ">FAQ</a></li>
+<li><a href="<?cs var:$trac.href.wiki ?>/DocumentsFaq">FAQ</a></li>
<li><a href="<?cs var:$trac.href.wiki ?>/DocumentsHistory">History</a></li>
</ul>
</div>
Deleted: demudi-trac/trunk/wiki/DocumentsFAQ
===================================================================
--- demudi-trac/trunk/wiki/DocumentsFAQ 2004-12-01 08:49:13 UTC (rev 283)
+++ demudi-trac/trunk/wiki/DocumentsFAQ 2004-12-01 22:02:48 UTC (rev 284)
@@ -1,357 +0,0 @@
-[[TOC]]
-
-= Fundamentals =
-
-== Conventions ==
-
-Commands prefaced by a {{{$}}} are to be entered as a normal user, commands
-with a {{{#}}} in front of them need to be entered as root. This is
-your prompt, that means you don't need to type it.
-
-== Using the shell ==
-
-If you've not used a text interface before (i.e. new to GNU/Linux)
-spend a while getting used to it, you're going to need it.
-
-PUT SOME GOOD LINK TO HOW TO USE THE SHELL HERE
-
-== Becoming root ==
-
-To get access to root type:
-
-{{{
- $ su
-}}}
-
-this will ask you for root's password and then allow you to execute
-commands as root.
-
-The command:
-
-{{{
- # exit
-}}}
-
-will return you to a normal user. Don't stay logged in as root and
-pay careful attention to what you are doing (write it down, even), mistakes
-here are often difficult to resolve, you have been warned!
-
-== Man pages ==
-
-If you want to know more about any of the commands type:
-
-{{{
- $ man some_command
-}}}
-
-at the prompt.
-
-= Hardware setup =
-
-== The X Window graphical systems fails to start ==
-
-This is probably due to your video card not being properly detected. You may need to
-google a little bit to find out if your video card is supported and which is the
-right module for it. Note also the NVidia cards need propertary drivers which can
-be found in the non-free section of Debian.
-
-Detailed instructions can be found [http://lists.agnula.org/pipermail/users/2004-September/003171.html here].
-
-You may also try with:
-
-{{{
- # dpkg-reconfigure xserver-xfree86
-}}}
-
-and
-
-{{{
- # xf86config
-}}}
-
-== I can't connect to the network ==
-
-The installer should configure the network for you. If for some reason that hasn't happened then you will
-need to configure the network by hand.
-
-
-If you use dial-up or PPPOE or something, use {{{pppconfig}}} or {{{pppoeconf}}}
-
-If you use DHCP, please become root and run
-
-{{{
- # dpkg-reconfigure etherconf
-}}}
-
-Then follow the instructions, and when asked for a domain name, leave the field empty.
-
-If you're on a laptop you may need to configure pcmcia-cs before this will work. As this is a
-GNU system, there are several different methods you could use for configuration. If you have
-a preferred method of setting up your network it should also be available and you can always
-edit {{{/etc/network/interfaces}}} by hand. The information you need to do this is at:
-
-{{{
- # man 5 interfaces
-}}}
-
-You can then bring the network up with:
-
-{{{
- # ifup eth0
-}}}
-
-or whatever interface you are using instead of eth0.
-
-= Boot process =
-
-== At boot no splash image appears and the boot loader looks crappy ==
-
-You've probably created a separate partition for /boot, so that the splash
-image can't be found. Please either move /boot to the root / partition, or
-change the paths in /boot/grub/menu.lst accordingly.
-
-= System architecture =
-
-{{{
-#!html
-
-<a><h2>Getting to Know JACK</a></h2>
-<p>
-OK, so that's the basic set-up, now you should be hearing some recognisable sound. To check that it's all working properly, it's probably best to go through the exercises in the <a href='http://www.agnula.org/documentation/dp_tutorials/first_steps/' class='external'>First steps in Agnula tutorial</a>.
-<h3>QJackCtl</h3>
-<p>
-Now you've done that, it's time to have a look at <code>qjackctl</code>, that funny little control panel sitting in the middle of your desktop. Hopefully it's already running, if not hit the <code>Start</code> button. All being well you'll see the word <code>Started</code> come up in the window with <code>0 (0)</code> below it. Click on the <code>Connect</code> button and it should show <code>alsa_pcm</code> in both the input and output windows. If so, you're ready to make some music.
-
-<p>
-If you need to alter the way Qjackctl and gkrellm start up look in:
-<pre> # cat /etc/X11/Xsession.d/51demudi.
-</pre><p>
-If it's not all gone so smoothly, click on <code>Messages</code>, if you see anything much more complicated than:
-<pre> 20:19:41.579 Client activated.
- 20:19:41.583 Audio connection change.
- 20:19:41.617 Audio connection graph change.
-</pre>then you're going to need to do some work to get the best out of this. If you only want to use one application at a time, you may not need to worry about JACK too much right now. However, if you want the full power of a Linux Audio system then it's worth taking the time to figure this out. The <code>Status</code> button also provides some slightly less verbose information.
-<h3>Setup</h3>
-<h4>Settings tab</h4>
-
-<p>
-The 'Server Path' should be set to <code>jackstart</code> and the 'Driver' to <code>alsa</code>. 'Parameters' - you probably want to check <code>Realtime</code> for most work and <code>Softmode</code> to start with. 'Softmode' means that JACK doesn't quit if you get odd xruns, obviously, you won't want this if you're recording. If you know your machine only works at 16bit resolution check <code>Force 16bit</code>. You'll probably want to leave most settings where they are.
-<p>
-If you're operating in realtime, your 'Priority' should usually be <code>0</code>, but some soundcards differ. 'Frames/Period' worth setting at the maximum to start and then working your way down. This setting affects your latency most directly, setting it too low will result in xruns. 'Sample Rate' probably wants to be <code>44100</code> (CD quality) but some soundcards prefer <code>48000</code> (DAT quality). 'Periods/Buffer' almost certainly wants to be <code>2</code>, but again, your soundcard may vary. ;-) 'Interface' - probably should be <code>hw:0</code> or whatever you specified in your ~/.asoundrc. 'Audio' try 'Playback' only if you're having trouble, mostly you'll want full <code>Duplex</code>. 'Dither' - 'Shaped' is best but CPU hungry, 'Triangular' gives a good compromise, you don't _need_ dithering, so <code>None</code> will do for now. 'Timeout' and 'Start Delay' you might want to consider increasing these in certain situations.
-
-<p>
-OK your new settings <code>Stop</code> if JACK is still running and <code>Start</code> again. You may need to play with the settings a bit to get satisfactory results.
-<p>
-<hr>
-
-<h2><a name="Permissions">Permissions & ALSA</a></h2>
-
-<p>
-Check that you have the necessary permissions to use the audio devices. <code>vi</code> is used for some of these examples, but again, your favourite text editor will do fine. Make sure your username is in this file next to the <code>audio</code> entry. It should be, by default, so you shouldn't need to change anything here.
-<pre> $ cat /etc/group
-</pre>If you need to add yourself to the list you can use this command:
-<pre> # useradd -G audio username
-</pre><p>
-Next you need to check the permissions of the devices themselves:
-<pre> $ ls -l /dev/dsp* /dev/mixer* /dev/cdrom*
-
-</pre>should give you some output that looks like this:
-<p>
-<pre> lrwxrwxrwx 1 root cdrom 9 2004-08-04 17:47 /dev/cdrom -> /dev/scd0
- lrwxrwxrwx 1 root cdrom 8 2004-08-02 22:16 /dev/cdrom1 -> /dev/hdc
- lrwxrwxrwx 1 root audio 9 2004-08-02 22:34 /dev/dsp -> /dev/dsp0
- crw-rw---- 1 root audio 14, 3 2004-08-02 22:34 /dev/dsp0
- crw-rw---- 1 root audio 14, 19 2004-08-02 22:34 /dev/dsp1
- crw-rw---- 1 root audio 14, 35 2004-08-02 22:34 /dev/dsp2
- crw-rw---- 1 root audio 14, 51 2004-08-02 22:34 /dev/dsp3
- lrwxrwxrwx 1 root audio 11 2004-08-02 22:34 /dev/mixer -> /dev/mixer0
- crw-rw---- 1 root audio 14, 0 2004-08-02 22:34 /dev/mixer0
- crw-rw---- 1 root audio 14, 16 2004-08-02 22:34 /dev/mixer1
- crw-rw---- 1 root audio 14, 32 2004-08-02 22:34 /dev/mixer2
- crw-rw---- 1 root audio 14, 48 2004-08-02 22:34 /dev/mixer3
-</pre><p>
-If it doesn't then you may need to perform these moves:
-<pre> # chgrp audio /dev/dsp* /dev/mixer*
- # chgrp cdrom /dev/cdrom*
-</pre><p>
-
-In this example /dev/cdrom points to the CD Burner, which is a SCSI device. If these links don't point to where you want, then you can change them like this:
-<pre> # rm /dev/cdrom
- # ln -s /dev/hdc /dev/cdrom
-</pre><p>
-check the settings in:
-<pre> # cat /etc/fstab
-</pre>to check that all your devices are mounted where they should be. If you make changes to this file then you'll need to:
-<pre> # mount -a
-</pre>afterwards.
-<p>
-
-In order to get alsa to function properly you may need to edit <code>/etc/alsa/modutils/1.0</code> and/or <code>/etc/modutils/alsa-base</code> then:
-
-<pre> # update-modules
-</pre>and also
-<pre> $ vi ~/.asoundrc
-</pre><p>
-notice that last command is in your home directory so you don't need to be root, so you shouldn't be ;-).
-<pre> # exit
-</pre>will take you back to the normal prompt. See the <a href='http://www.alsa-project.org/alsa-doc/' class='external'>ALSA website</a> for further details on what to put in these files.
-
-<p>
-There is a really useful script available at <a href="http://alsa.opensrc.org/?aadebug" class='external'>http://alsa.opensrc.org/?aadebug</a> that you can use to check that everything is set up right and to provide some useful info to accompany any further questions. You will need <a href="http://www.debian.org/doc/manuals/reference/ch-tutorial.en.html#s-unixlike" class='external'>a little knowledge of how BASH scripts work</a> to use this. The script is now included with the distribution.
-
-
-<p>
-If you look in your menu; Apps > System > Admin has some useful tools such as <code>alsaconf</code>, if your soundcard failed to autoconfigure. You may need to create the file <code>/etc/alsa/modutils/1.0</code> by hand before this will work. <code>/etc/modutils/alsa-base</code> should be a duplicate of this file. If not copy it across and don't forget to <code>update-modules</code>.
-
-<p>
-
-You may need to log out & back in before these changes take effect.
-
-<h2><a name="Xruns">Xruns</a></h2>
-<p>
-During recording sessions, the <code>Messages</code> panel in Qjackctl may report <code>xruns</code>. Xruns are basically an indications that while Jack is running something gets in the way of it running correctly and it becomes unable to cope with the flow of data causing dropouts in the sound. Let's look at the possibilities:
-
-<h3>Interrupts</h3>
-<p>
-If some other card has a higher priority then when it generates an interrupt, if it's slow responding, then possibly Jack and the sound card cannot get their job done.
-<p>
-<pre> # cat /proc/interrupts
-</pre><p>
-and
-<p>
-<pre> # lspci -v
-</pre><p>
-will give you some valuable information here. Generally speaking, you want your soundcard to be in the highest priority slot (9 or 10) and not sharing with anything. Solutions mostly involve physically moving the soundcard up to a higher slot and/or disabling unused hardware in the BIOS.
-<h3>Hard drive speed is too slow</h3>
-<p>
-
-<pre> # hdparm -tT /dev/hda
-</pre>(or whatever drive you use for audio) A/DeMuDi installs with optimal settings for most drives. You shouldn't need to edit <code>/etc/hdparm.conf</code> unless you know you do. You can cause irreversible data corruption messing with these settings. Read:
-<pre> # man hdparm
-</pre>before you attempt anything.
-<h3>Too many processes running</h3>
-<p>
-Processes that interrupt system operation on a regular basis can also cause xruns, although technically this shouldn't be a problem for a powerful enough machine running a low-latency kernel.
-
-<pre> $ ps fax
-</pre>will show you all the processes currently running on your box. One way of cutting down on running processes is to specify a runlevel that is reserved for making music, for example <code>/etc/rc5.d</code>, the default runlevel is <code>/etc/rc2.d</code>. These directories contain links to the scripts that start & stop essential services, usually when you boot up and shut down. Each of these links starts with <code>S##</code>, change the non-essential services to <code>K##</code> using your favourite runlevel editor (again, plenty of choice). Likely candidates for removal are anacron, klogd & cron, most are inessential apart from the obviously music related ones. You can then change runlevels by issuing:
-
-<pre> # telinit 5
-</pre>or whatever level number you chose. It's also worth disabling your screensaver and generally closing down any unused applications or XShells. You can automate this process in the <code>Options</code> tab of Qjackctl's <code>Setup</code> dialog to execute the appropriate commands on startup and shutdown.
-<p>
-<h3>Further Reading</h3>
-<p>
-<a href="http://www.linuxdj.com/audio/quality/" class='external'>http://www.linuxdj.com/audio/quality/</a><br>
- <a href="http://jackit.sourceforge.net/docs/faq.php" class='external'>http://jackit.sourceforge.net/docs/faq.php</a><br>
-
- <a href="http://alsa.opensrc.org/" class='external'>http://alsa.opensrc.org/</a><br>
- <a href="http://linux-sound.org/" class='external'>http://linux-sound.org/</a>
-</pre><p>
-<hr>
-<h1><a name="Unresolved">There's Just One Other Thing ...</a></h1>
-<p> <strong>Q: I've got unresolved symbols!</strong>
-<p> <strong>A</strong>: Yeah, we know.
-<pre> depmod:*** unresolved symbols in /lib/modules/2.4.25-1-multimedia-686/
-kernel/drivers/media/radio/micropcm20.o
- depmod:*** unresolved symbols in /lib/modules/2.4.25-1-multimedia-686/
-alsa/sndpdaudiocf.o
- depmod:*** unresolved symbols in /lib/modules/2.4.25-1-multimedia-686/
-alsa/snd-vx-cs.o
- depmod:*** unresolved symbols in /lib/modules/2.4.25-1-multimedia-686/
-alsa/snd-440.o
- depmod:*** unresolved symbols in /lib/modules/2.4.25-1-multimedia-686/
-alsa/snd-vxpocket.o
-
-</pre>
-<p>
-You can safely ignore all these messages. The last four are because you haven't installed pcmcia-modules.
-<p> <strong>Q: I think I forgot to configure something else.</strong>
-<p> <strong>A</strong>: If you're worried you've missed something out,
-<pre> # dpkg-reconfigure -a
-</pre>Will take you through the configurations of all packages. This will take some time and concentration.
-<p>
-<hr>
-<h1><a name="Upgrading">Upgrading existing installations</a></h1>
-<p> <strong>Q: Can I upgrade my existing 1.2.0-beta0 installation?</strong></p>
-
-<p> <strong>A:</strong> Yes, please read the Package Updates section below.</p>
-<p> <strong>Q: Can I install A/DeMuDi over an existing Debian
- installation?</strong></p>
-<p> <strong>A:</strong> Yes, at least as long as you are
- running Sarge. Follow the following steps</p>
-
-<ul>
-<li>become root</li>
-
-<li>edit your <code>/etc/apt/sources.list</code> adding<p> <pre>deb http://apt.agnula.org/demudi testing main local extra</pre></p>
-</li>
-<li>from the command line issue:<p> <pre># apt-get install demudi-install demudi-base</pre></p>
-</li>
-
-<li>install the tasks you are interested in;
- to have a look at them run:<p> <pre># apt-cache search demudi</pre></p>
-
-<p> the task <code>demudi</code> installs them all</p>
-</li>
-<li>install the appropriate kernel for your processor:<p> <pre># apt-get kernel-image-2.4.25-1-multimedia-<Type></pre></p>
-<p> where <Type> might be <code>386</code>, <code>586tsc</code>, <code>686</code>, <code>k6</code>, <code>k7</code>,
- and the relevant ALSA modules too:</p>
-
-<p> <pre># apt-get install alsa-modules-2.4.25-1-multimedia-<TYPE></pre></p>
-</li>
-<li>finally you may want to run some customisation scripts
- which automatically tune your system:<p> <pre># cfagent-demudi -D postbaseconfig -D upgrade</pre></p>
-</li>
-
-</ul>
-<p> <strong>Q: Can I upgrade my existing 1.0/1.1.0 installation?</strong></p>
-<p> <strong>A:</strong> Yes, using <code>apt</code>.
-See <a href="http://lurker.agnula.org/message/20040616.113908.06d6aea7.html">more info on
- upgrading</a>.</p>
-
-<p> <strong>Q: Can I upgrade my existing 1.1.1 LiveCD installation?</strong></p>
-<p> <strong>A:</strong> No <em>cannot</em> upgrade a 1.1.1 LiveCD install. It was not meant for hard disk
- installation, but only for demo porpoises.</p>
-<p> <strong>Q: Is this a LiveCD?</strong></p>
-<p> <strong>A:</strong> No. It requires installation to your hard drive.</p>
-
-
-<hr>
-<h1><a name="Packages">Package Updates</a></h1>
-<p> At some point you may want to update your packages in order to take advantage of upgrades, new software or bug fixes by using Debian's wonderful tool <code>apt</code> (this requires a network connection). Many people like to use a package manager such as dselect or aptitude, if you prefer a point & click GUI, synaptic is very useable.</p>
-<p> To configure <code>apt</code> to grab packages from the network, we
- need to edit <code>/etc/apt/sources.list</code>. Here is the whole file,
- but note that the only changes you need
- to make are uncommenting the two bottom lines, and changing
- the next-to-last entry to say "testing main local extra".</p>
-
-<p> <pre># cat /etc/apt/sources.list
-deb cdrom:[aGNUla/DeMuDi 1.2.0-beta2 - i386 Binary-1 (20040620)]/ unstable local main
-deb cdrom:[aGNUla/DeMuDi 1.2.0-beta2 - i386 Binary-1 (20040620)]/extra/ unstable main
-deb http://apt.agnula.org/demudi/ testing main local extra
-deb http://snapshot.debian.net/archive/2004/07/14/debian/ testing main contrib non-free</pre></p>
-<p> Now that apt is configured, let's get all the updated
- packages:</p>
-<p> <code># upgrade-demudi</code></p>
-<hr>
-<h1><a name="Further">And beyond ...</a></h1>
-<p>
-Next you'll be wanting to try out some of these wonderful Linux Audio applications, so we'll leave you in the capable hands of Dave Phillips and his excellent <a href='http://www.agnula.org/documentation/dp_tutorials/' class='external'>Tutorials</a>.
-
-<p> If by some strange chance you find a bug ;-) please submit
- a bug report at the <a href="http://devel.agnula.org/tracker/?group_id=8">development GForge portal</a>.</p>
-<p> If you want to discuss this FAQ or write a HOW-TO yourself, log in and make a contribution.
-<p> Subscribe to the <a href="http://www.agnula.org/lists/">mailing
- lists</a> and let us know what you think.</p>
-<p>
-
-Other previously answered questions are available at the
-<a href='http://lurker.agnula.org/splash/index.html' class='external'>mailing list archives</a>.
-Yes, this is a hint. ;)
-<p> Make some great <a href="http://muzik.agnula.org">music</a>!
-</p>
-
-
-
-</div>
-}}}
Copied: demudi-trac/trunk/wiki/DocumentsFaq (from rev 280, demudi-trac/trunk/wiki/DocumentsFAQ)