Recent Posts

1

Extension requests / WvDial

« Last post by neonix on Today at 02:00:28 AM »

WvDial for TC15x86-32 and TC15x86-64.

2

TCE Q&A Forum / Re: Retaining alsamixer settings between boots

« Last post by neonix on Today at 01:42:37 AM »

My goal is that every user who install fresh TCL, have working sound out of the box.
Why other distros can have this, and TCL don't have this? In TCL I have to make few procedures to have working sound in alsa, and wast time, when it could be automati zed.

3

TCE Q&A Forum / Re: Retaining alsamixer settings between boots

« Last post by Rich on January 18, 2025, 02:14:30 PM »

Hi neonix
If you are talking about adding a sleep command to the
pkg/usr/local/tce.installed/alsamixer script, no you can't.

That could block other extensions from loading and their
tce.installed scripts from running for 50 secs.

4

Raspberry Pi / Re: Getting started for a noob(ish)

« Last post by richiec on January 18, 2025, 01:59:29 PM »

Thank you for the comprehensive evaluation (genuinely). I’ll edit these in some time iver the weekend which will obviously lift the quality of the article significantly and ease some folk’s first experiences,

Many thanks

Richard

5

TCB Q&A Forum / Re: init (error -26) with Core 15.0

« Last post by Rich on January 18, 2025, 01:50:43 PM »

Hi linic

... At one point, I disabled too many things using make menuconfig, ...

Which is why I wrote this comment the way I did:

... Then navigating through the menus disabling anything you think you don't want. ...

I've done that too. You look at an option and think "nah, I don't need that", not
realizing there's something else in the dependency chain you do need.

... About the desktop, I ran this:

Code: [Select]

tce-load -wi Xorg-7.7 flwm_topside aterm wbar
tce-load -wi Xvesa
Xvesa -listmodes ...

Remove  Xorg-7.7  from your  /etc/sysconfig/tcedir/onboot.lst  file.
You don't need it because you're running Xvesa.

... and got to the desktop too (see screenshot in attachments). I'm blown away by this! Thanks again!

You are quite welcome. Glad it worked out for you.

6

Raspberry Pi / Re: Getting started for a noob(ish)

« Last post by Rich on January 18, 2025, 01:16:03 PM »

Hi richiec
Welcome to the forum.

Just a few thoughts ...

... TinyCore Linux is well suited to this, but it is far from easy to get working beyond ls working at the command line. This isn’t a tutorial on TinyCore itself — there are many introductions out there ...

Speaking of which, there used to be 2 files (IMPORTANT and README) in
the releases section that never got carried forward after TC12:
http://tinycorelinux.net/12.x/armv6/releases/RPi/

... but as we’ll see the partition resize process is destructive. ...

I was under the impression resizing could be done non-destructively
using the instructions in README at the above link:

... 2) Delete second partition with 'd' than recreate it with 'n' command.
   Use the same starting sector as deleted had and provide end
   sectore or size greater than deleted had having enough free space
   for Mounted Mode. When finished, exit fdisk with 'w' command. Now
   partition size increased but file system size is not yet changed.

3) Reboot piCore. It is necessary to make Kernel aware of changes.

4) After reboot expand file system to the new partition boundaries with
   typing the following command as root:

   resize2fs /dev/mmcblk0p2

Now you are ready to use the bigger partition. ...

... sudo reboot ...

That should be:

Code: [Select]

exitcheck.sh rebootor if you want to shutdown (poweroff):

Code: [Select]

exitcheck.shexitcheck ensures an orderly shutdown/reboot sequence:

Code: [Select]

exitcheck.sh reboot -> /opt/shutdown.sh -> /sbin/reboot -> /etc/inittab -> /etc/init.d/rc.shutdown
Then /etc/init.d/rc.shutdown performs the following:

Code: [Select]

1. Sync filesystems
2. Disable swap space
3. Kill all processes
4. Unmount all extensions
5. Delete extensions being updated
6. Unmount tce directory
7. Unmount backup directory
8. Unmount everything else
If you are running command line only (no GUI) and want backups
run automatically when rebooting/shutting down, see here:
https://forum.tinycorelinux.net/index.php/topic,24013.msg151369.html#msg151369

... There’s in fact no easy way of determining what the actual device is other than trying to mount it and seeing if your files show up. Here’s one way I narrowed it down a bit:

dmesg | grep sda ...

Run:

Code: [Select]

dmesg | tailThen plug in your device and run:

Code: [Select]

dmesg | tailYour device will be the new dmesg entries. If there are no new
dmesg entries, your device was not recognized.

... What you’re looking for is an sda number (which might be none — my USB stick got mounted just as sda ). ...

The last couple of lines should look something like this:

Code: [Select]

tc@E310:~$ dmesg | tail
 ----- Snip -----
[18036149.154763]  sdg: sdg1 sdg2
[18036149.157639] sd 7:0:0:0: [sdg] Attached SCSI removable disk
tc@E310:~$The device in this example is sdg and it has 2 partitions, sdg1 and sdg2.

... tce-load -i dhcpcd.tcz firmware-rpi-wifi.tcz net-usb-6.6.47-piCore-v7.tcz ...

You can also do it like this:

Code: [Select]

tce-load -i dhcpcd firmware-rpi-wifi net-usb-6.6.47-piCore-v7tce-load will work with or without the .tcz extension specified.

Typo:

... Edit the /etc/resolv.conf file and add a DNS server, which for me is simply my router of 192.168.1.1:

nameserver 193.168.1.1 ...

Should read:

... Edit the /etc/resolv.conf file and add a DNS server, which for me is simply my router of 192.168.1.1:

nameserver 192.168.1.1 ...

... ifconfig up eth0 ...

You need root permissions to run that

Code: [Select]

sudo ifconfig up eth0

7

TCB Talk / Re: Suggestion to embrace the yaml format for .info files

« Last post by DukeNukem on January 18, 2025, 07:24:53 AM »

Hi everyone,

Switching to YAML for .info files is an interesting idea. While the current format works well for its intended purpose, YAML could bring more consistency and make automated parsing easier for those who need it.

At the same time, it’s worth remembering that .info files are primarily for users installing extensions, so keeping things straightforward and easy to read should remain a priority. If a change is made, it would make sense to approach it gradually, allowing for compatibility with the existing format and ensuring smooth adoption.

8

TCB Q&A Forum / Re: init (error -26) with Core 15.0

« Last post by curaga on January 18, 2025, 07:16:28 AM »

Yes, custom kernels help boot time quite a bit, in addition to saving space and RAM. Something to have fun with, or if you do want that fast boot.

9

TCB Q&A Forum / Re: init (error -26) with Core 15.0

« Last post by linic on January 18, 2025, 07:13:12 AM »

Hi Rich,

When it comes to ease of modification, time invested, and predicting
memory savings, I feel modifying core.gz wins hands down.

I agree. It's way faster, easier and predictable to modify core.gz.

About custom kernels, I noticed that if I select the components I think I'll need and build directly in the kernel and not as modules the boot process seems faster. At one point, I disabled too many things using make menuconfig, I had no modules and everything was in the kernel and the system booted taking about 1/4 or 1/5 of the usual time, with network, but without being able mount partitions and fdisk -l would show nothing. I was missing some SCSI/ATA/PATA drivers if I remember correctly. What helped me guess a working set of kernel components were /var/log/messages and lsmod from Core 14.0 which doesn't need any customization to boot. Oh and make menuconfig helps also understand what each kernel option does by typing "?". That was also very useful.

About the desktop, I ran this:

Code: [Select]

tce-load -wi Xorg-7.7 flwm_topside aterm wbar
tce-load -wi Xvesa
Xvesa -listmodes

and then edited my .xsession

Code: [Select]

Xvesa -mode 0x0115 -br -2button -mouse /dev/input/mice,5 -nolisten tcp -I >/dev/null 2>&1 &
export XPID=$!
waitforX || ! echo failed in waitforX || exit
"$DESKTOP" 2>/tmp/wm_errors &
export WM_PID=$!
[ -x $HOME/.setbackground ] && $HOME/.setbackground
[ -x $HOME/.mouse_config ] && $HOME/.mouse_config &
[ $(which "$ICONS".sh) ] && ${ICONS}.sh &
[ -d "/usr/local/etc/X.d" ] && find "/usr/local/etc/X.d" -type f -o -type l | sort | while read F; do . "$F"; done
[ -d "$HOME/.X.d" ] && find "$HOME/.X.d" -type f -o -type l | sort | while read F; do . "$F"; done

and got to the desktop too (see screenshot in attachments). I'm blown away by this! Thanks again!

10

Extension requests / Re: firewalld Update

« Last post by Juanito on January 18, 2025, 06:55:30 AM »

I’ll take a look in 4-5 days time.