Hi, I think you didn't flash the module.img. You need to build the module with kernel.
Best Regards, Jaehoon Chung On 07/02/2014 01:04 AM, Byonggon Chun wrote: > hello i port tizen 2.2 on odroid u3 with 3.10 kernel > > but tizen systemd process stop after many Dependency failed. > > and there are only 4 penguins on my monitor which connect with odroid u3. > > i use RD-PQ img files. > http://download.tizen.org/snapshots/2.2/common/tizen-2.2_20140122.2/images/RD-PQ/ > > below is my logs. > > I don`t have any idea what is problem. > > ======================================================================== > > Welcome to Tizen 2.2.0 (Tizen)! > > Started Replay Read-Ahead Data [ OK > ] > Starting Collect Read-Ahead Data... > > Starting Runtime Directory... > > Starting Media Directory... > > Started POSIX Message Queue File System [ OK > ] > Starting Journal Service... > > Started Journal Service [ OK > ] > Starting Debug File System... > > Started Huge Pages File System [ OK > ] > Starting udev Kernel Device Manager... > > Starting udev Coldplug all Devices... > > Starting Generate environment from /etc/profile.d... > > Starting Smack filesystem mounting... > > [ 3.308433] tmpfs: Bad mount option smackfsroot > [ 3.312506] udevd[1494]: starting version 182 > Starting Security File System... > > Started udev Kernel Device Manager [ OK > ] > Started Collect Read-Ahead Data [ OK > ] > Failed to start Runtime Directory > [FAILED] > See 'systemctl status tmp.mount' for details. > > Started Media Directory [ OK > ] > Started Debug File System [ OK > ] > Failed to start Smack filesystem mounting > [FAILED] > See 'systemctl status smack.mount' for details. > > Dependency failed. Aborted start of Smack [ > ABORT] > Dependency failed. Aborted start of Default SMACK labeling [ > ABORT] > Dependency failed. Aborted start of Default SMACK labeling [ > ABORT] > Started Generate environment from /etc/profile.d [ OK > ] > Started Security File System [ OK > ] > Starting File System Check on Root Device... > > Starting Remount API VFS... > > Started Load Kernel Modules [ OK > ] > Started FUSE Control File System [ OK > ] > Starting Configuration File System... > > Started Set Up Additional Binary Formats [ OK > ] > Starting Apply Kernel Variables... > > Started Configuration File System [ OK > ] > Started Remount API VFS [ OK > ] > Started Apply Kernel Variables [ OK > ] > systemd-fsck[1585]: platform: clean, 29351/192000 files, 217952/786432 blocks > Started File System Check on Root Device [ OK > ] > Starting Remount Root FS... > > [ 3.714390] EXT4-fs (mmcblk0p2): re-mounted. Opts: (null) > Started Remount Root FS [ OK > ] > Starting File System Check on /dev/mmcblk0p1... > > Starting File System Check on /dev/mmcblk0p2... > > systemd-fsck[2281]: fsck.ext4: Bad magic number in super-block while trying > to open /dev/mmcblk0p1 > Started File System Check on /dev/mmcblk0p2 [ OK > ] > Starting Resize of File System on /dev/mmcblk0p2... > > systemd-fsck[2281]: /dev/mmcblk0p1: > Started File System Check on /dev/mmcblk0p1 [ OK > ] > systemd-fsck[2281]: The superblock could not be read or does not describe a > correct ext2 > systemd-fsck[2281]: filesystem. If the device is valid and it really > contains an ext2 > systemd-fsck[2281]: filesystem (and not swap or ufs or something else), then > the superblock > systemd-fsck[2281]: is corrupt, and you might try running e2fsck with an > alternate superblock: > systemd-fsck[2281]: e2fsck -b 8193 <device> > resize2fs[2301]: resize2fs 1.41.9 (22-Aug-2009) > resize2fs[2301]: The filesystem is already 786432 blocks long. Nothing to do! > Started Resize of File System on /dev/mmcblk0p2 [ OK > ] > Starting /boot... > > Starting Resize of File System on /dev/mmcblk0p1... > > Started /boot [ OK > ] > Starting /lib/modules... > > resize2fs[2366]: resize2fs 1.41.9 (22-Aug-2009) > resize2fs[2366]: /sbin/resize2fs: Bad magic number in super-block while > trying to open /dev/mmcblk0p1 > resize2fs[2366]: Couldn't find valid filesystem superblock. > Failed to start Resize of File System on /dev/mmcblk0p1 > [FAILED] > See 'systemctl status [email protected]' for details. > > Failed to start /lib/modules > [FAILED] > See 'systemctl status lib-modules.mount' for details. > > Dependency failed. Aborted start of Resize of File S... /dev/mmcblk0p6 [ > ABORT] > Dependency failed. Aborted start of File System Chec... /dev/mmcblk0p6 [ > ABORT] > Dependency failed. Aborted start of /opt [ > ABORT] > Dependency failed. Aborted start of /opt/usr [ > ABORT] > Dependency failed. Aborted start of /var [ > ABORT] > Dependency failed. Aborted start of Runtime Directory [ > ABORT] > Dependency failed. Aborted start of Initialize the VConf storage [ > ABORT] > Dependency failed. Aborted start of Resize of File S... /dev/mmcblk0p7 [ > ABORT] > Dependency failed. Aborted start of File System Chec... /dev/mmcblk0p7 [ > ABORT] > > ======================================================================== > > > _______________________________________________ > General mailing list > [email protected] > https://lists.tizen.org/listinfo/general > _______________________________________________ General mailing list [email protected] https://lists.tizen.org/listinfo/general
