Help - Search - Members - Calendar
Full Version: Final call for TP3
OESF Portables Forum > Model Specific Forums > Gemini PDA > Gemini PDA - Linux OS
Pages: 1, 2
Adam Boardman
Are there any changes you think should be included before we release DebianTP3?

Ideally quick easy fixes or tested pull requests for bigger changes.

I was wondering about:
  • Splitting of the bottom bar to a left and right one?
  • Graphical updates for wall papers or lock screen backgrounds?
Kiriririn
The one big thing I think would go down well is defaulting to no Glamor - disabling it transformed my device from alpha-quality to daily driver. It's a massive improvement in performance - scrolling feels as smooth as full size laptops afterwards. You do lose Chromium and VLC, but considering how well Firefox works with Glamor off I think it's a worthy default. Also needs a new login screen as sddm doesn't take kindly to it, so maybe too big a change for TP3...

Other smaller things:
- https://www.oesf.org/forum/index.php?showtopic=35185 (better to build from source and disable acceleration) - can't imagine using Gemini without this
- I've found a vertical panel works well, not something I'd normally use but it feels natural on the Gemini. (I don't think you need two bars, one double-width icon-only one is plenty)
- I can't remember if it's in already, but I've got lxqt-runner bound to alt+space, nicer than the fiddly start menu imo
Eric BF
QUOTE(Kiriririn @ Jan 30 2019, 10:15 AM) *
The one big thing I think would go down well is defaulting to no Glamor - disabling it transformed my device from alpha-quality to daily driver.

How do you disable Glamor? I would like to try. Thanks.
Kiriririn
QUOTE(Eric BF @ Jan 30 2019, 11:41 AM) *
QUOTE(Kiriririn @ Jan 30 2019, 10:15 AM) *
The one big thing I think would go down well is defaulting to no Glamor - disabling it transformed my device from alpha-quality to daily driver.

How do you disable Glamor? I would like to try. Thanks.


I believe I rebuilt xf86-video-hwcomposer without --enable-glamor-hybris, cant remember if there was more to it than that
Eric BF
Ah, okay; I was hoping to avoid having to build anything from source. (used to do this all the time in the old days of Linux in the 90s mind you...)
jornada720
Any chance you could fix the KDE keyboard situation?

It's soooo much more powerful and better suited for the high-dpi screen than LxQT. Among its many advantages, you can actually use the taskbar. Icons can be probably sized as well.
Kiriririn
QUOTE(jornada720 @ Jan 30 2019, 02:49 PM) *
Any chance you could fix the KDE keyboard situation?

It's soooo much more powerful and better suited for the high-dpi screen than LxQT. Among its many advantages, you can actually use the taskbar. Icons can be probably sized as well.


I've got no issues with DPI scaling on lxqt, it works excellently

I have the following env vars set:

GDK_DPI_SCALE=1.75
GTK_CSD=0
GTK_OVERLAY_SCROLLING=1
QT_AUTO_SCREEN_SCALE_FACTOR=1
XCURSOR_SIZE=48

And xdefaults

Xft.dpi: 192
Xcursor.size: 48

And 96 dpi set in lxqt

Basically all from https://wiki.archlinux.org/index.php/HiDPI
TheKit
QUOTE(Kiriririn @ Jan 30 2019, 02:33 PM) *
QUOTE(Eric BF @ Jan 30 2019, 11:41 AM) *

How do you disable Glamor? I would like to try. Thanks.

I believe I rebuilt xf86-video-hwcomposer without --enable-glamor-hybris, cant remember if there was more to it than that

It can be disabled by setting Option "AccelMethod" "None" in the device section of /etc/X11/xorg.conf, for example:
QUOTE
Section "Device"
Identifier "MediaTek HWC"
Driver "hwcomposer"
Option "AccelMethod" "None"
EndSection

If you update to latest libhybris and xf86-video-hwcomposer from Gemian repos, chromium will still work, but with color channels flipped. Might be interesting to compare performance though. If it is really much better without glamor, we could look into dri3 support without glamor, which would allow EGL applications to still work, although a bit slower due to buffer copy involved.
Kiriririn
QUOTE(TheKit @ Jan 30 2019, 08:04 PM) *
QUOTE(Kiriririn @ Jan 30 2019, 02:33 PM) *
QUOTE(Eric BF @ Jan 30 2019, 11:41 AM) *
QUOTE(Kiriririn @ Jan 30 2019, 10:15 AM) *
The one big thing I think would go down well is defaulting to no Glamor - disabling it transformed my device from alpha-quality to daily driver.

How do you disable Glamor? I would like to try. Thanks.


I believe I rebuilt xf86-video-hwcomposer without --enable-glamor-hybris, cant remember if there was more to it than that

It can be disabled by setting Option "AccelMethod" "None" in the device section of /etc/X11/xorg.conf, for example:
QUOTE
Section "Device"
Identifier "MediaTek HWC"
Driver "hwcomposer"
Option "AccelMethod" "None"
EndSection

If you update to latest xf86-video-hwcomposer from Gemian repos, chromium will still work, but with color channels flipped. Might be interesting to compare performance though. If it is really much better without glamor, we could look into dri3 support without glamor, which would allow EGL applications to still work, although a bit slower due to buffer copy involved.


That would be a good idea if possible

I've done a lot of work with gl + mali on android, it's borderline impossible to upload textures without heavy stalling using the standard GLES userspace api (even with pixel buffers etc), as glamor is doing (or was when I last checked). It must be possible at some level though for android itself and apps using things like hardwarebuffer/graphicbuffer to be unaffected
TheKit
QUOTE(Kiriririn @ Jan 30 2019, 10:17 PM) *
That would be a good idea if possible

I've done a lot of work with gl + mali on android, it's borderline impossible to upload textures without heavy stalling using the standard GLES userspace api (even with pixel buffers etc), as glamor is doing (or was when I last checked). It must be possible at some level though for android itself and apps using things like hardwarebuffer/graphicbuffer to be unaffected

Would be nice to have some comparisons/measurements beforehand though. I think when you last used glamor it was a bit slower than current due to glFinish hack from Rockchip.

The ultimate solution is switching to Wayland, as then the compositor renders with GLES and it is fast even with texture uploads for shmem windows, but that's outside of TP3 scope. The problem with Wayland though is that there is no standard server implementation like Xorg, each compositor is an implementation of its own.
mithrandir
With switching to Wayland we would loose X11 and many applications with it. This would be nearly the same as switching to Sailfish. So I would vote against it.
mithrandir
Any chance to get cameras and GPS?
mithrandir
Maybe it is worth to wait until the Android update. There might be a chance for a 4.x kernel with it. Well, or does anybody know the upcoming Oreo update sticks with the 3.18 kernel?

Anyways, the kernel should be upgraded (if not already happened, I am using a custom one) to current git. The latest fix, disabling the keyboard on lid close works quite well. Before, when recognizing the Gemini in the pocket getting hot, already a quarter of battery juice has been lost...
TheKit
QUOTE(mithrandir @ Jan 30 2019, 10:51 PM) *
With switching to Wayland we would loose X11 and many applications with it. This would be nearly the same as switching to Sailfish. So I would vote against it.

Desktop Wayland compositors have XWayland support, which is basically running Xorg server on top of Wayland and it works pretty good. It is just Sailfish choose not to support legacy apps for obvious reasons.

QUOTE(mithrandir @ Jan 30 2019, 10:54 PM) *
Any chance to get cameras and GPS?

For cameras, either libcamera_compat_layer from Ubuntu Touch or gst-droid from Sailfish can be used as middleware, but then we need respective camera app ported. For GPS, are there actually any "desktop" apps capable of utilizing it?

QUOTE(mithrandir @ Jan 30 2019, 11:08 PM) *
Maybe it is worth to wait until the Android update. There might be a chance for a 4.x kernel with it. Well, or does anybody know the upcoming Oreo update sticks with the 3.18 kernel?

Anyways, the kernel should be upgraded (if not already happened, I am using a custom one) to current git. The latest fix, disabling the keyboard on lid close works quite well. Before, when recognizing the Gemini in the pocket getting hot, already a quarter of battery juice has been lost...

It sticks with 3.18 as MediaTek did not port mt6797 support onto 4.x.
mithrandir
@TheKit:
Thanks, good to know.

Then (obviously) I would also like the Wayland solution, but as you told, this would be too much for TP3. The kernel part is a bit unfortunate, really hoped for an update. 3.18 is pretty much EOL... Also hoped for a newer kernel fixing the sd card performance after sleep issue, present in both, Android and Debian.

Regarding GPS apps, it should be possible to run navit on the gemini, still using this on my old n900, but there are quite some more, i.e. kismet supports GPS, via gpsd if I remember correctly.
mibry
I hope that TP3 will fix the problem I am encountering. I had to reflash my gemini with android and debian, when I did the dist-upgrade and install kernel I had not taskbasr come up after rebooting the gemini, I only had the background and was unable to access any menus.

Any ideas?

Thanks in advance.

QUOTE(mithrandir @ Jan 30 2019, 08:32 PM) *
@TheKit:
Thanks, good to know.

Then (obviously) I would also like the Wayland solution, but as you told, this would be too much for TP3. The kernel part is a bit unfortunate, really hoped for an update. 3.18 is pretty much EOL... Also hoped for a newer kernel fixing the sd card performance after sleep issue, present in both, Android and Debian.

Regarding GPS apps, it should be possible to run navit on the gemini, still using this on my old n900, but there are quite some more, i.e. kismet supports GPS, via gpsd if I remember correctly.

Kiriririn
QUOTE(mibry @ Jan 31 2019, 10:43 AM) *
I hope that TP3 will fix the problem I am encountering. I had to reflash my gemini with android and debian, when I did the dist-upgrade and install kernel I had not taskbasr come up after rebooting the gemini, I only had the background and was unable to access any menus.

Any ideas?

Thanks in advance.

QUOTE(mithrandir @ Jan 30 2019, 08:32 PM) *
@TheKit:
Thanks, good to know.

Then (obviously) I would also like the Wayland solution, but as you told, this would be too much for TP3. The kernel part is a bit unfortunate, really hoped for an update. 3.18 is pretty much EOL... Also hoped for a newer kernel fixing the sd card performance after sleep issue, present in both, Android and Debian.

Regarding GPS apps, it should be possible to run navit on the gemini, still using this on my old n900, but there are quite some more, i.e. kismet supports GPS, via gpsd if I remember correctly.



It's a dependency issue in the new pulseaudio update, I had assumed it was 'just me' with the amount I've changed things but I guess not

You can fix it by installing ubuntu-application-api3-touch via apt
mibry
Ok thanks

QUOTE(Kiriririn @ Jan 31 2019, 02:53 PM) *
QUOTE(mibry @ Jan 31 2019, 10:43 AM) *
I hope that TP3 will fix the problem I am encountering. I had to reflash my gemini with android and debian, when I did the dist-upgrade and install kernel I had not taskbasr come up after rebooting the gemini, I only had the background and was unable to access any menus.

Any ideas?

Thanks in advance.

QUOTE(mithrandir @ Jan 30 2019, 08:32 PM) *
@TheKit:
Thanks, good to know.

Then (obviously) I would also like the Wayland solution, but as you told, this would be too much for TP3. The kernel part is a bit unfortunate, really hoped for an update. 3.18 is pretty much EOL... Also hoped for a newer kernel fixing the sd card performance after sleep issue, present in both, Android and Debian.

Regarding GPS apps, it should be possible to run navit on the gemini, still using this on my old n900, but there are quite some more, i.e. kismet supports GPS, via gpsd if I remember correctly.



It's a dependency issue in the new pulseaudio update, I had assumed it was 'just me' with the amount I've changed things but I guess not

You can fix it by installing ubuntu-application-api3-touch via apt

wrobell
It would be great to have GPS indeed. smile.gif
Adam Boardman
QUOTE(Kiriririn @ Jan 30 2019, 11:15 AM) *
- https://www.oesf.org/forum/index.php?showtopic=35185 (better to build from source and disable acceleration) - can't imagine using Gemini without this

I thought I'd persuaded someone to report back to me when they had the perfect config for that mouse thing so I could branch it into gemian, they never got back to me, very happy to add that. I can add you to the project on github or whatever suits.

QUOTE(Kiriririn @ Jan 30 2019, 11:15 AM) *
- I've found a vertical panel works well, not something I'd normally use but it feels natural on the Gemini. (I don't think you need two bars, one double-width icon-only one is plenty)

Sounds interesting, I did try the double bars version for a while but lost the config when I got the digital rain and never got round to doing it again after a pointless reflash. Digital rain just needs a flat battery/disconnect to fix. If folks with interesting layouts could post screenshots then we can pick what we think is the most generally useful as a default, and the others would make a good set of examples for folks to see whats possible.

QUOTE(Kiriririn @ Jan 30 2019, 11:15 AM) *
- I can't remember if it's in already, but I've got lxqt-runner bound to alt+space, nicer than the fiddly start menu imo

Cool, I've put that in, very useful.
jornada720
QUOTE(Kiriririn @ Jan 30 2019, 01:12 PM) *
QUOTE(jornada720 @ Jan 30 2019, 02:49 PM) *
Any chance you could fix the KDE keyboard situation?

It's soooo much more powerful and better suited for the high-dpi screen than LxQT. Among its many advantages, you can actually use the taskbar. Icons can be probably sized as well.


I've got no issues with DPI scaling on lxqt, it works excellently

I have the following env vars set:

GDK_DPI_SCALE=1.75
GTK_CSD=0
GTK_OVERLAY_SCROLLING=1
QT_AUTO_SCREEN_SCALE_FACTOR=1
XCURSOR_SIZE=48

And xdefaults

Xft.dpi: 192
Xcursor.size: 48

And 96 dpi set in lxqt

Basically all from https://wiki.archlinux.org/index.php/HiDPI


Have you ever tried KDE Plasma compared to LXQT? It is about 3 or 4 times more useful. All of those settings can easily be adjusted with a GUI, for instance.

The Gemini is more than capable of running it, except the keyboard doesn't work correctly.
Kiriririn
QUOTE(jornada720 @ Feb 2 2019, 04:40 PM) *
QUOTE(Kiriririn @ Jan 30 2019, 01:12 PM) *
QUOTE(jornada720 @ Jan 30 2019, 02:49 PM) *
Any chance you could fix the KDE keyboard situation?

It's soooo much more powerful and better suited for the high-dpi screen than LxQT. Among its many advantages, you can actually use the taskbar. Icons can be probably sized as well.


I've got no issues with DPI scaling on lxqt, it works excellently

I have the following env vars set:

GDK_DPI_SCALE=1.75
GTK_CSD=0
GTK_OVERLAY_SCROLLING=1
QT_AUTO_SCREEN_SCALE_FACTOR=1
XCURSOR_SIZE=48

And xdefaults

Xft.dpi: 192
Xcursor.size: 48

And 96 dpi set in lxqt

Basically all from https://wiki.archlinux.org/index.php/HiDPI


Have you ever tried KDE Plasma compared to LXQT? It is about 3 or 4 times more useful. All of those settings can easily be adjusted with a GUI, for instance.

The Gemini is more than capable of running it, except the keyboard doesn't work correctly.


Yeah it's my desktop of choice, but I find lxqt fits the Gemini's limited hardware and screen area better. It's a shame that it's kind of unfinished software, especially the version shipped in stretch
Kiriririn
QUOTE(Adam Boardman @ Feb 2 2019, 02:24 PM) *
QUOTE(Kiriririn @ Jan 30 2019, 11:15 AM) *
- https://www.oesf.org/forum/index.php?showtopic=35185 (better to build from source and disable acceleration) - can't imagine using Gemini without this

I thought I'd persuaded someone to report back to me when they had the perfect config for that mouse thing so I could branch it into gemian, they never got back to me, very happy to add that. I can add you to the project on github or whatever suits.


Sounds good I'm happy to contribute whatever way works best

I'm still using the config as posted in that thread, no complaints using it regularly once you get used to the different gesture for dragging than what people might be used to on laptop synaptics touchpads, everything else feels pretty natural

QUOTE(Adam Boardman @ Feb 2 2019, 02:24 PM) *
QUOTE(Kiriririn @ Jan 30 2019, 11:15 AM) *
- I've found a vertical panel works well, not something I'd normally use but it feels natural on the Gemini. (I don't think you need two bars, one double-width icon-only one is plenty)

Sounds interesting, I did try the double bars version for a while but lost the config when I got the digital rain and never got round to doing it again after a pointless reflash. Digital rain just needs a flat battery/disconnect to fix. If folks with interesting layouts could post screenshots then we can pick what we think is the most generally useful as a default, and the others would make a good set of examples for folks to see whats possible.


This is my current layout:



(Really could do with https://github.com/lxqt/lxqt/issues/131)

QUOTE(Adam Boardman @ Feb 2 2019, 02:24 PM) *
QUOTE(Kiriririn @ Jan 30 2019, 11:15 AM) *
- I can't remember if it's in already, but I've got lxqt-runner bound to alt+space, nicer than the fiddly start menu imo

Cool, I've put that in, very useful.


Awesome, couple more things I've just remembered I added that might be useful...

In lxqt globalkeyshortcuts.conf

CODE
[Print.20]
Comment=scrot
Enabled=true
Exec=scrot

(+ dependency on scrot) for screenshots on Fn+R (key that looks most like it should take a screenshot imo)

CODE
[XF86TopMenu.34]
Comment=show desktop actual
Enabled=true
Exec=/(somewhere)/minimise-all

CODE
#!/bin/bash
for i in {1..20}
do
xdotool getactivewindow windowminimize
done

(+ dependency on xdotool) for a winkey+d/m like behaviour on Fn+D, since the lxqt show desktop command doesnt work (can't remember if this is a side effect of no compositor)
Adam Boardman
The shortcuts are defined in https://github.com/gemian/lxqt-common/blob/...yshortcuts.conf we already have print screen and show desktop working so far as I know, I'd rather you left working things working unless you get a consensus to change, ie a poll here to check which of two options people prefer.

So far I've given github access to the gemian project to anyone who wanted (messaging me with an email address is probably best), no abuse so far though also virtually zero use either. The gatekeeping comes in when we build components, currently you've to persuade either Nikita (TheKit) or I to code review any changes and kick off a jenkins build before it gets pushed to the apt repository.
TheKit
QUOTE(jornada720 @ Feb 2 2019, 06:40 PM) *
Have you ever tried KDE Plasma compared to LXQT? It is about 3 or 4 times more useful. All of those settings can easily be adjusted with a GUI, for instance.

The Gemini is more than capable of running it, except the keyboard doesn't work correctly.

It can be workarounded for now by disabling conflicting key shortcuts in System Settings.
bled82
Would it be possible to get USB c full dock support for Dell dock wd15? Aka ethernet/hdmi/display port/usb/power delivery?
Murple2
QUOTE(bled82 @ Feb 6 2019, 12:17 PM) *
Would it be possible to get USB c full dock support for Dell dock wd15? Aka ethernet/hdmi/display port/usb/power delivery?


This doesn't use displaylink technology so it is very unlikely you could ever use the video output. Impossible, I would go so far to say.
bled82
Ah ok , I think we have a Kingston sd4000 somewhere at work I can yet out, anything special I need? It's display lynk. I have the USB c adapter needed.
Murple2
QUOTE(bled82 @ Feb 6 2019, 01:49 PM) *
Ah ok , I think we have a Kingston sd4000 somewhere at work I can yet out, anything special I need? It's display lynk. I have the USB c adapter needed.



V2 displaylink has open source drivers and v3, AFAIK, does not. You will need the evdi kernel module and then some user space binaries for arm64. It may be possible but certainly not for the faint of heart.
ArchiMark
Has getting ethernet working been addressed?

Would be nice to have that option to use the Gemini hub (or possibly other usb adapter...) when WiFi not available.
Adam Boardman
QUOTE(ArchiMark @ Feb 7 2019, 05:09 AM) *
Has getting ethernet working been addressed?


Yes that's been working fine since August: https://github.com/gemian/gemini-linux-kern...509d60851cba362
ArchiMark
QUOTE(Adam Boardman @ Feb 7 2019, 12:57 AM) *
QUOTE(ArchiMark @ Feb 7 2019, 05:09 AM) *
Has getting ethernet working been addressed?


Yes that's been working fine since August: https://github.com/gemian/gemini-linux-kern...509d60851cba362


Great!

Thanks for all your excellent work for the Gemini!

Mark
PlasmaStrike
Multiple image choices would be nice.

Minimal Image -- I would like to set up this device from scratch arch linux style. That way I can try different window mangers under the gemini without trying to rip out lxde, As well for logging in I only want auto login, as I only use the device so lightdm is over complicated and a waste of spce among other things. I clean base to start off with would be nice. for instance here is what somebody else is doing with the base image New gemini experience. I will try to get exwm working with ming

Kde image -- I wouldn't use this but would have a different suite of apps compared to lxqt

other de/wm images -- So people can chose a base they want like void linux
Adam Boardman
Given Planets Gemini update 68, specifically releasing sfos 3 beta from Jolla, plus:
QUOTE
We will update the partition tool with new versions of the software when new images will be released by the community.

This has taken the pressure off the TP3 release which I had thought was supposed to go out along with the new Android 8 + SFOS 3 etc.

So we might as well wait till we've got a few more things sorted out. Plus someone needs to figure out what the plan is with multi-OS in the new LVM land of the sfos release. I'm assuming we can lvm resize things to fit in a debian image too? But as that would require reformatting my device I'm unsurprisingly not so keen.
idc
Thanks for this update. I very much want to try out Sailfish OS, but would like to be able to try Debian at the same time. For the moment I've held off installing SFOS, because I was hoping for a new Debian TP3 at the same time. If it really isn't due soon, I guess I might just give sailfish a go. But wouldn't it be better to get the new TP3 out anyway? There must be a fair number of people like myself who are waiting for it, and the increase in users might just help give it a boost. (My excuse for not having sorted it so far is being 'time poor' for fiddling with lots of settings.) I'm sure there are others like myself who are desperate for an escape from Google and Android on the Gemini. The hardware (by which I suppose I mean the keyboard) is great; I'm just waiting for a better OS!

Anyway, all this by way of thanking you, Adam, and others for the work that is being done on getting Linux running well on the gemini. If there is anything we can do to encourage you, please say!
Ian

QUOTE(Adam Boardman @ Feb 17 2019, 10:50 AM) *
Given Planets Gemini update 68, specifically releasing sfos 3 beta from Jolla, plus:
QUOTE
We will update the partition tool with new versions of the software when new images will be released by the community.

This has taken the pressure off the TP3 release which I had thought was supposed to go out along with the new Android 8 + SFOS 3 etc.

So we might as well wait till we've got a few more things sorted out. Plus someone needs to figure out what the plan is with multi-OS in the new LVM land of the sfos release. I'm assuming we can lvm resize things to fit in a debian image too? But as that would require reformatting my device I'm unsurprisingly not so keen.

Adam Boardman
QUOTE(idc @ Feb 17 2019, 12:37 PM) *
I very much want to try out Sailfish OS, but would like to be able to try Debian at the same time.

Check some other recent threads on the Sailfish chat, or for that matter the partition tool itself, you'll find that Planet have decided against the 'stowaways' form of multi OS hosting thus meaning that you can only install Android+One other OS with the flash tool. The options disappear as you select them from the drop-downs on the partition tool.

This is what I was referring too with my multi-OS comment above, if your game for it then you could try installing the Android+Sailfish as from planet (get happy with it and decide how much space you want to keep for it), then resize (shrink) your Sailfish LVM volumes, and get back to us and we could try making a LVM compatible version of Debian that you could then 'dd' to a boot partition/root unzip from within sailfish to a new debian volume in the space made available by shrinking the sfos volume. First thing I'd like to know is what the sailfish volume names/size etc are. The idea is that our debian LVM release (probably TP3) would have different names from sailfish and so you could then install either A+S or A+D from planet then later do the resize and copy the other one (or Kali/UBPorts/Other future OS) across later for multi-os usage. Thus allowing OS changes without resorting to the flash tool.

I'd also be interested to know if people would want to have things split so that maybe a stretch root and a buster root are available with a debianhome that they both mount so that you can share user files between os's? (could possibly also extend to get sfos/kali to mount the same root?) Or is it best to keep things clean and just allow users to mount the other homes as desired, there are some bits of software that change their file formats between versions and so for example Telegram Desktop gets confused when you launch the stretch version after launching the buster one (you just have to login/2fa again).
andrewl
QUOTE
I'd also be interested to know if people would want to have things split so that maybe a stretch root and a buster root are available with a debianhome that they both mount so that you can share user files between os's? (could possibly also extend to get sfos/kali to mount the same root?) Or is it best to keep things clean and just allow users to mount the other homes as desired, there are some bits of software that change their file formats between versions and so for example Telegram Desktop gets confused when you launch the stretch version after launching the buster one (you just have to login/2fa again).


I chose sailfish for all three positions on the online tool and all space to linux, zero for Android and the Gemini boots to sailfish, runs sailfish and there’s no Android there spoiling the party.
Adam Boardman
If you could do a 'sudo lvscan' to tell me the volume names that would be handy.
bled82
CIFS/SMB/NFS support I was unable to map widnows network share and my search indicated that the kernel modules don't support it ? Looking to map windows shares over network or vpn , I use zerotier one its really a nice vpn mesh network solution and quick .
Adam Boardman
QUOTE(bled82 @ Feb 22 2019, 07:15 PM) *
CIFS/SMB/NFS support

Can you perhaps list the modules you want added? Preferably after testing that the kernel boots & works. You can build a kernel on the device by pulling down https://github.com/gemian/gemini-linux-kernel-3.18.git and checking out the native branch, a 'debuild -b -uc -us' will give you a .deb to install, but you might find it easier to just selectively copy the relevant lines from: debian/rules to make a new .img file.
You'll want to add your modules to: arch/arm64/configs/aeon6797_6m_n_halium_defconfig
mithrandir
Adam, maybe it is worth taking a look at my kernel configuration at: https://www.mygnu.de/2019/02/modular-linux-...-lid-close-fix/. Well, the kernel boots and includes most useful modules and some other stuff. Some documentation on the config changes can be found in the older kernel posts there. Might make sense to use this config or something similar for the main kernel.

Btw.: Thx for the cut+paste fix.This greatly increases usability of the Gemini. Great job. Never thought it is a kernel issue. Thought it might have been some problem with my keyboard config...

Mith
Adam Boardman
I did try experimenting with building as modules based upon your blog (old version of that granted, actually very old I've clearly not been paying much attention to your kernel config work), but couldn't get it to work. Tested patches welcome, if you get a working kernel from a debuild on debian stretch (use native or packaging branch depending on arm64 vs amd64 host).
mithrandir
QUOTE(Adam Boardman @ Feb 23 2019, 06:35 AM) *
I did try experimenting with building as modules based upon your blog (old version of that granted, actually very old I've clearly not been paying much attention to your kernel config work), but couldn't get it to work. Tested patches welcome, if you get a working kernel from a debuild on debian stretch (use native or packaging branch depending on arm64 vs amd64 host).

I'll give it a try using the debuild aproach. My build machine for the Gemini kernels usually is a jetson board running Ubuntu 16.04. This should be ok for the debuild aproach. Right? Don' t have a powerful enough machine running Stretch... Otherwise I had to install a VM on my Laptop...

How does the kernel deb package distinguish which boot partition to flash? Have not tried any of the kernel debs on the Gemini, yet. Just want to make sure not to flash the wrong partition while testing (using the 1st boot partition for Debian).

Mith
Adam Boardman
I'd recommend you add a lxd/lxc Debian 9 container (thats how I test my kernel builds using the packaging branch), the build server does it though jenkins arm on amd building from the native branch as whilst I got the packaging branch building there I couldn't get it to put the right arch in the package in the right place.

I don't remember whether it was a build problem or a boot problem with the modules version but I remember getting stuck and deciding it wasn't important enough for me to be bothered with trying to figure it out.

If you've got the latest bootloader then we know which button you pressed to boot so we display the correct 'dd' line to install the kernel, if not then you get a more generic message telling you to select the right partition yourself.

The idea is once we've got some good feedback on the suggestion being right we might swap the kernel package to actually do the 'dd' itself, for now kernel updates are manual so you needn't worry about it writing to the wrong place.
mithrandir
Do I get you right, that if I build on amd64 I have to fork from the packaging branch and if I build on arm64 I have to fork from master?
Adam Boardman
Yea the names are confusing, master is the generic branch just has the fixes so is for use by others eg sailfish (though they appear to have a mer branch too now), 'packaging' was my first debian-ized version using stretch cross compiler (gcc-aarch64-linux-gnu), when I got stuck getting that into the jenkins build system I made the 'native' branch which uses the slow qemu building so is the same as if you were building natively on the gemini ie arm64. I still use it locally though so fixes have to be applied to all three branches in the end.

So for 'debuild -b -uc -us' use branches as per:
amd64 - packaging
arm64 - native
Kiriririn
QUOTE(TheKit @ Jan 30 2019, 07:04 PM) *
QUOTE(Kiriririn @ Jan 30 2019, 02:33 PM) *
QUOTE(Eric BF @ Jan 30 2019, 11:41 AM) *

How do you disable Glamor? I would like to try. Thanks.

I believe I rebuilt xf86-video-hwcomposer without --enable-glamor-hybris, cant remember if there was more to it than that

It can be disabled by setting Option "AccelMethod" "None" in the device section of /etc/X11/xorg.conf, for example:
QUOTE
Section "Device"
Identifier "MediaTek HWC"
Driver "hwcomposer"
Option "AccelMethod" "None"
EndSection

If you update to latest libhybris and xf86-video-hwcomposer from Gemian repos, chromium will still work, but with color channels flipped. Might be interesting to compare performance though. If it is really much better without glamor, we could look into dri3 support without glamor, which would allow EGL applications to still work, although a bit slower due to buffer copy involved.


An update on this: I've updated everything and reverted all packages (except for repowerd and gemian-lock) to unmodified versions - unfortunately it's still slow with glamor enabled. The effect is most noticeable in Firefox which literally goes from 15-30 fps to < 1 fps, but you can also feel the difference scrolling in terminals and other apps. I will say it is improved though compared to when I last tried

But thank you for that AccelMethod config tweak, saves me maintaining a modified xserver-xorg-video-hwcomposer package!
idc
QUOTE(Adam Boardman @ Feb 19 2019, 09:52 PM) *
If you could do a 'sudo lvscan' to tell me the volume names that would be handy.


Hi Adam,
Sorry for the delay getting back to you.
The result of # lvscan from my sailfishOS gemini is as follows:
/dev/mmcblk0rpmb: read failed after 0 of 4096 at 0: Input/output error
ACTIVE '/dev/sailfish/root' [2.44 GiB] inherit
ACTIVE '/dev/sailfish/home' [37.00 GiB] inherit

A df shows that I'm using 60% of the root, but only 3% of home, so I should be able to shrink that and give Debian 20 GiB or so to play with. That should be enough, given I've an SD card which could be pressed into service for extra storage.
I hope that helps. Are there other commands you'd like me to run?

I love the idea of trying out shrinking the Sailfish volumes and creating a Debian that can run. Happy to be a guinea pig, if you don't mind the fact that I'm an amateur not a professional and may need some hand-holding, if we start doing complicated stuff! (So I'd welcome recommendations for what commands to use from Sailfish—or Android—to backup the whole thing before I start, and then what commands to use from SailfishOS or Android to shrink the /dev/sailfish/home folder.)

I'm keen to try out Exagear's Eltech's Exagear desktop to run some Intel-only programmes and according to the manual it requires Debian, which if I've understood correctly precludes Sailfish, if it is based on Redhat Linux — I've not had much to do with non-Debian based Linuxes so a bit hazy as to the main differences beyond the fact that I can't apt-get stuff but have to pkcon.

Thanks again for all your work on all this.
All the best,
Ian
Adam Boardman
Cool, thanks, currently thinking of a plan that would involve dd'ing a new boot image to one of your bootX spots, that will look for an MMC card with a stretch.img.gz and a stretch.config.txt file on it. The config would say what space to allocate, and do the resize, copy, etc. Will send you link when we have something to test.
idc
Thanks, Adam. That sounds fantastic. I'll wait to hear more in due course!
(Currently I have Sailfish in boot 1, and Android in the 'hold esc and silver button' boot position—is that 3 or 4? In any case, that leaves space for Debian in the 'boot with silver button' position.)
This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please click here.
Invision Power Board © 2001-2019 Invision Power Services, Inc.