Tiny Core Base > Release Candidate Testing
Core v17.0beta1
Juanito:
--- Quote from: andyj on January 27, 2026, 05:41:21 PM ---I still think the 64-bit problem is an FLWM problem, but I can't prove it yet.
--- End quote ---
It's possible - in the x86 repo flwm is built against fltk-1.3, which supports x11 only. In the x86_64 repo flwm is built against fltk-1.4, which supports wayland and x11.
Rich:
Hi andyj
--- Quote from: andyj on January 27, 2026, 05:41:21 PM --- ... and unlike 64-bit, it works correctly after cycling through the monitors. I still think the 64-bit problem is an FLWM problem, but I can't prove it yet. ...
--- End quote ---
I would think Xorg sets the screen resolution, not FLWM.
There is one new feature in FLWM that may be coming into play:
--- Quote from: MikeLockmoore on May 03, 2025, 02:56:38 PM --- ... What does this mean? The biggest difference is that FLTK 1.3 does not support built-in fractional scaling of GUI applications, so you can't zoom the size of Fluff in the 32-bit version like you can the 64-bit version, ...
--- End quote ---
Does your environment include FLTK_SCALING_FACTOR= being exported?
What is the Xft.dpi setting in .Xdefaults? See:
https://forum.tinycorelinux.net/index.php/topic,27517.msg177719.html#msg177719
andyj:
The issue I'm having with 64-bit FLWM doesn't have anything to do with scaling. The scaling never changes when resizing the window, it's the virtual display resolution that changes. Everything looks right, I don't see anything not drawn right or other artifacts. The issue is after cycling in 64-bit, when a new window is opened, generally using wbar, instead of opening in the upper left at 0,0 it opens in the middle of the screen. 32-bit doesn't do this, it continues to open at 0,0 as before.
CNK:
Core 17.0beta1 boots fine on my AM486DX2-66 PC with 20MB RAM (HDD install).
Stories of Linux's 486 support being removed already have been greatly exaggerated!
CNK:
Core v17.0beta1 also boots on my HP 2533t with its VIA C7-M CPU, which didn't work with TC16.
It does still need "acpi=off" on the kernel command line or it reboots during start-up.
I tried this lock-up test script and it completes without issue too. So it seems the VIA C7 lock-up problem is fixed, whatever it was that caused it before.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version