ideasman69

Members
  • Content Count

    101
  • Joined

  • Last visited

  • Days Won

    2

ideasman69 last won the day on October 25 2018

ideasman69 had the most liked content!

Community Reputation

19 Good

About ideasman69

  • Rank
    Advanced Member

Recent Profile Visitors

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

  1. and hate to be that guy... but you really missed all these at the top of your browser?
  2. Thanks for this guide! I've had DSM5 installed on a kimsufi KS-1 server for a couple years now. Someone made a synboot.img file for DSM5 that was a single partition and fit perfectly in between two of the synology created partitions. I could never get the DSM6 bootloader working until now - so thanks a bunch. If you create your bootloader partition on the other unused area - you won't get any issues within the Synology GUI: I tried to get the DSM6.2 bootloader working but even after copying the extra files from both synboot.img partitions to the newly creat
  3. yeah they're awesome and they do a great job. just stick with loader 1.02b and DSM 6.1x
  4. sorry i still dont understand. I have a 1.04b build here with 6.2.2-24922 update 3 and working hardware acceleration. following your guide on replacing the extra.lmza file and cleaning out the modules folder removes the /dev/dri folder as expected.
  5. this is interesting because i just built a machine yesterday with a Intel I219V onboard NIC which the 1.04b bootloader doesn't like. I needed to stick in an old Intel 1000PT card to get it to appear on the network
  6. can you please clarify that? does /dev/dri exist when i915.ko drm_kms_helper.ko and drm.ko are removed? or does it only exist when you've replaced them with files from fedora?
  7. im assuming that using this extra.lzma kills hardware acceleration?
  8. it kinda has both. the interval on the left is in exact seconds, the transfer column is how many MBytes were transferred in that second - ie 112MBytes / sec anyway - after moving back to DSM 6.1 and EXT4, speeds have gone back to full speed:
  9. Hi guys.. Whats the go with slowish network file transfers? If i do an iperf in each direction from the nas to my study PC - it maxes out the connection. NAS as the server: $ ./iperf3_3.1.3 -s ----------------------------------------------------------- Server listening on 5201 ----------------------------------------------------------- Accepted connection from 192.168.1.101, port 49554 [ 5] local 192.168.3.2 port 5201 connected to 192.168.1.101 port 49555 [ ID] Interval Transfer Bandwidth [ 5] 0.00-1.00 sec 108 MBytes 907 Mbits/sec [ 5] 1
  10. really? compatibility, portability, upgradability - it's the future man the only apps i have on my xpeonology box are video station (for tuner support and hardware transcoding drivers) and docker. i've got 13 dockers running which remain perfectly intact after a reinstall or clean upgrade of DSM. only way to go IMO
  11. why not just use a unifi docker? super easy to auto update (via watchtower) and self contained
  12. bud - if you read any other thread about 6.2.1 you'd know that third party ethernet adapters only work in DSM 6.2 and below. As soon as you jump up to 6.2.1, you play yourself. either switch over to E1000 or drop back to 6.1.7 or 6.2
  13. yeah man - just create a virtual com port (make sure it presents itself as COM1 to the VM) and you should see the boot progress. Once it's finished starting up, you can login just as if you were SSH'd in.
  14. ideasman69

    DSM 6.2 Loader

    go this one matey. nothing really new in 6.2 and saves you accidently upgrading to 6.2.1 (which won't work with your realtek NICs. once you're on 6.1.7, just set your update settings to this:
  15. ideasman69

    DSM 6.2 Loader

    not worth it man.. while you might get the GPU driver to load, it doesn't help the the kernel version being incompatible with these boards. the overall system is super slow to boot and not worth using (imo :))