Posts by Jeffzapp

Hi Everyone

I guess your all stumped. Anyway I found this (below) in my /emu/log/check.log file and I assume this is what is causeing my problem.

After googleing *** stack smashing detected ***: /emu/cccam/CCcam.x86 terminated I came up with this answer from someone who has the same problem.

(who is responsible for this mistake? The programmer. It tries to use more memory than is actually available. Your standardmaeszig GCC has been patched by Debian so that instead of allowing a memory access error,it prints a warning message and prevents a buffer overflow.)

They say that you should use CCcam 2.0.9 to solve the problem as 2.0.9 is very stable whereas 2.1.3 etc is not. The only problem is that I have heared that 2.0.9 will not run along side oscam. Is this true??? Has anyone else had this problem? is there a fix for it.

*** stack smashing detected ***: /emu/cccam/CCcam.x86 terminated
======= Backtrace: =========
/lib/i686/cmov/libc.so.6(__fortify_fail+0x50)[0xb75ddaa0]
/lib/i686/cmov/libc.so.6(+0xe0a4a)[0xb75dda4a]
/emu/cccam/CCcam.x86[0x8079555]
/emu/cccam/CCcam.x86[0x8079a57]
/emu/cccam/CCcam.x86[0x806955b]
/emu/cccam/CCcam.x86[0x80bfb34]
/emu/cccam/CCcam.x86[0x80bfca5]
/lib/i686/cmov/libpthread.so.0(+0x5955)[0xb7783955]
/lib/i686/cmov/libc.so.6(clone+0x5e)[0xb75c91de]
======= Memory map: ========
08048000-08105000 r-xp 00000000 08:01 4915287 /emu/cccam/CCcam.x86
08105000-08106000 r--p 000bc000 08:01 4915287 /emu/cccam/CCcam.x86
08106000-08108000 rw-p 000bd000 08:01 4915287 /emu/cccam/CCcam.x86
08108000-0810e000 rw-p 00000000 00:00 0
09322000-09381000 rw-p 00000000 00:00 0 [heap]
b2afb000-b2afc000 ---p 00000000 00:00 0
b2afc000-b32fc000 rw-p 00000000 00:00 0
b32fc000-b32fd000 ---p 00000000 00:00 0
b32fd000-b3afd000 rw-p 00000000 00:00 0
b3afd000-b3afe000 ---p 00000000 00:00 0
b3afe000-b42fe000 rw-p 00000000 00:00 0
b42fe000-b42ff000 ---p 00000000 00:00 0
b42ff000-b4aff000 rw-p 00000000 00:00 0
b4aff000-b4b00000 ---p 00000000 00:00 0
b4b00000-b5300000 rw-p 00000000 00:00 0
b5300000-b5326000 rw-p 00000000 00:00 0
b5326000-b5400000 ---p 00000000 00:00 0
b54b9000-b54bb000 r-xp 00000000 08:01 5644801 /lib/libnss_mdns4.so.2
b54bb000-b54bc000 rw-p 00001000 08:01 5644801 /lib/libnss_mdns4.so.2
b54cb000-b54cc000 ---p 00000000 00:00 0
b54cc000-b5ccc000 rw-p 00000000 00:00 0
b5ccc000-b5cdc000 r-xp 00000000 08:01 5661188 /lib/i686/cmov/libresolv-2.11.3.so
b5cdc000-b5cdd000 r--p 00010000 08:01 5661188 /lib/i686/cmov/libresolv-2.11.3.so
b5cdd000-b5cde000 rw-p 00011000 08:01 5661188 /lib/i686/cmov/libresolv-2.11.3.so
b5cde000-b5ce0000 rw-p 00000000 00:00 0
b5ce0000-b5ce4000 r-xp 00000000 08:01 5661203 /lib/i686/cmov/libnss_dns-2.11.3.so
b5ce4000-b5ce5000 r--p 00004000 08:01 5661203 /lib/i686/cmov/libnss_dns-2.11.3.so
b5ce5000-b5ce6000 rw-p 00005000 08:01 5661203 /lib/i686/cmov/libnss_dns-2.11.3.so
b5ce6000-b5ce8000 r-xp 00000000 08:01 5644798 /lib/libnss_mdns4_minimal.so.2
b5ce8000-b5ce9000 rw-p 00001000 08:01 5644798 /lib/libnss_mdns4_minimal.so.2
b5cf8000-b5cf9000 ---p 00000000 00:00 0
b5cf9000-b64f9000 rw-p 00000000 00:00 0
b64f9000-b64fa000 ---p 00000000 00:00 0
b64fa000-b6cfa000 rw-p 00000000 00:00 0
b6cfa000-b6cfb000 ---p 00000000 00:00 0
b6cfb000-b74fd000 rw-p 00000000 00:00 0
b74fd000-b763d000 r-xp 00000000 08:01 5661202 /lib/i686/cmov/libc-2.11.3.so
b763d000-b763e000 ---p 00140000 08:01 5661202 /lib/i686/cmov/libc-2.11.3.so
b763e000-b7640000 r--p 00140000 08:01 5661202 /lib/i686/cmov/libc-2.11.3.so
b7640000-b7641000 rw-p 00142000 08:01 5661202 /lib/i686/cmov/libc-2.11.3.so
b7641000-b7644000 rw-p 00000000 00:00 0
b7644000-b7661000 r-xp 00000000 08:01 5644291 /lib/libgcc_s.so.1
b7661000-b7662000 rw-p 0001c000 08:01 5644291 /lib/libgcc_s.so.1
b7662000-b7686000 r-xp 00000000 08:01 5661184 /lib/i686/cmov/libm-2.11.3.so
b7686000-b7687000 r--p 00023000 08:01 5661184 /lib/i686/cmov/libm-2.11.3.so
b7687000-b7688000 rw-p 00024000 08:01 5661184 /lib/i686/cmov/libm-2.11.3.so
b7688000-b7771000 r-xp 00000000 08:01 6219815 /usr/lib/libstdc++.so.6.0.13
b7771000-b7775000 r--p 000e9000 08:01 6219815 /usr/lib/libstdc++.so.6.0.13
b7775000-b7776000 rw-p 000ed000 08:01 6219815 /usr/lib/libstdc++.so.6.0.13
b7776000-b777e000 rw-p 00000000 00:00 0
b777e000-b7793000 r-xp 00000000 08:01 5661192 /lib/i686/cmov/libpthread-2.11.3.so
b7793000-b7794000 r--p 00014000 08:01 5661192 /lib/i686/cmov/libpthread-2.11.3.so
b7794000-b7795000 rw-p 00015000 08:01 5661192 /lib/i686/cmov/libpthread-2.11.3.so
b7795000-b7797000 rw-p 00000000 00:00 0
b7797000-b77a0000 r-xp 00000000 08:01 5661187 /lib/i686/cmov/libcrypt-2.11.3.so
b77a0000-b77a1000 r--p 00008000 08:01 5661187 /lib/i686/cmov/libcrypt-2.11.3.so
b77a1000-b77a2000 rw-p 00009000 08:01 5661187 /lib/i686/cmov/libcrypt-2.11.3.so
b77a2000-b77c9000 rw-p 00000000 00:00 0
b77cb000-b77d5000 r-xp 00000000 08:01 5661189 /lib/i686/cmov/libnss_files-2.11.3.so
b77d5000-b77d6000 r--p 00009000 08:01 5661189 /lib/i686/cmov/libnss_files-2.11.3.so
b77d6000-b77d7000 rw-p 0000a000 08:01 5661189 /lib/i686/cmov/libnss_files-2.11.3.so
b77d7000-b77da000 rw-p 00000000 00:00 0
b77da000-b77db000 r-xp 00000000 00:00 0 [vdso]
b77db000-b77f6000 r-xp 00000000 08:01 5644304 /lib/ld-2.11.3.so
b77f6000-b77f7000 r--p 0001b000 08:01 5644304 /lib/ld-2.11.3.so
b77f7000-b77f8000 rw-p 0001c000 08:01 5644304 /lib/ld-2.11.3.so
bfae0000-bfaf5000 rw-p 00000000 00:00 0 [stack]
(UNKNOWN) [127.0.0.1] 16000 (?) : Connection refused
CCcam is not running, Restarting...
Pidfile allready found, Removing old pidfile
Restarting CCcam Server
kill: 63: Usage: kill [-s sigspec | -signum | -sigspec] [pid | job]... or
kill -l [exitstatus]
CCcam is running
CCcam is running
CCcam is running

Regards

Hi Everyone.

I have had my Debian server (CCcam 2.1.3/oscam) running flawlessly for 2 months without 1 problem then all of a sudden yesterday CCcam just started stoping whenever it feels like then after a couple of minutes it restarts itself. I have gone through everything (debug file etc) and the .cfg file hasn’t been altered in any way and all seems ok. I have finally done a format but the problem is still there. Any ideas would be appreciated. At my witts end.

Regards

h**p://tv.s*y.com/tv-guide

It's ok sussed it out.

Regards

Hi Ten

Could you point me in the direction of the latest or most stable Oscam file that is compatable with this setup. Ive looked in the Latest Oscam link at the top but i'm a bit confused as there is so many versions. Ive had this installed and running flawlesly for a week running 2 locals and all of a sudden it just wont see 1 of the cards. Checked everything seen no problems. Swapped the hub and cards to my backup and up and running strait away with no problems (as of yet)

This version for (AMD64) comes with oscam build 6012, My back up is Debian for Intel and that installs with Oscam svn 7029. I think the svn7029 seems far more stable. If you could help that would be great.

Regards

Hi Ten

When I go to here (Index of /debian-cd/current-live/amd64/bt-hybrid) it lists 6. Is there any one of them in particular I should use?

Regards

Thank Ten. I love this fooking forum. Just what I was after.

Regards

Hi Everyone

Is it possible to manualy insert an ip address you want to block into the iptables in Debian 6? I have tried the command iptables -L INPUT -s ???.???.???.??? -j DROP but I just get bash: iptables: command not found. Could anyone help please?

Regards

If you do what Ten suggests you will over come your problem m8.

Regards

Have I asked a stupid question???

Regards

Hi Everyone

Is there an e2 cccam2.1.3 oscam ipk file anywhere that will do the above available?

Regards

Hi Everyone

I have sorted it now. I was being a bit lazy and not using the serch button to solve the problem. I just followed this link below and everything installed as it should and is working fine.

http://linuxsat-support.com/li…cccam-oscam-amd64bit.html

Regards

Hi Everyone

I have installed Debian-6.0.6-amd64-netinst.iso as my pc is an AMD64.

I ran the Automated Oscam/CCcam 2.1.3 Install Package For Debian 6 and it seemed to install ok but it obviously hasn't because it wont work.

This is the install script from the terminal below. I can see that some directories are missing and I assume that because I haven’t used the Debian 32 net install package this is the reason for the failed install.

I used Tens Automated Oscam/CCcam 2.1.3 Install Package For Debian 6 on my Intel based machine and it installed and runs flawlessly. I also installed it on my AMD64 PC using the Debian 32 net install package and it installed and ran ok but it didn't run very smooth and kept crashing. I assumed that the reason for this is that the AMD64 PC doesn't like the Debian 32 net install package because I assume it is for Intel based machine's so that’s why I downloaded the Debian-6.0.6-amd64-netinst.iso hopeing that it may do the trick.

So what I am really asking is would it be possible for Ten to tweak his very user friendly Automated Oscam/CCcam 2.1.3 Install Package For Debian 6 to suit the AMD64 PC and the Debian-6.0.6-amd64-netinst.iso?

Starting download of installation script
Download successfull
Creating folders (if needed)
Unpacking installation files
cccam.sh
check.sh
configupdate.sh
illegal.sh
phpinfo/
phpinfo/entitlementstats.php
phpinfo/update.php
phpinfo/clientstats.php
phpinfo/CCcam.providers
phpinfo/node.php
phpinfo/pingAll.php
phpinfo/login.php
phpinfo/config.php
phpinfo/configserver.php
phpinfo/getconfigserver.php
phpinfo/CCcam_fake.providers
phpinfo/provider.php
phpinfo/CCcam_used.providers
phpinfo/common.php
phpinfo/server.php
phpinfo/cron_online.php
phpinfo/client.php
phpinfo/providerstats.php
phpinfo/cron_update.php
phpinfo/cron_ping.php
phpinfo/meniu.php
phpinfo/index.php
phpinfo/country.code
phpinfo/nodestats.php
phpinfo/readme.txt
phpinfo/cccam.css
phpinfo/serverstats.php
phpinfo/pairstats.php
runonce.sh
vsftpd.conf
phpinfo/CCcam.x86
phpinfo/oscam.x86
oscript.sh
rc.local
CCcam.cfg
oscam.conf
oscam.server
oscam.user
CCcam.x86
oscam
Moving script files to their right directory

mv: cannot stat `/tmp/ccinst/CCcam.x86_64': No such file or directory
chmod: cannot access `/emu/cccam/CCcam.x86_64': No such file or directory

Downloading and installing various needed programs like apache, ftp, ssh...
This is needed for the webinfo tool to work
This might take some time to download and install (depending on computer and network speeds)
################# Congratulations #################
You're server is ready to run.
Demo configs included
Please reboot your machine now

Regards

I do it 2 weeks before m8.

Regards

As far as I am aware m8 you don't have to enter your boxkey or boxid in oscam as it does it for you. If you want to update your entitlements you need to enter the following in your oscam.server file
blockemm-u = 0
blockemm-s = 0
blockemm-g = 1
blockemm-unknown = 1

After your card has updated change the value's I.E = 0, = 0, = 1 BACK TO = 1 = 1 = 1 to block all ecm trafic.

This works for me anyway

Regards

Hi Everyone

Panic over ha ha. The fight has just shown up on the Aljazeera web site (h**p://www.en.aljazeerasport.tv/Schedule) It's on Aljazeera + 3. Under live events choose boxing from the drop down box. It starts at around 7.15pm our time as there 3 hours ahead of us. Looks like the full card as well. Loverly Jubble!!!

It's on Orange Sport as well. Part of the Cyfra + package on Hotbird.

Regards

Hi Everyone

Here is how I cleared Primetime on a TM5402 HD.

First insert a USB stick into your 5402 and upload your channel data. (It will be a CNDF file)

Remove the USB stick and put it in your PC.

Download the TM-1000-5000-6000 series ChannelEditor.exe file. (I think the links are down in the TM download centre so I googled it and found it)

Open the editor then open your CNDF file.

Scroll down to ASTRA2/Eurobird and click on the +,

Scroll down to transponder number 12523 and click on the +

Click on Primetime

In the Service ID box (top right) change the Service ID to 0xd6e5

At the bottom tick the Don't update video/audio PIDs box

Click ok, Save and send it back to your box.

Regards

[quote='Jeffzapp','https://linuxsat-support.com/index.php?thread/&postID=84102#post84102']Hi Everyone

First of all the new Primetime frequency is 12523 H 27500 2/3.

I will now explain how I got Primetime to clear on a DM800 and a DM500

First use Dreamedit and download your channel list,

Open the channel list and find Primetime and highlight it, then right click it, click on (Show/Edit details),

First change Service Type to the number 1,

Then change the Service ID to 55013, Now go to the pids section and enter the numbers 2348 in the Video box then the numbers 2349 in the Audio box.

Now in the flags box below make sure the box with the letter K is checked and this box only.

Click on Save and send it back to your box.

Primetime should now be open.

I will follow this thread with How to open Primetime on a Technomate TM5400 HD.

Regards[/QUOTE

Sorry everyone It's How to open Primetime on a TM5402 HD and not a TM5400 HD.

Regards

Hi Everyone

First of all the new Primetime frequency is 12523 H 27500 2/3.

I will now explain how I got Primetime to clear on a DM800 and a DM500

First use Dreamedit and download your channel list,

Open the channel list and find Primetime and highlight it, then right click it, click on (Show/Edit details),

First change Service Type to the number 1,

Then change the Service ID to 55013, Now go to the pids section and enter the numbers 2348 in the Video box then the numbers 2349 in the Audio box.

Now in the flags box below make sure the box with the letter K is checked and this box only.

Click on Save and send it back to your box.

Primetime should now be open.

I will follow this thread with How to open Primetime on a Technomate TM5400 HD.

Regards

It's ok everyone I found them in /emu/

Regards