mmjc23
-
Posts
5 -
Joined
-
Last visited
Posts posted by mmjc23
-
-
On 10/27/2020 at 11:47 PM, IG-88 said:
i thought that but had no good point where that could be, 918+ can do uefi and csm and the cpu is ok for 918+ (4th gen cpu minimum)
when you see the grub menu and after this jun's message then its at least booting from usb (there can be problems with cpu gen in 918+ or cam mode not used with 3615/17 after this point resulting in a not found in network)
its the 2nd partiton, on the 1st it the grub.cfg but when you replaced the two files it must have been the right partition
just to find it in network you dont need any of that, the usb vid/pid is important but only later when installing the *.pat file with DSM
so for testing you might skip grub.cfg modification and only replace the extra/extra2.lzma
you usually see the message about "screen will stop updating shortly ..." and a blinking cursor but i'm not sure if its bad if the cursor does not blink
the interesting part can be seen on the serial console and kind of never look at the monitor (because there is nothing to be seen)
badly phrased, it refers to the e1000e driver, its its version in the extra/extra2
when you intent to use the hardware transcoding of the cpu or m.2 nvme ssd (as cache, only with two as write cache, in most cased not worth the effort especially with 1GBit nic) then it needs to be 918+
3615/17 with loader 1.03b can be tricky as it needs CSM mode in bios and you need to boot from the non uefi usb device (might only show up after rebooting with csm active and then going into bios to select the boot device)
maybe try loader 1.02b for 3615/17 that one can uefi and csm (as 918+ does) and with the last extra.lzma (4.8) the nic (8086:15a3) should work too, the driver in that version is only 3.3.4 but it has the id of the i218v in it so it should work
another test might be to use the 918+ and beside the extra/extra2 you also replace the zImage and rd.gz (on the same partition as extra/extra2) with the files from inside the dsm 6.2.3 918+ *.pat file (DSM_DS918+_25426.pat), you can open the *.pat file with 7zip or any other decent zip extractor
the kernel files on the loader are from dsm 6.2.0 and the drivers are made for 6.2.3, they are mostly compatible and i did not find any problems when testing it but maybe there are cases? it cant do anything worth
Hi IG-88, and sorry for the delay in answering you but I wanted to do some tests before bothering you again.
As you advised me, I tried loader 1.02b for 3615/17...
At first it didn't work so I tried to update the NUC BIOS and completely disable UEFI BOOT and leave only the legacy boot (in the NUC BIOS you can completely disable a type of boot).
In this way (with loader 1.02b) the DHCP assigned me an IP and the search for the NAS was successful.
I continued the installation but it was giving me the error "Failed to Format Disk (35)"
So, I deleted all the partitions on the disk and tried again ... but it gave me the error "The file is probably corrupt. (13)"
I read that it could be a USBKEY problem (my USBKEY had VID: abcd and PID: 1234).
So:
-I have changed USB KEY
-I loaded the new DS918 loader (without updated drivers extra918plus_v0.13.3)
-I changed the NUC's USB port
-I kept UEFI boot disabledIn this way, I was able to successfully install the latest version "DSM_DS918+_25426.pat"
I later found out that xpenology requires that the USBKEY must always be kept connected, is that correct?
So can I use the NUC harddisk for data?
Isn't it possible to install xpenology directly on the NUC Harddisk and remove the USBKEY?
Now I would like to try to connect a Hauppauge dongle for recording TV channels.
Soon, in Italy, we will switch to the new digital terrestrial and in the NAS that I would like to build, I would like to insert a PCIe Hauppauge multi tuner card, both to record TV channels and see TV channels on my old TV.
Do you think this is possible?
Don't worry...I'll do some tests...
I just wanted to thank you...if I managed to install it, it is only your credit...Thank you so much and have a good evening
-
2 hours ago, IG-88 said:
the e100e driver version in the extra 3.6.0 an ~1 year old, you device id is int that driver as supported device
the latest driver is from 3/2020, 3.8.4
with the driver also comes a file pci.updates and both contain the same entry for this device and no sub devices
from that it seems the 3.6.0 should be enough
you can try again at any time, just make a usb flash drive and boot it up, there should be no harm to a disk in the system by just booting the loader and trying to find it in network
would also be my next try if i ditched DSM
Hi IG-88 and thanks for your reply ... you are very kind.
I tried and tried again synoboot-ds918.zip + extra918plus_v0.13.3.zip following the Howto in XPENOLOGY Tool.
I have tried on two different NUC models (5i5RYK with Intel I218-V and 10i5FN with Intel I219-V) and on a Dell Optiplex 780 (with Intel 82567L) but I never get an IP from the DHCP Server (I checked router log).
I think I am doing something wrong.
I also tried two different USBKEYs.To load the updated drivers, I load partition 1 with osfmount and replace the extra.lzma and extra2.lzma files, is that correct?
I am sure I have set VID and PID of the USBKEY and the MAC of the network card correctly in the grub file and I have tried both with the serial number for 916+ (generated with "serial generator") and keeping the original one in the file.
But I think these parameters are used only after obtaining the IP or am I wrong? I can't even get the IP and I noticed that the cursor on the monitor is not blinking.What do you mean with "extra 3.6.0"? Are you referring to the "extra918plus_v0.13.3.zip" file?
In preparation of installing XPenology on a new NAS with Intel i5 10th in the future, is it correct to test with synoboot-ds918 and DSM_DS918 + _23739.pat or is it better DS3615 or DS3617?
Thank you so much for your help and forgive my English and my little knowledge of the subjects.
-
On 10/23/2020 at 12:09 PM, IG-88 said:
that nic might need a newer driver, so try the latest, extra/extra2 from the 6.2.3 driver thread and 6.2.3
1.03b for 3615/17 does not support uefi
does that system even has csm mode? if yes it needs to be on and you also need to boot from the non uefi boot device (might only show up after 1st reboot with csm on)
to say anything about the driver version and supporting this hardware it needs the pcie vendor- and product-id and its sub id (if present), usually you get this with lspci when booting a live/rescue linux
Thanks a lot IG-88 for the reply
I downloaded the file extra918plus_v0.13.3.zip and I copied the files inside, replacing those present in the partition of the USBKEY.
I tried both UEFI and Legacy boot and have also tried disabling other peripherals in BIOS, but the card does not get any IP from DHCP.
The LAN card is: VEN_8086 & DEV_15a3; if I run Windows 10 on the same NUC, it immediately gets an IP.
I wanted to try Xpenology on the NUC before buying the hardware for a new NAS (i5-10xxx or i3-10xxx) but I'm afraid it's too complicated for me.
I'll try with OMV.
Thank you very much and excude me for english
Have a good evening.
-
On 10/21/2020 at 6:27 AM, emailme0909 said:
I have Intel NUC (NUC7JYH). (j4005 processor + Realtek 8111H-CG ethernet).
I tried all three extra.lzma/extra2.lzma for loader 1.04b ds918+ DSM 6.2.2.
But cannot get IP address.
I also tried 3615 & 3617 loaders + pat files.
I am out of ideas now, Is there any other way to make DSM work on Intel NUC (NUC7JYH)?
Hello,
I have the same problem with NUC 5i5RYK with Intel I218-V and loader 1.04b ds918+ (or loader 1.02a2).
NAS not found also with loader DS3617XS and Loader 1.03b
NIC is a Intel I218-V with F4:4D:.... MAC Address
Installazione XPEnology
in ITALIAN
Posted
Ciao a tutti,
Sono nuovo del mondo XPEnology e, dato che durante la mia prima installzione su un Intel NUC di Test, ho avuto non poche difficoltà, mi sono scritto 4 appunti.
Quella di seguito, non vuole essere una procedura passo-passo (anche perchè conterrà sicuramente più di qualche errore/imprecisione).
Non voglio nemmeno sembrare il "saputello" di turno...sono solo 4 appunti in Italiano, che potrebbero suggerire qualche spunto, a chi, come me, si avvicina per la prima volta a questo O.S. e ha qualche difficoltà con la lingua della "perfida albione"😅
Considerate le premesse...difficilmente, potrò rispondere ad eventuali domande...saranno, invece, (molte e) molto apprezzate, eventuali correzioni e spunti per la realizzazione di una guida semplice, in italiano, e precisa.
INFO:
Il sistema operativo DSM installato sulle NAS Synology è sviluppato appositamente per l'hardware Synology.
XPEnology, non è altro che un bootloader "modificato", che simula Hardware Synology così da consentire l'installazione del relativo sistema operativo DSM su hardware diverso.
Per questo motivo, il dispositivo di boot XPEnology (USBKEY), deve SEMPRE essere inserito ad ogni avvio della NAS ed è quindi consigliabile configurarlo nel BIOS come primo dispositivo di Boot.
Il DSM Synology, per ragioni di sicurezza/backup, esegue automaticamente la copia dei file di sistema operativo, in tutti i dischi del NAS, in una partizione riservata all'inizio del disco.
Ciò nonostante, avviando il NAS ed eseguendo il Boot da uno dei dischi interni (invece che dalla USBKEY), il sistema operativo DSM non viene caricato, visualizzando lo schermo nero con il cursore lampeggiante.
PREREQUISITI:
LINK UTILI:
FORUM XPEnology: https://xpenology.com/forum/
VIDEO installazione: https://www.youtube.com/watch?v=y3KhEsztMEE
DOWNLOAD: https://xpenology.club/downloads/
COMPILE DRIVERS: https://xpenology.club/compile-drivers-xpenology-with-windows-10-and-build-in-bash/
CONSIDERAZIONI:
INSTALLAZIONE:
Il metodo più semplice per installare il sistema operativo XPEnology in una nuova NAS è utilizzando l'applicativo "Xpenology_Tool_V142.exe" (d'ora in poi "Tool").
NAS NON TROVATO
Come già accennato in precedenza, XPEnology, è un bootloader che emula Hardware Synology per consentire l'installazione del Sistema Operativo DSM su Hardware diverso.
Dato che, l'installazione del DSM Synology sulla NAS, viene effettuato via rete LAN, è chiaro che, se il bootloader XPEnology non include i drivers della scheda di rete del NAS, non sarà possibile ottenere
un indirizzo IP dal DHCP Server e quindi completare l'installazione.
Di seguito, verranno elencate una serie di verifiche e di prove (alcune molto banali) che si possono effettuare qualora la NAS non ottenga un indirizzo IP durante il boot dell'USBKEY e non venga quindi rilevata da Synology Assistant.