<Tusker>
heya guys, I am trying to define the gmac definition in the DTS for the device I am working on (ipq8068) - but the eth1 phy interface doesn't seem to be defined correctly and it fails to "attach"
<Tusker>
ipq806x-gmac-dwmac 37600000.ethernet eth1: no phy at addr -1
<Tusker>
how do I know what is connected on the mdio, and what reg = <0>; should it be set to ?
<Tusker>
i have busybox access to the factory firmware so I can check, but I'm not sure how to check...
snh has joined #openwrt-devel
Rentong has quit [Ping timeout: 480 seconds]
danitool has quit [Quit: Cubum autem in duos cubos, aut quadratoquadratum in duos quadratoquadratos]
rmilecki has joined #openwrt-devel
dorf has joined #openwrt-devel
dedeckeh has joined #openwrt-devel
valku has quit [Remote host closed the connection]
tohojo has quit [Quit: Bridge terminating on SIGTERM]
tohojo has joined #openwrt-devel
kpoman__ has quit [Remote host closed the connection]
kpoman has joined #openwrt-devel
kpoman has quit [Read error: Connection reset by peer]
kpoman has joined #openwrt-devel
<rsalvaterra>
jow: Ping. It could just be my imagination, but I'm seeing some oddness in fw3 chains…
<rsalvaterra>
I'm seeing empty chains, not associated to any interface, being created (in the form of {input,output,forwading}_rule. I noticed this just now, is it normal?
<rsalvaterra>
Of course, I have the normal {input,output,forwading}_<interface>_rule chains, and everything works, but I'm wondering if those other chains should exist at all.
<rsalvaterra>
They are referenced, though…
<rsalvaterra>
Ah, forget it, I'm an idiot.
<xback>
ynezz: hauke: jow: Any objections from any of you to pushing ath79/rb912 patches to 21.02? it's very late in the cycle but took a lot of work to get it top-notch and extensively/thoroughly tested. been running it for 2 weeks now and tested again this morning on todays latest 21.02
zorun has joined #openwrt-devel
<hauke>
xback: are you talking about the patches in your staging tree?
<hauke>
xback: you should deactivate CONFIG_GPIO_LATCH in target/linux/ath79/config-5.4
<hauke>
and MTD_NAND_RB91X
nlowe has joined #openwrt-devel
<hauke>
xback: you should add "cherry picked from commit " to all commits
Tapper has joined #openwrt-devel
<russell-->
Tusker: dmesg would be a place to look
<russell-->
also see if there is a device tree accessible from the OS or flash
<hauke>
xback: otherwise the patches are looking and you can merge them
nlowe has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
bookworm has quit [Remote host closed the connection]
<xback>
hauke: thanks for your insights! appreciated
nitroshift has quit [Quit: Gone that way --->]
<ldir>
rsalvaterra: hey! that's my job!
<EqUaTe>
ldir: you're just going to have to up your game ;)
<rsalvaterra>
ldir: Sorry, didn't mean to step on your toes… xD
* ldir
builds a better idiot
bookworm has joined #openwrt-devel
nlowe has joined #openwrt-devel
<Tusker>
russell--: yeah, I don't see much in the factory dmesg that helps me with ethernet stuff
<Tusker>
GMAC0(ecffc500) Invalid MAC@ - using 4e:4f:50:51:52:53
<Tusker>
i tried to grab the device tree blob, but I can't seem to decode it using dtc
nlowe has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
nlowe has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
minimal has joined #openwrt-devel
Rentong has quit [Ping timeout: 480 seconds]
goliath has joined #openwrt-devel
aleasto has quit [Remote host closed the connection]
Tapper has quit [Ping timeout: 480 seconds]
Tapper has joined #openwrt-devel
Tapper has quit [Ping timeout: 480 seconds]
valku has joined #openwrt-devel
Rentong has joined #openwrt-devel
Rentong has quit [Remote host closed the connection]
Rentong has joined #openwrt-devel
dr|z3d_ has joined #openwrt-devel
dorf has quit [Ping timeout: 480 seconds]
netprince has joined #openwrt-devel
Tusker has quit [Quit: Time wasted on IRC: 11 hours 44 minutes 32 seconds]
JohnA_ has joined #openwrt-devel
Luke-Jr has quit [Ping timeout: 480 seconds]
JohnA has quit [Ping timeout: 480 seconds]
<barhom>
I'm trying to setup 802.11s mesh. Is it supposed to work that anyone in the mesh network sends packet to the strongest nearest-mesh router?
<barhom>
Its working fine from main router->first-mesh-sub-router. But from first-mesh-sub-router -> second-mesh-sub-router it is unstable to the point it keeps on reconnecting
Edgaru089 has joined #openwrt-devel
<Edgaru089>
Hi, I just noticed that kernel configs for x86_64 has NR_CPU set to the small number 8.
<Edgaru089>
Is it of any special reason?
Tapper has joined #openwrt-devel
Luke-Jr has joined #openwrt-devel
<Edgaru089>
The point is that since the rise of AMD people can acquire x86 CPUs with core count more than 8, so should we have the number increased?
<Edgaru089>
I mean, on the cousumer level
rsalvaterra_ has joined #openwrt-devel
Edgaru089 has quit [Remote host closed the connection]
rsalvaterra has quit [Ping timeout: 480 seconds]
aleasto has joined #openwrt-devel
<stintel>
can anyone point me to the code that handles ifname '@wan' ?
<stintel>
nvm found it
Rentong has quit [Remote host closed the connection]
<rmilecki>
stintel: alias in netifd
Rentong has joined #openwrt-devel
<rmilecki>
ok, fuck, this got quite annoying for me now
<rmilecki>
i had poor wifi with Xiaomi Mi Router 4C (MT7628AN) - it was expected to be MT7628AN problem and people claim other devices behave OK
<rmilecki>
people are happy with Xiaomi Mi Router 4A Gigabit (MT7621 + MT7603 + MT7612)
<rmilecki>
people also recommend non-Xiaomi routers
<rmilecki>
so I've bought 2 x Netgear R6220 (MT7621ST + MT7603EN + MT7612EN) and it's the same shit: https://pastebin.com/raw/JrjwSKWT
<rmilecki>
PaulFertser nbd ^^
<rsalvaterra_>
rmilecki: Is that on the 03 or the 12?
<rmilecki>
do you mean release?
<rmilecki>
19.07.7
Rentong has quit [Ping timeout: 480 seconds]
<rsalvaterra_>
rmilecki: MT7603 or MT7612?
<rmilecki>
2 GHz so MT7603
<rmilecki>
it seems that MT7603 / MT7628AN is just broken
<rsalvaterra_>
rmilecki: Sorry, it wasn't explicit in either what you wrote or the pastebin… :)
<rmilecki>
you're right, i didn't specif
<rsalvaterra_>
I haven't measured the speed on the MT7603 specifically, but I also have one on my Redmi AC2100.
<stintel>
I've got a GL-MT1300 with MT7615E and that seems to work amazingly well
Tapper has quit [Ping timeout: 480 seconds]
<rmilecki>
rsalvaterra_: can you try running iperf over MT7603 connection for an hour?
<rsalvaterra_>
stintel: Also have the MT7615E on the Redmi. It's just unfortunate some features are still missing (beamforming, for example).
<rsalvaterra_>
rmilecki: Sorry, not yet… I'm on the Omnia, at the moment, with its craptastic pair of QCA9880 cards.
<stintel>
well either the macbook pro or the galaxy s9 from my new project made ath10k-ct firmware crap itself multiple times per minute
<stintel>
so my APs are basically all useless
<rmilecki>
stintel: that's why I chose mt76 instead of ath10k
<rmilecki>
it seems ath9k was a better idea
<stintel>
well ... ath9k is slow
<PaulFertser>
rmilecki: what does "iw dev .. station dump" saying during the high-speed phase of the iperf test? And is there anything special about your 2.4 GHz configuration? Probably forced HT40 or something? That's really odd you're getting that results.
<rmilecki>
stintel: i also works
<rsalvaterra_>
Wait, rmilecki… you said 19.07. Master, please.
<stintel>
or at least 21.02-rc?
<rsalvaterra_>
(I'm running master on the Redmi.)
<rmilecki>
rsalvaterra_: i tried master on Xiaomi 4C (MT7628AN) and got the same problems
<rmilecki>
but yes, I'm upgrading to master now
<rmilecki>
PaulFertser: nothing non-standard, I just booted clean OpenWrt, enabled wifi and set SSID + key
<rsalvaterra_>
I've heart stories of mt76 devices with crappy caldata… maybe it's the case…?
JohnA has joined #openwrt-devel
<rmilecki>
rsalvaterra_: it's not, I already provided a pretty eeprom dump
<rsalvaterra_>
Ah, right, I remember seeing it.
<PaulFertser>
I mean, there's a dump all right but how one can say if the data is crappy or not?
<rmilecki>
PaulFertser: every time I sow iperf slowing down, my 72.2 MBit/s got down to 6.0 MBit/s
<rmilecki>
nbd: ^^ does it mean anything?
<stintel>
on a Huawei (Qualcomm 11ax) AP
<rmilecki>
nbd: that is "iw" loop runnig on a Netgear R6220 (for MT7603 phy)
<stintel>
hmmmm I hope I'll be able to pull this off without my desoldering tool
Tapper has quit [Remote host closed the connection]
Tapper has joined #openwrt-devel
Rentong has quit [Remote host closed the connection]
Rentong has joined #openwrt-devel
Rentong has quit [Ping timeout: 480 seconds]
<stintel>
rip
slh has quit [Remote host closed the connection]
slh64 has quit [Read error: Connection reset by peer]
kpoman has quit [Quit: Leaving]
Tapper has quit [Ping timeout: 480 seconds]
jlsalvador has quit [Quit: jlsalvador]
Tapper has joined #openwrt-devel
rsalvaterra_ has quit []
rmilecki has quit [Quit: Konversation terminated!]
rsalvaterra has joined #openwrt-devel
rmilecki has joined #openwrt-devel
dr|z3d_ has quit [Remote host closed the connection]
dr|z3d_ has joined #openwrt-devel
dr|z3d_ has quit [Remote host closed the connection]
dr|z3d_ has joined #openwrt-devel
rmilecki has quit [Quit: Konversation terminated!]
rmilecki has joined #openwrt-devel
rmilecki has quit []
dr|z3d_ has quit [Remote host closed the connection]
Tapper has quit [Ping timeout: 481 seconds]
dr|z3d_ has joined #openwrt-devel
minimal has quit []
nlowe has joined #openwrt-devel
slh has joined #openwrt-devel
slh64 has joined #openwrt-devel
nlowe has quit []
nlowe has joined #openwrt-devel
nlowe has quit [Ping timeout: 480 seconds]
Rentong has joined #openwrt-devel
aleasto has quit [Ping timeout: 480 seconds]
Rentong has quit [Ping timeout: 480 seconds]
danitool has joined #openwrt-devel
Tapper has joined #openwrt-devel
Tapper has quit [Ping timeout: 482 seconds]
dr|z3d_ has quit [Remote host closed the connection]
dr|z3d_ has joined #openwrt-devel
swegener_ has quit [Quit: leaving]
swegener has joined #openwrt-devel
Weasel____ has quit [Quit: Leaving]
slh has quit [Ping timeout: 480 seconds]
slh64 has quit [Ping timeout: 480 seconds]
slh64 has joined #openwrt-devel
Weasel___ has joined #openwrt-devel
slh has joined #openwrt-devel
aleksander has quit [Remote host closed the connection]
Luke-Jr has quit [Ping timeout: 480 seconds]
Tapper has joined #openwrt-devel
Rentong has joined #openwrt-devel
Luke-Jr has joined #openwrt-devel
Rentong has quit [Ping timeout: 480 seconds]
JohnA has quit [Remote host closed the connection]
dr|z3d_ has quit [Remote host closed the connection]
dr|z3d_ has joined #openwrt-devel
<stintel>
Uncompressing ... LZMA: uncompress or overwrite error 1 - must RESET board to recover
<stintel>
that ramdisk flash method for GS108Tv3 is not safe
<slh>
that's surprising, it has worked for quite a few users on that hardware already (most of them had issues to connect on VID100 afterwards, but the flashing itself succeeded for them), but I've only worked with my gs1900-8 so far (waiting for a DGS-1210-16 revG1 to arrive)
<stintel>
I added a warning on the wiki just in case
<slh>
you could recover via serial console/ tftboot?
<stintel>
I nuked the RX pin hole because I don't have a desoldering pump or other tools here :(
<slh>
:(
<stintel>
I'll take it home next weekend and clamp the NOR
<stintel>
and I will probably go and buy some extra tools just to have in my secondary location to avoid things like this in the future :)
<stintel>
oooh managed to esc the bootloader while holding a jumper wire to the resistor connected to rx :P
<stintel>
I might just pull this off
<slh>
:)
<slh>
fortunately these managed switches tend to be easy to open (no hidden plastic clasps) - and at least the ZyXEL gs1900 series comes with a populated 2.54mm pin header for its serial console (I will have to solder on the DGS-1210-16)
* russell--
has avoided many problems by just insisting on a serial console all the time
<stintel>
yeah, like my DAP-2695
<stintel>
that now crap themselves many times per minute because ath10k-ct firmware doesn't like galaxy s9 ¯\_(ツ)_/¯
<stintel>
I'm not getting any network on the GS108Tv3 :/
<stintel>
rtk network on didn't help
<stintel>
ahh wait, reset and tried again, now seems ok
<stintel>
bingo
<russell-->
i have one here on my desk with serial if that's helpful at all
<stintel>
what do you mean ?
<russell-->
i mean i have a gs108t v3 on my desk with a serial console attached, so i can see what it's doing during boot, for example
<stintel>
ah well I just managed to boot mine via tftp / initramfs while holding a jumper wire against rx resistor
<stintel>
now networkmangler refuses to do VLAN :/
<stintel>
and for some reason this switch used vlan 100 for its management IP
<stintel>
since when do we do that in OpenWrt ?
<slh>
that is the default configuration for all the devices on the realtek target
<russell-->
yeah, i have a more normal network configuration with the help of the tom nixon patch
<slh>
there has been a patch on the mailing list to nuke that
<slh>
it somehow makes sense, but I don't like it either
<russell-->
no more crazy bridge_vlan silliness
<slh>
(all ports are WAN, firewalled to hell - but at the same time allowing opkg to fetch packages without a hitch; management restricted to VID100 on LAN1 only)
<russell-->
i have mine configured like an 8-port ubiquiti er-x router but with a stupidly-slow network
<stintel>
well yeah this particular soc is slower than >10y old ar71xx devices :P
<stintel>
it's not meant to be used as a router ;)
<stintel>
bah, didn't save its settings during sysupgrade
<stintel>
good thing I have lldpd in my image so I could see it went back to the default IP like that
<stintel>
but yeah quite frustrating, it did DHCP and got an IP but firewalled
<stintel>
maybe I should have left iptables out of the image
floof58 has quit [Ping timeout: 480 seconds]
takimata_ has joined #openwrt-devel
takimata has quit [Ping timeout: 480 seconds]
takimata_ is now known as takimata
<slh>
I was rather surprised how well (fast) luci is working, compared to e.g. lantiq or early generation ath79, but it's obviously not a router (although there is some untapped offloading potential into the switch fabric, albeit more with rtl839x and rtl93xx)
<stintel>
I'm looking forward to a model that is properly spec'd to replace my Huawei S6720-32C-PWH-SI
<slh>
rtl93xx does offer a few 10 GBit/s ports, but afaik it's still mostly a 1 GBit/s SOC
<stintel>
I'm currently using the Huawei as L3 switch for some VLANs but there's no stateful packet filtering so its use is limited to trusted VLANs
<stintel>
so I'm looking for a 10GbE capable router anyway
<slh>
there are apparently some efforts in regards to the xgs1930 series (still no full 10 GbE, just 4 ports among 1000BASE-T)
<stintel>
pfft I should have asked my father to install more RJ45 outlets in my old room :P
<stintel>
2 is .. ugh :)
<slh>
most wouldn't see a reason for two already (given free reign, on a new build, I'd put two ports into each corner, plus one somewhere around the ceiling, one in the vicinity of the windows, one close to the door and wherever desks/ TV sets, phones, etc. might be conceivable - just hard to do in an existing house)
<stintel>
haha, sounds about right
<stintel>
in my apartment I have 2 in the entire building
<stintel>
one that connects the lower floor with the upper floor