| View previous topic :: View next topic |
| Author |
Message |
devsk
Advocate
Joined: 24 Oct 2003
Posts: 3003
Location: Bay Area, CA
|
 Posted: Thu Aug 31, 2017 5:48 am Post subject: Issue with tg3 module load with kernel 4.12.x |
 |
|
I have this problem with the tg3 driver with this kernel. My work network has 802.1x encryption even for the wired connection. It seems like tg3 module loads but does not create the 'eth0' when I connect to the port at office. I do the same thing at home with my wired network and the module creates 'eth0' device and wicd can connect to it.
The weird thing is that if I reboot into MacOS, I can connect to the same wired port and get a connection after authorizing with my work credentials.
Has anybody seen this kind of issue with their wired connection of the laptop? |
|
| Back to top |
|
 |
charles17
Advocate
Joined: 02 Mar 2008
Posts: 3685
|
| Posted: Thu Aug 31, 2017 7:27 am Post subject: |
|
|
| Not sure, but maybe bug 623014? |
|
| Back to top |
|
|
devsk
Advocate
Joined: 24 Oct 2003
Posts: 3003
Location: Bay Area, CA
|
| Posted: Thu Aug 31, 2017 3:58 pm Post subject: |
|
|
| No, that's different. The problem for me is that when I am connected to the corporate network using wired connection, the tg3 module loads but does not create 'eth0'. 'ifconfig -a' does not even show eth0. Forget about network manager or wicd, it does not reach that level. At home, the eth0 shows up and wicd can work with it fine (irrespective of whether a wifi driver/connection is there or not). |
|
| Back to top |
|
|
charles17
Advocate
Joined: 02 Mar 2008
Posts: 3685
|
| Posted: Thu Aug 31, 2017 6:12 pm Post subject: |
|
|
Here, the tg3 comes up even when unplugged (laptop, mostly on wlan): | grep -E 'tg3|02:0e.0|eth0' /var/log/kern.log: | Aug 31 16:45:50 kernel: pci 0000:02:0e.0: [14e4:169c] type 00 class 0x020000
Aug 31 16:45:50 kernel: pci 0000:02:0e.0: reg 0x10: [mem 0xe8110000-0xe811ffff]
Aug 31 16:45:50 kernel: pci 0000:02:0e.0: PME# supported from D3hot D3cold
Aug 31 16:45:50 kernel: tg3.c:v3.137 (May 11, 2014)
Aug 31 16:45:50 kernel: tg3 0000:02:0e.0 eth0: Tigon3 [partno(BCM95788A50) rev 3003] (PCI:33MHz:32-bit) MAC address aa:bb:cc:dd:ee:ff
Aug 31 16:45:50 kernel: tg3 0000:02:0e.0 eth0: attached PHY is 5705 (10/100/1000Base-T Ethernet) (WireSpeed[0], EEE[0])
Aug 31 16:45:50 kernel: tg3 0000:02:0e.0 eth0: RXcsums[1] LinkChgREG[0] MIirq[0] ASF[0] TSOcap[1]
Aug 31 16:45:50 kernel: tg3 0000:02:0e.0 eth0: dma_rwctrl[763f0000] dma_mask[32-bit]
Aug 31 16:45:51 kernel: IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready |
What are you having in the logs and dmesg? |
|
| Back to top |
|
|
devsk
Advocate
Joined: 24 Oct 2003
Posts: 3003
Location: Bay Area, CA
|
| Posted: Thu Aug 31, 2017 7:00 pm Post subject: |
|
|
| charles17 wrote: | Here, the tg3 comes up even when unplugged (laptop, mostly on wlan): | grep -E 'tg3|02:0e.0|eth0' /var/log/kern.log: | Aug 31 16:45:50 kernel: pci 0000:02:0e.0: [14e4:169c] type 00 class 0x020000
Aug 31 16:45:50 kernel: pci 0000:02:0e.0: reg 0x10: [mem 0xe8110000-0xe811ffff]
Aug 31 16:45:50 kernel: pci 0000:02:0e.0: PME# supported from D3hot D3cold
Aug 31 16:45:50 kernel: tg3.c:v3.137 (May 11, 2014)
Aug 31 16:45:50 kernel: tg3 0000:02:0e.0 eth0: Tigon3 [partno(BCM95788A50) rev 3003] (PCI:33MHz:32-bit) MAC address aa:bb:cc:dd:ee:ff
Aug 31 16:45:50 kernel: tg3 0000:02:0e.0 eth0: attached PHY is 5705 (10/100/1000Base-T Ethernet) (WireSpeed[0], EEE[0])
Aug 31 16:45:50 kernel: tg3 0000:02:0e.0 eth0: RXcsums[1] LinkChgREG[0] MIirq[0] ASF[0] TSOcap[1]
Aug 31 16:45:50 kernel: tg3 0000:02:0e.0 eth0: dma_rwctrl[763f0000] dma_mask[32-bit]
Aug 31 16:45:51 kernel: IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready |
What are you having in the logs and dmesg? |
When I connect to corporate network, I don't get anything in 'dmesg' despite the module being loaded correctly. That's the strange thing. I would expect it to create eth0 even when it is not connected. It should leave eth0 unconfigured in that case but eth0 should be present for sure. That does not happen.
May be I need to look at some udev rules?
But it works at home as soon as I plug it in. Before its plugged in, just loading the module does not create eth0, even at home. This may be because the port that gets connected on a macbook is a thunderbolt port and not an ethernet port. So, the tg3 module quietly loads. Once the wire is plugged in, the thunderbolt module finds that its an ethernet cable connected (as opposed to a display port cable) and hence tells the ethernet module, which then loads the firmware etc. and creates eth0.
I don't know how a corporate network breaks this sequence. |
|
| Back to top |
|
|
charles17
Advocate
Joined: 02 Mar 2008
Posts: 3685
|
| Posted: Thu Aug 31, 2017 9:08 pm Post subject: |
|
|
| devsk wrote: | | When I connect to corporate network, I don't get anything in 'dmesg' despite the module being loaded correctly. |
I mean your logs or dmesg from booting, before plugging the thunderbolt or whatever. And what if you had built tg3 into the kernel instead as a module? |
|
| Back to top |
|
|
devsk
Advocate
Joined: 24 Oct 2003
Posts: 3003
Location: Bay Area, CA
|
| Posted: Fri Sep 01, 2017 12:24 am Post subject: |
|
|
| charles17 wrote: | | devsk wrote: | | When I connect to corporate network, I don't get anything in 'dmesg' despite the module being loaded correctly. |
I mean your logs or dmesg from booting, before plugging the thunderbolt or whatever. And what if you had built tg3 into the kernel instead as a module? |
That's what I am saying: there is nothing. 'modprobe tg3' just makes 'tg3' appear in 'lsmod'. There is nothing in the 'dmesg', UNTIL, I plug in the ethernet port into the thunderbolt port. This is because there is no ethernet port on the macbook. 'lspci' won't even show it, UNTIL, you plug in the thunderbolt dongle which converts the ethernet port on one side to thunderbolt male on the other side.
This is all fine.
At home, when I plug in the dongle without the cable attached to it, I see 'tg3' messages in 'dmesg' and eth0 shows up in ifconfig -a and lspci also shows the ethernet port. May be this is the trick I need to use: First attach the dongle without the cable and make eth0 appear and then, attach the corporate network cable. I will try this tomorrow and post. |
|
| Back to top |
|
|
charles17
Advocate
Joined: 02 Mar 2008
Posts: 3685
|
| Posted: Fri Sep 01, 2017 5:41 am Post subject: |
|
|
| devsk wrote: | | At home, when I plug in the dongle without the cable attached to it, I see 'tg3' messages in 'dmesg' and eth0 shows up in ifconfig -a and lspci also shows the ethernet port. |
Sounds like the ethernet device were integrated in the dongle and not in the laptop. What do you get with lspci -tvn, once with dongle plugged, once without? |
|
| Back to top |
|
|
devsk
Advocate
Joined: 24 Oct 2003
Posts: 3003
Location: Bay Area, CA
|
| Posted: Sun Sep 03, 2017 8:28 pm Post subject: |
|
|
| charles17 wrote: | | devsk wrote: | | At home, when I plug in the dongle without the cable attached to it, I see 'tg3' messages in 'dmesg' and eth0 shows up in ifconfig -a and lspci also shows the ethernet port. |
Sounds like the ethernet device were integrated in the dongle and not in the laptop. What do you get with lspci -tvn, once with dongle plugged, once without? |
So, I did the experiment of plugging in the dongle and then load the tg3 and eth0 appears. Phew!! So, there seems to be some hotplug issue with one of the two modules: thunderbolt and tg3. It used to work in 4.11.x. |
|
| Back to top |
|
|
|
Kernel & Hardware
