digitalhigh

Running on Bosch CCTV/DVR Appliance w. JUN, trying to upgrade to 916+

Recommended Posts

Okay, so, long story short, I've been running xpenology for over a year on a Bosch DVR appliance I inherited. It's got a nice 4-bay form-factor, has an all intel-chipset, and has more or less just worked, as long as I didn't mess up my bootloaders.  :P

However, I'm noticing Plex playback is very laggy, especially now that I'm starting to add 4k to my collection, and I was hoping to remedy that. 

I've always ran the DS3615xs firmware...and in reading up on hardware decoding, noticed mention that the 916+ version supported said decoding. Currently running the latest beta by @jun

"Okay, neat." I think. This shouldn't be hard. 

I download the new image, flash it to USB...it boots.  But my device is not showing in synology web assistant or normal assistant, and I'm not seeing it on the LAN. It has a link light, but I have no further way of establishing if it's really online or not. Assuming *not*.

The odd part is, I'd assume that if the 3615 loader would work on my Intel hardware, the 916+ wouldn't have an issue either.


So, question being - does anybody know what I may be doing wrong, or if there's a NIC firmware that's different that is causing me to not be able to detect this?

I've tried adding the extra drivers by @IG-88 as recommended by @Polanskiman, but that has not helped at all.  Tried booting into all 3x versions in the grub menu, and my grub.config is otherwise identical to the old one, aside from referencing the new model version.

Below is some hardware info I was able to dump from SSH...
 

Product Name: BOSCH CCTV APP AEL1
 

NIC 
driver: e1000e
version: 3.3.4-NAPI
firmware-version: 0.13-4
bus-info: 0000:00:19.0
supports-statistics: yes
supports-test: yes
supports-eeprom-access: yes
supports-register-dump: yes
supports-priv-flags: no
lspci
0000:00:00.0 Class 0600: Device 8086:0100 (rev 09)
0000:00:01.0 Class 0604: Device 8086:0101 (rev 09)
0000:00:02.0 Class 0300: Device 8086:0102 (rev 09)
0000:00:16.0 Class 0780: Device 8086:1c3a (rev 04)
0000:00:19.0 Class 0200: Device 8086:1502 (rev 05)
0000:00:1a.0 Class 0c03: Device 8086:1c2d (rev 05)
0000:00:1d.0 Class 0c03: Device 8086:1c26 (rev 05)
0000:00:1e.0 Class 0604: Device 8086:244e (rev a5)
0000:00:1f.0 Class 0601: Device 8086:1c56 (rev 05)
0000:00:1f.2 Class 0104: Device 8086:2822 (rev 05)
0000:00:1f.3 Class 0c05: Device 8086:1c22 (rev 05)
0000:01:00.0 Class 0c03: Device 1912:0015 (rev 02)
0001:07:00.0 Class 0000: Device 1b4b:9235 (rev ff)
0001:08:00.0 Class 0000: Device 1b4b:9235 (rev ff)
0001:09:00.0 Class 0000: Device 1b4b:9235 (rev ff)
0001:0a:00.0 Class 0000: Device 1b4b:9235 (rev ff)
 lspci -k | grep 'Kernel driver'
        Kernel driver in use: pcieport
        Kernel driver in use: e1000e
        Kernel driver in use: ehci-pci
        Kernel driver in use: ehci-pci
        Kernel driver in use: lpc_ich
        Kernel driver in use: ahci
        Kernel driver in use: xhci_hcd


 

Share this post


Link to post
Share on other sites

Bump.

Anybody? Anybody have any idea why my NIC is detected on the 3615 bootloader, but not the 916+?  It's the intel driver, e1000e, so I'm a little confused at what the issue would be.

@jun @Polanskiman @IG-88

Share this post


Link to post
Share on other sites

Have you tried doing it with complete fresh components.  Fresh bootloader USB and without your old HDDs to see if that will do it?  If you can get a working config, then plug in your old HDDs and migrate.  

 

I've had (and seen) issues where an existing DSM install on previous HDDs gets in the way of a new install. 

Share this post


Link to post
Share on other sites

ds916 version is not a generic build, it's for boards similar to official ones, otherwise no point to use it

通过我的 ONEPLUS A5000 上的 Tapatalk发言

Share this post


Link to post
Share on other sites

only way to find out might be a serial cable and console (putty) and having a look whats going on when the system comes up

maybe there will be something in the log to indicate why the e1000e driver does not work (that one comes from synology itself and was not replaced by me in the extra.lzma, as it is for the "newer" hardware of the 916+ i'd expect a older version of the nic should work with the driver)

 

but even if nic and storage work, not shure if you will be able to use any kind of hardware transcoding

 

Share this post


Link to post
Share on other sites
 

Have you tried doing it with complete fresh components.  Fresh bootloader USB and without your old HDDs to see if that will do it?  If you can get a working config, then plug in your old HDDs and migrate.  

 

I've had (and seen) issues where an existing DSM install on previous HDDs gets in the way of a new install. 

 

That's a great idea, and something I'd not tried until yesterday. Unfortunately, that yielded no more success. :(

 

 

ds916 version is not a generic build, it's for boards similar to official ones, otherwise no point to use it

通过我的 ONEPLUS A5000 上的 Tapatalk发言
 

 

Hey man, thanks for the reply. I really love the work you do.

So, you say "no point to use it".

The main reason I wanted to use it was, as I said, to enable hardware transcoding for Plex Media Server. My device currently doesn't have a /dev/dri directory. From digging, I understood that this was because the only bootloader that supported transcoding was for the 916 version.

So I guess I'm confused. Is the lack of /dev/dri specific to my bootloader, or is it more likely that I just don't have hardware to support it?

Is there a specific way I can find out what hardware I have, and if I can get transcoding to work?

 

 

only way to find out might be a serial cable and console (putty) and having a look whats going on when the system comes up

maybe there will be something in the log to indicate why the e1000e driver does not work (that one comes from synology itself and was not replaced by me in the extra.lzma, as it is for the "newer" hardware of the 916+ i'd expect a older version of the nic should work with the driver)

 

but even if nic and storage work, not shure if you will be able to use any kind of hardware transcoding

 


I'll try that this weekend if time allows, see how far it gets on boot.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now