Tiny Core Linux
Tiny Core Base => Raspberry Pi => Topic started by: meo on September 02, 2023, 02:18:53 AM
-
I have tried to make a fresh piCore install using the command: "tce-load -iw TC" that gives me an error message: "Connecting to repo.tinycore.net (128.127.66.77:80) wget: server returning error: HTTP/1.1 404 Not Found". Is the repository down? I've tried since last night local time (Sweden). // meo
-
Hi meo
The repo is fine. If you are running aarch64, there does not appear
to be a TC.tcz extension.
-
Actually I was using aarch64 so the missing Tc.tcz was the problem. I updated the installation I had which I shouldn't have done. After thar it didn't start. Hence my efforts to make a fresh installatiion, Since the aarch64 didn't work I went with the 32 bit (14.0.1) instead. All worked and I was welcomed with a GUI. Since nothing has worked fine naturally I couldn't connect to the repo from that one either. I got some error message telling me to check the network connection etc. So now I'm posting this from Kali Linux on my Raspberry Pi 4 B 8 GB and I haven't got a clue what to do when it comes to piCore. Any thougts about this? // meo
PS Yes, I am a distro junkie. DS
-
Hi meo
TC.tcz is just a meta extension. All loading it does is load its dependencies.
Run the following for the same result:
tce-load -iw Xorg flwm_topside wbar aterm
-
Well now I'm running Gentoo Linux on my RPi. Will test your suggestion even though I have a GUI. The problem comes when I try to connect to the repo to install more extensions. // meo
-
Hi Rich!
Thanks for trying to help an old man out with the installation of piCore! I Tried your suggestion on the install of piCore aarch64. Unfortunately the flvm_topside.tcz was also missing so it didn't work. I went back to the 32 bit piCore and finally got it setup. // meo
-
Hi meo
... Unfortunately the flvm_topside.tcz was also missing ...
Actually, it's spelled flwm_topside.tcz , and I checked the TC14 aarch64
repo to make sure it was present before I posted:
http://tinycorelinux.net/14.x/aarch64/tcz/flwm_topside.tcz.info
-
You are quite right Rich! I'm really sorry for making this typo when copying your suggestion. :( In other words "My bad". I'm very absintminded so again, I'm sorry! Just tried to install aarch64 and it went well and I got the GUI just the way it's supposed to be. Something went wrong later on. When installing ffmpeg onboot the screen went black. Don't have time to check this out right now but I'll get back to it. Thanks for your patience with an old absintminded man like me! // meo
-
When installing ffmpeg onboot the screen went black.
I think graphics-KERNEL is the cause.
http://forum.tinycorelinux.net/index.php/topic,26363.0.html (http://forum.tinycorelinux.net/index.php/topic,26363.0.html)
-
I went with the 32bit version of the last piCore just to be sure that it will work. The problem I've had since making an update that made the whole system crash and then making a fresh install is that I can't play mp4 videos in Firefox anymore. I'll keep testing to see if I can make it work otherwise I'll use piCore as a lean mean info getting machine. Info I want to save I copy over to an usb drive. // meo
-
If you’re using an RPi4 8GB then you might as well run piCore64 and Xorg-3d or wayland to take advantage of the 8gb and gpu acceleration.
In addition it looks like piCore has a problem when run on an RPi4 8gb with x11/wayland, which is being looked into.
-
If you have an 8GB board, using 32bit is just crippling the board anyway, as they have to do tricks to access all of the memory.
The symptom Juanito refers to is Xorg is getting killed due to the kernel running out of memory, when doing things that have lots of disk activity, like mounting extensions.
If you still want to use piCore 32bit, then for now, its best to turn your 8GB board into a 4GB board by adding
total_mem=4096 in the config.txt file.
Note: this does not impact headless systems that do not use Xorg
-
Hi guys!
Actually I'm setting up piCore64 right now. How do I change from Xorg to Xorg-3d? I have already installed Xorg and I'm typing this from Firefox in that installation. Sure I want to take advantage of my RPi to the full. But then I need help to install Xorg-3d. // meo
-
After thinking about it I guess that I have to make a new installation from the beginning. // meo
-
Just install Xorg-3d.tcz
Make sure your onboot.lst only has Xorg-3d. Do not try to load both.
This is why we don’t recommend the TC.tcz extension anymore, there are too many combinations with raspberrypi hardware.
-
You also need dtoverlay=vc4-kms-v3d-pi4
-
meo, from a younger man to older one...you may like to learn from my mistakes.
The boot order in your boot list such as onboot.lst needs this order
graphics-KERNEL.tcz
Xorg-3d.tcz
blah blah.tcz
You may like to look at Paul_123's get-chromium-browser as it plays mp4 out-of-the-box and plays sound if you are only using alsa. I am sure it would also play sound if you set up pulseaudio too.
He is too poiltie to recommend it, but it is more recent than FF built in 2020. Someone may be attempting to make a get-firefox TCE but until then....I recommend you try out chromium.
https://imgur.com/haC3JYJ
-
After thinking about it I guess that I have to make a new installation from the beginning. // meo
There’s no need to make a new installation, you just need to substitute Xorg-3d for Xorg when loading extensions.
-
Thanks guys! It took a while but with your help it worked. Typing this from the Chromium-browser. Thanks again! // meo
-
The installation has a snag though. :( When rebooting I get the error message "failed in waitforX". Apparently I have to make an entry in a configuration file to get x to start automatically. Getting the error message I was left with a command prompt and had to startx manually. I remember that this sometimes had to be done when booting from an usb drive. Don't remember though where the waitforX should be inserted. // meo
PS I feel bad bugging you guys all the time but my memory isn't what it should be. DS
-
Hi meo
I have a laptop that behaves the same way. I inserted a sleep
command in the .xsession file in my home directory like this:
tc@E310:~$ cat .xsession
sleep 3
/usr/local/bin/Xorg -nolisten tcp &
export XPID=$!
waitforX || ! echo failed in waitforX || exit
----- Snip -----
That got rid of the failed in waitforX error.
-
You may have to go higher with the sleep time. It happens because the graphics system takes a little time to initialize.
-
Thanks Rich! I was just about to say that I had to put it to sleep 10 then it starts. Thanks again! // meo
-
Hi meo
What Paul_123 just said jogged my memory. When I switched the
laptop from Xorg to Xorg-3d, I changed from sleep to this:
Timeout=60
while [ $Timeout -gt 0 ]
do
[ -e /dev/dri/card0 ] && break
Timeout=$(($Timeout - 1))
sleep 0.25
done
/usr/local/bin/Xorg -nolisten tcp &
export XPID=$!
waitforX || ! echo failed in waitforX || exit
----- Snip -----That waits for 15 seconds or until /dev/dri/card0 shows up, whichever
comes first. The laptop usually continues after 8 seconds.
I found the issue was /dev/dri/card0 by searching /var/log/Xorg.0.log
for errors after failed in waitforX occurred.
-
Hi again guys! Thank you both (well everyone that has helped me out)! I have to ge with the first suggestion since the latter didn't fix the problem. Now the GUI starts automatically. Thanks again! // meo
-
Hi meo
Did you search /var/log/Xorg.0.log for errors after failed in waitforX occurred?
It might not be called /dev/dri/card0 in piCore.
-
Hi Rich!
No I just mean that I use the first suggestion with the sleep command. That works for me. Thanks a lot!
// meo