[GH-ISSUE #49] Missing complete alpine installation support (3x DiskStation models with 7.2) #17

Closed
opened 2026-03-12 18:58:08 +03:00 by kerem · 10 comments
Owner

Originally created by @RSfuchs on GitHub (Dec 29, 2024).
Original GitHub issue: https://github.com/007revad/Video_Station_for_DSM_722/issues/49

uname -m
armv7l

platform_name
alpine

Originally created by @RSfuchs on GitHub (Dec 29, 2024). Original GitHub issue: https://github.com/007revad/Video_Station_for_DSM_722/issues/49 uname -m armv7l platform_name alpine
kerem closed this issue 2026-03-12 18:58:13 +03:00
Author
Owner

@RSfuchs commented on GitHub (Dec 29, 2024):

(DS715)
DS1517
(DS1515)
DS1817
are AL-314 ARMhf CPUs!
(ARM hard float) port was developed to support the floating-point unit found on most modern 32-bit ARM boards.

The Annapurna Labs Alpine AL-314 is a quad-core ARM Cortex-A15 processor.
Architecture: Armv7-A

$ readelf -A /proc/self/exe | grep VFP
Tag_FP_arch: VFPv2
Tag_ABI_VFP_args: VFP registers
(The command returns blank if it’s an ARMel system or a Tag_ABI_VFP_args tag if it’s ARMhf.)

readelf is provided by "SynoCli Development Tools" package

Also questionable is:
(DS215+ | AL-212)
DS416 | AL-212
(DS2015xs | AL-514)

<!-- gh-comment-id:2564714865 --> @RSfuchs commented on GitHub (Dec 29, 2024): (DS715) DS1517 (DS1515) DS1817 are AL-314 ARMhf CPUs! (ARM hard float) port was developed to support the floating-point unit found on most modern 32-bit ARM boards. The Annapurna Labs Alpine AL-314 is a quad-core ARM Cortex-A15 processor. Architecture: Armv7-A $ readelf -A /proc/self/exe | grep VFP Tag_FP_arch: VFPv2 Tag_ABI_VFP_args: VFP registers (The command returns blank if it’s an ARMel system or a Tag_ABI_VFP_args tag if it’s ARMhf.) readelf is provided by "SynoCli Development Tools" package Also questionable is: (DS215+ | AL-212) DS416 | AL-212 (DS2015xs | AL-514)
Author
Owner

@RSfuchs commented on GitHub (Dec 29, 2024):

cat /proc/cpuinfo

processor : 0
model name : ARMv7 Processor rev 4 (v7l)
Speed : 1.4GHz
Features : swp half thumb fastmult vfp edsp neon vfpv3 tls vfpv4 idiva idivt
CPU implementer : 0x41
CPU architecture: 7
CPU variant : 0x2
CPU part : 0xc0f
CPU revision : 4

<!-- gh-comment-id:2564723822 --> @RSfuchs commented on GitHub (Dec 29, 2024): # cat /proc/cpuinfo processor : 0 model name : ARMv7 Processor rev 4 (v7l) Speed : 1.4GHz Features : swp half thumb fastmult vfp edsp neon vfpv3 tls vfpv4 idiva idivt CPU implementer : 0x41 CPU architecture: 7 CPU variant : 0x2 CPU part : 0xc0f CPU revision : 4
Author
Owner

@007revad commented on GitHub (Dec 29, 2024):

Thank you for bringing this to my attention.

The '15 and '16 series cannot use DSM 7.2.2 so the only affected models are the DS1517, DS1817 and DS416.

DS1817 platform_name="alpine"
DS1517 platform_name="alpine"
DS416 platform_name="alpine4k"

When I look at the spk download urls from https://www.synology.com/en-global/support/download for those 3 models the url is for the armv7 spk file.
https://global.synologydownload.com/download/Package/spk/VideoStation/3.1.1-3168/VideoStation-armv7-3.1.1-3168.spk

So I need to translate "alpine" and "alpine4k" to "armv7".

<!-- gh-comment-id:2564854423 --> @007revad commented on GitHub (Dec 29, 2024): Thank you for bringing this to my attention. The '15 and '16 series cannot use DSM 7.2.2 so the only affected models are the DS1517, DS1817 and DS416. DS1817 platform_name="alpine" DS1517 platform_name="alpine" DS416 platform_name="alpine4k" When I look at the spk download urls from https://www.synology.com/en-global/support/download for those 3 models the url is for the armv7 spk file. https://global.synologydownload.com/download/Package/spk/VideoStation/3.1.1-3168/VideoStation-armv7-3.1.1-3168.spk So I need to translate "alpine" and "alpine4k" to "armv7".
Author
Owner

@007revad commented on GitHub (Dec 29, 2024):

What does uname -m return for DS1517, DS1817 and DS416 ?

<!-- gh-comment-id:2564855699 --> @007revad commented on GitHub (Dec 29, 2024): What does `uname -m` return for DS1517, DS1817 and DS416 ?
Author
Owner

@RSfuchs commented on GitHub (Dec 29, 2024):

Hi Dave,
the headline already tells us that it is only about the 3 models. I have already written and explained in detail that it is about supporting the hard float, which armv7 does not do because we have armv7l. I was able to create a workaround as armv7 by adding "armv7l" and setting cputype="armv7".

My request is not read at all!?

<!-- gh-comment-id:2564858356 --> @RSfuchs commented on GitHub (Dec 29, 2024): Hi Dave, the headline already tells us that it is only about the 3 models. I have already written and explained in detail that it is about supporting the hard float, which armv7 does not do because we have armv7l. I was able to create a workaround as armv7 by adding "armv7l" and setting cputype="armv7". My request is not read at all!?
Author
Owner

@RSfuchs commented on GitHub (Dec 29, 2024):

What does uname -m return for DS1517, DS1817 and DS416 ?
That's also what it says in the first line here. I don't have a DS416.

<!-- gh-comment-id:2564858722 --> @RSfuchs commented on GitHub (Dec 29, 2024): > What does `uname -m` return for DS1517, DS1817 and DS416 ? That's also what it says in the first line here. I don't have a DS416.
Author
Owner

@007revad commented on GitHub (Dec 30, 2024):

I read all your comments. I didn't see any request.

To install the armada38x package on a Synology with an alpine CPU would require:

  1. Unpacking the .spk file (easy to do).
  2. Editing the INFO file to change arch="armada38x" to arch="alpine armada38x" (easy to do).
  3. Repacking the .spk file so DSM 7.x package center doesn't reject it.

I've not been able to successfully do step 3. I tried for my first version of my ContainerManager_for_all_armv8 and the spk file caused a "Invalid file format. Contact the package developer." error.

The alternative would be to:

  1. Temporarily make package center think the NAS has an armada38x CPU by changing platform_name="alpine" or platform_name="armarda38x" in /etc.default/synoinfo.conf and /etc/synoinfo.conf (after backing them up).
  2. Download and install the armada38x video station package.
  3. Edit video station's INFO file to arch="alpine armada38x".
  4. Change the CPU type back to the correct platform name.

My ContainerManager_for_all_armv8 does the same thing, except it's only changing the NAS model and not the platform name.

In step 1 I may also have to change unique="synology_alpine_ds1817" to unique="synology_armad38x_ds1817".

<!-- gh-comment-id:2564942410 --> @007revad commented on GitHub (Dec 30, 2024): I read all your comments. I didn't see any request. To install the armada38x package on a Synology with an alpine CPU would require: 1. Unpacking the .spk file (easy to do). 2. Editing the INFO file to change `arch="armada38x"` to `arch="alpine armada38x"` (easy to do). 3. Repacking the .spk file so DSM 7.x package center doesn't reject it. I've not been able to successfully do step 3. I tried for my first version of my [ContainerManager_for_all_armv8](https://github.com/007revad/ContainerManager_for_all_armv8) and the spk file caused a "Invalid file format. Contact the package developer." error. The alternative would be to: 1. Temporarily make package center think the NAS has an armada38x CPU by changing `platform_name="alpine"` or `platform_name="armarda38x"` in /etc.default/synoinfo.conf and /etc/synoinfo.conf (after backing them up). 2. Download and install the armada38x video station package. 3. Edit video station's INFO file to `arch="alpine armada38x"`. 4. Change the CPU type back to the correct platform name. My [ContainerManager_for_all_armv8](https://github.com/007revad/ContainerManager_for_all_armv8) does the same thing, except it's only changing the NAS model and not the platform name. In step 1 I may also have to change `unique="synology_alpine_ds1817"` to `unique="synology_armad38x_ds1817"`.
Author
Owner

@RSfuchs commented on GitHub (Dec 30, 2024):

I read all your comments. I didn't see any request.

To install the armada38x package on a Synology with an alpine CPU would require:

  1. Unpacking the .spk file (easy to do).
  2. Editing the INFO file to change arch="armada38x" to arch="alpine armada38x" (easy to do).
  3. Repacking the .spk file so DSM 7.x package center doesn't reject it.

I've not been able to successfully do step 3. I tried for my first version of my ContainerManager_for_all_armv8 and the spk file caused a "Invalid file format. Contact the package developer." error.

The alternative would be to:

  1. Temporarily make package center think the NAS has an armada38x CPU by changing platform_name="alpine" or platform_name="armarda38x" in /etc.default/synoinfo.conf and /etc/synoinfo.conf (after backing them up).
  2. Download and install the armada38x video station package.
  3. Edit video station's INFO file to arch="alpine armada38x".
  4. Change the CPU type back to the correct platform name.

My ContainerManager_for_all_armv8 does the same thing, except it's only changing the NAS model and not the platform name.

In step 1 I may also have to change unique="synology_alpine_ds1817" to unique="synology_armad38x_ds1817".

Yes, that's right, I know all of this before.
Due to your expertise in the two projects mentioned, I wanted to ask you to apply the know-how here together, based on my above requirement:
packages to download/install must be
armada38x (like mine DS116)

Please also implement your alternative.

<!-- gh-comment-id:2565573303 --> @RSfuchs commented on GitHub (Dec 30, 2024): > I read all your comments. I didn't see any request. > > To install the armada38x package on a Synology with an alpine CPU would require: > > 1. Unpacking the .spk file (easy to do). > 2. Editing the INFO file to change `arch="armada38x"` to `arch="alpine armada38x"` (easy to do). > 3. Repacking the .spk file so DSM 7.x package center doesn't reject it. > > I've not been able to successfully do step 3. I tried for my first version of my [ContainerManager_for_all_armv8](https://github.com/007revad/ContainerManager_for_all_armv8) and the spk file caused a "Invalid file format. Contact the package developer." error. > > The alternative would be to: > > 1. Temporarily make package center think the NAS has an armada38x CPU by changing `platform_name="alpine"` or `platform_name="armarda38x"` in /etc.default/synoinfo.conf and /etc/synoinfo.conf (after backing them up). > 2. Download and install the armada38x video station package. > 3. Edit video station's INFO file to `arch="alpine armada38x"`. > 4. Change the CPU type back to the correct platform name. > > My [ContainerManager_for_all_armv8](https://github.com/007revad/ContainerManager_for_all_armv8) does the same thing, except it's only changing the NAS model and not the platform name. > > In step 1 I may also have to change `unique="synology_alpine_ds1817"` to `unique="synology_armad38x_ds1817"`. Yes, that's right, I know all of this before. Due to your expertise in the two projects mentioned, I wanted to ask you to apply the know-how here together, based on my above requirement: packages to download/install must be armada38x (like mine DS116) Please also implement your alternative.
Author
Owner

@RSfuchs commented on GitHub (Dec 30, 2024):

How can I just install the Videostation and Media Extensions?

found it myself:
=> 4) Skip Media Server

<!-- gh-comment-id:2565576329 --> @RSfuchs commented on GitHub (Dec 30, 2024): How can I just install the Videostation and Media Extensions? found it myself: => 4) Skip Media Server
Author
Owner

@007revad commented on GitHub (Jan 2, 2025):

First run these is as root or sudo

#!/bin/bash

# Backup synopackageslimit.conf if needed
if [[ ! -f /etc.defaults/synopackageslimit.conf.bak ]]; then
    cp -p /etc.defaults/synopackageslimit.conf /etc.defaults/synopackageslimit.conf.bak
fi

# Make DSM let us install the Video Station version we want
/usr/syno/bin/synosetkeyvalue /etc.defaults/synopackageslimit.conf VideoStation "3.1.0-3153"
/usr/syno/bin/synosetkeyvalue /etc/synopackageslimit.conf VideoStation "3.1.0-3153"

# Make DSM let us install the Media Extensions version we want
/usr/syno/bin/synosetkeyvalue /etc.defaults/synopackageslimit.conf CodecPack "3.1.0-3005"
/usr/syno/bin/synosetkeyvalue /etc/synopackageslimit.conf CodecPack "3.1.0-3005"

Then do a manual package install of these:

Next we need to edit their version numbers to prevent package center trying to update them. Run as root or sudo.

sudo synosetkeyvalue /var/packages/CodecPack/INFO version "30.1.0-3005"
sudo synosetkeyvalue /var/packages/VideoStation/INFO version "30.1.0-3153"
<!-- gh-comment-id:2567442736 --> @007revad commented on GitHub (Jan 2, 2025): First run these is as root or sudo ```bash #!/bin/bash # Backup synopackageslimit.conf if needed if [[ ! -f /etc.defaults/synopackageslimit.conf.bak ]]; then cp -p /etc.defaults/synopackageslimit.conf /etc.defaults/synopackageslimit.conf.bak fi # Make DSM let us install the Video Station version we want /usr/syno/bin/synosetkeyvalue /etc.defaults/synopackageslimit.conf VideoStation "3.1.0-3153" /usr/syno/bin/synosetkeyvalue /etc/synopackageslimit.conf VideoStation "3.1.0-3153" # Make DSM let us install the Media Extensions version we want /usr/syno/bin/synosetkeyvalue /etc.defaults/synopackageslimit.conf CodecPack "3.1.0-3005" /usr/syno/bin/synosetkeyvalue /etc/synopackageslimit.conf CodecPack "3.1.0-3005" ``` Then do a manual package install of these: - https://archive.synology.com/download/Package/CodecPack/3.1.0-3005 - https://archive.synology.com/download/Package/VideoStation/3.1.0-3153 Next we need to edit their version numbers to prevent package center trying to update them. Run as root or sudo. ```bash sudo synosetkeyvalue /var/packages/CodecPack/INFO version "30.1.0-3005" sudo synosetkeyvalue /var/packages/VideoStation/INFO version "30.1.0-3153" ```
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/Video_Station_for_DSM_722#17
No description provided.