belcher_ has joined #maemo-leste
sunshavi_ has quit [Remote host closed the connection]
belcher has quit [Ping timeout: 265 seconds]
cockroach has quit [Quit: leaving]
sunshavi has joined #maemo-leste
jk__000 has joined #maemo-leste
jk_000 has quit [Ping timeout: 250 seconds]
pagurus has quit [Ping timeout: 245 seconds]
Danct12 has joined #maemo-leste
joerg has quit [Killed (zinc.libera.chat (Nickname regained by services))]
joerg has joined #maemo-leste
rafael2k has quit [Ping timeout: 240 seconds]
freemangordon has quit [*.net *.split]
avoidr has quit [*.net *.split]
ikmaak has quit [*.net *.split]
[TheBug] has quit [*.net *.split]
blasty has quit [*.net *.split]
blasty_ has joined #maemo-leste
avoidr has joined #maemo-leste
ikmaak has joined #maemo-leste
freemangordon has joined #maemo-leste
[TheBug] has joined #maemo-leste
jk__000 has quit [Ping timeout: 240 seconds]
jrayhawk has quit [Quit: seuoia upgrades]
Pali has joined #maemo-leste
jrayhawk has joined #maemo-leste
uvos has joined #maemo-leste
Pali has quit [Ping timeout: 258 seconds]
jrayhawk has quit [Quit: leaving]
jrayhawk has joined #maemo-leste
rafael2k has joined #maemo-leste
<kshatriya> wlan on updated d4 died again - nothing showing in scan
<kshatriya> the available networks dialogue says "no connections available" but that disappears after 0.1 second and the dialogue is completely black
<Wizzup> kshatriya: hm, fully up to date?
<kshatriya> as of yesterday yes
<kshatriya> checking /var/log/messages has a lot of pvrsrckm_omap4_sgx540_120 errors - looking for something relevant to wlan
<kshatriya> Jul 26 02:53:21 ml1 kernel: [ 6.733489] platform regulatory.0: Direct firmware load for regulatory.db failed with error -2
<kshatriya> Jul 26 02:53:21 ml1 kernel: [ 6.733642] cfg80211: failed to load regulatory.db
<kshatriya> that looks like the culprit
<kshatriya> well no, that is the only thing i see.
<kshatriya> i can not conclude the thing i see is culprit
<kshatriya> j/
<kshatriya> there are no wlcore warnings in messages. the calibration was performed.
<Wizzup> Roal-Yr: we should be able to support the xt610 I guess
<Wizzup> kshatriya: odd, did the update complete properly? did you restart and is it still a problem?
<kshatriya> yes to both
<Wizzup> ok, as far as I know there really aren't any wifi-breaking changes now, so maybe something else happened to your device
<Wizzup> does apt complain about unfinished installation?
<Wizzup> is the wifi interface visible?
<kshatriya> thanks. if I find more info I will let you know
<kshatriya> ip a shows me a wlan0 interface state DOWN
<bencoh> try ifconfig wlan0 up
<bencoh> and open the connections dialog again
<kshatriya> same result.
<kshatriya> ok it was just the gremlins of wifi. starting up an AP nearby shows in the scan
<kshatriya> the normally visible access points are just not there for some reason
<kshatriya> the disappearance of the text in the networking dialogue is a bug though
<Wizzup> ok, so scanning itself (and connecting) is not broken
<Wizzup> tmlind: ok, mailed you some files
<Wizzup> hey juha replied :)
jrayhawk has quit [Quit: leaving]
jrayhawk has joined #maemo-leste
<uvos> can i have cc if you are discussing radiocomm settings?
<Wizzup> uvos: will forward
<kshatriya> after a minute or two the new AP is gone from scan results
<Wizzup> kshatriya: that is when they expire, that makes sense I think
<Wizzup> so it doesn't show even though it is still there?
<kshatriya> android phone still sees it, and two other networks
<kshatriya> iw dev wlan0 scan returns nothing
<Wizzup> oh, so we probably do not want to blame the ui then
<Wizzup> does maserati-calibrate help?
<sicelo> check scanning with wpa_cli if you can, instead of iw dev
<kshatriya> based on my reading maserati-calibrate should only be done after installing firmware-ti-connectivity*.deb
<Wizzup> there are a lot of xt610 on ebay: https://www.ebay.com/itm/144016066094?epid=99998236&hash=item218806c62e:g:1NcAAOSwd6pggHQ2
<Wizzup> kshatriya: those should be installed though
<Wizzup> uvos: btw I don't think the d3 does any 4g/lte
<uvos> Wizzup: no
<uvos> Wizzup: but you could also connect a d4
<uvos> Wizzup: since you will have it up and running
<Wizzup> uvos: radiocomm? yeah
<uvos> Wizzup: yeah
<Wizzup> not there yet, though
<kshatriya> Wizzup: uvos can tell you if re-running maserati-calibrate is advisable
<uvos> Wizzup: then again radiocomm v11.12 is so old (2009) that its sorta unlikely that it knows what to do with this chip
<uvos> kshatriya: no
<Wizzup> uvos: I could not find anything newer
<uvos> Wizzup: yeah i tried too
<Wizzup> are you sure it's that old
<Wizzup> I'm a bit surprised, I think I recall 2011 or so
<uvos> Wizzup: is says to
<uvos> i just installed it to a xp vm
<uvos> i cant use it tho
<uvos> since utagboot breaks all the access modes
<uvos> Wizzup: xt610 is not usefull unless you want to port leste to sholes
<dreamer> we need someone in the US: https://www.ebay.com/itm/144120942435
<uvos> Wizzup: i assume you have plenty of totaly stock d4's
* dreamer wants a 2nd d4 to experiment with
<kshatriya> sicelo: wpa_cli shows an address, wpa_state and uuid when asking for status. when running scal, wpa_cli returns no results
<kshatriya> *running scan
<Wizzup> uvos: yes, I do have some here
<Wizzup> dreamer: I mean I could send them to my work/office, but I have a lot of d4s, better if someone else gets it
<Wizzup> dreamer: lmk if you want me to get them here somehow
<Wizzup> kshatriya: for wpa_cli you also need to type scan_results
<Wizzup> uvos: what is sholes?
<uvos> at85x and friends.
<kshatriya> scan_results returns nothing
<uvos> *a85x and friends
<uvos> motorola phones with omap3 and ti pmic
<Wizzup> uvos: hm, I see omap3 at least yeah
<Wizzup> thought it would be similar to n900 maybe
<uvos> Wizzup: yeah it is
<uvos> it shares a kernel with a855 aka sholes
<uvos> these are omap3 refereance designes
<Wizzup> ah
<uvos> an the arch that preceded mapphone
<Wizzup> I am surprising you know this much :-D
<Wizzup> surprised*
<Wizzup> uvos: so winxp vm is what you did?
<uvos> Wizzup: yeah it needs 32bit
<Wizzup> wonder if I should just set up a winxp vm on my laptop and do usb passthrough
<uvos> if you start it on win10 i complains that you should download the 64bit version
<Wizzup> heh
<uvos> ofc we cant do that
<uvos> so you need 32bit windows
<dreamer> Wizzup: I was planning to buy one myself. which continent are you based atm? :P
<uvos> it installs lots of drivers
<uvos> so they really need to fit the win kernel bitedness
<Wizzup> dreamer: I am in europe, but I can order it to my office and have them ship it to me, but it won't safe much on import that way
<Wizzup> uvos: ok
<Wizzup> uvos: vm sounds better then
<dreamer> Wizzup: do you mean for those ebay units?
<Wizzup> dreamer: yes
<Wizzup> I guess you meant something else
<dreamer> no I wasn't 100% sure what we where talking about :D
<dreamer> I have some US contacts, will ask around if anyone is willing to do this. for that price it's not a huge risk. and I guess at least a few of that batch will work
<Wizzup> ok
<Wizzup> probably all of them will
<kshatriya> rmmod wl12xx and modprobe wl12xx, now i can scan again \o/
<Wizzup> bbiab
<Wizzup> kshatriya: odd.
inky has joined #maemo-leste
adc has quit [Quit: brb]
adc has joined #maemo-leste
jrayhawk has quit [Quit: leaving]
<dreamer> Wizzup: well it does say "
<dreamer> For parts or not working
<dreamer> Condition:
<dreamer> but perhaps just need battery replacements? :P
jrayhawk has joined #maemo-leste
<Wizzup> dreamer: I ordered 11 tablets that way and they're all 100% fine it seems
<dreamer> hehe
<dreamer> I asked madeddie if he would do it :)
<uvos> often sellers just cant be botherd to test such old devices
<uvos> makes sense i mean if you where to go and take the time to test them you would be getting almost nothing on hourly basis.
<dreamer> true, but testing a lot is generally easier then doing a single device
<dreamer> since you usually have to do the setup only once
<dreamer> anyway, lets see if we can get this batch in
cockroach has joined #maemo-leste
<uvos> ^^^ exaustive (to my knowlage) list of mapphones
<Wizzup> should we host that on the wiki somewhere?
<uvos> sure
<uvos> if you can convert that easy to a wiki table
<uvos> that might be best
<uvos> maybe wiki can take csv?
<Wizzup> wondering what wiki page to make though
<Wizzup> maybe it can be a category page with this info
<Wizzup> and then the mapphone can be part of that category
<Wizzup> uvos: isn't droid4 lte us only?
[TheBug] has quit [Changing host]
[TheBug] has joined #maemo-leste
<uvos> that collum means the only the us version has lte
<uvos> its not about the bands
<uvos> i have no idea if milestone 4 supports lte
<Wizzup> the same column says 'y us only' for some others
<uvos> right that means that there was a us and eu version
<Wizzup> (as opposed to 'y' for the droid4 and bionic)
<uvos> and the eu version dosent even have the chip
<Wizzup> aha
xmn has quit [Ping timeout: 265 seconds]
<Wizzup> (br dollars but still expensive!)
<uvos> i very mutch doubt
<Wizzup> (lots of milestone 3 on the website though)
<dreamer> Wizzup: ok, ordered to madeddie's place in NYC :D
<Wizzup> dreamer: neat
<dreamer> hopefully he can get them to me relatively cheaply ;)
<Wizzup> dreamer: mark them as 'for repair'
<Wizzup> (i.e. you'll be returning them after you repair them for him)
<dreamer> hehe
<dreamer> or as 'gift'
<dreamer> but 'for repair' is more accurate in a way :D
<kshatriya> the bottleneck isn't devices, it's developers
<Wizzup> :)
<dreamer> uhuh, madeddie will get one for sure. he's been meaning to play with maemo and sailfish back in the day. now he'll have a maemo-leste supported device ;)
<dreamer> will also put one at nurdspace for general showing off and hackery (I'm sure buZz will be pleased)
<dreamer> one at home for more dedicated testing
<dreamer> (compared to the `apt update` I run every other month now :D)
<Wizzup> neat
<Wizzup> uvos: I'll try to find some time later today to look again at the modem and stuff on the d3, since it has the same usbid, I think, and the kernel powers it up, but I just don't see a motmdm device
<buZz> dreamer: oooo nice
<dreamer> buZz: :) hopefully at his place in ~week and then another couple weeks to get here?
<buZz> could just wait for his next .nl visit?]
<dreamer> nah, he's not planning to come any time soon
<dreamer> at least easier to figure out shipping to .nl using him then some rando ebay seller ;)
<Wizzup> some ebay sellers to ship to .nl
<Wizzup> dreamer: but this way we get him to play with it, so yeah :p
<dreamer> :D
<kshatriya> it's a dream come true having 1GB RAM instead of 256MB, for maemo
<dreamer> :D
<dreamer> and two whole cores OMG
<Wizzup> with zram it is a bit more too
<kshatriya> two cores is a great win, giving final blitting to screen to one core, while other core run game full speed
<kshatriya> or video decoding
<kshatriya> droid4 can run full-resolution h265, in cpu only, using fastdecode tune
<buZz> wow really?
<buZz> thats amazing
<Wizzup> full-res you mean native, right?
<kshatriya> 960x540 yes, up to 30fps tested
<Wizzup> tbh our x setup could be quite a bit more optimised too I think
<buZz> i'd love to see that noise removed on powering up the device from sleep-ish
<Wizzup> hm?
<buZz> every time i press powerbutton on a 'sleeping' droid4 , i first get fullscreen of noise
<buZz> under 1 second, i guess
<uvos> yeah
<uvos> this started happening with kernel 5.10
<buZz> its minor, and doesnt seem to affect much
<kshatriya> https://talk.maemo.org/showthread.php?p=1572159 some tests and results. Power H265crf: 1760 mW
<uvos> btw for referance the cortex-a9 has about 125% the ipc of a8
<kshatriya> i haven't seen it buZz
<uvos> so over all the should d4 outperfrom the n900 by about 5x on parallel loads
<uvos> cpu wise
<uvos> omap5 adds a another, comparatively disapointing 50%
<Wizzup> I don't think there are omap5 phones, there is just the pyra, no?
<uvos> yeah
<kshatriya> and pyra didn't get the low-power omap5
<uvos> it was never made
<buZz> here's a vid showing the 'noise' on recovering from sleep ; https://streamable.com/21xpbq
<uvos> (milestone 5 prototype)
<Wizzup> neat
<buZz> bit hard to see i guess
<Wizzup> would be cool to find one of those
<uvos> clearer photo
<Wizzup> internet says:
<Wizzup> Inside, it will contain a MSM8960 Dual core Snapdragon Krait or S4 Plus processor chipset, an Adreno 225 GPU, with a RAM capacity of 1 Gigabyte to 2 Gigabytes, an internal built in storage capacity of 16 Gigabytes, powered by a 2,000mAh battery.
<buZz> -or- ?
<buZz> :D
<uvos> i kinda doubt the know...
<uvos> but yeah maybe
<buZz> > Diverging from recent Motorola Droid models, the Droid 5 might not have the Kevlar coating
<buZz> what
<buZz> droid4 had kevlar? :D
<uvos> no
<uvos> xt910
<uvos> has kevlar
<buZz> ah
<buZz> xt910 has a TI OMAP 4430
<buZz> :)
<Wizzup> yes
<Wizzup> see the ods that uvos linked
<buZz> ah, but no keyboard?
<bencoh> looks like a droid4 without keyboard
<buZz> hmhm
<uvos> x910 the supidest mapphone ever: a bionic with same display in a larger case and a smaller non removeable battery and no lte, relased 1 year after the bionic
<bencoh> huhu
<buZz> but kevlar! :)
<uvos> and slightly thinner!!!!!!!
<bencoh> I wouldn't call that 'stupid' but 'cheaper'
<bencoh> (manufacturing process)
<uvos> bencoh: it was more expensive
<bencoh> uvos: for the buyer, maybe
<uvos> yeah
<uvos> the redesign might have been because of the lawsuit from apple
<uvos> they got a patent on phones with rounded corners (thats not a joke) sued everyone
<uvos> i think thats why the moto devices immidatly after this affair have those wierd corners
<Wizzup> tmlind: any idea why the modem motmdm device would not show up?
<uvos> Wizzup: what mode are you in
<uvos> Wizzup: on a855
<uvos> the only one i ever used with radiocom
<uvos> you had to select one of the bp modes in the bootloader
<uvos> Wizzup: power on the deivce holding vol up and down at the same time
<uvos> mbm comes up with boot modes
<Wizzup> uvos: I don't mean radiocomm, I meant on leste
<uvos> oh right
<Wizzup> sorry, that was not clear
<Wizzup> I'm not ready for radiocomm yet, maybe tonight or tomorrow
<uvos> ok
<Wizzup> maybe it's related to the network lock somehow?
<uvos> do you have anything from it?
<uvos> is it on the usb bus?
<Wizzup> yes, it is on usb
<Wizzup> with the same usbids as d4
<uvos> ok
<Wizzup> and the usbtty's are there
<uvos> interupt might be somewhere esle
<Wizzup> which interrupt?
<uvos> the status gpios
<uvos> motorola,mode-gpios
<uvos> motorola,cmd-gpios
<uvos> motorola,status-gpios
<uvos> any of those might be wired somewhere else
<uvos> for board space reasons
<Wizzup> ok
<uvos> best compear the dts
<uvos> against maserati stock dts
<Wizzup> which I don't have converted to dts yet ;)
<Wizzup> ok
<uvos> just taking the dtb
<uvos> and diffing the binary section where all the gpios are defined
<uvos> would be enough
<uvos> its farly obvious in a hex editor
<Wizzup> it's a shame though since we have decompilers for dtb typcally
<uvos> best take a android 2.3 dts for maserati
<Wizzup> brb
<uvos> Wizzup: sure
<buZz> wow this tablet!
<buZz> first tablet i see with something of a hw keyboard :D
<kshatriya> only $1,711.53 too
<buZz> even pricier
<buZz> but that has omap4470 , so incompatible with our sgx stuff for 4430
<buZz> but also has a vivante for 2D
<Wizzup> the sgx is not limited to 4430
<uvos> *70 has a different sgx core
<uvos> but the ddk claims its for am44x0
<uvos> so should work
<buZz> ah well curious
<buZz> maybe i'll throw those devices in my ebay hunter, who knows
<Wizzup> maybe try to find the milestone 4 then ;)
<buZz> Wizzup: isnt that just a prototype?
<Wizzup> yes
<uvos> buZz: yeah all we know of it is that apearntly one got sold on german ebay.
<Wizzup> but it might have certain (signed) firmware that's very useful
<buZz> lots of milestone2's
<uvos> yes m2 was the last device sold in europe
<uvos> m3 was sold only in other regions (sa and asia)
<buZz> that intermec device is so tempting :P lol
<buZz> *quickly closes ebay*
xmn has joined #maemo-leste
akossh has joined #maemo-leste
<tmlind> Wizzup: sorry not sure what you mean modem does not show up, is this for radiocomm or something?
<Wizzup> tmlind: on leste, one sec
<Wizzup> I will boot it now
<tmlind> ok
<Wizzup> (booting now)
<tmlind> Wizzup, uvos: fyi, the modem can be made to show up on the pc usb bus with just some extra mux settings, that's all there is to the bp only mode i think really
<Wizzup> tmlind: still booting, but what I am seeing is the modem shows up in lsusb on the droid 3, and the kernel also shows that it powers it up and is successful in doing so, and I see /dev/ttyUSB{1,2,3,4}, but no /dev/motmdm1
<Wizzup> so ofono also doesn't pick the modem up
<tmlind> Wizzup: sounds like the /dev/gsmtty* related gpio pins are different
<Wizzup> ok
<Wizzup> so I do see this kind of stuff:
<Wizzup> Jul 26 18:42:52 localhost kernel: [ 11.208496] phy-mapphone-mdm6600 usb-phy@1: using device tree for GPIO lookup
<Wizzup> Jul 26 18:42:52 localhost kernel: [ 15.534454] phy-mapphone-mdm6600 usb-phy@1: Waiting for power up request to complete..
<Wizzup> Jul 26 18:42:52 localhost kernel: [ 18.504394] phy-mapphone-mdm6600 usb-phy@1: modem status: 4 awake
<Wizzup> Jul 26 18:42:52 localhost kernel: [ 18.510650] phy-mapphone-mdm6600 usb-phy@1: Powered up OK
<Wizzup> tmlind: sounds like what uvos said earlier then (and I will look into)
<Wizzup> 16:22 < Wizzup> which interrupt?
<Wizzup> 16:23 < uvos> motorola,status-gpios
<Wizzup> 16:23 < uvos> motorola,mode-gpios
<Wizzup> 16:23 < uvos> motorola,cmd-gpios
<Wizzup> 16:23 < uvos> the status gpios
<tmlind> Wizzup: check the gpios for motorola,mapphone-mdm6600 compatible
<tmlind> heh that's "only" 11 gpios to match :)
<uvos> yeah those are the ones i linked
<uvos> or mentiond rather
<tmlind> hmm the modem usb phy status sure looks ok above
<tmlind> maybe the revision is different if there's a check for it/
<tmlind> ?
<uvos> also enable and power
lyubov has quit [Ping timeout: 250 seconds]
<Wizzup> ok, will do
<tmlind> looks like we have no modem firmware revision check
<tmlind> Wizzup: try modprobe n_gsm debug=0xff and take a look at the traffic
lyubov has joined #maemo-leste
<Wizzup> tmlind: yeah I did that but didn't see any traffic I think
<Wizzup> anyway, let me move to the other place and try it out
<Wizzup> (looking at the pins)
<tmlind> ok
inky has quit [Quit: Leaving.]
inky has joined #maemo-leste
sunshavi has quit [Read error: Connection reset by peer]
sunshavi has joined #maemo-leste
lyubov has quit [Remote host closed the connection]
lyubov has joined #maemo-leste
<sicelo> buZz: haha, more like - remote controller (that tablet)
<buZz> sicelo: just imagine being a waitress in a small paris bar
<buZz> whipping out your MAEMO LESTE POS unit
<buZz> to take payment in bitcoin
<buZz> :)
<buZz> *nokia tune plays on churchbells in the background*
<sicelo> :P
<Wizzup> uvos: btw, you recommended that I downclock the droid3 because I saw some resets, right?
<uvos> Wizzup: yes the omap4 chip in d3 is a different version
<uvos> its rated to 1.0 ghz only
<uvos> your running it at 1.2ghz currently
<uvos> i strongly doubt that this is the reason
<uvos> but its something to try
<Wizzup> I think it is on 1Ghz actually, but I set it to 600 Mhz and it still happens
<Wizzup> I need to fix other things as well
<uvos> no
<uvos> its 1.2
<Wizzup> probably also keep in on serial and do pstore stuff etc
<uvos> i changed this
<uvos> myself
<Wizzup> uvos: well cpupower said 1000 I thikn
<Wizzup> in any case setting it to 600Mhz didn't help
<uvos> no its 1200000 1375000
<uvos> see &cpu in mapphone dtsi
<uvos> but yeah i doubt its the reason anyhow
<uvos> and 600mhz confirms this
<Wizzup> I think it happens when a lot of power is in use, screen brightness is still max
<uvos> Wizzup: try pstore
<Wizzup> uvos: yeah, need to make sure it survives kexec and stuff I guess, but too much going on at te same time
<Wizzup> if I don't open the display it's ine
<uvos> Wizzup: the battery might be deadish
<uvos> under load the voltage would then sag to mutch
<Wizzup> maybe
<Wizzup> it lasts like a day though
<uvos> the ir goes before the capacity goes
<uvos> usualy
<uvos> try loading it in android
<Wizzup> ok
<Wizzup> well, it's a very early port, we'll see
<uvos> run some benchmark or something in android and see i gues
<uvos> its not printing anything on serial right?
<uvos> when it crashes
<Wizzup> I haven't checked yet, I will
<uvos> remeber that we disabeld the serial console output in standart cmdline for d4/bionic
<uvos> in case you are copying that
<Wizzup> mhm
<Wizzup> argh, pulseaudio-modules-nemo just builds on my droid4 but not in jenkins
<Wizzup> I wonder if something removes the *.o files, or the timestamp causes problems or something
<kshatriya> imagine if phones had standard physical connectors on the edge, where radios approved for different regions could be snapped-on
<Wizzup> would be sweet
<Wizzup> parazyd: any idea how I can debug the armhf build failures on jenkins?
<Wizzup> parazyd: pulseaudio-modules-nemo fails only in jenkins
<Wizzup> the 'ar x' command in src/common/Makefile/am is never run
<Wizzup> Makefile.am
Pali has joined #maemo-leste
<uvos> kshatriya: will be really hard to have the fcc sign of on that, that was also a problem for project ara.
<kshatriya> is there a reasonable objection they could make?
<uvos> yes phones have lots of additional requirements regarding emmissions to users head, total emmisions in various directions etc that are impossible to cert except by certing every single combination of phone and radio
<uvos> so it will never work
<uvos> project ara had exactly this problem
<kshatriya> there is legitimate concern over glioblastomas, studies in france and netherlands with DECT phones etc.
lyubov has quit [Remote host closed the connection]
lyubov has joined #maemo-leste
inky has quit [Ping timeout: 240 seconds]
inky has joined #maemo-leste
akossh has quit [Quit: Leaving.]
<parazyd> Wizzup: Lemme check that in a little bit
<parazyd> Wizzup: Can you paste a link here pls?
<Wizzup> parazyd: ohi
<Wizzup> the ar x never happens
<parazyd> Wizzup: So seems you need to enable ARM_HARDFP?
<Wizzup> parazyd: yes, but the same happens on the d4
<Wizzup> same configure args
<Wizzup> and the error is not there
<Wizzup> parazyd: even if that's not enabled, there's still the other ar x
<Wizzup> parazyd: as in, if X86 is not defined, there has to be one 'ar x' at least no?
<parazyd> Yes
<parazyd> I don't have a charged d4 atm
<Wizzup> I built it on my d4 and it works
<parazyd> Did you compare cflags?
<Wizzup> that's the problem
<Wizzup> yeah they are the same
<parazyd> ok
<Wizzup> I think maybe it's timestamp related or something
<Wizzup> I don't know...
<parazyd> And on d4 you also build with dpkg?
<Wizzup> parazyd: yes
<parazyd> What if you try --no-parallel on debian/rules:17
<Wizzup> I was thinking that but then saw it was using -j1 in jenkins
<parazyd> I wonder if it's some weird quirk
<parazyd> ah
<Wizzup> see:
<Wizzup> make[1]: Leaving directory '/build/pulseaudio-modules-nemo-12.2.31+2m7.1'
<Wizzup> dh_auto_build -a
<Wizzup> make -j1
<parazyd> oh
<parazyd> wait
<parazyd> /usr/share/automake-1.16/am/ltlibrary.am: archiver requires 'AM_PROG_AR' in 'configure.ac'
<parazyd> You need to add this?
<Wizzup> check
<Wizzup> good catch
<Wizzup> let me see if that helps somehow
<uvos> hi parazyd ;)
<parazyd> Hey
<parazyd> Running late, I'll be around in the morning
<parazyd> (Visiting my parents on Brac)
<uvos> nice hf, ttyl
<parazyd> ttyl
<parazyd> Do write if there's anything I can help with
<Wizzup> I wish I could see the contents of the generated Makefile ;)
<kshatriya> fullscreen opengles is broken on D4
<kshatriya> diagonal lines
<kshatriya> once it happens, i need to reboot to get windowed opengles back to normal
<uvos> no
<uvos> "fullscreen" gles is not catigoricly broken
<uvos> please be more specific
<uvos> what is not working
<kshatriya> everything fullscreen. try glmark2-est --fullscreen
<uvos> neverball fullscreen works
<kshatriya> glmark2-es2 --fullscreen
<kshatriya> i'll try this thanks
<uvos> so dose clowd gps
<uvos> etc
<uvos> its possible glmark dosent work
<uvos> gles is buggy in general on d4
<uvos> note it is impossible for us to ever change this
<uvos> its closed source
<kshatriya> listing things that work can perhaps help me find what triggers it
<kshatriya> might be just related to egl, or sdl
<uvos> everything that uses gles must use egl
<uvos> so...
<kshatriya> after glmark2-es2 i get kernel panic / reboot with kernel:[ 297.050384] Internal error: : 1406 [#1] PREEMPT SMP ARM
<uvos> anyhow the egl implmentation is also closed source
<kshatriya> that should be illegal
<uvos> the kernel driver is known broken
<uvos> for complex reasons we will not fix it
<uvos> (instead we are working on hoepfully replacing it with a never code drop, incl kernel driver and binary userspace)
<uvos> however there are manny problems with this newer drop
<uvos> so its takeing a long while
<kshatriya> i will look into neverball . where can i find clowd gps
<uvos> its cloud gps
<uvos> unfortionatly the gpu drivers are and very likely allways will be terrible on sgx
<uvos> you need to comopile neverball yourself
<uvos> as the gles backend is not the default in debian
<kshatriya> do you know any 'reset powervr sgx to good state' besides rebooting?
<uvos> no
<uvos> not anything you can do without killing most of the usersapce
<kshatriya> then little time would be saved
<kshatriya> i have something cool to show as soon as i find this workaround
<kshatriya> neverball crashes here, neverputt runs fine in window but crashes with corrupted double-linked list when set to fullscreen
<kshatriya> several other games also result in corrupted double-linked list
<Wizzup> I think you need a neverball built for gles
<kshatriya> this is built for gles
<kshatriya> GL renderer: PowerVR SGX 540
<kshatriya> GL version: OpenGL ES-CM 1.1
<kshatriya> do you have a build that works in fullscreen Wizzup ?
<kshatriya> game has nice title music
<kshatriya> i'll keep experimenting
<Wizzup> nah, sorry, don't have that
elastic_dog has quit [Ping timeout: 252 seconds]
elastic_dog has joined #maemo-leste
Pali has quit [Ping timeout: 250 seconds]
kshatriya has quit [Ping timeout: 265 seconds]
kshatriya has joined #maemo-leste
<kshatriya> it's very helpful that the droid4 is cheap so i can run code on older image and kernel also
<Wizzup> you're stano, right?
<kshatriya> yes
<Wizzup> k
<Wizzup> confusing
uvos has quit [Ping timeout: 252 seconds]
BenLand100 has quit [Ping timeout: 240 seconds]
Treebeard has joined #maemo-leste
Treebeard has quit [Changing host]
Treebeard has joined #maemo-leste
Treebeard is now known as BenLand100