tinycore_2.4rc3

[roberts]

Use version command.

[gerald_clark]

/etc/issue would be a good place.

[bmarkus]

Use version command.

Thanks, I didn't know this command.

[roberts]

See http://forum.tinycorelinux.net/index.php?topic=724.0:

[bmarkus]

See http://forum.tinycorelinux.net/index.php?topic=724.0:

I have never used TC 1.x started with 2.0rc..

[jpeters]

There doesn't seem to be much if any difference in the boot time with this version, and I'll certainly miss watching what is going on while booting. I like to see which programs are the pigs, conflicts, things that aren't installing correctly, permission problems, etc, etc, while it's booting.  The rotdash is great for those who don't want to know what's happening.   (psychologically, it makes the boot seem longer).

[curaga]

Let's clean up the DHCP message as well. Patch, also uploaded:

--- dhcp.sh   2009-10-03 11:12:48.000000000 +0300
+++ dhcp.sh.new   2009-10-03 11:13:27.000000000 +0300
@@ -10,7 +10,7 @@
 for DEVICE in $NETDEVICES; do
   ifconfig $DEVICE | grep -q "inet addr"
   if [ "$?" != 0 ]; then
-    echo  "${GREEN}Network device ${MAGENTA}$DEVICE${GREEN} detected, DHCP broadcasting for IP.${NORMAL}"
+    echo -e "\n${GREEN}Network device ${MAGENTA}$DEVICE${GREEN} detected, DHCP broadcasting for IP.${NORMAL}"
     trap 2 3 11
     /sbin/udhcpc -b -i $DEVICE -h $(/bin/hostname) -p /var/run/udhcpc.$DEVICE.pid >/dev/null 2>&1 &
     trap "" 2 3 11

[meo]

Hi again Robert!

Thanks for your response but I still think there is something that isn't well with the Refresh Menu option, The screen went black when pressing it. All was made from scratch with no backup or restore. I usually test this out when there is a new cut. After that (if nothing dramatically has changed) I just use tce=hda6 and restore=hda1. Those contain the apps I need and the files that have to be restored to make tinycore 2.4.x work on my 8,5 years old laptop. So I really find tinycore very swift and comfortable to use in my daily use of a computer. Thanks a lot to all of you who are making tinycore progress.

Have fun with tinycore,
meo

[gerald_clark]

Hello, Robert

How about including the tftp/nfs patches from http://forum.tinycorelinux.net/index.php?topic=2705.0 ?
They allow an nfs share to be used just like a drive for PPR/TCZ.
Other people are using the patch, and have said they would like it added.

[perthie]

I have a NIC that requires additional firmware. In some previous versions, I had to install the separate firmware extension. However, in 2.4rc1, it looked like the firmware was being installed automatically.  Now in 2.4rc3, I'm getting a message at the end of boot-up "etho: failed to load firmware tigon/tg3_ts05.bin". On the other hand, the NIC appears to be working properly.

[bmarkus]

I just sorted tcz2ram.lst file and learned that each extensions are listed 5 times. In fact in /tce there are 83 extensions. Deleting tcz2ram.lst and rebooting 80 extensions are mounted on /dev/loop0 .... /dev/loop79 while others are lost without error message.

[gwalther]

Mike...

try booting without the ...noswap....option

noswap ..caused similar problems on earlier version for me...think it's a timing issue

[roberts]

I just sorted tcz2ram.lst file and learned that each extensions are listed 5 times. In fact in /tce there are 83 extensions. Deleting tcz2ram.lst and rebooting 80 extensions are mounted on /dev/loop0 .... /dev/loop79 while others are lost without error message.

It is a well known fact our kernel was compiled for 80 loops 0 - 79.
http://forum.tinycorelinux.net/index.php?topic=3008.msg15673#msg15673

Even though, in v2.4, there are now /dev/loop items to 254, you must inform the kernel that such are available. You need to add the boot code max_loops=255
http://www.tinycorelinux.com/faq.html#loops

This will provide loop 0 -254

The other item concerning doubling up of tc2ram.lst is a bug, still part of the full pathing error.
It is an easy fix, and is in fact done for the next cut.

[roberts]

As excited as I am to get started using 2.4... I'm having problems with 2.4rc3.  I had a bunch of .tcz's in my hdc4/tce directory.  I have been boothing 2.3.1 with the options:

  tce=hdc4 noswap laptop

In my menu.lst, I copied the 2.3.1 section for 2.4rc3, pointed it to the new bzImage and tincycore.gz files, and used the same boot options listed above.  2.4rc3 boots right up and displays the flwm desktop, but no extensions are loaded, and if I go to the status window in the control panel, the extensions list is empty.  I can can use AppBrowser to install extensions, but they get stored in the home folder (/home/tc), and if I reboot, they will not be automatically reloaded.  

I tried to boot with the option tce=hdc4/tce_2_4, to create a new 2.4-specific tce directory, but booting like this does not create the hdc4/tce_2_4 directory, nor does installing apps from appbrowser.    What am I doing wrong?

My restored files are ok that come from mydata.gz.  I tried to reset .xsession and .profile from /etc/skel to make sure those files where not causing a problem, but I did not see any change in the tce/ situation.  Is there something else I can do to troubleshoot this?  Or do differently to set up a tce/ that works?  Thanks for any help.
--
Mike L.

Make sure hdc4 is still hdc4 as you think it is, this is especially true for removal devices that may now be attached to your system.

Upon first boot, go to shell and use fdisk to make sure hdc4 is the proper physical disk.
After you first boot is hdc4 mounted?

Another item to check, could be a needed waitusb=5 boot option. Typically tce directory not getting mounted may need more time to be detected.

Where is your backup data? Also on hdc4 or ?

[roberts]

Hello, Robert

How about including the tftp/nfs patches from http://forum.tinycorelinux.net/index.php?topic=2705.0 ?
They allow an nfs share to be used just like a drive for PPR/TCZ.
Other people are using the patch, and have said they would like it added.

With it being so late in this release cycle, and with major infrastructure changes as in 2.4, lets hold off until v2.5 rc1. When 2.4 goes final make me a patch and email to me. I will put it in early in the next release candidate cycle.