Messages

31

Gemini PDA - Linux / Mainline linux kernel

« on: August 09, 2018, 04:40:51 am »

When I tried

Code: [Select]

make Image.gz-dtbit just worked

Is that with the mainline kernel source?

32

Gemini PDA - Linux / Hang on Shutdown

« on: August 06, 2018, 04:03:16 am »

Thank you for your very fast response.

>>systemd journal (set to non-volatile)<< That's a bit above my paygrade in Linux. Could you give me quick pointers on the right way to access that journal.

I'm using the stock version of systemd.

Thanks again,
Jake

Edit /etc/systemd/journald.conf and set Storage=persistent. You'll need to reboot or

Code: [Select]

systemctl restart systemd-journald. You should then have logs saved to /var/log/journald. Although you still need to use journalctl to read them, which is a tad controversial but allows you to do neat things like 'journalctl -b -1' (show messages from last boot) or 'journalctl --since "5 min ago"'

33

Gemini PDA - Linux / How to run Linux userland under Android

« on: August 04, 2018, 02:56:03 pm »

As a bonus, if you flash Linux dualboot, you can configure Linux Deploy to mount Linux partition and chroot there.

I've installed Linux Deploy, but I have no idea how to mount my dualboot image as you suggest.  Any hints?

Create a new profile and then in the settings for that profile select 'installation type: partition' and 'installation path: /dev/block/mmcblk0p29'. Select debian for your distro. Don't 'install' as linux is already on the partition. If you look around the forum you'll find some instructions for setting up the networking. otherwise you are pretty much golden.

34

Gemini PDA - Linux / Mainline linux kernel

« on: August 04, 2018, 11:09:42 am »

You need to append dtb to Image.gz. MediaTek's lk bootloader actually handles device tree (there is no appended dtb support for aarch64 in kernel), but in current implementation bootloader searches for appended device tree. The reason is that --dt option isn't/wasn't standard for abootimg format, it's generally used only by Qualcomm devices.

Thanks, I will give this another try. I was doing this:

Code: [Select]

cat Image.gz dtb_file > Image-dtb >
Is this correct? I also tried gunzipping the Image, appending and the gzipping it back up. But I dont think thats right..?

35

Gemini PDA - Linux / Mainline linux kernel

« on: August 01, 2018, 01:46:40 pm »

TheKit managed to boot a mainline X20 kernel at the gemini - almost, stuck at switching to user mode (or initrd)

I collected some informations at https://github.com/gemian/gemini-keyboard-a...LinuxMainlining . Here is also a boot log.

The bootlog is 404, does anyone have another link to it?

I have been trying to boot mainline now I have a UART cable but I keep getting device tree not found error. I was creating boot images with mkbootimg and using the --dt option to specify the dtb, but i've also tried appending the dtb to the kernel image. Both methods give me the same error. IMO appending the dtb to the kernel is hacky and very un-futureproof, does anyone know why we are doing this? Is it a limitation of our version of lk? I know old arm boards did this as a workaround for nonexistant or  buggy device tree support in their bootloaders, but this is going back years. It shouldnt be required in the world of arm8 and mature multiplatform support in the kernel

36

Gemini PDA - Linux / wlan0 internal wifi interface with other linux OS(s)

« on: August 01, 2018, 01:29:42 pm »

I didn't appreciate how reliant debian TP is on android shims. I really want to get linux running on an open stack without reliance on halium/libhybris.  X with fbdev is fine (apart from the chronic rebooting problem - but that happens anyway it's just worse when I run X) and midgard opensource driver will hopefully mature in the not too distant future (and can hopefully be back ported for 3.18). I know other devices (banana pi r2?) have mediatek internal wifi working natively in linux, but I don't hold out any hope for the telephony/modem (which I am not too fussed about).

Can anyone tell me how the initramfs is configured? The gemian wiki Kernel Compilation pages talks about it containing an "init script forked from hybris-boot, which is currently configured to boot system from /dev/mmcblk0p29 partition" but I can't find reference to this partition. Unless the partition is passed as a variable from little kernel bootloader?  

If anyone familiar with halium can explain a little about what is going on I would appreciate. I want to understand so I can not use it!

PS It made me chuckle how the halium documentation explicitly warns people from porting to mediatek devices! Lulz

37

Gemini PDA - Linux / wlan0 internal wifi interface with other linux OS(s)

« on: July 31, 2018, 04:38:45 pm »

Copy of post from developer.planetcom.co.uk (https://developer.planetcom.co.uk/showthread.php?tid=153&pid=371#pid371):

Hi,

I am trying to bring up the internal wifi under Arch Linux using the stock 3.18 kernel (recompiled with module support).

I've copied the firmware from .stowaways in the Debian TP sailfish rootfs to /lib/firmware (and symlinked to /etc/firmware, /system/extra/firmware and somewhere else I forget).

I then compiled these tools - https://github.com/abbradar/wmt. (I couldn't use the one from sailfish rootfs as the were compiled for the wrong arch (armhf? 32 bit?)

I then run wmt_loader and I get the following:

Code: [Select]

init combo device
Opened combo device
get device id : 26519
set device id : 26519
do module init: 26519
failed to init module
I can't for the life of me work out how you are bringing up the wifi in Debian TP - any pointers would be greatly appreciated! Just to clarify I am not even getting a wlan0 interface.  The networking with external devices is fine ie USB ethernet/wifi dongles.

Anyone over here have any thoughts?

38

Gemini PDA - General Discussion / Need copy of working NVRAM

« on: July 25, 2018, 06:35:16 pm »

Lost my copy of my working nvram and cant restore it , would I be able to use someone else's ? Not sure if that is doable or not . I have been able to recover the imei multiple times but cant clear issue with err 0x10 on the wifi and I think it might also be blocking my cell data on Debian side idk for sure .

I'm  sorry, I figure it's a bit of a security risk handing over the imei for my phone. Perhaps someone here who doesn't use the device as a  phone  might oblige?

39

Gemini PDA - General Discussion / Unable to boot

« on: July 25, 2018, 06:45:01 am »

I had the same problem - unable to boot.

Long pressing ESC + silver button to restart. Screen hanged up at planet logo.

1. I dried the battery to zero
2. made a full recharge
3. boot up worked again

If someone has the balls and the knowhow it would be interesting to see if disconnecting the battery fixes the issues. It sounds like the device is staying in some strange state and it finally gets a truly cold boot once the battery has drained. Disconnecting and reconnecting the battery would ensure the device has reached a completely off state.

40

Gemini PDA - Linux / My last post here : another user ( gbiot ) with video problem

« on: July 24, 2018, 08:51:03 am »

You are seriously stretching the definition of "my last post". In this thread, and the umpteenth others you have scattered around the place.

41

Gemini PDA - Linux / Linux desktop in lower resolution?

« on: July 20, 2018, 10:45:18 am »

Also, any other tips for making it more touch friendly?

In lxqt settings you could select larger fonts, resulting in larger menus. Maybe there are more interesting settings.

try
"xrandr --dpi 144"
and then open an app to see if it makes a difference (you'll need to restart an app for changes to appear)

 I haven't used lxqt but you could try influencing QT envs e.g.
"export QT_AUTO_SCREEN_SCALE_FACTOR=1"
https://blog.qt.io/blog/2016/01/26/high-dpi...port-in-qt-5-6/

or this may be of some help
https://wiki.debian.org/MonitorDPI

42

Gemini PDA - Android / Android Rooted/Unrooted Partitioning

« on: July 20, 2018, 10:31:53 am »

As far as I know it's one android installation.  The boot.img differs so you can either boot in rooted or unrooted mode, everything else remains constant.

Thanks, however when I installed them neither were rooted, I ran Magisk and now both are rooted. Is there a way to unroot the one image?

This has also confused me for some time.  Firstly I think (correct me if wrong) there are TWO ways of getting a rooted system

OPTION1 - Install the dual/tri boot option using the Web partitioning tool.

OPTION2- use the normal stock Android and install Magisk manager and then somehow use this to root the device - I am not very clear on this, perhaps someone can explain step by step what they did

I went with option 1 - normal boot is rooted,  silver button and power is non rooted.  When I downloaded all the files from Gemini I did a diff on them - the difference in the scatter file was there was a different boot image listed for the root one.  Everything else is the same.  So I think I have the same files in both modes but can only change the protected part of them in root mode?

I installed Magist manager as this has has the SU manager on it- i.e. a box pops up when an app wants root access.  And also one of the rootchecker apps off the play store - this correctly shows root / non root depending on how I boot.

Installing Magisk Manager and installing Magisk is not the same thing.  You can install Magisk to the boot.img by selecting 'install' from inside the Magisk Manager app. You can unistall it by using the Magisk Manager app and selecting 'uninstall'. If you have flashed a rooted boot.img then you don't need to install Magisk, but you can install the Magisk Manager app to get the SU binary as you  point out.

43

Gemini PDA - Hardware / Keyboard ghosting

« on: July 20, 2018, 10:28:22 am »

For the brave: I have created a Android boot image which has a fix for this issue.

You can find the image here:

https://github.com/zevv/gemini-android-kern...nux_boot-v1.img

Install with flashtool by downloading only the 'boot' partition and unticking the rest.

The original fix was made by Nathan Banks, I just took his code and built the image. It works fine for me, but use at your own risk, things might break.

Thanks that's really awesome. Can you post a link to Nathan Banks' code, or explain the fix?

44

Gemini PDA - Linux / My last post here : another user ( gbiot ) with video problem

« on: July 18, 2018, 01:42:17 pm »

I didn't want to say but I feel there was something fishy about this whole thing. I'm not even sure the videos of the broken gemini were completely legit and I don't think galodoido has been entirely truthful. I'm sorry to say that and I'd be happy to be wrong.

45

Gemini PDA - Linux / My Gemini is now useless Video Problem

« on: July 12, 2018, 01:48:29 pm »

This should probably be in the hardware or general discussion subforum.

Try removing the covers on the screen/hinge (as described here https://www.oesf.org/forum/index.php?showtopic=35377) and make sure the ribbon cable is seated correctly and there are no obvious signs of damage. A loose ribbon cable should be easy to fix if that is the case.