Probelm with tces

[ir]

Hello

I am a newcomer to tinycore. I hav installed tinycore-2.1rc1 on a usb pendrive and installed grub to boot it (it works!). Usb drive is sdb (whole drive used as a single partition sdb1). I want to add a few tces (abiword,
xpdf, wiv etc). To this end I use the kernel option in grub as:
  ...
  kernel /boot/bzImage quier local=sdb1 noswap waitusb=5
...

I install the tce using applbrowser (connect->tce) but it disappears on a reboot (and I can;t find the .tce package any where). The sdb1 partiiton
has directories (/tce, /tcz, /local).

Sdb1 is also the tinycore boot/* partition??

Any help will be appreciated.

-ir

[Lee]

kernel /boot/bzImage quier local=sdb1 noswap waitusb=5

You can remove the

Code: [Select]

local=sdb1 from your kernel line, then create a directory named tce in the root directory of the pendrive

Code: [Select]

mkdir /mnt/sdb1/tce
(you might have to use sudo)

Upon reboot, tc will load any *.tce files it finds in that directory and any that you install from the repository will be copied there to be loaded at upon subsequent reboots.

If you happen to have directories named tce in the root directories of other filesystems, you can specify which one to use with

Code: [Select]

tce=sdb1
on the kernel line, but that's not necessary if you only have one such directory.

Its "quiet", not "quier". 

[alu]

check your boot line in grub, it must show:


kernel /boot/bzImage
append initrd=/boot/tinycore.gz quiet tce=sdb1/tce noswap waitusb=5

then download your apps from appbrowser and place them in the /sdb1/tce directory. restart, tc will load your tce at boot.

[alu]

oups, sorry Lee, i posted it short after you, it seems

[ir]

kernel /boot/bzImage quier local=sdb1 noswap waitusb=5

You can remove the

Code: [Select]

local=sdb1 from your kernel line, then create a directory named tce in the root directory of the pendrive

Code: [Select]

mkdir /mnt/sdb1/tce
(you might have to use sudo)

Upon reboot, tc will load any *.tce files it finds in that directory and any that you install from the repository will be copied there to be loaded at upon subsequent reboots.

If you happen to have directories named tce in the root directories of other filesystems, you can specify which one to use with

Code: [Select]

tce=sdb1
on the kernel line, but that's not necessary if you only have one such directory.

Its "quiet", not "quier".  

Ok changed the kernel line to
kernel /boot/bzImage quiet noswap waitusb=5

created /tce (on sdb1 -- the boot device fs) , downloaded the
.tces of interest, rebooted but none the .tce was loaded. I was
able to install them using applbrowser->File->Install  Local

Is there no way to auotmate this? or I am doing something wrong?

-ir

[philip]

When I had a similar problem, choosing a larger number for "waitusb" cured it. (If the USB key isn't fully mounted and settled when the tc-config script starts looking for saved extensions, it will just proceed without loading them.) Adding the word "pause" to the boot command line until you get everything working just right may also help. It lets you see what messages the boot process generates before replacing the console with an X session. Good luck.

[samedirection]

You can confirm that the tce's went to the right place?  (That is, to /tce in drive sdb1).  And not to /tce/optional, which they may have done if you chose to "only download" not install them).
 or to someplace else. 

Don't worry, you're just a few moves away from getting it all to work as you expect.  We just have to figure out what moves.

[ir]

You can confirm that the tce's went to the right place?  (That is, to /tce in drive sdb1).  And not to /tce/optional, which they may have done if you chose to "only download" not install them).
 or to someplace else. 

Don't worry, you're just a few moves away from getting it all to work as you expect.  We just have to figure out what moves.

The tces were downloaded and then copied to /mnt/sdb1/tce, so the files are there. Adding tce=sdb1/tce and waitusb=25 also did not help.

-ir

[roberts]

Perhaps using UUID or LABEL would be helpful.
See FAQ: http://www.tinycorelinux.com/faq.html#pendrives

Also, in 2.1rc2, is a pendrive install script, which automatically sets up Tiny Core and uses UUID to ensure tce loading is from where it is excepted.