search

notro / fbtft

Linux Framebuffer drivers for small TFT LCD display modules. Development has moved to https://git.kernel.org/cgit/linux/kernel/git/gregkh/staging.git/tree/drivers/staging/fbtft?h=staging-testing
1.86k stars 494 forks source link

FBTFT Module Failing to load at startup #369

Closed theLuthier closed 8 years ago

theLuthier commented 8 years ago

I’m using a 2.2″ SPI TFT display with my RPi2. In conjunction with RetroPie 3.2, everything worked fine with FBTFT and FBCP working at startup. I’ve since installed Retropie 3.4 and I keep running into 2 problems:

1 -- FBTFT module fails to load when added to /etc/modules.

screen-shot-2016-02-01-at-3 29 16-pm

I’ve managed to work around it by adding “modprobe fbtft_device name=adafruit22a” to /etc/rc.local, however it only works about 50% of the time. The module loading after reboot seems to be determined by the flip of a coin..

2 -- Following the trend, FBCP only runs at startup about 50% of the time. I've tried adding “/usr/local/bin/fbcp &” seemingly everywhere I've seen suggested online: rc.local, init.d/asplashscreen, my own custom startup script as recommend in the wiki (http://www.stuffaboutcode.com/2012/06/raspberry-pi-run-program-at-start-up.html).

However as soon as I get to the console, “modprobe fbtft_device” loads fine as does “fbcp&”. So this tells me that perhaps there’s an issue with when the module loads and when/if the fbcp command runs.

Any help is very appreciated at this point.

PS - Huge thanks to notro for making this possible in the first place!

notro commented 8 years ago

Have you followed this: https://github.com/notro/fbtft/wiki#make-it-permanent-debian-jessie-arch-linux-systemd

theLuthier commented 8 years ago

Thanks for the repy, notro. Yes I have, here's the output from dmesg:

screen shot 2016-02-04 at 3 21 37 pm

notro commented 8 years ago

This kernel seem to be using the out-of-tree spi-bcm2708 driver, so you need to specify spi-bcm2708 instead of spi-bcm2835.

theLuthier commented 8 years ago

That seems to have fixed it! Though dmesg still gives an error:

screen shot 2016-02-04 at 4 19 35 pm

I'm used to this working sometimes and not others, so I'll give it a couple days and update if this appears to be a permanent fix. Thanks a ton for the help!

notro commented 8 years ago

If you add debug to /boot/cmdline.txt, you'll get a lot of systemd debug messages in the kernel log. Maybe that can aid you in tracking down the reason for the error.

theLuthier commented 8 years ago

Oh nice, thanks for the suggestion - I'll certainly try it.

notro commented 8 years ago

Closing old issues, reopen if needed.

Zhairgling commented 7 years ago

Hi did you solved this error ? I've the same :

image