01:32 <marex> is there some reason why the list in "targets" is enumerated when, if I try such a simple thing as "targets 0", I get a message "use <long-cryptic-name> as target identifier, not 0' ?

09:05 <Xogium> heh now at least the wifi doesn't disconnect with reason=0 anymore… Which I'm glad for because reason=0 we have no idea what happens

09:06 <Xogium> but now getting this at random with my wifi automatically reconnecting after, as if nothing out of the ordinary happens

09:06 <Xogium> Jan 25 09:37:35 Tsenahale wpa_supplicant[1149]: wlan0: CTRL-EVENT-DISCONNECTED bssid=24:5a:4c:6e:b5:fa reason=3

09:06 <Xogium> aka it decided to leave just like that ? Maybe powersaving

09:08 <Xogium> guess that rebooting my AP helped in a way because I don't get reason=0 anymore

09:26 <Xogium> I tried and disabled powersaving again, wonder if it will help. I also notice packet loss when no actual disconnect occure so it might be partly due to powersaving. 1183 packets received against 1211 packets sent. Not *that* big, but still on the mean side. It could be normal for wifi though?

09:40 <PaulFertser> No, 50 % loss is not normal.

09:42 <karlp> nope, I still only come up with 2.3% loss.

09:42 <karlp> (which is still kinda shit)

09:43 <karlp> (do you have antenna connected? some dev boards only have an anntenna connector, and you'r emeant to attach it yourself later. and things.... work, without antennas, just not very well)

09:44 <Xogium> indeed 2.31% packet loss

09:45 <Xogium> karlp: I don't think this one has external antenna. Signal strength is also -40 DBm

09:46 <Xogium> then again I'm right beside the AP ;)

09:50 <Xogium> thanks ping for being half translated

09:50 <Xogium> with powersaving turned off

09:50 <Xogium> 1583 paquets transmis, 1583 reçus, 0% packet loss, time 1584111ms

09:51 <Xogium> I suspect powersaving was messing up pings

09:59 <PaulFertser> Lol, I couldn't read the "packets received" number because I use a broken LCD panel which has vertical stripe on that area, sorry.

10:00 <Xogium> haha

10:00 <Xogium> PaulFertser: it was

10:00 <Xogium> 1183 r 1211 s

10:01 <PaulFertser> Guess I'm just too sleepy to understand anything, sorry.

10:01 <Xogium> hehe that's ok

11:46 <borneoa_> No antenna connector on stm32mp1 board.

11:48 <borneoa_> Xogium: as I already told you there was some report of low throughput. Maybe it's caused by the packet loss. How did you turned off the power saving?

11:48 <Xogium> borneoa_: iw dev wlan0 set power_save off

11:48 <Xogium> that helped with the pings, like on 3580 packet sent I only have 0.1% packet loss

11:49 <Xogium> so that did something

11:49 <Xogium> but the reason=3 one now won't go away and is random

13:27 <Xogium> ah reason=0 came back. Erk. Even with powersave disabled

13:27 <Xogium> I must be royally unlucky

16:18 <Xogium> borneoa_: probably wishful thinking on my part but, I don't suppose there is a way to use the third mmc interface on the dk2 kit?

16:19 <Xogium> for example to hook up a 2nd micro sd slot

16:23 <borneoa_> Xogium: the sdmmc3 pins are available on the gpio expansion connector. You need to set them as sdmmc3 in the device tree. Then another gpio for the card detect switch. Looks feasible

16:33 <Xogium> borneoa_: ooh really ? Wow

16:33 <Xogium> that could be a lifesaver

16:35 <Xogium> borneoa_: if you're interested, I found a wifi+bt sdio module in sd card form factor, based on a QCA8377 SiP. I reckon this should also be supported by mainline linux, but it might be more portable for me than a rather bulky wifi usb dongle

16:36 <Xogium> I tried all I could to get the brcm chip to behave here, but I honestly can't manage it. It keeps disconnecting with reason=3 on wpa2 only network, and with reason=0 when wpa2/wpa3 is used

16:37 <Xogium> and since I can't find the cause for this… well. I kind of have to come up with new ways, I guess

16:38 <Xogium> reason=3 is apparently ok ciao I've had enough, I disconnect from this network

16:39 <Xogium> then 3 seconds later it reconnects

16:44 <borneoa_> Xogium: what is your plan for your products? To use dk2 boards or to make your own board later? In second case you can try different wifi.

16:45 <Xogium> borneoa_: well this is more for a personnal project of mine in the house, so I was thinking to use the dev kit, since it had everything I needed

16:45 <borneoa_> Xogium: Anyway ST buy the modules from Murata, so if the issue is with module's firmware it's in ST interest to get it fixed. If it's ST SW issue, it's ST duty to fix it. So far the issue appears with your AP. Would be good to replicate it somehow

16:46 <Xogium> yeah :/ I don't really know how though. How to replicate it, that is. I only have this one AP here, so I can't try with a different one

16:46 <PaulFertser> Xogium: it might be related to some fancy setting in that ubnt firmware, true.

16:46 <PaulFertser> Xogium: what about your computer, can't you run hostapd on it to serve as an AP?

16:48 <Xogium> PaulFertser: hmmm maybe ? It uh might work… I don't know actually, this wifi card is AX200 wifi 6

16:49 <Xogium> I don't know if it can do AP in 2.4 ghz mode

16:49 <PaulFertser> Xogium: check "iw list"

16:50 <PaulFertser> It should on 2.4 GHz band, afair.

16:51 <Xogium> ah yep I see it

16:54 <Xogium> lets try that

17:50 <Xogium> ok setup as an AP, we'll see how that goes

21:20 <karlp> PaulFertser: or anyone with acces to sourceforge: there's no "milestone" for 0.12 or anything future? the drop down only has 0.11 and 0.10?

21:28 <PaulFertser> karlp: just set 0.11

21:28 <PaulFertser> karlp: I'll add milestone later

21:45 <karlp> I think this is related the problem I've had before, the internal state of the flash vs the elf that gdb is looking for can be _wildly_ out of sync when you've connected, as you don't know what's in flash.

21:46 <karlp> and there's use cases for both, "yes, assume flash matches my flash when I connect" and "no, don't try and decoded rtos symbols based on the elf yet, that isn't what's in flash"