Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - Elevennails

Pages: [1]
1
Cosmo Communicator - Linux / Docker install causes unrecoverable NMI
« on: March 05, 2020, 12:06:14 pm »
Quote from: Beiriannydd
Quote from: Elevennails
If i install docker on the Cosmo it NMI reboots during the software installs. Not sure why guess it's a missing library I've followed the instructions from here selecting the arm64 build.

Unfortunately I can't capture the log files as i am unable to restart the debian image once it fails and have to flash the image back.

I have had this running on an ODRIOD before so i know it should work.

The ODROID was, I expect, running a Linux rather than an android kernel.  The permissions on Android are essentially single user oriented and the root account isn't just trusted to be able to do anything.

If we can turn the Android off in the kernel and keep a functioning machine (I don't need more than wifi when in Linux mode) then we'll be able to use docker.  There is no port I know of docker to Android which works.

This is what some people want, but it is useless to me.  Termux is a more useful linux environment on Cosmo than Gemian is for me.  Yes, Docker doesn't work but I don't expect it to and it isn't laggy or with widgets which fill the useful screen area.

Unfortunately I have a lot on at the moment and can't spend the time on this.  I suspect that we may be close to being able to run a standard kernel on the old Gemini.  That is probably where I will put my effort when I have time and keep this machine as a really decent Android.


Thanks for your efforts. Hopefully one day

2
Cosmo Communicator - Linux / Docker install causes unrecoverable NMI
« on: March 05, 2020, 12:04:09 pm »
Quote from: szopin
Quote from: Elevennails
If i install docker on the Cosmo it NMI reboots during the software installs. Not sure why guess it's a missing library I've followed the instructions from here selecting the arm64 build.

https://docs.docker.com/install/linux/docker-ce/debian

Unfortunately I can't capture the log files as i am unable to restart the debian image once it fails and have to flash the image back.

I have had this running on an ODRIOD before so i know it should work.

Has anyone got any ideas how i can debug? does any know why it force reboots?

Sorry i'm a noob really.

Thanks

Elevennails

You could try armhf version, not really sure how good the support for arm64 is from libhybris side (jolla doesn't support it yet afaik and they are(were?) the biggest contributor to libhybris, so very likely it's still lacking)

Thanks gave it a go didn't work loads of missing libraries

3
Cosmo Communicator - Linux / Docker install causes unrecoverable NMI
« on: February 29, 2020, 09:43:26 am »
Just tried again, Seems to get as far as trying to create sockets and powers off. Trying to restart then sends the cosmo into a reboot loop and i have to revert the image to a fresh install.

This is my last hurdle to have everything i need

Anyone got any ideas how i can debug. Or what might be going wrong.

4
Cosmo Communicator - Linux / MAC address changing during reboot
« on: February 29, 2020, 08:40:02 am »
Quote from: szopin
Quote from: g.husson
Hello, path seems to be /mnt/vendor/nvdata --> /mnt/vendor/nvdata/APCFG/APRDEB/WIFI
I don't know if the same tweak applies to this file...
This has the MAC address reported by android on mine, but the ones it's getting seem random. For automatically connecting to wifi it's enough to clear the 'Restrict to device' field in NetworkManager settings. macchanger seems to work, so if you have mac filtering on your router a shell script to 'ifconfig wlan0 down/macchanger -m aa:bb... wlan0/ifconfig wlan0 up' should do it (apt-get wireless-tools and macchanger first as needed). Not sure yet how to properly and once and for all replace NetworkManager with connman for mobile data, as it seems to revert to NetworkManager after reboot (and probably also is causing the random mac ignoring the file you mentioned), but still haven't got a nano sim to test it properly


Changing the mac in hexedit as per the DebainTP3 Connman link didn't work for me.

As you suggested clearing the "Restrict to device" field resolves my problem. I'm not bothered if the mac address changes it's was just a pain to have to re-enter the WIFI password everytime i rebooted

Thanks for the tip.

5
Cosmo Communicator - Linux / Docker install causes unrecoverable NMI
« on: February 25, 2020, 12:49:32 pm »
If i install docker on the Cosmo it NMI reboots during the software installs. Not sure why guess it's a missing library I've followed the instructions from here selecting the arm64 build.

https://docs.docker.com/install/linux/docker-ce/debian

Unfortunately I can't capture the log files as i am unable to restart the debian image once it fails and have to flash the image back.

I have had this running on an ODRIOD before so i know it should work.

Has anyone got any ideas how i can debug? does any know why it force reboots?

Sorry i'm a noob really.

Thanks

Elevennails

6
Cosmo Communicator - Linux / Beta Linux Testing
« on: February 25, 2020, 12:42:19 pm »
Someone mentioned they had difficulties getting the keyboard characters to properly display earlier in this thread. Here's the config changes and work arounds i've made so far.

Here's how I've set mine for the UK It does seem to be working fine.

Language

1. Time/Date

settings | Regional Settings | Date & Time | Time Zone | Search London - Click Apply

2. Language

settings Regional Settings | Language | Add Languages - British English - Move it up to top of list to make default - Click apply

3. Formats

Settings Regional Settings | Formats | Region| United Kingdom - British English (en_GB) - I left the "Detailed Settings Check box unticked"

4. Keyboard

settings Regional Settings | Input Devices | Hardware (Tab) | Keyboard model: "Planet | Planet Comupters Cosmo COmmunicator" - Apply
settings Regional Settings | Input Devices | Layouts (Tab) | Configure Layouts | Add "English (UK) n- Select English (USA) and click remove - Apply

Blanks screen on powersave
Next I've disabled the power management. As it seems to keep leaving me with blank screen from which i'm to force a reboot. This does seem to prevent the black screen.
System tray | click the battery icon | Untick "Enable Power Management"


Mouse fix
Next I implemented the mouse fix from here...

https://www.oesf.org/forum/index.php?showtopic=35185

Here's a script to update and upgrade + add the support for the above help topic.

1. create a file called 40-libinput.conf on your sdcard

[div class=\'codetop\']CODE[/div][div class=\'codemain\' style=\'height:200px;white-space:pre;overflow:auto\']Section "InputClass"
        Identifier "libinput touchscreen catchall"
        MatchIsTouchscreen "on"
        MatchDevicePath "/dev/input/event*"
        Driver "mtrack"
        Option "ScrollDistance" "40"
        Option "FingerLow" "1"
        Option "FingerHigh" "2"
        Option "Sensitivity" "1.8"
        Option "BottomEdge" "0"
        Option "SwipeDistance" "100"
        Option "ScaleDistance" "40"
        Option "ButtonMoveEmulate" "false"
        Option "ClickTime" "25"
        Option "MaxTapMove" "55"
        Option "EdgeBottomSize" "0"
EndSection[/div]

Create a file call mouse.sh on your SDcard

[div class=\'codetop\']CODE[/div][div class=\'codemain\' style=\'height:200px;white-space:pre;overflow:auto\']#!/bin/bash
echo cosmopda    127.0.0.1 >> /etc/hosts #Stops sudo complaining!
apt-get update
apt-get upgrade
apt-get install xserver-xorg-input-mtrack
cp 40-libinput.conf /usr/share/X11/xorg.con/40-libinput.conf
shutdown -r now #This reboot applies the changes. the service restart didn't work for me[/div]                        

Open a terminal
move to the sdcard location you saved the above files. (mine is here... cd /media/cosmo/3B3A-191B your's may be different)

sudo su #and enter the password for cosmo
. mouse.sh

Hope someone finds this useful. I've copy typed from my cosmo cos i was too lazy to copy file across hopefully there's no typos...

This makes the mouse behave more like a VNC session and not stick to your finger like the default one does. For some reason i was having difficulty getting to the screen extents top and bottom. I like this solution better. You also get gestures for left mouse click etc. I didn't turn off the mouse acceleration in LXQT or build from source. I just used the default debian driver. If you save the 2 script files to your SD card you'll be able to reapply these changes back quickly should you default and start again.

If anyone has any info on how to stop the Wifi card getting a new mac address after each boot. This could save me some agro  I've posted about it here.

https://www.oesf.org/forum/index.php?showtopic=36146

Looks like the same issue as the gemini had.

Hey Dev's great job. I've been longing for the debian release for ages! It's great we finally have it    Thanks for all your efforts


Elevennails

7
Cosmo Communicator - Linux / MAC address changing during reboot
« on: February 24, 2020, 04:28:32 pm »
Hi I'm using the image PC have just released. I've noticed that the mac address is changing on they cosmo between reboots and i assume it's the same Connman issue as this from the gemini forum

https://github.com/gemian/gemian/wiki/DebianTP3

However this folder structure does not exist. Does anyone know how to prevent the mac address changing on the cosmo? Has anyone got work around?

Thanks
Elevennails

8
Cosmo Communicator - Linux / Linux community?
« on: January 27, 2020, 06:45:16 pm »
Quote from: Elevennails
Ok so found this today...  Jumping the gun a bit, but thinking about building it. I guess now we can resize and change the bootloader, all we need to do i put the an img file on an SD card and point the bootloader at it.... Has anyone else tried successfully yet?

https://github.com/gemian/cosmo-linux-kernel-4.4

Thanks

OK Still trying to jump the gun  

As above I've resized the partition ready for Debian. If i copy the gemini debain_boot.img and linux.img files to the SDCard from here

http://support.planetcom.co.uk/download/Li...uxFirmware.html

Boot to recovery and select "Install custom OS on your COSMO"

a. Will the install actually find the .img files and start the install?
b. If the install starts will it trash the existing android partitions (that would be upsetting) or will it just consume the free space I've created. Or will it prompt
c. If the install completes will anything work . If i can get the basic OS to install, I could extract the debian.img and change the runlevel and reinstall just to get a prompt and start fixing stuff.


Thanks

Elevennails

9
Cosmo Communicator - Linux / Linux community?
« on: January 22, 2020, 11:33:53 am »
Ok so found this today...  Jumping the gun a bit, but thinking about building it. I guess now we can resize and change the bootloader, all we need to do i put the an img file on an SD card and point the bootloader at it.... Has anyone else tried successfully yet?

https://github.com/gemian/cosmo-linux-kernel-4.4

Thanks

10
Cosmo Communicator - General Discussion / HDMI Output
« on: January 20, 2020, 06:14:34 pm »
Quote from: mithrandir
Quote from: Elevennails
All is good so far I'm now working on the 20200117_1823.

I'm wondering what the requirements for the hdmi support are. I have a startech hdmi to usb c adapter but it doesn't seem to work.

Has anyone else been able to connect to hdmi? Is the planet hdmi adapter proprietary?

I've tried both USB c ports.
Yes,  it is proprietary. Third party adapters are unlikely to work (never heard a success with Gemini or Cosmo). Displaylink should work, alternatively.


Do you think that will also be the case under debian. I know Samsung galaxy note 10 works with the starhdmi to usbc cable I have. So it sounds like its just a driver issue.

11
Cosmo Communicator - General Discussion / HDMI Output
« on: January 20, 2020, 02:36:52 pm »
All is good so far I'm now working on the 20200117_1823.

I'm wondering what the requirements for the hdmi support are. I have a startech hdmi to usb c adapter but it doesn't seem to work.

Has anyone else been able to connect to hdmi? Is the planet hdmi adapter proprietary?

I've tried both USB c ports.

12
Cosmo Communicator - General Discussion / Firmware update
« on: January 20, 2020, 02:27:02 pm »
Quote from: mithrandir
Quote from: Elevennails
Quote from: PNuT
I resized mine earlier!

FN+ESC+ Right side of rocker switch to get the recovery menu


Thanks PNuT that worked I've resized  at least I can use Droid now  hopefully the debian img will come soon

Here's how i did it

From Off.

ESC (poweron) + rear rocker (top... volume up). Let go of power when Planet logo displays.

Driod pic on it's back. With Red triangle warning. Words "No Command" in really small letters underneath

Now

Fn+ESC+Rear rocker (Volume up)

Now we are in the recovery menu. Resize away

Well, this way we get to a menu allowing to repartition. It says all data will be lost. So I aborted for now, since I don't know how to reinstall the OS afterwards (without downloadable images). Any hints on how to get at least Android up again after repartitioning? Or don't we loose the OS with the resize?

Sorry yes the repartition will delete all your user data. But not the os. Be same as a factory reset. So you'll have to reinstall all your apps.

13
Cosmo Communicator - General Discussion / Firmware update
« on: January 19, 2020, 06:30:57 pm »
Quote from: PNuT
I resized mine earlier!

FN+ESC+ Right side of rocker switch to get the recovery menu


Thanks PNuT that worked I've resized  at least I can use Droid now  hopefully the debian img will come soon

Here's how i did it

From Off.

ESC (poweron) + rear rocker (top... volume up). Let go of power when Planet logo displays.

Driod pic on it's back. With Red triangle warning. Words "No Command" in really small letters underneath

Now

Fn+ESC+Rear rocker (Volume up)

Now we are in the recovery menu. Resize away

14
Cosmo Communicator - General Discussion / Firmware update
« on: January 19, 2020, 07:44:48 am »
Quote from: zottel
I received an update yesterday and installed it without problems. I didn't find anything that changed yet, not even the Android security patch level, so I guess it's mainly about the fix for the backdoor? No cover display update this time, either.

As nobody has written about it here yet and it's also still not mentioned on the support website, I'm beginning to feel a bit strange, though. Did anybody else receive the update, or does anybody know more about it?

I have Android build number Cosmo-9.0-Planet-01182020-V19 now.

I also had the update yesterday. The only change I think I can see is that I don't appear to be able to get to the recover boot menu. It now seems to go into safe mode instead.

Power on <esc> fingerprint toggle <button> down. Unless I'm doing this wrong. I'm sure I used to get a recovery menu.

Was hoping. To be able to resize partitions ready for debian. So I can start using the driod partition without worrying about reinstallimg or loosing my driod data later. Guess I'll have to be more patient

Pages: [1]