|
After updating the kernel can't enter fs and terminal can not input
Posted at 10/13/2015 10:49:46
View:4015
|
Replies:2
Print
Only Author
[Copy Link]
1#
hi,
I reference http://wiki.t-firefly.com/index.php/Firefly-RK3288/Flash_image/en and flash Firefly-RK3288_Ubuntu14.04_201501271612.img,when I update kernel reference http://wiki.t-firefly.com/index.php/Firefly-RK3288/Build_kernel/en can't enter fs and can't input on terminal,fllow is detail:
[ 9.355094] init: plymouth-upstart-bridge main process (312) terminated with status 1
[ 9.365994] init: plymouth-upstart-bridge main process ended, respawning
[ 9.382414] 2, baud is:115200
[ 9.498739] init: mounted-proc main process (325) terminated with status 1
[ 9.923637] systemd-udevd[452]: could not open moddep file '/lib/modules/3.10.0/modules.dep.bin'
* Starting Mount filesystems on boot[ OK ]
* Starting Signal sysvinit that the rootfs is mounted[ OK ]
* Starting Initialize or finalize resolvconf[ OK ]
* Starting Clean /tmp directory[ OK ]
* Stopping Track if upstart is running in a container[ OK ]
* Stopping Clean /tmp directory[ OK ]
* Starting Signal sysvinit that virtual filesystems are mounted[ OK ]
* Starting Signal sysvinit that virtual filesystems are mounted[ OK ]
* Starting Bridge udev events into upstart[ OK ]
* Starting Signal sysvinit that remote filesystems are mounted[ OK ]
* Starting device node and kernel event manager[ OK ]
* Starting Signal sysvinit that local filesystems are mounted[ OK ]
* Starting restore software rfkill state[ OK ]
* Starting load modules from /etc/modules[ OK ]
* Starting cold plug devices[ OK ]
* Starting log initial device creation[ OK ]
* Stopping Mount filesystems on boot[ OK ]
* Stopping restore software rfkill state[ OK ]
* Stopping load modules from /etc/modules[ OK ]
* Starting flush early job output to logs[ OK ]
* Starting D-Bus system message bus[ OK ]
* Stopping flush early job output to logs[ OK ]
* Starting SystemD login management service[ OK ]
* Starting set console font[ OK ]
* Stopping set console font[ OK ]
* Starting userspace bootsplash[ OK ]
* Stopping userspace bootsplash[ OK ]
* Starting Send an event to indicate plymouth is up[ OK ]
* Stopping Send an event to indicate plymouth is up[ OK ]
* Starting configure network device security[ OK ]
* Starting system logging daemon[ OK ]
* Starting configure network device[ OK ]
* Starting bluetooth initialization[ OK ]
* Starting bluetooth initialization[fail]
* Starting bluetooth daemon[ OK ]
* Starting configure network device security[ OK ]
* Starting configure network device security[ OK ]
* Starting configure network device[ OK ]
* Starting Mount network filesystems[ OK ]
* Starting Failsafe Boot Delay[ OK ]
* Starting Turn on/off the ap6335 bluetooth[ OK ]
* Starting configure network device[ OK ]
* Stopping Failsafe Boot Delay[ OK ]
* Starting System V initialisation compatibility[ OK ]
* Starting configure network device security[ OK ]
* Stopping Mount network filesystems[ OK ]
[ OK ]ting up X socket directories...
* Stopping System V initialisation compatibility[ OK ]
* Starting System V runlevel compatibility[ OK ]
* Starting save kernel messages[ OK ]
* Starting configure network device security[ OK ]
* Starting OpenSSH server[ OK ]
* Starting anac(h)ronistic cron[ OK ]
* Starting regular background program processing daemon[ OK ]
* Stopping save kernel messages[ OK ]
* Stopping anac(h)ronistic cron[ OK ]
[ 10.954992] turn on mali power
* Stopping Restore Sound Card State[ OK ]
* Starting configure virtual network devices[ OK ]
[ 40.459762] systemd-udevd[457]: timeout 'accelerometer /devices/virtual/input/input3'
[ 41.452521] systemd-udevd[457]: timeout: killing 'accelerometer /devices/virtual/input/input3' [485]
[ 41.749646] systemd-udevd[457]: 'accelerometer /devices/virtual/input/input3' [485] terminated by signal 9 (Killed)
|
|