junland has quit [Quit: %ZNC Disconnected%]
junland has joined #openwrt-devel
<mangix> cool, kmods are broken on the buildbots
victhor has joined #openwrt-devel
dangole has quit [Ping timeout: 240 seconds]
gch98121396932 has joined #openwrt-devel
gch9812139693 has quit [Ping timeout: 240 seconds]
gch98121396932 is now known as gch9812139693
gch9812139693 has quit [Read error: Connection reset by peer]
gch9812139693 has joined #openwrt-devel
<voltagex> is there a way to compile kernel modules with NLS but not the rest of the system? Enabling NLS is breaking the compilation of gammu
<voltagex> nevermind, got it - you don't need NLS globally for NLS in the kernel it seems
<pkgadd> I assume taking out https://github.com/openwrt/packages/blob/master/utils/gammu/Makefile#L27 would already do (untested)
<pkgadd> at worst you add some cmake config options
<voltagex> not sure, and I can't get builds of single packages working to test.
<voltagex> shouldn't that like mean that building with nls works?
<Grommish> ./staging_dir/hostpkg/bin is in the build path, correct?
samantaz_ has quit [Ping timeout: 268 seconds]
hbug___ has joined #openwrt-devel
hbug__ has quit [Ping timeout: 240 seconds]
rsalvaterra has quit [Quit: Leaving.]
tobleminer-tSYS has quit [Quit: AS4242423214]
tobleminer-tSYS has joined #openwrt-devel
<Grommish> Interesting... the build system uses $(TMP_DIR)/$(TMPDIR) as $(TOP_DIR)/tmp.. Why is it writing to tmp to disk? Is there any reason I shoudln't just symlink ./tmp to /tmp?
<Grommish> I am cringing at all the cycles this ssd has gone thru with tmp being io'd like that
<Grommish> at least it's using the system ram now.. wonder if it's faster in the build though
victhor has quit [Ping timeout: 240 seconds]
Grommish has quit [Read error: Connection reset by peer]
Grommish has joined #openwrt-devel
Grommish has quit [Client Quit]
Grommish has joined #openwrt-devel
goliath has quit [Quit: SIGSEGV]
Grommish has quit [Read error: Connection reset by peer]
Grommish has joined #openwrt-devel
gch98121396932 has joined #openwrt-devel
gch9812139693 has quit [Read error: Connection reset by peer]
gch98121396932 is now known as gch9812139693
danitool has quit [Ping timeout: 264 seconds]
hgl_ has quit [Quit: Bye]
hgl has joined #openwrt-devel
hgl has quit [Changing host]
hgl has joined #openwrt-devel
_whitelogger has joined #openwrt-devel
lmore377 has quit [Quit: https://quassel-irc.org - Chat comfortably. Anywhere.]
lmore377 has joined #openwrt-devel
SmugLeaf is now known as Guest53204
Weedy has joined #openwrt-devel
Guest53204 has quit [Ping timeout: 264 seconds]
lmore377 has quit [Ping timeout: 256 seconds]
lmore377 has joined #openwrt-devel
_whitelogger has joined #openwrt-devel
lmore377_ has joined #openwrt-devel
lmore377 has quit [Ping timeout: 256 seconds]
lmore377_ has quit [Read error: Connection reset by peer]
lmore377 has joined #openwrt-devel
lmore377 has quit [Ping timeout: 256 seconds]
lmore377 has joined #openwrt-devel
lmore377 has quit [Read error: Connection reset by peer]
lmore377 has joined #openwrt-devel
lmore377 has quit [Read error: Connection reset by peer]
gch98121396937 has joined #openwrt-devel
gch9812139693 has quit [Ping timeout: 240 seconds]
gch98121396937 is now known as gch9812139693
lmore377 has joined #openwrt-devel
lmore377_ has joined #openwrt-devel
lmore377 has quit [Ping timeout: 260 seconds]
lmore377 has joined #openwrt-devel
lmore377_ has quit [Read error: Connection reset by peer]
lmore377 has quit [Read error: Connection reset by peer]
Darkmatter66 has joined #openwrt-devel
lmore377 has joined #openwrt-devel
_whitelogger has joined #openwrt-devel
danitool has joined #openwrt-devel
feriman has joined #openwrt-devel
dedeckeh has joined #openwrt-devel
gch9812139693 has quit [Ping timeout: 240 seconds]
gch9812139693 has joined #openwrt-devel
Borromini has joined #openwrt-devel
ivanich has joined #openwrt-devel
Darkmatter66 has quit [Quit: ZNC 1.7.5 - https://znc.in]
Darkmatter66 has joined #openwrt-devel
danitool has quit [Quit: Cubum autem in duos cubos, aut quadratoquadratum in duos quadratoquadratos]
danitool has joined #openwrt-devel
rsalvaterra has joined #openwrt-devel
Borromini has quit [Ping timeout: 240 seconds]
Ycarus has joined #openwrt-devel
ivanich has quit [Quit: Konversation terminated!]
Floppe has quit [Ping timeout: 246 seconds]
Floppe has joined #openwrt-devel
gch9812139693 is now known as gch981213
dangole has joined #openwrt-devel
ivanich has joined #openwrt-devel
<rsalvaterra> dangole: I'm going to break zram. :P
Tapper has joined #openwrt-devel
noltari has quit [Quit: Bye ~ Happy Hacking!]
noltari has joined #openwrt-devel
Nick_Lowe has joined #openwrt-devel
feriman has quit [Quit: WeeChat 3.0]
Darkmatter66_ has joined #openwrt-devel
Darkmatter66 has quit [Ping timeout: 260 seconds]
jlanda has quit [Quit: jlanda]
jlanda has joined #openwrt-devel
Nick_Lowe has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
Nick_Lowe has joined #openwrt-devel
black_ant has joined #openwrt-devel
black_ant has joined #openwrt-devel
black_ant has quit [Changing host]
Darkmatter66_ has quit [Quit: ZNC 1.7.5 - https://znc.in]
dangole has quit [Remote host closed the connection]
mwarning has joined #openwrt-devel
Darkmatter66 has joined #openwrt-devel
victhor has joined #openwrt-devel
ReDaLeRt has joined #openwrt-devel
<ReDaLeRt> Hello.
<ReDaLeRt> I'm using a Ea7500 v1 with these settings:
<ReDaLeRt> But I can't get the TX rate above 400 Mbps. Just the RX is 866Mbps.
<ReDaLeRt> I'm close to the router and the 5GHz band channel selected is empty (apart from my one router)
<ReDaLeRt> On the status page, the client get its TX is limited to 40 MHz, but the RX gets 80 MHz.
<PaulFertser> ReDaLeRt: the rate control algorithms are monitoring the results all the time and choose the best possible option. I suggest you to check the link with "iw dev wlan0 station dump" at the moment when the link is fully loaded (that is, when you're running the speed test in the direction you want).
<PaulFertser> ReDaLeRt: that would show you what specific MCS and other link parameters are used.
black_an- has joined #openwrt-devel
black_ant has quit [Ping timeout: 272 seconds]
ReDaLeRt has quit [Ping timeout: 245 seconds]
ReDaLeRt95 has joined #openwrt-devel
<ReDaLeRt95> well, everytime the router reboots, I get a mad TX rate of 24mbps:
feriman has joined #openwrt-devel
<ReDaLeRt95> Just after many hours the TX rate "corrects" to 400 mbps under load.
<ReDaLeRt95> I'm now getting:
<ReDaLeRt95> 866.7 Mbit/s, 80 MHz, VHT-MCS 9, VHT-NSS 2, Short GI24.0 Mbit/s, 20 MHz
<PaulFertser> ReDaLeRt95: but not before? So if you push some load through it, it still stays at 24 Mb/s, do I get it right?
<ReDaLeRt95> yes, it stays at 24mbps under logs.
<ReDaLeRt95> *under load
<PaulFertser> And takes hours to change? Now that's odd.
<PaulFertser> Is that the Tx rate on the router itself?
<ReDaLeRt95> Yup.
<ReDaLeRt95> yes, on the status page
<PaulFertser> For the reference, MCS explained https://en.wikipedia.org/wiki/802.11ac#Data_rates_and_speed
<PaulFertser> So MCS 9 is the maximum, and apparently your client chooses it.
<ReDaLeRt95> this is weird:
<ReDaLeRt95> tx bitrate: 24.0 MBit/s tx duration: 87357367 us rx bitrate: 866.7 MBit/s VHT-MCS 9 80MHz short GI VHT-NSS 2 rx duration: 0 us
<ReDaLeRt95> why the tx duration is that higher?
<PaulFertser> ath10k is not known to misbehave like that, this disbalance is rather odd.
<rsalvaterra> PaulFertser: I have the vague idea that ath10k hardware doesn't report the TX rate.
dangole has joined #openwrt-devel
<PaulFertser> rsalvaterra: but then it wouldn't correlate to real throughput values.
<rsalvaterra> PaulFertser: True, that.
<PaulFertser> ReDaLeRt95: do I get it right that throughput testing confirms those rates?
<ReDaLeRt95> yes, both speedtest.net and iperf3
<PaulFertser> ReDaLeRt95: is that the same with different clients or do you have just one 802.11ac to test with?
<ReDaLeRt95> with an intel 8265 and a samsung J7
<ReDaLeRt95> if I load it with 64 iperf3 streams, I get the 400 mbps 40 MHz full bandwith, at the same time...
linzst has joined #openwrt-devel
<rsalvaterra> ReDaLeRt95: Which firmware are you using?
<ReDaLeRt95> yesterday snapshot
<rsalvaterra> No, I mean which ath10k firmware variant.
<ReDaLeRt95> SNAPSHOT, r14935-95b0751d0f
<ReDaLeRt95> 8064
<rsalvaterra> ReDaLeRt95: opkg list-installed grep ath10k
<rsalvaterra> | grep
<ReDaLeRt95> ath10k-firmware-qca99x0-ct - 2020-07-02-1kmod-ath10k-ct - 5.4.75+2020-06-30-edfbf916-1
<ReDaLeRt95> ath10k-firmware-qca99x0-ct - 2020-07-02-1kmod-ath10k-ct - 5.4.75+2020-06-30-edfbf916-1
<ReDaLeRt95> (sorry)
<rsalvaterra> Hm. You're also using the ath10k-ct driver, correct?
<ReDaLeRt95> kmod-ath10k-ct - 5.4.75+2020-06-30-edfbf916-1
<ReDaLeRt95> It seems to.
<rsalvaterra> Ok. The first thing I'd try would be to use the -htt variant.
<ReDaLeRt95> ath10k-firmware-qca99x0-ct-full-htt
<ReDaLeRt95> or
<ReDaLeRt95> ath10k-firmware-qca99x0-ct-htt
<ReDaLeRt95> ?
<rsalvaterra> ath10k-firmware-qca99x0-ct-htt
<ReDaLeRt95> Do i need to remove the ct only version after installing the ct-htt?
<rsalvaterra> ReDaLeRt95: I'd advise you to build an image with the image builder. I personally haven't used opkg in years, so I don't remember the restrictions.
<ReDaLeRt95> do you mean compiling the openwrt source code and using the menuconfig to replace those packadges?
<PaulFertser> Probably they conflict already so opkg will remove the other version automatically.
ReDaLeRt has joined #openwrt-devel
<ReDaLeRt> OK. (changed to another PC :))
<rsalvaterra> ReDaLeRt: You could build from scratch, yes. But the image builder is a great compromise for most people. https://openwrt.org/docs/guide-user/additional-software/imagebuilder
<rsalvaterra> ReDaLeRt: And you're Portuguese too, I see. ;)
<ReDaLeRt> Sim. :P
<rsalvaterra> Keep it English here, though. :)
<ReDaLeRt> the pain is that taking almost an hour, even with parallel compiling.
<rsalvaterra> ReDaLeRt: Don't complain. A full build from scratch takes about 4 hours on my system (but I'm crazy enough to use computers until they break, so I'm using a system from 2006).
<PaulFertser> Firmware can be installed even manually, that's all just files in /lib/firmware
<PaulFertser> rsalvaterra: don't you fix them after they break and continue using? ;)
<rsalvaterra> PaulFertser: Bah… :P
<PaulFertser> rsalvaterra: my laptop has literally welded plastic and long screws holding it together
<rsalvaterra> PaulFertser: I'm not punishing laptops with OpenWrt builds… That's a workstation job. ;)
<DonkeyHotei> i build on my laptop with 8 gigs ram
<PaulFertser> 3d printing filament plus SMD soldering hot air gun can do wonders (after few hours of training to weld that way)
<rsalvaterra> PaulFertser: I don't have the equipment for that… yet…
<rsalvaterra> DonkeyHotei: my build machine has 4 GiB of RAM, of which 3.2 are actually available. :)
<PaulFertser> rsalvaterra: I have some cheap luckey soldering/rework station for years, it's OK. Got ts100 soldering iron recently and that's much better though.
<dangole> ReDaLeRt: just use the ImageBuilder, that should take a few second and doesn't involve any compiling
<ReDaLeRt> My PC is not that newer, is from 2011, but with an intel 2500k overlocked to 4.3 GHz, and 16 Gb of RAM.
<dangole> ReDaLeRt: i think you are building from source, as you have mentioned menuconfig before. ImageBuilder doesn't have menuconfig
<ReDaLeRt> yup, compiling it from the github source code.
<dangole> ReDaLeRt: my host similar, i5 M560 made in 2011, 8GB of RAM
<rsalvaterra> PaulFertser: I'll get there, eventually… but what I need first is a flash reader/programmer and a SOP8 clip. I still hope I can teach my TL-SG2008 v1 a few new tricks (and replace that awful VxWorks with OpenWrt)…
<dangole> ReDaLeRt: just download ImageBuilder for your target and that can assemble an image (ie. kernel+squashfs) within seconds with exactly the packages you like
<rsalvaterra> ReDaLeRt: If you're compiling from the source, you just have to select the desired firmware variant in the Firmware menu.
<PaulFertser> rsalvaterra: I use my TUMPA (full) for flash programming, it's much better in all regards (and can do much more too) than all those ch341 boards.
<ReDaLeRt> rsalvaterra, I did just that.
<dangole> ReDaLeRt, rsalvaterra: but compiling from source takes a long time and much more error-prone than using ImageBuilder. As you have suggested before as well, ImageBuilder should be the way to go in such case.
<rsalvaterra> PaulFertser: I've seen some cheap TL866 II Plus programmers on AliExpress… any opinions?
Nick_Lowe has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
<rsalvaterra> dangole: I fully agree, if ReDaLeRt doesn't have a lot of experience building from source.
<PaulFertser> rsalvaterra: not support by flashrom afaik?
<PaulFertser> rsalvaterra: not supported -> crap.
<rsalvaterra> PaulFertser: True. I'd need (ARGHHH!) Windows.
<PaulFertser> rsalvaterra: ft2232h-based devices just work
<dangole> rsalvaterra: what he wants is to swap on package from default build against something else. no changes to any sources made. hence just waste of time and kWh to compile from source.
Nick_Lowe has joined #openwrt-devel
<rsalvaterra> dangole: Yeah, the image builder is the way to go, definitely.
<PaulFertser> dangole: and the fastest way would be to just opkg install it
<ReDaLeRt> I'm not used to use the imagebuilder. I felt quite lost following its usage instructions... -.-'
<PaulFertser> Or even manually copy to /lib/firmware
<zorun> ReDaLeRt: download, untar, "make help"
<ReDaLeRt95> # opkg install ath10k-firmware-qca99x0-ct-httInstalling ath10k-firmware-qca99x0-ct-htt (2020-07-02-1) to root...Downloading https://downloads.openwrt.org/snapshots/packages/arm_cortex-a15_neon-vfpv4/base/ath10k-firmware-qca99x0-ct-htt_2020-07-02-1_arm_cortex-a15_neon-vfpv4.ipkCollected errors: * check_data_file_clashes: Package
<ReDaLeRt95> ath10k-firmware-qca99x0-ct-htt wants to install file /lib/firmware/ath10k/QCA99X0/hw2.0/board-2.bin But that file is already provided by package * ath10k-firmware-qca99x0-ct * check_data_file_clashes: Package ath10k-firmware-qca99x0-ct-htt wants to install file /lib/firmware/ath10k/QCA99X0/hw2.0/board.bin But that file is already
<ReDaLeRt95> provided by package * ath10k-firmware-qca99x0-ct * opkg_install_cmd: Cannot install package ath10k-firmware-qca99x0-ct-htt.
<PaulFertser> ReDaLeRt95: opkg remove the other first
<ReDaLeRt> removed it and rebooted the router. Let's see.
<PaulFertser> ReDaLeRt95: after installing the -htt one I hope? :)
<rsalvaterra> dangole: Something completely different, have you tried any mklibs builds lately (after your update)? I tried one a couple of days ago and haven't noticed any size difference whatsoever.
<ReDaLeRt> (rebooted with the newer installed)
<rsalvaterra> (I remember mklibs made quite a difference in 19.07.)
<ReDaLeRt> well, I get the same result.
<dangole> rsalvaterra: haven't tried mklibs in a long while. is there newer upstream available by now with upstream Python 3 support?
<ReDaLeRt> :(
ReDaLeRt95 has quit [Ping timeout: 245 seconds]
<rsalvaterra> dangole: Not really, I'm using our heavily patched version. :/
ReDaLeRt96 has joined #openwrt-devel
<ReDaLeRt96> 866.7 Mbit/s, 80 MHz, VHT-MCS 9, VHT-NSS 2, Short GI24.0 Mbit/s, 20 MHz
<ReDaLeRt96> -.-'
gch9812139 has joined #openwrt-devel
<PaulFertser> In other words, the client does the right thing and chooses maximum, but the AP for whatever reason is stuck with something really weird and slow?
<ReDaLeRt> Correct.
gch981213 has quit [Read error: Connection reset by peer]
gch9812139 is now known as gch981213
<PaulFertser> ReDaLeRt: you can try non-ct firmware then
<rsalvaterra> ReDaLeRt96: Well… ath10k is not exactly the greatest hardware (from first-hand experience, I have both QCA9880 wave 1 and QCA9886 wave 2).
<ReDaLeRt96> the intel one:
<ReDaLeRt96> 866.7 Mbit/s, 80 MHz, VHT-MCS 9, VHT-NSS 2, Short GI24.0 Mbit/s, 20 MHz
<ReDaLeRt96> the samsung:
<ReDaLeRt96> 433.3 Mbit/s, 80 MHz, VHT-MCS 9, VHT-NSS 1, Short GI200.0 Mbit/s, 40 MHz, VHT-MCS 9, VHT-NSS 1, Short GI
<ReDaLeRt96> -.-'
<ReDaLeRt96> both underload at the same time.
<PaulFertser> ReDaLeRt: https://github.com/greearb/ath10k-ct/issues/139 might be related etc. Try non-ct firmware.
<rsalvaterra> ReDaLeRt96: Beware: with non-ct firmware you may have issues with WPA3 (with QCA9880, WPA3 is only stable with -ct firmware).
<PaulFertser> Why stupid android devices do not support wpa3?
<rsalvaterra> PaulFertser: Because stupid Google is stupid. Surprisingly, it does support OWE (Android 10+).
<dangole> PaulFertser: because they are stuck on Google-patched wpa_supplicant from 10 years ago...?
<rsalvaterra> dangole: Yeah, that too. :P
<PaulFertser> Too bad so many people insist on using android.
<rsalvaterra> And also using wpa_supplicant for hostap, which is borderline nuts.
<rsalvaterra> PaulFertser: What's the alternative? Smoke signals?
<PaulFertser> rsalvaterra: dumb featurephone + netbook or something similar that runs proper OS.
<rsalvaterra> PaulFertser: I have an Eee PC 901… :P
Borromini has joined #openwrt-devel
ReDaLeRt96 has quit [Ping timeout: 245 seconds]
<rsalvaterra> PaulFertser: Unfortunately, I do like Android's convenience. I use LineageOS, though. OEM Android is a cancer.
Nick_Lowe has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
<ReDaLeRt> Now, it reports TX @ 6mbps for both clients, but I get the 400mbps upstream performance from the router.
<rsalvaterra> ReDaLeRt: Yeah, that's what I said about not reporting the TX rate.
<rsalvaterra> It's always stuck at 6 Mb/s.
Nick_Lowe has joined #openwrt-devel
<ReDaLeRt> but, still, caps at 40 MHz bandwidth...
<ReDaLeRt> on TX
Borromini has quit [Quit: Lost terminal]
linzst has quit [Ping timeout: 264 seconds]
<ReDaLeRt> Any guesses? :S
ReDaLeRt has left #openwrt-devel [#openwrt-devel]
ReDaLeRt has joined #openwrt-devel
<rsalvaterra> ReDaLeRt: At this point, not really, no… :/
samantaz_ has joined #openwrt-devel
<ReDaLeRt> There is no way to create a package with the newest CT driver?
<PaulFertser> ReDaLeRt: just download and overwrite the existing files
<ReDaLeRt> I don't even see any driver there for the QCA9990
<ReDaLeRt> :S
<ReDaLeRt> well, why openwrt reports QCA9990 when this router has Atheros QCA9983 and Atheros QCA9982?
<PaulFertser> Reports where?
<ReDaLeRt> on the wireless configuration page
<rsalvaterra> There's still this pending series from stintel… https://patchwork.ozlabs.org/project/openwrt/list/?series=199172
<PaulFertser> I'd trust dmesg and PCI IDs.
<jow> LuCI, which draws the info from libiwinfo
<PaulFertser> iwinfo has its own list of PCI IDs with names.
<jow> which uses https://git.openwrt.org/?p=project/iwinfo.git;a=blob;f=hardware.txt
Nick_Lowe has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
OutBackDingo has quit [Ping timeout: 246 seconds]
<svanheule[m]> ReDaLeRt: the QCA9982 has the exact same PCI vendor, product and subsystem IDs as the QCA9990. The only way to see the difference is by checking the number of available antennas.
Nick_Lowe has joined #openwrt-devel
ghjk has joined #openwrt-devel
eduardas has joined #openwrt-devel
ReDaLeRt has quit [Remote host closed the connection]
Darkmatter66 has quit [Quit: ZNC 1.7.5 - https://znc.in]
ReDaLeRt has joined #openwrt-devel
black_an- has quit [Ping timeout: 260 seconds]
ReDaLeRt has quit [Remote host closed the connection]
Net147 has quit [Ping timeout: 260 seconds]
Net147 has joined #openwrt-devel
linzst has joined #openwrt-devel
adrianschmutzler has joined #openwrt-devel
<nick[m]> nbd blogic I saw u published usteer. could we maybe work together. I did this dawn stuff. I don't see any reason maintaining two projects that have the same goal.
Misanthropos has quit [Ping timeout: 260 seconds]
linzst has quit [Quit: Leaving]
Nick_Lowe has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
Misanthropos has joined #openwrt-devel
goliath has joined #openwrt-devel
Nick_Lowe has joined #openwrt-devel
linzst has joined #openwrt-devel
linzst has quit [Quit: Leaving]
adrianschmutzler has quit [Quit: ~ Trillian - www.trillian.im ~]
Net147 has quit [Ping timeout: 272 seconds]
Nick_Lowe has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
ReDaLeRt has joined #openwrt-devel
Nick_Lowe has joined #openwrt-devel
Net147 has joined #openwrt-devel
dopje_ has joined #openwrt-devel
dopje has quit [Ping timeout: 265 seconds]
black_ant has joined #openwrt-devel
black_ant has quit [Changing host]
black_ant has joined #openwrt-devel
linzst has joined #openwrt-devel
ghjk has quit [Remote host closed the connection]
linzst has quit [Client Quit]
dangole has quit [Quit: Leaving]
ReDaLeRt has quit [Remote host closed the connection]
Borromini has joined #openwrt-devel
mwarning has quit [Ping timeout: 272 seconds]
valku has joined #openwrt-devel
Darkmatter66 has joined #openwrt-devel
<jow> nbd: your recent buildroot symvers handling changes appear to break compilation of out-of-tree kmods
N4gi0s has joined #openwrt-devel
N4gi0s has quit [Client Quit]
victhor has quit [Ping timeout: 246 seconds]
black_ant has quit [Quit: simplicity does not kill]
victhor has joined #openwrt-devel
<nbd> jow: ah, it's probably just an mkdir call missing in the sdk
<nbd> will fix it, sorry about the mess
Nick_Lowe has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
<jow> np
<eduardas> hello, this might sound like a stupid question, but does it ever make sense to have more than one watchdog timer enabled on an embedded Linux system?
<eduardas> i.e. if I'm using an external watchdog IC, does it still make sense to use the one on the SoC?
gch981213 has quit [Quit: The Lounge - https://thelounge.chat]
gch981213 has joined #openwrt-devel
Nick_Lowe has joined #openwrt-devel
Nick_Lowe has quit [Client Quit]
Olipro has quit [Read error: Connection reset by peer]
Nick_Lowe has joined #openwrt-devel
Olipro has joined #openwrt-devel
Olipro has joined #openwrt-devel
Olipro has quit [Changing host]
hsp has quit [Quit: WeeChat 3.0]
hsp has joined #openwrt-devel
mwarning has joined #openwrt-devel
<swalker> updated openwrt/upstream, https://sdwalker.github.io/uscan/index.html
<jow> eduardas: interesting question
<jow> eduardas: considering the /dev/watchdog api, I can't even imagine how multiple WDs would work with it
gch9812133 has joined #openwrt-devel
gch981213 has quit [Read error: Connection reset by peer]
gch9812133 is now known as gch981213
<karlp> well, you can have a watchdog that attempts to do a "lighter" or faster action?
<eduardas> jow: why not? separate device files get created for different WDTs so the separation is pretty clear when it comes to userspace
<karlp> ie, try and do something stmarter than the OOMkiller for isntance,
<karlp> perhaps try more graceful shutdowns
<eduardas> jow: unless there is some limitation at the kernel level I am not aware of
<karlp> the watchdog governor framework might be interesting too, you cna get "pre-timeout" actions?
mwarning has quit [Ping timeout: 260 seconds]
<eduardas> karlp: thanks for pointing that out...was not even aware pretimeout actions were a thing
<jow> eduardas: yes, you're right. I misremembered
dangole has joined #openwrt-devel
<xdarklight> Hauke: if you have any idea on what might cause this then please let me know: https://github.com/openwrt/openwrt/pull/3085#issuecomment-727281848
<xdarklight> (internal GPHY with FE firmware)
mwarning has joined #openwrt-devel
gch981213 has quit [Read error: Connection reset by peer]
gch981213 has joined #openwrt-devel
Nick_Lowe has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
mwarning has quit [Ping timeout: 260 seconds]
Nick_Lowe has joined #openwrt-devel
Nick_Lowe has quit [Client Quit]
<rsalvaterra> dedeckeh: Thanks for letting me know the pain of rebasing patches. :P
Nick_Lowe has joined #openwrt-devel
<rsalvaterra> Seemed like a trivial conflict, just keep my changes and continue… and quilt just says "f**k you, I'm not applying this". :P
<Hauke> xdarklight: not really, this is probably signaled by the PHY
<xdarklight> Hauke: yep, that's why I'm surprised about it. the GPHY firmware is the same, the PHY driver is the same so I don't see any reason why it would be different with the DSA driver
<Hauke> me too
<Hauke> it could be that the swconfig driver did not handle the phy event
<xdarklight> I'll see if I can find my O2 6431 somewhere which uses 4x internal GPHY with FE firmware to see if I can somehow reproduce it
matteosilex has quit [Ping timeout: 260 seconds]
m4t has quit [Ping timeout: 260 seconds]
Dave has quit [Remote host closed the connection]
Dave has joined #openwrt-devel
matteosilex has joined #openwrt-devel
m4t has joined #openwrt-devel
gch9812135 has joined #openwrt-devel
gch981213 has quit [Read error: Connection reset by peer]
gch9812135 is now known as gch981213
mwarning has joined #openwrt-devel
gch981213 has quit [Read error: Connection reset by peer]
gch981213 has joined #openwrt-devel
mwarning has quit [Ping timeout: 260 seconds]
<rsalvaterra> I rebased and resent my dropbear series. Would someone please take a look?
mwarning has joined #openwrt-devel
mwarning has quit [Ping timeout: 260 seconds]
<dangole> ping grift
valku has quit [Remote host closed the connection]
valku has joined #openwrt-devel
<dangole> ping olmari
<olmari> lul... err... pong... haven't done anything yet, exept taken sauna ;P
<dangole> olmari: wow, sauna... i miss that... had access to a nice sauna back in Leipzig on one of the trailerparks...
<dangole> olmari: also spend some time trying to get OpenWrt PPC (mpc8540) to boot in QEMU, no luck yet, no serial output what-so-ever, probably i have to append DTS which matches the machine QEMU emulates...
<dangole> olmari: so if you can still try installing current master with procd-ujail on wdr4900 that'd be great help
<olmari> dangole: yeah... intentions still exists
mwarning has joined #openwrt-devel
valku has quit [Quit: valku]
gch9812139 has joined #openwrt-devel
gch981213 has quit [Read error: Connection reset by peer]
gch9812139 is now known as gch981213
Ycarus has quit [Quit: Ycarus]
mwarning has quit [Ping timeout: 260 seconds]
Darkmatter66 has quit [Quit: ZNC 1.7.5 - https://znc.in]
Nick_Lowe has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
Borromini has quit [Quit: Lost terminal]
mwarning has joined #openwrt-devel
junland has quit [Quit: %ZNC Disconnected%]
junland has joined #openwrt-devel
mwarning has quit [Ping timeout: 260 seconds]
opal has quit [Remote host closed the connection]
opal has joined #openwrt-devel
<karlp> eduardas: last I checked, of the common owrt targetrs, ath79 wdt (at least) didn't have support for any of the governor hooks, so ymmv
dedeckeh has quit [Remote host closed the connection]
muhaha has joined #openwrt-devel
gch981213 has quit [Read error: Connection reset by peer]
gch981213 has joined #openwrt-devel
myownnick has joined #openwrt-devel
muhaha has quit [Quit: Connection closed]
gch9812131 has joined #openwrt-devel
gch981213 has quit [Read error: Connection reset by peer]
gch9812131 is now known as gch981213
feriman has quit [Ping timeout: 256 seconds]
ivanich has quit [Quit: Konversation terminated!]
eduardas has quit [Quit: Konversation terminated!]
fork_ has joined #openwrt-devel
fork has quit [Ping timeout: 256 seconds]
Nick_Lowe has joined #openwrt-devel
Nick_Lowe has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
Nick_Lowe has joined #openwrt-devel
myownnick has quit [Remote host closed the connection]
rsalvaterra1 has joined #openwrt-devel
rsalvaterra1 has quit [Client Quit]
rsalvaterra has quit [Ping timeout: 264 seconds]