<FirstTime_NoTime>
Using the latest master and configuring it for a new rt7620 device. I would like the rt2x00 driver to stop registering LEDs as they are not physically connected on this board (i.e. remove rt2800soc-phy1::assoc from /sys/class/leds) (same for mt76-phy0) . How can I do that?
Grommish has quit [Remote host closed the connection]
csrf has joined #openwrt-devel
nmrh has joined #openwrt-devel
samantaz__ has quit [Quit: Bye]
<mangix>
rsalvaterra: GCC 10 has better support for C++20, which is nice.
swalker has quit [Remote host closed the connection]
Risk64 has quit [Quit: Risk64]
victhor has quit [Ping timeout: 265 seconds]
hbug_ has joined #openwrt-devel
hbug has quit [Ping timeout: 240 seconds]
<rr123>
downloads.openwrt.org is down
<rr123>
it's said gcc10 finally caught up llvm/clang and got ahead a bit, before gcc10 it's kind of behind
danitool has quit [Quit: Cubum autem in duos cubos, aut quadratoquadratum in duos quadratoquadratos]
swalker has joined #openwrt-devel
ivanich has quit [Read error: Connection reset by peer]
tobleminer-tSYS has quit [Quit: AS4242423214]
tobleminer-tSYS has joined #openwrt-devel
nmrh has quit [Ping timeout: 264 seconds]
grift has quit [Ping timeout: 272 seconds]
grift has joined #openwrt-devel
nmrh has joined #openwrt-devel
<FirstTime_NoTime>
I have spent days to work out why I cannot control that single LED this board has. It uses the builtin 2.4 Wifi and another 5ghz chip - MediaTek MT76x2E 802.11nac/MediaTek MT7620 802.11bgn. And it seems that the driver for MT76x2E is creating an LED entry, but the MT7620 driver is not
<FirstTime_NoTime>
Both seem to use the same code (mt76_led) for that task
swex has joined #openwrt-devel
Tusker has joined #openwrt-devel
<Tusker>
heya guys, I have a single node ceph cluster which I use to do my openwrt builds locally, but I find the performance a bit on the slow side, given that I have ssd cache in front of the spinning drives etc, the rm -rf *linux* often takes ages to complete, so was wondering what the general opinion on filesystems for a openwrt build server ?
<mangix>
rr123: in what way?
gch98121337 has joined #openwrt-devel
gch9812133 has quit [Read error: Connection reset by peer]
gch98121337 is now known as gch9812133
<Tusker>
would bcachefs be a good option for it ?
nmrh has quit [Ping timeout: 260 seconds]
<m4t>
Tusker: maybe 'eatmydata' could help queue up all the small fs operations
gch9812133 has quit [Read error: Connection reset by peer]
gch9812133 has joined #openwrt-devel
<m4t>
helps with apt on sd cards anyways
<m4t>
ime small io size + network filesystems don't go well together
<Tusker>
ok, will have a look at it. what underlying filesystem is best ? RAID5 + btrfs + eatmydata ?
<m4t>
Tusker: or try mounting the cephs with 'nowsync'
<enyc>
jow: overloaded by genuine use, or some sort of problem-bots/junk/etc?
<enyc>
jow: At what point shuold openwrt move to wide distributed mirrors in similar style to linux distros I wonder!
Darkmatter66 has joined #openwrt-devel
<owrt-snap-builds>
build #675 of ath79/nand is complete: Failure [failed updatefeeds] Build details are at http://buildbot.openwrt.org/master/images/builders/ath79%2Fnand/builds/675 blamelist: DENG Qingfang <dengqf6@mail2.sysu.edu.cn>, Paul Fertser <fercerpav@gmail.com>, Adrian Schmutzler <freifunk@adrianschmutzler.de>
gch9812133 has quit [Read error: Connection reset by peer]
gch98121338 has joined #openwrt-devel
ivanich has joined #openwrt-devel
Misanthropos has quit [Ping timeout: 260 seconds]
hbug_ has quit [Remote host closed the connection]
hbug_ has joined #openwrt-devel
rsalvaterra1 has quit [Quit: Leaving.]
rsalvaterra has joined #openwrt-devel
feriman has joined #openwrt-devel
Grommish has quit [Remote host closed the connection]
hsp has quit [Ping timeout: 265 seconds]
Grommish has joined #openwrt-devel
Misanthropos has joined #openwrt-devel
FirstTime_NoTime has quit [Remote host closed the connection]
Darkmatter66 has quit [Quit: ZNC 1.7.5 - https://znc.in]
Grommish has quit [Quit: No Ping reply in 180 seconds.]
Grommish has joined #openwrt-devel
hsp has joined #openwrt-devel
xback has quit [Ping timeout: 265 seconds]
<rsalvaterra>
mangix: One thing that worries me about GCC 10.x is the inliner aggressiveness… -finline-functions is now enabled at -O{s,2,3}, and it makes the code noticeably larger (I can't fathom why they enabled it at -Os, doesn't make any sense). I don't know if the speed benefits outweigh the bloat, but this should be *thoroughly* tested before we bump GCC to 10.x, in order to decide whether or not we disable -finline-functions.
Borromini has joined #openwrt-devel
goliath has joined #openwrt-devel
<mangix>
i assume that will happen after the release
<rsalvaterra>
mangix: You mean the testing, right? :)
<Borromini>
somebody talking release? \o/
Ycarus has joined #openwrt-devel
<mangix>
I assume there will be done kind of release based on kernel 5.4
<rsalvaterra>
Borromini: I'm talking about GCC 10.x being more (code) cache-hostile. :P
<mangix>
rsalvaterra: I'm talking about switching to GCC10
<mangix>
keep in mind that every GCC release increases compiled size
<Borromini>
rsalvaterra: oh :P :(
<rsalvaterra>
mangix: Yes, but this time the increase is more significant, from my experience.
<pkgadd>
keep in mind, 'embedded' := as smartphone these days...
<rsalvaterra>
pkgadd: My smartphone has *three* times more RAM than my laptop. I'm not sure I agree.
<pkgadd>
hehe, well...
<mangix>
my smartphone has three times more RAM than my NAS
<mangix>
which is funny given that NAS typically uses a lot of RAM
<rsalvaterra>
Sure, my laptop has 2 GiB of RAM, but it gets sh*t done. :P
<Borromini>
and all your smartphone does is phone home :P
<Tapper>
Borromini Is that not what phones are fore? /s
<Borromini>
:P
<Tapper>
My wife calls her phone her facebook. lol
<rsalvaterra>
Borromini: Yeah… the price of convenience… :(
<Tapper>
When I asked here about she said that is all the dam thing seems to do.
<Tapper>
her*
<mangix>
apple device i'm guessing
<Borromini>
rsalvaterra: that's how they get us all :)
<rsalvaterra>
I swear, every time I see someone suggesting echo 1 > drop_caches I just want to scream.
<karlp>
in what context?
<rsalvaterra>
Are you debugging the page cache? No? Then why the f**k are you messing with it?
<karlp>
this is the whole "ram's being used! I don't want it to be used!" confusion
<Borromini>
that's the real redmond legacy
fredrikhl has joined #openwrt-devel
<Borromini>
until they fessed up and turned around, of course. 'oh no we'll start using that ram as well, don't mind us, we've been pointing fingers at unices all along, but hey, nevermind, all good!'
<Namidairo>
im trying to think whether or not dropbear would tell the kernel to start ejecting stuff if I were to scp over a new image on those 4/32 devices
<rsalvaterra>
People don't seem to understand kernels smartened up since KRNL386.EXE…
<karlp>
smartened, aka, someone somewhere else decided it knew how to do things better and less predictably ;)
<rsalvaterra>
Namidairo: On a 4/32 device you want to bring down non-essential services before flashing a new image, to make room for it.
feriman has quit [Ping timeout: 265 seconds]
<Borromini>
karlp: the regular industry definition of 'smart' ;)
feriman has joined #openwrt-devel
Dracos-C- is now known as Dracos-Carazza
<rsalvaterra>
And speaking of memory management, would someone please review/merge my procd patches, so we can end the "mount /tmp on zram" silliness once and for all…? :/
<nitroshift>
rsalvaterra, o/
<rsalvaterra>
nitroshift: o/
<mangix>
rsalvaterra: there qas such a bug with mt7621
<mangix>
i lost quite a bit od data that way...
<mangix>
cache coherency bug that is
<rsalvaterra>
mangix: Cache coherency bug? On MT7621?
adrianschmutzler has joined #openwrt-devel
Redfoxmoon has quit [Ping timeout: 260 seconds]
victhor has joined #openwrt-devel
Redfoxmoon has joined #openwrt-devel
Redfoxmoon has quit [Changing host]
Redfoxmoon has joined #openwrt-devel
<mangix>
yeah. it's fixed now
<rsalvaterra>
Good to know, since I got myself four Redmi AC2100 devices (one for me, three for friends of mine). :P
<rsalvaterra>
I installed OpenWrt on one of them yesterday… the procedure described in the wiki is nuts, completely unnecessary with the 2.0.23 firmware version.
<rsalvaterra>
They're even nice enough to include curl, so you can just directly download the OpenWrt images from the router itself. :P
<Namidairo>
I did what I did when only the release firmware was around so meh
<rsalvaterra>
And even that video is overly complicated, you don't need a local HTTP server to upload the images, you can just curl them down from the OpenWrt repository.
<Namidairo>
just in case one didn't have a working internet connection for whatever reason
<rsalvaterra>
Namidairo: In that case, you can use SCP or SSH directly. No HTTP server needed, again.
<rsalvaterra>
mangix: Wonderful explanation. It's long fixed, fortunately.
Misanthropos has quit [Ping timeout: 240 seconds]
Fishman has quit [Ping timeout: 264 seconds]
<Namidairo>
well feel free to write up a new process
<Namidairo>
since you'll probably be flashing 4 of them soon :P
<rsalvaterra>
One down, three to go. ;)
<rsalvaterra>
Namidairo: I had a look inside the OEM firmware to see the firewall configuration and running services… it's terrifying.
<Namidairo>
it was a janky process to begin with
linzst has joined #openwrt-devel
<rsalvaterra>
The damn thing boots up with completely open wifi, to which you can connect and do the basic configuration procedure. You're basically racing against your evil neighbour.
<Namidairo>
that was part of the reason i didn't want to have mine hooked up to my network during setup
<Namidairo>
did you see the lua as well
<Namidairo>
all nice and scrambled
Fishman has joined #openwrt-devel
<rsalvaterra>
I didn't look at the Lua scripts. I just looked at /etc/config/firewall and felt sorry for whoever bought this to use as-is (was?)…
<rsalvaterra>
(And I'm sure it's been a lot of people, judging from how fast they were sold on AliExpress…)
<Namidairo>
in fairness I think many of those sales may have happened after I published the poc
<rsalvaterra>
Namidairo: I truly hope so!
adrianschmutzler has quit [Quit: ~ Trillian - www.trillian.im ~]
linzst has quit [Quit: Leaving]
Misanthropos has joined #openwrt-devel
<Hauke>
any objections to tag and start the build of 18.06.9 today in the evning? In the release notes we should then decare it end of life and make this the final release.
<Hauke>
*evening
<jow>
fine with me
<ynezz>
nice, so we're going to maintain one stable release from now on?
<jow>
that is until 20.x comes out
<jow>
or 21.x
<jow>
19.x will not receive heavy maintenance after that, but I'd prefer to keep it "open" for eventual security fixes
nmrh has joined #openwrt-devel
repulse has joined #openwrt-devel
opal has quit [Ping timeout: 240 seconds]
opal has joined #openwrt-devel
<rsalvaterra>
Hmm… Is it safe to ignore this? Looks ominous enough…
<rsalvaterra>
[ 0.631956] nand: WARNING: mt7621-nand: the ECC used on your system is too weak compared to the one required by the NAND chip
feriman has quit [Ping timeout: 246 seconds]
<Namidairo>
I don't have that
<rsalvaterra>
Namidairo: Really? This is yesterday's snapshot.
<Namidairo>
I haven't put a new snapshot on for a few weeks
nmrh has quit [Quit: nmrh]
<Namidairo>
you also might have different nand chip to mine
<Namidairo>
I think a few of the later units were shipping with toshiba (?)
<rsalvaterra>
I'm on macOS at the moment. Does the image builder work here? (Never tried.)
<aparcar[m]>
no clue
<rsalvaterra>
No problem, I'll SFTP to the Debian machine.
<aparcar[m]>
thank you
<rsalvaterra>
Extracting.
<rsalvaterra>
Shall I make a specific image, or any will suffice?
<Grommish>
I need to restrict a package to x86_64 arches only. Does this cover all of them? DEPENDS:=@((x86_64)||(USE_GLIBC&&(i386)))
<Grommish>
or is there an i686?
<aparcar[m]>
rsalvaterra: anything is fine. It's mostly about the key generation
<rsalvaterra>
Built fine. No unusual output.
lmore377 has quit [Quit: No Ping reply in 180 seconds.]
lmore377 has joined #openwrt-devel
<rsalvaterra>
Now I have a question… When we make kernel_oldconfig CONFIG_TARGET=subtarget and a bunch of config symbols are removed, doesn't it mean the configuration should be refreshed (as the symbols are already part of the generic config)?
<aparcar[m]>
I'm not a kernel refresh person sorry
<aparcar[m]>
there are like two usual suspects that do all the kernel bumps, maybe ping them?
<rsalvaterra>
I will, but not just yet, I still need to dig a bit more. :)
<ldir>
hostnames with '-' in them are legal right? e.g. 'big-server'
<rsalvaterra>
Good question. Intuitively, I'd say yes, but I don't know for sure.
<svanheule[m]>
I use hostnames with dashes, and that works :-)
<svanheule[m]>
rsalvaterra: but ipset does appear to resolve them for you
<svanheule[m]>
ldir: I get the same error on my machine, it appears ipset is splitting the hostname at the dash
<rsalvaterra>
That's very strange… dnsmasq has a facility to fill ipsets at DNS resolution time.
<ldir>
indeed ipset will try to resolv hostnames to an address.
<rsalvaterra>
That's what I use for those situations.
<rsalvaterra>
I was positive you couldn't put hostnames in ipsets, but I'd love to be wrong.
<ldir>
I'm trying to force an entry into a set, as a permanent entry hence the timeout 0
<ldir>
you can't put hostnames in, you can put addresses in - ipset 'helpfully' resolves names to addresses... except it appears to have problems with '-' characters in the hostname.
<stintel>
If host names or service names with dash in the name are used instead of IP addresses or service numbers, then the host name or service name must be enclosed in square brackets. Example:
<ldir>
stintel: thanks - I did look at the man page, not closely enough
<stintel>
welcome
<rsalvaterra>
I still believe the dnsmasq solution is more elegant, especially if you're dealing with CDNs.
<ldir>
yes, but I want to add a couple of 'fixed' entries in at 'boot time' with a zero (permanent) timeout
<rsalvaterra>
Fair enough. :)
<ldir>
The set is added to dynamically by the dnsmasq ipset mechanism
<rsalvaterra>
ldir: Well, since you're here, and you're also a kernel guy…
<ldir>
I have some entries that must stick!
<rsalvaterra>
… did you see my question? :P
<ldir>
rsalvaterra: I saw the question, I'm not a kernel guy by any stretch of the imagination and no I have no idea
<rsalvaterra>
Oh, and about the hyphens, I had totally forgot https://cm-sintra.pt/ *facepalm*.
<rsalvaterra>
ldir: I see you do kernel updated from time to time, that's why I asked. :P
<ldir>
there's a magic script that does the bumps, but when it comes to symbols...I put my head in the sand & hope
<ldir>
I have never understood the kernel symbols & subtarget thing. Sorry
<rsalvaterra>
ldir: That much I understand. :)
netprince has quit [Quit: Leaving]
Ycarus has quit [Quit: Ycarus]
black_ant has quit [Ping timeout: 260 seconds]
ivanich has quit [Quit: Konversation terminated!]
Nick_Lowe has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
dedeckeh has quit [Remote host closed the connection]
muhaha has quit [Quit: Connection closed]
dopje_ has quit [Quit: Checking other places]
dopje has joined #openwrt-devel
feriman has quit [Ping timeout: 272 seconds]
ivanich has joined #openwrt-devel
ivanich has quit [Quit: Konversation terminated!]
xback has joined #openwrt-devel
<xback>
Hauke: Just noticed this one: https://git.openwrt.org/?p=openwrt/openwrt.git;a=commit;h=2a8279c161efeb243084d78d8077661c9122bb18
<xback>
Hauke: Thanks for the fixup. Apologies for the mistake :(
<Hauke>
xback: no problem, I did an update of the kernel earlier but did not really test and pushed it
<Hauke>
saw this in the comparision
<rsalvaterra>
Hauke, xback, could one of you please tell me if my reasoning is correct, about the kernel symbols?
<rsalvaterra>
This is what I asked: when we make kernel_oldconfig CONFIG_TARGET=subtarget and a bunch of config symbols are removed, doesn't it mean the configuration should be refreshed (as the symbols are already part of the generic config)?
ivanich has joined #openwrt-devel
<Hauke>
rsalvaterra: yes
<rsalvaterra>
Thanks, I thought so.
<rsalvaterra>
I just noticed this on ramips/mt7621.