This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

about hwclock error message

Hello,

If we don't use RTC and we use the arago-base-tisdk-image-am335x-evm filesystem
How to clear the following hwclock error message


....
Starting Bootlog daemon: bootlogd: cannot allocate pseudo tty: No such file or d
irectory
bootlogd.
ALSA: Restoring mixer settings...
/usr/sbin/alsactl: load_state:1686: No soundcards found...
Configuring network interfaces... done.
hwclock: can't open '/dev/misc/rtc': No such file or directory
Tue Jun 25 23:08:00 UTC 2013
hwclock: can't open '/dev/misc/rtc': No such file or directory
Configuring update-modules.
INIT: Entering runlevel: 5

  • Hi Justin,

    I assume this is called from one of the init scripts located in /etc/init.d (hwclock.sh). You can remove it from the runtime control with:

    sudo update-rc.d -f hwclock.sh remove

    Please let me know if this fixes your problem.

    Best regards,
    Miroslav

  • Hello Miroslav,

    I delete the link S20hwclock.sh in /etc/rc5.d,then i make the ramdisk.gz

    it still show following message

    ...

    EXT3-fs (mmcblk0p3): using internal journal
    EXT3-fs (mmcblk0p3): recovery complete
    EXT3-fs (mmcblk0p3): mounted filesystem with ordered data mode
    Starting Bootlog daemon: bootlogd: cannot allocate pseudo tty: No such file or d
    irectory
    bootlogd.
    ALSA: Restoring mixer settings...
    /usr/sbin/alsactl: load_state:1686: No soundcards found...
    Configuring network interfaces... done.
    hwclock: can't open '/dev/misc/rtc': No such file or directory
    Tue Jun 25 23:08:00 UTC 2013
    hwclock: can't open '/dev/misc/rtc': No such file or directory
    Configuring update-modules.
    INIT: Entering runlevel: 5
    Disabling lock debugging due to kernel taint

    ...

  • Justin,

    I found another init script that is calling hwclock.sh:

    /etc/rcS.d/S55bootmisc.sh

    # Set the system clock from hardware clock
    # If the timestamp is more recent than the current time,
    # use the timestamp instead.
    test -x /etc/init.d/hwclock.sh && /etc/init.d/hwclock.sh start
    if test -e /etc/timestamp
    then
        SYSTEMDATE=`date -u +%4Y%2m%2d%2H%2M`
        read TIMESTAMP < /etc/timestamp
        if [ ${TIMESTAMP} -gt $SYSTEMDATE ]; then
            date -u ${TIMESTAMP#????}${TIMESTAMP%????????}
            test -x /etc/init.d/hwclock.sh && /etc/init.d/hwclock.sh stop
        fi
    fi

    I think this is it, because the error messages appear before you enter runlevel 5.

    Best regards,
    Miroslav

  • Hello Miroslav

    Thank you:)

    I killed the S55bootmisc.sh ,it is no error!!