SamyGo Extension Pack modified for NFS recording

Here are software that related with Samsung C series TVs, applications, programs that will run in your TV or computer...:!:This forum is NOT FOR USER QUESTIONS or Problems.

Rohel
Posts: 28
Joined: Sun Apr 22, 2012 3:49 pm

Re: SamyGo Extension Pack modified for NFS recording

Post by Rohel » Tue Apr 24, 2012 4:29 pm

hi
i have a little problem activating PVR over NFS on my D6
i have applyed hospitality hack, so i have SamyGo Widget on the TV memory, not on a USB drive

It seems that its mandatory to exec samygo from the same USB drive where you store the xfs image. Im correct?
If i have to exec the USB hosted sammyapp, how can i do?
If its no mandatory, what i have to do to reference the XFS image on the init scripts?

User avatar
beatfreak
SamyGO Project Donor
Posts: 539
Joined: Tue Aug 23, 2011 9:03 am
Location: Hamburg
Contact:

Re: SamyGo Extension Pack modified for NFS recording

Post by beatfreak » Fri Nov 02, 2012 9:17 am

hi everybody,

as i currently only have a 1G usb pendrive available i thought of mounting a nfs share containing the xfs-image so that the structure would look like

directory with xfs-image
(via nfs mount of exportA) in your suggested solution this would be on already mounted usb drive
..virtual XFS USB Drive
..(via mount of xfs-image)
....recording dir
....(via nfs mount of exportB)

the question ist if it would produce double traffic for recording as the chain goes tv-server-tv-server..?



btw.
i had a look at current init scripts in unzipped extensons folder with 80_80_record_to_nwshare.init.kayaweed included
the xfs image will be created during execution but i cant find any point where placeholder file will be created, it only gets checked for existance..

and i'm not clear about the record_to_nwshare scripts (the ".init" and the ".init.remi71") version, the script content is so completely different that i think both of them have to be executed, but as only one of them has the extansion .init this won't be the case... or is there a point where remi-script is called anyway?

in vusb init script we check if xfs_img is present in samygo dir, but as nfsmount script will be called later there will be no image available at this point...(if my xfs_img is located at a nfs share)
now i could
a) change the order of script execution so that nfs mounts happen before vusb execution --> wont work since nfsmount relies on a vusb drive to get its mountpoints...

b) after nfsmount script recall vusb script ??

c) copy pvrimage check-code from vusb script to nfsmount script and have it executed after successful mount

d) ignore the "pvrimage not present - record over nfs won't be enabled" message

meanwhile i bought a 4G pendrive and nfs recording is working fine (speedtest with dd gets about 9MB/s but Samsung performancetest says its not suitable)

but it would still be nice to have the xfs image available via nfs, then people wo have extensions in TV-flash won't need the pendrive anymore...
//UE40C6500 @ T-VALDEUC 3011 // rooted manual HotelMode style // PVR to NFS via 18MB on-the-fly sparse XFS //
FYI: you can close your ssh session with SamyGO with

Code: Select all

~.
If you can't fix it using dvct tape, you are not using enough dvct tape.

lexyan
Posts: 4
Joined: Thu Aug 23, 2012 7:33 am
Location: France

Re: SamyGo Extension Pack modified for NFS recording

Post by lexyan » Sat Nov 17, 2012 10:41 am

Hi All

i modified remi71 init.d scripts and official init.d scripts to avoid the need of the xfs image on usb pen

all i do is installing mofidied g_file_storage.ko to allow custom names of virtual device => viewtopic.php?t=4722&p=35336

and make the virtual device removable in the vusb init script.

I test the mod on my UE40D6530 with firmware 1021.1 and hospitality hack

scheduled recording worked properly

PS : sorry for my english, it s not my native language
You do not have the required permissions to view the files attached to this post.

User avatar
beatfreak
SamyGO Project Donor
Posts: 539
Joined: Tue Aug 23, 2011 9:03 am
Location: Hamburg
Contact:

Re: SamyGo Extension Pack modified for NFS recording

Post by beatfreak » Sun Nov 18, 2012 8:30 pm

hi lexyan,

could you please explain it more detailed?
do you need no xfs image at all or do you have it moved to another location?
and what steps would be exactly necessary to reproduce this patch?
//UE40C6500 @ T-VALDEUC 3011 // rooted manual HotelMode style // PVR to NFS via 18MB on-the-fly sparse XFS //
FYI: you can close your ssh session with SamyGO with

Code: Select all

~.
If you can't fix it using dvct tape, you are not using enough dvct tape.

User avatar
juusso
SamyGO Moderator
Posts: 9604
Joined: Sun Mar 07, 2010 6:20 pm

Re: SamyGo Extension Pack modified for NFS recording

Post by juusso » Sun Nov 18, 2012 8:34 pm

he mounts xfs image from another nfs share which is mounted before. Means xfs image needed, but not on TV.
LE40B653T5W,UE40D6750
Have questions? Read SamyGO Wiki, Search on forum first!
FFB (v0.8), FFB for CI+ . Get root on: C series, D series, E series, F series, H series, exeDSP/exeTV patches[C/D/E/F/H]

DO NOT EVER INSTALL FIRMWARE UPGRADE

lexyan
Posts: 4
Joined: Thu Aug 23, 2012 7:33 am
Location: France

Re: SamyGo Extension Pack modified for NFS recording

Post by lexyan » Sun Nov 18, 2012 10:01 pm

beatfreak wrote:hi lexyan,

could you please explain it more detailed?
do you need no xfs image at all or do you have it moved to another location?
and what steps would be exactly necessary to reproduce this patch?
Hi Beatfreak,

I explain a little :

for my mod to function, yu need the modified version of g_file_storage.ko (viewtopic.php?t=4722&p=35336), it permits to change the name of the virtual usb device.

- in the vusb init script I change the line loading the module with removable=1 and luns=2 (2 virtual usb, maximum 8 possible)

Code: Select all

insmod $MOD_DIR/kernel/drivers/usb/gadget/g_file_storage.ko removable=1 luns=2 model="SamyGo,Recorder"
removable permits loading dynamicaly the image of the device

I load the original vusb image created by the script as usual

Code: Select all

echo '/dtv/vusb' > /sys/devices/platform/dummy_udc/gadget/gadget-lun0/file
- i use the nfsmount init script by remi for multiple nfs shares and modified for custom share name

- in the record_to_nwshare init script some variables

Code: Select all

# Name of the xfs image file on the server
XFSFILE='xfs_img'

# Remote NFS fileserver for recording 
PVRSERVER='192.168.1.250'

# Remote NFS share for recording
XFSPATH='/home/alexandre/nfs_dir'

# Remote NFS share for recording
PVRPATH="$XFSPATH/pvr_record"
then i affect the xfs image wich is on the nfs share to the second virtual usb device

Code: Select all

# if xfs_image found on nfs share mount it on second virtual usb
	if [ -e "$NFS_PATH/$XFSFILE" ]; then
		WriteToLog "Found $XFSFILE on $NFS_PATH try to plug it on removable usb" 1
		echo "$NFS_PATH/$XFSFILE" > /sys/devices/platform/dummy_udc/gadget/gadget-lun1/file
and mount the nfs share on it like remi71 does.

in the zip i linked in my other post you find the xfs_img file (1,5Go gziped in 35ko) you must store it in a share on the nfs server

the other files (init script) goes to the TV in the SamyGO folder etc/init.d/

you must modify the script variable in accordance with your nfs shares
mine are :

Code: Select all

Serveur (IP 192.168.1.250) => /home/alexandre/nfs_dir/ -> xfs_img
                                                       -> pvrrecord/ -> CONTENT/
                                                                     -> database/

User avatar
pohybel
Posts: 45
Joined: Wed Jun 13, 2012 4:35 pm
Location: Poland

Re: SamyGo Extension Pack modified for NFS recording

Post by pohybel » Wed Nov 21, 2012 9:27 pm

Right now modified g_file_storage.ko is also available for C-series TVs => SamyGo virtual drive MOD

User avatar
beatfreak
SamyGO Project Donor
Posts: 539
Joined: Tue Aug 23, 2011 9:03 am
Location: Hamburg
Contact:

Re: SamyGo Extension Pack modified for NFS recording

Post by beatfreak » Thu Nov 22, 2012 10:13 pm

so the way i understand this, the point of renaming the Virtual USB Drive is negligible, we just need to create one more where we later mount the xfs image right after nfs share is accessible. after this the remi71-script record_to_nwshare may run as usual as it only looks for placeholder file in mounted xfs image and then mounts second nfs-share over mounted xfs-image...?
//UE40C6500 @ T-VALDEUC 3011 // rooted manual HotelMode style // PVR to NFS via 18MB on-the-fly sparse XFS //
FYI: you can close your ssh session with SamyGO with

Code: Select all

~.
If you can't fix it using dvct tape, you are not using enough dvct tape.

lexyan
Posts: 4
Joined: Thu Aug 23, 2012 7:33 am
Location: France

Re: SamyGo Extension Pack modified for NFS recording

Post by lexyan » Fri Nov 23, 2012 3:24 pm

beatfreak wrote:so the way i understand this, the point of renaming the Virtual USB Drive is negligible, we just need to create one more where we later mount the xfs image right after nfs share is accessible. after this the remi71-script record_to_nwshare may run as usual as it only looks for placeholder file in mounted xfs image and then mounts second nfs-share over mounted xfs-image...?
it's exactly this, we create a second virtual usb device and mount the xfs image file on it then the script from remi71 takes over

Cichas
Posts: 11
Joined: Tue May 08, 2012 12:45 am
Location: Czech Republic

Re: SamyGo Extension Pack modified for NFS recording

Post by Cichas » Sat Nov 24, 2012 10:28 pm

BTW: you do not need two USB drives. With "mount -o bind" you need only one. And also you can use original g_file_storage.ko for such solution.

More details: viewtopic.php?f=9&t=4034

Post Reply

Return to “[C] Software”