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. 

I've attached a screenshot, which has a lot of whitespace to help it compress to within the required size limit.

Depending on your graphics card, you could try Xorg-7.7-3d to use hardware acceleration if you have a compatible gpu.

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: [Select]

# Firmware loader
#
CONFIG_FW_LOADER=y
CONFIG_EXTRA_FIRMWARE=""..but it's not been set to anything as far back as tc-10.x

I also see this:

Code: [Select]

/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)..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]

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.

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: [Select]

config EXTRA_FIRMWARE
        string "Build named firmware blobs into the kernel binary"You set it like this:

Code: [Select]

EXTRA_FIRMWARE="foo.bin bar.bin etc.bin"
Then there is:

Code: [Select]

config EXTRA_FIRMWARE_DIR
        string "Firmware blobs root directory"
        depends on EXTRA_FIRMWARE != ""
        default "/lib/firmware"It's where the build system gets the firmware it's compiling into the kernel.

[Rich]

Knoppix1337
I think it's as curaga said:

It's a kernel bug of some kind, but it will be hard to track down without messages, if you can't compile the kernel and try to bisect where it broke down.

I'm not sure where to go from here.

Just my opinion, but unless you have some compelling reason to
move to TC16, you might want to consider sticking with TC15 if
it works on your system.

[MikeLockmoore]

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.

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.

Yes, if I have Xft.dpi at the default resolution of 96.0 dots per inch, the titlebars look fine and the window size buttons are visible.  I've also discovered that the Ctrl+"Plus" really means you need to use the shift key to get the "+" character (Ctrl + Shift + "+") to make the windows grow, and it is perfectly capable of growing above 100%.  However, the window title bar and buttons do not scale with the other FLTK GUI elements inside the window, either smaller or larger.  Maybe this is OK if the Xft.dpi setting in the .Xdefaults file was honored by FLWM for the window frame & decoration.

I must say, the scaled-up text for scaled-up button labels, etc. looks quite nice and smooth.  The ControlPanel app is scaled to 200% in this screen shot and Fluff at 150% I think.
. 

[Knoppix1337]

Some users are reporting that firmware will not load from /usr/local/lib/firmware - has anybody else seen this problem?

Is it something like this?

Got the following message when booting my HP 2133, took a picture, but it was too large, so I used an on-line jpeg to ocr converter

Core is distributed with ABSOLUTELY NO WARRANTY. www.tinycorelinux.net
tc@box:'$ tg3 0000:07:03.0: Direct firmware load for tigon/tg3_tso5.bin failed with error -2
tg3 0000:07:03.0: Falling back to sysfs fallback for:  tigon/tg3_tso5.bin
tg3 0000:07:03.0 eth0: Failed to load firmware "tigon/taJso5.bin"
tg3 0000:07:03.0 eth0: TSO capability disabled

Let me know if you need me to try anything on this machine.

[MikeLockmoore]

Some users are reporting that firmware will not load from /usr/local/lib/firmware - has anybody else seen this problem?

To use my built-in Intel WiFi adapter in my ThinkPad, I'm using the firmware-iwlwifi extension without issue.  Running on WiFi at the moment, actually!
--
Mike

Code: [Select]

ccm 16384 6 - Live 0x0000000000000000
cpufreq_conservative 12288 0 - Live 0x0000000000000000
cpufreq_powersave 12288 0 - Live 0x0000000000000000
cpufreq_userspace 12288 0 - Live 0x0000000000000000
snd_hda_codec_hdmi 49152 1 - Live 0x0000000000000000
iwlmvm 319488 0 - Live 0x0000000000000000
mac80211 425984 1 iwlmvm, Live 0x0000000000000000
i915 2289664 4 - Live 0x0000000000000000
joydev 20480 0 - Live 0x0000000000000000
drm_display_helper 114688 1 i915, Live 0x0000000000000000
iwlwifi 253952 1 iwlmvm, Live 0x0000000000000000
drm_kms_helper 102400 2 i915,drm_display_helper, Live 0x0000000000000000
thinkpad_acpi 81920 0 - Live 0x0000000000000000
sparse_keymap 12288 1 thinkpad_acpi, Live 0x0000000000000000
intel_gtt 16384 1 i915, Live 0x0000000000000000
snd_ctl_led 20480 0 - Live 0x0000000000000000
cfg80211 303104 3 iwlmvm,mac80211,iwlwifi, Live 0x0000000000000000
snd_hda_codec_realtek 118784 1 - Live 0x0000000000000000
snd_hda_scodec_component 12288 1 snd_hda_codec_realtek, Live 0x0000000000000000
snd_hda_codec_generic 57344 1 snd_hda_codec_realtek, Live 0x0000000000000000
platform_profile 12288 1 thinkpad_acpi, Live 0x0000000000000000
snd_hda_intel 28672 0 - Live 0x0000000000000000
snd_hda_codec 81920 4 snd_hda_codec_hdmi,snd_hda_codec_realtek,snd_hda_codec_generic,snd_hda_intel, Live 0x0000000000000000
ttm 49152 1 i915, Live 0x0000000000000000
agpgart 28672 2 intel_gtt,ttm, Live 0x0000000000000000
drm_buddy 16384 1 i915, Live 0x0000000000000000
drm 348160 8 i915,drm_display_helper,drm_kms_helper,thinkpad_acpi,ttm,drm_buddy, Live 0x0000000000000000
snd_hda_core 49152 5 snd_hda_codec_hdmi,snd_hda_codec_realtek,snd_hda_codec_generic,snd_hda_intel,snd_hda_codec, Live 0x0000000000000000
snd_hwdep 12288 1 snd_hda_codec, Live 0x0000000000000000
snd_intel_dspcfg 12288 1 snd_hda_intel, Live 0x0000000000000000
i2c_i801 24576 0 - Live 0x0000000000000000
i2c_smbus 12288 1 i2c_i801, Live 0x0000000000000000
snd_pcm 86016 4 snd_hda_codec_hdmi,snd_hda_intel,snd_hda_codec,snd_hda_core, Live 0x0000000000000000
snd_timer 24576 1 snd_pcm, Live 0x0000000000000000
snd 65536 10 snd_hda_codec_hdmi,thinkpad_acpi,snd_ctl_led,snd_hda_codec_realtek,snd_hda_codec_generic,snd_hda_intel,snd_hda_codec,snd_hwdep,snd_pcm,snd_timer, Live 0x0000000000000000
soundcore 12288 2 snd_ctl_led,snd, Live 0x0000000000000000
cec 36864 2 i915,drm_display_helper, Live 0x0000000000000000
rtsx_pci_sdmmc 20480 0 - Live 0x0000000000000000
mmc_core 110592 1 rtsx_pci_sdmmc, Live 0x0000000000000000
mei_hdcp 12288 0 - Live 0x0000000000000000
think_lmi 24576 0 - Live 0x0000000000000000
wmi_bmof 12288 0 - Live 0x0000000000000000
firmware_attributes_class 12288 1 think_lmi, Live 0x0000000000000000
squashfs 40960 210 - Live 0x0000000000000000
pcspkr 12288 0 - Live 0x0000000000000000
xhci_pci 16384 0 - Live 0x0000000000000000
e1000e 167936 0 - Live 0x0000000000000000
rtsx_pci 61440 1 rtsx_pci_sdmmc, Live 0x0000000000000000
ac 12288 0 - Live 0x0000000000000000
xhci_hcd 114688 1 xhci_pci, Live 0x0000000000000000
mei_me 24576 1 - Live 0x0000000000000000
mei 69632 3 mei_hdcp,mei_me, Live 0x0000000000000000
battery 16384 1 thinkpad_acpi, Live 0x0000000000000000
video 57344 2 i915,thinkpad_acpi, Live 0x0000000000000000
backlight 12288 5 i915,drm_display_helper,thinkpad_acpi,drm,video, Live 0x0000000000000000
loop 24576 420 - Live 0x0000000000000000
lpc_ich 24576 0 - Live 0x0000000000000000
wmi 16384 3 think_lmi,wmi_bmof,video, Live 0x0000000000000000
intel_smartconnect 12288 0 - Live 0x0000000000000000


[Rich]

Hi Knoppix1337

Is it something like this? ...

Yes, but typically it should find it after the firmware extension is
loaded, firmware-tigon.tcz in your case.

[Juanito]

Yes, if I have Xft.dpi at the default resolution of 96.0 dots per inch, the titlebars look fine and the window size buttons are visible.  I've also discovered that the Ctrl+"Plus" really means you need to use the shift key to get the "+" character (Ctrl + Shift + "+") to make the windows grow, and it is perfectly capable of growing above 100%.  However, the window title bar and buttons do not scale with the other FLTK GUI elements inside the window, either smaller or larger.  Maybe this is OK if the Xft.dpi setting in the .Xdefaults file was honored by FLWM for the window frame & decoration.

I must say, the scaled-up text for scaled-up button labels, etc. looks quite nice and smooth.  The ControlPanel app is scaled to 200% in this screen shot and Fluff at 150% I think.

Does the scaling require a scalable font defined in flwm/config.h or will it work with a fixed font?

[Juanito]

flwm/flwm_topside in the tc-16.x x86 repo have been recompiled against the latest fltk-1.3 and the font has been set to the flwm default by un-commenting the following in config.h, which was commented out previously.

#define TITLE_FONT "-*-helvetica-medium-r-normal--*"

[Juanito]

Using tc-16.x and Xorg-7.7, I can start the gui once, although there is a faint coloured band at the top of the screen, which disappears once the gui is fully started.

If I try to exit to the console prompt I get a blank screen or a screen with a couple of green squares only recoverable by cycling the power.

This is on a dell e7240 laptop using intel haswell hd graphics 4400.

This seems to be a worsening problem with x86, it doesn't happen with x86_64.

Also with x86 the Xorg-7.7-3d/modesetting driver combination will not start, but Xorg-7.7-3d/xf86-video-intel will start, whereas both start with x86_64.

It's my understanding that xf86-video-intel has been depreciated in favour of modesetting.

[MikeLockmoore]

flwm/flwm_topside in the tc-16.x x86 repo have been recompiled against the latest fltk-1.3 and the font has been set to the flwm default by un-commenting the following in config.h, which was commented out previously.

#define TITLE_FONT "-*-helvetica-medium-r-normal--*"

On the x86_64 side, I've been experimenting with adding some fonts.  I used the notosans-fonts-ttf.tcz, plus I downloaded and manually installed two other font faces from Google's online font browser & repository... "Roboto" (similar to Lexi Sans and Noto Sans), and "Rancher" which is very stylized.  In this screenshot, I built FLWM to use Rancher for the titlebars, and I set the font size to something intentionally overly large to see the letter shapes more clearly.  Howdy, partner!

[Rich]

Hi MikeLockmoore
Open a terminal and try this under fltk-1.4:

Code: [Select]

export FLTK_SCALING_FACTOR=1.3
apps
Does that help you with regard to scaling fltk apps?