Installed new stable firmware v4.8.3 for Flint3 (local install)
Update was successful , every thing works fine but once enabled luci and check the software upgrade availability , Found at least 20 qsdk-nss / cnss platform driver update available (like qsd-nss-platform driver -dirty2 etc).
Installed these , reboot and bang , flint 3 refuse to boot properly.
Tried 3 times , same issue , had to restore from uboot and back to v4.8.1
Strangely there is no platform driver update available for firmware v4.8.1 within luci.
Yep, because you shouldn't run software upgrades manually. Never ever try to update packages just by using the package manager. It will brick nearly all GL devices because the firmware isn't a rolling release at all.
@bruce Would it be a good idea to add some nuances to the package page in the gl ui?
I think one issue is that most people think it is for maintaining security, when this actually is not true, it should be only for user selected packages, security goes per firmware image basis.
They won't understand that the packages are part of a toolchain on newer snapshots not publicly available, and this might break their systems, especially core packages with different kernels it got compiled against to.
Have the same issues and my box doesnāt boot up at all after upgrade (just FW update and not update packages in LUCI). Cannot boot up and need to do UBoot restore and found the following packages are listed to have updates:
Package name
Version
Size (.ipk)
Description
kmod-emesh-sp
5.4.213+g2dbe543-1 Ā» 5.4.213+g69d0506-dirty-1
~15.44 KiB
This is the kernel module for Service Prioritization in EasyMesh
Upgradeā¦
kmod-nss-udp-st-drv
5.4.213+g2dbe543-1 Ā» 5.4.213+g69d0506-dirty-1
~10.72 KiB
Kernel driver for NSS UDP Speedtest
Upgradeā¦
kmod-qca-cnss
5.4.213+g2dbe543-1 Ā» 5.4.213+g69d0506-dirty-1
~153.59 KiB
CNSS Platform Driver
Upgradeā¦
kmod-qca-mcs
5.4.213+g2dbe543-1 Ā» 5.4.213+g69d0506-dirty-1
~32.94 KiB
This package installs the IGMP/MLD Snooping Module
Upgradeā¦
kmod-qca-nss-dp
5.4.213+g2dbe543-1 Ā» 5.4.213+g69d0506-dirty-1
~74.96 KiB
Kernel driver for NSS data plane
Upgradeā¦
kmod-qca-nss-macsec
5.4.213+g2dbe543-1 Ā» 5.4.213+g69d0506-dirty-1
~82.17 KiB
Kernel driver for NSS macsec
Upgradeā¦
kmod-qca-nss-nsm
5.4.213+g2dbe543-1 Ā» 5.4.213+g69d0506-dirty-1
~7.79 KiB
Network Status Module
Upgradeā¦
kmod-qca-nss-ppe
5.4.213+g2dbe543-2 Ā» 5.4.213+g69d0506-dirty-2
~158.95 KiB
Kernel driver for PPE (core driver)
Upgradeā¦
kmod-qca-nss-ppe-bridge-mgr
5.4.213+g2dbe543-2 Ā» 5.4.213+g69d0506-dirty-2
~8.75 KiB
Kernel driver for NSS PPE bridge manager
Upgradeā¦
kmod-qca-nss-ppe-ds
5.4.213+g2dbe543-1 Ā» 5.4.213+g69d0506-dirty-1
~10.85 KiB
Kernel driver for PPE Direct Switch (core driver)
Upgradeā¦
kmod-qca-nss-ppe-lag-mgr
5.4.213+g2dbe543-2 Ā» 5.4.213+g69d0506-dirty-2
~3.78 KiB
Kernel driver for NSS LAG manager
Upgradeā¦
kmod-qca-nss-ppe-mirror-test
5.4.213+g2dbe543-1 Ā» 5.4.213+g69d0506-dirty-1
~8.51 KiB
Kernel driver for PPE test module
Upgradeā¦
kmod-qca-nss-ppe-netlink
5.4.213+g2dbe543-2 Ā» 5.4.213+g69d0506-dirty-2
~5.95 KiB
PPE netlink Manager
Upgradeā¦
kmod-qca-nss-ppe-pppoe-mgr
5.4.213+g2dbe543-2 Ā» 5.4.213+g69d0506-dirty-2
~3.04 KiB
Kernel driver for NSS PPE PPPoE manager
Upgradeā¦
kmod-qca-nss-ppe-qdisc
5.4.213+g2dbe543-2 Ā» 5.4.213+g69d0506-dirty-2
~37.72 KiB
Kernel module for configuring schedulers and shapers in PPE
We will check the list and remove some plugins' update packages that affect system stability. Some packages are not compatible with sdk v4.8 or part of the toolchain on snapshot, and updates will cause the system to not start or crash.
Bruce thanks, but I don't think that would be a full solution, in OpenWrt this is very normal nature you just don't want to update all packages, since it is the same system it would be better to have a text informing the user this is not designed to update all plugins for security and potential break the system and that security updates go per firmware basis and this is only for user packages.
The issue with this solution is that you have no control in the future what effects other packages have, and basically becomes unable to maintain, when resources could be better put in into developing the firmware
I think it makes sense, and we will evaluate the frequency of such questions.
Adding to the GL GUI may cause confusion among some novice users, since maybe they cannot distinguish between what is installed manually and what is the system pre-installed; and if add in the GUI, we need to evaluate with the PM team.
If added to docs, our docs are relatively large and have a lot of content.
If added to the "Interface guide-Applications-Plug-ins", I think some users may not read it.
It's difficult at the moment.
Then it is their own mistake, what now the bigger issue is that is that none of these texts are on this plugin page inside the gl ui which causes a repeating problem.
If these users are novice users, they also need to understand the plugin system is the same as OpenWrts, and it is not recommend to update all packages, it is only for user selected packages or for someone who knows what he is doing (a dev).
Because it will influence bug solving and analyzing bugs in the firmware, some older firmware images from Flint 1 I believe still had the OpenWrt feed in it.
The scope is too large to just filter 'core' packages it will be out of control.
