WelcomeWelcome | FAQFAQ | DownloadsDownloads | WikiWiki

Recent Posts

Pages: [1] 2 3 ... 10
1
Raspberry Pi / Re: Submitted extensions received ok?
« Last post by Rich on Today at 09:26:44 AM »
Hi rhermsen
Last I heard, we lost access to picoresubmit.

Please send it to tcesubmit and include in your message
Which TC version and architecture your submission is for.
2
TCE Talk / Re: 0ad game error: "Failed to compile shader" (TCL16 x86_64)
« Last post by GNUser on Today at 09:08:55 AM »
I think that's just the softwares way of politely saying "you're screwed" ::)

Hi Rich. Yeah, that's a great paraphrase ;D

I don't have time to investigate this further. Sorry for the noise.

Happy hacking :)
3
Raspberry Pi / Submitted extensions received ok?
« Last post by rhermsen on Today at 09:01:54 AM »
A week of 6 or 7 ago I submitted two extensions via email to picoresubmit.
I wonder if they have been received ok.

I have not seen any updates on the list lately:
http://tinycorelinux.net/15.x/armhf/tcz/updates/updatelist.txt
4
TCE Talk / Re: DIG Package
« Last post by ronan on Today at 08:45:16 AM »
I could indeed try, but I expect that at some point it will not work. Wonder why it is present in 9.x but not in 15. ?
5
Final Releases / Re: Tiny Core v16.0
« Last post by CNK on April 03, 2025, 06:42:03 PM »
Before we think about recompiling the kernel, you might want to ask the kernel people why the patch wasn't included?

OK, I'll ask there on the weekend. I figured I'd better test the patch myself before doing that, so I compiled the TC16 kernel with the patch applied, and sure enough it no longer reboots at start-up on my 486s. It does need >16MB of RAM now too though, since on the laptop the boot fails later when it runs out of memory (with error messages though).

Also that kernel boots on my VIA C7-M system. Maybe because I used GCC v12 to build it instead of the newer GCC Juanito used (GCC v14). I haven't tested for hangs during use (that might need rebuilding glibc with an older GCC version too?). I'm not suggesting TC16 revert to older GCC, just posting my observations.
6
TCE Talk / Re: 0ad game error: "Failed to compile shader" (TCL16 x86_64)
« Last post by Rich on April 03, 2025, 03:12:59 PM »
Hi GNUser
... P.S. I just noted how strange it is that first it says that GLSL 4.30 is not supported, then it says GLSL 4.30 (or GLSL ES 3.10) is required.
I think that's just the softwares way of politely saying "you're screwed" ::)
7
TCE Talk / Re: 0ad game error: "Failed to compile shader" (TCL16 x86_64)
« Last post by GNUser on April 03, 2025, 02:10:45 PM »
I discovered that 0ad writes log files to ~/.config/0ad/logs. The logs are attached (the errors that apper on the title screen also appear in mainlog.html).
8
TCE Talk / 0ad game error: "Failed to compile shader" (TCL16 x86_64)
« Last post by GNUser on April 03, 2025, 01:37:02 PM »
At this point, 0ad is only game that's not working perfectly on TCL16. I'm trying to run the AppImage for 0ad version 0.27 available here.

Game seems to successfully start, but I see this error message superimposed on the title screen:
Code: [Select]
error: Failed to compile shader 'shaders/glsl/compute_upscale_fsr.cs':
error: 0:1(10): error: GLSL 4.30 is not supported. Supported versions are: 1.10, 1.20, 1.30, 1.40, 1.50, 3.30, 4.00, 4.10, 4.20, 1.00 ES, and 3.00 ES.
error: 0:0(0): error: Compute shaders require GLSL 4.30 or GLSL ES 3.10
Followed by similar errors related to  shaders/glsl/compute_rcas.cs  and  shaders/glsl/compute_downscale.cs

Game is sometimes playable after those errors scroll by, sometimes crashes. When quitting from game, X consistently crashes.

Any ideas how to make these errors go away? I already tried everything I learned in this thread but nothing there seems to help with this.

P.S. I just noted how strange it is that first it says that GLSL 4.30 is not supported, then it says GLSL 4.30 (or GLSL ES 3.10) is required.
9
Hi GNUser
... The thread may be marked as Solved.
Done. :)
10
TCE Q&A Forum / Re: openssh connection refused
« Last post by Rich on April 03, 2025, 11:35:32 AM »
Hi cparke
... Quite surprising that such a simple and commonly used tool doesn't work in Tinycore even after so much time!
It does work. The end user can either copy the included config file
example, or create one that meets their needs.

The error message is a reminder that it's your job to figure out how
you need openssh configured. There's no universal config file that
will meet everyones needs, so a default is not placed where openssh
would find it.
Pages: [1] 2 3 ... 10