Tiny Core Linux
Tiny Core Extensions => TCE Q&A Forum => Topic started by: badhon_raj on March 09, 2013, 12:26:39 PM
-
Hello all. I've two question.
1. Why on earth there is 4 step human verification required for registration? This is very annoying. I've never seen such thing in any other site.
Ok there are another two before I post this topic. :facepalm:
2. How do I install extension without internet connection?
I've downloaded latest one.
4.x > x86 > release > TinyCore-current.iso
used Universal usb installer to put it into a flash drive.
I want to install file manager. So I've downloaded
tinycorelinux > 4.x > x86 > fluff.tcz
Put it into /tce folder of flash drive. Now it won't boot. It stuck at a screen with
tc@box :~$ _
now what do I do?
If I remove tce directory, it boots normally.
Thank you..
-
Start by spending some time in the wiki.
-
Start by spending some time in the wiki.
Nice response form a moderator.
I'm googling around since morning. Now I don't have any more clue where to look at. That's why asked for a right direction.
Edit: FYI this is one of the first pages I read this morning.
http://wiki.tinycorelinux.net/wiki:install_apps
-
It's /tce/optional
-
Hi badhon_raj
I would suggest booting the drive on a machine with an Internet connection connection and using the Apps
utility to install any extensions you need. Trying to download and install apps manually is generally not a
good idea.
-
The forum is not a substitute for reading the documentation.
You need to read the wiki articles on persistence.
http://wiki.tinycorelinux.net/wiki:persistence_for_dummies
and extensions
http://wiki.tinycorelinux.net/wiki:install_apps
-
It's /tce/optional
thanks. I've tried that too.
fluff.tcz has no dep file. So I guess it doesn't have any dependancy. Still I tried
fluff.tcz
fluff_unicode.tcz
fluff_unicode.tcz.dep
fltk-1.3.tcz
and fltk_upgrade.tcz putting together.
Still no luck. :(
-
I would suggest booting the drive on a machine with an Internet connection connection and using the Apps
utility to install any extensions you need.
Which may be facilitated with CorePlus
-
Hi badhon_raj
2. How do I install extension without internet connection?
Is the problem that the machine uses a wireless connection and you can't connect? If that's the case, use
tinypoodles suggestion and install CorePlus to the drive instead, it contains the tools and drivers you need
to set up a connection.
-
Hi badhon_raj
2. How do I install extension without internet connection?
Is the problem that the machine uses a wireless connection and you can't connect? If that's the case, use
tinypoodles suggestion and install CorePlus to the drive instead, it contains the tools and drivers you need
to set up a connection.
yes. That is the problem. I've only EDGE connection with a nokia phone using as a modem. And I belive it is quite a hassle to set up that. That's why I was trying to avoid that.
Sadly now I ended up with more hassle than that. :(
edit: ok I've downloaded older versions and installation works perfectly for 3.8.4. That'll do now for me. But still I couldn't find out why it wasn't working on the latest version.
Thank you all. :)
-
ok I've downloaded older versions and installation works perfectly for 3.8.4. That'll do now for me. But still I couldn't find out why it wasn't working on the latest version.
Difference being that with 3.8.4 GUI components are within initrd, while they were outfactored to extensions since.
As opposed to what you claim in OP, when you meet a prompt "tc@box :~$" _ your system has fully booted, just no X server is running.
-
ok, I'm here again with a new problem.
I can't copy/move any files of my hdd. Tried xfe, fluff, and emelfm. It says
can't write to /mnt/sda2: permission denied.
Can't create '/mnt/sda2/a.txt' Read-only file system.
Running as root doesn't help.
How do I mount them as read-write.
Please help me. Which article (s) do I need to read?
-
I'm guessing an NTFS issue.
http://wiki.tinycorelinux.net/wiki:persistence_for_dummies
If you are using an NTFS file system it can only be mounted in read-only mode unless you install ntfs-3g.
That means your tce dirrectory cannot be on an NTFS filesystem without remastering.
http://wiki.tinycorelinux.net/wiki:start#remastering
-
I'm guessing an NTFS issue.
http://wiki.tinycorelinux.net/wiki:persistence_for_dummies
If you are using an NTFS file system it can only be mounted in read-only mode unless you install ntfs-3g.
That means your tce dirrectory cannot be on an NTFS filesystem without remastering.
http://wiki.tinycorelinux.net/wiki:start#remastering
my hdd is NTFS. but I'm running tcl from a flashdrive. And tce directory is on th flash drive as well. It is formatted in FAT16.
Oh wait, you mean I need to install ntfs-3g in order to work with any ntfs partition, right?
-
If you want to write to it, yes.
-
If you want to write to it, yes.
thank you. It is working now. :)
I couldn't find this info on wiki. So you can not blame me for not reading for this one I guess. :p
-
I couldn't find this info on wiki.
Not to expect - it's about NTFS access under Linux in general ;)
-
Difference being that with 3.8.4 GUI components are within initrd, while they were outfactored to extensions since.
As opposed to what you claim in OP, when you meet a prompt "tc@box :~$" _ your system has fully booted, just no X server is running.
I've on idea what is that and how to solve that. For now I'm using an older version and so far liking it.
Hopefully I'll come up with many new problems to annoy you all. :p
-
For starters, relying on unsupported 3rd party installers could lead to unpredictable results.
One possible reason for not getting a GUI after boot could be slow storage medium like USB, for which you can use boot code "waitusb= "
-
For starters, relying on unsupported 3rd party installers could lead to unpredictable results.
One possible reason for not getting a GUI after boot could be slow storage medium like USB, for which you can use boot code "waitusb= "
waitusb=5 not working. Same result.
Anyway can any one please confirm for me if chntpw.tcz extension working for you or not? It installs but doesn't open for me in tinycore 4.00
it has one dependency. libssl-0.9.8.tcz
although it says it requires openssl for it in chntpw.tcz.info file. This is confusing me.
http://forum.tinycorelinux.net/index.php?topic=1004.0
-
it has one dependency. libssl-0.9.8.tcz
although it says it requires openssl for it in chntpw.tcz.info file.
from the libssl-0.9.8 info file: Current: 2011/10/30 This is now just the shared lib to support existing apps. Please use the current openssl-1.x and it's -dev extension for building against or to use as openssl.
Basically the chntpw extension was originally built against openssl-0.9.8, but this was obsoleted by openssl-1.0.0 - the libssl-0.9.8 extension allows it work.
-
waitusb=5 not working. Same result.
you can't exclude anything with a value of 5, try 30.
-
Basically the chntpw extension was originally built against openssl-0.9.8, but this was obsoleted by openssl-1.0.0 - the libssl-0.9.8 extension allows it work.
sorry my bad. chntpw working fine from terminal. I expected a GUI first. Then realised it is a command line only tool.
you can't exclude anything with a value of 5, try 30.
waitusb=60. Same result. :(
anyway, I've got a new problem now.
I couldn't get sound out my pc.
Installed alsa, alsamixergui, gnome-mplayer.
I've followed the guide about setting_up_sound.
But still I can't hear any sound. :(
the unlock sign in alsamixergui means unmute, isn't it?
Have a look on my alsamixergui.
-
Hi badhon_raj
the unlock sign in alsamixergui means unmute, isn't it?
Yes, and it shows the Master volume is muted.
Please don't try to use this thread as a catch all for problems. If you are having audio problems, start a new thread
under TCE Q&A Forum.
-
waitusb=60. Same result. :(
Then it's possible your unsupported installer deals better with older versions than with newer ones.
-
unsupported installer
I don't understand. I'm not using anything. If I put any extension downloaded from
http://tinycorelinux.net/4.x/x86/tcz/
(i.e. ntfs-3g.tcz or fluff.tcz) into tce/optional, it won't boot.
However, if I put it into /cde/optional and add it manually to /cde/onboot.lst then it loads without any problem.
This problem is occuring on tinycore version 4.2 or later only. All previous version works good.
-
Hi badhon_raj
That's because the 3.x version did not have a cde directory. The cde directory is intended for read only media
like CDs. Rename the cde directory to tce and remove the cde boot code from your boot loader. Had you used
an installer designed for Tinycore such as http://sourceforge.net/projects/core2usb (as listed in the FAQ) instead
of some third party installer you would not have had this problem.
-
unsupported installer
I don't understand. I'm not using anything.
Was RE:
I've downloaded latest one.
4.x > x86 > release > TinyCore-current.iso
used Universal usb installer to put it into a flash drive.
What Rich said.
-
sorry I thought you meant extension installer.
I skipped the faq/wiki about installing in usb cause I assumed Universal usb installer works perfectly for all distro of linux.
Update: ok problem solved. Used core2usb as suggested. Although Just renaming the cde directory to tce also works as good.
Topic marked as solved. I couldn't get the audio working yet. I'll open another thread about that later.
Thanks to everyone. :)
-
1. The thread relates to early stage newbs getting a USB Flash Drive working; in this case with little or no internet for extensions.
2. This response is a quickie class to help them get through it, without posting the same question; HOW DOES A NEWB BOOT TC QUICKLY, EVEN IF a,b,c LIMITATIONS APPLY?"
Hopefully this reduces questions about that.
1. Format the USB Flash Drive Fat 32 - later you can play with various EXT file systems.
If you don't have this from the start, you will have issues going back and forth with your other "old box" to adjust things.
When formatting, make sure you make it bootable. You may need a utility to handle this; Linux has fdisk - easy/simple - but you may be operating in Windows.
Note: folders are almost always lowercase unless otherwise shown, though CAPS are used to highlight key words below.
2. Make a TCE folder and in that, make an OPTIONAL folder, or E:\tce\optional, and a boot folder or E:\tce\boot
This structure isn't quite standard, but if you have multiple versions of TCE it can be handy later and keeps everything in one folder - under TCE.
3. Mount the ISO. If you need help with that, find a tutorial on mounting an ISO.
4. Copy the files in the ISO BOOT folder into the E:\tce\boot folder..
5. Also, copy onboot.lst and other files from the ISO CDE folder to the E:\tce folder.
6. Copy the files in the ISO CDE/OPTIONAL folder to the E:\tce\optional folder
7. Grub4Dos is more reliable than syslinux - get it and run it to make your USB bootable, then copy the file grldr to E:grldr
8. Create a file E:\menu.lst with these lines.
(don't add the === lines)
========================
timeout=5
default=0
title BOOT NEWER TINY CORE LINUX
find --set-root /tce/boot/vmlinuz
kernel /tce/boot/vmlinuz quiet waitusb=10 norestore xvesa=1024x768x32
initrd /tce/boot/tinycore.gz
title BOOT OLDER TINY CORE LINUX
find --set-root /tce/boot/bzImage
kernel /tce/boot/bzImage quiet waitusb=10 norestore xvesa=1024x768x32
initrd /tce/boot/tinycore.gz
===========================
9. Make sure your .gz files in the boot folders have these names
OR change the names in the menu.lst file to match what's in the boot folder.
Simple.
10. Don't forget when you boot from USB you have to press F2 or DEL to set up your BIOS to boot the USB first. Otherwise your system will keep trying to go to whatever operating system is on your hard drive.
11. TEST IT: If you've got a FAT32 USB and your boot record is good and your menu.lst and grldr are good, and your folders have the right files in them, you will get a basic TC boot.
If it stalls while booting grub4dos, there's probably a file missing or misnamed in the E:\tce\boot folder or you misspelled E:\tce\optional or you forgot the E:\tce\onboot.lst file. TC is so simple, its almost certainly one of these 3 problems.
...or when you formatted it to make it bootable, or you used grub4dos it failed - which can also happen sometimes, depending on your system.