Can't open /dev/ttymxc0: No such device or file?

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Can't open /dev/ttymxc0: No such device or file?

4,793 Views
DonaldR_PooleJr
Contributor I

So, I've successfully compiled Freescale's imx_2.6.35_11.04.01 kernel and imx_v2009.08_11.04.01 u-boot and everything boots fine until it tries to initialize the console.  That's when it start displaying "Can't open /dev/ttymxc0: No such file or directory" repeatedly.  Has anyone come across this problem before?  I'm so close to getting my kernel up an running.  I just need to overcome this issue.

0 Kudos
Reply
3 Replies

2,662 Views
VadivelmuruganR
Contributor I

Apply the root permission to all the files in this /dev/ 

directory.

Murugan

iWave Systems


Fabio Estevam said:

Looks like your kernel booted and the rootfs was mounted, but it failed to run sbin/getty or something.

If you use LTIB rootfs for MX53QSB, it should open sbin/getty -L ttymxc0 for you.

Regards,

Fabio Estevam

0 Kudos
Reply

2,662 Views
DonaldR_PooleJr
Contributor I

Thanks Fabio for the reply.  This is what my inittab looks like:

# /etc/inittab

#

# Copyright (C) 2001 Erik Andersen <andersen@codepoet.org>

#

# Note: BusyBox init doesn't support runlevels.  The runlevels field is

# completely ignored by BusyBox init. If you want runlevels, use

# sysvinit.

#

# Format for each entry: <id>:<runlevels>:<action>:<process>

#

# id        == tty to run on, or empty for /dev/console

# runlevels == ignored

# action    == one of sysinit, respawn, askfirst, wait, and once

# process   == program to run

# Startup the system

null::sysinit:/bin/mount -t proc proc /proc

null::sysinit:/bin/mount -o remount,rw / # REMOUNT_ROOTFS_RW

null::sysinit:/bin/mkdir -p /dev/pts

null::sysinit:/bin/mkdir -p /dev/shm

null::sysinit:/bin/mount -a

null::sysinit:/bin/hostname -F /etc/hostname

# now run any rc scripts

::sysinit:/etc/init.d/rcS

# Put a getty on the serial port

ttymxc0::respawn:/sbin/getty -L ttymxc0 115200 vt100 # GENERIC_SERIAL

# Stuff to do for the 3-finger salute

::ctrlaltdel:/sbin/reboot

# Stuff to do before rebooting

null::shutdown:/usr/bin/killall klogd

null::shutdown:/usr/bin/killall syslogd

null::shutdown:/bin/umount -a -r

null::shutdown:/sbin/swapoff -a

Looking at the getty part, it should be working.  Does anything look wrong? Here is the last bit of output before the Can't open /dev/ttymxc0: No such file of directory output:

EXT3-fs: barriers not enabled

kjournald starting.  Commit interval 5 seconds

EXT3-fs (mmcblk0p1): using internal journal

EXT3-fs (mmcblk0p1): recovery complete

EXT3-fs (mmcblk0p1): mounted filesystem with writeback data mode

VFS: Mounted root (ext3 filesystem) on device 179:1.

Freeing init memory: 172K

Starting logging: OK

Populating  using udev: done

Starting portmap: done

Starting system message bus: done

Starting network...

Starting Network Interface Plugging Daemon: eth0.

eth0: Freescale FEC PHY driver [Generic PHY] (mii_bus:phy_addr=0:00, irq=-1)

Getting initial time via ntp.

Starting network time protocol daemon: ntpd.

Starting gpsd: OK

Generating RSA Key...

PRNG is not seeded

Generating RSA Key...

PRNG is not seeded

Generating DSA Key...

THIS CAN TAKE A MINUTE OR TWO DEPENDING ON YOUR PROCESSOR!

PRNG is not seeded

Generating ECDSA Key...

THIS CAN TAKE A MINUTE OR TWO DEPENDING ON YOUR PROCESSOR!

PRNG is not seeded

Starting sshd: PRNG is not seeded

OK

Starting network management services:.

Starting domain name daemon: namedwarning: `named' uses 32-bit capabilities (legacy support in use)

failed

Starting input-event-daemon: input-event-daemon: open(/dev/input/event0): No such file or directory

done

can't open /dev/ttymxc0: No such file or directory

can't open /dev/ttymxc0: No such file or directory

can't open /dev/ttymxc0: No such file or directory

can't open /dev/ttymxc0: No such file or directory

can't open /dev/ttymxc0: No such file or directory



Fabio Estevam said:

Looks like your kernel booted and the rootfs was mounted, but it failed to run sbin/getty or something.

If you use LTIB rootfs for MX53QSB, it should open sbin/getty -L ttymxc0 for you.

Regards,

Fabio Estevam

0 Kudos
Reply

2,662 Views
fabio_estevam
NXP Employee
NXP Employee

Looks like your kernel booted and the rootfs was mounted, but it failed to run sbin/getty or something.

If you use LTIB rootfs for MX53QSB, it should open sbin/getty -L ttymxc0 for you.

Regards,

Fabio Estevam

0 Kudos
Reply