First installed as dependency for multiple packages and second is used
by debconf, but not installed as it's dependency. This enables package
configuration during install or dpkg-reconfigure(7) from debconf.
This removes following messages on console during package install:
debconf: unable to initialize frontend: Dialog
debconf: (No usable dialog-like program is installed, so the dialog \
based frontend cannot be used. at \
/usr/share/perl5/Debconf/FrontEnd/Dialog.pm line 76, <> line 11.)
debconf: falling back to frontend: Readline
Signed-off-by: Sergey Popovich <sergey.popovich@ordnance.co>
This variable is only required and used for dynamic network configs:
validating and configuring it for rest of the paths isn't necessary.
While there split warning message to two lines to make code and
runtime output more readable.
Signed-off-by: Sergey Popovich <sergey.popovich@ordnance.co>
There are three types of value accepted by NETAUTO:
1) "dhcp" for automatic network settings via DHCP
2) "up" to bring link up, wait for IPv6 tentative and link up
operstate
3) anything else: apply static configuration, wait for IPv6
tentative and link up operstate
Note that empty ("") value is subset of 3) and we only skip link up
operstate monitoring for it since commit 3e89468cd0
("Don't require link-up on ma1 if NETAUTO is not specified.").
Add fourth case with NETAUTO=none to skip all but NETHW (hardware
address) from boot-config file and support different management
adapter config methods (e.g. Debian network config system).
This also fixes incorrect "return" statement usage outside of function
introduced with commit 3e89468cd0
("Don't require link-up on ma1 if NETAUTO is not specified.") and adds
newline before wait_link_up() to make code more readable.
Signed-off-by: Sergey Popovich <sergey.popovich@ordnance.co>
Since empty NETAUTO= in /mnt/onl/boot/boot-config is valud according to
rules in initramfs /boot/ifup, follow this behavior in onl-boot-config
to get rid of incorrect message:
root@localhost:/# onl-boot-config --show
NETDEV=ma1
BOOTMODE=INSTALLED
SWI=images::latest
NETAUTO=
The NETAUTO value '' is invalid.
The boot configuration has not been changed.
Signed-off-by: Sergey Popovich <sergey.popovich@ordnance.co>
It is very similar to Aurora 420, even onlp shared object part from
Aurora 620 considered as example when porting support for 420 (see
the diff between 620 and 420 to find differences if necessary).
Main difference in onlp is that we have four LEDs (1 SYS STAT, 2 PSU
and 1 for FAN), 7 thermal (4 for two PSU, 1 for MAC, 1 for front and
1 for rear) and 6 fans (4 for board, 2 for PSU).
New 420, as well as 620 and 720 requires upstream ONIE to install
correctly. Install and boot tested with ONIE "master-201805301609".
Signed-off-by: Sergey Popovich <sergey.popovich@ordnance.co>
Following enhancements come with this change:
o New ASTERION board
o New/updated sysfs interface to:
+ detect rxlos (rxlos1..rxlos4)
+ set tx_disable (tx_disable1..tx_disable4)
+ detect tx_fault (tx_fault1..tx_fault4)
+ read/update sfp_copper eeprom
Signed-off-by: Sergey Popovich <sergey.popovich@ordnance.co>
According to IANA assignments for enterprise Netberg company has number
50424, not 47294. Correct this to match one in ONIE.
Signed-off-by: Sergey Popovich <sergey.popovich@ordnance.co>
The transmitter disable bytes are standardized by the MSA and managed by the upper layer using the dev_writeb() routines when
appropriate based on module type.
Writing the transmitter enable bytes are not appropriate for CR cables and will generate write errors so attempting to
emulate this behavior without knowing the type of module is also troublesome.
