Servman

TP-Link PCI Network-Card not seen

Recommended Posts

Hi All,

 

I'm new to Xpenology and DSM-6.1.

 

I have a Network card issue i have a TP-Link Model No: TG-3468 PCI-Express, and DSM-6.1 dose not see the card, i have added the MAC address to the 1.02b-Loader- synoboot.img as per the instruction.

 

Hardware Spec:

AMD Phenom II

8Gig ram

 

i was just hoping for some help in getting the card working as i would like a Bonded network.

 

I'm using  DS3615xs.

 

Regards

Share this post


Link to post
Share on other sites

it has a realtek 8168/8111 chip so it should work with jun's 10.2b loader ootb, you can also try my extra.lzma, it contains a newer version of the realtek driver

if your system is already running with a different card, whats in the log about the 2nd card (var/log/dmesg)

 

Share this post


Link to post
Share on other sites

Hi @IG-88

 

Thank you for your reply, is there any chance you could provide the link to the extra.lzma file or post? or point me in the right direction. 

 

i will have a look at the logs tonight and post the output.

Share this post


Link to post
Share on other sites

@IG-88 i have found the post regarding the extra.lzma, i will try the extra.lzma for ds3615 v4.7 and let you know as well.

Share this post


Link to post
Share on other sites
...
[Wed Apr  4 19:51:51 2018] r8168 Gigabit Ethernet driver 8.044.02-NAPI loaded
[Wed Apr  4 19:51:51 2018] r8168 0000:02:00.0: irq 42 for MSI/MSI-X
[Wed Apr  4 19:51:51 2018] r8168: This product is covered by one or more of the following patents: US6,570,884, US6,115,776, and US6,327,625.
[Wed Apr  4 19:51:51 2018] r8168  Copyright (C) 2017  Realtek NIC software team <nicfae@realtek.com> 
                            This program comes with ABSOLUTELY NO WARRANTY; for details, please see <http://www.gnu.org/licenses/>. 
                            This is free software, and you are welcome to redistribute it under certain conditions; see <http://www.gnu.org/licenses/>. 
[Wed Apr  4 19:51:51 2018] qed_init called
  ...
[Wed Apr  4 19:51:53 2018] eth0: 0xffffc9001106a000, 20:cf:30:52:8b:0e, IRQ 42
[Wed Apr  4 19:51:53 2018] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
  ...
[Wed Apr  4 19:51:56 2018] r8168: eth0: link up
[Wed Apr  4 19:51:56 2018] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready  
  ...
    

technically for the driver it works, the driver detects a hardware  and does not crash but its still jun's driver not the one from the extra.lzma that is loaded the one in my extra.lzma i version "8.045.08-NAPI"

 

On 4/3/2018 at 3:01 AM, Servman said:

i was just hoping for some help in getting the card working as i would like a Bonded network.

 

i cant see any 2nd nic, just the realtek and it seem to load and get ready as eth0 as it would be the only one

whats the other nic? anobard? what systemboard?

i'd guess the 2nd is nvidia chipset based and jun's loader does not contain nvidia forcedeth.ko driver so only the additional card is working

the fact that the log is about jun's realtek driver (older version) indicates that my extra.lzma is not used oder properly installed as it is not loaded, my extra.lzma also contains a driver for nvidia so if it's loaded i guess both nic's will be seen

 

simple method to test, disconnect disks, remove realtek card, boot from usb flash drive if the nvidia driver works the synology assistant should find something, if not check installation of extra.lzma on flash drive

 

 

 

Share this post


Link to post
Share on other sites

Hi @IG-88

 

I was only able to get the log last nigh ti have not change over to you new driver pack i hope to do that tonight.

 

the motherboard is an Asus M4A78LT-M LE

 

once updated i will provide the logs again, hope that will fix my issue.

 

And thank you in advance for all your help.

Share this post


Link to post
Share on other sites
Posted (edited)

from the picture in the manual there is a ar8131, that would be atl1c.ko and that one is already part of juns lloader, so in theory it should work for both nic's ootb

on closer look

atl1c 0000:03:00.0: version 1.0.1.1-NAPI

so it looks like the qualcom/atheros driver is loaded (finds hardware) but des not get a ethX asigned

did you change set netif_num=2 in grub.cfg

Edited by IG-88

Share this post


Link to post
Share on other sites
Posted (edited)

i would think so as well but i will try your drive pack anyway and see what happens i will let you know how i go.

 

form what i can tell the Asus network card is work  and seen in DSM and i'm pretty sure that the TP-link card is the one that is not seen in DSM, as it all work when i was using FreeNas. so not sure.

Edited by Servman

Share this post


Link to post
Share on other sites
Posted (edited)

i was asuming that the realtek would be working as the driver is asigned irq 42 and the eth0 says its using irq 42

also

r8168: eth0: link up

 

Edited by IG-88

Share this post


Link to post
Share on other sites

i think i will try your drive pack and i will disconnected one cable at a atime and see if the Syno finder see the DMS an let you know for sure, which one is having the issue. 

Share this post


Link to post
Share on other sites

my experiences if you don't assign new mac address in loader link never up. (led status on card & hub display ok)

for usb wireless don't need to assign mac address.

 

Share this post


Link to post
Share on other sites
13 minutes ago, rungkit said:

my experiences if you don't assign new mac address in loader link never up. (led status on card & hub display ok)

for usb wireless don't need to assign mac address.

 

 

Hi@rungkit

 

i have made sure i added the MAC to the boot loader and i checked it twice, and the card lights up.

Share this post


Link to post
Share on other sites
5 hours ago, IG-88 said:

from the picture in the manual there is a ar8131, that would be atl1c.ko and that one is already part of juns lloader, so in theory it should work for both nic's ootb

on closer look


atl1c 0000:03:00.0: version 1.0.1.1-NAPI

 

 

That module seems is posing problems. The module is not necessarily crashing but seems to indicate there is a bug somewhere in the module.

------------[ cut here ]------------
[Wed Apr  4 19:51:54 2018] WARNING: at kernel/irq/manage.c:1244 __free_irq+0xa7/0x200()
[Wed Apr  4 19:51:54 2018] Trying to free already-free IRQ 18
[Wed Apr  4 19:51:54 2018] Modules linked in: bromolow_synobios(PO) button ax88179_178a usbnet tg3 r8169 cnic bnx2 vmxnet3 pcnet32 e1000 sfc netxen_nic qlge qlcnic qla3xxx pch_gbe ptp_pch sky2 skge jme ipg uio alx atl1c atl1e atl1 libphy mii exfat(O) btrfs synoacl_vfs(PO) zlib_deflate hfsplus md4 hmac bnx2x(O) libcrc32c mdio mlx5_core(O) mlx4_en(O) mlx4_core(O) mlx_compat(O) compat(O) qede(O) qed(O) atlantic(O) r8168(O) tn40xx(O) i40e(O) ixgbe(O) be2net(O) igb(O) i2c_algo_bit e1000e(O) dca fuse vfat fat glue_helper lrw gf128mul ablk_helper sha512_generic arc4 cryptd ecryptfs sha256_generic sha1_generic ecb aes_x86_64 authenc des_generic ansi_cprng cts md5 cbc cpufreq_conservative cpufreq_powersave cpufreq_performance cpufreq_ondemand acpi_cpufreq mperf processor thermal_sys cpufreq_stats freq_table dm_snapshot
[Wed Apr  4 19:51:54 2018]  crc_itu_t crc_ccitt quota_v2 quota_tree psnap p8022 llc sit tunnel4 ip_tunnel ipv6 zram(C) sg etxhci_hcd mpt3sas 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 el000(O) [last unloaded: bromolow_synobios]
[Wed Apr  4 19:51:54 2018] CPU: 0 PID: 8840 Comm: ifconfig Tainted: P        WC O 3.10.102 #15266
[Wed Apr  4 19:51:54 2018] Hardware name: System manufacturer System Product Name/M4A78LT-M-LE, BIOS 0704    06/11/2010
[Wed Apr  4 19:51:54 2018]  ffffffff814a9ec3 ffffffff81032ee6 0000000000000000 ffff8800c74b3cf8
[Wed Apr  4 19:51:54 2018]  ffff8800caa4da80 0000000000000012 ffff8800caa4db0c ffffffff81032f47
[Wed Apr  4 19:51:54 2018]  ffffffff816f5e60 ffff880000000020 ffff8800c74b3d08 ffff8800c74b3cc8
[Wed Apr  4 19:51:54 2018] Call Trace:
[Wed Apr  4 19:51:54 2018]  [<ffffffff814a9ec3>] ? dump_stack+0xc/0x15
[Wed Apr  4 19:51:54 2018]  [<ffffffff81032ee6>] ? warn_slowpath_common+0x56/0x70
[Wed Apr  4 19:51:54 2018]  [<ffffffff81032f47>] ? warn_slowpath_fmt+0x47/0x50
[Wed Apr  4 19:51:54 2018]  [<ffffffffa0aacc25>] ? atl1c_alloc_rx_buffer+0x385/0x410 [atl1c]
[Wed Apr  4 19:51:54 2018]  [<ffffffff8109c837>] ? __free_irq+0xa7/0x200
[Wed Apr  4 19:51:54 2018]  [<ffffffff8109ca0f>] ? free_irq+0x2f/0xa0
[Wed Apr  4 19:51:54 2018]  [<ffffffffa0aadddc>] ? atl1c_up+0x9c/0x190 [atl1c]
[Wed Apr  4 19:51:54 2018]  [<ffffffffa0aab396>] ? atl1c_free_irq+0x16/0x40 [atl1c]
[Wed Apr  4 19:51:54 2018]  [<ffffffffa0aae458>] ? atl1c_open+0x288/0x2e0 [atl1c]
[Wed Apr  4 19:51:54 2018]  [<ffffffff813ef92e>] ? __dev_open+0x7e/0xe0
[Wed Apr  4 19:51:54 2018]  [<ffffffff813efb81>] ? __dev_change_flags+0x91/0x140
[Wed Apr  4 19:51:54 2018]  [<ffffffff813efcb2>] ? dev_change_flags+0x12/0x50
[Wed Apr  4 19:51:54 2018]  [<ffffffff8144a12c>] ? devinet_ioctl+0x5fc/0x6c0
[Wed Apr  4 19:51:54 2018]  [<ffffffff810296e8>] ? __do_page_fault+0x1b8/0x480
[Wed Apr  4 19:51:54 2018]  [<ffffffff813d599b>] ? sock_do_ioctl+0x1b/0x50
[Wed Apr  4 19:51:54 2018]  [<ffffffff813d5dc8>] ? sock_ioctl+0x1d8/0x2a0
[Wed Apr  4 19:51:54 2018]  [<ffffffff8110d0fe>] ? do_vfs_ioctl+0x20e/0x880
[Wed Apr  4 19:51:54 2018]  [<ffffffff81238f86>] ? apparmor_cred_prepare+0x26/0x40
[Wed Apr  4 19:51:54 2018]  [<ffffffff810f3417>] ? SyS_faccessat+0x197/0x2c0
[Wed Apr  4 19:51:54 2018]  [<ffffffff8110d7f0>] ? SyS_ioctl+0x80/0xa0
[Wed Apr  4 19:51:54 2018]  [<ffffffff814afeb2>] ? system_call_fastpath+0x16/0x1b
[Wed Apr  4 19:51:54 2018] ---[ end trace 14fdad943159d686 ]---

 

Share this post


Link to post
Share on other sites
Posted (edited)
12 hours ago, Polanskiman said:

That module seems is posing problems. The module is not necessarily crashing but seems to indicate there is a bug somewhere in the module.

 

the only thing i could make out was irq 18 and that one was used by usb

but on 3rd look, yeah there are references to ifconfig and atl1c in this one

the hardware in question seem pretty dated so the fact that kernel 3.10.102 isnt recent should not be a problem

 

in my extra.lzma is a different one (new compiled, no new version, compared to jun's) of that module

good thing to have a change log:

[09.12.2017] uploaded v4.2 for all versions
...
- replaced alt1c.ko in all three ramdisks with fresh compiled ones from 15152 as i got feedback that this modules where not working in jun's version 
...

 

at least it woth a try with my extra.lzma, in the driver thread there was someone in feb. 2018 who used that module successfully so its not broken in general in my extra.lzma

 

so its defiantly a good idea to use my extra.lzma in this case

 

Edited by IG-88

Share this post


Link to post
Share on other sites

Hi @IG-88

 

I had applyed your extra.lzma and it has fixed the issue, looks like it was a driver issue .

 

Thank you fo all your help.

Share this post


Link to post
Share on other sites
Hi [mention=36953]IG-88[/mention]
 
I had applyed your extra.lzma and it has fixed the issue, looks like it was a driver issue .
 
Thank you fo all your help.


Can you please post dmesg log now that it is working?


Sent from my iPhone using Tapatalk

Share this post


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

Hi @Polanskiman

 

please see the new log attached.

dmesg

 

14 hours ago, IG-88 said:

 

the only thing i could make out was irq 18 and that one was used by usb

but on 3rd look, yeah there are references to ifconfig and atl1c in this one

the hardware in question seem pretty dated so the fact that kernel 3.10.102 isnt recent should not be a problem

 

in my extra.lzma is a different one (new compiled, no new version, compared to jun's) of that module

good thing to have a change log:


[09.12.2017] uploaded v4.2 for all versions
...
- replaced alt1c.ko in all three ramdisks with fresh compiled ones from 15152 as i got feedback that this modules where not working in jun's version 
...

 

at least it woth a try with my extra.lzma, in the driver thread there was someone in feb. 2018 who used that module successfully so its not broken in general in my extra.lzma

 

so its defiantly a good idea to use my extra.lzma in this case

 

 

That atl1c was the problem. Your compiled version of the module fixed it.

atl1c 0000:03:00.0: atl1c: eth1 NIC Link is Up<1000 Mbps Full Duplex>

Now you see the value of a change log ;)

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now