Tiny Core Base > Raspberry Pi
Issues with Adafruit PiTFT display on picore 15
Rich:
Hi segfault
Please use Code Tags when posting commands and responses seen in a terminal. To use Code Tags click on the # icon
above the reply box and paste your text between the Code Tags as shown in this example:
--- Quote ---[code][ 36.176529] pcm512x 1-004d: Failed to get supply 'AVDD': -517
[ 36.176536] pcm512x 1-004d: Failed to get supplies: -517
[ 36.191753] pcm512x 1-004d: Failed to get supply 'AVDD': -517[/code]
--- End quote ---
It will appear like this in your post:
--- Code: ---[ 36.176529] pcm512x 1-004d: Failed to get supply 'AVDD': -517
[ 36.176536] pcm512x 1-004d: Failed to get supplies: -517
[ 36.191753] pcm512x 1-004d: Failed to get supply 'AVDD': -517
--- End code ---
Code Tags serve as visual markers between what you are trying to say and the information you are posting. They also preserve
spacing so column aligned data displays properly. Code tags also automatically add horizontal and or vertical scrollbars
to accommodate long lines and listings.
patrikg:
Make it easy for you and begin with raspberryos, and get it working with your display.
And then transfer all logic and knowledge to diet picore.
segfault:
--- Quote from: Juanito on October 17, 2024, 03:52:23 PM ---libgallium is in mesa - mesa was updated today, have you checked for updates?
--- End quote ---
Ok, I tried it and while it did solve the missing .so files desktop failed to boot. Same SDCARD worked fine on my RPB4 though.
--- Quote from: Rich on October 17, 2024, 04:32:13 PM ---Please use Code Tags when posting commands and responses seen in a terminal.
--- End quote ---
Oh sorry. :-[ Will do!
--- Quote from: patrikg on October 17, 2024, 04:59:33 PM ---...begin with raspberryos...
--- End quote ---
Good idea. 8) I will do this. I downloaded Raspberry OS Lite and the display works fine there. I will create a diff of the OS before and after I run the adafruit install script. This way I guess I will be able to find changes to config files, etc.
Rich:
Hi segfault
Comparing dmesg between a working and non-working setup
can provide valuable information about what the kernel is
doing as it's starting up.
segfault:
I installed Raspberry Pi OS and my Adafruit PiTFT display. Display works perfectly. I used dmesg as Rich suggested (thanks! :)) and found at that it uses fb_hx8357d.
I rebooted my picore15. I don't have /dev/fb1 and there is no mention of hx8357d when I run dmesg. Therefore I tried to manually load the driver using sudo modprobe fb_hx8357d but it wasn't available.
I used uname -a to find out machine/os info:
--- Code: ---tc@box:~$ uname -a
Linux box 6.6.47-piCore-v7 #20 SMP Sat Aug 31 14:54:55 EDT 2024 armv7l GNU/Linux
--- End code ---
and proceeded to downloaded drivers from this link http://tinycorelinux.net/15.x/armhf/releases/RPi/src/kernel/modules-6.6.47-piCore-v7l.tar.xz. I create my own .TCZ package, installed it and rebooted the computer. My TCE has a tce.sh script that copies the fb_hx8357d.to I extacted from the download, to /lib/modules/6.6.47-piCore-v7/kernel/drivers/video/fb_hx8357d.ko.
After rebooting my picore, I get this:
--- Code: ---tc@box:~$ sudo modprobe fb_hx8357d
modprobe: can't load module fb_hx8357d (kernel/drivers/video/fb_hx8357d.ko): invalid module format
--- End code ---
Strange... I verified again that my OS matches with the downloaded resources (and it did) and the date 31 Aug, is also the same.
Am I on the right track at all here? :o
Should I try with some other versions of picore or other download link for fb_hx8357d?
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version