Transition Members
  • Content Count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About digitalhigh

  • Rank

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. That's a great idea, and something I'd not tried until yesterday. Unfortunately, that yielded no more success. 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? I'll try that this weekend if time allows, see how far it gets on boot.
  2. 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
  3. Also, CPU is core i3 4130 4th-gen, so it should support HW decoding?
  4. 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. 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 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
  5. Running 6.1 on bare metal Intel hardware! All packages and services seem to be working correctly. Jun, YOU ROCK!!
  6. Not dead, just haven't had time to devote to it yet. Don't worry people it is far from dead and will be released within a few weeks or less. Sent from my SM-N920T using Tapatalk How is the progress coming on this? I see it's been about a month. I've got a super-weird Bosch recording appliance that's been repurposed to run DSM 5.2 beautifully, but I'd like to get it running 6.0 or 6.1. Without too much looking at the PID's of everything, I see that it's running all Intel silicone for NIC, RAID Controller and most everything else. What Intel drivers are you including in this that aren't present in the available version of JUN's loader? WIth his, I get the "Sata errors have been detected and ports have been disabled" message. So, count me in the list of people patiently watching this thread for an updated version. If you need a tester, I'd be glad to volunteer.