[Solved] Network : static IP config

AKA Not Another Static IP Problem
Hi guys,
I'm trying to setup my network and guess what... it doesn't work
Well, i mean my Arch laptop won't.
The problem : i can't browse websites with the browser
Here are the configs :
/etc/rc.conf :
HOSTNAME="ArchX"
eth0="eth0 192.168.1.3 netmask 255.255.255.0 broadcast 192.168.1.255"
INTERFACES=(eth0)
gateway="default gw 192.168.1.1"
ROUTES=(gateway)
/etc/hosts
127.0.0.1 localhost.localdomain localhost ArchX
/etc/resolv.conf
nameserver 212.71.8.10
nameserver 212.71.0.33
* It works well when using dhcp instead of statip IP
* i can ping and access the router
* i can ping www.google.com
My guess :
In the wiki, there is this line in the /etc/resolv.conf file :
search example.com
And it says to replace it with my domain name
Could it be the problem and if so, how do i know my domain name ?
Is there something i'm missing ?
Thank in advance for your help
Last edited by Kronophage (2009-02-12 01:51:08)

Well... you know what ?
Posting to these forums has some kind of magical effect
I mean almost every time, i get the thing like 10-20 minutes after i hit "post".
And don't think i don't take the time to search answers and try several things, in this case i've been trying & searching for like 2 hours.
Now, i might be dumb... who knows...
Anyway, to give this post even the tiniest interest, i'll put the solution :
in /etc/resolv.conf
nameserver xxx.xxx.xxx.xxx
nameserver xxx.xxx.xxx.xxx
search localdomain #added this line
At least that did the trick for me...
Alright guys have a good day/night, i for myself am going back to pr0n surfing
ps: i double-post so that this thread doesn't stay unanswered.

Similar Messages

[solved] network

Hi all,
I've been trying to set network working on my desktop but haven't been succeeded till now..
I noticed a weird situation (at least to me)
if I do ping google: ping -c 3 www.google.com
I'll get in the final statistics time = 11149ms
but if I do ping google as : ping -c 3 209.85.229.147
I'll get time = 2003 ms
>.< hope anyone knows what's wrong so I can fix this
tks in advance for your time
Last edited by babalu_pt (2010-04-20 22:07:38)

First of all I wanna say tks for all that gave me some replies >.<
apparently I got this working
steps I've done ..
1st remove wicd and reactivate network
2nd setup static IP
3nd deactivate resolv.conf update
4th set nameservers manually
this is my actual config:
rc.conf:
# /etc/rc.conf - Main Configuration for Arch Linux
# HARDWARE
MODULES=(!net-pf-10 !snd_pcsp !pcspkr loop sis900 !mii !ppp_generic !slhc !soundcore)
# one of the 1st things I've done ( heading to solve the problem ) was only load the module I wanted to use
# so I ran hwdetect --show-net to see what it'd show (mii ppp_generic sis900 slhc)
# so I loaded the sis900 and discarded all others... dunno if it has any influence but I did :)
# have I done the correct thing?
# NETWORKING
HOSTNAME="arch"
#Static IP
eth0="eth0 10.10.10.171 netmask 255.255.255.0 broadcast 10.10.10.255"
INTERFACES=(eth0 !wlan0)
gateway="default gw 10.10.10.1"
ROUTES=(gateway)
# DAEMONS
DAEMONS=(network dhcdbd !networkmanager @syslog-ng gpm netfs @crond dbus hal oss !wicd)
# here I did discarded wicd and set back network :)
I only pasted the things that I've changed to set up network.. all others erased them
then I disabled the nameserver refresh at /etc/dhcpd.conf
# A sample configuration for dhcpcd.
# See dhcpcd.conf(5) for details.
# Inform the DHCP server of our hostname for DDNS.
hostname
# To share the DHCP lease across OSX and Windows a ClientID is needed.
# Enabling this may get a different lease than the kernel DHCP client.
# Some upstream DHCP servers may also require a ClientID, such as FRITZ!Box.
#clientid
# A list of options to request from the DHCP server.
option domain_name_servers, domain_name, domain_search, host_name
option classless_static_routes
# Most distributions have NTP support.
option ntp_servers
# Respect the network MTU.
option interface_mtu
# A ServerID is required by RFC2131.
require dhcp_server_identifier
# A hook script is provided to lookup the hostname if not set by the DHCP
# server, but it should not be run by default.
nohook lookup-hostname
noipv4ll
nohook resolv.conf
I just added this last line
then I set up nameservers manualy at /etc/resolv.conf
# Generated by dhcpcd
# /etc/resolv.conf.head can replace this line
nameserver 212.55.154.174
nameserver 212.55.154.190
# /etc/resolv.conf.tail can replace this line
this way it's all working apparently fine
if there is any thing that I've done worng pls correct me.. so I won't have troubles in the future
ps. I guess all I needed to do was to set the nohook at dhcpd.conf and set the nameservers manualy... but I feel ok with the static ip tougth I had to try till make it to work
Last edited by babalu_pt (2010-04-20 22:33:40)

[Solved] Network doesn't work after hibernate?

Hello! This is my first legit Linux install so excuse me if I'm a bit slow. I installed Arch last night and everything went smoothly. However, after I tested out hibernate on my machine, the network doesn't seem to work. Just prior to the hibernate, I installed Pidgin and Skype but they worked alright, so I think that the hibernate caused a problem on eth0.
I have an Asus P8Z68-V Pro motherboard with an Intel 82579V Gigabit Ethernet Controller that's using the e1000e driver. Running "dmesg | grep e1000e" says that it is up.
I'm not entirely clear here, but from reading, I think that I have several ways of connecting to the network, including network, dhcpcd, networkmanager, and wicd. I am using wicd so I did the following (or at least I think I am only using wicd):
#rc.d stop network
#rc.d stop dhcpcd
#rc.d stop networkmanager
Similarly, I put a ! in front of network in rc.conf:
# /etc/rc.conf - Main Configuration for Arch Linux
# LOCALIZATION
# LOCALE: available languages can be listed with the 'locale -a' command
# DAEMON_LOCALE: If set to 'yes', use $LOCALE as the locale during daemon
# startup and during the boot process. If set to 'no', the C locale is used.
# HARDWARECLOCK: set to "", "UTC" or "localtime", any other value will result
# in the hardware clock being left untouched (useful for virtualization)
# Note: Using "localtime" is discouraged, using "" makes hwclock fall back
# to the value in /var/lib/hwclock/adjfile
# TIMEZONE: timezones are found in /usr/share/zoneinfo
# Note: if unset, the value in /etc/localtime is used unchanged
# 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"
DAEMON_LOCALE="no"
HARDWARECLOCK="UTC"
TIMEZONE="America/New_York"
KEYMAP="us"
CONSOLEFONT=
CONSOLEMAP=
USECOLOR="yes"
# HARDWARE
# MODULES: Modules to load at boot-up. Blacklisting is no longer supported.
# Replace every !module by an entry as on the following line in a file in
# /etc/modprobe.d:
# blacklist module
# See "man modprobe.conf" for details.
MODULES=()
# Udev settle timeout (default to 30)
UDEV_TIMEOUT=30
# Scan for FakeRAID (dmraid) Volumes at startup
USEDMRAID="no"
# Scan for BTRFS volumes at startup
USEBTRFS="no"
# 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="Vicious"
# Use 'ip addr' or 'ls /sys/class/net/' to see all available interfaces.
# Wired network setup
# - interface: name of device (required)
# - address: IP address (leave blank for DHCP)
# - netmask: subnet mask (ignored for DHCP) (optional, defaults to 255.255.255.0)
# - broadcast: broadcast address (ignored for DHCP) (optional)
# - gateway: default route (ignored for DHCP)
# Static IP example
# interface=eth0
# address=192.168.0.2
# netmask=255.255.255.0
# broadcast=192.168.0.255
# gateway=192.168.0.1
# DHCP example
# interface=eth0
# address=
# netmask=
# gateway=
interface=eth0
address=
netmask=
broadcast=
gateway=
# Setting this to "yes" will skip network shutdown.
# This is required if your root device is on NFS.
NETWORK_PERSIST="no"
# Enable these netcfg profiles at boot-up. These are useful if you happen to
# need more advanced network features than the simple network service
# supports, such as 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 requires the netcfg package
#NETWORKS=(main)
# 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
# If something other takes care of your hardware clock (ntpd, dual-boot...)
# you should disable 'hwclock' here.
DAEMONS=(hwclock syslog-ng dbus !network netfs crond wicd)
Restarting eth0 through wicd-cli still did not work. I also tried resuscitating the network via instructions on the configure network page before trying to focus solely on wicd.
I found a few similar problems on the forums by searching "wicd hibernate" and tried several solutions but they did not work. Several problems seem to be that the network doesn't work after a suspend because I guess the stuff in RAM did not get saved? But people were able to restart the network by running "/usr/lib/wicd/autoconnect.py" and I wasn't able to get this to work. As a final effort, I added "resume" into mkinitcpio.conf and placed the machine into sleep again to see if it may magically reset something but of course this did not happen .
mkinitcpio.conf:
# vim:set ft=sh
# MODULES
# The following modules are loaded before any boot hooks are
# run. Advanced users may wish to specify all system modules
# in this array. For instance:
# MODULES="piix ide_disk reiserfs"
MODULES=""
# BINARIES
# This setting includes any additional binaries a given user may
# wish into the CPIO image. This is run first, so it may be used to
# override the actual binaries used in a given hook.
# (Existing files are NOT overwritten if already added)
# BINARIES are dependency parsed, so you may safely ignore libraries
BINARIES=""
# FILES
# This setting is similar to BINARIES above, however, files are added
# as-is and are not parsed in any way. This is useful for config files.
# Some users may wish to include modprobe.conf for custom module options
# like so:
# FILES="/etc/modprobe.d/modprobe.conf"
FILES=""
# HOOKS
# This is the most important setting in this file. The HOOKS control the
# modules and scripts added to the image, and what happens at boot time.
# Order is important, and it is recommended that you do not change the
# order in which HOOKS are added. Run 'mkinitcpio -H <hook name>' for
# help on a given hook.
# 'base' is _required_ unless you know precisely what you are doing.
# 'udev' is _required_ in order to automatically load modules
# 'filesystems' is _required_ unless you specify your fs modules in MODULES
# Examples:
## This setup specifies all modules in the MODULES setting above.
## No raid, lvm2, or encrypted root is needed.
# HOOKS="base"
## This setup will autodetect all modules for your system and should
## work as a sane default
# HOOKS="base udev autodetect pata scsi sata filesystems"
## This is identical to the above, except the old ide subsystem is
## used for IDE devices instead of the new pata subsystem.
# HOOKS="base udev autodetect ide scsi sata filesystems"
## This setup will generate a 'full' image which supports most systems.
## No autodetection is done.
# HOOKS="base udev pata scsi sata usb filesystems"
## This setup assembles a pata mdadm array with an encrypted root FS.
## Note: See 'mkinitcpio -H mdadm' for more information on raid devices.
# HOOKS="base udev pata mdadm encrypt filesystems"
## This setup loads an lvm2 volume group on a usb device.
# HOOKS="base udev usb lvm2 filesystems"
HOOKS="base udev autodetect pata scsi sata resume filesystems usbinput"
# COMPRESSION
# Use this to compress the initramfs image. With kernels earlier than
# 2.6.30, only gzip is supported, which is also the default. Newer kernels
# support gzip, bzip2 and lzma. Kernels 2.6.38 and later support xz
# compression.
#COMPRESSION="gzip"
#COMPRESSION="bzip2"
#COMPRESSION="lzma"
#COMPRESSION="xz"
#COMPRESSION="lzop"
# COMPRESSION_OPTIONS
# Additional options for the compressor
#COMPRESSION_OPTIONS=""
Not sure if my fstab.conf is useful but if this has something to do with settings getting "lost" in swap, here it is. Linux is on an SSD and HDD (sda and sdc) and Windows 7 is on a HDD (sdb).
fstab.conf:
# /etc/fstab: static file system information
# <file system> <dir> <type> <options> <dump> <pass>
none /tmp tmpfs nodev,nosuid,noatime,size=2000M,mode=1777 0 0
/dev/sda1 / ext4 defaults,noatime,discard 0 1
/dev/sda2 /home ext4 defaults,noatime,discard 0 2
/dev/sdc1 /boot ext4 defaults 0 1
/dev/sdc2 /var ext4 defaults 0 0
/dev/sdc3 swap swap defaults 0 0
/dev/sdc4 /media/data ext4 defaults 0 0
shm /dev/shm tmpfs nodev,nosuid,size=10G 0 0
Is wicd causing these problems or did I configure something else improperly? Would appreciate any help to get eth0 up again!
Last edited by TheBigCow7 (2011-09-13 17:57:20)

Ok, I think I've made some progress! Hibernate definitely affects my network connection. Could this be a kernel 3.0 problem?
I noticed that ifconfig showed eth0 without an inet addr, just an inet6 addr for the longest time. e1000e seemed to be loading up ok. I'm not certain here, but I think that meant the dhcp settings didn't stick, or something along those lines.
Trying to use dhcpcd like the instructions here did not work. By some chance, one attempt did work and while it did, I downloaded and installed dhclient. After that one successful attempt, renewing the DHCP lease via dhcpcd did not work again.
Luckily though, I found that running "dhclient eth0" worked. My DHCP settings seemed to have somehow gotten messed up after my initial, problematic hibernate to the point where none would stick, even after a reboot. Manually typing in "dhclient eth0" would get eth0 working, so I decided to add it to the bottom of /etc/rc.local, like in the example on the networking page.
Now, eth0 works after a boot. However, after the daemons load up during the boot process, my computer takes a long time to get to the login prompt (this is relatively speaking, since I am on a SSD and the boot process used to be blazing fast before). I'm pretty sure it's because I added "dhclient eth0" to /etc/rc.local.
I should say that even with these changes, after a hibernate, my eth0 still does not work and if it weren't for the edit to /etc/rc.local, eth0's inet settings would still not stick after a reboot (that is to say, the hibernate does do something to my network settings).
Is this the correct/most efficient way to fix my DHCP problem? Can I fix my "eth0 after hibernate" issue? Also, can I make my DHCP settings boot up without changes to /etc/rc.local so that I can get a fast boot again (still not sure how it was able to work before without my edit)?

[solved]Network fails to start sometimes

Hello!
I'm having a problem with my network. Sometimes it fails to start. Usually, a reboot solves this. Here is the error log:
[root@claudia log]# cat errors.log
Aug 6 03:16:28 claudia dhcpcd[3194]: dhcpStart: interface eth0 is not Ethernet or 802.2 Token Ring
rc.conf:
# NETWORKING
HOSTNAME="claudia"
# 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
# Note: to use DHCP, set your interface to be "dhcp" (eth0="dhcp")
lo="lo 127.0.0.1"
eth0="dhcp"
INTERFACES=(lo 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.1.1"
ROUTES=(!gateway)
hosts:
[root@claudia log]# cat /etc/hosts
# /etc/hosts: static lookup table for host names
#<ip> <hostname> <hostname>
127.0.0.1 localhost.localdomain localhost claudia
# End of file
What should I do to solve this?
Thanks and regards,
Gustavo

I'd say it's because since the ethernet over firewire module is loaded too, it's counted as a network device too - and which one gets to be eth0 depends if the NIC or ethernet over firewire module is loaded first. There are many solutions to this:
1) If you don't need ethernet over firewire, keep it from being loaded by putting the module name (eth1394 I think) in MOD_BLACKLIST in /etc/rc.conf, like this:
MOD_BLACKLIST=(eth1394)
2) You can make both eth0 and eth1 (and perhaps other NICs too) start up together (I do this with my 2 NICs). To do that, make the rc.conf network section something like this:
lo="lo 127.0.0.1"
eth0="dhcp"
eth1="dhcp"
INTERFACES=(lo eth0 eth1)
Then you should put a @ in front of "network" ( @network ) in the DAEMONS array unless you like waiting for a NIC that won't start

[SOLVED] Network Difficulties

I have reinstalled Arch this afternoon only to run into a problem I have had in the past. My desktop is connected to a school network, which requires a user name and password. To solve this problem in the past I simply installed elinks from a usb drive. Today, when I run elinks I am told "Unable to retrieve http://www.google.com/: Host not found." I also cannot ping Google. Normally I would be redirect in elinks to the login site. I may very well be making a simple mistake as I am not terribly experienced with networking.
Log of ifconfig -a
Fri Apr 10 04:02:42 2009
eth0 Link encap:Ethernet HWaddr 00:22:15:EA:85:CF
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
Interrupt:17
eth1 Link encap:Ethernet HWaddr 00:22:15:EA:9D:97
BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
Interrupt:18
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
Fri Apr 10 04:02:42 2009
# /etc/hosts: static lookup table for host names
#<ip-address> <hostname.domain.org> <hostname>
127.0.0.1 localhost.localdomain localhost lotte
# End of file
# /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"
# USEDIRECTISA: use direct I/O requests instead of /dev/rtc for hwclock
# 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.utf8"
HARDWARECLOCK="UTC"
USEDIRECTISA="no"
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=()
# 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="lotte"
# 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
#eth0="eth0 192.168.0.2 netmask 255.255.255.0 broadcast 192.168.0.255"
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=(main)
# 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 network netfs @crond)
Last edited by filam (2009-04-11 01:00:41)

Tenken wrote:It looks like you're missing a dhcp client (dhcpcd or dhclient) in your daemons line.
Wow. Thank you. I can't believe I didn't think to check my daemons.

[SOLVED] Network interface enp2s0 no longer detected

Hello,
Yesterday after rebooting, right after Grub, systemd-fsck does its stuff (clearing blocks, etc...) then nothing.
After a quick research I've found that removing "quiet" from the Grub command line would allow more messages to be displayed, which was quite helpful.
This is in fact not a partition mounting problem, here is what I have:
[ OK ] Started Accounts Service.
[ TIME ] Time out waiting for device sys-subsytem-net-devices-enp2s0.device
[ DEPEND ] Dependency failed for dhcpcd on enp2s0.
[ OK ] Reached target Multi-User System.
[ OK ] Reached target Graphical Interface.
I obviously have a networking problem (and probably a "Graphical Interface" or Nvidia related thing problem), so I log in another console, and after doing ip link list, I only have the loopback listed, no enp2s0 or WiFi interface, for some reason they are no longer detected.
I've run the live version of Arch to mount and arch-chroot my partitions, not to mention my network interfaces are detected and I can upgrade things with pacman, I've tried to disable dhcpcd on enp2s0 to avoid the time out thing, and while I can say it does what it's supposed to do, it doesn't solve anything anyway since I'm still stuck at Reached target Graphical Interface. (and don't have any network access, to state the obvious).
I've even thought about a Kernel/Driver problem after an update, but I'm not sure, any idea or some log I can have a look at ?
Thank you for your time.
Last edited by Blaxar (2013-06-25 18:35:50)

Thank for the tip, I've just had a look at pacman.log:
[2013-06-23 11:07] [PACMAN] Running 'pacman -Syu'
[2013-06-23 11:07] [PACMAN] synchronizing package lists
[2013-06-23 11:08] [PACMAN] starting full system upgrade
[2013-06-23 11:10] [PACMAN] upgraded automake (1.13.2-1 -> 1.13.4-1)
[2013-06-23 11:10] [PACMAN] upgraded ca-certificates (20130119-2 -> 20130610-1)
[2013-06-23 11:10] [PACMAN] upgraded cantarell-fonts (0.0.12-1 -> 0.0.13-1)
[2013-06-23 11:10] [PACMAN] upgraded cloog (0.18.0-1 -> 0.18.0-2)
[2013-06-23 11:10] [PACMAN] upgraded libcups (1.6.2-2 -> 1.6.2-3)
[2013-06-23 11:10] [PACMAN] upgraded cups (1.6.2-2 -> 1.6.2-3)
[2013-06-23 11:10] [PACMAN] upgraded e2fsprogs (1.42.7-2 -> 1.42.8-1)
[2013-06-23 11:10] [PACMAN] upgraded glib2 (2.36.2-1 -> 2.36.3-2)
[2013-06-23 11:10] [PACMAN] upgraded xkeyboard-config (2.9-1 -> 2.9-2)
[2013-06-23 11:10] [PACMAN] upgraded iso-codes (3.41-1 -> 3.43-1)
[2013-06-23 11:10] [PACMAN] upgraded gnome-desktop (1:3.8.3-1 -> 1:3.8.3-2)
[2013-06-23 11:10] [PACMAN] upgraded gnome-icon-theme-symbolic (3.8.2.2-1 -> 3.8.3-1)
[2013-06-23 11:10] [PACMAN] upgraded gzip (1.5-3 -> 1.6-1)
[2013-06-23 11:10] [PACMAN] upgraded lib32-e2fsprogs (1.42.7-1 -> 1.42.8-1)
[2013-06-23 11:10] [PACMAN] upgraded lib32-glib2 (2.36.2-1 -> 2.36.3-2)
[2013-06-23 11:10] [PACMAN] upgraded lib32-krb5 (1.11.2-1 -> 1.11.3-1)
[2013-06-23 11:10] [PACMAN] upgraded libxi (1.7.1-1 -> 1.7.1-2)
[2013-06-23 11:10] [PACMAN] upgraded lib32-libxi (1.7.1-1 -> 1.7.1-2)
[2013-06-23 11:10] [PACMAN] upgraded mesa (9.1.3-1 -> 9.1.3-2)
[2013-06-23 11:10] [PACMAN] upgraded lib32-mesa (9.1.3-2 -> 9.1.3-3)
[2013-06-23 11:10] [PACMAN] upgraded libbsd (0.5.2-1 -> 0.5.2-2)
[2013-06-23 11:10] [PACMAN] upgraded libltdl (2.4.2-9 -> 2.4.2-10)
[2013-06-23 11:10] [PACMAN] upgraded libmbim (1.0.0-1 -> 1.2.0-1)
[2013-06-23 11:10] [PACMAN] upgraded libnautilus-extension (3.8.1-1 -> 3.8.2-1)
[2013-06-23 11:10] [PACMAN] upgraded libpeas (1.8.0-2 -> 1.8.1-1)
[2013-06-23 11:10] [PACMAN] upgraded libqmi (1.2.0-2 -> 1.4.0-1)
[2013-06-23 11:10] [PACMAN] upgraded libreoffice-uk (4.0.3-1 -> 4.0.4-1)
[2013-06-23 11:10] [PACMAN] upgraded libtool (2.4.2-9 -> 2.4.2-10)
[2013-06-23 11:10] [PACMAN] upgraded libusb-compat (0.1.4-2 -> 0.1.5-1)
[2013-06-23 11:10] [PACMAN] upgraded libxv (1.0.8-1 -> 1.0.9-1)
[2013-06-23 11:10] [ALPM-SCRIPTLET] >>> Updating module dependencies. Please wait ...
[2013-06-23 11:10] [ALPM-SCRIPTLET] >>> Generating initial ramdisk, using mkinitcpio. Please wait...
[2013-06-23 11:10] [ALPM-SCRIPTLET] ==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'default'
[2013-06-23 11:10] [ALPM-SCRIPTLET] -> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux.img
[2013-06-23 11:10] [ALPM-SCRIPTLET] ==> Starting build: 3.9.7-1-ARCH
[2013-06-23 11:10] [ALPM-SCRIPTLET] -> Running build hook: [base]
[2013-06-23 11:10] [ALPM-SCRIPTLET] -> Running build hook: [udev]
[2013-06-23 11:10] [ALPM-SCRIPTLET] -> Running build hook: [autodetect]
[2013-06-23 11:10] [ALPM-SCRIPTLET] -> Running build hook: [modconf]
[2013-06-23 11:10] [ALPM-SCRIPTLET] -> Running build hook: [block]
[2013-06-23 11:10] [ALPM-SCRIPTLET] -> Running build hook: [filesystems]
[2013-06-23 11:10] [ALPM-SCRIPTLET] -> Running build hook: [keyboard]
[2013-06-23 11:10] [ALPM-SCRIPTLET] -> Running build hook: [fsck]
[2013-06-23 11:10] [ALPM-SCRIPTLET] ==> Generating module dependencies
[2013-06-23 11:10] [ALPM-SCRIPTLET] ==> Creating gzip initcpio image: /boot/initramfs-linux.img
[2013-06-23 11:10] [ALPM-SCRIPTLET] ==> Image generation successful
[2013-06-23 11:10] [ALPM-SCRIPTLET] ==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'fallback'
[2013-06-23 11:10] [ALPM-SCRIPTLET] -> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-fallback.img -S autodetect
[2013-06-23 11:10] [ALPM-SCRIPTLET] ==> Starting build: 3.9.7-1-ARCH
[2013-06-23 11:10] [ALPM-SCRIPTLET] -> Running build hook: [base]
[2013-06-23 11:10] [ALPM-SCRIPTLET] -> Running build hook: [udev]
[2013-06-23 11:10] [ALPM-SCRIPTLET] -> Running build hook: [modconf]
[2013-06-23 11:10] [ALPM-SCRIPTLET] -> Running build hook: [block]
[2013-06-23 11:10] [ALPM-SCRIPTLET] ==> WARNING: Possibly missing firmware for module: aic94xx
[2013-06-23 11:10] [ALPM-SCRIPTLET] ==> WARNING: Possibly missing firmware for module: bfa
[2013-06-23 11:10] [ALPM-SCRIPTLET] -> Running build hook: [filesystems]
[2013-06-23 11:11] [ALPM-SCRIPTLET] -> Running build hook: [keyboard]
[2013-06-23 11:11] [ALPM-SCRIPTLET] -> Running build hook: [fsck]
[2013-06-23 11:11] [ALPM-SCRIPTLET] ==> Generating module dependencies
[2013-06-23 11:11] [ALPM-SCRIPTLET] ==> Creating gzip initcpio image: /boot/initramfs-linux-fallback.img
[2013-06-23 11:11] [ALPM-SCRIPTLET] ==> Image generation successful
[2013-06-23 11:11] [PACMAN] upgraded linux (3.9.6-1 -> 3.9.7-1)
[2013-06-23 11:11] [PACMAN] upgraded logrotate (3.8.4-2 -> 3.8.5-1)
[2013-06-23 11:11] [PACMAN] upgraded nautilus (3.8.1-1 -> 3.8.2-1)
[2013-06-23 11:11] [PACMAN] upgraded nvidia (319.23-2 -> 319.23-3)
[2013-06-23 11:11] [PACMAN] upgraded openresolv (3.5.4-3 -> 3.5.5-1)
[2013-06-23 11:11] [PACMAN] upgraded pacman (4.1.1-1 -> 4.1.2-1)
[2013-06-23 11:11] [PACMAN] upgraded poppler (0.22.4-1 -> 0.22.5-1)
[2013-06-23 11:11] [PACMAN] upgraded poppler-glib (0.22.4-1 -> 0.22.5-1)
[2013-06-23 11:11] [PACMAN] upgraded ppp (2.4.5-7 -> 2.4.5-8)
[2013-06-23 11:13] [PACMAN] Running 'pacman -S libreoffice-fr'
[2013-06-23 11:13] [PACMAN] installed libreoffice-fr (4.0.4-1)
[2013-06-23 11:13] [PACMAN] Running 'pacman -S libreoffice'
[2013-06-23 11:15] [PACMAN] installed raptor (2.0.9-2)
[2013-06-23 11:15] [PACMAN] installed rasqal (1:0.9.30-1)
[2013-06-23 11:15] [PACMAN] installed redland (1:1.0.16-2)
[2013-06-23 11:15] [PACMAN] installed hyphen (2.8.6-1)
[2013-06-23 11:15] [PACMAN] installed boost-libs (1.53.0-2)
[2013-06-23 11:15] [PACMAN] installed clucene (2.3.3.4-6)
[2013-06-23 11:15] [ALPM-SCRIPTLET] * see https://wiki.archlinux.org/index.php/LibreOffice
[2013-06-23 11:15] [ALPM-SCRIPTLET] -------------------------------------------------------------------
[2013-06-23 11:15] [ALPM-SCRIPTLET] LibreOffice has been split into several packages:
[2013-06-23 11:15] [ALPM-SCRIPTLET] - libreoffice-common
[2013-06-23 11:15] [ALPM-SCRIPTLET] - libreoffice-{base,calc,draw,impress,math,writer} - frontend applications
[2013-06-23 11:15] [ALPM-SCRIPTLET] - libreoffice-{gnome,kde4} - desktop integration plugins
[2013-06-23 11:15] [ALPM-SCRIPTLET] - libreoffice-{sdk,sdk-doc} - add-on and doc for programming using
[2013-06-23 11:15] [ALPM-SCRIPTLET] the LibreOffice APIs and for creating
[2013-06-23 11:15] [ALPM-SCRIPTLET] extensions (UNO components).
[2013-06-23 11:15] [ALPM-SCRIPTLET] -------------------------------------------------------------------
[2013-06-23 11:15] [ALPM-SCRIPTLET] * you need to install at least one libreoffice-langpack
[2013-06-23 11:15] [ALPM-SCRIPTLET] * you may want to pacman -Ss libreoffice-extensions
[2013-06-23 11:15] [ALPM-SCRIPTLET] to see what additional extensions are prepared to install
[2013-06-23 11:15] [ALPM-SCRIPTLET] * it's recommended to install {hunspell,mythes,hyphen}-xx pkg
[2013-06-23 11:15] [ALPM-SCRIPTLET] for spell checking
[2013-06-23 11:15] [ALPM-SCRIPTLET] * make sure you have installed some ttf font (ttf-dejavu recommended)
[2013-06-23 11:15] [PACMAN] installed libreoffice-common (4.0.4-1)
[2013-06-23 11:15] [PACMAN] installed libreoffice-base (4.0.4-1)
[2013-06-23 11:15] [PACMAN] installed lpsolve (5.5.2.0-2)
[2013-06-23 11:15] [PACMAN] installed libreoffice-calc (4.0.4-1)
[2013-06-23 11:15] [PACMAN] installed libreoffice-draw (4.0.4-1)
[2013-06-23 11:15] [PACMAN] installed libreoffice-gnome (4.0.4-1)
[2013-06-23 11:15] [PACMAN] installed libreoffice-impress (4.0.4-1)
[2013-06-23 11:15] [PACMAN] installed libreoffice-math (4.0.4-1)
[2013-06-23 11:15] [PACMAN] installed libwpd (0.9.6-1)
[2013-06-23 11:15] [PACMAN] installed libwps (0.2.9-1)
[2013-06-23 11:15] [PACMAN] installed libreoffice-writer (4.0.4-1)
[2013-06-23 19:57] [PACMAN] Running 'pacman -S ssh-key'
[2013-06-23 23:01] [PACMAN] Running 'pacman -Syu'
[2013-06-23 23:01] [PACMAN] synchronizing package lists
--From the live CD from now on--
[2013-06-23 23:29] [PACMAN] Running 'pacman -Syu'
[2013-06-23 23:29] [PACMAN] synchronizing package lists
[2013-06-23 23:30] [PACMAN] starting full system upgrade
[2013-06-23 23:32] [PACMAN] removed grub-bios (2.00-2)
[2013-06-23 23:32] [PACMAN] removed grub-common (2.00-2)
[2013-06-23 23:32] [ALPM-SCRIPTLET] Generating grub.cfg.example config file...
[2013-06-23 23:32] [ALPM-SCRIPTLET] This may fail on some machines running a custom kernel.
[2013-06-23 23:32] [ALPM-SCRIPTLET] done.
[2013-06-23 23:32] [PACMAN] installed grub (2.00-1)
[2013-06-23 23:32] [PACMAN] upgraded lib32-libjpeg-turbo (1.3.0-2 -> 1.3.0-3)
[2013-06-23 23:32] [PACMAN] upgraded libgsf (1.14.26-1 -> 1.14.27-1)
[2013-06-23 23:32] [PACMAN] upgraded libquvi-scripts (0.4.15-1 -> 0.4.16-1)
Among all of that, I've spotted this:
[2013-06-23 11:10] [ALPM-SCRIPTLET] ==> WARNING: Possibly missing firmware for module: aic94xx
[2013-06-23 11:10] [ALPM-SCRIPTLET] ==> WARNING: Possibly missing firmware for module: bfa
Do you think this may explain something ?
Anyway, from lspci:
00:00.0 Host bridge: Intel Corporation Core Processor DMI (rev 11)
00:03.0 PCI bridge: Intel Corporation Core Processor PCI Express Root Port 1 (rev 11)
00:08.0 System peripheral: Intel Corporation Core Processor System Management Registers (rev 11)
00:08.1 System peripheral: Intel Corporation Core Processor Semaphore and Scratchpad Registers (rev 11)
00:08.2 System peripheral: Intel Corporation Core Processor System Control and Status Registers (rev 11)
00:08.3 System peripheral: Intel Corporation Core Processor Miscellaneous Registers (rev 11)
00:10.0 System peripheral: Intel Corporation Core Processor QPI Link (rev 11)
00:10.1 System peripheral: Intel Corporation Core Processor QPI Routing and Protocol Registers (rev 11)
00:16.0 Communication controller: Intel Corporation 5 Series/3400 Series Chipset HECI Controller (rev 06)
00:1a.0 USB controller: Intel Corporation 5 Series/3400 Series Chipset USB2 Enhanced Host Controller (rev 06)
00:1b.0 Audio device: Intel Corporation 5 Series/3400 Series Chipset High Definition Audio (rev 06)
00:1c.0 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI Express Root Port 1 (rev 06)
00:1c.2 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI Express Root Port 3 (rev 06)
00:1c.3 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI Express Root Port 4 (rev 06)
00:1c.5 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI Express Root Port 6 (rev 06)
00:1d.0 USB controller: Intel Corporation 5 Series/3400 Series Chipset USB2 Enhanced Host Controller (rev 06)
00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev a6)
00:1f.0 ISA bridge: Intel Corporation 5 Series Chipset LPC Interface Controller (rev 06)
00:1f.2 RAID bus controller: Intel Corporation 82801 SATA Controller [RAID mode] (rev 06)
00:1f.3 SMBus: Intel Corporation 5 Series/3400 Series Chipset SMBus Controller (rev 06)
01:00.0 VGA compatible controller: NVIDIA Corporation GT200 [GeForce GTX 260] (rev a1)
02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168 PCI Express Gigabit Ethernet controller (rev 03)
03:00.0 FireWire (IEEE 1394): VIA Technologies, Inc. VT6315 Series Firewire Controller
04:00.0 Multimedia video controller: Conexant Systems, Inc. CX23887/8 PCIe Broadcast Audio and Video Decoder with 3D Comb (rev 04)
05:00.0 Network controller: Ralink corp. RT3090 Wireless 802.11n 1T/1R PCIe
ff:00.0 Host bridge: Intel Corporation Core Processor QuickPath Architecture Generic Non-Core Registers (rev 04)
ff:00.1 Host bridge: Intel Corporation Core Processor QuickPath Architecture System Address Decoder (rev 04)
ff:02.0 Host bridge: Intel Corporation Core Processor QPI Link 0 (rev 04)
ff:02.1 Host bridge: Intel Corporation Core Processor QPI Physical 0 (rev 04)
ff:03.0 Host bridge: Intel Corporation Core Processor Integrated Memory Controller (rev 04)
ff:03.1 Host bridge: Intel Corporation Core Processor Integrated Memory Controller Target Address Decoder (rev 04)
ff:03.4 Host bridge: Intel Corporation Core Processor Integrated Memory Controller Test Registers (rev 04)
ff:04.0 Host bridge: Intel Corporation Core Processor Integrated Memory Controller Channel 0 Control Registers (rev 04)
ff:04.1 Host bridge: Intel Corporation Core Processor Integrated Memory Controller Channel 0 Address Registers (rev 04)
ff:04.2 Host bridge: Intel Corporation Core Processor Integrated Memory Controller Channel 0 Rank Registers (rev 04)
ff:04.3 Host bridge: Intel Corporation Core Processor Integrated Memory Controller Channel 0 Thermal Control Registers (rev 04)
ff:05.0 Host bridge: Intel Corporation Core Processor Integrated Memory Controller Channel 1 Control Registers (rev 04)
ff:05.1 Host bridge: Intel Corporation Core Processor Integrated Memory Controller Channel 1 Address Registers (rev 04)
ff:05.2 Host bridge: Intel Corporation Core Processor Integrated Memory Controller Channel 1 Rank Registers (rev 04)
ff:05.3 Host bridge: Intel Corporation Core Processor Integrated Memory Controller Channel 1 Thermal Control Registers (rev 04)
and ip a:
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
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
Last edited by Blaxar (2013-06-24 20:10:25)

[SOLVED] Network Manager cannot connect to wifi after suspend

Hi,
There appears to be similar threads recently, but they relate to no wifi at all. I did some updates today, and now if I suspend or hibernate, network manager cannot reconnect to my wifi. It will (after a while) ask me to authenticate, but still fails. Nothing works except a reboot where it connects without issue.
It was fine yesterday, has only started today. Here is my pacman log for today's updates:
[2012-04-11 17:13] upgraded libpciaccess (0.13-1 -> 0.13.1-1)
[2012-04-11 17:13] upgraded lib32-libpciaccess (0.13-1 -> 0.13.1-1)
[2012-04-11 17:13] upgraded mpd (0.16.7-3 -> 0.16.8-2)
[2012-04-11 17:13] upgraded xorg-server-common (1.12.0.901-1 -> 1.12.0.902-1)
[2012-04-11 17:13] upgraded xorg-server (1.12.0.901-1 -> 1.12.0.902-1)
[2012-04-11 17:13] upgraded xorg-server-devel (1.12.0.901-1 -> 1.12.0.902-1)
[2012-04-11 17:13] upgraded xorg-server-xephyr (1.12.0.901-1 -> 1.12.0.902-1)
Here is my messages log:
Apr 11 18:38:28 localhost NetworkManager[1475]: <info> Auto-activating connection 'Padfoot'.
Apr 11 18:38:28 localhost NetworkManager[1475]: <info> Activation (wlan0) starting connection 'Padfoot'
Apr 11 18:38:28 localhost NetworkManager[1475]: <info> (wlan0): device state change: disconnected -> prepare (reason 'none') [30 40 0]
Apr 11 18:38:28 localhost NetworkManager[1475]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled...
Apr 11 18:38:28 localhost NetworkManager[1475]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) started...
Apr 11 18:38:28 localhost NetworkManager[1475]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled...
Apr 11 18:38:28 localhost NetworkManager[1475]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) complete.
Apr 11 18:38:28 localhost NetworkManager[1475]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) starting...
Apr 11 18:38:28 localhost NetworkManager[1475]: <info> (wlan0): device state change: prepare -> config (reason 'none') [40 50 0]
Apr 11 18:38:28 localhost NetworkManager[1475]: <info> Activation (wlan0/wireless): connection 'Padfoot' has security, and secrets exist. No new secrets needed.
Apr 11 18:38:28 localhost NetworkManager[1475]: <info> Config: added 'ssid' value 'Padfoot'
Apr 11 18:38:28 localhost NetworkManager[1475]: <info> Config: added 'scan_ssid' value '1'
Apr 11 18:38:28 localhost NetworkManager[1475]: <info> Config: added 'key_mgmt' value 'WPA-PSK'
Apr 11 18:38:28 localhost NetworkManager[1475]: <info> Config: added 'psk' value '<omitted>'
Apr 11 18:38:28 localhost NetworkManager[1475]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) complete.
Apr 11 18:38:28 localhost NetworkManager[1475]: <info> Config: set interface ap_scan to 1
Apr 11 18:38:28 localhost NetworkManager[1475]: <info> (wlan0): supplicant interface state: disconnected -> scanning
Apr 11 18:38:29 localhost NetworkManager[1475]: <info> (wlan0): supplicant interface state: scanning -> authenticating
Apr 11 18:38:53 localhost NetworkManager[1475]: <warn> Activation (wlan0/wireless): association took too long.
Apr 11 18:38:53 localhost NetworkManager[1475]: <info> (wlan0): device state change: config -> need-auth (reason 'none') [50 60 0]
Apr 11 18:38:53 localhost NetworkManager[1475]: <warn> Activation (wlan0/wireless): asking for new secrets
Apr 11 18:38:53 localhost NetworkManager[1475]: <info> (wlan0): supplicant interface state: authenticating -> disconnected
Apr 11 18:38:53 localhost NetworkManager[1475]: <warn> Couldn't disconnect supplicant interface: This interface is not connected.
Apr 11 18:38:53 localhost NetworkManager[1475]: <warn> No agents were available for this request.
Apr 11 18:38:53 localhost NetworkManager[1475]: <info> (wlan0): device state change: need-auth -> failed (reason 'no-secrets') [60 120 7]
Apr 11 18:38:53 localhost NetworkManager[1475]: <warn> Activation (wlan0) failed for access point (Padfoot)
Apr 11 18:38:53 localhost NetworkManager[1475]: <info> Marking connection 'Padfoot' invalid.
Apr 11 18:38:53 localhost NetworkManager[1475]: <warn> Activation (wlan0) failed.
Apr 11 18:38:53 localhost NetworkManager[1475]: <info> (wlan0): device state change: failed -> disconnected (reason 'none') [120 30 0]
Apr 11 18:38:53 localhost NetworkManager[1475]: <info> (wlan0): deactivating device (reason 'none') [0]
Last edited by Padfoot (2012-04-13 23:47:55)

heiko wrote:linux-3.3.2 is released on www.kernel.org and reverts the patch that introduced this problem.
For those using the arch repo kernel the next release will solve this issue. So I suggest waiting for this (no more than a few days) and use the LTS kernel in the meantime (or using a fixed ath9k module if already built).
Thanks for that heiko. I thought that would be the case, hence I just waited.
Will mark this as solved.
Cheers.

[Solved] Network does not starts on every boot

Yet another problem on fresh arch...
Network service does not starts every time I booting my headless. For every 10 attempts service starts 5 or 6 times only.
Ping says: Networking unreachable.
systemctl status network:
network.service - Static IP Connectivity
Loaded: loaded (/etc/systemd/system/network.service; enabled)
Active: inactive (dead)
'systemctl start network' just hangs. In order to get it start I have to reboot the box hoping next boot service will start.
I am not using dhcp (if it makes a sence). Service was configured as described in wiki for static IP assigning.
The config itself:
[Unit]
Description=Static IP Connectivity
Wants=network.target
Before=network.target
BindsTo=sys-subsystem-net-devices-enp4s1.device
After=sys-subsystem-net-devices-enp4s1.device
[Service]
Type=oneshot
RemainAfterExit=yes
ExecStart=/sbin/ip link set dev enp4s1 up
ExecStart=/sbin/ip addr add 192.168.1.5/24 dev enp4s1
ExecStart=/sbin/ip route add default via 192.168.1.1
ExecStop=/sbin/ip addr flush dev enp4s1
ExecStop=/sbin/ip link set dev enp4s1 down
[Install]
WantedBy=multi-user.target
What's wrong?
Thanks in advance for any help.
Last edited by chord (2013-06-03 17:04:55)

Thaks for your reply.
I got this interface name from ip addr, how it should be named if 'enp4s1' is wrong?
journalctl is here: http://bpaste.net/show/104083/
I found only one string realted to this device name:
Jun 03 15:18:23 localhost systemd[1]: Expecting device sys-subsystem-net-devices-enp4s1.device...
Is there some other logs where it can be checked?

[SOLVED] netcfg static IP not persisting across reboots in VM

I ran into an issue with netcfg static IP not persisting across reboots in a VM. I figured it out, but it took me awhile as a brand new user, so I thought I'd post it.
Setup
Using VMWare Workstation 8.0.3 build-703057 with bridged networking
Host OS: Linux Mint 14 64-bit
Guest OS: Arch Linux 2013.03.01 x86_64
Given a fresh install on the guest, setup netcfg:
cd /etc/network.d
cp examples/ethernet-static ./myprofile
nano myprofile
# customize this file. I also added NETMASK='255.255.255.0'
systemctl enable netcfg@myprofile
systemctl start netcfg@myprofile
Test the configuration. It should be successful:
ping google.com
Problem
See if the changes survive a reboot.
reboot
ping google.com
I got the error "connect: Network is unreachable".
Check the logs:
journalctl
G
I found the following netcfg failure..
[email protected]: main process exited, code=exited, status=1/FAILURE
..prior to the following device initialization:
kernel: e1000 0000:02:00.0 eth0: Intel(R) PRO/1000 Network Connection
system-udevd[117]: renamed network interface eth0 to emp2s0
Solution
It looks like netcfg is being started before the device it depends on has been initialized. Inform systemd of the
dependency so they start in the proper order:
# nano /etc/systemd/system/multi-user.target.wants/[email protected]
# Add the following to [Unit]. Remember to replace enp2s0 with your device name.
Requires=sys-subsystem-net-devices-enp2s0.device
After=sys-subsystem-net-devices-enp2s0.device
Test again:
reboot
ping google.com
This should now be successful.

fukawi2 wrote:
$ man netcfg-profiles wrote:
Miscellaneous options
IPCFG
Array of arguments to pass to ip. The power of this options is
that it allows both simple and complicated routing
configurations, within the framework of netcfg.
SKIPNOCARRIER
‘yes’/‘no’. Don’t abort interface setup if no carrier is
found.
Thank you, [Solved].

[SOLVED] network randomly doesn't work after reboot (e100)

Hi
Lately I have some weird issues with network. I shutdown computer during night, so basicly I reboot it at least once per day and every now and then without any pattern network doesn't work at all and so far only solution I have found is to reboot (again).
Before anything else I'm sure it's not hardware problem, since other OS on same computer don't have any issues, neither is router since other devices in network from laptops to mobile phones work flawless.
Relevant info and what I have found so far (not everything is copy/pasted so there may be some typos):
$less rc.conf (network part)
eth1="eth1 192.168.1.242 netmask 255.255.255.0 broadcast 192.168.1.255
INTERFACES=(eth1)
gateway="default gw 192.168.1.1"
ROUTES=(gateway)
$ifconfig
eth1 Link encap:Ethernet HWaddr 00:D0:B7:5A:7A:A9
inet addr:192.168.1.242 Bcast:192.168.1.255 Mask:255.255.255.0
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:380 errors:0 dropped:0 overruns:0 frame:0
TX packets:380 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:36154 (35.3 Kb) TX bytes:36154 (35.3 Kb)
$route
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
192.168.1.0 * 255.255.255.0 U 0 0 0 eth1
default 192.168.1.1 0.0.0.0 UG 0 0 0 eth1
$ping 192.168.1.1
PING 192.168.1.1 (192.168.1.1) 56(84) bytes of data
From 192.168.1.242 icmp_seq=2 Destination Host Unreachable
So basicly network is dead, can't even ping router, cable connection is detected tho (lights are on). I have tried to restart newtork with /etc/rc.d/network stop/start, nothing. Only clue is dmesg.
$dmesg
Linux version 2.6.30-ARCH (root@T-POWA-LX) (gcc version 4.4.1 (GCC) ) #1 SMP PREEMPT Fri Jul 31 07:30:28 CEST 2009
e100: Intel(R) PRO/100 Network Driver, 3.5.24-k2-NAPI
e100: Copyright(c) 1999-2006 Intel Corporation
e100 0000:03:07.0: PCI INT A -> Link[APC2] -> GSI 17 (level, low) -> IRQ 17
e100 0000:03:07.0: PME# disabled
e100: eth1: e100_probe: addr 0xfdfff000, irq 17, MAC addr 00:d0:b7:5a:7a:a9
e100 0000:03:07.0: firmware: requesting e100/d101m_ucode.bin
ADDRCONF(NETDEV_UP): eth1: link is not ready
modrope -r e100 and then reloading it doesn't help either, but reboot does (once I had to reboot twice tho).
Anyone with more clue and ideas then me, it's getting really annoying, it also kill whole KDE plasma-desktop for couple of minutes before plasmoids find out network is really down and I'm not really fan of morning "gamble". I can't pinpoint some hard date/update when this started to happening because like I said it's random but last couple of months should be quite accurate. Thanks in advance.
EDIT: dmesg when network works:
tilen@pikmin ~]$ dmesg | grep e100
pci 0000:03:07.0: Firmware left e100 interrupts enabled; disabling
e100: Intel(R) PRO/100 Network Driver, 3.5.24-k2-NAPI
e100: Copyright(c) 1999-2006 Intel Corporation
e100 0000:03:07.0: PCI INT A -> Link[APC2] -> GSI 17 (level, low) -> IRQ 17
e100 0000:03:07.0: PME# disabled
e100: eth0: e100_probe: addr 0xfdfff000, irq 17, MAC addr 00:d0:b7:5a:7a:a9
Last edited by NoOrdinary (2009-09-05 09:47:20)

I don't have anything special set at router but I doubt rc.conf play any role. I will try to set it up with dhcp (but I think I have tried that already) if there is any change.
This morning I had to reboot twice, so new kernel didn't help. Fowler, what network card are you using, also e100 (well or some intel)? I dunno, should this be handed to the kernel team? If it will piss me enough one morning I'll just go and buy a new network card, just wanna be sure that will really solve the problem.
UPDATE: OK, this is just silly. I remebered I have acctualy onboard LAN so I edited rc.conf and dived into the dust under my desk to move cable and there I found out it was acctual onboard in use all the time Now this dosen't make much sense to me anymore, when I can't get net up all the stuff in dmesg is e100 related. Anyway, I connected network to e100 and rebooted, suprise, same story. Dmesg reported again link was not ready. I edited rc.conf to
INTERFACES=(eth0 !eth1)
in case this has anything to do with proper timing at assigning whatever needs to be assigned to network cards at boot so I'm sure just 1 card with all info provided get's kicked in at boot. First reboot after that works, it dosen't prove anything yet but at leat it's some kind of progress in recognising proper cause.
UPDATE 2: Nah, still happens. Googling for "no link during initialization" show a lot of familiar problems, almost all on nforce motherboards and mine is nforce too. I just don't get it why this mess seperate PCI network card. In any case it's extremely annoying.
Last edited by NoOrdinary (2009-09-02 11:46:27)

[SOLVED]Xorg.conf, mouse config problem

The Rapoo M765 mouse can not work properly under normal mouse configuration.
The mouse goes beyond controll when config as below:
hacksign@XSign [14:13:13] : ~
>> cat /etc/X11/xorg.conf.d/50-mouse-acceleration.conf
#Section "InputClass"
# Identifier "Mouse2"
# MatchProduct "RAPOO RAPOO 2.4G Remote Mouse"
# MatchIsPointer "yes"
# MatchDevicePath "/dev/input/event*"
# Driver "mouse"
# Option "Protocol" "auto"
# Option "Emulate3Buttons" "no"
# Option "Buttons" "7"
# Option "ButtonMapping" "1 2 3 6 7"
#EndSection
When there is no any configuration, the mouse can work abnormally. Movement and right/left click work fine, but I can not use scroll wheel,and the "go forward"&"go backward" mouse key can not work too.
(I know Option "ZAxisMapping" "4 5" is the configuration of scroll wheel emulation.)
The real problem is 'mouse beyond controll',the cursor goes crazyly on screen ....
I guess it is something wrong of ButtonMapping option. But when I tried to get button number from command xev,when scroll wheel scrolles, I get something below(the scroll wheel movement is identified as a key event~):
//left click
ButtonPress event, serial 34, synthetic NO, window 0x4a00001,
root 0x264, subw 0x0, time 3766452, (135,143), root:(2287,595),
state 0x0, button 1, same_screen YES
ButtonRelease event, serial 34, synthetic NO, window 0x4a00001,
root 0x264, subw 0x0, time 3766588, (135,143), root:(2287,595),
state 0x100, button 1, same_screen YES
//right click
ButtonPress event, serial 34, synthetic NO, window 0x4a00001,
root 0x264, subw 0x0, time 3767716, (135,143), root:(2287,595),
state 0x0, button 3, same_screen YES
ButtonRelease event, serial 34, synthetic NO, window 0x4a00001,
root 0x264, subw 0x0, time 3767852, (135,143), root:(2287,595),
state 0x400, button 3, same_screen YES
//mouse scroll, identified as keyboard event(?)
KeyRelease event, serial 34, synthetic NO, window 0x4a00001,
root 0x264, subw 0x0, time 3769332, (135,143), root:(2287,595),
state 0x0, keycode 123 (keysym 0x1008ff13, XF86AudioRaiseVolume), same_screen YES,
XLookupString gives 0 bytes:
XFilterEvent returns: False
KeyPress event, serial 34, synthetic NO, window 0x4a00001,
root 0x264, subw 0x0, time 3769332, (135,143), root:(2287,595),
state 0x0, keycode 122 (keysym 0x1008ff11, XF86AudioLowerVolume), same_screen YES,
XLookupString gives 0 bytes:
XmbLookupString gives 0 bytes:
XFilterEvent returns: False
here is some Information(I dont know why the mouse is identified as 'type:KEYBOARD'):
hacksign@XSign [14:55:03] : ~
>> xinput
⎡ Virtual core pointer id=2 [master pointer (3)]
⎜ ↳ Virtual core XTEST pointer id=4 [slave pointer (2)]
⎜ ↳ RAPOO RAPOO 2.4G Remote Mouse id=13 [slave pointer (2)]
⎜ ↳ SynPS/2 Synaptics TouchPad id=15 [slave pointer (2)]
⎜ ↳ TPPS/2 IBM TrackPoint id=16 [slave pointer (2)]
⎣ Virtual core keyboard id=3 [master keyboard (2)]
↳ Virtual core XTEST keyboard id=5 [slave keyboard (3)]
↳ Power Button id=6 [slave keyboard (3)]
↳ Video Bus id=7 [slave keyboard (3)]
↳ Sleep Button id=8 [slave keyboard (3)]
↳ Heng Yu Technology Poker Pro S id=9 [slave keyboard (3)]
↳ Heng Yu Technology Poker Pro S id=10 [slave keyboard (3)]
↳ Integrated Camera id=11 [slave keyboard (3)]
↳ RAPOO RAPOO 2.4G Remote Mouse id=12 [slave keyboard (3)]
↳ AT Translated Set 2 keyboard id=14 [slave keyboard (3)]
↳ ThinkPad Extra Buttons id=17 [slave keyboard (3)]
hacksign@XSign [14:55:06] : ~
>> xinput list-props 13
Device 'RAPOO RAPOO 2.4G Remote Mouse':
Device Enabled (142): 1
Coordinate Transformation Matrix (144): 1.000000, 0.000000, 0.000000, 0.000000, 1.000000, 0.000000, 0.000000, 0.000000, 1.000000
Device Accel Profile (270): 0
Device Accel Constant Deceleration (271): 1.000000
Device Accel Adaptive Deceleration (272): 1.000000
Device Accel Velocity Scaling (273): 10.000000
Device Product ID (260): 9390, 8192
Device Node (261): "/dev/input/event8"
Evdev Axis Inversion (274): 0, 0
Evdev Axes Swap (276): 0
Axis Labels (277): "Rel X" (152), "Rel Y" (153), "Rel Horiz Wheel" (267), "Rel Dial" (268), "Rel Vert Wheel" (269)
Button Labels (278): "Button Left" (145), "Button Middle" (146), "Button Right" (147), "Button Wheel Up" (148), "Button Wheel Down" (149), "Button Horiz Wheel Left" (150), "Button Horiz Wheel Right" (151), "Button Side" (265), "Button Extra" (266), "Button Unknown" (263), "Button Unknown" (263), "Button Unknown" (263), "Button Unknown" (263)
Evdev Scrolling Distance (279): 1, 1, 1
Evdev Middle Button Emulation (280): 0
Evdev Middle Button Timeout (281): 50
Evdev Third Button Emulation (282): 0
Evdev Third Button Emulation Timeout (283): 1000
Evdev Third Button Emulation Button (284): 3
Evdev Third Button Emulation Threshold (285): 20
Evdev Wheel Emulation (286): 0
Evdev Wheel Emulation Axes (287): 0, 0, 4, 5
Evdev Wheel Emulation Inertia (288): 10
Evdev Wheel Emulation Timeout (289): 200
Evdev Wheel Emulation Button (290): 4
Evdev Drag Lock Buttons (291): 0
hacksign@XSign [14:55:14] : ~
>> grep -i rapoo /var/log/Xorg.0.log
[ 29.102] (II) config/udev: Adding input device RAPOO RAPOO 2.4G Remote Mouse (/dev/input/event7)
[ 29.102] (**) RAPOO RAPOO 2.4G Remote Mouse: Applying InputClass "evdev keyboard catchall"
[ 29.102] (II) Using input driver 'evdev' for 'RAPOO RAPOO 2.4G Remote Mouse'
[ 29.102] (**) RAPOO RAPOO 2.4G Remote Mouse: always reports core events
[ 29.102] (**) evdev: RAPOO RAPOO 2.4G Remote Mouse: Device: "/dev/input/event7"
[ 29.102] (--) evdev: RAPOO RAPOO 2.4G Remote Mouse: Vendor 0x24ae Product 0x2000
[ 29.102] (--) evdev: RAPOO RAPOO 2.4G Remote Mouse: Found keys
[ 29.102] (II) evdev: RAPOO RAPOO 2.4G Remote Mouse: Configuring as keyboard
[ 29.102] (II) XINPUT: Adding extended input device "RAPOO RAPOO 2.4G Remote Mouse" (type: KEYBOARD, id 12)
[ 29.103] (II) config/udev: Adding input device RAPOO RAPOO 2.4G Remote Mouse (/dev/input/event8)
[ 29.103] (**) RAPOO RAPOO 2.4G Remote Mouse: Applying InputClass "evdev pointer catchall"
[ 29.103] (**) RAPOO RAPOO 2.4G Remote Mouse: Applying InputClass "evdev keyboard catchall"
[ 29.103] (II) Using input driver 'evdev' for 'RAPOO RAPOO 2.4G Remote Mouse'
[ 29.103] (**) RAPOO RAPOO 2.4G Remote Mouse: always reports core events
[ 29.103] (**) evdev: RAPOO RAPOO 2.4G Remote Mouse: Device: "/dev/input/event8"
[ 29.103] (--) evdev: RAPOO RAPOO 2.4G Remote Mouse: Vendor 0x24ae Product 0x2000
[ 29.103] (--) evdev: RAPOO RAPOO 2.4G Remote Mouse: Found 9 mouse buttons
[ 29.103] (--) evdev: RAPOO RAPOO 2.4G Remote Mouse: Found scroll wheel(s)
[ 29.103] (--) evdev: RAPOO RAPOO 2.4G Remote Mouse: Found relative axes
[ 29.103] (--) evdev: RAPOO RAPOO 2.4G Remote Mouse: Found x and y relative axes
[ 29.103] (--) evdev: RAPOO RAPOO 2.4G Remote Mouse: Found absolute axes
[ 29.103] (II) evdev: RAPOO RAPOO 2.4G Remote Mouse: Forcing absolute x/y axes to exist.
[ 29.103] (--) evdev: RAPOO RAPOO 2.4G Remote Mouse: Found keys
[ 29.103] (II) evdev: RAPOO RAPOO 2.4G Remote Mouse: Configuring as mouse
[ 29.103] (II) evdev: RAPOO RAPOO 2.4G Remote Mouse: Configuring as keyboard
[ 29.103] (II) evdev: RAPOO RAPOO 2.4G Remote Mouse: Adding scrollwheel support
[ 29.103] (**) evdev: RAPOO RAPOO 2.4G Remote Mouse: YAxisMapping: buttons 4 and 5
[ 29.103] (**) evdev: RAPOO RAPOO 2.4G Remote Mouse: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
[ 29.103] (II) XINPUT: Adding extended input device "RAPOO RAPOO 2.4G Remote Mouse" (type: KEYBOARD, id 13)
[ 29.104] (II) evdev: RAPOO RAPOO 2.4G Remote Mouse: initialized for relative axes.
[ 29.104] (WW) evdev: RAPOO RAPOO 2.4G Remote Mouse: ignoring absolute axes.
[ 29.104] (**) RAPOO RAPOO 2.4G Remote Mouse: (accel) keeping acceleration scheme 1
[ 29.104] (**) RAPOO RAPOO 2.4G Remote Mouse: (accel) acceleration profile 0
[ 29.104] (**) RAPOO RAPOO 2.4G Remote Mouse: (accel) acceleration factor: 2.000
[ 29.104] (**) RAPOO RAPOO 2.4G Remote Mouse: (accel) acceleration threshold: 4
[ 29.104] (II) config/udev: Adding input device RAPOO RAPOO 2.4G Remote Mouse (/dev/input/mouse0)
hacksign@XSign [14:59:47] : ~
>> yaourt -Q|grep -i 'input-'
local/xf86-input-evdev-trackpoint 2.9.1-1
extra/xf86-input-keyboard 1.8.0-3 (xorg-drivers xorg)
extra/xf86-input-mouse 1.9.1-1 (xorg-drivers xorg)
extra/xf86-input-synaptics 1.8.1-1 (xorg-drivers xorg)
Last edited by Hacksign (2015-01-14 02:22:51)

Thanks for reply !
change Driver 'mouse' to Driver 'evdev',solved cursor goes beyond controll problem.
but I still can not use scroll button and 'go forward'&'go backward' button.
(BTW:evdev_drv.so is from local/xf86-input-evdev-trackpoint, and local/xf86-input-evdev-trackpoint package is from AUR)
I think, maybe something wrong with my button number mapping, but I still can not get scroll button number with 'xev' command....
below is my configuration:
hacksign@XSign [17:15:19] : /var/log
>> cat /etc/X11/xorg.conf.d/50-mouse-acceleration.conf
Section "InputClass"
Identifier "Mouse2"
MatchProduct "RAPOO RAPOO 2.4G Remote Mouse"
MatchIsPointer "yes"
MatchDevicePath "/dev/input/event*"
Driver "evdev"
Option "Protocol" "auto"
Option "Emulate3Buttons" "no"
Option "ZAxisMapping" "4 5"
Option "Buttons" "9"
Option "ButtonMapping" "1 2 3 6 7 8 9 4 5"
EndSection
and here is Xorg.0.log
[ 11357.287] (**) RAPOO RAPOO 2.4G Remote Mouse: Applying InputClass "evdev keyboard catchall"
[ 11357.287] (II) Using input driver 'evdev' for 'RAPOO RAPOO 2.4G Remote Mouse'
[ 11357.287] (**) RAPOO RAPOO 2.4G Remote Mouse: always reports core events
[ 11357.287] (**) evdev: RAPOO RAPOO 2.4G Remote Mouse: Device: "/dev/input/event7"
[ 11357.287] (--) evdev: RAPOO RAPOO 2.4G Remote Mouse: Vendor 0x24ae Product 0x2000
[ 11357.287] (--) evdev: RAPOO RAPOO 2.4G Remote Mouse: Found keys
[ 11357.287] (II) evdev: RAPOO RAPOO 2.4G Remote Mouse: Configuring as keyboard
[ 11357.287] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.2/2-1.2:1.0/0003:24AE:2000.0003/input/input8/event7"
[ 11357.288] (II) XINPUT: Adding extended input device "RAPOO RAPOO 2.4G Remote Mouse" (type: KEYBOARD, id 12)
[ 11357.288] (**) Option "xkb_rules" "evdev"
[ 11357.288] (**) Option "xkb_model" "pc104"
[ 11357.288] (**) Option "xkb_layout" "us"
[ 11357.288] (II) config/udev: Adding input device RAPOO RAPOO 2.4G Remote Mouse (/dev/input/event8)
[ 11357.288] (**) RAPOO RAPOO 2.4G Remote Mouse: Applying InputClass "evdev pointer catchall"
[ 11357.288] (**) RAPOO RAPOO 2.4G Remote Mouse: Applying InputClass "evdev keyboard catchall"
[ 11357.288] (**) RAPOO RAPOO 2.4G Remote Mouse: Applying InputClass "Mouse2"
[ 11357.288] (II) Using input driver 'evdev' for 'RAPOO RAPOO 2.4G Remote Mouse'
[ 11357.288] (**) RAPOO RAPOO 2.4G Remote Mouse: always reports core events
[ 11357.288] (**) evdev: RAPOO RAPOO 2.4G Remote Mouse: Device: "/dev/input/event8"
[ 11357.288] (**) evdev: RAPOO RAPOO 2.4G Remote Mouse: ButtonMapping '1 2 3 6 7 8 9 4 5'
[ 11357.288] (--) evdev: RAPOO RAPOO 2.4G Remote Mouse: Vendor 0x24ae Product 0x2000
[ 11357.288] (--) evdev: RAPOO RAPOO 2.4G Remote Mouse: Found 9 mouse buttons
[ 11357.288] (--) evdev: RAPOO RAPOO 2.4G Remote Mouse: Found scroll wheel(s)
[ 11357.288] (--) evdev: RAPOO RAPOO 2.4G Remote Mouse: Found relative axes
[ 11357.288] (--) evdev: RAPOO RAPOO 2.4G Remote Mouse: Found x and y relative axes
[ 11357.288] (--) evdev: RAPOO RAPOO 2.4G Remote Mouse: Found absolute axes
[ 11357.288] (II) evdev: RAPOO RAPOO 2.4G Remote Mouse: Forcing absolute x/y axes to exist.
[ 11357.288] (--) evdev: RAPOO RAPOO 2.4G Remote Mouse: Found keys
[ 11357.288] (II) evdev: RAPOO RAPOO 2.4G Remote Mouse: Configuring as mouse
[ 11357.288] (II) evdev: RAPOO RAPOO 2.4G Remote Mouse: Configuring as keyboard
[ 11357.288] (II) evdev: RAPOO RAPOO 2.4G Remote Mouse: Adding scrollwheel support
[ 11357.288] (**) Option "Emulate3Buttons" "no"
[ 11357.288] (**) evdev: RAPOO RAPOO 2.4G Remote Mouse: YAxisMapping: buttons 4 and 5
[ 11357.288] (**) evdev: RAPOO RAPOO 2.4G Remote Mouse: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
[ 11357.288] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.2/2-1.2:1.1/0003:24AE:2000.0004/input/input9/event8"
[ 11357.288] (II) XINPUT: Adding extended input device "RAPOO RAPOO 2.4G Remote Mouse" (type: KEYBOARD, id 13)
[ 11357.288] (**) Option "xkb_rules" "evdev"
[ 11357.288] (**) Option "xkb_model" "pc104"
[ 11357.288] (**) Option "xkb_layout" "us"
[ 11357.288] (II) evdev: RAPOO RAPOO 2.4G Remote Mouse: initialized for relative axes.
[ 11357.288] (WW) evdev: RAPOO RAPOO 2.4G Remote Mouse: ignoring absolute axes.
[ 11357.289] (**) RAPOO RAPOO 2.4G Remote Mouse: (accel) keeping acceleration scheme 1
[ 11357.289] (**) RAPOO RAPOO 2.4G Remote Mouse: (accel) acceleration profile 0
[ 11357.289] (**) RAPOO RAPOO 2.4G Remote Mouse: (accel) acceleration factor: 2.000
[ 11357.289] (**) RAPOO RAPOO 2.4G Remote Mouse: (accel) acceleration threshold: 4
[ 11357.289] (II) config/udev: Adding input device RAPOO RAPOO 2.4G Remote Mouse (/dev/input/mouse0)
[ 11357.289] (II) No input driver specified, ignoring this device.
[ 11357.289] (II) This device may have been added with another device file.
olive wrote:In the config file you mentioned, all is commented; do you mean that you have problems when you have uncommented it? You should not use the mouse driver (old deprecated driver) but evdev. Try to remove xf86-input-mouse and xf86-input-keyboard (same as before, this is deprecated and handled by evdev) and remove also a "joystick" driver if you have it (I have had problem with it conflicting with the evdev driver).
Last edited by Hacksign (2015-01-13 09:27:06)

[SOLVED] Network speed very slow, no apparent reason

Hello, recently I switched from Windows 7 RC1 to Arch on my home machine (I have used Gentoo, Ubuntu, and Fedora 10 on the same machine in the past), and for some reason network speed is very slow.
I have Verizon's 20mbit/5mbit package, and I have always gotten that speed.
Using speedtest.net and 100mb.test from cachefly on multiple computers I have come to the conclusion that it is infact my Arch install that is causing the problem:
- All other machines on my network are getting 20/5 (both wired and wireless)
- I ran a speedtest from 2 other machines using the ethernet cable that this PC is on. Again, full 20/5.
- scp transfer of 100mb.test from this PC -> other Arch box: ~2.8MB/s.
- scp transfer of 100mb.test from other Arch box -> this PC: ~2.8MB/s.
- scp transfer of 100mb.test from this PC -> UK VPS (100mbit line): ~539KB/s
- scp transfer of 100mb.test from UK VPS -> this PC: ~76KB/s
- scp transfer of 100mb.test from this PC -> Chicago Server (dual gbit lines): ~563KB/s
- scp transfer of 100mb.test from Chicago Server -> this PC: ~91KB/s
speedtest.net result:
Upload speed seems to be unaffected.
I have tried disabling TCP window scaling, and appending my hostname to /etc/hosts.
What is weird though is that the other Arch box has an identical network config, I don't see any reason why it shouldn't work.
My NIC is an integrated Realtek something, I can get the exact model if needed.
Last edited by whipsch (2009-06-05 18:29:21)

Hi, whipsch
Can you try ethtool to see if your ethernet card is actually negociating and using a 100Mb full duplex link on your LAN ? If not you can try to force the link parameter with ethtool. Also maybe the driver of your NIc has options related to link negociation.
Hope this helps,
JF

[SOLVED] Network interface name keeps changing

My network interface name keeps changing between wlp2s0 and wlan0. This is a real pain, since I never know what name will be generated at boot. Most of the time it's called wlp2s0, so this is what netctl is set up to handle by itself. At boots were wlan0 is generated I have to connect manually.
I've tried making the name static by adding a rule to the /etc/udev/rules.d/10-network.rules. The rule i added was:
SUBSYSTEM=="net", ACTION=="add", ATTR{address}=="48:5d:60:7e:64:e9", NAME="wlp2s0"
Wlp2s0 is generated at boot alright, but I still have to connect manually with this solution. As if the "new" wlp2s0 is not recognized as the old one (same MAC). What gives?
This is on an Asus Eee 1001PXD, with the Qualcomm Atheros AR9285.
Last edited by madr (2013-05-18 20:09:34)

I've now been able to replicate the issue, and run the command:
journalctl -b
I did find the output:
mai 18 02:30:02 <hostname> systemd-udevd[126]: error changing net interface name wlan0 to wlp2s0: Device or resource busy
I haven't been able to process the whole output yet (I'll continue tomorrow if necessary), but I've found some things that I hope will clearify things. I get similar outputs to the following a lot throughout:
mai 18 02:30:03 <hostname> dhcpcd[237]: wlan0: carrier lost
mai 18 02:30:03 <hostname> dhcpcd[237]: wlan0: waiting for carrier
mai 18 02:30:04 <hostname> systemd[1]: [email protected]: control process exited, code=exited status=1
mai 18 02:30:04 <hostname> systemd[1]: Failed to start Automatic wireless network connection using netctl profiles.
mai 18 02:30:04 <hostname> systemd[1]: Unit [email protected] entered failed state.
mai 18 02:30:04 <hostname> systemd[1]: Starting Network.
mai 18 02:30:04 <hostname> systemd[1]: Reached target Network.
EDIT:
I see now that this is later in time, so that's not so strange after all. I'll look some more.
EDIT2:
The error code that a name change i impossible is the first time the term 'wlan0' occurs in the log. However there's a line much earlier that talks about wlp2s0:
mai 18 02:29:59 <hostname> systemd[1]: Expecting device sys-subsystem-net-devices-wlp2s0.device...
But as I said, if this information doesn't help, I'll have a closer look at the output tomorrow. Getting late here in Norway now.
Last edited by madr (2013-05-18 01:20:50)

[SOLVED] Network manager only works as root

Hello everyone,
I am brand new to arch and have been quite impressed over the past few days over all it has to offer. Everything has been running quite smoothly and I am now in the process of setting up wireless. I installed network manager and was able to connect to a wireless network as root. For my regular user, however, I am running into some issues. First one was that the nm-applet could not be opened in fluxbox. I received the following error:
** (nm-applet:1576): WARNING **: <WARN> request_name(): Could not acquire the NetworkManagerUserSettings service.
Error: (9) Connection ":1.27" is not allowed to own the service "org.freedesktop.NetworkManagerUserSettings" due to security policies in the configuration file
I "fixed" this by adding the following to /etc/dbus-1/system.d/nm-applet.conf. Original credit goes to the user in this thread (I only slightly modified his code): https://bbs.archlinux.org/viewtopic.php?id=63576

<policy user="myusername">
<allow own="org.freedesktop.NetworkManagerUserSettings"/>
<allow send_destination="org.freedesktop.NetworkManagerUserSettings"/>
<allow send_interface="org.freedesktop.NetworkManagerUserSettings"/>
<deny send_interface="org.freedesktop.NetworkManagerSetting.Secrets"/>
</policy>

Now the applet shows up for my regular user, the problem being that it doesn't connect to the wireless networks (only wired). Whenever I try to connect to wireless, nothing happens (the symbol doesn't change in any way, i.e. the green spheres should start circling); I am still able to succesfully connect to wireless using root. Does anyone know what the source of this issue may be? Thank you very much in advance.
Last edited by Ipozya (2011-01-20 04:49:55)

Solved: Had to install consolekit and add "ck-launch-session" to my .xinitrc file when starting fluxbox.
Edit: Please note that this also allowed me to remove the previous change to nm-applet.conf (no longer necessary)!
Last edited by Ipozya (2011-01-20 04:54:20)

[SOLVED] network-online.target is reached too early

Hi,
I want to start a systemd service once my wireless card is correctly set up (especially the wifi channel).
I think that the network-online is what I need.
So, I added the following lines at the beginning of my service file :
[Unit]
Description=...
Wants=network-online.target
After=network-online.target
However, it seems that the network-online.target is reached really early in the boot process, far before the discovery of the wireless card.
I don't know if it's important, but my wireless network is configured with netctl-auto.
I'm not very familiar with systemd, so I don't even understand how network-online.target is supposed to be notified that the network is online.
So, any help would be apreciated.
Thanks.
PS : I hope my approximative English is understandable enough.
Last edited by PHF (2013-10-28 02:51:43)

Lone_Wolf wrote:PHF, if i understand correctly you need to be sure the wireless connection is up and configured before the hostapd daemon runs ?
Yes, exactly.
Lone_Wolf wrote:a solution to achieve this might be to write a special command to check if the connection is up and add a service for it like the NetworkManager-wait-online.service .
This special command could be simple, like grepping the output op of ip addr show <interfacename> in a loop until it has a valid ip address.
Well, that's what I started to guess, without certitude : I need to manually order a waiting service before network-online.target.
I think my problem is solved now .
Meanwhile, I have found the ExecUpPost option for my netctl profiles.
It gives me the ability to execute a command once the connection is active.
So, I should be able to use it for unlocking my waiting service.
Thanks a lot for your help.

[Solved] Network : static IP config

Similar Messages

Maybe you are looking for