Difference between revisions of "Change Media Server Name"
(Created page with "If you have more than one Humax HDR Fox-T2 on the same network and use the '''Content Sharing (DLNA Server)''' feature, you may wish to change the name that they use to advertise...") |
Ezra pound (talk | contribs) (Undo revision 5207 by Ezra pound (talk)) (Tag: Undo) |
||
(23 intermediate revisions by 2 users not shown) | |||
Line 1: | Line 1: | ||
− | If you have | + | __NOTOC__ |
+ | |||
+ | <big><big>{{Note|There is a Custom Firmware package called DLNA-Servername that can change the Media Server name of your Humax without having to follow the procedure below}}</big></big> | ||
+ | |||
+ | |||
+ | If you have multiple Humax HDR Fox-T2s on the same network and use the ''Content Sharing (DLNA Server)'' feature, you may wish to change the name that they use to advertise themselves on the network. The following instructions take you through the process of creating a new '''customised firmware update file''' to change the name. The commands are all run on the Humax itself. | ||
== Gain telnet access to your Humax command prompt == | == Gain telnet access to your Humax command prompt == | ||
− | Follow the instructions [[ | + | Follow the instructions [[Telnet|at http://wiki.humy.tv/wiki/Telnet]] |
+ | |||
+ | Once you have connected to the Humax command line then you will see a prompt that is the hostname followed by a hash (#) character, like this: | ||
− | |||
humax# | humax# | ||
− | The commands in the following sections show this prompt for context but you should not type it. | + | The commands in the following sections show this prompt for context but you should not type it. The command that you need to type will be shown <span style="background:#FFFF00">'''in bold with yellow background'''</span> whereas the prompt and other output that you will see is shown in normal font. |
== Install the required packages == | == Install the required packages == | ||
Line 20: | Line 26: | ||
Since you're already at the command prompt, you can just install them using the <tt>opkg</tt> command: | Since you're already at the command prompt, you can just install them using the <tt>opkg</tt> command: | ||
− | humax# opkg install humidify squashfs-tools bsed | + | humax# <span style="background:#FFFF00">'''opkg update'''</span> |
+ | Downloading http://hummypkg.org.uk/hdrfoxt2/base/Packages.gz. | ||
+ | Inflating http://hummypkg.org.uk/hdrfoxt2/base/Packages.gz. | ||
+ | Updated list of available packages in /mod/var/opkg/base. | ||
+ | humax# <span style="background:#FFFF00">'''opkg install humidify squashfs-tools bsed'''</span> | ||
+ | Installing humidify (1.0.2) to root... | ||
+ | Downloading http://hummypkg.org.uk/hdrfoxt2/base/humidify_1.0.2_mipsel.opk. | ||
+ | Installing squashfs-tools (3.1r2) to root... | ||
+ | Downloading http://hummypkg.org.uk/hdrfoxt2/base/squashfs-tools_3.1r2_mipsel.opk. | ||
+ | Installing bsed (1.0.0) to root... | ||
+ | Downloading http://hummypkg.org.uk/hdrfoxt2/base/bsed_1.0.0_mipsel.opk. | ||
+ | Configuring humidify. | ||
+ | Configuring bsed. | ||
+ | Configuring squashfs-tools. | ||
+ | |||
+ | == Insert a USB Flash drive containing the firmware update == | ||
+ | |||
+ | Put the '''customised firmware update file''' onto a USB flash drive, just as you would to apply the update, and plug it into your Humax. Just as with an update, the firmware bundle should be the only thing on the disk. Since the Humax is already turned on, it will not try and apply the update. If your TV is turned on and the Humax input is selected then the screen may show the ''loading USB'' and ''Video/Music/Photo/Copy'' box. This can be dismissed with the ''Exit'' button or just ignored until it times out. | ||
+ | |||
+ | Unless you have any other drives connected, this USB flash drive will now be mounted into the Humax filesystem as ''/media/drive1''. Change into that directory and list the contents: | ||
+ | |||
+ | humax# <span style="background:#FFFF00">'''cd /media/drive1'''</span> | ||
+ | humax# <span style="background:#FFFF00">'''ls'''</span> | ||
+ | HDR_FOX_T2_upgrade.hdf | ||
+ | |||
+ | == Unpacking the firmware bundle == | ||
+ | |||
+ | Unpack the firmware bundle using ''humidify''. This takes around 30 seconds. | ||
+ | |||
+ | humax# <span style="background:#FFFF00">'''humidify -x HDR_FOX_T2_upgrade.hdf'''</span> | ||
+ | HDF Tool v1.0.2, by af123, 2011. | ||
+ | |||
+ | Opening HDR_FOX_T2_upgrade.hdf, 17176677 bytes. | ||
+ | |||
+ | Blocks: 527 | ||
+ | Model: 4 | ||
+ | System ID: 80bc.7e00 | ||
+ | |||
+ | x 1.hdfbin-1-000000.raw (17223680 bytes) | ||
+ | |||
+ | Processed in: 22.97s | ||
+ | humax# <span style="background:#FFFF00">'''ls'''</span> | ||
+ | 1.hdfbin-1-000000.raw HDR_FOX_T2_upgrade.hdf | ||
+ | |||
+ | There are now two files on the USB drive. | ||
+ | |||
+ | == Extract the file system == | ||
+ | |||
+ | Extract the filesystem using ''unsquashfs''. This takes around 5 seconds. | ||
+ | |||
+ | humax# <span style="background:#FFFF00">'''unsquashfs -d /mod/tmp/firmware 1.hdfbin-1-000000.raw'''</span> | ||
+ | |||
+ | created 1383 files | ||
+ | created 124 directories | ||
+ | created 144 symlinks | ||
+ | created 200 devices | ||
+ | created 0 fifos | ||
+ | |||
+ | and change directory to the location of the extracted firmware. | ||
+ | |||
+ | humax# <span style="background:#FFFF00">'''cd /mod/tmp/firmware'''</span> | ||
+ | humax# <span style="background:#FFFF00">'''ls'''</span> | ||
+ | bin etc lib mnt opt root share tmp var | ||
+ | dev home media mod proc sbin sys usr | ||
+ | |||
+ | == Change the media server name == | ||
+ | |||
+ | Choose a new name for your media server which is exactly 12 characters long (the length of the original ''Media Server'' string). You can add spaces to the end if you don't need all the characters. Run the ''bsed'' command to modify the Humax binary and replace the standard name with yours; the example here just changes it to ''Media Serve2'' | ||
+ | |||
+ | humax# <span style="background:#FFFF00">'''bsed -v -1 usr/bin/humaxtv "Media Server" "Media Serve2"'''</span> | ||
+ | Replacement at offset 0x83e465 | ||
+ | Skipping replacement at offset 0x83e47a | ||
+ | Skipping replacement at offset 0x852eaf | ||
+ | Skipping replacement at offset 0xa12538 | ||
+ | Skipping replacement at offset 0xa1255e | ||
+ | |||
+ | == Re-pack the filesystem == | ||
+ | |||
+ | Change directory back to the flash drive and rebuild the filesystem using squashfs. This takes up to a minute. | ||
+ | |||
+ | humax# <span style="background:#FFFF00">'''cd /media/drive1'''</span> | ||
+ | humax# <span style="background:#FFFF00">'''mksquashfs /mod/tmp/firmware 1.hdfbin-1-000000.raw -le -all-root -noappend'''</span> | ||
+ | Parallel mksquashfs: Using 1 processor | ||
+ | Creating little endian 3.0 filesystem on 1.hdfbin-1-000000.raw, block size 65536. | ||
+ | |||
+ | Little endian filesystem, data block size 65536, compressed data, compressed metadata, compressed fragments | ||
+ | Filesystem size 16819.80 Kbytes (16.43 Mbytes) | ||
+ | 44.73% of uncompressed filesystem size (37602.17 Kbytes) | ||
+ | Inode table size 17944 bytes (17.52 Kbytes) | ||
+ | 31.14% of uncompressed inode table size (57615 bytes) | ||
+ | Directory table size 18381 bytes (17.95 Kbytes) | ||
+ | 42.25% of uncompressed directory table size (43501 bytes) | ||
+ | Number of duplicate files found 19 | ||
+ | Number of inodes 1851 | ||
+ | Number of files 1383 | ||
+ | Number of fragments 141 | ||
+ | Number of symbolic links 144 | ||
+ | Number of device nodes 200 | ||
+ | Number of fifo nodes 0 | ||
+ | Number of socket nodes 0 | ||
+ | Number of directories 124 | ||
+ | Number of uids 1 | ||
+ | root (0) | ||
+ | Number of gids 0 | ||
+ | |||
+ | == Remove the temporary filesystem == | ||
+ | |||
+ | humax# <span style="background:#FFFF00">'''rm -rf /mod/tmp/firmware'''</span> | ||
+ | |||
+ | == Rebuild the firmware bundle == | ||
+ | |||
+ | The last step is to rebuild the firmware bundle using the new filesystem file. This takes just over a minute. | ||
+ | |||
+ | humax# <span style="background:#FFFF00">'''humidify -c HDR_FOX_T2_upgrade.hdf 80bc.7e00 1.hdfbin-1-000000.raw'''</span> | ||
+ | HDF Tool v1.0.2, by af123, 2011. | ||
+ | |||
+ | Adding 1.hdfbin-1-000000.raw (17223680 bytes)... 0.31% compression | ||
+ | |||
+ | Processed in: 65.90s | ||
+ | |||
+ | == Flash the new firmware image == | ||
+ | |||
+ | Install the modified firmware image as normal and your media server should be renamed! |
Latest revision as of 12:46, 12 December 2019
Note: There is a Custom Firmware package called DLNA-Servername that can change the Media Server name of your Humax without having to follow the procedure below
If you have multiple Humax HDR Fox-T2s on the same network and use the Content Sharing (DLNA Server) feature, you may wish to change the name that they use to advertise themselves on the network. The following instructions take you through the process of creating a new customised firmware update file to change the name. The commands are all run on the Humax itself.
Gain telnet access to your Humax command prompt
Follow the instructions at http://wiki.humy.tv/wiki/Telnet
Once you have connected to the Humax command line then you will see a prompt that is the hostname followed by a hash (#) character, like this:
humax#
The commands in the following sections show this prompt for context but you should not type it. The command that you need to type will be shown in bold with yellow background whereas the prompt and other output that you will see is shown in normal font.
Install the required packages
This process uses several packages which may not already be installed on your Humax:
- humidify
- squashfs-tools
- bsed
Since you're already at the command prompt, you can just install them using the opkg command:
humax# opkg update Downloading http://hummypkg.org.uk/hdrfoxt2/base/Packages.gz. Inflating http://hummypkg.org.uk/hdrfoxt2/base/Packages.gz. Updated list of available packages in /mod/var/opkg/base. humax# opkg install humidify squashfs-tools bsed Installing humidify (1.0.2) to root... Downloading http://hummypkg.org.uk/hdrfoxt2/base/humidify_1.0.2_mipsel.opk. Installing squashfs-tools (3.1r2) to root... Downloading http://hummypkg.org.uk/hdrfoxt2/base/squashfs-tools_3.1r2_mipsel.opk. Installing bsed (1.0.0) to root... Downloading http://hummypkg.org.uk/hdrfoxt2/base/bsed_1.0.0_mipsel.opk. Configuring humidify. Configuring bsed. Configuring squashfs-tools.
Insert a USB Flash drive containing the firmware update
Put the customised firmware update file onto a USB flash drive, just as you would to apply the update, and plug it into your Humax. Just as with an update, the firmware bundle should be the only thing on the disk. Since the Humax is already turned on, it will not try and apply the update. If your TV is turned on and the Humax input is selected then the screen may show the loading USB and Video/Music/Photo/Copy box. This can be dismissed with the Exit button or just ignored until it times out.
Unless you have any other drives connected, this USB flash drive will now be mounted into the Humax filesystem as /media/drive1. Change into that directory and list the contents:
humax# cd /media/drive1 humax# ls HDR_FOX_T2_upgrade.hdf
Unpacking the firmware bundle
Unpack the firmware bundle using humidify. This takes around 30 seconds.
humax# humidify -x HDR_FOX_T2_upgrade.hdf HDF Tool v1.0.2, by af123, 2011. Opening HDR_FOX_T2_upgrade.hdf, 17176677 bytes. Blocks: 527 Model: 4 System ID: 80bc.7e00 x 1.hdfbin-1-000000.raw (17223680 bytes) Processed in: 22.97s humax# ls 1.hdfbin-1-000000.raw HDR_FOX_T2_upgrade.hdf
There are now two files on the USB drive.
Extract the file system
Extract the filesystem using unsquashfs. This takes around 5 seconds.
humax# unsquashfs -d /mod/tmp/firmware 1.hdfbin-1-000000.raw
created 1383 files
created 124 directories
created 144 symlinks
created 200 devices
created 0 fifos
and change directory to the location of the extracted firmware.
humax# cd /mod/tmp/firmware humax# ls bin etc lib mnt opt root share tmp var dev home media mod proc sbin sys usr
Change the media server name
Choose a new name for your media server which is exactly 12 characters long (the length of the original Media Server string). You can add spaces to the end if you don't need all the characters. Run the bsed command to modify the Humax binary and replace the standard name with yours; the example here just changes it to Media Serve2
humax# bsed -v -1 usr/bin/humaxtv "Media Server" "Media Serve2"
Replacement at offset 0x83e465
Skipping replacement at offset 0x83e47a
Skipping replacement at offset 0x852eaf
Skipping replacement at offset 0xa12538
Skipping replacement at offset 0xa1255e
Re-pack the filesystem
Change directory back to the flash drive and rebuild the filesystem using squashfs. This takes up to a minute.
humax# cd /media/drive1 humax# mksquashfs /mod/tmp/firmware 1.hdfbin-1-000000.raw -le -all-root -noappend Parallel mksquashfs: Using 1 processor Creating little endian 3.0 filesystem on 1.hdfbin-1-000000.raw, block size 65536. Little endian filesystem, data block size 65536, compressed data, compressed metadata, compressed fragments Filesystem size 16819.80 Kbytes (16.43 Mbytes) 44.73% of uncompressed filesystem size (37602.17 Kbytes) Inode table size 17944 bytes (17.52 Kbytes) 31.14% of uncompressed inode table size (57615 bytes) Directory table size 18381 bytes (17.95 Kbytes) 42.25% of uncompressed directory table size (43501 bytes) Number of duplicate files found 19 Number of inodes 1851 Number of files 1383 Number of fragments 141 Number of symbolic links 144 Number of device nodes 200 Number of fifo nodes 0 Number of socket nodes 0 Number of directories 124 Number of uids 1 root (0) Number of gids 0
Remove the temporary filesystem
humax# rm -rf /mod/tmp/firmware
Rebuild the firmware bundle
The last step is to rebuild the firmware bundle using the new filesystem file. This takes just over a minute.
humax# humidify -c HDR_FOX_T2_upgrade.hdf 80bc.7e00 1.hdfbin-1-000000.raw
HDF Tool v1.0.2, by af123, 2011.
Adding 1.hdfbin-1-000000.raw (17223680 bytes)... 0.31% compression
Processed in: 65.90s
Flash the new firmware image
Install the modified firmware image as normal and your media server should be renamed!