Search the Community

Dell Intel PRO 1000 PT Dual Port PCIe x8 Gigabit Ethernet Network Card G174P or OEM Dell G174P Intel Pro/1000 PT Dual Port Gigabit PCI-E Network Card You can get this on ebay

Guten Morgen. Ich bin seit ein paar Tagen dabei, mir ein NAS aufzubauen und einzurichten. Als Hardware kommt dabei ein ASRock J3455B-ITX mit 12 GB RAM zum Einsatz. Nachdem ich das Ganze schlussendlich mit dem Loader 1.02 und 3615 (6.1) zum Laufen gebracht habe, wollte ich gern meine Dateien auf das NAS hochladen. Bei kleineren Dateien (bis ca 4GB) funktioniert es auch. Alles darüber allerdings bekommt zum Einen kaum mehr als 12MB/s Bandbreite und wird zum Anderen mit der Fehlermeldung "dieses Benutzerkonto hat nicht die erforderlichen Berechtigungen, um diese Aktion auszuführen" abgebrochen. Berechtigungen sind aber - so weit ich das sehen kann - auf Lesen/Schreiben eingestellt. Übersehe ich etwas? Oder liegt es gar am Netzwerkadapter? Sowohl das NAS, als auch der Desktop-Rechner haben den Realtek 8111 Gbit verbaut. Zwei Intel Pro 1000 sind aber bestellt und sollten bis morgen da sein.

I'm wondering about almost the same question. Want to upgrade my 3516 from a RTL8111 to an Intel Pro 1000 and would like to keep all my files and settings in my Device.

- Результат: Успешно - Версия и модель загрузчика: JUN'S LOADER v1.02b - DS3615xs - Версия DSM: DSM 6.1.7-15284 Update 2 - Дополнительные модули extra.lzma: NO - Аппаратное решение: Asus P5QLD PRO (P43) / Intel Xeon L5408 / 2 * 2 Gb DDR2-800 Kingmax / int. LAN + Intel PRO 1000 VT (4 * 1 Gb) - Короткий комментарий: завелось без проблем, настройки BIOS стандартные (только биос с микрокодами ксеона, кто знает про 771 -> 775 - тот в курсе)

Wenn Du keine eigenen Treiber einfrickeln willst, tut es eine Intel Pro 1000 GT. Die gibts massenweise ab 4 € im Netz.

I have an intel pro 1000 pt added, but it won't work. My mobo is J3455B-itx

Bought an intel pro 1000 pt, same thing, no ip after restart. Tried with DSM 6.1 image for 916+, all is working as it should with hardware transcoding. Tried esxi, but I get an error 22 there.

I had the problem with a Relatek 8111 onboard NIC. After a initial install of DSM 6.2 with loader 1.03b the transfer speeds where @ 110MB/s, Gigabit ethernet speed. After installing Update 2 DSM still stated that the speed is 1000Mbps but transfer speed dropped to 10MB/s. I added an Intel Pro 1000 and everything worked fine again.

ESXi wird mit der CPU wahrscheinlich keine Freude. Sataportmap kannst Du bei dem Board auf "1" stehen lassen. Im Board sitzt eine onboard NIC mit RTL8111GR. Der Chip ist eher suboptimal bzw. wird nicht immer erkannt. Alternative, die immer funktioniert, sind Intel Pro 1000 Karten. Gibts gebraucht für sehr wenig Geld. Übrigens: (klassisch) zukunftssicher ist XPEnology nie, das steht auch in der von Dir genannten Anleitung 😉

Hi guys, I'm new to the XPenology, please, bear with me. I've tried to install XPenology on my computer and was sucessfull with DSM 5.5-5644. I am using hte DS3615xs files. My issue is when i try to upgrade, all goes well but do not see my SAS controller. Please can someone help me out. Motherboard- Asus P8z77-V CPU Intel i5-4440 SAS Controller -Marvell 88se63xx/64xx(Supermicro SAS) NIC Intel Pro 1000 MB Sata 1 SSD for DSM MB Sata 2 Empty MB Sata 3 2TB MB Sata 4 2TB MB sata 5 2TB MB Sata 6 2TB SAS port 1 2TB Sas Port 2 3TB Sas port 3 2TB list of my devices Jarvis> lspci -k | grep 'Kernel driver' Kernel driver in use: pcieport Kernel driver in use: pcieport Kernel driver in use: xhci_hcd Kernel driver in use: e1000e Kernel driver in use: ehci-pci Kernel driver in use: pcieport Kernel driver in use: pcieport Kernel driver in use: pcieport Kernel driver in use: ehci-pci Kernel driver in use: lpc_ich Kernel driver in use: ahci Kernel driver in use: mvsas Kernel driver in use: e1000e Kernel driver in use: xhci_hcd Jarvis>

Switched from onboard RTL8111H to Intel Pro 1000 CT and LAN speed is normal again (114MB/s).

PCI Intel PRO 1000 так же не видит.

Bonjour à vous, Déjà je tiens à féliciter les développeurs pour leur super boulot !! Je débute tout juste et j'ai récupéré un ancien PC HP Compaq 8000 Elite SFF, possédant un processeur Intel Core 2 Quad Q8400 @ 2.66 Ghz et une carte réseau intégrée Intel Pro 1000 (chipset 82567LM-3). Ce PC a 4 ports SATA et serait parfait pour un NAS avec Plex Server dessus ! Souhaitant en faire un Xpenology, j'ai créé sans soucis une clé USB avec le loader "DS3615xs_DSM6.1_JunsMod_V1.02b_MBR_Genesys" pour pouvoir y mettre un DSM 6.1.3. J'ai choisi ce loader car le PC n'est pas UEFI. J'ai bien modifié dans grub.cfg les valeurs VID, PID, MAC (celle de la carte réseau Intel intégrée), sans oublier un numéro de série DS3615xs généré sur le site comme indiqué dans le premier post de ce Thread or, lorsque le PC Boot, il démarre bien sur la séquence "DS3615xs 6.1 Baremetal" mais Synology Assistant ne trouve rien, même au bout de plusieurs minutes... Cependant, ma Freebox V6 lui attribue bien une IP en 192.168... et je peux le pinger... En mettant un live CD Ubuntu 17.04, la carte intel 82567LM-3 est gérée nativement et est pleinement fonctionnelle. Le pilote s'appelle "e1000e", En regardant dans la section "Modules inclus dans le Loader de Jun par défaut" du premier Thead, il est mentionné que le pilote "e1000.ko" pouvez-vous me dire si celui-ci gère le chipset 82567LM-3 svp ? Merci beaucoup pour votre aide. DaveVador

Big thanks to everybody: @Polanskiman, @jun, @quicknick, @Trantor, @IG-88 and everybody esle involved in R&D and testing. Finally with extra.lzma my system Gigabyte Z 170 Board with Intel Pro 1000 NIC and adaptec HBA 1000 SAS Controller is fully migrated to 6.1.3. I can confirm up and running with this combination.

I think i did that. I use the Jun loader 1.01 But i notice this on the Asus motherboard spec : Gigabit Realtek[emoji768] 8111E optimize fir the Ai NET2 technology Think i will find another nic for testing... Intel Pro 1000 GT or PT My server actually run Win 10 + VmWare Pro (with the Jun loader 1.01). When I test it, i simply remove the sata connector of the win10 installation (internal SSD). I test it for fun! (already own a DS410 and DS212J).... But if i can make it work stable for a long period of time, probably i will switch Envoyé de mon SM-T560NU en utilisant Tapatalk

скорее всего у нас с тобой разные чипсеты сетевых, но у меня Intel Pro 1000 pt dual заводится без проблем на 3615

Hallo, ersteinmal vielen Dank für die vielen How-To Anleitungen in diesem Forum, denn sie haben mir bisher sehr geholfen. Jetzt habe ich ein Problem, wobei ich noch keine Lösung via google und in diesem Forum gefunden habe. Meine DS beteht aus folgenden Bauteilen: Model : DS3615xs DSM : DSM 6.0.2-8451 Update 8 Jun Mainboard: ASRock N3150M CPU: Intel® Quad-Core Processor N3150 onboard NIC1: Realtek RTL8111GR 1GbE PCIe NIC2: Intel Pro 1000 PT Server Adapter Quad Port Gigabit NIC PCIe x4 Die DS läuft Prima und alle Dienste laufen zuverlässig. Nun dachte ich, für meinen ESXI 6 wäre es doch Prima ISCSI LUN's auf der DS zu speichern. Doch leider ist der Speed naja sagen wir mal ..... betagt. Also kam mir die fixe Idee 2 10GbE Karten zu suchen und zwischen der DS und dem ESXI eine CrossOver Verbindung für die ISCSI Lun's zu schaffen. Dann mal fix 2 HP Mellanox 10GbE Connext-2 1Port 10GbE Karten bestellt, ABER nun stehe ich vor dem Problem das in der DS die 10GBit Karte erkannt wird aber leider der 1Gbit onboard NIC deaktiviert ist. Demnach ist die DS nur noch über die 10Gbit Karte errichbar. entferne ich die Karte ist der 1Gbit onboard Port wieder da. (die Intel Pro 1000 PT Server Adapter Quad Port Gigabit Karte musste für die 10Gbit Karte raus) Ich habe versucht in der /etc/sysconfig/network-scripts/ifcfg-eth0 und eth1 die IP's anzupassen doch leider verwehrt mir das System jegliche Änderungen trotz Admin Login. Vielleicht kann mir jemand helfen, sodass ich beide (eth0 onboard und eth1 die 10Gbit Karte zum laufen bekomme). Vielen Dank im voraus

Вот тут добрый человек описал как в 1.02a дрова добавлять... [spoiler=how to build and inject missing drivers in jun loader 1.02a]IG-88 » 25 апр 2017 01:37 kernel modules/drivers are specifically compiled for a kernel (-versions) and even distributions it's not like windows where you can download a driver somewhere and just put it in so don't take any *.ko file, stick it in and expect it to work if you haven't build the *.ko yourself or don't know exactly where it came from, expect it to fail I'm no expert but as there is no how-to here in the forum - lets start one hopefully other will correct and help refine or take over and rewrite it some steps are made in windows (osfmount) but will also possible in the chroot environment on linux basic knowledge about using a linux console and command-line tools (or midnight commander) is needed, if you never used this you should not start with this how-to, choose something easier or invite someone who is able to help (do a workshop) doing all this from scratch will take at least 1-2 hours, in most cases (re-read, google, try, google, try again, ...) much longer, maybe plan a weekend of text-adventure fun 1. building the kernel module (driver) 1.1 what driver/module i need you will have to find out (google) what the name of the driver/module is that your hardware needs or you will have to know where to find the rigt option in the menu-system of the kernel when configuring it example: nForce 630 chipset with RTL8211E, youu might expect it to be a realtek driver like rtl*.ko but it's not its "forcedeth.ko" because the RTL8211 is not a fully working PCIe Network Chip in some cases you might be forced to find out by booting a linux distribution and look in /var/log/, use lspci or other tools it also helps if the hardware provider has already compiled packages for specific distributions like redhat, you can look inside these packages for *.ko files you also can look in the .config file of the kernel (more below) with a text editor to find a section where the module is mentioned, this will also give you a hint where to find it in the menu-system when configuring the kernel 1.2 you need the kernel source in the case of synology that seemed sometimes difficult but at the moment there is kernel source for dsm 6.1 https://sourceforge.net/projects/dsgpl/ ... %20Source/ 15047 is the version and tells you about what dsm version it is (15057 = dsm 6.1), it might change in a later version of 6.1 so always check for what version your bootloader from usb stick is made for (jun 1.02 is for 15047) as i write this for ds3615xs it's bromolow as a platform, for ds3617xs it's broadwell and ds916+ is braswell (you usually see that name on the update files for a synology system like "synology_broadwell_3617xs.pat") so for ds3615xs we use this: https://sourceforge.net/projects/dsgpl/ ... z/download 1.3 setting up a DSM 6.1 ds3615xs test environment with virtualbox (its free) or whatever works with juns loader look in the forum to find something that works, basics for virtualbox are - mac of the nic (intel pro 1000 desktop) in vm and grub.conf need to be the same - boot controller for jun's image (vmdk with reference to img file) is ide, controller for dsm disks is scsi lsi (!!!) - choose esx server option in grub menu 1.4 installing chroot put in http://packages.synocommunity.com for custom packages (http://packages.synocommunity.com) and change the setting that beside synology packages trusted ones are also to install install debian-chroot plugin (https://synocommunity.com/package/debian-chroot) from community section (some info's about it: https://github.com/SynoCommunity/spksrc ... e-services) you might also install midnight commander if you are on it, makes things easier if you're not a command-line junky and more used to a graphical environment that give you clues activate ssh in dsm connect with ssh/putty to you dsm, login with user admin (and if you want to be root use "sudo -i") start the chroot with: /var/packages/debian-chroot/scripts/start-stop-status chroot after that you are inside the chroot, check with ls and you won't see "/volume1" or other sysnology specific directory's from the dsm environment, you can leave the chroot environment with "exit" later if you want now we have to update and install tools: apt-get update apt-get upgrade apt-get install locales dpkg-reconfigure locales dpkg-reconfigure tzdata apt-get install mc make gcc build-essential kernel-wedge libncurses5 libncurses5-dev libelf-dev binutils-dev kexec-tools makedumpfile locate after that we create a directory (lets say "test") 1.5 copying kernel files and create kernel modules copy the downloaded kernel (linux-3.10.x.txz) to a share on the dsm, open a 2nd putty and copy the linux-3.10.x.txz (/volume1/...) to /volume1/@appstore/debian-chroot/var/chroottarget/test/ (that's where the "test" directory of the chroot environment is located in your real system) change back to your first putty where you are in chroot (the same way can be used to get the created files back to your shared folder on your volume1 which can be accessed from windows) change into "test", extract the linux-3.10.x.txz to a directory named "linux-3.10.x" and change into it the following copy's the kernel config file from synology to the right place for use/build cp synoconfigs/bromolow .config we make a fallback copy make ARCH="x86_64" oldconfig we start the ascii art menu and search for the missing driver to activate cursor/return are your friend in navigating, space selects, we activate the driver to an "M" so its build as module (*.ko file we need) there will be tons of descriptions how to do it, just google if needed make ARCH="x86_64" menuconfig on exit we save the configuration and with the following we make/create the modules (will take a while) make ARCH="x86_64" modules now you have to find your *.ko file (use some nice ls options, to be expanded later) usually you will have to look in /test/linux-3.10.x/drivers/scsi or block copy that file to /test for easy access when we put it in the boot image 2. modify the "synoboot.img" use osfmount (windows) to extract the "extra.lzma" (see dsm 5.2 to 6.0 guide, used there to edit grub.cfg in synoboot.img) in "extra.lzma" are the additional *.ko files and a config file where the files to be loaded on boot are named -> see forum thread "dsm 5.2 to 6.0" with howto to modify jun's loader for usb vid/pid and mac, its basically the same you just open the other partition (30MB) and extract the "extra.lzma" copy the "extra.lzma" to the share of the dsm so we have local access in a putty session on dsm in putty session #2 ("normal" session without chroot) we copy the "extra.lzma" to the "test" directory in the chroot environment go to putty session#1 (in chroot) decompress "extra.lzma" to "extra" ("extra.lzma" is a compressed cpio file) with: lzma -d extra.lzma with ls we can check that "extra.lzma" is now just ""extra" (a cpio file without the extension cpio) create a new directory, copy the "extra" there, change into it and extract it with: cpio -idv < extra delete the remaining file "extra" inside this directory we copy the *.ko file into usr/lib/modules/ and in /etc we edit the file rc.modules (easy with midnight commander, go to file, press F4, internal editor) network drivers seems to be added under EXTRA_MODULES, storage drivers under DISK_MODULES, just go to the end of the line and fill in the name of the *.ko file without the ".ko", what you add is bsicly a blank and the name rc.modules looks like this: EXTRA_MODULES="mii mdio libphy atl1 atl1e atl1c alx uio ipg jme skge sky2 ptp_pch pch_gbe qla3xxx qlcnic qlge netxen_nic sfc e1000 pcnet32 vmxnet3 bnx2 libcrc32c bnx2x cnic e1000e igb ixgbe r8101 r8168 r8169 tg3 usbnet ax88179_178a button evdev ohci-hcd" DISK_MODULES="BusLogic vmw_pvscsi megaraid_mm megaraid_mbox megaraid scsi_transport_spi mptbase mptscsih mptspi mptsas mptctl ata_piix megaraid_sas mpt2sas mpt3sas" EXTRA_FIRMWARES="bnx2/bnx2-rv2p-09ax-6.0.17.fw bnx2/bnx2-rv2p-09-6.0.17.fw bnx2/bnx2-rv2p-06-6.0.15.fw tigon/tg3_tso5.bin tigon/tg3_tso.bin tigon/tg3.bin" if your controller or nic needs a firmware, you add the file under usr/lib/modules/firmware/ and add the appropriate line in EXTRA_FIRMWARES, if a extra directory inside "firmware "is used it has to be added to the name, see the bnx2 firmware files after everything is in place we recreate the cpio file, re-compress it as lzma and write it in the directory above as "extra.lzma" the command is used inside the directory where we extracted the file "extra" (commandline taken from https://github.com/kref/scripts, its what jun uses to create it): (find . -name modprobe && find . \! -name modprobe) | cpio --owner root:root -oH newc | lzma -8 > ../extra.lzma in putty session #2 (without the chroot) we copy "extra.lzma" from the chroot position in filesystem to the location where we can access it from windows if you still have osfmount open to the "synoboot.img" replace the "extra.lzma" with the new one, dismount and close osfmount - our new "synoboot.img" is ready to test it ps: i was asked to make a video - thats much harder to change and i'm to old for this

Yeah that is what I was using, doesn't seem to boot properly though. Using the same settings on a Ubuntu live disc results in a network connection but not with the v1.02a2 img weird. Will start fresh and see how I go. i have 1.02a running 3617xs in virtual box,using the intel pro 1000/mt desktop (bridge mode with the hardware nic) and i gave the nic the mac that was used inside the synoboot.vmdk image (on IDE controller) - try to set the mac propperly so synoimage and vm nic using the same mac? for the disks used in dsm6.1 the vm has to use scsi controller/disks

Update: Decided to have the following set-up: ESXi 6.0 Intel DQ67OW Motherboard 2 x 8GB Corsair Vengeance & 1 x 2GB Kingston (Had Lying about) Dual Port Intel Pro 1000 PCI-E Currently got a SAS3041E-HP and a generic 2 port Sata I have 2x500GB, 2x1TB (SHR on Motherboard sata - Pass-Through) 2x2TB (Raid1 on SAS3041E-HP - Pass-Through) Datastore on generic sata card. My question now is do i put all the hard drives with the same set up in the same vm or separate the 2 disk groups? If i go in same vm i will purchase a better sas card to cope with all he disk drives Sent from my iPhone using Tapatalk Pro

Если не затруднит, укажите модель взлетевшей, для статистики. Ну и не взлетели очень разные, да. если подскажете какой командой посмотреть, посмотрю. а грубо что то такое: intel pro 1000 gt pci e и виртуал бокс у меня не устанавливается, а я отчасти из за него переходил с квик коннект какой то косяк. серийник и мак взял старые из 6,02. при попытке подключить, пишет: невозможно выполнить запрошенную операцию в связи с неизвестной ошибкой. закрываешь окно, и через непродолжительное время квик коннект сам подключается

Если не затруднит, укажите модель взлетевшей, для статистики. Ну и не взлетели очень разные, да. если подскажете какой командой посмотреть, посмотрю. а грубо что то такое: intel pro 1000 gt pci e

Intel Pro 1000 PT can be had on eBay for $15. I can confirm it works with the current Dsm 6 loader. My on-board would not work either. Thanks for the tip ! i'll check that

Intel Pro 1000 PT can be had on eBay for $15. I can confirm it works with the current Dsm 6 loader. My on-board would not work either.

Intel Pro 1000 PT can be had on eBay for $15. I can confirm it works with the current Dsm 6 loader. My on-board would not work either.