Hello Christopher, thank you for your help and feedback. I finish rebuild my raid, so i perform some checks.
Answers below. On Sun, 19 Nov 2023 13:19:18 +0100 Christopher Zimmermann <chr...@openbsd.org> wrote: > On Sun, Nov 19, 2023 at 02:49:33AM +0100, Olivier Burelli wrote: > >Questions : > > > >1. In both cases: > > _ emmc has issue: Card did not respond to voltage select! : -110 > > > > I see this too on a rk3399 RockPro64, but the emmc is still working > just fine. I broke my rockpro64 (usb2... and can not install install openbsd anymore on it, so i bought this board and confuse dwqe a dwge on RP64...) --> for this board (RP64), i remember that dtb was mandatory to write on emmc. > > > _ if i use rockchip/rk3566-quartz64-a.dtb: > > _ freeze during installation > > Does it really freeze or is it just reeeeeaaaaaaaaaaaaly slow ? > Because I had problems with a JMicron ahci on rk3399 not delivering > interupts, which just made it ridiculously slow: > > https://www.mail-archive.com/arm@openbsd.org/msg02336.html > In fact i understood that /usr/local/share/u-boot/quartz64-a-rk3566/u-boot-rockchip.bin integrates device tree blob. So it's really freeze at this stage of the openbsd kernel : dwpcie0: can't initialize hardware sdmmc1: can't enable card sdmmc2: can't enable card umass0 at uhub2 port 1 configuration 1 interface 0 "Lexar USB Flash Drive" rev 2.10/11.00 addr 2 umass0: using SCSI over Bulk-Only scsibus0 at umass0: 2 targets, initiator 0 sd0 at scsibus0 targ 1 lun 0: <Lexar, USB Flash Drive, 1100> removable serial.05dca838E89K3FOCINZ7 sd0: 7634MB, 512 bytes/sector, 15634432 sectors softraid0 at root scsibus1 at softraid0: 256 targets root on rd0a swap on rd0b dump on rd0b WARNING: bad clock chip time WARNING: CHECK AND RESET THE DATE! cpu0: regulator not implemented ��3���0��\��� At the first stage of u-boot i saw this error : WARNING: No OPTEE provided by BL2 boot loader, Booting device without OPTEE initialization. SMC`s destined for OPTEE will return SMC_UNK ERROR: Error initializing runtime service opteed_fast At second stage of u-boot for emmc : MMC: mmc@fe2b0000: 1, mmc@fe2c0000: 2, mmc@fe310000: 0 in sub system mmc : => mmcinfo Device: mmc@fe310000 Manufacturer ID: 45 OEM: 0 Name: DA4064 Bus Speed: 52000000 Mode: MMC DDR52 (52MHz) Rd Block Len: 512 MMC version 5.1 High Capacity: Yes Capacity: 58.2 GiB Bus Width: 8-bit DDR Erase Group Size: 512 KiB HC WP Group Size: 8 MiB User Capacity: 58.2 GiB WRREL Boot Capacity: 4 MiB ENH RPMB Capacity: 16 MiB ENH Boot area 0 is not write protected Boot area 1 is not write protected I performed usb start to find the flashdisk and boot on it. My understandings, u-boot do not provide the emmc informations to the openbsd kernel. > I could work around it by disabling msi interrupts. In the end I > switched to using a better supported ahci controller (ASMedia ASM1061) > > > Does the dtb has to be used ? > > Yes, a dtb is needed. > > > Does emmc is currently supported ? > > Yes, according to https://www.openbsd.org/arm64.html it is supported. > > > >2. Once installation done on the sdcard: > > _ issue with the link of kernel after restart > > I'm not understanding what you are trying to say here. I talked about ld.so libc lybcrypto reordering. Not happened anymore in the last install. > > > _ no ethernet connectivity : regarding this article: > > https://beta.pine64.org/documentation/Quartz64/Troubleshooting/ > > > > Does this issue is due to CONFIG_MOTORCOMM_PHY not set to y ? > > No. The Motorcamm Phy is configured according to your dmesg: > > dwqe0 at mainbus0 gmac 1: rev 0x51, address da:c6:99:15:68:ef > ytphy0 at dwqe0 phy 0: YT8511 10/100/1000 PHY > > ytphy0 is the Motorcamm Phy. > Here i checked my network, i tried to force 100baseTX also... no connectivity. When i tried to ping my gateway... Host is unreachable. quartz# ifconfig dwqe0 media dwqe0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500 lladdr da:c6:99:15:68:ef index 1 priority 0 llprio 3 groups: egress media: Ethernet autoselect (1000baseT full-duplex) status: active supported media: media none media 10baseT media 10baseT mediaopt full-duplex media 100baseTX media 100baseTX mediaopt full-duplex media 1000baseT mediaopt full-duplex media autoselect inet xxx.xxx.xxx.xxx netmask 0xffffff00 broadcast xxx.xxx.xxx.255 > > Hope this helps, > > Christopher Thank you. I am lost, i will try to boot linux and check the hardware... on this plateforme :)
