Driver extension jun 1.02b/DSM6.1.x for 3615xs / 3617xs / 916+


Recommended Posts

5 hours ago, zOnDeR said:

I did everything according to the instructions on which you gave the link

-(DSM 6.0.2, v1.01 loader, Customized extra.lzma ramdisk.)

please open a new topic then if you want to go deeper into 6.0

Link to post
Share on other sites

Hello,

 

I just managed to run Xpenoboot DS3615xs 5.2 5644 with the DSM_DS3615xs_5644.pat.

I works perfectly fine, I just can't use the first HDD slot but this should be easily fixed with BIOS access and modified Boot order.

 

Any idea why it would work under 5.2.5644 and not above ?

If you think it could be driver related, let me know if I can get some interesting data output for you to put your eyes on. If not, next post will be in a more appropriate thread.

 

Thanks,

 

 

Link to post
Share on other sites

the interesting part for 6.1 would be the log when loading the realtek driver (on the booting/running 6.1 system), from the lspci with ubuntu 16.04 you did we already know the drivers needed for the hardware (r8169 for nic and ahci for storage)

kind of crazy that it does get a dhcp adress and cant be reached/found in network, in theory when ping does work the network is up and running so it might be something else, but that thing should happen too when using a different nic i guess

 

did you configure the real mac address in grub.cfg with 6.1?

also disconnecting any additional hardware when trying to install 6.1 could be a thing

 

Edited by IG-88
Link to post
Share on other sites

Hi @IG-88. Can you please look into r8168.ko for DS3617xs? It seems that the new DSM 6.1.6 is breaking that module. I have seen two reports of people not being able to have network access after the update. Both users where running DS3617xs with following boards: EP45-DS3L (Realtek 8111C) and N3150ITX-DC (Realtek RTL8111GR). Not sure if DS3615xs is also affected.

Link to post
Share on other sites

 

On 3/29/2018 at 2:22 PM, Polanskiman said:

Can you please look into r8168.ko for DS3617xs? It seems that the new DSM 6.1.6 is breaking that module.

 

Nothing general I'd say

I have a pci-e card with rtl8168e for testing

jun's 1.02b (3617, only vid/pid changed), extra.lzma 4.7, dsm 6.1.6 fresh install -> no problems

I will do a update test later (6.1.5->6.1.6)

 

there seem to be unsuccessfuls with 3617 on esxi too, maybe nothing to do with the nic?

 

i could do a test version with just the original kernel driver instead of the realtek driver if that helps

 

also there is a entry with success with a 8111C

    - Outcome of the update: SUCCESSFUL
    - DSM version prior update: DSM 6.1.5
    - Loader version and model: JUN'S LOADER v1.02b - DS3617xs
    - Using custom extra.lzma: YES - extra.lzma for DS3617 v4.5 made by IG-88
    - Installation type: BAREMETAL Asus  P5Q-EM
    - Additional comments: REBOOT REQUIRED

 

from my extra.lzma change log

[13.12.2017] new 4.3 with newer realtek r8168/r8169 drivers

so if he used 4.5 it has the same drivers as the actual 4.7

 

EDIT: also tested update 6.1..5->6.1.6, no problems found

 

Link to post
Share on other sites

Yeah strange not sure what is going on. Didn’t actually look in details and don’t have those nics so couldn’t test. It was just a guess because the two first who reported issues had two different realtek NICs using that module. But something is wrong with ds3617xs because even re-imaging the loader and trying to reinstall did not work for them. VMs are also experiencing issues. Only using 3615xs did work for all of them. As for that entry it was posted after.

 

 

Link to post
Share on other sites
Le 28/03/2018 à 00:53, IG-88 a dit :

did you configure the real mac address in grub.cfg with 6.1?

also disconnecting any additional hardware when trying to install 6.1 could be a thing

 

 

I've ran another set of tests to check this area.

 

I can confirm that the mac address i get with any working setup is 00:26:2d:01:d2:2a

I have tried 6.1 with this mac@ in grub cfg with no disk, same result as usual : request an IP and is ping-able but is not discovered by the syno assistant and cannot be directly reached with a browser.

I have tried 6.1 with a random mac@ in grub.cfg with no disk, same as above.

 

Is there a tutorial that could guide me on how to provide the log for driver init on 6.1 ?

 

Just in case, here's an extract of my grub.cfg :

set vid=0x0951
set pid=0x1666
set sn=1430LWN003630
set mac1=00262D01D22A
set rootdev=/dev/md0
set netif_num=1
set extra_args_3615=''

 

 

Link to post
Share on other sites
On 3/29/2018 at 2:22 PM, Polanskiman said:

Hi @IG-88. Can you please look into r8168.ko for DS3617xs? It seems that the new DSM 6.1.6 is breaking that module. I have seen two reports of people not being able to have network access after the update. Both users where running DS3617xs with following boards: EP45-DS3L (Realtek 8111C) and N3150ITX-DC (Realtek RTL8111GR). Not sure if DS3615xs is also affected.

There seems to be something odd with 6.1.6, on a ESXi VM with DS3617xs the paravirtual controller and virtual LSI SAS controller don't load either:

Loading module vmw_pvscsi[ 3.849379] general protection fault
Loading module mptsas[ 3.997779] BUG: unable to handle kernel paging request

 

Link to post
Share on other sites
On 3/31/2018 at 9:29 PM, swords80 said:

There seems to be something odd with 6.1.6, on a ESXi VM with DS3617xs the paravirtual controller and virtual LSI SAS controller don't load either:

 

Loading module vmw_pvscsi[ 3.849379] general protection fault

Loading module mptsas[ 3.997779] BUG: unable to handle kernel paging request

 

However, if Xpenology ESXi VM is booted with a USB key attached to the virtual USB controller, these modules load fine.

root@testnas:/etc# cat /proc/cmdline
syno_hdd_powerup_seq=0 HddHotplug=0 syno_hw_version=DS3617xs vender_format_version=2 console=ttyS0,115200n8
withefi quiet root=/dev/md0 sn=[redacted] mac1=[redacted] netif_num=1
root@testnas:/etc# cat /etc.defaults/VERSION
majorversion="6"
minorversion="1"
productversion="6.1.6"
buildphase="GM"
buildnumber="15266"
smallfixnumber="0"
builddate="2018/03/26"
buildtime="16:58:27"
root@testnas:/etc# lsmod | grep mptsas
mptsas                 38463  2
mptscsih               18705  2 mptsas,mptspi
mptbase                61898  4 mptctl,mptsas,mptspi,mptscsih
root@testnas:/etc# lsmod | grep vmw_pvscsi
vmw_pvscsi             15239  0

 

 

Link to post
Share on other sites
On 3/31/2018 at 1:30 PM, BonanzaCreek said:

Is there a tutorial that could guide me on how to provide the log for driver init on 6.1 ?

 

you would need a serial port an the system that installs dsm and you would connect that with a serial cable to another system and use putty over serial as console

for most people thats to much (they dont even have a serial cable and if the computer that is used as console does not have a serial ports you would also need a usb2serial converter), in you case the easiest way would be to install a 2nd nic, install dsm with it and when dsm boots normal you can (over network with 2nd nic) check the logs to see whats wrong with the onboard realtek and if its to much hassle just leave the 2nd nic and use it for dsm and ignore the onbard nic

 

Link to post
Share on other sites

Thanks for the help @IG-88

 

The ex-490 does not have a serial or ILO.

I also tried to add a second NIC using a USB/RJ45 cable, but apparently it is not recognized by the system.

 

I guess that will be the end of the line.

 

For general knowledge, 5.2.5967 works perfectly fine with the ex490 bare metal without any tinkering in the BIOS and XPEnoboot_DS3615xs_5.2-5644.4 loader.

Link to post
Share on other sites

Hi all. Faced with strange bug, maybe someone could help.

Got an ASUS P9A-I/C2750/SAS/4L motherboard with two Marvell 88SE9485 controllers onboard.

Made a bootable usb flash with 3617xs image, put there extra.lzma v4.7, installed DSM successfully.

All works fine, except sas-controllers:


admin@fSyn:/$ lspci -k | grep 'Kernel driver'
        Kernel driver in use: pcieport
        Kernel driver in use: pcieport
        Kernel driver in use: pcieport
        Kernel driver in use: pcieport
        Kernel driver in use: igb
        Kernel driver in use: igb
        Kernel driver in use: igb
        Kernel driver in use: igb
        Kernel driver in use: ehci-pci
        Kernel driver in use: ahci
        Kernel driver in use: lpc_ich
admin@fSyn:/$ lsmod | grep mvsas
mvsas                  53061  0
admin@fSyn:/$ lspci -v
...
0000:01:00.0 Class 0104: Device 1b4b:9485 (rev c3)
        Subsystem: Device 1043:8635
        Flags: bus master, fast devsel, latency 0, IRQ 7
        Memory at de240000 (64-bit, non-prefetchable) [size=128K]
        Memory at de200000 (64-bit, non-prefetchable) [size=256K]
        Expansion ROM at de260000 [disabled] [size=64K]
        Capabilities: <access denied>

0000:02:00.0 Class 0104: Device 1b4b:9485 (rev c3)
        Subsystem: Device 1043:8635
        Flags: bus master, fast devsel, latency 0, IRQ 7
        Memory at de140000 (64-bit, non-prefetchable) [size=128K]
        Memory at de100000 (64-bit, non-prefetchable) [size=256K]
        Expansion ROM at de160000 [disabled] [size=64K]
        Capabilities: <access denied>
...

For some reason driver doesn't recognize controller.

Checked device id's in kernel sources at https://sourceforge.net/projects/dsgpl/files/Synology NAS GPL Source/15047branch/broadwell-source/ - mvsas driver have these ids in mv_init.c

There is nothing in dmesg regarding mvsas.

Also all work fine on Ubuntu 17.10

Have no idea what to check next.

Please help :)

Link to post
Share on other sites

Motherboard GA-G31M-ES2L
Intel® Celeron® E3300 2.50 GHz processor
Memory two modules of 1 GB DDR2 Patriot Memory PSD21G8002
One hard drive WD Red WD40EFRX, 4TB, HDD, SATA III, 3.5 "
Two drives ST4000DM005-2DP166 4TB, HDD, SATA III, 3.5 "
Two disks lWD Caviar Black WD1003FZEX 1Tb SATA III, 3.5 "

Controller Adaptec RAID ASR-5405Z

When installing DSM DSM 6.1.5 with the modified Customized extra.lzma ramdisk, unfortunately Controller Adaptec RAID ASR-5405Z did not detect the hard drive.

cat /var/log/dmesg >> /volumeUSB1/usbshare/dmesg.log

dmesg.log

 
admin@NAS13:/$ lspci -k | grep 'Kernel driver'  
admin@NAS13:/$ lspci -k | grep 'Kernel driver'
        Kernel driver in use: pcieport
        Kernel driver in use: pcieport
        Kernel driver in use: pcieport
        Kernel driver in use: uhci_hcd
        Kernel driver in use: uhci_hcd
        Kernel driver in use: uhci_hcd
        Kernel driver in use: uhci_hcd
        Kernel driver in use: ehci-pci
        Kernel driver in use: lpc_ich
        Kernel driver in use: ata_piix
        Kernel driver in use: aacraid
        Kernel driver in use: e1000e
        Kernel driver in use: atl1c

 

How to fix?
sorry for my English
Thank you!
Edited by Polanskiman
Added code tag.
Link to post
Share on other sites
1 hour ago, zOnDeR said:

Controller Adaptec RAID ASR-5405Z

When installing DSM DSM 6.1.5 with the modified Customized extra.lzma ramdisk, unfortunately Controller Adaptec RAID ASR-5405Z did not detect the hard drive.

cat /var/log/dmesg >> /volumeUSB1/usbshare/dmesg.log

dmesg.log

 

the driver crashed on load, try to install dsm 6.1.3 (thats the version the source for the drivers is used) also try to use the new 4.8 version (it will contain a frehly compiled version, but i dont think that will fix it, the drivers seemed to be compiled in a way that thea where working, could also be a incompatibility from synology or a general one that was fixed in later kernel versions)

Link to post
Share on other sites
5 hours ago, tr33ks said:

Hi all. Faced with strange bug, maybe someone could help.

Got an ASUS P9A-I/C2750/SAS/4L motherboard with two Marvell 88SE9485 controllers onboard.

...

- mvsas driver have these ids in mv_init.c

There is nothing in dmesg regarding mvsas.

Also all work fine on Ubuntu 17.10

Have no idea what to check next.

Please help :)

 

found this patch

https://marc.info/?l=linux-scsi&m=146005515401214

i will change the kernel source and compile a new driver, new extra.lzma version 4.8 should be ready later this evening

 

Edited by IG-88
Link to post
Share on other sites
On 4/9/2018 at 2:11 AM, IG-88 said:

 

found this patch

https://marc.info/?l=linux-scsi&m=146005515401214

i will change the kernel source and compile a new driver, new extra.lzma version 4.8 should be ready later this evening

 

 

Thanks for help.

Took me a while to find a com cable, but now i have a log.

Something went wrong.

 
Spoiler

:: Loading module sx8 ... [  OK  ]
:: Loading module aacraid ... [  OK  ]
:: Loading module aic94xx ... [  OK  ]
:: Loading module 3w-9xxx ... [  OK  ]
:: Loading module 3w-sas ... [  OK  ]
:: Loading module mvumi ... [  OK  ]
:: Loading module mvsas[    8.208271] sd 3:0:0:0: [synoboot] No Caching mode page found
[    8.214351] sd 3:0:0:0: [synoboot] Assuming drive cache: write through
[    8.224186] sd 3:0:0:0: [synoboot] No Caching mode page found
[    8.230211] sd 3:0:0:0: [synoboot] Assuming drive cache: write through
[    8.491062] sd 3:0:0:0: [synoboot] No Caching mode page found
[    8.496934] sd 3:0:0:0: [synoboot] Assuming drive cache: write through
[   12.950713] BUG: unable to handle kernel NULL pointer dereference at 0000000000000078
[   12.958773] IP: [<ffffffff81329ed2>] sas_scsi_recover_host+0xf2/0xd20
[   12.965356] PGD 4673a5067 PUD 4670a7067 PMD 0
[   12.969950] Oops: 0002 [#1] SMP
[   12.973296] Modules linked in: mvsas(+) mvumi 3w_sas 3w_9xxx aic94xx aacraid sx8 mpt3sas(O) mpt2sas(O) megaraid_sas ata_piix mptctl mptsas mptspi mptscsih mptbase scsi_transport_spi megaraid megaraid_mbox megaraid_mm vmw_pvscsi BusLogic usb_storage xhci_hcd uhci_hcd ohci_hcd ehci_pci ehci_hcd usbcore usb_common mv14xx(O) el000(O)
[   13.003617] CPU: 0 PID: 3982 Comm: scsi_eh_2 Tainted: G           O 3.10.102 #15266
[   13.011417] Hardware name: ASUS P9A-I/C2750/SAS/4L/P9A-I/C2750/SAS/4L, BIOS 1902 11/07/2016
[   13.019944] task: ffff88046ad3f800 ti: ffff8804669c8000 task.ti: ffff8804669c8000
[   13.027555] RIP: 0010:[<ffffffff81329ed2>]  [<ffffffff81329ed2>] sas_scsi_recover_host+0xf2/0xd20
[   13.036601] RSP: 0000:ffff8804669cbda8  EFLAGS: 00010296
[   13.041993] RAX: 0000000000000078 RBX: ffff8804669af800 RCX: 000000000000000e
[   13.049254] RDX: 0000000000000032 RSI: 0000000000000246 RDI: ffffffff81a66968
[   13.056528] RBP: ffff8804669af800 R08: 000000000000000a R09: 000000000000fffe
[   13.063795] R10: 00007fcc7ae1d9d0 R11: 00000000000002bc R12: ffff88046ad3f800
[   13.071079] R13: ffff8804669cbe78 R14: ffff88046ad3f800 R15: 0000000000000000
[   13.078348] FS:  0000000000000000(0000) GS:ffff88047fc00000(0000) knlGS:0000000000000000
[   13.086568] CS:  0010 DS: 0000 ES: 0000 CR0: 000000008005003b
[   13.092421] CR2: 0000000000000078 CR3: 0000000469fe0000 CR4: 00000000001007f0
[   13.099687] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
[   13.106962] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
[   13.114254] Stack:
[   13.116310]  0000000000000000 ffff88046ad3f800 ffffffff8106522b 0000000000000000
[   13.123942]  ffff8804669af800 0000000000000000 000000016aca5410 0000000000000078
[   13.131562]  0000000000000080 0000000000000198 0000000000009000 ffff8804669af888
[   13.139185] Call Trace:
[   13.141690]  [<ffffffff8106522b>] ? idle_balance+0x11b/0x140
[   13.147435]  [<ffffffff81060103>] ? pick_next_task_fair+0x63/0x160
[   13.153714]  [<ffffffff8130f0bb>] ? scsi_error_handler+0x9b/0x470
[   13.159949]  [<ffffffff814aee97>] ? __schedule+0x3a7/0x8e0
[   13.165532]  [<ffffffff8130f020>] ? scsi_eh_get_sense+0x100/0x100
[   13.171741]  [<ffffffff810501ff>] ? kthread+0xaf/0xc0
[   13.176885]  [<ffffffff81050150>] ? kthread_create_on_node+0x110/0x110
[   13.183544]  [<ffffffff814b0f48>] ? ret_from_fork+0x58/0x90
[   13.189232]  [<ffffffff81050150>] ? kthread_create_on_node+0x110/0x110
[   13.195874] Code: 58 80 00 01 fb 8b 8b dc 00 00 00 8b 93 d8 00 00 00 48 c7 c6 e0 6d 65 81 48 c7 c7 90 91 72 81 31 c0 e8 64 04 18 00 48 8b 44 24 38 <f0> 80 08 08 48 8b 83 10 05 00 00 4c 8b 6c 24 68 48 8b 8b c8 00
[   13.216398] RIP  [<ffffffff81329ed2>] sas_scsi_recover_host+0xf2/0xd20
[   13.223084]  RSP <ffff8804669cbda8>
[   13.226640] CR2: 0000000000000078
[   13.230040] ---[ end trace acef4991e89cc10b ]---

 

 

Edited by Polanskiman
Updated spoiler plugin code
Link to post
Share on other sites
  • 3 weeks later...

I am using Xpenology 5.2.

I have Xpenology 6.1, but it does not support my system yet.

When booting using Xpenology 6.1 (Jun's 1.02b + Extra 4.8), I can not find NAS on the network.

AMD CPU is used.
I did not load all of the drivers that support my hardware, so I did not find it on the network, so I got the following information after booting with Xpenology 5.2.5967.1 Loader.
If you need other information to resolve this issue, please tell us. Thank you.

 

Spoiler

lspci -k | grep 'Kernel driver'

	Kernel driver in use: pcieport
	Kernel driver in use: pcieport
	Kernel driver in use: ahci
	Kernel driver in use: ohci_hcd
	Kernel driver in use: ehci-pci
	Kernel driver in use: ohci_hcd
	Kernel driver in use: ehci-pci
	Kernel driver in use: ohci_hcd
	Kernel driver in use: pcieport
	Kernel driver in use: ohci_hcd
	Kernel driver in use: ehci-pci
	Kernel driver in use: r8168

 

 

Spoiler

lsmod | grep mvsas

mvsas                  51605  0 

 

 

Spoiler

lspci -v

00:00.0 Class 0600: Device 1022:1510
	Subsystem: Device 1022:1510
	Flags: bus master, 66MHz, medium devsel, latency 32

00:01.0 Class 0300: Device 1002:9804
	Subsystem: Device 1022:1511
	Flags: bus master, fast devsel, latency 0, IRQ 11
	Memory at b0000000 (32-bit, prefetchable) [size=256M]
	I/O ports at f000 [size=256]
	Memory at feb00000 (32-bit, non-prefetchable) [size=256K]
	Expansion ROM at <unassigned> [disabled]
	Capabilities: [50] Power Management version 3
	Capabilities: [58] Express Root Complex Integrated Endpoint, MSI 00
	Capabilities: [a0] MSI: Enable- Count=1/1 Maskable- 64bit+
	Capabilities: [100] Vendor Specific Information: ID=0001 Rev=1 Len=010 <?>

00:01.1 Class 0403: Device 1002:1314
	Subsystem: Device 1022:1511
	Flags: bus master, fast devsel, latency 0, IRQ 10
	Memory at feb44000 (32-bit, non-prefetchable) [size=16K]
	Capabilities: [50] Power Management version 3
	Capabilities: [58] Express Root Complex Integrated Endpoint, MSI 00
	Capabilities: [a0] MSI: Enable- Count=1/1 Maskable- 64bit+
	Capabilities: [100] Vendor Specific Information: ID=0001 Rev=1 Len=010 <?>

00:04.0 Class 0604: Device 1022:1512
	Flags: bus master, fast devsel, latency 0
	Bus: primary=00, secondary=01, subordinate=01, sec-latency=0
	I/O behind bridge: 00001000-00001fff
	Memory behind bridge: 7f000000-7f1fffff
	Prefetchable memory behind bridge: 000000007f200000-000000007f3fffff
	Capabilities: [50] Power Management version 3
	Capabilities: [58] Express Root Port (Slot+), MSI 00
	Capabilities: [a0] MSI: Enable- Count=1/1 Maskable- 64bit+
	Capabilities: [b0] Subsystem: Device 1022:1234
	Capabilities: [b8] HyperTransport: MSI Mapping Enable+ Fixed+
	Capabilities: [100] Vendor Specific Information: ID=0001 Rev=1 Len=010 <?>
	Kernel driver in use: pcieport

00:07.0 Class 0604: Device 1022:1515
	Flags: bus master, fast devsel, latency 0
	Bus: primary=00, secondary=02, subordinate=02, sec-latency=0
	I/O behind bridge: 0000e000-0000efff
	Memory behind bridge: fea00000-feafffff
	Prefetchable memory behind bridge: 00000000d0000000-00000000d00fffff
	Capabilities: [50] Power Management version 3
	Capabilities: [58] Express Root Port (Slot+), MSI 00
	Capabilities: [a0] MSI: Enable- Count=1/1 Maskable- 64bit+
	Capabilities: [b0] Subsystem: Device 1022:1234
	Capabilities: [b8] HyperTransport: MSI Mapping Enable+ Fixed+
	Capabilities: [100] Vendor Specific Information: ID=0001 Rev=1 Len=010 <?>
	Kernel driver in use: pcieport

00:11.0 Class 0106: Device 1002:4391 (rev 40) (prog-if 01)
	Subsystem: Device 1002:4393
	Flags: bus master, 66MHz, medium devsel, latency 32, IRQ 19
	I/O ports at f140 [size=8]
	I/O ports at f130 [size=4]
	I/O ports at f120 [size=8]
	I/O ports at f110 [size=4]
	I/O ports at f100 [size=16]
	Memory at feb4f000 (32-bit, non-prefetchable) [size=1K]
	Capabilities: ['70'] SATA HBA v1.0
	Capabilities: ['a4]' PCI Advanced Features
	Kernel driver in use: ahci

00:12.0 Class 0c03: Device 1002:4397 (prog-if 10)
	Subsystem: Device 1002:4397
	Flags: bus master, 66MHz, medium devsel, latency 32, IRQ 18
	Memory at feb4e000 (32-bit, non-prefetchable) [size=4K]
	Kernel driver in use: ohci_hcd

00:12.2 Class 0c03: Device 1002:4396 (prog-if 20)
	Subsystem: Device 1002:4396
	Flags: bus master, 66MHz, medium devsel, latency 32, IRQ 17
	Memory at feb4d000 (32-bit, non-prefetchable) [size=256]
	Capabilities: [c0] Power Management version 2
	Capabilities: [e4] Debug port: BAR=1 offset=00e0
	Kernel driver in use: ehci-pci

00:13.0 Class 0c03: Device 1002:4397 (prog-if 10)
	Subsystem: Device 1002:4397
	Flags: bus master, 66MHz, medium devsel, latency 32, IRQ 18
	Memory at feb4c000 (32-bit, non-prefetchable) [size=4K]
	Kernel driver in use: ohci_hcd

00:13.2 Class 0c03: Device 1002:4396 (prog-if 20)
	Subsystem: Device 1002:4396
	Flags: bus master, 66MHz, medium devsel, latency 32, IRQ 17
	Memory at feb4b000 (32-bit, non-prefetchable) [size=256]
	Capabilities: [c0] Power Management version 2
	Capabilities: [e4] Debug port: BAR=1 offset=00e0
	Kernel driver in use: ehci-pci

00:14.0 Class 0c05: Device 1002:4385 (rev 42)
	Subsystem: Device 1002:4385
	Flags: 66MHz, medium devsel

00:14.2 Class 0403: Device 1002:4383 (rev 40)
	Subsystem: Device 1002:4383
	Flags: bus master, slow devsel, latency 32, IRQ 7
	Memory at feb40000 (64-bit, non-prefetchable) [size=16K]
	Capabilities: [50] Power Management version 2

00:14.3 Class 0601: Device 1002:439d (rev 40)
	Subsystem: Device 1002:439d
	Flags: bus master, 66MHz, medium devsel, latency 0

00:14.4 Class 0604: Device 1002:4384 (rev 40) (prog-if 01)
	Flags: bus master, VGA palette snoop, 66MHz, medium devsel, latency 64
	Bus: primary=00, secondary=03, subordinate=03, sec-latency=64

00:14.5 Class 0c03: Device 1002:4399 (prog-if 10)
	Subsystem: Device 1002:4399
	Flags: bus master, 66MHz, medium devsel, latency 32, IRQ 18
	Memory at feb4a000 (32-bit, non-prefetchable) [size=4K]
	Kernel driver in use: ohci_hcd

00:15.0 Class 0604: Device 1002:43a0
	Flags: bus master, fast devsel, latency 0
	Bus: primary=00, secondary=04, subordinate=06, sec-latency=0
	I/O behind bridge: 0000d000-0000dfff
	Memory behind bridge: fe000000-fe9fffff
	Prefetchable memory behind bridge: 00000000c0000000-00000000cfffffff
	Capabilities: [50] Power Management version 3
	Capabilities: [58] Express Root Port (Slot+), MSI 00
	Capabilities: [a0] MSI: Enable- Count=1/1 Maskable- 64bit+
	Capabilities: [b0] Subsystem: Device 1002:0000
	Capabilities: [b8] HyperTransport: MSI Mapping Enable+ Fixed+
	Capabilities: [100] Vendor Specific Information: ID=0001 Rev=1 Len=010 <?>
	Kernel driver in use: pcieport

00:16.0 Class 0c03: Device 1002:4397 (prog-if 10)
	Subsystem: Device 1002:4397
	Flags: bus master, 66MHz, medium devsel, latency 32, IRQ 18
	Memory at feb49000 (32-bit, non-prefetchable) [size=4K]
	Kernel driver in use: ohci_hcd

00:16.2 Class 0c03: Device 1002:4396 (prog-if 20)
	Subsystem: Device 1002:4396
	Flags: bus master, 66MHz, medium devsel, latency 32, IRQ 17
	Memory at feb48000 (32-bit, non-prefetchable) [size=256]
	Capabilities: [c0] Power Management version 2
	Capabilities: [e4] Debug port: BAR=1 offset=00e0
	Kernel driver in use: ehci-pci

00:18.0 Class 0600: Device 1022:1700 (rev 43)
	Flags: fast devsel

00:18.1 Class 0600: Device 1022:1701
	Flags: fast devsel

00:18.2 Class 0600: Device 1022:1702
	Flags: fast devsel

00:18.3 Class 0600: Device 1022:1703
	Flags: fast devsel
	Capabilities: [f0] Secure device <?>

00:18.4 Class 0600: Device 1022:1704
	Flags: fast devsel

00:18.5 Class 0600: Device 1022:1718
	Flags: fast devsel

00:18.6 Class 0600: Device 1022:1716
	Flags: fast devsel

00:18.7 Class 0600: Device 1022:1719
	Flags: fast devsel

02:00.0 Class 0200: Device 10ec:8168 (rev 06)
	Subsystem: Device 10ec:0123
	Flags: bus master, fast devsel, latency 0, IRQ 40
	I/O ports at e000 [size=256]
	Memory at fea00000 (64-bit, non-prefetchable) [size=4K]
	Memory at d0000000 (64-bit, prefetchable) [size=16K]
	Capabilities: [40] Power Management version 3
	Capabilities: [50] MSI: Enable+ Count=1/1 Maskable- 64bit+
	Capabilities: [70] Express Endpoint, MSI 01
	Capabilities: [b0] MSI-X: Enable- Count=4 Masked-
	Capabilities: [d0] Vital Product Data
	Capabilities: [100] Advanced Error Reporting
	Capabilities: [140] Virtual Channel
	Capabilities: [160] Device Serial Number a0-00-00-00-68-4c-e0-00
	Kernel driver in use: r8168

 

 

Edited by Polanskiman
updated spoiler plugin code
Link to post
Share on other sites
  • 1 month later...

Hello!

 

It is possible to integrate nVidia GeForce GT 730 driver to jun's 1.0b 3617xs loader? 

 

I would like to use this low TDP card for hardware transcoding with Enby Server. Thanks for the answer.

Link to post
Share on other sites
  • 2 weeks later...

Hello,

 

Im upgrading my xpenology build with new hardware/ My board is: https://www.asrock.com/MB/Intel/H370M-ITXac/index.asp#Specification ? It has 2 intel NICs. One  is a Giga PHY Intel I219V and one is a GigaLAN Intel I211AT.

 

I have tried jun's loader and also @IG-88's Custom extra.lzma ramdisk. However in both cases only one NIC comes online. Now i dont know if its the 1219V or the 1211AT. 

I have made sure my grub has mac and mac2 set. I also set the number of interfaces in grub to 2. So im assuming its a case of a missing driver?

Link to post
Share on other sites

So this might be a duplicate post that i posted in another thread but i think that was the wrong place to post.

my dsm 6.1.7
Jun's loader 1.0.2b

My board has two NICs. output of "lspci -k" in ubuntu shows modules for the two NICs are "e1000e" and "igb". Both of which i can find in the extra custom ram dis that i have inserted in jun's loader.
However, only the one using the "igb" module seems to be the functional one under xpenology. The other nic does get load/get a connection.  I'm also pasting my grub info below in case there is something wrong in there.

 

"lspci -k" out from ubuntu:

00:1f.6 Ethernet controller: Intel Corporation Ethernet Connection (7) I219-V (rev 10)
    Subsystem: ASRock Incorporation Ethernet Connection (7) I219-V
    Kernel driver in use: e1000e
    Kernel modules: e1000e
01:00.0 Ethernet controller: Intel Corporation I211 Gigabit Network Connection (rev 03)
    Subsystem: ASRock Incorporation I211 Gigabit Network Connection
    Kernel driver in use: igb
    Kernel modules: igb
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

The relevant extract from grub.cfg:  (i've hidden the last 5 digits of the mac below)

set mac1=7085c28XXXXb
set mac2=7085c28XXXX9
set rootdev=/dev/md0
set netif_num=2
set extra_args_3617=''

set common_args_3617='syno_hdd_powerup_seq=0 HddHotplug=0 syno_hw_version=DS3617xs vender_format_version=2 console=ttyS0,115200n8 withefi elevator=elevator quiet syno_port_thaw=1'

---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

The board also has a wifi adapter built in which also doesnt work, info below, Though i dont care about that really. Just providing info as FYI

 02:00.0 Network controller: Intel Corporation Device 24fb (rev 10)
    Subsystem: Intel Corporation Device 2110
    Kernel driver in use: iwlwifi
    Kernel modules: iwlwifi

Link to post
Share on other sites

im done some digging and i see that in @IG-88's custom extra ram disk, the intel e1000e driver version is 3.3.4. I have found that on the CD that came with my asrock h370m motherboard, they have provided the linux driver and it seems to be version 3.4.0.2. The src is in the package also. Im attaching that here.  Could that please me compiled for xpenology?

 

intel e1000e 3.4.0.2 driver LINUX.zip

Link to post
Share on other sites

not sure why it wont let me edit my post above. I wanted to add that currently "lsmod" shows the following related to network. I dont see e1000e being used by any module

 

Module            Size  Used by
igbvf                  31192  0 
igb                   175037  0 
dca                     4512  2 igb,ixgbe                <---- This is interesting. It says used by two. But only one of my NIC is functional.

e100                   28629  0 
e1000                  99699  0 
mii                     3763  11 ipg,jme,e100,asix,atl1,r8152,mcs7830,usbnet,pch_gbe,pcnet32,ax88179_178a
e1000e                169017  0 

Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.