[Demudi-commits] r279 - in demudi-trac/trunk: debian wiki
Free Ekanayaka
free-guest@haydn.debian.org
Tue, 30 Nov 2004 04:50:42 -0700
Author: free-guest
Date: 2004-11-30 04:49:36 -0700 (Tue, 30 Nov 2004)
New Revision: 279
Modified:
demudi-trac/trunk/debian/changelog
demudi-trac/trunk/wiki/DocumentsFAQ
demudi-trac/trunk/wiki/LinksAudio
demudi-trac/trunk/wiki/LinksDebian
Log:
demudi-trac:
* added the TOC to the FAQ, started reorganising
Modified: demudi-trac/trunk/debian/changelog
===================================================================
--- demudi-trac/trunk/debian/changelog 2004-11-29 15:13:44 UTC (rev 278)
+++ demudi-trac/trunk/debian/changelog 2004-11-30 11:49:36 UTC (rev 279)
@@ -15,5 +15,6 @@
* under construction icon
* banner is a/demudi instead of demudi
* how to use pseudo-packages for bug reporting
+ * added the TOC to the FAQ, started reorganising
-- Free Ekanayaka <free@agnula.org> Mon, 1 Nov 2004 12:33:45 +0100
Modified: demudi-trac/trunk/wiki/DocumentsFAQ
===================================================================
--- demudi-trac/trunk/wiki/DocumentsFAQ 2004-11-29 15:13:44 UTC (rev 278)
+++ demudi-trac/trunk/wiki/DocumentsFAQ 2004-11-30 11:49:36 UTC (rev 279)
@@ -1,143 +1,144 @@
-= Frequently Asked questions =
+[[TOC]]
- * [:Hardware Hardware setup]
- * [:HardwareGraphic The X Window graphical systems fails to start]
- * [:HardwareNetwork I can't connect to the network]
- * [:HardwareSound My sound card doesn't work ]
+= 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:
+
{{{
-#!html
-<h2><a name="Hardware">Hardware setup</a></h2>
+ $ su
}}}
+this will ask you for root's password and then allow you to execute
+commands as root.
+
+The command:
+
{{{
-#!html
-<a name="HardwareGraphic">The X Window graphical systems fails to start</a>
+ # 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!
-<p> <strong>A</strong>: 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.<p> Detailed instructions can be found
-<a href="http://lists.agnula.org/pipermail/users/2004-September/003171.html">
-here</a>.</p>
+== 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:
+
{{{
-#!html
+ # dpkg-reconfigure xserver-xfree86
+}}}
- <h1>DeMuDi 1.2 FAQ</h1>
+and
- <div class="description">Frequently Asked Questions about installing and configuring AGNULA/DeMuDi 1.2.0
-</div>
+{{{
+ # xf86config
+}}}
-<ul>
-<li><a href="#Installation">Installation</a></li>
-<li><a href="#Configuration">Configuration</a></li>
-<li><a href="#Network">Network</a></li>
-<li><a href="#Permissions">Permissions & ALSA</a></li>
-<li><a href="#JACK">JACK Audio Connection Kit</a></li>
+== I can't connect to the network ==
-<li><a href="#Xruns">Xruns, interupts, hdparm & runlevels</a></li>
-<li><a href="#Unresolved">Unresolved Issues</a></li>
-<li><a href="#Upgrading">Upgrading existing installations</a></li>
-<li><a href="#Packages">Package Updates</a></li>
-<li><a href="#Further">Further Help</a></li>
-</ul>
- <p>This started out as a simple FAQ for beta-release testers and
-would-be testers, but it appears to have grown into a mini-manual.</p>
+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.
-<h1><a name="Installation">Installation</a></h1>
+If you use dial-up or PPPOE or something, use {{{pppconfig}}} or {{{pppoeconf}}}
-<h2> CD</h2>
-<p> The installer CD is bootable. To boot it, your machine must
- be configured to boot from the CD-ROM drive before the hard
- drive in the BIOS. If you don't know how to configure this
- in your BIOS, don't have the option, or have no idea what
- this means, just put the CD in your drive and reboot the
- computer. On many modern machines, booting from CD first
- is the default, hope that yours is this way.</p>
-<p> The DeMuDi (Debian) installation is divided into two halves.
- The first half installs a base system, then you will be
- asked to reboot the computer, and the new base system will
- boot and finish the configuration and package installation.
- As we saw in the previous paragraph, your computer will try
- to boot from the CD-ROM drive if a bootable CD is inserted
- when it boots up.</p>
-<p> When the installer asks you to reboot the computer, it will
- ask you to eject the CD-ROM so we can boot from the (newly
- installed) base system on the hard drive. When you get to
- the blue GRUB boot screen (with the "aGNUla/DeMuDi: kernel
- 2.4.25-multimedia" options), please re-insert the CD-ROM.
- Do not re-insert it prior to this screen. </p>
+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.
-<hr>
-<h1><a name="Configuration">Configuration</a></h3>
-<p>
+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:
-Assuming you've followed all the instructions so far, you'll now be gazing at a
-blank fluxbox or GNOME destop depending on whether you chose the 'minimalistic' or'user friendly' interface during installation, but little of it works, at least, not the way you want it to. If you haven't even got that far, you may need to do a little troubleshooting first:</p>
+{{{
+ # man 5 interfaces
+}}}
+You can then bring the network up with:
-</p>
+{{{
+ # ifup eth0
+}}}
-<p> <strong>Q: I can't get a picture to display at all and my mouse doesn't work</strong></p>
-<p> <strong>A</strong>: You can reconfigure the X server with the command
-<code> # dpkg-reconfigure xserver-xfree86</code>
-or
-<code> # xf86config</code>
-</p>
+or whatever interface you are using instead of eth0.
-<p> <strong>Q: At boot no splash image appears and the boot
- loader looks crappy</strong></p>
-<p> <strong>A</strong>: 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.</p>
+= Boot process =
+== At boot no splash image appears and the boot loader looks crappy ==
-<p>Choose an XShell you're comfortable with. 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. Commands prefaced by a <code>$ </code> are to be entered as a normal user, commands with a <code># </code> in front of them need to be entered as root, this is your prompt. (You don't need to type it)
-<p>
+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.
-To get access to root type: <code>$ su</code> this will ask you for root's password and then allow you to execute commands as root. <code># exit</code> 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! If you want to know more about any of the commands type <code>man <command></code> at the prompt.
+= System architecture =
+
+== Getting to Know JACK</a></h2>
<p>
-<hr>
-<h2><a name="Network">Network</a></h2>
+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>
-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.
+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> If you use dial-up or PPPOE or something, use <code>pppconfig</code> or
- <code>pppoeconf</code>.</p>
-<p> If you use DHCP, please become root and run</p>
-<p> <pre># apt-get install etherconf</pre></p>
-<p> Then follow the instructions, and when
- asked for a domainname, leave the field empty.</p>
-
-<p>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 <code>/etc/network/interfaces</code> by hand. The information you need to do this is at:
-<pre> # man 5 interfaces
-</pre>You can then bring the network up with:
-<pre> # ifup eth0
-</pre>or whatever interface you are using instead of eth0.
<p>
-As soon as you're online, open up a web browser and read these:
+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>
- <a href="http://www.agnula.org/documentation/FAQ/">http://www.agnula.org/documentation/FAQ/</a><br>
+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.
- <a href="http://www.alsa-project.org/alsa-doc/" class='external'>http://www.alsa-project.org/alsa-doc/</a><br>
- <a href="http://www.debian.org/doc/manuals/reference/reference.en.html" class='external'>http://www.debian.org/doc/manuals/reference/reference.en.html</a><br>
- <a href="http://d-i.alioth.debian.org/manual/en.i386/index.html" class='external'>http://d-i.alioth.debian.org/manual/en.i386/index.html</a><br>
- <a href="http://kreiger.linuxgods.com/kiki/?linux+sound-permissions" class='external'>http://kreiger.linuxgods.com/kiki/?linux+sound-permissions</a><br>
-</p>
<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>
@@ -203,36 +204,6 @@
You may need to log out & back in before these changes take effect.
-<p>
-<hr>
-<h2><a name="JACK">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="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:
Modified: demudi-trac/trunk/wiki/LinksAudio
===================================================================
--- demudi-trac/trunk/wiki/LinksAudio 2004-11-29 15:13:44 UTC (rev 278)
+++ demudi-trac/trunk/wiki/LinksAudio 2004-11-30 11:49:36 UTC (rev 279)
@@ -6,3 +6,6 @@
* [http://www.djcj.org/LAU/guide/Low_latency-Mini-HOWTO.php3 Low latency Mini HOWTO]
* [http://www.agnula.org/Members/tormod/compile-2.6/document_view How to compile the 2.6]
* [http://www.agnula.org/Members/tormod/kernel-2.4.27/document_view How to compile the 2.4]
+ * [http://www.alsa-project.org ALSA]
+ * [http://www.alsa-project.org/alsa-doc/ Documentation]
+ * [http://kreiger.linuxgods.com/kiki/?linux+sound-permissions Permissions]
Modified: demudi-trac/trunk/wiki/LinksDebian
===================================================================
--- demudi-trac/trunk/wiki/LinksDebian 2004-11-29 15:13:44 UTC (rev 278)
+++ demudi-trac/trunk/wiki/LinksDebian 2004-11-30 11:49:36 UTC (rev 279)
@@ -1,6 +1,8 @@
= Debian related links =
-
- * [http://www.debian.org Main site] (start here)
- * [http://www.debian.org/MailingLists/subscribe Mailing lists]
- * [http://www.debian.org/doc/manuals/debian-faq/index.en.html The Debian GNU/Linux FAQ]
- * [http://www.debian.org/doc/user-manuals Debian manuals]
+
+ * [http://www.debian.org/devel/debian-installer/ Installer]
+ * [http://d-i.alioth.debian.org/manual/en.i386/index.html Manual]
+ * [http://www.debian.org/MailingLists/ Mailing lists]
+ * [http://www.debian.org/MailingLists/subscribe Subscribe]
+ * [http://www.debian.org/doc/user-manuals User documentation]
+ * [http://www.debian.org/doc/manuals/debian-faq/index.en.html FAQ]