Nothing showing up with lspci -v

My wireless card is TL-WDN4800(TP-link), support PCIe x 1 port, and it worked on my pc normaly, but can’t detect on my tx1, so how can i let my tx1 detect the wireless card ?

Need to install a 1 port pcie wireless card in my TX1. Instructions say to verify the card is active run lspci -v. Nothing shows up. Not even the controller. This is the output from dmesg | grep pci.

[ 0.609911] platform 1003000.pcie-controller: domain=ffffffc0fe27d558 allocates as[0]=ffffffc0fe1e83e8
[ 0.774979] libata version for pci by jiangche
[ 1.955489] PCIE: tegra_pcie_probe(3966)
[ 1.959130] PCIE: tegra_pcie_read_plat_data(2871)
[ 1.964710] PCIE: tegra_pcie_parse_dt(2935)
[ 1.967966] PCIE: tegra_pcie_probe_complete(3922)
[ 1.972522] PCIE: tegra_pcie_init(2532)
[ 1.976334] PCIE: tegra_pcie_get_resources(1801)
[ 1.981031] PCIE: tegra_pcie_clocks_get(1728)
[ 1.985405] PCIE: tegra_pcie_enable_regulators(1394)
[ 1.990237] tegra-pcie 1003000.pcie-controller: PCIE: Enable power rails
[ 1.996879] PCIE: tegra_pcie_power_on(1629)
[ 2.001057] PCIE: tegra_pcie_map_resources(1488)
[ 2.005640] PCIE: tegra_pcie_power_ungate(1442)
[ 2.010884] PCIE: tegra_pcie_enable_pads(1277)
[ 2.014582] PCIE: tegra_pcie_enable_controller(1329)
[ 2.019512] PCIE: tegra_pcie_enable_wrap(1307)
[ 2.023926] PCIE: tegra_pcie_conf_gpios(2293)
[ 2.028310] PCIE: tegra_pcie_enable_msi(2760)
[ 2.032607] PCIE: tegra_pcie_check_ports(2243)
[ 2.037005] tegra-pcie 1003000.pcie-controller: probing port 0, using 4 lanes and lane map as 0x14
[ 2.045945] PCIE: tegra_pcie_port_enable(1891)
[ 2.050377] PCIE: tegra_pcie_port_reset(1872)
[ 2.056702] PCIE: tegra_pcie_enable_rp_features(2129)
[ 2.059774] PCIE: tegra_pcie_enable_aer(1041)
[ 2.064088] PCIE: tegra_pcie_apply_sw_war(1980)
[ 2.068626] PCIE: tegra_pcie_prsnt_map_override(1099)
[ 2.073623] PCIE: tegra_pcie_isr(1182)
[ 2.077362] tegra-pcie 1003000.pcie-controller: probing port 1, using 1 lanes and lane map as 0x14
[ 2.086277] PCIE: tegra_pcie_port_enable(1891)
[ 2.090717] PCIE: tegra_pcie_port_reset(1872)
[ 2.097043] PCIE: tegra_pcie_enable_rp_features(2129)
[ 2.100115] PCIE: tegra_pcie_enable_aer(1041)
[ 2.104429] PCIE: tegra_pcie_apply_sw_war(1980)
[ 2.108965] PCIE: tegra_pcie_prsnt_map_override(1099)
[ 2.113964] PCIE: tegra_pcie_isr(1182)
[ 2.138723] PCIE: tegra_pcie_port_check_link(1946)
[ 2.141520] tegra-pcie 1003000.pcie-controller: link 0 down, ignoring
[ 2.147955] PCIE: tegra_pcie_port_disable(1915)
[ 2.152435] PCIE: tegra_pcie_port_check_link(1946)
[ 2.157217] tegra-pcie 1003000.pcie-controller: link 1 down, ignoring
[ 2.163616] PCIE: tegra_pcie_port_disable(1915)
[ 2.168148] tegra-pcie 1003000.pcie-controller: PCIE: no ports detected
[ 2.174710] PCIE: tegra_pcie_disable_msi(2831)
[ 2.179159] PCIE: tegra_pcie_power_off(1680)
[ 2.183374] PCIE: tegra_pcie_prsnt_map_override(1099)
[ 2.188426] PCIE: tegra_pcie_prsnt_map_override(1099)
[ 2.193429] PCIE: tegra_pcie_isr(1182)
[ 2.197166] PCIE: tegra_pcie_pme_turnoff(1594)
[ 2.201575] PCIE: tegra_pcie_isr(1182)
[ 2.205304] PCIE: tegra_pcie_enable_pads(1277)
[ 2.209759] PCIE: tegra_pcie_unmap_resources(1544)
[ 2.214637] PCIE: tegra_pcie_disable_regulators(1417)
[ 2.219531] tegra-pcie 1003000.pcie-controller: PCIE: Disable power rails
[ 2.226279] PCIE: tegra_pcie_clocks_put(1779)
[ 3.087233] ehci-pci: EHCI PCI platform driver

That’s showed my tx1 can’t enum pcie device. then disabled pcie port. And somebody suggest disble the SSC on the tx1 , i tried , but there is no effect.

jiang

On your PC I’m assuming it is running Linux (I only saw that the card supports Windows officially, so I’m trying to figure out which driver was used on Linux).

Under Linux you can get a brief list of visible PCIe devices via “lspci”. You’ll see the left side shows a slot ID, e.g., something like “01:00.0”. Find out which device under Linux your card shows as, then run this (with your slot substituted) and see which driver is used:

sudo lspci -s '00:00.0' -vvv | egrep -i 'driver'

Then on the Jetson find out if “lspci” shows anything, and whether or not it does, see if “lsmod” shows a module which might match that driver. If the driver isn’t a module, then lsmod wouldn’t show it, but lspci will always list a driver when found…lsmod is just to see if we can verify the driver is already loaded (in which case the issue is configuration).

Hi

This is my log on pc , if i must be load the wilesscard’s driver first and then i can detect the pcie ? I thought there was no connection between them.

jc@jc-B85M-DS3H-A:~ lspci 00:00.0 Host bridge: Intel Corporation 4th Gen Core Processor DRAM Controller (rev 06) 00:02.0 VGA compatible controller: Intel Corporation 4th Generation Core Processor Family Integrated Graphics Controller (rev 06) 00:03.0 Audio device: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor HD Audio Controller (rev 06) 00:14.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family USB xHCI (rev 05) 00:16.0 Communication controller: Intel Corporation 8 Series/C220 Series Chipset Family MEI Controller #1 (rev 04) 00:1a.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family USB EHCI #2 (rev 05) 00:1b.0 Audio device: Intel Corporation 8 Series/C220 Series Chipset High Definition Audio Controller (rev 05) 00:1c.0 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #1 (rev d5) 00:1c.2 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #3 (rev d5) 00:1c.5 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #6 (rev d5) 00:1d.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family USB EHCI #1 (rev 05) 00:1f.0 ISA bridge: Intel Corporation B85 Express LPC Controller (rev 05) 00:1f.2 SATA controller: Intel Corporation 8 Series/C220 Series Chipset Family 6-port SATA Controller 1 [AHCI mode] (rev 05) 00:1f.3 SMBus: Intel Corporation 8 Series/C220 Series Chipset Family SMBus Controller (rev 05) 02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 0c) 03:00.0 Network controller: Qualcomm Atheros AR93xx Wireless Network Adapter (rev 01) jc@jc-B85M-DS3H-A:~
jc@jc-B85M-DS3H-A:~ jc@jc-B85M-DS3H-A:~ sudo lspci -s ‘03:00.0’ -vvv | egrep -i ‘driver’
Kernel driver in use: ath9k
jc@jc-B85M-DS3H-A:~ jc@jc-B85M-DS3H-A:~ lsmod
Module Size Used by
ctr 16384 3
ccm 20480 3
arc4 16384 2
ath9k 147456 0
ath9k_common 32768 1 ath9k
ath9k_hw 479232 2 ath9k_common,ath9k
rfcomm 69632 0
bnep 24576 2
bluetooth 516096 10 bnep,rfcomm
ar9003_csi 106496 1 ath9k_hw
ath 32768 3 ath9k_common,ath9k,ath9k_hw
snd_hda_codec_realtek 90112 1
snd_hda_codec_hdmi 53248 1

[quote]

On your PC I’m assuming it is running Linux (I only saw that the card supports Windows officially, so I’m trying to figure out which driver was used on Linux).

Under Linux you can get a brief list of visible PCIe devices via “lspci”. You’ll see the left side shows a slot ID, e.g., something like “01:00.0”. Find out which device under Linux your card shows as, then run this (with your slot substituted) and see which driver is used:

sudo lspci -s '00:00.0' -vvv | egrep -i 'driver'

Then on the Jetson find out if “lspci” shows anything, and whether or not it does, see if “lsmod” shows a module which might match that driver. If the driver isn’t a module, then lsmod wouldn’t show it, but lspci will always list a driver when found…lsmod is just to see if we can verify the driver is already loaded (in which case the issue is configur

I tried load ath driver by add ath and ath9k to the system file /etc/modules-load.d/modules, and then reboot, it insmod driver sucucessed , like this :
Module Size Used by
bnep 14912 2
bcmdhd 7465176 0
ath9k 157715 0
ath9k_common 3124 1 ath9k
ath9k_hw 443606 2 ath9k_common,ath9k
ar9003_csi 93993 1 ath9k_hw
mac80211 486125 1 ath9k
ath 20244 3 ath9k_common,ath9k,ath9k_hw
cfg80211 452931 4 ath,ath9k,mac80211,bcmdhd
bluedroid_pm 11420 0

So i checked the boot process of pc(by dmesg), pcie bus is boot earlier than ath driver . so i think that the pcie may be have other problem on my jetson tx1

Hi,

I found a link , he said the jetpack2.4.1 and 2.3.2 have the same question ,and he belived that nvidia never test the pcie interface, so i don’t known if it is true ,and if it has resovled in new jetpack. And I wonder if it is necessary to continue to do so . Looking forward to your reply.

https://devtalk.nvidia.com/default/topic/937896/pcie-cards-known-to-work-for-tx1/?offset=2

How PCIe is arranged for control versus data may be useful knowledge for what you’re asking. In simpler communications control is achieved over the same wires as the data…for example, a telephone. If you are talking to someone over the telephone you’ll notice that the touch tone for control uses the same wire that you’re talking over. If you were to provide a separate wire for that touch tone, then it is known as “out of band” (OOB).

When a data line is expected to always work without adjustment, you’ll probably not use the extra wiring of OOB. In the case of PCIe the data runs quite fast and needs adjustment during operation to get the best results. An OOB control is required…the data wiring is separate from control wiring. OOB control runs slower and is expected to always work. If for any reason OOB signal itself is bad, then no device can be detected. Even if OOB itself works, there are further tests for determining if there is a PCIe device. Here’s a good explanation:
https://www.xilinx.com/support/answers/52996.html

Either the OOB control signal is failing, or the further tests (think amplitude threshold) are telling the system that there is no useful hardware there.

A driver for your device does not need to be loaded to detect a functional PCIe card via lspci…at least nothing specific to the card. PCIe itself has its own drivers, but those are there and you can pretty much guarantee (short of catastrophic failure) that those drivers are loaded for detecing PCIe presence. If any PCIe device plugged into that PCIe slot can be found, then you know the PCIe drivers are loaded. You may want to test other PCIe cards to see if lspci shows anything, but this would not necessarily detect PCIe driver issues…if that slot fails with all PCIe devices then it is more likely a hardware failure.

Once a PCIe device is found the system needs to associate a driver with the device…this is the driver specific to your device. Since the device was not detected you can’t attempt to load a device-specific driver. Detection never got far enough for this to be relevant or possible.

On a gen. 2 capable device and gen. 2 bus the control will be looking at signals…if gen. 2 speeds are not reliable, it’ll switch back to gen. 1 speeds. If that too is not reliable, then I’m not sure if the card will no longer be listed via lspci or not…if the control signal itself is not reliable, then you can guarantee lspci cannot see the device. In your case I don’t know if the OOB signal is failing, or if the card is not listing because OOB returned that the signal quality is bad even at gen. 1 speeds. I have no way to know, but those are the possibilities.

It is rare for the OOB control signal to outright fail. I know this slot works with many add-on cards, so I have to tend to lean towards data signal issues instead of OOB control.

A related comment on spread spectrum: The data signal on a desktop PC normally does not enable SS, but offers it as an option in the BIOS/UEFI. One would turn on SS if experiencing interference…the SS makes it more difficult for the PCIe card to run at full speed, but also reduces interference generation. This applies to the data lane…I don’t know if this applies to the OOB control signal, but I would doubt that a slower signal in need of reliability would use SS with control signals (the OOB signal is slow enough it would be unlikely SS would matter even if OOB uses SS). Disabling SS can give you a slightly better signal, but it seems things are bad enough with this card SS is unlikely to matter at all.

I have tested some PCIe cards, e.g., a gigabit NIC (Realtek chipset) which works. I don’t know what else to test on this to see where the issue is for this particular case without some very expensive test equipment.

EDIT: Perhaps someone can suggest how to measure if power rails are delivering proper power. I saw another post about a failure to detect when the power rail was not valid.

Thanks ,I tried another gigabit NIC(Realtek 8168e), it is worked well, so it is a compatibility issues ? Beacause I belived that my wireless card is not a bad hardware it is worked well on my pc. As i test the signal level with my gigabit NIC and wireless card on the jetson tx1, i found the signal level of RSW Pin and OPETn0/OPETp0 Pin is diffrent.

I will read your reply carefully and if you find the problem where it will be better

The following is my gigabit NIC print log:

tu@tegra-ubuntu:~ ubuntu@tegra-ubuntu:~ lspci
00:01.0 PCI bridge: NVIDIA Corporation Device 0fae (rev a1)
01:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 06)
ubuntu@tegra-ubuntu:~ ubuntu@tegra-ubuntu:~
ubuntu@tegra-ubuntu:~$ dmesg | grep pci
[ 0.609863] platform 1003000.pcie-controller: domain=ffffffc0fe26d558 allocates as[0]=ffffffc0fe1e83e8
[ 0.774769] libata version for pci by jiangche
[ 1.954505] PCIE: tegra_pcie_probe(3966)
[ 1.958140] PCIE: tegra_pcie_read_plat_data(2871)
[ 1.963721] PCIE: tegra_pcie_parse_dt(2935)
[ 1.966931] PCIE: tegra_pcie_probe_complete(3922)
[ 1.971573] PCIE: tegra_pcie_init(2532)
[ 1.975341] PCIE: tegra_pcie_get_resources(1801)
[ 1.980035] PCIE: tegra_pcie_clocks_get(1728)
[ 1.984412] PCIE: tegra_pcie_enable_regulators(1394)
[ 1.989241] tegra-pcie 1003000.pcie-controller: PCIE: Enable power rails
[ 1.995885] PCIE: tegra_pcie_power_on(1629)
[ 2.000064] PCIE: tegra_pcie_map_resources(1488)
[ 2.004648] PCIE: tegra_pcie_power_ungate(1442)
[ 2.009881] PCIE: tegra_pcie_enable_pads(1277)
[ 2.013589] PCIE: tegra_pcie_enable_controller(1329)
[ 2.018518] PCIE: tegra_pcie_enable_wrap(1307)
[ 2.022933] PCIE: tegra_pcie_conf_gpios(2293)
[ 2.027319] PCIE: tegra_pcie_enable_msi(2760)
[ 2.031614] PCIE: tegra_pcie_check_ports(2243)
[ 2.036013] tegra-pcie 1003000.pcie-controller: probing port 0, using 4 lanes and lane map as 0x14
[ 2.044952] PCIE: tegra_pcie_port_enable(1891)
[ 2.049385] PCIE: tegra_pcie_port_reset(1872)
[ 2.055709] PCIE: tegra_pcie_enable_rp_features(2129)
[ 2.058780] PCIE: tegra_pcie_enable_aer(1041)
[ 2.063095] PCIE: tegra_pcie_apply_sw_war(1980)
[ 2.067631] PCIE: tegra_pcie_prsnt_map_override(1099)
[ 2.072629] PCIE: tegra_pcie_isr(1182)
[ 2.076359] tegra-pcie 1003000.pcie-controller: probing port 1, using 1 lanes and lane map as 0x14
[ 2.085295] PCIE: tegra_pcie_port_enable(1891)
[ 2.089725] PCIE: tegra_pcie_port_reset(1872)
[ 2.096050] PCIE: tegra_pcie_enable_rp_features(2129)
[ 2.099121] PCIE: tegra_pcie_enable_aer(1041)
[ 2.103436] PCIE: tegra_pcie_apply_sw_war(1980)
[ 2.107972] PCIE: tegra_pcie_prsnt_map_override(1099)
[ 2.112970] PCIE: tegra_pcie_isr(1182)
[ 2.137716] PCIE: tegra_pcie_port_check_link(1946)
[ 2.140511] PCIE: tegra_pcie_port_check_link(1946)
[ 2.145279] tegra-pcie 1003000.pcie-controller: link 1 down, ignoring
[ 2.151715] PCIE: tegra_pcie_port_disable(1915)
[ 2.156197] PCIE: tegra_pcie_setup(729)
[ 2.160028] PCIE: tegra_pcie_scan_bus(783)
[ 2.164167] PCIE: tegra_pcie_add_bus(763)
[ 2.168099] tegra-pcie 1003000.pcie-controller: PCI host bridge to bus 0000:00
[ 2.175270] pci_bus 0000:00: root bus resource [mem 0x13000000-0x1fffffff]
[ 2.182125] pci_bus 0000:00: root bus resource [mem 0x20000000-0x3fffffff pref]
[ 2.189419] pci_bus 0000:00: root bus resource [bus 00-ff]
[ 2.194852] pci_bus 0000:00: root bus resource [io 0x1000-0xffff]
[ 2.201016] pci_bus 0000:00: scanning bus
[ 2.201051] pci 0000:00:01.0: [10de:0fae] type 01 class 0x060400
[ 2.201094] pci 0000:00:01.0: calling pci_fixup_ide_bases+0x0/0x44
[ 2.201149] pci 0000:00:01.0: PME# supported from D0 D1 D2 D3hot D3cold
[ 2.201160] pci 0000:00:01.0: PME# disabled
[ 2.201334] pci_bus 0000:00: fixups for bus
[ 2.201351] pci 0000:00:01.0: scanning [bus 00-00] behind bridge, pass 0
[ 2.201358] pci 0000:00:01.0: bridge configuration invalid ([bus 00-00]), reconfiguring
[ 2.209018] pci 0000:00:01.0: scanning [bus 00-00] behind bridge, pass 1
[ 2.209123] PCIE: tegra_pcie_add_bus(763)
[ 2.212961] PCIE: tegra_pcie_bus_alloc(554)
[ 2.217149] pci_bus 0000:01: scanning bus
[ 2.217184] pci 0000:01:00.0: [10ec:8168] type 00 class 0x020000
[ 2.217211] pci 0000:01:00.0: reg 10: [io 0x0000-0x00ff]
[ 2.217250] pci 0000:01:00.0: reg 18: [mem 0x00000000-0x00000fff 64bit pref]
[ 2.217277] pci 0000:01:00.0: reg 20: [mem 0x00000000-0x00003fff 64bit pref]
[ 2.217297] pci 0000:01:00.0: reg 30: [mem 0x00000000-0x0000ffff pref]
[ 2.217312] pci 0000:01:00.0: calling pci_fixup_ide_bases+0x0/0x44
[ 2.217390] pci 0000:01:00.0: supports D1 D2
[ 2.217397] pci 0000:01:00.0: PME# supported from D0 D1 D2 D3hot D3cold
[ 2.217408] pci 0000:01:00.0: PME# disabled
[ 2.237084] pci_bus 0000:01: fixups for bus
[ 2.237101] pci_bus 0000:01: bus scan returning with max=01
[ 2.237111] pci_bus 0000:01: busn_res: [bus 01-ff] end is updated to 01
[ 2.237121] pci_bus 0000:00: bus scan returning with max=01
[ 2.237128] PCIE: tegra_pcie_configure_aspm(910)
[ 2.239768] PCIE: tegra_pcie_config_l1ss_l12_thtime(818)
[ 2.245042] PCIE: tegra_pcie_enable_ltr_support(839)
[ 2.250016] pci 0000:00:01.0: fixup irq: got 130
[ 2.250024] pci 0000:00:01.0: assigning IRQ 130
[ 2.250034] pci 0000:01:00.0: fixup irq: got 130
[ 2.250040] pci 0000:01:00.0: assigning IRQ 130
[ 2.250067] pci 0000:00:01.0: BAR 15: assigned [mem 0x20000000-0x200fffff pref]
[ 2.257273] pci 0000:00:01.0: BAR 13: assigned [io 0x1000-0x1fff]
[ 2.263413] pci 0000:01:00.0: BAR 6: assigned [mem 0x20000000-0x2000ffff pref]
[ 2.270632] pci 0000:01:00.0: BAR 4: assigned [mem 0x20010000-0x20013fff 64bit pref]
[ 2.278345] pci 0000:01:00.0: BAR 4: set to [mem 0x20010000-0x20013fff 64bit pref] (PCI address [0x20010000-0x20013fff])
[ 2.278354] pci 0000:01:00.0: BAR 2: assigned [mem 0x20014000-0x20014fff 64bit pref]
[ 2.286044] pci 0000:01:00.0: BAR 2: set to [mem 0x20014000-0x20014fff 64bit pref] (PCI address [0x20014000-0x20014fff])
[ 2.286053] pci 0000:01:00.0: BAR 0: assigned [io 0x1000-0x10ff]
[ 2.292124] pci 0000:01:00.0: BAR 0: set to [io 0x1000-0x10ff] (PCI address [0x1000-0x10ff])
[ 2.292134] pci 0000:00:01.0: PCI bridge to [bus 01]
[ 2.297048] pci 0000:00:01.0: bridge window [io 0x1000-0x1fff]
[ 2.303106] pci 0000:00:01.0: bridge window [mem 0x20000000-0x200fffff pref]
[ 2.315933] pci 0000:00:01.0: enabling bus mastering
[ 2.315949] pci 0000:00:01.0: calling tegra_pcie_relax_enable+0x0/0x20
[ 2.315960] pci 0000:00:01.0: calling tegra_pcie_fixup_bridge+0x0/0x5c
[ 2.316129] pcieport 0000:00:01.0: Signaling PME through PCIe PME interrupt
[ 2.322878] pci 0000:01:00.0: Signaling PME through PCIe PME interrupt
[ 2.329392] pcie_pme 0000:00:01.0:pcie01: service driver pcie_pme loaded
[ 2.329474] aer 0000:00:01.0:pcie02: service driver aer loaded
[ 2.329533] pci 0000:01:00.0: calling tegra_pcie_relax_enable+0x0/0x20
[ 2.329547] pci 0000:01:00.0: calling tegra_pcie_fixup_bridge+0x0/0x5c
[ 2.329556] PCIE: tegra_pcie_enable_features(2512)
[ 2.334126] PCIE: tegra_pcie_link_speed(2498)
[ 2.338473] PCIE: tegra_pcie_change_link_speed(2430)
[ 2.343399] PCIE: tegra_pcie_change_link_speed(2430)
[ 2.348373] tegra-pcie 1003000.pcie-controller: PCIE: No Link speed change happened
[ 2.355968] PCIE: tegra_pcie_apply_sw_war(1980)
[ 3.251215] ehci-pci: EHCI PCI platform driver
[ 13.329014] vgaarb: this pci device is not a vga device
[ 13.416043] vgaarb: this pci device is not a vga device

As you said , In jetson document , the pcie is PCIE2.0(GEN2) interface, and I have confirmed from the tplink official website TL-WDN4800(wireless card) is PCIE2.0 yet, and my gigabit NIC(model:BL-TL8168) is PCIE1.0a . So the jetson tx1 should be able to support both .

In JetsonTX1_Module_DataSheet_DS07224010v1.pdf, nvidia said:
PCI Express Base Specification Revision 2.0 :
Jetson TX1 meets the timing requirements for the Gen2 (5.0 GT/s) data rates. Refer to
specification for complete interface timing details.
Although NVIDIA validates that the Jetson TX1 design complies with the PCIe
specification, PCIe software support may be limited.

  1. I try to add the print in the kernel to track the problem, it is the implementation process is following describe, and finally there is a problem here, but I did not find the relevant documents to explain these registers, so I can not continue to track down.

kernel pcie fuctions process: tegra_pcie_check_ports -> tegra_pcie_port_check_link -> get_rdet_status(port->index); ->tegra_phy_get_lane_rdet
bool tegra_phy_get_lane_rdet(u8 lane_num)
{
u32 data;
void __iomem *pad_base = IO_ADDRESS(TEGRA_XUSB_PADCTL_BASE);

switch (lane_num) {
case 0:
	data = readl(pad_base + XUSB_PADCTL_UPHY_MISC_PAD_P0_CTL1);
	data = data &
		XUSB_PADCTL_UPHY_MISC_PAD_P0_CTL1_AUX_TX_RDET_STATUS;
	break;
case 1:
	data = readl(pad_base + XUSB_PADCTL_UPHY_MISC_PAD_P1_CTL1);
	data = data &
		XUSB_PADCTL_UPHY_MISC_PAD_P1_CTL1_AUX_TX_RDET_STATUS;
	break;
case 2:
	data = readl(pad_base + XUSB_PADCTL_UPHY_MISC_PAD_P2_CTL1);
	data = data &
		XUSB_PADCTL_UPHY_MISC_PAD_P2_CTL1_AUX_TX_RDET_STATUS;
	break;
case 3:
	data = readl(pad_base + XUSB_PADCTL_UPHY_MISC_PAD_P3_CTL1);
	data = data &
		XUSB_PADCTL_UPHY_MISC_PAD_P3_CTL1_AUX_TX_RDET_STATUS;
	break;
case 4:
	data = readl(pad_base + XUSB_PADCTL_UPHY_MISC_PAD_P4_CTL1);
	data = data &
		XUSB_PADCTL_UPHY_MISC_PAD_P4_CTL1_AUX_TX_RDET_STATUS;
	break;
default:
	return 0;
}
return !(!data);

}

  1. Then the previous reply, I found several pin levels are different beetwen my gigabit NIC and wireless card(TL-WDN7500), and even i do not known if it is useful for explain my problem, as follows:
    pin PCIE0_L0_CLKREQ: NIC(0v) TL-WDN7500(3.3v)
    pin REFCLK: TL-WDN7500 have no clk
    pin PEX_TX4_P(N):NIC(0v) TL-WDN7500(0.76v)
    pin PEX0_RST: MIC(3.3v) TL-WDN7500(0v)

I couldn’t tell you about those registers either. Someone with knowledge of that level of PCIe debugging might be able to help. Here are some thoughts though on your most recent information…

The gigabit uses a different driver than the wireless…but that driver won’t have any effect on lspci, it is PCIe which is testing for a response which is unrelated to the actual device PCIe talks to (the device driver isn’t loaded during query and query does not care). Compatibility for support in PCIe might be for the driver running the end device, e.g., DMA support may change when one driver was designed for 32-bit user space support and the other for 64-bit…once detected, the actual operation of a PCIe wifi card might suffer if this is not correct, but detection itself should be 100% on any functional card with correct electrical support.

Your gigabit works…you know there is no catastrophic failure. You know that signal integrity can work for OOB control, and since OOB does not try to run at cutting edge maximum speed, it is likely the Jetson side does what is needed to query the wifi card. It is unknown why the wifi card is failing…as mentioned before, OOB could itself fail, or some return value about signals via OOB could be telling the system there is nothing there. I’m unsure as to how you would differentiate among the different reasons the card does not show up without something like a protocol analyzer on the OOB communications.

One very minor possibility is that one card may consume more power than the other…if power rails were insufficient the one consuming more power might fail to enumerate. I have no particular reason to think this is the case, it’s just something which could be tested.

Thanks

I am now more troubled by this problem, and I found that other people are facing the same problem and I have not resolved, nvidia official if you can follow this problem is better, detailed under the test. The information on hand at hand can not let me continue to track this problem, I almost can not think of a way to analyze this problem.

Below it is link that he said the tx1 carrier dev board is not reliable
https://devtalk.nvidia.com/default/topic/1000827/custom-pcie-card-with-kintex-7-not-showing-up-on-jetson-tx1-in-lspci/#5126767

So I wonder if I need to keep track of this problem, can you give me some suggestion?

This looks more like an inter-operability issue. We will check if we have the same PCIe device available and see what is the issue issue with link up?
Can you please provide us the output of ‘sudo lspci -xx’ when it is connected to an x86-Ubuntu machine?

jc@jc-B85M-DS3H-A:~ jc@jc-B85M-DS3H-A:~ lspci
00:00.0 Host bridge: Intel Corporation 4th Gen Core Processor DRAM Controller (rev 06)
00:02.0 VGA compatible controller: Intel Corporation 4th Generation Core Processor Family Integrated Graphics Controller (rev 06)
00:03.0 Audio device: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor HD Audio Controller (rev 06)
00:14.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family USB xHCI (rev 05)
00:16.0 Communication controller: Intel Corporation 8 Series/C220 Series Chipset Family MEI Controller #1 (rev 04)
00:1a.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family USB EHCI #2 (rev 05)
00:1b.0 Audio device: Intel Corporation 8 Series/C220 Series Chipset High Definition Audio Controller (rev 05)
00:1c.0 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #1 (rev d5)
00:1c.2 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #3 (rev d5)
00:1c.5 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #6 (rev d5)
00:1d.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family USB EHCI #1 (rev 05)
00:1f.0 ISA bridge: Intel Corporation B85 Express LPC Controller (rev 05)
00:1f.2 SATA controller: Intel Corporation 8 Series/C220 Series Chipset Family 6-port SATA Controller 1 [AHCI mode] (rev 05)
00:1f.3 SMBus: Intel Corporation 8 Series/C220 Series Chipset Family SMBus Controller (rev 05)
02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 0c)
03:00.0 Network controller: Qualcomm Atheros AR93xx Wireless Network Adapter (rev 01)
jc@jc-B85M-DS3H-A:~ jc@jc-B85M-DS3H-A:~
jc@jc-B85M-DS3H-A:~$ lspci -xx
00:00.0 Host bridge: Intel Corporation 4th Gen Core Processor DRAM Controller (rev 06)
00: 86 80 00 0c 06 00 90 20 06 00 00 06 00 00 00 00
10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
20: 00 00 00 00 00 00 00 00 00 00 00 00 58 14 00 50
30: 00 00 00 00 e0 00 00 00 00 00 00 00 00 00 00 00

00:02.0 VGA compatible controller: Intel Corporation 4th Generation Core Processor Family Integrated Graphics Controller (rev 06)
00: 86 80 1e 04 07 04 90 00 06 00 00 03 00 00 00 00
10: 04 00 80 f7 00 00 00 00 0c 00 00 e0 00 00 00 00
20: 01 f0 00 00 00 00 00 00 00 00 00 00 58 14 00 d0
30: 00 00 00 00 90 00 00 00 00 00 00 00 0b 01 00 00

00:03.0 Audio device: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor HD Audio Controller (rev 06)
00: 86 80 0c 0c 06 04 10 00 06 00 03 04 10 00 00 00
10: 04 40 e1 f7 00 00 00 00 00 00 00 00 00 00 00 00
20: 00 00 00 00 00 00 00 00 00 00 00 00 86 80 10 20
30: 00 00 00 00 50 00 00 00 00 00 00 00 0b 01 00 00

00:14.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family USB xHCI (rev 05)
00: 86 80 31 8c 06 04 90 02 05 30 03 0c 00 00 00 00
10: 04 00 e0 f7 00 00 00 00 00 00 00 00 00 00 00 00
20: 00 00 00 00 00 00 00 00 00 00 00 00 58 14 07 50
30: 00 00 00 00 70 00 00 00 00 00 00 00 0b 01 00 00

00:16.0 Communication controller: Intel Corporation 8 Series/C220 Series Chipset Family MEI Controller #1 (rev 04)
00: 86 80 3a 8c 06 04 10 00 04 00 80 07 00 00 80 00
10: 04 e0 e1 f7 00 00 00 00 00 00 00 00 00 00 00 00
20: 00 00 00 00 00 00 00 00 00 00 00 00 58 14 3a 1c
30: 00 00 00 00 50 00 00 00 00 00 00 00 0b 01 00 00

00:1a.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family USB EHCI #2 (rev 05)
00: 86 80 2d 8c 06 00 90 02 05 20 03 0c 00 00 00 00
10: 00 c0 e1 f7 00 00 00 00 00 00 00 00 00 00 00 00
20: 00 00 00 00 00 00 00 00 00 00 00 00 58 14 06 50
30: 00 00 00 00 50 00 00 00 00 00 00 00 0b 01 00 00

00:1b.0 Audio device: Intel Corporation 8 Series/C220 Series Chipset High Definition Audio Controller (rev 05)
00: 86 80 20 8c 06 04 10 00 05 00 03 04 10 00 00 00
10: 04 00 e1 f7 00 00 00 00 00 00 00 00 00 00 00 00
20: 00 00 00 00 00 00 00 00 00 00 00 00 58 14 02 a0
30: 00 00 00 00 50 00 00 00 00 00 00 00 03 01 00 00

00:1c.0 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #1 (rev d5)
00: 86 80 10 8c 07 00 10 00 d5 00 04 06 10 00 81 00
10: 00 00 00 00 00 00 00 00 00 01 01 00 f0 00 00 20
20: f0 ff 00 00 f1 ff 01 00 00 00 00 00 00 00 00 00
30: 00 00 00 00 40 00 00 00 00 00 00 00 0b 01 10 00

00:1c.2 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #3 (rev d5)
00: 86 80 14 8c 07 00 10 00 d5 00 04 06 10 00 81 00
10: 00 00 00 00 00 00 00 00 00 02 02 00 e0 e0 00 00
20: d0 f7 d0 f7 01 f0 01 f0 00 00 00 00 00 00 00 00
30: 00 00 00 00 40 00 00 00 00 00 00 00 0b 03 10 00

00:1c.5 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #6 (rev d5)
00: 86 80 1a 8c 07 00 10 00 d5 00 04 06 10 00 81 00
10: 00 00 00 00 00 00 00 00 00 03 03 00 f0 00 00 00
20: c0 f7 c0 f7 f1 ff 01 00 00 00 00 00 00 00 00 00
30: 00 00 00 00 40 00 00 00 00 00 00 00 0a 02 10 00

00:1d.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family USB EHCI #1 (rev 05)
00: 86 80 26 8c 06 00 90 02 05 20 03 0c 00 00 00 00
10: 00 b0 e1 f7 00 00 00 00 00 00 00 00 00 00 00 00
20: 00 00 00 00 00 00 00 00 00 00 00 00 58 14 06 50
30: 00 00 00 00 50 00 00 00 00 00 00 00 03 01 00 00

00:1f.0 ISA bridge: Intel Corporation B85 Express LPC Controller (rev 05)
00: 86 80 50 8c 07 00 10 02 05 00 01 06 00 00 80 00
10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
20: 00 00 00 00 00 00 00 00 00 00 00 00 58 14 01 50
30: 00 00 00 00 e0 00 00 00 00 00 00 00 00 00 00 00

00:1f.2 SATA controller: Intel Corporation 8 Series/C220 Series Chipset Family 6-port SATA Controller 1 [AHCI mode] (rev 05)
00: 86 80 02 8c 07 04 b0 02 05 01 06 01 00 00 00 00
10: b1 f0 00 00 a1 f0 00 00 91 f0 00 00 81 f0 00 00
20: 61 f0 00 00 00 a0 e1 f7 00 00 00 00 58 14 05 b0
30: 00 00 00 00 80 00 00 00 00 00 00 00 0a 02 00 00

00:1f.3 SMBus: Intel Corporation 8 Series/C220 Series Chipset Family SMBus Controller (rev 05)
00: 86 80 22 8c 01 00 80 02 05 00 05 0c 00 00 00 00
10: 04 90 e1 f7 00 00 00 00 00 00 00 00 00 00 00 00
20: 41 f0 00 00 00 00 00 00 00 00 00 00 58 14 01 50
30: 00 00 00 00 00 00 00 00 00 00 00 00 0b 03 00 00

02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 0c)
00: ec 10 68 81 07 04 10 00 0c 00 00 02 10 00 00 00
10: 01 e0 00 00 00 00 00 00 04 00 d0 f7 00 00 00 00
20: 0c 00 00 f0 00 00 00 00 00 00 00 00 58 14 00 e0
30: 00 00 00 00 40 00 00 00 00 00 00 00 0b 01 00 00

03:00.0 Network controller: Qualcomm Atheros AR93xx Wireless Network Adapter (rev 01)
00: 8c 16 30 00 07 00 10 00 01 00 80 02 10 00 00 00
10: 04 00 c0 f7 00 00 00 00 00 00 00 00 00 00 00 00
20: 00 00 00 00 00 00 00 00 00 00 00 00 8c 16 12 31
30: 00 00 c2 f7 40 00 00 00 00 00 00 00 0a 01 00 00

jc@jc-B85M-DS3H-A:~ jc@jc-B85M-DS3H-A:~ ls -vv
1.log Documents Music Public Videos matlab_crash_dump.2254-1 matlab_crash_dump.4163-1 matlab_crash_dump.5755-1
Desktop Downloads Pictures Templates examples.desktop matlab_crash_dump.2317-1 matlab_crash_dump.4494-1 share
jc@jc-B85M-DS3H-A:~$ lspci -vv
00:00.0 Host bridge: Intel Corporation 4th Gen Core Processor DRAM Controller (rev 06)
Subsystem: Gigabyte Technology Co., Ltd Device 5000
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort+ >SERR- <PERR- INTx-
Latency: 0
Capabilities:
Kernel driver in use: hsw_uncore

00:02.0 VGA compatible controller: Intel Corporation 4th Generation Core Processor Family Integrated Graphics Controller (rev 06) (prog-if 00 [VGA controller])
Subsystem: Gigabyte Technology Co., Ltd Device d000
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- SERR- <PERR- INTx-
Latency: 0
Interrupt: pin A routed to IRQ 28
Region 0: Memory at f7800000 (64-bit, non-prefetchable)
Region 2: Memory at e0000000 (64-bit, prefetchable)
Region 4: I/O ports at f000
Expansion ROM at [disabled]
Capabilities:
Kernel driver in use: i915

00:03.0 Audio device: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor HD Audio Controller (rev 06)
Subsystem: Intel Corporation Device 2010
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- SERR- <PERR- INTx-
Latency: 0, Cache Line Size: 64 bytes
Interrupt: pin A routed to IRQ 30
Region 0: Memory at f7e14000 (64-bit, non-prefetchable)
Capabilities:
Kernel driver in use: snd_hda_intel

00:14.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family USB xHCI (rev 05) (prog-if 30 [XHCI])
Subsystem: Gigabyte Technology Co., Ltd Device 5007
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- SERR- <PERR- INTx-
Latency: 0
Interrupt: pin A routed to IRQ 24
Region 0: Memory at f7e00000 (64-bit, non-prefetchable)
Capabilities:
Kernel driver in use: xhci_hcd

00:16.0 Communication controller: Intel Corporation 8 Series/C220 Series Chipset Family MEI Controller #1 (rev 04)
Subsystem: Gigabyte Technology Co., Ltd Device 1c3a
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- SERR- <PERR- INTx-
Latency: 0
Interrupt: pin A routed to IRQ 27
Region 0: Memory at f7e1e000 (64-bit, non-prefetchable)
Capabilities:
Kernel driver in use: mei_me

00:1a.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family USB EHCI #2 (rev 05) (prog-if 20 [EHCI])
Subsystem: Gigabyte Technology Co., Ltd Device 5006
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- SERR- <PERR- INTx-
Latency: 0
Interrupt: pin A routed to IRQ 16
Region 0: Memory at f7e1c000 (32-bit, non-prefetchable)
Capabilities:
Kernel driver in use: ehci-pci

00:1b.0 Audio device: Intel Corporation 8 Series/C220 Series Chipset High Definition Audio Controller (rev 05)
Subsystem: Gigabyte Technology Co., Ltd Device a002
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- SERR- <PERR- INTx-
Latency: 0, Cache Line Size: 64 bytes
Interrupt: pin A routed to IRQ 29
Region 0: Memory at f7e10000 (64-bit, non-prefetchable)
Capabilities:
Kernel driver in use: snd_hda_intel

00:1c.0 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #1 (rev d5) (prog-if 00 [Normal decode])
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- SERR- <PERR- INTx-
Latency: 0, Cache Line Size: 64 bytes
Bus: primary=00, secondary=01, subordinate=01, sec-latency=0
Secondary status: 66MHz- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort+ <SERR- Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Capabilities:
Kernel driver in use: pcieport

00:1c.2 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #3 (rev d5) (prog-if 00 [Normal decode])
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- SERR- <PERR- INTx-
Latency: 0, Cache Line Size: 64 bytes
Bus: primary=00, secondary=02, subordinate=02, sec-latency=0
I/O behind bridge: 0000e000-0000efff
Memory behind bridge: f7d00000-f7dfffff
Prefetchable memory behind bridge: 00000000f0000000-00000000f00fffff
Secondary status: 66MHz- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- <SERR- Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Capabilities:
Kernel driver in use: pcieport

00:1c.5 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #6 (rev d5) (prog-if 00 [Normal decode])
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- SERR- <PERR- INTx-
Latency: 0, Cache Line Size: 64 bytes
Bus: primary=00, secondary=03, subordinate=03, sec-latency=0
Memory behind bridge: f7c00000-f7cfffff
Secondary status: 66MHz- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- <SERR- Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Capabilities:
Kernel driver in use: pcieport

00:1d.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family USB EHCI #1 (rev 05) (prog-if 20 [EHCI])
Subsystem: Gigabyte Technology Co., Ltd Device 5006
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- SERR- <PERR- INTx-
Latency: 0
Interrupt: pin A routed to IRQ 23
Region 0: Memory at f7e1b000 (32-bit, non-prefetchable)
Capabilities:
Kernel driver in use: ehci-pci

00:1f.0 ISA bridge: Intel Corporation B85 Express LPC Controller (rev 05)
Subsystem: Gigabyte Technology Co., Ltd Device 5001
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- SERR- <PERR- INTx-
Latency: 0
Capabilities:
Kernel driver in use: lpc_ich

00:1f.2 SATA controller: Intel Corporation 8 Series/C220 Series Chipset Family 6-port SATA Controller 1 [AHCI mode] (rev 05) (prog-if 01 [AHCI 1.0])
Subsystem: Gigabyte Technology Co., Ltd Device b005
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- SERR- <PERR- INTx-
Latency: 0
Interrupt: pin B routed to IRQ 25
Region 0: I/O ports at f0b0
Region 1: I/O ports at f0a0
Region 2: I/O ports at f090
Region 3: I/O ports at f080
Region 4: I/O ports at f060
Region 5: Memory at f7e1a000 (32-bit, non-prefetchable)
Capabilities:
Kernel driver in use: ahci

00:1f.3 SMBus: Intel Corporation 8 Series/C220 Series Chipset Family SMBus Controller (rev 05)
Subsystem: Gigabyte Technology Co., Ltd Device 5001
Control: I/O+ Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- SERR- <PERR- INTx-
Interrupt: pin C routed to IRQ 11
Region 0: Memory at f7e19000 (64-bit, non-prefetchable) [disabled]
Region 4: I/O ports at f040

02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 0c)
Subsystem: Gigabyte Technology Co., Ltd Motherboard
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- SERR- <PERR- INTx-
Latency: 0, Cache Line Size: 64 bytes
Interrupt: pin A routed to IRQ 26
Region 0: I/O ports at e000
Region 2: Memory at f7d00000 (64-bit, non-prefetchable)
Region 4: Memory at f0000000 (64-bit, prefetchable)
Capabilities:
Kernel driver in use: r8169

03:00.0 Network controller: Qualcomm Atheros AR93xx Wireless Network Adapter (rev 01)
Subsystem: Qualcomm Atheros Device 3112
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- SERR- <PERR- INTx-
Latency: 0, Cache Line Size: 64 bytes
Interrupt: pin A routed to IRQ 17
Region 0: Memory at f7c00000 (64-bit, non-prefetchable)
Expansion ROM at f7c20000 [disabled]
Capabilities:
Kernel driver in use: ath9k

hi vidyas,

Add:
My wireless card is TL-WDN4800, with pcie 2.0 1x, and other info:
03:00.0 Network controller: Qualcomm Atheros AR93xx Wireless Network Adapter (rev 01)

FYI, whenever you need any details from lspci it needs sudo or it won’t show what is actually available (“access denied” messages).