Oolite + Chromebook

[jlager]

Quick update...

I tried reopening the Terminal - and after some time it got around to allowing me to type.

Tried the "glxinfo -B" command, got the following response...

[===========] Ready
jonwoolrich@penguin:~$ glxinfo -B
No protocol specified

Error: unable to open display :2

[MrFlibble]

Quick update...

I tried reopening the Terminal - and after some time it got around to allowing me to type.

Tried the "glxinfo -B" command, got the following response...

[===========] Ready
jonwoolrich@penguin:~$ glxinfo -B
No protocol specified

Error: unable to open display :2

Sounds like there's no xserver running. I'll look into this after eating.

[jlager]

There’s no rush - just whenever you get a chance - hopefully this is not becoming too much of a headache!

[MrFlibble]

There’s no rush - just whenever you get a chance - hopefully this is not becoming too much of a headache!

Thanks.. Got sidetracked

Edit : A Chromebook just landed in my lap. Not sure yet if it'll do for this gig, but will let you know as soon as I know.

Meanwhile:-

This article may be helpful. It shows how to restart the penguin container from crosh.
https://www.reddit.com/r/Crostini/comme ... rminal_or/

Basically, if this is how it still works, you can list/stop/start containers at will (from the Chrome end of course).

Open Crosh: Ctrl + Alt + T

which will launch the terminal window in a new browser tab.

type: vmc start termina

To see what containers are running enter:

lxc list

(vmc container "penguin" is crostini, and should be there)

Type: lxc stop penguin

Then type: lxc start penguin

this should restart crostini

to quit, Type: exit

And again, Type: exit

It may also be that by installing some window manager type stuff, one got started silently during install, but did not restart after reboot. I'll help you across that bridge if appropriate.

[jlager]

Apologies for the delayed response…

This morning, I have opened up the Chromebook - all seems stable…

I opened Oollite from the prev installed icon - and all worked fine!

I have messed about in the game for a couple of hours (been obliterated repeatedly - my fault - never checked system status/rulings etc!)

I have suffered a few frame freezes (mostly whilst under attack with a lot of in-screen laser fire etc) - but nothing more than few seconds at a time.

I also tried opening the Terminal which was returning an error previously - and also opened fine immediately.

Just to confirm - the GPU Support is still not enabled and the DEBIOO window has not popped up again.

I have also shut down/rebooted a couple of times - and all remains stable as above.

I guess I probably need to put a good few hours into the game and see which errors occur etc and feed back?

Ultimately, I’d like to use some OXPs - as these seem to enhance the experience- but I guess I need to walk before I run?

Any thoughts?

*just another repeat of thanks for help and support to date - I would have 100% given up on this without your repeated guidance!

[MrFlibble]

Apologies for the delayed response…

This morning, I have opened up the Chromebook - all seems stable…

I opened Oollite from the prev installed icon - and all worked fine!

I have messed about in the game for a couple of hours (been obliterated repeatedly - my fault - never checked system status/rulings etc!)

Great news!

I have suffered a few frame freezes (mostly whilst under attack with a lot of in-screen laser fire etc) - but nothing more than few seconds at a time.

I also tried opening the Terminal which was returning an error previously - and also opened fine immediately.

The frame freezes may just be an issue with the amount of memory allocated to the container, and/or latency swapping to disk. ChromeOS will be using quite a lot of the available resources itself. I'll know more when I have a crack at doing this on the real thing.

Re: the terminal... same thing. When I get a little hands-on time, I'll understand the layers and abstractions better.

Just to confirm - the GPU Support is still not enabled and the DEBIOO window has not popped up again.

I have also shut down/rebooted a couple of times - and all remains stable as above.

Weird about the GPU, as without that I'd expect things to be terrible. Maybe there's a context issue here, and it's working for Oolite but not the terminal you're querying from.

Glad it's stable though.

I guess I probably need to put a good few hours into the game and see which errors occur etc and feed back?

Yes please.

Ultimately, I’d like to use some OXPs - as these seem to enhance the experience- but I guess I need to walk before I run?

Any thoughts?

OXPs will increase the system load. I find the vanilla game very slick indeed on my gutless laptop, but it can be a bit clunky with a heap of OXPs. I even had out of memory errors until I added a load of swap space. That's with 4G of ram (and no ChromeOS). I'd agree that it's not a bad idea to keep it as light as possible while finding your way in, and certainly while troubleshooting.

*just another repeat of thanks for help and support to date - I would have 100% given up on this without your repeated guidance!

No worries. I've enjoyed the 'black box challenge' so far. It's also given me an excuse to try and help things along on another platform. Thanks for not giving up!

[Cholmondely]

Ultimately, I’d like to use some OXPs - as these seem to enhance the experience- but I guess I need to walk before I run?

Great to see things are finally up and running for you!

The OXPs make a massive difference to the game. You can pretty much tailor it to your whims.

BUT. Our developers (a_c is the sole surviving exemplar of our original developers) went to a lot of trouble to make the vanilla game very playable. And even though it is not obvious, there are many subtleties which quietly enhance the experience.

Enjoy!

[Commander_X]

[...]

Just to confirm - the GPU Support is still not enabled and the DEBIOO window has not popped up again.

I have also shut down/rebooted a couple of times - and all remains stable as above.

Weird about the GPU, as without that I'd expect things to be terrible. Maybe there's a context issue here, and it's working for Oolite but not the terminal you're querying from.

Glad it's stable though.
[...]

If GPU Support was enabled into the chrome:// settings, but "glxinfo -B" still reports "Accelerated: No", there could be some explanations:
- your version of Chrome OS support for Linux is too old (that is, Chrome OS itself)
- you're not running "glxinfo -B" in a "Terminal" window of Chrome OS, but under a (some) terminal running under a different X server than the one provided by Google
I noticed this behavior while dabbling with the VM and trying to get some of the X apps under XFCE suite. The bottom line is that the display server provided by Google Chrome OS (sommelier?) is basically a Wayland compositor, and the X11 apps are executed under the Xwayland umbrella. In these conditions, the acceleration will work as expected (if Xwayland is the one installed side-by-side with the display server).
If another Xwayland (or X server for that matter) is executed, the acceleration won't be available.

A definitely useful notice is that what I installed in the qemu VM is not Chrome OS, but Chrome OS Flex. I'm not sure if this makes any difference.