2017-10-22 9:31 GMT+03:00 Rick Ashford <Rick.Ashford@suse.com>:
There is a great thread on the Armbian forum about the EspressoBin, and it helped me get things up and running with Tumbleweed.
One of the guys there has a public Dropbox link that includes their images for flashing the u-boot loader: https://www.dropbox.com/sh/kmgmo1uubhcczx5/AAAYEvTIFxpBr0dHG2QcapTza?dl=0
The thread: https://forum.armbian.com/index.php?/topic/4089-espressobin-support-development-efforts/&page=4
With their boot loader I was able to finally use BTRFS images as well as PXE boot. It also has an EFI load function in the help that I need to get around to trying.
Well, If armian u-boot is able to boot our standard EFI-Grub JeOS, then we can recommend to use it with openSUSE and don't reinvent the wheel.
Rick Ashford Sales Engineering Manager - West SUSE Linux rick.ashford@suse.com Office: 512-782-4318 Mobile: 512-731-3035
On Oct 21, 2017, at 12:32 PM, Matwey V. Kornilov <matwey.kornilov@gmail.com> wrote:
2017-10-21 19:47 GMT+03:00 Matwey V. Kornilov <matwey.kornilov@gmail.com>:
2017-10-21 19:35 GMT+03:00 Matwey V. Kornilov <matwey.kornilov@gmail.com>:
2017-10-20 18:02 GMT+03:00 Matwey V. Kornilov <matwey.kornilov@gmail.com>:
2017-10-20 17:37 GMT+03:00 Alexander Graf <agraf@suse.de>:
On 20.10.17 16:21, Matwey V. Kornilov wrote:
20.10.2017 17:12, Alexander Graf пишет:
On 20.10.17 13:57, Matwey V. Kornilov wrote:
Hi,
I've just received EspressoBin 1G. Any success stories how to run openSUSE?
I think you'll basically have to somehow flash a working U-Boot with
distro boot onto it and then just dd the tumbleweed/42.3 iso onto a usb
stick and cross your fingers that gets you to a point where you can
install :)
It has microsd card, I think it should be able to boot from sd, no?
I also need to to find serial console pins on the board :)
There seems to be a lengthy discussion on the mailing list. I guess you
can select the boot device using DIP switches though?
Yes, I can. I think it is preferred way. Need to find expected layout
to place u-boot image.
Well, at least while booting from SATA, they say that BootRom looks
for code starting with zero offset, which implies that there can not
be any GPT partition table.
Probably, it is similar for SD. If so, we need to flash our EFI-aware
u-boot instead of upstream one.
Well, SATA flash image from here
http://wiki.espressobin.net/tiki-index.php?page=Boot+ESPRESSObin+from+SATA+drive&highlight=sata
suits for booting from microsd card, when it is flushed from zero
offset and boot selection switchs are set to 7.
At least, there is non-destructive way to check out u-boot image.
Double checked. Seems that microsd boot doesn't work and is not supported. At least for my V5 board. It just falls back to SPINOR
http://espressobin.net/forums/topic/how-to-flash-u-boot/
Alex
--
With best regards,
Matwey V. Kornilov
--
With best regards,
Matwey V. Kornilov
--
With best regards,
Matwey V. Kornilov
-- With best regards, Matwey V. Kornilov -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
-- With best regards, Matwey V. Kornilov -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
2017-10-22 10:36 GMT+03:00 Matwey V. Kornilov <matwey.kornilov@gmail.com>:
2017-10-22 9:31 GMT+03:00 Rick Ashford <Rick.Ashford@suse.com>:
There is a great thread on the Armbian forum about the EspressoBin, and it helped me get things up and running with Tumbleweed.
One of the guys there has a public Dropbox link that includes their images for flashing the u-boot loader: https://www.dropbox.com/sh/kmgmo1uubhcczx5/AAAYEvTIFxpBr0dHG2QcapTza?dl=0
The thread: https://forum.armbian.com/index.php?/topic/4089-espressobin-support-development-efforts/&page=4
With their boot loader I was able to finally use BTRFS images as well as PXE boot. It also has an EFI load function in the help that I need to get around to trying.
Well, If armian u-boot is able to boot our standard EFI-Grub JeOS, then we can recommend to use it with openSUSE and don't reinvent the wheel.
Well, I've just managed to build marvell u-boot 2017.03-armada-17.10.1-g440395a and run it from SATA drive. I also started EFI grub using this bootloader. Also, it appeared that placing loader to LBA0 is not necessary, the loader can be placed to separate partition with 0x4d type. Unfortunately, marvell u-boot config is only use tftp in bootcmd. So, I think the next step is to try upstream u-boot.
Rick Ashford Sales Engineering Manager - West SUSE Linux rick.ashford@suse.com Office: 512-782-4318 Mobile: 512-731-3035
On Oct 21, 2017, at 12:32 PM, Matwey V. Kornilov <matwey.kornilov@gmail.com> wrote:
2017-10-21 19:47 GMT+03:00 Matwey V. Kornilov <matwey.kornilov@gmail.com>:
2017-10-21 19:35 GMT+03:00 Matwey V. Kornilov <matwey.kornilov@gmail.com>:
2017-10-20 18:02 GMT+03:00 Matwey V. Kornilov <matwey.kornilov@gmail.com>:
2017-10-20 17:37 GMT+03:00 Alexander Graf <agraf@suse.de>:
On 20.10.17 16:21, Matwey V. Kornilov wrote:
20.10.2017 17:12, Alexander Graf пишет:
On 20.10.17 13:57, Matwey V. Kornilov wrote:
Hi,
I've just received EspressoBin 1G. Any success stories how to run openSUSE?
I think you'll basically have to somehow flash a working U-Boot with
distro boot onto it and then just dd the tumbleweed/42.3 iso onto a usb
stick and cross your fingers that gets you to a point where you can
install :)
It has microsd card, I think it should be able to boot from sd, no?
I also need to to find serial console pins on the board :)
There seems to be a lengthy discussion on the mailing list. I guess you
can select the boot device using DIP switches though?
Yes, I can. I think it is preferred way. Need to find expected layout
to place u-boot image.
Well, at least while booting from SATA, they say that BootRom looks
for code starting with zero offset, which implies that there can not
be any GPT partition table.
Probably, it is similar for SD. If so, we need to flash our EFI-aware
u-boot instead of upstream one.
Well, SATA flash image from here
http://wiki.espressobin.net/tiki-index.php?page=Boot+ESPRESSObin+from+SATA+drive&highlight=sata
suits for booting from microsd card, when it is flushed from zero
offset and boot selection switchs are set to 7.
At least, there is non-destructive way to check out u-boot image.
Double checked. Seems that microsd boot doesn't work and is not supported. At least for my V5 board. It just falls back to SPINOR
http://espressobin.net/forums/topic/how-to-flash-u-boot/
Alex
--
With best regards,
Matwey V. Kornilov
--
With best regards,
Matwey V. Kornilov
--
With best regards,
Matwey V. Kornilov
-- With best regards, Matwey V. Kornilov -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
-- With best regards, Matwey V. Kornilov
-- With best regards, Matwey V. Kornilov -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
2017-11-12 19:57 GMT+03:00 Matwey V. Kornilov <matwey.kornilov@gmail.com>:
2017-10-22 10:36 GMT+03:00 Matwey V. Kornilov <matwey.kornilov@gmail.com>:
2017-10-22 9:31 GMT+03:00 Rick Ashford <Rick.Ashford@suse.com>:
There is a great thread on the Armbian forum about the EspressoBin, and it helped me get things up and running with Tumbleweed.
One of the guys there has a public Dropbox link that includes their images for flashing the u-boot loader: https://www.dropbox.com/sh/kmgmo1uubhcczx5/AAAYEvTIFxpBr0dHG2QcapTza?dl=0
The thread: https://forum.armbian.com/index.php?/topic/4089-espressobin-support-development-efforts/&page=4
With their boot loader I was able to finally use BTRFS images as well as PXE boot. It also has an EFI load function in the help that I need to get around to trying.
Well, If armian u-boot is able to boot our standard EFI-Grub JeOS, then we can recommend to use it with openSUSE and don't reinvent the wheel.
Well, I've just managed to build marvell u-boot 2017.03-armada-17.10.1-g440395a and run it from SATA drive. I also started EFI grub using this bootloader. Also, it appeared that placing loader to LBA0 is not necessary, the loader can be placed to separate partition with 0x4d type.
Unfortunately, marvell u-boot config is only use tftp in bootcmd. So, I think the next step is to try upstream u-boot.
In upstream u-boot, sata/scsi doesn't work. And distro boot cmd is not integrated into upstream config.
Rick Ashford Sales Engineering Manager - West SUSE Linux rick.ashford@suse.com Office: 512-782-4318 Mobile: 512-731-3035
On Oct 21, 2017, at 12:32 PM, Matwey V. Kornilov <matwey.kornilov@gmail.com> wrote:
2017-10-21 19:47 GMT+03:00 Matwey V. Kornilov <matwey.kornilov@gmail.com>:
2017-10-21 19:35 GMT+03:00 Matwey V. Kornilov <matwey.kornilov@gmail.com>:
2017-10-20 18:02 GMT+03:00 Matwey V. Kornilov <matwey.kornilov@gmail.com>:
2017-10-20 17:37 GMT+03:00 Alexander Graf <agraf@suse.de>:
On 20.10.17 16:21, Matwey V. Kornilov wrote:
20.10.2017 17:12, Alexander Graf пишет:
On 20.10.17 13:57, Matwey V. Kornilov wrote:
Hi,
I've just received EspressoBin 1G. Any success stories how to run openSUSE?
I think you'll basically have to somehow flash a working U-Boot with
distro boot onto it and then just dd the tumbleweed/42.3 iso onto a usb
stick and cross your fingers that gets you to a point where you can
install :)
It has microsd card, I think it should be able to boot from sd, no?
I also need to to find serial console pins on the board :)
There seems to be a lengthy discussion on the mailing list. I guess you
can select the boot device using DIP switches though?
Yes, I can. I think it is preferred way. Need to find expected layout
to place u-boot image.
Well, at least while booting from SATA, they say that BootRom looks
for code starting with zero offset, which implies that there can not
be any GPT partition table.
Probably, it is similar for SD. If so, we need to flash our EFI-aware
u-boot instead of upstream one.
Well, SATA flash image from here
http://wiki.espressobin.net/tiki-index.php?page=Boot+ESPRESSObin+from+SATA+drive&highlight=sata
suits for booting from microsd card, when it is flushed from zero
offset and boot selection switchs are set to 7.
At least, there is non-destructive way to check out u-boot image.
Double checked. Seems that microsd boot doesn't work and is not supported. At least for my V5 board. It just falls back to SPINOR
http://espressobin.net/forums/topic/how-to-flash-u-boot/
Alex
--
With best regards,
Matwey V. Kornilov
--
With best regards,
Matwey V. Kornilov
--
With best regards,
Matwey V. Kornilov
-- With best regards, Matwey V. Kornilov -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
-- With best regards, Matwey V. Kornilov
-- With best regards, Matwey V. Kornilov
-- With best regards, Matwey V. Kornilov -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
Well, 4.13.12-1-default has issues with mmc-driver, so KIWI cannot find boot device. [ 9.651177] sdhci: Secure Digital Host Controller Interface driver [ 9.651182] sdhci: Copyright(c) Pierre Ossman [ 9.652213] sdhci-pltfm: SDHCI platform and OF driver helper [ 9.655798] xenon-sdhci d00d0000.sdhci: failed to get IRQ number [ 9.655809] xenon-sdhci d00d0000.sdhci: sdhci_pltfm_init failed -6 I will see, if different version of dtb file helps. -- With best regards, Matwey V. Kornilov -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
mSD card is enabled in kernel dtb file only in 4.14. https://github.com/torvalds/linux/commit/9be778f6c6d8f90ff2fad88d1770e2a7843... 2017-11-14 14:09 GMT+03:00 Matwey V. Kornilov <matwey.kornilov@gmail.com>:
Well, 4.13.12-1-default has issues with mmc-driver, so KIWI cannot find boot device.
[ 9.651177] sdhci: Secure Digital Host Controller Interface driver [ 9.651182] sdhci: Copyright(c) Pierre Ossman [ 9.652213] sdhci-pltfm: SDHCI platform and OF driver helper [ 9.655798] xenon-sdhci d00d0000.sdhci: failed to get IRQ number [ 9.655809] xenon-sdhci d00d0000.sdhci: sdhci_pltfm_init failed -6
I will see, if different version of dtb file helps.
-- With best regards, Matwey V. Kornilov
-- With best regards, Matwey V. Kornilov -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
Now It is booting. Now, I cannot figure out how to configure networking: 2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 532 link/ether 00:51:82:11:22:00 brd ff:ff:ff:ff:ff:ff inet6 fe80::251:82ff:fe11:2200/64 scope link valid_lft forever preferred_lft forever 3: wan@eth0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000 link/ether 00:51:82:11:22:00 brd ff:ff:ff:ff:ff:ff 4: lan0@eth0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000 link/ether 00:51:82:11:22:00 brd ff:ff:ff:ff:ff:ff 5: lan1@eth0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000 link/ether 00:51:82:11:22:00 brd ff:ff:ff:ff:ff:ff 2017-11-14 14:48 GMT+03:00 Matwey V. Kornilov <matwey.kornilov@gmail.com>:
mSD card is enabled in kernel dtb file only in 4.14.
https://github.com/torvalds/linux/commit/9be778f6c6d8f90ff2fad88d1770e2a7843...
2017-11-14 14:09 GMT+03:00 Matwey V. Kornilov <matwey.kornilov@gmail.com>:
Well, 4.13.12-1-default has issues with mmc-driver, so KIWI cannot find boot device.
[ 9.651177] sdhci: Secure Digital Host Controller Interface driver [ 9.651182] sdhci: Copyright(c) Pierre Ossman [ 9.652213] sdhci-pltfm: SDHCI platform and OF driver helper [ 9.655798] xenon-sdhci d00d0000.sdhci: failed to get IRQ number [ 9.655809] xenon-sdhci d00d0000.sdhci: sdhci_pltfm_init failed -6
I will see, if different version of dtb file helps.
-- With best regards, Matwey V. Kornilov
-- With best regards, Matwey V. Kornilov
-- With best regards, Matwey V. Kornilov -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
Hm. It refuses to boot after KIWI deployed. For some reason dracut-generated initrd failed to obtain /dev/mmcblk? devices. 14.11.2017 15:05, Matwey V. Kornilov пишет:
Now It is booting.
Now, I cannot figure out how to configure networking:
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 532 link/ether 00:51:82:11:22:00 brd ff:ff:ff:ff:ff:ff inet6 fe80::251:82ff:fe11:2200/64 scope link valid_lft forever preferred_lft forever 3: wan@eth0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000 link/ether 00:51:82:11:22:00 brd ff:ff:ff:ff:ff:ff 4: lan0@eth0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000 link/ether 00:51:82:11:22:00 brd ff:ff:ff:ff:ff:ff 5: lan1@eth0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000 link/ether 00:51:82:11:22:00 brd ff:ff:ff:ff:ff:ff
2017-11-14 14:48 GMT+03:00 Matwey V. Kornilov <matwey.kornilov@gmail.com>:
mSD card is enabled in kernel dtb file only in 4.14.
https://github.com/torvalds/linux/commit/9be778f6c6d8f90ff2fad88d1770e2a7843...
2017-11-14 14:09 GMT+03:00 Matwey V. Kornilov <matwey.kornilov@gmail.com>:
Well, 4.13.12-1-default has issues with mmc-driver, so KIWI cannot find boot device.
[ 9.651177] sdhci: Secure Digital Host Controller Interface driver [ 9.651182] sdhci: Copyright(c) Pierre Ossman [ 9.652213] sdhci-pltfm: SDHCI platform and OF driver helper [ 9.655798] xenon-sdhci d00d0000.sdhci: failed to get IRQ number [ 9.655809] xenon-sdhci d00d0000.sdhci: sdhci_pltfm_init failed -6
I will see, if different version of dtb file helps.
-- With best regards, Matwey V. Kornilov
-- With best regards, Matwey V. Kornilov
-- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
gpio_regulator has to be included into initrd to make mmc working. 25.11.2017 21:27, Matwey V. Kornilov пишет:
Hm. It refuses to boot after KIWI deployed. For some reason dracut-generated initrd failed to obtain /dev/mmcblk? devices.
14.11.2017 15:05, Matwey V. Kornilov пишет:
Now It is booting.
Now, I cannot figure out how to configure networking:
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 532 link/ether 00:51:82:11:22:00 brd ff:ff:ff:ff:ff:ff inet6 fe80::251:82ff:fe11:2200/64 scope link valid_lft forever preferred_lft forever 3: wan@eth0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000 link/ether 00:51:82:11:22:00 brd ff:ff:ff:ff:ff:ff 4: lan0@eth0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000 link/ether 00:51:82:11:22:00 brd ff:ff:ff:ff:ff:ff 5: lan1@eth0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000 link/ether 00:51:82:11:22:00 brd ff:ff:ff:ff:ff:ff
2017-11-14 14:48 GMT+03:00 Matwey V. Kornilov <matwey.kornilov@gmail.com>:
mSD card is enabled in kernel dtb file only in 4.14.
https://github.com/torvalds/linux/commit/9be778f6c6d8f90ff2fad88d1770e2a7843...
2017-11-14 14:09 GMT+03:00 Matwey V. Kornilov <matwey.kornilov@gmail.com>:
Well, 4.13.12-1-default has issues with mmc-driver, so KIWI cannot find boot device.
[ 9.651177] sdhci: Secure Digital Host Controller Interface driver [ 9.651182] sdhci: Copyright(c) Pierre Ossman [ 9.652213] sdhci-pltfm: SDHCI platform and OF driver helper [ 9.655798] xenon-sdhci d00d0000.sdhci: failed to get IRQ number [ 9.655809] xenon-sdhci d00d0000.sdhci: sdhci_pltfm_init failed -6
I will see, if different version of dtb file helps.
-- With best regards, Matwey V. Kornilov
-- With best regards, Matwey V. Kornilov
-- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
Currently, I have two issues. MAC addr are different after each reboot. Link auto-detection either not work or not supposed to work. 26.11.2017 15:46, Matwey V. Kornilov пишет:
gpio_regulator has to be included into initrd to make mmc working.
25.11.2017 21:27, Matwey V. Kornilov пишет:
Hm. It refuses to boot after KIWI deployed. For some reason dracut-generated initrd failed to obtain /dev/mmcblk? devices.
14.11.2017 15:05, Matwey V. Kornilov пишет:
Now It is booting.
Now, I cannot figure out how to configure networking:
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 532 link/ether 00:51:82:11:22:00 brd ff:ff:ff:ff:ff:ff inet6 fe80::251:82ff:fe11:2200/64 scope link valid_lft forever preferred_lft forever 3: wan@eth0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000 link/ether 00:51:82:11:22:00 brd ff:ff:ff:ff:ff:ff 4: lan0@eth0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000 link/ether 00:51:82:11:22:00 brd ff:ff:ff:ff:ff:ff 5: lan1@eth0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000 link/ether 00:51:82:11:22:00 brd ff:ff:ff:ff:ff:ff
2017-11-14 14:48 GMT+03:00 Matwey V. Kornilov <matwey.kornilov@gmail.com>:
mSD card is enabled in kernel dtb file only in 4.14.
https://github.com/torvalds/linux/commit/9be778f6c6d8f90ff2fad88d1770e2a7843...
2017-11-14 14:09 GMT+03:00 Matwey V. Kornilov <matwey.kornilov@gmail.com>:
Well, 4.13.12-1-default has issues with mmc-driver, so KIWI cannot find boot device.
[ 9.651177] sdhci: Secure Digital Host Controller Interface driver [ 9.651182] sdhci: Copyright(c) Pierre Ossman [ 9.652213] sdhci-pltfm: SDHCI platform and OF driver helper [ 9.655798] xenon-sdhci d00d0000.sdhci: failed to get IRQ number [ 9.655809] xenon-sdhci d00d0000.sdhci: sdhci_pltfm_init failed -6
I will see, if different version of dtb file helps.
-- With best regards, Matwey V. Kornilov
-- With best regards, Matwey V. Kornilov
-- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
Op zondag 26 november 2017 18:52:01 CET schreef Matwey V. Kornilov:
Currently, I have two issues. MAC addr are different after each reboot. Link auto-detection either not work or not supposed to work.
You can edit a file /etc/systemd/system/macspoof@.service with following content: [Unit] Description=MAC Address Change %I Wants=network-pre.target Before=network-pre.target BindsTo=sys-subsystem-net-devices-%i.device After=sys-subsystem-net-devices-%i.device [Service] Type=oneshot ExecStart=/usr/sbin/ip link set dev %i address <MAC_address> ExecStart=/usr/sbin/ip link set dev %i up [Install] WantedBy=multi-user.target -------------------- Where you enter a MAC address at <MAC_address> you saw previously. After that you give the command (on one line) in case the device name for the Ethernet device is eth0: ln -s /etc/systemd/system/macspoof@.service /mnt/ll/etc/systemd/system/multi- user.target.wants/macspoof@eth0.service -- fr.gr. Freek de Kruijf member openSUSE -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
On 27.11.2017 02:49, Freek de Kruijf wrote:
Op zondag 26 november 2017 18:52:01 CET schreef Matwey V. Kornilov:
Currently, I have two issues. MAC addr are different after each reboot. Link auto-detection either not work or not supposed to work.
You can edit a file /etc/systemd/system/macspoof@.service with following content: [Unit] Description=MAC Address Change %I Wants=network-pre.target Before=network-pre.target BindsTo=sys-subsystem-net-devices-%i.device After=sys-subsystem-net-devices-%i.device
[Service] Type=oneshot ExecStart=/usr/sbin/ip link set dev %i address <MAC_address> ExecStart=/usr/sbin/ip link set dev %i up
[Install] WantedBy=multi-user.target -------------------- Where you enter a MAC address at <MAC_address> you saw previously. After that you give the command (on one line) in case the device name for the Ethernet device is eth0: ln -s /etc/systemd/system/macspoof@.service /mnt/ll/etc/systemd/system/multi- user.target.wants/macspoof@eth0.service
It seems that MAC issue is related to u-boot. When I touch network commands in u-boot console, then MAC addr is set from ${ethaddr} variable, which is read from EEPROM (where it is a right place to store MAC actually). -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
participants (2)
-
Freek de Kruijf -
Matwey V. Kornilov