| ajr | Looks like my lucky day.. snagged a brand new d4 from ebay | 02:25 |
|---|---|---|
| mighty17[m] | <parazyd "Thanks for considering :)"> Form unavailable:( | 06:15 |
| ajr | Worked for me a couple hours ago, must have closed | 06:16 |
| ajr | looks like a cool project | 06:16 |
| tmlind | uvos: ok so bad emmc, but still some hope for usable xoom2 allow-mbmloader-flashing-mbm.bin then, i need to at least make a backup of my rootfs before i will try it though | 07:03 |
| tmlind | also what needs to be tested is if booting to recovery and resetting the system also resets the utags partition, i doubt it though, but would allow a way to recover | 07:04 |
| parazyd | ajr, mighty17[m]: thanks. Yeah, I guess it's done. | 08:32 |
| uvos | parazyd: missed it :( | 10:32 |
| parazyd | No worries :D | 10:32 |
| parazyd | btw. I'll try to compile also 5.10 kernel with the updates and patches today. | 10:33 |
| parazyd | -devel with 5.11 seems fine. | 10:33 |
| Wizzup | ajr: great @ snag :) | 10:34 |
| Wizzup | parazyd: do we have a way to test that 5.10 before it goes out to everyone? | 10:35 |
| parazyd | Not unless we use the same kernel both in devel and stable | 10:36 |
| parazyd | Which we should imo | 10:36 |
| Wizzup | how do we test new kernel versions then? | 10:36 |
| Wizzup | I'm trying to guard against a one time bad build or something that breaks all user devices after upgrade | 10:37 |
| parazyd | We test new versions in devel. | 10:37 |
| parazyd | My point is we would propagate 5.11 to stable (but we cant because of bugs) | 10:37 |
| parazyd | Ideally we go to ddk 1.19 and solve everything | 10:38 |
| Wizzup | mhm | 10:38 |
| parazyd | err 1.17 but you get the point | 10:39 |
| uvos | we could revert to 5.1o in devel | 10:39 |
| uvos | we could revert to 5.10 in devel | 10:39 |
| uvos | and put 5.11 into expieramental | 10:39 |
| uvos | or drop it | 10:39 |
| parazyd | Also a possibility, yes | 10:39 |
| mighty17[m] | uvos: kernel panics, no working init found | 10:56 |
| mighty17[m] | i passed init=/init in cmdline `mkbootimg --kernel Image-dtb --cmdline "console=tty0 ignore_loglevel debug earlycon ro rootwait rootfstype=ext4 root=/dev/mmcblk0p1 init=/init" --output ~/maemo/boot.img` | 10:56 |
| uvos | why? | 10:56 |
| uvos | there is no /init | 10:57 |
| mighty17[m] | so how do i fix that | 10:57 |
| parazyd | init=/sbin/init, or just leave itout | 10:58 |
| mighty17[m] | leaving it out causes kernel panic | 10:58 |
| parazyd | Saying what? | 10:58 |
| mighty17[m] | can i send in a pic here? | 10:58 |
| parazyd | Sure | 10:58 |
| mighty17[m] | ok gimme a sec | 10:58 |
| uvos | i also doubt that /dev/mmcblk0p1 is rootfs | 10:59 |
| uvos | since you flashed the d4 image | 10:59 |
| * parazyd too | 10:59 | |
| uvos | it should be the second partition | 10:59 |
| parazyd | Guessing that's the panic | 10:59 |
| * mighty17[m] uploaded an image: (127KiB) < https://libera.ems.host/_matrix/media/r0/download/matrix.org/iVEruvPFsrocUYsbbmfqdKJw/IMG_2021-06-13-14-29-46-831.jpg > | 11:00 | |
| parazyd | Yeah wrong partition for root= | 11:00 |
| parazyd | Most probably | 11:00 |
| mighty17[m] | oh as i flashed d4 rootfs | 11:01 |
| uvos | you flashed d4 imaga | 11:01 |
| uvos | not rootfs | 11:01 |
| uvos | the image contains a boot and a root partition | 11:01 |
| parazyd | Then you probably want root=/dev/mmcblk0p2 | 11:01 |
| uvos | d4 just boots zimage form a ext2 partition | 11:01 |
| uvos | also drop ro | 11:02 |
| mighty17[m] | still the same error | 11:02 |
| uvos | ok | 11:03 |
| uvos | dose --cmdline " in mkbootimg even work for you | 11:03 |
| uvos | i know that it dosent on mapphones | 11:03 |
| uvos | ie is the cmdline set | 11:03 |
| mighty17[m] | hm i'll rebuild the kernel then | 11:03 |
| uvos | also is mmcblk0 even the sdcard | 11:03 |
| mighty17[m] | yes i think, simplefb goes too fast to read | 11:04 |
| * mighty17[m] uploaded an image: (156KiB) < https://libera.ems.host/_matrix/media/r0/download/matrix.org/PaIhEkediDtZOrGrMBaOWspz/IMG_2021-06-13-14-40-23-864.jpg > | 11:10 | |
| mighty17[m] | uvos should I just rm the fstab | 11:10 |
| uvos | no | 11:11 |
| uvos | it never even mouts rootfs | 11:11 |
| uvos | so fstab has nothing to do with it | 11:12 |
| uvos | why is it trying to mount that | 11:12 |
| uvos | thats wierd | 11:12 |
| uvos | soemthing is wrong in your kernel side... | 11:12 |
| mighty17[m] | :( | 11:13 |
| mighty17[m] | Wait d4 has 5.10 kernel in /boot | 11:13 |
| mighty17[m] | But I flash my boot.img so that shouldn't matter | 11:13 |
| uvos | right the kernel in /boot is irrelivant | 11:13 |
| uvos | either mmcblk0 is not the sdcard | 11:14 |
| uvos | or your kernel has a broken block layer | 11:14 |
| mighty17[m] | Well there's no way to chech | 11:15 |
| mighty17[m] | Check* | 11:15 |
| uvos | mmcblk1p2 and mmcblk2p2 | 11:17 |
| uvos | or build a initramfs with busybox and take a look around | 11:18 |
| uvos | hmm no you cant do that you have no keyboard and no external serial port | 11:18 |
| mighty17[m] | Mmcblk1p2 worked but it's stuck | 11:18 |
| uvos | stuck where? | 11:18 |
| * mighty17[m] uploaded an image: (148KiB) < https://libera.ems.host/_matrix/media/r0/download/matrix.org/jOoyOyWuxzbHhNffNgRabQRq/IMG_2021-06-13-14-48-18-694.jpg > | 11:19 | |
| mighty17[m] | Sorry if I'm spamming with these images :( | 11:19 |
| uvos | if it just freezes there it proubly becuase omapdrm/ pannel driver is missconfigured | 11:20 |
| uvos | likely its continueing to boot but never refreshing the display again | 11:20 |
| mighty17[m] | I'll wait then | 11:20 |
| uvos | i wont ever do anything else that you can see | 11:21 |
| uvos | if this is the case | 11:21 |
| uvos | *it | 11:21 |
| uvos | you really need serial somehow really.... | 11:22 |
| mighty17[m] | No the cursor is blinking | 11:22 |
| uvos | oh ok | 11:22 |
| uvos | something else then | 11:22 |
| mighty17[m] | I got crng init done after 100s | 11:22 |
| uvos | oh right | 11:23 |
| uvos | yeah if you have no entropy sources it might wait forever really | 11:23 |
| mighty17[m] | But now 300s have passed and nothing | 11:23 |
| uvos | right | 11:23 |
| uvos | it cant setup /dev/random because of no entropy sources | 11:23 |
| uvos | no its proubly not it accutally | 11:24 |
| mighty17[m] | Huh never faced it | 11:24 |
| uvos | if its done | 11:24 |
| uvos | rm fstab | 11:24 |
| uvos | it might be waiting for /dev/mmcblk0p1 | 11:25 |
| uvos | also your sdcard is /dev/mmcblk2p2 | 11:27 |
| uvos | it saies in the image | 11:27 |
| mighty17[m] | It looks like MMC values change with every boot | 11:27 |
| uvos | so your booting something else there | 11:27 |
| uvos | yeah well you need to fix that then | 11:28 |
| mighty17[m] | Isn't this already an issue in linux-omap | 11:28 |
| mighty17[m] | Also now it's unable to mount rootfs, looks like same issue of mmc | 11:28 |
| uvos | not randomly | 11:29 |
| uvos | also was fixed iirc | 11:29 |
| uvos | tmlind: ^^^ knows details | 11:29 |
| mighty17[m] | In pmos boot 1 - emmc =mmc0 sdcard =mmc1 boot 2 - emmc =mmc1 sdcard =mmc2, they take random vlaues | 11:30 |
| mighty17[m] | uvos pvr fails for me now | 11:35 |
| * mighty17[m] uploaded an image: (125KiB) < https://libera.ems.host/_matrix/media/r0/download/matrix.org/GClvlIaLnsfKzoRdmNMcbztA/IMG_2021-06-13-15-05-18-062.jpg > | 11:35 | |
| mighty17[m] | Probably coz the kernel u told to use doesn't have pvr :P | 11:36 |
| uvos | right we merge in pvr just before compileing | 11:38 |
| uvos | the patches are supposed to be on top of the non pvr kenrel | 11:38 |
| uvos | you should run the the non pvr kernel with pvr merged on top | 11:38 |
| mighty17[m] | Okay... It seems like it boots! I saw cursor for split second but no ui/display yet ig | 11:40 |
| uvos | ok you should merge in pvr and fix the mmcblk problem | 11:41 |
| uvos | and then it should work now | 11:41 |
| mighty17[m] | Yay! | 11:41 |
| uvos | dont worry about x not working without pvr | 11:42 |
| uvos | its missconfigured for you atm | 11:42 |
| mighty17[m] | Also I have an older dts with working usb (it's some twl6030 and twl6032 issue) I'll give that a go | 11:48 |
| parazyd | uvos: Does the "generate entropy at boot" kernel config option help with this? I remember seeing it. | 12:06 |
| mighty17[m] | Still no ui with pvr kernel :( | 13:29 |
| mighty17[m] | It's just blank screen | 13:29 |
| Wizzup | mighty17[m]: does x start? do you have ssh/serial? | 13:33 |
| * mighty17[m] uploaded an image: (135KiB) < https://libera.ems.host/_matrix/media/r0/download/matrix.org/IAOarmRRdtFwouFAvgeoQdVO/Screenshot_20210613-170717_Gallery.png > | 13:37 | |
| mighty17[m] | Wizzup I am trying to get in ssh, will req some changes | 13:38 |
| mighty17[m] | Changes in kernel* | 13:38 |
| Wizzup | mighty17[m]: aha, ok | 13:41 |
| mighty17[m] | Any clues the image I sent gives! | 13:41 |
| mighty17[m] | Pvr doesn't load | 13:41 |
| mighty17[m] | Pretty sure some module isue | 13:42 |
| Wizzup | depmod -a perhaps | 13:42 |
| Wizzup | is our powervr service starting? | 13:43 |
| Wizzup | the one that sets up stuff? | 13:43 |
| mighty17[m] | Nope doesn't looke like it's starting | 13:43 |
| Wizzup | can you run depmod -a on the device? | 13:49 |
| Wizzup | I'm surprised also that it says it cannot find some modules | 13:49 |
| Wizzup | did you copy the modules over? | 13:49 |
| mighty17[m] | Wizzup: yes i copied modules over | 14:02 |
| mighty17[m] | Wizzup: https://pastebin.ubuntu.com/p/vXx42V95h6/ whats the ssh ip? | 14:03 |
| mighty17[m] | seems like ssh isnt working | 14:08 |
| mighty17[m] | https://pastebin.ubuntu.com/p/RhbMQCyjVs/ | 14:10 |
| Wizzup | mighty17[m]: ssh ip for usbnet, you mean? | 14:10 |
| Wizzup | https://leste.maemo.org/Status/USB_Peripheral | 14:10 |
| mighty17[m] | yup Wizzup | 14:10 |
| Wizzup | mighty17[m]: ^^ | 14:10 |
| mighty17[m] | https://pastebin.ubuntu.com/p/RhbMQCyjVs/ Wizzup thats what i did | 14:11 |
| Wizzup | $ sudo ip address add 192.168.42.1/24 dev enx2612631b80da | 14:11 |
| Wizzup | RTNETLINK answers: File exists | 14:11 |
| Wizzup | that does not sound like it worked | 14:11 |
| Wizzup | I don't know the magic of these commands, so it's harder for me to help debug | 14:11 |
| mighty17[m] | mighty@insipron:~/Tab2Dev/Maemo-Leste/pvr-kernel$ sudo ip address add 192.168.42.1/24 dev enx2612631b80da | 14:11 |
| mighty17[m] | [sudo] password for mighty: | 14:11 |
| Wizzup | can you ping it? | 14:11 |
| mighty17[m] | wait, i have a vid of the simplefb stuff, maybe that will help | 14:16 |
| Wizzup | mighty17[m]: if usbnet works, maybe host mod works too? so can you plug in a keyboard? | 14:16 |
| mighty17[m] | i dont hv a keyboard | 14:16 |
| mighty17[m] | Wizzup: | 14:18 |
| mighty17[m] | https://pastebin.ubuntu.com/p/QkDsKcRxYT/ | 14:18 |
| mighty17[m] | pinging 192.168.42.1 seems to work | 14:19 |
| Wizzup | that is yourself | 14:20 |
| Wizzup | so maybe the usbnet doesn't go up | 14:20 |
| Wizzup | hard to tell why that would be the case, how did you get the rootfs set up? | 14:20 |
| Wizzup | (really, serial or keyboard would be much easier to debug) | 14:20 |
| mighty17[m] | <Wizzup "hard to tell why that would be t"> rootfs is droid4 | 14:20 |
| mighty17[m] | but this device isnt droid4*** | 14:20 |
| Wizzup | so you dd'd a droid4 to a sd card and starting modifying it, right? | 14:21 |
| Wizzup | a droid4 image | 14:21 |
| mighty17[m] | yes | 14:21 |
| Wizzup | ok | 14:21 |
| Wizzup | I am not sure if the usbnet service starts when X does not start | 14:22 |
| mighty17[m] | ohk, well where can i upload a vid of simplefb logs | 14:23 |
| tmlind | mighty17[m]: if you have your mmc devices moving around, apply commit 77335a040178 ("ARM: dts: Fix moving mmc devices with aliases for omap4 & 5") | 19:57 |
| mighty17[m] | Thanks, so it will start from &mmc1 now? | 20:04 |
| tmlind | mighty17[m]: it keeps micro-sd at mmc0 and emmc typically at mmc1 | 20:11 |
| mighty17[m] | and sdio would be mmc(x-1) right | 20:12 |
| tmlind | mighty17[m]: depends where it's wired, but keeps the order specified in the aliases | 20:14 |
| mighty17[m] | yeah basically mmc1(sdcard) -> mmc0 , mmc2 -> mmc1 and so on | 20:16 |
| tmlind | yeah | 20:21 |
| uvos | mighty17[m]: forget about the random thing, i missinterpreted something | 20:30 |
| mighty17[m] | yes i know the cause was random mmc names | 20:30 |
| uvos | mighty17[m]: like Wizzup saies the modules thing is strange, the image loades those modules via modules-load.d | 20:31 |
| uvos | you dont need them but if you built omap2plus_defconfig and installed it properly they should exist | 20:31 |
| uvos | (but then not probe) | 20:31 |
| mighty17[m] | <uvos "you dont need them but if you bu"> i installed then in the rootfs/sdcard | 20:32 |
| mighty17[m] | oops reply sorry | 20:32 |
| uvos | so maybe you are building the wrong defconfig or you failed to install the kernel modules to /lib/modules/$(uname) | 20:32 |
| uvos | but then again i would expect the system to not boot at all wthout modules | 20:32 |
| uvos | unless you specified some additional stuff to be built in | 20:33 |
| mighty17[m] | no the modules do get loaded | 20:33 |
| uvos | ok | 20:34 |
| uvos | so is the pvr module loaded? | 20:34 |
| mighty17[m] | they did show that in simplefb, but even if pvr fails, no ui? not even sw rendering | 20:34 |
| mighty17[m] | uvos: is the /var/log/dmesg of any help | 20:34 |
| uvos | if pvr fails no ui | 20:34 |
| uvos | becuase the ui will try to use libgles and segfault | 20:34 |
| uvos | mighty17[m]: best would be some whay to have an interactive shell on device | 20:35 |
| uvos | mighty17[m]: since you have no serial (im very thankfull motorola made this very easy for us :P) you should setup wpa_supplicant to auto connect | 20:36 |
| mighty17[m] | yes there were comr CRITICAL ERRORS or smth | 20:36 |
| mighty17[m] | s/comr/some | 20:36 |
| uvos | and mv /etc/init.d/dsme /etc/init.d/dsme_ | 20:36 |
| uvos | then you should be able to boot to shell | 20:36 |
| mighty17[m] | yeah wifi ssh is the only option ig, how would i do that | 20:37 |
| uvos | and have ssh | 20:37 |
| uvos | just setup wpa_supplicant | 20:37 |
| uvos | google around its not so hard | 20:37 |
| uvos | ssh is enabled by default on leste | 20:37 |
| mighty17[m] | ohk great thank | 20:37 |
| mighty17[m] | yeah i read that | 20:37 |
| mighty17[m] | heres /var/log/dmesg https://pastebin.ubuntu.com/p/YZZjMpSDCt/ | 20:38 |
| lel | IMbackK opened a pull request: https://github.com/maemo-leste/leste-config/pull/23 (Mapphones: switch away from mono mode on exiting internal speaker hifi output) | 21:26 |
| inky | i don't understand, i think i was able to change the d4 from pc by using usb condom. i forgot the wire and the condom somewhere, and was unable to change d4 for a week. now i got it, d4 is exhausted, and it doesn't take charge, i am trying second day. | 21:32 |
| inky | it wasn't taking charge with usb condom immediately, i had to enter safestram android distro, then it would draw this empty battery with the question mark. | 21:33 |
| inky | and then that battery would start to charge. that was the way. | 21:33 |
| uvos | if the battery is to low android will (rightfully) refuse to charge it | 21:34 |
| inky | to be precise, that battery would show the slow charge process. and it was usually second time i entered the safstrap android. not the first time. | 21:34 |
| uvos | unfortionatly the mainline kernel can cause the battery to underdischarge | 21:34 |
| inky | omg. | 21:34 |
| inky | so i need to get it out and charge separately? | 21:34 |
| uvos | if android wont charge it and cpcap dosent charge it without booting yes | 21:35 |
| inky | cpcap is what? | 21:35 |
| uvos | in a very narrow band around 3v cpcap will charge the battery slowly while the device is off (led will light). with a condom this should also happen. | 21:36 |
| uvos | a condom should not boot the device | 21:36 |
| uvos | since the id pin should not be disconnected... | 21:36 |
| inky | hmmm, condom boots it. well turns it on, and i see the boot menu. | 21:36 |
| uvos | hmm | 21:36 |
| uvos | with just vbus and gnd connected? | 21:37 |
| inky | well i don't know may be my usb condom is wrong, but this device claims to be that. | 21:37 |
| inky | (: | 21:37 |
| uvos | inky: ok so micro usb has 5 pins | 21:37 |
| uvos | vbus d+ d- and id | 21:38 |
| uvos | a condom could have id connected and still be a condom | 21:38 |
| uvos | but this would boot the device (which is undesirable here) | 21:38 |
| inky | ok i see. the condom i have is not condomy enough. | 21:38 |
| uvos | anyhow if you cant charge via android and have no full condom (with id disconnected) you must charge the battery externaly | 21:38 |
| uvos | sorry | 21:39 |
| inky | okay (: | 21:39 |
| inky | i don't understand, what is 'battery calibration'? | 21:39 |
| uvos | Wizzup: please please review the mce patches that prevent users ending up in this situation.... | 21:39 |
| uvos | inky: hmm? | 21:39 |
| inky | is it something about internals of the battery or is it something inside the os that knows the battery better. | 21:39 |
| uvos | bettery callibration where? | 21:39 |
| uvos | just that the os knows the battery | 21:39 |
| inky | well, since i changed the battery it is 'uncalibrated'. | 21:40 |
| uvos | inky: yeah sure thats fine | 21:40 |
| uvos | its allways uncalibrated in leste untill the device sees full or empty on that boot btw | 21:40 |
| uvos | this dosent affect anything but the accuracy of the battery display | 21:40 |
| inky | i mean that means leste 'remembers' something about the battery. | 21:41 |
| inky | what is calibration, so can battery be calibrated in leste but uncalibrated in android? | 21:41 |
| inky | just interesting. | 21:41 |
| uvos | inky: yeah sure | 21:41 |
| uvos | but andorid hides the callibrated state anyhow | 21:41 |
| inky | okay. | 21:41 |
| uvos | i dont think it ever tells you if it knows | 21:41 |
| inky | now i think i understand it better. | 21:42 |
| inky | uvos, i found a charger that doesn't boot it, and green led lights up. (: | 22:02 |
| Wizzup | uvos: ok. tomorrow I can do all of that, will you be around to coordinate? | 22:14 |
| uvos | Wizzup: do you have some time after 17 CEST till around 21? | 22:15 |
| Wizzup | yeah, I think that should be fine, I might have a mtg around 1830 but otherwise I have time | 22:16 |
| uvos | ok | 22:16 |
| Wizzup | uvos: sorry it's taking a while, I just got the place where I will spend several months so I'm more stable now | 22:18 |
| Wizzup | (and I have the tablets here, and soon lab psu, and pinephone, and d4, and bionic, and d3 ... :-D) | 22:18 |
| uvos | Wizzup: no stress | 22:18 |
| uvos | nice :) | 22:18 |
| * uvos is doing 700 ish package upgrade on n900 | 22:20 | |
| Wizzup | ehe | 22:21 |
| Wizzup | yeah, I need to fix the locale gen and language applet to make it work | 22:21 |
| uvos | that will finish like thusday | 22:21 |
| Wizzup | there's some weird bug | 22:21 |
| uvos | ok | 22:21 |
| Wizzup | for me all the entries get set to "Nederlands" (Dutch) and one to English | 22:22 |
| uvos | btw due to me being an idiot all d4s where playing music in downmixed mono | 22:23 |
| uvos | upps | 22:23 |
| uvos | (on headphones) | 22:23 |
| Wizzup | I saw that yeah, does it affect earpiece in any way? | 22:23 |
| uvos | no | 22:23 |
| Wizzup | ok | 22:26 |
| uvos | oh yes the change dosent affect earpice | 22:27 |
| uvos | but the earpice profile has the same bug | 22:28 |
| uvos | Wizzup: (which is what you ment i assume) | 22:28 |
| Wizzup | well, earpiece is mono though | 22:29 |
| uvos | right | 22:29 |
| uvos | but the earpice profile dosent switch out of mono | 22:29 |
| Wizzup | ah | 22:29 |
| uvos | so if you go internal speaker -> earpice -> headphones | 22:29 |
| uvos | headphones ends up in mono again | 22:30 |
| uvos | sec ill fix it | 22:30 |
| lel | IMbackK synchronize a pull request: https://github.com/maemo-leste/leste-config/pull/23 (Mapphones: switch away from mono mode on exiting internal speaker hifi output) | 22:30 |
| uvos | fixed | 22:30 |
| Wizzup | cool | 22:32 |
| freemangordon | Wizzup: uvos: did you try latest wlan fixes? Are connection problems still exist? | 22:44 |
| freemangordon | *Do | 22:44 |
| Wizzup | freemangordon: I started to, but didn't finish, I should try the python-conic example | 22:46 |
| Wizzup | that was a 100% fail | 22:46 |
| Wizzup | I am fixing another bug atm | 22:47 |
| uvos | freemangordon: sorry not yet | 22:47 |
| uvos | ill do it rn | 22:47 |
| Wizzup | osso-applet-languageregional only works when launched with controlpanel.launch, not with controlpanel | 22:47 |
| Wizzup | maemo-launcher restart fixes it, meh | 22:50 |
| * uvos grubles something about the usefullness of maemo-launcher | 22:50 | |
| uvos | :P | 22:50 |
| uvos | freemangordon: so it still seams buggy | 22:51 |
| freemangordon | which one? | 22:51 |
| uvos | so i started d4 and waited untill icd starts | 22:51 |
| uvos | then i upend the dialog and pressed on my ap | 22:51 |
| Wizzup | uvos: that is wifi | 22:52 |
| uvos | this immidatly failed with the retry thing | 22:52 |
| Wizzup | sometimes assocation fails | 22:52 |
| Wizzup | and the plugin should try harder | 22:52 |
| Wizzup | that is not the bug fmg fixed | 22:52 |
| uvos | right | 22:52 |
| uvos | Wizzup: wait a second | 22:52 |
| uvos | so then the popup would you like to try again came up | 22:52 |
| uvos | i pressed yes | 22:52 |
| uvos | and then the network cooser came up again but my ap was missing | 22:53 |
| uvos | i waited some time | 22:53 |
| uvos | it dident appear | 22:53 |
| uvos | so i closed the dialog | 22:53 |
| uvos | and opend it again | 22:53 |
| uvos | my ap was there again | 22:53 |
| uvos | i clicked on it | 22:53 |
| uvos | and now the status menu icon is blinking forever | 22:53 |
| uvos | and its connected | 22:53 |
| uvos | let me reboot and try again. | 22:54 |
| freemangordon | uvos: this is the latest icd2, connui-common and connui-interned, right? | 22:54 |
| freemangordon | *connui-internet | 22:54 |
| uvos | freemangordon: yeah i just updated on devel | 22:54 |
| uvos | freemangordon: so i have whatever is latest on devel | 22:54 |
| Wizzup | freemangordon: the bug is solved for me | 22:54 |
| Wizzup | I cloned python-conic and ran this: | 22:54 |
| Wizzup | python tests/test_connect.py | 22:54 |
| Wizzup | and then I could connect right away | 22:55 |
| freemangordon | uvos: good. with older versions didn;t you have "no saved connections available" message over and over again? | 22:55 |
| uvos | no | 22:55 |
| uvos | i never saw that | 22:55 |
| freemangordon | weird | 22:55 |
| freemangordon | I've seen it lots of times on d4. But anyway, as Wizzup said, what you explain is another issue | 22:56 |
| uvos | ok | 22:56 |
| uvos | ok this time it just connected | 22:56 |
| uvos | i dont think it ever did it first try before | 22:56 |
| * uvos reboots again | 22:57 | |
| Wizzup | uvos: the icd2 wlan plugin should perhaps retry on initial association failure | 22:57 |
| freemangordon | on d4 it always fails for me after reboot even if I use wpa_supplicant only | 22:57 |
| Wizzup | currently it just gives up right away | 22:57 |
| uvos | freemangordon: thats wierd | 22:57 |
| uvos | it never fails with just wpa for me | 22:58 |
| freemangordon | maybe I shall upgrade kernel and retest though | 22:58 |
| uvos | anyhow i think the other issue is fixed | 22:58 |
| uvos | ie you can connect again after failuer | 22:58 |
| freemangordon | mhm | 22:58 |
| uvos | without closing all dialogs | 22:58 |
| freemangordon | this is what I was talking about | 22:59 |
| uvos | ok | 22:59 |
| uvos | but there is something else | 22:59 |
| freemangordon | yes, but I think it is something d4 specific | 22:59 |
| freemangordon | FW bug or something | 22:59 |
| uvos | the endless blinking wifi icon is still a bug thats not d4 specific | 22:59 |
| freemangordon | yes, this is a bug in icd2 wlan plugin | 22:59 |
| uvos | ok | 22:59 |
| freemangordon | Wizzup is aware of it | 23:00 |
| uvos | ok | 23:00 |
| freemangordon | but I think wlan is in a much better shape now that it was a week ago | 23:00 |
| uvos | no doubt | 23:00 |
| uvos | yeah works | 23:01 |
| uvos | it just failed to connect | 23:01 |
| uvos | i could rety after pressing yes on the prompt | 23:01 |
| uvos | so confirmed | 23:01 |
| freemangordon | great | 23:01 |
| freemangordon | Wizzup: good that python test case also confirms it, I think we will be able to close a couple of issues | 23:03 |
| Wizzup | freemangordon: yeah | 23:10 |
| uvos | Wizzup: parazyd: please update fbkeyboard from https://github.com/IMbackK/fbkeyboard | 23:19 |
| uvos | also please just give me commit access to my packages | 23:19 |
| uvos | this is somewhat silly | 23:19 |
| Wizzup | uvos: agreed, zzz first for me though | 23:38 |
| uvos | Wizzup: good night | 23:38 |
| parazyd | uvos: ok, will do it in the morning | 23:43 |
| uvos | parazyd: great thank you | 23:49 |
| uvos | parazyd: byw any ideas how we could bring fbkeayboard to devices other than xt875? | 23:50 |
| uvos | the only real universal thing i can think of is have a charge-mode style thing that checks if vol down is pressed or so | 23:51 |
| uvos | and then switches to the fbkeyboard mode | 23:51 |
| parazyd | Will think about it. Need some sleep now :) | 23:52 |
| uvos | i dont like this that much | 23:52 |
| uvos | ok good night :) | 23:52 |
| parazyd | Should be fairly simple really | 23:52 |
| parazyd | gn | 23:52 |
Generated by irclog2html.py 2.17.0 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!
