jlsalvador has quit [Read error: No route to host]
jlsalvador has joined #openwrt-devel
slh has joined #openwrt-devel
lmore377 has quit [Ping timeout: 480 seconds]
slh has quit [Quit: leaving]
Rentong has joined #openwrt-devel
Rentong has quit [Remote host closed the connection]
Rentong has joined #openwrt-devel
Rentong has quit [Ping timeout: 480 seconds]
_whitelogger has joined #openwrt-devel
xdarklight has quit [Ping timeout: 480 seconds]
Rentong has joined #openwrt-devel
<hexagonwin[m]> Oh and there's a heatsink stuck above the 2.4g and 5g wifi chip so I can't see what's written on it :(
<hexagonwin[m]> There are 3 heatsink/big chips on the board, however on the board there's a square marking 2.4g area and 5g area
<hexagonwin[m]> and in each area one chip
<hexagonwin[m]> so those seems to be the wifi chip..
<hexagonwin[m]> (and the outside one is ap)
Tapper has quit [Ping timeout: 480 seconds]
danitool has quit [Quit: Cubum autem in duos cubos, aut quadratoquadratum in duos quadratoquadratos]
slh has joined #openwrt-devel
slh64 has joined #openwrt-devel
<slh> hexagonwin[m]: the FCC images might provide some clues, the chip marking 'should' be readable there (but sadly aren't alway)
Luke-Jr has quit [Ping timeout: 480 seconds]
<owrt-snap-builds> Build [#261](https://buildbot.openwrt.org/master/images/#builders/2/builds/261) of `layerscape/armv7` completed successfully.
<hexagonwin[m]> <slh> "hexagonwin: the FCC images might..." <- This router don't have FCC thing it's South Korea only sold :(
<slh> then the kernel messages of the proprietary OEM firmware might be close enough
Luke-Jr has joined #openwrt-devel
<slh> after all there aren't that many alternative with mt7621
<hexagonwin[m]> Thanks I do have a boot log of OEM firmware that i got with uart
<slh> interesting, I would have expected something like validFlashEepromID(): eeFlashId=7915, pAd->ChipID=7915
jlsalvador has quit [Read error: Connection reset by peer]
jlsalvador has joined #openwrt-devel
<hexagonwin[m]> I can't find a thing about wifi in the log :(
<slh> or info about the payload, but those messages are still very much rt2860 era
<slh> which would be in line with mt7628, but less so with mt7621
<hexagonwin[m]> I guess that's a bit weird..?
<hexagonwin[m]> There's a source about the oem firmware
<hexagonwin[m]> (although for some parts it contains binaries instead of sources;;)
<hexagonwin[m]> by the way is running echo disabled 0 > /etc/config/wireless the right way to enable wifi??
<slh> no
<hexagonwin[m]> then how should I?
<slh> configure it, as you normally would on any other OpenWrt device - thereby removing the option disabled 1 line
<hexagonwin[m]> As i mention earlier I don't have this file /etc/config/wireless
<hexagonwin[m]> Sorry I'm new to owrt, is not having that file weird..?
<slh> then no wireless hardware is detected (as in no drivers/ firmware present)
<hexagonwin[m]> I just flashed the initramfs now not the sysupgrade image
<hexagonwin[m]> ohh alright
<hexagonwin[m]> thats weird
Rentong has quit [Ping timeout: 480 seconds]
<hexagonwin[m]> Oh and running lspci also returns no command, do i need to install it?
<russell--> if you want to run it, you'll need to install it
<slh> you're in charge of installing anything you might want to use, including selecting the necessary wireless drivers and their firmware packages, if you're porting a new device
<hexagonwin[m]> Ohh alright
<russell--> you might be able to get away with looking in /sys/bus/pci
<hexagonwin[m]> Thanks
<russell--> or dmesg | grep pci
dangole has quit [Ping timeout: 480 seconds]
<hexagonwin[m]> when I do it has some failed to assign is it normal?
<hexagonwin[m]> pci 0000:00:00.0: BAR 0: failed to assign [mem size 0x80000000 ]
<hexagonwin[m]> things like these
<hexagonwin[m]> If I get a shell in oem firmware can I see which wlan I have?
Luke-Jr has quit []
Luke-Jr has joined #openwrt-devel
<hexagonwin[m]> Can I see which packages are available in OWRT repository?
<hexagonwin[m]> (In order to find correct names for the packages I need to put in mt7621.mk)
<hexagonwin[m]> Found it
<hexagonwin[m]> Which package should i put for mt7612e and mt7602e ???
<hexagonwin[m]> i mean the kernel module name. Thanks
noltari has quit [Read error: Connection reset by peer]
<hexagonwin[m]> Fixed!
noltari has joined #openwrt-devel
<hexagonwin[m]> By adding kmod-mt76x2 in makefile
* enyc meeps
<Tusker> enyc: is meep less annoying? :)
<enyc> Tusker: who deal with channel topic !!!?!?
<Tusker> not really sure sorry
<hexagonwin[m]> Hmm so now it seemed to work.. I connected wan and installed luci, on luci it also sees the wlan, however after I turn it on to work as an AP my smartphones and computers all don't see it. (LEDs aren't also working but that's normal since I didn't fix yet) how should I debug this..?
<hexagonwin[m]> discovering wifi inside luci works
<hexagonwin[m]> booting uart shows that mt76x2 firmware loaded
<owrt-snap-builds> Build [#223](https://buildbot.openwrt.org/master/images/#builders/36/builds/223) of `mediatek/mt7629` completed successfully.
<hexagonwin[m]> Phone doesn't see wifi named OpenWrt
Guest3673 has quit []
<hexagonwin[m]> Is there a way to test if antennas are intact?
oftc has joined #openwrt-devel
oftc is now known as Guest3684
<Tusker> hexagonwin[m]: can you see anything in something like WiFi Anlayzer android app ?
Guest3684 is now known as xdarklight
<hexagonwin[m]> Tusker: Oh yes I have that app and I don't see it
<hexagonwin[m]> I got a copy from F-Droid
<Tusker> ok, what happens when you try to scan from openwrt ? can it see any networks itself ?
valku has joined #openwrt-devel
<hexagonwin[m]> So in my phone I see like 20 wifis
<hexagonwin[m]> and in OpenWRT now i turned it off but in network/wireless there was two scan buttons and one gave only one wifi and one gave none
<hexagonwin[m]> and the one that it showed is from my house...
<hexagonwin[m]> I'll try flashing oem firmware and see if it works there or not
<Tusker> that doesn't sound like the antennas are connected properly then
<Tusker> OK
valku has quit []
<hexagonwin[m]> weird
<hexagonwin[m]> working in stock firmware
KGB-0 has quit [Quit: KGB-0]
<hexagonwin[m]> by the way is there a way to install luci offline?
<hexagonwin[m]> It's hard to connect wan cable because it's too far away
KGB-0 has joined #openwrt-devel
<owrt-snap-builds> Build [#223](https://buildbot.openwrt.org/master/images/#builders/32/builds/223) of `omap/generic` completed successfully.
jlsalvador has quit [Read error: Connection reset by peer]
jlsalvador has joined #openwrt-devel
KGB-0 has quit [Quit: KGB-0]
KGB-0 has joined #openwrt-devel
<Tusker> hexagonwin[m]: you can build an image with luci in it
<hexagonwin[m]> <Tusker> "hexagonwin: you can build an..." <- set in menuconfig?
KGB-0 has quit [Quit: KGB-0]
KGB-0 has joined #openwrt-devel
<Tusker> yeah, after you update the feeds (./scripts/feeds update -a && ./scripts/feeds install -a && make menuconfig)
<hexagonwin[m]> Yeah thanks
<hexagonwin[m]> I reinstalled OpenWrt now with luci and installed initramfs => sysupgrade
<hexagonwin[m]> and still it doesn't detect wifi
<hexagonwin[m]> it literally shows no wifi at all now
<hexagonwin[m]> but what does this mean device is not active ??
<hexagonwin[m]> in wireless the mt76x2e 802.11bgn shows it
<hexagonwin[m]> and mt76x2e 802.11nac shows channel 36 blah blah
nitroshift has joined #openwrt-devel
<Tusker> not really sure about that device sorry, what is it again ?
<hexagonwin[m]> it's iptime a3004ns-dual
<hexagonwin[m]> ramips
<hexagonwin[m]> mt7621, 256mb ram, 16mb nand
rmilecki has joined #openwrt-devel
<hexagonwin[m]> mt7602e and mt7612e for wifi
<hexagonwin[m]> (And is very similar to currently supported in openwrt device named iptime a8004t)
<hexagonwin[m]> no matter what i do it doesn't work and now doesn't even detect any wifi network
<Tusker> yeah OK, I haven't used mtk enough to lend much assitance, sorry
<hexagonwin[m]> Alright, thanks anyway!
dedeckeh has joined #openwrt-devel
xback has quit [Remote host closed the connection]
<hexagonwin[m]> In here the signal and tx power offset is all none
<hexagonwin[m]> is it normal?
<hexagonwin[m]> For example here https://mans0n.github.io/2020/08/22/openwrt-add-new-device/031-iwinfo.png signal is shown
wulfy23 has joined #openwrt-devel
<wulfy23> dangole: in your travels... if its agreeable with you can we print the bus path on exceptions?
<wulfy23> aka netifd-2021-06-04-50381d0a/main.c:fprintf(stderr, "Failed to connect to ubus\n"
<wulfy23> many thanks
<hexagonwin[m]> When I install wrong wifi firmwares then it doesn't even get loaded right?
goliath has joined #openwrt-devel
<wulfy23> (oops technically thats a generic request everywhere only pinged daniel seems active around those parts)
<wulfy23> s/request/preference
<russell--> hexagonwin[m]: that sounds similar to the dlink 860l
Rentong has joined #openwrt-devel
wulfy23 has quit [Remote host closed the connection]
jlsalvador has quit [Quit: jlsalvador]
Rentong has quit [Ping timeout: 480 seconds]
<hexagonwin[m]> D-Link 860L? I'll search
<hexagonwin[m]> mt7621_dlink_dir-860l-bl.dts
<hexagonwin[m]> right?
<hexagonwin[m]> https://openwrt.org/toh/d-link/dir-860l_b1 not much info in wiki, how was the issue fixed for this device?
<hexagonwin[m]> Oh and I'm working on latest git master of http://github.com/openwrt/openwrt
<fda> and maybe mute all the "Command failed: Not found" appearing everywhere, eg on service commands?
<hexagonwin[m]> russell--:
<hexagonwin[m]> * I don't find anything in dlink dts different from thisrussell--:
jlsalvador has joined #openwrt-devel
<russell--> hexagonwin[m]: no issues on the dir860l-b1 that i'm aware of
<russell--> mine is running r17127-99a22d48f2 right now
goliath has quit [Quit: SIGSEGV]
<hexagonwin[m]> Then in what part sound similar? it seems like specs are similar though
<russell--> radios
<hexagonwin[m]> Ah the chips are same? Or the issue?
<russell--> chips
dangole has joined #openwrt-devel
<hexagonwin[m]> weird
<russell--> what is your issue? the iwinfo output looks normal to me
<hexagonwin[m]> wifi doesn't work at all
<hexagonwin[m]> even when ap is enabled other devices doesn't see it
<hexagonwin[m]> and also the router itself doesn't see other wifis
<hexagonwin[m]> I thought I broke the antenna so i went to oem firmware again and it worked again
<russell--> pastebin "dmesg | grep mt76" output
<russell--> this is what i see on the dir860l: http://sprunge.us/naVXYN
<hexagonwin[m]> This is mine
<hexagonwin[m]> hmm..
<russell--> how about "iw phy0 info | curl -F 'sprunge=<-' http://sprunge.us"
<russell--> my phy0 is the 5GHz
danitool has joined #openwrt-devel
Tapper has joined #openwrt-devel
<russell--> hexagonwin[m]: ?
rejoicetreat has joined #openwrt-devel
goliath has joined #openwrt-devel
<owrt-2102-builds> Build [#102](https://buildbot.openwrt.org/openwrt-21.02/images/#builders/41/builds/102) of `mediatek/mt7623` failed.
<hexagonwin[m]> Sorry!
<hexagonwin[m]> The router isn't connected to the internet
jlsalvador has quit [Remote host closed the connection]
jlsalvador has joined #openwrt-devel
rmilecki has quit [Ping timeout: 480 seconds]
<hexagonwin[m]> This is it russell--
<hexagonwin[m]> <russell--> "this is what i see on the..." <- http://sprunge.us/mmV2eQ
<PaulFertser> hexagonwin[m]: looks proper. Try doing "iw dev wlan0 scan" (and same for wlan1)
<PaulFertser> hexagonwin[m]: and after your APs are brought up check "iw dev"
<hexagonwin[m]> Okay
<PaulFertser> "Parsing DT failed" looks wrong but since it's able to run firmware anyway on both cards it probably doesn't matter.
<hexagonwin[m]> Yeah and russell-- 's log also shows it
<russell--> PaulFertser: yeah, was just going to say i see that the parsing dt failed, and my radios work fine afaict
<hexagonwin[m]> <PaulFertser> "hexagonwin: and after your APs..." <- http://sprunge.us/RhfjpW
<hexagonwin[m]> Sorry for late send
rmilecki has joined #openwrt-devel
<hexagonwin[m]> PaulFertser: is the wlan0/1 scan failing normal when wifi ap is turned on?
<hexagonwin[m]> (i mean in luci)
rmilecki has quit [Quit: Konversation terminated!]
<hexagonwin[m]> I disabled wifi in luci and wlan0 and wlan1 device disappeared.
<hexagonwin[m]> I'll try a reboot
<PaulFertser> hexagonwin[m]: hm, how about calibration data, is mediatek,mtd-eeprom set properly in your DTS? Have you checked manually the data is there? (the first word should match the model name)
<hexagonwin[m]> Oh I'll check
<hexagonwin[m]> Ah yes I did
<hexagonwin[m]> I did grep with hexdump on factory partition where the mac address is in
<PaulFertser> hexagonwin[m]: e.g. on my mir3g I have hexdump -C showing this: 00008000 62 76 01 00 and 00000000 03 76 01 02
<hexagonwin[m]> (followed a guide in https://mans0n.github.io/2020/08/22/openwrt-add-new-device/ but korean)
<PaulFertser> hexagonwin[m]: so 7603 should get offset 0 from the factory partition and 7662 offset 0x8000
<PaulFertser> I do not think any guides should be used, they often lead to confusion.
<hexagonwin[m]> so 2g was in 0x0000 and 5g was 0x8000
<hexagonwin[m]> i mean 0000000000 and 000008000 or something like that
<hexagonwin[m]> hexdump grep showed
<hexagonwin[m]> cat /proc/mtd returned factory as mtd2 for me also so I ran "hexdump -C /dev/mtd | grep "my mc"
<hexagonwin[m]> and my mc is the last four digits of my mac address
<hexagonwin[m]> that returns few lines since those are all numbers in my mac address but I could easily find what is the mac address and what isnt
<PaulFertser> hexagonwin[m]: but I'm saying about model number, it's at the very beginning of what you should give as mtd-eeprom.
<hexagonwin[m]> Oh
<PaulFertser> hexagonwin[m]: and do you see the expected mac addresses in "ip a" now?
<hexagonwin[m]> Yes the mac addresses are correct
<hexagonwin[m]> as the stock firmware one
<hexagonwin[m]> each 2.4g and 5g wifi mac address
<hexagonwin[m]> but i didn't check lan ports' mac address yet
<hexagonwin[m]> PaulFertser: Im sorry I can't understand what you mean.. sorry
<hexagonwin[m]> which model number..?
<PaulFertser> hexagonwin[m]: 7612 and 7602.
<hexagonwin[m]> Oh
<hexagonwin[m]> I realized what chip I have from OEM firmware's source code
<PaulFertser> hexagonwin[m]: i see your first pcie device seems to be 7612 and you specify "factory 0" for it. What is the first word you see at factory 0?
<PaulFertser> hexagonwin[m]: and what is the first word you see at factory 0x8000 ?
<hexagonwin[m]> PaulFertser: how can I see the first word in factory 0..? run hexdump?
<hexagonwin[m]> sorry :(
<PaulFertser> hexagonwin[m]: hexdump -C, yes
<Tusker> hexdump -C -n 8 /dev/mtd1
<Tusker> something like that
<PaulFertser> In case mtd1 is the same partition that has label factory in your DTS.
<hexagonwin[m]> root@Alice-Net:~# hexdump -C /dev/mtd2 | grep "00000000"
<hexagonwin[m]> 00000000 62 76 01 00 90 9f 33 be 41 20 02 76 c3 14 00 00 |bv....3.A .v....|
<hexagonwin[m]> Oh
<hexagonwin[m]> Tusker: what is -n 8? line 8?
<PaulFertser> mtd2 I think.
<Tusker> number of bytes
<hexagonwin[m]> yes mtd2 is factory
<hexagonwin[m]> okay
<Tusker> hexdump -s 0x8000 -C -n 8 /dev/mtd2
<Tusker> to check at offset 0x8000
<hexagonwin[m]> So in 8000 that isn't the mac address
<hexagonwin[m]> weird
<PaulFertser> hexagonwin[m]: I would expect your 0 pcie device to be used for 5 GHz and the 1st pcie device to be used for 2.4 GHz, but you have it the opposite way.
<hexagonwin[m]> Oh that makes sense
<hexagonwin[m]> but wait..!
<hexagonwin[m]> ls
<hexagonwin[m]> * 2.4ghz wifi mac address : 90:9f:33:be:41:20
<hexagonwin[m]> 5.4 : 90:9f:33:be:41:22
<hexagonwin[m]> Hmm
<Tusker> so maybe -n 16 to capture the rest of the mac
<hexagonwin[m]> 2.4 one is in 00000000
<hexagonwin[m]> Tusker: rest of the mac? Oh you mean rest of factory partition
<Tusker> no, in your matrix captures above, you had a truncated mac address...
<PaulFertser> hexagonwin[m]: factory partition is needed for per-board individual calibration data!
<hexagonwin[m]> Ohh, but what do you mean by truncated macaddress..? I thought it has the whole mac address line 1 except that there's two spaces
<Tusker> yes, nevermind... my suggestion of -n 8 was too small...
<hexagonwin[m]> Oh sorry if I was rude, I don't speak this language properly :(
<Tusker> no worries :) for example - https://matrix.org/_matrix/media/r0/download/matrix.org/tSplmqZKUumyyYiANYbnovOP/message.txt - shows only 90 9f 33 be, and misses 41 20
<hexagonwin[m]> Ah.. next time I'll use a pastebin
<hexagonwin[m]> matrix seems to be strange with irc, I guess I'll need to sign up oftc later
<Tusker> matrix is fine... my command I suggested you to use was incorrect
<hexagonwin[m]> oh
<hexagonwin[m]> so then this means that mac address and those location (?) isn't the error here..
<Tusker> the two locations look good to me, just confirm on your side that the label of each MAC matches what shows on each interface
<Tusker> ie, if you look at iw list, you can see phy0 showing 2G and phy1 showing 5G for example
<Tusker> and if the mac addresses for 5G matches the right physical interface etc
<hexagonwin[m]> the mac address i saw previousely on luci matches these
<hexagonwin[m]> i'll check iw now
<hexagonwin[m]> well I don't have mac address in output of iw list, the wifi need to be enabled to see those?
<hexagonwin[m]> I have wifi disabled right now for some test
<Tusker> i mean... i just wanted you to check that phy0 has the frequency you expect
<Tusker> iw dev wlan0 info will show you the mac
<hexagonwin[m]> phy 0 is 2.4g and phy1 is 5g
<hexagonwin[m]> but I don't know which is which because no mac address
<hexagonwin[m]> + wlan0 is 2.4 wlan1 is 5h
<hexagonwin[m]> * - wlan0 is 2.4 wlan1 is 5g
<hexagonwin[m]> is wlan number and phy number supposed to be the same?
<Tusker> they usually match up, iw dev wlan0 info will show you the phy that it is matched to
<hexagonwin[m]> iw dev wlan something gives strange output
<hexagonwin[m]> Oh
<hexagonwin[m]> yes it gives wiphy 0
<hexagonwin[m]> this is phy 0 same right?
<Tusker> yes
<Tusker> so, it seems as expected
<hexagonwin[m]> okay
<hexagonwin[m]> then yes as expectetd
<Tusker> maybe an issue with country or DFS etc
<Tusker> what happens if you put in the country code and change the channel to auto ?
<hexagonwin[m]> Well that's possible
<hexagonwin[m]> because I set my country code here
<hexagonwin[m]> wait! I'll try
<Tusker> perhaps try with US or KR or TW to see if that changes anything
<hexagonwin[m]> but it's actually dangerous for me to set to other country's settings
<hexagonwin[m]> since I pay a lot (...) of fine if it goes against law
<hexagonwin[m]> but where set channel?
<hexagonwin[m]> And coverage cell density is set to disabled, i guess this is default..
<hexagonwin[m]> oh sorry found it
<Tusker> country KR: DFS-JP
<hexagonwin[m]> setting channel auto doesn't help
<hexagonwin[m]> at least for 2.4g
<Tusker> iw reg get should show
<hexagonwin[m]> Yes
rmilecki has joined #openwrt-devel
<Tusker> i wonder if the factory firmware actually uses those settings... and I would not really be too worried about the law if you are just testing for a few minutes... I am sure you could explain it
<hexagonwin[m]> I tried TW Taiwan and it doesn't work still
<hexagonwin[m]> I can go to stock firmware if needed, and afaik they do have these settings
<hexagonwin[m]> and if language is set to korean and I maximize something and it's against law it warns about it
<PaulFertser> hexagonwin[m]: why are you sure phy0 should work in 2.4 GHz?
<hexagonwin[m]> what do you mean?
<PaulFertser> hexagonwin[m]: your DTS assignes whatever is on pcie0 to 2.4 GHz band. Why not 5 GHz?
<hexagonwin[m]> those commands that i tried earlier showed phy0 and wlan0 is same and that is 2.4g
<hexagonwin[m]> Oh wait really
<hexagonwin[m]> I'll check...
<hexagonwin[m]> In here?
<PaulFertser> hexagonwin[m]: no, in @pcie0 and @pcie1
<PaulFertser> hexagonwin[m]: have you pasted full dmesg with OpenWrt anywhere?
<hexagonwin[m]> PaulFertser: No, but I'll do if you need
<hexagonwin[m]> PaulFertser: There is no word @pci in my dts file
<PaulFertser> hexagonwin[m]: of course I do
<hexagonwin[m]> which line?
<PaulFertser> &pcie0
<hexagonwin[m]> ah
<hexagonwin[m]> Those seem to be just pasted from a8004t (which is what I based from) so I'll edit that
<hexagonwin[m]> And I'm rebooting router for logs now..
* Tusker is away --- back soon
<PaulFertser> hexagonwin[m]: it looks like you have mt7612 on pcie0 and mt7602 on pcie1. So I would expect mt7612 to be used for 5 GHz but you do it the opposite way!
<hexagonwin[m]> Ohhh
<hexagonwin[m]> that's very possible
<hexagonwin[m]> I'll try reversing
<hexagonwin[m]> after putting log
<PaulFertser> hexagonwin[m]: and after booting do "iw list" too.
jlsalvador has quit [Read error: Connection reset by peer]
jlsalvador has joined #openwrt-devel
<hexagonwin[m]> this is the uart log
<hexagonwin[m]> this is iw list
<hexagonwin[m]> I'll try reverse now
<hexagonwin[m]> [ Now I'm rebulding with pcie0 and 1 reversed ]
<hexagonwin[m]> hmm, but is openwrt based on alpine..?
<PaulFertser> hexagonwin[m]: it's not
<PaulFertser> Interesting, they both have 14c3:7662 ID.
<PaulFertser> hexagonwin[m]: you didn't paste hexdump -C for the whole factory partition did you?
aleksander has joined #openwrt-devel
Rentong has joined #openwrt-devel
jlsalvador has quit [Remote host closed the connection]
jlsalvador has joined #openwrt-devel
<owrt-snap-builds> Build [#229](https://buildbot.openwrt.org/master/images/#builders/49/builds/229) of `mvebu/cortexa53` failed.
Rentong has quit [Ping timeout: 480 seconds]
mva has quit [Quit: ZNC - https://znc.in]
mva has joined #openwrt-devel
<PaulFertser> hexagonwin[m]: any luck?
<Tusker> PaulFertser: FYI, I gave up for now for my gmac0 issue, just modified the uboot so that it does a ping on every boot...
<PaulFertser> Tusker: sometimes one just needs a break and be able to proceed with the other aspects of support.
<Tusker> exactly :) Was planning on using it to run frr (quagga), but maybe will use a different AP for that with 512MB RAM should be enough... 128MB might be a bit tight
<Tusker> saw a Cisco MR52 for AU$100 on ebay too... looks like clayface has it 99% supported already in the PR
<hexagonwin[m]> I reversed both, now wifi does work!!
<hexagonwin[m]> Now all except button and led working.
<PaulFertser> hexagonwin[m]: cool :)
<PaulFertser> hexagonwin[m]: I hope you're going to send the support upstream once you get it fully working?
<hexagonwin[m]> Thanks for helping me
<hexagonwin[m]> Yeah I'm going to
<hexagonwin[m]> The device's specs are fully capable of running OWRT and it's also working nicely right now, in terms of speed
<PaulFertser> hexagonwin[m]: you've read https://openwrt.org/docs/techref/hardware/port.gpio already haven't you?
<hexagonwin[m]> PaulFertser: Oh I didn't
<hexagonwin[m]> I'll read now
<hexagonwin[m]> https://github.com/iptime-gpl/userapps_a3004nd/blob/master/fs/mt7621/clones/a3004nd/si/hw This file says both 2g and 5g wifi led indicator is gpio -1, is this normal?
<hexagonwin[m]> Other iptime device's that file shows two dfferent value
<PaulFertser> hexagonwin[m]: and? Do you suspect you have no LEDs or that they're not controlled by GPIO?
<hexagonwin[m]> I do have two leds
<hexagonwin[m]> I mean that I was confused why two different leds had same gpio number
<hexagonwin[m]> and that number was minus one
<PaulFertser> hexagonwin[m]: I would assume that to mean no led can be controlled at all.
jlsalvador2 has joined #openwrt-devel
jlsalvador has quit [Read error: Connection reset by peer]
jlsalvador2 is now known as jlsalvador
<hexagonwin[m]> Hmm, alright
<hexagonwin[m]> so the lan port leds worked out of the box correctly when I had reversed lan port orders in dts so I guess that's an uncontrollable one
<hexagonwin[m]> and power led also works even when power off is done so I guess that also is
<hexagonwin[m]> but the cpu led and two wifi, and usb would need to be controllable I guess
<hexagonwin[m]> for usb there's a number so it's fine
<PaulFertser> hexagonwin[m]: so that wiki page has the scripts that should help you find the number.
<hexagonwin[m]> Yes
<hexagonwin[m]> I did the script
<hexagonwin[m]> it keep just gives
<hexagonwin[m]> 0 and 1
<hexagonwin[m]> In led there is something like label = "orange:cpu";
<hexagonwin[m]> what does the orange mean?
<hexagonwin[m]> For some other devices there is blue or green too..
<hexagonwin[m]> and in my device's dts all is set to orange but the real leds are blue onl
<hexagonwin[m]> * and in my device's dts all is set to orange but the real leds are blue only
<PaulFertser> hexagonwin[m]: probably you didn't read the page then :(
<hexagonwin[m]> I did..
jlsalvador2 has joined #openwrt-devel
jlsalvador has quit [Remote host closed the connection]
jlsalvador2 is now known as jlsalvador
dangole has quit [Remote host closed the connection]
Tapper has quit [Ping timeout: 480 seconds]
Rentong has joined #openwrt-devel
Rentong has quit [Ping timeout: 480 seconds]
plntyk has quit [Remote host closed the connection]
rejoicetreat has quit [Remote host closed the connection]
rejoicetreat has joined #openwrt-devel
jlsalvador has quit [Read error: Connection reset by peer]
jlsalvador has joined #openwrt-devel
plntyk has joined #openwrt-devel
valku has joined #openwrt-devel
Luke-Jr has quit [Ping timeout: 480 seconds]
Tusker has quit [Quit: Time wasted on IRC: 1 day 1 hour 38 minutes 47 seconds]
takimata has quit [Quit: wat?]
Luke-Jr has joined #openwrt-devel
takimata has joined #openwrt-devel
Rentong has joined #openwrt-devel
nitroshift has quit [Quit: Gone that way --->]
aleksander has quit [Quit: Leaving]
goliath has quit [Quit: SIGSEGV]
minimal has joined #openwrt-devel
Rentong has quit [Ping timeout: 480 seconds]
Rentong has joined #openwrt-devel
Rentong has quit [Remote host closed the connection]
Rentong has joined #openwrt-devel
Rentong has quit [Ping timeout: 480 seconds]
rejoicetreat has quit [Ping timeout: 480 seconds]
rejoicetreat has joined #openwrt-devel
Rentong has joined #openwrt-devel
Rentong has quit [Remote host closed the connection]
danitool has quit [Quit: Cubum autem in duos cubos, aut quadratoquadratum in duos quadratoquadratos]
Rentong has joined #openwrt-devel
KGB-0 has quit [Quit: KGB-0]
Rentong has quit [Ping timeout: 480 seconds]
KGB-0 has joined #openwrt-devel
Rentong has joined #openwrt-devel
rejoicetreat has quit [Ping timeout: 480 seconds]
Rentong has quit [Ping timeout: 480 seconds]
Tapper has joined #openwrt-devel
goliath has joined #openwrt-devel
dedeckeh has quit [Remote host closed the connection]
Borromini has joined #openwrt-devel
Rentong has joined #openwrt-devel
danitool has joined #openwrt-devel
Tapper has quit [Ping timeout: 480 seconds]
Rentong has quit [Ping timeout: 480 seconds]
shibboleth has joined #openwrt-devel
Tapper has joined #openwrt-devel
<Borromini> stintel: ping
zhoreeq has joined #openwrt-devel
<zhoreeq> Hello, can anyone help to get this PR merged? https://github.com/openwrt/luci/pull/5193
shibboleth has quit [Quit: shibboleth]
clayface_ has joined #openwrt-devel
<aparcar[m]> jow: does the luci request.get() function support .catch?
clayface has quit [Ping timeout: 480 seconds]
Borromini has quit [Quit: leaving]
Tapper has quit [Read error: Connection reset by peer]
Tapper has joined #openwrt-devel
<enyc> rmilecki: thankyou =)
<enyc> rmilecki: can you do #openwrt too?
<aparcar[m]> jow: nevermind, it's a bug in the docs https://github.com/openwrt/luci/pull/5239
noahm has quit [Quit: reboot]
noahm has joined #openwrt-devel
Rentong has joined #openwrt-devel
Rentong has quit [Ping timeout: 480 seconds]
Weasel___ has quit [Ping timeout: 480 seconds]
rejoicetreat has joined #openwrt-devel
KGB-0 has quit [Quit: KGB-0]
Tapper has quit [Ping timeout: 480 seconds]
<rmilecki> thanks enyc
KGB-0 has joined #openwrt-devel
Tapper has joined #openwrt-devel
<enyc> rmilecki: =) downloads.openwrt.org still shows -rc3 ... but there we go, I guess it will just be 21.02 quite soon
KGB-0 has quit [Read error: Connection reset by peer]
KGB-0 has joined #openwrt-devel
Tapper has quit [Ping timeout: 480 seconds]
rejoicetreat has quit [Ping timeout: 480 seconds]
goliath has quit [Quit: SIGSEGV]
<owrt-snap-builds> Build [#228](https://buildbot.openwrt.org/master/images/#builders/31/builds/228) of `layerscape/armv8_64b` completed successfully.
jlsalvador has quit [Read error: No route to host]
jlsalvador has joined #openwrt-devel
Tusker has joined #openwrt-devel
jlsalvador has quit [Remote host closed the connection]
jlsalvador has joined #openwrt-devel
<Tusker> zhoreeq: do you use yggdrasil for any use case ?
<zhoreeq> Tusker: yes, a lot of use cases
<Tusker> could you enlighten me? it seems an interesting project, but wondering what you actually use it for
<zhoreeq> I mostly use it as a free zeroconf VPN
<Tusker> yeah, that could be useful
<Tusker> what is the memory usage like on openwrt ?
<zhoreeq> Tusker: not sure, around 10MB
<Tusker> that's pretty reasonable, how does it handle different bandwidth requirements ? ie, if you are a node, do you get lots of other traffic coming through you ?
jlsalvador2 has joined #openwrt-devel
jlsalvador has quit [Read error: Connection reset by peer]
jlsalvador2 is now known as jlsalvador
<zhoreeq> Tusker: I don't think so, but you better ask public peer operators at #yggdrasil (that channel is at libera.chat now iirc)
<Tusker> ah ok, will investigate more, thanks!
<zhoreeq> np :^)
<blocktrron_> fda: see my staging tree for a fix
<fda> blocktrron_: here https://github.com/blocktrron/openwrt ?
Tapper has joined #openwrt-devel
bluew has quit [Remote host closed the connection]
bluew has joined #openwrt-devel
zhoreeq has quit [Remote host closed the connection]
zhoreeq has joined #openwrt-devel
jlsalvador has quit [Remote host closed the connection]
jlsalvador has joined #openwrt-devel
Tapper has quit [Ping timeout: 480 seconds]
<blocktrron_> fda: https://git.openwrt.org/?p=openwrt/staging/blocktrron.git;a=summary
<owrt-snap-builds> Build [#230](https://buildbot.openwrt.org/master/images/#builders/49/builds/230) of `mvebu/cortexa53` completed successfully.
Tapper has joined #openwrt-devel
danitool has quit [Quit: Cubum autem in duos cubos, aut quadratoquadratum in duos quadratoquadratos]