Tiny Core Base > Release Candidate Testing
tinycore_2.4rc3
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:
--- Quote from: bmarkus on October 03, 2009, 11:40:17 AM ---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.
--- End quote ---
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:
--- Quote from: MikeLockmoore on October 03, 2009, 12:12:40 AM ---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.
--- End quote ---
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:
--- Quote from: gerald_clark on October 03, 2009, 10:02:22 AM ---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.
--- End quote ---
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.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version