Posts by xe`

    DEPRECATED Current versions of LE will identify this problem and set a MAC based on the serial of the device. If you have already applied this fix you do not need to do any further changes as this will be automatically catered for as well.

    Posting here for later migration to the wiki.

    Tested with a Khadas VIM s905x on LE 8.1.3 but will likely be relevant to many other platforms.

    All? VIM (1) running "Vim_Marshmallow_Root_170303.7z" share a common MAC address 00:15:18:01:81:31.

    This causes serious network issues if you operate more than one VIM on the same LAN.

    Khadas if you read this then this needs fixed.

    None of the methods listed in this thread work however there is an easier way.

    This is intentionally written long hand as it is important no mistakes are made and given how low level it is mistakes are entirely possible. A mistake with a MAC address will break all network connectivity and all the headaches that come with it.


    SSH to the box

    Confirm current MAC

    # ip link

    1: lo: mtu 4096 qdisc noqueue

    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00

    2: eth0:
    mtu 1500 qdisc fq_codel qlen 1000

    link/ether 00:15:18:01:81:31 brd ff:ff:ff:ff:ff:ff

    3: wlan0:
    mtu 1500 qdisc noop qlen 1000

    link/ether cc:b8:a8:19:96:86 brd ff:ff:ff:ff:ff:ff

    Confirm the origin of this MAC address is

    fw_printenv | grep ethaddr


    Stop here if this does not match.

    Generate and take a note of a new random MAC address

    # dbus-uuidgen | cut -c1-12 | sed -e 's/../:&/2g' -e 's/^://' | tr [:lower:] [:upper:]


    Update the system to use this MAC

    #fw_setenv ethaddr 18:C0:1B:66:29:93

    Confirm it took:

    fw_printenv | grep ethaddr


    Reboot. Any static DHCP leases will change since the MAC has changed.

    This procedure will survive auto updates.

    This is works to you when the devices work together on same network ?

    In simple terms if you have two devices on the same network with the same MAC then they will both be unreliable or may not even work at all.

    The fixes above are various ways to change the MAC address of a box so to remove this clash. It should only be done as a last resort and after you are sure this is really the issue.

    I just looked at my generic loaded machine and was coming back to say that it seems to have both nvidia and nvidia-legacy drivers. But you beat me to it.

    Sent from my U65GT using Tapatalk

    Yes LE generic has a feature where it will magically use the legacy driver if the GPU is not currently supported by nvidea. This doesn't cover archaic GPUs but ION2 etc will work fine. The beauty of this is that generic and legacy are now one build simplifying it for users.