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 - gabs5807

Pages: 1 2 [3]
31
Gemini PDA - Linux / [GUIDE] HowTo to install Gemian beside SailfishOS
« on: August 26, 2019, 10:32:26 am »
Hello,
here a quick HowTo to install gemian beside a licensed SailfishOS on the PDA.

I use a Scatter file from planet partitioning tool with following settings:

First: SailfishOS
Second: recovery
Third: empty (it seems, that there also is the sailfishos_boot.img flushed like at First)
Fourth: TWRP

After downloading all files from Planet and Jolly i modified the content of the .../etc/sysconfig/init from the ramdisk on the sailfishos_boot.img:
Code: [Select]
# Common settings for normal and recovery init.

# Amount of space to keep unallocated for refilling root or home later on.
LVM_RESERVED_MB=20480

# Default size for root LV
LVM_ROOT_SIZE=4096

Then i rebuild the ramdisk and the sailfishos_boot.img.
After installation there is 20G free space on the sailfish LVM.

On SailfishOS i create a new logical volume named gemian on the free space:
Code: [Select]
lvcreate -v -ay -Ay -l 100%FREE -n gemian sailfish
Next i extracted the latest linux-boot-lvm-stretch.img and gemian-stretch.img.xz from Adam Boardman (see the thread Final call for TP3) many thanks to Adam.
Code: [Select]
xzcat gemian-stretch.img.xz | dd of=/dev/sailfish/gemian bs=1024k
dd if linux-boot-lvm-gemian.img of=/dev/disk/by-partlabel/boot2 bs=1024k # 1)
And expand the filesystem on /dev/sailfish/gemian
Code: [Select]
e2fsck -f /dev/mapper/sailfish-gemian
fsadm resize /dev/sailfish/gemian

Then reboot the PDA using the silver Button to the installed system.

1) It should also be possible to change the filename at boot2 from sailfishos_boot.img to linux-boot-lvm-gemian.img at the Scatter file,
then it should be not necessary to write the stretch boot image on SailfishOS to /dev/disk/by-partlabel/boot2.

Many thanks to all who make this possible  

Gabriel

32
Hello,
i updated my Debian 9 to Debian 10 (buster).
Now the Linux Flash Tool did not work anymore  .
I also tried it on a new installation.
The PDA is detected, but readback or flush did not work.
The error is:
Code: [Select]
ERROR : STATUS_PROTOCOL_ERR (-1073676283) , MSP ERROE CODE : 0x00.
[HINT]:
Then i tried to compile it by myself, but compiling also did not work:
Code: [Select]
$ make HOST=linux BUILD_TYPE=release
make BUILD_TYPE=release HOST=linux LOG=off  2>&1 | tee build_log.txt
..
g++ -c -m64 -pipe -O2 -Wall -W -D_REENTRANT -fPIC -DQT_NO_CAST_FROM_CAST -D_LINUX -DQT_NO_DEBUG -DQT_WEBKIT_LIB -DQT_GUI_LIB -DQT_XMLPATTERNS_LIB -DQT_NETWORK_LIB -DQT_CORE_LIB -I../../../SP-Flash-Tool-src-master -I. -isystem /usr/include/x86_64-linux-gnu/qt5 -isystem /usr/include/x86_64-linux-gnu/qt5/QtWebKit -isystem /usr/include/x86_64-linux-gnu/qt5/QtGui -isystem /usr/include/x86_64-linux-gnu/qt5/QtXmlPatterns -isystem /usr/include/x86_64-linux-gnu/qt5/QtNetwork -isystem /usr/include/x86_64-linux-gnu/qt5/QtCore -I. -isystem /usr/include/libdrm -I/usr/lib/x86_64-linux-gnu/qt5/mkspecs/linux-g++-64 -o AppCore.o ../../../SP-Flash-Tool-src-master/Public/AppCore.cpp
In file included from ../../../SP-Flash-Tool-src-master/Public/AppCore.h:16,
                 from ../../../SP-Flash-Tool-src-master/Public/AppCore.cpp:8:
../../../SP-Flash-Tool-src-master/Public/../Utility/Utils.h: In function ?€˜void Utils::SetTextCodec()?€™:
../../../SP-Flash-Tool-src-master/Public/../Utility/Utils.h:114:17: error: ?€˜setCodecForTr?€™ is not a member of ?€˜QTextCodec?€™
     QTextCodec::setCodecForTr(coder);
                 ^~~~~~~~~~~~~
../../../SP-Flash-Tool-src-master/Public/../Utility/Utils.h:116:17: error: ?€˜setCodecForCStrings?€™ is not a member of ?€˜QTextCodec?€™
     QTextCodec::setCodecForCStrings(coder);
                 ^~~~~~~~~~~~~~~~~~~
../../../SP-Flash-Tool-src-master/Public/AppCore.cpp: In member function ?€˜bool AppCore::IsSecuLoaded(APKey)?€™:
../../../SP-Flash-Tool-src-master/Public/AppCore.cpp:135:26: warning: catching polymorphic type ?€˜class BromException?€™ by value [-Wcatch-value=]
     }catch(BromException e){
                          ^
../../../SP-Flash-Tool-src-master/Public/AppCore.cpp: In member function ?€˜bool AppCore::IsAuthLoaded(APKey)?€™:
../../../SP-Flash-Tool-src-master/Public/AppCore.cpp:152:26: warning: catching polymorphic type ?€˜class BromException?€™ by value [-Wcatch-value=]
     }catch(BromException e){
                          ^
../../../SP-Flash-Tool-src-master/Public/AppCore.cpp: In member function ?€˜int AppCore::CheckSecUnlock(APKey, int)?€™:
../../../SP-Flash-Tool-src-master/Public/AppCore.cpp:169:26: warning: catching polymorphic type ?€˜class BromException?€™ by value [-Wcatch-value=]
     }catch(BromException e)
                          ^
../../../SP-Flash-Tool-src-master/Public/AppCore.cpp: In member function ?€˜bool AppCore::GetScatterVersion(APKey, char*)?€™:
../../../SP-Flash-Tool-src-master/Public/AppCore.cpp:187:26: warning: catching polymorphic type ?€˜class BromException?€™ by value [-Wcatch-value=]
     }catch(BromException e)
                          ^
make[2]: *** [Makefile:2437: AppCore.o] Fehler 1
make[2]: Verzeichnis ?€ž/home/gabs/Software/Gemini/_Output/linux/release?€œ wird verlassen
make[1]: *** [Build/build-linux.mk:54: all] Fehler 2
make[1]: Verzeichnis ?€ž/home/gabs/Software/Gemini/SP-Flash-Tool-src-master?€œ wird verlassen
$

The planet support give me the following answer:
...
Unfortunately, we do not provide support for the flash tool with Linux. Linux tends to fail 9/10 times when tried to flash our devices with it. This is due to Linux often lacking libraries or settings necessary for the flash tool work, combined with a general lack of understandable diagnostics and issue reports to the user.

The quickest fix here would be to use an available Windows (ideally windows 7) machine. You can also use a virtual machine running Windows 7 through Debian.
...

I did not have any Windows on my computers (and don't think to buy one ;-)).
So did anyone solved this problem?
Or did i miss some files/packages on my system?

Many thanks

Gabriel

33
Quote from: flotsam
I have been struggling, without success, to get dual-boot Sailfish/Android working. This is using the new partition tool and firmware, doing a full flash ("firmware upgrade").

What I do is:
  • Flash the device
  • Boot into Sailfish. Everything works fine. Can reboot (to sailfish) without problems.
  • Boot into Android. All goes well.
  • Boot back to sailfish. Device is now broken.
The symptoms of the problem are:
  • The wireless interface gets a new pseudo-random MAC address. This happens on every reboot, with both Android and Sailfish.
  • The wifi scanning in sailfish returns a bogus network named "NVRAM Warning: Err=0x10". While harmless enough, this seems to indicate some error.
  • Sailfish fails to recall any WiFi networks that I have connected to before. So it is necessary to reenter passwords, etc. This makes the device pretty much worthless.
The only fix that I have found is to do a full reflash of the device. I have tried various combinations (including some unsupported ones) of Android+Sailfish. I have not tried other OS combinations, so I don't know if any of them also have issues.

So is it just my device, or has someone else encountered this issue? Even better would be if someone has found a fix.

[Edited to add]: See also this thread. It appears that I'm not the only one with the problem, and that it is not specific to sailfish. Does someone from Planet Computers want to help?

[Edited to change topic title]
The problem also occurs on single boot (no Android - only SailfishOS).
I installed SailfishOS from Jolla version 3.1.0.11 from scratch and the Problem is still here :-(.
But there is no '/nvdata/APCFG/APRDEB/WIFI'. The /nv* directory(s) only contains:

# ls -l /nv*
/nvcfg:
total 0

/nvdata:
total 12
drwxrwx--- 2 root  system 4096 Jul 13 12:32 md
drwxrwx--- 2 root  system 4096 Jul 13 12:32 md3
drwxrwx--x 2 media audio  4096 Jul 13 12:32 media


No WIFI file on any subdirectory :-(.

Edit: 2019-08-23:
When installing SailfishX Version 3.0.3.10 first and upgrade to 3.1.0.11 the problem did not occur.
Seems a configuration (or database) problem.

34
Gemini PDA - Linux / Final call for TP3
« on: March 18, 2019, 01:08:55 pm »
Quote from: idc
Quote from: Adam Boardman
<snip> I could write either of these up in more detail if needed. Its also occurred to me that you don't need to name the new LV in the config file as that is set from the cmdline inside the boot image which was one of the issues I had before where the config was making a different LV to the one the boot image was going to try to boot.

gabs5807 - given your current selection of boots (your using all of them) you'll have to sacrifice one, I'd probably drop TWRP to start with myself... but whatever you use the least.
</snip>

Hi Adam,
My new sd card is now arrived. And I realised (thanks to your mention) that I can of course use a USB stick to hold the files. The offer of a more detailed write up—a bit more hand-holding— would therefore be of great help to me. (I haven't messed with LVM partitions before) I have sailfish on boot 1 (i.e. default), and Android at the last boot (holding esc and silver button together). Ideally, I would like to avoid having to reinstall the Android.
Available, then, I have 40GB devoted to 'Linux' (i.e. Sailfish at present—I'm sure this could be reduced to 16GB or less, leaving 24GB to Debian); and 16 GB to Android. I have 128GB sd card (currently in vfat or xfat—still in its packet—what's the best way to format this to make it available to Debian). And I've a 16GB USB stick, which sounds like the way to get the bemoan-config.txt and .img onto the whole thing.
For the initial step, of resizing the Sailfish partition, I presume I need to be in something other than Sailfish—so presumably, as I only have SFOS and Android on my gemini as yet, that has to be done when I'm booted into Android, is that right? So I presumably need to install some sort of terminal? Or is there another route ...?
Gabriel, did you manage to find time this weekend? How did it go?
Looking forward to trying it out.
All the best,
Ian

@idc: Hello Ian, sorry i'm not able to test it  .
My wife use the PDA for some work and she was on the run during this weekend    .
I hope i can manage it soon.

By the way, i see that jolla is releasing the next version soon (see tjc   ).

Best regards

Gabriel

35
Gemini PDA - Linux / Final call for TP3
« on: March 10, 2019, 02:32:20 pm »
Quote from: Adam Boardman
A first bash at an (untested) LVM install.

You'll need an SD card with a ext4 partition containing: You may omit NEW_LV_SIZE from the config to allow the new volume to take the remaining space after the home partition is reduced in size. Though having both smaller and then online growing whichever happens to need extra space first might be a nice way to use the system.

You'll need to flash/dd a new boot image:The boot image only attempts an install if it fails to find the volume to mount, so no need to flash a different kernel if it works, reboots should take you back to the installed system.

Note: I've not tried this out, so only guinea pigs who are happy to go back to the flashing station should try it out... You may also like to pre-review the scripts geminipda

Hello Adam,
may thanks for files. I hope i can install it next weekend.
About the linux-boot-lvm-stretch.img, which boot (boot, boot2, or boot3) device i have to use for dd?
I created a Gemini_x27_A4GB_L52GB_Multi_Boot.txt with 'default boot' SailfishX, (second is recovery) and third is TWRP recovery and fourth is Android.

I think i can scaling down the SailfishX about 10GB.
If i'm able to set the German keyboard on SailfishX and debian without booting Android (last time i didn't work :-(), i also will delete the Android partition ;-).

36
Gemini PDA - Linux / Final call for TP3
« on: March 07, 2019, 03:09:52 pm »
Quote from: 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.

Hello Adam,
using an own boot partition on the Sailfish LVM would also allow to use the same /home (if somebody wish)   .
Sailfish use the user nemo with following IDs (i take it from my FP2 not from an original SailfishX, but it should be the same - may be @idc could check this?):

$ id
uid=100000(nemo) gid=100000(nemo) groups=39(video),100(users),990(ssu),991(timed),995(oneshot),1000(system),1002(b
uetooth),1003(graphics),1004(input),1005(audio),1006(camera),1013(media),1023(me
ia_rw),1024(mtp),100000(nemo)
$ id

Using the same /home would allow access the SailfishX nemo account from debian and vice versa with out splitting up the /home partition in two separate partitions.
May be some security reasons speak again this approach, but if the PDA is used as a single user system it should work (and if someone will split access rights it is possible to use an other id for the gemini account on the debian system).
Using the same ID for nemo and gemini require a symlink on home from /home/gemini (or an other account if required) to /home/nemo.

Only my thought - should be discussed   ..

37
Gemini PDA - Linux / Final call for TP3
« on: March 05, 2019, 03:07:26 pm »
Hello Adam,
many thanks for the debian stuff. I'm also using a trible boot (debian, Sailfish and Android - only 4GB for that ;-)).
And so i'm also very interested in a solution which allow me to boot debian and Sailfish. So you can also count on me for testing proposes.
At the moment i did not update to the licenced Sailfish because of losing debian :-( which i did not want.
So if you have something please let me know. May be i cannot install it right now (i first have to order a Sailfish licence but i will order it if a solution is available).

Again many thanks

Gabriel

Btw. i think at tjc (together.jolla.com) you can also find some information about the Sailfish lvm configuration - and many more ..

Quote from: 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.

38
Gemini PDA - Sailfish OS / SailfishOS 3.0.1.11 released by Jolla
« on: January 12, 2019, 07:35:15 am »
Hallo,
today i read at https://together.jolla.com/question/186471/...anet-computers/ that the SailfishOS Version 3.0.1.11 is released by Jolla (older versions came from Community).

At the link above there is a detailed description howto install it.
Third party licensed Software is not included, but landscape mode should work out of the box  .
 
I installed it per ssh and after having a short look on it everything worked fine  .

39
Gemini PDA - Sailfish OS / Dosbox
« on: November 27, 2018, 09:40:34 am »
Quote from: arisel
Quote from: gabs5807
When i have a full map i can upload it (if some one is interested   ).

I am.

OK. Here it is. But i did not find any information about the names and used by key.map file :-(.
Not at the internet nor at the dosbox source ..
So some of the keys could not described at the map.

I added the modifier key:
  • mod1 -> key_lctrl
  • mod2 -> key_lalt
  • mod3 -> key_fn
I did not know weather it is possible to add key_lshift and key_rshift as additional modifier (mod4) so i comment all keys which need shift.
May be this keys must be described otherwise.

Same problem for '?' which has an unusual position for German keyboards on the gemini keyboard.
Normally it is a shifted 'sz' but i did not find a key name for the 'sz' or the '?' key ..

I attached the created map and a picture of the German gemini keyboard.

Any comment and corrections are welcome :-).

40
Gemini PDA - Sailfish OS / Dosbox
« on: November 19, 2018, 03:26:50 pm »
Quote from: vader
So I compiled up the version that prints out the key codes. To use it, uncompress the attached dosbox executable and put it in /tmp. Make sure it is executable, then run it redirecting output to a file. Press keys in dosbox, then quit. look at the file. It is really rudimentary, however it does the job (until I write the nice gui wrapper).

Enjoy.

Many thanks.
I have the list of the key codes.
Is there a list of the key names for all keys (e.g. key_q, ..)?
For some keys i did not find the key names (the German Umlaute Ä, Ö, Ü, and funnily enough '$', '§', ..  .

When i have a full map i can upload it (if some one is interested   ).

41
Gemini PDA - Sailfish OS / Dosbox
« on: November 15, 2018, 08:06:25 am »
Quote from: vader
The normal keymapper doesn't work properly as it was hard coded for portrait orientation. I was going to rewrite it but haven't yet. Ideally, the qml front end will take care of that. To work out the keys, I actually added print statements to the program  They have been removed now. I could always compile up a version for you that printed the key presses and you could run that one to map your keyboard. I added the fn key as alt3 so you can get the extra characters.

Have you enabled dynamic? Auto normally chooses the dynamic cpu, however some games don't - one example is elder scrolls. It was slow until I set the cpu core to always use dynamic in the config file. With dynamic, you can run duke3d at full speed, along with all the doom/doom2 games (eg dark forces). Quake needs a few small tweaks, but after that it runs well.

Let me know if you want the dosbox version with printout so you can configure your keyboard.

Yes  . It would be fine to get this version.
At the moment i tried low performance games like Agentman and Commander Keen  .

But some more modern games (like Space Quest and Monkey Island )  are waiting to be played.
At this point i also have to look on the cpu speed.
And the i have to use the keyboard (especially on the first adventures) ..

Many thanks

42
Gemini PDA - Sailfish OS / Dosbox
« on: November 14, 2018, 01:54:07 pm »
Quote from: vader
Quote from: gabs5807
trying to install latest Dosbox version 0.4_1 to my Gemini PDA with Sailfish version 3.0.0.5 (devel version), i got an error about missing libaudioresource.so.1.
Did i missed something that must be installed additionally, or is this a change during upgrade from Sailfish version 2.1.x.x to 3.0.x.x?

I haven't upgraded to 3 yet, but you need libaudioresource. You can manually add the package from the command line. Make sure you are root by running devel-su first (or put devel-su before each command).

Code: [Select]
pkcon search libaudioresource
look for the package (not the qt version), so for example in my system you have

libaudioresource-1.0.5-1.1.1.armv7hl

You would then type:

Code: [Select]
pkcon install libaudioresource-1.0.5
This is normally done in the rpm file, so maybe there is something different. If you successfully installed libaudioresource, do the following:

Code: [Select]
ldd /usr/bin/dosbox | less
This will show what libraries it is trying to load, and if any are missing.

Hello vader, many thanks for the hint. Now it works fine (i tryied some old dos games ;-)).
The only problem i have is the wrong mapping of my german keyboard.
The key mapping file i use on my Linux did not work correctly.
Do you know if there is a tool which shows the code of the pressed key?

Many thanks

43
Gemini PDA - Sailfish OS / Dosbox
« on: November 11, 2018, 06:11:35 am »
Quote from: vader
OK, here is the latest version. It runs significantly faster than the old one. If you have installed version 0.3, the easiest thing is to rename your ~/dos and ~/.dosbox to ~/dos.good and ~/.dosbox.good, then create dummy .dosbox and dos directories. Uninstall the old dosbox, then install the new one. Delete the new .dosbox and dos directories, and rename your .good directories back to .dosbox and dos. As usual, gunzip the rpm first

Hello vader,
trying to install latest Dosbox version 0.4_1 to my Gemini PDA with Sailfish version 3.0.0.5 (devel version), i got an error about missing libaudioresource.so.1.
Did i missed something that must be installed additionally, or is this a change during upgrade from Sailfish version 2.1.x.x to 3.0.x.x?
There are also no other versions of this lib on the system  ..
Many thanks for any hint ..

Gabriel

Pages: 1 2 [3]