Tiny Core Linux
Tiny Core Base => TCB Talk => Topic started by: Sashank999 on June 23, 2020, 07:46:50 AM
-
I am a TCL x86 user (for small sized tczs). Now, I want to use TCL x64.
My questions :
1) Which files should I download ?
I mean should I download the whole Coreplus x64 iso or just the kernel and core.gz files.
2) Can I use x86 tczs on x64 ?
It may sound awkward because the archs are different but I should ask this if I should download only the kernel and core.gz . And also, I have only a wifi card but no ethernet connection so I must have wifi tczs.
3) Where are the files to download ?
I mean the links. I don't know where are they. I know they are in tinycorelinux.net/11.x/ but where in it ?
There is no way to set the path of TCE Dir(unless the current path is in /tmp) in GUI Apps. So, if I install both archs in same partition, will the apps GUI find the TCEs for the correct arch ?
-
You can download the files from here:
http://tinycorelinux.net/11.x/x86_64/release/distribution_files/
You need corepure64.gz and vmlinuz64 - you can copy them into the same directory as core.gz and vmlinuz.
Create a second menu entry in your boot loader configuration file - you can copy the 32-bit entry and change core.gz -> corepure64.gz and vmlinuz -> vmlinuz64.. Note that you also need to add a boot code "tce=tce64" or similar as CorePure64 uses different extensions.
-
"tce=tce64" ? Never heard that. I thought it was only for partitions. Can we specify directories in it ?
And also, will the Xorg, fltk, wifi modules of x86 work on x64 ? I only need those three for now.
-
Hi Sashank999
I am a TCL x86 user (for small sized tczs). Now, I want to use TCL x64.
My questions :
1) Which files should I download ?
I mean should I download the whole Coreplus x64 iso or just the kernel and core.gz files. ...
Just the kernel and core.gz files.
... 2) Can I use x86 tczs on x64 ? ...
No.
... It may sound awkward because the archs are different but I should ask this if I should download only the kernel and core.gz . And also, I have only a wifi card but no ethernet connection so I must have wifi tczs. ...
Create a directory for 64 bit extensions next to your tce directory called tce64/optional. Then cd into tce64/optional and
download the script available here:
http://forum.tinycorelinux.net/index.php/topic,23034.0.html
Edit the script to change this:
# Tinycore version
TC="10.x"
# Processor architecture, current options are x86 x86_64 armv6 armv7
ARCH="x86"
To this:
# Tinycore version
TC="11.x"
# Processor architecture, current options are x86 x86_64 armv6 armv7
ARCH="x86_64"
The script assumes nothing about your system. Any extension name containing KERNEL or 5.4.3-tinycore will not be found. You
will need to run the script again for those extensions, for example:
./FetchExt.sh wireless-5.4.3-tinycore64to fetch the 64 bit version.
... 3) Where are the files to download ?
I mean the links. I don't know where are they. I know they are in tinycorelinux.net/11.x/ but where in it ? ...
http://tinycorelinux.net/11.x/x86_64/release/distribution_files/
-
I am getting
http://repo.tinycorelinux.net/11.x/x86_64/tcz/firmware-amdgpu.tcz.tcz.tree not found.
Error when downloading firmware-amdgpu.
EDIT : I realised that we should not input the .tcz when giving input. Sorry. :P
-
@Juanito @Rich I got a problem. Used the scripts and downloaded the extensions. I then added the 64 bit kernel and core.gz to Grub2, added boot code tce=tce64 and then booted 64 bit. I got a prompt (as I didn't write anything into onboot.lst). I mounted my partition and went to tce64/optional and did "tce-load -i wifi" but nothing happened. I then tried with sudo. But that showed don't run this as root. I tried with other extensions but none worked.
Are there any dependencies for tce-load ?
-
OK. I now understand. When I applied "chmod +rwx * " in the optional folder, it worked.
But now, I get 2 problems.
1) "startx" says "failed in waitforX"
2) "tce-load -i firmware.tcz" says "mount /dev/loop6 failed: Invalid Argument"
Note : tce32 works fine. And also, above specified boot code (tce=tce32) doesn't work. tce=sda5/tce32 works.
-
The tce folders (tce, tce32, tce64, etc) and everything in them should be owned by tc:staff.
Just to be sure it's understood, tce=tce32 or tce=sda5/tce32 are telling tinycore which tce folder to use and are not telling it to boot a 32-bit version of tinycore.
Which Xserver are you trying to use - Xvesa (32-bit only), Xfbdev or Xorg-7.7?
-
I have read somewhere in the forums that Xvesa is 32bit only and hence I used Xfbdev.
-
In that case, you need a boot code like, for example, vga=791
Edit: from the faq: Tiny Core accepts the following additional boot time options:
Color 640x480 800x600 1024x768 1280x1024
256 8 bit 769 771 773 775
32000 15 bit 784 787 790 793
65000 16 bit 785 788 791 794
16.7M 24 bit 786 789 792 795
tinycore vga=7xx 7xx from table above
-
Oh. Will add that.
I am getting error when using wifi.sh as libelogind.so.0 is missing but I loaded all tcz.
-
You're missing the elogind extension, which depends on acl, attr and libcap.
Edit: If startx still fails, run the following from the console prompt: $ Xfbdev -mouse /dev/input/mice,5 -nolisten tcp -I
-
Might be helpful to someone. VGA Chart :
| Depth | 800×600 | 1024×768 | 1152×864 | 1280×1024 | 1600×1200 |
| 8 bit | vga=771 | vga=773 | vga=353 | vga=775 | vga=796 |
| 16 bit | vga=788 | vga=791 | vga=355 | vga=794 | vga=798 |
| 24 bit | vga=789 | vga=792 | none | vga=795 | vga=799 |
Source : https://www.pendrivelinux.com/vga-boot-modes-to-set-screen-resolution/
You can find required height, weight,depth by using "xwininfo -root" command.
Source : https://askubuntu.com/questions/555759/how-to-check-what-color-depth-my-monitors-are-using-in-ubuntu-14-10-unity
But Juanito, I have all those tcz. Trying with -dev.
-
For sure the *-dev extensions will not help.
Does this show elogind is loaded: $ tce-status -i | grep elogind
-
Oh. It is only for 64 bit TCL. Hence I did not download it(in fact, I didnot know there is a module with that name :D ).
I will now download it.
-
tce-load -i wifi.tcz is not working. dmesg is empty. What should I do now ?
I have also done chmod +rwx * . But nothing happened.
-
Even when I add vga=792 boot code, the startx says "Giving Up. Failed in waitforX" .
Just a small doubt. Why should we use startx instead of just typing Xfbdev or Xorg (they don't load directly, they say that Display is not found) ?
-
I suggest double-checking that the correct tce folder is being used:
$ ls -l /etc/sysconfig/tcedir
Next check that a simple desktop is loaded: $ tce-load -i Xfbdev flwm aterm wbar
Then, if startx does not work, use the Xfbdev command mentioned several posts earlier and paste the error message here.
-
Well, the tcedir is correct.
When I also add vga=792 to the bootcodes, I get an note that "vga=792 is deprecated. We suggest using gfxterm=...(some blah blah)". I don't know whether it is from grub2 or TCL. But that vga note comes before the line "Loading kernel 5.4.3-tinycore64". It is also disappearing very fast and hence I was unabe to read all of note.
The desktop loads when I add the vga=792 boot code but the aterm is not loaded and also fltk is not loaded(the x icon, maximise and minimise icons were not there on top of windows.). When I do "tce-load -i Xfbdev flwm aterm wbar" it says all are loaded but there is no fltk-1.3 command.
-
Are you using legacy bios or uefi boot? With uefi boot you can set the efifb resolution to your screens optimal resolution and then you don't need the vga=7xx boot code.
Is it possible that you missed out downloading some of the *tcz.dep files (are Xfbdev.tcz.dep, flwm.tcz.dep, etc, all present)?
Note startx performs several housekeeping tasks for the desktop - the Xfbdev command is for troubleshooting only.
-
My system is too old and I have only BIOS. No UEFI.
I downloaded all things with the script Rich provided. And hence I am sure that all .dep files are downloaded too.
This time I got another error when I returned back from desktop back to prompt :
Could not init font path element /usr/local/lib/X11/fonts/100dpi/, removing from list!
-
I now realised that the script did't work as expected. I think it has a few errors. It did not download .dep for adwaita-icon-theme.tcz which has gtk3. Now running the script again for all deps.
-
Did you download the wifi extension and its deps with the script? If so, the elogind extension should have been downloaded.
If the wifi extension works, you can download what is needed with "tce-load -w".
The warning about 100dpi fonts, which can be ignored, would seem to suggest that you using Xorg-7.7 and not Xfbdev. What does this give: $ cat /etc/sysconfig/Xserver
-
It says "Xfbdev".
And also, entering "wifi.sh" says command not found.
Then, I deleted all files in tce.installed folder and the did "tce-load -i wifi". It says that mount is failed : Invalid Argument.
-
Why did you delete the files in /usr/local/tce.installed?
Are you sure you downloaded the extensions from the correct repo - 11.x x86_64?
I suggest you reboot, load only Xfbdev, flwm, aterm and wbar and try again.
-
I deleted files in tce.installed in an hope of installing the extensions again.
Yes. I have downloaded them from correct repo.
That Worked ! Thank You !
The elogind.tcz is actually corrupt download. And hence the error. Sorry and Thank You again.
-
Just asking, why should we use the startx script instead of just making the X Window System itself running ?
And also, which window manager gives that grey color bar on top with different desktops and a clock ?
-
Take a look at the contents of startx with:
$ cat /usr/local/bin/startx
If you use the apps gui "tags" function and enter "wm", you get a list of the window managers available.
-
Because the plain X server may confuse users. Inexperienced users may think the machine has hung.
-
Oh. So the startx launches all wbar, Xorg, wm and create a clean desktop. Thank You.
This thread can be marked as solved :D .
-
Hi Sashank999
... This thread can be marked as solved :D .
Done.
-
Thank You :D .