[Aug 6] Debian Stretch Minimal 64bit (0.7.8) / Ubuntu 18.04 Bionic LXDE Desktop Image (0.7.8) / Ubuntu 18.04 Bionic minimal 64bit / 32bit Image (0.7.8) / Ubuntu 18.04 Bionic Containers Image (0.7.8) / Stretch OpenMediaVault OS Image armhf / Stretch OpenMediaVault OS Image arm64 ( 0.7.8) - ROCK64 | [June 25] Stock Android 8.1 - ROCK64 | [June 19] Armbian (5.42) - ROCK64 | [June 19] Armbian (5.38) - PINE A64(+) / PINE A64-LTS / SOPINE

Project Inspiration | Get Started | IRC Logs | Forum Rules/Policy


PCIe-Bus not initialized, no devices detected
#1
Hey guys,

I bought one of those beauties (v.2.1 2018-06-06) and flashed a micro SD-Card with the latest image of debian stretch minimal (0.7.9).
I had to notice however, that not even the pcie bus is showing up. (The output of lspci is empty, no matter if a card is in the slot or not)

When a card is in the slot, it does not seem to get any power. (No lights turn on, neither do they get warm)
The cards I tested:
- Logilink Dual LAN-Card with two Realtek chips on it http://www.logilink.com/media/datasheets/PC0075.pdf
- Intel Ethernet LAN Card D33025

- Varius graphics cards (wasn't expecting them to work, really)

I tested multiple versions and images. Did not work with either BSP nor mainline kernel.
The last image I tried was (0.7.8) of minimal Ubuntu with Kernel (4.4.132-1072-rockchip-ayufan-ga1d27dba5a2e).
I attached the boot-log (dmesg output) on that one.

Have I forgotten something?
I already crawled through the entire forum of Frank Mankel, unfortunately to no avail.
I read something about setting jumpers for a similar problem somewhere, but for a solution, the post links to an entry on Frank Mankel's deleted blog.  Confused


Attached Files
.log   dmesg.log (Size: 63.01 KB / Downloads: 6)
Reply
#2
Hi,

i get only the two cards from pine64 to work.
  • PCIe NVMe card
  • PCIe SATA card
Both cards works fine on bionic-minimal 0.7.9. All other cards i tested failed. Most with kernel panic.

For links from my forum use subdomain forum.frank-mankel.org
Sorry for any mistakes. English is not my native language

https://forum.frank-mankel.org/category/14/rockpro64

Reply
#3
Hi,

thanks for your response!
Is your output of lspci empty as well, when no card is in the slot?
For me, it didn't matter what card was in the slot. It just booted and completely ignored the card, not powering it.

Does anyone know if it is currently a software limitation, what cards are working, or will certain cards never work because of a hardware limitation?
Reply
#4
(08-09-2018, 02:59 AM)seiji Wrote: Hi,

thanks for your response!
Is your output of lspci empty as well, when no card is in the slot?
For me, it didn't matter what card was in the slot. It just booted and completely ignored the card, not powering it.

Does anyone know if it is currently a software limitation, what cards are working, or will certain cards never work because of a hardware limitation?

Hi,
In my case the sata card show up 50% of the time and i got 0 stability.  Some time I boot and my drive is there,some time not AND when it work some time the OS/kernel lost the connexion to the drive.
Reply
#5
I'm having similar problems with 3/4 boards I've tested in my Rock64Pro running Ayufan's minimal image v0.7.9.

Here's the one card I was able to detect successfully, an Intel I350-T4:

Code:
[email protected]:~# dmesg | grep pci
[    0.503668] of_get_named_gpiod_flags: parsed 'gpio' property of node '/vcc3v3-pcie-regulator[0]' - status (0)
[    0.503718] reg-fixed-voltage vcc3v3-pcie-regulator: Looking up vin-supply from device tree
[    0.503757] vcc3v3_pcie: supplied by dc_12v
[    0.503822] vcc3v3_pcie: 3300 mV
[    0.503980] reg-fixed-voltage vcc3v3-pcie-regulator: vcc3v3_pcie supplying 3300000uV
[    1.161570] ehci-pci: EHCI PCI platform driver
[    2.441251] vcc3v3_pcie: disabling
[    2.871941] phy phy-pcie-phy.9: Looking up phy-supply from device tree
[    2.871948] phy phy-pcie-phy.9: Looking up phy-supply property in node /pcie-phy failed
[    2.905026] rockchip-pcie f8000000.pcie: GPIO lookup for consumer ep
[    2.905037] rockchip-pcie f8000000.pcie: using device tree for GPIO lookup
[    2.905068] of_get_named_gpiod_flags: parsed 'ep-gpios' property of node '/[email protected][0]' - status (0)
[    2.905373] rockchip-pcie f8000000.pcie: Looking up vpcie3v3-supply from device tree
[    2.905474] rockchip-pcie f8000000.pcie: Looking up vpcie1v8-supply from device tree
[    2.905484] rockchip-pcie f8000000.pcie: Looking up vpcie1v8-supply property in node /[email protected] failed
[    2.905509] rockchip-pcie f8000000.pcie: no vpcie1v8 regulator found
[    2.908771] rockchip-pcie f8000000.pcie: Looking up vpcie0v9-supply from device tree
[    2.908783] rockchip-pcie f8000000.pcie: Looking up vpcie0v9-supply property in node /[email protected] failed
[    2.908804] rockchip-pcie f8000000.pcie: no vpcie0v9 regulator found
[    2.912068] rockchip-pcie f8000000.pcie: invalid power supply
[    2.972482] PCI host bridge /[email protected] ranges:
[    2.986000] rockchip-pcie f8000000.pcie: PCI host bridge to bus 0000:00
[    2.990385] pci_bus 0000:00: root bus resource [bus 00-1f]
[    2.994575] pci_bus 0000:00: root bus resource [mem 0xfa000000-0xfbdfffff]
[    2.998916] pci_bus 0000:00: root bus resource [io  0x0000-0xfffff] (bus address [0xfbe00000-0xfbefffff])
[    3.003598] pci 0000:00:00.0: [1d87:0100] type 01 class 0x060400
[    3.003706] pci 0000:00:00.0: supports D1
[    3.003714] pci 0000:00:00.0: PME# supported from D0 D1 D3hot
[    3.004059] pci 0000:00:00.0: bridge configuration invalid ([bus 00-00]), reconfiguring
[    3.008725] pci_bus 0000:01: busn_res: can not insert [bus 01-ff] under [bus 00-1f] (conflicts with (null) [bus 00-1f])
[    3.008760] pci 0000:01:00.0: [8086:1521] type 00 class 0x020000
[    3.008809] pci 0000:01:00.0: reg 0x10: [mem 0x00000000-0x000fffff]
[    3.008837] pci 0000:01:00.0: reg 0x1c: [mem 0x00000000-0x00003fff]
[    3.008865] pci 0000:01:00.0: reg 0x30: [mem 0x00000000-0x0007ffff pref]
[    3.008969] pci 0000:01:00.0: PME# supported from D0 D3hot D3cold
[    3.009276] pci 0000:01:00.1: [8086:1521] type 00 class 0x020000
[    3.009319] pci 0000:01:00.1: reg 0x10: [mem 0x00000000-0x000fffff]
[    3.009347] pci 0000:01:00.1: reg 0x1c: [mem 0x00000000-0x00003fff]
[    3.009374] pci 0000:01:00.1: reg 0x30: [mem 0x00000000-0x0007ffff pref]
[    3.009456] pci 0000:01:00.1: PME# supported from D0 D3hot D3cold
[    3.009686] pci 0000:01:00.2: [8086:1521] type 00 class 0x020000
[    3.009726] pci 0000:01:00.2: reg 0x10: [mem 0x00000000-0x000fffff]
[    3.009754] pci 0000:01:00.2: reg 0x1c: [mem 0x00000000-0x00003fff]
[    3.009782] pci 0000:01:00.2: reg 0x30: [mem 0x00000000-0x0007ffff pref]
[    3.009861] pci 0000:01:00.2: PME# supported from D0 D3hot D3cold
[    3.010067] pci 0000:01:00.3: [8086:1521] type 00 class 0x020000
[    3.010107] pci 0000:01:00.3: reg 0x10: [mem 0x00000000-0x000fffff]
[    3.010135] pci 0000:01:00.3: reg 0x1c: [mem 0x00000000-0x00003fff]
[    3.010162] pci 0000:01:00.3: reg 0x30: [mem 0x00000000-0x0007ffff pref]
[    3.010251] pci 0000:01:00.3: PME# supported from D0 D3hot D3cold
[    3.012276] pci_bus 0000:01: busn_res: [bus 01-ff] end is updated to 01
[    3.012315] pci 0000:00:00.0: BAR 8: assigned [mem 0xfa000000-0xfa6fffff]
[    3.016738] pci 0000:01:00.0: BAR 0: assigned [mem 0xfa000000-0xfa0fffff]
[    3.021057] pci 0000:01:00.1: BAR 0: assigned [mem 0xfa100000-0xfa1fffff]
[    3.025324] pci 0000:01:00.2: BAR 0: assigned [mem 0xfa200000-0xfa2fffff]
[    3.029545] pci 0000:01:00.3: BAR 0: assigned [mem 0xfa300000-0xfa3fffff]
[    3.033675] pci 0000:01:00.0: BAR 6: assigned [mem 0xfa400000-0xfa47ffff pref]
[    3.037841] pci 0000:01:00.1: BAR 6: assigned [mem 0xfa480000-0xfa4fffff pref]
[    3.041994] pci 0000:01:00.2: BAR 6: assigned [mem 0xfa500000-0xfa57ffff pref]
[    3.042002] pci 0000:01:00.3: BAR 6: assigned [mem 0xfa580000-0xfa5fffff pref]
[    3.042008] pci 0000:01:00.0: BAR 3: assigned [mem 0xfa600000-0xfa603fff]
[    3.042022] pci 0000:01:00.1: BAR 3: assigned [mem 0xfa604000-0xfa607fff]
[    3.042031] pci 0000:01:00.2: BAR 3: assigned [mem 0xfa608000-0xfa60bfff]
[    3.042039] pci 0000:01:00.3: BAR 3: assigned [mem 0xfa60c000-0xfa60ffff]
[    3.042054] pci 0000:00:00.0: PCI bridge to [bus 01]
[    3.042063] pci 0000:00:00.0:   bridge window [mem 0xfa000000-0xfa6fffff]
[    3.042324] pcieport 0000:00:00.0: enabling device (0000 -> 0002)
[    3.042799] pcieport 0000:00:00.0: Signaling PME through PCIe PME interrupt
[    3.042809] pci 0000:01:00.0: Signaling PME through PCIe PME interrupt
[    3.042817] pci 0000:01:00.1: Signaling PME through PCIe PME interrupt
[    3.042824] pci 0000:01:00.2: Signaling PME through PCIe PME interrupt
[    3.042831] pci 0000:01:00.3: Signaling PME through PCIe PME interrupt
[    3.042845] pcie_pme 0000:00:00.0:pcie01: service driver pcie_pme loaded
[    3.043053] aer 0000:00:00.0:pcie02: service driver aer loaded
[email protected]:~#

And here's dmesg output from a Mellanox ConnectX-2 10GbE card:

Code:
[email protected]:~# dmesg | grep pci
[    0.503629] of_get_named_gpiod_flags: parsed 'gpio' property of node '/vcc3v3-pcie-regulator[0]' - status (0)
[    0.503680] reg-fixed-voltage vcc3v3-pcie-regulator: Looking up vin-supply from device tree
[    0.503719] vcc3v3_pcie: supplied by dc_12v
[    0.503784] vcc3v3_pcie: 3300 mV 
[    0.503942] reg-fixed-voltage vcc3v3-pcie-regulator: vcc3v3_pcie supplying 3300000uV
[    1.160247] ehci-pci: EHCI PCI platform driver
[    2.278195] vcc3v3_pcie: disabling
[    2.584943] phy phy-pcie-phy.9: Looking up phy-supply from device tree
[    2.584980] phy phy-pcie-phy.9: Looking up phy-supply property in node /pcie-phy failed
[    2.587855] rockchip-pcie f8000000.pcie: GPIO lookup for consumer ep
[    2.587872] rockchip-pcie f8000000.pcie: using device tree for GPIO lookup
[    2.587948] of_get_named_gpiod_flags: parsed 'ep-gpios' property of node '/[email protected][0]' - status (0)
[    2.588363] rockchip-pcie f8000000.pcie: Looking up vpcie3v3-supply from device tree
[    2.588791] rockchip-pcie f8000000.pcie: Looking up vpcie1v8-supply from device tree
[    2.588813] rockchip-pcie f8000000.pcie: Looking up vpcie1v8-supply property in node /[email protected] failed
[    2.588855] rockchip-pcie f8000000.pcie: no vpcie1v8 regulator found
[    2.594825] rockchip-pcie f8000000.pcie: Looking up vpcie0v9-supply from device tree
[    2.594853] rockchip-pcie f8000000.pcie: Looking up vpcie0v9-supply property in node /[email protected] failed
[    2.594897] rockchip-pcie f8000000.pcie: no vpcie0v9 regulator found
[    2.601122] rockchip-pcie f8000000.pcie: invalid power supply
[    3.106847] rockchip-pcie f8000000.pcie: PCIe link training gen1 timeout!
[    3.107078] rockchip-pcie: probe of f8000000.pcie failed with error -110

lspcie output is blank on every board besides the Intel nic.
Reply
#6
I am having similar problems using Ayufan's LXDE image v0.7.9
Nothing shows up using lspci
If I look through dmesg I see last line probe of f8000000.pcie failed with error -110
Reply
#7
(08-10-2018, 11:16 AM)mikeD Wrote: I am having similar problems using Ayufan's LXDE image v0.7.9
Nothing shows up using lspci
If I look through dmesg I see last line probe of f8000000.pcie failed with error -110

Yeah, the rockchip-pcie driver doesn't seem to be functioning except in a handful of cases at the moment. I'm going to hook a serial cable up to mine and dump a boot log of the 4.4 and mainline kernels, we'll probably get this fixed faster if we give ayufan something to work with.
Reply
#8
(08-10-2018, 02:12 PM)Arglebargle Wrote:
(08-10-2018, 11:16 AM)mikeD Wrote: I am having similar problems using Ayufan's LXDE image v0.7.9
Nothing shows up using lspci
If I look through dmesg I see last line probe of f8000000.pcie failed with error -110

Yeah, the rockchip-pcie driver doesn't seem to be functioning except in a handful of cases at the moment. I'm going to hook a serial cable up to mine and dump a boot log of the 4.4 and mainline kernels, we'll probably get this fixed faster if we give ayufan something to work with.

You could additionally provide it in this upstream-issue. This is probably a good place to upload the boot log to, since pcie is a chip-feature not specific to the rockpro64-board, right?
Reply
#9
(08-11-2018, 11:14 AM)seiji Wrote:
(08-10-2018, 02:12 PM)Arglebargle Wrote:
(08-10-2018, 11:16 AM)mikeD Wrote: I am having similar problems using Ayufan's LXDE image v0.7.9
Nothing shows up using lspci
If I look through dmesg I see last line probe of f8000000.pcie failed with error -110

Yeah, the rockchip-pcie driver doesn't seem to be functioning except in a handful of cases at the moment. I'm going to hook a serial cable up to mine and dump a boot log of the 4.4 and mainline kernels, we'll probably get this fixed faster if we give ayufan something to work with.

You could additionally provide it in this upstream-issue. This is probably a good place to upload the boot log to, since pcie is a chip-feature not specific to the rockpro64-board, right?

Definitely. Thanks for the link, I wasn't sure who was responsible for the pcie driver.
Reply
#10
I think my PCie is working OK.
The original problem has turned out to be a bad SSD.
I tried another PCIe capture card in the slot and it gets recognized by lspci.
So I think the slot is OK
So am about to order a new SSD and hope that one works.
Hope that has not misled anyone.
Reply


Possibly Related Threads...
Thread Author Replies Views Last Post
  Considering buying and question on the PCIe slot MobileJAD 13 950 08-12-2018, 02:14 PM
Last Post: joe2gaan
  PCIe SSD drive still not working ?? dr_ju_ju 5 205 08-08-2018, 01:08 PM
Last Post: dr_ju_ju
  Rockpro64 with sata pcie card and omv xtract 12 1,920 05-08-2018, 07:29 PM
Last Post: yours_david

Forum Jump:


Users browsing this thread: 1 Guest(s)