MSI H410I PRO WIFI & I3 10100, Intel® I219V Gigabit LAN


Recommended Posts

Hi, would like to ask for some help regarding the installation of DSM for MSI H410I PRO WIFI & I3 10100.

I was using DSM 6.1 previously and it crash so i upgraded to the above hardware.

I'm having issue detecting the hardware, unable to find synology using synology assistance.

 

I have follow the guide and change the VID (USB Drive), SID(USB Drive), Sn(USB Drive) and mac address(motherboard NIC).

Is there anything that i miss out. I have also try to replacing the extra.lzma/extra2.lzma from below thread.

Anyone can point me to the correct direction?

Many thanks.

 

 

Link to post
Share on other sites

 

8 hours ago, Benedict said:

MSI H410I PRO WIFI & I3 10100.

I was using DSM 6.1 previously and it crash so i upgraded to the above hardware.

I'm having issue detecting the hardware, unable to find synology using synology assistance.

 

you did not specify what loader and dsm type you where using, the hardware is capable of 918+ but not all people choose that

8 hours ago, Benedict said:

Sn(USB Drive)

no thats supposed to be the SN of the synology product, but a valid sn is only needed for same special things and there are ways around that too, just keep the original sn and mod the last 4 digits (avoids possible blacklisting from synology)

 

8 hours ago, Benedict said:

I'm having issue detecting the hardware,

imho to early for that conclusion, depends on what dsm type you tried

if you used 3615/17 loader 1.03b then you would need to use csm mode and the legacy (non-uefi) usb boot device

 

if possible boot a rescue linux and check the pci vid/pid of the i219 nic with lspci

thats the device list for the i219 you can use with the drivers you can download atm

https://xpenology.com/forum/topic/37536-hi-guys-any-driver-for-intel%C2%AE-i219v/?tab=comments#comment-180769

 

also you are linking to a old driver thread for dsm 6.2.2, if you combine these drivers with dsm 6.2.3 its not going to work, you need extra drivers for 6.2.3

https://xpenology.com/forum/topic/28321-driver-extension-jun-103b104b-for-dsm623-for-918-3615xs-3617xs/

(if you let it download dsm over internet its going to be 6.2.3 (25426)

 

Link to post
Share on other sites

Hi IG-88,

 

Thanks for your reply.

I'm using 1.04b ds918+ loader.

I have used OSFmount to change the VIP,PID and MAC on the grub file. Kept the sno as default.

Copied extra.lzma/extra2.lzma for loader 1.04b ds918+ DSM 6.2.3 v0.13.3 and burn it to USB.

I also tried to copy the zImage and rd.gz from "DSM_DS918+_25426.pat

I'm still unable to detect xpenology.

 

Is it due to my NIC is not supported?

I'm trying to get my pci vid/pid now.

 

Any advise?

Link to post
Share on other sites
4 hours ago, Benedict said:

Is it due to my NIC is not supported?

 

might be the case, 918+ does work in uefi and csm mode so it should not be a boot problem

 

4 hours ago, Benedict said:

I'm trying to get my pci vid/pid now.

that would be the way to know for sure (beside using a serial port on the system and monitor the boot process with a null-modem-cable on a serial console)

 

4 hours ago, Benedict said:

Any advise?

use a added nic that works in a pcie slot until i have the new extra/extra2 with the newer intel drivers that would support newer i219

Link to post
Share on other sites

Hi IG-88,

 

I have the output for ispci. I used Truenas shell to get the output thou.

is my NIC supported?


root@truenas[~]# lspci
00:00.0 Class 0600: Device 8086:9b63 (rev 03)
00:02.0 Class 0300: Device 8086:9bc8 (rev 03)
00:08.0 Class 0880: Device 8086:1911
00:14.0 Class 0c03: Device 8086:a3af
00:14.2 Class 1180: Device 8086:a3b1
00:16.0 Class 0780: Device 8086:a3ba
00:17.0 Class 0106: Device 8086:a382
00:1d.0 Class 0604: Device 8086:a398 (rev f0)
00:1d.2 Class 0604: Device 8086:a39a (rev f0)
00:1f.0 Class 0601: Device 8086:a3da

Link to post
Share on other sites
On 12/13/2020 at 5:28 AM, Benedict said:

root@truenas[~]# lspci

that list should be longer, like this

(and yes class 0200 would be network, in this example a realtek 8168/8111 and a dualport 10G broadcom nic)

 

0000:00:00.0 Class 0600: Device 8086:3e1f (rev 08)
0000:00:01.0 Class 0604: Device 8086:1901 (rev 08)
0000:00:02.0 Class 0300: Device 8086:3e91
0000:00:08.0 Class 0880: Device 8086:1911
0000:00:14.0 Class 0c03: Device 8086:a2af
0000:00:16.0 Class 0780: Device 8086:a2ba
0000:00:17.0 Class 0106: Device 8086:a282
0000:00:1b.0 Class 0604: Device 8086:a2e9 (rev f0)
0000:00:1b.3 Class 0604: Device 8086:a2ea (rev f0)
0000:00:1b.4 Class 0604: Device 8086:a2eb (rev f0)
0000:00:1c.0 Class 0604: Device 8086:a292 (rev f0)
0000:00:1c.3 Class 0604: Device 8086:a293 (rev f0)
0000:00:1c.4 Class 0604: Device 8086:a294 (rev f0)
0000:00:1c.5 Class 0604: Device 8086:a295 (rev f0)
0000:00:1c.6 Class 0604: Device 8086:a296 (rev f0)
0000:00:1c.7 Class 0604: Device 8086:a297 (rev f0)
0000:00:1d.0 Class 0604: Device 8086:a298 (rev f0)
0000:00:1f.0 Class 0601: Device 8086:a2cc
0000:00:1f.2 Class 0580: Device 8086:a2a1
0000:00:1f.3 Class 0403: Device 8086:a2f0
0000:00:1f.4 Class 0c05: Device 8086:a2a3
0000:01:00.0 Class 0106: Device 197b:0585
0000:04:00.0 Class 0200: Device 14e4:16a1 (rev 11)
0000:04:00.1 Class 0200: Device 14e4:16a1 (rev 11)
0000:07:00.0 Class 0200: Device 10ec:8168 (rev 16)
0000:0a:00.0 Class 0106: Device 1b4b:9215 (rev 11)
0001:00:02.0 Class 0000: Device 8086:6f04 (rev ff)
0001:00:02.2 Class 0000: Device 8086:6f06 (rev ff)
0001:00:03.0 Class 0000: Device 8086:6f08 (rev ff)
0001:00:03.2 Class 0000: Device 8086:6f0a (rev ff)
0001:00:1f.0 Class 0000: Device 8086:8c54 (rev ff)
0001:00:1f.3 Class 0000: Device 8086:8c22 (rev ff)
0001:06:00.0 Class 0000: Device 1b4b:1475 (rev ff)
0001:08:00.0 Class 0000: Device 1b4b:9235 (rev ff)
0001:09:00.0 Class 0000: Device 8086:1533 (rev ff)
0001:0c:00.0 Class 0000: Device 8086:1533 (rev ff)
0001:0d:00.0 Class 0000: Device 8086:1533 (rev ff)

 

Link to post
Share on other sites
15 hours ago, Benedict said:

00:1f.6 Class 0200: Device 8086:0d55

i edited my old post , about already supported i219, looks like i forgot to copy a block with lower id's used for i219

https://xpenology.com/forum/topic/37536-hi-guys-any-driver-for-intel®-i219v/?do=findComment&comment=180769

 

so the drivers we use should support the i219 on your systemboard

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

Hi guys,

 

Not sure which part that i did wrong or miss out, I'm unable to detect my synology after it boot to Jun's loader.

 

Here are the steps that i perform, any help will be deeply appreciated.

Used Jun's loader - v1.04b (DS918+)

Replaced grub.cfg VID (USB), PID (USB), S.no.(No change), MAC (Systemboard MAC)

Replaced the following extra.lzma/extra2.lzma from extra.lzma/extra2.lzma for loader 1.04b ds918+ DSM 6.2.3 v0.13.3

Replaced the following zImage and rd.gz from "DSM_DS918+_25426.pat"

Write to thumbdrive.

 

I manage to boot to Jun's loader screen.

After awhile, the NIC port no more connectivity. Unable to scan my synology from synology assistance.

 

 

 

Link to post
Share on other sites
On 12/20/2020 at 2:44 AM, Benedict said:

Any help on the installation steps?

Do I need to format the data disk before the installation?

maybe just try loader 1.04b as it comes without any changes or newer extra.lzma

the basic boot and network operations are working without any changes, the usb vid/pid would only be important when trying to install dsm to a disk but atm you are failing even the 1st step of finding it in network, if you get this part working then you can start things like  usb vid/pid and mac an grub.cfg

beside synology assistant you can check your dhcp server for activity aka new addresses

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.