WelcomeWelcome | FAQFAQ | DownloadsDownloads | WikiWiki

Recent Posts

Pages: 1 ... 8 9 [10]
91
TCB Bugs / Re: Wiki login problem
« Last post by Paul_123 on July 15, 2024, 06:42:28 AM »
I see your avatar is missing, was that a recent upload?  The file backup was a couple of weeks old, the database was fresh.
92
TCB Bugs / Re: Wiki login problem
« Last post by bernhard on July 15, 2024, 06:40:12 AM »
with Forums and Wiki migration to new server  the problems are resolved. Many thanks and congratulations to Paul_123
93
Raspberry Pi / Re: libcamera
« Last post by segfault on July 15, 2024, 05:49:53 AM »
On TC13 lsmod does list i2c-mux and i2c-mux-pinctrl-pinctrl along with imx219, but on TC14 it does not. I discovered a useful tool insmod with which I could load imx219 from the kernel.tclocal and then it shows up in lsmod also on TC14. But I don't find the i2c muxes folder on TC14 at all... maybe it was built into the kernel and just a red herring.

But I guess that perhaps it's noteworthy that imx219 doesn't show up on TC14, even though I got camera_auto_detect, start_x and dtoverlay=im219 in the config file, along with dtparam=i2c_arm=on.
94
Raspberry Pi / Re: libcamera
« Last post by segfault on July 15, 2024, 04:56:12 AM »
Thank for the input Rich! 8)

I'm a JavaScript developer and not well versed in the intricacies of Linux, so there be dragons. Anyway since I don't know much about how Linux works, I created a delta between TC13 and TC14 and started to compare the two.

Studying the delta of dmesg logs, I noticed that something called imx219 was not showing up in TC14 while in TC13 it is ("imx219 10-0010: Consider updating driver imx219 to match on endpoints"). imx219 sees to be related to picamera. It also seems as though imx219 is dependent on i2c. While lsmod on TC14 does lists i2c, when I run cat /lib/modules/<piCore-version>/modules.dep and compared the two, there was a lot of i2c use on TC13, but in the kernel dep on TC14, i2c is barely mentioned.  There is only one mention of imx219 on both of the systems: kernel.tclocal/drivers/media/i2c/imx219.ko but while im219 depends on kernel.tclocal/drivers/media/v4l2-core/v4l2-fwnode.ko kernel on TC13, on TC14 it depends on v4l2-async.ko (a ko that does not exist on TC13).

i2c and v4l2-async seems to serve different purposes.

Adding to config.txt: dtoverlay=imx219, startx=1 doesn't fix the problem, so this is where I'm at right now:
Maybe i2c is not properly loaded or something on TC14, or maybe v4l2-async fails at registering the camera.

Will investigate further...

95
Off-Topic - Tiny Core Lounge / Re: Documentaries about information technologies
« Last post by mocore on July 15, 2024, 04:50:51 AM »
not realy documentory but it is foundational (afaik) to much of our modern tech world
https://en.wikipedia.org/wiki/The_Mother_of_All_Demos


what is the perpose of the list btw? ( hopfuly not for training athropomohised ML!! ;-)
96
General TC Talk / Re: Forums and Wiki migration to new server
« Last post by mocore on July 15, 2024, 04:26:02 AM »
+1
thanks!
97
General TC Talk / Forums and Wiki migration to new server
« Last post by Leee on July 15, 2024, 12:44:34 AM »
Regarding Forums and Wiki migration to new server - Thanks and congratulations to Paul_123 and the team for handling this!  Bringing the wiki back to life is -huge-.

98
piCore Test Releases / Re: piCore15.0 Beta
« Last post by Juanito on July 14, 2024, 10:48:16 AM »
Yes, it’s there
99
piCore Test Releases / Re: piCore15.0 Beta
« Last post by Paul_123 on July 14, 2024, 10:20:17 AM »
Can you check to make sure I added the vc4.conf file?
100
piCore Test Releases / Re: piCore15.0 Beta
« Last post by Juanito on July 14, 2024, 10:12:24 AM »
I just updated to piCore15.0 Beta armhf by copying over files to an sd card containing piCore-13.x running on an RPi3.

piCore-15.x booted and after copying over xorg-server (for the vc4 snippet) and graphics-KERNEL, the gui started.

I then updated all the extensions (due to the change in squashfs block size they are all marked for update) and now the gui will not start.

* I added the missing cairo dep to the harfbuzz dep file
* I created the missing llvm15-lib dep file containing gcc_libs, libzstd, ncurses and libxml2
* cairo-sphinx is missing a dep on pcre (this will probably disappear if compiled without pcre present).

There are no errors in Xorg.0.log, it looks like a normal startup - xorg does not start from boot due to the race condition loading modules, but starts with startx to a blank screen.

Strangely the screen comes up at 2048x1152, when I would have expected it to come up at 4khd or hd, but perhaps that's a limitation of the RPi3. If I add a snippet to set the screen to 1920x1080, it still comes up blank.

dmesg gives this:
Code: [Select]
dmesg | grep vc4
[    7.330096] vc4-drm soc:gpu: bound 3f400000.hvs (ops vc4_hvs_ops [vc4])
[    7.338553] rc rc0: vc4-hdmi as /devices/platform/soc/3f902000.hdmi/rc/rc0
[    7.339287] input: vc4-hdmi as /devices/platform/soc/3f902000.hdmi/rc/rc0/input0
[   17.755263] vc4-drm soc:gpu: bound 3f400000.hvs (ops vc4_hvs_ops [vc4])
[   17.757370] rc rc0: vc4-hdmi as /devices/platform/soc/3f902000.hdmi/rc/rc0
[   17.757667] input: vc4-hdmi as /devices/platform/soc/3f902000.hdmi/rc/rc0/input1
[   17.766294] input: vc4-hdmi HDMI Jack as /devices/platform/soc/3f902000.hdmi/sound/card1/input2
[   17.767677] vc4-drm soc:gpu: bound 3f902000.hdmi (ops vc4_hdmi_ops [vc4])
[   17.768153] vc4-drm soc:gpu: bound 3f004000.txp (ops vc4_txp_ops [vc4])
[   17.768499] vc4-drm soc:gpu: bound 3f206000.pixelvalve (ops vc4_crtc_ops [vc4])
[   17.768826] vc4-drm soc:gpu: bound 3f207000.pixelvalve (ops vc4_crtc_ops [vc4])
[   17.769153] vc4-drm soc:gpu: bound 3f807000.pixelvalve (ops vc4_crtc_ops [vc4])
[   17.769413] vc4-drm soc:gpu: bound 3fc00000.v3d (ops vc4_v3d_ops [vc4])
[   17.775203] [drm] Initialized vc4 0.0.0 20140616 for soc:gpu on minor 0
[   17.778549] vc4-drm soc:gpu: [drm] Cannot find any crtc or sizes

Any ideas?
Pages: 1 ... 8 9 [10]