SYNC issues dm500s with commando v12 - Page 4 - UkCvs.org
 

Go Back   UkCvs.org > Digital Tv Box Section > Dreambox Section

Dreambox Section All things dreambox here

Reply
 
LinkBack Thread Tools Display Modes
Old 03-01-2011, 12:08 PM   #31 (permalink)
Developer
UkCvs Senior Member
 
LraiZer's Avatar
 
Join Date: Oct 2008

Posts: 971
iTrader: (0)
Casino cash: $312240
Thanks: 346
Thanked 1,622 Times in 731 Posts
Nominated 19 Times in 7 Posts
Nominated TOTW/F/M Award(s): 7
Groans: 0
Groaned at 0 Times in 0 Posts
Default
Quote:
Originally Posted by PaphosAL View Post
No ideas on that Uncommitted Switch in Zapit Config menu, then?

Cheers- AL
unless you have more than one sat lnb and are running them all through a diseqc switch to your box via a single cable then you can leave setting as it is, this should make it all clear as mud for you



Quote:
DiSEqC = Digital Satellite Equipment Control, this was designed for FTA receivers.
DiSEqC switches come in 2 main flavors, Committed(1.0) and Uncommitted(1.1),
but also Committed 2-way(2.0) and UnCommitted 2-way(2.1).
Committed(1.0) switches are the most common and are what come with the receivers.
These switches require FACTORY software in your FTA to operate properly,
1.0 means your receiver can operate Committed switches ONLY,
1.1 means it can operate Committed AND UnCommitted switches,
1.2 means it can operate Committed and UnCommitted plus DiSEqC motor controls.
2.0 is the same as above,
2.0, 2.1, 2.2 but the receiver can also receive information back from the switch,
2.0 switches receive the pulse command from the receiver, then change ports,
they then send back a confirmation to the receiver, if a 2.0 receiver doesn't
receive the confirmation it will send the DiSEqC pulse again and again until the
switch confirms it is on the right port.
Putting 2 DiSEqC Committed switches on one cable is a no-no, which is why there are
Committed and UnCommitted types of switches, a Committed switch is placed first in
line (DiSEqC pulse comes from the receiver so first would be closest to the receiver),
then you can hookup an UnCommitted switch to the Committed switch, the Committed switch
will ignore the UnCommitted switches commands.
Committed 4x1 switches are about half price of UnCommitted 4x1 switches, so unless
you have to have 16 LNBs hooked up to one receiver stick with Committed switches.
LraiZer is offline   Reply With Quote
The Following 2 Users Say Thank You to LraiZer For This Useful Post:
PaphosAL (03-01-2011), Tyke (04-01-2011)
Old 03-01-2011, 04:35 PM   #32 (permalink)
Nagging Old Git
Team-UkCvs Senior Member
 
PaphosAL's Avatar
 
Join Date: Aug 2008

Location: A park bench, near you
Age: 75
Posts: 3,108
iTrader: (0)
Casino cash: $848260
Thanks: 2,645
Thanked 1,586 Times in 876 Posts
Nominated 2 Times in 2 Posts
Nominated TOTW/F/M Award(s): 2
Groans: 1
Groaned at 0 Times in 0 Posts
Default
Nice one, thanks, LraiZer- that explains that one perfectly. So it's an option for the experts, then? I'll leave well alone, LOL!

Back to head.ko now... The vital bit for the first time boot on a newly-compiled dm500 image appears to start here, at line #46 in the rcS of C12:

Code:
 
# check if /var/.init exist .. then no flash erase is needed .. this is new !
if [ ! -e /var/.init ]; then
# new /var/.init not found.. check if old /var/tmp/init exist.. 
# then not flash erase ist needed
    if [ -e /var/tmp/init ]; then
# ok old /var/tmp/init exist.. no create the new flash_erase detection file..
 touch /var/.init
# delete /var/tmp folder now..  
 rm -rf /var/tmp
# create link to /tmp <- this is mounted to RAM 
 ln -sf /tmp /var/tmp
    else
# flash erase is needed ...     
 init=1
    fi
fi
if [ $init -eq 1 ] ; then 
 cp -a /var_init/* /var
 touch /var/.init
 sync
 umount /var
 /bin/mount -t jffs2 /dev/mtdblock/1 /var
fi
Is it safe to delay the external call to init1 (and the head.ko load) until AFTER this point, or would this be doomed to fail, on account of other init1 related stuff being present prior to line #46, do you think?

Cheers- AL
PaphosAL is offline   Reply With Quote
Old 03-01-2011, 06:25 PM   #33 (permalink)
Developer
UkCvs Senior Member
 
Join Date: Nov 2008

Posts: 209
iTrader: (0)
Casino cash: $104800
Thanks: 210
Thanked 319 Times in 111 Posts
Nominated 2 Times in 1 Post
Nominated TOTW/F/M Award(s): 1
Groans: 0
Groaned at 0 Times in 0 Posts
Default
Quote:
Originally Posted by PaphosAL View Post
Is it safe to delay the external call to init1 (and the head.ko load) until AFTER this point, or would this be doomed to fail, on account of other init1 related stuff being present prior to line #46, do you think?

Cheers- AL
Yes it is
just changed this
Code:
#!/bin/sh

/bin/mount -n -t proc proc /proc
/bin/mount -n -t devpts devpts /dev/pts
export INSMOD="/sbin/insmod"
export RMMOD="/sbin/rmmod"
export MODDIR="/lib/modules/"$(uname -r)
#export TZ=CET-1CEST,M3.5.0/2,M10.5.0/3
/etc/init.d/init1

#set environment variables ( mID )
. /proc/bus/dbox.sh

# check if no DM500
if [ $mID -ne 07 ] ; then
    init=0
    /bin/boot || init=1
    if [ $init -eq 1 ] ; then
        /bin/eraseall /dev/mtd/1
    fi
fi

# do not mount jffs2 when not booting from flash
if [ ! -e /root/platform/kernel/bild ] ; then
    mount -t jffs2 /dev/mtdblock/1 /var
fi


/bin/mount -t ramfs none /tmp
# /var/run links here
mkdir /tmp/run
init=0

# check if /var/.init exist .. then no flash erase is needed .. this is new !
if [ ! -e /var/.init ]; then
# new /var/.init not found.. check if old /var/tmp/init exist.. 
# then not flash erase ist needed
    if [ -e /var/tmp/init ]; then
# ok old /var/tmp/init exist.. no create the new flash_erase detection file..
    touch /var/.init
# delete /var/tmp folder now..     
    rm -rf /var/tmp
# create link to /tmp <- this is mounted to RAM 
    ln -sf /tmp /var/tmp
    else
# flash erase is needed ...     
    init=1
    fi
fi

if [ $init -eq 1 ] ; then 
    cp -a /var_init/* /var
    touch /var/.init
    sync
    umount /var
    /bin/mount -t jffs2 /dev/mtdblock/1 /var
fi

ln -sf sound/dsp /dev/dsp
To this

Code:
#!/bin/sh

/bin/mount -n -t proc proc /proc
/bin/mount -n -t devpts devpts /dev/pts
export INSMOD="/sbin/insmod"
export RMMOD="/sbin/rmmod"
export MODDIR="/lib/modules/"$(uname -r)
# check if no DM500
if [ $mID -ne 07 ] ; then
    init=0
    /bin/boot || init=1
    if [ $init -eq 1 ] ; then
        /bin/eraseall /dev/mtd/1
    fi
fi

# do not mount jffs2 when not booting from flash
if [ ! -e /root/platform/kernel/bild ] ; then
    mount -t jffs2 /dev/mtdblock/1 /var
fi


/bin/mount -t ramfs none /tmp
# /var/run links here
mkdir /tmp/run
init=0

# check if /var/.init exist .. then no flash erase is needed .. this is new !
if [ ! -e /var/.init ]; then
# new /var/.init not found.. check if old /var/tmp/init exist.. 
# then not flash erase ist needed
    if [ -e /var/tmp/init ]; then
# ok old /var/tmp/init exist.. no create the new flash_erase detection file..
    touch /var/.init
# delete /var/tmp folder now..     
    rm -rf /var/tmp
# create link to /tmp <- this is mounted to RAM 
    ln -sf /tmp /var/tmp
    else
# flash erase is needed ...     
    init=1
    fi
fi

if [ $init -eq 1 ] ; then 
    cp -a /var_init/* /var
    touch /var/.init
    sync
    umount /var
    /bin/mount -t jffs2 /dev/mtdblock/1 /var
fi
#export TZ=CET-1CEST,M3.5.0/2,M10.5.0/3
/etc/init.d/init1

#set environment variables ( mID )
. /proc/bus/dbox.sh



ln -sf sound/dsp /dev/dsp
so just moved the
Code:
#export TZ=CET-1CEST,M3.5.0/2,M10.5.0/3
/etc/init.d/init1

#set environment variables ( mID )
. /proc/bus/dbox.sh
to after all the jffs mounting crud.

box boots fine.
now it needs a test with a commando image and a different head.ko file.

Will still need in the init1 file
Code:
if [ -f /lib/modules/$(uname -r)/.reload_modules ] ; then
    $RMMOD $MODDIR/extra/head.ko
    $RMMOD /var/driver/head.ko
fi
if [ -e /var/driver/head.ko ] ; then
$INSMOD /var/driver/head.ko
else
$INSMOD $MODDIR/extra/head.ko
fi
pointless moving the existing head.ko file.
scruff1963 is offline   Reply With Quote
The Following User Says Thank You to scruff1963 For This Useful Post:
PaphosAL (03-01-2011)
Old 03-01-2011, 07:08 PM   #34 (permalink)
Nagging Old Git
Team-UkCvs Senior Member
 
PaphosAL's Avatar
 
Join Date: Aug 2008

Location: A park bench, near you
Age: 75
Posts: 3,108
iTrader: (0)
Casino cash: $848260
Thanks: 2,645
Thanked 1,586 Times in 876 Posts
Nominated 2 Times in 2 Posts
Nominated TOTW/F/M Award(s): 2
Groans: 1
Groaned at 0 Times in 0 Posts
Default
Disagree about the pointlessness of moving the existing head.ko from $MODDIR/extra - you haven't thought this through fully.

We need the new one in /var_init/driver to copy to the new /var/driver when it's first created, don't we? So why have two in squashfs root, when one will suffice?

Your earlier fall-back code to load from /var_init/driver looked flawless to me...

PaphosAL is offline   Reply With Quote
Old 03-01-2011, 07:21 PM   #35 (permalink)
Developer
UkCvs Senior Member
 
Join Date: Nov 2008

Posts: 209
iTrader: (0)
Casino cash: $104800
Thanks: 210
Thanked 319 Times in 111 Posts
Nominated 2 Times in 1 Post
Nominated TOTW/F/M Award(s): 1
Groans: 0
Groaned at 0 Times in 0 Posts
Default
Quote:
Originally Posted by PaphosAL View Post
Disagree about the pointlessness of moving the existing head.ko from $MODDIR/extra - you haven't thought this through fully.

We need the new one in /var_init/driver to copy to the new /var/driver when it's first created, don't we? So why have two in squashfs root, when one will suffice?

Your earlier fall-back code to load from /var_init/driver looked flawless to me...

You havn't thought it out Al
If you leave the original where it's supposedto be then space is where it was.
If you put it into /var_init/etc/driver then on 1st boot it will be put into /var/etc/driver taking space from the jffs which isn't needed as it exists in the squashfs area.
Only people needing a different one need to lose the space in /var or do I take it space is no longer an issue ?
If you leave it where it is then there is no need for one in /var/etc/driver or /var_init/etc/driver unless the user needs to use the space in /var then they just put one into /var/etc/driver which will take precedence over the one in /lib/modules/2.6.9/extra which is why I did this bit of code
Code:
if [ -f /lib/modules/$(uname -r)/.reload_modules ] ; then
    $RMMOD $MODDIR/extra/head.ko
    $RMMOD /var/driver/head.ko
fi
if [ -e /var/driver/head.ko ] ; then
$INSMOD /var/driver/head.ko
else
$INSMOD $MODDIR/extra/head.ko
fi
In the init1 file

I don't understand your obsession with space but I tailored it to keep you happy and your trying to throw away 300kb of it
scruff1963 is offline   Reply With Quote
Reply

Bookmarks


Currently Active Users Viewing This Thread: 1 (0 members and 1 guests)
 
Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On


All times are GMT. The time now is 08:57 AM.


Powered by vBulletin® Version 3.7.4
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.
Search Engine Friendly URLs by vBSEO 3.3.0
Any information provided on this site is not guaranteed in any way. Some articles may discuss topics that are illegal, so this information is provided for educational purposes only, use at your own risk !! Ukcvs.org cannot be held responsible for the content of any post on this forum.