[Demudi-commits] r298 - demudi-trac/trunk/wiki
Steve Doonan
xscd-guest@haydn.debian.org
Fri, 03 Dec 2004 20:15:19 -0700
Author: xscd-guest
Date: 2004-12-03 20:14:51 -0700 (Fri, 03 Dec 2004)
New Revision: 298
Modified:
demudi-trac/trunk/wiki/DocumentsFaq
Log:
still becoming familiar with TracWiki formatting
Modified: demudi-trac/trunk/wiki/DocumentsFaq
===================================================================
--- demudi-trac/trunk/wiki/DocumentsFaq 2004-12-04 02:51:38 UTC (rev 297)
+++ demudi-trac/trunk/wiki/DocumentsFaq 2004-12-04 03:14:51 UTC (rev 298)
@@ -18,9 +18,10 @@
* [http://linux.org.mt/article/terminal The Linux Terminal - a Beginners' Bash]
* [http://www.tuxfiles.org/linuxhelp/theshell.html The Linux Shell, at TuxFiles]
-== Becoming root ==
+== Becoming root (the system administrator) ==
To get access to root type:
+
{{{
$ su
}}}
@@ -29,9 +30,11 @@
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!
@@ -39,9 +42,11 @@
== Man pages ==
If you want to know more about any of the commands type:
+
{{{
$ man some_command
}}}
+
at the prompt.
= Hardware setup =
@@ -58,10 +63,13 @@
[http://lists.agnula.org/pipermail/users/2004-September/003171.html here].
You may also try with the following commands:
+
{{{
# dpkg-reconfigure xserver-xfree86
}}}
+
and
+
{{{
# xf86config
}}}
@@ -74,9 +82,11 @@
If you use dial-up or PPPOE (PPP over Ethernet) 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
@@ -85,14 +95,17 @@
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 =
@@ -125,15 +138,20 @@
If you need to alter the way Qjackctl and gkrellm start up look in:
+
{{{
# cat /etc/X11/Xsession.d/51demudi.
}}}
-If it's not all gone so smoothly, click on {{{Messages}}}, if you see anything much more complicated than:
+
+If it's not all gone so smoothly, click on {{{Messages}}}, if you see anything
+much more complicated than:
+
{{{
20:19:41.579 Client activated.
20:19:41.583 Audio connection change.
20:19:41.617 Audio connection graph change.
}}}
+
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
@@ -154,7 +172,7 @@
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 {{{44100}}} (CD quality) but some soundcards prefer {{{48000}}} (DAT
-quality). 'Periods/Buffer' almost certainly wants to be {{{2}}}, but again,
+quality). 'Periods/Buffer' almost certainly wants to be {{{2}}}, but again,
your soundcard may vary. ;-) 'Interface' - probably should be {{{hw:0}}} or
whatever you specified in your ~/.asoundrc. 'Audio' try 'Playback' only if
you're having trouble, mostly you'll want full {{{Duplex}}}. 'Dither' -
@@ -165,28 +183,32 @@
OK your new settings {{{Stop}}} if JACK is still running and {{{Start}}} again.
You may need to play with the settings a bit to get satisfactory results.
-== ALSA and "permissions" ==
+== ALSA and 'permissions' ==
Check that you have the necessary permissions to use the audio devices.
'''{{{vi}}}''' (a command-line text editor) 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 {{{audio}}} entry. It should be, by default, so you
shouldn't need to change anything here.
+
{{{
$ cat /etc/group
}}}
If you need to add yourself to the list you can use this command:
+
{{{
# useradd -G audio username
}}}
Next you need to check the permissions of the devices themselves:
+
{{{
$ ls -l /dev/dsp* /dev/mixer* /dev/cdrom*
}}}
This should give you some output that looks like this:
+
{{{
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
@@ -203,6 +225,7 @@
}}}
If it doesn't then you may need to perform these moves:
+
{{{
# chgrp audio /dev/dsp* /dev/mixer*
# chgrp cdrom /dev/cdrom*
@@ -210,34 +233,46 @@
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:
+
{{{
# rm /dev/cdrom ln -s /dev/hdc /dev/cdrom
}}}
+
check the settings in:
+
{{{
# cat /etc/fstab
}}}
+
to check that all your devices are mounted where they should be. If you
make changes to this file then you'll need to:
+
{{{
# mount -a
}}}
+
afterwards.
In order to get alsa to function properly you may need to edit
{{{/etc/alsa/modutils/1.0}}} and/or {{{/etc/modutils/alsa-base}}}, then:
+
{{{
# update-modules
}}}
+
and also
+
{{{
$ vi ~/.asoundrc
}}}
+
notice that last command is in your home directory (denoted by the shell
shorthand tilde) so you don't need to be root--so you shouldn't be ;-).
+
{{{
# exit
}}}
+
will take you back to the normal prompt. See the
[http://www.alsa-project.org/alsa-doc/ ALSA website] for further details on
what to put in these files.
@@ -275,10 +310,13 @@
{{{
# cat /proc/interrupts
}}}
+
and
+
{{{
# lspci -v
}}}
+
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
@@ -289,13 +327,16 @@
{{{
# hdparm -tT /dev/hda
}}}
+
(or whatever drive you use for audio) A/DeMuDi installs with optimal settings
for most drives. You shouldn't need to edit {{{/etc/hdparm.conf}}} unless you
know you do. You can cause irreversible data corruption messing with these
settings. Read:
+
{{{
# man hdparm
}}}
+
before you attempt anything.
=== Too many processes running ===
@@ -307,6 +348,7 @@
{{{
$ ps fax
}}}
+
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 {{{/etc/rc5.d}}}, the default runlevel is
@@ -321,6 +363,7 @@
{{{
# telinit 5
}}}
+
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 {{{Options}}} tab of Qjackctl's {{{Setup}}} dialog to
@@ -338,6 +381,7 @@
= There's Just One Other Thing ... =
'''Q: What the-- I've got unresolved symbols!?'''
+
{{{
depmod:*** unresolved symbols in /lib/modules/2.4.25-1-multimedia-686/
kernel/drivers/media/radio/micropcm20.o
@@ -350,25 +394,31 @@
depmod:*** unresolved symbols in /lib/modules/2.4.25-1-multimedia-686/
alsa/snd-vxpocket.o
}}}
+
'''A:''' Yeah, we know.
You can safely ignore all these messages. The last four are because you haven't
installed pcmcia-modules.
'''Q: I think I forgot to configure something else.'''
+
'''A:''' If you're worried you've missed something,
+
{{{
# dpkg-reconfigure -a
}}}
+
will take you through the configurations of all packages. This will take some
time and concentration.
= Upgrading existing installations =
'''Q: Can I upgrade my existing 1.2.0-beta0 installation?'''
+
'''A:''' Yes, please read the Package Updates section below.
'''Q: Can I install !A/DeMuDi over an existing Debian installation?'''
+
'''A:''' Yes, at least as long as you are running Sarge. Take the following steps--
* become root
@@ -413,16 +463,19 @@
}}}
'''Q: Can I upgrade my existing 1.0/1.1.0 installation?'''
+
'''A:''' Yes, using {{{apt}}}.
See [http://lurker.agnula.org/message/20040616.113908.06d6aea7.html] for more info on
upgrading.
'''Q: Can I upgrade my existing 1.1.1 LiveCD installation?'''
+
'''A:''' No, ''cannot'' upgrade a 1.1.1 LiveCD install. It was not meant for
hard disk installation, but only for demo purposes.
'''Q: Is this a LiveCD?'''
+
'''A:''' No. It requires installation to your hard drive.
= Package Updates =