<pkgadd>
Borromini: TP-Link and serial console access isn't nice (you usually have to bridge some tiny 0W SMD resistor solder points on the rx line), but it's always worth checking
<Borromini>
pkgadd: v2 shouldn't need that, it has the holes exposed but not populated
<Borromini>
i tried with some wire as makeshift pins and then a serial cable but it didn't budge.
<pkgadd>
o.k., even better :) (I had lots of 'fun' recovering my tl-wr941ndv2)
<Borromini>
it's a 2,4 GHz only device, i was gonna give it to a friend... so it's not a big loss. just too bad it's because of some breakage in master
<Borromini>
i should have learned from last time i bricked a tp-link with a broken master build :P :P
<pkgadd>
yeah, I didn't really use my tl-wr9641ndv2 either - but I just couldn't accept it remaining bricked
<pkgadd>
although I had literally thrown it into the trash already
<pkgadd>
and slavaged it for parts (soldered-on pigtails, SPI-NOR flash, etc.)
<Borromini>
:P
<Borromini>
i'll keep the detachable antennae of the v2
<Borromini>
the gl-mt1300 is 32/256, that doesn't sound bad at all.
<Borromini>
and mt75
<Borromini>
* mt7615
<Borromini>
for what it's worth, i've been flashing mt7621 images all day, so the breakage looks ath79 specific.
<Borromini>
night guys
Borromini has quit [Quit: leaving]
mkresin has quit [Ping timeout: 268 seconds]
scde has joined #openwrt-devel
scde has quit [Client Quit]
mkresin has joined #openwrt-devel
ivanich_ has quit [Remote host closed the connection]
<Tapper>
I will test the mvebu kernel bump for you. You will have to tell me how to build as I onley know how to build master.
nitroshift has quit [Quit: Gone that way --->]
<mangix>
Hauke: breakage is about what I expected. I think this is one of the reasons the Turris people abandoned glibc when they had their OpenWrt fork.
<mangix>
Tapper: dengqf6 will probably handle that :)
<Tapper>
OK no probs
danitool has quit [Quit: Cubum autem in duos cubos, aut quadratoquadratum in duos quadratoquadratos]
<Borromini>
mangix: i don't but openssl pulls it in.
<Tapper>
I hade the same thing go rong for me but when trying to fix it I bricked mine and ldir fixt it for me.
<mangix>
Borromini: I think that dependency is adjustable in menuconfig
<Borromini>
mangix: no, somehow not.
<Borromini>
at least not with all the options i've ticked. i checked
<mangix>
Hauke: I briefly looked at the build failures. Seems pkgconf is not being compiled properly.
ivanich has quit [Ping timeout: 240 seconds]
<Borromini>
mangix: i don't mind to much, helping bring up 5.10 as well that way, so :)
<Hauke>
mangix: for me this looks like a problem in the SDK build
<Hauke>
libubox is compiling against glibc without SDK
ivanich has joined #openwrt-devel
hsp has quit [Quit: WeeChat 3.0]
Darkmatter66 has quit [Ping timeout: 260 seconds]
hsp has joined #openwrt-devel
hsp has quit [Client Quit]
dorf has joined #openwrt-devel
ivanich_ has joined #openwrt-devel
ivanich has quit [Read error: Connection reset by peer]
ivanich_ has quit [Ping timeout: 256 seconds]
hsp has joined #openwrt-devel
kakaka has quit [Ping timeout: 240 seconds]
ivanich_ has joined #openwrt-devel
feriman has quit [Quit: WeeChat 3.0]
feriman has joined #openwrt-devel
slh64 has quit [Ping timeout: 268 seconds]
dedeckeh has quit [Ping timeout: 245 seconds]
slh64 has joined #openwrt-devel
kakaka has joined #openwrt-devel
ivanich_ has quit [Ping timeout: 256 seconds]
ivanich_ has joined #openwrt-devel
ivanich_ has quit [Ping timeout: 264 seconds]
dedeckeh has joined #openwrt-devel
dorf has quit [Remote host closed the connection]
dorf has joined #openwrt-devel
ivanich_ has joined #openwrt-devel
dorf has quit [Remote host closed the connection]
dorf has joined #openwrt-devel
ivanich_ has quit [Ping timeout: 240 seconds]
ivanich_ has joined #openwrt-devel
* russell--
working on updating iproute2, discovers complaints about missing dependencies libmnl and libelf despite them being selected as 'm', something to do with the condition dependency?
<russell-->
exists on current 5.9.0 as well
mwarning has joined #openwrt-devel
<russell-->
Package tc is missing dependencies for the following libraries:
<Borromini>
his nick on irc is not neheb, i meant.
lmore377 has quit [Ping timeout: 260 seconds]
lmore377 has joined #openwrt-devel
damex has joined #openwrt-devel
falk0n has quit [Ping timeout: 256 seconds]
damex has quit [Read error: Connection reset by peer]
damex has joined #openwrt-devel
falk0n has joined #openwrt-devel
blb4393 has joined #openwrt-devel
Darkmatter66 has joined #openwrt-devel
valku has joined #openwrt-devel
blb4393 has quit [Quit: ChatZilla 0.9.93 [Waterfox 56.3/MOZ_BUILDID]]
swex has quit [Quit: swex]
victhor has joined #openwrt-devel
damex has quit [Read error: Connection reset by peer]
lmore377 has quit [Ping timeout: 260 seconds]
damex has joined #openwrt-devel
lmore377 has joined #openwrt-devel
rsalvaterra1 has quit [Quit: Leaving.]
rsalvaterra has joined #openwrt-devel
philipp64 has joined #openwrt-devel
lmore377 has quit [Ping timeout: 260 seconds]
lmore377 has joined #openwrt-devel
<rr123>
ath79 broken on master, bisecting here, not sure what's the annoying warning from: Makefile:86: warning: ignoring old recipe for target openwrt-ath79-generic-dlink_dap-2660-a1-squashfs-sysupgrade.bin"
ivanich_ has quit [Quit: Konversation terminated!]
<pkgadd>
I may be missing the obvious, but that commit does appear to be harmless
danitool has joined #openwrt-devel
<pkgadd>
I would believe some freak interaction for sysupgrading from that commit onwards, maybe also problems with uci-defaults network preconfiguration (does not apply to upgrades with keeping settings - but I don't see any issues in those hunks), but nothing that would explain boot problems after a sysupgrade
<Borromini>
pkgadd: that's what i thought too (and i said as much)
<Borromini>
looked harmless to me as well
<pkgadd>
what it does however, is touching the timestamp of the Makefile, which might make update the dependency chain
<pkgadd>
*might make GNU-make
<Borromini>
would that make a build break in such a way it produced defective firmware
<swegener>
https://bugs.openwrt.org/index.php?do=details&task_id=3531 the IMAGE/sysupgrade.bin/squashfs definition from 5fc28ef4 is leaking to other devices, result in sysupgrade.bin images being sysupgrade tarballs, which do not boot
gch981213 has quit [Read error: Connection reset by peer]
gch981213 has joined #openwrt-devel
<pkgadd>
ah, hat makes sense
<pkgadd>
that*
<Borromini>
oh lovely.
<Borromini>
thanks swegener
* Borromini
looks at his bricked 1043nd v2 :(
<mangix>
philipp64: pong
dorf has joined #openwrt-devel
<mangix>
Borromini: we wish you a merry christmas and a happy new brick :)
<swegener>
Borromini: yeah, i had to debrick my device with an spi programmer, because it has no uboot console or tftp recovery
<Borromini>
mangix: and a working recovery to you too :P
<Borromini>
swegener: yeah i have no soldering skills and the header is not populated, so this one's a write-off. such are the dangers of running master eh :P
<russell-->
Borromini: some pins and a spare thumb to maintain contact is enough
<Borromini>
russell--: i have wires that just fit. i can tell you it spewed out garbage first, then i switched tx/rx (vcc not connected), and after that it went silent.
linzst has joined #openwrt-devel
<Borromini>
might get someone to soler it and try the serial cable properly, but not much hope frankly.
linzst has quit [Max SendQ exceeded]
<PaulFertser>
Garbage might mean lack of gnd connection too.
<pkgadd>
at least a completely unpopulated header (without existing solder in the holes) would be trivial to solder (getting solder out of the holes needs a little more equipment, solder wick and solder sucker, and some basic experience)
<Borromini>
PaulFertser: i had all those wires angled (gnd as well), and inserted into the serial cable.
<Borromini>
pkgadd: i'm not in a hurry, i'll leave that to someone who knows how, but thanks for the tips
<russell-->
the garbage sounds like you had it right
<russell-->
rx anyway ;-)
<pkgadd>
yep (just bad GND)
<Borromini>
oh well...
<russell-->
i've learned to just not move for a few minutes
<Borromini>
how so? :P
<pkgadd>
yep, I nanddump/ backed up and flashed my bthub5 by pressing small cut/ insulated tinfoil leads to the solder points, using latex finger cots and keeping my fingers steady for around an hour
<pkgadd>
(given that the vias to connect to are so fragile)
<Borromini>
ok you won. i'll think about it :P
<pkgadd>
:)
<Borromini>
i'm trying to find what's breaking the n radio on my DIR-860L. it's on and off. very weird.
<Borromini>
(hijacked the ramips 5.10 pr)
<Borromini>
that's getting precedence atm :P
<mangix>
Borromini: 19.07 works?
<Borromini>
mangix: it does, albeit not reliably i think. i remember seeing the 2,4 GHz radio request resets all the time
<Borromini>
i had to revert to 19.07 through the bootloader, then it worked, sysupgraded to master again, there sometimes it works, sometimes it doesn't.
<russell-->
Borromini: i don't immediately see why that commit would break anything, do you have a link to an explanation of the bug?
<Borromini>
swegener: is the empty definition already there in ipq806x? because someone in #openwrt reported having an ipq806x device break (tp-link c2600)
<rr123>
this leakage killed my holiday :(
<swegener>
Borromini: the issue 5fc28e introduced is specific to ath79. ipq806x has some devices that uses sysupgrade tarballs, but it should be correct
<pkgadd>
it's sad how many vendors still don't care about a robust and reliable recovery mechanism
<Borromini>
swegener: ok, thanks
<Borromini>
pkgadd: i'm not buying tp-link anymore without checking available recovery methods first. learned my lesson.
<mangix>
Borromini: or join the dark side with breed :)
<rr123>
Borromini: tftp recovery worked well for me, i have 4 tplinks at home
<rr123>
not 100% robust but 95%, plus I can reach to uart if needed
<rr123>
but yes breed/never-die-uboot will be nicer
<Borromini>
mangix: i might yes, next time.
* rr123
tplink firmware is actually openwrt/luci undernearth as far as I can tell
<Borromini>
rr123: well this is the second 1043 v2 that bricks on me this way. hadn't tried serial with the first one though, gotta be honest about that
<Borromini>
rr123: a lot of vendor firmware is. just outdated SDKs though.
<pkgadd>
Borromini: that's actually the main reason why I didn't buy the archer c2600 (ipq8064), because they intentionally 'broke' the serial header (you need to bridge two solder points under the SOC tin and cooler, add some voltage level shifter, etc. pp. --> https://openwrt.org/toh/tp-link/tp-link_archer_c2600_v1#serial) - no, thanks
<rr123>
no uart, no deal, absolutely
<Borromini>
pkgadd: yeah, i've seen a few pictures on the wiki, even the 1043 v5 etc seems to need bridging like that nowadays
<pkgadd>
nb6817 --> easily accessible (unpopulated) header; r7800 --> populated header, a bit hidden under the cooler, but accessible with some bending of the pins
<pkgadd>
that (and the newer ipq8065 SOC) was worth the ~40 EUR markup for me
<russell-->
swegener: the author and committer of the problematic commit should probably be tagged
* enyc
meows at BT-HHv5a's working nicely on master =) will eep testing builds -- curious what sort of invasive changes expected into 20.x
swex has joined #openwrt-devel
<pkgadd>
enyc: DSA might be possible, afaik the mainline DSA drivers are close, not quite 100% ready, but close
<Borromini>
are there any targets that might still move to DSA before 20.x/21.x gets branched?
<pkgadd>
(for lantiq specifically)
<pkgadd>
Borromini: at this point, I hope not - quite quickly after probably ipq40xx (ipq806x shouldn't be too far away either), that should solve the VLAN issues
<Borromini>
that would be neat
<pkgadd>
mvebu and mt7621 imho switched rather late already
<Borromini>
:)
<Borromini>
it's a pity realtek won't be in the new stable release, but understandable given how fresh it is
<pkgadd>
it's looking quite cool, just keeping my fingers crossed for gs1900-24e support ;)
<Borromini>
:D
<Borromini>
i'm a bit in limbo on whether to stick with bkobl's tree or with openwrt master. the latter works. but i'll have to wait till someone ports fixes from it to openwrt master, if there are any
<pkgadd>
the target renaming made the situation a bit more complex to compare
<enyc>
pkgadd: humm i see. All I can say is so-far my lantiq VLANs are working fine!
<pkgadd>
enyc: different story, the VLAN situation is specific to ipq40xx with swconfig
<Borromini>
pkgadd: that as well.
<enyc>
age-old query when to fork openwrt 20.12, is the idea to do so before new year anyhow!?!? judgement call to make with ''new stuff' constantly on horizon, anyhow?
<pkgadd>
I hope it'll become 21.01 (especially considering the date), more reasonable to explain
<pkgadd>
imho it would be better to branch off as 21.01 in early january, than to squeeze it in within the coming week, just to hit the magic numbers (2020 date)
<pkgadd>
especially as you can expect 6+ weeks for the -rc phase
<Slimey>
excuse me while i whip this out
<russell-->
lol, naming something 2020 is going to weaken adoption ;-)
<Borromini>
pkgadd: i think we should christen it 'the covid edition' :P
<dana44>
nbd Sorry to bother you in the IRC channel. But after a couple days I finally was able to make time to respond in the forum. While the GF is out getting groceries I have a small window of a time to do any kind of further testing that might be useful. Let me know if I can do anything useful
<enyc>
the page lists hostapd 5.10 backports, ?!!? can't see 510 anywhere. .. and the DSA already mentioned.
<blocktrron>
Borromini: just find a cocktail receipe with corona beer to go full circle
<Borromini>
enyc: nbd has a tree with 5.10 bringup and there's a PR for ramips e.g.
<Borromini>
blocktrron: hehehe
<Borromini>
enyc: oh 5.10 mac80211. sorry. hauke has those in his tree as well i think (the wireless stack, not the full kernel bump)
<enyc>
Borromini: uerrr aaaah, to backport extra device support?
<Borromini>
enyc: no to backport wireless drivers. e.g. 19.07 uses 4.19 wireless stack (whereas most targets use a 4.14 kernel)
<Borromini>
allows openwrt to stick closer to upstream for drivers where it matters a lot (wireless)
<Borromini>
while not needing the most recent (and relatively more unstable) kernel
<enyc>
Borromini: I see. In x64 / desktop land I'm seeing all sorts of consternation about 5.4 vs 5.8 5.9 5.10 and new Ryzen support ;p
<Borromini>
desktop is different :)
<Borromini>
a desktop is something you shut down or reboot. you don't want your wifi to be down
<enyc>
sure, but still lots of 'what is stable' grumble grumble
<enyc>
arguments-arguments going on ;p
<enyc>
Borromini: hrrm you make me wonder if ath10k client mode works in updated release I shall try.......
<Borromini>
enyc: check what patches are in the mac80211 bump, usually gives an idea
Darkmatter66 has quit [Ping timeout: 268 seconds]
<enyc>
Borromini: happy to look if you have link to reference, i'm not yet that level of git voodoo =)
danitool has quit [Remote host closed the connection]
<Borromini>
enyc: you can check hauke's tree on git.openwrt.org
<Borromini>
for some reason i am unable to paste my buffer into irc atm >_>
<pkgadd>
his mac80211 updates for 5.10 are working fine for me