Arch Linux

hasardeur

Member

Registered: 2011-09-29

Posts: 17

[Solved] problems with device enumeration and autostart with systemd

Hello.
Yesterday I posted in the laptop section. In short, what I thought to be a driver issue seems to be a network and systemd problem. I have two NICs:

01:04.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ (rev 10)
	Subsystem: Mitac Device 8048
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
	Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 128 (8000ns min, 16000ns max)
	Interrupt: pin A routed to IRQ 20
	Region 0: I/O ports at c000 [size=256]
	Region 1: Memory at cc001000 (32-bit, non-prefetchable) [size=256]
	Capabilities: [50] Power Management version 2
		Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=375mA PME(D0-,D1+,D2+,D3hot+,D3cold+)
		Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
	Kernel driver in use: 8139too

01:05.0 Network controller: Intel Corporation PRO/Wireless 2200BG [Calexico2] Network Connection (rev 05)
	Subsystem: Intel Corporation Device 2701
	Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
	Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 128 (750ns min, 6000ns max)
	Interrupt: pin A routed to IRQ 21
	Region 0: Memory at cc000000 (32-bit, non-prefetchable) [size=4K]
	Capabilities: [dc] Power Management version 2
		Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0+,D1-,D2-,D3hot+,D3cold+)
		Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=1 PME-
	Kernel driver in use: ipw2200

I configured both with netcfg profiles: 1) ethernet-dhcp 2) wireless-wpa. Usually the wlan card is assigned eth0 and ethernet gets eth1. But these assignments randomly switch places, so it is impossible to autostart them via systemd. I have to edit both profiles time and time again to establish a connection. How can I "statically" assign a device name?

In advance, thank you for your time.

Last edited by hasardeur (2012-09-20 09:48:20)

Strike0

Member

From: Germany

Registered: 2011-09-05

Posts: 1,429

Re: [Solved] problems with device enumeration and autostart with systemd

Have a look, if that helps: https://wiki.archlinux.org/index.php/Ud … vice_names

hasardeur

Member

Registered: 2011-09-29

Posts: 17

Re: [Solved] problems with device enumeration and autostart with systemd

Yes, that was it. Sometimes I don't see what is right in front of me. The devices work as expected, thank you Strike0.

I have one question left. Now wifi and ethernet connection are established during boot (whenever possible). Is there a way to establish connections on demand? Is it possible to trigger the netcfg profile "ethernet-dhcp" when the cable is plugged in or "wireless-wpa" when in range?

tomk

Forum Fellow

From: Ireland

Registered: 2004-07-21

Posts: 9,839

Re: [Solved] problems with device enumeration and autostart with systemd

ifplugd and wpa_actiond, respectively, to be used with net-auto-wired and net-auto-wireless, provided by netcfg.

hasardeur

Member

Registered: 2011-09-29

Posts: 17

Re: [Solved] problems with device enumeration and autostart with systemd

Perfect. Works just fine.
On a side note, I don't quite get why the functionality is split that way. Speaking only for myself, it seems a bit counter intuitive to introduce "net-auto-wired" and "net-auto-wireless" instead of creating the option in "/etc/conf.d/netcfg" as review / editing is required anyway.
Be that as it may, now I get it and everything works. Thank you tomk.

tomk

Forum Fellow

From: Ireland

Registered: 2004-07-21

Posts: 9,839

Re: [Solved] problems with device enumeration and autostart with systemd

No problem.

If you disagree with the way it's implemented, feel free to submit feature requests, ideally with appropriate patches.