Recent Posts

21

General TC Talk / Re: Dedicated modern legacy CSM box for TinyCore

« Last post by PDP-8 on June 19, 2025, 06:44:56 PM »

That was fun.  I reset the bios to default (uefi only), and ran with the *latest* Ventoy and TinyCorePure64 again, manually setting up persistence with tce-setdrive.  Still left EMMC support disable in bios though.

The performance increase was noticeable, even with xfbdev.

22

Raspberry Pi / Re: Raspberry Pi 2 Wifi (nl80211, cheap dongle)

« Last post by bradwiggo on June 19, 2025, 07:15:43 AM »

Hi bradwiggo
While it is likely that device is supported, posting the
result of lsusb for an actual device is the best way to
know for sure.

Tp-link has used several different chipsets for this device.

Thanks, looking at buying one from Amazon.

Do you know if these models are supported?

Edimax EW-7811Un V2 (seems to use rt8192cu)
TP-Link Archer T2U Nano (uses rtl8812au according to AskUbuntu)
TP-Link Archer T3U Nano (AC1300) (I think it uses rtl88x2bu)
TP-Link Archer T2UB Nano (TL-WN725N) (rtl8188eu according to AskUbuntu)

(or is there a list somewhere, don't want to spam questions)

Update: Bought the TP-Link Archer T2UB Nano (TL-WN725N) from Amazon, will report back when it arrives.

23

Other architectures / Re: Which board to support?

« Last post by CentralWare on June 18, 2025, 04:34:20 PM »

@Béla,

+1 for OrangePi (RiscV and ARM both!)

I purchased a couple of the OrangePi RiscV boards but haven't had the time to really get my hands dirty with them yet as much as I would like.  (I did design/build an mITX adapter and case and have tested 6x SATA SSD drives with MDADM but other projects tore me away before much else was accomplished.)

24

Programming & Scripting - Unofficial / Re: Poor Man's cpu-frequency scaling monitor

« Last post by gadget42 on June 18, 2025, 08:05:07 AM »

mostly for the visitors of the future...

referencing previous post with image using "welcome to the colored toilet"

https://delightlylinux.wordpress.com/2015/11/13/colored-text-with-toilet/

25

TCE Talk / Re: DPMS and UTF-8 keyboard layouts in TinyX

« Last post by PDP-8 on June 18, 2025, 06:48:44 AM »

One of the reasons I LOVE 32-bit Tinycore, is that in xvesa, even if one does

Code: [Select]

xset q
and sees that DPMS is not active, a *modern* display (non-glass) will honor the old glass "screen blank" as if it were a dpms monitor shutdown!

Therefore, without having xorg loaded, I can change the two monitor shutdown values to say something longer:

Code: [Select]

xset s 1200 1200
However, using the old glass crt blanking with xset s does not work with 64-bit xfbdev, to trick a modern monitor to actually shutdown like 32-bit xvesa does.  One must load Xorg to get a "real" dpms shutdown.

I looked into this, and the whole screensaver vs dpms thing with Xorg gives most people gray hair, with BOTH screen blanking AND dpms fighting each other.

On most other distros that have a billion options for this, I found a way around it:

Objective:  Simply shut down the monitor after an hour.

TRICK:  To prevent fighting between screen blank and dpms on modern monitor, I set the screen blank to outer space out of the way, and use dpms to fire first.  I'll either do it manually or with a script, or add it to an "autostart" function of say XFCE, Openbox and the like.

Here is the simple XSET way to trick and only get a dpms shutdown after an hour:

Code: [Select]

xset s 5000 5000
xset dpms 3600 3600 3600
So when my monitor shuts down due to dpms after an hour, (3600) who cares if it later gets the old-school glass crt blank later on!! (5000)

Anyway, total thumbs up for 32-bit xvesa's in TC "acting like" a dpms shutdown with only the old school xset glass blanking with modern monitors!

26

TCB Bugs / Re: Black screen TinyCorePure64-15.0 and Ventoy

« Last post by PDP-8 on June 18, 2025, 05:19:48 AM »

Hi Vito - now you know why the Ventoy solution is unofficial.  I have replied elsewhere on the need to update to the latest, ver 1.104 or later, as it fixed a bug with booting the latest TinyCores.

I can verify that the one you are using here, ver 1.099 will NOT work.  Some people are hanging on to this version for the different way it handles Windows secure-boot.  Whatever - get the latest version if you want Ventoy to boot the TC 64-bit iso on modern uefi machines such as you have.

27

Corepure64 / Re: I can't install tiny core plus on usb

« Last post by PDP-8 on June 18, 2025, 04:28:02 AM »

Ah, "new computer" signifies a 64-bit one that is in UEFI mode for the most part.

And on these, any "dd" or dd-like utilities, even Rufus, won't boot the TC iso.  Not TC's fault.

One UNOFFICIAL solution is to use Ventoy (version 1.104 or later as it fixed an earlier Tc problem).  From either windows or linux versions, create the Ventoy usb drive.  Now copy the TinyCorePure64 iso onto it.  Found in the "Other Ports" section of the webpage.

Reboot into Ventoy passing into TinyCore.  In order to have persistence, in the aterm terminal, run

Code: [Select]

tce-setdrive
Point this to any writable storage you have.  I prefer either another usb stick formatted previously as ext2 as a data-only stick, but others might point to say their ext4 hard drive with the big linux distro.

You can now get a feel, save your stuff, applications, etc.

AND, if you desire to make a multi-boot 64-bit stand-alone without Ventoy, you have the tools available to follow Juanito's classic instructions here now that you are up and running!

This Ventoy / TC drive is similar to the old CD-rom boot days with an external tce-setdrive.  As such since it boots a read-only iso, to make any grub boot option changes, you can only do that during boot, interrupting the process with "e", make your changes, and F10 to continue.

(Ventoy has a way of externalizing this which I've detailed elsewhere here....)

Again, not TC's fault about the usual "dd" or "burn the iso" failing on uefi machines.  This workaround may whet your appetite!

28

Programming & Scripting - Unofficial / Re: Poor Man's cpu-frequency scaling monitor

« Last post by neonix on June 18, 2025, 03:54:04 AM »

Orr create fancy conky with figlet.

https://www.howtogeek.com/fun-linux-commands/
https://www.binarytides.com/linux-fun-commands/

29

TCB Q&A Forum / Re: Is there a way to boot Tiny Core from .iso on Ventoy (GPT)?

« Last post by PDP-8 on June 18, 2025, 12:40:42 AM »

Vito - There was a problem with booting the latest TC kernels.  This has been fixed since Ventoy 1.104, so get or update to the latest.

Seeing the date of your post, this might be the case.  Also, if you are running a modern uefi capable machine, then I'd suggest the 64-bit TinyCorePure64.

The TC 64-bit iso's can be found on the download page in the "Other Ports" window, not the main page which are the classic 32 bit versions.

30

TCB Bugs / Re: provides.sh pinging 8.8.8.8 --- bug or feature ? piCore 64 , 16.x

« Last post by Rich on June 17, 2025, 11:51:50 PM »

Hi uli

... There must be other places within tiny / Core where network access is being probed and confirmed successfully, ...

Hi GNUser

... Why not go with Robert's approach (which shows up in  tc-config  and  settime.sh ):

Code: [Select]

ifconfig | grep -q Bcast || return 1 ...

Funny you should mention it. That will detect the NIC was brought up.
It will not detect an unplugged network cable or problems upstream.
Oh, and watch this:

Code: [Select]

tc@box:~$ ifconfig eth0 | grep Bcast
          inet addr:192.168.1.45  Bcast:192.168.1.255  Mask:255.255.255.0
tc@box:~$ sudo ifconfig eth0 down
tc@box:~$ ifconfig eth0 | grep Bcast
          inet addr:192.168.1.45  Bcast:192.168.1.255  Mask:255.255.255.0
tc@box:~$
I also considered using this:

Code: [Select]

ifconfig eth0 | grep RUNNINGThat will detect taking down the NIC and unplugging the network cable.
While it detects a disconnect between computer and network switch, it
won't detect a disconnect between network switch and router.

The Apps utility will hang for a minute or two if it can't connect to
the repo, a behavior we want to avoid in provides.sh.

... Maybe trying to ping the selected mirror would be a better option ? ...

Hi t18
Pinging the repo will temporarily lock you out:

... About the ping, that's part of the port scanning protection. You essentially blocked yourself for a short time.

...

... Just wouldn't have thought it to be a rare case, ...

You are the first person to report this as an issue.