Recent Posts

31

General dCore Talk / gui install?

« Last post by LubielTheStoopid on September 15, 2025, 08:30:02 AM »

just pass the text to install the gui i can figure out the rest hopefully

32

Off-Topic - Tiny Core Lounge / Re: Octa core Risc V .....sbc

« Last post by gadget42 on September 15, 2025, 01:21:20 AM »

did a quick forum search for "riscv" and this seems like the best place to post this interesting work(yes it is oldish circa 2020):

direct pdf link:
https://www.openbsd.org/papers/Porting_OpenBSD_to_RISCV_FinalReport.pdf

found via:
https://lobste.rs/s/koetct/porting_openbsd_risc_v_isa_2020
via:
https://lobste.rs/t/openbsd

33

General TC Talk / Re: Recommended hosts file blocklist ?

« Last post by gadget42 on September 14, 2025, 04:18:47 PM »

another good write-up: cloudflare 20250912 dashboard and api outage

https://blog.cloudflare.com/deep-dive-into-cloudflares-sept-12-dashboard-and-api-outage/

34

TCE Tips & Tricks / Re: firefox 144 as last version for x86 (32 bits)?

« Last post by nick65go on September 13, 2025, 09:12:57 AM »

Probably someone compile Firefox from source code in 32-bit Linux, if libraries will be compatible.

Wow, so your hope is that someone (unknown person) will share somewhere (on a not trusted site) few times in a year, for many years, a binary for a browser, then I wish you all the best for your fortune/wealth.

35

TCE Tips & Tricks / Re: firefox 144 as last version for x86 (32 bits)?

« Last post by neonix on September 13, 2025, 07:20:03 AM »

Most probably, old hardware will decode 144p video, even with new codecs.

Probably someone compile Firefox from source code in 32-bit Linux, if libraries will be compatible.

Firefox has about 4% market share, and if Mozilla won't find out new source of money, the project will decline.

Online banking is not problem on old browser, if you have good one-time password mechanism, and you don't alocatte your fortune in one bank, and online banking is designed to protect any movement of money with one-time password.

36

TCE Tips & Tricks / Re: firefox 144 as last version for x86 (32 bits)?

« Last post by nick65go on September 12, 2025, 10:00:54 AM »

Maybe some of you did not understand the main concern. It does not matter if it runs on linux or windows (Xp, w10-12 etc). It matters that the current version that you run to be up to date regarding the securities holes to be patched. and to be capable to decode the latest internet movies.

Or else, (if you just want to browse the internet for reading text files or downloading some archives), you do not need the latest Firefox. Just use wget or curl to download something. Or dillo, netsurtf, elinks or even an very old firefox/chrome/palemon whatever to read web pages.

Anyway the old hardware will NOT be able to decode latest codes on you-tube in real time. My humble recommendation, do not even think about banking of financing online with the old Firefox. YMMV.

37

Raspberry Pi / Re: Upgrading piCore 13 to run on Raspberry Pi 5

« Last post by Rabie on September 12, 2025, 09:27:22 AM »

yes i have it in my config.txt

Code: [Select]

cat /mnt/mmcblk0p1/config.txt
# For more options and information see
# http://rpf.io/configtxt
# Some settings may impact device functionality. See link above for details

# RPi PI0-1-2 are not supported on this image.

[PI02]
initramfs rootfs-piCore64-16.0.gz,modules-6.12.25-piCore-v8.gz followkernel
kernel kernel61225v8.img

[PI3]
initramfs rootfs-piCore64-16.0.gz,modules-6.12.25-piCore-v8.gz followkernel
kernel kernel61225v8.img

[PI4]
initramfs rootfs-piCore64-16.0.gz,modules-6.12.25-piCore-v8.gz followkernel
kernel kernel61225v8.img

[PI5]
initramfs rootfs-piCore64-16.0.gz,modules-6.12.25-piCore-v8-16k.gz followkernel
kernel kernel61225v8-16k.img

[CM4]
otg_mode=1

[cm5]
dtoverlay=dwc2,dr_mode=host

[ALL]
cmdline cmdline.txt

# Run in 64-bit mode
arm_64bit=1

# Run as fast as firmware / board allows
arm_boost=1

# uncomment if you get no picture on HDMI for a default "safe" mode
#hdmi_safe=1

# uncomment this if your display has a black border of unused pixels visible
# and your display can output without overscan
#disable_overscan=1

# uncomment the following to adjust overscan. Use positive numbers if console
# goes off screen, and negative if there is too much border
#overscan_left=16
#overscan_right=16
#overscan_top=16
#overscan_bottom=16

# uncomment to force a console size. By default it will be display's size minus
# overscan.
# Does not work with the vc4 driver.

#framebuffer_width=1280
#framebuffer_height=720

# uncomment if hdmi display is not detected and composite is being output
#hdmi_force_hotplug=1

# Uncomment some or all of these to enable the optional hardware interfaces
#dtparam=i2c_arm=on
#dtparam=i2s=on
#dtparam=spi=on

# Additional overlays and parameters are documented /mnt/mmcblk0p1/overlays/README

# Enable audio (loads snd_bcm2835)
dtparam=audio=on

[PI5]
# Don't have the firmware create an initial video= setting in cmdline.txt.
# Use the kernel's default instead.
disable_fw_kms_setup=1

[all]
# Enable DRM VC4 V3D driver
dtoverlay=vc4-kms-v3d
max_framebuffers=2

But i improvised and created the following file:

Code: [Select]

sudo nano /etc/X11/xorg.conf

Section "Device"
    Identifier  "Framebuffer"
    Driver      "fbdev"
    Option      "fbdev" "/dev/fb0"
EndSection

Section "Screen"
    Identifier "Default Screen"
    Device "Framebuffer"
EndSection

After that, X started immediately on reboot!

Is it actually a bad idea to use the framebuffer fb0?
Because technically, the two HDMI outputs are called card0 and card1.

the next question is whether this setup will also work with the 32-bit version.
The reason I ask is that there are a few extensions available in the 32-bit version that are missing in the 64-bit one.

38

Raspberry Pi / Re: Upgrading piCore 13 to run on Raspberry Pi 5

« Last post by Juanito on September 12, 2025, 08:43:37 AM »

You should see:

Code: [Select]

[     2.886] (II) xfree86: Adding drm device (/dev/dri/card0)
[     2.886] (II) Platform probe for /sys/devices/platform/axi/1002000000.v3d/drm/card0
[     2.886] (II) xfree86: Adding drm device (/dev/dri/card1)
[     2.886] (II) Platform probe for /sys/devices/platform/axi/axi:gpu/drm/card1
[     2.891] (**) OutputClass "vc4" setting /dev/dri/card1 as PrimaryGPU

39

Raspberry Pi / Re: Upgrading piCore 13 to run on Raspberry Pi 5

« Last post by Juanito on September 12, 2025, 08:41:20 AM »

Do you have this in config.txt:

Code: [Select]

[PI5]
# Don't have the firmware create an initial video= setting in cmdline.txt.
# Use the kernel's default instead.
disable_fw_kms_setup=1

[all]
# Enable DRM VC4 V3D driver
dtoverlay=vc4-kms-v3d
max_framebuffers=2

40

Raspberry Pi / Re: Upgrading piCore 13 to run on Raspberry Pi 5

« Last post by Rich on September 12, 2025, 08:39:21 AM »

Hi Rabie
I don't run any Pi hardware myself, so this is just an observation.
Your log shows it detecting  /dev/dri/card0 , which is what I would expect:

Code: [Select]

----- Snip -----
[     2.452] (II) xfree86: Adding drm device (/dev/dri/card0)
[     2.452] (II) Platform probe for /sys/devices/platform/axi/1002000000.v3d/drm/card0
[     2.452] (II) no primary bus or device found
[     2.452]    falling back to /sys/devices/platform/axi/1002000000.v3d/drm/card0
 ----- Snip -----
Yet for some reason it tries to use a non-existant /dev/fb0:

Code: [Select]

----- Snip -----
[     2.466] (EE) open /dev/fb0: No such file or directory
 ----- Snip -----
I suspect either something in  config.txt  or  cmdline.txt  needs to be adjusted.