Tiny Core Base > Alpha Releases
Tiny Core 16.0 Alpha 1 Testing
MikeLockmoore:
I got the FLTK apps rescaled bigger by changing the Xft.dpi setting in .Xdefaults. I tried 120.0 (133% bigger than default 96.0), but I think I could live with 120.0 (125% bigger than default 96.0) fairly well.
However, there is an issue with FLWM in this mode that the title bar does not grow to show the fully-scaled font and the window sizing buttons disappear, which I think @Juanito has noted before. When I have some time over the next week, I hope to look into this and try to develop a patch for FLWM to better handle the window scaling. If we can also support scaling FLTK aps up above 100%, I'd like to do that too, but at least changing the Xft.dpi in .Xdefaults gives me a bigger "100%" to start from. :D
I've attached a screenshot, which has a lot of whitespace to help it compress to within the required size limit.
--- Quote from: Juanito on February 24, 2025, 11:12:11 AM ---Depending on your graphics card, you could try Xorg-7.7-3d to use hardware acceleration if you have a compatible gpu.
--- End quote ---
Thanks for letting me know about this, but with just the thinkpad-acpi extension, it is running fairly well... perfectly usable like this. If I feel the need to do something with real 3D rendering, I could look into that.
Juanito:
I looked under linux-6.12.11/drivers/net/wireless/realtek/rtw88 and don't see that /lib/firmware is hard coded anywhere.
I see this in the kernel config:
--- Code: ---# Firmware loader
#
CONFIG_FW_LOADER=y
CONFIG_EXTRA_FIRMWARE=""
--- End code ---
..but it's not been set to anything as far back as tc-10.x
I also see this:
--- Code: ---/tmp/linux-6.12.11/drivers/base/firmware_loader/Kconfig: the directory specified by the EXTRA_FIRMWARE_DIR option, which is
/tmp/linux-6.12.11/drivers/base/firmware_loader/Kconfig:config EXTRA_FIRMWARE_DIR
/tmp/linux-6.12.11/drivers/base/firmware_loader/builtin/Makefile:# Create $(fwdir) from $(CONFIG_EXTRA_FIRMWARE_DIR) -- if it doesn't have a
/tmp/linux-6.12.11/drivers/base/firmware_loader/builtin/Makefile:fwdir := $(CONFIG_EXTRA_FIRMWARE_DIR)
--- End code ---
..but I wonder if this is for firmware blobs to be built in to the kernel.
I have a couple of devices that require firmware and both load it from /usr/local/lib/firmware without problems.
Juanito:
--- Quote from: MikeLockmoore on February 24, 2025, 11:14:45 AM ---However, there is an issue with FLWM in this mode that the title bar does not grow to show the fully-scaled font and the window sizing buttons disappear, which I think @Juanito has noted before.
--- End quote ---
That was referring to enlarging a window by dragging - prior to the patch to flwm, enlarging a window in flwm_topside would result in the window border and buttons disappearing, which was fixed by the patch.
Knoppix1337:
Ok, sorta rude awakening this morning.
Yesterday I ran the printk kernel with the #!/bin/sh version of the script to make sure it indeed locks up, and it did after 170,000 loop iterations (I changed the echo to print the loop number instead of a dot and increased the number of loops)
Then I did as you listed;
installed coreutils + bash, ran ps, killed processes, changed the script to #!/bin/bash, and ran the script overnight.
It locked after 348,000 iterations.
So what can we try next?
Rich:
Hi Juanito
I took a look at the Kconfig file and it lists:
--- Code: ---config EXTRA_FIRMWARE
string "Build named firmware blobs into the kernel binary"
--- End code ---
You set it like this:
--- Code: ---EXTRA_FIRMWARE="foo.bin bar.bin etc.bin"
--- End code ---
Then there is:
--- Code: ---config EXTRA_FIRMWARE_DIR
string "Firmware blobs root directory"
depends on EXTRA_FIRMWARE != ""
default "/lib/firmware"
--- End code ---
It's where the build system gets the firmware it's compiling into the kernel.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version