Slackware - ARM This forum is for the discussion of Slackware ARM. |
Notices |
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
|
|
|
02-17-2021, 11:16 AM
|
#1
|
Senior Member
Registered: Aug 2014
Posts: 2,063
Rep:
|
Quartz64 RK3566 (slarm64, aarch64)
information board: - SoC – Rockchip RK3566 quad-core Cortex-A55 processor up to 1.8 GHz with Arm Mali-G52 GPU supporting OpenGL ES 1.1/2.0/3.2, OpenCL 2.0, Vulkan 1.1, 0.8 TOPS NPU for AI acceleration
- System Memory – 2GB to 8GB LPDDR4
- Storage
- SPI Flash
- optional eMMC module from 16GB up to 128GB capacity
- bootable SDHC/SDXC MicroSD card up to 256GB (or is it 2TB?)
- SATA 3.0 port (multiplexed with USB 3.0)
- Video Output / Display Interfaces
- HDMI 2.0a up to 4Kp60
- 4-lane eDP up to 2560×1600 @ 60Hz
- 4-lane MIPI DSI up to 1440p
- SPI Touch Panel Port, SPI with interrupt
- Camera I/F – 4-lane MIPI CSI camera Interface up to 8MP
- Networking
- 10/100/1000Mbps Gigabit Ethernet RJ45 port
- Optional WiFi 802.11 b/g/n/ac with Bluetooth 5.0 via header via SDIO 3.0 and UART
- USB – 3x USB 2.0 host ports, 1xUSB 3.0 host port
- Expansion
- 2x 10-pin GPIO header
- PCIe x4 open-ended slot with PCIe 2.0 x1 interface
- Misc – RTC battery connector
- Power Supply
- 12V/3A DC input via 5.5/2.1mm DC barrel jack
- VBAT Lithium Battery Connector with temperature sensor input
- Dimensions – 133 x 80 x 19mm
|
|
|
04-16-2021, 02:21 AM
|
#2
|
Senior Member
Registered: Aug 2014
Posts: 2,063
Original Poster
Rep:
|
Quartz64 Model B
Quartz64 Model B
Specifications: - SoC – Rockchip RK3566 quad-core Cortex-A55 processor up to 1.8 GHz with Arm Mali-G52 GPU supporting OpenGL ES 1.1/2.0/3.2, OpenCL 2.0, Vulkan 1.1, 0.8 TOPS NPU for AI acceleration
- System Memory – 2GB to 8GB LPDDR4
- Storage
128 Mbit SPI Flash
optional eMMC module from 16GB up to 128GB capacity
bootable SDHC/SDXC MicroSD card up to 2TB
- Video Output / Display Interfaces
HDMI 2.0a up to 4Kp60
2-lane MIPI DSI up to 1080p
- Camera I/F – 2-lane MIPI CSI camera Interface up to 5MP
- Audio – 3.5mm audio jack
- Networking
10/100/1000Mbps Gigabit Ethernet RJ45 port
WiFi & Bluetooth via either a Realtek Bluetooth/WiFi chipset or Bouffalo BL602 module (Note: two models of the board will be provided)
- USB – 2x USB 2.0 host ports, 1xUSB 3.0 host port
- Expansion
40-pin GPIO header
M.2 PCIe socket
- Misc – RTC battery connector, IR Tx/Rx
- Power Supply – 5V/3A DC input via 3.5/1.35mm DC barrel jack
- Dimensions – 85 x 56 x 18.8mm
|
|
|
06-15-2021, 03:05 PM
|
#3
|
Senior Member
Registered: Aug 2014
Posts: 2,063
Original Poster
Rep:
|
sale of Quartz64 model A started.
|
|
|
07-07-2021, 07:06 PM
|
#4
|
Member
Registered: Mar 2019
Distribution: Slackware
Posts: 301
Rep:
|
Just curious, have you been able to build any images for this board yet? I have been contemplating getting a Model A to tinker with (now that the Pinebook is stable).
|
|
|
07-08-2021, 11:16 AM
|
#5
|
Senior Member
Registered: Aug 2014
Posts: 2,063
Original Poster
Rep:
|
model A acquired on the way after receiving I will start full integration into images build kit
|
|
1 members found this post helpful.
|
07-17-2021, 10:01 AM
|
#6
|
Senior Member
Registered: Aug 2014
Posts: 2,063
Original Poster
Rep:
|
start testing boot:
Code:
U-Boot SPL board init
U-Boot SPL 2017.09-ga1f6fc00a0-210413 #ldq (Apr 13 2021 - 11:35:00)
unknown raw ID phN
unrecognized JEDEC id bytes: 00, 00, 00
Trying to boot from MMC2
No misc partition
## Verified-boot: 0
## Checking atf-1 0x00040000 ... sha256+ OK
## Checking uboot 0x00a00000 ... sha256+ OK
## Checking fdt 0x00b21290 ... sha256+ OK
## Checking atf-2 0xfdcc9000 ... sha256+ OK
## Checking atf-3 0xfdcd0000 ... sha256+ OK
## Checking optee 0x08400000 ... sha256+ OK
Jumping to U-Boot(0x00a00000) via ARM Trusted Firmware(0x00040000)
Total: 258.14 ms
INFO: Preloader serial: 2
NOTICE: BL31: v2.3():v2.3-135-gcda1658bc-dirty:xsf
NOTICE: BL31: Built : 19:32:20, Jun 2 2021
INFO: GICv3 without legacy support detected.
INFO: ARM GICv3 driver initialized in EL3
INFO: pmu v1 is valid
INFO: dfs DDR fsp_param[0].freq_mhz= 1056MHz
INFO: dfs DDR fsp_param[1].freq_mhz= 324MHz
INFO: dfs DDR fsp_param[2].freq_mhz= 528MHz
INFO: dfs DDR fsp_param[3].freq_mhz= 780MHz
INFO: Using opteed sec cpu_context!
INFO: boot cpu mask: 0
INFO: BL31: Initializing runtime services
INFO: BL31: Initializing BL32
I/TC:
I/TC: Start rockchip platform init
I/TC: Rockchip release version: 1.0
I/TC: OP-TEE version: 3.6.0-307-g0b06ae94 #1 Fri May 7 01:52:27 UTC 2021 aarch64
I/TC: Initialized
INFO: BL31: Preparing for EL3 exit to normal world
INFO: Entry point address = 0xa00000
INFO: SPSR = 0x3c9
U-Boot 2017.09 (Jun 15 2021 - 16:55:48 +0000)
Model: Pine64 RK3566 Quartz64 Board
PreSerial: 2, raw, 0xfe660000
DRAM: 7.7 GiB
Sysmem: init
Relocation Offset: ed39f000, fdt: eb9f9f78
no mmc device at slot 1
dwmmc@fe2b0000: 1 (SD), dwmmc@fe2c0000: 2, sdhci@fe310000: 0
Bootdev(atags): mmc 1
MMC1: Legacy, 50Mhz
PartType: EFI
No misc partition
boot mode: None
FIT: No boot partition
No resource partition
Failed to load DTB
Failed to get kernel dtb, ret=-19
io-domain: OK
** Unable to use mmc 1:3 for loading the env **
Using default environment
Model: Pine64 RK3566 Quartz64 Board
rockchip_set_serialno: could not find efuse/otp device
CLK: (sync kernel. arm: enter 816000 KHz, init 816000 KHz, kernel 0N/A)
apll 816000 KHz
dpll 528000 KHz
gpll 1188000 KHz
cpll 1000000 KHz
npll 24000 KHz
vpll 24000 KHz
hpll 24000 KHz
ppll 100000 KHz
armclk 816000 KHz
aclk_bus 150000 KHz
pclk_bus 50000 KHz
aclk_top_high 300000 KHz
aclk_top_low 200000 KHz
hclk_top 150000 KHz
pclk_top 50000 KHz
aclk_perimid 300000 KHz
hclk_perimid 150000 KHz
pclk_pmu 50000 KHz
Net: clk_get_by_name(master_bus) failed: -22eqos_probe_resources() failed: -22No ethernet found.
Hit key to stop autoboot('CTRL+C'): 0
## Booting FIT Image FIT: No boot partition
FIT: No FIT image
Could not find misc partition
ANDROID: reboot reason: "(none)"
optee api revision: 2.0
TEEC: Waring: Could not find security partition
Not AVB images, AVB skip
android_image_load_by_partname: Can't find part: boot
Android image load failed
Android boot failed, error -1.
switch to partitions #0, OK
mmc1 is current device
Scanning mmc 1:2...
Found /extlinux/extlinux.conf
Retrieving file: /extlinux/extlinux.conf
reading /extlinux/extlinux.conf
388 bytes read in 4 ms (94.7 KiB/s)
1: Slarm64
Retrieving file: /Image
reading /Image
29239808 bytes read in 2429 ms (11.5 MiB/s)
append: root=/dev/mmcblk0p3 ro earlycon=uart8250,mmio32,0xfe660000 console=tty1 console=ttyS2,1500000n8 verbosity=4
Retrieving file: /dtb/rk3566-quartz64a.dtb
reading /dtb/rk3566-quartz64a.dtb
75961 bytes read in 12 ms (6 MiB/s)
Fdt Ramdisk skip relocation
## Flattened Device Tree blob at 0x0a100000
Booting using the fdt blob at 0x0a100000
'reserved-memory' ramoops@110000: addr=110000 size=f0000
Using Device Tree in place at 000000000a100000, end 000000000a1158b8
Adding bank: 0x00200000 - 0x08400000 (size: 0x08200000)
Adding bank: 0x09400000 - 0xf0000000 (size: 0xe6c00000)
Adding bank: 0x100000000 - 0x200000000 (size: 0x100000000)
Total: 2824.447 ms
Starting kernel ...
Last edited by sndwvs; 07-17-2021 at 10:05 AM.
|
|
1 members found this post helpful.
|
07-18-2021, 02:58 AM
|
#7
|
Senior Member
Registered: Aug 2014
Posts: 2,063
Original Poster
Rep:
|
|
|
1 members found this post helpful.
|
08-18-2021, 09:44 AM
|
#8
|
Member
Registered: Mar 2019
Distribution: Slackware
Posts: 301
Rep:
|
Quote:
Originally Posted by sndwvs
|
I have been testing out this image, and it works surprisingly well. There are obvious hardware support issues, but I think those are all upstream. I have been using it to build all of my other images, actually.
I was trying to build a fresh image to track kernel changes, but I am running into kernel config issues with both legacy and next kernels. Legacy does not finish building, and next is stuck at 5.13.0-rc4. Maybe a version bump? Just curious, thanks for everything.
|
|
|
08-18-2021, 10:47 AM
|
#9
|
Senior Member
Registered: Aug 2014
Posts: 2,063
Original Poster
Rep:
|
Legacy has not yet tested, 5.13.0-rc4 should already be switched to 5.14.y.
|
|
1 members found this post helpful.
|
08-18-2021, 09:28 PM
|
#10
|
Member
Registered: Mar 2019
Distribution: Slackware
Posts: 301
Rep:
|
Ah, I see what is going on. In config/sources/rk3568.conf, I changed
Code:
KERNEL_BRANCH="quartz64::"
to
Code:
KERNEL_BRANCH="quartz64-5.14::"
as per https://gitlab.com/pgwipeout/linux-next
It is building now, we shall see how it goes.
Thanks for the tip.
|
|
|
08-20-2021, 11:29 PM
|
#11
|
Senior Member
Registered: Aug 2014
Posts: 2,063
Original Poster
Rep:
|
|
|
1 members found this post helpful.
|
09-27-2021, 01:44 PM
|
#12
|
Member
Registered: Mar 2019
Distribution: Slackware
Posts: 301
Rep:
|
u-boot troubles - solved
I have been having troubles getting u-boot to build for this image. I have tried changing sources and branches, and no matter what I do I keep getting stuck at this point;
Code:
[...]
CC drivers/video/drm/drm_dp_helper.o
CC lib/avb/libavb/avb_sha256.o
LD fs/fat/built-in.o
CC fs/fs_internal.o
CC net/tftp.o
CC lib/avb/libavb/avb_sha512.o
CC drivers/video/drm/dw_mipi_dsi.o
LD fs/built-in.o
CC lib/avb/libavb/avb_sysdeps_posix.o
CC lib/avb/rk_avb_user/rk_avb_ops_user.o
CC lib/avb/rk_avb_user/rk_ab_ops_user.o
CC lib/avb/libavb/avb_slot_verify.o
LD net/built-in.o
CC drivers/video/drm/rockchip_dw_hdmi.o
CC drivers/video/drm/dw_hdmi.o
LD lib/avb/rk_avb_user/built-in.o
lib/avb/libavb/avb_slot_verify.c: In function ‘load_and_verify_vbmeta’:
lib/avb/libavb/avb_slot_verify.c:476:40: error: ‘found’ may be used uninitialized in this function [-Werror=maybe-uninitialized]
476 | loaded_partition->partition_name = avb_strdup(found);
| ^~~~~~~~~~~~~~~~~
lib/avb/libavb/avb_slot_verify.c:299:15: note: ‘found’ was declared here
299 | const char* found;
| ^~~~~
CC test/dm/cmd_dm.o
CC drivers/video/drm/inno_mipi_phy.o
LD test/dm/built-in.o
CC drivers/video/drm/inno_video_combo_phy.o
CC drivers/video/drm/analogix_dp.o
CC drivers/video/drm/analogix_dp_reg.o
cc1: all warnings being treated as errors
make[2]: *** [scripts/Makefile.build:280: lib/avb/libavb/avb_slot_verify.o] Error 1
make[1]: *** [scripts/Makefile.build:425: lib/avb/libavb] Error 2
make: *** [Makefile:1305: lib] Error 2
make: *** Waiting for unfinished jobs....
CC drivers/video/drm/rockchip_lvds.o
CC drivers/video/drm/rockchip_panel.o
LD drivers/video/drm/built-in.o
LD drivers/video/built-in.o
LD drivers/built-in.o
I have seen in other posts (pine64 forum, for example) that some people are getting this error even though the build completes. For me, this error is fatal, the build stops here. Is this a GCC version issue, or something like that? Searching around has not been very fruitful, yet.
Oh, by the way, I am still using the 5.13.0-rc4-next-20210603 image. All of the others I have downloaded and tried have had either networking (next) or boot (legacy) issues that prevented me from using them. I have yet to build an image of my own successfully for this board. Hopefully if I can get past this u-boot issue, I can start testing images.
Just FYI. Thanks much.
UPDATE: The patch mentioned in this post fixed the problem for me. It is probably worth adding to the patch directory.
Last edited by shelldweller; 09-28-2021 at 01:23 AM.
Reason: Added patch info
|
|
|
10-01-2021, 07:45 PM
|
#13
|
Senior Member
Registered: Aug 2014
Posts: 2,063
Original Poster
Rep:
|
shelldweller thanks,
I have not seen this error since I compiled gcc 10, updating gcc to 11 got the same error, here is the fix.
|
|
1 members found this post helpful.
|
10-08-2021, 11:34 PM
|
#14
|
Senior Member
Registered: Aug 2014
Posts: 2,063
Original Poster
Rep:
|
kernel 4.19.209
Working
slarm64-current-aarch64-server-quartz64-4.19.209-build-20211008.img.zst
slarm64-current-aarch64-server-quartz64-4.19.209-build-20211008.img.zst.sha256
slarm64-current-aarch64-xfce-quartz64-4.19.209-build-20211008.img.zst
slarm64-current-aarch64-xfce-quartz64-4.19.209-build-20211008.img.zst.sha256
Code:
[ 0.000000] Booting Linux on physical CPU 0x0000000000 [0x412fd050]
[ 0.000000] Linux version 4.19.209 (root@slarm64-dev) (gcc version 11.2.0 (GCC), GNU ld version 2.37-slack15) #1 SMP Fri Oct 8 22:30:38 UTC 2021
[ 0.000000] Machine model: Pine64 RK3566 Quartz64-A Board
[ 0.000000] earlycon: uart8250 at MMIO32 0x00000000fe660000 (options '')
[ 0.000000] Kernel command line: root=/dev/mmcblk0p3 ro rootwait rootfstype=ext4 init=/sbin/init loglevel=4 earlycon=uart8250,mmio32,0xfe660000 console=tty1 console=ttyFIQ0,1500000n8
[ 0.122453] SCSI subsystem initialized
[ 0.122511] libata version 3.00 loaded.
[ 0.264745] rockchip-csi2-dphy csi2-dphy0: csi2 dphy0 probe successfully!
[ 0.264912] rockchip-csi2-dphy-hw fe870000.csi2-dphy-hw: csi2 dphy hw probe successfully!
[ 0.267406] phy phy-fe8a0000.usb2-phy.0: Looking up phy-supply from device tree
[ 0.267430] vcc5v0_host: could not add device link phy-fe8a0000.usb2-phy.0 err -2
[ 0.267488] phy phy-fe8a0000.usb2-phy.0: Linked as a consumer to regulator.1
[ 0.267630] phy phy-fe8a0000.usb2-phy.1: Looking up phy-supply from device tree
[ 0.267649] vcc5v0_host: could not add device link phy-fe8a0000.usb2-phy.1 err -2
[ 0.267699] phy phy-fe8a0000.usb2-phy.1: Linked as a consumer to regulator.1
[ 0.267808] phy phy-fe8a0000.usb2-phy.1: Looking up vbus-supply from device tree
[ 0.267822] phy phy-fe8a0000.usb2-phy.1: Looking up vbus-supply property in node /usb2-phy@fe8a0000/otg-port failed
[ 0.267840] phy phy-fe8a0000.usb2-phy.1: No vbus specified for otg port
[ 0.269574] extcon extcon1: failed to create extcon usb2-phy link
[ 0.269689] phy phy-fe8b0000.usb2-phy.2: Looking up phy-supply from device tree
[ 0.269718] vcc5v0_host: could not add device link phy-fe8b0000.usb2-phy.2 err -2
[ 0.269800] phy phy-fe8b0000.usb2-phy.2: Linked as a consumer to regulator.1
[ 0.269942] phy phy-fe8b0000.usb2-phy.3: Looking up phy-supply from device tree
[ 0.269961] vcc5v0_host: could not add device link phy-fe8b0000.usb2-phy.3 err -2
[ 0.270013] phy phy-fe8b0000.usb2-phy.3: Linked as a consumer to regulator.1
[ 0.270121] phy phy-fe8b0000.usb2-phy.3: Looking up vbus-supply from device tree
[ 0.270135] phy phy-fe8b0000.usb2-phy.3: Looking up vbus-supply property in node /usb2-phy@fe8b0000/otg-port failed
[ 0.270153] phy phy-fe8b0000.usb2-phy.3: No vbus specified for otg port
[ 0.272538] phy phy-fe850000.video-phy.4: Looking up phy-supply from device tree
[ 0.272554] phy phy-fe850000.video-phy.4: Looking up phy-supply property in node /video-phy@fe850000 failed
[ 0.278664] rk-pcie 3c0000000.pcie: Looking up vpcie3v3-supply from device tree
[ 0.278694] reg-fixed-voltage vcc3v3_pcie_p: Looking up vin-supply from device tree
[ 0.279293] pwm-backlight backlight: Looking up power-supply from device tree
[ 0.279308] pwm-backlight backlight: Looking up power-supply property in node /backlight failed
[ 0.279326] pwm-backlight backlight: backlight supply power not found, using dummy regulator
[ 0.279418] pwm-backlight backlight: Linked as a consumer to regulator.0
[ 0.279747] mpp_service mpp-srv: 7cf7399dd author: Stephen 2021-08-23 arm64: dts: rk3568-rock3a: enable pwm8 for fan
[ 0.279754] mpp_service mpp-srv: probe start
[ 0.280952] iommu: Adding device fdf40000.rkvenc to group 3
[ 0.280981] mpp_rkvenc fdf40000.rkvenc: Linked as a consumer to fdf40f00.iommu
[ 0.281243] mpp_rkvenc fdf40000.rkvenc: probing start
[ 0.281840] mpp_rkvenc fdf40000.rkvenc: Looking up venc-supply from device tree
[ 0.281856] mpp_rkvenc fdf40000.rkvenc: Looking up venc-supply property in node /rkvenc@fdf40000 failed
[ 0.281875] mpp_rkvenc fdf40000.rkvenc: no regulator, devfreq is disabled
[ 0.282360] mpp_rkvenc fdf40000.rkvenc: probing finish
[ 0.283723] iommu: Adding device fdea0400.vdpu to group 0
[ 0.283753] mpp_vdpu2 fdea0400.vdpu: Linked as a consumer to fdea0800.iommu
[ 0.283976] mpp_vdpu2 fdea0400.vdpu: probe device
[ 0.284756] mpp_vdpu2 fdea0400.vdpu: probing finish
[ 0.285459] iommu: Adding device fdee0000.vepu to group 2
[ 0.285488] mpp_vepu2 fdee0000.vepu: Linked as a consumer to fdee0800.iommu
[ 0.285732] mpp_vepu2 fdee0000.vepu: probe device
[ 0.286507] mpp_vepu2 fdee0000.vepu: probing finish
[ 0.287501] iommu: Adding device fded0000.jpegd to group 1
[ 0.287529] mpp_jpgdec fded0000.jpegd: Linked as a consumer to fded0480.iommu
[ 0.287714] mpp_jpgdec fded0000.jpegd: probe device
[ 0.288499] mpp_jpgdec fded0000.jpegd: probing finish
[ 0.289190] iommu: Adding device fdf80200.rkvdec to group 4
[ 0.289219] mpp_rkvdec2 fdf80200.rkvdec: Linked as a consumer to fdf80800.iommu
[ 0.289526] mpp_rkvdec2 fdf80200.rkvdec: probing start
[ 0.290181] mpp_rkvdec2 fdf80200.rkvdec: shared_niu_a is not found!
[ 0.290241] rkvdec2_init:875: No niu aclk reset resource define
[ 0.290273] mpp_rkvdec2 fdf80200.rkvdec: shared_niu_h is not found!
[ 0.290299] rkvdec2_init:878: No niu hclk reset resource define
[ 0.290775] mpp_rkvdec2 fdf80200.rkvdec: sram_start 0x00000000fdcc0000
[ 0.290784] mpp_rkvdec2 fdf80200.rkvdec: rcb_iova 0x0000000010000000
[ 0.290791] mpp_rkvdec2 fdf80200.rkvdec: sram_size 45056
[ 0.290798] mpp_rkvdec2 fdf80200.rkvdec: rcb_size 65536
[ 0.290807] mpp_rkvdec2 fdf80200.rkvdec: min_width 512
[ 0.290839] mpp_rkvdec2 fdf80200.rkvdec: probing finish
[ 0.291252] mpp_service mpp-srv: probe success
[ 0.299170] dma-pl330 fe530000.dmac: Loaded driver for PL330 DMAC-241330
[ 0.299184] dma-pl330 fe530000.dmac: DBUFF-128x8bytes Num_Chans-8 Num_Peri-32 Num_Events-16
[ 0.302485] dma-pl330 fe550000.dmac: Loaded driver for PL330 DMAC-241330
[ 0.302497] dma-pl330 fe550000.dmac: DBUFF-128x8bytes Num_Chans-8 Num_Peri-32 Num_Events-16
[ 0.304863] rockchip-system-monitor rockchip-system-monitor: system monitor probe
[ 0.306083] Serial: 8250/16550 driver, 10 ports, IRQ sharing disabled
[ 0.306907] fdd50000.serial: ttyS0 at MMIO 0xfdd50000 (irq = 17, base_baud = 1500000) is a 16550A
[ 0.307811] fe650000.serial: ttyS1 at MMIO 0xfe650000 (irq = 62, base_baud = 1500000) is a 16550A
[ 0.311010] random: fast init done
[ 0.311335] random: crng init done
[ 0.334913] mali fde60000.gpu: Kernel DDK version g2p0-01eac0
[ 0.335005] mali fde60000.gpu: Looking up mali-supply from device tree
[ 0.335028] mali fde60000.gpu: Power management initialization failed error = -517
[ 0.335111] mali fde60000.gpu: Device initialization Deferred
[ 0.352030] clk: failed to reparent clk_gmac1_rx_tx to gmac1_clkin: -22
[ 0.352636] rk_gmac-dwmac fe010000.ethernet: Looking up phy-supply from device tree
[ 0.352661] rk_gmac-dwmac fe010000.ethernet: Looking up phy-supply property in node /ethernet@fe010000 failed
[ 0.352683] rk_gmac-dwmac fe010000.ethernet: no regulator found
[ 0.352734] rk_gmac-dwmac fe010000.ethernet: clock input or output? (input).
[ 0.352743] rk_gmac-dwmac fe010000.ethernet: TX delay(0x4f).
[ 0.352752] rk_gmac-dwmac fe010000.ethernet: RX delay(0x25).
[ 0.352765] rk_gmac-dwmac fe010000.ethernet: integrated PHY? (no).
[ 0.352827] rk_gmac-dwmac fe010000.ethernet: clock input from PHY
[ 0.357846] rk_gmac-dwmac fe010000.ethernet: init for RGMII
[ 0.358172] rk_gmac-dwmac fe010000.ethernet: User ID: 0x30, Synopsys ID: 0x51
[ 0.358185] rk_gmac-dwmac fe010000.ethernet: DWMAC4/5
[ 0.358194] rk_gmac-dwmac fe010000.ethernet: DMA HW capability register supported
[ 0.358201] rk_gmac-dwmac fe010000.ethernet: RX Checksum Offload Engine supported
[ 0.358207] rk_gmac-dwmac fe010000.ethernet: TX Checksum insertion supported
[ 0.358212] rk_gmac-dwmac fe010000.ethernet: Wake-Up On Lan supported
[ 0.358261] rk_gmac-dwmac fe010000.ethernet: TSO supported
[ 0.358269] rk_gmac-dwmac fe010000.ethernet: Enable RX Mitigation via HW Watchdog Timer
[ 0.358277] rk_gmac-dwmac fe010000.ethernet: TSO feature enabled
[ 0.987894] [drm] failed to init overlay plane Cluster0-win1
[ 0.987931] [drm] failed to init overlay plane Cluster1-win1
[ 0.988095] rockchip-drm display-subsystem: bound fe040000.vop (ops 0xffffff8008ef7890)
[ 0.988277] dwhdmi-rockchip fe0a0000.hdmi: Detected HDMI TX controller v2.11a with HDCP (DWC HDMI 2.0 TX PHY)
[ 0.989173] dwhdmi-rockchip fe0a0000.hdmi: registered DesignWare HDMI I2C bus driver
[ 0.990840] rockchip-drm display-subsystem: bound fe0a0000.hdmi (ops 0xffffff8008efb8b0)
[ 0.990893] rockchip-drm display-subsystem: bound fe060000.dsi (ops 0xffffff8008efc200)
[ 0.990903] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
[ 0.990906] [drm] No driver support for vblank timestamp query.
[ 0.991042] rockchip-drm display-subsystem: failed to parse loader memory
[ 0.999125] rockchip-vop2 fe040000.vop: [drm:vop2_crtc_atomic_enable] Update mode to 1200x1920p60, type: 16 for vp1
[ 0.999502] dw-mipi-dsi fe060000.dsi: [drm:dw_mipi_dsi_encoder_enable] final DSI-Link bandwidth: 996 x 4 Mbps
[ 1.225657] dwmmc_rockchip fe2b0000.dwmmc: Successfully tuned phase to 270
[ 1.225702] mmc0: new ultra high speed SDR104 SDHC card at address 0001
[ 1.228838] mmcblk0: mmc0:0001 EB1QT 29.8 GiB
[ 1.235404] mmcblk0: p1 p2 p3
[ 1.751642] Console: switching to colour frame buffer device 150x120
[ 1.811379] rockchip-drm display-subsystem: fb0: frame buffer device
[ 1.812706] [drm] Initialized rockchip 2.0.0 20140818 for display-subsystem on minor 0
[ 1.813214] mali fde60000.gpu: Kernel DDK version g2p0-01eac0
[ 1.813329] mali fde60000.gpu: Looking up mali-supply from device tree
[ 1.813427] mali fde60000.gpu: Linked as a consumer to regulator.8
[ 1.813435] mali fde60000.gpu: Looking up shadercores-supply from device tree
[ 1.813448] mali fde60000.gpu: Looking up shadercores-supply property in node /gpu@fde60000 failed
[ 1.813521] mali fde60000.gpu: Looking up mali-supply from device tree
[ 1.813546] vdd_gpu: could not add device link fde60000.gpu err -17
[ 1.813556] vdd_gpu: Failed to create debugfs directory
[ [ 1.841720] ALSA device list:
[ 1.841723] #0: rockchip,hdmi
[ 1.841726] #1: rockchip,rk817-codec
[ 1.842171] dwmmc_rockchip fe2c0000.dwmmc: IDMAC supports 32-bit address mode.
[ 1.842457] dwmmc_rockchip fe2c0000.dwmmc: Using internal DMA controller.
[ 1.842466] dwmmc_rockchip fe2c0000.dwmmc: Version ID is 270a
[ 1.842502] dwmmc_rockchip fe2c0000.dwmmc: DW MMC controller at irq 49,32 bit host data width,256 deep fifo
[ 1.842521] dwmmc_rockchip fe2c0000.dwmmc: Looking up vmmc-supply from device tree
[ 1.842533] dwmmc_rockchip fe2c0000.dwmmc: Looking up vmmc-supply property in node /dwmmc@fe2c0000 failed
[ 1.842561] dwmmc_rockchip fe2c0000.dwmmc: Looking up vqmmc-supply from device tree
[ 1.842567] dwmmc_rockchip fe2c0000.dwmmc: Looking up vqmmc-supply property in node /dwmmc@fe2c0000 failed
[ 1.848350] EXT4-fs (mmcblk0p3): mounted filesystem without journal. Opts: (null)
[ 1.848401] VFS: Mounted root (ext4 filesystem) readonly on device 179:3.
[ 1.849263] devtmpfs: mounted
[ 1.852209] Freeing unused kernel memory: 1600K
[ 1.872223] Run /sbin/init as init process
[ 1.919710] devfreq fde60000.gpu: Couldn't update frequency transition information.
[ 1.992164] headset_interrupt:get pin level again, pin=148,i=0
[ 1.992309] (headset in is low level)headset status is in
[ 2.165622] phy phy-fe8a0000.usb2-phy.1: charger = USB_DCP_CHARGER
[ 2.371172] udevd[193]: starting eudev-3.2.10
[ 3.049589] EXT4-fs (mmcblk0p3): Remounting file system with no journal so ignoring journalled data option
[ 3.051804] EXT4-fs (mmcblk0p3): re-mounted. Opts: data=writeback,errors=remount-ro
[ 3.181336] EXT4-fs (mmcblk0p2): mounted filesystem with ordered data mode. Opts: (null)
|
|
|
10-09-2021, 05:23 PM
|
#15
|
Member
Registered: Mar 2019
Distribution: Slackware
Posts: 301
Rep:
|
Quote:
Originally Posted by sndwvs
|
Wow, you got LAN to work? I just built the same image, but LAN was not working for me. It was cool to see HDMI working for a change, though. I will check out your images and try to figure out what I did wrong.
thanks much!
|
|
|
All times are GMT -5. The time now is 01:28 AM.
|
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
|
Latest Threads
LQ News
|
|