• State Resolved
  • Locked Locked
  • Replies 10 replies
  • Subscribers 99 subscribers
  • Views 4490 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.

Error opening /dev/fb0

Dennis McLeod
Intellectual 925 points

Other Parts Discussed in Thread: AM3874

During boot, I am getting a line that says "Error opening /dev/fb0: No such file or directory"  

What is /dev/fb0 ?   What startup script is running that? 

I am using an AM3874, no DSPs and not using any gui at all on my platform.. console only. 

  • 0
    TI__Guru**** 496475 points

    Hi,

     

    could you send the complete console log? it looks like fbdev module is not getting inserted.

     

    Regards,

    brijesh jadav

  • 0 in reply to Brijesh Jadav
    Intellectual 925 points

    I probably wasn't clear enough in my original post. But starting at square 1, most important question: 

    1. What is fb0?  Is it something to do with GUI support? 

    2. if it IS something to do with GUI support, how do I remove the error message? (NOT how do i get an unnecessary module inserted?)

  • 0 in reply to Dennis McLeod
    TI__Guru**** 496475 points

    Hi,

     

    Yes, Fb0 is frame buffer driver, which is used for displaying GUI. This /dev/fb0 node will be created only when frame buffer is successfully inserted inside the kernel. It looks like it is not.

     

    Regards,

    Brijesh Jadav

     

  • 0 in reply to Brijesh Jadav
    Intellectual 925 points

    Ok, thank you. 

    I am not using any GUI on my platform. I would like to know what causes the error message. I am guessing there is some type of init script or service that is attempting to open /dev/fd0. I can't find anything though. Do you have any ideas on where to look for what might be causing the error message to be printed? 

    Thanks again! 

  • 0 in reply to Dennis McLeod
    TI__Guru**** 496475 points

    Hi Dennis,

     

    Which application are you running? Is it DVR-RDK or ez-SDK?

     

    Regards,

    Brijesh Jadav

  • 0 in reply to Brijesh Jadav
    Intellectual 925 points

    Brijesh Jadav said:
    Which application are you running? Is it DVR-RDK or ez-SDK?

    EZSDK

  • 0 in reply to Dennis McLeod
    TI__Guru**** 496475 points

    Hi Dennis,

     

    In ezSDK, there will be some init script, which will load the vpss.ko and frame buffer module. could you please check if they really get loaded?

     

    Regards,

    Brijesh

  • 0 in reply to Brijesh Jadav
    Intellectual 925 points

    Brijesh Jadav said:

    Hi Dennis,

     

    In ezSDK, there will be some init script, which will load the vpss.ko and frame buffer module. could you please check if they really get loaded?

     

    Regards,

    Brijesh

    I wish I knew. The output of "lsmod" only shows the column headers. No modules are listed.  
    However, if they ARE being loaded, then I don't want them to be.. nor do I want any scripts trying to spawn anything that uses them. My question is, how do I get rid of the error message AND anything related to framebuffers and GUIs. I don't want or need them, and I just want the error message to go away. 
    Thank you! 
  • 0 in reply to Dennis McLeod
    Intellectual 465 points

    If you're using the EZSDK, there's a good chance a TI splash screen is still being loaded, to output a TI logo/progress bar at boot and at shutdown.  I believe I've seen cases where it starts up prematurely.

    The splash screen program will attempt to open the framebuffer, which won't exist if the modules aren't loaded, as in your case.

    Check and see if you still have /etc/init.d/psplash being loaded at boot.

  • 0 in reply to Nick Reed
    Intellectual 925 points

    Nick Reed said:

    If you're using the EZSDK, there's a good chance a TI splash screen is still being loaded, to output a TI logo/progress bar at boot and at shutdown.  I believe I've seen cases where it starts up prematurely.

    The splash screen program will attempt to open the framebuffer, which won't exist if the modules aren't loaded, as in your case.

    Check and see if you still have /etc/init.d/psplash being loaded at boot.

    Bingo! Thank you!