Ubuntu desktop 2 logins needed

I think with the heatsink I am just going to get 4 more 20mm Brass Hex posts and put a small blower there as like the m.2 board on top.
Heat sink has holes and presume they are tapped the same as the other side

I think we all got 2 ribbon cables and a confused expression.
Mine is already turning into a FrankenPi :slight_smile:

But with it being on the bottom its sitting on a fairly non thermally conductive wooden table.
I have a 3.5" & 2.5" SSD to a 2 port sata m.2 card to try out tomorrow that is powered via the RockPi4 & 12V supply, so it is never going to be eloquent in looks.
The pillars I just got are 25mm with a 40mm fan than is only 10mm width, the heat sink isn’t that hot, it gets quite toasty but not too hot to touch.
I presume you can mangle the DTS as 2.0Ghz should be possible on the big cores.
"dual 1.8GHz Cortex-72 and qual 1.4GHz Cortex-A53 "

The 1.4 you saw was prob little core speed.

You can check with

sudo watch -n 1  cat /sys/devices/system/cpu/cpu*/cpufreq/cpuinfo_cur_freq
1 Like

I will test it works struggled to find m.2 sata cards at a decent price so the 2 port is just a test.

1 Like

PS the chromium dependency is for http://ftp.de.debian.org/debian/pool/main/libj/libjpeg-turbo/libjpeg62-turbo_1.5.1-2_arm64.deb

sudo dpkg -i libjpeg62-turbo_1.5.1-2_arm64.deb was all it needed

1 Like

The infor you are posting is top quality with great scripts, but just some feedback.
Making raid across eMMc and M.2 just hobnails the M.2 to the slower eMMc.
It would be great if Radxa could make a really cheap and really usefull 128/256mb eMMC module as soldering on nand flash for SPI for a purchase is severe and essentially breaks warranty.

I really love the assembled form factor of the RockPi4, I actually like the heatsink, m.2 extender and think its just brilliant when finished, but for Dev and playing the ribbon on the m.2 and the eMMc under the heatsink can be a proper pain in the ass.

@anon77784915 you got any ideas on how to access SD or eMMc without starting to disassemble there prob is but generally I am used just grabbing the Micro SD putting in a reader and flashing whatever I am playing with.

@raxda you guys got any chance of sourcing a 4 port m.2 sata?

I am not having much look either you any ideas how to force PCIe gen2 training?

LVM is probably an ecumenical matter you any ideas how to force pcie gen2?

Already have but seems to do little both dto & dts are set to gen2

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

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

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

Its already done

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?

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

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

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.

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

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

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

Still the same and seems positively deceased