Ubuntu desktop 2 logins needed

#52

Nothing

sudo dmesg | grep -E “pcie”

ends with
rockchip-pcie f8000000.pcie: PCIe link training gen1 timeout!
[ 2.173158] rockchip-pcie: probe of f8000000.pcie failed with error -110

Full list is

[    1.489159] of_get_named_gpiod_flags: parsed 'gpio' property of node '/vcc3v3-pcie-regulator[0]' - status (0)
[    1.489201] reg-fixed-voltage vcc3v3-pcie-regulator: Looking up vin-supply from device tree
[    1.489236] vcc3v3_pcie: supplied by vcc3v3_sys
[    1.489697] vcc3v3_pcie: at 3300 mV 
[    1.489857] reg-fixed-voltage vcc3v3-pcie-regulator: vcc3v3_pcie supplying 0uV
[    1.623989] phy phy-pcie-phy.9: Looking up phy-supply from device tree
[    1.623999] phy phy-pcie-phy.9: Looking up phy-supply property in node /pcie-phy failed
[    1.625451] rockchip-pcie f8000000.pcie: GPIO lookup for consumer ep
[    1.625461] rockchip-pcie f8000000.pcie: using device tree for GPIO lookup
[    1.625490] of_get_named_gpiod_flags: parsed 'ep-gpios' property of node '/pcie@f8000000[0]' - status (0)
[    1.625725] rockchip-pcie f8000000.pcie: Looking up vpcie3v3-supply from device tree
[    1.625736] rockchip-pcie f8000000.pcie: Looking up vpcie3v3-supply property in node /pcie@f8000000 failed
[    1.625748] rockchip-pcie f8000000.pcie: no vpcie3v3 regulator found
[    1.626340] rockchip-pcie f8000000.pcie: Looking up vpcie1v8-supply from device tree
[    1.626350] rockchip-pcie f8000000.pcie: Looking up vpcie1v8-supply property in node /pcie@f8000000 failed
[    1.626360] rockchip-pcie f8000000.pcie: no vpcie1v8 regulator found
[    1.626951] rockchip-pcie f8000000.pcie: Looking up vpcie0v9-supply from device tree
[    1.626960] rockchip-pcie f8000000.pcie: Looking up vpcie0v9-supply property in node /pcie@f8000000 failed
[    1.626970] rockchip-pcie f8000000.pcie: no vpcie0v9 regulator found
[    2.172391] rockchip-pcie f8000000.pcie: PCIe link training gen1 timeout!
[    2.173158] rockchip-pcie: probe of f8000000.pcie failed with error -110
#54

Linux linux 4.4.154-83-rockchip-00023-gae7a309 #2 SMP Fri Apr 12 20:04:24 CST 2019 aarch64 aarch64 aarch64 GNU/Linux

lspci -vv | grep -E 'PCI bridge|LnkCap'

Like I say nothing

#57

Yeah its there hw_intfc.conf in boot, but nope nothing

#60

Its already done

#63 
rock@linux:/boot$ lspci
00:00.0 PCI bridge: Fuzhou Rockchip Electronics Co., Ltd Device 0100
01:00.0 SATA controller: ASMedia Technology Inc. ASM1062 Serial ATA Controller (rev 02)

Needed me to disassemble put my glasses on and check the ribbon and everything, never noticed anything and all looks the same but now with not image changes all works.
Must of not had the ribbon cable in or straight … dunno?

#65

Maybe not as managed to work once and on reboot back to how it was.
Must be a doddy connection or dry joint somewhere as for one boot it did turn up working.

Its completely nuts as it works lspci on a about 1 in 3 boots.
Nope got lucky seems much higher just tried 6 times in a run.
But lspci has returned correct 3 times now.

Seems like timings maybe but looking like something hardware wise isn’t happy, but slightly bemused to what.

rock@linux:~$ dmesg | grep pci
[    1.489111] of_get_named_gpiod_flags: parsed 'gpio' property of node '/vcc3v3                 -pcie-regulator[0]' - status (0)
[    1.489153] reg-fixed-voltage vcc3v3-pcie-regulator: Looking up vin-supply fr                 om device tree
[    1.489188] vcc3v3_pcie: supplied by vcc3v3_sys
[    1.489649] vcc3v3_pcie: at 3300 mV
[    1.489808] reg-fixed-voltage vcc3v3-pcie-regulator: vcc3v3_pcie supplying 0u                 V
[    1.623688] phy phy-pcie-phy.9: Looking up phy-supply from device tree
[    1.623698] phy phy-pcie-phy.9: Looking up phy-supply property in node /pcie-                 phy failed
[    1.625172] rockchip-pcie f8000000.pcie: GPIO lookup for consumer ep
[    1.625182] rockchip-pcie f8000000.pcie: using device tree for GPIO lookup
[    1.625211] of_get_named_gpiod_flags: parsed 'ep-gpios' property of node '/pc                 ie@f8000000[0]' - status (0)
[    1.625452] rockchip-pcie f8000000.pcie: Looking up vpcie3v3-supply from devi                 ce tree
[    1.625462] rockchip-pcie f8000000.pcie: Looking up vpcie3v3-supply property                  in node /pcie@f8000000 failed
[    1.625475] rockchip-pcie f8000000.pcie: no vpcie3v3 regulator found
[    1.626067] rockchip-pcie f8000000.pcie: Looking up vpcie1v8-supply from devi                 ce tree
[    1.626077] rockchip-pcie f8000000.pcie: Looking up vpcie1v8-supply property                  in node /pcie@f8000000 failed
[    1.626087] rockchip-pcie f8000000.pcie: no vpcie1v8 regulator found
[    1.626675] rockchip-pcie f8000000.pcie: Looking up vpcie0v9-supply from devi                 ce tree
[    1.626684] rockchip-pcie f8000000.pcie: Looking up vpcie0v9-supply property                  in node /pcie@f8000000 failed
[    1.626694] rockchip-pcie f8000000.pcie: no vpcie0v9 regulator found
[    1.810499] PCI host bridge /pcie@f8000000 ranges:
[    1.812367] rockchip-pcie f8000000.pcie: PCI host bridge to bus 0000:00
[    1.813004] pci_bus 0000:00: root bus resource [bus 00-1f]
[    1.813531] pci_bus 0000:00: root bus resource [mem 0xfa000000-0xfbdfffff]
[    1.814190] pci_bus 0000:00: root bus resource [io  0x0000-0xfffff] (bus addr                 ess [0xfbe00000-0xfbefffff])
[    1.815130] pci 0000:00:00.0: [1d87:0100] type 01 class 0x060400
[    1.815242] pci 0000:00:00.0: supports D1
[    1.815253] pci 0000:00:00.0: PME# supported from D0 D1 D3hot
[    1.815619] pci 0000:00:00.0: bridge configuration invalid ([bus 00-00]), rec                 onfiguring
[    1.816531] pci_bus 0000:01: busn_res: can not insert [bus 01-ff] under [bus                  00-1f] (conflicts with (null) [bus 00-1f])
[    1.816574] pci 0000:01:00.0: [1b21:0612] type 00 class 0x010601
[    1.816628] pci 0000:01:00.0: reg 0x10: initial BAR value 0x00000000 invalid
[    1.817300] pci 0000:01:00.0: reg 0x10: [io  size 0x0008]
[    1.817321] pci 0000:01:00.0: reg 0x14: initial BAR value 0x00000000 invalid
[    1.817993] pci 0000:01:00.0: reg 0x14: [io  size 0x0004]
[    1.818013] pci 0000:01:00.0: reg 0x18: initial BAR value 0x00000000 invalid
[    1.818685] pci 0000:01:00.0: reg 0x18: [io  size 0x0008]
[    1.818705] pci 0000:01:00.0: reg 0x1c: initial BAR value 0x00000000 invalid
[    1.819377] pci 0000:01:00.0: reg 0x1c: [io  size 0x0004]
[    1.819397] pci 0000:01:00.0: reg 0x20: initial BAR value 0x00000000 invalid
[    1.820069] pci 0000:01:00.0: reg 0x20: [io  size 0x0020]
[    1.820090] pci 0000:01:00.0: reg 0x24: [mem 0x00000000-0x000001ff]
[    1.820111] pci 0000:01:00.0: reg 0x30: [mem 0x00000000-0x0000ffff pref]
[    1.828295] pci_bus 0000:01: busn_res: [bus 01-ff] end is updated to 01
[    1.828341] pci 0000:00:00.0: BAR 8: assigned [mem 0xfa000000-0xfa0fffff]
[    1.828996] pci 0000:01:00.0: BAR 6: assigned [mem 0xfa000000-0xfa00ffff pref                 ]
[    1.829687] pci 0000:01:00.0: BAR 5: assigned [mem 0xfa010000-0xfa0101ff]
[    1.830340] pci 0000:01:00.0: BAR 4: no space for [io  size 0x0020]
[    1.830939] pci 0000:01:00.0: BAR 4: failed to assign [io  size 0x0020]
[    1.831570] pci 0000:01:00.0: BAR 0: no space for [io  size 0x0008]
[    1.832169] pci 0000:01:00.0: BAR 0: failed to assign [io  size 0x0008]
[    1.832817] pci 0000:01:00.0: BAR 2: no space for [io  size 0x0008]
[    1.833416] pci 0000:01:00.0: BAR 2: failed to assign [io  size 0x0008]
[    1.834048] pci 0000:01:00.0: BAR 1: no space for [io  size 0x0004]
[    1.834646] pci 0000:01:00.0: BAR 1: failed to assign [io  size 0x0004]
[    1.835278] pci 0000:01:00.0: BAR 3: no space for [io  size 0x0004]
[    1.835877] pci 0000:01:00.0: BAR 3: failed to assign [io  size 0x0004]
[    1.836525] pci 0000:00:00.0: PCI bridge to [bus 01]
[    1.837006] pci 0000:00:00.0:   bridge window [mem 0xfa000000-0xfa0fffff]
[    1.837725] pcieport 0000:00:00.0: enabling device (0000 -> 0002)
[    1.838611] pcieport 0000:00:00.0: Signaling PME through PCIe PME interrupt
[    1.839275] pci 0000:01:00.0: Signaling PME through PCIe PME interrupt
[    1.839901] pcie_pme 0000:00:00.0:pcie01: service driver pcie_pme loaded
[    1.840036] aer 0000:00:00.0:pcie02: service driver aer loaded
[    2.001348] ehci-pci: EHCI PCI platform driver

Took about 5-7 power cycles for it to come back again added the dmesg of when lspci reports its there

#67

There is someone else just posted that I think is the same.

#68

Try to update to the latest u-boot and check if it works.

sudo apt-get install rockpi4b-rk-u-boot-latest
sudo  /usr/local/sbin/rockpi4b_upgrade_bootloader.sh

We enabled the power for the m.2 devices in u-boot, so that the device is ready when the kernel driver probes.

#69

Already have Jack its strange and think maybe something hardware as without firmware change I have had it work, seemed at one stage chance but has seemed to become less and less.
Even did a benchmark but since then it has stubbornly refused with no change and not even the bridge showing.

Auto Mode
        Include fsync in write timing
        O_DIRECT feature enabled
        File size set to 81920 kB
        Record Size 4 kB
        Command line used: iozone -a -e -I -i 0 -i 1 -i 2 -s 80M -r 4k
        Output is in kBytes/sec
        Time Resolution = 0.000001 seconds.
        Processor cache size set to 1024 kBytes.
        Processor cache line size set to 32 bytes.
        File stride size set to 17 * record size.
                                                              random    random     bkwd    record    stride
              kB  reclen    write  rewrite    read    reread    read     write     read   rewrite      read   fwrite frewrite    fread  freread
           81920       4    28607    34861    39915    40103    16139    30980

I have this feeling its a timing thing and the kernel probes too soon or something, I dunno its just giving the above and even bridge is not registering… ?

All I can get now via dmesg | grep pcie

[    1.489159] of_get_named_gpiod_flags: parsed 'gpio' property of node '/vcc3v3-pcie-regulator[0]' - status (0)
[    1.489201] reg-fixed-voltage vcc3v3-pcie-regulator: Looking up vin-supply from device tree
[    1.489236] vcc3v3_pcie: supplied by vcc3v3_sys
[    1.489697] vcc3v3_pcie: at 3300 mV 
[    1.489857] reg-fixed-voltage vcc3v3-pcie-regulator: vcc3v3_pcie supplying 0uV
[    1.623989] phy phy-pcie-phy.9: Looking up phy-supply from device tree
[    1.623999] phy phy-pcie-phy.9: Looking up phy-supply property in node /pcie-phy failed
[    1.625451] rockchip-pcie f8000000.pcie: GPIO lookup for consumer ep
[    1.625461] rockchip-pcie f8000000.pcie: using device tree for GPIO lookup
[    1.625490] of_get_named_gpiod_flags: parsed 'ep-gpios' property of node '/pcie@f8000000[0]' - status (0)
[    1.625725] rockchip-pcie f8000000.pcie: Looking up vpcie3v3-supply from device tree
[    1.625736] rockchip-pcie f8000000.pcie: Looking up vpcie3v3-supply property in node /pcie@f8000000 failed
[    1.625748] rockchip-pcie f8000000.pcie: no vpcie3v3 regulator found
[    1.626340] rockchip-pcie f8000000.pcie: Looking up vpcie1v8-supply from device tree
[    1.626350] rockchip-pcie f8000000.pcie: Looking up vpcie1v8-supply property in node /pcie@f8000000 failed
[    1.626360] rockchip-pcie f8000000.pcie: no vpcie1v8 regulator found
[    1.626951] rockchip-pcie f8000000.pcie: Looking up vpcie0v9-supply from device tree
[    1.626960] rockchip-pcie f8000000.pcie: Looking up vpcie0v9-supply property in node /pcie@f8000000 failed
[    1.626970] rockchip-pcie f8000000.pcie: no vpcie0v9 regulator found
[    2.172391] rockchip-pcie f8000000.pcie: PCIe link training gen1 timeout!
[    2.173158] rockchip-pcie: probe of f8000000.pcie failed with error -110

Obviously lspci shows nothing

#70

Already have Jack its strange and think maybe something hardware as without firmware change I have had it work.
Even did a benchmark when I remembered once.

Auto Mode
        Include fsync in write timing
        O_DIRECT feature enabled
        File size set to 81920 kB
        Record Size 4 kB
        Command line used: iozone -a -e -I -i 0 -i 1 -i 2 -s 80M -r 4k
        Output is in kBytes/sec
        Time Resolution = 0.000001 seconds.
        Processor cache size set to 1024 kBytes.
        Processor cache line size set to 32 bytes.
        File stride size set to 17 * record size.
                                                              random    random     bkwd    record    stride
              kB  reclen    write  rewrite    read    reread    read     write     read   rewrite      read   fwrite frewrite    fread  freread
           81920       4    28607    34861    39915    40103    16139    30980
#71

Check if a warm reboot can always find the device and cold power on/off can not.

#72

Still the same and seems positively deceased

#73

@Jack yeah its dead positively deceased the other Rockpi4 works fine, strange though as it fizzled slowly.
It went from working intermittently on boot to less and less then not at all.

#74

:eyes: (crunching popcorn noises) :clap::clap::clap:
This is the most awesome action unfolding on live TV! A lot is over my head, kinda like watching an action movie with so much stuff flying by that you have to see it again and again.:crazy_face:
@stuartiannaylor Wow! You are wasting no time!
@anon77784915 Excellent brain dump! Thanks for sharing. Do you recommend that everyone follow the steps that you have documented? Or, are these scripts going to become part of an upcoming install package, downloadable from Radxa, GitHub, …?

Thanks for the work both of you are doing. Looking forward to the end product>😎

1 Like
#75

Yeah cevap has done some great scripts and why there isn’t a singular script by radxa rockpi4-update.sh I dunno rather than remembering each package…

The Renesas USB3.0 Host Controller µPD720201/µPD720202 are ok but they only use a single PCIe lane and never checked multiple port access. Like I say they are ok but not great and confusingly the 201 is the 4 port and the 202 is the 2 port.

I haven’t found another yet dunno if they exist the chipsets do but find a pciex2/x4 sata host controller ready avail in m.2 format so far has escaped me.

Also USB OTG Gadget mode seems to be very much locked to a single host which is a shame really as with g_ether you could essentially aggregate x2, but its kernel and the module and of the scope of the RockPi4.

The size and form factor of the rockpi4 and m.2 is brilliant but availability of product isn’t so great, but quite a few boards have adopted it and maybe fingers crossed more might be on its way.

I will not have product but likely will lead to some tutorial/articles on OpenMediaVault/AnsibleNas with a rockpi4 and the marvel 9235 looks like the only real solution.
The 9230 prob needs setup but without bios access or a linux version of the Marvell Storage Utility which is just a software version of the bios setup I don’t think it will work and might not with.

Again the lesser embedded 9235 has the higher chip number but yeah that looks like the beasty to go for if you want software RAID.
I am going to hang 4x 120gb Integral p5 SSDs are @ £17 with free delivery they are pretty cheap and already have one here.

So I will have some benchmarks on the way and also g_ether iperf and maybe some eth port aggregation trials.

There is a 2 port single header version that is on a darker board and may be better quality than the one I have. It does seem to have more components and it looks that way but could well offer the same perf but less is shared on a single lane.

I am not going to bother though as the single lane sata was vastly faster and hoping the 2 lane Marvel is even more so.

As for product you can get a really cheap 5 bay stick your RockPi4 on top and have one of the cheapest most capable NAS systems available. £16

That is where I am headed but only a tutorial/how-to and some benchmarks of what to expect.

#76

You are truly a man on an honorable quest. I’m pretty content with booting from eMMC and storing everything on NVMe, including a backup image accessible from microSD.

On the other hand, I’m in the middle of modifying an eleduino RPi aluminum case to house 2 x 12VDC Noctura 40 x10 mm fans with a PWM controller, power switch, and 5.5 x 2.1 mm chassis jack. The fans will hang underneath an aluminum plate, mounted 1/8" away from the heatsink, to provide even airflow away from the center. With vented side panels, it forms an intake and exhaust manifold. The SSD is just below the fans, so that incoming airflow passes over the SSD. Sound familiar?

Parts arrive this week, along with a soldering station/12VDC PSU, magnifying headset, USB-C to 5.5 mm barrel adapters, and power switches (which we had previously discussed). I’m not just taking notes.:sunglasses:

2 Likes
#77

Yeah that is equally valid, there are prob going to be 2 distinct uses of the RockPi4 one being a MicroPC and the other being a MicroServer.

That is what has rekindled my interest as having a pcie bus with reasonable entry level computing power is a watershed with my experiment with Arm SBC as it really increases choice of use.
Oooh! 2x 40 Noctura hey, you went posh! :slight_smile:

I keep looking at that heatsink though and wondering if 2 legs should go to the posts and the eMMC & PCIe ribbon should be exposed but hey ho.
You going to stick some thermal pads on the mem chips? Maybe even some heatsink through holes that might push some air?

I noticed on the Armbian forum they have found a stable OC of just less than 2.0Ghz for the big cores and the little should do 1.5Ghz maybe higher.
Converting and editing the DTS/DTO is actually quite easy and with the extra active cooling, should be more about stability than overheat.
Been meaning to do the same with OC with article/howtos/scripts got as far as noticing that the CPUs don’t seem to scale and are fixed frequency and never explored any further. I did convert the dtbo and stared at it blankly for a while.
I have a RockPi4B-4gb with a dead PCIe bus that might get pushed as a sacrificial lamb :slight_smile:
PS the rev 1.4 boards have onboard flash (spi nor) that with a soldering iron us 1.3 owners will be able to upgrade after Raxda provide an image and utility.

I ordered direct from the iocrest aliexpress shop and should have a 4 port that works to benchmark.

1 Like
#78

You’re probably right about the uses. Still debating that one, too.
Yeah, ExplainingComputers likes Noctura fans, so I took the bait. Got a thing about not wasting time and money on doing things half-a$$ed. What’s the point unless I can be proud of the end result? That’s also the reason for the SMT soldering gear, etc.

I’ve ended up making a ‘bump-out’ to cover the FPC ribbon. So the case looks like it has a booty in the back. lol

Will need to test the airflow to determine whether additional protection will be needed for the memory chips. The eleduino case comes with a 5 vdc fan above the board, but I’m hoping that it won’t be necessary. Want to keep the GPIO header available for a ribbon cable.

Pretty soon, the Rock Pi will be all dressed up with nowhere to go. Then, I’ll have no excuse for not diving into Linux.:sunglasses:

1 Like
#80

Dear All,

I still don’t know how to solve the captioned issue “need login twice”, maybe I miss the suggestion in this thread even I’ve gone through many times.

Thanks in advance :slight_smile:

#82

Thanks, but how can I check it? I just look at
$ ls /etc/init/
anacron.conf lightdm.conf whoopsie.conf
none of these files have ‘startx’