View Full Version : Maemo-Leste pre-alpha announcement
Hi,
We're happy to let you know about the pre-alpha release of "Maemo Leste" - an attempt to port/run large parts/bits from Fremantle on the latest stable Devuan/Debian.
There are currently SD-card images of the pre-alpha version available for the N900, you can find them on our (temporary?) website: https://maemo-leste.github.io/pages/n900-status.html
You will need u-boot (bootmenu) from Pali: http://talk.maemo.org/showthread.php?t=81613
We also wrote our first "status update": https://maemo-leste.github.io/maemo-leste-standing-on-the-shoulders-of-giants.html - which also talks about other devices that are partially supported and could perhaps be used for development as well. Please check out this news post to see what the current status is.
https://maemo-leste.github.io/
The software is not ready for end users -- but we could REALLY use more developers! So if you're interested, but not sure how you could help out, please post here, or talk to us on #maemo or #maemo-leste on Freenode. Or file an issue on Github: https://github.com/maemo-leste/bugtracker/
Here are some additional photos and screenshot:
https://maemo-leste.github.io/images/maemo-leste-ascii-h-d-n900-3.jpg
https://maemo-leste.github.io/images/maemo-leste-ascii-h-d-n900-4.jpg
Wow great work I will try the image in the next days. What kind of sdk or toolchain you suggesting to use for development?
Which qt version will be possible 4.7 from maemo or the newer from devuan.
Thanks for releasing this alpha.
Wow. Porting Hildon to a newer Debian release. Way to go guys.
I guess I found a way to re use the N900 once again. I will test it. Thank you very much for your support and your hard work!!!!
chenliangchen
2018-02-04, 15:37
This is the most exciting info I learned recently! The most!!
Wow great work I will try the image in the next days. What kind of sdk or toolchain you suggesting to use for development?
Which qt version will be possible 4.7 from maemo or the newer from devuan.
Thanks for releasing this alpha.
Regarding an SDK, we usually just build natively on the arch we like to work on (amd64 for freemangordon, I usually work on armhf since my laptop in armhf)
Our Jenkins CI doesn't use qemu to build, I have an arm64 machine that we use for armel and armhf builds, an amd64 is done natively on the jenkins server.
We will have to take the cssu Qt build and see if we just build that, or go with the one from Debian/Devuan. See this issue: https://github.com/maemo-leste/bugtracker/issues/53
Yay I got i booting through the flasher.
As freemangordon pointed out that zImage is needed for booting through the flasher and Wizzup gave the hint to read out the zImage from an uImage I got it running.
So take the uImage from the smaller partition of the sd card.
convert:
tail -c+65 < uImage > zImage
boot:
flasher-3.5 -l -k zImage -b
or
0xFFFF -m kernel:zImage -l -b
We will have to take the cssu Qt build and see if we just build that, or go with the one from Debian/Devuan. See this issue: https://github.com/maemo-leste/bugtracker/issues/53
It would be nice if they could co exists and maybe later porting qt-maemo stuff to qt5?
Yeah not all applications using gtk:).
Android_808
2018-02-04, 23:03
Do you have a virtual box image? Could be worthwhile to let people try it out or just have instructions to get people started.
One area that might need a little cosmetic work is osso-xterm settings. From when I played with it last the settings doesn't match the style of other apps. It's a bit cluttered.
Do you have a virtual box image? Could be worthwhile to let people try it out or just have instructions to get people started.
One area that might need a little cosmetic work is osso-xterm settings. From when I played with it last the settings doesn't match the style of other apps. It's a bit cluttered.
Not yet, but we should have one pretty soon: https://github.com/maemo-leste/bugtracker/issues/45
The software is not ready for end users -- but we could REALLY use more developers! So if you're interested, but not sure how you could help out, please post here
Hi Wizzup_
For sometime I've been working of my own mobile OS, initially with Debian on the N900 (https://github.com/dderby/debian900/) but more recently I've been reworking these scripts (not yet public) to run with Devuan and to separate out device specific config to make them multi-device, initially with support the N900 and Droid 4, and support for N950 and N9 coming shortly after. Unfortunately in the last few months I've been too busy with work and haven't had enough time to complete them. My general idea was to make them as generic as possible in order to produce basic image builds for a variety of devices by just specifying a defconfig and dts already present in mainline Linux. The idea behind this was that by having basic images for a variety of devices, even if untested, it might encourage new developers to try them and start contributing further hardware adaptations (bootloader config and mainline Linux). I've been tracking devices with mainline support here (https://talk.maemo.org/showthread.php?t=99357) and keeping it up to date, although I still need to check if anything interesting has gone in since the merge window opened for Linux 4.16.
I've known about Maemo Leste for while now and I've been meaning to contact you. I don't know if my scripts would be useful to you. I haven't yet looked into how your builds are produced but it shouldn't require much effort to adapt my scripts to produce Maemo Leste builds should you be interested.
By any means, you can count on me to help out with Maemo Leste. I certainly would like to contribute to it. I have my own ideas about how a free mobile operating system should be produced and Maemo Leste is the first effort I've seen that aligns with most of them. Given my limited free time, it makes sense to join forces rather than continue with my one man effort. I could probably help with producing images for N950 and N9 which have seen significant progress recently in mainline (although I don't yet have an N9 for testing).
I'll try to reach out to you on Freenode sometime this week to discuss how I might be able to contribute. Otherwise, feel free to respond in this thread or by PM.
ynzinier
2018-02-05, 19:24
I've been thinking recently about how original N900 is, well, not so great because of bugs and lack of RAM. The alternative is to create new hardware (I know about Neo900...) and reducing bugs.
How far from here or fully ported maemo is to make it independent from omap architecture?
I would love to contribute but I don't know much about programming in Linux :(
freemangordon
2018-02-05, 20:14
@wicket - We'll definitely appreciate your help, there are tasks that need more thinking than coding (fixing the spaghetti fremantle boot process is for example), so even if you lack time to do programming, your experience will help a lot.
Not sure what your vision about free mobile linux is, however what we aim is a device independent distro, to the extent that's possible given that usually each device needs it's own kernel. Though that seems to change with DT. And by device independent, we don't only aim ARM world - actually most of the development so far was done in amd64 VM that boots to hildon-desktop in exactly the same way n900 or allwinner does.
Having such a base we can strip lots of fat, in terms of scratchbox for example.
Wizzup can elaborate on the the build system (jenkins) , but I think it is more or less functional and stable.
So, please join ##fptf-private, at least to see how is the cooperation going on :) .
Android_808
2018-02-05, 21:55
In terms of getting a Virtualbox/VMWare image running, would I just do a minimal Devuan install and then add a custom repo to pull the packages or are they still only in git?
I've been thinking recently about how original N900 is, well, not so great because of bugs and lack of RAM. The alternative is to create new hardware (I know about Neo900...) and reducing bugs.
How far from here or fully ported maemo is to make it independent from omap architecture?
I would love to contribute but I don't know much about programming in Linux :(
The actual packages also work on Allwinner ARM devices (apart from some device specific features in mce, but those can be ported/fixed), so we are already not necessarily dependent on omap.
In terms of getting a Virtualbox/VMWare image running, would I just do a minimal Devuan install and then add a custom repo to pull the packages or are they still only in git?
Add the testing key from here: http://maedevu.maemo.org/
And then add the 'kawai' repo (we will soon rename that to leste again, we initially aimed for jessie with leste, and used kawai as temporary name for stretch/ascii, but now it's confusing).
Then install hildon-meta, but make sure that apt doesn't start services while installing (RUNLEVEL=1 apt-get install hildon-meta)
I think Parazyd is working on Vbox images, not sure how far he is, I think he is pretty close, he already has something that generates images for Devuan, so he just needs to add the Maemo Leste script(s).
Hi Wizzup_
For sometime I've been working of my own mobile OS, initially with Debian on the N900 (https://github.com/dderby/debian900/) but more recently I've been reworking these scripts (not yet public) to run with Devuan and to separate out device specific config to make them multi-device, initially with support the N900 and Droid 4, and support for N950 and N9 coming shortly after. Unfortunately in the last few months I've been too busy with work and haven't had enough time to complete them. My general idea was to make them as generic as possible in order to produce basic image builds for a variety of devices by just specifying a defconfig and dts already present in mainline Linux. The idea behind this was that by having basic images for a variety of devices, even if untested, it might encourage new developers to try them and start contributing further hardware adaptations (bootloader config and mainline Linux). I've been tracking devices with mainline support here (https://talk.maemo.org/showthread.php?t=99357) and keeping it up to date, although I still need to check if anything interesting has gone in since the merge window opened for Linux 4.16.
I've known about Maemo Leste for while now and I've been meaning to contact you. I don't know if my scripts would be useful to you. I haven't yet looked into how your builds are produced but it shouldn't require much effort to adapt my scripts to produce Maemo Leste builds should you be interested.
By any means, you can count on me to help out with Maemo Leste. I certainly would like to contribute to it. I have my own ideas about how a free mobile operating system should be produced and Maemo Leste is the first effort I've seen that aligns with most of them. Given my limited free time, it makes sense to join forces rather than continue with my one man effort. I could probably help with producing images for N950 and N9 which have seen significant progress recently in mainline (although I don't yet have an N9 for testing).
I'll try to reach out to you on Freenode sometime this week to discuss how I might be able to contribute. Otherwise, feel free to respond in this thread or by PM.
Cool, nice list of devices with mainline support, we could try to extend our support for some of those devices given time and demand. Freemangordon has hildon-desktop, mce, dsme and all the other things on an Allwinner A33 tablet - similar to Q8 tablets I think.
Parazyd is doing the actual image building (also for Devuan, he's a devuan dev), and I've worked with him in setting up the Jenkins (auto)building and repository generation. It would be useful to see your scripts and see if/how we can use them to extend our builds.
Would love to join forces. I don't have either a N9 or N950, so that'd be a great addition. I'm "Wizzup" on Freenode, but we're also in #maemo-leste and ##fptf-private - our dev channel (might move all of it to #maemo-leste or #maemo at some point, just takes time to sort these things :))
Nice work! Would be great to see if you could work together with postmarketOS as well as they are moving in the same direction, and have a large list of ported devices.
Also, will maemo-leste support the existing applications on the community repository?
Android_808
2018-02-05, 23:50
Running an updated kernel, glibc etc it would be interesting to see if there are any performance gains over Fremantle. Due to current graphics stack Todo items and lack of some components like the telephony stack a benchmark test wouldn't be fair to either variant.
I've know Dosbox was a lot faster after making use of some newer arm instructions (armv6 iirc).
Nice work! Would be great to see if you could work together with postmarketOS as well as they are moving in the same direction, and have a large list of ported devices.
Also, will maemo-leste support the existing applications on the community repository?
We've been collaborating on some points - they actively watch our bugtracker, and we watch theirs (to some degree :)). Personally, I think the goals might be different - from my pespective they seem to work on a lot of devices and offer a lot of choice, while our goal is "more simple" (in some sense), we want to offer the Maemo experience, first on the N900, and then on some other devices.
Additionally, I'm personally not satisfied with older vendor kernels, so I'd really want to push for a 'mainline only' (or very close to) policy. I believe postmarketOS is also pushing for this, but they (AFAIK, could be wrong) also ship various devices with Android kernels, I believe.
But others know more about pmOS. Both projects exist, and I think it's important that we collaborate. But don't expect Maemo Leste to switch to KDE plasma any time soon, so to say.
Virtual machine images are up (qemu and virtualbox). Also new N900 images (armhf and armel, armel is untested).
There are no changes on the N900 images, except that the repos now point to 'leste' and not 'kawai', since this rightfully confused some. ('kawai' is our name for testing, and no, it's not 'kawaii')
There's been some activity on the bugtracker, regarding gps, phone calls, and pulseaudio. I wonder what is the best way to coordinate between all interested parties. Maybe a mailing list?
http://maedevu.maemo.org/images/20180207/
Maybe someone can port and build 'extmou', so that cursors are visible in the virtual images: https://github.com/maemo-leste/bugtracker/issues/50
Is it possible to run these images on (high end) smartphones?
Is it possible to run these images on (high end) smartphones?
Sounds like the answer depends on: is that smartphone supported on mainline Linux ... So I guess quickest answer is No, at least not yet.
And of course the images provided are for specific devices, although you can build for other devices too
freemangordon
2018-02-07, 18:22
...
Maybe someone can port and build 'extmou', so that cursors are visible in the virtual images: https://github.com/maemo-leste/bugtracker/issues/50
This is not a good idea, extmou was an ugly hack I invented to overcome the way mouse cursor is hidden in fremantle (by using an empty cursor). if one wants cursor in the VM or on device, all she needs is to install (or link) to the appropriate cursor theme.
Android_808
2018-02-07, 18:22
With regards to extmou, would it be worth enumerating input devices in hildon-desktop and show/hide based on last input event?
freemangordon
2018-02-07, 18:24
With regards to extmou, would it be worth enumerating input devices in hildon-desktop and show/hide based on last input event?
Or better - enumerate input devices on such device added/removed and show the cursor if there is at least one device of type mouse.
EDIT: I think they did something similar in cordia, we can just reuse it.
EDIT2: this (https://github.com/Cordia/hildon-desktop/commit/df2dd4a9514504285f04f4a6a26e43440b7346f5)
Android_808
2018-02-07, 19:06
Yeah, that's the one. Not 100% sure it worked correctly on my Cordia based port or if it made it in to the Fremantle-GTK3 version.
Sounds like the answer depends on: is that smartphone supported on mainline Linux ... So I guess quickest answer is No, at least not yet.
And of course the images provided are for specific devices, although you can build for other devices too
but qemu is available for Android?
(Like Limbo https://limboemulator.weebly.com/)
but qemu is available for Android?
(Like Limbo https://limboemulator.weebly.com/)
Oh wow! That I wasn't aware of. Probably might work :-)
Oh wow! That I wasn't aware of. Probably might work :-)
The Limbo app has even settings for the N800 and the N810 :p
Edit: There are a lot of settings to choose from, couldn't get it to work :(
Is there also a Kernel and Initrd available?
Edit2: Ok got it to work using the amd64 build
I hope to see some arm builds will show up :)
Android_808
2018-02-08, 17:52
Has anyone had any luck getting Virtualbox Guest Additions to work?
After installing the GA's it just goes to black screen. With 3D acceleration enabled in machine settings for the VM it spews out VERR_BUFFER_OVERFLOW message in another VT, without its just black.
Edit: reverted to stock image. First boot fails to start X, second seems to work ok. Not going to try GA's yet.
endsormeans
2018-02-08, 19:36
The Limbo app has even settings for the N800 and the N810 :p
Edit: There are a lot of settings to choose from, couldn't get it to work :(
Is there also a Kernel and Initrd available?
Edit2: Ok got it to work using the amd64 build
I hope to see some arm builds will show up :)
Limbo....eh?
hm..
Wonder if this app is any relation at all to the programming language for Inferno os ...which also runs on the n8x0.
3rd step-cousin twice removed ?
@wicket - We'll definitely appreciate your help, there are tasks that need more thinking than coding (fixing the spaghetti fremantle boot process is for example), so even if you lack time to do programming, your experience will help a lot.
As you've probably already noticed, I've been adding comments to the GitHub issues where I feel I my input might be useful. The spaghetti Fremantle boot process might be interesting. I'll take a look at what Leste is currently doing to bring up Hildon and get back to you on that one.
Not sure what your vision about free mobile linux is, however what we aim is a device independent distro, to the extent that's possible given that usually each device needs it's own kernel. Though that seems to change with DT. And by device independent, we don't only aim ARM world - actually most of the development so far was done in amd64 VM that boots to hildon-desktop in exactly the same way n900 or allwinner does.
Having such a base we can strip lots of fat, in terms of scratchbox for example.
My vision of free mobile Linux is to start off with a solid base. By this I mean build off mainline Linux and build on top of an existing mainstream distro. When starting out small, it's the only sustainable way of keeping it up to date and to ensure that security fixes are delivered in a timely manner. Leste is the first mobile Linux to get this right. postmarketOS half got it right but it's more focused on being an after-market OS for Android devices where mainline Linux is a secondary goal.
I'm actually less concerned about the GUI. Hildon is obviously a welcome addition. We need a GUI anyway.
I wanted to create a device independent mobile Linux base, based the above ideas. My plan was to create a free version and a non-free version. The non-free version would be something somewhat similar to Leste and would include blobs needed to make it as functional as possible. The free version would obviously be less functional but in the case of the N900 for example, all that would be missing would be video acceleration, Wi-Fi and Bluetooth.
I think there is a need for a mobile OS that can be 100% vetted and this can only be done with free software. The US has virtually complete control all mobile operating systems and I'm surprised this sits well with most countries. I often wonder what kind of mobile phones are issued by non-US governments to their officials. It seems that only the Russians were smart enough to realise the problem. They funded some ex-Nokia employees to make a certain OS well known to this forum ;). Unfortunately they don't want to share all of it with the rest of the world and most ports are stuck with Android kernel forks.
You've seen my list of mainline Linux devices. My next list will be of SoCs used in modern phones which already have mainline support but no device support other than dev/evaluation boards. A lot of people are unaware how much work has already been done in mainline. Like I said in my previous post, I want too try to encourage contributions and it might help if more people knew they would not need to start from scratch.
That's the basis of my vision. I could elaborate more but that's a discussion for another day. :)
Wizzup can elaborate on the the build system (jenkins) , but I think it is more or less functional and stable.
I found the image-builder and jenkins-integration repos on GitHub so I'll see if I can figure it out.
So, please join ##fptf-private, at least to see how is the cooperation going on :) .
I've not had a chance to talk on Freenode yet, I can probably get on there tomorrow.
Cool, nice list of devices with mainline support, we could try to extend our support for some of those devices given time and demand. Freemangordon has hildon-desktop, mce, dsme and all the other things on an Allwinner A33 tablet - similar to Q8 tablets I think.
Parazyd is doing the actual image building (also for Devuan, he's a devuan dev), and I've worked with him in setting up the Jenkins (auto)building and repository generation. It would be useful to see your scripts and see if/how we can use them to extend our builds.
Would love to join forces. I don't have either a N9 or N950, so that'd be a great addition. I'm "Wizzup" on Freenode, but we're also in #maemo-leste and ##fptf-private - our dev channel (might move all of it to #maemo-leste or #maemo at some point, just takes time to sort these things :))
I'm looking forward to working together! Once I'm familiar with how your images are built, we can discuss what can be done to extend your builds. I think I covered the rest in my reply to freemangordon.
As you've probably already noticed, I've been adding comments to the GitHub issues where I feel I my input might be useful. The spaghetti Fremantle boot process might be interesting. I'll take a look at what Leste is currently doing to bring up Hildon and get back to you on that one.
My vision of free mobile Linux is to start off with a solid base. By this I mean build off mainline Linux and build on top of an existing mainstream distro. When starting out small, it's the only sustainable way of keeping it up to date and to ensure that security fixes are delivered in a timely manner. Leste is the first mobile Linux to get this right. postmarketOS half got it right but it's more focused on being an after-market OS for Android devices where mainline Linux is a secondary goal.
I'm actually less concerned about the GUI. Hildon is obviously a welcome addition. We need a GUI anyway.
I wanted to create a device independent mobile Linux base, based the above ideas. My plan was to create a free version and a non-free version. The non-free version would be something somewhat similar to Leste and would include blobs needed to make it as functional as possible. The free version would obviously be less functional but in the case of the N900 for example, all that would be missing would be video acceleration, Wi-Fi and Bluetooth.
I think there is a need for a mobile OS that can be 100% vetted and this can only be done with free software. The US has virtually complete control all mobile operating systems and I'm surprised this sits well with most countries. I often wonder what kind of mobile phones are issued by non-US governments to their officials. It seems that only the Russians were smart enough to realise the problem. They funded some ex-Nokia employees to make a certain OS well known to this forum ;). Unfortunately they don't want to share all of it with the rest of the world and most ports are stuck with Android kernel forks.
You've seen my list of mainline Linux devices. My next list will be of SoCs used in modern phones which already have mainline support but no device support other than dev/evaluation boards. A lot of people are unaware how much work has already been done in mainline. Like I said in my previous post, I want too try to encourage contributions and it might help if more people knew they would not need to start from scratch.
That's the basis of my vision. I could elaborate more but that's a discussion for another day. :)
So we can have a functional Maemo Leste with some blobs, and then with Maemo Libre™ being a deblobbed version of Maemo Leste? ;)
Agreed on the whole base discussion. We have similar ideas/thoughts.
I found the image-builder and jenkins-integration repos on GitHub so I'll see if I can figure it out.
I've not had a chance to talk on Freenode yet, I can probably get on there tomorrow.
Just to clarify -- we use Jenkins to build packages for the repo. I don't think it makes sense to for everyone to set up their own Jenkins instance. What I and freemangordon usually do is to develop on a amd64 VM or just on the device itself (this is what I do most of the time) and then build & test. When it's done, commit and have someone (currently, me or parazyd) rebuild the package in Jenkins.
We can definitely give some people access to Jenkins. From the UI one can rebuild packages easily.
Adding packages to Jenkins requires shell access to the jenkins account.
As for the building the image, I think it's completely separate -- I think it's a debootstrap on steriods + kernel building + other stacking scripts. You can just use our repos when doing that.
Right now most open tasks don't require one to set up their own Jenkins or build their own image, I think. When I help parazyd with debugging an image, I just test the image, fix that needs to be fixed (kernel params, packages missing, wrong versions, missing scripts, config) and then let him know. And then makes a new image - repeat.
Messed around a bit with usb applet and battery applet.
Neither are functional yet, have to replace the hal parts, but getting there.
https://wizzup.org/n900-initial-battery.png
https://wizzup.org/initial-usb-applet.png
Edits/updates in blue...
I finally got around to trying Leste last night. I tried the N900 armel build (maemo-leste-1.0-armel-n900-20180207.img.xz) and I have a few observations...
It failed to complete initialisation. Xorg failed to start and then it shut down the OS automatically. It looks like there are some missing shared libraries. Here's my Xorg.0.log:
[ 62.738] [3/504]
X.Org X Server 1.19.2
Release Date: 2017-03-02
[ 62.752] X Protocol Version 11, Revision 0
[ 62.757] Build Operating System: Linux 4.9.0-4-armmp-lpae armv7l Debian
[ 62.762] Current Operating System: Linux devuan 4.15.0-rc6+ #1 PREEMPT Wed Feb 7 15:47:47 CET 2018 armv7l
[ 62.763] Kernel command line: root=/dev/mmcblk0p6 rootwait ro console=tty0 vram=12M ubi.mtd=5
[ 62.773] Build Date: 16 October 2017 09:52:58AM
[ 62.778] xorg-server 2:1.19.2-1+deb9u2 (https://www.debian.org/support)
[ 62.783] Current version of pixman: 0.34.0
[ 62.794] Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
[ 62.794] Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[ 62.813] (++) Log file: "/tmp/Xorg.0.log", Time: Thu Jan 1 00:01:02 1970
[ 62.828] (==) Using config directory: "/etc/X11/xorg.conf.d"
[ 62.834] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[ 62.842] (==) No Layout section. Using the first Screen section.
[ 62.842] (==) No screen section available. Using defaults.
[ 62.842] (**) |-->Screen "Default Screen Section" (0)
[ 62.842] (**) | |-->Monitor "<default monitor>"
[ 62.851] (==) No monitor specified for screen "Default Screen Section".
Using a default monitor configuration.
[ 62.851] (==) Automatically adding devices
[ 62.851] (==) Automatically enabling devices
[ 62.851] (==) Automatically adding GPU devices
[ 62.852] (==) Max clients allowed: 256, resource mask: 0x1fffff
[ 62.874] (WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist.
[ 62.874] Entry deleted from font path.
[ 62.874] (WW) The directory "/usr/share/fonts/X11/100dpi/" does not exist.
[ 62.875] Entry deleted from font path.
[ 62.875] (WW) The directory "/usr/share/fonts/X11/75dpi/" does not exist.
[ 62.875] Entry deleted from font path.
[ 62.875] (WW) The directory "/usr/share/fonts/X11/Type1" does not exist.
[ 62.875] Entry deleted from font path.
[ 62.875] (WW) The directory "/usr/share/fonts/X11/100dpi" does not exist.
[ 62.875] Entry deleted from font path.
[ 62.875] (WW) The directory "/usr/share/fonts/X11/75dpi" does not exist.
[ 62.876] Entry deleted from font path.
[ 62.876] (==) FontPath set to:
/usr/share/fonts/X11/misc,
built-ins
[ 62.876] (==) ModulePath set to "/usr/lib/xorg/modules"
[ 62.876] (II) The server relies on udev to provide the list of input devices.
If no devices become available, reconfigure udev or disable AutoAddDevices.
[ 62.886] (--) using VT number 2
[ 62.887] (II) systemd-logind: logind integration requires -keeptty and -keeptty was not provided, disabling logind integration
[ 62.888] (II) no primary bus or device found
[ 62.896] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[ 62.907] (EE) Failed to load /usr/lib/xorg/modules/extensions/libglx.so: libGL.so.1: cannot open shared object file: No such file or directory
[ 62.907] (II) Unloading glx
[ 62.908] (EE) Failed to load module "glx" (loader failed, 7)
[ 62.908] (==) Matched modesetting as autoconfigured driver 0
[ 62.908] (==) Matched fbdev as autoconfigured driver 1
[ 62.908] (==) Assigned the driver to the xf86ConfigLayout
[ 62.911] (II) Loading /usr/lib/xorg/modules/drivers/modesetting_drv.so
[ 62.919] (II) Module modesetting: vendor="X.Org Foundation"
[ 62.919] compiled for 1.19.2, module version = 1.19.2
[ 62.921] (II) Loading /usr/lib/xorg/modules/drivers/fbdev_drv.so
[ 62.935] (EE) Failed to load /usr/lib/xorg/modules/drivers/fbdev_drv.so: libpvr2d.so: cannot open shared object file: No such file or directory
[ 62.935] (II) Unloading fbdev
[ 62.936] (EE) Failed to load module "fbdev" (loader failed, 7)
[ 62.936] (II) modesetting: Driver for Modesetting Kernel Drivers: kms
[ 62.936] (WW) xf86OpenConsole: setpgid failed: Operation not permitted
[ 62.936] (WW) xf86OpenConsole: setsid failed: Operation not permitted
[ 62.957] (WW) Falling back to old probe method for modesetting
[ 62.958] (EE) open /dev/dri/card0: No such file or directory
[ 62.958] (EE) No devices detected.
[ 62.958] (EE)
Fatal server error:
[ 62.959] (EE) no screens found(EE)
[ 62.959] (EE)
Please consult the The X.Org Foundation support
at http://wiki.x.org
for help.
[ 62.959] (EE) Please also check the log file at "/tmp/Xorg.0.log" for additional information.
[ 62.960] (EE)
[ 62.987] (EE) Server terminated with error (1). Closing log file.
As per fmg's recommendation, Hard FP works fine and boots into Hildon.
I haven't what looked to see what triggers the automatic shutdown but I think it would be better to roll back to the previous run level with a console login prompt instead completely shutting down.
There appears to be a bug (watchdog kicks in perhaps?) which causes a complete shutdown when switching run levels. Fremantle also had this quirk. I'll file this on the bug tracker soon, after I've done more testing.
I noticed that the image uses a separate vfat /boot slice. Is there any particular reason for using vfat? U-Boot can boot off ext4 directly without any issues. I frequently test on an SD card with multiple slices, each with a different OS install. To accommodate this, I had to manually copy the zImage and uImage to the root slice and edit /etc/fstab. I can see this becoming annoying if I have to do this every time I test an image. If there are no objections, I'd like to move it all to single ext4 slice. I don't mind fixing this myself.
Never mind about this. I found the tarball which is easy enough to unpack to a single slice. Although it still might be worth removing the /boot line from the fstab, at least for the tarball, as it's not needed.
I'm not sure why, but I couldn't mount the Leste ext4 slice on my SD card under Fremantle (kernel power). I've never had a problem with ext4 before and I can still mount other ext4 slices under Fremantle. The same slice mounts without any problems under Devuan on my N900. Not critical, just an observation. We can let this one go if you like.
Wizzup pointed out that this relates to new ext4 features. I guess these are incompatible with kernel-power's ext4 support.
This one's not a problem, I'm just curious. I noticed that it's running OpenRC. Is that something specific to Leste or is OpenRC now the default in Devuan Ascii (Devuan Jessie didn't use it)?
Found that the openrc package it explicitly added to the Leste image build. Good choice in my opinion. Also found out that is installable using the expert install path in Ascii.
In DebiaN900, I create a "run once" SysV init RC script which runs interactive commands to configure things like passwords, locale and timezone (https://github.com/dderby/debian900/blob/master/install_debian.sh#L270-L306) on first boot. Do we need something similar in Leste?
I'll probably integrate this soon. In the long term, we may want to set up these things in Hildon on its first run. Fremantle does something similar.
freemangordon
2018-02-12, 21:46
@wicket - try armhf image, it should work
Wikiwide
2018-02-13, 05:11
Or better - enumerate input devices on such device added/removed and show the cursor if there is at least one device of type mouse.
EDIT: I think they did something similar in cordia, we can just reuse it.
EDIT2: this (https://github.com/Cordia/hildon-desktop/commit/df2dd4a9514504285f04f4a6a26e43440b7346f5)
Would be neat to be able to see cursor even if event comes from touchscreen. If multiple cursors are supported, such as finger at touchscreen and external mouse, at the same time, then different cursors (round circle for touch, usual arrow pointer for mouse)? If it is possible, of course. Makes for more interesting video screenshots if cursors can be seen.
Thank you. Best wishes.
~~~~~~~~~~~~~~~~~
Per aspera ad astra...
Android_808
2018-02-13, 08:04
Taking the same code snippet from Cordia, you could check a setting for touchscreen cursor visibility and set it to selected cursor. Other than needing a section in Hildon control panel, pretty straightforward.
For screen recording, at least regarding N900, I would use a desktop and make use of the click animation in the desktop software, if it works with VMs. For that reason, I would leave the touch cursor for now.
The status-area-applet-battery initial port is pretty much done. [0]
Pending a N900 kernel bug it should start to work nicely. [1]
It has been ported to use UPower, one missing feature right now is proper mAh reporting. These values are present in /sys, but UPower doesn't pass them along... So don't expect that to be correct yet. Otherwise -- low power warnings, charging animations, gconf, etc should all work. Relevent open issues are [2] and [3].
Once the kernel problem is solved, we'll make a new image.
It also works on the Droid4, kind of. The Droid4 does not yet report 'capacity' (percentage), so that's always 0.
Looking at at hildon-status-bar-usb atm, will need porting to udev and perhaps provide a dbus service for this: https://github.com/maemo-leste/bugtracker/issues/39
Likely we will extend this applet to use CONFIGFS_USB for mass-storage,g-nokia, and so on, so that we can even make multifunction usb peripherals. This should also work out of the box for the Droid4 and the LIME2.
[0] https://github.com/maemo-leste/status-area-applet-battery/
[1] https://marc.info/?l=linux-omap&m=151869726709281&w=2
[2] https://github.com/maemo-leste/bugtracker/issues/67
[3] https://github.com/maemo-leste/bugtracker/issues/68
can't wait for the droid images :D
can't wait for the droid images :D
The Droid 4 images are already available. ;) There was a problem with yesterday's images but it was fixed and there were new images built today (http://maedevu.maemo.org/images/droid4/20180216/). I tried them and Hildon came up successfully. :)
Make sure you place the image on slice 2 of your SD card. Otherwise you'll need to edit the kernel cmdline in the /etc/kexec/kexec script in ddroid and point "root" to the right device.
The Droid 4 images are already available. ;) There was a problem with yesterday's images but it was fixed and there were new images built today (http://maedevu.maemo.org/images/droid4/20180216/). I tried them and Hildon came up successfully. :)
Make sure you place the image on slice 2 of your SD card. Otherwise you'll need to edit the kernel cmdline in the /etc/kexec/kexec script in ddroid and point "root" to the right device.
If you "apt-get update && apt-get upgrade mce" you will have mce on droid4 with backlight/brightness support. I also locally have mce where the power button (top of the phone) is mapped to screen lock like the slider on the n900, but not sure how to continue there. Works quite well though.
https://github.com/maemo-leste/bugtracker/issues/65
https://github.com/maemo-leste/bugtracker/issues/71
I'd really love to see a picture of a Droid 4 running Maemo-Leste :)
I'd really love to see a picture of a Droid 4 running Maemo-Leste :)
Check out slide 14:
https://fosdem.org/2018/schedule/event/hwenablement_mainline_linux_on_motorola_droid_4/attachments/slides/2463/export/events/attachments/hwenablement_mainline_linux_on_motorola_droid_4/slides/2463/fosdem_2018_droid4.pdf
Sorry if this is a bit noobish question but why not use the cordia/Android_808 version of hildon as it seems a bit more updated and less targeted to n900.
Sorry if this is a bit noobish question but why not use the cordia/Android_808 version of hildon as it seems a bit more updated
I'm also no expert in this, but as far as I know, both cordia and other work by Android_808 are part of the project. I know he has contributed at least ideas (if not code) on Github.
and less targeted to n900.
I know of at least two other devices besides N900 that Maemo Leste runs on - Motorola Droid 4, and an Allwinner tablet (no idea about exact model)
So yes, the project is not n900-specific :)
Just happens that N900 has slightly better support in mainline, which makes it easier to test stuff, but Droid4 is a much faster device than N900, and there's also a lot of work being done upstream to improve kernel support for it.
Android_808
2018-02-21, 17:57
Sorry if this is a bit noobish question but why not use the cordia/Android_808 version of hildon as it seems a bit more updated and less targeted to n900.
My code isn't complete and depending on the variant used is incompatible with Maemo packages. It, as the thread suggested, was an experiement to see what could be done. Leste, although currently GTK2 based, is working.
Cordia ripped out a lot of Maemo code marked as deprecated, so my Cordia/Mer userland based version is the same. The second variant, the one fmg and myself were working on (Fremantle-GTK3) was rebased on top of the Maemo versions to try to remain as compatible as possible. Some of this work also made its way into fmg's Fremantle-GTK2 project. As far as I can tell, Leste is using the work started in Fremantle-GTK2.
I keep meaning to take a look at migrating the libsdl1.2 patches to 1.2.15 to see if that will help with the fullscreen issue. I may also look at building a version of hildon-gtk3 on top of Leste.
Perhaps we could support both GTKs?
For the Xorg issue on the VM: remove -noreset from /etc/init.d/xorg (this allows X to retry startup and not fall back to tty on first try)
since it launches a URL, User Guide app (which has a unlocalized name for some reason) will start working once a browser is available that can handle such things.
great work so far!
Android_808
2018-03-02, 17:29
I've just submitted a version of libsdl1.2-1.2.15 to the fullscreen ticket. I don't know if this is usable on Fremantle, it builds in a CSSU-T Fremantle X86 scratchbox target. I won't post links here as it is not an "Extras" package as Chess, Marble etc depend on it.
EDIT: Won't build on Leste atm:
_XData32 redefined.
debian/compat needs to be 5+
dhinstall throws error about missing sdl-config-1*..that's already in the correct folder
More packaging errors.
Will rebase patches on current Debian version to pull in current packaging over the weekend hopefully.
There's a new blog post out, our March 2018 update: https://maemo-leste.github.io/maemo-leste-first-update-march-2018.html
(Android_808 - cool!)
Thanks, great to see some detailed blog posts like that, it's very appreciated! Awesome to see that Anbox might work with Maemo-Leste one day, that would be a game changer for using it on modern devices.
Android_808
2018-03-03, 13:57
Ok, first working-ish version of libsdl1.2 fixes uploaded to comments.
amigo157
2018-03-11, 09:25
Is there a chance to run maemo leste on N8x0?
Is there a chance to run maemo leste on N8x0?
I would say yes. Leste support largely depends on mainline Linux support. There is mainline Linux support for all 3 N8x0 devices, and the 770, although I don't know what state they are in. Support is (currently) provided via board files, notand DT. It definitely worked at some stage, see the eLinux status page (https://elinux.org/N800).
There is also support for them in QEMU but it seems current mainline booting is broken right now:
https://www.spinics.net/lists/linux-omap/msg141167.html
EDIT:
I see you've already found and updated the eLinux status page. ;)
I should also add that I don't know how well Leste/Hildon will scale to a device with only 128MB RAM and lower screen resolution, but in principle it should be possible to get something running on it.
endsormeans
2018-03-11, 16:50
wellllll.....
yes and no the n8x0's run on 128mb ram...
extending the memory an additional 128mb via virtual memory ..they also have the ability to bump it up to 256mb ....
but ...that additional virtual memory may not have an impact ...depending on what the intended usage is ...
for example,...I have no idea the impact ...if any... the virtual memory would have in this use case...
unexplored n8x0 country..
as far as running maemo leste from a card instead of onboard storage...
I imagine it would be little different than the current methods for the n8x0...
meaning one is not restricted to capacity...
similar to the n900 in it's methods of running os's off cards...
as far as res conflicts go...between the n900 and n8x0's...
the n900 is what... 800×480? right?
same for the n800..
the n810 has 800x458...I think...
so I would hope the difference would be negligible and manageable for the n810...
and that it should have no prob for the n800....
but that is just superficial hoping that is based on simply the screen res comparison...there may be ...god knows what issues... which may impede...
but...
If maemo leste can run on the n8x0 ...
then all I can say are 3 things...
#1- "Wow"
#2- "All praise the Great Kernel in the Sky.." :D
and #3- "Do it ...do it...do it ...do it!!!! For God's sake man...do it! "
It would modernize and make current again ...an army of devices and hardcore n8x0 lovers which deserve the opportunity...
and doubtless...bring back many users who left ages ago ...
amigo157
2018-03-11, 17:02
I would say yes. Leste support largely depends on mainline Linux support. There is mainline Linux support for all 3 N8x0 devices, and the 770, although I don't know what state they are in. Support is (currently) provided via board files, not DT. It definitely worked at some stage, see the eLinux status page (https://elinux.org/N800).
There is also support for them in QEMU but it seems current mainline booting is broken right now:
https://www.spinics.net/lists/linux-omap/msg141167.html
EDIT:
I see you've already found and updated the eLinux status page. ;)
I should also add that I don't know how well Leste/Hildon will scale to a device with only 128MB RAM and lower screen resolution, but in principle it should be possible to get something running on it.
I just edited the previous information. Now I want to find information, patches and collect everything on elinux.org
wellllll.....
yes and no the n8x0's run on 128mb ram...
extending the memory an additional 128mb via virtual memory ..they also have the ability to bump it up to 256mb ....
but ...that additional virtual memory may not have an impact ...depending on what the intended usage is ...
for example,...I have no idea the impact ...if any... the virtual memory would have in this use case...
unexplored n8x0 country..
as far as running maemo leste from a card instead of onboard storage...
I imagine it would be little different than the current methods for the n8x0...
meaning one is not restricted to capacity...
similar to the n900 in it's methods of running os's off cards...
as far as res conflicts go...between the n900 and n8x0's...
the n900 is what... 800×480? right?
same for the n800..
the n810 has 800x458...I think...
so I would hope the difference would be negligible and manageable for the n810...
and that it should have no prob for the n800....
but that is just superficial hoping that is based on simply the screen res comparison...there may be ...god knows what issues... which may impede...
but...
If maemo leste can run on the n8x0 ...
then all I can say are 3 things...
#1- "Wow"
#2- "All praise the Great Kernel in the Sky.." :D
and #3- "Do it ...do it...do it ...do it!!!! For God's sake man...do it! "
It would modernize and make current again ...an army of devices and hardcore n8x0 lovers which deserve the opportunity...
and doubtless...bring back many users who left ages ago ...
I stand corrected. The 770 and N8x0 all have an 800x480 display, the same as the N900.
Also there are already DTs in mainline for all 3 N8x0 devices (I should've known this, they are linked to in my doc!). They do still have legacy board files so there are probably things still to be migrated to DT, that's what confused me I think.
If there is significant interest and people willing to help out, it should be easy enough to produce basic builds for N8x0 devices, starting off with the DTs and omap2plus_defconfig. Maybe I should get myself a device for testing. ;) Although I should probably get N950 and N9 working before I look at this.
In Leste we've been using zram for virtual memory instead of eMMC based swap. It won't give you as much as 128MB extra but it is much faster. Of course we could add normal swap too which may help.
endsormeans
2018-03-12, 04:08
huh...
zram you say...
well that should be acceptable for the n8x0..since running diablo turbo from card... the use of zram is a given...
But yet again...that is a casually stated observation...subtle finer points of difference will yet again apply....concerning compat.
there is something I have to dig for...
give me a few days and I will be right back....with something...
endsormeans
2018-03-12, 07:17
ok...
I must do some more digging...
since I bought my place and moved ...I haven't had much time...
this summer I hope to have more...
So I did some quick digging through boxes...I must dig some more..
for my spare n8x0's and accessories...
I have kept out 1 n800 and 1 n810 for daily use and packed the rest...
so I must find that cache of n8x0 stuff...
anyway ....
found one of my spares..in an unlikely box..
.
so...
wicket..
I have a spare n800 for you ...
it is one I used to loan out to a friend until he managed somehow to literally break the steel stand for it.
purely a cosmetic issue.
I may or may not be able to help much...depends...
But I can send you an n800 ...possibly an n810 as well ...(upon finding them)
a battery (of dubious charge....at worst a few hours...but that matters little since usb and power are two separate cables...unlike the n900 n950 and n9...so such issues surrounding cable connections and charging are rather moot..)
And a power cable...(which works for both the n800 and n810)
usb cable for the n810 is the same as the n900...
usb for the n800 is mini...not micro...which is quite common..as well.
So wicket...
I can send at the very least ...an n800 ...if not an n800 and a n810...
Give me a few days...(even a week...to hunt down all my n8x0 stuff)
and I can find out the cost to ship to you..
You spring for the shipping and they are yours to work with ..
I may or may not be much help...
but I can donate ..
once you play with 'em you're hooked...believe me...
for example...just install xmms (LOVE xmms!)
and play with that for a bit...and you'll see...
as far as doing leste for the n950 and n9 first...
well...
perhaps it is possible that my judgement is clouded and I am biased...
But I don't think so...
do the n950 and n9 first?
No man...
Fcuk 'em ...
those ugly buck - toothed fourth - cousin - removed b-tards have had it good long enough...let 'em wait.
Do the n8x0's first.
:D
Do the n900 first.
:D
Fix‘d
10 chars
endsormeans
2018-03-12, 14:55
https://www.youtube.com/watch?v=5YztNYiZrzo
so...
wicket..
I have a spare n800 for you ...
it is one I used to loan out to a friend until he managed somehow to literally break the steel stand for it.
purely a cosmetic issue.
I may or may not be able to help much...depends...
But I can send you an n800 ...possibly an n810 as well ...(upon finding them)
a battery (of dubious charge....at worst a few hours...but that matters little since usb and power are two separate cables...unlike the n900 n950 and n9...so such issues surrounding cable connections and charging are rather moot..)
And a power cable...(which works for both the n800 and n810)
usb cable for the n810 is the same as the n900...
usb for the n800 is mini...not micro...which is quite common..as well.
So wicket...
I can send at the very least ...an n800 ...if not an n800 and a n810...
Give me a few days...(even a week...to hunt down all my n8x0 stuff)
and I can find out the cost to ship to you..
You spring for the shipping and they are yours to work with ..
I may or may not be much help...
but I can donate ..
once you play with 'em you're hooked...believe me...
for example...just install xmms (LOVE xmms!)
and play with that for a bit...and you'll see...
Thank you endsormeans, that's very kind of you to offer, but let's just hold off for the moment though. After shipping and import duty, it often works out cheaper to get hold of one locally. So I'll have a look to see if I can get one here first.
I'd also want to make sure I'd at least have a serial console before accepting any donation or it could be a complete waste of time and money. Lack of a serial console is what's hindering my N950 progress right now.
as far as doing leste for the n950 and n9 first...
well...
perhaps it is possible that my judgement is clouded and I am biased...
But I don't think so...
do the n950 and n9 first?
No man...
Fcuk 'em ...
those ugly buck - toothed fourth - cousin - removed b-tards have had it good long enough...let 'em wait.
Do the n8x0's first.
:D
Sorry to disappoint but I'm doing the N950 first as I already have one (well, on loan from Nokia :D). I've already started it and I want to finish it. ;) My intention is to attract more developers and I believe there are potentially more N9 developers than N8x0 (it will be easy enough to enable N9 builds once N950 is done). I'm nearly there, I have mainline Linux booting with the display using Pali's 0xFFFF, I just need to figure out what's going wrong with ubiboot.
Do the n900 first.
:D
Fix‘d
10 chars
I hope it didn't sound like the N900 is being neglected for other devices because that certainly isn't the case. We already have builds for the N900 and although they aren't yet ready for general use, rest assured there are more experienced people than me working to improve it everyday. What we lack right now is developers and by me looking at enabling other devices, I hope we can attract more developers. That will benefit the N900 in the long run as there is plenty of device agnostic stuff still to be fixed.
endsormeans
2018-03-12, 23:01
There may possibly be more n9 developers watching and listening...
But I really doubt there are more n9 developers than there were for the n8x0...
It is just the bulk of the n8x0 developers have left and are not watching and listening at this point in time.
Take for example ...
All the recorded various alternate os's, de's and wm's done for the n900, n950 and n9 ...and add them all up ...
and they don't even come close to the number of os's, de's, and wm's done for the n8x0 ...
With the massive volume of years of easily accessible data ...
and with some email's sent out to those departed n8x0 devels ...
I think it would be done far faster than the n900, n950, and n9..
But this is purely my perspective...
As far as the shipping and import costs go for the donor n8x0's...
I was considering that possibility of it being cheaper to source them locally....
Let me know
I thought I'd share some news which I'm genuinely very excited about...
Incoming and outgoing calls are working with mainline Linux (on the Droid 4). (https://www.spinics.net/lists/linux-omap/msg142302.html)
It's only a matter of time before this lands in Leste. :)
There is now a mediawiki, thanks to parazyd: https://leste.maemo.org/Main_Page
There were lots of people who wanted to add bits to the wiki - there is absolutely no structure yet, so let's get this going. If at all possible, let's try to coordinate some wiki structure. Either on IRC, or here, on tmo (new thread or this thread, both fine by me).
Are there people who want to take the lead on the wiki effort?
(P.S. Yes, we can merge this wiki into the main maemo.org wiki at some point, but currently it seems to make more sense to keep this separate, as not to confuse pages that are relevant for diablo, fremantle, etc)
There were lots of people who wanted to add bits to the wiki - there is absolutely no structure yet, so let's get this going. If at all possible, let's try to coordinate some wiki structure. Either on IRC, or here, on tmo (new thread or this thread, both fine by me).
I think we could start by migrating the devices from https://maemo-leste.github.io/ to the wiki.
I'll take care of the initial pages for the N950 and N9 as I'm doing the ports.
I think we should have an FAQ wiki page. We can start drafting questions and answers before writing them up on the wiki. I've started a draft FAQ here (https://public.etherpad-mozilla.org/p/Maemo_Leste_FAQ) so if anyone has a question they would like answering, please add it there.
I would also like to start migrating my mainline devices list to the wiki and I will expand it to start documenting SoCs and drivers supported by mainline Linux. What I would actually like to have is a database backend to store this information. It would need to be updated by editing the wiki. What I want is to build an extensive knowledge base that allows one to quickly see what's supported and what's missing for each device, even those which we haven't created ports for yet or don't even have DTs in mainline. That will help us to identify if there are any devices that have several drivers already available in mainline which would potentially be good candidates for further mainlining work.
I found this extension (https://www.mediawiki.org/wiki/Extension:Cargo). I think it's what I'm looking for. Has anyone got a better recommendation?
Are there people who want to take the lead on the wiki effort?
I'd like to take the lead for documenting devices in mainline Linux. That's a job in itself so I'll leave it to someone else to lead the rest of the wiki.
Hi and thanks to each and everyone of you who are working on this project! My friend just analyzed me and said that "with your linux you are a modern day amish and the N900 is your old Toyota Corolla". I disagree with him and what you are doing is helping me to prove his wrong. My contribution to this project is probably only to make you laugh cause I may ask stupid questions and suggest bad ideas cause I don't understand anything about coding or building or whatever. But just bought two N900s and gonna buy more and then found out that there are you guys who are doing some magic! Sooo glad!
you will lose the argument/bet/dare/whatever it is...
on the other hand, i hope you find your Linux/N900 journey fulfilling.
the N900 is your old Toyota Corolla
If it works, it works!
endsormeans
2018-04-09, 22:39
I have to say "Sorry" twice here....
Sorry to hear about your newly diagnosed N900 ailment...
N900-itis is more common than you'd think...
Once caught ..it is like a stubborn std ...
it never leaves...
After your gripping tale...
I am truly sorry...
but I just can't call you "peduism"....ever....
Even my usual tag-name... I call everyone new here for the first 100 thanks..."Newmo" ...
I can't even call you that...now..
Your story was so moving ...
I think I even saw unicorns whilst reading it...
So I just can't personally call you "peduism"...now...
I find it a toss up to either call you "Corolla"...
or...
"Maemish"...
and I am leaning heavily towards Maemish....
Re-post cause my post disappeared after sending.
How can N900 + Linux lose anything? Isn't that combo a measure to be measured against?
One question: how can one change a username here? Should change it to Maemish.
Not gonna post here more unless it's on topic. You are all honoured from here and just waiting to be able to use the Leste.
endsormeans
2018-04-10, 09:27
Haha
Ach...hate to tell you ..
I don't think its possible to change your username...
I think you have to petition the Pope for high level stuff like that..
Or.. just use a different email and sign up again and choose a new username...
That's what i do anyway...
How do you think all the greatest minds end up being voted in for council?
You see...
I must have thousands of usernames here ..
It makes the elections easier to deal with....
Frankly ...out of the thousands and thousands and thousands of members and usernames here...
There are really only 10 actual people here...
The rest are pretty much all just me...
All the posting and counterposting i do between "members"
..to keep up the illusion of free will and the illusion of a massive community has become burdensome and time consuming though...
So i just let an algorithm deal with the conversations here now...
So if you find postings fom "members "
with odd typos in them...
Just tell me...
And I'll hit the "reset" button.
And, all i can say fom this POV is....
It's always more convincing to spread extreme opinions on multiple user accounts.
Yaya.
Dunno why,
Doesn't feel like a conspiracy then.
You know, more like in the old days.
When we visited BBSs with no more than 2 user lines.
Coisy times.
Didn't we all learn that best results come from talk to ourselves back then?
And this awkward feeling when the hordes suddenly entered our internet and began to speak in a language we invented for quick typing. LOL.
Forget Elop, Trump and Putin, ^that was the beginning of the end.
endsormeans
2018-04-10, 10:36
Hahaha...
Truth ...
endsormeans
2018-04-10, 16:05
Hahahahahahaha
You actually did it!
You got game Maemish...
https://geneticliteracyproject.org/wp-content/uploads/2017/12/Amish-Facts-Dont-Go-For-The-Trim.jpg
Android_808
2018-04-10, 16:27
Did anyone else manage to test the SDL patches I uploaded?
tortoisedoc
2018-04-10, 17:23
If it works, it works!
If it works like an N900, and looks like an N900, it must be a N900!
We now have dists available for the N950 and N9 (https://maedevu.maemo.org/images/) running Linux 4.16.4 from linux-stable. More info here (https://github.com/maemo-leste/bugtracker/issues/121) (will write this up on the wiki soon). N9 is untested so I'm hoping for a guinea pig to try it out. ;) The N9 port is mostly identical to the N950 port which has been tested. There is no virtual keyboard yet but Hildon is currently unusable anyway (other window managers work fine). I'm hoping someone else can help to get this working so I can focus on other stuff. USB networking works fine out-of-the-box (see the linked GitHub issue for info on how to set up the PC side in Linux).
There is a new status update out. Aim was to have it ready early april, but it became late april instead. Enjoy!
https://maemo-leste.github.io/maemo-leste-second-update-april-2018.html
A very important question: how do you pronounce Leste? "Les-teh" or "less tea"?
A very important question: how do you pronounce Leste? "Les-teh" or "less tea"?
Ask Wikipedia: https://en.wikipedia.org/wiki/Leste :)
Ask Wikipedia: https://en.wikipedia.org/wiki/Leste :)
Continuing on the wind theme, I like it.
Your link does not answer the question explicitly but gives a locale that at least suggests the answer. That's good enough for me, thanks.
endsormeans
2018-05-04, 08:56
wellllll....
I have been mucking about with my latest acquisition ..a nexus 5...
As far as what I think of it...
Def. one of the better smartphones I have had in my hands (no compare to the nxx0's of course...) ..
I have virtually no additional apps installed.
Updated to droid 5.1
rooted of course..
crap bloat I would never use I have uninstalled back to the stock apps...cleared the caches...
and only 3 things I do NOT like...
1- it's running android. :D
2- it's running android :D ....nono...actually ..I do NOT like the fact it has no sd card slot. ...sure I can do usb storage on the go ...but crap sticking out of a phone dangling around like some ganglia doesn't impress me .
and hence ...with no sd slot..so goes options to move apps to sd card with it.
3- the result of #2...is that 16 gb is all fine and dandy to have..internally..
but to have 2 gb of ram of which 1.5+ gb is consumed by the system and stock and a couple apps...does NOT impress me at all...
what a colossal waste.
Wicket hope you can get Leste workin' on your nexus 5...
Reason I got mine was it is one of the few devices open enough to do some experimenting with alt. os's (which obviously is why wicket got his)
Hope it works man...
Otherwise I will go down the plasma road...
I am not keen on SF...
there is just too much goin' on there politically that I do not run with..
let alone the closed nature of their endeavor.
I totally agree. I am using the nexus 5 with SF and I'm happy with it. You can use the whole screen without any additional bar like on Android, the screen and the brightness are really good.
You can also try Ubuntu from UBports on it.
endsormeans
2018-05-04, 10:07
thanks for that claustn...
actually buntu would be my 3rd choice (due to wif and sim and volume bugs)
after my 2nd choice of plasma (which seems to have really only 1 sticking point for me...the "getting wifi to run" issue...if I can get it to run on plasma on the nexus 5 ...well ...hell...I won't complain...)
after my primary choice of Leste (of course)...
So yeah...that is the plan anyway...
If one fails...
I have a few options with escalating buggy issues on the way down that slippery slide to the iphone...
hahahahahaha
My interest in the Nexus 5 piqued when I found out that someone got calls working on it with mainline Linux shortly after Droid 4 calls started working (probably no coincidence that both devices use an MSM modem). The Nexus 5 is one of the devices that has reasonably mature mainline Linux support which makes it a great target for Maemo Leste. I haven't really done anything with mine yet other than boot the test image found here (https://github.com/flto/linux/wiki/hammerhead-upstream). The display comes up and USB networking works which is a great starting point for porting Leste so I don't envisage any huge difficulties in getting something basic up and running. I'm looking forward to trying video acceleration which should automatically work out-of-the-box thanks to Freedreno/Mesa. The Nexus 5 port isn't my immediate priority but I'll try to get to it soon. :)
Has anyone tried the N9 port yet? I'd love to get some feedback.
Has anyone tried the N9 port yet? I'd love to get some feedback.
I would like to try, on my N9 I have ubiboot with MeeGo and Nitdroid, what do I have to do to have it as another OS to boot?
I would like to try, on my N9 I have ubiboot with MeeGo and Nitdroid, what do I have to do to have it as another OS to boot?
If you have ubiboot installed then you're already halfway there. There is a new version ubiboot but it isn't required as Leste is booted without an initrd. The new ubiboot does however now include a nice Maemo Leste graphic and a few things preconfigured for it. That reminds me that I should send a pull request to juiceme to set a few more defaults for Leste (described below).
To get Leste running, you'll need to create a new partition (ext4 is fine). Then you can unpack the .tar.gz dist for the N9 (https://maedevu.maemo.org/images/n9/20180425/maemo-leste-1.0-armhf-n9-20180425.tar.gz) to that partition and configure ubiboot.conf to use it. Assuming you'll use slot 5 (https://github.com/juiceme/ubiboot-animatronics/blob/master/ubiboot.conf#L275-L293):
Set G_OS5_INITSCRIPT (https://github.com/juiceme/ubiboot-animatronics/blob/master/ubiboot.conf#L126) to "\/sbin\/preinit" (those are "\" and "/", not Vs)
Set G_OS5_NUM (https://github.com/juiceme/ubiboot-animatronics/blob/master/ubiboot.conf#L277) to "1"
Set G_OS5_PARTITION (https://github.com/juiceme/ubiboot-animatronics/blob/master/ubiboot.conf#L279) to the partition number of your new partition
Set G_OS5_NAME (https://github.com/juiceme/ubiboot-animatronics/blob/master/ubiboot.conf#L280) to "Maemo"
Set G_OS5_1_LABEL (https://github.com/juiceme/ubiboot-animatronics/blob/master/ubiboot.conf#L282) to "Maemo Leste - Linux 4.16" or whatever description you like
Set G_OS5_1_FILE (https://github.com/juiceme/ubiboot-animatronics/blob/master/ubiboot.conf#L283) to "/boot/Maemo/boot/zImage".
I'll write up a guide on the wiki once I've sent that patch to juiceme but in the meantime the above should get you going.
As I already mentioned, Hildon is broken on the N950 so I suspect it might be broken on the N9 too. So don't expect wonders, but USB networking works so that will give you complete access to the Devuan-like system to play around with.
The guide is now on the wiki (https://leste.maemo.org/Main_Page#N9.2FN950). It also mentions a couple of alternative methods for if you don't want to repartition your eMMC.
Relevant/notrelevant, a few weeks ago some exploits came out to get the Nintendo Switch booting into recovery mode (runs Tegra X1) so since then people have gotten linux booting off it.
Around then is when I bought one, because finally a decent solid little linux tablet.
Also just saw this when I was looking at ways to get hildon UI on debian.
Looking forward to the aarch64 release to try out on the Switch :)
There has been some talk of an AArch64 port of Maemo Leste. We'll need to ensure all of the packages build for this architecture. AArch64 CPUs should be backward compatible with ARMv7 so feel free to give that a try in the meantime.
In semi-related news, the first release candidate for Devuan Ascii has been released (https://dev1galaxy.org/viewtopic.php?id=2047) and integrates some of device porting work done for Maemo Leste. Builds are available (https://files.roundr.devuan.org/devuan_ascii_rc/embedded/) for the N900, N950, N9, Droid 4 and more.
wpa_supplicant plugin for icd2 is getting there, hope to have it packaged by the end of the weekend:
https://wizzup.org/n900-net-1.png
https://wizzup.org/n900-net-2.png
https://wizzup.org/n900-net-3.png
https://wizzup.org/n900-net-4.png
https://wizzup.org/n900-net-5.png
https://wizzup.org/n900-net-6.png
https://wizzup.org/n900-net-7.png
https://wizzup.org/n900-net-8.png
https://wizzup.org/n900-net-9.png
https://wizzup.org/n900-net-10.png
https://wizzup.org/n900-net-11.png
https://wizzup.org/n900-net-12.png
https://wizzup.org/n900-net-13.png
Android_808
2018-05-18, 10:11
Has the work on this taught you enough about integrating plugins to be able to resolve some of the other issues faced in Fremantle or to integrate other solutions? Thinking like Bluetooth networking without relying on scripts or possibly integrating Intel's IWD should wpa_supplicant actually be superceded/replaced.
Has the work on this taught you enough about integrating plugins to be able to resolve some of the other issues faced in Fremantle or to integrate other solutions? Thinking like Bluetooth networking without relying on scripts or possibly integrating Intel's IWD should wpa_supplicant actually be superceded/replaced.
I think so, yes - but there is more to think about.
Specifically on bluetooth, I know very little about it. But I can imagine we should be able to make an icd2 plugin for this. It will be some work, but I can't imagine why it should not work.
What I've also been trying to think about is to have vpn (openvpn, wireguard) and/or Tor support more properly integrated. I want to continue with that after the plugin and some other (usb, droid4 and tablet) bits.
Regarding IWD, I'm personally unimpressed with the design choices they made and see no reason to switch, so for now I don't think it makes sense to work on this. wpa_supplicant just works, can do many of the bits as non-root user, and the dbus api is now almost implemented by me. Implementing another dbus api is not exactly exciting me right now. :)
pythoneye2
2018-05-18, 15:40
bluetooth afaik doesnt work at the moment in recent kernels.
(Brocken since 4.13? but it never worked for me on 4.x, I tried a few of the reichel 4.12 kernels. (similiar https://www.spinics.net/lists/linux-bluetooth/msg71173.html and https://lkml.org/lkml/2017/10/6/54)
4.16.3 can pair but nothing more.
serdev, device tree and powermanagment still needs work.
(edit added first url and finally second url)
Android_808
2018-05-20, 16:09
Regarding IWD, I'm personally unimpressed with the design choices they made and see no reason to switch, so for now I don't think it makes sense to work on this. wpa_supplicant just works, can do many of the bits as non-root user, and the dbus api is now almost implemented by me. Implementing another dbus api is not exactly exciting me right now. :)
I just used IWD as an example. I can't see it replacing wpa_supplicant for quite some time if at all. I do like the idea of OpenVPN/Wireguard integration here.
There is now a pre-alpha package libicd-network-wpasupplicant in the repos. You really need to know how to use it (e.g. what doesn't work - some obvious things to do not work yet), but otherwise it works stable. It also requires manually starting some services currently, so it's not yet ready for testing, but I wanted to give a status update.
WPA-EAP is now partially implemented. PEAP with MSCHAPV2 works, and TTLS with PAP should work, including anonymous identity (I will test this today or tomorrow). (eduroam, yay!)
What doesn't work is connecting to a (previously unconfigured) network directly from the applet scan dialog. All networks must be added/configured via control panel "internet connectivity". Password popups also are not yet implemented yet. Some minor gconf features are also not implemented yet (ask for password always). autoconnect check is also not fully implement, for similar reasons. (e.g. we cannot autoconnect if require a password manually every time).
There's also some code cleanups to be done, and I have not tried ad-hoc at all yet.
(The package in the repo doesn't have the WPA-EAP support yet)
Tested to work not just on N900, but also on Raspberry pi 3, Motorola Droid 4 and even virtual machine (with usb passthrough).
So i accidentally found out this boots on the droid bionic using he droid4 images. i guess now i just have to wait for a virtual keyboard.
i bought what i thought was a droid4 on ebay, rooted and set it up, and then noticed it didnt have a keyboard and the listing called it a "Droid 4G"
endsormeans
2018-05-29, 20:23
The cunning cunning bastard!
So i accidentally found out this boots on the droid bionic using he droid4 images. i guess now i just have to wait for a virtual keyboard.
i bought what i thought was a droid4 on ebay, rooted and set it up, and then noticed it didnt have a keyboard and the listing called it a "Droid 4G"
That is impressive. I guess the hardware is similar enough to the droid 4. Maybe the linux-omap people wouldn't mind hearing about that.
Can you take a picture?
(EDIT: If you're lucky, OTG may just work, you perhaps you can connect a keyboard over usb otg?)
Regarding virtual keyboard, we hope to have it ready soon. I should be writing another status update soon, but I want to finish some wifi code before I do that.
I did get to test WPA EAP with TTLS and MSCHAPv2 last week, and it is working for spacenet (so it should work for eduroam too):
https://wizzup.org/n900-libicd-wpasupplicant-spacenet.png
i cant seem to find an otg cable. im sure i've bought like 5 of em in the past, but they seem to have ran off.
pic is 2 bionics, one running leste, resting on top of a nexus s. my wife says i have to much junk on this desk
There's a new update/status/blog post here: https://maemo-leste.github.io/maemo-leste-third-update-may-june-2018.html
Enjoy!
Can't wait for the Nexus 5 port. I have a spare one which was bought for Ubuntu Touch and Plasma but they both don't work for me. Maybe Leste will! Will be more than happy to be a guinea pig for the Nexus 5 port. A non tech guinea pig ;)
endsormeans
2018-06-22, 08:05
agreed.
buntu touch has nice interface...scant apps, and I have come to hate their container method.
plasma is great if it weren't so heavy ...
and yes..
I too am waiting for Leste for the nexus 5
Leste should freakin' fly on it.
I don't mind being a experimental lab animal either..
I have 3 5's to roast...so "expendable" is my middle name right now..
My Nexus 5 arrived. I'll see if I can find a few free evenings and do the port. :)
endsormeans
2018-06-25, 18:59
Excellent .
Looking forward to puttering away with it...
And looking forward to a future with a viable modern maemo experience again...
My Nexus 5 arrived. I'll see if I can find a few free evenings and do the port. :)
Sorry I haven't been very active recently, I'm hoping to find some time to pick things up again soon. If I can collaborate at all with the Nexus 5 port, please let me know. :)
All still wip, but ... (more) awesome work done by freemangordon:
N900 virtual keyboard:
https://wizzup.org/n900-touch-kb1.png
https://wizzup.org/n900-touch-kb2.png
https://wizzup.org/n900-touch-kb3.png
And here on the raspi:
https://wizzup.org/raspi-keyb-2.png
mr_pingu
2018-07-14, 20:00
All still wip, but ... (more) awesome work done by freemangordon:
N900 virtual keyboard:
https://wizzup.org/n900-touch-kb1.png
https://wizzup.org/n900-touch-kb2.png
https://wizzup.org/n900-touch-kb3.png
And here on the raspi:
https://wizzup.org/raspi-keyb-2.png
Nice work.
Portrait supported too?
There is a fourth status update out: https://maemo-leste.github.io/maemo-leste-fourth-update-july-august-2018.html
We might release another set of images tomorrow, to fix a dpkg-divert issue, but I didn't want to delay the status post (also since this is the last day of August ;) )
Nice work.
Portrait supported too?
No, there is no portrait support in Maemo Leste yet - at least not on the N900. Last time I tried that, X crashed, I think. There's still some work to be done PowerVR wise.
pythoneye2
2018-09-01, 22:23
"Some initial research is being done on power usage/saving, it is reported that Maemo Leste currently uses about 90mA, versus the 10mA that Fremantle uses"
For some applications a working suspend to ram might "already" suffice, has someone some numbers for "echo 'mem'>/sys/power/state" on a leste kernel?
"Some initial research is being done on power usage/saving, it is reported that Maemo Leste currently uses about 90mA, versus the 10mA that Fremantle uses"
For some applications a working suspend to ram might "already" suffice, has someone some numbers for "echo 'mem'>/sys/power/state" on a leste kernel?
I tried it a year ago or so, not necessarily on Leste, and I think it worked. But for most of my application this is not particularly useful, and 80mA is simple too much IMHO - right now I get about 15 hours of battery life on Leste. Knowing that it can (easily, probably) become at least 60 hours makes me quite eager to just fix that. :)
sirvival
2018-09-02, 10:54
Hi,
its nice to see things happening for the n900 again.
I have a broken (GSM module) n900 and a everyday working one.
So my plan is to try out leste when it leaves the alpha and goes beta on the broken one.
I have some questions (hope they have not been answered already):
- I have not counted the people involved but from what I gather there are not a lot doing the heavy lifting. If the beta is out and lets say there is a bug in the kernel, will the fix be automatically available or will it require work on your side?
- Will most of the applications from extra etc. be adapted to leste? Or is your scope in maemo "standard" applications only?
Thx!
Hi,
its nice to see things happening for the n900 again.
I have a broken (GSM module) n900 and a everyday working one.
So my plan is to try out leste when it leaves the alpha and goes beta on the broken one.
I have some questions (hope they have not been answered already):
- I have not counted the people involved but from what I gather there are not a lot doing the heavy lifting. If the beta is out and lets say there is a bug in the kernel, will the fix be automatically available or will it require work on your side?
I am not exactly sure what you mean, but there will definitely be work required to fix the bug. Sometimes reporting the bug upstream is enough, other times, we have to do it ourselves. Really, I hope that once we show that what we are trying to achieve is worthwhile, more people will join in. A lot of work has been done by many people over the years, without this work Maemo Leste would not have been possible. Some of these people are still around, still do kernel work, or other work. I believe that with the right focus, we can get these people to (re)join the effort, and have more (wo)manpower.
- Will most of the applications from extra etc. be adapted to leste? Or is your scope in maemo "standard" applications only?
Thx!
That depends on demand. Many application might just need recompilation, so then there is just a bit of packaging work involved. Others might need some fixes, or parts rewritten.
You won't be able to take existing debs and just run them, but that is by design. Getting stuff from extras in will be, just like everything else, based on demand, time, and community effort.
Android_808
2018-09-02, 17:46
Are you planning on replicating/ porting the existing media framework/ mafw? There was some packages that came up when looking at porting another package for games frontend used by Marble etc. I know my earlier work on GTK3 and the Fremantle-GTK2 work that fmg did, didn't really look into it.
freemangordon
2018-09-02, 21:26
Are you planning on replicating/ porting the existing media framework/ mafw? There was some packages that came up when looking at porting another package for games frontend used by Marble etc. I know my earlier work on GTK3 and the Fremantle-GTK2 work that fmg did, didn't really look into it.
https://github.com/maemo-leste/mafw/commits/master
http://maedevu.maemo.org/leste/pool/main/libm/libmafw/
https://github.com/maemo-leste/mafw-shared/commits/master
http://maedevu.maemo.org/leste/pool/main/m/mafw-shared/
more to follow :)
P.S. I ported mafw-iradio-source as well, but in my eternal wisdom I put the code in /tmp and rebooted before pushing, however, the only tough package will be mafw-gst-renderer, it needs gst-0.10->gst-1.0 port. Not impossible though.
Android_808
2018-09-03, 05:54
Typical, can't remember what package it was now. Still needed for other packages like media player.
Whilst mentioning media player, I have one request. For the love of god, can someone please change tracker handling of albums with same name (Greatest Hits) by looking at album artist during scanning.
pythoneye2
2018-09-25, 22:30
# a look (or Howto) at maemo-leste Running on real hardware (amd64)
# base system is ubuntu 16.04 and we use the latest maemo-leste-1.0-amd64-virtual-20180425.vdi virtualbox image and grub2
# why? hildon needs 3d hardware acceleration which is often not so well supported in a VM
# the leste wiki (https://leste.maemo.org/Virtual_Machine) on this topic is not so well?
# (are the .box images really Virtualbox images, for me it looks more like Vagrant images (sorry, i downloaded the 1GB image 2 times))
# as usual perform all action on your own risk, dont risk your data, you are playing with your disks. Make backups.
# to get disk raw image
vboxmanage clonehd -format RAW maemo-leste-1.0-amd64-virtual-20180425.vdi maemo-leste-1.0-amd64-virtual-20180425.raw
# to get partion image
sudo bash
losetup -f -P maemo-leste-1.0-amd64-virtual-20180425.raw
cat /dev/loop0p1 > maemo-leste-1.0-amd64-virtual-20180425.imgP
# if you have a free partition (Y) on hdd X slot you can do
# (careful dont overwrite a wrong one!)
cat maemo-leste-1.0-amd64-virtual-20180425.imgP > /dev/sdXpY
# and create an u-boot boot entry in /etc/grub.d/40_custom
menuentry "maemo-leste" {
set root='(hdX,msdosY)'
linux /boot/vmlinuz-4.9.0-6-amd64 root=/dev/sdXpY ro quit net.ifnames=0
initrd /boot/initrd.img-4.9.0-6-amd64
}
# and
update-grub
# sadly i didnt had a free spot for leste so above is untested.
# if you dont have a free partion you can also boot from the partion image stored on a "data" partion
# but for that you have to modify the initramdisk located in maemo-leste-1.0-amd64-virtual-20180425.imgP/boot/initrd.img-4.9.0-6-amd64
losetup -f -P maemo-leste-1.0-amd64-virtual-20180425.imgP
# assuming we get mapped to /dev/loop0
mkdir /mnt/maemo
mount /dev/loop0 /mnt/maemo/
mkdir /mnt/maemo/root/initrd
cd /mnt/maemo/root/initrd
# decompress initrd
zcat ../../boot/initrd.img-4.9.0-6-amd64 | cpio -i
# replace the function local_mount_root() in /mnt/maemo/root/initrd/scripts/local with an ADJUSTED Version of this
# we need to fix the location to your maemo-leste-1.0-amd64-virtual-20180425.imgP rootfs image
local_mount_root()
{
local_top
local_device_setup "${ROOT}" "root file system"
ROOT="${DEV}"
# Get the root filesystem type if not set
if [ -z "${ROOTFSTYPE}" ]; then
FSTYPE=$(get_fstype "${ROOT}")
else
FSTYPE=${ROOTFSTYPE}
fi
local_premount
if [ "${readonly}" = "y" ]; then
roflag=-r
else
roflag=-w
fi
# FIXME This has no error checking
modprobe ${FSTYPE}
mkdir rootfs_base
chmod 0777 rootfs_base
# FIRST ADJUST
# fix this to the location of your maemo-leste-1.0-amd64-virtual-20180425.imgP filesystem
# in this case maemo-leste-1.0-amd64-virtual-20180425.imgP ist stored on an ext4 data partiton on /dev/sda10
mount -w -t ext4 /dev/sda10 /rootfs_base
# SECOND ADJUST
# fix this to the right path of your maemo-leste-1.0-amd64-virtual-20180425.imgP filesystem
# the path to maemo-leste-1.0-amd64-virtual-20180425.imgP in this case is /antiX/maemo-leste-1.0-amd64-virtual-20180425.imgP
# (this creates a loop mount for the root filesystem)
mount -w ${ROOTFLAGS} -t ext4 /rootfs_base/antiX/maemo-leste-1.0-amd64-virtual-20180425.imgP ${rootmnt}
[ "$quiet" != "y" ] && log_begin_msg "root mounted"
# checkfs ${ROOT} root "${FSTYPE}"
# # FIXME This has no error checking
# # Mount root
# if [ "${FSTYPE}" != "unknown" ]; then
# mount ${roflag} -t ${FSTYPE} ${ROOTFLAGS} ${ROOT} ${rootmnt}
# else
# mount ${roflag} ${ROOTFLAGS} ${ROOT} ${rootmnt}
# fi
}
# compress the initrd image again
cd /mnt/maemo/root/initrd
find . | cpio -o -H newc | gzip -9 > /mnt/maemo/boot/initrdImg.img
# and create an ADJUSTED u-boot boot entry in /etc/grub.d/40_custom
# again fix the device and the path
menuentry "maemo-leste.img" {
set isofile="/antiX/maemo-leste-1.0-amd64-virtual-20180425.imgP"
loopback loop (hd0,10)$isofile
linux (loop)/boot/vmlinuz-4.9.0-6-amd64 ro quit net.ifnames=0
initrd (loop)/boot/initrdImg.img
}
# and
update-grub
# Yippy: i managed to boot into maemo-leste on real amd64 hardware
# first impressions:
# nice, lean, cool old school mouse pointer
# a few bugs
# the mouse pointer is invisible in firefox
# i havent found out how to effective navigate the UI with the keyboard (switch desktops, switch windows) (seems it is somehow more optimised for touch ;))
pythoneye2
2018-09-28, 22:04
use at your own risk and reponsibility.
A first try at customizing menus in maemo-leste
install:
download
leste-menu_noicon.tar.gz (https://www.file-upload.net/download-13332319/leste-menu_noicon.tar.gz.html)
extract to leste root
cd /
tar xvvf leste-menu_noicon.tar.gz
# copy icons (for example from maemo) to leste
scp -r /opt/usr/share/icons/hicolor/64x64/hildon/app_install* root@$maemo-leste-ip:/usr/share/icons/hicolor/64x64/hildon/
scp -r /opt/usr/share/icons/hicolor/64x64/apps/app_install* root@$maemo-leste-ip:/usr/share/icons/hicolor/64x64/apps/
# on leste
update-icon-caches /usr/share/icons/*
done.
Result should look very similar to http://maemo.hinoarashi.de/catorise/screens/Screenshot-20110526-190524.png from https://talk.maemo.org/showthread.php?t=73443
how it is done and some insights:
I just copied my maemo configuration generated by catorise over to leste.
Involving
/opt/catorise and /etc/xdg/menus/hildon.menu
/etc/xdg/menus/hildon.menu is a xml file, which uses /opt/catorise/share/*.directory as menus
At this time i have the usual catorise submenus, but right icons doesnt show up and the names are
ai_category_?
root@devuan:~# cat /opt/catorise/share/system.directory
[Desktop Entry]
Type=Directory
Name=ai_category_system
Icon=app_install_system
X-Text-Domain=hildon-application-manager
ai_category seems to be a naming convention from catorise.
So icons arent found and Name is taken.
Lets look at the user_guide
cat /usr/share/applications/hildon/user-guide.desktop
[Desktop Entry]
Encoding=UTF-8
Version=1.0
Name=tana_ap_user_guide
Comment=Show the user guide in a new window
Exec=dbus-send --print-reply --dest=com.nokia.osso_browser /com/nokia/osso_browser/request com.nokia.osso_browser.open_new_window string:http://maemo.nokia.com/n900/userguides/
Icon=tasklaunch_user_guide
Terminal=false
Type=Application
Categories=System
X-HildonDesk-ShowInToolbar=true
X-Osso-Type=application/x-executable
lets modify /opt/catorise/share/system.directory
root@devuan:~# cat /opt/catorise/share/system.directory
[Desktop Entry]
Type=Directory
Name=ai_category_system
#Icon=app_install_system
Icon=tasklaunch_user_guide
X-Text-Domain=hildon-application-manager
and we get a nice white on blue question mark.
find / | grep tasklaunch_user_guide
/usr/share/icons/hicolor/64x64/hildon/tasklaunch_user_guide.png
on maemo
find / | grep app_install_system
/opt/usr/share/icons/hicolor/64x64/apps/app_install_system.png
/opt/usr/share/icons/hicolor/64x64/hildon/app_install_system.png
so to be save i copy both, (they seem to be the same)
scp -r /opt/usr/share/icons/hicolor/64x64/hildon/app_install* root@$maemo-leste-ip:/usr/share/icons/hicolor/64x64/hildon/
scp -r /opt/usr/share/icons/hicolor/64x64/apps/app_install* root@$maemo-leste-ip:/usr/share/icons/hicolor/64x64/apps/
no, still just tasklaunch_user_guide icon is working.
ok, i guess we need to update some icon cache
after
update-icon-caches /usr/share/icons/*
(and a reboot ?)
we have working icons (great) and .. names, ahm (thats different on maemo), great (if the names werent all ai_category_? like on maemo).
[fix using emacs on path /opt/catorise/share
dired-do-query-replace-regexp Name=ai_category_ Name=
doesnt work ???]
but sed did
cd /opt/catorise/share
find ./ -type f -exec sed -i -e 's/Name=ai_category_/Name=/g' {} \;
resulting in more meaningful names
lets try to install a debian packet and see if it shows up, lets try something small and useful: mc
apt-get install mc
and it didnt show up (there is a known fix https://github.com/maemo-leste/bugtracker/issues/82)
cp /usr/share/applications/mc.desktop /usr/share/applications/hildon/mc.desktop
update-icon-caches /usr/share/icons/*
Icon and name should show up, but it doesnot launch. (https://github.com/maemo-leste/bugtracker/issues/165)
Lets look why.
# devuan
cat /usr/share/applications/mc.desktop
[Desktop Entry]
Name=Midnight Commander
Name[af]=Middernag Kommandeur
Name[eo]=Meznokta komandanto
Name[fa]=فرمان*دار نیمه شب
Name[ko]=미드나잇 커멘더
Name[lv]=Pusnakts Komandieris
Name[nso]=Molaedi wa Bosegogare
Name[th]=มิดไนท์คอมมานเดอร์
Name[ve]=Muhulwane wa vhukati ha vhusiku
Name[xh]=Umyaleli Waphakathi kobusuku
Name[zu]=Umyaleli waphakathi nobusuku
Comment=File manager
Comment[pl]=Menedżer plików
Exec=mc
Icon=MidnightCommander
Terminal=true
Type=Application
Categories=ConsoleOnly;Utility;FileManager;System; FileTools;
Keywords=file manager;console;
# on Maemo
cat /usr/share/applications/hildon/mc.desktop
[Desktop Entry]
Encoding=UTF-8
Version=1.0
Type=Application
Name=Midnight Commander
Comment=Console-based file manager and visual shell
Exec=osso-xterm -e mc
Icon=mc
# Terminal=true does not work in Maemo
X-Window-Icon=mc
X-Window-Icon-Dimmed=mc
X-HildonDesk-ShowInToolbar=true
X-Osso-Type=application/x-executable
Found "Terminal=true does not work in Maemo"
fixing to
root@devuan:~# cat /usr/share/applications/hildon/mc.desktop
[Desktop Entry]
Name=Midnight Commander
Name[af]=Middernag Kommandeur
Name[eo]=Meznokta komandanto
Name[fa]=فرمان*دار نیمه شب
Name[ko]=미드나잇 커멘더
Name[lv]=Pusnakts Komandieris
Name[nso]=Molaedi wa Bosegogare
Name[th]=มิดไนท์คอมมานเดอร์
Name[ve]=Muhulwane wa vhukati ha vhusiku
Name[xh]=Umyaleli Waphakathi kobusuku
Name[zu]=Umyaleli waphakathi nobusuku
Comment=File manager
Comment[pl]=Menedżer plików
Exec=osso-xterm -e mc
Icon=MidnightCommander
#Terminal=true
Type=Application
Categories=ConsoleOnly;Utility;FileManager;System; FileTools;
Keywords=file manager;console;
starts mc in osso-xterm
to put it in a category edit /etc/xdg/menus/hildon.menu
for example in utilities:
...
<Menu>
<Name>utilities</Name>
<Directory>utilities.directory</Directory>
<Include>
<Filename>emacs24.desktop</Filename>
<Filename>mc.desktop</Filename>
<Filename>osso-xterm.desktop</Filename>
</Include>
<Layout>
<Filename>mc.desktop</Filename>
<Filename>osso-xterm.desktop</Filename>
<Filename>emacs24.desktop</Filename>
</Layout>
</Menu>
<Menu>
<Name>all</Name>
<Directory>all.directory</Directory>
<Include>
<All/>
</Include>
<Layout>
<Filename>osso-xterm.desktop</Filename>
<Filename>emacs24.desktop</Filename>
<Filename>mc.desktop</Filename>
<Merge type="all"/>
</Layout>
<Exclude>
<Filename>catorise-browser.desktop</Filename>
<Filename>catorise-calendar.desktop</Filename>
<Filename>catorise-image-viewer.desktop</Filename>
<Filename>catorise-modest.desktop</Filename>
<Filename>catorise-osso-addressbook.desktop</Filename>
<Filename>catorise-rtcom-call-ui.desktop</Filename>
<Filename>catorise-rtcom-messaging-ui.desktop</Filename>
</Exclude>
</Menu>
...
I dont know if there is a way to not repeat the entry in Include and Layout. Layout defines the actual gui position.
So in "utilities" mc goes first, in "all" osso-xterm.
Remarks
You cant currently use /debian/.desktop files in hildon directly cause terminal=true is not supported.
So currently seperation of /debian/.desktop and /hildon/.desktop files make sense,
you have to "import" them and cant just add the /usr/share/applications directory.
This alignes with the different ui interfaces of hildon apps and debian apps.
(and their problems right click, drag and drop, hover, keyboard shortcuts collisions)
osso-xterm -e should be something like debian-terminal-app i just used osso-xterm -e cause i didnt know better.
(Is something like debian-gui-app needed too?)
You currently have to modify (maemo-hildon) catorise for rebased hildon to fix "Name"s.
Rant
To make a nice menu creation application for hildon (hildon-rebased and many other modern UX) you need to follow
the (free)Desktop(.org) Menu Specification (which uses xml in Menus and the "Desktop Entry Specification"
which includes a simpler own file format)
and finally find out about the current icon caching mechanism.
different formats, different tools, different bugs, more to learn, easier to automate.
Android_808
2018-09-30, 12:22
Would it be worth you adding an issue to add terminal flag support to hildon? In addition, part of me seems to remember a memory leak when using catorise.
pythoneye2
2018-09-30, 15:56
Would it be worth you adding an issue to add terminal flag support to hildon?
That is one one way to handle it.
Another one is to parse debian .desktop files and keep the hildon debian seperation.
for me that issue is https://github.com/maemo-leste/bugtracker/issues/165
As usual the post just forget to add some basic info to recreate the issue (like what app/.desktop was tried)
I dont have a github account and im not registered on freenet, so i simply post some info in the only leste thread on maemo.org.
In addition, part of me seems to remember a memory leak when using catorise.
So xdg menus (directories) in hildon are brocken, cause if i remember correctly catorise just creates a config for hildon.
I havent notice the impact on my daily, but of course havent looked at it.
But now that there is a test case for leste we can hopefully find some lost memorys (yours on this issue would be easier ) ;)
Android_808
2018-09-30, 17:44
I haven't done much with .desktop files. I know there is the issue with hildon menu starting in applications/hildon as mentioned in the link you referred to. I'm thinking more along the lines of making it so the desktop entries aren't hard coded to use osso-xterm should a replacement or alternative come along.
As it is part of the specs (https://standards.freedesktop.org/desktop-entry-spec/latest/ar01s06.html) I don't see why it couldn't be added. The launcher would then just need to check for flag before executing the app.
That is one one way to handle it.
Another one is to parse debian .desktop files and keep the hildon debian seperation.
for me that issue is https://github.com/maemo-leste/bugtracker/issues/165
As usual the post just forget to add some basic info to recreate the issue (like what app/.desktop was tried)
I dont have a github account and im not registered on freenet, so i simply post some info in the only leste thread on maemo.org.
So xdg menus (directories) in hildon are brocken, cause if i remember correctly catorise just creates a config for hildon.
I havent notice the impact on my daily, but of course havent looked at it.
But now that there is a test case for leste we can hopefully find some lost memorys (yours on this issue would be easier ) ;)
You can also join the mailing list: https://subscribe.dyne.org/
'maemo-leste'
Archives: https://subscribe.dyne.org/
I removed the require-registered flag from the irc channel for now.
USB "PC Suite" mode kinda works with the applet now:
https://wizzup.org/n900-usb-pcsuite-1.png
https://wizzup.org/n900-usb-pcsuite-2.png
Decided to download the source for the wi-fi signal applet (http://maemo.org/packages/view/wifi-signal-applet/) and it just build and works:
https://wizzup.org/n900-wifi-applet.png
New blog post with much more info in a couple of days. :)
Any news on the Nexus 5 front? My phone is up and redy for testing:)
endsormeans
2018-10-14, 21:22
yup.
ditto
+1 to that...!
here here...!!
bring it on for the nexus 5!
I have an extra one waiting JUST for Leste...
I have a Nexus 5 at home. For some reason I assumed it would have a MicroSD card slot, but it doesn't. So I'm trying to figure out what the sensible/easy way to load an OS on it would be, without bricking the device. I think postmarketos has a wiki page on the Nexus 5, so perhaps I just need to check what they do/did.
I did boot an some test image (not Leste) over usb and verified that quite some kernel stuff works. I'll try it coming Wednesday.
You can load OSs via multiROM. Which OS to use is selected at boot time.
imaginaryenemy
2018-10-16, 15:55
I have a Nexus 5 at home. For some reason I assumed it would have a MicroSD card slot, but it doesn't. So I'm trying to figure out what the sensible/easy way to load an OS on it would be, without bricking the device. I think postmarketos has a wiki page on the Nexus 5, so perhaps I just need to check what they do/did.
I did boot an some test image (not Leste) over usb and verified that quite some kernel stuff works. I'll try it coming Wednesday.
I used a micro-USB drive when putting Sailfish on my Nexus 5.
I have a Nexus 5 at home. For some reason I assumed it would have a MicroSD card slot, but it doesn't. So I'm trying to figure out what the sensible/easy way to load an OS on it would be, without bricking the device. I think postmarketos has a wiki page on the Nexus 5, so perhaps I just need to check what they do/did.
I did boot an some test image (not Leste) over usb and verified that quite some kernel stuff works. I'll try it coming Wednesday.
With multirom you can transfer files easily with the usb cable from a pc or mount an external drive with an OTG cable.
Getting there ...
https://wizzup.org/leste-n5-initial.jpg
There is a Maemo-Leste lecture announced for OpenFest in Bulgaria next week... Will try to be there. :)
There is a Maemo-Leste lecture announced for OpenFest in Bulgaria next week... Will try to be there. :)
There is indeed (parazyd and I will give the talk), and it might actually be largest Maemo Leste team gathering so far (3 people). Please do come and say hi before or after the talk.
There is indeed (parazyd and I will give the talk), and it might actually be largest Maemo Leste team gathering so far (3 people). Please do come and say hi before or after the talk.
Greeting from a new member of this awesome community! Been reading for quite some time about this project and it really got me hooked! As i'd like to visit you guys on this lecture, could you provide some more info about it, tickets if necessary, location, etc. AFAIK, it will be located in Sofia Tech Park so me living near Sofia would be easy to find it. Big thanks!
https://www.openfest.org/2018/bg/full-schedule-bg/
14:30 on Sunday (second day)
zxcvbnm3230
2018-10-30, 22:23
There is a Maemo-Leste lecture announced for OpenFest in Bulgaria next week... Will try to be there. :)
Will they record it on video?
Hi everyone, I have a question. (I will have many silly questions, so buckle up)
It's been quite some days that I started testing Maemo Leste... Does someone know how to take screenshots ?
And I have another question half-related to maemo leste and WPA2 Entreprise. The mobile is connecting fine to internet, but I can't do it back in Maemo (freemanlte) when it comes to WPA2 entreprise (eduroam style).
I know it has been mentionned here and there on the forum without some good solutions but I was wondering if I could ask here... so the question is : Is there a way to copy-paste the config files, or the WPA_Supplicant config file from leste to freemantle ?
So...yeah, I am still playing with it, I'm a big noob so there is no many things to do with it for now....(I almost forgot everything linux, I had to do a google search just to remember how to do a simple apt-get update). I'm still figuring out how to install and use some apps, but for now, thank you for your hard work!
Sorry I didn't use my awesome translator today :D , so sorry for my english!!
Maemo Leste already supports WPA2 Enterprise (https://talk.maemo.org/showpost.php?p=1544808&postcount=104) properly (because it uses wpa_supplicant backend). You do not need any config file on Leste.
On Fremantle, some have been able to connect to eduroam by carefully entering the options, e.g. make sure that the "Manual username" field is filled.
I don't have eduroam where I am, but the N900 can't connect to our WPA2 Enterprise network (https://talk.maemo.org/showpost.php?p=1492488&postcount=3). So I use wpa_supplicant, which works beautifully. As a result, I do have a config, but you also need to remember that WPA2 Enterprise is just an 'umbrella' designation - there are various ways that the network can be configured, e.g. PEAP, TTLS, TLS, etc. So you would need to figure that out first, before you can write an appropriate config
Simplest way ... look at how Android/Windows saves the connection :)
Maemo Leste already supports WPA2 Enterprise (https://talk.maemo.org/showpost.php?p=1544808&postcount=104) properly (because it uses wpa_supplicant backend). You do not need any config file on Leste.
On Fremantle, some have been able to connect to eduroam by carefully entering the options, e.g. make sure that the "Manual username" field is filled.
I don't have eduroam where I am, but the N900 can't connect to our WPA2 Enterprise network (https://talk.maemo.org/showpost.php?p=1492488&postcount=3). So I use wpa_supplicant, which works beautifully. As a result, I do have a config, but you also need to remember that WPA2 Enterprise is just an 'umbrella' designation - there are various ways that the network can be configured, e.g. PEAP, TTLS, TLS, etc. So you would need to figure that out first, before you can write an appropriate config
Simplest way ... look at how Android/Windows saves the connection :)
Thank you for your quick reply. Yeah like I said, I have no problem with Maemo leste connecting to the Wifi...I was just wondering if one could just copy paste the config file from Leste to fremantle..I know it sounds simple...I'm a simple man :D But don't worry, that's not the subject!! (But thanks again for your answer)
I mostly wanted to know how I can take screenshots from the mobile.
And regarding the apps from the repository, The only one I was able to install was conky, but I had no icon in the menu, and the app did not open...
Finally, did someone think about Chroot ? I know it's not the aim of the topic, but I still have ubuntu chroot in the N900 and it works just fine, I was just wondering if it was possible with devuan too!!!
Will they record it on video?
I fully support this as a request. Video record it please.
peterleinchen
2018-10-31, 14:22
Screenshots on fremantle / N900
can be achieved the simplest way:
CTRL-SHIFT-p
and look under MyDocs/.images/Screenshots/
No idea of Leste alreafy supports it but I would guess yes.
Screenshots on fremantle / N900
can be achieved the simplest way:
CTRL-SHIFT-p
and look under MyDocs/.images/Screenshots/
No idea of Leste alreafy supports it but I would guess yes.
I suppose you could try "dd if=/dev/fb0 of=~/capture.raw" or similar... :cool:
Will they record it on video?
Not sure, will check.
Greeting from a new member of this awesome community! Been reading for quite some time about this project and it really got me hooked! As i'd like to visit you guys on this lecture, could you provide some more info about it, tickets if necessary, location, etc. AFAIK, it will be located in Sofia Tech Park so me living near Sofia would be easy to find it. Big thanks!
There are no tickets required - you can just walk in.
Will they record it on video?
Yes, they should.
Hi everyone, I have a question. (I will have many silly questions, so buckle up)
It's been quite some days that I started testing Maemo Leste... Does someone know how to take screenshots ?
And I have another question half-related to maemo leste and WPA2 Entreprise. The mobile is connecting fine to internet, but I can't do it back in Maemo (freemanlte) when it comes to WPA2 entreprise (eduroam style).
I know it has been mentionned here and there on the forum without some good solutions but I was wondering if I could ask here... so the question is : Is there a way to copy-paste the config files, or the WPA_Supplicant config file from leste to freemantle ?
So...yeah, I am still playing with it, I'm a big noob so there is no many things to do with it for now....(I almost forgot everything linux, I had to do a google search just to remember how to do a simple apt-get update). I'm still figuring out how to install and use some apps, but for now, thank you for your hard work!
Sorry I didn't use my awesome translator today :D , so sorry for my english!!
We're going to roll out new n900 images really soon, you should give those new ones a try. They will have much nicer/better wifi (UI) than our old images.
apt install scrot allows you to takescreenshots using 'scrot' (command line tool)
Screenshots on fremantle / N900
can be achieved the simplest way:
CTRL-SHIFT-p
and look under MyDocs/.images/Screenshots/
No idea of Leste alreafy supports it but I would guess yes.
By the way, yes, this also works in Leste.
If you have ubiboot installed then you're already halfway there. There is a new version ubiboot but it isn't required as Leste is booted without an initrd. The new ubiboot does however now include a nice Maemo Leste graphic and a few things preconfigured for it. That reminds me that I should send a pull request to juiceme to set a few more defaults for Leste (described below).
To get Leste running, you'll need to create a new partition (ext4 is fine). Then you can unpack the .tar.gz dist for the N9 (https://maedevu.maemo.org/images/n9/20180425/maemo-leste-1.0-armhf-n9-20180425.tar.gz) to that partition and configure ubiboot.conf to use it. Assuming you'll use slot 5 (https://github.com/juiceme/ubiboot-animatronics/blob/master/ubiboot.conf#L275-L293):
Set G_OS5_INITSCRIPT (https://github.com/juiceme/ubiboot-animatronics/blob/master/ubiboot.conf#L126) to "\/sbin\/preinit" (those are "\" and "/", not Vs)
Set G_OS5_NUM (https://github.com/juiceme/ubiboot-animatronics/blob/master/ubiboot.conf#L277) to "1"
Set G_OS5_PARTITION (https://github.com/juiceme/ubiboot-animatronics/blob/master/ubiboot.conf#L279) to the partition number of your new partition
Set G_OS5_NAME (https://github.com/juiceme/ubiboot-animatronics/blob/master/ubiboot.conf#L280) to "Maemo"
Set G_OS5_1_LABEL (https://github.com/juiceme/ubiboot-animatronics/blob/master/ubiboot.conf#L282) to "Maemo Leste - Linux 4.16" or whatever description you like
Set G_OS5_1_FILE (https://github.com/juiceme/ubiboot-animatronics/blob/master/ubiboot.conf#L283) to "/boot/Maemo/boot/zImage".
I'll write up a guide on the wiki once I've sent that patch to juiceme but in the meantime the above should get you going.
As I already mentioned, Hildon is broken on the N950 so I suspect it might be broken on the N9 too. So don't expect wonders, but USB networking works so that will give you complete access to the Devuan-like system to play around with.
Yep, it works and yep hildon is broken but I couldn't get it to connect via usb with my bionic desktop.
This is a dream come true however, modern linux on handhelds, way to go.
Btw have you managed to run firefox? I think I saw a screenshot somewhere in the thread (I did apt install iceweasel but firefox crashes just after launch.)
Will they record it on video?
They had streaming, so there might be videos too. Until they are released - I've recorded the entire session, here is the video:
https://www.youtube.com/watch?v=ckQAnvAWjqE
There is a blurry minute at the start, as I've switched to manual focus and the screen was too small from the distance I've placed it on :)
P.S. The "RAKIA - connecting people" t-shirts are a nice touch :D
They had streaming, so there might be videos too. Until they are released - I've recorded the entire session, here is the video:
https://www.youtube.com/watch?v=ckQAnvAWjqE
There is a blurry minute at the start, as I've switched to manual focus and the screen was too small from the distance I've placed it on :)
P.S. The "RAKIA - connecting people" t-shirts are a nice touch :D
Link doesn't work for me :confused:
peterleinchen
2018-11-05, 21:38
Neither for me
Oops, sorry, forgot to make it public - should be okay now.
They had streaming, so there might be videos too. Until they are released - I've recorded the entire session, here is the video:
https://www.youtube.com/watch?v=ckQAnvAWjqE
There is a blurry minute at the start, as I've switched to manual focus and the screen was too small from the distance I've placed it on :)
P.S. The "RAKIA - connecting people" t-shirts are a nice touch :D
Thanks for making an additional recording - it's nice to have one available so soon.
There's now also a new status update, covering the changes from September and October (and a bit of November): https://maemo-leste.github.io/maemo-leste-fifth-update-september-october-2018.html
Btw have you managed to run firefox? I think I saw a screenshot somewhere in the thread (I did apt install iceweasel but firefox crashes just after launch.)
No, I think it crashes on start, I didn't yet try to figure out why. I think it used to work, though.
Android_808
2018-11-06, 21:28
Regarding the latest update, I'm guessing the Qt5 build no longer suffers from the issues we had with Fremantle needing to ship a seperate libX11.so.6 built with --with-xcb. It needed a seperate lib because xcb broke keyboard support with other apps. I guess it would be okay unless someone tries install a Fremantle closed source deb.
Also, as OMP was mentioned, in keeping with the more modern take on Qt, would it also be worth porting qt-components-hildon?
Regarding the latest update, I'm guessing the Qt5 build no longer suffers from the issues we had with Fremantle needing to ship a seperate libX11.so.6 built with --with-xcb. It needed a seperate lib because xcb broke keyboard support with other apps. I guess it would be okay unless someone tries install a Fremantle closed source deb.
Also, as OMP was mentioned, in keeping with the more modern take on Qt, would it also be worth porting qt-components-hildon?
freemangordon should give the authorative answer here, but I haven't seen this issue so far.
I am assuming you mean: https://github.com/marx1an/qt-components-hildon - openmediaplayer doesn't seem to depend on it, though, right?
I haven't toyed with qt-component-hildon myself - but I assume it will make sense for someone to port them. It might not even be a long of work.
Android_808
2018-11-11, 23:22
No OMP doesn't need it. It's used by cutenews, cuteradio and qml-browser.
I suggested it as there was a push for mobile devices to make use of qml and qtquick. On N900 though performance wasn't always that great iirc because of a driver issue.
The openfest talk is now also uploaded in official form: https://www.youtube.com/watch?v=WT1hwtEPt7o
Random screenshot of the day, initial compile-fixed bringup of hildon-application-manager (otherwise completely untested):
https://wizzup.org/raspi-ham.png
endsormeans
2018-11-24, 17:10
great presentation.
Loved the shout-out for the n8x0's ...hahaha :D
great presentation.
Loved the shout-out for the n8x0's ...hahaha :D
Yeah I really loved the presentation. I wish I had more skills to help you. I guess I will keep on stress testing the N900 :rolleyes:
Very good slides and very well presented. Just bought more N900 hundreds in hope for Maemo Leste. If you need I could probably send you couple if it is of any help.
I'm not very tech-savvy so maybe someone could explain me if the Maemo Leste on Nexus 5 is using the same method as Sailfish or Ubuntu? Is there some sort of MIR / libhybris or whatever they are named which bind the android blobs with the top layer and make things run on this hardware (If I understand things correctly that is). I had my Nexus 5 running Ubuntu but it is half backed, Jolla is running smooth but smacking Cyanogenmod 13 in the days of LineageOs 16 doesn't convince me but that's maybe my lack of knowledge. Not trying to point fingers at any of the mentioned OS and especially devs working on them. Just trying to understand everything with my small question/rant ;)
I'm not very tech-savvy so maybe someone could explain me if the Maemo Leste on Nexus 5 is using the same method as Sailfish or Ubuntu? Is there some sort of MIR / libhybris or whatever they are named which bind the android blobs with the top layer and make things run on this hardware (If I understand things correctly that is).
No, mainline Linux kernel is used for Nexus 5, which has Freedreno support for 3D graphics, so there is no libhybris involved in Leste.
endsormeans
2018-11-25, 21:59
Yup...
Helluva Guy..
Fred Reno ...
:D
Owes me $50 bucks
November update: https://maemo-leste.github.io/maemo-leste-sixth-update-november-2018.html :) (and new website theme: thank you parazyd!)
I'm not very tech-savvy so maybe someone could explain me if the Maemo Leste on Nexus 5 is using the same method as Sailfish or Ubuntu? Is there some sort of MIR / libhybris or whatever they are named which bind the android blobs with the top layer and make things run on this hardware (If I understand things correctly that is)
No, mainline Linux kernel is used for Nexus 5, which has Freedreno support for 3D graphics, so there is no libhybris involved in Leste.
OK, then it is a bit better alternative than I actually thought! :)
Now I wonder would it be worthwhile to build SFOS on that base, skipping the adaptation libraries alltogether?
Are there some devices (sensors, radio, wlan, bt, ...) that are not working with Nexus5 mainline kernel?
endsormeans
2018-12-05, 15:17
You see now why I am so keen on leste on nexus 5...eh juice?
Fred Reno rocks.
Great guy...
Owes me 50 bucks...
princefakhan
2018-12-07, 08:20
gosh darn it! If only my N900 booted up properly so I could test it. welp!
freemangordon
2018-12-07, 16:15
FYI
https://necunos.com/blog/necuno-solutions-and-maemo-leste-collaboration/
endsormeans
2018-12-07, 16:39
NOW Necunos has my attention.
Lets hope they follow through.
I would be prepared to buy one if they do.
Well I said
Now I wonder would it be worthwhile to build SFOS on that base, skipping the adaptation libraries alltogether?
Are there some devices (sensors, radio, wlan, bt, ...) that are not working with Nexus5 mainline kernel?
To where @endsormeans replied like
You see now why I am so keen on leste on nexus 5...eh juice?
Fred Reno rocks.
Great guy...
Owes me 50 bucks...
Which still does not answer my question... :(
endsormeans
2018-12-07, 17:05
https://www.youtube.com/watch?v=PSjjZM1Ovs0
https://www.youtube.com/watch?v=PSjjZM1Ovs0
I don't understand how this is relevant?
I'm not familiar with these comedians.
Hi everybody testing Leste (N900). Back again whit my questions :D
I noticed a small issue with the icons on the desktop when the phone boots.
So, as soon as the phone boots, when I click on the icons shortcuts (settings or terminal) the phone freezes. This happens only when it boots and the screen is idle. I noticed that going to the menu before and reverting back to the desktop seems to solve the issue.
So uhm yeah, that's it. Now my question is about Increasing the filesystem size as described here https://leste.maemo.org/Nokia_N900#Increase_filesystem_size. I test Leste with a 4GB card, is there a way to increase the file system in another system than Linux ? Obviously I am on windows :D , I know I can use a Live distro to do it, but yeah, I just wanted to ask...we never know!!! If it's not possible, never mind, I will do it with linux. Is there a way to do it with maemo ?
What size do I need to specify if I want to enlarge to the max capacity of the card!?? (4GB)
Thanks in advance :cool: and have a good wknd!
Special Lima/Mali update: https://maemo-leste.github.io/maemo-leste-lima-works.html
(Also: we're on twitter now: https://twitter.com/maemoleste)
Hi everybody testing Leste (N900). Back again whit my questions :D
I noticed a small issue with the icons on the desktop when the phone boots.
So, as soon as the phone boots, when I click on the icons shortcuts (settings or terminal) the phone freezes. This happens only when it boots and the screen is idle. I noticed that going to the menu before and reverting back to the desktop seems to solve the issue.
This is a known and unfortunate problem. It happens once or twice on boot, and not anymore after that (to be clear: just be patient, it will unfreeze). I'm sure we'll be able to fix it eventually, but it might take some time, and hasn't been a priority. In general, the performance isn't that great either.
So uhm yeah, that's it. Now my question is about Increasing the filesystem size as described here https://leste.maemo.org/Nokia_N900#Increase_filesystem_size. I test Leste with a 4GB card, is there a way to increase the file system in another system than Linux ? Obviously I am on windows :D , I know I can use a Live distro to do it, but yeah, I just wanted to ask...we never know!!! If it's not possible, never mind, I will do it with linux. Is there a way to do it with maemo ?
What size do I need to specify if I want to enlarge to the max capacity of the card!?? (4GB)
Thanks in advance :cool: and have a good wknd!
There should be a script in /etc/ to resize the card. (At least in the latest image)
Holy smokes! There is actually hope for a new maemo like experience with a decent price tag for the device. 2019 might be the Linux smartphone year ;)
Wasmachinemann-NL
2018-12-09, 11:33
Very outlandish, but will this be ported to the ReadyFx?
freemangordon
2018-12-09, 14:18
Very outlandish, but will this be ported to the ReadyFx?
ReadyFx what?
ReadyFx what?
It is an attempt to create a phone with hardware keyboard. Discussion about it in this thread: http://talk.maemo.org/showthread.php?t=100554
endsormeans
2018-12-09, 18:04
Readyfx??
Huh...
Well if that is the case ...
And there is a growing X-mas list of obscurities...
I want a port for the Mylo and the Vic 20, Santa...
https://i.dailymail.co.uk/i/pix/2015/12/08/11/2F2A929800000578-3350797-image-a-70_1449575448309.jpg
(the moment of terror..)
freemangordon
2018-12-09, 21:03
It is an attempt to create a phone with hardware keyboard. Discussion about it in this thread: http://talk.maemo.org/showthread.php?t=100554
As long as device is supported by upstream linux, leste will just work. To the extend it works at all, ofc :)
I briefly read through the above thread and somehow was left with the impression that this device-to-be-someday will use android GPU drivers and libhybris. If that's the case (no FOSS GPU drivers or no GPU drivers that work with upstream kernel) then it doesn't really make sense to put leste on it, hildon-desktop rendering with 1-3 FPS is not something I would call a good user experience.
I tried to get maemo leste running on a pcduino3b. Therefore I used the rootfs from the allwinner image and compiled the lime2-linux kernel from leste git.
But I get a boot loop caused by the watchdog. On the first look it seems that the xorg-server doesn't find a screen. Is there some possibility to deactivate the watchdog?
I tried to get maemo leste running on a pcduino3b. Therefore I used the rootfs from the allwinner image and compiled the lime2-linux kernel from leste git.
But I get a boot loop caused by the watchdog. On the first look it seems that the xorg-server doesn't find a screen. Is there some possibility to deactivate the watchdog?
I am assume you're using the right dts. Try booting with a mouse and monitor plugged in - you may be hitting this: https://github.com/maemo-leste/bugtracker/issues/204
What branch did you use for the lime2-linux kernel? The one we ship with our latest images is not using lima (lima also might require dts changes and some .config changes that are not yet online)
In short - are you trying to get lima to work as well?
We were planning to make lima images soon, but it (lima) is still a bit unstable, so it might not very usable/clever to do so.
This device? https://www.sparkfun.com/products/retired/13707
EDIT: I would prefer to help debugging over IRC or over our mailing list (ML preferred), btw. I check both way more often than tmo. :)
I am assume you're using the right dts. Try booting with a mouse and monitor plugged in - you may be hitting this: https://github.com/maemo-leste/bugtracker/issues/204
At the moment there is no lvds lcd with touch installed. I connected a usb mouse, usb keyboard and a hdmi monitor.
I need to figure out what is needed to make the hdmi as default screen. I guess I need to set it in the kernel and maybe in xorg.
But for a headless setup it would be nice to stop the rebooting behaviour.
What branch did you use for the lime2-linux kernel? The one we ship with our latest images is not using lima (lima also might require dts changes and some .config changes that are not yet online)
I am using linux-4.18.y branch.
In short - are you trying to get lima to work as well?
I would like to help to get it running. However I need to learn basic steps first like image creation and get a feeling for maemo-leste.
I also want to use the pcduino3b as my build maschine.:o
So I don't need gpu power right now, but for sure it is nice to have.
We were planning to make lima images soon, but it (lima) is still a bit unstable, so it might not very usable/clever to do so.
Ok I see.
This device? https://www.sparkfun.com/products/retired/13707
Yes exactly.
EDIT: I would prefer to help debugging over IRC or over our mailing list (ML preferred), btw. I check both way more often than tmo. :)
I tried IRC but I have no talking power, so I will use ML in the future.
At the moment there is no lvds lcd with touch installed. I connected a usb mouse, usb keyboard and a hdmi monitor.
I need to figure out what is needed to make the hdmi as default screen. I guess I need to set it in the kernel and maybe in xorg.
But for a headless setup it would be nice to stop the rebooting behaviour.
Agreed. I will try to at least fix that mce problem soon.
I am using linux-4.18.y branch.
This is just plain linux branch, without any of our patches. ;-)
You really need our .config too. Let me try to put this online soon.
I would like to help to get it running. However I need to learn basic steps first like image creation and get a feeling for maemo-leste.
I also want to use the pcduino3b as my build maschine.:o
So I don't need gpu power right now, but for sure it is nice to have.
The first step would be to mount the sd card/image, and do:
# mv /mnt/pcd/etc/init.d/dsme /mnt/pcd/etc/init.d/dsme_
Then the device will no longer reboot. From there you should already have network, ssh, and maybe a console on HDMI.
I tried IRC but I have no talking power, so I will use ML in the future.
Please, join again. I thought there were no limitations in place anymore. Send me a message on IRC if you still can't write.
CactusinGasmask
2019-01-10, 18:38
Hey, is there a way to run it in tty-only mode, without xorg?
Hey, is there a way to run it in tty-only mode, without xorg?
One such way is right in the post above yours, viz.
The first step would be to mount the sd card/image, and do:
# mv /mnt/pcd/etc/init.d/dsme /mnt/pcd/etc/init.d/dsme_
CactusinGasmask
2019-01-10, 22:22
One such way is right in the post above yours, viz.
Oh, ok. It works, thanks.
Now, the question is: how to enable fn key combinations?
December 2018 update!
Sorry for the delay...
https://maemo-leste.github.io/maemo-leste-seventh-update-december-2018.html
Oh, ok. It works, thanks.
Now, the question is: how to enable fn key combinations?
Silly answer: use xorg. hildon-input-method makes those work in X.
Awesome progress! Especially after hearing of postmarket OS is somewhat stalled.
The day Maemo Leste will run somewhat well on Droid 4 will make very happy. I got it to try Sailfish with a keyboard, but the port is so far from usable I quit and put Android LineageOS on it.
How well Android runs? I could rant a long time. In short:
Battery runtime fluctuates between 5 and 40 hours in idle state.
Sometimes even keyboard input lags.
Spontaneous reboots,spontaneous loss of wifi functionality (but hotspot still works ...)
Your progress gives me hope for having great operating system, not limited by an ancient kernel, not by the 256MB ram of the N900 and not dependent on support for proprietary components.
Thank you for your admirable dedication and impressive work!
Especially after hearing of postmarket OS is somewhat stalled
postmarketOS is not stalled in any way. It may even be moving slightly faster than Leste because it has a larger team of developers/hackers working on it. See https://blog.postmarketos.org
That said, Leste is my number 1 choice without a doubt.
I know that PostmarketOS has a larger team behind it, but especially the last blogpost on the site you linked invoked that idea:
We are stuck in a proof-of-concept stage, and it's time to get out.
This quote is followed by ideas to do that and by a list of devices where boot or hardware activation bugs were fixed. They use an N900 and made "a few usability improvement patches" which, if you click on the link, consist of changed wallpapers, twice, a shell replacement and improvements for running i3wm, which is not general user friendly in any way.
From my perspective it seems they are stuck in the playground and lost focus for their goals. If I got that wrong I am happy to be corrected.
The progress in Maemo Leste seems way more tangible and I applaud the small development team for that.
I've just watched the FOSDEM Lightning Talk video which is now online. Great job. Congrats!
https://fosdem.org/2019/schedule/event/maemo_leste_mobile/
Aargh. N900 can't open the media. How annoying. Why to put it in such form or does some player on N900 play it?
Aargh. N900 can't open the media. How annoying. Why to put it in such form or does some player on N900 play it?
Try this one: https://video.fosdem.org/2019/H.2215/maemo_leste_mobile.mp4
Nope. That didn't work either. I have the default player. Should I use something else instead? What is a better player? Or is it possible to try still some other format?
Ok. Mplayer did it. I installed also smplayer for it to be easier for me. Thanks once more wizzup.
You can also use that option in ~/.mplayer/config file for performance:
lavdopts="gray=1:skiploopfilter=all:skipframe=bidir:fast=1:e c=1:er=0:bitexact=1:skipidct=all:sb=5:st=5"
and for fast play in the same file:
af="scaletempo=stride=16:overlap=0.9:search=4,format=s 16le"
for more options, man mplayer in web search
In the end it was Kmplayer with mplayer with decoder code pack which gave both audio and video.
Can't wait to get leste running fast and smoothly on N900!
Wasmachinemann-NL
2019-03-11, 12:00
In the end it was Kmplayer with mplayer with decoder code pack which gave both audio and video.
Can't wait to get leste running fast and smoothly on N900!
And I can't wait for Leste to get ported to the Fxtec!
I understood there would be soon news from leste but haven't seen any since january.
You were right!
New update: https://maemo-leste.github.io/maemo-leste-eight-update-january-february-2019.html
Did I understand correct that Alpha release will be in the end of the year? That would be cool. And nice to see my own work on news. First time my work on any news I think.
Android_808
2019-03-12, 06:52
I think it would be interesting to compare Fremantle graphics stack against Leste to see what improvements/ regressions have been made. I'm thinking to see if it's worth extending the GL usage by Hilton as previously it didn't do a lot.
I think it would be interesting to compare Fremantle graphics stack against Leste to see what improvements/ regressions have been made. I'm thinking to see if it's worth extending the GL usage by Hilton as previously it didn't do a lot.
If you have some time to spare and would like to help out, we could use help figuring out what patches clutter 1.x needs (if any) from clutter 0.8. The clutter 0.8 version of h-d runs smooth, but the clutter 1.x one does not. There are some deprecated functions that we're using in our clutter 1.x port of hildon-desktop that we should not use anymore, and I think we might have run into a bug with cogl (that may go away if we stop using deprecated functions).
None of us have had a lot of time to work on this, so if you have some time and want to look at GL usage of hildon, that'd be welcome... :)
Android_808
2019-03-12, 18:27
Fmg did far more work on clutter than me when working on gtk3 port. The clutter issue I had was the deprecated functions were replaced with now deprecated functions which were replaced by functions with no decent examples. Even within mutter.
I'm working on some other projects at the moment but if I get time I'll have a look.
Did I understand correct that Alpha release will be in the end of the year? That would be cool. And nice to see my own work on news. First time my work on any news I think.
The first Alpha should be out way sooner. What you saw was a fluke / page that should not have been there with a stub date.
Even better! Thanks for update.
Github page for the Droid 4 repo seems to be down?
https://github.com/maemo-leste/droid4-linux
Would be glad to mirror it somewhere if it can be recovered.
Github page for the Droid 4 repo seems to be down?
https://github.com/maemo-leste/droid4-linux
Would be glad to mirror it somewhere if it can be recovered.
Works for me... maybe there was a temporary outage?
freemangordon
2019-03-27, 14:15
Works for me... maybe there was a temporary outage?
It is broken for me as well, but well, I guess it was a just matter of time things to start breaking up since M$ bought github.
Github page for the Droid 4 repo seems to be down?
https://github.com/maemo-leste/droid4-linux
Would be glad to mirror it somewhere if it can be recovered.
FYI, related to droid4, I just posted some more droid4-kexecboot instructions to github. It might be of interest to folks who no longer need the old stock install on droid 4 and want just basic LineageOS images.
The instructions also contain some more info on how to use mmcblk1p25 emstorage 8GB partition for Linux distros. See files PARTITIONS and INSTALL at:
https://github.com/tmlind/droid4-kexecboot
Probably best to stick to the micro-SD for Maemo Leste install images for now though.. But there should not be anything stopping people installing Maemo Leste to the mmcblk1p25 partition :)
FYI, related to droid4, I just posted some more droid4-kexecboot instructions to github. It might be of interest to folks who no longer need the old stock install on droid 4 and want just basic LineageOS images.
The instructions also contain some more info on how to use mmcblk1p25 emstorage 8GB partition for Linux distros. See files PARTITIONS and INSTALL at:
https://github.com/tmlind/droid4-kexecboot
Probably best to stick to the micro-SD for Maemo Leste install images for now though.. But there should not be anything stopping people installing Maemo Leste to the mmcblk1p25 partition :)
Thanks - this is great!
On a related note, Parazyd gave a talk at the Devuan conference yesterday - using a Droid 4. Presentation and demo in one:
https://parazyd.org/pub/tmp/photo/IMG_20190407_134644.jpg
https://parazyd.org/pub/tmp/photo/IMG_20190407_135349.jpg
Freemangordon has been doing a lot of work on connui-cellular, the modem framework and UI that we need in place to integrate ofono, the work has now been packaged. It lacks any ofono integration (I'm supposed to write that soon), but here are two screenshots showing it in action:
(No sim card detected; status applet starts)
https://wizzup.org/leste-connui-initial.png
(Phone control panel applet)
https://wizzup.org/leste-connui-initial-2.png
Woohoo - we really are getting there.
Next for this will be ofono support for connui-cellular and writing the ofono icd plugin for gprs data.
Wasmachinemann-NL
2019-04-15, 11:58
Stupid question: can we port things like osso-notes to Leste even though it's closed source?
freemangordon
2019-04-15, 13:09
Stupid question: can we port things like osso-notes to Leste even though it's closed source?
The biggest issue would be that it is armel binary, but we decided to drop armel support recently. The reasoning being that there is no working armel SGX driver.
mr_pingu
2019-04-16, 21:04
Which device has currently the best support, droid 4 or n900? In other words, should I buy a droid4?
endsormeans
2019-04-16, 21:35
Good question.
Personally I am waiting for more stable audio in Leste...
out of either the n900 or the nexus 5
I have a keen desire to utilize rakarrack and other real time effects processors...
Until then ...it is Fremantle on my n900 running Gnome Tool Kit Guitar Effects Processor (GTKgep is less a mouthful to say)
And messing with attempted containerization of effects processors on a nexus 5 with buntu touch
Good question.
Personally I am waiting for more stable audio in Leste...
out of either the n900 or the nexus 5
I have a keen desire to utilize rakarrack and other real time effects processors...
Until then ...it is Fremantle on my n900 running Gnome Tool Kit Guitar Effects Processor (GTKgep is less a mouthful to say)
And messing with attempted containerization of effects processors on a nexus 5 with buntu touch
Hi Endsormeans. I will take my N900 out of the drawer, dust it off and charge it up if you can tell me how to get GTKgep to work on it. Thanks!
endsormeans
2019-04-17, 15:16
It is easier to get running than most things around here.
Of course.
You bet mscion.
Give me about ....hm...
give me a bit.
a few days maybe..
at worst it may be longer ..
I am just dealing currently with a few things.
It isn't difficult to get GTKgep installed and running..
and shouldn't take long before you are obliviously ignoring everything else around you whilst playing guitar (or whatever else electrified) pumping it through GTKgep on your n900 and outing it to either headphones / earbuds or your computer or your mixer or your amp
Which device has currently the best support, droid 4 or n900? In other words, should I buy a droid4?
Each has its own pros and cons. Buy both of them if you can afford it. Droid4 is a bit more future-proof, I guess, due to its CPU/RAM.
Main Droid 4 problem, - currently no acceleration, which slows down hildon. However this is being worked on.
N900 is let down by the ram/cpu combo mainly, and then getting audio from voice calls is going to be another PITA aiui, but otherwise support for it is really good.
endsormeans
2019-04-17, 16:44
hm...
interesting.
but could it handle GTKgep without blowing the n900 audio?
that is my only drawback to using Leste on n900 right away...
It looked too sketchy from the mention of audio not quite there yet.
moodroid
2019-04-17, 17:31
So, at a guess, we might get a Droid 4 version that can be used for phone calls/SMS first, but it might be without acceleration?
Also, does anyone know how practical it would be to support the Photon Q with ML (or PMOS) as I've not seen it mentioned, and it has slightly higher specs.?
Stupid question: can we port things like osso-notes to Leste even though it's closed source?
Your best shot is to reverse engineer it. We might be able to make fremantle-in-a-chroot work, but it's not a priority. Or a leste armel build, but there's a lot of things that might just not work.
hm...
interesting.
but could it handle GTKgep without blowing the n900 audio?
that is my only drawback to using Leste on n900 right away...
It looked too sketchy from the mention of audio not quite there yet.
I don't think it's easy to blow up the audio at all. And you can just use the HP instead of the speakers and then there is no chance to damage anything.
Which device has currently the best support, droid 4 or n900? In other words, should I buy a droid4?
I think the N900 has the best support, but the Droid 4 is more likely to get working voice calls soon. The Droid 4 will be great once we have PowerVR working on there. Probably a few months out, though. You could also check out / wait for the pine64 phone.
So, at a guess, we might get a Droid 4 version that can be used for phone calls/SMS first, but it might be without acceleration?
Also, does anyone know how practical it would be to support the Photon Q with ML (or PMOS) as I've not seen it mentioned, and it has slightly higher specs.?
Correct regaring Droid 4. N900 can also do SMS though, calls are just annoying with audio routing, but that too could work in the near future.
No idea on the Photon, but I think we have a lot of devices we have to worry about already, so I am not personally inclined to work on more, but you could try to make it work. Or help the postmarketOS people with packaging all of Maemo Leste - https://gitlab.com/postmarketOS/pmaports/issues/234
Hi,
PinePhone support is coming together. Thanks to the work done by Pine64 for making the device, giving us devkits, but also postmarketOS, UBports and KDE Plasma guys for working on the drivers.
Here's a quick video (sorry for the focus): https://wizzup.org/pinephone-hd-initial.mp4
Some screenshots:
https://wizzup.org/pinephone-rot-1.jpg
https://wizzup.org/pinephone-rot-2.jpg
https://wizzup.org/pinephone-rot-3.jpg
https://wizzup.org/pinephone-rot-4.jpg
https://wizzup.org/pinephone-rot-5.jpg
In 'normal' rotation:
https://wizzup.org/pinephone-initial-1.jpg
https://wizzup.org/pinephone-initial-2.jpg
https://wizzup.org/pinephone-initial-3.jpg
szilveszter.domotor
2019-05-17, 12:54
hmmmm sounds interesting, is there any chance to make gemini pda supported :) I would give a try to leste
carlosgonz
2019-05-18, 00:56
yes, i am interested on gemini-p.d.a and maemo-7
hmmmm sounds interesting, is there any chance to make gemini pda supported :) I would give a try to leste
yes, i am interested on gemini-p.d.a and maemo-7
Someone did a port to the Gemini PDA already, based on the stock kernel and libhybris, see https://maemo-leste.github.io/maemo-leste-second-update-april-2018.html
That said, 'official' support (whatever that means) might not follow until there is decent mainline support. Currently I've been doing quite some hardware enablement/testing and I don't want to do more of it, but rather focus on software.
There is no image for it yet, but I assume we could help provide such an image.
It's been too long since a status update post, one will follow in the next few days.
szilveszter.domotor
2019-05-22, 16:54
Someone did a port to the Gemini PDA already, based on the stock kernel and libhybris, see https://maemo-leste.github.io/maemo-leste-second-update-april-2018.html
That said, 'official' support (whatever that means) might not follow until there is decent mainline support. Currently I've been doing quite some hardware enablement/testing and I don't want to do more of it, but rather focus on software.
There is no image for it yet, but I assume we could help provide such an image.
It's been too long since a status update post, one will follow in the next few days.
Would be very nice, Gemini by default include a flasher where you can select the downloadable android, linux + sailfish ... If you can create an image for their flasher It would be my 3rd boot option :)... Gemini is a robust big device and fully open and friendly.
I just received my device had no chance to dig deeper into it, but together with my n900 one of the best choice as far i can see now...
I tried to install Maemo -Leste on Nokia n9 but seems like all files are corrupted or broken.. whenever I tried to extract the file on pc it always gives me an error at the end of extraction.
I followed the steps of sailfish installation and I also flash the latest ubiboot but still not working... just let me know is there any possible way to install on my Nokia n9. if anybody has the working file of Maemo-Leste please share with me and also guide me in the correct way of installation.
Please help me guys, I want to give a try to Maemo-Leste.
Thank You :)
I tried to install Maemo -Leste on Nokia n9 but seems like all files are corrupted or broken.. whenever I tried to extract the file on pc it always gives me an error at the end of extraction.
I followed the steps of sailfish installation and I also flash the latest ubiboot but still not working... just let me know is there any possible way to install on my Nokia n9. if anybody has the working file of Maemo-Leste please share with me and also guide me in the correct way of installation.
Please help me guys, I want to give a try to Maemo-Leste.
Thank You :)
Hi!
I think you made a github issue too - I asked Parazyd and wicket to check it out. Just to be clear: Maemo Leste on the N9 is very alpha, way more than on Droid4, N900 or on Allwinner devices. If you want to try Maemo Leste, a virtual machine may be the easiest first step.
Thanks for figuring out the extraction issue though, I'm sure we'll have that part fixed soon.
Hi!
I think you made a github issue too - I asked Parazyd and wicket to check it out. Just to be clear: Maemo Leste on the N9 is very alpha, way more than on Droid4, N900 or on Allwinner devices. If you want to try Maemo Leste, a virtual machine may be the easiest first step.
Thanks for figuring out the extraction issue though, I'm sure we'll have that part fixed soon.
Thnx Wizzup for your quick response.
well right now I only have Nokia n9 with me so, Will you please suggest me the best alt_os for Nokia n9 in 2019. I tried android and sailfish... if u know some other OS which is really good and stable so please help me out.
Thank you :).
szilveszter.domotor
2019-05-28, 10:23
IF you have a working distribution for Gemini please share with us the the kernel and secondary bootloader image (linux.bin, debian_boot.img). Unfortunately as far I have my experiences the flashing the only possibility to manage the multiboot properly and eventually both avaiable distrobutions has some conflict by default in ARM64 apt (debian with libreoffice, kali had some libraries, which seemed to be system library)... But if you can make an image for gemini users, you can use eighter the debian/kali/sailfish to have the wifi driver,audio etc what required, I am not sure if leste in a phase where we can talk about the cellular functionality, with linux wifi would be enough max 4g modem could be handy.
I have read your comment and you told someone "managed" to install it if you have the flash image just send the link across :)
IF you have a working distribution for Gemini please share with us the the kernel and secondary bootloader image (linux.bin, debian_boot.img). Unfortunately as far I have my experiences the flashing the only possibility to manage the multiboot properly and eventually both avaiable distrobutions has some conflict by default in ARM64 apt (debian with libreoffice, kali had some libraries, which seemed to be system library)... But if you can make an image for gemini users, you can use eighter the debian/kali/sailfish to have the wifi driver,audio etc what required, I am not sure if leste in a phase where we can talk about the cellular functionality, with linux wifi would be enough max 4g modem could be handy.
I have read your comment and you told someone "managed" to install it if you have the flash image just send the link across :)
Hi szilveszter,
Below are the link of Maemo-Laste of N9, N950 & N900. I used to flash in my Nokia n9 with N9 and N950 files but just got stuck with an error. Just for the cross check I also downloaded the file of n900 but the issue was same.. when I tried to extract the file at the end it gives me an error. I faced the same issue with the .img file.
N9: https://maedevu.maemo.org/images/n9/20190315/
N900: https://maedevu.maemo.org/images/n900/20190225/
N950: https://maedevu.maemo.org/images/n950/20190225/
_____________
Thanks to Maemo-Laste team they help me to boot into Maemo-laste..
it is very alpha for Nokia n9, I just booted into Maemo but there is only Menu icon in the left center of the display nothing else. I think I need to wait for the stable version. :)
Thank You :)
meemorph
2019-06-06, 14:34
...
Thanks to Maemo-Laste team they help me to boot into Maemo-laste..
it is very alpha for Nokia n9, I just booted into Maemo but there is only Menu icon in the left center of the display nothing else. I think I need to wait for the stable version.
Thank You
I can confirm this and many log messages that watchdogs could not be killed.
endsormeans
2019-06-06, 14:41
God I love your username.
Reminds me of MR. Meeseeks
https://simg.nicepng.com/png/small/148-1487177_mr-meeseeks-rick-and-morty-mr-meeseeks-png.png
The only one better would be "Give us a kiss"
Thanks to Maemo-Laste team they help me to boot into Maemo-laste..
it is very alpha for Nokia n9, I just booted into Maemo but there is only Menu icon in the left center of the display nothing else. I think I need to wait for the stable version.
Better yet, join the effort ... if you can help with some of the work, then that'd help a lot
I just read a bit about kernel 5.1 and the advantages of it. Maemo Leste is 5.0 I believe. In 5.1 there was some mention of ability to use persistent flash memory as ram. Does anybody know better and could it give any new possibilities with N900 (like more ram somehow)? I really don't understand that stuff but just spotted the news.
I just read a bit about kernel 5.1 and the advantages of it. Maemo Leste is 5.0 I believe. In 5.1 there was some mention of ability to use persistent flash memory as ram. Does anybody know better and could it give any new possibilities with N900 (like more ram somehow)? I really don't understand that stuff but just spotted the news.
Well yes and no :)
The new memory mode is designed to be used with a fast persistent memory and emmc is not really that fast to use... the erase cycle actually makes it extremely slow...
So it might be possible but it'd slow down your device to glacial speeds :eek:
...emmc is not really that fast to use... the erase cycle actually makes it extremely slow...
Naive question: I guess the same can be said for the uSD ?
endsormeans
2019-06-24, 23:37
No question is naive ...
Either it is :
A- an honest valid question.
B- A ridiculously hilarious question.
Or
C- outright dumb one.
Yours and Maemish's question is an honest valid one.
*
In the most rudimentary of parallels to keep it as close to home as possible...
think of it like the n8x0's that have 128 mb of ram WITH the ability to give a tiny bit of oomph with up to an additional 128 mb of ram from allocating "virtual memory" to it.
It helps some ..sure.
"allocating" can help a bit..
can help a lot even...
But it only helps with processes and progs which normally would handle an expected load from the device in question
For example...
You can't run world of warcraft (I do not play ...I like more high brow like Neverwinter nights) on a pentium I ....no matter how much virtual fictitious ram you manage to allocate. (along with a plethora of other valid reasons as well)
BUT ...the processes and progs that would normally be able to run on the pentium I (perhaps even a few borderline slower heavier ones too)..you could run a few more of at the same time...or they would be a bit snappier ...
But that would be the extent of your ability..
In short.. nothing takes the place of dedicated ram
So if one were hoping to double or triple or whatever ...their ram in such a way...
you can fake out the system only so far...
but when process(es) or progs which are beyond the ability for the system to handle normally, need "actual" serious ram to run and look to the availability to utilize it...
It won't be pretty as your device tries its best to accommodate and does this in your hand instead
https://media.giphy.com/media/6we45Lecki2ME/giphy.gif
*
(calls it like I sees it...personally I aim for B or C...A is stultifying -ly boring....since it is predictable and has usually been asked 1000 x before...so ask something way out there...may have a "eureka!" come of it...like a battery mod using electricity from potatoes ...way out there..outright hilarious and borderline dumb / mad...but it would probably work...just need a lot of potatoes or one giant potato hooked up to it...BTW- We REALLY need this mod...For years we have had the super smart solving issues ...and we are now hitting the brick walls...its time to bring in the mad and crazy folks to break through those walls with their ingenious ideas and pulpy bodies ...and solve the unsolvable ...)
Just a teaser...
Nokia N900:
https://wizzup.org/leste-n900-cellular-v0.1.png
QEMU AMD64 VM with USB passthrough modem:
https://wizzup.org/leste-cellular-operator-name-home.png
Would so much like to read an update. Have there been yet phone calls made with ofono? And other news too about leste. In their page their talked of monthly news but I think that wasn't reasonable idea. So much to do. Would just love that they would get it done, there would be an updated linux system.
Would so much like to read an update. Have there been yet phone calls made with ofono? And other news too about leste. In their page their talked of monthly news but I think that wasn't reasonable idea. So much to do. Would just love that they would get it done, there would be an updated linux system.
Trying to get one written. Been very busy, hopefully one or two more days.
More teasers (yes, it's not well integrated.):
https://wizzup.org/leste-sms-telepathy-ring-1.png
endsormeans
2019-08-14, 23:45
You're doing God's work ...my good man.
I should know...
He told me so yesterday....
Of course our conversation had absolutely nothing to do with the fact I have been sleep deprived and chocolate high'd for 3 days straight...
Update post time!
https://maemo-leste.github.io/maemo-leste-ninth-update-march-till-august-2019.html
Thank you! And thank you for putting time to give this detailed and thorough update. To hear the amount of work you have done and how much work it requires is eye opening. I will try to think a way to contribute to the project.
This makes me to buy Motorola Droid 4 to run Maemo, it seems that it run SailfishOS too, so my only guestion is can I run both in same phone, just switching in boot?
vBulletin® v3.8.8, Copyright ©2000-2025, vBulletin Solutions, Inc.