Welcome, Guest. Please login or register.
Did you miss your activation email?
Need an Introduction to Tiny Core? Or peruse Core Concepts.
Seems like a clue, is your system trying to run two WMs(?), did you check?
No I'm not, but I agree this is weird. ...
Yes you were.
for translation, using default messages.
BScreen::BScreen: an error occured while querying the X server.
Error: Couldn't find screens to manage.
Make sure you don't have another window manager running.
That terminal from GUI desktop you tried to start fluxbox from was provided by the other WM that was running.
Well, for now I'm just sticking with flwm_topside. It's way faster for whatever reason. Thanks for the replies anyways.
Then edit the onboot.lst to remove flwm and replace with fluxbox You don’t need VLC etc etc as the test is only temporary.
Ensure you’re extensions are installed on the fastest available storage media and you’re system is actually loading them..?
sda1 ? Really is tc installed on the first partition of your HDD?
Make sure no other installation like CD, USB DRIVE is influencing the outcome, remove them!
It looks to me as if Xorg + Radeon drivers are causing many loading issues, if that’s not the cause then maybe the media where fluxbox.tcz is loaded from is extremely slow?
tce=sda1/tce is like asking tc to look inside tce=sda1/tce/tce for your extensions and when it can’t find any looks to other drives like a CD for potential tce directories.. Which explains slow loading issues..
tce=sda1Without specifying tce unless you’ve changed its name..
I’m simply pointing out the obvious causes here since fluxbox itself installs in a second or two at worst in all my tests and those tests were all from a USB thumb drive!! doesn’t matter if first time install and loading either..
Also...
Also..
Another troubleshooting step you can try since we're only concerned with the install time from a mounted extension is a selective copy2fs; installing fluxbox.tcz & dependencies to the file system before X attempts to run it.
Ok, I experimented per above and what worked was re-imaging a Core Plus to the existing partition. I verified that Fluxbox started within about 2 seconds.
I then tried making a persistent home. The home folder was still on the hard drive from before. This resulted in slow startup again. Therefore I think something related to a setup file in the home folder or the persistence is/was slowing down Fluxbox.
Reimaged again. I got used to using flwm_topside though...so kind of a moot point now. Thanks to everyone, again.
