phanly

I have php4 running with apache and mysql on mdk 9.1 Simple php pages work (eg telling the date from the server in a web page) Simple php pages interacting with a simple mysql database work eg a simple login form. However, once I use include(myfile.php) in a script I get errors relating to myfile not being found in an include_path which refers to pear eg /usr/share/pear or something like that. I have looked at php.ini (based on the two supplied php.ini versions) but cant find how to set the include path so it loads files in my web directory where I try to include() them: /var/www/html/membersite/ (http://localhost/membersite/) Is there a way to set the include_path globally and should I, and can you add multiple include paths to search? Do I need to specify a particular include_path in the script before I use the include()? Any help would be appreciated. cheers Paul

If new to installing drivers and other software see: http://www.mandrakeusers.org/index.php?showtopic=9713 for a list of useful commands. For installing the alsa drivers generally see: http://alsa.opensrc.org/ and http://alsa.opensrc.org/index.php?page=AlsaDrivers If you have a Turtle Beach soundcard with Aureal chip see: http://alsa.opensrc.org/index.php?page=au88x0 and the pages linked from there, particularly http://alsa.opensrc.org/index.php?page=Qui...ll+-+snd-au88x0 A quick browse of all the pages linked from the au88x0 page before starting is likely to save you hours!!! Don't foget to read the readme and install files before doing ./configure or make. Cheers Paul

Here is a list of linux console/terminal commands I found useful in installing alsa-driver-0.9.8 for my system. Some might be Mandrake or RedHat specific. I hope they save you lots of time. Some were found in Australian Linux Journal Issue 1. Useful Linux console commands for newbies installing drivers A. Software installation bunzip2 (unzips a .bz2 file into teh same directory and drops the .bz2 extension) tar -xf (undoes a .tar file and puts the files in a new subdirectory with a name based on the name of the tar file but without .tar) NB after using the tar -xf command, swap into the new directory and read any read.. and install files. ./configure (with -- switches . produces a configure file which will be read by the make command to compile before running make install ) make (build (compile, link, etc) a project described in the Makefile found in the current directory) make install (installs modules as per the directions in the make file) make clean (delete the executable file and all the object files from the directory) make uninstall (uninstalls software provided the make file still exists and has appropriate instructions - if make uninstall doesn't work it is a tedious manual process to uninstall) insmod (inserts a moduel but no diagnostics) modprobe (installs a module with some diagnostic info) depmod -ae (tells what the problems are in a module) lsmod (lists installed modules) patch (patch <name of file that needs patch> <name of file with patch>) urpmi (mandrake rpm command to get package and install eg urpmi alsamixergui) rpm -q (is rpm package installed eg rpm -q alsamixergui) rpm -Uvh -aid (install or upgrade package eg rpm -Uvh -aid alsamixergui)(the -aid might be RedHat specific and depend n a macro being installed) rpm - Fvh -aid (freshen package))(the -aid might be RedHat specific and depend n a macro being installed) rpm -e (uninstall and rpm package) rpm -V (verify the files within an rpm package are correct) rpm -qi (get information about an installed rpm package) rpm -qip (list the files in a package file) rpm -qf (which package installed a particular file eg rpm -qf alsamixer) rpm -checksig (check the digital signature of a package) rpm -qa -last (find out when all software was installed on a system B. Diagnostics lspci -v (list pci devices in a verbose manner ie with lots of info) modprobe -ae (probe modules for dependencies that are not met) C. File handling cp (copy eg cp "Old File" "New Copy" ) mkdir name (make a directory called name in the current place) pwd (list the full path of the current working directory) ls -la (lists the contents of the current directory one line per file or folder) dir (lists the contents of the current directory) cd (change into a directory eg: cd /usr/src If no path it must be a subdirectory) touch (creates a new empty file eg: touch "New File" or touch NewFile) mkdir (make a new directory eg mkdir NewDir or mkdir "New Directory") mv (moves a file from one directory to another eg move "New File" "new directory") rm (remove (delete) a file/directory) eg rm "old file" or rm oldfile) mv (can be used to rename a file eg mv "new File" "renamed file" - ??? what is the difference between moving to a new directory and changeing a file name? su (change to supervisor mode ie become root (requires password to be entered next)) whoami (lists user logged in) exit (if logged in as root - logs root out and resumes as previous user) exit (if logged in not as root - ends console session) D. File permissions File permissiions are written using 3 characters for each of user group and others in that order. The 3 characters represent read write and execute. enabled permissions are shown by the relevant letter rwx. Disabled permissions are indicated by a -. A permissions for a file could look like: rwxr----- If the user for this file was root then root could read write and execute the file, anyone in the root group but not root could read the file but not write or execute it and others could not read write or execute it. Permissions are called modes. chmod g+rw <path/filename> (give group read and write access) chmod u-x <path/filename> (remove user execute permission from filename file in the path shown) chmod u=rwx,g=rx,o= <path/filename> (gives the permissions indicated to each of user, group and others, and other permissions not indicated are disabled) chgrp (change the group to which a file belongs eg chgrp sales <path/filename> puts the file or directory filename in the path into the sales group. chown (change the owner of a file to a know user eg chown david <path/filename>)

See: http://www.mail-archive.com/alsa-devel@lis...t/msg09813.html Even after this I still have a problem: [root@localhost alsa-utils-0.9.8]# modprobe snd-au8820;modprobe snd-pcm-oss;modprobe snd-mixer-oss; modprobe snd-seq-oss /lib/modules/2.4.21-0.13mdk/kernel/sound/acore/snd.o: unresolved symbol snd_verbose_printk modprobe: insmod /lib/modules/2.4.21-0.13mdk/kernel/sound/acore/snd.o failed modprobe: insmod snd-au8820 failed /lib/modules/2.4.21-0.13mdk/kernel/sound/acore/snd.o: unresolved symbol snd_verbose_printk modprobe: insmod /lib/modules/2.4.21-0.13mdk/kernel/sound/acore/snd.o failed modprobe: insmod snd-pcm-oss failed /lib/modules/2.4.21-0.13mdk/kernel/sound/acore/snd.o: unresolved symbol snd_verbose_printk modprobe: insmod /lib/modules/2.4.21-0.13mdk/kernel/sound/acore/snd.o failed modprobe: insmod snd-mixer-oss failed /lib/modules/2.4.21-0.13mdk/kernel/sound/acore/snd.o: unresolved symbol snd_verbose_printk modprobe: insmod /lib/modules/2.4.21-0.13mdk/kernel/sound/acore/snd.o failed modprobe: insmod snd-seq-oss failed I have double checked the kernel-source is installed using urpmi kernel-source See: http://alsa.opensrc.org/index.php?page=Qui...ll+-+snd-au88x0 for a guide to setting up Alsa for au8820, and the other pages linked re 8820 If anyone can solve the snd-verbose-printk issue I would be grateful. The top link in htis post might give some clues but it is too hard for a noobie like me. Cheers Paul

There is more information at: http://alsa.opensrc.org/index.php?page=au88x0 Follow the links at the bottom of that page for some installation instructions.

Thanks for that. I will give it a try. I have tried the latest Alsa driver 0.9.8 but found that it has some problems in that some of the makefiles apparently have lines missing. Details of the problem described above and the necessary patching appear at: http://www.mail-archive.com/alsa-devel@lis...t/msg09813.html but I still get one error (which I unfortuately can't give you now as I have to use windows to surf as my wnmodem won't work under Linux in spite of the use of the Linuxant driver.) It is a similar error to that described in the quotes above re an unresolved symbol and I assume it has a similar cause which I will try to get help on. One other person has confirmed that after making the suggested changes as outlined in the patch (effectively adding the lines marked + into the file (eg Alsa0.9.8/driver/acore/makefile at the top of each section of the patch) into the relevant makefile using Kwrite ) but without specifying the particular soundcard or distro version or kernel version. I am still hopeful of getting the soundcard working properly but will probably do a reinstall of mdk9.1 before I try the 0.9.7c driver as I am sure I have stuffed it by now as I am starting to have problems with Noatun and Kaboodle and Kmix which didn't exist before. I have downloaded the 0.9.7c driver while typing this so here goes! Cheers Paul

According to the soundcard matrix at http://www.alsa-project.org/alsa-doc/ neither Aureal or Turtle Beach are presently supported. Vortex isn't mentioned. There is an indication that the Aureal 8830 might be possible to be supported. The Aureal 8820 isn't mentioned. On the other hand the post at http://www.mail-archive.com/alsa-devel@lis...t/msg09813.html indicates that maybe the Aureal 8820 can be made work, so I am off to http://savannah.nongnu.org/projects/openvortex to try. I would still welcome any advice as to how to overcome the problems mentioned in the original post. Cheers Paul

I need help with Aureal Semiconductor Vortex 1 (rev 02) Subsystem: Voyetra Technologies Montego soundcard I have used the CVS files from aureal.sourceforge.net and others as described below. Particular problems are: 1. a tainted kernel if I use modprobe au8820 2. insmod -f au8820 complains about "trying to load a module without a GPL compatible license" 3. make all rather than make au8820 gave error messages but make au8820 seemed to work OK and so did make install au8820 (I didn't try make install all) Background: I have read the posts found by searching the Hardware list for Aureal and tried everything in them with the exceptions of http://savannah.nongnu.org/projects/openvortex/ ALSA and recompliling the kernel. If I have missed anything apart from the savannah open vortex project (where the comments from browsing the CVS files didn't inspire confidence that the sound would operate normally) it isn't for want of trying. I have used aureal.sourceforge.net and the CVS files from the project and the files kept at http://jayasolutions.cjb.net/ I am sure that kernel sources are installed - urpmi kernel-sources confirms that. I did the editing of au8810.o au8820.o and au8830.o using Khexedit and the makefile using Kwrite (after changing file permissions using Right click on the file > Properties > permissions on the aureal.sourceforge.net CVS. I had to use wincvs to get them as my winmodem won't work under linux and it took me a while to work out that you login and separately checkout and basically ignore the messages about exiting with code 0. Luckily mdk9.1 can see the win partitions on the other drive on my computer and then copy the files into mdk9.1 directories. Using either the aureal.sourceforge.net CVS files or the au88xx.1.1.3.2 files from jaya I end up with If I use insmod -f au8820 I get If I use modprobe au8820 I get Without doing Modprobe au8820 there is no sound at all. After doing modprobe au8820 there is some very unreliable sound from Kaboodle (Kaboodle At this stage Kaboodle will play some wav files from /usr/share/toppler such as water.wav but not others such as score.wav It will play some files on opening (as configured) but others require the > icon to be clicked/double clicked) and error messages from Noatun: I tried the backtrace function of the KDE crash handler and got : Hope there is a solution someone can offer Paul