Tiny Core Linux
Tiny Core Base => Corepure64 => Topic started by: tektonikos on July 13, 2026, 12:11:01 AM
-
Hi,
I’ve not been using Core Pure 64 for many years and am trying to understand where the issues are coming from.
When I boot from the 200+ MB image and enter the GUI, the first stop is the Apps browser. If I choose “fastest mirror,” it says to check connectivity, but I can resolve and ping Google, so the network appears to be working.
The CLI tce tool behaves better in one respect, but it still has problems: when I enter a keyword, nothing is returned and it drops back to the menu. The providers do return results, and after selecting a .tcz, the description is displayed as ASCII characters. I can sometimes download an extension, but more often it reports that the checksums do not match.
For example, I downloaded these files with wget:
http://tinycorelinux.net/17.x/x86_64/tcz/glibc_add_lib.tcz
http://tinycorelinux.net/17.x/x86_64/tcz/glibc_add_lib.tcz.md5.txt
The checksum for glibc_add_lib.tcz is 56123a147076325062ddf1513fe2b581(stays consistent), but when I try to load it I get:
mount: mounting /dev/loop46 on /tmp/tcloop/glibc_add_lib failed: Invalid argument
Also note same activity on 16.1 (pure64)
the screen from the gui is tincycore(32-bit) plus iso v17.
-
Is the problem ocurred in older version or only in 17.x86-64?
If only on 17.x, then how you boot iso file?
What is the type of your internet connection and what is the speed of your internet?
-
Is the problem ocurred in older version or only in 17.x86-64?
If only on 17.x, then how you boot iso file?
What is the type of your internet connection and what is the speed of your internet?
Seems as though its the internet connection. Using an ATT phone the checksum is not accurate. Using a VZW phone the checksum matches. Seems as though there is something how the HTTP traffic returned is getting encoded odd. Noticed when goto ipchicken the IP shown is not the IP that returns to me but when i logon to another site the IP is slightly different. So anyhow, guess its ATT.
-
Seems resolved by switching carriers, VZW appears working though still get network issues question dialog from select fastest server though package list displays in gui and description is not ascii. checksums match. very odd to me but yeah, thanks!
Well actually, cli tce does not search, does not keywords, and providers works but checksum does not match. im not sure now.. ha
Is the problem ocurred in older version or only in 17.x86-64?
If only on 17.x, then how you boot iso file?
What is the type of your internet connection and what is the speed of your internet?
Seems as though its the internet connection. Using an ATT phone the checksum is not accurate. Using a VZW phone the checksum matches. Seems as though there is something how the HTTP traffic returned is getting encoded odd. Noticed when goto ipchicken the IP shown is not the IP that returns to me but when i logon to another site the IP is slightly different. So anyhow, guess its ATT.
-
how to close this?
Hi,
I’ve not been using Core Pure 64 for many years and am trying to understand where the issues are coming from.
When I boot from the 200+ MB image and enter the GUI, the first stop is the Apps browser. If I choose “fastest mirror,” it says to check connectivity, but I can resolve and ping Google, so the network appears to be working.
The CLI tce tool behaves better in one respect, but it still has problems: when I enter a keyword, nothing is returned and it drops back to the menu. The providers do return results, and after selecting a .tcz, the description is displayed as ASCII characters. I can sometimes download an extension, but more often it reports that the checksums do not match.
For example, I downloaded these files with wget:
http://tinycorelinux.net/17.x/x86_64/tcz/glibc_add_lib.tcz
http://tinycorelinux.net/17.x/x86_64/tcz/glibc_add_lib.tcz.md5.txt
The checksum for glibc_add_lib.tcz is 56123a147076325062ddf1513fe2b581(stays consistent), but when I try to load it I get:
mount: mounting /dev/loop46 on /tmp/tcloop/glibc_add_lib failed: Invalid argument
Also note same activity on 16.1 (pure64)
the screen from the gui is tincycore(32-bit) plus iso v17.
-
Hi tektonikos
By close I guess you mean marking it as solved.
Once a post is 30 minutes old, you can no longer edit it.
If you need a thread marked as solved, mention it and I'll take care of it.
-
ASCII characters are ussualy a sign of corruption. Maybe you could reinstall all packages.
I noticed that when I use slow mobile internet connection, the risk of loosing connection, freez connetion or packet lost is higer than in broadband LAN connection.