| mighty | hi, just build lib\ | 12:54 |
|---|---|---|
| mighty | libglvnd and mesa-amber, but they do not seem to be applied, ie my device still uses mainline mesa | 12:54 |
| mighty | i tried putting the flags __GLX_VENDOR_LIBRARY_NAME=amber and mesa_loader_driver_override=pvr but no dice | 12:55 |
| mighty | samsung-espresso7:~$ __GLX_VENDOR_LIBRARY_NAME=amber MESA_LOADER_DRIVER_OVERRIDE=pvr kmscube | 12:55 |
| mighty | did not find extension DRI_Mesa version 1 | 12:55 |
| mighty | failed to bind extensions | 12:55 |
| mighty | failed to initialize | 12:55 |
| mighty | failed to initialize EGL | 12:55 |
| mighty | i just rebased maemo's mesa on amber, do i also need to change mainline mesa to amber with its binaries? | 13:00 |
| uvos | im not quite sure how to select the right gl implementation with vnd __GLX_VENDOR_LIBRARY_NAME is likely wrong | 13:10 |
| uvos | since your interested in egl | 13:10 |
| uvos | try setting __EGL_VENDOR_LIBRARY_FILENAMES or just uninstalling regular mesa | 13:10 |
| uvos | alos check egl_vendor.d and see if both implementations are present | 13:10 |
| mighty | uvos: you mean __EGL_VENDOR_LIBRARY_FILENAMES=amber kmscube, same results | 13:13 |
| uvos | it seams really unlikely that the LIBRARY_FILENAME is simply "amber" | 13:14 |
| uvos | check egl_vendor.d | 13:14 |
| mighty | uvos: cant seem to find it, is it some nvidia specifc thing? | 13:16 |
| uvos | no its part of glnvd | 13:20 |
| uvos | glnvd is ofc required | 13:20 |
| mighty | it isnt packaged by me it seems, my libglvnd has https://paste.debian.net/1281683/ | 13:21 |
| uvos | the config file itself should be created by mesa, glnvd uses it to decide what to choose | 13:22 |
| uvos | should be in usr/share or maybe etc or both | 13:22 |
| mighty | i cant seem to find it anywhere | 13:22 |
| mighty | sudo find -name *egl_vendor* is blank :P | 13:22 |
| uvos | on leste its /usr/share/glvnd/egl_vendor.d | 13:23 |
| uvos | i cant tell you anythin on how alpine chooses to package things | 13:23 |
| mighty | its most likely not packaged at all since even arch doesnt have it https://archlinux.org/packages/extra/x86_64/libglvnd/ | 13:24 |
| uvos | the config file (and this the dir) is create by glvnd gl _implementations_ | 13:24 |
| uvos | not the the lib itslef | 13:24 |
| uvos | on leste its part of the mesa package | 13:24 |
| uvos | pacman -Qo /usr/share/glvnd/egl_vendor.d/50_mesa.json | 13:26 |
| uvos | /usr/share/glvnd/egl_vendor.d/50_mesa.json is owned by mesa 23.1.0-1 | 13:26 |
| uvos | arch absolutly ofc has it too | 13:26 |
| uvos | it _must_ | 13:26 |
| uvos | unless you dont use glvnd at all you need this | 13:26 |
| mighty | alpine probably doesnt use glvnd at all | 13:26 |
| uvos | if glvnd is not in use you must have your amber based mesa replace stock mesa | 13:27 |
| uvos | instead of installing beside it | 13:27 |
| mighty | it does replace mesa-gles mesa-egl and mesa-gl (https://pkgs.alpinelinux.org/packages?name=*mesa*&branch=v3.18&repo=&arch=armv7&maintainer=) | 13:28 |
| boobay | hey guys! my droid 4 won't boot for some reason after getting wifi to work. any suggestions? | 14:35 |
| dsc_ | boobay: try holding the power button for 10 sec | 14:37 |
| dsc_ | if I remember correctly.. | 14:37 |
| boobay | thx, but it doesn't help | 14:37 |
| dsc_ | it could also be powerbutton + volume down button | 14:38 |
| dsc_ | but maybe I am misremembering things... | 14:38 |
| dsc_ | probably. | 14:38 |
| boobay | it's 1 sec vol down + pwr for fastboot and 10 secs pwr for power off. but it doesn't work((( | 14:39 |
| boobay | might go around my block in search of a screwdriver that fits | 14:39 |
| dsc_ | so you got wifi to work and then the device just went black? | 14:39 |
| boobay | i don't really know.. i left it in perfectly working condition on the table, returned the next day, rebooted it a few times and now it's stuck | 14:41 |
| boobay | correlation with wifi fix is really loose | 14:41 |
| dsc_ | ok :) | 14:42 |
| uvos__ | what do you mean "wont boot" | 14:42 |
| uvos__ | please describe further | 14:42 |
| boobay | it shows green light when i plug the cable. besides that it doesn't respond to anything | 14:43 |
| uvos__ | its simply empty | 14:44 |
| uvos__ | this means its below the trickle charge voltage | 14:44 |
| uvos__ | it wont boot in this state | 14:44 |
| uvos__ | you need to let it trickle charge for a long time | 14:44 |
| uvos__ | or charge the battery externally | 14:44 |
| boobay | oof... 24h should be enough? | 14:45 |
| uvos__ | couple of h should be enough | 14:45 |
| uvos__ | you might end up in a motorla logo boot cycle | 14:45 |
| dsc_ | can you get into kexecboot menu? | 14:45 |
| dsc_ | guess not :P | 14:46 |
| uvos__ | that means your battery is simply to weak to work without you will need to charging externally and realistcly replace the battery as this means its really degraded | 14:46 |
| boobay | thx. should i control the battery level in cron so it doesn't happen again? | 14:46 |
| uvos__ | we control the batttery level just fine | 14:46 |
| uvos__ | it must have hanged in some state or your battery is really degraded | 14:46 |
| uvos__ | this assumes force reset dosent do anything | 14:47 |
| uvos__ | (power + vol-down for 10 sec while not on charger) | 14:47 |
| boobay | yep, this is exactly the case. i suspect the battery, this phone has seen a lot | 14:49 |
| uvos__ | also make sure the screw terminals are on tight | 14:49 |
| uvos__ | i have had those back out | 14:50 |
| boobay | they're fine. just wondering what motivates you to help me this extensively? :) | 14:52 |
Generated by irclog2html.py 2.17.0 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!