On Tue, Feb 26, 2019, at 3:34 PM, Vagrant Cascadian wrote:
> On 2019-02-26, Rick Thomas wrote:
> >> On Feb 26, 2019, at 10:49 AM, Vagrant Cascadian wrote:
> >>
> >> On 2019-02-26, Rick Thomas wrote:
> >>> On my Cubox-i4Pro when I run fw_printenv (from the u-boot-tools
> >>> package) it says “W
On 2019-02-26, Rick Thomas wrote:
>> On Feb 26, 2019, at 10:49 AM, Vagrant Cascadian wrote:
>>
>> On 2019-02-26, Rick Thomas wrote:
>>> On my Cubox-i4Pro when I run fw_printenv (from the u-boot-tools
>>> package) it says “Warning: Bad CRC, using default environment”.
...
>> fw_printenv will only
> On Feb 26, 2019, at 10:49 AM, Vagrant Cascadian wrote:
>
> On 2019-02-26, Rick Thomas wrote:
>> On my Cubox-i4Pro when I run fw_printenv (from the u-boot-tools
>> package) it says “Warning: Bad CRC, using default environment”.
>
> If when booting, it also gives you this message, that would
On 2019-02-26, Rick Thomas wrote:
> On my Cubox-i4Pro when I run fw_printenv (from the u-boot-tools
> package) it says “Warning: Bad CRC, using default environment”.
If when booting, it also gives you this message, that would suggest you
have no saved environment for fw_printenv to read from, as i
On my Cubox-i4Pro when I run fw_printenv (from the u-boot-tools package) it
says “Warning: Bad CRC, using default environment”.
The “default environment” is clearly *not* the environment that u-boot is using
to boot the box. At least the “ethaddr” variable in that environment is
clearly a fake
5 matches
Mail list logo
