<ozgur>
So I have an ISP router, ZYXEL EX3501-T0 and want to create a wiki page for it. So I want to get the bootlog. I have soldered wires to the serial pins, and using a ch340g. But I was not able to get practicly anything while trying vaious pins. Any ideas ?
plappermaul has joined #openwrt-devel
<mrkiko>
have there been any news / progress / anything on the QCA SSDK (or related components) upstreaming? And regarding the whole ipq807 / qualcommax target?
guidosarducci has quit [Ping timeout: 480 seconds]
efahl has quit [Ping timeout: 480 seconds]
guidosarducci has joined #openwrt-devel
<Rondom>
from what I have seen there is mostly upstream activity for the qualcommbe targets
efahl has joined #openwrt-devel
<KanjiMonster>
I always read this as qualcomm big endian at first, and need to remind myself that they mean 802.11be
<mrkiko>
KanjiMonster: :)
<mrkiko>
Rondom: thanks
<mrkiko>
uh, bricked my NBG7815 :( due to a missing /24 after an ip address in an uci-default
<mrkiko>
uh, I can recover it luckily via wg
<mrkiko>
was feeling bad .......
_whitelogger has joined #openwrt-devel
<linusw_>
tmn505: thanks a ton! The link was pointing to python 3.11 instead of python3.13 and now everything works!
<linusw_>
I had to fix the links manually though, I wonder why the old python was picked up...
ozgur has quit [Remote host closed the connection]
_whitelogger has joined #openwrt-devel
n3ph has joined #openwrt-devel
efahl has quit [Remote host closed the connection]
plappermaul has quit [Remote host closed the connection]
efahl has joined #openwrt-devel
efahl has quit [Remote host closed the connection]
efahl has joined #openwrt-devel
efahl has quit [Remote host closed the connection]
n3ph has quit [Ping timeout: 480 seconds]
n3ph has joined #openwrt-devel
digitalcircuit has quit [Quit: Signing off from Quassel - see ya!]
<tmn505>
linusw_: handling python host side in OpenWrt is not ideal. Check the include/prereq-build.mk. The newest one is 3.12. Since Your distro upgraded python to 3.13 the check encounters 3.11 and creates symlink to that version, which may not be the one You currently work with.
<tmn505>
Another issue is if wide system upgrade was done and the python version gets replaced, the symlink is dangling with pointing to older version. The fix would be to run prereq again but the staging_dir/host/.prereq-build stamp prevents it. Remove that stamp and on next make run it should update the symlink.
<tmn505>
I've encountered this multiply times with Arch Linux. That's why I've created symlink to hot system python3 in staging_dir. If it breaks then so be it.