kewag Posted February 18, 2020 Share #1 Posted February 18, 2020 (edited) Hi Using 1.03b 3615xs loader with onboard NIC and Intel NIC as pci-e. Grub.cfg has correct mac1 and 2. Interfaces set to 2. During boot and installazion both NICs get IP addresses. Installation is running using port1, the onboard NIC.. After installation is finished, everything is fine but the second ethernet port is gone. Onboad is Realtek. 2nd is Intel. Recreated the USB and the NAS successfully migrated again. But still no Intel Any ideas? Edited February 18, 2020 by kewag Quote Link to comment Share on other sites More sharing options...
luchuma Posted February 18, 2020 Share #2 Posted February 18, 2020 3 hours ago, kewag said: Any ideas? incompatible Intel NIC Quote Link to comment Share on other sites More sharing options...
bearcat Posted February 18, 2020 Share #3 Posted February 18, 2020 There is many different nic's based on intel, wich one do you try to use? Quote Link to comment Share on other sites More sharing options...
kewag Posted February 18, 2020 Author Share #4 Posted February 18, 2020 9 minutes ago, bearcat said: There is many different nic's based on intel, wich one do you try to use? 2 hours ago, luchuma said: incompatible Intel NIC It is the famous gigabit ct one.. 🤔 Quote Link to comment Share on other sites More sharing options...
luchuma Posted February 18, 2020 Share #5 Posted February 18, 2020 try to be more specific Quote Link to comment Share on other sites More sharing options...
kewag Posted February 18, 2020 Author Share #6 Posted February 18, 2020 Gigabit LAN PCI-E Express Intel 10/100/1000 CT Desktop Adapter EXPI9301CTBLK Quote Link to comment Share on other sites More sharing options...
kewag Posted February 18, 2020 Author Share #7 Posted February 18, 2020 2 hours ago, luchuma said: try to be more specific Gigabit LAN PCI-E Express Intel 10/100/1000 CT Desktop Adapter EXPI9301CTBLK Quote Link to comment Share on other sites More sharing options...
luchuma Posted February 18, 2020 Share #8 Posted February 18, 2020 no idea. this nic should be supported as e1000e driver Quote Link to comment Share on other sites More sharing options...
IG-88 Posted February 18, 2020 Share #9 Posted February 18, 2020 11 hours ago, kewag said: During boot and installazion both NICs get IP addresses. Installation is running using port1, the onboard NIC.. After installation is finished, everything is fine but the second ethernet port is gone. my guess would be you use jun's unmodded loader and the laode starts the kernel from dsm 6.2.0 and the drivers are for that version (found before installing), when installing people usually end up using the latest and thats 6.2.2, it this case the drivers don't match anymore and lots of them will not load as of changes synology made to the 6.2.2 kernel you can try this theory when installing "DSM_DS3615xs_23739.pat" (aka 6.2.0) without updting to 6.2.2, it should have both nic's after installing/running 6.2.0 to correct it you can use the 6.2.2 drivers from here https://xpenology.com/forum/topic/21663-driver-extension-jun-103b104b-for-dsm622-for-3615xs-3617xs-918/ Quote Link to comment Share on other sites More sharing options...
kewag Posted February 18, 2020 Author Share #10 Posted February 18, 2020 29 minutes ago, IG-88 said: my guess would be you use jun's unmodded loader and the laode starts the kernel from dsm 6.2.0 and the drivers are for that version (found before installing), when installing people usually end up using the latest and thats 6.2.2, it this case the drivers don't match anymore and lots of them will not load as of changes synology made to the 6.2.2 kernel you can try this theory when installing "DSM_DS3615xs_23739.pat" (aka 6.2.0) without updting to 6.2.2, it should have both nic's after installing/running 6.2.0 to correct it you can use the 6.2.2 drivers from here https://xpenology.com/forum/topic/21663-driver-extension-jun-103b104b-for-dsm622-for-3615xs-3617xs-918/ It is as you said. I updated quickly and didn't check before if 2 ethernet ports were there with the old version. Will give 6.2.2 drivers a try. Thanks Quote Link to comment Share on other sites More sharing options...
flyride Posted February 18, 2020 Share #11 Posted February 18, 2020 Intel CT and e1000e driver on 6.2.2 usually works. It's possible that there now is a CT silicon release that is not supported by the current driver. OP can you post the PCI device ID and related info of the card in question? lspci -k Quote Link to comment Share on other sites More sharing options...
kewag Posted February 18, 2020 Author Share #12 Posted February 18, 2020 (edited) *deleted double post* Edited February 18, 2020 by kewag Quote Link to comment Share on other sites More sharing options...
kewag Posted February 18, 2020 Author Share #13 Posted February 18, 2020 1 minute ago, kewag said: root@NAS:/dev# lspci -k 0000:00:00.0 Class 0600: Device 8086:0100 (rev 09) Subsystem: Device 1043:844d 0000:00:01.0 Class 0604: Device 8086:0101 (rev 09) Kernel driver in use: pcieport 0000:00:02.0 Class 0300: Device 8086:0102 (rev 09) Subsystem: Device 1043:844d 0000:00:16.0 Class 0780: Device 8086:1c3a (rev 04) Subsystem: Device 1043:844d 0000:00:1a.0 Class 0c03: Device 8086:1c2d (rev 05) Subsystem: Device 1043:844d Kernel driver in use: ehci-pci 0000:00:1b.0 Class 0403: Device 8086:1c20 (rev 05) Subsystem: Device 1043:8444 0000:00:1c.0 Class 0604: Device 8086:1c10 (rev b5) Kernel driver in use: pcieport 0000:00:1c.2 Class 0604: Device 8086:1c14 (rev b5) Kernel driver in use: pcieport 0000:00:1c.3 Class 0604: Device 8086:1c16 (rev b5) Kernel driver in use: pcieport 0000:00:1c.5 Class 0604: Device 8086:1c1a (rev b5) Kernel driver in use: pcieport 0000:00:1c.6 Class 0604: Device 8086:1c1c (rev b5) Kernel driver in use: pcieport 0000:00:1c.7 Class 0604: Device 8086:244e (rev b5) 0000:00:1d.0 Class 0c03: Device 8086:1c26 (rev 05) Subsystem: Device 1043:844d Kernel driver in use: ehci-pci 0000:00:1f.0 Class 0601: Device 8086:1c44 (rev 05) Subsystem: Device 1043:844d Kernel driver in use: lpc_ich 0000:00:1f.2 Class 0106: Device 8086:1c02 (rev 05) Subsystem: Device 1043:844d Kernel driver in use: ahci 0000:00:1f.3 Class 0c05: Device 8086:1c22 (rev 05) Subsystem: Device 1043:844d 0000:01:00.0 Class 0106: Device 1b4b:9215 (rev 11) Subsystem: Device 1b4b:9215 Kernel driver in use: ahci 0000:03:00.0 Class 0200: Device 8086:10d3 Subsystem: Device 8086:a01f Kernel driver in use: e1000e 0000:04:00.0 Class 0106: Device 1b4b:9215 (rev 11) Subsystem: Device 1b4b:9215 Kernel driver in use: ahci 0000:05:00.0 Class 0c03: Device 1b21:1042 Subsystem: Device 1043:8488 Kernel driver in use: xhci_hcd 0000:06:00.0 Class 0200: Device 10ec:8168 (rev 06) Subsystem: Device 1043:8432 0000:07:00.0 Class 0604: Device 1b21:1080 (rev 01) 0000:08:00.0 Class 0104: Device 1095:3114 (rev 02) Subsystem: Device 1095:7114 0001:07:00.0 Class 0000: Device 1b4b:9235 (rev ff) 0001:08:00.0 Class 0000: Device 1b4b:9235 (rev ff) 0001:09:00.0 Class 0000: Device 1b4b:9235 (rev ff) 0001:0a:00.0 Class 0000: Device 1b4b:9235 (rev ff) 4 minutes ago, flyride said: Intel CT and e1000e driver on 6.2.2 usually works. It's possible that there now is a CT silicon release that is not supported by the current driver. OP can you post the PCI device ID and related info of the card in question? lspci -k Quote Link to comment Share on other sites More sharing options...
flyride Posted February 18, 2020 Share #14 Posted February 18, 2020 (edited) So your CT card is supported by the e1000e driver and is recognized: 0000:03:00.0 Class 0200: Device 8086:10d3 Subsystem: Device 8086:a01f Kernel driver in use: e1000e Something else is going on. Does dmesg show anything regarding the card? Also are you sure it's the Intel that is not being recognized and not Realtek? What motherboard? Edited February 18, 2020 by flyride Quote Link to comment Share on other sites More sharing options...
kewag Posted February 18, 2020 Author Share #15 Posted February 18, 2020 (edited) 15 minutes ago, flyride said: So your CT card is supported by the e1000e driver and is recognized: 0000:03:00.0 Class 0200: Device 8086:10d3 Subsystem: Device 8086:a01f Kernel driver in use: e1000e Something else is going on. Does dmesg show anything regarding the card? Also are you sure it's the Intel that is not being recognized and not Realtek? What motherboard? Not sure if I'm using dmesg correctly but weird output for eth0. [ 17.499125] e1000e 0000:03:00.0 eth0: registered PHC clock [ 17.499128] e1000e 0000:03:00.0 eth0: (PCI Express:2.5GT/s:Width x1) 68:05:ca :0b:50:3a [ 17.499129] e1000e 0000:03:00.0 eth0: Intel(R) PRO/1000 Network Connection [ 17.499142] e1000e 0000:03:00.0 eth0: MAC: 3, PHY: 8, PBA No: E46981-007 [ 18.944322] device eth0 entered promiscuous mode [ 18.945217] device ovs_eth0 entered promiscuous mode [ 20.033999] device eth0 left promiscuous mode [ 20.034039] device ovs_eth0 left promiscuous mode [ 20.051500] device ovs_eth0 entered promiscuous mode [ 20.240316] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready [ 20.243519] device eth0 entered promiscuous mode [ 22.803122] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx [ 22.803447] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready The MAC is the one from the onboard Realtek on an ASUS ASUS P8z68-V LX Uh? Maybe I mixed it up and the Realtek isnt working Edited February 18, 2020 by kewag Quote Link to comment Share on other sites More sharing options...
kewag Posted February 18, 2020 Author Share #16 Posted February 18, 2020 Just checked the MAC. Belongs to ASUStek Quote Link to comment Share on other sites More sharing options...
luchuma Posted February 18, 2020 Share #17 Posted February 18, 2020 id rather say that realtek is not working eth0 - mac1 (maybe here is mac from realtek but this is intel card) eth1 - mac2 check grub cfg Quote Link to comment Share on other sites More sharing options...
kewag Posted February 18, 2020 Author Share #18 Posted February 18, 2020 (edited) 4 minutes ago, luchuma said: id rather say that realtek is not working eth0 - mac1 (maybe here is mac from realtek but this is intel card) eth1 - mac2 check grub cfg Do you mean I should swap it? This is how it is set up right now: set mac1=5404A6BF1E9B set mac2=6805CA0B503A Edited February 18, 2020 by kewag Quote Link to comment Share on other sites More sharing options...
luchuma Posted February 18, 2020 Share #19 Posted February 18, 2020 well, easiest way to check it is to take out cable from intel nic ;] Quote Link to comment Share on other sites More sharing options...
kewag Posted February 18, 2020 Author Share #20 Posted February 18, 2020 25 minutes ago, luchuma said: well, easiest way to check it is to take out cable from intel nic ;] Yes... It is the Intel. The Realtek isnt working. So, I deactivated the onboard and plugged in another Intel CT. But this one is a PCI-Version. Same 1GB chip. Do I have to rebuild the stick and do the migrate? A simple reboot didn't work. Quote Link to comment Share on other sites More sharing options...
kewag Posted February 18, 2020 Author Share #21 Posted February 18, 2020 Damn. The PCI card caused the PC not to shutdown /reboot.... Removed it again. Can live with 1 ethernet port for now Thanks everybody for helping out Quote Link to comment Share on other sites More sharing options...
flyride Posted February 18, 2020 Share #22 Posted February 18, 2020 @IG-88's extra.lzma may make your Realtek work again. Quote Link to comment Share on other sites More sharing options...
kewag Posted February 19, 2020 Author Share #23 Posted February 19, 2020 10 hours ago, IG-88 said: my guess would be you use jun's unmodded loader and the laode starts the kernel from dsm 6.2.0 and the drivers are for that version (found before installing), when installing people usually end up using the latest and thats 6.2.2, it this case the drivers don't match anymore and lots of them will not load as of changes synology made to the 6.2.2 kernel you can try this theory when installing "DSM_DS3615xs_23739.pat" (aka 6.2.0) without updting to 6.2.2, it should have both nic's after installing/running 6.2.0 to correct it you can use the 6.2.2 drivers from here https://xpenology.com/forum/topic/21663-driver-extension-jun-103b104b-for-dsm622-for-3615xs-3617xs-918/ Couldnt sleep, so I 6.2.2 drivers.... and guess what............. :)))))))) The Realtek is working. Two Ethernetports up and running. Thank you ! Can sleep again. 1 Quote Link to comment Share on other sites More sharing options...
bearcat Posted February 19, 2020 Share #24 Posted February 19, 2020 @kewag I'm glad to see you worked it out, and finally can get some sleep It's known to happen, that sometimes an addon-card will become eth0 (linux) = MAC1 (grub.cfg) = LAN1 (DSM), and that can be very confusing 😕 Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.