| 2013-03-04 19:05:52 |
vbooh |
bug |
|
|
added bug |
| 2013-03-04 19:05:52 |
vbooh |
attachment added |
|
network-interface.conf.patch https://bugs.launchpad.net/bugs/1144997/+attachment/3556920/+files/network-interface.conf.patch |
|
| 2013-03-04 20:18:47 |
Ubuntu Foundations Team Bug Bot |
tags |
|
patch |
|
| 2013-03-04 20:18:52 |
Ubuntu Foundations Team Bug Bot |
bug |
|
|
added subscriber Ubuntu Review Team |
| 2013-03-04 22:33:03 |
vbooh |
description |
Wi-Fi interfaces, that use configuration file /etc/network/interfaces and wpa_supplicant package, should be bring up after mounting /run, because wpa_supplicant uses /run mountpoint. In other case sometimes on boot Wi-Fi connection can be established properly, sometimes can not. |
Wi-Fi interfaces, that use configuration file /etc/network/interfaces and wpa_supplicant package, should be bring up after mounting /run, because wpa_supplicant uses /run mountpoint. In other case sometimes on boot Wi-Fi connection can be established properly, sometimes can not.
Proposed patch is not the best solution, but I can not get working solution with "mounted MOUNTPOINT=/run" instead of "filesystem". If I use "mounted MOUNTPOINT=/run", I do not get any errors messages using "initctl check-config" and "init-checkconf -d /etc/init/network-interface.conf", init just does not want start on boot, there is black screen after bootloader even without 'quite splash' kernel parameters and with '--debug' kernel parameter, there is no records in logs. |
|
| 2013-03-05 11:43:39 |
vbooh |
attachment added |
|
system_info.txt https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1144997/+attachment/3558100/+files/system_info.txt |
|
| 2013-03-05 11:52:51 |
vbooh |
description |
Wi-Fi interfaces, that use configuration file /etc/network/interfaces and wpa_supplicant package, should be bring up after mounting /run, because wpa_supplicant uses /run mountpoint. In other case sometimes on boot Wi-Fi connection can be established properly, sometimes can not.
Proposed patch is not the best solution, but I can not get working solution with "mounted MOUNTPOINT=/run" instead of "filesystem". If I use "mounted MOUNTPOINT=/run", I do not get any errors messages using "initctl check-config" and "init-checkconf -d /etc/init/network-interface.conf", init just does not want start on boot, there is black screen after bootloader even without 'quite splash' kernel parameters and with '--debug' kernel parameter, there is no records in logs. |
Wi-Fi interfaces, that use configuration file /etc/network/interfaces and wpa_supplicant package, should be bring up after mounting /run, because wpa_supplicant uses /run mountpoint. In other case sometimes on boot Wi-Fi connection can be established properly, sometimes can not. In logs I can see:
/var/log/upstart/network-interface-wlan0.log
mkdir[ctrl_interface]: No such file or directory
wpa_supplicant: /sbin/wpa_supplicant daemon failed to start
run-parts: /etc/network/if-pre-up.d/wpasupplicant exited with return code 1
Proposed patch is not the best solution, but I can not get working solution with "mounted MOUNTPOINT=/run" instead of "filesystem". If I use "mounted MOUNTPOINT=/run", I do not get any errors messages using "initctl check-config" and "init-checkconf -d /etc/init/network-interface.conf", init just does not want start on boot, there is black screen after bootloader even without 'quite splash' kernel parameters and with '--debug' kernel parameter, there is no records in logs.
Also there is another workaround or dirty hack, but it should not affect network filesystems mount, see attachment "network-interface.conf.workaround". |
|
| 2013-03-05 11:54:02 |
vbooh |
attachment added |
|
network-interface.conf.workaround https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1144997/+attachment/3558102/+files/network-interface.conf.workaround |
|
