<missMyN900> I have been playing with ML for some months now and was amazing to be able to see and interact with Hildon again after all these years :)
<missMyN900> I have some questions, observations and suggestions
<missMyN900> I have been trying a lot of web browsers to try to find something that is somewhat usable for at least a little bit of daily web browsing but I have not found anything that works on ML
<missMyN900> on pmOS the best I have found is Falkon (which I also use on my Debian desktop), which has good touch screen support and is quite fast
<missMyN900> unfortunately Falkon cannot be installed currently on ML/Devuan because it depends on kf5-walletmanager, which cannot be installed for some reason (systemd dependence?)
<missMyN900> I saw on GitHub that there were some plans to hildonize surf IIRC
ruleh has quit [Ping timeout: 256 seconds]
<missMyN900> I would suggest modifying netsurf-gtk instead. 3.10 has a new GTK GUI (both 3 and 2 are supported, by the way) and has been packaged for chimaera, which is quite suitable for small screens
<missMyN900> the only thing it needs is support for touch screen scrolling and pinch to zoom. I think it would be a better candidate for the less powerful Maemo Leste devices (especially N900) as well due to its extremely low RAM consumption
<missMyN900> furthermore, if desired it can be hildonized more easily because it can still be compiled against GTK2
<Wizzup> How modern is netsurf?
<missMyN900> it is under active development
<missMyN900> @Wizzup in what way?
<Wizzup> Does it support js?
<missMyN900> JS is experimental and disabled by default
<missMyN900> still, I thnk it would make for a good default browser. People can always use Falkon (or perhaps Firefox with patches) for websites that do not work in netsurf
<missMyN900> the web experience is going to be limited on the N900, Droid 4 etc anyway
<missMyN900> when I was using Opera Mini (or was it Mobile?) back in 2013 there were already some issues
<missMyN900> same for MicroB, of course
<missMyN900> I cannot imagine running a modern WebKit or Blink based browser with 256 MB of RAM
<missMyN900> running Chromium on OpenBSD on my 2 GB laptop was already not great
<missMyN900> with a few tabs open it would start to swap
<missMyN900> @Wizzup you can try netsurf-gtk on your desktop/laptop if you run Debian 11 or Devuan 4.0 at least
<Wizzup> tmlind: wonder if this is useful - reset on 5.15: https://dpaste.com/2YZ4DJ6JP.txt
<Wizzup> surf is webkit based afaik
missMyN900 has quit [Quit: No Ping reply in 180 seconds.]
missMyN900 has joined #maemo-leste
<missMyN900> netsurf is great for things like wiki pages, documentation and mobile news websites (e.g. mobile.reuters.com)
<missMyN900> sorry my WiFi is working poorly. Maybe switching to connman was not such a good idea after all...
* Wizzup zzz
<Wizzup> ttyl
missMyN900 has quit [Quit: No Ping reply in 180 seconds.]
missMyN900 has joined #maemo-leste
<missMyN900> there is some glitch on the Pinephone where the time (minutes) keeps flickering back and forth under CPU load (when I web page is loading)
missMyN900 has quit [Ping timeout: 264 seconds]
missMyN900 has joined #maemo-leste
<missMyN900> resolved my WiFi issues by getting rid of wpa_supplicant and using iwd with connman instead. Now I can even connect to the 5 GHz networks again, which was broken even when I was still using NetworkManager (on Debian 11)
<missMyN900> I wonder whether it is possible to use iwd with Maemo Leste as well
Wikiwide_ is now known as Wikiwide
Pali has quit [Ping timeout: 260 seconds]
lel has quit [Ping timeout: 264 seconds]
lel has joined #maemo-leste
Guest21 has joined #maemo-leste
Guest21 has quit [Client Quit]
<sunshavi> iwd is a systemd unit
<missMyN900> @sunshavi so it cannot be used with any other init system?
<missMyN900> I guess I will have to stick with Debian then on my desktop (I was thinking of installing Devuan eventually) because there is no way I am going back to NetworkManager and wpa_supplicant
<sunshavi> before iwd I was using wifi-menu. It worked fine. But not autoconnect with different dongles
<missMyN900> never heard of it
<missMyN900> I loved how WiFi works on OpenBSD
<missMyN900> so much simpler
<sunshavi> mmm. on freebsd they do not support a lot of wifi-cards. is it different on openbsd?
<missMyN900> my USB WiFi is supported (Ralink RT5592)
<missMyN900> I also bought one of the Alfa Wireless adapters with the AR9271
<sunshavi> mine is not supported atheros ar971 or something like that
<missMyN900> AR9271 has excellent support
<missMyN900> OpenBSD is much better than FreeBSD IMHO
<missMyN900> FreeBSD quality control is bad; Ars Technica did an article on it and I have heard the same from other people
<missMyN900> OpenBSD is also better for desktop use as FreeBSD devs mainly use macOS
<missMyN900> biggest problem with OpenBSD is interoperability
<missMyN900> there is no ext4 or UTF16 support, for example
<missMyN900> there is no way to run a Linux virtual machine and the Linux compatibility was removed some while back
<missMyN900> that is why I had to ditch it
<sunshavi> r u on irc from ur PP?
<missMyN900> I ran NetBSD on a Raspberry Pi B+ for a while that I used for some stuff but I have no need for it anymore and got sick of the limitations of the Raspberry Pi
<missMyN900> no
<missMyN900> I'm on my desktop
<missMyN900> is there a good IRC client?
<missMyN900> I am using Quassel on my desktop, which is what I used years ago; I haven't been active on IRC for years
<sunshavi> opi+2e here. I am on erc now
<missMyN900> CLI client?
<sunshavi> erc is part of emacs
<missMyN900> Is that an OrangePi?
<sunshavi> it is cli if u prefer it
<sunshavi> Right
<missMyN900> I only have a B+ and an old Wandboard. I would love to get a newer SBC but can't justify it right now
<missMyN900> especially after I got the Pinephone (I was intending to use it for tethering as my cable internet is unreliable sometimes)
<sunshavi> country?
<missMyN900> US
<sunshavi> PP is my future. But not this year. Still with n900
<missMyN900> I got rid of my N900 because I thought it was slowing down the WiFi network due to it not supporting N :(
<missMyN900> I sold it for very little money
<missMyN900> I bought it for $100 in like new condition late 2012
<missMyN900> now I have an iPhone :(
<sunshavi> But You are almost back with ur PP+mleste
<missMyN900> well, it is not quite ready yet in my experience
<missMyN900> LTE data is not working, for instance
<missMyN900> not on any OS
<missMyN900> pmOS + Plasma experience is not great either
<missMyN900> I barely use the PP
<missMyN900> just hoping for LTE to start working and for Maemo Leste to mature
<sunshavi> be patient. It is still evolving
<missMyN900> @sunshavi for sure. I have installed some applications today to try to make the Pinephone a bit more useful right now
<missMyN900> @sunshavi I am leaving the ML card inserted for now as I will not be using pmOS anyway as long as LTE data does not work
<missMyN900> I think smplayer, xournal and pluma are useful
<missMyN900> I hope that battery status support is implemented soon for the Pinephone. There are also graphical glitches that need fixing.
missMyN900 has quit [Ping timeout: 264 seconds]
joerg has quit [Ping timeout: 245 seconds]
joerg has joined #maemo-leste
<sicelo> sunshavi: iwd doesn't necessarily need systemd. at least the pmOS people use it (and they definitely have no systemd)
<sicelo> missMyN900: LTE data not working on PP in any OS? That's interesting. I thought it works on at least pmOS and Mobian. Anyway, not a PP owner, so I might have misread
<freemangordon> uvos: seems all other drivers have &dri2ConfigQueryExtension.base in their screen extenstions, no matter that they *do not* announce __DRI2_CONFIG_QUERY in version info
missMyN900 has joined #maemo-leste
<missMyN900> @sicelo: yes, I tried the Manjaro Plasma image my PP came with, the latest pmOS Plasma stable, the latest pmOS Phosh edge and now pmOS Plasma edge and still have not gotten LTE data to work once
<missMyN900> text messages and calls worked at least on pmOS Plasma stable
<missMyN900> nothing cellular related worked at all on Mobian Phosh
<missMyN900> this is with T-Mobile US
<freemangordon> Wizzup: where is the mesa source code?
<missMyN900> @Wizzup TMO works well in netsurf as well :) just checking out your post in the ML alpha thread
<freemangordon> oh, my remote is wrong
<missMyN900> @sicelo oh nice, I did not know pmOS was using iwd as well
<missMyN900> I quite like Alpine/pmOS
<missMyN900> will be installing Alpine on my old Wandboard over the holidays; I used to run it on my Raspberry Pi some years ago
<missMyN900> I don't like Plasma Mobile though and don't get me started on Phosh...
<missMyN900> just reading about the Qt5 port: that is awesome. I had no idea that Maemo widgets had been ported. I was wondering what was being done about GTK2 having been deprecated a long time ago (does not feel like it though ;) )
<missMyN900> this reminds me, there is some Qt demo web browser for mobile devices that is available on pmOS (scaling is broken though so it is currently unusable); it even has its own virtual keyboard
<missMyN900> packaging and fixing that could be quite a win for Maemo Leste IMHO
<missMyN900> found its homepage: https://doc.qt.io/QtWebBrowser/
<missMyN900> it uses QtWebEngine (Blink/Chromium)
<freemangordon> uvos: going to fix that, lets see if it will affect swaps as well
<missMyN900> if that were to be packaged and tested and touch screen support was added to netsurf-gtk, there would be two excellent browsers for Maemo Leste
<missMyN900> one traditional mobile browser with full support for the modern web and an ultralightweight alternative for low RAM devices
<freemangordon> Wizzup: hmm, what is this 0002-pvr-build-with-new-mesa.patch about? I see code changes there.
<sicelo> missMyN900: maybe ask about LTE on either the mobian or pmos rooms
<missMyN900> @sicelo: I will try that some time, thanks
<sicelo> including other cellular things ... for sure i know there are people who daily drive the pp
<missMyN900> yes, I am aware. Unfortunately there are also multiple reports on the forums of cellular related issues :(
<freemangordon> Wizzup: oh, Isee
<missMyN900> I downloaded a PDF today with Firefox on the Pp and moved it to MyDocs with Spacefm and then viewed it with the PDF reader
<missMyN900> the PDF reader is working very nicely on Maemo Leste
<freemangordon> Wizzup: though, I think we shall incorporate those changes in the code, not as patches
<missMyN900> based on my brief testing I would recommend Pluma, Xournal and Spacefm for use on Maemo Leste
<sicelo> we did have xournal on fremantle. i still use it there :-)
<missMyN900> it seems to work well on the Pp with Leste
<missMyN900> I tried to find some non-Gnome Gtk apps with big buttons
<missMyN900> Smplayer works okay as well though
<missMyN900> the stylus of the N900 would have been great to have with the Pp...
<missMyN900> the hardware keyboard will be a massive improvement though
sicelo_ has joined #maemo-leste
sicelo_ has quit [Client Quit]
sicelo_ has joined #maemo-leste
<sicelo_> PING 1637739169 293661
<sicelo_> PING 1637739174 545487
<missMyN900> netsurf really shines on "traditionalist" sites like TMO
mardy has joined #maemo-leste
<missMyN900> Alright, I've got to go
<sicelo> i think netsurf has been tried on ML, yes
missMyN900 has quit [Quit: https://quassel-irc.org - Chat comfortably. Anywhere.]
sicelo_ has quit [Client Quit]
inky has joined #maemo-leste
_inky has quit [Ping timeout: 268 seconds]
inky_ has quit [Ping timeout: 256 seconds]
pere has quit [Ping timeout: 264 seconds]
_inky has joined #maemo-leste
uvos has joined #maemo-leste
pere has joined #maemo-leste
<uvos> freemangordon: huh strange
<uvos> missMyN900: on d4 firefox works really well, if you activate all the touch gestures and hide the tab and menu bar, see http://uvos.xyz/maserati/screenshots/2020-06-17-195309_960x540_scrot.png im also hoping to modify http://uvos.xyz/maserati/screenshots/qtwebbrowser.png a bit to make it maybe the default leste browser in the future, at least for devices with 512mb+ ram
<uvos> on n900 its a bit harder, both ff and qtwebbrowser just get oom killed on startup for me
<uvos> so something like surf etc will have to do
<uvos> problem i have with surf is its abysmal scroling performance
<uvos> freemangordon: btw qwebengine renders black on ddk1.17
<uvos> not that this is your fault most likley
<uvos> [12977:13001:1124/094752.436859:ERROR:gles2_cmd_decoder.cc(2603)] [.RenderWorker-0x4f8fa8]GL ERROR :GL_INVALID_OPERATION : ScopedTextureBinder::dtor: <- error from previous GL command
<parazyd> uvos: For Firefox we could also provide a user.js that modifies it to be more mobile friendly.
<uvos> parazyd: yeah but long term i dread the next -esr
<parazyd> True, it's getting worse
<uvos> parazyd: ff changed a lot behind the scenes with the replacement of gecko
<parazyd> There's some alternatives called palemoon or something
<parazyd> Perhaps worth a look
<uvos> yeah
Wikiwide has quit [Ping timeout: 245 seconds]
ruleh has joined #maemo-leste
Pali has joined #maemo-leste
Wikiwide_ has joined #maemo-leste
<Wizzup> freemangordon: hi
<Wizzup> freemangordon: I think you figured out the patches I made to make it build with newer mesa?
<freemangordon> yes
<freemangordon> the point is that we shall incorporate them in code, rather than ceeping them n debian/patches
<freemangordon> *keeping
<Wizzup> freemangordon: yes, my mesa patches are "wip" in that sense since I didn't expect the rebase to surface these problems
<Wizzup> so I just stuck them in there since I didn't want to change the git log otherwise (yet)
<Wizzup> please feel free to take that and apply it
<freemangordon> ok
<freemangordon> will do
<Wizzup> the other one I would leave (the fix for freedreno)
<Wizzup> mesa master hasn't fixed it yet
<freemangordon> Wizzup: how to remove your patches? I mean - shall I revert or drop (and overwrite history)?
<freemangordon> or, make another branch?
<Wizzup> patch -p1 < debian/patches/foo.patch ; git add -p ; git commit -m "foo" ; git rm debian/patches/foo vi debian/patches/series; git add -p debian/patches/series maybe ?
<Wizzup> the thing is if you add it to git history you will need to re-tag
<Wizzup> but that should not be a problem I think :)
<Wizzup> I don't think you need to keep my work, you can also drop the commits if you want
<Wizzup> do whatever really
<freemangordon> Wizzup: I know how to apply the patches by hand, the point is that we have commit messages for them in the history I would like to drom
<freemangordon> but ok, I'll force-push with patches dropped
<freemangordon> hmm, mesa failed to build for me :(
<freemangordon> Wizzup: https://pastebin.com/YX8vqAGd any idea?
<Wizzup> freemangordon: out of memory?
<Wizzup> check dmesg for oom killer
<freemangordon> trying now with a single job only
<freemangordon> yeah
<freemangordon> Out of memory: Killed process 14933 (cc1plus) total-vm:600988kB, anon-rss:421664kB, file-rss:304kB, shmem-rss:0kB, UID:0 pgtables:590kB oom_score_adj:0
<freemangordon> added 1GB swap, lets see
joerg has quit [Read error: Connection reset by peer]
<uvos> i see we are still compileing mesa on omap4 :)
<Wizzup> uvos: he is, I am not, I use bencoh's lxc setup and the CI
<Wizzup> but yeah the CI does it on raspi4's :p
<Wizzup> (for now)
<uvos> do we plan on using lxc on ci?
<Wizzup> no, I ordered an ~1000 usd powerful arm server
<Wizzup> (well with the ram its 1000 usd)
<Wizzup> I'll put it in a chassic at my place so it shares the LAN with th rest of the builders
<uvos> ok great
<dreamer> fancy
<Wizzup> mid december or so I'll set it up
<dreamer> oh only 16 core :P
<Wizzup> well we got some funding to get the hw, so might as well since it's slowing us down
<dreamer> ja, good idea
<uvos> any idea what LX2160A corrisponds to roughly in terms of x86 processors?
<Wizzup> not really, others might know, we'll find out I supose
<Wizzup> the CI doesn't run on super fast x86 processors either
joerg has joined #maemo-leste
<bencoh> oh, solid-run <3
<Wizzup> It runs on AMD Opteron(tm) Processor 6278
<Wizzup> bencoh: they're basically the only feasible option atm (from what I could see)
<uvos> i mean operatorn 62xx is really old
<Wizzup> yes
<uvos> bulldozer - outch :P
<Wizzup> but it fits in my coreboot kdpe-d16 :p
<uvos> heh
<Wizzup> kgpe-d16*
<sunshavi> 64 Gb emmc. I have the same but with a uSD adapter on my SBC
<Wizzup> sunshavi: I think it has pci or something, so we'll go for with ssd on sata or m.2
<bencoh> :)
<sunshavi> Yes. I have compiled mesa in the past 2 Gb memory was enough for doing an in-memory compilation
<sunshavi> Wizzup: Do You remember when I was trying to put ML on my SBC. And I failed. It was because of an error with EmmmModule+uSDAdapter.
<sunshavi> After a couple of lines within mmc-sunxi.c I have been able of booting archlinux on it. So I think I could try soon ML again
<Wizzup> freemangordon: I'd like to package osso-abook for -devel some time, that ok?
<Wizzup> I know it's not finished, but it's finished enough to build some pkgs
<freemangordon> ok
<freemangordon> lemme see if I have pushed everything so far
<freemangordon> Wizzup: yep, everything is pushed
<freemangordon> please, have a look if you can invent a better versioning scheme :)
<Wizzup> freemangordon: this is about abook?
Guest6233 has joined #maemo-leste
<Wizzup> freemangordon: uvos: do you use a powervr.ini on d4 or n900? I moved mine on n900 and I don't think there is a difference
Guest6233 has quit [Client Quit]
<Wizzup> sicelo: # sleep 10 ; /etc/init.d/n900-powermanagement status
<Wizzup> d=2021-11-24|t=13:48:57|i=OFF:0,RET:0|p=408|c=NA|b=ST_SDRC,ST_OMAPCTRL,ST_I2C1,ST_MCSPI4
<Wizzup> I think this is useful :-)
<Wizzup> tmlind: looks like spi4 is wifi, and it does idle some time, i2c1 is twl, but a lot is twl, so that might be hard to narrow
<Wizzup> I don't know about SDRC and OMAPCTRL really
<Wizzup> I'm going to figure out how we can add to the bootmenu from our partition(s)
<Wizzup> and then add emergency mode and such
<Wizzup> hm: [ 30.164733] rx51-audio n900-audio: snd_soc_register_card failed (-517)
inky has quit [Ping timeout: 264 seconds]
inky_ has joined #maemo-leste
inky_ has quit [Remote host closed the connection]
<sicelo> mmm, yes, our N900 needs some loving. its dts is getting outdated, it seems
<Wizzup> sicelo: so you've seen this before I reckon?
inky_ has joined #maemo-leste
<Wizzup> this might be one for pavel maybe
pere has quit [Ping timeout: 250 seconds]
<sicelo> i don't think i've seen it. but i've seen similar stuff. most of the time it's because our dts needs updating in line with latest binding specifications, etc.
<Wizzup> ok
<Wizzup> so I am thinking that there are some random boot failures which are the real reason the device would reset, and I'm seeing the same with the droid on 5.15, so that's probably some of the problems we're seeing (might be able to use console on the d4 to find that)
<lel> MerlijnWajer opened an issue: https://github.com/maemo-leste/bugtracker/issues/587 (N900 Linux 5.15)
<Wizzup> sicelo: if you have time, please add/comment ^
<uvos> random boot failures on d4 are "normal"
<uvos> if you mean right after kexec
<uvos> thats the 3.0.8 kernels fault
<Wizzup> it happens more frequently now I'm sure
<Wizzup> I'll attach serial some time, but there's so much to do :)
<uvos> dose it vibrate when it happens?
<uvos> ie is it kexecboot menu->select entry->vibrate->motorola logo
<uvos> or kexecboot menu->select entry->motorola logo
<Wizzup> I don't remember, but I am pretty sure after kexecboot menu
<uvos> sure both of those are after the menu
inky_ has quit [Ping timeout: 264 seconds]
<sicelo> i'm surprised nokia modem isn't enabled by default. i am quite sure omap2plus has it enabled ootb
<freemangordon> Wizzup: I don;t think we shall user powervr.ini on any of the devices
<freemangordon> it was used because of glamor
<Wizzup> freemangordon: ok, it is not purged by default
<Wizzup> sicelo: no @ enabled ootb
pere has joined #maemo-leste
<freemangordon> Wizzup: it should not be
<Wizzup> freemangordon: right
<sicelo> ah i see. i was enabling it in my own config
<Wizzup> yes
<Wizzup> uvos: parazyd: I want to tweak the omap2plus_defconfig for our purposes a bit like spinal did, making some more essential things built in
<Wizzup> any suggestion on how to best approach it?
<Wizzup> in particular keeping in mind upstream omap2plus_defconfig will change with time
<sicelo> it hardly changes (upstream)
<uvos> i think its perfectly sane to have a leste_omap_defconfig or whatever
<uvos> and have just the modules we need for the devices the omap kernel is built for + whatever you want built in
<uvos> i would not go around patching omap2plus forever
<uvos> this is quite usual behavior for a distrobution in general
<uvos> (having an own defconfig)
<Wizzup> yeah n9xx-linux has n900_defconfig
inky_ has joined #maemo-leste
<Wizzup> Pali: do you create your bootmenu entries from fremantle still, or do you manage them externally? I'm wondering what the best way for leste to manage this would be
<Wizzup> I think we probably want some bootmenu.scr file on the sd card
<Wizzup> I was looking at u-boot/include/configs/nokia_rx51.h but it wasn't quite clear to me
<Wizzup> reading u-boot doc...
<Pali> IIRC upstream u-boot read bootmenu.scr also from sd card
<Wizzup> any clue what has preference?
<Wizzup> or are they combined somehow?
<Wizzup> I saw the preboot section
<Pali> now I checked it
<Pali> yes, it first loads it from sd card and then fallbacks to emmc
<Pali> include/configs/nokia_rx51.h
<Pali> preboot=
<Wizzup> ok, so if we have it on sd card we better make sure we have fremantle entry to allow booting fremantle with sd card in
<Pali> yes!
<Wizzup> parazyd: fyi ^
<Wizzup> well, whatever I did, it no longer boots 5.15 kernels anymore, meh
<Wizzup> interesting, now 5.1 also gives panic trying to find root device
<sicelo> :-) n900 is always 'fun' when playing with new kernels, haha
<Wizzup> *not* :)
* uvos grumbels over uart ... no one hears him
<Wizzup> uvos: ?
<uvos> its a joke, thats whats happening to n900 its complaining over uart, but no one listens
<Wizzup> ah yeah
<Wizzup> well we just need to find a way to easily make a few of these serial adapters
<sicelo> we are listening actually. just only Wizzup has serial for now.
<sicelo> i'm still going to go ahead and permanently solder some thin wires onto my old broken on
<Wizzup> uvos: I don't have any cnc equipment available
<Wizzup> I guess we could ask some commercial place to make some
<uvos> Wizzup: im fine with using my equitment, but it dont want to invest the time to design something.
<uvos> Wizzup: ie give me sane and compleat cad files (ie sres isent either) and i can make you some parts.
<uvos> we have milling, turning, fdm printing and laser cutting available
<uvos> with 3,2,3,2 axies
<uvos> respectively
<Wizzup> with drm built in at least I quickly see a penguin, but seems console is not on that tty - weird
<Wizzup> maybe something with run sdboot
<Wizzup> uvos: hm, ok...
belcher has quit [Ping timeout: 260 seconds]
<uvos> theres no better time to learn freecad than now :P
<uvos> Wizzup: is power duplicated on the pogo landing pads?
<uvos> Wizzup: if so it should be realy easy, just mill out a battery shaped object with some holes in the right places to glue pogo pins
<Wizzup> the serial module I have I tihnk uses the battery pads
<Wizzup> s/pads/connector/
<uvos> probubly not then
<uvos> well designing something to fit the battery connector will be a bit more dificult
<uvos> unless the n900 can be powerd via only usb via some trick like moto a85x
<uvos> any how im happy to help with any other infomation you might need, eg desin rules etc.
<uvos> or hints on tools etc
<Wizzup> yeah, I'm not going to volunteer to do it since it will take me weeks probably
<uvos> Wizzup: ok yeah makes sense
<freemangordon> Wizzup: I think I am ready with mesa fixes
<freemangordon> doing one last test and will force-push
<uvos> what are we fixing?
<freemangordon> may I leave tagin/versioning to you?
<freemangordon> segfault
<uvos> great :)
<freemangordon> I have glx enabled in omap.conf and no segfault anymore
<freemangordon> enabled like "not disabled" :)
<Wizzup> freemangordon: do you mean to me?
<freemangordon> yes
<uvos> it falls back to llvm/swrast or dose it fail to create a surface?
<freemangordon> uvos: no idea, how to check?
<Wizzup> freemangordon: ok, I'll make a note and try to remember but I am fighting a losing fight with my n900 and kernrel
<uvos> glxgears?
<freemangordon> Wizzup: ok
<freemangordon> uvos: sec
<freemangordon> uvos: do you know which pacjage is that?
<freemangordon> *package
<uvos> mesa-demos
<uvos> iirc
<freemangordon> hmm, maybe mesa-tools
<freemangordon> or mesa-utils :)
<uvos> dpkg -S /usr/bin/glxgears
<uvos> mesa-utils: /usr/bin/glxgears
<uvos> yeah
<freemangordon> mhm
<freemangordon> Error: glXCreateContext failed
<Wizzup> great
<uvos> freemangordon: ok thats fine
<freemangordon> cool
<uvos> freemangordon: but ddk1.9 fell back to llvm
<uvos> witch is slightly bettermaybe
<Wizzup> I don't think we want that really
<Wizzup> if we do anything here at all we should use gl4es
<uvos> idk sometimes soemthing working at all is better than it being slow
<Wizzup> things falling back to llvmpipe for "acceleration" is just an outright nightmare
<uvos> you can still block glx if you want in xorg.conf
<uvos> but yeah its fine for now
<uvos> it might be because of the pvr override acctually
d4irc has quit [Remote host closed the connection]
<Wizzup> weird, modules_install does not install pvrsrvkm and related modules to the path for me
<Wizzup> that explains why my n900 resets after trying to start X (without anything in dmegs)
<Wizzup> hmm
<uvos> lifeguard strikes again? :P
<Wizzup> no
belcher has joined #maemo-leste
<Wizzup> lf is not happening
<uvos> then why would it reboot?
<Wizzup> some internal kernel oops?
<Wizzup> I had SGX_OMAP=y instead of SGX_OMAP=m, I think this is why it did not install the other modules
<uvos> ah ok
<uvos> merly missing pvrsrvkm should not cause a reset ofc
<Wizzup> looks like it does though
<Wizzup> in any case this is not important atm
<Wizzup> this really illustrates why computers are so painful, it still doesn't install it with modules_install
<Wizzup> so maybe DRM=y and DRM_OMAP=y causes it just to skip installing the modules
d4irc has joined #maemo-leste
* bencoh headscratches
<uvos> that would be very wierd
<uvos> but idk
<Wizzup> I'll do make clean and new defconfig..
<bencoh> do make savedefconfig first
<Wizzup> no need
<bencoh> unless you don't want to debug it
<Wizzup> not really, I just want my modified defconfig to work
<uvos> do the sgx modules have any depends in Kconfig?
<uvos> maybe they depend on omapdrm being a module
<uvos> you can do that
<Wizzup> well they get build...
<Wizzup> they just don't get installed
<uvos> ¯\_(ツ)_/¯
* freemangordon hates meson/ninja
<freemangordon> why the hell a simple touch of some config file would cause 2000 files to be recompiled is beyond my capabilities to grok
<Wizzup> make clean made it work..
<freemangordon> use ninja next time, it cleans everything even if you don't want it to :D
<bencoh> :]
<uvos> the user side experiance of meson is not so great yeah
<uvos> but developer side is quite good
<uvos> not that i recommend using it
<bencoh> well, many projects are slowly moving to it
<bencoh> so I feel like we won't have much choice in some close future
<uvos> yeah because its really easy to maintin dev side, using autotools is a mess really
<freemangordon> uvos: hmm, so I am user?
<uvos> freemangordon: yeah
<bencoh> (maybe not so near, but ....)
<freemangordon> good to know :D
<uvos> freemangordon: of the build system
<uvos> freemangordon: your not writing mesas buld system
<freemangordon> Wizzup: ok, what you want me to do wiht mesa tag?
<freemangordon> shall I increase version or what?
<Wizzup> freemangordon: do you want it built soon?
<Wizzup> I'm a phone call atm
<freemangordon> ah, sorry
<Wizzup> I think I tagged it
<Wizzup> if I did, then feel free to delete tag and re-tag
<freemangordon> yes, you did
<freemangordon> ok
<freemangordon> will do
<freemangordon> and will spin a build in CI
<Wizzup> cool
<freemangordon> uvos: do you have an idea how to fix one and the same 12MiB .so being copied 30 times?
<freemangordon> xxx_dri.so files I mean
<uvos> freemangordon: where?
<freemangordon> /usr/lib/armhf-xxxx/dri
<uvos> no i mean what builds it? mesa?
<freemangordon> yes
<uvos> what so are we talking about here
<uvos> pvr?
<freemangordon> uvos: do 'ls -al /usr/lib/arm-linux-gnueabihf/dri/'
<freemangordon> no matter pvr or not
<freemangordon> it copies one and the same .so under different names
<uvos> is it that way in your debian direcory?
<freemangordon> using 200-300 MiB instead of ~15
<uvos> ie before install runs
<freemangordon> I guess, but I have stopped the build
<freemangordon> lemme restart it
<freemangordon> but it will take 2 hours
<uvos> heh
<freemangordon> bencoh: do you have mesa build around?
<uvos> maybe ill build it on vm later
<uvos> *i will build it on vm later
<uvos> and see
<freemangordon> lemme check what is installed in debian
<uvos> essentally check if its mesa buildsystem screwing up the build the install or if its the debian packaging
<freemangordon> yes, I know
<freemangordon> I mean - I understand your point
<bencoh> freemangordon: do you want me to build it?
<freemangordon> if possible
<bencoh> sure, which commit/branch?
<freemangordon> bencoh: wait
<freemangordon> I did 'ninja -j2' all the time
<freemangordon> so my debian directory is intact
<bencoh> hm?
<freemangordon> debian build was not cleaned
<bencoh> ah
<freemangordon> uvos: https://pastebin.com/Nbnb792w
<freemangordon> as expected
<bencoh> I guess you fetched libdrm/llvm8/libclang8 from backports btw?
<freemangordon> yeah
<bencoh> tell me if you still want me to build it :)
<freemangordon> no need, thanks
<uvos> freemangordon: its the same on arch linux
<uvos> freemangordon: looks like there really is only 2 different .so files
<uvos> mesa classic and gallium3d
<uvos> wth
<uvos> aperantly mesa people dont know what a symbolic link is
<freemangordon> yeah
<freemangordon> looks like
<freemangordon> maybe this is because of dx12 support :D
<uvos> freemangordon: they link everyting into one so
<uvos> on purpose it seams
<uvos> and then call ./bin/install_megadrivers.py on it
<uvos> i dont get wth they are trying to achive here
<freemangordon> yes, linking everyting into once might have sense
<freemangordon> but copying this 30 times is insane
<freemangordon> this will easily fill onenand on n900 when we decide to move there :)
<Wizzup> maybe they all use btrfs with CoW
<bencoh> huhu
<freemangordon> no matter, this needs to be fixed
<bencoh> so I wasn't entirely wrong when I said that there were duplicate files :]
<Wizzup> :P
<Wizzup> maybe we make an issue and fix it later?
<uvos> bencoh: yeah
<freemangordon> Wizzup: well, better fix it while we are on it
<bencoh> I think they expect package managers to split it
<freemangordon> but, no me :D
<uvos> i dont like them linking everything into one so either
<uvos> huge waste of ram
<freemangordon> uvos: yeah, but his is easy to be maintained
<uvos> what do i need the driver for r300
<freemangordon> not really
<freemangordon> (waste of RAM)
<uvos> how not?
<freemangordon> you dont read pages into RAM unless needed
<bencoh> yeah
<uvos> ok
<bencoh> in that regard it's not *that* bad
<freemangordon> *that bad* being the key here :)
<bencoh> ;)
<freemangordon> but otherwise you have to maintain several .so files
<freemangordon> and keep iterfaces comparibel, etc,etc
<freemangordon> *compatible
<freemangordon> one big blob is easier to maintain
<freemangordon> "(17,40,32) uvos: but developer side is quite good"
<freemangordon> :p
<bencoh> :]
<freemangordon> uvos: did you have time to further look into buffer swap issue?
<uvos> well there writing custom python scripts here
<uvos> its hardly just meson anymore
<uvos> but sure
<uvos> freemangordon: not yet
<freemangordon> ok
<uvos> but i will get to it
<freemangordon> thanks
<freemangordon> appreciated
<freemangordon> I want to start looking into vrfb
<freemangordon> hmm, maybe I shall power-up my n950 soon
<bencoh> wow, n950
<freemangordon> mhm
<freemangordon> I was awarded back then
<bencoh> yeah I know, I was just surprised to read that now :)
<bencoh> it might be easier to tinker with than n900 though :)
<freemangordon> maybe
<bencoh> what about serial on it?
<freemangordon> no idea
<bencoh> is it simpler?
<bencoh> ah
<freemangordon> and don;'t wan't to risk it
<bencoh> right
<freemangordon> I plan this to be my next device
<bencoh> oh
<freemangordon> yeah
<uvos> daily carring a unreplaceable device
<uvos> ok..
<uvos> whatever floats your boat
<bencoh> well ...
<uvos> :P
<freemangordon> why non-replaceable?
<Wizzup> ok, I have a custom boot menu on the n900 and it prints sensible stuff on the console now, but something causing resets isn't fun surely
<bencoh> assuming leste goes strong and works on other devices, he could still migrate to droid4 if needed
<freemangordon> I mean - if it breaks, I have d4 ;)
<freemangordon> bencoh: yeah
<bencoh> ;)
<freemangordon> Wizzup: if you have high-fps camera around, you may try to capture a video
<Wizzup> no, the screen is black, it happens after X is being started
<freemangordon> Wizzup: or, set mtdoops partition
<uvos> Wizzup: boot to emergency shell
<uvos> start xorg by hand via ssh
<freemangordon> or move dsme out of /etc/init.d
<uvos> that way you have some output while it starts
<freemangordon> you'll get login shell
<Wizzup> there are many things to try, first I will just try building from within the lxc container and get something that works again
<freemangordon> ok
<Wizzup> freemangordon: doing that (mv dsme) means I have to manually type on the keyboard to get usb net up
<Wizzup> and it's a pain
<Wizzup> :D
<freemangordon> I use wpa_supplicant with conf file
<Wizzup> mhm
<freemangordon> I typed the command once
<freemangordon> and from then on I use ctrl-r ;)
<uvos> the n900 having so little special keys in console can get pretty frustrating
<uvos> yeah
<Wizzup> I will do that if it turns out to be a problem that keeps recurring
panzeroceania has quit [Ping timeout: 245 seconds]
panzeroceania has joined #maemo-leste
<Wizzup> having drm built in is real nice though since you get display in seconds rather than after 30 seconds
uvos__ has joined #maemo-leste
Pali has joined #maemo-leste
Pali has quit [Killed (zinc.libera.chat (Nickname regained by services))]
asrieldreemurr has joined #maemo-leste
pere_ has joined #maemo-leste
peetah_ has joined #maemo-leste
joerg has quit [Excess Flood]
pere has quit [*.net *.split]
uvos has quit [*.net *.split]
nohit has quit [*.net *.split]
peetah has quit [*.net *.split]
zhxt has quit [*.net *.split]
asriel has quit [*.net *.split]
zhxt has joined #maemo-leste
nohit has joined #maemo-leste
<Wizzup> damn, now even the kernels that used to work reset in X, ok.... I guess I'll have to debug it now :(
<Wizzup> maybe it's the powervr.ini that I moved away somehow
<freemangordon> I have powervr.ini on neither d4 or n900
<Wizzup> ok
<freemangordon> *nor
joerg has joined #maemo-leste
<Wizzup> weird, X and h-d are fine, so wth is causing the resets
<freemangordon> who resets? dsme?
<Wizzup> no, kernel just resets
<freemangordon> hmm
<Wizzup> leaving all log files corrupted
<freemangordon> bad battery?
<Wizzup> seems unlikely
<freemangordon> ok
<freemangordon> uvos__: hmm, after thinking about that a bit, DRI2 actually uses doulble-buffering, but it works like that:
<freemangordon> 1. a frame is rendered and is send to be displayed
<freemangordon> 2. driver waits for vsync and only then it completes the swap
<freemangordon> 3. client renders back buffer again and requests swap
<freemangordon> 4. after vsync back buffer becomes front and only the swap is completed
<freemangordon> *then
<freemangordon> so, we need to implement tripple-buffering in DDX
<freemangordon> maybe we can do it better if the first swap is returned immediately
<bencoh> is triple-buffering really mandatory here?
<freemangordon> no
<bencoh> it's usually not that good perf-wise
<freemangordon> but it seems DDX is done in such a way that client waits in SwapBuffers until vsync
<freemangordon> I am not sure I explain this correctly
<bencoh> (hmm, actually the screen is small enough that it wouldn't hurt *that* much the memory bus)
<freemangordon> actually I think we shall block only if we have more than one buffer waiting for vsync
<freemangordon> yes, that should be it
<bencoh> sounds reasonable
<bencoh> that would mean the driver always have another buffer ready to push to display
<freemangordon> lemme see if I can implement that
<bencoh> (assuming I got that right)
<bencoh> s/have/has/
parazyd has quit [Quit: parazyd]
<dsc_> ship it(tm)
parazyd has joined #maemo-leste
<Wizzup> freemangordon: looks like icd2 starting causes the kernel reset
<bencoh> uh
<freemangordon> weird
<Wizzup> maybe wifi driver
<freemangordon> yeah
<Wizzup> it was working before though
<Wizzup> yeah it does... wow
lexik_ has joined #maemo-leste
lexik has quit [Ping timeout: 268 seconds]
<uvos__> freemangordon: ok yeah id avoid tripple buffering if at all possible
<freemangordon> uvos__: yeah, but I think there is something broken in mesa with double-buffering
uvos__ is now known as uvos
<freemangordon> I think SwapBuffers shall not block
<freemangordon> not that I debugged it, but I think it does
<freemangordon> some random thoughts - 'vsync' on d4 is 80 Hz
<freemangordon> it seems to be the max rate display can be updated to
<freemangordon> max FPS reported by clutter on d4 for h-d scrolling is 40
<freemangordon> on n900, vsync is 60, max fps reported by clutter - 30
<freemangordon> so, we are not vsync limited, but vsinc/2 limited
<freemangordon> which is single-buffering IIUC :)
<freemangordon> hmm, wait
<freemangordon> no, this is double-buffering
<freemangordon> because we cannot render on buffer A until buffer B is not flipped
<freemangordon> uvos: DRI3 does tripple-buffering by default
<freemangordon> so I don;t see a reason why dri2 shall not
<freemangordon> we have 1/60th of a second delay, so what?
<freemangordon> worse-case
<uvos> i mean 1/60 of a second is quite a bit
<freemangordon> *worst
<uvos> you can feal that for sure
<uvos> so dose vblank_mode on hildon-desktop change this any
<uvos> ?
<freemangordon> no
<uvos> ok
<uvos> so its not h-d
<freemangordon> vblank_mode, like clutter_vblank_mode?
<freemangordon> no, it is not h-d
<uvos> no the mesa override
<freemangordon> hmm, what is this?
<uvos> looks light it might just be implemented for some drivers
<uvos> (that list is wrong for sure tho)
<uvos> same effect as clutter_vblank_mode
<uvos> most likely
<uvos> just mesa forcing things
<freemangordon> anyway, with modesetting/dri3 we have tripple-buffering
<uvos> only if you set it in xorg.conf no?
<freemangordon> no
<freemangordon> this is out of x control
<freemangordon> in dri3 clients control buffers
<uvos> ok iirc x has a option for this
<uvos> but might just apply to dri2/be broken
<freemangordon> no, this is totally out of server's control
<uvos> well xorg also dose its own rendering
<uvos> might be refering to that
<freemangordon> could be
<freemangordon> but in terms of page flipping, server has no sayng
<freemangordon> *saying
<uvos> ok
<uvos> i hear you
<freemangordon> sh, I think we shall implement tripple-buffering in ddx
<freemangordon> 40fps is too low
<uvos> so why is h-d special?
<uvos> btw
<freemangordon> what do you mean?
<uvos> well other egl clients in non-composing mode arnt locked to 40fps (at least they dont think they are)
<freemangordon> it is not special, it is just that for h-d ddx does page-flipping, glmark does blits
<uvos> ah ok
<uvos> yeah
pere_ is now known as pere
<uvos> freemangordon: but its not working?
<uvos> otherwise why is it wating
<freemangordon> well, I don't understand what is "client explicitly request the third buffer." supposed to mean
<freemangordon> somehow, someone shall request DRI2BufferThirdLeft
<freemangordon> hmm seems armsoc ddx has this 3buffering implemented
<freemangordon> I can use that as an example
inky_ has quit [Remote host closed the connection]
inky_ has joined #maemo-leste
<Wizzup> interesting... even with wifi module unloaded icd still causes reset - maybe it's me adding nokia modem...
<Wizzup> (which you wouldn't see since you probably don't have ofono installed)
<uvos> well at least your having fun.
<uvos> maybe try touching the modem interfaces
<Wizzup> it's only fun because I'm not stuck anymore :)
_inky has quit [Ping timeout: 245 seconds]
<Wizzup> I don't think I will debug the modem problems now if that turn out to be the problem
<Wizzup> I want to get a more usable config first (drm built in, etc)
<uvos> ah yes the endless cycle: i hate this, oh neat, i hate this, oh neat, i hate this....
<uvos> Wizzup: ok
<uvos> Wizzup: makes sense
<Wizzup> yes, removing nokia modem and friends made the freeze go away
<uvos> might be usefull to know from sicelo if he used the modem on some newer version than 5.1 to have something to bisect from
<uvos> sicelo: ^^^^
<Wizzup> It's probably a unbalanced pm thing I bet
<Wizzup> most other things don't cause resets like these
<uvos> anything that hangs the kernel can cause a watchdog reset like this or?
<uvos> sure a unbalanced pm sleep/wake would do it
_inky has joined #maemo-leste
<Wizzup> uvos: not sure how it works exactly (when it hangs and resets)
<Wizzup> blacklisting nokia_model makes the kernel stuck trying to load it anyway it seems
<Wizzup> modem*
<Wizzup> easier to not build the module yet, hehe
<uvos> hmm that def should not happen..
<Wizzup> # cat /mnt/extern/etc/modprobe.d/nokia-modem.conf
<Wizzup> options nokia-modem pm=1
<Wizzup> maybe I should have written nokia-modem and not nokia_modem
<Wizzup> (lsmod shows nokia_modem though)
<Wizzup> anyway we have that pm=1 thing in there specifically on leste
<sicelo> freemangordon: "I plan this to be my next device" ... meaning, daily drive N950?
inky has joined #maemo-leste
<freemangordon> why not?
epilys has left #maemo-leste [Leaving]
mardy has quit [Quit: WeeChat 2.8]
inky_ has quit [Ping timeout: 260 seconds]
<Wizzup> uvos: yeah looks like the nokia-modem.conf caused it to be loaded
<sicelo> uvos, Wizzup - yes i was building nokia modem on 5.9-5.12. i don't remember if i actually used it
<sicelo> re - N950, just interesting. it definitely seems like a fun device
<sicelo> nokia-modem - even if i might not have used it, i distinctly remember it was probing just fine
<Wizzup> it probes fine
<Wizzup> the problem occurs when icd2 talks to ofono which talks to modem
<sicelo> ok. i really can't remember if i put it to any use. maybe i didn't
<Wizzup> it works in 5.1 for sure
<Wizzup> it might be the pm= option
<Wizzup> at least I got the following done today: working bootmenu on sd card, drm built in for smoother boot, zImage booting works
<sicelo> it'd be really sad if more stuff is 'broken' for N900 by now, although i hope fixing all of them should not be too hard
<Wizzup> lol as I wrote this xorg ddx crashed
<Wizzup> sicelo: this was the case every time we try newer kernel after a while
<sicelo> oh great @zImage!
<Wizzup> nobody but us uses it
<uvos> well pmos
<uvos> they use 5.6 i think
<sicelo> 5.7
<Wizzup> they are also looking for a maintainer, and I am not sure if they are finding volunteers
<uvos> so that pobubly works
<Wizzup> (for n900)
<Wizzup> sicelo: yeah I need to test booting without dtb appended but I think it will work too
<Wizzup> that is necessary to make our single kernel pkg
<sicelo> i had started to 'track' the kernel and test for n900 each time (from 5.9 until there was 5.13-rc1, i think). when it became fun, then life got extra busy ... hopefully mid-dec things normalize
<Wizzup> freemangordon: I apt upgraded to latest mesa and I think my n900 is unhappy now, let me reboot and try again - anything you changed that might affect it?
<Wizzup> (can't get a break hehe)
<Wizzup> freemangordon: nevermind for now, let me debug further...
<sicelo> cannice to know built in drm works. i once tried it, and my n900 wouldn't boot. but it was booting fine with drm as module
<sicelo> s/cannice/nice/
<Wizzup> yeah but something broke since I upgraded mesa
<Wizzup> now the device is unusable again :D
<Wizzup> but I think the problem is that powervr doesn't init now, and I am pretty sure it did
<uvos> well what dose pvrsrvinit say? (in logs dont run it again)
<Wizzup> I can't get into the device because usbnet also doesn't work anymore, and the display doesn't respond, so I cna't tell you for sure
<uvos> mhh ok
<uvos> fun
<Wizzup> powervr |PVR:(Error): OpenServices: PVRDRMOpenRender failed [0, ]
<Wizzup> powervr |PVR:(Error): PVRSRVInitSrvConnect: PVRSRVConnect failed [0, ]
<Wizzup> powervr |PVR:(Error): SrvInit: PVRSRVInitSrvConnect failed (4) [0, ]
<Wizzup> powervr |failed to initialize server
<Wizzup> powervr | * ERROR: powervr failed to start
<Wizzup> prety generic
<uvos> im pretty sure thats the same as when you dont have the module probed
<uvos> but yeah its not very detailed
<Wizzup> maybe it's also racy somehow
<Wizzup> oh, I see
<Wizzup> 2981 Nov 24 19:22:15 localhost kernel: [ 2.190307] [drm] Initialized omapdrm 1.0.0 20110917 for omapdrm.0 on minor 0
<Wizzup> vs
<Wizzup> 2580 Nov 24 19:07:56 localhost kernel: [ 28.333038] [drm] Initialized pvr 1.17.4948957 20110701 for 50000000.gpu on minor 1
<Wizzup> the one with built-in drm doesn't seem to init pvr
<Wizzup> so yeah, probably it is not being loaded somehow
<Wizzup> maybe because the mode is not available drm is being loaded
<Wizzup> 3267 Nov 24 19:22:16 localhost kernel: [ 2.283264] [drm] Initialized omapdrm 1.0.0 20110917 for omapdrm.0 on minor 0
<Wizzup> (2.2s after boot)
<uvos> inserting the pvr moule later works fine
<uvos> like haveing it blacklisted and inserting it minutes after boot
<uvos> i have done that plenty of times
<Wizzup> but nothing loads it
<Wizzup> I guess pvrsrvctl would ;)
<Wizzup> looks like keyboard also doesn't work when drm loads early :(
<Wizzup> and usb otg
<uvos> it should be loaded by kernel normaly
<Wizzup> they are not :(
<uvos> omapdrm being built in has no bearing on it
<Wizzup> right, except that when omapdrm is not built in, the keyboard works
<Wizzup> so there's some loading magic going on
<uvos> i mean this suggests some terrible issue
<uvos> maybe compile the kernel with all the debuging stuff enabled
<Wizzup> maybe another day, I just wanted to do the packaging for now
<Wizzup> but looks like I won't finish that today either ;)
<Wizzup> I wouldn't be surprised if some parts not probing blocks other parts from probing, I've seen this a lot
<Wizzup> this is the current score https://github.com/maemo-leste/bugtracker/issues/587
<sicelo> i do recall having issues with built in drm, but i was too noob to debug back then
<Wizzup> I am too
<uvos> i mean omapdrm built in has no issues on mapphones w/o sgx
<uvos> thats how bionic boots
* freemangordon is zzzz
<freemangordon> night
<Wizzup> uvos: then what loads sgx?
<Wizzup> gn
<uvos> w/o sgx
<uvos> nothing
<uvos> its a untainted kernel
<Wizzup> I'm going to reboot my machine in a bit, maybe all my usb ports are dead and that's why I am not seeing the device now
<sicelo> i was doing drm fror sgx purposes
<Wizzup> the droid4 with leste has a habit of killing the usb controllers
<Wizzup> lol
<uvos> laptops dont like it if you pull high power usb class current but dont ask first
<Wizzup> it's more about the switching between charging and discharging
<Wizzup> that happens every second or so for an hour, and it'll die
<uvos> inrush current maybe
<uvos> either way
<uvos> yeah cpcap-charger is terribly behaved wrt usb spec
missMyN900 has joined #maemo-leste
<missMyN900> uvos: I would suggest netsurf(-gtk) instead of surf, particularly for the N900. It has very low RAM consumption and can be compiled against GTK2 still. They just introduced a new (small-screen-friendly) GTK UI in 3.10. It is available in Devuan Chimaera (and Debian 11, also pmOS edge).
<missMyN900> uvos: awesome that you are looking into qtwebbrowser. I think it has a lot of potential.
inky has quit [Ping timeout: 245 seconds]
_inky has quit [Ping timeout: 240 seconds]
inky has joined #maemo-leste
_inky has joined #maemo-leste
<missMyN900> uvos: according to Phoronix benchmarks the LX2160A is faster than an i7-4770K for video encoding, which is something that x86 excels at
<missMyN900> @Wizzup: M.2 can be SATA as well. I have a SATA M.2 SSD in my desktop (the X470 motherboard accepts both NVMe and SATA SSDs in the M.2 slot)
<missMyN900> @Wizzup: and my laptop (older HP EliteBook) only is compatible with M.2 SATA SSDs (I have an M.2 860 Evo installed)
* sicelo wants one of those for his T440p
<uvos> missMyN900: sure netsurf is useful on n900 maybe
<uvos> missMyN900: otherwise it think its way to janky for general usage/ recommendation
<missMyN900> @uvos: all it needs is touch screen support
<missMyN900> @uvos: it works well on TMO, wiki pages, documentation and some mobile news sites (e.g. mobile.reuters.com)
<uvos> it also needs a layout engine that works on popular websites
<missMyN900> Pine64 forums as well probably
<uvos> i mean yeah
<uvos> if thats what you want thats fine
<missMyN900> @uvos: well, but there is a limit to what you can do with low resource devices
<uvos> but the deafult browser must apeal to a bit more casual audiance
<missMyN900> even on devices with a bit more RAM it could be useful as a second browser
<uvos> only the n900 is low resource in this sense
<missMyN900> @uvos: Chromium struggles with 2 GB RAM
<uvos> but yes for n900 its likely the best you can do
<missMyN900> even the Pinephone non-Convergence edition only has 2 GB RAM
<uvos> i use d4 daily with ff and 2-3 pages open
<uvos> i have never had problems with ram ever
<ashley> Chrom(e|ium) struggles with 8GB of RAM on desktop/laptop ;-)
<uvos> this is true
<missMyN900> netsurf is useful even on a Pinephone or some 1 GB RAM device when you are multitasking
<uvos> sure im not saying: dont make it instalable
<uvos> just its not suitable as a default browser
<missMyN900> I think it should be the default browser with qtwebbrowser as an alternative browser
<missMyN900> the default browser should work well on every ML device IMHO
<missMyN900> it is also useful to have a browser with JS disabled by the default, whether for privacy, security or battery life reasons
<missMyN900> @uvos: I think that if Maemo Leste ever becomes a real alternative to Android and iOS, then that will be the time to make something other than netsurf the default browser
<missMyN900> @uvos: but as long as it is an enthusiast OS run on old and cheap hardware by people who are used to the limitations of that, netsurf is an adequate default browser IMHO
<missMyN900> maybe a whole new Maemo web browser can be developed from scratch (well, except for the rendering/JS engine obviously) eventually with special privacy and security features, strong integration with the OS etc, but until then netsurf-gtk is something that is relatively easy modify into something useful and that works well on all current popular ML devices
<missMyN900> @sunshavi: iwd is available in the Devuan Chimaera repositories so it definitely can work without systemd and could be used in Maemo Leste as well
Wikiwide_ has quit [Remote host closed the connection]
Wikiwide_ has joined #maemo-leste
<sicelo> i switched to iwd on Debian sid after reading a pmOS discussion on it ... it works. haven't really seen how 'better' it is. yes, has a nicer interactive shell (iwctl) than wpa_supplicant's (wpa_cli). anyway, i guess it's the future
Wikiwide_ is now known as Wikiwide
<missMyN900> sicelo: switching to connman+iwd from networkmanager+wpa_supplicant fixed my 5 GHz WiFi
<missMyN900> before I was not able to connect to my 5 GHz network with Debian 11. No 5 GHz networks would show up at all
<missMyN900> connman+wpa_supplicant worked extremely poorly though
xes has quit [Ping timeout: 246 seconds]
xes has joined #maemo-leste
<missMyN900> @sicelo: I loathe wpa_supplicant. I have NEVER gotten it to work manually, only with frontends. And I have very carefully followed the tutorials. OpenBSD's ifconfig is so much better than the mess networking is (or used to be at least) on Linux