------- Comment From [email protected] 2016-08-24 12:34 EDT------- Thanks very much vorlon and pitti. Pretty nice findings!
But...the issue still persists. I'll summarize the tests I made: 1) Firstly, I changed the link /usr/bin/readlink and, as vorlon predicted, this didn't solve the issue. 2) Then, independently of (1), I applied pitti's patch to xenial's "73 -usb-net-by-mac.rules" and...unfortunately it also didn't solve the issue. What impress me more is the difficult/interference of the simplest debug on the issue! After testing pitti's patch, still with the patch applied, I changed the start-udev load like this: (before) SYSTEMD_LOG_LEVEL=notice /lib/systemd/systemd-udevd --daemon --resolve-names=never (after my change) SYSTEMD_LOG_LEVEL=debug /lib/systemd/systemd-udevd --daemon --resolve-names=never --debug Well, the issue reproduced and I didn't see a single extra log message. After this, I kept both pitti's patch and this systemd debug parameter, but I booted with command-line "BOOT_DEBUG=1". Guess what? I was flooded by messages but the installer showed up. This is really weird for me...I'll attach a screen session of this last trial. I appreciate any suggestion you have to debug the issue further - by the way, using "net.ifnames=1" workarounds the issue too. Basically, any command-line option seems to solve it, even the simplest debug parameter. Thanks very much for the help and advice, Guilherme -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1615021 Title: Unable to network boot Ubuntu 16.04 installer normally on Briggs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/busybox/+bug/1615021/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
