_inky | we don't have libosso-gnomevfs2-dev | 00:18 |
---|---|---|
_inky | right? | 00:18 |
_inky | but mappero needs it. :/ | 00:18 |
lel | MerlijnWajer assigned an issue: https://github.com/maemo-leste/bugtracker/issues/261 (gtk3 port) | 00:18 |
lel | MerlijnWajer assigned an issue: https://github.com/maemo-leste/bugtracker/issues/261 (gtk3 port) | 00:18 |
Wizzup | inky: you need to port from gnomevfs to gio, it's usually simple | 00:21 |
Wizzup | err _inky ^ | 00:21 |
Wizzup | libosso-gnomevfs2-dev is dead, basically, iiuc :) | 00:22 |
_inky | i don't even understand what you've said | 00:22 |
_inky | can i just use gnome-vfs packages? | 00:22 |
_inky | instead of libosso-gnomevfs | 00:22 |
_inky | oh there are nothing like that. | 00:23 |
_inky | i am not sure what in mappero needs it. | 00:23 |
Wizzup | _inky: gnomevfs does not exist anymore | 00:26 |
Wizzup | _inky: so you can no longer link against the library | 00:26 |
Wizzup | it's mostly used to read/parse the filesystem and such, to do i/o | 00:26 |
Wizzup | trhe replacement is "gio" | 00:26 |
Wizzup | there are various examples out there, I can take a look with you if you want | 00:27 |
_inky | minute | 00:27 |
_inky | https://github.com/norayr/mappero/ | 00:27 |
_inky | this is it, fremantle's latest mappero. | 00:27 |
_inky | if you can make it use gio instead of libosso-gnomevfs, would be very thankful. | 00:28 |
Wizzup | I'd rather you take a look and try :p | 00:28 |
Wizzup | let me see | 00:28 |
_inky | what is gio, is it in debian or maemo repos? | 00:28 |
Wizzup | are you able to write C? | 00:29 |
Wizzup | btw, mappero as you linked doesn't have a debian dir? | 00:29 |
_inky | well, i guess so. | 00:29 |
_inky | it has, minute | 00:30 |
_inky | check maemo/beowulf branch | 00:30 |
_inky | i have a working ready for jenkins port of lagrange - gemini browser. | 00:31 |
_inky | but that's another story. i did many changes but not in c source. | 00:31 |
Wizzup | _inky: hang on, brb | 00:38 |
_inky | yes | 00:39 |
Wizzup | _inky: it seems to just compile, but there is a linking problem | 00:49 |
Wizzup | working on it | 00:49 |
Wizzup | but pls study the commit so you can do it too :) | 00:49 |
Wizzup | ah ok now I hit the gnome-vfs stuff | 00:51 |
Wizzup | _inky: https://wizzup.org/0001-Update-debian-dependencies-remove-gvfs-includes.patch | 00:54 |
_inky | heh. | 00:54 |
_inky | aha let me see | 00:54 |
Wizzup | this should getr you to the point where you can build it and vfs complains | 00:54 |
Wizzup | it doesn't actually do the gvfs porting yet | 00:54 |
Wizzup | the first I see is this: | 00:55 |
Wizzup | maps.c: In function ‘download_tile’: | 00:55 |
Wizzup | maps.c:461:5: error: unknown type name ‘GnomeVFSResult’; did you mean ‘GTestResult’? GnomeVFSResult vfs_result; | 00:55 |
_inky | i was guessing so, that it needs the lib to store downloaded tiles. | 00:55 |
Wizzup | yes, but gio replaces gnome vfs, you just need to do the actual porting | 00:56 |
_inky | ok i guess it's very late at your side. i'll see what can i do. | 00:56 |
_inky | thank you. | 00:56 |
Wizzup | for example, gnome_vfs_read_entire_file might become https://docs.gtk.org/gio/method.InputStream.read_all.html in combination with something that opens a url as file handle | 00:58 |
Wizzup | yeah it's 1am so I can't/won't do it now | 00:58 |
Wizzup | lmk if you run into trouble, I like gps apps :) | 00:58 |
Wizzup | also just googling for "gio read remote url" or "glib read remote url" might help | 00:58 |
Wizzup | for example that gives this: https://stackoverflow.com/questions/10622642/fetch-a-file-from-web-using-glib-gio-from-c | 00:59 |
Wizzup | https://docs.gtk.org/gio/type_func.File.new_for_uri.html | 00:59 |
Wizzup | keep in mind that gnome/gtk broke *all* their doc links | 00:59 |
Wizzup | it's insane but true, so when you click a link and it doesn't work, search for the method name again in the title bar | 00:59 |
inky | okay! | 00:59 |
Wizzup | in any case dpkg-buildpackage -b -uc should mostly work now with the patch applied | 01:00 |
inky | oh indeed it's later here, about 3 am (: | 01:00 |
Wizzup | (git am blabla.patch) | 01:00 |
Wizzup | also just 'make' will work if you did dpkg-buildpackage -b -uc once | 01:01 |
Wizzup | I made one other change: | 01:01 |
Wizzup | #ifdef MAEMO_CHANGES /* probably not the best macro to check for here */ | 01:01 |
Wizzup | -# include <device_symbols.h> | 01:01 |
Wizzup | +//# include <device_symbols.h> #endif | 01:01 |
Wizzup | because I don't know where that file is, but it's not in the repo | 01:01 |
inky | yeah. i hope i'll tinker tomorrow. | 01:01 |
Wizzup | :) | 01:01 |
inky | oh | 01:01 |
inky | i see | 01:01 |
inky | i suffered with build system of lagranfe gemini browser a lot | 01:02 |
inky | it builds but sometimes crashes | 01:02 |
inky | also | 01:02 |
inky | it says on console that | 01:02 |
inky | libgl error: failed to load omapdrm | 01:03 |
inky | it works nice even without it | 01:03 |
Wizzup | are you building on the droid? | 01:05 |
Wizzup | ooh, sorry, got confused | 01:05 |
Wizzup | yeah, that libgl error is 'normal' | 01:05 |
Wizzup | I would recommend generally to try building in the VM if you can | 01:05 |
_inky | yep, building on the droid (: | 01:05 |
Wizzup | would recommend to do it on a VM if you can | 01:06 |
_inky | i did so before | 01:06 |
Wizzup | ok | 01:06 |
_inky | but it's not that convenient. | 01:06 |
Wizzup | it's just much faster/easier | 01:06 |
Wizzup | ok :P | 01:06 |
_inky | (: | 01:06 |
Wizzup | let me know wrt mappero, I might have more time later if you need help | 01:07 |
Wizzup | there doesn't seem to be too much, maybe 6 places/uses of vfs | 01:07 |
_inky | okay, i'll see, i hope will be able to solve this. | 01:14 |
Wizzup | it's probably ~1-2h if you know what you're doing | 01:14 |
Wizzup | there are also examples of this porting in other repos | 01:14 |
_inky | i never used gtk and its libs, but i'll see. | 01:14 |
Wizzup | https://github.com/maemo-leste/osso-pdf-viewer/commit/536da6652e44b9e5dc25a9eab004e252e17b452e | 01:15 |
Wizzup | that shows how to replace the string escaping (provided I did it right) | 01:15 |
Wizzup | there's more porting here https://github.com/maemo-leste/osso-pdf-viewer/commits/master | 01:15 |
_inky | thaaanks | 01:16 |
_inky | this seems very helpful. | 01:16 |
Wizzup | sure, lmk | 01:16 |
mighty17[m] | <MartijnBraam[m]> "the pmos n900 kernel is a bit..." <- We should package openpvrsgx kernel for pmos :D | 06:12 |
^-^hi | Ok, so bootlocks only let one type of kernel they have signed to boot | 07:21 |
^-^hi | And Android runs some sort of Linux | 07:21 |
^-^hi | And Linux's kernel could be upgraded on the fly as I heard. | 07:22 |
^-^hi | So... can one boot the Android kernel and then change it to mainline Linux after the boot, thereby salvaging the bootlocked phones? | 07:23 |
sicelo | Yes. That's what kexecboot does on the motorola droids, and lk2nd in the qcoms. | 07:36 |
uvos | Wizzup: no | 09:01 |
uvos | Wizzup: but i do test it on amd64 arch linux | 09:01 |
freemangordon | Wizzup: yes, please http://46.249.74.23/leste/n900/ | 09:18 |
freemangordon | openpvrsgx doesn;t boot either | 10:02 |
uvos | did you try vanilla? | 10:02 |
freemangordon | pulling linux stable ATM | 10:02 |
dreamer | heh. friend had noticed some TI userspace build activations on 3430 and 4430 trees recently. but was wondering why 3630 wasn't done hehe | 10:16 |
dreamer | the sgx handling, right? | 10:16 |
* mighty17[m] uploaded an image: (84KiB) < https://libera.ems.host/_matrix/media/r0/download/matrix.org/XeWipCSzJhLiLMOSvkCLfsAG/IMG_20211009_133052.jpg > | 10:24 | |
mighty17[m] | Is the green lines GPU issue? | 10:24 |
mighty17[m] | Or display | 10:24 |
Wizzup | freemangordon: trying now | 10:35 |
Wizzup | freemangordon: did you append the dtb, btw? | 10:37 |
freemangordon | yes | 10:37 |
freemangordon | wait, I have dmesg log | 10:37 |
freemangordon | looking at it ATM | 10:37 |
freemangordon | acx565akm spi0.2: failed to find video source | 10:38 |
freemangordon | https://pastebin.com/1kcKDB2T | 10:40 |
freemangordon | any idea? | 10:40 |
freemangordon | tmlind: ^^^ | 10:40 |
Wizzup | is this omap2plus_defconfig ? | 10:41 |
freemangordon | no | 10:41 |
freemangordon | lemme try with it | 10:41 |
uvos | why are we on rc2 again | 10:41 |
freemangordon | this is old dmesg | 10:41 |
freemangordon | with vanilla I have the same error | 10:41 |
freemangordon | uvos: https://pastebin.com/Tbbf9RgL | 10:42 |
freemangordon | the same with openpvrsgx tree | 10:42 |
sicelo | Nice! It's always the display :-( | 10:43 |
Wizzup | btw, I tried on serial and uh it doesn't boot for me on several tries which is weird, also no output on serial, let me try once more | 10:43 |
Wizzup | I thought extra_bootargs with console= set to serial would work but maybe that appends the arg | 10:44 |
freemangordon | Wizzup: don't waste time I have dmesg log | 10:45 |
Wizzup | ok | 10:45 |
uvos | just stabbin in the dark here but maybe omapdss dosent probe? boot with initcall_debug=1 nd ignore_loglevel=1 | 10:48 |
uvos | maybe | 10:48 |
uvos | or since it boots ssh in and take a look around in sys and proc | 10:49 |
freemangordon | I can;t ssh | 10:49 |
freemangordon | also, I see no dss logs, so maybe you are right | 10:49 |
freemangordon | but, lemme trey with omap2plus_defconfig first | 10:50 |
uvos | ok | 10:50 |
freemangordon | with omap2plus_defconfig it doesn't write anything in /var/log | 11:12 |
freemangordon | I guess it dies before mounting root | 11:13 |
Wizzup | is this plain 5.15 | 11:18 |
Wizzup | I can try to build it today | 11:18 |
freemangordon | wait, I think I know what happens | 11:18 |
freemangordon | but yeah, you may try vanilla with omap2plus_defconfig to see why it hangs | 11:19 |
Wizzup | latest rc? | 11:19 |
freemangordon | yes | 11:19 |
freemangordon | rc-4 | 11:19 |
freemangordon | iiuc | 11:19 |
Wizzup | sicelo: (and others) btw, if you know of a way to produce a few serials at not an insanely high cost I'd like to know | 11:19 |
Wizzup | freemangordon: ok, but it will be later today, maybe late afternoon or eve | 11:20 |
freemangordon | ok, no hurry | 11:20 |
uvos | some one has to design them | 11:20 |
uvos | i can make some | 11:20 |
Wizzup | uvos: sre designed them | 11:20 |
Wizzup | https://n900.elektranox.org/serial-adapter.html | 11:20 |
uvos | there are no files and he used a laser cutter wich i could do but its not a great idea | 11:20 |
Wizzup | but we'd need to order the parts and use a cnc | 11:20 |
Wizzup | I also have a laser cutter at the local hackerspace here | 11:20 |
Wizzup | aren't there files? | 11:20 |
uvos | i have various cnc machines | 11:21 |
Wizzup | neat | 11:21 |
sicelo | no there arent. but i'm sure he could share them if we ask | 11:21 |
Wizzup | i'm sure he'll share the files | 11:21 |
freemangordon | I think it would be better to re-desigh to use a simple flex cable (an a terminator) that lives under the battery | 11:22 |
uvos | i dont like the dsign | 11:22 |
uvos | really | 11:22 |
freemangordon | me neither | 11:22 |
uvos | tentioning the flex cable might be hard | 11:22 |
uvos | an easy way to do it | 11:22 |
uvos | would be to use a flex cable with the same pin pattern as the n900 | 11:23 |
uvos | and then using conductive adheasive | 11:23 |
freemangordon | adhesive? | 11:23 |
uvos | like is used on lcd display cables to bond to the glass | 11:23 |
uvos | yeah | 11:23 |
freemangordon | this is even worse | 11:23 |
freemangordon | I mean: | 11:23 |
freemangordon | you can;t reuse that device anymore | 11:23 |
uvos | why just have the cable wrap around the battery | 11:23 |
freemangordon | unless I missed the point | 11:24 |
uvos | on the other end of the flex you have a eadge connector | 11:24 |
freemangordon | uvos: wait, you need to have pogo-pins contacting the MOBO | 11:24 |
uvos | freemangordon: no here 1 sec | 11:24 |
uvos | so you have a flat flex | 11:26 |
uvos | and a regular pcb | 11:26 |
uvos | on the regular pcb you have the voltage level conversion and usb uart chip | 11:26 |
uvos | and a connector like this https://eu.mouser.com/ProductDetail/GCT/FFC2B22-45-T?qs=TuK3vfAjtkVWLNrSep2AyA%3D%3D | 11:26 |
uvos | the flat flex is just long enough to wrap arround the battery half way | 11:27 |
freemangordon | ok | 11:27 |
uvos | on one end it ends with the connector pins like this https://community.voltera.io/uploads/default/original/1X/c94b8fae9c2c7a44bb8ce84afcd97ec08d77c3fa.jpg | 11:27 |
uvos | on the other end you have the n900 pad pattern exposed | 11:27 |
uvos | you bond the n900 end to the mainboard permanently | 11:27 |
uvos | and wrap the flex around the battery | 11:27 |
uvos | so you can still close the door | 11:27 |
uvos | if you want serial you open the door an plug in the regular fr4 pcb | 11:28 |
freemangordon | uvos: everything is fine, besides the 'bond' part | 11:28 |
freemangordon | as soon as you disconnect, you have 4-5 cm wire attached directly to SoC hanging in the air | 11:28 |
uvos | ? to the pcb not the soc | 11:28 |
uvos | and its just a pice that goes around the battery a half turn | 11:29 |
freemangordon | it is PCB, but there are no bufers or sumething | 11:29 |
freemangordon | so basically it is to the SoC | 11:29 |
uvos | i dont think its a big problem emi wise | 11:29 |
uvos | you would only connect the uart pins ofc | 11:29 |
uvos | the rest you bond for stability | 11:29 |
freemangordon | I would say it is, because, as I said, there is no buffersing | 11:29 |
uvos | but dont give them any long tail | 11:29 |
uvos | dont worry fine electrically | 11:30 |
freemangordon | so you attach an antenna to the SoC | 11:30 |
uvos | yeah but just to the uart pins | 11:30 |
freemangordon | doesn;t really matter, as long as there are no buffers or filter caps | 11:31 |
freemangordon | afaik this pin is floating | 11:31 |
uvos | yes it dose its not a big deal you might get some noise on the pins but nothing else | 11:31 |
uvos | yes its floating | 11:31 |
freemangordon | what about finding a connector that fits pcb pins and use the battery to keep it attached to the PCB? | 11:31 |
freemangordon | and use bond to attach flex to the connector | 11:32 |
uvos | well then you need a grid of pogo pins | 11:32 |
freemangordon | ok | 11:32 |
uvos | to get defined force | 11:32 |
uvos | i doubt you can do that in the space availbe | 11:32 |
freemangordon | it is not that small | 11:32 |
uvos | its pretty small | 11:32 |
* freemangordon checks | 11:32 | |
uvos | pogo pins need travel | 11:32 |
freemangordon | I know | 11:33 |
uvos | and a backing of sufficant stiffness | 11:33 |
freemangordon | pcb is ok | 11:33 |
Wizzup | well the pogo pin design of nokia works well no? | 11:33 |
uvos | sure | 11:33 |
Wizzup | at least for me | 11:33 |
uvos | but that replaces the whole battery | 11:33 |
Wizzup | yup | 11:33 |
Wizzup | but sre's is kinda simple | 11:33 |
freemangordon | anyway, back to kernel | 11:33 |
Wizzup | :) | 11:33 |
uvos | machineing a battery shaped object is no issue | 11:33 |
uvos | the premis here was that fmg wants the adapter to work with stock battery | 11:34 |
uvos | anyhow if someone makes cad files for a battery shaped object and a pcb with pogo pins i can machine or 3d print it | 11:34 |
freemangordon | hmm, maybe I should compile on my laptop (8x i7) not on my desktop (4x i5 from 2010 or something) :) | 11:35 |
sicelo | :-) | 11:36 |
freemangordon | not to say that laptop is with nvme | 11:36 |
Wizzup | uvos: we'll also need to order parts to get the proper voltage | 11:36 |
Wizzup | https://www.sparkfun.com/short/8745 | 11:36 |
Wizzup | I have this at home, sre gave me one at fosdem | 11:36 |
uvos | i would just design a pcb that integrates the voltage shifter and | 11:36 |
uvos | uart | 11:36 |
Wizzup | aha | 11:36 |
freemangordon | Wizzup: this level shifter is simple mosfets and resistors | 11:37 |
Wizzup | freemangordon: yeah | 11:37 |
freemangordon | yes, as uvos said | 11:37 |
Wizzup | won't it be too much of a time sink? | 11:37 |
Wizzup | otherwise, sounds like a great idea imho | 11:37 |
Wizzup | idk how long it takes to do those things | 11:37 |
uvos | not very long | 11:37 |
uvos | but i dont have any interest in n900 really | 11:37 |
freemangordon | such a simple pcb, maybe a couple of hours | 11:37 |
Wizzup | ok, so we need cad files with the n900 battery size? | 11:38 |
uvos | you might not even need to do any voltage shiftig | 11:38 |
Wizzup | buZz: do you think you can help? | 11:38 |
uvos | there are bound to be some usb uart chips with 1.8v logic level | 11:38 |
sicelo | you do need voltage shifting. the n900 uart is 2.7v | 11:38 |
Wizzup | uvos: it might be neat to allow connecting random 3.3v uarts to the pcb as well | 11:39 |
uvos | sicelo: omap logic level is 1.8 | 11:39 |
uvos | not sure where 2.7 would come from | 11:39 |
sicelo | i know. but, N900 uart is 2.7v. sre's design uses 2.5v, which is reasonably close | 11:41 |
uvos | well its ttl i should have 0.8 as the high threshold so anything in that range will work | 11:42 |
uvos | as long as its below the maximum rating the pin | 11:43 |
uvos | let me check the datasheet | 11:43 |
sicelo | uvos: maybe this will make you understand, http://wiki.maemo.org/N900_Hardware_Hacking#Debug_ports | 11:45 |
uvos | so omap3 datasheet says that uart is max 2.1V input with ll high thresh of 1.17V low thesh of 0.63V and output of 1.8V | 11:46 |
uvos | if its doing something else there must be a chip between the uart and the debug port | 11:47 |
sicelo | of course, there is | 11:48 |
uvos | well fmg just said there isent | 11:48 |
freemangordon | well, we don;t know what is there | 11:49 |
uvos | well not omap directly | 11:49 |
uvos | so i see the issue of putting a 3cm lead on there even less now | 11:49 |
freemangordon | its ugly | 11:49 |
uvos | okaaay | 11:50 |
uvos | wel its not my problem | 11:50 |
freemangordon | yeah | 11:50 |
Wizzup | unrelated but I do care about the n900 if only to show that it's possible to make a modern linux smartphone os that mostly just works fine, of course, don't expect browsers to work well | 12:09 |
Wizzup | but I think it's nice to support it | 12:09 |
freemangordon | 5.14.10 boots | 13:16 |
freemangordon | so it is a regression in 5.15 it seems | 13:17 |
uvos | should not be to hard to bisct from there | 13:17 |
freemangordon | yeah | 13:17 |
uvos | we really need some kind of automatic testing | 13:18 |
uvos | that at least checks if the devices boot & load all requesit modules | 13:18 |
uvos | n900 not booting has been a theme.. | 13:18 |
freemangordon | going to check if 5.14.0 boots and then will bisect | 13:19 |
sicelo | nice. that's great progress :-) | 13:30 |
freemangordon | yep, it does | 13:31 |
sicelo | omap2plus? or your own config? | 13:31 |
freemangordon | omap2plus | 13:57 |
freemangordon | WTF? now 5.15-rc4 boots :( | 13:58 |
freemangordon | the difference is that I build it on my laptop | 13:58 |
sicelo | :-) | 13:59 |
sicelo | hehe, i also experienced that a lot - the same kernel would not boot first time, but boot second or third time. i wonder if something doesn't get reset properly somewhere, but my knowledge in this area is lacking. | 14:01 |
freemangordon | no, kernel build on leste does not boot | 14:01 |
freemangordon | I tried maybe 10 different kernels | 14:02 |
freemangordon | the ones build on ubuntu 18.04 boot | 14:02 |
sicelo | mmm. gcc version issues? | 14:03 |
freemangordon | 8.3 vs 8.4, should not make a difference | 14:03 |
freemangordon | well, tmlind's kernel does not boot still | 14:16 |
Wizzup | freemangordon: did you figure out what was up? | 14:30 |
freemangordon | no | 14:30 |
Wizzup | ok | 14:30 |
freemangordon | vanilla boots | 14:30 |
freemangordon | but not tmlind's | 14:30 |
freemangordon | now I am trying to find tag on his tree that boots to bisect | 14:30 |
Wizzup | ok | 14:35 |
Wizzup | and tmlinds is both pvr and other patches? | 14:35 |
freemangordon | droid4-pending-pvr-omapdrm-v5.15 | 14:36 |
freemangordon | whatever it is | 14:36 |
Wizzup | ok | 14:36 |
freemangordon | Wizzup: if you have time, please compile and try to get boot log | 14:37 |
freemangordon | bisecting this may turn to be impossible | 14:37 |
_uvos_ | did you merge in rc4? | 14:54 |
_uvos_ | please take rc4 and merge in the pending-pvr branch | 14:55 |
freemangordon | why shall I do that? | 14:55 |
freemangordon | vanilla rc2 boots fine | 14:55 |
_uvos_ | ok | 14:55 |
_uvos_ | i thought it was rc4 | 14:55 |
freemangordon | rc4 too | 15:00 |
Wizzup | freemangordon: ok, pls tell me what config and git repo+brachh | 16:12 |
freemangordon | omap2plus_defconfig | 16:53 |
freemangordon | https://github.com/tmlind/linux_openpvrsgx.git | 16:53 |
freemangordon | droid4-pending-pvr-omapdrm-v5.15 | 16:54 |
freemangordon | Wizzup: ^^^ | 16:54 |
Wizzup | ok | 17:32 |
Wizzup | will do in 1-2 hrs | 17:32 |
freemangordon | why the hell the whole kernel gets rebuild every time I do make? without changing anything? | 18:30 |
Wizzup | freemangordon: shouldn't | 18:32 |
freemangordon | hmm, yeah, false alarm it seems | 18:33 |
Wizzup | just got home | 18:33 |
freemangordon | good | 18:33 |
freemangordon | I have 3 steps to finish the bisect | 18:34 |
Wizzup | ok | 18:36 |
Wizzup | cloning now | 18:36 |
freemangordon | hmm, I guess it is some stupid setting on config, each bisect step leads to a full rebuild | 18:45 |
freemangordon | n ever happened before | 18:45 |
freemangordon | maybe .ko symbols or something | 18:45 |
freemangordon | CONFIG_MODVERSIONS that is | 18:47 |
Wizzup | freemangordon: how do you make the uImage ? | 18:52 |
freemangordon | cat arch/arm/boot/zImage arch/arm/boot/dts/omap3-n900.dtb > zImage | 18:53 |
freemangordon | mkimage -A arm -O linux -T kernel -C none -a 80008000 -e 80008000 -d zImage uImage | 18:53 |
Wizzup | freemangordon: it's booting for me | 19:05 |
freemangordon | cool | 19:05 |
freemangordon | well, no idea then | 19:06 |
Wizzup | well it doesn't seem to boot all the way to leste | 19:06 |
Wizzup | the screen stays on but black | 19:06 |
freemangordon | the same here | 19:06 |
freemangordon | actually it is stuck | 19:07 |
freemangordon | eventually it will power-down | 19:07 |
Wizzup | [ 15.690734] omapdss_dss 48050000.dss: supply vdda_video not found, using dummy regulator | 19:07 |
Wizzup | [ 15.722290] st-accel-i2c 3-001d: supply vddio not found, using dummy regulator | 19:07 |
freemangordon | shouldn't be an issue | 19:07 |
Wizzup | it's recurring | 19:07 |
freemangordon | ah | 19:08 |
mighty17[m] | The supply not found happens with me aswell, not an issue | 19:08 |
Wizzup | [ 20.243591] rx51-audio n900-audio: snd_soc_register_card failed (-517) | 19:08 |
freemangordon | do you have rootfs mounted? | 19:08 |
Wizzup | yeh | 19:08 |
freemangordon | here is does not mount | 19:08 |
Wizzup | [ 17.445861] lp5523x: probe of 2-0032 failed with error -22 | 19:08 |
freemangordon | at least judging by the missing dmesg log in /var/log | 19:08 |
freemangordon | hmm 223790cf892de9cee6a97fdf95c267ad36507951 is the first bad commit | 19:10 |
freemangordon | does not make sense | 19:10 |
Wizzup | https://wizzup.org/log.txt | 19:10 |
freemangordon | drm: pvrsgx: 1.17.4948957 remove never implemented MODULE_SUPPORTED_DEVICE like commit 6417f03132a69 | 19:10 |
freemangordon | ok, lemme try again | 19:11 |
Wizzup | just stops there for me | 19:12 |
Wizzup | it doesn't reset for me either | 19:12 |
freemangordon | could you remove dsme from /etc/init.d to see if it will boot to the shell? | 19:12 |
mighty17[m] | `mmc1: switch to bus width 8 failed` | 19:12 |
freemangordon | that's normal | 19:13 |
Wizzup | maybe some depmod is necessary | 19:13 |
Wizzup | unlikely but maybe | 19:14 |
freemangordon | the others boot without depmod | 19:15 |
freemangordon | Wizzup: does it boot to shell with dsme removed? | 19:18 |
freemangordon | or rather - are you able to see any output on the display? | 19:22 |
freemangordon | hmm, it boots on b98125a4f1287bc29df93c43abe49cc661030ff4 | 19:56 |
Wizzup | freemangordon: with display? | 20:15 |
freemangordon | yes | 20:16 |
freemangordon | I mean - I have no other means to distinguish between boot/does not boot but if it displays anything | 20:17 |
freemangordon | on 4a75f05f070785db5ffcbe21bd45b1482ef99e37 I have display too | 20:17 |
freemangordon | not trying the next one | 20:17 |
freemangordon | 614eb7536d3adad342b04fd1666bb3880e660dab that is | 20:18 |
freemangordon | *now trying | 20:18 |
freemangordon | Wizzup: so, what happens on youre device if you remove dsme? | 20:20 |
freemangordon | do you get console? | 20:20 |
Wizzup | can try momentarily | 20:32 |
Wizzup | I don't think so, I think it blocks on udev events to settle or something | 20:33 |
Wizzup | but will try | 20:33 |
freemangordon | ok | 20:33 |
Wizzup | freemangordon: so it's stuck here: | 20:49 |
Wizzup | [ 12.403442] udevd[480]: starting eudev-3.2.9 | 20:49 |
Wizzup | . ok | 20:49 |
Wizzup | [ ok ] Synthesizing the initial hotplug events (subsystems)...done. | 20:49 |
Wizzup | [....] Synthesizing the initial hotplug events (devices)... | 20:49 |
Wizzup | (with dsme renamed) | 20:51 |
Wizzup | so no | 20:51 |
freemangordon | same here | 20:52 |
freemangordon | so, actually it does not boot for you :) | 20:52 |
freemangordon | I mean "same" like :no console" | 20:52 |
freemangordon | anyway, I am doing a kind of a manual bisect | 20:52 |
Wizzup | right | 20:54 |
Wizzup | alpine doesn't have eudev probably? not sure what tmlind usually tests with | 20:54 |
freemangordon | no idea | 20:54 |
freemangordon | why the hell on every "git checkout" the whole kernel gets rebuild?!? | 20:55 |
Wizzup | probably a lot of files change mod time | 20:57 |
freemangordon | single file only | 20:58 |
freemangordon | just disabled module symbols versioning, lets see if it will help | 21:00 |
freemangordon | didn;t help | 21:05 |
freemangordon | wtf is going on? it is like I am compiling the kernel for a first time :( | 21:05 |
freemangordon | 33bc438d6d8883d77e37b369fe5144ee9b01fad8 breaks it | 21:17 |
freemangordon | hmm, I think I know why it breaks it, lemme try | 21:21 |
Wizzup | :) | 21:24 |
Wizzup | https://news.ycombinator.com/item?id=28809559 | 21:25 |
Wizzup | freemangordon: ^^ | 21:26 |
freemangordon | :) | 21:27 |
freemangordon | yeah | 21:27 |
freemangordon | hmm, no, it's something different, I need tmlind | 21:35 |
Wizzup | I guess init=/bin/sh does work? | 21:36 |
Wizzup | must, since it starts openrc | 21:37 |
freemangordon | I'll just revert that commit, to see if pvr works on n900 | 21:42 |
freemangordon | because that was the point of the whole exercise | 21:42 |
Wizzup | reverting 33bc438d6d8883d77e37b369fe5144ee9b01fad8 solves your hangs? | 21:43 |
freemangordon | yes | 21:43 |
Wizzup | let me try | 21:43 |
freemangordon | well, on 33bc438d6d8883d77e37b369fe5144ee9b01fad8 it hangs while on d8d18c28963fd9b9ed4425d79c4d5d5d3b496771 it does not | 21:44 |
freemangordon | now building with 33bc reverted to see | 21:44 |
Wizzup | yeah looks like that makes it boot for me too | 21:48 |
Wizzup | waiting to get agetty | 21:48 |
Wizzup | [....] Synthesizing the initial hotplug events (devices)... | 21:48 |
Wizzup | done. | 21:48 |
Wizzup | yeah now it gets past that | 21:48 |
Wizzup | so I can confirm reverting that commit makes it boot | 21:49 |
freemangordon | how you were able to compile so fast? | 21:50 |
Wizzup | model name: AMD Ryzen 7 PRO 4750U with Radeon Graphics | 21:50 |
freemangordon | doesn;t it recompile the whole kernel when you revert? | 21:50 |
Wizzup | 16 threads | 21:50 |
Wizzup | the revert didn't recompile the whole kernel, no | 21:50 |
freemangordon | it does here | 21:50 |
Wizzup | maybe it's a .config option that is enabled? | 21:50 |
freemangordon | something's wrong here it seems | 21:50 |
freemangordon | omap2plus_defconfig | 21:51 |
freemangordon | I'll clone tmlind's tree only | 21:51 |
freemangordon | and try again | 21:51 |
Wizzup | yeah that's what I did | 21:51 |
Wizzup | still, surprising that that would cause udev events to hang | 21:51 |
Wizzup | maybe it causes some operation that doesn't finish on n900 and then omapdrm never probes fully? | 21:52 |
freemangordon | could be | 21:52 |
Wizzup | looks like it | 21:55 |
Wizzup | on this kernel: | 21:55 |
Wizzup | [ 21.217407] omapdrm omapdrm.0: [drm] fb0: omapdrm frame buffer device | 21:55 |
Wizzup | [ 21.343597] [drm] Initialized omapdrm 1.0.0 20110917 for omapdrm.0 on minor 0 | 21:55 |
Wizzup | right above that: [ 20.081420] omapdrm omapdrm.0: DMM not available, disable DMM support | 21:55 |
Wizzup | and then without the commit reverted, it never gets past this: | 21:56 |
Wizzup | [ 19.809112] omapdrm omapdrm.0: DMM not available, disable DMM support | 21:56 |
freemangordon | mhm | 21:56 |
freemangordon | hmm, cannot start wpa_supplicant | 21:56 |
freemangordon | Wizzup: any hint how to start usb networking? | 21:58 |
Wizzup | yeah | 21:58 |
Wizzup | /usr/sbin/hildon-usb-gadget-network | 21:58 |
Wizzup | but if you have the same kernel as me then the usb gadget does not work | 21:58 |
freemangordon | maybe I should modprobe something? | 22:00 |
Wizzup | I see no wlan0 btw | 22:01 |
freemangordon | me too | 22:01 |
freemangordon | lemme check if it is enabled | 22:01 |
Wizzup | kind of expect it to be | 22:01 |
freemangordon | btw, did you send your patch upstream? | 22:02 |
Wizzup | not yet | 22:03 |
Wizzup | I think it just needs modprobe | 22:03 |
Wizzup | modprobe wl1251 | 22:03 |
Wizzup | modprobe wl1251_spi | 22:03 |
freemangordon | lemme check | 22:03 |
Wizzup | oh yeah without that patch icd2 fails heh | 22:03 |
Wizzup | Jan 1 02:16:03 (none) icd2 0.98[2702]: libicd-network-wpasupplicant: close_wpa_control: 0x51bba0 | 22:04 |
Wizzup | Jan 1 02:16:03 (none) icd2 0.98[2702]: libicd-network-wpasupplicant: try_open_wpa_control: 0x5422c0 | 22:04 |
Wizzup | Jan 1 02:16:03 (none) wpa_supplicant[2711]: wlan0: CTRL-EVENT-SCAN-FAILED ret=-22 | 22:04 |
Wizzup | not yet | 22:04 |
freemangordon | yse wext | 22:04 |
freemangordon | *use | 22:04 |
Wizzup | right, that will work, but not what we use on n900 these days | 22:05 |
freemangordon | yeah, but I need only shell anyways | 22:05 |
Wizzup | yeah | 22:05 |
Wizzup | I will let you mess with this now, lmk if you need help | 22:05 |
Wizzup | I'm quite motivated to see if we can move all our pvr stuff to 1.17 somehow.. | 22:05 |
freemangordon | I am in through wifi | 22:06 |
Wizzup | ok, then I will get back to droid3 kexecboot | 22:06 |
Wizzup | that's the last thing remaining for me to start writing the news post :D | 22:07 |
freemangordon | [ 808.276550] PVR_K: UM DDK-(4948957) and KM DDK-(4948957) match. [ OK ] | 22:07 |
Wizzup | that's the init? | 22:07 |
freemangordon | mhm | 22:08 |
freemangordon | and kmscube made it hang :( | 22:08 |
freemangordon | the same regression as with 5.10 | 22:09 |
Wizzup | shit | 22:09 |
freemangordon | yeah | 22:09 |
freemangordon | ok, tomorrow I will try to bisect | 22:11 |
Wizzup | rough | 22:12 |
Wizzup | I didn't send the wifi patch in part because I'd have to rebase on latest kernel | 22:12 |
Wizzup | and test it as well | 22:12 |
Wizzup | I might just try to use just modesetting | 22:13 |
freemangordon | hmm, why wl1251 is not probed? | 22:15 |
Wizzup | maybe that's a depmod thing | 22:15 |
freemangordon | ah, right | 22:15 |
Wizzup | will verify now | 22:15 |
Wizzup | (ran depmod -a, rebooting) | 22:15 |
Wizzup | X doesn't start in modesetting without powervr though for me, so need to figure out what's up there | 22:15 |
Wizzup | even unaccelerated X is still helpful in testing wifi patch and such | 22:16 |
freemangordon | mhm | 22:16 |
Wizzup | hm, didn't help (depmod -a) | 22:18 |
freemangordon | :( | 22:19 |
Wizzup | things really never work with computers :D | 22:20 |
freemangordon | yeah | 22:20 |
Wizzup | removing /dev/dri/card1 and /dev/dri/render129 makes X start at least | 22:21 |
freemangordon | bisecting will be a nightmare, there are several things broken in 5.10 IIRC | 22:24 |
freemangordon | like mmc renaming and panel reset | 22:24 |
freemangordon | what I am missing? | 22:24 |
Wizzup | when exactly did it break? | 22:25 |
Wizzup | not exact commit, but version | 22:25 |
freemangordon | I am not really sure | 22:25 |
Wizzup | did 5.9 work? | 22:25 |
freemangordon | ah, in 5.10 | 22:25 |
freemangordon | yes, 5.9 did work | 22:25 |
Wizzup | hm | 22:28 |
Wizzup | there must be a sensible way to debug it | 22:28 |
freemangordon | yeah, jtag :) | 22:29 |
Wizzup | did anyone ever manage to do that? ;) | 22:29 |
freemangordon | sure, in TI/Nokia ;) | 22:29 |
Wizzup | I wonder if the device I have here can do it | 22:29 |
Wizzup | parazyd: the latest vm images will lock the screen upon timeout, and then *all* input devices are disabled | 22:40 |
Wizzup | and then it's not possible to unlock unless you send the 'power' key to the vm | 22:40 |
Wizzup | I don't have this problem on my dev vm, so IDK what's different | 22:40 |
Wizzup | but it's likely something inside of the images, rather than leste-config related? | 22:40 |
Wizzup | parazyd: ah my vm has 'lock screen automatically' disabled | 23:35 |
Wizzup | but the fresh image does not | 23:35 |
Generated by irclog2html.py 2.17.0 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!