Firefly开源社区

4.4.16内核不能加载文件系统,wait-for-root /dev/block/mtd/by-name/linuxroot,

205

积分

0

威望

0

贡献

技术达人

Rank: 2

积分
205
发表于 2017-5-4 15:44:38     
[    3.786619] input: MOSART Semi. 2.4G Keyboard Mouse as /devices/platform/ff540000.usb/usb1/1-1/1-1.1/1-1.1:1.1/0003:062A:4182.0002/input/input1
[    3.825703] rockchip-drm display-subsystem: fb0:  frame buffer device
[    3.843748] hid-generic 0003:062A:4182.0002: input,hiddev0,hidraw1: USB HID v1.10 Mouse [MOSART Semi. 2.4G Keyboard Mouse] on usb-ff540000.usb-1.1/input1
[    3.980848] asoc-simple-card sound_i2s: i2s-hifi <-> ff890000.i2s mapping ok
[    3.990119] asoc-simple-card sound_i2s: ES8323 HiFi <-> ff890000.i2s mapping ok
[    4.000487] input: gpio-keys as /devices/platform/gpio-keys/input/input2
[    4.007646] rtc-hym8563 0-0051: no valid clock/calendar values available
[    4.014500] rtc-hym8563 0-0051: hctosys: unable to read the hardware clock
[    4.029565] dovdd_1v8: disabling
[    4.032914] vcc_sd: disabling
[    4.036526] ALSA device list:
[    4.039573]   #0: rockchip,firefly-codec
[    4.043911] ttyS2 - failed to request DMA
[    4.048987] Freeing unused kernel memory: 1024K (c0e00000 - c0f00000)
Loading, please wait...
/init: line 224: can't create /sys/class/display/HDMI/enable: nonexistent directory
[    4.082911] udevd[143]: starting version 175
Begin: Loading essential drivers ... FATAL: Could not load /lib/modules/4.4.16/modules.dep: No such file or directory
FATAL: Could not load /lib/modules/4.4.16/modules.dep: No such file or directory
FATAL: Could not load /lib/modules/4.4.16/modules.dep: No such file or directory
FATAL: Could not load /lib/modules/4.4.16/modules.dep: No such file or directory
done.
Begin: Running /scripts/init-premount ... done.
Begin: Mounting root file system ... Begin: Running /scripts/local-top ... done.
[    4.218951] random: nonblocking pool is initialized
wait-for-root /dev/block/mtd/by-name/linuxroot, retry 2...
wait-for-root /dev/block/mtd/by-name/linuxroot, retry 3...
wait-for-root /dev/block/mtd/by-name/linuxroot, retry 4...
wait-for-root /dev/block/mtd/by-name/linuxroot, retry 5...
wait-for-root /dev/block/mtd/by-name/linuxroot, retry 6...
wait-for-root /dev/block/mtd/by-name/linuxroot, retry 7...
wait-for-root /dev/block/mtd/by-name/linuxroot, retry 8...
wait-for-root /dev/block/mtd/by-name/linuxroot, retry 9...
wait-for-root /dev/block/mtd/by-name/linuxroot, retry 10...
[   13.657735] aaaaa  vga_encoder_atomic_check 125 1
wait-for-root /dev/block/mtd/by-name/linuxroot, retry 11...
wait-for-root /dev/block/mtd/by-name/linuxroot, retry 12...
wait-for-root /dev/block/mtd/by-name/linuxroot, retry 13...
wait-for-root /dev/block/mtd/by-name/linuxroot, retry 14...
wait-for-root /dev/block/mtd/by-name/linuxroot, retry 15...
wait-for-root /dev/block/mtd/by-name/linuxroot, retry 16...
wait-for-root /dev/block/mtd/by-name/linuxroot, retry 17...
wait-for-root /dev/block/mtd/by-name/linuxroot, retry 18...
wait-for-root /dev/block/mtd/by-name/linuxroot, retry 19...
wait-for-root /dev/block/mtd/by-name/linuxroot, retry 20...
wait-for-root /dev/block/mtd/by-name/linuxroot, retry 21...
wait-for-root /dev/block/mtd/by-name/linuxroot, retry 22...
wait-for-root /dev/block/mtd/by-name/linuxroot, retry 23...
wait-for-root /dev/block/mtd/by-name/linuxroot, retry 24...
wait-for-root /dev/block/mtd/by-name/linuxroot, retry 25...
wait-for-root /dev/block/mtd/by-name/linuxroot, retry 26...
wait-for-root /dev/block/mtd/by-name/linuxroot, retry 27...
wait-for-root /dev/block/mtd/by-name/linuxroot, retry 28...
wait-for-root /dev/block/mtd/by-name/linuxroot, retry 29...
wait-for-root /dev/block/mtd/by-name/linuxroot, retry 30...
Gave up waiting for root device.  Common problems:
- Boot args (cat /proc/cmdline)
   - Check rootdelay= (did the system wait long enough?)
   - Check root= (did the system wait for the right device?)
- Missing modules (cat /proc/modules; ls /dev)
ALERT!  /dev/block/mtd/by-name/linuxroot does not exist.  Dropping to a shell!
FATAL: Could not load /lib/modules/4.4.16/modules.dep: No such file or directory
FATAL: Could not load /lib/modules/4.4.16/modules.dep: No such file or directory
/bin/sh: can't access tty; job control turned off
(initramfs)

上面是片段日志,我用官网的镜像我更新了内核启动就是这样.我制作的跟文件系统也是如此.


回复

使用道具 举报

781

积分

0

威望

0

贡献

技术大神

Rank: 3Rank: 3

积分
781
QQ
发表于 2017-7-7 16:18:10     
系统制作有问题
回复

使用道具 举报

47

积分

0

威望

0

贡献

游客

积分
47
发表于 2017-11-22 17:23:10     
请问是什么问题导致的?系统制作的哪一步出问题了?能否明确一下?
我按照牛头版主的操作步骤,并未出现任何异常,将CMDLINE改成/dev/mmcblk0p3也是一样的。
我是在Firefly-rk3288_Ubuntu_1604_201705250940.img的版本上改变内核3.14 kernel。
回复

使用道具 举报

371

积分

5

威望

0

贡献

技术达人

Rank: 2

积分
371
发表于 2017-12-12 17:37:53     
root=/dev/mmcblk1p6   
确定,你烧写固件文件系统在第几个分区,你设置为p3 ,肯定是不对的,
然后,确定,是mmcblk0 还是 mmcblk1
回复

使用道具 举报

44

积分

0

威望

0

贡献

游客

积分
44
发表于 2017-12-15 14:34:30     
luvings 发表于 2017-12-12 17:37
root=/dev/mmcblk1p6   
确定,你烧写固件文件系统在第几个分区,你设置为p3 ,肯定是不对的,
然后,确 ...

请问怎么确定文件系统在第几个分区?mmcblk0如何确定?
回复

使用道具 举报

44

积分

0

威望

0

贡献

游客

积分
44
发表于 2017-12-15 14:35:02     
楼主问题解决了没?
回复

使用道具 举报

371

积分

5

威望

0

贡献

技术达人

Rank: 2

积分
371
发表于 2017-12-18 11:08:29     
lzhfdwpl 发表于 2017-12-15 14:34
请问怎么确定文件系统在第几个分区?mmcblk0如何确定?

解包固件,看parameter ,一般来说是第6个分区,也就是(boot)分区

小白的话,试试,不是mmcblk0, 就是k1
回复

使用道具 举报

*滑块验证:
您需要登录后才可以回帖 登录 | 立即注册

本版积分规则

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