elastic_dog has joined #maemo-leste
elastic_dog is now known as Guest1530
dev has left #maemo-leste [Disconnected: closed]
joerg has quit [Ping timeout: 264 seconds]
joerg has joined #maemo-leste
macros_ has quit [Ping timeout: 248 seconds]
macros_ has joined #maemo-leste
xes has quit [Remote host closed the connection]
joerg has quit [Ping timeout: 268 seconds]
joerg has joined #maemo-leste
xes has joined #maemo-leste
akossh has joined #maemo-leste
dev has joined #maemo-leste
mardy has joined #maemo-leste
xes has quit [Read error: Connection reset by peer]
dev has left #maemo-leste [Disconnected: Replaced by new connection]
dev has joined #maemo-leste
xes has joined #maemo-leste
<freemangordon> Wizzup: what is this 'lima' var supposed to do?
<freemangordon> like, don;t we use the same mesa on all devices?
<Wizzup> I think it includes the lima component for mesa
<Wizzup> we have it for pinephone so I added it
<freemangordon> but isn;t it already there?
<freemangordon> I mean - in mesa for n900, for example?
<Wizzup> deb https://maedevu.maemo.org/${codename} ${release} main contrib non-free ${lima} ${devname}
<freemangordon> isn;t that obsolete?
<Wizzup> freemangordon: probably, I just did it anyway :)
<freemangordon> that's my point
<freemangordon> ah
<freemangordon> ok
<freemangordon> ok, I found SD card on my desk, and building u-boot is ok
<freemangordon> Wizzup: the issue is with dependencies
<freemangordon> they say we need some 'multilib' gcc
<freemangordon> but later on it fails to fing hardfp gcc
<freemangordon> *find
<freemangordon> now I only need a kernel
<freemangordon> Wizzup: will arm-sdk build DTBs for us?
<freemangordon> hmm, looks like yes
Twig has joined #maemo-leste
<Wizzup> freemangordon: it might, but it usually fails
ceene has joined #maemo-leste
<Wizzup> freemangordon: I was thinking of using the domains as layed out here for the talk https://wiki.maemo.org/Documentation/Maemo_5_Developer_Guide/Architecture/Top_Level_Architecture
<Wizzup> seems sensible, yeah?
<Wizzup> of course it would need to be updated
<freemangordon> do you have time to update that now?
<Wizzup> not the whole diagram no :)
<freemangordon> Wizzup: where shall I change the dependency so gcc-8-arm-linux-gnueabihf to be pulled instead of gcc-multilib in our image builder?
rafael2k has joined #maemo-leste
<freemangordon> that allows u-boot to be build
<Wizzup> I am not sure, it looks like various builds don't build u-boot or kernel because of missing packages
<Wizzup> I thought it was the resolv.conf problem that prevented it from being installed
<Wizzup> but that doesn't seem to be the case
<freemangordon> not, it is missing cross-compiler
<freemangordon> at least that's whaty happened here, in leste VM I am using for build
<Wizzup> yeah, that seems relevant, but I don't get really know where this is set up in arm-sdk or if it's even in arm-sdk
<freemangordon> no, it is in the VM we use
<freemangordon> we just need to install that there
<Wizzup> I can do that
<freemangordon> I guess
<freemangordon> please do and re-enable u-boot
<freemangordon> now I am trying to compile the kernel
<freemangordon> 5.18.y
<Wizzup> so I just install gcc-8-arm-linux-gnueabihf on the host?
<freemangordon> yes
<Wizzup> on the 32 bit image builder I guess
<freemangordon> this will remove gcc-multilib
<freemangordon> yes
<Wizzup> on the 64 bit one we also need a way to build arm64 kernel(s)
<Wizzup> since the raspi4 ones also fail
dev has left #maemo-leste [Disconnected: closed]
<Wizzup> ok, it's installed
<freemangordon> do we have failure log?
<Wizzup> yes
dev has joined #maemo-leste
<freemangordon> ok, I will look at it later on
<Wizzup> so you want me to re-enable u-boot and rebuild the sunxi image?
<freemangordon> yes
<freemangordon> umm...: "Finished: SUCCESS"
<Wizzup> scroll up
<freemangordon> ok
<Wizzup> btw, the sunxi build failed in some python thing for me
<Wizzup> (u-boot)
<Wizzup> Traceback (most recent call last):
<Wizzup> File "scripts/dtc/pylibfdt/setup.py", line 21, in <module>
<Wizzup> ModuleNotFoundError: No module named 'distutils.core'
<Wizzup> from distutils.core import setup, Extension
<Wizzup> make[3]: *** [scripts/dtc/pylibfdt/Makefile:27: scripts/dtc/pylibfdt/_libfdt.so] Error 1
<Wizzup> that is why I disabled it
<Wizzup> and yes we could install that package
<freemangordon> make: aarch64-linux-gnu-gcc: Command not found
<freemangordon> exactly the same issue
<freemangordon> missing cross-compiler
<Wizzup> that is for kernel, but u-boot also fails
<freemangordon> Wizzup: apt install gcc-aarch64-linux-gnu
* freemangordon checks
<Wizzup> I can install python3-distutils, but idk if it's using python 3
<freemangordon> lemme check if I have it here
<Wizzup> both python2 and python3 have distutils, on the host
<Wizzup> ah, python3 does not have distutils.core
<Wizzup> I solved it with python3-distutils
xmn has quit [Ping timeout: 268 seconds]
<Wizzup> shall I issue a new build of the sunxi image?
<freemangordon> I have python3-distutils 3.7.3-1 here
<freemangordon> yes, lets check that at least u-boot is ok
<freemangordon> in the meanwhile I am checkoing if kernel bui;ds
<freemangordon> tooks a while, my machine is slow :)
<freemangordon> *takes
<Wizzup> image builds also take 1-2 hours
<freemangordon> ugh
<freemangordon> I tried to run image builder on my laptop with ubuntu
<Wizzup> hence me reverting to uglier fixes ealier
<freemangordon> no dice
<Wizzup> :)
<freemangordon> when I have some spare time I will install leste VM there
<freemangordon> this pal is 4 cores i7 (HT) + 1TB SSD :)
<freemangordon> I guess it will need 20 minutes to build an image
macros_2ndPC has joined #maemo-leste
macros_ has quit [Ping timeout: 260 seconds]
Twig has quit [Read error: Connection reset by peer]
<Wizzup> brb
xmn has joined #maemo-leste
elastic_1 has joined #maemo-leste
elastic_dog has quit [Killed (osmium.libera.chat (Nickname regained by services))]
elastic_1 is now known as elastic_dog
uvos__ has joined #maemo-leste
Twig has joined #maemo-leste
alex1216 has joined #maemo-leste
<freemangordon> the fuck :( "dd: error writing '/home/user/imgbld/image-builder/arm-sdk/tmp/devuan-armhf-build/maemo-leste-1.0-armhf-sunxi-20221014.img': No space left on device"
<Wizzup> where?
<Wizzup> ah
<freemangordon> in my VM :)
<Wizzup> df -h ?
<Wizzup> :)
<freemangordon> it does not lie
<freemangordon> I will have to extend rootfs
pere has quit [Ping timeout: 268 seconds]
pere has joined #maemo-leste
dev has left #maemo-leste [Disconnected: Replaced by new connection]
dev has joined #maemo-leste
dev has left #maemo-leste [Disconnected: Replaced by new connection]
<freemangordon> Wizzup: do yuu know if those tablets come with li-po or li-ion batteries and does it make any difference for the replacement?
<freemangordon> *you
<Wizzup> the q8 ones?
<freemangordon> mhm
<Wizzup> no idea sorry
<Wizzup> is your battery dead?
<freemangordon> yep
<Wizzup> too bad
<freemangordon> I will have to find a replacement
<freemangordon> it is some 2800mAh cell
<freemangordon> shouldn't be hard to find
<freemangordon> even mobile phone battery should be ok
xmn has quit [Ping timeout: 248 seconds]
<buZz> freemangordon: lipo vs liion should not matter for most chargers
<buZz> both are empty at 2.8 full at 4.2 , and do CCCV charging
<buZz> the biggest difference for a phone, is that lipo slightly expands during its lifespan
<freemangordon> this is a tablet
<freemangordon> and it has lots of space I think
Twig has quit [Ping timeout: 250 seconds]
dev has joined #maemo-leste
<Wizzup> freemangordon:
<Wizzup> scripts/dtc/pylibfdt/libfdt_wrap.c:149:11: fatal error: Python.h: No such file or directory # include <Python.h>
<Wizzup> more pkgs are necessary I guess
<Wizzup> (python3-dev)
<buZz> freemangordon: then you can go crazy :P
<buZz> my fav is just connecting a 18650 batteryholder on the back with wires :D
<buZz> like this tomtom ; https://i.imgur.com/TgLO7Zs.jpeg
<Wizzup> brainparty works on the lime2
<Wizzup> everything works great except for exiting the application, that hangs
<Wizzup> lol
<buZz> hehe
<Wizzup> I might try to fix that after the presentation is done just to make it more demo-able
<freemangordon> omg
<Wizzup> since it's a great demo
Twig has joined #maemo-leste
<Wizzup> freemangordon: it's alive again?
<freemangordon> which one? q8?
<freemangordon> Wizzup: do you know where it puts the kernel?
<Wizzup> freemangordon: the sunxi image? probably /boot
<Wizzup> or, what is it?
<uvos__> hmm brainparty dosen work on the d4
<freemangordon> is it ok to replace 2800mAh with 2600mAh?
<uvos__> i mean it kinda works, but touch is messup sometimes and it segfaults often when starting a new challange
<uvos__> freemangordon: yes
<freemangordon> ok, thanks
<Wizzup> uvos__: yes, it's resolution related
<Wizzup> uvos__: and maybe also screen orientation
<freemangordon> uvos__: shall I keep the original electronics?
<uvos__> yes - its probubly nessecary
<uvos__> often the device will read an eeprom or refuse to charge wihout a thermistor it expects etc
<freemangordon> the new one comes with alectronics as well
<freemangordon> this is cheapo allwinner tablet
<uvos__> right but probubly not what it expects
<freemangordon> ther are only 2 wires
<uvos__> then it dosent matter
<freemangordon> ok
<uvos__> you can keep the bms that comes with the battery in this case
<freemangordon> bms?
<freemangordon> s?
<freemangordon> schematic?
<uvos__> system
<uvos__> battery managment system
<freemangordon> ok
<uvos__> the "BMS" i this case is just a chip that disconnects the battery if it goes above 4.25 or below 2.9 usually
<uvos__> in multi cell batteries its also resposable for balanceing
<uvos__> but that dosent apply here
<freemangordon> yeah
<freemangordon> thanks
<buZz> uvos__: hey i had dual screen sorta working on d4 :D
<buZz> with something like > xrandr --fb 1920x1080 --output LVDS1 --mode 1600x900 --scale-from 1920x1080 --output HDMI1 --mode 1920x1080 --scale 1x1 --same-as LVDS1
<buZz> (it can scale outputs that are mirrored to other resolutions!)
<buZz> but, a issue appeared; the DSI-1 output is rotated :P
<uvos__> sure that applies a transformation matrix
<uvos__> i mentioned this works
<uvos__> however its not accelerated
<buZz> yeah, its cool :)
<uvos__> shuld be very slow
<buZz> it did work pretty fast, not really noticably slow
<uvos__> hm ok
<buZz> also, -booting- d4 with HDMI attached gets you a dual video output aswell
<buZz> but something gets seriously confused , and ends up just disabling all video outputs :P
<uvos__> wierd that its fast enough
<uvos__> freemangordon: do you know if omapddx accelerates transformation matrixices?
<buZz> uvos__: the matrix would just be x2/4 btw, 960 * 2 = 1920 , 540 * 2 = 1080
<uvos__> freemangordon: ie xrandr --outputie --transform
<Wizzup> is pkgmaster.devuan.org slow for anyone else?
<buZz> that might help the speed
<buZz> 12ms ping Wizzup
<uvos__> buZz: maybe it optimizes that yeah
<uvos__> buZz: can you try some other matrix?
dev has left #maemo-leste [Disconnected: Replaced by new connection]
<Wizzup> buZz: I mean I got 4kB/s after a few seconds
dev has joined #maemo-leste
<Wizzup> s/got/get/
<buZz> isnt pkgmaster. a round robin?
<Wizzup> well I get the same robin :)
<uvos__> something like xrandr --output DSI-0 --transfrom <whatever non integer scaleing>
<buZz> lets see
<freemangordon> Wizzup: it is extremely slow
<freemangordon> uvos__: no idea
<buZz> uvos__: 'xrandr --output DSI-1 --scale-from 800x600' -> black screen
<freemangordon> uvos__: but copy with resising is accelerated through gpu
<freemangordon> *resizing
<freemangordon> or rather all copies
<uvos__> buZz: ^^ ok that explains it for trivial matricies
<buZz> ah, cool, that might help to make some 'maemo friendly' videooutput :)
<uvos__> (--scale-from just applies a simple matrix)
<buZz> yeah
<uvos__> that also explains why rotation dosent work
<buZz> i think it would be nice to just have a 'enable screen mirror' option somewhere
mardy has quit [Read error: Connection reset by peer]
<uvos__> if you have a rotated primary and a non rotated secondary
<buZz> i didnt try to rotate myself yet
<uvos__> x has to rotate the buffer for one output
<buZz> it might just work through a transformation matrix aswell?
<uvos__> but it cant unless you accelerate non trivial matricies too
<buZz> hmhm
<uvos__> yes thats how modesetting works
<freemangordon> and is slow as snail
<uvos__> no
<buZz> rotating is slow?
<freemangordon> yes, see on PP
<uvos__> the sw fallback is slow
<uvos__> that works totaly differantly
<buZz> freemangordon: but we're rotating 24/7 on d4
<uvos__> buZz: yes
<uvos__> thats not modesetting
<freemangordon> buZz: but, we use TILER to rotate
dev has left #maemo-leste [Disconnected: closed]
* buZz confused :)
<buZz> freemangordon: ah
<uvos__> the sw fallback of modeseting to rotate the display
<freemangordon> buZz: uvos__ was just giving an example
<uvos__> dosent use the transformation matrixies
dev has joined #maemo-leste
<buZz> and i guess TILER doesnt want to do differnent stuff on multiple outputs?
<uvos__> it uses a custom function to rotate the frame
<freemangordon> it does whatever you tell him to do
<buZz> hmm :)
<freemangordon> the issue is not with tiler but with rendering
<Wizzup> buZz: what about hdmi capture device with the same res as the d4 screen?
<buZz> Wizzup: seems my capture unit doesnt like 960x540 :/
<buZz> maybe i can get xorg to see 1920x1080 as 2/4x smaller?
<buZz> but , the rotation is still a slight issue then
<buZz> oh yeah, connecting a USB mouse, enabling HDMI as primary, restarting hildon, gets you mousecursor on the LCD (rotated) , and all maemo output to HDMI :P so weird
<Wizzup> that's unfortunate @ capture unix
<uvos__> 960x540 is a unloved resoultion for some reason
<uvos__> really theres no good reason any 1080p pannel should not accept it as an input
<uvos__> but they dont
<uvos__> at least in edid
<uvos__> often they do all kinds of resolutions if you force it via modeline
<Wizzup> yeah
<buZz> yeah i'll need to try that, but will have to be later, otherjob today
<Wizzup> :)
<Wizzup> I have brainparty working I think now, without hang upon exit
<Wizzup> so I'm happy
<Wizzup> these was a hang in a pthread join in the audio closing
<buZz> w00t
<Wizzup> I justcommented it since it was just before sdl_quit anyway
<Wizzup> will figure out a proper fix later :p
<buZz> hmm last i tried brainparty did work on d4 btw
<Wizzup> yeah but it's buggy
<uvos__> it "wroks"
<Wizzup> > 4,553 B/s 24min 46s
<Wizzup> :(
<buZz> yeah just works here, but touchscreen is confused because of smaller window?
<Wizzup> brainparty was never made for anything other than 800x480
<buZz> ah no, its accurate, just a bit smaller
<buZz> right
<Wizzup> there is a newer version for different screens
<uvos__> somhow the coordinates get confused
<uvos__> also it sefaults alot
<Wizzup> but I never tried to reconcile them
<buZz> Wizzup: we'd have to rework all the graphics?
<uvos__> *segfaults
<Wizzup> the author made newer versions
<buZz> or just stretch perhaps
<buZz> ah ok
<uvos__> buZz: the version we have is an ainchent maemo one
<uvos__> theres a desktop linux one that supports more
<uvos__> thats newer
<buZz> k k
<Wizzup> but the maemo one is nice :D
<uvos__> on n900 maybe
<Wizzup> on this lime2 tablet as well :)
<uvos__> it also segfaults on n900 for me btw
<uvos__> when loading the next game
<Wizzup> just tried it
<uvos__> ok
<Wizzup> ?
<uvos__> yeah
<Wizzup> I suspect this might be (more) libsdl stuff
<uvos__> more like a bug in brainparty that old libs wher hideing
<Wizzup> maybe
<Wizzup> did you attach gdb?
<uvos__> no, i have to say, brainparty was never a priority before :P
<Wizzup> :D
<Wizzup> I just want to attracts folks to the stand ;)
<Wizzup> attract*
mardy has joined #maemo-leste
<buZz> also, closing brainparty just worked
<Wizzup> yeah, maybe it's related to no audio on the lime
<Wizzup> not sure
<buZz> ah hmhm
<Wizzup> (the lime2 has no audio port, you have to use the pins unfortunately)
<buZz> maybe hookup a usb soundcard?
<Wizzup> then we'd need headphones or speakers as well
* buZz hands Wizzup 10kg of amplified speakers
<buZz> :P
<buZz> which gps application is nicest on d4 to grab maps over gprs and show (and maybe record) gps location?
<buZz> maep?
<Wizzup> I like maep, but others work too
<Wizzup> cloudgps can be 'smooth'
<Wizzup> but maep is my preferred one usually
<Wizzup> there's also modrana which is more featured
<Wizzup> and one uvos uses but it is not hildonized iir
<Wizzup> c
<buZz> navit
<Wizzup> could be yes
<uvos__> yes navit
<buZz> i got em all installed now, i'll try to record some while in the car today
<uvos__> navit is the only one of these that works offline
<Wizzup> looks like there is a maemo navit, I remember I looked at this before
<Wizzup> uvos__: does it also do routing?
<buZz> navit doesnt grab maps dynamically at all
<uvos__> Wizzup: yes
<Wizzup> if you could make a guide some times :)
<Wizzup> I would love that
<buZz> uvos__: really? doesnt navit require some external daemon for routing?
<uvos__> no
<uvos__> or maybe its included in the devuan package
<buZz> oh
<uvos__> it just works
<buZz> nice :)
<buZz> maybe i should quickly put a navit map dump on my d4
<Wizzup> if it works semi well I'm happy to work on porting the hildon port
<buZz> navit is quite amazing, they also have a whole distro they maintain for those ancient tomtoms
<uvos__> it works but: its really really slow (even on a very fast pc), the ui is "touch optimized" and intended for in dash navigation but ultra klunky and counter intuative, configuring it via its xml file is a pain
<buZz> > OpenTom fork NavitTom on a 2007 Tomtom One XL new OSM maps
<buZz> slow gets a new definition there ;) takes ages to boot, start up , etc
<uvos__> the wierd thing with navit
<buZz> but, does work
<uvos__> is that the map rendering takes constant time
<uvos__> dosent matter if its on a droid4 or a ryzen9
<uvos__> and its allways slow
<uvos__> its like it dose sleep(1) before rendering a map tile xD
<buZz> :P
<uvos__> also idk what you would hildonize even
<uvos__> it uses sdl to render its own ui
<buZz> yeah, like cloudgps (?)
<buZz> which is somehow hildonizing itself, it seems
<uvos__> theres not mutch here to do except maybe use liblocation instead of gpsd
<uvos__> buZz: i renders a ui that sorta looks like hildon
<uvos__> thats all (for cloudgps)
<buZz> ah yes, that was some issue, gpsd doesnt start normally
<buZz> uvos__: oo thats right, navit has 'ui layouts' in xml files
<buZz> maybe we can make a 'hildon-esque' xml layout
<uvos__> buZz: yes
<uvos__> buZz: but have a fun time changeing anything
<buZz> :D
<buZz> yay! funtimes are fun
<Wizzup> there is/was gtk
<Wizzup> whic iirc the hildon one uses
<uvos__> there are also different frontends
<uvos__> theres a qt one the default sdl one and there used to be a gtk one untill it was removed
<uvos__> they are universaly terrible
<buZz> :)
<uvos__> its like some alien decided to do a humanz ui :P
<buZz> navit is a weird bunch :P but they are very helpful on github
<uvos__> they are clearly aliens that are preparing the invasion by implementing mapping systems of earth to use
<buZz> osm_bbox_2.9,50.7,7.3,53.8.bin 61% 979MB 277.3KB/s 38:24 ETA
<buZz> pfff
<buZz> keeps hanging during transfer a lot
<buZz> really start to think something is wrong on my d4 which 'disk io'
pere has quit [Ping timeout: 246 seconds]
<freemangordon> Wizzup: 5.18 does not boot :(
<freemangordon> what's worse is that there is nothing on the screen
<uvos__> buZz: iw phy phy0 set txpower fixed 1000000000
<uvos__> try that
<uvos__> for some reason sometimes the wifi fw dosent ramp up tx power on auto
<uvos__> when its clearly nessecary to not get terrible packet loss
<uvos__> maybe is also kerel bug instead of fw
<uvos__> *kernel
<Wizzup> freemangordon: mhm
<freemangordon> I found an old kernel here, trying it now
<freemangordon> no dice :(
<freemangordon> well, that kernel seems to boot at least
<freemangordon> hmm, maybe I was not patient enough
<freemangordon> or mce licked the screen :)
<freemangordon> *locked
<freemangordon> "no space left on the device" :)
<freemangordon> seems 2GB are not enough
<freemangordon> "welcome to leste" :)
<freemangordon> colors are weird and TS does not work
<Wizzup> freemangordon: /etc/expandcard.sh ?
<freemangordon> I did that with gparted
<buZz> does gparted also resize the fs?
<freemangordon> yes
<buZz> nice
<buZz> oh, the SD card is literally just 2GB? :)
<freemangordon> Wizzup: we have the same issue 32bit vs64bit, do you rmember?
<freemangordon> *remember
<freemangordon> when we build 32 bit image on 64bit
<Wizzup> sorry, what issue?
<Wizzup> yes I remember, something with themes
<freemangordon> missing icons/pixmaps etc
<freemangordon> yes
<Wizzup> it was some qemu / glib thing iirc
<freemangordon> yes
<freemangordon> oh, sorry
<freemangordon> it is my fault
<freemangordon> :)
<Wizzup> so you have some life in the tablet?
<freemangordon> my VM is 64 bits
<freemangordon> yes
<Wizzup> cool
<freemangordon> unfortunately with some old kernel
<Wizzup> mhm
<freemangordon> 4.11
<Wizzup> might be mali even (not lima)
<freemangordon> FB even :)
<Wizzup> right
<freemangordon> will ask on #linux-sunxi later on
<Wizzup> they're on oftc now I think
<freemangordon> sees so
<freemangordon> yes. and does not boot :)
<Wizzup> mhm, at least on your tablet
<Wizzup> do you have serial?
<freemangordon> ah, which kernel is that?
<freemangordon> 5.11?
<Wizzup> uh
<Wizzup> yes
<Wizzup> 5.11.y
<freemangordon> do not change it, lets see if it will boot here
<Wizzup> it's still on uboot btw, I was wrong
<Wizzup> let's see if kernel builds though
<freemangordon> it will
<Wizzup> the image-builder's are on hdd now, not on ssd
<Wizzup> maybe I should move them back once I have a bit of time
<buZz> Wizzup: with bcache you could use (a part of) your SSD to cache the HDD
<buZz> at nurdspace i made a bcache on a raid0 over two nvme drives for a raid1 on hdds , gets ~1.5GB/s reads now
<Wizzup> this is a qemu qcow image
<buZz> if its on a blockdevice, you could add bcache
<Wizzup> it's not
<buZz> but i think you'd have to reinitialize it
<buZz> the image file isnt on a blockdevice?
<Wizzup> it's on a btrfs fs
<Wizzup> which consists of 6 block devices
<Wizzup> so please let's not go down the path
<buZz> yeah i think thats still supported
<Wizzup> I'm not interested in bcache
<buZz> ok :)
<Wizzup> buZz or uvos__: how does one go about connecting a bt keyboard
<Wizzup> assuming bt drivers work etc
<buZz> you could apt install blueman
<buZz> and connect it with that
<buZz> but i havent tried keyboards yet, headphones and speakers work though
<buZz> its a gtk gui, i think
<Wizzup> ok
<Wizzup> buZz: it's not obvious how to use it, but maybe I am missing something
<Wizzup> it looks like it just backgrounded
<buZz> oh yeah, its very unobvious indeed
<Wizzup> ah hcitool sees no device
<Wizzup> ok then
<Wizzup> won't bother
<sicelo> iirc hcitool is deprecated:-(
<Wizzup> in any case there's no bt device seen
<buZz> did you remove the blacklisted bt?
<buZz> at least on d4 afaik its still blacklisted
<buZz> not sure
<Wizzup> this is rpi
<buZz> ah
<buZz> not all rpi have bt iirc
<Wizzup> rpi4 does
<Wizzup> p sure
<buZz> but might not be in the image then
<Wizzup> I made the image
<buZz> yeah pi4 should
pere has joined #maemo-leste
<buZz> random tutorial installs 'pi-bluetooth' on it
<uvos__> buZz: modprobe hci_uart, start bluez, have blueman installed
<Wizzup> on d4/bionic I guess?
<uvos__> run blueman-manger
<buZz> seems pi4 has firmware needed for bt that isnt in other package?
ceene has quit [Remote host closed the connection]
<uvos__> search for a device, click on it pair
<uvos__> etc
<uvos__> everything works pretty much as expected from that point
<uvos__> i use it all the time
<uvos__> Wizzup: yes
<uvos__> but on other devices it should be the same
<uvos__> besides the modprobe of the mapphone driver ofc
<buZz> seems pi4 also uses hciuart
<uvos__> haveing bluez running costs a tone of power tho
<uvos__> on d4
<uvos__> so better exit it right after
<buZz> uvos__: this is probably for the demos at booth, so likely has power available
<Wizzup> yes
<uvos__> sure im just saying i use it daliy on d4
<uvos__> but have to stop bluez
<buZz> alright, maybe some day we can reduce that powerdraw
<Wizzup> starting bluez, that is /etc/init.d/bluetooth start ?
<buZz> yeah
<buZz> should be ..
<buZz> don't think i ever started it differently :P
<Wizzup> freemangordon: oh right I forgot that for sunxi I had also disabled the kernel build by skipping it
dev has quit [Quit: Gateway shutdown]
norayr has quit [Quit: Gateway shutdown]
norayr has joined #maemo-leste
norayr has left #maemo-leste [#maemo-leste]
norayr has joined #maemo-leste
norayr has left #maemo-leste [#maemo-leste]
norayr has joined #maemo-leste
uvos__ has quit [Ping timeout: 248 seconds]
macros_ has joined #maemo-leste
macros_2ndPC has quit [Ping timeout: 264 seconds]
norayr has left #maemo-leste [Error from remote client]
norayr has joined #maemo-leste
xmn has joined #maemo-leste
<Wizzup> freemangordon: for some reason I had to set roamingallowed to true for my a1 bg sim to work here
<Wizzup> on leste
<Wizzup> the ui would blink forever
<Wizzup> the mdbus command failed immediately with 'gprs not attached'
<Wizzup> setting roamingallowed to true made it work
<freemangordon> weird
<Wizzup> yup
Twig has quit [Remote host closed the connection]
rafael2k has quit [Ping timeout: 268 seconds]
<Wizzup> got stickers :p
rafael2k has joined #maemo-leste
norayr has left #maemo-leste [Error from remote client]
norayr has joined #maemo-leste
rafael2k has quit [Ping timeout: 268 seconds]
<freemangordon> Wizzup: Oct 14 15:51:56 localhost kernel: [ 0.126953] [drm] Initialized lima 1.1.0 20191231 for 1c40000.gpu on minor 0
<freemangordon> this is with 5.15
alex1216 has quit [Quit: WeeChat 2.3]
<Wizzup> freemangordon: that is good, right?
<freemangordon> mhm
<freemangordon> I have to play a bit because of the panel, but that should be trivial
<Wizzup> ok
<Wizzup> great :)
<freemangordon> TS is tricky too
<freemangordon> anyway, going on a ride, ttyl
<Wizzup> ttyl
uvos has joined #maemo-leste
<buZz> meh :(
rafael2k has joined #maemo-leste
<buZz> recorded a 6hr track on Maep , went to 'export' , selected location , (no save button???) tapped outside of panel, Maep closed/crashed and zero recorded track
<buZz> :(
<rafael2k> what is this version "+2m7"?
<rafael2k> should I use in new packages too?
<buZz> m7 = maemo 7?
<buZz> (aka leste)
<rafael2k> ah
<rafael2k> right
<rafael2k> : )
<rafael2k> Unpacking connui-conndlgs-internet (2.79.7+2m7) over (2.79.6+2m7) ...
<rafael2k> dpkg: dependency problems prevent processing triggers for gconf2:
<rafael2k> gconf2 depends on default-dbus-session-bus | dbus-session-bus; however:
<rafael2k> Package default-dbus-session-bus is not installed.
<rafael2k> Package dbus-session-bus is not installed.
<rafael2k> Package dbus-x11 which provides dbus-session-bus is not configured yet.
<rafael2k> apt-get upgrade just broke here
<rafael2k> it gets in a look
<rafael2k> *loop
<rafael2k> :(
<buZz> tried apt-get -f install ?
<buZz> just without a pkg behind it
<rafael2k> yes
<buZz> :(
<rafael2k> crazy loop
<buZz> dpkg-reconfigure dbus-x11 ?
<rafael2k> never saw this before in 12 yrs using debian
<rafael2k> 12 no, much more
<rafael2k> lemme try to fix
<rafael2k> dpkg: dependency problems prevent processing triggers for gconf2:
<rafael2k> gconf2 depends on default-dbus-session-bus | dbus-session-bus; however:
<rafael2k> Package default-dbus-session-bus is not installed.
<rafael2k> Package dbus-x11 which provides dbus-session-bus is not configured yet.
<rafael2k> Package dbus-session-bus is not installed.
<rafael2k> dpkg-reconfigure dbus-x11
<rafael2k> dbus-x11 is broken or not fully installed
<buZz> :(
<buZz> was this just a update on leste today?
<rafael2k> I dunno
<rafael2k> I did not do a apt-get upgrade in some days...
<rafael2k> I did not manage to unbreak yet
<rafael2k> uff
<rafael2k> unbroke
<buZz> :(
<rafael2k> force-removed dbus-x11 and installed it again
<rafael2k> : )
<buZz> fixed?
<rafael2k> yeap
<rafael2k> good ol' debian... it seems it is not unix... but it is
<buZz> ooo new xorg-video-omap again? does it implement Vulkan now? :D
<rafael2k> wow
<rafael2k> I get some crazy shit
<rafael2k> iphb?
<buZz> (highly doubt it'll be vulkan)
<buZz> what kind of crazy shit?
<rafael2k> Your kernel headers for kernel 5.15.7-3-MANJARO-ARM cannot be found at
<buZz> ... MANJARO? :D
<buZz> what device is this?
<rafael2k> Your kernel headers for kernel 5.9.0-rc7-00376-g2e49b58e9b10 cannot be found at
<rafael2k> Maemo-West
<rafael2k> Wild Wild West
<buZz> maemo -west- ? :D
<buZz> lol
<buZz> weird image you're running rafael2k :D
<rafael2k> Your kernel headers for kernel 5.10-sunxi64 cannot be found at
<rafael2k> just apt-get'd dist-upgrade !!
<buZz> what device are you using rafael2k ?
<rafael2k> the same image from 2 years ago I never changed
<rafael2k> PP
<buZz> ok .. well i did see Wizzup do some sunxi stuff today, maybe some packages got updated incompatible?
<buZz> i'll try updating the PP here
<buZz> btw i never do dist-upgrade
<buZz> only on upgrading distributions :)
<buZz> i'll try dist-upgrade now, yeah , nothing
<buZz> 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
<rafael2k> hum
<rafael2k> do you use -devel?
<rafael2k> iphb-dkms
<rafael2k> try this ^
<buZz> how could you do -dkms if our kernels dont have source?
<buZz> but i do have that installed
<buZz> iphb-dkms/testing,now 1.2+2m7.2 all [installed,automatic]
<rafael2k> : )
<rafael2k> so all good
<buZz> oh i guess just -headers is enough
<rafael2k> true
<rafael2k> interesting I have not asked to install this package
<rafael2k> it was a dependency of something else
<buZz> yeah might be pulled in by a metapackage i guess
<rafael2k> uhum
<rafael2k> me no like
<rafael2k> :P
<rafael2k> hildon-connectivity-something
<buZz> afaiui iphb can help us reduce powerusage a lot on some applications
<rafael2k> we could at least put the linux-headers as depency
<rafael2k> dependency*
<rafael2k> right, first time I hear about it
<buZz> me too (when i saw it suddenly in this channel)
<buZz> i think its from maemo too
<rafael2k> cool
rafael2k has quit [Ping timeout: 260 seconds]
rafael2k has joined #maemo-leste
rafael2k has quit [Ping timeout: 260 seconds]
norayr has left #maemo-leste [Error from remote client]
norayr has joined #maemo-leste
norayr has left #maemo-leste [#maemo-leste]
norayr has joined #maemo-leste
<norayr> they say pocophone and plus6 (with same soc) work with mainline very well. does anyone have one of those to support with maemo?
<Wizzup> I think maybe parazyd tried for the pocophone
<norayr> eh.
<norayr> it is the fastest device which supports mainline as i understand.
<sicelo> yes, lots of devs working on that SoC, so progress is quite good
mardy has quit [Quit: WeeChat 3.5]
<Wizzup> what I mean is that arm-sdk supports pocophone
<uvos> pocophone wored
<uvos> *worked
<uvos> and had an image even
<uvos> but it hasend been tested in quite some time
<uvos> but yeah its an interesting non-mapphone to support i have it on a short list next to xt1602 and friends to try
<uvos> oh look related article on the bbc news main page: https://www.bbc.com/news/science-environment-63245150
<buZz> yeah nice, i didnt have any trouble with iphb-dkms though
<buZz> rafael2k had issues around dbus-x11 i hink?
danielinux has quit [Ping timeout: 248 seconds]
xmn has quit [Ping timeout: 260 seconds]
akossh has quit [Quit: Leaving.]
elastic_dog has quit [Ping timeout: 264 seconds]
elastic_dog has joined #maemo-leste
uvos has quit [Ping timeout: 268 seconds]