Dear Wiki user, You have subscribed to a wiki page or wiki category on "Freevo Wiki" for change notification.
The following page has been changed by 62.127.13.240: http://freevo.sourceforge.net/cgi-bin/moin.cgi/DocumentationPage ------------------------------------------------------------------------------ @@ -372,34 +372,8 @@ that sends all keypad events to the computer. (It's "AT+CMER=3,2,0,0,0", if you send it to your phone with minicom it should say "OK" back.) * The Bluetooth Subsystem (kernel) - * Bluez-utils (and it's deps, http://bluez.sf.net) -The bluetooth subsystem was tricky with a patched kernel so I recommend the 2.4.21 kernel or newer, which has the bluetooth subsystem by default. When you are sure you got that working (test by running "dmesg | less" and look for bluetooth driver messages) you may want to create a bluetooth device in /dev/ if bluetooth doesn't make one for you. Google for it, I don't know how you do that (makedev 43 115 or similiar, but that aren't the right numbers though). - -When you got your device set up you run some bluez command to look for your phone. - -"hciconfig hci0 up" -Set your bluetooth interface. - -"hcitool scan" -Look for your bluetooth phone. On my T68 you must set the phone to "Searchable", item number one in the bluetooth menu. (Then the phone says "You may find me for 3 minutes" or something like that) - -hcitool then reports the bluetooth adress for your phone. Remember it. You will use it later on. - -Now you need to find out on which port the serial interface is on. (On the phone that is.) On my phone it's port number 6. -"hcitool info bluetooth adress" -hcitool info and the adress that hcitool scan gave you. Look for "Serial" somewhere in there. (And the port/channel that represents it) - -Then you bind that port/channel on the phone to a device in /dev/. -"rfcomm bind 1 bluetooth adress channel" -(rfcomm bind 1 00:11:22:33:44:55:66 6. THAT IS AN EXAMPLE ONLY! :)) - -Check if it's working with "rfcomm". - - - -I made an init-script to start the bluetooth interface (hciconfig) and rfcomm. This script also starts the deamon, which I also recommend you to do. It must be started after freevo (untested, but I think so). If you need any help you can find my email adress in the deamon source. @@ -450,332 +424,4 @@ Here is a list of all the above mentioned parameters for simple cutting and pasting: {{{ -#The following are for adding and configuring the CD Audio backup plugin: -AUDIO_BACKUP_DIR = '/music/MP3' - -CD_RIP_PN_PREF= '%(genre)s/%(artist)s/%(album)s/%(song)s' -CDPAR_CMD = 'cdparanoia' - -LAME_CMD = 'lame' -CD_RIP_LAME_OPTS = '--vbr-new' - -#You can leave this out if you never use ogg and it won't show up in the backup menu -OGGENC_CMD ='oggenc' -CD_RIP_OGG_OPTS = ' ' - -#To activate the cdbackup plugin: -plugin.activate('audio.cdbackup') -}}} - - -=== XMMS for playing music === - -Normally MPlayer is used for playing both music and movies, but XMMS can be used for -music instead. Please see the XmmsPlayer page for more info. Because of some code rewrite, the current CVS version has no XMMS support. - -=== Recompiling the Linux kernel === - -This is only needed if your kernel is missing support for the videocard, capture card etc. - -Use this for configuration of a kernel with V''''''ideo4Linux+G400 support. You -probably have to add support for your particular V''''''ideo4Linux device as -well. - -Here is an example kernel config for Matrox G400 support: - - {{{ -Multimedia devices ---> - [Y] Video For Linux - Video For Linux ---> - [Y] V4L information in proc filesystem - -Console drivers ---> - [Y] VGA text console - [Y/M] MDA text console (dual-headed) - Frame-buffer support ---> - [Y] Support for frame buffer devices - [Y/M] Matrox acceleration - [Y] Millenium I/II support - [Y] Mystique support - [Y] G100/G200/G400/G450/G550 support - [Y/M] Matrox I2C support - [Y/M] G400 second head support - [Y] Multihead support -}}} - - -=== Booting into Freevo === - -Anand Patel has written a good webpage about booting Freevo in RH8: - - * [http://www.knet-work.co.uk/freevo-redhat8-guide.htm RH8 Freevo Boot] - -After freevo has been installed correctly and verified to work -when run from the command prompt, the system can be configured -for standalone operation where freevo will startup automatically -without the need for entering a username and password. Standalone -operation implies that the system will be somewhat 'insecure' as -freevo needs root priviledges for mplayer to access TV Capture -cards properly. - -'''(TBD: How to improve security settings)''' - -The following assumes that freevo will be running under X11, and -not in framebuffer mode, since X11 mode is more widely supported -by a variety of VGA display cards. The display type argument for -freevo's configure script should be either 'xv' or 'x11'. These -steps were tested on a Red Hat distribution of Linux. - -'''(TBD: TV-Out?)''' - -''Note'': The X11 window manager is started together with freevo due to -some interactions between mplayer and the freevo fullscreen menu -which may cause mplayer to hang when trying to access the screen if -the freevo menu cannot be windowed. - - 1. Create a new user account (let's use freevo for simplicity). - # adduser freevo - # passwd freevo - - 1. Create a new entry in /etc/sudoers using 'visudo' and add the following line into the file: - - freevo ALL=(ALL) NOPASSWD: /usr/local/bin/startfreevo - - 1. Create the following script 'startfreevo' in /usr/local/bin - - {{{ - # cd /usr/local/bin - # <your_favorite_editor> startfreevo - - ----------- startfreevo script contents ------------------ - #!/bin/sh - cd /usr/local/freevo; ./freevo - ----------- startfreevo script end ----------------------- - (This script assumes that the freevo directory is /usr/local/freevo) - - # chmod 755 /usr/local/bin/startfreevo - }}} - - 1. cd to the freevo home directory. - - {{{ - # cd ~freevo - - Create a .Xclients file in the freevo directory - - # <your_favorite_editor> .Xclients - - - ----------- .Xclients script contents ----------------- - sudo /usr/local/bin/startfreevo & - if [ -f /etc/X11/xinit/Xclients ]; then - [ -x /usr/bin/ssh-agent -a -z "$SSH_AGENT_PID" ] && \ - exec ssh-agent /etc/X11/xinit/Xclients || \ - exec /etc/X11/xinit/Xclients - fi - ----------- .Xclients script end ----------------------- - - # chmod 755 .Xclients; chown freevo.freevo .Xclients - }}} - - 1. The steps given in http://www.linuxgazette.com/issue52/tag/14.html to startup X11 automatically could be used to configure the system to boot into X11 on startup. - -see also ["RunningUnderX"] - - -== Troubleshooting == - -=== Logfiles === - -There is an option MPLAYER_DEBUG in freevo_config.py to turn on logging the MPlayer output to a logfile. -The logfiles are written in the directory freevo is started from, and they're named 'mplayer_stdout.log' and -'mplayer_stderr.log' - -Freevo also writes its own log files by default in /var/log/freevo - -= Usage = - -Please see the /UsageInfo page for information on how Freevo is used. - -= Supported Hardware = - -See the [http://pvrhw.goldfish.org/tiki-pvrhwdb.php?find=freevo&search=find&sort_mode=lmodified_desc PVR HW Database] and http://freevo.sourceforge.net/hardware.html for hints about what people are using. - -== CPU speed == - -''Add statistics about what CPUs are required (basic, MP3, Divx, DVD, recording)'' - -== Graphic Cards == - -=== Matrox G400/450/etc === - -The Matrox G400 is used by some of the main developers, it works well in framebuffer mode. - -/MatroxInfo - -=== Radeon === - -''Add info'' - -See the Radeon7000Page for information about that board. - -=== dxr3 === -See the Dxr3Page for information about that board. - -=== Nvidia === - -See the NvidiaPage for information. - -=== Voodoo3 === - -See the Voodoo3Page for information. - -== TV Capture Cards == - -Any video card that supports the * [http://bytesex.org/bttv/ v4l] or [http://bytesex.org/bttv/ v4l2] API. Should be possible to use under Linux. However, -If you are looking into new hardware, some models are highlighted. - - -=== Cards using the BTTV kernel module === - -According to http://bytesex.org/bttv/ bttv is linux driver for TV cards based on the bt848 and bt878 chips. - -see the BttvPage for module setup. This page also contains a listing of cards supported by the BTTV driver. - -=== Hauppauge WinTV Cards === - -Many people have reported good performance and strong driver support for the Hauppauge WinTV series -of cards. They have a large number of cards, but only the WinTV PCI cards using analog reception -will be of much use. -Warning: if you're considering to buy a Hauppauge WinTV card check the chipset on the card before buying. Hauppauge has changed the chipset on some cards without any mention. -For example the older version of the WinTV PCI Radio (401) has bt878 chip which is well supported by BTTV, but a newer revision contains the CX881 chip which currently -(2003-07-08) is not supported. - -=== Hauppauge WinTV-PVR Cards === - -There is support for the WinTV-PVR series of cards. - -The WinTV-PVR card appears to possibly have some minimal support in the recent BTTV 0.9.x drivers. It appears the BTTV author ported some of the old code from the http://pvr.sourceforge.net project. - -The WinTV-PVR 250/350 cards have recently been getting a lot more attention. The drivers for these cards are under active development and are becoming stable. Please make sure your card and drivers are working properly before trying to use it in Freevo. For more information see http://ivtv.sourceforge.net . - -In order to record using the PVR-250/350 cards please read the information in the Recording Server section above. - -In order to watch live TV with a PVR-250/350 the following 2 lines are needed in local_conf.py -[[BR]]{{{plugin.remove('tv.mplayer')}}} -[[BR]]{{{plugin.activate('tv.ivtv_basic_tv')}}} - -=== ATI All-in-Wonder Models === - -Check out [http://gatos.sourceforge.net the Gatos website] for information on the All-in-Wonder cards. They have incredible support for even the really really old All-in-Wonder cards. NOTE: ALL of the All-in-Wonder cards, even the original 4MB one will give DVD hardware acceleration if you use the Gatos drivers. It's worth the effort if you have one of the oldies. - - -== Remote Controls == - -As far as I can tell, there is no way to get lirc to work without recompiling kernel. I *just* read below that doing a "make dep" might be enough, but if you're already that far -- you might as well recompile and install a custom kernel. (especially if you're kernel is compiled for i386, you can optimize for pentium or athlon, etc) ALSO, make sure you get the source tarball of lirc, and that you dont' have an RPM or DEB installed of it on your computer. (They don't work, at least not for me the 5-10 times I've tried) - -Read the section on the ATI remote part -- most of the instructions are applicable even if you aren't using that specific receiver. - -=== Streamzap USB Remote === -This wonderful remote is available from thinkgeek.com and actually I bought mine at my local CompUSA. The remote is USB and works very nicely with the Streamzap patch to the lirc project. - -The Streamzap USB patch to Lirc is available here http://sourceforge.net/projects/szremote/ - -Note that the diff will not patch correctly against the release version 0.6.6 you must patch against the CVS version. My binary reports a version numbe of 0.7.0pre1. So I'm assuming anything newer then this should be alright.. - -If anybody needs help with it, you may reach me at josh at engr dot arizona dot edu - -=== ATI USB Remote === -This remote is absolutely great. It is USB and has it's own receiver. However, it is an RF (radio frequency) receiver, as oppoased to an infrared receiver. There is a third-party hack to let it work with LIRC until support for this remote is included into the LIRC main branch. Here is how to get it working: - -==== Requirements ==== - 1. Linux system running devfs - 2. Kernel source for your running kernel, located at '/usr/src/linux' (NOTE: This kernel source must have had at least 'make dep' run in it, so that the proper header files, etc. have been generated). - 3. 'lirc-0.6.6' (or greater) from [http://lirc.sourceforge.net] - 4. 'lirc_usb.c' from 'ati_remote' [http://gatos.sourceforge.net] (NOTE: Please make sure you get the file from the CVS, as it is not yet in the 'ati_remote' tarball) - 5. OPTIONAL: While in the CVS for 'ati_remote', you can grab the 'lircd.conf', but I have never had any luck getting it working; I have had to always generate my own. Your mileage may vary. - 6. UPDATE: The lirc_usb.c is no longer available from either CVS or alternate sources (googled). The Gatos people seems to have integrated everything inte just one source file. Compliling the single source file ati_remote.c and running "insmod ati_remote.o" works. You just have to remember to recompile kernel with "input" and "USB" support. - -==== Compilation ==== -'''METHOD ONE:''' lirc is not already installed - 1. Untar and uncompress 'lirc-0.6.6.tar.[gz|bz2]' - 2. Copy 'lirc_usb.c' into one of the driver directories, and rename it to the same as whatever 'lirc_*.c' already exists in there. For example, if you copy into the 'drivers/lirc_sir' directory, you would rename the 'lirc_usb.c' file to 'lirc_sir.c' (This will overwrite the existing file 'lirc_*.c' file in the directrory) - 3. Run './configure --with-driver=sir' (replace 'sir' with whatever directory you copied your lirc_usb.c' file into in Step 2). Of course, you can also add whatever additional './configure' options you wish :-) - 4. Run 'make' then 'make install'. - 5. Change to the '/lib/modules/<kernel_version>/misc' directory, and change the name of the 'lirc_*.o' file to 'lirc_usb.o' (e.g., 'mv lirc_sir.o lirc_usb.o'). - 6. Run 'depmod -a' again. - -'''METHOD TWO:''' lirc is already installed - 1. Untar and uncompress 'lirc-0.6.6.tar.[gz|bz2]' - 2. Copy 'lirc_usb.c' into one of the driver directories, and rename it to the same as whatever 'lirc_*.c' already exists in there. For example, if you copy into the 'drivers/lirc_sir' directory, you would rename the 'lirc_usb.c' file to 'lirc_sir.c' (This will overwrite the existing file 'lirc_*.c' file in the directrory) - 3. Staying in the driver's directory, run 'make'. - 4. Rename the resulting 'lirc_*.o' file to 'lirc_usb.o' (e.g., 'mv lirc_sir.o lirc_usb.o') - 5. Copy 'lirc_usb.o' to the '/lib/modules/<kernel_version>/misc' directory - 6. Run 'depmod -a' - -==== Configuration ==== - 1. Load the module: 'modprobe lirc_usb debug=1' - 2. Generate an 'lircd.conf' file for the remote: 'irrecord -d /dev/usb/remote0' (follow the instructions from 'irrecord') - 3. Copy the resulting file to '/etc/lircd.conf' - 4. Run '~freevo/helpers lircd2lircrc.pl' to generate an 'lircrc' file from your 'lircd.conf' file, that you can then put into '/etc/freevo' - 5. Edit '/etc/freevo/lircrc' to change the name of some of the Freevo events to what Freevo is looking for, so as to have the remote work properly (refer to Freevo's sample 'lircrc' file for this) - -==== Loading and Running ==== - 1. Load the module: 'modprobe lirc_usb debug=1' - 2. Start lirc: 'lircd -d /dev/usb/remote0 /etc/lircd.conf' - 3. Confirm the remote is working properly by running 'irw' and pressing a few buttons - -Congratulations! You now have a working ATI USB remote for use with Freevo! - -== Drives == - -These are devices that might require different setup than standard CR-ROM or DVD-ROM drives. - -=== CD-RW === - -Xine and MPlayer will have problems with these drives if your distro doesn't create a link to /dev/cdrom/ the best fix is just "ln /dev/cdrom /dev/dvd" - -= Skins = - -Please see the /SkinInfo for documentation on Freevo skin usage and development. - -= Plugins = - -Read the config files in the freevo directory. There are explainations on how to add/remove plugins. (NOTE: Just about everything is a plugin now, so this is something you want to look at) - -Please see the /PluginInfo page for documentation on how to configure the different plugins and how to write your own plugins. - - -= Extra File Information in XML metafiles = - -== Movie files == - -Please see the /UsageInfo for more info about this. - -=== Getting info from IMDB === - -You can use '''imdb.py''' in the helpers directory. Depeding on what version you have, it'll write a fxd (>1.3.2) or xml file which contains movie information and a jpg file which contains the movie cover to your harddisk. - -How to use imdb.py is a bit non obvious. Firstly you need to look for your movie, lets say we want to get the data for 'Romancing the Stone'. - -{{{ %imdb.py -s romancing -342943 Romancing Along (1937, Movie) -0114293 Romancing Sara (1995, Movie) -0088011 Romancing the Stone (1984, Movie) -0093056 Fu xing jia qi (1987, Movie) -0095404 Jing zhuong zhui nu zi zhi er (1988, Movie) -0098217 Lang zhi yi zu (1989, Movie) -}}} - -Now we can download the actual data into movies-data (you may need to add this directory) - -{{{ %imdb.py 0088011 movie-data/romance dvd -}}} - -Use '''imdb.py --help''' to see more options - -== Audio files == - -= FAQ = - -[http://freevo.sourceforge.net/cgi-bin/moin.cgi/FrequentlyAskedQuestions FAQ] +# ------------------------------------------------------- This SF.net email is sponsored by: IBM Linux Tutorials. Become an expert in LINUX or just sharpen your skills. Sign up for IBM's Free Linux Tutorials. Learn everything from the bash shell to sys admin. Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click _______________________________________________ Freevo-wikilog mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freevo-wikilog
