I just installed arch on my Thinkpad t42p which has a ipw2100 wireless chip. I configured the whole network manually and a corresponding systemd entry. Sometimes the network comes up at boot at sometimes it doesn't. When it doesn't boot I still can start it manually with
# systemctl start network
Why could it be that it sometimes boots and sometimes it doesn't?
Last edited by dead_kenny (2012-11-10 08:35:03)
Thx for the link skunktrader. Now I fixed the matter by asining a udev rule to the network interfaces as described in the wiki.
Now I installed arch on an ASUS notebook where the interfaces don't shift during boot but there the network.service also won't boot. I have to start the service manually after boot. The output of
doesn't present the Network Connectivity until I start it manually. Could there be another reason for this? E.g. driver starts to late? How should I look for why systemd cannot start boot the network.service?
Now this is weird. The output of
$ systemctl status network.service
network.service - Network Connectivity
Loaded: loaded (/etc/systemd/system/network.service; enabled)
Active: inactive (dead)
Means it is loaded but inactive? Why does it load but not become active?
Last edited by dead_kenny (2012-11-16 07:43:04)