ideasman69
Member-
Posts
117 -
Joined
-
Last visited
-
Days Won
2
Everything posted by ideasman69
-
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
-
why not just use a unifi docker? super easy to auto update (via watchtower) and self contained
-
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
-
Use virtual serial port to correct bad static route?
ideasman69 replied to wingspinner's topic in DSM 6.x
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. -
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:
-
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 :))
-
you can always use Jun's Loader v1.03b DS3615xs to get to 6.2 but you'll need an intel NIC to get to 6.2.1 just no hardware transcoding
-
Nah, just get another board There's an compatibility problem with Linux kernel 4.4.57 and these boards. I think the best hope is that DSM 7 runs on a newer kernel and Jun can perform his magic
-
Ah ok. Yeah I didn't try esx on the j4455-m. It only has 2 sata ports which isn't enough for me and I was trying to avoid extra cards If you can run esx and passthrough the GPU, the -m model might be the best pick of the three. Maybe I'll give it a shot!
-
nah this doesn't work. the GPU is in the same IOMMU group as the network card - so once you assign the GPU to a VM and boot it, you lose all network connectivity.
-
I spent a tiny bit more time on these boards and found something interesting. I installed Ubuntu 16.04 LTS and it ran perfectly fine - fast to boot and responsive. However, after purposely downgrading the kernel to 4.4.57 (matching the kernel version of 1.04b / DSM 6.2) - these boards take ages to load and feel sluggish. So i reckon as soon as the kernel is upgraded, we might be in luck (maybe excluding the last board in my list above due to the i915 driver crashing). On another note - i picked up a gigabyte B85M-HD3G / i5 4570S / 8GB DDR second hand for $100 and it rocks using the 1.04b bootloader. Super quick and full hardware acceleration (for h264). Thanks again Jun
-
Hi guys, I'm a bit out of my depth here but I'm really hoping I can get a couple of HVR-2200 tuners working in DSM6.1 or DSM6.2. I'm currently running Jun's DS918+ loader which is kernel 4.4.57(+?) so figured I'd load up ubuntu on another machine, install the same kernel version and copy the saa7164.so file from it over to DSM. Of course it didn't work but how does one go about compiling a version of the saa7164 driver into DSM? I noticed that there's already another similar module but the sizes are way different: -rw-r--r-- 1 root root 30579 Oct 27 00:14 saa7115.ko -rw-r--r-- 1 root root 223582 Dec 9 12:41 saa7164.ko and trying to force load it: sh-4.3# insmod saa7164.ko insmod: ERROR: could not insert module saa7164.ko: Invalid module format Any help or advice would be greatly appreciated! Or even better, if someone would be able to compile a version for me that would be awesome! Thanks
-
DSM 6.x.x Loader (with MBR partition Table)
ideasman69 replied to Genesys's topic in Member Tweaked Loaders
-
DSM 6.x.x Loader (with MBR partition Table)
ideasman69 replied to Genesys's topic in Member Tweaked Loaders
Ok, but the 1.04b loader only works on Haswell CPUs or above. Any Haswell (or above) motherboards will boot from it without any modification. That was my point -
hey guys. i know we need a haswell or newer for the 918+ boot loader but what about the GPU, does it need to be kaby lake or skylake for hardware transcoding to work?
-
DSM 6.x.x Loader (with MBR partition Table)
ideasman69 replied to Genesys's topic in Member Tweaked Loaders
why do you need an MBR version of this loader? It only works on 4th gen intel Core processors (and newer) anyway - and surely they all have UEFI BIOSs. I'm using the current loader in CSM / BIOS mode and it works fine -
yeah downgrade is possible. just use afudos.exe on a usb boot disk with DOS (but i have one of these as backup) 1.30 was the last release before all the spectre/meltdown stuff. bios' past this gave unpredictable results in Windows 10 and lowered performance.
-
nah just standard drives but this high speed burst is due to the inbuilt cache on each of the drives. using a 10GB file gives a real world result: sh-4.3# sudo dd bs=1M count=10240 if=/dev/zero of=/volume1/backups/test.file 10240+0 records in 10240+0 records out 10737418240 bytes (11 GB) copied, 44.0262 s, 244 MB/s using a smaller test like 256MB basically only writes to the cache: sh-4.3# sudo dd bs=1M count=256 if=/dev/zero of=/volume1/backups/test.file 256+0 records in 256+0 records out 268435456 bytes (268 MB) copied, 0.278405 s, 964 MB/s
-
Done that dude. I've tested basically every combination of bios setting, bios version, drives and everything on three different j3455 model boards. C states is the first thing I disable
-
yep you're out of luck matey.. the cpu is only an intel atom n270. you really need an x64 chip for any of the loaders to work https://ark.intel.com/products/36331/Intel-Atom-Processor-N270-512K-Cache-1-60-GHz-533-MHz-FSB-
-
grab the 3615 loader from here:
-
if you have one of the Asrock J3455 boards - check out these disk performance benchmark results comparing the 3615 and 918+ boot loaders using the same hardware and same 4 drive RAID5 volume: 1.0.4b 918+ / DSM 6.2.1: 1.0.2b 3615 / DSM 6.1.7: why is it so slow? who knows! maybe these boards just suck.
-
with the same hardware and same 4 drive RAID5 volume but using the 1.02b 3615 bootloader and DSM 6.1.7: 1073741824 bytes (1.1 GB) copied, 1.17239 s, 916 MB/s results speak for themselves 😉
-
It's not worth it - there's nothing new this bios really provides. In fact - the exact same bios was release back in june for the j3455M. they've just finally got around to updating it for the other j3455 model boards. http://www.asrock.com/mb/Intel/J3455M/?cat=Download&os=BIOS from testing each of the versions on 3 different models with a handful of operating systems - v1.30 is the one i recommend