• State Resolved
  • Locked Locked
  • Replies 5 replies
  • Subscribers 98 subscribers
  • Views 492 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

How to slove the fb0 error when booting the EVM8168(EZSDK5.05) through NAND.

Haoran Li1
Expert 1850 points

Hi,

   Since the EZSDK has been updated to Ver5.05, I decide to upgrade the environment of my EVM8168 system, especially the data in NAND.  After flashing the u-boot.noxip.bin, uImage and rd-jffs2.bin into the NAND, I changed the boot ENV as below:

bootcmd=nand read 0x81000000 0x280000 0x440000;bootm 0x81000000
bootargs=console=ttyO2,115200n8 root=/dev/mtdblock7 rw noinitrd rootfstype=jffs2 mem=100M notifyk.vpssm3_sva=0xbf900000 earlyprintk

  Then I trigged the DIP_SW, and reset the whole system.  Although I could successfully log into the EVM8168, some errors were post through the serial terminal after mounting the filesystem:

INIT: version 2.86 booting Please wait: booting...
Error opening /dev/fb0: No such file or directory
Starting udev
udevd (74): /proc/74/oom_adj is deprecated, please use /proc/74/oom_score_adj instead.
notify_shm_drv_sendevent failed! status = 0xfffffff0
notify_send_event failed! status = 0xfffffff0
notify_shm_drv_sendevent failed! status = 0xfffffff0
notify_send_event failed! status = 0xfffffff0


  It seems that device fb0 has lost.  Changing the directory into EVM8168@/dev, listing files, I cannot find such a file (device) named "fb0".  However, there must be a 'fb0' file in the ezsdk-dm816x-evm-rootfs.tar.gz package.

  Could you give me a hand to slove this problem?


Naroah

130627

  • 0
    Expert 1460 points

    Hi, 

         There should not be any harm with that fb0 print. Later it is gettting  created and all the graphics are through /dev/fb0 only. I think you should worry about the other prints on notify module. Double check your bootargs with your build environment (Like the DDR size).

    Regards

    Faizel K B

  • 0
    TI__Guru**** 476595 points

    Hi,

     

    FBDev is supproted as loadable module only and kernel tries to open Fb0 at boot time, whch is why you are seeing this print, but it should not be any problem as this node will be created later on when FbDev module gets inserted.

     

    Rgds,

    Brijesh

  • 0 in reply to Faizel
    Expert 1850 points

    Hi, Faizel

       Thank you for your reply!  I feel better now.  But I still have some questions remained:

    1.  How can I disable the fb0 checking procedure when I boot EVM8168 through NAND?  The EVM8168 would try several times to load the fb0 device and then give up trying.  It takes a lot of time to do such a checking procedure.

    2.  How can I insert the fb0 device manually? 

    3.  What is the fb0 used for?

    4.  Why this error would not occur when the NFS is used?  I have never seen this error post when I tried to boot the EVM through Ethernet.

      I am sincerely looking forward to your reply.

    Naroah

    130627

  • 0 in reply to Brijesh Jadav
    Expert 1850 points

    Hi Brijesh,

      Thank you for your reply!

      I can't find any file like "FbDev.ko".  Should I insert the module manually?

      The booting process would not continue until this fb0 checking procedure was canceled automatically.  It takes a lot of time. How can I fix this problem?


    I am sincerely looking forward to your reply.

    Naroah

    130627

  • 0 in reply to Haoran Li1
    TI__Guru**** 476595 points

    It should be ti81xxfb.ko not Fbdev.ko.

     

    Rgds,

    Brijesh