New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
not working for Ubiquity devices #26
Comments
f.i. board-name is "loco-m-xw", but imagebuilder wants "ubnt-loco-m-xw". root@74-57:~# ubus call system board { so please check LEDE (maybe a new ticket there?) and write a workaround. function image_request() { |
thanks for the testing, seems like the imagebuilder calls the image |
is it only happening for ubnt-devices? |
On Thu, Aug 10, 2017 at 06:15:35AM -0700, FreifunkUFO wrote:
is it only happening for ubnt-devices?
what about a workaround? (with an "if model=Ubiquity"-question and modified subfunction (+=ubnt))
unifying the board_name to be identical with the IB profile name should
be done in OpenWrt/LEDE. As a temporary work-around there could be a DB
table to resolve this in a generic way.
Please don't introduce any vendor-name regex in the Python code...
|
as reported [here][1] the board_name is not everywhere unified yet. to solve this problem, the model name is transported as well and used as a fallback identifier [1]: openwrt/asu#26 Signed-off-by: Paul Spooren <paul@spooren.de>
"model": "Ubiquiti Loco M XW", The ImageBuilder uses a different model string and a different profile string as stored on the device. Looks like I have to work with (SQL) regex after all. @dangowrt @FreifunkUFO other ideas to solve this in a more generic way? |
First of all, you should file a bug at http://bugs.lede-project.org/
because the board_name should be changed in
target/linux/ar71xx/base-files/lib/ar71xx.sh and its users to be
consistent with the name used when creating the an image.
However, it might not be feasible to backport this change to
lede-17.01.
Hence you might still need an extra table for alternative board names.
This will be needed anyway as sometimes a boardname changes between
releases...
|
as reported [here][1] the board_name is not everywhere unified yet. to solve this problem, the model name is transported as well and used as a fallback identifier [1]: openwrt/asu#26 Signed-off-by: Paul Spooren <paul@spooren.de>
ticket was closed. but please link the filed bug at lede-project about board_name |
there is an error when trying it with UBNT devices: board not found
The text was updated successfully, but these errors were encountered: