You are not logged in.

Pages: 1 2 3 4 5 6 7

Topic closed

#101 2013-02-08 07:42:08

jasonwryan
Anarchist
From: .nz
Registered: 2009-05-09
Posts: 30,424
Website

Re: New network naming schema in systemd 197

Merging with the stickied thread...

Arch + dwm   •   Mercurial repos  •   Surfraw

Registered Linux User #482438

Offline

#102 2013-02-08 13:48:19

nomorewindows
Member
Registered: 2010-04-03
Posts: 3,396

Re: New network naming schema in systemd 197

imbob wrote:

Hello, I've just installed arch and I was able to connect to the internet automatically via the boot disk, however after running the following commands on my newly built system (after reboot):

systemctl  enable dhcpcd@eth0.service
systemctl start dhcpcd@eth0.service

I got the following errors in journal

 
Timeout waiting for device sys-subsystem-net-devices-eth0.device.
Subject: Unit sys-subsystem-net-devices has failed.
Defined-By: systemd


The result is timeout.
Dependency failed for dhcpcd on eth0.
Subject: Unit dhcpcd@eth0.service has failed
Defined-By: systemd

Any ideas on what the dependency is and what I can do to solve it? Like I said, I was able to ping google from the bootdisk...

My guess is this is back to the step where you use ip link command to find out what interfaces you have.

I may have to CONSOLE you about your usage of ridiculously easy graphical interfaces...
Look ma, no mouse.

Offline

#103 2013-02-09 14:50:07

mloskot
Member
From: London, United Kingdom
Registered: 2012-06-01
Posts: 86
Website

Re: New network naming schema in systemd 197

Hi,

I have installed Arch on Asus Eee PC 901 and I'm experiencing
some problems with Wireless networking.

During the installation, I booted from USB pendrive, created partitions, filesysems, and followed all steps of typical Arch installation. I also used wifi-menu to get Wireless connectivity.
BTW, I also installed wireless_tools, netcft and wifi-menu in the chrooted system (one of the Eee PC wiki articles suggested that).
So, the installation went without any troubles.

The problem is that after reboot to the newly installed system, I can't get the wireless card working.
It loooks like the devices are somehow blocked, rmmod/modprobe of ath5k module does not help.

Here are details of the two configurations relevant to networking:

1) listed when I boot to live Arch from the USB pendrive
2) listed when I boot to the installed Arch


1) Live system

List of network devices:

# lspci -v
...
01:00.0 Ethernet controller: Atheros Communications Inc. AR242x / AR542x Wireless Network Adapter (PCI-Express) (rev 01)
	Subsystem: AzureWave AW-GE780 802.11bg Wireless Mini PCIe Card
	Physical Slot: eeepc-wifi
	Flags: bus master, fast devsel, latency 0, IRQ 19
	Memory at fbef0000 (64-bit, non-prefetchable) [size=64K]
	Capabilities: [40] Power Management version 2
	Capabilities: [50] MSI: Enable- Count=1/1 Maskable- 64bit-
	Capabilities: [60] Express Legacy Endpoint, MSI 00
	Capabilities: [90] MSI-X: Enable- Count=1 Masked-
	Capabilities: [100] Advanced Error Reporting
	Capabilities: [140] Virtual Channel
	Kernel driver in use: ath5k

04:00.0 Ethernet controller: Atheros Communications Inc. AR8121/AR8113/AR8114 Gigabit or Fast Ethernet (rev b0)
	Subsystem: ASUSTeK Computer Inc. Device 8324
	Flags: bus master, fast devsel, latency 0, IRQ 44
	Memory at fbfc0000 (64-bit, non-prefetchable) [size=256K]
	I/O ports at ec80 [size=128]
	Capabilities: [40] Power Management version 2
	Capabilities: [48] MSI: Enable+ Count=1/1 Maskable- 64bit+
	Capabilities: [58] Express Endpoint, MSI 00
	Capabilities: [6c] Vital Product Data
	Capabilities: [100] Advanced Error Reporting
	Capabilities: [180] Device Serial Number ff-1d-24-a7-00-24-8c-ff
	Kernel driver in use: ATL1E

List of kernel modules loaded:

# lsmod
Module                  Size  Used by
arc4                    1604  2 
option                 19805  0 
usb_wwan                7153  1 option
joydev                  7532  0 
usbserial              27050  2 option,usb_wwan
ath5k                 125273  0 
uvcvideo               63774  0 
snd_hda_codec_realtek    52725  1 
videobuf2_vmalloc       2217  1 uvcvideo
ath                    12382  1 ath5k
videobuf2_memops        2103  1 videobuf2_vmalloc
coretemp                5183  0 
iTCO_wdt                4316  0 
videobuf2_core         20913  1 uvcvideo
iTCO_vendor_support     1546  1 iTCO_wdt
mac80211              372648  1 ath5k
videodev               81821  2 uvcvideo,videobuf2_core
snd_hda_intel          23416  0 
media                   8578  2 uvcvideo,videodev
snd_hda_codec          86035  2 snd_hda_codec_realtek,snd_hda_intel
snd_hwdep               4843  1 snd_hda_codec
cfg80211              155615  3 ath,ath5k,mac80211
snd_pcm                63698  2 snd_hda_codec,snd_hda_intel
eeepc_laptop           12814  0 
microcode              11030  0 
snd_page_alloc          6039  2 snd_pcm,snd_hda_intel
acpi_cpufreq            9359  0 
snd_timer              14903  1 snd_pcm
lpc_ich                 9886  0 
mperf                   1024  1 acpi_cpufreq
sparse_keymap           2533  1 eeepc_laptop
snd                    45066  6 snd_hda_codec_realtek,snd_hwdep,snd_timer,snd_pcm,snd_hda_codec,snd_hda_intel
rfkill                 12849  2 cfg80211,eeepc_laptop
soundcore               4379  1 snd
pci_hotplug            20183  1 eeepc_laptop
i2c_i801               10417  0 
psmouse                76851  0 
thermal                 6886  0 
battery                 5691  0 
pcspkr                  1456  0 
processor              24552  1 acpi_cpufreq
ac                      1893  0 
serio_raw               4066  0 
evdev                   7657  5 
nfs                   109439  0 
lockd                  53983  1 nfs
sunrpc                158761  2 nfs,lockd
fscache                36588  1 nfs
ext4                  409085  2 
crc16                   1092  1 ext4
jbd2                   66480  1 ext4
mbcache                 4387  1 ext4
dm_snapshot            26611  2 
dm_mod                 61142  3 dm_snapshot
squashfs               34372  1 
loop                   14627  6 
isofs                  28554  1 
sd_mod                 28499  4 
ata_generic             2435  0 
pata_acpi               2400  0 
usb_storage            37273  1 
ata_piix               19705  1 
libata                147808  3 pata_acpi,ata_generic,ata_piix
uhci_hcd               21409  0 
i915                  467256  1 
scsi_mod              110426  3 usb_storage,libata,sd_mod
ehci_hcd               46061  0 
usbcore               148406  7 uhci_hcd,uvcvideo,usb_storage,usbserial,ehci_hcd,option,usb_wwan
usb_common               623  1 usbcore
i2c_algo_bit            4584  1 i915
drm_kms_helper         29071  1 i915
atl1e                  26716  0 
drm                   181744  2 i915,drm_kms_helper
intel_agp               8593  1 i915
intel_gtt              12001  3 i915,intel_agp
i2c_core               19184  6 drm,i915,i2c_i801,drm_kms_helper,i2c_algo_bit,videodev
agpgart                21936  3 drm,intel_agp,intel_gtt
video                   9932  1 i915
button                  3718  1 i915

Bits of dmesg output related to the newtorking devices:

# dmesg
...
[   13.215633] ath5k 0000:01:00.0: registered as 'phy0'
[   13.230888] input: USB 2.0 Camera as /devices/pci0000:00/0000:00:1d.7/usb1/1-8/1-8:1.0/input/input10
[   13.234000] usbcore: registered new interface driver uvcvideo
[   13.234008] USB Video Class driver (1.1.1)
[   13.306118] input: ETPS/2 Elantech Touchpad as /devices/platform/i8042/serio1/input/input11
[   13.314065] cfg80211: World regulatory domain updated:
[   13.314076] cfg80211:   (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
[   13.314085] cfg80211:   (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
[   13.314093] cfg80211:   (2457000 KHz - 2482000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
[   13.314100] cfg80211:   (2474000 KHz - 2494000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
[   13.314107] cfg80211:   (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
[   13.314115] cfg80211:   (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
[   13.384360] usbcore: registered new interface driver usbserial
[   13.385154] usbcore: registered new interface driver usbserial_generic
[   13.386645] usbserial: USB Serial support registered for generic
[   13.512641] usbcore: registered new interface driver option
[   13.513805] usbserial: USB Serial support registered for GSM modem (1-port)
[   13.514104] option 1-6:1.0: GSM modem (1-port) converter detected
[   13.514677] usb 1-6: GSM modem (1-port) converter now attached to ttyUSB0
[   13.514765] option 1-6:1.1: GSM modem (1-port) converter detected
[   13.515234] usb 1-6: GSM modem (1-port) converter now attached to ttyUSB1
[   13.515310] option 1-6:1.2: GSM modem (1-port) converter detected
[   13.515750] usb 1-6: GSM modem (1-port) converter now attached to ttyUSB2
[   13.953743] ath: EEPROM regdomain: 0x60
[   13.953753] ath: EEPROM indicates we should expect a direct regpair map
[   13.953763] ath: Country alpha2 being used: 00
[   13.953768] ath: Regpair used: 0x60
[   14.046354] ieee80211 phy0: Selected rate control algorithm 'minstrel_ht'
[   14.052341] Registered led device: ath5k-phy0::rx
[   14.052649] Registered led device: ath5k-phy0::tx
[   14.052687] ath5k: phy0: Atheros AR2425 chip found (MAC: 0xe2, PHY: 0x70)
[   14.061500] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[   14.359246] eeepc_laptop: TYPE (2000000) not reported by BIOS, enabling anyway
[   14.364368] eeepc_laptop: PANELPOWER (4000000) not reported by BIOS, enabling anyway
[   14.364382] eeepc_laptop: Get control methods supported: 0x6301711
[   14.371923] input: Asus EeePC extra buttons as /devices/platform/eeepc/input/input12
[   15.581618] eeepc_laptop: BIOS says wireless lan is unblocked, but the pci device is absent
[   15.581629] eeepc_laptop: skipped wireless hotplug as probably inappropriate for this model

2) Installed system

Now, when I boot to the installed Arch on this netbook, the corresponding output of the commands is this:

# lspci -v
...
01:00.0 Ethernet controller: Atheros Communications Inc. AR242x / AR542x Wireless Network Adapter (PCI-Express) (rev 01)
	Subsystem: AzureWave AW-GE780 802.11bg Wireless Mini PCIe Card
	Physical Slot: eeepc-wifi
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
	Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0, Cache Line Size: 32 bytes
	Interrupt: pin A routed to IRQ 19
	Region 0: Memory at fbef0000 (64-bit, non-prefetchable) [size=64K]
	Capabilities: [40] 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-
	Capabilities: [50] MSI: Enable- Count=1/1 Maskable- 64bit-
		Address: 00000000  Data: 0000
	Capabilities: [60] Express (v1) Legacy Endpoint, MSI 00
		DevCap:	MaxPayload 128 bytes, PhantFunc 0, Latency L0s <512ns, L1 <64us
			ExtTag- AttnBtn- AttnInd- PwrInd- RBE- FLReset-
		DevCtl:	Report errors: Correctable- Non-Fatal- Fatal- Unsupported-
			RlxdOrd+ ExtTag- PhantFunc- AuxPwr- NoSnoop-
			MaxPayload 128 bytes, MaxReadReq 512 bytes
		DevSta:	CorrErr- UncorrErr+ FatalErr- UnsuppReq+ AuxPwr- TransPend-
		LnkCap:	Port #0, Speed 2.5GT/s, Width x1, ASPM L0s L1, Latency L0 <512ns, L1 <64us
			ClockPM- Surprise- LLActRep- BwNot-
		LnkCtl:	ASPM Disabled; RCB 128 bytes Disabled- Retrain- CommClk+
			ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-
		LnkSta:	Speed 2.5GT/s, Width x1, TrErr- Train- SlotClk+ DLActive- BWMgmt- ABWMgmt-
	Capabilities: [90] MSI-X: Enable- Count=1 Masked-
		Vector table: BAR=0 offset=00000000
		PBA: BAR=0 offset=00000000
	Capabilities: [100 v1] Advanced Error Reporting
		UESta:	DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq+ ACSViol-
		UEMsk:	DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol-
		UESvrt:	DLP+ SDES- TLP- FCP+ CmpltTO- CmpltAbrt- UnxCmplt- RxOF+ MalfTLP+ ECRC- UnsupReq- ACSViol-
		CESta:	RxErr- BadTLP- BadDLLP- Rollover- Timeout- NonFatalErr-
		CEMsk:	RxErr- BadTLP- BadDLLP- Rollover- Timeout- NonFatalErr-
		AERCap:	First Error Pointer: 14, GenCap+ CGenEn- ChkCap+ ChkEn-
	Capabilities: [140 v1] Virtual Channel
		Caps:	LPEVC=0 RefClk=100ns PATEntryBits=1
		Arb:	Fixed- WRR32- WRR64- WRR128-
		Ctrl:	ArbSelect=Fixed
		Status:	InProgress-
		VC0:	Caps:	PATOffset=00 MaxTimeSlots=1 RejSnoopTrans-
			Arb:	Fixed- WRR32- WRR64- WRR128- TWRR128- WRR256-
			Ctrl:	Enable+ ID=0 ArbSelect=Fixed TC/VC=01
			Status:	NegoPending- InProgress-
	Kernel driver in use: ath5k

04:00.0 Ethernet controller: Atheros Communications Inc. AR8121/AR8113/AR8114 Gigabit or Fast Ethernet (rev b0)
	Subsystem: ASUSTeK Computer Inc. Device 8324
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
	Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0, Cache Line Size: 32 bytes
	Interrupt: pin A routed to IRQ 17
	Region 0: Memory at fbfc0000 (64-bit, non-prefetchable) [size=256K]
	Region 2: I/O ports at ec80 [size=128]
	Capabilities: [40] 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=0 PME-
	Capabilities: [48] MSI: Enable- Count=1/1 Maskable- 64bit+
		Address: 0000000000000000  Data: 0000
	Capabilities: [58] Express (v1) Endpoint, MSI 00
		DevCap:	MaxPayload 4096 bytes, PhantFunc 0, Latency L0s <4us, L1 unlimited
			ExtTag- AttnBtn+ AttnInd+ PwrInd+ RBE- FLReset-
		DevCtl:	Report errors: Correctable- Non-Fatal- Fatal- Unsupported-
			RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop-
			MaxPayload 128 bytes, MaxReadReq 512 bytes
		DevSta:	CorrErr- UncorrErr+ FatalErr- UnsuppReq+ AuxPwr+ TransPend-
		LnkCap:	Port #0, Speed 2.5GT/s, Width x1, ASPM L0s, Latency L0 unlimited, L1 unlimited
			ClockPM- Surprise- LLActRep- BwNot-
		LnkCtl:	ASPM Disabled; RCB 64 bytes Disabled- Retrain- CommClk+
			ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-
		LnkSta:	Speed 2.5GT/s, Width x1, TrErr- Train- SlotClk+ DLActive- BWMgmt- ABWMgmt-
	Capabilities: [6c] Vital Product Data
		Unknown small resource type 0b, will not decode more.
	Capabilities: [100 v1] Advanced Error Reporting
		UESta:	DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq+ ACSViol-
		UEMsk:	DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol-
		UESvrt:	DLP+ SDES- TLP- FCP+ CmpltTO- CmpltAbrt- UnxCmplt- RxOF+ MalfTLP+ ECRC- UnsupReq- ACSViol-
		CESta:	RxErr- BadTLP- BadDLLP- Rollover- Timeout- NonFatalErr-
		CEMsk:	RxErr- BadTLP- BadDLLP- Rollover- Timeout- NonFatalErr-
		AERCap:	First Error Pointer: 14, GenCap+ CGenEn- ChkCap+ ChkEn-
	Capabilities: [180 v1] Device Serial Number ff-1d-24-a7-00-24-8c-ff
	Kernel driver in use: ATL1E

List of modules:

# lsmod
Module                  Size  Used by
joydev                  7532  0 
arc4                    1604  2 
coretemp                5183  0 
uvcvideo               63774  0 
videobuf2_vmalloc       2217  1 uvcvideo
videobuf2_memops        2103  1 videobuf2_vmalloc
videobuf2_core         20913  1 uvcvideo
videodev               81821  2 uvcvideo,videobuf2_core
media                   8578  2 uvcvideo,videodev
i915                  467256  1 
iTCO_wdt                4316  0 
iTCO_vendor_support     1546  1 iTCO_wdt
option                 19805  0 
snd_hda_codec_realtek    52725  1 
usb_wwan                7153  1 option
usbserial              27050  2 option,usb_wwan
drm_kms_helper         29071  1 i915
ath5k                 125273  0 
ath                    12382  1 ath5k
snd_hda_intel          23416  0 
snd_hda_codec          86035  2 snd_hda_codec_realtek,snd_hda_intel
snd_hwdep               4843  1 snd_hda_codec
snd_pcm                63698  2 snd_hda_codec,snd_hda_intel
mac80211              372648  1 ath5k
snd_page_alloc          6039  2 snd_pcm,snd_hda_intel
drm                   181744  2 i915,drm_kms_helper
snd_timer              14903  1 snd_pcm
psmouse                76851  0 
intel_agp               8593  1 i915
snd                    45066  6 snd_hda_codec_realtek,snd_hwdep,snd_timer,snd_pcm,snd_hda_codec,snd_hda_intel
i2c_algo_bit            4584  1 i915
intel_gtt              12001  3 i915,intel_agp
microcode              11030  0 
cfg80211              155615  3 ath,ath5k,mac80211
soundcore               4379  1 snd
lpc_ich                 9886  0 
evdev                   7657  5 
serio_raw               4066  0 
agpgart                21936  3 drm,intel_agp,intel_gtt
atl1e                  26716  0 
i2c_i801               10417  0 
pcspkr                  1456  0 
i2c_core               19184  6 drm,i915,i2c_i801,drm_kms_helper,i2c_algo_bit,videodev
thermal                 6886  0 
battery                 5691  0 
video                   9932  1 i915
eeepc_laptop           12814  0 
sparse_keymap           2533  1 eeepc_laptop
ac                      1893  0 
rfkill                 12849  2 cfg80211,eeepc_laptop
acpi_cpufreq            9359  0 
mperf                   1024  1 acpi_cpufreq
pci_hotplug            20183  1 eeepc_laptop
processor              24552  1 acpi_cpufreq
button                  3718  1 i915
usb_storage            37273  1 
ext4                  409085  2 
crc16                   1092  1 ext4
jbd2                   66480  1 ext4
mbcache                 4387  1 ext4
sd_mod                 28499  4 
ata_generic             2435  0 
pata_acpi               2400  0 
ata_piix               19705  1 
uhci_hcd               21409  0 
libata                147808  3 pata_acpi,ata_generic,ata_piix
ehci_hcd               46061  0 
scsi_mod              110426  3 usb_storage,libata,sd_mod
usbcore               148406  7 uhci_hcd,uvcvideo,usb_storage,usbserial,ehci_hcd,option,usb_wwan
usb_common               623  1 usbcore

and the relevant dmesg messages:

[    2.363706] ath5k 0000:01:00.0: registered as 'phy0'
[    2.383796] usbcore: registered new interface driver usbserial
[    2.383858] usbcore: registered new interface driver usbserial_generic
[    2.383912] usbserial: USB Serial support registered for generic
[    2.406224] input: HDA Digital PCBeep as /devices/pci0000:00/0000:00:1b.0/input/input7
[    2.412680] usbcore: registered new interface driver option
[    2.412825] usbserial: USB Serial support registered for GSM modem (1-port)
[    2.413302] option 1-6:1.0: GSM modem (1-port) converter detected
[    2.418339] usb 1-6: GSM modem (1-port) converter now attached to ttyUSB0
[    2.418911] option 1-6:1.1: GSM modem (1-port) converter detected
[    2.420418] usb 1-6: GSM modem (1-port) converter now attached to ttyUSB1
[    2.420918] option 1-6:1.2: GSM modem (1-port) converter detected
[    2.422970] usb 1-6: GSM modem (1-port) converter now attached to ttyUSB2
[    2.443802] iTCO_vendor_support: vendor-support=0
[    2.450934] iTCO_wdt: Intel TCO WatchDog Timer Driver v1.10
[    2.451007] iTCO_wdt: Found a ICH7-M or ICH7-U TCO device (Version=2, TCOBASE=0x0860)
[    2.459128] iTCO_wdt: initialized. heartbeat=30 sec (nowayout=0)
[    2.467319] input: HDA Intel Mic as /devices/pci0000:00/0000:00:1b.0/sound/card0/input8
[    2.470718] input: HDA Intel Headphone as /devices/pci0000:00/0000:00:1b.0/sound/card0/input9
[    2.493576] microcode: CPU1 sig=0x106c2, pf=0x4, revision=0x212
[    2.507047] systemd-udevd[141]: renamed network interface eth0 to enp4s0
[    2.514022] media: Linux media interface: v0.10
[    2.518894] checking generic (d0000000 1e0000) vs hw (d0000000 10000000)
...
[    2.996535] ath: EEPROM regdomain: 0x60
[    2.996537] ath: EEPROM indicates we should expect a direct regpair map
[    2.996542] ath: Country alpha2 being used: 00
[    2.996543] ath: Regpair used: 0x60
[    3.129392] psmouse serio1: elantech: assuming hardware version 2 (with firmware version 0x020030)
[    3.200191] psmouse serio1: elantech: Synaptics capabilities query result 0x00, 0x02, 0x64.
...
[    3.327100] ieee80211 phy0: Selected rate control algorithm 'minstrel_ht'
[    3.327914] Registered led device: ath5k-phy0::rx
[    3.328054] Registered led device: ath5k-phy0::tx
[    3.328087] ath5k: phy0: Atheros AR2425 chip found (MAC: 0xe2, PHY: 0x70)
...
[    3.387054] systemd-udevd[136]: renamed network interface wlan0 to wlp1s0
...
[    4.010299] eeepc_laptop: TYPE (2000000) not reported by BIOS, enabling anyway
[    4.016026] eeepc_laptop: PANELPOWER (4000000) not reported by BIOS, enabling anyway
[    4.016047] eeepc_laptop: Get control methods supported: 0x6301711
[    4.020477] input: Asus EeePC extra buttons as /devices/platform/eeepc/input/input12
[    5.230163] eeepc_laptop: BIOS says wireless lan is unblocked, but the pci device is absent
[    5.230181] eeepc_laptop: skipped wireless hotplug as probably inappropriate for this model

I have noticed some differences between these two configurations that seems to be relevant to the problem.
For example, in dmesg messages I see some messages about wlan0, the 1) shows:

[   14.061500] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready

whereas the configuration 2) shows:

[    3.387054] systemd-udevd[136]: renamed network interface wlan0 to wlp1s0

I searched the Web a lot trying to figure out what's the problem and many articles mention use of rfkill.
For example, all these seem to be direclty related to my problem:

Netcfg Tips wiki on Eee PC

Wireless network stopped working after updating to gnome3 thread

AcerAspire 3500 ath5k rfkill hard block

Interestingly, there is no rfkill command available on the installed system with configuration 2),
although the rfkill module is loaded. I'm curious why the installer skipped the rfkill.

On the live system 1), I see /etc/conf.d/rfkill file which is missing from the installed system 2):

# /etc/conf.d/rfkill
# Configuration for the rfkill startup script
#

# List of devices to block on startup (space-separated)
RFKILL_BLOCK=""

# List of devices to unblock on startup (space-separated)
RFKILL_UNBLOCK="all"

Is that possible the missing or incomplete rfkill setup on the installed system 2) is the root of the problem?

I have tried to juggle the ath5k (wireless) and atl1e (ethernet) modules manuall to see if there is
any difference. I also played with hardware switching of WiFi on the Eee PC.
I always see the same message in dmesg: renamed network interface wlan0 to wlp1s0.

Unfortunately, web searching does not give anything useful about the wlp1s0.

If I need the rfkill installed indeed, can I do it by booting to live Arch
then arch-chroot the root partition, and pacman missing packages?
Is that enough?

I'd be thankful for any help in solving this mystery and helping me to get the WiFi working.

Mateusz Loskot | github | archlinux-config
Arch (x86-64) | ThinkPad T400  | Intel P8600| Intel i915
Arch (x86-64) | ThinkPad W700 | Intel T9600 | NVIDIA Quadro FX 2700M

Offline

#104 2013-02-09 15:03:12

headkase
Member
Registered: 2011-12-06
Posts: 1,983

Re: New network naming schema in systemd 197

Systemd has brought about new behaviour.  It will rename your network interfaces while booting.  Just use the renamed interface it gives you.  The reason it now does this is because of race conditions when naming interfaces.  Previously interfaces weren't guaranteed to always get the same names.  With the new systemd behaviour an adapter interface will always receive the same name even if you change the hardware configuration of the computer.  So, short: just use the name systemd gives you as part of the boot process.

Offline

#105 2013-02-09 16:42:36

DSpider
Member
From: Romania
Registered: 2009-08-23
Posts: 2,273

Re: New network naming schema in systemd 197

https://wiki.archlinux.org/index.php/Be … e#Wireless

If you're coming from another distribution, or if this is your first time installing Arch Linux since the deprecation of the old interface naming scheme, you might be surprised to learn that the first wireless interface is not named "wlan0". In fact, none of the interfaces are automatically prefixed with "wlan" any longer. Don't panic; simply execute iwconfig to discover the name of your wireless interface.

Warning: At the moment, netcfg's wifi-menu, when executed without arguments, will look for "wlan0". Execute wifi-menu with your interface as the argument in order to use it.

Last edited by DSpider (2013-02-09 16:44:43)

"How to Succeed with Linux"

I have made a personal commitment not to reply in topics that start with a lowercase letter. Proper grammar and punctuation is a sign of respect, and if you do not show any, you will NOT receive any help (at least not from me).

Offline

#106 2013-02-09 19:08:02

jasonwryan
Anarchist
From: .nz
Registered: 2009-05-09
Posts: 30,424
Website

Re: New network naming schema in systemd 197

Merging with the stickied thread...

Arch + dwm   •   Mercurial repos  •   Surfraw

Registered Linux User #482438

Offline

#107 2013-02-10 02:50:05

mloskot
Member
From: London, United Kingdom
Registered: 2012-06-01
Posts: 86
Website

Re: New network naming schema in systemd 197

headkase wrote:

Systemd has brought about new behaviour.  It will rename your network interfaces while booting. (...) So, short: just use the name systemd gives you as part of the boot process.

Thanks for the explanation. If I only had linked my problem to the new features of systemd, I would have not contributed to this growing thread smile

DSpider wrote:

My lesson learned: keep coming back to wiki, pages get updated often!

The problem is solved for me and 

wifi-menu wlp1s0

works like a charm.

Thanks!

Mateusz Loskot | github | archlinux-config
Arch (x86-64) | ThinkPad T400  | Intel P8600| Intel i915
Arch (x86-64) | ThinkPad W700 | Intel T9600 | NVIDIA Quadro FX 2700M

Offline

#108 2013-02-10 19:10:57

jorants
Member
Registered: 2013-01-25
Posts: 7

Re: New network naming schema in systemd 197

Hey,

I just did a fresh install on my server (previosly debian) and a can't get my internet working, my network cards don't even show.
if i type "ip addr" is get:

1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
    inet6 ::1/128 scope host
       valid_lft forever preferred_lft forever

And "lspci -v" gives: (after some cleanup)

00:0a.0 Ethernet controller: NVIDIA Corporation MCP67 Ethernet (rev a2)
    Subsystem: ASUSTeK Computer Inc. Device 82b3
    Flags: bus master, 66MHz, fast devsel, latency 0, IRQ 21
    Memory at fe9fc000 (32-bit, non-prefetchable) [size=4K]
    I/O ports at b880 [size=8]
    Memory at fe9fe400 (32-bit, non-prefetchable) [size=256]
    Memory at fe9fe000 (32-bit, non-prefetchable) [size=16]
    Capabilities: [44] Power Management version 2
    Capabilities: [50] MSI: Enable- Count=1/8 Maskable+ 64bit+
    Capabilities: [6c] HyperTransport: MSI Mapping Enable- Fixed+
    Kernel driver in use: forcedeth

01:07.0 Ethernet controller: 3Com Corporation 3c905C-TX/TX-M [Tornado] (rev 74)
    Subsystem: 3Com Corporation 3C905CX-TX/TX-M Fast Etherlink for PC Management NIC
    Flags: bus master, medium devsel, latency 64, IRQ 19
    I/O ports at dc00 [size=128]
    Memory at feaffc00 (32-bit, non-prefetchable) [size=128]
    Expansion ROM at feac0000 [disabled] [size=128K]
    Capabilities: [dc] Power Management version 2
    Kernel driver in use: 3c59x

i'm realy stuck on this one :-S
maby usefull: when i installed the system fstab was not well generated so my root was readonly, but i was able to fix that.

hope you can help,

Joran

Offline

#109 2013-02-10 19:39:41

karol
Archivist
Registered: 2009-05-06
Posts: 25,440

Re: New network naming schema in systemd 197

https://bbs.archlinux.org/viewtopic.php?id=156283 ?

Offline

#110 2013-02-10 19:40:10

jasonwryan
Anarchist
From: .nz
Registered: 2009-05-09
Posts: 30,424
Website

Re: New network naming schema in systemd 197

Merging with the stickied thread directly above this...

Arch + dwm   •   Mercurial repos  •   Surfraw

Registered Linux User #482438

Offline

#111 2013-02-12 22:18:36

joaowojwicz
Member
Registered: 2013-02-12
Posts: 11

Re: New network naming schema in systemd 197

Hello arch community,

I always used arch linux, but a while ago I decided to fresh install it again, to get rid of a lot of crap, like useless files and libraries, bad programs and a lot of other junk. So I grabbed my disc and reinstalled following the official arch installation guide (I have always followed it to not screw things up), but after the installation, I can't connect to the internet. I have reinstalled arch a lot and yet installed on another computer (desktop), but still the same thing happened.
When I try to connect via wifi-menu, I got no wlan0 device message.

I tried various solutions but none of them worked for me. Any ideas?

Offline

#112 2013-02-12 22:21:05

skanky
Member
From: WAIS
Registered: 2009-10-23
Posts: 1,847

Re: New network naming schema in systemd 197

https://bbs.archlinux.org/viewtopic.php?id=156283

"...one cannot be angry when one looks at a penguin."  - John Ruskin
"Life in general is a bit shit, and so too is the internet. And that's all there is." - scepticisle

Offline

#113 2013-02-12 22:24:51

jasonwryan
Anarchist
From: .nz
Registered: 2009-05-09
Posts: 30,424
Website

Re: New network naming schema in systemd 197

Merging with the stickied thread skanky linked to...

Arch + dwm   •   Mercurial repos  •   Surfraw

Registered Linux User #482438

Offline

#114 2013-02-13 00:39:23

Darkgod
Member
Registered: 2012-11-12
Posts: 7

Re: New network naming schema in systemd 197

After installing Arch from scratch using the 2013-02-01 image my system boots fine but without any network.  I've tried everything I can think of still to no end... systemctl enable dhcpcd@eth0.service was used during install.  They system was running fine but I had a HDD failure so I know the NIC is good because it connects fine when I boot up the image.  Any thoughts on what this could be?


Thanks for any help

Offline

#115 2013-02-13 00:44:19

WonderWoofy
Member
From: Los Gatos, CA
Registered: 2012-05-19
Posts: 8,414

Re: New network naming schema in systemd 197

Darkgod, please search the forums before posting. You will find your answer... over and over and over again.

Offline

#116 2013-02-13 00:45:02

jasonwryan
Anarchist
From: .nz
Registered: 2009-05-09
Posts: 30,424
Website

Re: New network naming schema in systemd 197

Merging with the stickied thread...

Arch + dwm   •   Mercurial repos  •   Surfraw

Registered Linux User #482438

Offline

#117 2013-02-13 01:15:14

Darkgod
Member
Registered: 2012-11-12
Posts: 7

Re: New network naming schema in systemd 197

WonderWoofy wrote:

Darkgod, please search the forums before posting. You will find your answer... over and over and over again.

Yeah Sorry, I was in a panic because I have a paper do in 2days... I normally search hard before I post but I wasn't using a good enough search string... Right after I posted I found the post that explained everything.

Last edited by Darkgod (2013-02-13 01:15:26)

Offline

#118 2013-02-13 13:01:11

ripread
Member
Registered: 2013-02-13
Posts: 6

Re: New network naming schema in systemd 197

I'm a brand new Arch user, but I have wetted my feet with Ubuntu before. I did a brand new install of arch yesterday following this guide

Because I'm using only a wired connection with a dynamic ip I enabled the dhcpcd service with the command 

# systemctl enable dhcpcd@eth0.service

but when I reboot and login I am not connected to my network and 

# ping -c 3 www.google.com

returns an unknown host error

and when I attempt to enable eth0 manually with 

# sudo dhcpcd eth0

it returns eth0: interface not found or invalid. Believing it to be a bad install I wiped the partitions and reinstalled, this time using ifplugd alternateive method found in the guide.

#pacman -S ifplugd
# cd /etc/network.d
# ln -s examples/ethernet-dhcp .
# systemctl enable net-auto-wired.service

but I have the same problem and receive the same errors

I then attempted a solution I found on a forum post from 2009

# lspci | grep Eth
00:0a.0 Ethernet controller: nVidia Corporation MCP78S [GeForce 8200] Ethernet (rev a2)
07:00.0 Ethernet controller: Atheros Communications Inc. AR242x 802.11abg Wireless PCI Express Adapter (rev 01)
# lspci -s 00:0a.0 -n
00:0a.0 0200: 10de:0760 (rev a2)
# grep  -e '10de.*0760' /lib/modules/`uname -r`/modules.pcimap
forcedeth            0x000010de 0x00000760 0xffffffff 0xffffffff 0x00000000 0x00000000 0x0

however 

# grep  -e '10de:0760' /lib/modules/`uname -r`/modules.pcimap

returned a no such file or directory error on the path  /lib/modules/3.7.7-1-ARCH/modules.pcimap  (yes, I did substitute my Ethernet controller for the examples')

Both the ifconfig and rc.conf commands are not found (I believe because I have not installed them yet) and I am using the newest release (2013.02.01)

Last edited by ripread (2013-02-13 13:06:38)

Offline

#119 2013-02-13 13:07:24

Trilby
Inspector Parrot
Registered: 2011-11-29
Posts: 30,237
Website

Re: New network naming schema in systemd 197

Welcome to archlinux.  Please make sure to do your own searches before posting new issues.  This particular issue has been covered ad naseum over the past month.  There is a stickied thread in the forums dedicated to this change.  And there is a big red highlighted box in the very same wiki page you said you followed: https://wiki.archlinux.org/index.php/Be … connectionThe whole netowrking section of that wiki page elaborates on this in detail.

Last edited by Trilby (2013-02-13 13:08:51)

"UNIX is simple and coherent" - Dennis Ritchie; "GNU's Not Unix" - Richard Stallman

Offline

#120 2013-02-13 17:18:57

jasonwryan
Anarchist
From: .nz
Registered: 2009-05-09
Posts: 30,424
Website

Re: New network naming schema in systemd 197

As Trilby has pointed out: this is covered in the thread into which I am merging this...

Arch + dwm   •   Mercurial repos  •   Surfraw

Registered Linux User #482438

Offline

#121 2013-02-16 00:15:07

joaowojwicz
Member
Registered: 2013-02-12
Posts: 11

Re: New network naming schema in systemd 197

hello, I have read this new naming for those devices now and I do have both when I type ip link. Basically I got:
1:lo
2:enp5s0
3:wlp9s0

2 and 3 down.

But I can`t connect to wlp9s0, and when I type ip link set wlp9s0 up, I got:

RTNETLINK  answers: Operation not possible due to RF-kill

so wifi-menu wlp9s0 can`t connect to my network, saying Interface unavailable.

However, enp5s0 works when I set it up and enable dhcpcd service.


What can I do to connect via wifi?

Offline

#122 2013-02-16 01:54:21

jasonwryan
Anarchist
From: .nz
Registered: 2009-05-09
Posts: 30,424
Website

Re: New network naming schema in systemd 197

This is unrelated to the current issue, please don't hijack threads:
https://wiki.archlinux.org/index.php/Fo … _Hijacking

What has searching told you? Toggle the kill switch and bring the interface up...
If that doesn't work, open a new thread and include all of the steps you have tried and any relevant error messages.

Arch + dwm   •   Mercurial repos  •   Surfraw

Registered Linux User #482438

Offline

#123 2013-02-17 16:43:00

mcloaked
Member
From: Yorkshire, UK
Registered: 2012-02-02
Posts: 1,273

Re: New network naming schema in systemd 197

Trilby wrote:

Welcome to archlinux.  Please make sure to do your own searches before posting new issues.  This particular issue has been covered ad naseum over the past month.  There is a stickied thread in the forums dedicated to this change.  And there is a big red highlighted box in the very same wiki page you said you followed: https://wiki.archlinux.org/index.php/Be … connectionThe whole netowrking section of that wiki page elaborates on this in detail.

Is it worth adding a cautionary warning/link in the wiki Beginner's Guide for the case where there is more than one wired ethernet NIC in the motherboard?  I have had quite a few issues with this until I read the details at https://wiki.archlinux.org/index.php/Ud … ork_device - even experienced linux users can be caught out by that issue (I have been using linux exclusively for a decade!)

Last edited by mcloaked (2013-02-17 16:43:25)

Mike C

Offline

#124 2013-02-18 19:35:03

jtag1458
Member
Registered: 2013-02-18
Posts: 9

Re: New network naming schema in systemd 197

Hello.

I have seen a few other posts regarding this issue, but none of them have resolved my problem. I have used linux for a while (Ubuntu/Debian, Fedora, Opensuse), and I really want to use Arch. I followed an instalation guide from http://lifehacker.com/5680453/build-a-k … he-process and everything went smooth, except that my internet was not working when I rebooted. Everything I know isn't working.

(ifconfig) - command not found, (rc.d)- command not found (ip link set eth0 up) - cannot find device 'eth0'

Maybe somebody else knows whats up?

Offline

#125 2013-02-18 19:37:12

WorMzy
Administrator
From: Scotland
Registered: 2010-06-16
Posts: 12,328
Website

Re: New network naming schema in systemd 197

There's a stickied topic in the network subforum all about the new networking device naming system, did you read that?

Sakura:-
Mobo: MSI MAG X570S TORPEDO MAX // Processor: AMD Ryzen 9 5950X @4.9GHz // GFX: AMD Radeon RX 5700 XT // RAM: 32GB (4x 8GB) Corsair DDR4 (@ 3000MHz) // Storage: 1x 3TB HDD, 6x 1TB SSD, 2x 120GB SSD, 1x 275GB M2 SSD

Making lemonade from lemons since 2015.

Offline

Pages: 1 2 3 4 5 6 7

Topic closed

Board footer

Powered by FluxBB