Tiny Core Base > piCore Final Releases
piCore-13.0.3 released (32-bit)
Rich:
Hi MrPorcine
--- Quote from: MrPorcine on May 12, 2021, 07:13:14 PM ---The kernel in the 13.0.3 release is 5.10.16. In the source folder http://tinycorelinux.net/www/13.x/armv6/releases/RPi/src/kernel/, the kernel is indeed 5.10.16. However, the .config and the module files are all 5.10.13. ...
--- End quote ---
You'll have to wait for bmarkus to sort that out.
--- Quote --- ... There is no more a module called rpi-ft5406 ...
--- End quote ---
I did a little digging, and I think I can shed a little light on that one. I downloaded and unpacked 5.10.13-piCore_modules.tar.xz.
Searching for ft5406 in the included modules.alias file returned edt-ft5406 among many others being handled by
kernel/drivers/input/touchscreen/edt-ft5x06. Maybe that's the driver you want?
Unfortunately, you won't be able to use anything from that modules file. I checked the vermagic value of the edt-ft5x06
driver and it is 5.10.13 so you won't be able to load it. You'll have to wait for bmarkus for this one too.
MrPorcine:
I modified the .config file and recompiled so the vermagic strings are the same on my newly compiled raspberrypi-ts.ko module and any other module that I checked in the 13.0.3 image. This is still not enough - apparently there is a check for identical data structures between the module and the kernel. So unless someone can suggest a path forward it looks like I'll have to wait for bmarcus.
I have X running, I'm not sure what the problem was earlier. Symptoms were that the screen went blank and you could not get back to a command prompt with <ctrl><alt>F1. One could still ssh in. Now, other than the touch screen not working, everything I need has worked so far.
Rich:
Hi MrPorcine
--- Quote from: MrPorcine on May 13, 2021, 06:08:20 PM --- ... Symptoms were that the screen went blank and you could not get back to a command prompt with <ctrl><alt>F1. ...
--- End quote ---
I think sometimes loading the graphics extension can cause that. Were you loading graphics-5.10.16-piCore.tcz ?
MrPorcine:
--- Quote from: Rich on May 13, 2021, 07:58:25 PM ---Hi MrPorcine
--- Quote from: MrPorcine on May 13, 2021, 06:08:20 PM --- ... Symptoms were that the screen went blank and you could not get back to a command prompt with <ctrl><alt>F1. ...
--- End quote ---
I think sometimes loading the graphics extension can cause that. Were you loading graphics-5.10.16-piCore.tcz ?
--- End quote ---
I don't think so. Symptoms were that the screen would flash once with the default background, then the UI would hang. I could either ssh in, or turn the machine off. I did add "dtoverlay=rpi-ft5406" to the config.txt file. Since the handling of the touchscreen has changed, this may have broken the system. I'm not doing that now.
My onboot.lst is pretty short:
--- Code: ---openssh.tcz
Xorg.tcz
busybox-httpd.tcz
minicom.tcz
inetutils.tcz
coreutils.tcz
--- End code ---
Xorg.tcz brings in a ton of dependencies. The display works now other than the touchscreen. My core app is working with a mouse. Next on my list is to get the HTTP server and the FTP server working.
MrPorcine:
I have X running (no touchscreen) on the 7" official Raspberry Pi touchscreen. I have seen some strange filesystem behavior, perhaps someone can explain what is going on.
The display uses xf86-video-fbturbo.tcz. This tcz adds two files, "/usr/local/share/X11/xorg.conf.d/fbturbo.conf" and "/usr/local/lib/xorg/modules/drivers/fbturbo_drv.so". So far so good. I need to add a few font files, so I added the folders 100dpi and 75dpi to the X font folder "/usr/local/lib/X11/fonts" Both the new folders only have a few fonts, so are pretty small. I restarted the X server and it restarted fine and found the new fonts.
I added these folders to "/opt/.filetool.lst", did a "filetool.sh -b" and rebooted. Xorg now failed because it couldn't find the fbturbo driver! When I looked at the filesystem, fbturbo.conf was present, but fbturbo_drv.so was not. I then checked "/tmp/tcloop/ xf86-video-fbturbo" and both files were present in the overlay. I rebooted a few time, it was always the same.
I then removed the 100dpi and 75dpi folders from .filetool.lst, did a filetool.sh -b and rebooted. fbturbo_drv.so reappeared so Xorg starts fine! So it appears that restoring files via the tcz mechanism and restoring files via the filetool mechanism sometimes interfere with each other. Is this known? Did I do something wrong?
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version