i just installed a current snapshot onto my FB7520.
Now i've got less informations in LuCI's Overview-DSL Status.
It's now like
Line State: Showtime with TC-Layer sync
Line Mode: G.993.2 (VDSL2, Profile 17a, with down- and upstream vectoring)
Line Uptime: 1h 9m 26s
Data Rate: 111.881 Mb/s / 42.462 Mb/s
Noise Margin: 12.1 dB / 7.1 dB
whereas before there were much more columns with informations about the quality of the line, occurred errors an so on.
Is there any way to get the informations back into the overview?
It looks more neat now, but i'd like to have the choice to view the full output.
I wasn't aware that this package is not available in the repository. I suspect that is due to dependency on ltq-dsl-base which isn't available on the package buildbot, as it is architecture-dependent. In that case, this issue won't solve itself. But I'm not quite sure how to fix that (aside from just removing the dependency).
I have the same problem and I just had a look at ltq-dsl-base. It lists ipq40xx as a dependency and it is even installed on my 7520. Any other ideas why the app is not available?
I think the problem is that the phase2 buildbots are per-architecture, i.e. they build packages for multiple targets, and don't have access to this target-specific dependency.
So, maybe removing dependency would actually be the right thing to do here? But that would at least require making sure that the code falls back gracefully on devices without a DSL modem.
@janh - the fix would be adding PKG_FLAGS:=nonshared to luci-mod-dsl's Makefile, this should force the build of this package in the phase1 bots, but that would drag a lot of fundamental LuCI dependencies along, so not ideal either.
I'll drop the explicit dep on +ltq-dsl-base for now and would appreciate if you could follow up with some graceful error handling later on.
Edit:
Looking at ltq-dsl-base... it only seems to ship a bunch of hotplug scripts and it is not depending on anything DSL specific either, so it provides nothing the LuCI ui would rely on. The ubus DSL metrics are provided by something else, so I think it is fine to simply drop the dependency without further changes.
Ah okay, good to know. We can easily disable the DSL menu entries at runtime by adding a dependency on some file shipped by ltq-dsl-app to the menu JSON definition
luci-mod-status and luci-mod-network call network.getDSLModemType, which looks at board.json to detect whether there is a DSL modem. But it doesn't look like that would be possible for the menu?