Firefly开源社区

打印 上一主题 下一主题

[Linux] Core-3399-JD4编译的内核启动失败

39

积分

0

威望

0

贡献

技术小白

积分
39

Core-3399-JD4编译的内核启动失败

发表于 2019-12-17 17:00:55      浏览:6499 | 回复:2        打印      只看该作者   [复制链接] 楼主
当前硬件是Core-3399-JD4核心板以及配套底板,使用官网下载的固件能正常启动。此时使用SDK编译得到的内核则无法正常启动。官网下载的SDK已更新,且无修改,编译方式为http://wiki.t-firefly.com/zh_CN/ ... nt.html#bian-yi-sdk。仅编译内核。将内核写入0x00280000后,启动失败。

报错打印一:此处仅报错,未停止运行
[    4.028549] systemd[1]: Detected architecture arm64.
[    4.036898] EXT4-fs error (device mmcblk1p5): ext4_iget:4434: inode #42191: comm systemd: bad extended attribute block 3942645823
[    4.038814] Aborting journal on device mmcblk1p5-8.

报错打印二:在Started D-Bus System Message Bus.成功后,系统停止。
[  OK  ] Started Apply Kernel Variables.
[  OK  ] Started udev Coldplug all Devices.
[  OK  ] Started udev Kernel Device Manager.
[  OK  ] Mounted POSIX Message Queue File System.
[  OK  ] Mounted Kernel Debug File System.
[  OK  ] Mounted Kernel Configuration File System.
[  OK  ] Mounted FUSE Control File System.
[  OK  ] Started Flush Journal to Persistent Storage.
[  OK  ] Started Set the console keyboard layout.
[  OK  ] Reached target Local File Systems (Pre).
[  OK  ] Reached target Local File Systems.
         Starting Create Volatile Files and Directories...
         Starting Set console font and keymap...
         Starting Tell Plymouth To Write Out Runtime Data...
[  OK  ] Started Dispatch Password Requests to Console Directory Watch.
[  OK  ] Reached target Local Encrypted Volumes.
[  OK  ] Created slice system-systemd\x2dbacklight.slice.
         Starting Load/Save Screen Backlight鈥ghtness of backlight:backlight...
[FAILED] Failed to start Load/Save Screen Ba鈥rightness of backlight:backlight.
See 'systemctl status systemd-backlight鈥klight:backlight.service' for details.
[  OK  ] Started Tell Plymouth To Write Out Runtime Data.
[FAILED] Failed to start Create Volatile Files and Directories.
See 'systemctl status systemd-tmpfiles-setup.service' for details.
[FAILED] Failed to start Network Name Resolution.
See 'systemctl status systemd-resolved.service' for details.
[  OK  ] Reached target Host and Network Name Lookups.
[FAILED] Failed to start Network Time Synchronization.
See 'systemctl status systemd-timesyncd.service' for details.
[  OK  ] Reached target System Time Synchronized.
         Starting Update UTMP about System Boot/Shutdown...
[  OK  ] Started Set console font and keymap.
[  OK  ] Stopped Network Time Synchronization.
[FAILED] Failed to start Network Time Synchronization.
See 'systemctl status systemd-timesyncd.service' for details.
[  OK  ] Stopped Network Name Resolution.
[FAILED] Failed to start Network Name Resolution.
See 'systemctl status systemd-resolved.service' for details.
[  OK  ] Found device /dev/ttyFIQ0.
[  OK  ] Stopped Network Time Synchronization.
[FAILED] Failed to start Network Time Synchronization.
See 'systemctl status systemd-timesyncd.service' for details.
[  OK  ] Stopped Network Name Resolution.
[FAILED] Failed to start Network Name Resolution.
See 'systemctl status systemd-resolved.service' for details.
[  OK  ] Stopped Network Name Resolution.
[FAILED] Failed to start Network Name Resolution.
See 'systemctl status systemd-resolved.service' for details.
[  OK  ] Stopped Network Time Synchronization.
[FAILED] Failed to start Network Time Synchronization.
See 'systemctl status systemd-timesyncd.service' for details.
[  OK  ] Reached target Sound Card.
[FAILED] Failed to start Update UTMP about System Boot/Shutdown.
See 'systemctl status systemd-update-utmp.service' for details.
[DEPEND] Dependency failed for Update UTMP about System Runlevel Changes.
[  OK  ] Stopped Network Time Synchronization.
[FAILED] Failed to start Network Time Synchronization.
See 'systemctl status systemd-timesyncd.service' for details.
[  OK  ] Stopped Network Name Resolution.
[FAILED] Failed to start Network Name Resolution.
See 'systemctl status systemd-resolved.service' for details.
[  OK  ] Reached target System Initialization.
[  OK  ] Listening on Avahi mDNS/DNS-SD Stack Activation Socket.
[  OK  ] Listening on D-Bus System Message Bus Socket.
         Starting Socket activation for snappy daemon.
         Starting Docker Socket for the API.
[  OK  ] Reached target Paths.
[  OK  ] Listening on Socket activation for snappy daemon.
[  OK  ] Stopped Network Time Synchronization.
[FAILED] Failed to start Network Time Synchronization.
See 'systemctl status systemd-timesyncd.service' for details.
[  OK  ] Stopped Network Name Resolution.
[FAILED] Failed to start Network Name Resolution.
See 'systemctl status systemd-resolved.service' for details.
[  OK  ] Listening on Docker Socket for the API.
[  OK  ] Reached target Sockets.
[  OK  ] Reached target Basic System.
         Starting Dispatcher daemon for systemd-networkd...
         Starting LSB: automatic crash report generation...
[  OK  ] Started D-Bus System Message Bus.

回复

使用道具 举报

39

积分

0

威望

0

贡献

技术小白

积分
39
发表于 2019-12-17 17:39:11        只看该作者  沙发
追加:固件使用的是AIO-3399-JD4-LVDS-UBUNTU18.04-GPT-20190904-1740.img,但是SDK是Ubuntu16的,不知道是否存在匹配问题。
另外使用./build.sh全编译时,在编译过程中需要联网下载资源,不知此现象是否正常?
回复

使用道具 举报

428

积分

0

威望

0

贡献

技术达人

Rank: 2

积分
428
发表于 2019-12-18 09:36:57        只看该作者  板凳
首先看看device/rockchip/rk3399/parameter-ubuntu.mk这个文件中,boot分区的地址,不知道是不是0x28000,我查看的地址好像不一样。
全编译时,根文件系统默认编译buildroot根文件系统,所以当然会联网下载资源
回复

使用道具 举报

您需要登录后才可以回帖 登录 | 立即注册

本版积分规则

友情链接 : 爱板网 电子发烧友论坛 云汉电子社区 粤ICP备14022046号-2
快速回复 返回顶部 返回列表