Differences between version dated 2001-01-20 23:29:16 and 2001-06-05 01:10:11
(spanning 83 versions)
Deletions are marked like this.
Additions are marked like this.
How to install and run the OpenMediaSystem:
How to install and run the OpenMediaSystem:
[http://www.linuxvideo.org/docs/]
These packages probably have dependencies to Debian '''unstable''' packages.
Add the following to {{{ /etc/apt/sources.list }}}:
Ad d the following to {{{ /etc/apt/sources.list }}}:
{{{ deb http://linuxvideo.org/oms/data/debian/ ./ }}}
Note that as of 01/13/2001, /usr/doc/oms/README.Debian says that
the oms package is unusable !! ("to get familiar with Debian packaging...")
== RedHat ==
Yeah, ignore that. It's only maybe 70% true now. ;)
DENT: latest sources do allow RH-package building using 'make dist-rpm', so
stay tuned until we've found a maintainer for those packages - do you like to volunteer?
== RPM ==
Please see OMS RPM Page [http://www.linuxvideo.org/oms/rpm/]
== tarball ==
DENT: latest sources do allow tar-package building using 'make dist' and 'make distcheck',
so stay tuned until we've found a maintainer for those packages - do you like to volunteer?
/!\ Binary tarballs are not yet available. Would you like to volunteer to maintain these?
= Source =
1. Install {{{libcss}}}, {{{oms}}}, and {{{omi}}} source (described below).
1. Make sure your library paths are setup to where you intend to install the libraries. (see description of this in problems section)
1. Install required packages according to OpenMediaInterface.
== Obtaining From CVS ==
{{{
# export CVSROOT=:pserver:anonymous@cvs.linuxvideo.org:/cvs/livid
# cvs login (Just press Return when prompted for a password)
# cvs -z3 co module_name
}}}
Get modules {{{libcss}}}, {{{oms}}}, {{{omi}}}.
== Obtaining Source Tarballs ==
* "stable": [http://www.linuxvideo.org/user/dl.html]
* nightly snapshots: [http://www.linuxvideo.org/devel/dl.html]
== Building/Compiling ==
1. Install packages required to do the build. (see OpenMediaInterface)
1. Get the source for {{{libcss}}}, {{{oms}}}, and {{{omi}}}. (see subsections)
1. Unpack the source source if needed.
1. Make sure your library paths are setup to where you intend to install the libraries. (see description of this in OmsProblems)
1. Build libcss:
1. {{{$ cd libcss}}}
1. {{{$ ./bootstrap}}}
1. {{{$ ./configure}}}
1. {{{$ make}}}
1. {{{$ make install}}}
run 'ldconfig'
1. Build OMI
1. {{{$ cd omi}}}
1. {{{$ ./bootstrap}}}
1. {{{$ make install}}}
1. Run {{{oms_shell}}} or {{{omi_gtk}}}.
== CVS ==
{{{
# export CVSROOT=:pserver:anonymous@cvs.linuxvideo.org:/cvs/livid
# cvs login (Just press Return when prompted for a password)
# cvs -z3 co -dP module_name
}}}
Get modules {{{libcss}}}, {{{oms}}}, {{{omi}}}.
== tarball ==
Visit [http://www.linuxvideo.org/devel/dl.html].
/!\ {{{oms_shell}}} is broken at the moment... sorry. use {{{omi_gtk}}}.
= Configuration =
OpenMediaSystem uses a configuration file located at {{{~/.oms/config}}}.
...
= Problems =
== I get "autoheader: error: AC_CONFIG_HEADERS not found in configure.in" when running bootstrap on libcss ==
Make sure you are using autoconf version 2.13. Newer versions will cause this error.
== Building my omi_gtk binary failed! ==
When building OpenMediaInterface check {{{./configure}}} output, {{{config.log}}}, and {{{./src/config.h}}}. Assure that the proper libs were detected. For a list of what is needed see OpenMediaInterface.
In case the make of omi aborts with undefined references to gtk things:
== ~/.oms/config ==
Run "gtk-config --libs" and add the missing parts to the configuration
settings in Makefile and/or src/Makefile.
grep for the problematic function names in /usr/lib and add the resulting
libs as -Lxxx or -lxxx.
OpenMediaSystem uses a configuration file located at {{{~/.oms/config}}}.
== I ran XYZ and it segfaulted! ==
The format as of 20010324 is {{{key=value}}} one per line.
Yeah, that can happen sometimes. Sorry. But there is hope! Make sure that you don't have old versions of OpenMediaSystem or OpenMediaInterface libraries and plugins on your system. You can also try a clean rebuild just to make sure everything is sane.
The file get's automatically overwritten if you use the GUI configuration.
== I think I have a region code problem with my drive ==
Example:
Run {{{dmesg}}} to see if you have a problem. You may see output like the following:
{{{
ATAPI device hdc:
Error: Illegal request -- (Sense key=0x05)
System resource failure -- (asc=0x55, ascq=0x00)
Media region code is mismatched to logical unit -- (asc=0x6f, ascq=0x04)
The failed "Report Key" packet command was:
"a4 00 00 00 00 00 00 00 00 0c 04 00 "
ypos=538
xpos=959
devices=dvd:/dev/dvd
output_video_device=
output_video_plugin=sdl
output_audio_device=/dev/dsp
output_audio_plugin=sys
skin=some
}}}
Get the regionset program from [http://linuxtv.org/download/dvd/dvd_disc_20000215_css.tar.gz linuxtv.org]
use that to reset the region on your dvd drive. '''Remember''': you can only do this 5 times or so on most drives, so don't get carried away.
|| '''field''' || '''description''' || '''examples''' ||
|| {{{ypos}}} || vertical position of GUI || {{{538}}} ||
|| {{{xpos}}} || horizontal position of GUI || {{{959}}} ||
|| {{{devices}}} || sources of media || {{{dvd:/dev/dvd}}}, (files?) ||
|| {{{output_video_plugin}}} || plugin to use for video output || {{{x11}}}, {{{sdl}}}, etc ||
|| {{{output_video_device}}} || device to use for video output || plugin specific or empty ||
|| {{{output_audio_plugin}}} || plugin to use for video output || {{{sys}}}, {{{esd}}}, etc ||
|| {{{output_audio_device}}} || device to use for audio output || plugin specific or empty, {{{/dev/dsp}}} for {{{sys}}} plugin ||
To compile, untar the file downloaded, and run:
1. {{{# gcc -c dvd_udf.c}}}
1. {{{# gcc -c regionset.c}}}
1. {{{# gcc -o regionset dvd_udf.o regionset.o}}}
1. {{{# ./regionset}}}
== /dev/dvd ==
If you have no region code set, you will see {{{type: NONE}}} as part of the output, as well as {{{drive plays discs from region(s):}}} with no number after it. Set the code according to your region (e.g. United States is 1).
You can set the {{{devices=}}} line in the config file to any device you want. Many people like to have a {{{/dev/dvd}}} but this is not strictly needed.
== "GetTitleKey failed: Input/output error" ==
If you want to create a {{{/dev/dvd}}} JeremyErwin suggests:
This may appear for other reasons, but one reason was because the region code on the DVD drive wasn't set at all . See above subsection for a fix.
You need to symbolicly link the appropriate IDE or SCSI device to {{{/dev/dvd}}}.
== Something really weird happend... ==
If you're using IDE, the following values are standard
* {{{/dev/hda}}} primary master
* {{{/dev/hdb}}} primary slave
* {{{/dev/hdc}}} secondary master
* {{{/dev/hdd}}} secondary slave
Check your {{{~/.oms/config}}} for sanity.
If you're using SCSI, the devices are labeled {{{/dev/scdn}}}, where {{{n}}} is the id of your DVD drive.
Also, run "ldconfig -v" (as root) and check the output carefully. I discovered all sorts of problems, including conflicting and old libraries. When I fixed all those problems, oms started working.
So, if your DVD drive is the primary ide slave, the correct command would be:
== "error while loading shared libraries:" ==
{{{
ln -s /dev/hdb /dev/dvd
}}}
If you get a message like {{{error while loading shared libraries:" liboms.so.0; cannot open shared object file; No such file or directory.}}} then your library paths are incorrect.
= Problems =
By default the libraries install in {{{/usr/local/lib}}} (but this may be different depending on system configuration). You can change this with {{{configure}}} options like {{{--prefix=}}} and {{{--exec-prefix=}}}.
For problems with configuring or running OpenMediaSystem, look at the OmsProblems page or the GeneralProblems page.
Make sure to have the libdir you use added your library path
:
* System wide
1. add {{{/usr/local/lib}}} to your {{{/etc/ld.so.conf}}}
1. run {{{ldconfig}}}
* User based
* add your libdir to shell environment var {{{LD_LIBRARY_PATH}}}
== ** Invalid mantissa - skipping frame ** ==
= Other Tips =
Sometimes you can get {{{** Invalid mantissa - skipping frame **}}} from OpenMediaSystem. Usually caused when skipping chapters?
== User Defined Install Directory ==
Ac3Dec is spewing this when it get fed a bad stream?
You can install in your own directory by using the {{{--prefix=}}} option to {{{configure}}}.
It does this because OpenMediaSystem doesn't correctly jump between chapters, it lands in the middle of a stream and Ac3Dec gets confused(I think thats why)
- no OpenMediaSystem does a correct jump to the start of the next chapter,
but doesn't wait anymore for the end of a proper chunk. - ac3decs resampling
has been optimized and fixed and will be commited to CVS this week.
If you have {{{oms}}} and {{{omi}}} in a dir called {{{~/livid}}} and want to install in {{{~/livid/inst}}} do something like this:
== oms CVS: I get an aclocal error when running bootstrap ==
{{{
$ cd ~/livid
You need to install the automake package on your system
in case aclocal isn't found.
$ cd oms
$ ./bootstrap
$ ./configure --prefix=`pwd`/../inst
$ make install
$ cd ../omi
$ ./bootstrap
$ ./configure --prefix=`pwd`/../inst --with-oms-prefix=`pwd`/../inst
$ make install
= Other Tips =
$ cd ../inst/bin
$ ./omi_gtk
You can install in your own directory by using the {{{--prefix=}}} option to {{{configure}}}.
}}}
ShowText
of this page
EditText
of this page
FindPage
by browsing, searching, or an index
Or try one of these actions:
LikePages,
SpellCheck
MoinMoin 1.108, Copyright © 2000-2001 by Jürgen Hermann
config = 0.000
total = 0.230
imports = 0.150
