Trantor
-
Posts
583 -
Joined
-
Last visited
-
Days Won
7
Posts posted by Trantor
-
-
Forget to tell that I have 3 synology box that can be used to reverse engineer if needed.
I have:
DS918+
RS820RP+
RS815RP+
-
1
-
-
Hi all,
I just check if this project is still alive and it is
and some amazing work have been done.
Unfortunately I don't have time to spent of this but I just seen that Synology uploaded new source code for 24922branch:
https://sourceforge.net/projects/dsgpl/files/Synology NAS GPL Source/24922branch/
Long life to XPEnology
-
5
-
-
seeiis said:Do you have the download link for V1.02-alpha-TEST ?
-
I have done more test about network detecting issues.
I found a "old" Intel I340-T4 adapter (that use igb driver) to run some test:
My test system have an onboard realtek adapter (RTL8102EL 10/100M) + Intel I340-T4
Using jun 1.02 alpha:
No disk in the system : Syno Assistant find both network adapters (intel and realtek)
Disk with DSM (current or old) : Syno Assistant find nothing even using Reinstall boot option
Using my modified version of jun 1.02 alpha:
No disk in the system : Syno Assistant find both network adapters
Disk with DSM (current or old) : Syno Assistant find both network adapters using Reinstall boot option (normal boot doesn't find anything)
After installing DSM 6.1 I loose the realtek adapter.
After checking loaded modules with lsmod it only shows official synology modules ! None of the extra's modules are loaded.
Modules are not even copied in /lib/modules/update/
I think there is something wrong during boot sequence that prevent modules to be loaded/copied properly.
I've ordered a serial rs232 cable in order to debug this sh*t and see what's going on during boot.
EDIT:
No time to run some test with blank disk
-
There are lot of people which have network detecting issues.
All intel drivers (igb, e1000e, ixgbe) are already included, updated and loaded by Synology so don't ask if someone can add them.
And Yes on some systems with intel adapter it's not working
After some digging I found some topic about intel 10gb not working properly due to Synology parameter in /etc.defaults/modules.conf
Removing these lines seems to fix the issue.
In this file there are parameters for ixgbe (10gb) AND for igb (i210, i340, i350, 825xx)
So I build a test version based on jun's 1.02 alpha for DSM 6.1.
I only modified two things:
- Remove parameters for ixgbe and igb in/etc.defaults/modules.conf (ramdrive)
- Replace the realtek r8169 by the latest one from realtek website (r8168, r8169 and r8101) this fix the network issue for my Zotac with RTL8111/8168/8411
Download : https://download.xpenology.xyz/ALPHA/DS3615xs%206.1%20Jun's%20Mod%20V1.02-alpha-TEST.zip
Please give feedback if you have i210 adapter
This is a TEST build based on an Alpha loader do not use it unless you know what you are doing !
EDIT:
During installation /etc.defaults/modules.conf is replace by the one inside the PAT file.
IF the modification in the ramdrive allows your system to shows on the network, it will not survive the first reboot during setup.
But if this happen we will just have to make little patch to prevent overwriting the file during setup
Feedback for @junI was able to get the network drivers to load one time on the DS916p 6.1 Jun's Mod V1.02-alpha synoboot image. This was on a Gigabyte GA-Z87x-UD5H motherboard which has 2 on-board network ports. The chips are
LAN Chipset
Intel i217V
Second LAN Chipset
Intel i210AT
After the initial boot, subsequent reboots the loader would not recognize the network ports.
My Gigabyte GA-X99-UD3 with i218V is working ok with jun's 1.02 alpha loader.
Your i217V adapter should be working.
It's supported by the e1000e drivers (i217, i218, i219...)
-
Clean OP, add link to Pokanskiman's tutorial and add download mirror.
DMS 6.1 uses updated kernel (3.10.102).
The kernel sources for 6.0.2 (3.10.77) has not been released yet so don't hope anything from Syno before months.
Like before no sources = no loader
jun's v1.01 loader CAN'T support DSM 6.1 so DO NOT UPGRADE !
I've rebased the vendor changes on 3.10.77 to 3.10.102, seems still works.
jun your are the MAN
Next step is I think to troubleshoot the network issue on some system that "prevent" network driver to load at boot.
How can I (or the community) help you to debug ?
How do you display/access the early boot stage without serial console ?
-
Add download mirror for jun's loader in the OP
-
Clean OP, add link to Pokanskiman's tutorial and add download mirror.
DMS 6.1 uses updated kernel (3.10.102).
The kernel sources for 6.0.2 (3.10.77) has not been released yet so don't hope anything from Syno before months.
Like before no sources = no loader
jun's v1.01 loader CAN'T support DSM 6.1 so DO NOT UPGRADE !
-
Also please integrate Realtek RTL8111GR
thanks in advance
Another vote for Realtek RTL8111GR nic driver especially for new DSM6.0.2 loader.
Thanks.
+1 more for Realtek RTL8111GR driver being integrated so I can continue to use my ASRock N3150-ITX mobo.
I assume 6.0.2 will NOT work on with my on board NIC after reading this:
"Polanskiman wrote:
* Note: r8169 from Trantor archive doesn't work with my on-board Realtek RTL8111GR. So I kept the existing which is also much bigger."
viewtopic.php?f=2&t=22100&start=280&hilit=Realtek+RTL8111GR
THANK YOU!!
Does anyone with "problematic" Realtek RTL8111GR have tried latest XPEnoboot 5.2 release ?
If some of you have working 5.2 release with 8111GR nic can you please give more details about it (lspci, loaded drivers..)
-
I would like to help the community about some nic not detected by jun's loader.
I read that lot of people are asking for reatek,intel,atheros... driver.
These driver are already included and loaded at boot.
But it seems that some nic doesn't come up
I even read that editing grub.conf allow a user to get his i210 working : https://xpenology.com/forum/topic/7507-tutorial-installmigrate-dsm-52-to-602-juns-loader/?do=findComment&comment=62079
So I test myself and here are the results:
With initrd $img/ramdisk.lzma $img/$extra_initrd (latest drivers are loaded)
admin@Diskstation:/$ dmesg | grep -i intel [ 19.425168] e1000e: Intel(R) PRO/1000 Network Driver - 3.1.0.2-NAPI [ 19.448365] Intel(R) Gigabit Ethernet Network Driver - version 5.2.17 [ 19.459710] Intel(R) 10 Gigabit PCI Express Network Driver - version 4.3.13
With initrd $img/$extra_initrd $img/ramdisk.lzma ("old" drivers are loaded from ramdisk.lzma)
admin@Diskstation:/$ dmesg | grep -i intel [ 20.458148] e1000e: Intel(R) PRO/1000 Network Driver - 3.3.5-NAPI [ 20.472911] Intel(R) Gigabit Ethernet Network Driver - version 5.3.5.4 [ 20.508066] Intel(R) 10GbE PCI Express Linux Network Driver - version 4.4.6
In both case e1000e, igb and ixgbe are loaded but in the second case extra.lzma (updated drivers) are overwritten by the "old" in the ramdrive.lzma
I'm glad to see that this trick allow some user to get their nic working but it's not normal that old driver works and the updated one doesn't.
Something is going wrong during the initial/pre boot step but I don't have serial cable at home to run some debug.
Gigabyte X99-UD4 with an Intel I218 (e1000e) is ok
Zotac ID11 with a Realtek RTL8111/8168/8411 (r8168) is ok
Asus E35M1-I DELUXE wit Realtek RTL8111E (r8168) is ok
I really don't understand what's happen on some system
PS : Big thank to Polanskiman for your amazing jobs in this thread
-
Great work Arcao
OP Updated with latest links
-
During my test with updated network modules, I have tried to add sata driver including ata_piix (needed for my old ICH7 mobo).
When trying to insmod these sata modules it complain about unknow syno_libata_get_index or something like that.
This function should be included in the kernel (function declared in libata-core) but it doesn't.
I even try building these module with vanilla 3.10.77 kernel.
sata_sil, sata_via, sata_amd .... load ok but ata_piix module is stuck during insmod.
Of course using vanilla is not great idea and probably will cause disk naming conflict and other bugs.
I tried to set CONFIG_SYNO_FIXED_DISK_NAME=n (in menuconfig: Synology Enhancement Features -> Device Drivers -> SATA -> Use Fixed Disk Name) and compile ata_piix kernel module. Now it's successfully loaded with insmod, but hard to say how it will work without Use Fixed Disk Name.
Use Fixed Disk NameMake internal SATA disk use fixed device name. For example, the first channel is sda, the second is sdb, etc. All USB disk would start from sdq.
Interesting...
If syno_libata_get_index is missing in the genuine syno kernel it means that it's disable, otherwise when we insmod module it shouldn't complain about missing function.
Can you repack this in a test ramdisk so I can test it with my mobo using ata_piix.
About your r8169 not working I think it's a crappy adapter that need firmware like my old dlink s*** ^^
r8169 from kernel is FULL of bugs for lot of adapters. This is why realtek create r8168 to split support in separate modules.
Edited OP with new links.
-
I can't find the name of the controller but it's integrated in the motherboard.
I know the chipset is an Intel® Q963 Express chipset. Is it also controlling the sata ports?
I'm still looking for the controller's name.
It's ICH8R - You need ata_piix.ko, which is not included, I will add it to bootimage.
During my test with updated network modules, I have tried to add sata driver including ata_piix (needed for my old ICH7 mobo).
When trying to insmod these sata modules it complain about unknow syno_libata_get_index or something like that.
This function should be included in the kernel (function declared in libata-core) but it doesn't.
I even try building these module with vanilla 3.10.77 kernel.
sata_sil, sata_via, sata_amd .... load ok but ata_piix module is stuck during insmod.
Of course using vanilla is not great idea and probably will cause disk naming conflict and other bugs.
-
Here is my little contribution to this release :
https://download.xpenology.xyz/drivers/ ... rs-dsm6.7z
Updated broadcom tg3, bnx2, bnx2x, cnic
Updated intel e1000e (I219 support)
Add/Updated realtek r8168, r8169 and r8101 (r8169 from realtek website no the one inside the kernel tree)
I use kernel source/toolchain from first post to compile these modules.
Sorry no time to repack this inside the current loader.
-
I just edited the first post in this thread to add links from setsunakawa, quicknick and arcao to help user to get what they need easily.
If I forgot to add some link just tell me.
I think it should be great if someone can compile more common/updated network drivers like r8168, r8169 (from realtek.com not the in the kernel tree), bnx2x, e1000e (recent version which support I219 adapters), forcedeth (for nvidia adapters)... and repack them with the new loader
-
Sticky
About the LSI adapter I think it's related to the fact that DSM (3615xs) look for SYNO_DISK_SATA and LSI adapters return things like Avago/LSI xxxx....
DSM return SYNO_DISK_UNKNOWN or SYNO_DISK_SAS so no disks are detected.
In XPEnoboot 5.x the sd.c file is patched in order to never return SYNO_DISK_UNKNOWN nor SYNO_DISK_SAS but always return SYNO_DISK_SATA.
To sum up I don't think is related to driver because mpt2sas in already incldued in genuine Syno but rather in the way that kernel/dsm detect drives.
There is more informations about this here : viewtopic.php?f=2&t=18089
-
This is very interesting
Unfortunately I'm very busy at work and have no time for XPEnology.
I'm glad that people continue to develop this project.
Don't forget that compiling kernel from Syno sources is very tricky.
Syno don't release all sources, some parts are missing like iscsi and synoacl.
Using original syno kernel + additional modules is very great but should prevent us to edit some part of the kernel.
You can use XPEnoboot 5.2 sources if you want to check how I did to add/update drivers and/or the HARDWARE SUPPORTED LIST to ckeck drivers names.
For exemple Broadcom tg3, bnx2 and bnx2x are higly patched in order to have successful compilation. Intel and realtek are very easy to update.
Keep in mind that including latest version of module/driver allow more hardware support that using sources from kernel tree.
Happy XPEnologing
-
I found a Fujitsu adapter based on LSI chip.
I will run more test this week-end.
-
Hi @all.
Does anyone know if the HPE SC08e card works with XPEnology? I have a HP MSA P2000 G3 with 12x2TB which I would like to connect to one of my XPEnology bare-metal systems.
Cheers
Yes the HPE SC08e adapter uses LSI chip supported by the mpt2sas driver which is included by Synology on their genuine NAS
So I think you can install the standard XPEnoboot and DSM should detects it
Download : viewtopic.php?f=2&t=5026
Before testing the standard version, can you please test my test version based on RS18016xs+ which use SAS controller like yoursand report back if your drives are detected or not.
It's an early test build so test it with disk without data !
Download : viewtopic.php?f=2&t=18089&p=71404#p71404
-
I have edited the actual bootloader so it's uses the RS18016xs+ rd.gz file.
In this iso the isolinux.cfg file is edited in order to show what type of disk DSM detect at boot (syno_disk_type_get : XXXX).
If you don't use this iso (and use flash drive instead) you have to set syno_hw_version=RS18016xs+ and loglevel=1 in syslinux.cfg !
Download : https://download.xpenology.xyz/XPEnoboo ... .1-SAS.iso
I run this on a VM and bare metal
Both are showing SYNO_DISK_SATA (SYNO_DISK_UNKNOW (scsi) ->SATA for the VM) during boot so DSM can't detect them.
I pretty sure with your SAS adapter it will show syno_disk_type_get : SYNO_DISk_SAS at boot and DSM should detects your drives.
Use this PAT if DSM detects your drives : https://usdl.synology.com/download/DSM/ ... +_5967.pat
This is a test version so DO NOT USE IT unless you know what you are doing
-
I just make some modification to the kernel and boot loader.
I remove the "patch" that prevent LSI card to return SYNO_DISK_SAS.
I add debug informations at boot to display the type of disk DSM detects (SYNO_DISK_SATA, SYNO_DISK_SAS or SYNO_DISK_UNKNOW)
You need to set loglevel=1 in GRUB or syslinux.cfg to see the debug informations.
I also added sas_enclosure_max="14" and supportsas="yes" to synoconfig file.
I reduce the retry want_idx from 15 to 5 to get faster boot when there is lot of drives.
Like I said above I don't have LSI adapter anymore.
I tested this new kernel on my current test system which as two SATA drives connected to the mainboard.
DSM detect the disks as SYNO_DISK_SATA but Syno Assistant and Web Assistant say that there is no disk in my system !
I use the console with syno telnet secret password to edit the synoconfig file and remove sas_enclosure_max and supportsas.
Just click refresh on the Web Assistant and DSM detects my drives....so these options are somehow preventing DSM to properly detect drives and allow install on them.
So maybe with a LSI Adapter DSM will detect drives as SYNO_DISK_SAS and maybe DSM can install on them.
If someone have LSI adapter and want to test and gives feedbacks
Remember this is a test version with bugs so DO NOT USE IT unless you know what you are doing
Download : https://download.xpenology.xyz/zImage-sas
Rename zImage-sas to zImage and copy it to your flash drive.
-
Does anyone know if this card is supported by XPEnology?
ExpressSAS H60F
Low-Profile 16-Internal Port 6Gb/s SAS/SATA PCIe 2.0 Host Bus Adapter
Model No. ESAS-H60F-000
It should be by the adapter pm80xx driver.
-
Found lot of code in the kernel source about SAS.
Like in sd.c:
* SAS disk names starts at sas1. The 26th device is sas26 and the * 27th is sas27.
I think this confirm the fact that enclosure have static numbering.
Right now in this file, someone make a patch to "fix" LSI but I think break sas in the same time
#ifndef XPENOLOGY// sas disks
if (SYNO_PORT_TYPE_SAS == sdp->host->hostt->syno_port_type) {
return SYNO_DISK_SAS;
}
#endif /*Fix LSI Controllers Broken*/
We can try adding some debug code to see what kind of disk DSM detect at boot and add supportsas to synoconfig.
I can't do it because I don't have my LSI adapter anymore
-
Again with problems.
when i was completly rearmed my shr raid with 3 disk i want to expand with another one and ...what happen ?
again, i check all de thisk with crystal disk and all are Ok but the raid always fail, mvsas problem again?
After some lame fix I "backported" mvsas from kernel 4.7.
- Download mvsas.ko : https://download.xpenology.xyz/mvsas.ko
- Boot your system and copy mvsas.ko to your DSM (do not copy it in /lib/modules/ it will be overwritten at reboot)
- rmmod mvsas (during grub or when DSM is booted) and insmod the "new" one (!! if DSM is only installed on disk connected to your marvell controller your system will crash !!)
- Run some tests
Can you please give the output of /var/messages when DSM mark your drive as faulty/bad.
Synology Sources for 24922branch
in Developer Discussion Room
Posted
Apart from the kernel version that changes from DSM 6.1 (3.10.102) to 6.2 (3.10.105), does syno included new protection ?
The issue with 6.2 when loading drivers/modules that crash, does it crash because of protection or "just" because these modules are not build with latest GPL released ?
I've been offline from long long time but I discovered that Syno released GPL sources for DSM 6.1-15047 (kernel 3.10.102) in september 2017 and no one tried to build it's own kernel from there. I am very suprised 😮 since there are loader that fool the protection, the only missing part is a working kernel that we can custom.