Any chance of supporting this?
Its a plugin for MythTV if i'm right so if MythTV works inside LinuxMCE then this plugin should also work ?
Thanks & keep up the great work.
should be, if compatible with the version, and with the os version!!!
I'm not certain, but I believe the version of Myth running on LinuxMCE has been modified from the baseline build. I don't think plug-ins are supported with this version.
it's also a hack... (I've been waiting for it too)
sasc requires the recompiling the myth source.. it would be nice to see what changes were made to myth to make it work with linuxmce..
Then again, an up-to-date svn would come in handy... :O
that's not a cheap shot, just commenting..
It you have any luck with it, lemme know...
Dan
Hi guys
I have been running sasc-ng with mythtv and pluto for many months, you do not need to patch mythtv unless you are watching certain DVB programmes in the US.
sasc-ng provided a virtual DVB adapter so applications such as mythtv require no modifications. You just tell mythtv to use the virtual rather than the physical adapter.
Obviously you will have to compile sasc-ng on LMCE and to do that you need the kernel sources
NOS
Quote from: ddamron on June 21, 2007, 06:45:29 AM
it's also a hack... (I've been waiting for it too)
sasc requires the recompiling the myth source.. it would be nice to see what changes were made to myth to make it work with linuxmce..
Then again, an up-to-date svn would come in handy... :O
that's not a cheap shot, just commenting..
It you have any luck with it, lemme know...
Dan
Sasc-NG up and running with linuxMCE!
Just followed some howto:s for redhat and myth... and now it´s running!
I´m using MCE 0704, smartmouse, dvb-t card(boxer sweden), Newcamd and sasc-ng 6.10b.
/johan
johan
Care to share the directions that you followed so that we can try them here in the States? Many have determined that it cannot be properly used for the satellite channels that people here otherwise use sasc-ng with MythTV while in LinuxMCE. Can't hurt to review your steps, and see, whether, just maybe its a little different and might work. Note, there are other steps that we have to take over here to get our MythTV working.
Ok, the wiki I followed is in swedish for fedora and here is the link:
http://mythtv.pbwiki.com/MythTV+och+SASC-NG
I had to apt-get the kernel-source before I could compile sasc-ng and I used the latest revision far sasc-ng(not -r 89) .
Works for me and hope it works for u!
/johan
hi,
sasc-ng and linuxmce works very fine with DVB-S. Just follow the install instruction https://opensvn.csie.org/traccgi/sascng/wiki/SascIndex (https://opensvn.csie.org/traccgi/sascng/wiki/SascIndex)
lg
avajon
Has anyone been able to compile sasc-ng on 0710b3?
I'm not able to do it.
I'm stopping at this command:
/lib/modules/`uname -r`/source
I have tried sudo apt-get install kernel-source but that package is not available.
I have been able to get a bit longer... But make still fails, and I do not understand the errors...
linuxmce@dcerouter:~/sasc-ng/trunk$ sudo make
echo 'const char *source_version =' '"'`(svnversion /home/linuxmce/sasc-ng/trunk 2>/dev/null) || echo Unknown`/`(svnversion /home/linuxmce/sasc-ng/trunk/dvbloopback 2>/dev/null) || echo Unknown`'";' > .vers.new ; diff .vers.new objs/version.cpp > .vers.diff 2>&1 ; if test -s .vers.diff ; then mv -f .vers.new objs/version.cpp ; fi ; rm -f .vers.new .vers.diff
make -C ./sc/PLUGINS/src/sc-src CXX=g++ SASC=1 STATIC=1 all
cat: .distvers: No such file or directory
sed: can't read ../../../ci.c: No such file or directory
make[1]: Entering directory `/home/linuxmce/sasc-ng/trunk/sc/PLUGINS/src/sc-src'
xgettext -C -cTRANSLATORS --no-wrap --no-location -k -ktr -ktrNOOP --msgid-bugs-address='<noone@nowhere.org>' -o po/sc.pot sc.c system.c systems/nagra/nagra1.c systems/nagra/nagra2.c systems/nagra/.svn/text-base/nagra2.c.svn-base systems/nagra/.svn/text-base/nagra1.c.svn-base systems/cardclient/cc.c systems/cardclient/.svn/text-base/cc.c.svn-base systems/sc-cryptoworks/.svn/text-base/sc-cryptoworks.c.svn-base systems/sc-cryptoworks/sc-cryptoworks.c systems/sc-seca/sc-seca.c systems/sc-seca/.svn/text-base/sc-seca.c.svn-base
make[1]: xgettext: Command not found
make[1]: *** [po/sc.pot] Error 127
make[1]: Leaving directory `/home/linuxmce/sasc-ng/trunk/sc/PLUGINS/src/sc-src'
make: *** [sc-plugin] Error 2
linuxmce@dcerouter:~/sasc-ng/trunk$
Quote from: cirion on February 13, 2008, 12:04:24 AM
I have been able to get a bit longer... But make still fails, and I do not understand the errors...
linuxmce@dcerouter:~/sasc-ng/trunk$ sudo make
echo 'const char *source_version =' '"'`(svnversion /home/linuxmce/sasc-ng/trunk 2>/dev/null) || echo Unknown`/`(svnversion /home/linuxmce/sasc-ng/trunk/dvbloopback 2>/dev/null) || echo Unknown`'";' > .vers.new ; diff .vers.new objs/version.cpp > .vers.diff 2>&1 ; if test -s .vers.diff ; then mv -f .vers.new objs/version.cpp ; fi ; rm -f .vers.new .vers.diff
make -C ./sc/PLUGINS/src/sc-src CXX=g++ SASC=1 STATIC=1 all
cat: .distvers: No such file or directory
sed: can't read ../../../ci.c: No such file or directory
make[1]: Entering directory `/home/linuxmce/sasc-ng/trunk/sc/PLUGINS/src/sc-src'
xgettext -C -cTRANSLATORS --no-wrap --no-location -k -ktr -ktrNOOP --msgid-bugs-address='<noone@nowhere.org>' -o po/sc.pot sc.c system.c systems/nagra/nagra1.c systems/nagra/nagra2.c systems/nagra/.svn/text-base/nagra2.c.svn-base systems/nagra/.svn/text-base/nagra1.c.svn-base systems/cardclient/cc.c systems/cardclient/.svn/text-base/cc.c.svn-base systems/sc-cryptoworks/.svn/text-base/sc-cryptoworks.c.svn-base systems/sc-cryptoworks/sc-cryptoworks.c systems/sc-seca/sc-seca.c systems/sc-seca/.svn/text-base/sc-seca.c.svn-base
make[1]: xgettext: Command not found
make[1]: *** [po/sc.pot] Error 127
make[1]: Leaving directory `/home/linuxmce/sasc-ng/trunk/sc/PLUGINS/src/sc-src'
make: *** [sc-plugin] Error 2
linuxmce@dcerouter:~/sasc-ng/trunk$
Looks like your system is missing the "xgettext" binary, here is what I usually do when I run into something like that:
# xgettext
The program 'xgettext' is currently not installed. You can install it by typing:
apt-get install gettext
-bash: xgettext: command not found
Just try to execute it manually and then Kubuntu is nice enough to let you know what (and even how) to install, in this case "apt-get install gettext".
EDIT:
If you could keep a list of the things you have to install and then post it here, that would be most helpful to others trying the same.
Thanks. gettext is now installed....
But make still fails on the same line:
make -C ./sc/PLUGINS/src/sc-src CXX=g++ SASC=1 STATIC=1 all
cat: .distvers: No such file or directory
sed: can't read ../../../ci.c: No such file or directory
What does ../../../ mean?
The full log is now:
linuxmce@dcerouter:~/sasc-ng/trunk$ sudo make
echo 'const char *source_version =' '"'`(svnversion /home/linuxmce/sasc-ng/trunk 2>/dev/null) || echo Unknown`/`(svnversion /home/linuxmce/sasc-ng/trunk/dvbloopback 2>/dev/null) || echo Unknown`'";' > .vers.new ; diff .vers.new objs/version.cpp > .vers.diff 2>&1 ; if test -s .vers.diff ; then mv -f .vers.new objs/version.cpp ; fi ; rm -f .vers.new .vers.diff
make -C ./sc/PLUGINS/src/sc-src CXX=g++ SASC=1 STATIC=1 all
cat: .distvers: No such file or directory
sed: can't read ../../../ci.c: No such file or directory
make[1]: Entering directory `/home/linuxmce/sasc-ng/trunk/sc/PLUGINS/src/sc-src'
make[2]: Entering directory `/home/linuxmce/sasc-ng/trunk/sc/PLUGINS/src/sc-src/systems/cardclient'
make[2]: Nothing to be done for `all'.
make[2]: Leaving directory `/home/linuxmce/sasc-ng/trunk/sc/PLUGINS/src/sc-src/systems/cardclient'
make[2]: Entering directory `/home/linuxmce/sasc-ng/trunk/sc/PLUGINS/src/sc-src/systems/conax'
make[2]: Nothing to be done for `all'.
make[2]: Leaving directory `/home/linuxmce/sasc-ng/trunk/sc/PLUGINS/src/sc-src/systems/conax'
make[2]: Entering directory `/home/linuxmce/sasc-ng/trunk/sc/PLUGINS/src/sc-src/systems/constcw'
make[2]: Nothing to be done for `all'.
make[2]: Leaving directory `/home/linuxmce/sasc-ng/trunk/sc/PLUGINS/src/sc-src/systems/constcw'
make[2]: Entering directory `/home/linuxmce/sasc-ng/trunk/sc/PLUGINS/src/sc-src/systems/cryptoworks'
make[2]: Nothing to be done for `all'.
make[2]: Leaving directory `/home/linuxmce/sasc-ng/trunk/sc/PLUGINS/src/sc-src/systems/cryptoworks'
make[2]: Entering directory `/home/linuxmce/sasc-ng/trunk/sc/PLUGINS/src/sc-src/systems/irdeto'
make[2]: Nothing to be done for `all'.
make[2]: Leaving directory `/home/linuxmce/sasc-ng/trunk/sc/PLUGINS/src/sc-src/systems/irdeto'
make[2]: Entering directory `/home/linuxmce/sasc-ng/trunk/sc/PLUGINS/src/sc-src/systems/nagra'
make[2]: Nothing to be done for `all'.
make[2]: Leaving directory `/home/linuxmce/sasc-ng/trunk/sc/PLUGINS/src/sc-src/systems/nagra'
make[2]: Entering directory `/home/linuxmce/sasc-ng/trunk/sc/PLUGINS/src/sc-src/systems/sc-conax'
make[2]: Nothing to be done for `all'.
make[2]: Leaving directory `/home/linuxmce/sasc-ng/trunk/sc/PLUGINS/src/sc-src/systems/sc-conax'
make[2]: Entering directory `/home/linuxmce/sasc-ng/trunk/sc/PLUGINS/src/sc-src/systems/sc-cryptoworks'
make[2]: Nothing to be done for `all'.
make[2]: Leaving directory `/home/linuxmce/sasc-ng/trunk/sc/PLUGINS/src/sc-src/systems/sc-cryptoworks'
make[2]: Entering directory `/home/linuxmce/sasc-ng/trunk/sc/PLUGINS/src/sc-src/systems/sc-irdeto'
make[2]: Nothing to be done for `all'.
make[2]: Leaving directory `/home/linuxmce/sasc-ng/trunk/sc/PLUGINS/src/sc-src/systems/sc-irdeto'
make[2]: Entering directory `/home/linuxmce/sasc-ng/trunk/sc/PLUGINS/src/sc-src/systems/sc-nagra'
make[2]: Nothing to be done for `all'.
make[2]: Leaving directory `/home/linuxmce/sasc-ng/trunk/sc/PLUGINS/src/sc-src/systems/sc-nagra'
make[2]: Entering directory `/home/linuxmce/sasc-ng/trunk/sc/PLUGINS/src/sc-src/systems/sc-seca'
make[2]: Nothing to be done for `all'.
make[2]: Leaving directory `/home/linuxmce/sasc-ng/trunk/sc/PLUGINS/src/sc-src/systems/sc-seca'
make[2]: Entering directory `/home/linuxmce/sasc-ng/trunk/sc/PLUGINS/src/sc-src/systems/sc-viaccess'
make[2]: Nothing to be done for `all'.
make[2]: Leaving directory `/home/linuxmce/sasc-ng/trunk/sc/PLUGINS/src/sc-src/systems/sc-viaccess'
make[2]: Entering directory `/home/linuxmce/sasc-ng/trunk/sc/PLUGINS/src/sc-src/systems/sc-videoguard2'
make[2]: Nothing to be done for `all'.
make[2]: Leaving directory `/home/linuxmce/sasc-ng/trunk/sc/PLUGINS/src/sc-src/systems/sc-videoguard2'
make[2]: Entering directory `/home/linuxmce/sasc-ng/trunk/sc/PLUGINS/src/sc-src/systems/seca'
make[2]: Nothing to be done for `all'.
make[2]: Leaving directory `/home/linuxmce/sasc-ng/trunk/sc/PLUGINS/src/sc-src/systems/seca'
make[2]: Entering directory `/home/linuxmce/sasc-ng/trunk/sc/PLUGINS/src/sc-src/systems/shl'
make[2]: Nothing to be done for `all'.
make[2]: Leaving directory `/home/linuxmce/sasc-ng/trunk/sc/PLUGINS/src/sc-src/systems/shl'
make[2]: Entering directory `/home/linuxmce/sasc-ng/trunk/sc/PLUGINS/src/sc-src/systems/viaccess'
make[2]: Nothing to be done for `all'.
make[2]: Leaving directory `/home/linuxmce/sasc-ng/trunk/sc/PLUGINS/src/sc-src/systems/viaccess'
make[1]: Leaving directory `/home/linuxmce/sasc-ng/trunk/sc/PLUGINS/src/sc-src'
g++ -g -Wall -o sasc-ng -Wl,-whole-archive ./sc/PLUGINS/lib/libsc-*.a -Wl,-no-whole-archive ./sc/PLUGINS/lib/libvdr-sc.a objs/forward.o objs/process_req.o objs/msg_passing.o objs/plugin_getsid.o objs/plugin_ringbuf.o objs/plugin_showioctl.o objs/plugin_legacysw.o objs/plugin_dss.o objs/plugin_cam.o objs/plugin_ffdecsa.o objs/version.o objs/misc.o objs/dvbdevice.o objs/osdbase.o objs/menuitems.o objs/device.o objs/thread.o objs/tools.o objs/sasccam.o objs/log.o objs/vdrcompat.o objs/libsi.a FFdecsa/FFdecsa.o -lpthread -lcrypto -lcrypt
linuxmce@dcerouter:~/sasc-ng/trunk$
For those who want to try compiling sasc-ng I have followed the instructions from these links:
https://opensvn.csie.org/traccgi/sascng/wiki/SascDownload
https://opensvn.csie.org/traccgi/sascng/wiki/SascInstall
Before even beginning I had my DVB-C card up and running in VDR and FTA working.
I'm using a Terratec Cinergy C PCI card with the mantis driver:
http://jusst.de/hg/mantis/summary
Before installing I did need a few things:
sudo apt-get install build-essential subversion gettextTo download:
svn co https://OpenSVN.csie.org/sascng sasc-ngTo configure:
cd sasc-ng/
cd trunk/
/lib/modules/`uname -r`/build
./configure --dvb-dir=<Path to driver>
I did not need the kernel source since I'm using a self compiled driver.
Make the module:
make moduleI was missing a compiler.h like it said in the instructions and I just added it in linux/include/linux folder of my driverfolder with this command:
sudo touch compiler.hAnd after this it is just make and sudo make install....
I had this plugin compiled and working in Kaffeine in 0710Beta2, but it was with a HVR4000 DVB-S card.
I have not been able to finish the make command yet in 0710Beta3.
Cirion.
I have been running sasc-ng since lmce0704.
It work really well.
In my setup I fetch keys from my dreambox, dm-500t were I have my (paid for) smartcard.
Since myth in lmce is almost unusable for me. It crash after a couple of seconds so i´m stuck with recording only, watch later.
VDR is a lot better. Almost superb stability.
Haven´t tried any of the nightly build so I don´t know how much further vdr integration have come.
And so far I can say the same about sasc-ng. It have never failed me.
One thing to look out for it to manage load/unload of sasc-ng carefully.
In my opionon do not unload dvbloopback module unless you really need to and do not have any applications that are using the virtual adapters. If you do the kernel will Oops. Perhaps fixed in later svn version of dvbloopback.
My hardware is based on 64-bit lmce0704b with vdr at the moment. Seem to be the best app to use for tv here in europe even though it lack functionality like automatic channel scan and so on. To recieve dvb-t I use a hauppage nova-t 500 and a usb nova-t.
One thing to look out for in vdr is to lock down which tuners vdr can use. Otherwise it will try to use the physical adapters too wich can lead to instability.
I have been talking to danielk about myth stability since I have a production mythbuntu 0710 install with sasc-ng to which never ever crash. (using exactly the same hw as I have for my lmce test machine).
Do we dare to a wiki page out of the info in the thread? (since it in a grey area)
/niz23
Quote from: niz23 on February 13, 2008, 09:56:56 PMDo we dare to a wiki page out of the info in the thread? (since it in a grey area)
Is it any worse to see paytv with a payed subscription through a cs to make it work, than to rip a Bluray/HD-DVD to view it?
Cirion.
Quote from: cirion on February 13, 2008, 10:58:27 PM
Quote from: niz23 on February 13, 2008, 09:56:56 PMDo we dare to a wiki page out of the info in the thread? (since it in a grey area)
Is it any worse to see paytv with a payed subscription through a cs to make it work, than to rip a Bluray/HD-DVD to view it?
Absolutely no.
However there is resistance towards cs solutions. Most of the times this type of solutions are discussed it end it with only silency.
Other people suggest private forums for further discussion.
I have creted a wiki page with some info about sasc-ng in. Feel free to edit and add more to it.
English is not my native language so things may read strange sometimes.
I will add more text inte this page as over time. Need to verify how to build sasc-ng without manual hacks first.
/niz23
i think yes, we should be able to discuss technical topics freely. I don't see that as instruction to break the law. I don't know which laws you have to comply to. Everybody has to decide that on his own, according to local legislation.
The problem with CS is that a user (depending on local laws) probably does the following:
1.) Patent violation of the DVB standards
2.) Copyright violations (nagra rom, ...)
3.) Circumventing copy protection (wait, its a viewing protection)
4.) Breaking the contract with the pay tv provider
I think you should ask daniel if we could get troubles with the hosting if we publish that information. If we are not allowed we could make a "non-free" Wiki on some .RU server ;)
best regards,
Hari
Quote from: cirion on February 13, 2008, 05:56:53 PM...
What does ../../../ mean?
...
Glad to see you got it sorted, and thanks for adding it to the wiki as well.
Just to answer that question, each directory always has 2 special "sub"-directories: "." and ".." which stand for the current directory and the parent directory respectively, so ../../../ simply is the relative path for 3 directories up in this case.
Quote from: Zaerc on February 14, 2008, 08:38:18 PM
Glad to see you got it sorted, and thanks for adding it to the wiki as well.
I never got it sorted :( I have no idea on how to finish compiling this plugin.
If anyone is able to understand what is wrong please tell!
I'm still stopping at these to lines. I have no idea on what they mean:
cat: .distvers: No such file or directory
sed: can't read ../../../ci.c: No such file or directory
Is the error before or after these lines?
As posted earlier this is what I get:
linuxmce@dcerouter:~/sasc-ng/trunk$ sudo make
echo 'const char *source_version =' '"'`(svnversion /home/linuxmce/sasc-ng/trunk 2>/dev/null) || echo Unknown`/`(svnversion /home/linuxmce/sasc-ng/trunk/dvbloopback 2>/dev/null) || echo Unknown`'";' > .vers.new ; diff .vers.new objs/version.cpp > .vers.diff 2>&1 ; if test -s .vers.diff ; then mv -f .vers.new objs/version.cpp ; fi ; rm -f .vers.new .vers.diff
make -C ./sc/PLUGINS/src/sc-src CXX=g++ SASC=1 STATIC=1 all
cat: .distvers: No such file or directory
sed: can't read ../../../ci.c: No such file or directory
make[1]: Entering directory `/home/linuxmce/sasc-ng/trunk/sc/PLUGINS/src/sc-src'
make[2]: Entering directory `/home/linuxmce/sasc-ng/trunk/sc/PLUGINS/src/sc-src/systems/cardclient'
make[2]: Nothing to be done for `all'.
make[2]: Leaving directory `/home/linuxmce/sasc-ng/trunk/sc/PLUGINS/src/sc-src/systems/cardclient'
make[2]: Entering directory `/home/linuxmce/sasc-ng/trunk/sc/PLUGINS/src/sc-src/systems/conax'
make[2]: Nothing to be done for `all'.
make[2]: Leaving directory `/home/linuxmce/sasc-ng/trunk/sc/PLUGINS/src/sc-src/systems/conax'
make[2]: Entering directory `/home/linuxmce/sasc-ng/trunk/sc/PLUGINS/src/sc-src/systems/constcw'
make[2]: Nothing to be done for `all'.
make[2]: Leaving directory `/home/linuxmce/sasc-ng/trunk/sc/PLUGINS/src/sc-src/systems/constcw'
make[2]: Entering directory `/home/linuxmce/sasc-ng/trunk/sc/PLUGINS/src/sc-src/systems/cryptoworks'
make[2]: Nothing to be done for `all'.
make[2]: Leaving directory `/home/linuxmce/sasc-ng/trunk/sc/PLUGINS/src/sc-src/systems/cryptoworks'
make[2]: Entering directory `/home/linuxmce/sasc-ng/trunk/sc/PLUGINS/src/sc-src/systems/irdeto'
make[2]: Nothing to be done for `all'.
make[2]: Leaving directory `/home/linuxmce/sasc-ng/trunk/sc/PLUGINS/src/sc-src/systems/irdeto'
make[2]: Entering directory `/home/linuxmce/sasc-ng/trunk/sc/PLUGINS/src/sc-src/systems/nagra'
make[2]: Nothing to be done for `all'.
make[2]: Leaving directory `/home/linuxmce/sasc-ng/trunk/sc/PLUGINS/src/sc-src/systems/nagra'
make[2]: Entering directory `/home/linuxmce/sasc-ng/trunk/sc/PLUGINS/src/sc-src/systems/sc-conax'
make[2]: Nothing to be done for `all'.
make[2]: Leaving directory `/home/linuxmce/sasc-ng/trunk/sc/PLUGINS/src/sc-src/systems/sc-conax'
make[2]: Entering directory `/home/linuxmce/sasc-ng/trunk/sc/PLUGINS/src/sc-src/systems/sc-cryptoworks'
make[2]: Nothing to be done for `all'.
make[2]: Leaving directory `/home/linuxmce/sasc-ng/trunk/sc/PLUGINS/src/sc-src/systems/sc-cryptoworks'
make[2]: Entering directory `/home/linuxmce/sasc-ng/trunk/sc/PLUGINS/src/sc-src/systems/sc-irdeto'
make[2]: Nothing to be done for `all'.
make[2]: Leaving directory `/home/linuxmce/sasc-ng/trunk/sc/PLUGINS/src/sc-src/systems/sc-irdeto'
make[2]: Entering directory `/home/linuxmce/sasc-ng/trunk/sc/PLUGINS/src/sc-src/systems/sc-nagra'
make[2]: Nothing to be done for `all'.
make[2]: Leaving directory `/home/linuxmce/sasc-ng/trunk/sc/PLUGINS/src/sc-src/systems/sc-nagra'
make[2]: Entering directory `/home/linuxmce/sasc-ng/trunk/sc/PLUGINS/src/sc-src/systems/sc-seca'
make[2]: Nothing to be done for `all'.
make[2]: Leaving directory `/home/linuxmce/sasc-ng/trunk/sc/PLUGINS/src/sc-src/systems/sc-seca'
make[2]: Entering directory `/home/linuxmce/sasc-ng/trunk/sc/PLUGINS/src/sc-src/systems/sc-viaccess'
make[2]: Nothing to be done for `all'.
make[2]: Leaving directory `/home/linuxmce/sasc-ng/trunk/sc/PLUGINS/src/sc-src/systems/sc-viaccess'
make[2]: Entering directory `/home/linuxmce/sasc-ng/trunk/sc/PLUGINS/src/sc-src/systems/sc-videoguard2'
make[2]: Nothing to be done for `all'.
make[2]: Leaving directory `/home/linuxmce/sasc-ng/trunk/sc/PLUGINS/src/sc-src/systems/sc-videoguard2'
make[2]: Entering directory `/home/linuxmce/sasc-ng/trunk/sc/PLUGINS/src/sc-src/systems/seca'
make[2]: Nothing to be done for `all'.
make[2]: Leaving directory `/home/linuxmce/sasc-ng/trunk/sc/PLUGINS/src/sc-src/systems/seca'
make[2]: Entering directory `/home/linuxmce/sasc-ng/trunk/sc/PLUGINS/src/sc-src/systems/shl'
make[2]: Nothing to be done for `all'.
make[2]: Leaving directory `/home/linuxmce/sasc-ng/trunk/sc/PLUGINS/src/sc-src/systems/shl'
make[2]: Entering directory `/home/linuxmce/sasc-ng/trunk/sc/PLUGINS/src/sc-src/systems/viaccess'
make[2]: Nothing to be done for `all'.
make[2]: Leaving directory `/home/linuxmce/sasc-ng/trunk/sc/PLUGINS/src/sc-src/systems/viaccess'
make[1]: Leaving directory `/home/linuxmce/sasc-ng/trunk/sc/PLUGINS/src/sc-src'
g++ -g -Wall -o sasc-ng -Wl,-whole-archive ./sc/PLUGINS/lib/libsc-*.a -Wl,-no-whole-archive ./sc/PLUGINS/lib/libvdr-sc.a objs/forward.o objs/process_req.o objs/msg_passing.o objs/plugin_getsid.o objs/plugin_ringbuf.o objs/plugin_showioctl.o objs/plugin_legacysw.o objs/plugin_dss.o objs/plugin_cam.o objs/plugin_ffdecsa.o objs/version.o objs/misc.o objs/dvbdevice.o objs/osdbase.o objs/menuitems.o objs/device.o objs/thread.o objs/tools.o objs/sasccam.o objs/log.o objs/vdrcompat.o objs/libsi.a FFdecsa/FFdecsa.o -lpthread -lcrypto -lcrypt
linuxmce@dcerouter:~/sasc-ng/trunk$
Sorry my bad, it seemed to be solved...
Those errors mean that the build process can't find the files .distvers and ci.c.
Any tips on what to do about that?
Hi Cirion,
Those 3 error messages are just fine, the sasc-ng binary is made and fully usable with those errors,
next go to dvbloopback/src/module than make and copy the dvbloopback.ko modules to
/lib/modules/`uname -r`/kernel/drivers/media/dvb/
add dvbloopback in the /etc/modules file than setup /etc/init.d/vdr to start sasc-ng before starting vdr
Quote from: rafik24 on March 10, 2008, 02:20:31 PM
next go to dvbloopback/src/module than make and copy the dvbloopback.ko modules to
/lib/modules/`uname -r`/kernel/drivers/media/dvb/
add dvbloopback in the /etc/modules file than setup /etc/init.d/vdr to start sasc-ng before starting vdr
Tried to do like that but modprob cannot find the module:
QuoteFATAL: Module dvbloopback not found.
Quote from: Michael on March 20, 2008, 10:03:02 AM
Quote from: rafik24 on March 10, 2008, 02:20:31 PM
next go to dvbloopback/src/module than make and copy the dvbloopback.ko modules to
/lib/modules/`uname -r`/kernel/drivers/media/dvb/
add dvbloopback in the /etc/modules file than setup /etc/init.d/vdr to start sasc-ng before starting vdr
Tried to do like that but modprob cannot find the module:
QuoteFATAL: Module dvbloopback not found.
You probably have to run:
depmod -a after copying the kernel module so the system knows about it.
QuoteYou probably have to run:
Code:
depmod -a
after copying the kernel module so the system knows about it.
Excellent point, Zaerc. It works finally :)
I'm trying SASC-NG again...
But I am only getting errors... When I try to load the dvbloopback adapter I get this:
linuxmce@dcerouter:~/sasc-ng/trunk$ sudo modprobe dvbloopback
FATAL: Error inserting dvbloopback (/lib/modules/2.6.22-14-generic/kernel/drivers/media/dvb/dvbloopback.ko): Unknown symbol in module, or unknown parameter (see dmesg)
dmesg gives me this:
[ 2049.964000] dvbloopback: disagrees about version of symbol dvb_register_adapter
[ 2049.964000] dvbloopback: Unknown symbol dvb_register_adapter
Quote from: cirion on October 21, 2008, 02:57:58 PM
I'm trying SASC-NG again...
But I am only getting errors... When I try to load the dvbloopback adapter I get this:
linuxmce@dcerouter:~/sasc-ng/trunk$ sudo modprobe dvbloopback
FATAL: Error inserting dvbloopback (/lib/modules/2.6.22-14-generic/kernel/drivers/media/dvb/dvbloopback.ko): Unknown symbol in module, or unknown parameter (see dmesg)
dmesg gives me this:
[ 2049.964000] dvbloopback: disagrees about version of symbol dvb_register_adapter
[ 2049.964000] dvbloopback: Unknown symbol dvb_register_adapter
I reckon that kernel module was probably built for/against a different kernel version, or you're missing other modules/options.
Any tips on what I can do?
I have tried getting older versions of SASC-NG down to revision 167 and I am still getting the same message.
Revisions below 167 dont let me compile the dvbloopback adapter...
May I kindly ask you to not discuss this topic in the forums?
I'm sure you can get some help on irc or some other designated site.
best regards,
Hari