[solved] netcfg fails only on reconnect

Hi there,
I am running system.d and I am able to start netcfg once. Netcfg reconnect fails, as well as attempting to connect a second time when e.g. network was not available on first attempt. Normally I start netcfg on boot, and if it fails I am not able to try a connection manually. Basically it means I have only one try to connect to a wireless network before reboot.
I first thought it might be related to https://bbs.archlinux.org/viewtopic.php?id=151662 but I could not help myself.
Here is the output when netcfg is disabled in systemd.
ᐅ sudo netcfg mynetwork
[sudo] password for kodiak:
:: mynetwork up [DONE]
sudo netcfg down mynetwork
:: mynetwork down [DONE]
ᐅ sudo netcfg mynetwork
:: mynetwork up [BUSY]
ctrl_iface exists and seems to be in use - cannot override it
Delete '/var/run/wpa_supplicant/wlan0' manually if it is not used anymore
Failed to initialize control interface 'DIR=/var/run/wpa_supplicant GROUP=users'.
You may have another wpa_supplicant process already running or the file was
left by an unclean termination of wpa_supplicant in which case you will need
to manually remove this file before starting wpa_supplicant again.
> wpa_supplicant did not start, possible configuration error
[FAIL]
ᐅ sudo rm /var/run/wpa_supplicant/wlan0
ᐅ sudo netcfg mynetwork
:: mynetwork up [BUSY]
> WPA Authentication/Association Failed
Configuration:
ᐅ cat /etc/network.d/mynetwork
CONNECTION='wireless'
DESCRIPTION='A wpa_supplicant configuration based wireless connection'
INTERFACE='wlan0'
SECURITY='wpa-config'
WPA_CONF='/etc/wpa_supplicant.conf'
IP='dhcp'
# Uncomment this if your ssid is hidden
#HIDDEN=yes
ᐅ cat /etc/wpa_supplicant.conf
ctrl_interface=DIR=/var/run/wpa_supplicant GROUP=users
network={
ssid="WLAN1"
psk="PASSWD"
network={
ssid="WLAN2"
psk=PASSWD
network={
ssid="WLAN3"
psk="PASSWD"
ᐅ yaourt -Ss netcfg
core/netcfg 3.0-1 (base) [installed]
ᐅ lsmod
Module Size Used by
fuse 60479 2
btusb 10369 0
gspca_sn9c20x 25911 0
gspca_main 18645 1 gspca_sn9c20x
videodev 79257 2 gspca_sn9c20x,gspca_main
bluetooth 168947 2 btusb
crc16 1092 1 bluetooth
iTCO_wdt 4316 0
iTCO_vendor_support 1546 1 iTCO_wdt
media 8546 1 videodev
radeon 788285 2
arc4 1604 2
thinkpad_acpi 54674 0
ttm 46988 1 radeon
iwl3945 47929 0
drm_kms_helper 28942 1 radeon
iwlegacy 41403 1 iwl3945
drm 180117 4 ttm,drm_kms_helper,radeon
mac80211 367308 2 iwl3945,iwlegacy
cfg80211 153457 3 iwl3945,iwlegacy,mac80211
snd_hda_codec_analog 62229 1
lpc_ich 9214 0
nvram 4795 1 thinkpad_acpi
i2c_algo_bit 4584 1 radeon
tpm_tis 7155 0
coretemp 4959 0
joydev 7696 0
kvm_intel 117536 0
snd_hda_intel 22257 2
acpi_cpufreq 5142 1
mperf 1024 1 acpi_cpufreq
rfkill 12569 4 cfg80211,thinkpad_acpi,bluetooth
pcmcia 31186 0
tpm 11958 1 tpm_tis
tg3 126080 0
snd_hda_codec 83678 2 snd_hda_intel,snd_hda_codec_analog
snd_hwdep 4843 1 snd_hda_codec
snd_pcm 61958 2 snd_hda_codec,snd_hda_intel
snd_page_alloc 5902 2 snd_pcm,snd_hda_intel
snd_timer 14903 1 snd_pcm
intel_agp 8593 0
tpm_bios 4262 1 tpm
psmouse 71891 0
intel_gtt 12212 1 intel_agp
agpgart 21936 4 drm,ttm,intel_agp,intel_gtt
i2c_i801 8464 0
snd 45098 11 snd_hwdep,snd_timer,snd_pcm,snd_hda_codec,snd_hda_intel,thinkpad_acpi,snd_hda_codec_analog
battery 5214 0
kvm 324233 1 kvm_intel
soundcore 4379 1 snd
ac 1893 0
video 9885 0
serio_raw 3714 0
processor 24040 3 acpi_cpufreq
thermal 6660 0
button 3711 0
libphy 17294 1 tg3
yenta_socket 18841 0
pcmcia_rsrc 8809 1 yenta_socket
i2c_core 16944 6 drm,i2c_i801,drm_kms_helper,i2c_algo_bit,radeon,videodev
evdev 7663 14
pcmcia_core 10242 3 pcmcia,pcmcia_rsrc,yenta_socket
pcspkr 1456 0
microcode 8922 0
vboxdrv 222106 0
btrfs 705337 1
crc32c 1277 1
libcrc32c 715 1 btrfs
zlib_deflate 18101 1 btrfs
sr_mod 13149 0
sd_mod 27312 2
cdrom 30345 1 sr_mod
ata_generic 2435 0
pata_acpi 2400 0
uhci_hcd 19841 0
ata_piix 19705 1
libata 146129 3 pata_acpi,ata_generic,ata_piix
scsi_mod 113073 3 libata,sd_mod,sr_mod
sdhci_pci 8878 0
sdhci 20459 1 sdhci_pci
tifm_7xx1 3575 0
mmc_core 73455 2 sdhci,sdhci_pci
firewire_ohci 27535 0
tifm_core 3890 1 tifm_7xx1
firewire_core 45541 1 firewire_ohci
crc_itu_t 1096 1 firewire_core
ehci_hcd 36685 0
usbcore 126796 5 gspca_sn9c20x,btusb,uhci_hcd,ehci_hcd,gspca_main
usb_common 623 1 usbcore
ᐅ cat /usr/lib/systemd/system/netcfg.service
[Unit]
Description=Netcfg multi-profile daemon
Before=network.target
Wants=network.target
After=sys-devices-pci0000:00-0000:00:1c.1-0000:03:00.0-net-wlan0.device
BindTo=sys-devices-pci0000:00-0000:00:1c.1-0000:03:00.0-net-wlan0.device
[Service]
Type=oneshot
RemainAfterExit=yes
ExecStart=/usr/bin/netcfg-daemon start
ExecStop=/usr/bin/netcfg-daemon stop
KillMode=none
[Install]
WantedBy=multi-user.target
ᐅ 0.status net-auto-wireless
net-auto-wireless.service - Provides automatic netcfg wireless connection
Loaded: loaded (/usr/lib/systemd/system/net-auto-wireless.service; disabled)
Active: inactive (dead)
CGroup: name=systemd:/system/net-auto-wireless.service
ᐅ 0.status net-auto-wired
net-auto-wired.service - Provides automatic netcfg wired connection
Loaded: loaded (/usr/lib/systemd/system/net-auto-wired.service; disabled)
Active: inactive (dead)
CGroup: name=systemd:/system/net-auto-wired.service
I noticed that behaviour after I switched over to systemd, with initscripts it did run fine.
Last edited by kodiak (2013-01-05 16:29:39)

Ok, finaly I got it working - first time with systemd. Things I changed:
1. in wpa_supplicant.conf I updated from '/var/run' to '/run' and added 'fast_reauth=1' and 'ap_scan=1'
2. in my networkprofile I added 'TIMEOUT=10' and 'DHCP_TIMEOUT=20'
3. finally I enabled dhcpcd: I think this one actually did it. It was never was in the array of rc.conf though

Similar Messages

  • [solved] netcfg fails with no apparent reason

    So, I'm trying to set up a very simple profile with netcfg:
    CONNECTION='ethernet'
    DESCRIPTION='ok'
    INTERFACE='eth0'
    IP='dhcp'
    Here's what happens when I try to bring it up:
    DEBUG: Loading profile eth0-dhcp
    DEBUG: Configuring interface eth0
    :: eth0-dhcp up
    DEBUG: status reported to profile_up as:
    DEBUG: Loading profile eth0-dhcp
    DEBUG: Configuring interface eth0
    DEBUG: ethernet_iproute_up ifup
    > No connection
    DEBUG: profile_up connect failed
    [FAIL]
    If I just do
    sudo ifconfig eth0 up
    sudo dhcpcd eth0
    , the network works fine.
    So, what might be the root of my problems with netcfg?
    Last edited by popoffka (2012-04-03 11:46:12)

    How long does it take for the interface to come up when you do it manually?
    Looking at what looks like the relevant lines of code (30-40) it could be a timeout issue, though not necessarily. You could manually try the commands issued in the scripts at that time.
    Just thinking aloud as, if it is a bug, then any info will be useful and netcfg is/has just getting a new maintainer, I think.

  • [SOLVED] netcfg fails to add IPv6 gateway

    After updating the (~2-month backlog of) packages on an Arch Linux VPS, I can no longer get netcfg to bring up eth0 with an IPv6 gateway.  However, if I bring up eth0 manually, it works...
    [root@inception ~]# ifconfig
    lo: flags=73<UP,LOOPBACK,RUNNING> mtu 16436 metric 1
    inet 127.0.0.1 netmask 255.0.0.0
    inet6 ::1 prefixlen 128 scopeid 0x10<host>
    loop txqueuelen 0 (Local Loopback)
    RX packets 0 bytes 0 (0.0 B)
    RX errors 0 dropped 0 overruns 0 frame 0
    TX packets 0 bytes 0 (0.0 B)
    TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
    [root@inception ~]# lsmod
    Module Size Used by
    evdev 9370 0
    pcspkr 1819 0
    ext4 374587 1
    crc16 1359 1 ext4
    jbd2 71543 1 ext4
    mbcache 5977 1 ext4
    xen_netfront 17247 0
    xen_blkfront 12625 2
    xenbus_probe_frontend 3239 2 xen_blkfront,xen_netfront
    [root@inception ~]# rc.d start net-profiles
    :: eth0 up [BUSY] RTNETLIN
    K answers: No route to host
    > Adding gateway 2a00:7b80:3008::1 failed
    [FAIL]
    > No profile started.
    [root@inception ~]# ifconfig eth0 up
    [root@inception ~]# rc.d start net-profiles
    :: eth0 up [DONE]
    [root@inception ~]# cat /etc/network.d/eth0
    CONNECTION='ethernet'
    DESCRIPTION='Ethernet 0'
    INTERFACE='eth0'
    IP='static'
    ADDR='xx.xx.xxx.xxx'
    GATEWAY='77.95.224.1'
    IP6='static'
    ADDR6=('xxxx:xxxx:xxxx:x::xxxx:xxxx' 'xxxx:xxxx:xxxx:x::xxxx:xxxx' 'xxxx:xxxx:xxxx:x::xxx
    x:xxxx' 'xxxx:xxxx:xxxx:x::xxx:xxxx' 'xxxx:xxxx:xxxx:x::xxxx:xxxx')
    GATEWAY6='2a00:7b80:3008::1'
    DNS=('8.8.8.8' '8.8.4.4' '2001:4860:4860::8888' '2001:4860:4860::8844')
    [root@inception ~]# uname -a
    Linux inception 3.0.38-1-lts #1 SMP PREEMPT Fri Jul 20 09:22:28 CEST 2012 x86_64 GNU/Linu
    x
    I don't know if I borked something during the package upgrades -- there were those couple announced ones that required minor manual intervention.  Any ideas?
    Last edited by MindlessXD (2013-01-26 16:44:42)

    (I've changed the IP addresses.)
    # cat /etc/network.d/eth0
    INTERFACE="eth0"
    DESCRIPTION="static IP for eth0"
    CONNECTION="ethernet"
    IP="static"
    ADDR="204.51.26.215"
    GATEWAY="204.51.26.1"
    IP6="static"
    ADDR6=(2402:4400:2:16c1::1/64)
    GATEWAY6="2402:4400:2::2"
    # netcfg -v
    netcfg v2.8.3
    # NETCFG_DEBUG="yes" netcfg eth0
    DEBUG: Loading profile eth0
    DEBUG: Configuring interface eth0
    :: eth0 up DEBUG: status reported to profile_up as:
    DEBUG: Loading profile eth0
    DEBUG: Configuring interface eth0
    DEBUG: ethernet_up ifup
    DEBUG: ethernet_up ip addr add 204.51.26.215/24 brd + dev eth0
    DEBUG: ethernet_up ip route add default via 204.51.26.1 dev eth0
    DEBUG: ethernet_up ip -6 addr add 2402:4400:2:16c1::1/64 dev eth0
    DEBUG: ethernet_up ip -6 route replace default via 2402:4400:2::2 dev eth0
    DEBUG: ethernet_up ip -6 addr show dev eth0 tentative
    DEBUG: ethernet_up hostname galloway
    [done]
    # netcfg -v
    netcfg v2.8.8
    # NETCFG_DEBUG="yes" netcfg eth0
    DEBUG: Loading profile eth0
    DEBUG: Configuring interface eth0
    :: eth0 up DEBUG: status reported to profile_up as:
    DEBUG: Loading profile eth0
    DEBUG: Configuring interface eth0
    DEBUG: ethernet_up bring_interface up eth0
    DEBUG: ethernet_up ip addr add 204.51.26.215/24 brd + dev eth0
    DEBUG: ethernet_up ip route add default via 204.51.26.1 dev eth0
    DEBUG: ethernet_up ip -6 addr add 2402:4400:2:16c1::1/64 dev eth0
    DEBUG: ethernet_up ip -6 route replace default via 2402:4400:2::2 dev eth0
    RTNETLINK answers: No route to host
    Adding gateway 2402:4400:2::2 failed
    DEBUG: profile_up connect failed
    [fail]

  • [Solved] Netcfg switches between interfaces

    Hello,
    I switched to netcfg, to get a pure systemd install.
    How ever, sometimes the netcfg can't bring up the interface even though it used that interface before.
    It's like netcfg are switching between what interface it can use. Sometimes it's eth0 other times eth1.
    So when I boot and don't have any network connection, I change the config files to use the other interface (ex. eth1) and netcfg can connect.
    How can this be?
    configs:
    /etc/network.d/mynetwork
    CONNECTION='ethernet'
    DESCRIPTION='A basic static ethernet connection using iproute'
    INTERFACE='eth1'
    IP='static'
    ADDR='192.168.1.3'
    #ROUTES=('192.168.0.0/24 via 192.168.1.2')
    GATEWAY='192.168.1.1'
    DNS=('dns1', 'dns2)
    ## For IPv6 autoconfiguration
    #IP6=stateless
    ## For IPv6 static address configuration
    #IP6='static'
    #ADDR6=('1234:5678:9abc:def::1/64' '1234:3456::123/96')
    #ROUTES6=('abcd::1234')
    #GATEWAY6='1234:0:123::abcd'
    /etc/conf.d/netcfg
    # Enable these netcfg profiles at boot time.
    # - prefix an entry with a '@' to background its startup
    # - set to 'last' to restore the profiles running at the last shutdown
    # - set to 'menu' to present a menu (requires the dialog package)
    # Network profiles are found in /etc/network.d
    NETWORKS=(mynetwork)
    # Specify the name of your wired interface for net-auto-wired
    WIRED_INTERFACE="eth1"
    # Specify the name of your wireless interface for net-auto-wireless
    #WIRELESS_INTERFACE="wlan0"
    # Array of profiles that may be started by net-auto-wireless.
    # When not specified, all wireless profiles are considered.
    #AUTO_PROFILES=("profile1" "profile2")
    Last edited by KLIM (2012-12-06 14:22:23)

    Did you checked for netcfg.service is enabled (systemd) ?
    BTW, I see a missing single quote on DNS line : DNS=('dns1', 'dns2)
    You may check these forum posts :
    "[SOLVED] Netcfg.service always failing." @ https://bbs.archlinux.org/viewtopic.php?id=148079
    "Systemd and Netcfg" @ https://bbs.archlinux.org/viewtopic.php?id=151662
    "netcfg/systemd not bringing up eth0 (static profile)" @ https://bbs.archlinux.org/viewtopic.php?id=147300
    "[SOLVED] netcfg fails at boot" @ https://bbs.archlinux.org/viewtopic.php?pid=1200518
    And this wiki entry about netcfg @ https://wiki.archlinux.org/index.php/Netcfg

  • Weblogic Bridge "failed and will reconnect later"

    The enterprise architecture is as follows:
    1 Physical machine where I have 2 VMs on this machine, and each VM I have 1 domain, 1 Cluster and 1 managed server, and the second VM I have the replicated what I have in first VM.
    In first domain I have the OSB, in the second domain I have SOA.
    What I need ? Send information of queues (topics) of First Domain (OSB) to second domain(SOA).
    At first the only thing I did was:
    In the first domain I created OSB JMS Server, JMS Module, Connection Factory and Queue Topic.
    In the second domain SOA I replied the same thing but with different names.
    Then I created the bridge with configuration default between the first domain and the second domain, the bridge and when active it generates me a message Weblogic Bridge "failed and will reconnect later"
    I did a test on my local machine windows where I created two domains, and the same procedures you did above, but the point was funcinou been activated now for the enterprise environment I'm not managing to make it work, you could tell me what is wrong . in both cases restarted the weblogic server as the machine itself the question that ran on my machine and machine company no.
    If you can give me a light thank.

    This is a bug (6973877, derby only) which has been fixed in 4.5 build14 and 4.4u2p1. Thanks for reporting. The problem is the missing "FOR BIT DATA" in LOG_RECORD column in derby table definition MQTMLRJMSBG41 in broker default.properties file
    - LOG_RECORD VARCHAR(2048) NOT NULL,\
    + LOG_RECORD VARCHAR(2048) FOR BIT DATA NOT NULL,\

  • SSIS 2012 ETL is failing only at one server (No BIDS) but running successfully from BIDS on different sever . In this ETL, I have used Stored Procedure in OLEDB Source.

    Hi Guys,
    SSIS 2012 ETL is failing only at one server (No BIDS) but running successfully from BIDS on different sever . In this ETL, I have used Stored Procedure in OLEDB Source.
    Note: I have couple of ETLs developed in 2005 using same logic and upgraded to 2012, working perfectly.
    I am getting Error Message:
    SSIS
    Error Code
    DTS_E_OLEDBERROR. 
    An OLE DB
    error has occurred.
    Error code: 0x80004005.
    An
    OLE DB
    record is available. 
    Source: "Microsoft OLE DB Provider for SQL Server" 
    Hresult: 0x80004005 
    Description: "Error converting data type varchar to datetime.".
    Unable
    to retrieve
    column information
    from the data
    source. Make
    sure your target
    table in
    the database is
    available.
    "OLE DB Source"
    failed validation
    and returned
    validation status
    "VS_ISBROKEN".
    I tried below word around and found It is working perfectly.
    I loaded data into a table (dbo.TEMP) using Stored procedure and then I used this dbo.TEMP table in OLEDB source and then found no issue.
    MY SP Details: (This SP I am calling in OLEDB source of ETL) and when I run it from one server IT is working fine and when I run from ETL dedicated Server getting error:   Guys Help me out.
    USE
    [TEST_DB]
    GO
    SET
    ANSI_NULLS ON
    GO
    SET
    QUOTED_IDENTIFIER ON
    GO
    ALTER
    PROCEDURE  [DBO].[SP_TEST]
    --EXEC [DBO].[SP_TEST] '2014-09-30','2014-10-01'
    @FROMDATETIME
    DATETIME,
    @TODATETIME
    DATETIME
    AS
    SET
    NOCOUNT ON
    BEGIN
    DECLARE
    @FROMDATEKEY INT,
    @TODATEKEY INT,
    SET
    @FROMDATEKEY=
    CONVERT(VARCHAR(10),@FROMDATETIME,112)
    SET
    @TODATEKEY=
    CONVERT(VARCHAR(10),@TODATETIME,112)
    IF 1 = 1
    BEGIN
    SELECT
    CAST(NULL
    AS DATETIME) 
    AS TXN_DATE
    , CAST(NULL
    AS DATETIME
    ) AS PROCESS_DATE     
    , CAST(NULL
    AS money)
    AS  S1_AMT
    , CAST(NULL
    AS money)
    AS  S2_AMOUNT
    , CAST(NULL
    AS money)
    AS  S2_INVALID_AMOUNT
    , CAST(NULL
    AS money)
    AS  INVALID_MOVED_IN_VALID_S2_AMOUNT
    , CAST(NULL
    AS VARCHAR(20))
    AS SYSTEM_ID
    , CAST(NULL
    AS money)
    AS  S3_AMT
    END
    SELECT
    TXN_DATE
    ,PROCESS_DATE
    ,S1_AMT
    ,S2_AMOUNT
    ,S2_INVALID_AMOUNT
    ,INVALID_MOVED_IN_VALID_S2_AMOUNT
    ,SYSTEM_ID
    S3_AMT
    FROM
    DBO.TABLE_1
    WHERE TNX_DATE_KEY
    BETWEEN @FROMDATEKEY
    and @TODATEKEY
    UNION
    ALL
    SELECT
    TXN_DATE
    ,PROCESS_DATE
    ,S1_AMT
    ,S2_AMOUNT
    ,S2_INVALID_AMOUNT
    ,INVALID_MOVED_IN_VALID_S2_AMOUNT
    ,SYSTEM_ID
    S3_AMT
    FROM
    DBO.TABLE_2
    WHERE TNX_DATE_KEY
    BETWEEN @FROMDATEKEY
    and @TODATEKEY
    UNION
    ALL
    SELECT
    TXN_DATE
    ,PROCESS_DATE
    ,S1_AMT
    ,S2_AMOUNT
    ,S2_INVALID_AMOUNT
    ,INVALID_MOVED_IN_VALID_S2_AMOUNT
    ,SYSTEM_ID
    S3_AMT
    FROM
    DBO.TABLE_3
    WHERE TNX_DATE_KEY
    BETWEEN @FROMDATEKEY
    and @TODATEKEY
    END
    Data Source Mode: SQL Command for Variable
    "EXEC [DBO].[SP_TEST]  '"+ (DT_WSTR, 24) @[User::V_EXTRACT_FROM_DT]  +"','"+ (DT_WSTR, 24) @[User::V_EXTRACT_TO_DT]  +"'"
    Where variable @[User::V_EXTRACT_FROM_DT] and @[User::V_EXTRACT_TO_DT] is defined as DATETIME 
    Thanks Shiven:) If Answer is Helpful, Please Vote

    Hi,
    Yes you are right. At one sever where I was getting error, DateTime was in USA format and Where It was running successfully was in AUS format.
    I changed from USA to AUS and I did another changes:
    Data Source Mode: SQL
    Command
    EXEC  [DBO].[SP_TEST] 
    @FROMDATETIME = ?,
    @TODATETIME = ?
    and It is working fine.
    Thanks Shiven:) If Answer is Helpful, Please Vote

  • [SOLVED] netcfg "IP lease attempt failed" on ethernet connection

    Since the latest update today I can't connect to the Internet (using an ethernet cable) any more.
    # NETCFG_DEBUG="yes" netcfg cable
    DEBUG: Loading profile cable
    DEBUG: Configuring interface eth0
    :: cable up [BUSY]
    DEBUG: status reported to profile_up as:
    DEBUG: Loading profile cable
    DEBUG: Configuring interface eth0
    DEBUG: ethernet_iproute_up ifup
    DEBUG: ethernet_up dhcpd -qL -t 30 eth0
    DEBUG:
    > DHCP IP lease attempt failes.
    DEBUG: profile_up connect failed
    [FAIL]
    System: Arch 64
    Does anyone have any idea what might be wrong? Not sure where to start there, as the interface eth0 seems to be up and all right under ifconfig.
    Thanks for any hints.
    Last edited by JackH79 (2011-12-01 00:53:19)

    Thanks very much for your suggestions, ewaller.
    Weirdly enough though, this morning I came into work, plugged in the cable and, voilà, it worked straight away.
    Maybe it's just that time of the month.
    Anyway, thanks again to you and cybertorture. I'll mark this as solved for now.
    EDIT: Just a little follow up to make it a bit more embarassing: I just realised that it was actually the port of the switch that's broken. So thanks to ewaller for stating the obvious
    Last edited by JackH79 (2011-12-01 07:05:25)

  • [SOLVED] Netcfg.service always failing.

    Hello,
    Since systemd got pushed down with an update I decided to jump the ship (even though roughly a week ago I tried it and decided to wait a while, the irony ) With the help of my previous topic and the knowledge that e4rat does work with systemd, I got everything working and it's working faster than ever too. Win/win if you ask me.
    There's only one issue: the netcfg.service that I have enabled with systemctl enable netcfg.service always fail on boot and I have to manually connect later. I don't know why it fails, so I hope you can help me tracking the issue.
    This is the output of systemctl status netcfg.service right after booting:
    ┌─[jente @ lappy ~] 19:39:30
    └─■ systemctl status netcfg.service
    netcfg.service - Netcfg multi-profile daemon
    Loaded: loaded (/usr/lib/systemd/system/netcfg.service; enabled)
    Active: failed (Result: exit-code) since Fri, 31 Aug 2012 19:35:04 +0200; 4min 27s ago
    Process: 253 ExecStart=/usr/bin/netcfg-daemon start (code=exited, status=1/FAILURE)
    CGroup: name=systemd:/system/netcfg.service
    And here's systemctl --failed list-units:
    ┌─[jente @ lappy ~] 19:39:32
    └─■ systemctl --failed list-units
    UNIT LOAD ACTIVE SUB JOB DESCRIPTION
    netcfg.service loaded failed failed Netcfg multi-profile daemon
    LOAD = Reflects whether the unit definition was properly loaded.
    ACTIVE = The high-level unit activation state, i.e. generalization of SUB.
    SUB = The low-level unit activation state, values depend on unit type.
    JOB = Pending job for the unit.
    1 units listed. Pass --all to see inactive units, too.
    And here's the journal output:
    ----- Reboot -----
    Aug 31 19:35:04 lappy netcfg-daemon[253]: :: [ESSID] up interface wlan0 does not exist
    Aug 31 19:35:04 lappy netcfg-daemon[253]: [fail]
    I don't think it's any netcfg configuration file, because it did work with SysV and the net-profiles daemon.
    Last edited by Unia (2012-10-31 14:20:21)

    I use a custom "network.service" as I have a static ip on my wireless lan (oh, and I chucked in the hdparm stuff because after suspend I found the disk had lost those settings, so don't copy that line). Based on this wiki section.
    $ cat /etc/systemd/system/network.service
    [Unit]
    Description=Network Connectivity
    Wants=network.target
    Before=network.target
    After=sys-devices-pci0000:00-0000:00:1c.1-0000:02:00.0-bcma0:0-net-wlan0.device
    BindTo=sys-devices-pci0000:00-0000:00:1c.1-0000:02:00.0-bcma0:0-net-wlan0.device
    [Service]
    Type=oneshot
    RemainAfterExit=yes
    EnvironmentFile=/etc/conf.d/network
    ExecStart=/sbin/hdparm --yes-i-know-what-i-am-doing -m 16 -S0 -B255 /dev/sda
    ExecStart=/usr/sbin/wpa_supplicant -B -i ${interface} -c /etc/wpa_supplicant/wpa_supplicant-wlan0.conf
    ExecStart=/sbin/ip link set dev ${interface} up
    ExecStart=/sbin/ip addr add ${address}/${netmask} broadcast ${broadcast} dev ${interface}
    ExecStart=/sbin/ip route add default via ${gateway}
    ExecStop=/sbin/ip addr flush dev ${interface}
    ExecStop=/sbin/ip link set dev ${interface} down
    ExecStop=/usr/bin/killall wpa_supplicant
    [Install]
    WantedBy=multi-user.target

  • [Solved] Netcfg 2.6.1 - suddenly fails to associate with WPA2 network

    Everything around here seems to be breaking these days... Anyways.
    I upgraded netcfg yesterday. Today I fire up my laptop, but no wireless. I run netcfg again, this is what wpa_supplicant spits out:
    # netcfg intel
    :: intel up [BUSY]
    Failed to connect to wpa_supplicant - wpa_ctrl_open: No such file or directory
    Failed to connect to wpa_supplicant - wpa_ctrl_open: No such file or directory
    ^C
    The funny thing is, nothing's changed in the netcfg config file, which looks like this:
    CONNECTION="wireless"
    INTERFACE="intel"
    HOSTNAME="hermes"
    # AP authentication
    SCAN="yes"
    SECURITY="wpa-config"
    WPA_CONF="/etc/wpa_supplicant.conf"
    WPA_OPTS="-Dwext -B"
    ESSID="Zeus 802.11n"
    # IP address
    IP="dhcp"
    DHCP_TIMEOUT=10
    I compared my config to the examples that come with netcfg - just to be sure nothing's changed that I wasn't aware of - but it looks pretty identical. Oddly enough, calling wpa_supplicant and then dhcpcd directly just connects me to my WLAN, like netcfg used to be able to do.
    For reference, netcfg seems to call wpa_supplicant like this, going by htop's output:
    wpa_supplicant -Dwext,nl80211 -c /etc/wpa_supplicant.conf -B -i intel -d
    When run separately, however, that works just fine, just like using -Dwext like I used to do before.
    Last edited by .:B:. (2011-06-21 22:29:55)

    My understanding is that the thing fails in start_wpa(). From /usr/lib/network/8021x:
    start_wpa()
    local INTERFACE="$1" WPA_CONF="$2" WPA_DRIVER="$3"
    shift 3
    local WPA_OPTS="$*"
    wpa_supplicant -B -P "/run/wpa_supplicant_${INTERFACE}.pid" -i "$INTERFACE"-D "$WPA_DRIVER" -c "$WPA_CONF" $WPA_OPTS
    sleep 1
    if [[ ! -f "/run/wpa_supplicant_${INTERFACE}.pid" ]]; then
    return 1
    fi
    So, you should have seen "-P' in htop, no? Have you tried w/o WPA_OPTS?
    EDIT: OK, I was wrong. The error seems to come from wpa_supplicant/wp_cli calls with the new /run standard:
    arch~> grep "/run/wpa_supplicant" ./usr/lib/network/8021x
    WPA_CLI="wpa_cli -p /run/wpa_supplicant"
    wpa_supplicant -B -P "/run/wpa_supplicant_${INTERFACE}.pid" -i "$INTERFACE" -D "$WPA_DRIVER" -c "$WPA_CONF" $WPA_OPTS
    if [[ ! -f "/run/wpa_supplicant_${INTERFACE}.pid" ]]; then
    if [[ -f "/run/wpa_supplicant_$1.pid" ]]; then
    kill "$(cat "/run/wpa_supplicant_$1.pid")" &>/dev/null &
    wpa_supplicant -B -i"$INTERFACE" -Dnl80211,wext -C/run/wpa_supplicant -P/run/wpa_supplicant.pid || return 1
    kill "$(cat /run/wpa_supplicant.pid)"
    echo "ctrl_interface=/run/wpa_supplicant" >> "$WPA_CONF/wpa.conf" # we know $WPA_CONF now has no spaces, but it may have other nasty chars, so still needs to be quoted
    Could you change the ctrl_interface to to /run/wpa_supplicant in /etc/wpa_supplicant.conf?
    Last edited by Leonid.I (2011-06-21 21:19:59)

  • [SOLVED] netcfg DHCP IP lease attempt failed

    I'm trying to configure my network settings, I made a profile, netcfg recognizes the profile, but when it loads I get that error (DHCP IP lease attempt failed). Here is my profile...
    CONNECTION='wireless'
    INTERFACE='wlan0'
    SECURITY='none'
    ESSID='my network name'
    IP='dhcp'
    DCHP_TIMEOUT='30'
    Last edited by oldstutz (2010-07-30 18:33:54)

    jogan wrote:
    jogan wrote:
    Do you have any idea how to load the rt2860 driver from /lib/firmware/rt2860.bin?
    My attempt to load the driver with MODULES in /etc/rc.conf has been unsuccessful.
    oldstutz wrote:RaLink RT2860, and I have rt2860sta in my modules
    I've battled this issue for weeks on my notebook ... wireless worked on Arch (2009.08)
    last year.  Seems to me now the culprit maybe rt2860sta.
    OK, let's check
    lsmod | grep -i rt2860

  • [SOLVED] Wireless fails after suspending (Realtek 8192se)

    This problem is already solved on the first post: I spent so long trying to solve it that I thought people should know the solution.
    I have a Lenovo X100e with a Realtek 8192SE wireless card.  I'm running kernel 3.0.  The machine has, since upgrading to the 3.0 kernel had the annoying problem of failing wireless connections after suspending: I'll have a running wireless connection, then suspend the machine, and then wake the machine up and the machine cannot connect to any wireless network (perhaps the same one I was connected to before, in the same place). 
    Things that did not work:
    Installing the Realtek drivers from their website
    Downgrading the kernel from 3.1 to 3.0
    Using wicd instead of networkmanager
    Walking around
    Other distributions
    The solution was to put an entry in /etc/pm/config.d/config:
    SUSPEND_MODULES="rtl8192se rtlwifi mac80211 cfg80211"
    Now the machine reconnects with no problems.
    This may be the solution to the other big problem I was having with the 3.1 kernel: I would suspend the machine by any means and the screen goes black and the machine becomes non-responsive without actually suspending.  I may try upgrading to the 3.1 kernel and adding radeon to the SUSPEND_MODULES list above.

    Found out more which might be significant for madwifi users:
    According to the wiki I loaded the following modules in rc.conf: ath-hal, ath9k, wlan
    Beside this one line in the modprobe.conf should be added: alias ath0 ath_pci. This way wicd as well as networkmanager used ath0 for connecting to wireless.
    After the update I noticed that there is another wifi device in ifconfig listed: wlan0. So I suspected that 2 devices pointing at the same hardware may cause the instability, but de-activating one by ifconfig didn't help. Now I noticed by loading the modules one by one that the new ath9k is already defining wlan0 and the wireless starts working without loading the module wlan. It looks stable so far, but if I should be right I'm impossibly the only one having this trouble.
    Confirmation would be nice, but I will mark this thread "solved" now.

  • [SOLVED] Netcfg.service not starting with systemd

    I have net-auto-wireless.service enabled and working, but when I try to start netcfg.service, it gives the error:
    Job for netcfg.service failed. See 'systemctl status netcfg.service' and 'journalctl' for details.
    "systemctl status netcfg.service" gives me:
    netcfg.service - Netcfg multi-profile daemon
    Loaded: loaded (/usr/lib/systemd/system/netcfg.service; enabled)
    Active: failed (Result: exit-code) since Thu, 04 Oct 2012 13:43:05 -0400; 5min ago
    Main PID: 1510 (code=exited, status=1/FAILURE)
    CGroup: name=systemd:/system/netcfg.service
    Oct 04 13:43:05 arch systemd[1]: Starting Netcfg multi-profile daemon...
    Oct 04 13:43:05 arch netcfg-daemon[1510]: No recorded netcfg state to restore
    Oct 04 13:43:05 arch systemd[1]: Failed to start Netcfg multi-profile daemon.
    And the output of "journalctl" is:
    Oct 04 13:43:05 arch netcfg-daemon[1510]: No recorded netcfg state to restore
    Oct 04 13:43:05 arch systemd[1]: netcfg.service: main process exited, code=...=1
    Oct 04 13:43:05 arch systemd[1]: Unit netcfg.service entered failed state.
    Am I missing something in setting it up?  I followed the netcfg wiki as closely as I could.
    Last edited by mellowmaroon (2012-10-04 18:46:16)

    Good call, I changed it from "last", to the profile I use in /etc/network.d that net-auto-wireless autoconnects to.  It failed for a different reason after changing the NETWORKS in /etc/conf.d/netcfg, because net-auto-wireless was still running.
    But it works now, thanks for the help!
    I wanted to use netcfg instead of net-auto-wireless because I was unable to find a suitable way to connect to available networks that is non-graphical, and I felt like giving netcfg a try and seeing if it's any easier than running "systemctl restart net-auto-wireless.service" every time I want to reconnect.
    Although my question for this thread is solved, is there any way to have netcfg autoconnect to profiles once I am within range?

  • [SOLVED] Bumblebee: Failed to initialize GPU with Lenovo ThinkPad W530

    SOLVED: See post #20
    After years, I decided to come back to the wonderful distro, Arch and back to the forums. Yay!
    However, I installed Arch to my new laptop - Lenovo ThinkPad W530 and it uses NVIDIA Quadro K1000M alongside Intel graphics with Optimus technology. Arch is running fine, but I cannot run applications through optirun and I get:
    [exitium@rambutan ~]$ optirun -vv nvidia-settings
    [ 485.536478] [DEBUG]Reading file: /etc/bumblebee/bumblebee.conf
    [ 485.536909] [DEBUG]optirun version 3.2.1 starting...
    [ 485.536922] [DEBUG]Active configuration:
    [ 485.536927] [DEBUG] bumblebeed config file: /etc/bumblebee/bumblebee.conf
    [ 485.536931] [DEBUG] X display: :8
    [ 485.536934] [DEBUG] LD_LIBRARY_PATH: /usr/lib/nvidia:/usr/lib32/nvidia
    [ 485.536938] [DEBUG] Socket path: /var/run/bumblebee.socket
    [ 485.536941] [DEBUG] Accel/display bridge: auto
    [ 485.536945] [DEBUG] VGL Compression: proxy
    [ 485.536948] [DEBUG] VGLrun extra options:
    [ 485.536952] [DEBUG] Primus LD Path: /usr/lib/primus:/usr/lib32/primus
    [ 485.536972] [DEBUG]Using auto-detected bridge virtualgl
    [ 485.537190] [INFO]Response: No - error: [XORG] (EE) NVIDIA(0): Failed to initialize the NVIDIA GPU at PCI:1:0:0. Please
    [ 485.537204] [ERROR]Cannot access secondary GPU - error: [XORG] (EE) NVIDIA(0): Failed to initialize the NVIDIA GPU at PCI:1:0:0. Please
    [ 485.537209] [DEBUG]Socket closed.
    [ 485.537223] [ERROR]Aborting because fallback start is disabled.
    [ 485.537229] [DEBUG]Killing all remaining processes.
    As seen, it says "Failed to initialize the NVIDIA GPU". I have tried different solutions found from these forums and several other places but none of them have worked - the problem remains same. Does anyone have idea how I could fix this? I read somewhere else that there could be issues with newest nvidia drivers - is this possible?
    bumblebee.conf:
    # Configuration file for Bumblebee. Values should **not** be put between quotes
    ## Server options. Any change made in this section will need a server restart
    # to take effect.
    [bumblebeed]
    # The secondary Xorg server DISPLAY number
    VirtualDisplay=:8
    # Should the unused Xorg server be kept running? Set this to true if waiting
    # for X to be ready is too long and don't need power management at all.
    KeepUnusedXServer=false
    # The name of the Bumbleblee server group name (GID name)
    ServerGroup=bumblebee
    # Card power state at exit. Set to false if the card shoud be ON when Bumblebee
    # server exits.
    TurnCardOffAtExit=false
    # The default behavior of '-f' option on optirun. If set to "true", '-f' will
    # be ignored.
    NoEcoModeOverride=false
    # The Driver used by Bumblebee server. If this value is not set (or empty),
    # auto-detection is performed. The available drivers are nvidia and nouveau
    # (See also the driver-specific sections below)
    Driver=
    # Directory with a dummy config file to pass as a -configdir to secondary X
    XorgConfDir=/etc/bumblebee/xorg.conf.d
    ## Client options. Will take effect on the next optirun executed.
    [optirun]
    # Acceleration/ rendering bridge, possible values are auto, virtualgl and
    # primus.
    Bridge=auto
    # The method used for VirtualGL to transport frames between X servers.
    # Possible values are proxy, jpeg, rgb, xv and yuv.
    VGLTransport=proxy
    # List of paths which are searched for the primus libGL.so.1 when using
    # the primus bridge
    PrimusLibraryPath=/usr/lib/primus:/usr/lib32/primus
    # Should the program run under optirun even if Bumblebee server or nvidia card
    # is not available?
    AllowFallbackToIGC=false
    # Driver-specific settings are grouped under [driver-NAME]. The sections are
    # parsed if the Driver setting in [bumblebeed] is set to NAME (or if auto-
    # detection resolves to NAME).
    # PMMethod: method to use for saving power by disabling the nvidia card, valid
    # values are: auto - automatically detect which PM method to use
    # bbswitch - new in BB 3, recommended if available
    # switcheroo - vga_switcheroo method, use at your own risk
    # none - disable PM completely
    # https://github.com/Bumblebee-Project/Bumblebee/wiki/Comparison-of-PM-methods
    ## Section with nvidia driver specific options, only parsed if Driver=nvidia
    [driver-nvidia]
    # Module name to load, defaults to Driver if empty or unset
    KernelDriver=nvidia
    PMMethod=auto
    # colon-separated path to the nvidia libraries
    LibraryPath=/usr/lib/nvidia:/usr/lib32/nvidia
    # comma-separated path of the directory containing nvidia_drv.so and the
    # default Xorg modules path
    XorgModulePath=/usr/lib/nvidia/xorg/,/usr/lib/xorg/modules
    XorgConfFile=/etc/bumblebee/xorg.conf.nvidia
    ## Section with nouveau driver specific options, only parsed if Driver=nouveau
    [driver-nouveau]
    KernelDriver=nouveau
    PMMethod=auto
    XorgConfFile=/etc/bumblebee/xorg.conf.nouveau
    xorg.conf.nvidia
    Section "ServerLayout"
    Identifier "Layout0"
    Option "AutoAddDevices" "false"
    Option "AutoAddGPU" "false"
    Option "UseDisplayDevice" "none"
    EndSection
    Section "Device"
    Identifier "DiscreteNvidia"
    Driver "nvidia"
    VendorName "NVIDIA Corporation"
    # If the X server does not automatically detect your VGA device,
    # you can manually set it here.
    # To get the BusID prop, run `lspci | egrep 'VGA|3D'` and input the data
    # as you see in the commented example.
    # This Setting may be needed in some platforms with more than one
    # nvidia card, which may confuse the proprietary driver (e.g.,
    # trying to take ownership of the wrong device). Also needed on Ubuntu 13.04.
    BusID "PCI:01:00:0"
    # Setting ProbeAllGpus to false prevents the new proprietary driver
    # instance spawned to try to control the integrated graphics card,
    # which is already being managed outside bumblebee.
    # This option doesn't hurt and it is required on platforms running
    # more than one nvidia graphics card with the proprietary driver.
    # (E.g. Macbook Pro pre-2010 with nVidia 9400M + 9600M GT).
    # If this option is not set, the new Xorg may blacken the screen and
    # render it unusable (unless you have some way to run killall Xorg).
    Option "ProbeAllGpus" "false"
    Option "NoLogo" "true"
    Option "UseEDID" "false"
    Option "UseDisplayDevice" "none"
    EndSection
    Thank you in advance!
    Last edited by Exitium (2013-12-18 11:29:54)

    Hi!
    Exactly the same issue here. Notebook -> Thinkpad W530
    Currently running on:
    linux 3.11.3-1
    nvidia 325.15-8
    nvidia-utils 325.15-1
    bbswitch 0.7-14
    Error:
    username@hostname ~ $ optirun -vv nvidia-settings
    [  839.449203] [DEBUG]Reading file: /etc/bumblebee/bumblebee.conf
    [  839.449495] [INFO]Configured driver: nvidia
    [  839.449729] [DEBUG]optirun version 3.2.1 starting...
    [  839.449774] [DEBUG]Active configuration:
    [  839.449817] [DEBUG] bumblebeed config file: /etc/bumblebee/bumblebee.conf
    [  839.449836] [DEBUG] X display: :8
    [  839.449856] [DEBUG] LD_LIBRARY_PATH: /usr/lib/nvidia:/usr/lib32/nvidia
    [  839.449875] [DEBUG] Socket path: /var/run/bumblebee.socket
    [  839.449890] [DEBUG] Accel/display bridge: auto
    [  839.449909] [DEBUG] VGL Compression: proxy
    [  839.449936] [DEBUG] VGLrun extra options:
    [  839.449953] [DEBUG] Primus LD Path: /usr/lib/primus:/usr/lib32/primus
    [  839.449996] [DEBUG]Using auto-detected bridge virtualgl
    [  839.450294] [INFO]Response: No - error: [XORG] (EE) NVIDIA(0): Failed to initialize the NVIDIA GPU at PCI:1:0:0.  Please
    [  839.450344] [ERROR]Cannot access secondary GPU - error: [XORG] (EE) NVIDIA(0): Failed to initialize the NVIDIA GPU at PCI:1:0:0.  Please
    [  839.450373] [DEBUG]Socket closed.
    [  839.450398] [ERROR]Aborting because fallback start is disabled.
    [  839.450419] [DEBUG]Killing all remaining processes.
    dmesg output:
    [   81.162604] bbswitch: enabling discrete graphics
    [   81.396637] pci 0000:01:00.0: power state changed by ACPI to D0
    [   81.396663] thinkpad_acpi: EC reports that Thermal Table has changed
    [   81.483200] nvidia: module license 'NVIDIA' taints kernel.
    [   81.483205] Disabling lock debugging due to kernel taint
    [   81.488096] vgaarb: device changed decodes: PCI:0000:01:00.0,olddecodes=io+mem,decodes=none:owns=none
    [   81.488289] [drm] Initialized nvidia-drm 0.0.0 20130102 for 0000:01:00.0 on minor 1
    [   81.488294] NVRM: loading NVIDIA UNIX x86_64 Kernel Module  325.15  Wed Jul 31 18:50:56 PDT 2013
    [   81.665938] nvidia 0000:01:00.0: irq 50 for MSI/MSI-X
    [   81.670434] ACPI Warning: \_SB_.PCI0.PEG_.VID_._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20130517/nsarguments-95)
    [   81.670528] ACPI Warning: \_SB_.PCI0.PEG_.VID_._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20130517/nsarguments-95)
    [   81.670594] ACPI Warning: \_SB_.PCI0.PEG_.VID_._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20130517/nsarguments-95)
    [   81.670659] ACPI Warning: \_SB_.PCI0.PEG_.VID_._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20130517/nsarguments-95)
    [   81.670723] ACPI Warning: \_SB_.PCI0.PEG_.VID_._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20130517/nsarguments-95)
    [   81.670960] ACPI Warning: \_SB_.PCI0.PEG_.VID_._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20130517/nsarguments-95)
    [   81.671192] ACPI Warning: \_SB_.PCI0.PEG_.VID_._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20130517/nsarguments-95)
    [   81.671258] ACPI Warning: \_SB_.PCI0.PEG_.VID_._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20130517/nsarguments-95)
    [   85.879826] ACPI Warning: \_SB_.PCI0.PEG_.VID_._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20130517/nsarguments-95)
    [   85.905471] NVRM: GPU at 0000:01:00.0 has fallen off the bus.
    [   85.905479] NVRM: os_pci_init_handle: invalid context!
    [   85.905481] NVRM: os_pci_init_handle: invalid context!
    [   85.905486] NVRM: GPU at 0000:01:00.0 has fallen off the bus.
    [   85.905490] NVRM: os_pci_init_handle: invalid context!
    [   85.905491] NVRM: os_pci_init_handle: invalid context!
    [   85.930135] ACPI Warning: \_SB_.PCI0.PEG_.VID_._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20130517/nsarguments-95)
    [   85.930442] ACPI Warning: \_SB_.PCI0.PEG_.VID_._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20130517/nsarguments-95)
    [   85.930719] ACPI Warning: \_SB_.PCI0.PEG_.VID_._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20130517/nsarguments-95)
    [   85.930990] ACPI Warning: \_SB_.PCI0.PEG_.VID_._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20130517/nsarguments-95)
    [   85.931258] ACPI Warning: \_SB_.PCI0.PEG_.VID_._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20130517/nsarguments-95)
    [   85.931526] ACPI Warning: \_SB_.PCI0.PEG_.VID_._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20130517/nsarguments-95)
    [   85.931794] ACPI Warning: \_SB_.PCI0.PEG_.VID_._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20130517/nsarguments-95)
    [   85.932062] ACPI Warning: \_SB_.PCI0.PEG_.VID_._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20130517/nsarguments-95)
    [   85.932329] ACPI Warning: \_SB_.PCI0.PEG_.VID_._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20130517/nsarguments-95)
    [   85.932595] ACPI Warning: \_SB_.PCI0.PEG_.VID_._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20130517/nsarguments-95)
    [   85.932862] ACPI Warning: \_SB_.PCI0.PEG_.VID_._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20130517/nsarguments-95)
    [   85.933129] ACPI Warning: \_SB_.PCI0.PEG_.VID_._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20130517/nsarguments-95)
    [   85.933396] ACPI Warning: \_SB_.PCI0.PEG_.VID_._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20130517/nsarguments-95)
    [   85.933662] ACPI Warning: \_SB_.PCI0.PEG_.VID_._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20130517/nsarguments-95)
    [   85.933942] ACPI Warning: \_SB_.PCI0.PEG_.VID_._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20130517/nsarguments-95)
    [   85.934197] ACPI Warning: \_SB_.PCI0.PEG_.VID_._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20130517/nsarguments-95)
    [   85.934452] ACPI Warning: \_SB_.PCI0.PEG_.VID_._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20130517/nsarguments-95)
    [   85.934706] ACPI Warning: \_SB_.PCI0.PEG_.VID_._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20130517/nsarguments-95)
    [   85.934960] ACPI Warning: \_SB_.PCI0.PEG_.VID_._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20130517/nsarguments-95)
    [   85.935215] ACPI Warning: \_SB_.PCI0.PEG_.VID_._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20130517/nsarguments-95)
    [   85.935469] ACPI Warning: \_SB_.PCI0.PEG_.VID_._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20130517/nsarguments-95)
    [   85.935722] ACPI Warning: \_SB_.PCI0.PEG_.VID_._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20130517/nsarguments-95)
    [   85.935976] ACPI Warning: \_SB_.PCI0.PEG_.VID_._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20130517/nsarguments-95)
    [   85.940508] NVRM: RmInitAdapter failed! (0x25:0x28:1157)
    [   85.940517] NVRM: rm_init_adapter(0) failed
    xorg.conf.nvidia:
    Section "ServerLayout"
        Identifier  "Layout0"
        Option      "AutoAddDevices" "false"
        Option      "AutoAddGPU" "false"
    EndSection
    Section "Device"
        Identifier  "DiscreteNvidia"
        Driver      "nvidia"
        VendorName  "NVIDIA Corporation"
    #   If the X server does not automatically detect your VGA device,
    #   you can manually set it here.
    #   To get the BusID prop, run `lspci | egrep 'VGA|3D'` and input the data
    #   as you see in the commented example.
    #   This Setting may be needed in some platforms with more than one
    #   nvidia card, which may confuse the proprietary driver (e.g.,
    #   trying to take ownership of the wrong device). Also needed on Ubuntu 13.04.
        BusID "PCI:01:00:0"
    #   Setting ProbeAllGpus to false prevents the new proprietary driver
    #   instance spawned to try to control the integrated graphics card,
    #   which is already being managed outside bumblebee.
    #   This option doesn't hurt and it is required on platforms running
    #   more than one nvidia graphics card with the proprietary driver.
    #   (E.g. Macbook Pro pre-2010 with nVidia 9400M + 9600M GT).
    #   If this option is not set, the new Xorg may blacken the screen and
    #   render it unusable (unless you have some way to run killall Xorg).
        Option "ProbeAllGpus" "false"
        Option "NoLogo" "true"
        Option "UseEDID" "false"
        Option "UseDisplayDevice" "none"
    EndSection
    bumblebee.conf:
    # Configuration file for Bumblebee. Values should **not** be put between quotes
    ## Server options. Any change made in this section will need a server restart
    # to take effect.
    [bumblebeed]
    # The secondary Xorg server DISPLAY number
    VirtualDisplay=:8
    # Should the unused Xorg server be kept running? Set this to true if waiting
    # for X to be ready is too long and don't need power management at all.
    KeepUnusedXServer=false
    # The name of the Bumbleblee server group name (GID name)
    ServerGroup=bumblebee
    # Card power state at exit. Set to false if the card shoud be ON when Bumblebee
    # server exits.
    TurnCardOffAtExit=false
    # The default behavior of '-f' option on optirun. If set to "true", '-f' will
    # be ignored.
    NoEcoModeOverride=false
    # The Driver used by Bumblebee server. If this value is not set (or empty),
    # auto-detection is performed. The available drivers are nvidia and nouveau
    # (See also the driver-specific sections below)
    Driver=nvidia
    # Directory with a dummy config file to pass as a -configdir to secondary X
    XorgConfDir=/etc/bumblebee/xorg.conf.d
    ## Client options. Will take effect on the next optirun executed.
    [optirun]
    # Acceleration/ rendering bridge, possible values are auto, virtualgl and
    # primus.
    Bridge=auto
    # The method used for VirtualGL to transport frames between X servers.
    # Possible values are proxy, jpeg, rgb, xv and yuv.
    VGLTransport=proxy
    # List of paths which are searched for the primus libGL.so.1 when using
    # the primus bridge
    PrimusLibraryPath=/usr/lib/primus:/usr/lib32/primus
    # Should the program run under optirun even if Bumblebee server or nvidia card
    # is not available?
    AllowFallbackToIGC=false
    # Driver-specific settings are grouped under [driver-NAME]. The sections are
    # parsed if the Driver setting in [bumblebeed] is set to NAME (or if auto-
    # detection resolves to NAME).
    # PMMethod: method to use for saving power by disabling the nvidia card, valid
    # values are: auto - automatically detect which PM method to use
    #         bbswitch - new in BB 3, recommended if available
    #       switcheroo - vga_switcheroo method, use at your own risk
    #             none - disable PM completely
    # https://github.com/Bumblebee-Project/Bu … PM-methods
    ## Section with nvidia driver specific options, only parsed if Driver=nvidia
    [driver-nvidia]
    # Module name to load, defaults to Driver if empty or unset
    KernelDriver=nvidia
    PMMethod=auto
    # colon-separated path to the nvidia libraries
    LibraryPath=/usr/lib/nvidia:/usr/lib32/nvidia
    # comma-separated path of the directory containing nvidia_drv.so and the
    # default Xorg modules path
    XorgModulePath=/usr/lib/nvidia/xorg/,/usr/lib/xorg/modules
    XorgConfFile=/etc/bumblebee/xorg.conf.nvidia
    ## Section with nouveau driver specific options, only parsed if Driver=nouveau
    [driver-nouveau]
    KernelDriver=nouveau
    PMMethod=auto
    XorgConfFile=/etc/bumblebee/xorg.conf.nouveau

  • [SOLVED]Netcfg works great manually, but when using the daemon it wont

    I installed netcfg a really long time ago following the arch wiki. When I first installed it and set everything up, it was all working perfectly.
    For the past three or four months Ive been having problems where netcf daemon is failing to connect (home wireless network 256bit wep). It takes about 20 seconds just waiting and eventually says failed. If I log in and run the command manually (sudo netcfg home-wifi) it connect perfectly fine every time.
    Ive tried everything I can think of including different QUIRKS and changing permissions on the profiles but nothing works. I also tried using the netcfg menu but it doesnt work like that either. I went over the wiki page again thinking something might have chnaged, but its all the same. I even reinstalled and configured again but still nothing.
    heres my rc.conf
    # /etc/rc.conf - Main Configuration for Arch Linux
    # LOCALIZATION
    # LOCALE: available languages can be listed with the 'locale -a' command
    # HARDWARECLOCK: set to "UTC" or "localtime", any other value will result
    # in the hardware clock being left untouched (useful for virtualization)
    # TIMEZONE: timezones are found in /usr/share/zoneinfo
    # KEYMAP: keymaps are found in /usr/share/kbd/keymaps
    # CONSOLEFONT: found in /usr/share/kbd/consolefonts (only needed for non-US)
    # CONSOLEMAP: found in /usr/share/kbd/consoletrans
    # USECOLOR: use ANSI color sequences in startup messages
    LOCALE="en_US.UTF-8"
    HARDWARECLOCK="UTC"
    TIMEZONE="America/New_York"
    KEYMAP="us"
    CONSOLEFONT=
    CONSOLEMAP=
    USECOLOR="yes"
    # HARDWARE
    # MOD_AUTOLOAD: Allow autoloading of modules at boot and when needed
    # MOD_BLACKLIST: Prevent udev from loading these modules
    # MODULES: Modules to load at boot-up. Prefix with a ! to blacklist.
    # NOTE: Use of 'MOD_BLACKLIST' is deprecated. Please use ! in the MODULES array.
    MOD_AUTOLOAD="yes"
    #MOD_BLACKLIST=() #deprecated
    MODULES=(acpi-cpufreq cpufreq_ondemand vboxdrv loop)
    # Scan for LVM volume groups at startup, required if you use LVM
    USELVM="no"
    # NETWORKING
    # HOSTNAME: Hostname of machine. Should also be put in /etc/hosts
    HOSTNAME="Arch"
    # Use 'ifconfig -a' or 'ls /sys/class/net/' to see all available interfaces.
    # Interfaces to start at boot-up (in this order)
    # Declare each interface then list in INTERFACES
    # - prefix an entry in INTERFACES with a ! to disable it
    # - no hyphens in your interface names - Bash doesn't like it
    # DHCP: Set your interface to "dhcp" (eth0="dhcp")
    # Wireless: See network profiles below
    #Static IP example
    #eth0="dhcp"
    eth0="dhcp"
    INTERFACES=(eth0)
    # Routes to start at boot-up (in this order)
    # Declare each route then list in ROUTES
    # - prefix an entry in ROUTES with a ! to disable it
    gateway="default gw 192.168.0.1"
    ROUTES=(!gateway)
    # Enable these network profiles at boot-up. These are only useful
    # if you happen to need multiple network configurations (ie, laptop users)
    # - set to 'menu' to present a menu during boot-up (dialog package required)
    # - prefix an entry with a ! to disable it
    # Network profiles are found in /etc/network.d
    # This now requires the netcfg package
    NETWORKS=(home-wifi)
    # DAEMONS
    # Daemons to start at boot-up (in this order)
    # - prefix a daemon with a ! to disable it
    # - prefix a daemon with a @ to start it up in the background
    DAEMONS=(syslog-ng crond hal cpufreq !network net-profiles @netfs @alsa @sensors @mpd)
    What gets me is that it actually takes longer to fail then it does when I manually connect. It times out for like 20 seconds, but when I manually connect its almost instantaneous.
    Last edited by tjwoosta (2010-03-02 05:31:37)

    I had arch installed on my Sony VAIO, had this problem, and then fixed it somehow.  That was several months ago, recently I fried the laptop so I just reinstalled and can't remember.  But now I have a "solution"  haha
    this is kind of silly how I got it to work, though.
    I created another profile "home-wifi-boot" with a short timeout, this is called from rc.conf.
    then I put "/usr/bin/netcfg home-wifi" in my /etc/rc.local  , which is exactly the same but has a 30 sec timeout.
    This just does the same thing as I was doing manually, runs netcfg a second time.  It works for me!
    Last edited by jamba (2010-02-14 15:30:58)

  • [SOLVED] MPD: Failed to create socket

    I've  been attempting to get MPD working today and I'm rather stumped here. I got it to start out of its default directory, however, that denied it access to my music folder. So, I switched all of that to a ~/.mpd folder as the wiki page instructed me (https://wiki.archlinux.org/index.php/Mu … _as_a_User), and for purposes of keeping organized.
    Now, however, I'm getting this error whenever I run "mpd ~/.mpd/mpd.conf"
    Failed to bind to '[::]:6600': Failed to create socket: Address family not supported by protocol
    I remember that happening before, and it had to do with user permissions and so on. I think I set "user" to "mpd" that time. "User" is now set to my user, where the .mpd folder is located. Is there a way to allow mpd to continue?
    EDIT: My mpd.conf is:
    playlist_directory "~/.mpd/playlists"
    db_file "~/.mpd/mpd.db"
    log_file "~/.mpd/mpd.log"
    pid_file "~/.mpd/mpd.pid"
    state_file "~/.mpd/mpdstate"
    user "spencer"
    mixer_type "software"
    audio_output {
    type "alsa"
    name "Sound Card"
    bind_to_address "any"
    Last edited by DrKillPatient (2011-08-05 02:38:35)

    DrKillPatient wrote:
    That worked, thanks. At first it gave "failed to open database" but in subsequent startups it's not doing that-- I suppose it created the file at the first time. audio_output's not defined, I suppose that's up to me to set it? It's autodetected at this point and seems to work fine. Should I leave it that way?
    And out of curiosity, what was changed to fix my error?
    First of all: thanks for testing. my setup creates 2 static hosts, instead of letting mpd autodetect it. sometimes ipv6 detection is prefered and this *can* lead to stuff not working properly.
    Also i use absolute paths, to make sure everything works.
    mpds audio output detection works decently, you can of course enable one in ~/.mpdconf to get rid of the warning.
    Also you had one obvious error: you followed mpds wiki entry to start mpd as user. but you defined a user in mpd.conf. this will not work, since mpd can only drop previlegs to that user, when run as root.
    Oh, please mark this thread as solved.
    Last edited by Rasi (2011-08-05 01:26:43)

Maybe you are looking for

  • How to use my time capsule on my new macbook pro retina (time machine error)

    Hello all, I've been using my old mac for a while with my time capsule, but recently I bought the new macbook pro retina and I wanted to use the time capsule as the backup disk on the new one. However, whenever I try to run the backup, a message appe

  • What are the Settings for DefaultFreq as YTD...

    Hi Experts, If I want to set "DefaultFreq" as YTD, what are the settings I have to do. 1) In Application profile (Time Periods, View, and Periods). 2) In Scenario (DefaultFreq and Default View). And also the load data file format. Pls explain me in d

  • My impression after 1 day having my Ipad2

    Hi everybody, I just wanted to share my first impression on my Ipad2. As a non-apple user (I never had any Apple related computer, Ipod,...) In Spain the release dat was last friday. Well here go my impression of my Ipad2 32GB + 3G: 1) First of all t

  • How do I determine logged-in user ID from syscall probe ?

    Hello All - I am trying to determine the actual logged in user ID for the process/thread that is making a syscall from within a dtrace syscall probe handler. If I use the dtrace variable curpsinfo->pr_uid or curpsinfo->pr_euid I can obtain the correc

  • How to implement parametric genericity

    i.e executing the same implementation but be able to accept a range of different types of parameters. In C++ it is done by the use of templates. How to do this in java?