[solved] new systemd-sysctl applies 99-sysctl.conf before networkd?

Recently pacman updated systemd.
I use systemd-networkd for Ethernet (wired) control (Wireless LAN is hard blocked)
I have this in /etc/sysctl.d/99-sysctl.conf
net.ipv4.ip_forward = 1
This is to allow sharing of internet where my system is gateway.
This worked fine before the recent update.
But after upgrade internet sharing stopped.
I noticed the following sysctl variables (sysctl -a)
net.ipv4.conf.all.forwarding = 1
net.ipv4.conf.default.forwarding = 1
net.ipv4.conf.ens5.forwarding = 0
net.ipv4.conf.ppp1.forwarding = 1
net.ipv4.conf.wls1.forwarding = 1
net.ipv4.ip_forward = 1
Three strange things:
1st is wls1 is disabled yet it is shown (but lets ignore it)
ens5 fowarding is 0?? while rest all are 1.
ppp1 is actually PPPoE based connection activated by [email protected] and runs over ens5
Once I do:
sysctl net.ipv4.conf.ens5.forwarding=1
Internet sharing starts working as expected.
So what is the issue? What changed?
Is it that systemd-sysctl gets applied before systemd-network brings ens5 up?
But then ppp1 is based on ens5 - how is that 1?
Thanks in advance.
Last edited by amish (2015-04-21 06:49:04)

Looks like someone has already file bugreport:
https://bugs.freedesktop.org/show_bug.cgi?id=89509
Possible solution would be to add
IPForward=yes
to systemd-networkd .network file

Similar Messages

[SOLVED] Some systemd processes (e.g. systemd-journald) can't start.

After a fresh install on a new laptop (dual boot with Windows 8.1 vie rEFInd) I notice some error messages whilst booting. systemd-journald fails to start, and I also see some errors relating to the creation of the volatile filesystem. It's hard for me to give a lot detail about this as without journaling as I'm not sure how to get the error messages.
I did see this from dmesg:
[ 128.638674] systemd[1]: Starting Stop Read-Ahead Data Collection...
[ 128.662550] systemd[1]: Started Stop Read-Ahead Data Collection.
[ 194.545294] systemd[1]: Starting Journal Socket (/dev/log).
[ 194.545391] systemd[1]: Listening on Journal Socket (/dev/log).
[ 194.545471] systemd[1]: Starting Journal Socket.
[ 194.545540] systemd[1]: Listening on Journal Socket.
[ 194.545613] systemd[1]: Starting Journal Service...
[ 194.546604] systemd[1]: Started Journal Service.
[ 194.549797] systemd-journald[711]: Failed to get machine id: No such file or directory
[ 194.553931] systemd[1]: systemd-journald.service has no holdoff time, scheduling restart.
[ 194.554205] systemd[1]: Stopping Journal Service...
[ 24.362121] systemd-tmpfiles[330]: [/usr/lib/tmpfiles.d/systemd.conf:26] Failed to replace specifiers: /run/log/journal/%m
[ 24.364106] systemd-tmpfiles[330]: [/usr/lib/tmpfiles.d/systemd.conf:29] Failed to replace specifiers: /var/log/journal/%m
[ 24.404888] systemd[1]: systemd-tmpfiles-setup.service: main process exited, code=exited, status=1/FAILURE
[ 24.409499] systemd[1]: Failed to start Create Volatile Files and Directories.
[ 24.412303] systemd[1]: Unit systemd-tmpfiles-setup.service entered failed state.
And if I check the status of journald through systemctl I get:
systemd-journald.service - Journal Service
Loaded: loaded (/usr/lib/systemd/system/systemd-journald.service; static)
Active: failed (Result: start-limit) since Wed 2014-08-27 10:37:50 UTC; 1h 2min ago
Docs: man:systemd-journald.service(8)
man:journald.conf(5)
Process: 720 ExecStart=/usr/lib/systemd/systemd-journald (code=exited, status=1/FAILURE)
Main PID: 720 (code=exited, status=1/FAILURE)
Status: "Shutting down..."
I've tried reinstalling systemd, and adding systemd to HOOKS in mkinitcpio.conf, neither of these things seem to help. I also can't start the services manually.
If anybody can help it would be greatly appreciated, thanks!
Last edited by Tim Butters (2014-08-28 15:49:50)

Normally, as Loqs said, 'systemd-firstboot --setup-machine-id' should have been run when you first installed the systemd package.
You can verify if the '/etc/machine-id' file exists:
$ ls -l /etc/machine-id
-rw-r--r-- 1 root root 33 25 mars 2009 /etc/machine-id
If you don't find one, maybe use 'systemd-machine-id-setup' instead to create one.
But have you seen error messages during the Arch installation? Because that should not be necessary.
Edit: 'systemd-firstboot' is new in systemd 216, so should not be found in the live installation disk 2014.08.
Last edited by berbae (2014-08-28 15:44:52)

[SOLVED] Verifying systemd conversion

Good Afternoon Fellow Archers,
I have an x86_64 installation of Arch when Arch was still using sysV init. When systemd was recommended, I switched over as recommended. So my system should be pure systemd, at least so I think. And the changeover was fairly easy. I just had to change how I start/stop/enable/restart daemons using systemctl. Minor.....
I have no "/etc/init.d" dirtree, and "/etc/rc.d" only has six entries in it, all scripts, and no dirtrees of any kind. It has a date/time stamp that keeps getting refreshed periodically. LIke today, after a "pacman -Syu" in which a new systemd was installed (204). In "/etc/rc.d" there are six scripts, "bluetooth, ip6tables, iptables, ntpd, ntpdate, and ppp".
I have looked at the systemd wiki, checked out the forums, and followed links to other related articles on the site...but I do not find the specific information (guide) I am looking for.
I am looking for a way to determine absolutely, if I have a pure systemd installation now, or if there are any remnants of sysV that I still need to convert/remove.
Question: How can I determine if I have a pure systemd implementation?
And in asking, I also highly recommend adding the answer to the wiki page of "systemd" to allow others to determine that they are running a pure systemd implementation.
I will certainly be appreciative for any information/quide.
Sincerly and respectfully,
Dave
Last edited by dcbdbis (2013-05-22 23:40:24)

Thank you for the link, and for the reply,
I didn't use the code tags as it was not code that I wanted someone to copy and paste into their own system.
I'll use them next time... my apologies.
And also my thanks for the responses. I'm good to go now.
Dave....
PS: I followed the other forum link, and like one of the poster's, I deleted my /etc/rc.d dir. Rebooted. Everything came back up just perfect. So systemd it is! I already had the sysv compat utilities installed.
Last edited by dcbdbis (2013-05-22 23:47:46)

I bought new Macbook Pro 13" around two months before .My Apple ID is working on all other things except app store . It is buffering for a lot of time and lastly coming on screen " can not connect to app store " Please help me

I bought new Macbook Pro 13" around two months before .My Apple ID is working on all other things except app store . It is buffering for a lot of time and lastly coming on screen " can not connect to app store " Please help me

Have you tried repairing disk permissions : iTunes download error -45054

Old computer died and I am trying to install Illustrator CS5 on new computer. Last version I had before CS5 was/is Illustrator 10, which has been installed in new computer. CS5 install says I need CS2,3, or 4 before installing 5, but old computer went dir

Old computer died and I am trying to install Illustrator CS5 on new computer.
Last version I had before CS5 was/is Illustrator 10,which has been installed on new computer.
CS5 install says I need CS2,3 or 4 before installing 5, but old computer went directly from 10 to CS5.
How can I repeat this 10 to CS5 install?

It does not seem likely that CS6 was upgraded from version 10. You might want to check your purchase history in your Adobe account to see if there is some missing link in the chain of purchases you made.
You can always try contacting Adobe support thru chat to see if they can find information or otherwise assist you in this matter.
Serial number and activation chat support (non-CC)
http://helpx.adobe.com/x-productkb/global/service1.html ( http://adobe.ly/1aYjbSC )

Windows 8.1 PC, using reader, when searching a folder containing approx 100 doc's. If i search for a word, no results are returned. only the doc names can be found but nothing from within the doc. This is a new problem and was not the case before.

Windows 8.1 PC, using reader, when searching a folder containing approx 100 doc's. If i search for a word, no results are returned. only the doc names can be found but nothing from within the doc.
This is a new problem and was not the case before.

Works perfectly fine for me with the latest Reader version (11.0.09).
You write that it worked "before"; before what? An update? Update from what version to what version?

HT204053 How do you get your last batch of down loads to the new computer if the old one crashed before i was able to get it on my ipod

How do you get your last batch of down loads to the new computer if the old one crashed before i was able to get it on my ipod

See Here > Download Past Purchases
http://support.apple.com/kb/HT2519

[SOLVED] /etc/systemd/system.conf: DumpCore

What's that option for?
I cannot find it by myself, sorry...
Last edited by kokoko3k (2015-01-22 15:27:50)

karol wrote:
/etc/systemd/system.conf has a man page:
man systemd-system.conf wrote: LogLevel=, LogTarget=, LogColor=, LogLocation=, DumpCore=yes, CrashShell=no, ShowStatus=yes,
CrashChVT=1, DefaultStandardOutput=journal, DefaultStandardError=inherit
Configures various parameters of basic manager operation. These options may be overridden by
the respective command line arguments. See systemd(1) for details about these command line
arguments.
but it doesn't say what does this option do.
man systemd wrote: --dump-core
Dump core on crash. This switch has no effect when run as user instance.

[SOLVED] Gnome doesn't apply the theme to new opened windows

Hi,
I'm using Gnome as desktop environment, but encountered a really annoying issue .
I want to change the theme and therefore do the following "Right click on desktop -> "Change desktop background" -> Theme -> "Darklooks". All opened windows (as well as the panels) get now dark, just as expected. But as soon as I open up a new windows (or add something to a panel) it doesn't get affected by the theme, but it is display with the standard bright grey. After changing the theme again (I have to choose another first, and then go back to "Darklooks") all "new" windows get dark also.
As I'm not happy with this situation I ask you for help? What is wrong with my Gnome?
Last edited by johnpatcher (2009-09-05 19:37:14)

I furthermore found out that this bug is already reported: http://bugzilla.gnome.org/show_bug.cgi?id=540796

[SOLVED] cpupower/systemd, cannot set 'performance' governor at boot

Hi all, i upgraded to systemd and everything is working fine and faster: the only one thing i'm missing is cpufrequtils since this was the only way to set the "performance" governor at boot and have it stay this way.
Since i upgraded to cpupower and enabled the cpupower.service unit, the governor is automatically switched to ondemand even if i specified performance in the /etc/conf.d/cpupower config file: i don't get what's happening because if i restart the cpupower.service unit manually everything is fine and it will not switch to ondemand on its own o_O
Processor information
vendor_id : GenuineIntel
cpu family : 6
model : 26
model name : Intel(R) Core(TM) i7 CPU 920 @ 2.67GHz
stepping : 5
microcode : 0x11
cpu MHz : 1600.000
cache size : 8192 KB
physical id : 0
siblings : 8
core id : 3
cpu cores : 4
apicid : 7
initial apicid : 7
fpu : yes
fpu_exception : yes
cpuid level : 11
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc aperfmperf pni dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm sse4_1 sse4_2 popcnt lahf_lm ida dtherm tpr_shadow vnmi flexpriority ept vpid
bogomips : 5322.83
clflush size : 64
cache_alignment : 64
address sizes : 36 bits physical, 48 bits virtual
power management:
/etc/conf.d/cpupower
# Define CPUs governor
# valid governors: ondemand, performance, powersave, conservative, userspace.
governor='performance'
# Limit frequency range
# Valid suffixes: Hz, kHz (default), MHz, GHz, THz
#min_freq="2668MHz"
#max_freq="2668MHz"
# Specific frequency to be set.
# Requires userspace governor to be available and loaded.
#freq=
# Utilizes cores in one processor package/socket first before processes are
# scheduled to other processor packages/sockets.
# See man (1) CPUPOWER-SET for additional details.
#mc_scheduler=0
# Utilizes thread siblings of one processor core first before processes are
# scheduled to other cores. See man (1) CPUPOWER-SET for additional details.
#smp_scheduler=0
# Sets a register on supported Intel processore which allows software to convey
# its policy for the relative importance of performance versus energy savings to
# the processor. See man (1) CPUPOWER-SET for additional details.
#perf_bias=
# vim:set ts=2 sw=2 ft=sh et:
sytemctl status cpupower.service
cpupower.service - Apply cpupower configuration
Loaded: loaded (/usr/lib/systemd/system/cpupower.service; enabled)
Active: active (exited) since Sat, 01 Sep 2012 10:50:05 +0200; 1min 27s ago
Process: 2148 ExecStart=/usr/lib/systemd/scripts/cpupower (code=exited, status=0/SUCCESS)
CGroup: name=systemd:/system/cpupower.service
journalctl |grep -i cpupower
(empty)
I even tried to mimic an rc.local with a custom service i use to set RTC max frequency (for the Android emulator) but it doesn't set the governor to performance, even if i know this script works since i can query max_user_freq and read 2048 as i need it to be, here is the script launched by the custom service.
#!/bin/bash
echo 2048 > /sys/class/rtc/rtc0/max_user_freq
echo 2048 > /proc/sys/dev/hpet/max-user-freq
cpupower frequency-set -g performance
Does this happen for you too? I remember having this problem one year ago, and switched to cpufrequtils since that was working: now that is being deprecated i would like to pinpoint the problem and solve it once and for all, can you help me?
I think i could auto-start some script via gnome-session-properties but i would love to have a systemd-only solution working :-/
Thank you,
Manuel
Last edited by bmanuel (2012-09-07 17:39:01)

z0id wrote:Are the proper kernel modules loaded?
Sure they are, "ondemand" and "performance" modules should be compiled-in into the default kernel, i can even run it *after* logging in gnome-shell and the settings will stay correctly.
$ cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_available_governors
ondemand performance

[SOLVED]New Build, no sound, Alsa unable to open slave

I've been happily using Arch on an old laptop I had lying around for 4/5 months, alongside ARM on my Raspberry Pi for a year or so. Being more than happy with it I decided to sell my 2011 i5 iMac, build a pc and hopefully learn something along the way. I mention this as it's my first build and the issue may be hardware realted, or more likely my assembly of the hardware, I've updated my sig to reflect the new parts.
The first decision I made two days ago upon putting the system together. I had two plugs, one for HD audio, another for Realtek audio, I went with the HD option. The other variable that is new to me is an audio option in the Gigabyte uefi/bios for audio which has options for enabled, disabled & auto - I've tried all three. I thought at first going with HD option may have meant sound only via hdmi, I'm using an old vga monitor, but after a little reading it seems the HD option should work with the standard audio out's on the motherboard & case too.
I've got a 3.5mm jack plugged into the line out on the back of the motherboard going to a phono connection on my stereo, I've also tried the headphone out on the front of the case, Zalman Z9.
I've installed alsa-plugins and alsa-utils. Upon running speaker-test, or speaker-test -c 2 I'm getting:
speaker-test -c 2
speaker-test 1.0.27.2
Playback device is default
Stream parameters are 48000Hz, S16_LE, 2 channels
Using 16 octaves of pink noise
ALSA lib pcm_dmix.c:1022:(snd_pcm_dmix_open) unable to open slave
Playback open error: -2,No such file or directory
Using aplay:
aplay piano2.wav
ALSA lib pcm_dmix.c:1022:(snd_pcm_dmix_open) unable to open slave
aplay: main:722: audio open error: No such file or directory
Some info:
lsmod | grep '^snd' | column -t
snd_hda_codec_hdmi 30162 1
snd_hda_codec_realtek 40772 1
snd_hda_intel 36904 0
snd_hda_codec 149633 3 snd_hda_codec_realtek,snd_hda_codec_hdmi,snd_hda_intel
snd_hwdep 6340 1 snd_hda_codec
snd_pcm 77709 3 snd_hda_codec_hdmi,snd_hda_codec,snd_hda_intel
snd_page_alloc 7242 2 snd_pcm,snd_hda_intel
snd_timer 18726 1 snd_pcm
snd 59173 7 snd_hda_codec_realtek,snd_hwdep,snd_timer,snd_hda_codec_hdmi,snd_pcm,snd_hda_codec,snd_hda_intel
ls -l /dev/snd
total 0
drwxr-xr-x 2 root root 80 Dec 1 19:31 by-path
crw-rw----+ 1 root audio 116, 13 Dec 1 19:31 controlC0
crw-rw----+ 1 root audio 116, 8 Dec 1 19:31 controlC1
crw-rw----+ 1 root audio 116, 12 Dec 1 19:31 hwC0D0
crw-rw----+ 1 root audio 116, 7 Dec 1 19:31 hwC1D2
crw-rw----+ 1 root audio 116, 11 Dec 1 19:31 pcmC0D3p
crw-rw----+ 1 root audio 116, 10 Dec 1 19:31 pcmC0D7p
crw-rw----+ 1 root audio 116, 9 Dec 1 19:31 pcmC0D8p
crw-rw----+ 1 root audio 116, 6 Dec 1 19:31 pcmC1D0c
crw-rw----+ 1 root audio 116, 5 Dec 1 19:31 pcmC1D0p
crw-rw----+ 1 root audio 116, 4 Dec 1 19:31 pcmC1D1c
crw-rw----+ 1 root audio 116, 3 Dec 1 19:31 pcmC1D1p
crw-rw----+ 1 root audio 116, 2 Dec 1 19:31 pcmC1D2c
crw-rw---- 1 root audio 116, 1 Dec 1 19:31 seq
crw-rw----+ 1 root audio 116, 33 Dec 1 19:31 timer
aplay -l
**** List of PLAYBACK Hardware Devices ****
card 0: MID [HDA Intel MID], device 3: HDMI 0 [HDMI 0]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 0: MID [HDA Intel MID], device 7: HDMI 1 [HDMI 1]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 0: MID [HDA Intel MID], device 8: HDMI 2 [HDMI 2]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 1: PCH [HDA Intel PCH], device 0: ALC892 Analog [ALC892 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 1: PCH [HDA Intel PCH], device 1: ALC892 Digital [ALC892 Digital]
Subdevices: 1/1
Subdevice #0: subdevice #0
The above is all without any .asoundrc in my home directory or anything in /etc.modprobe.d/*.conf
From the wiki I've tried putting
options snd slots=snd_mia,snd_hda_intel
options snd_mia index=0
options snd_hda_intel index=1
in /etc/modprobe.d/alsa-base.conf, and tried reversing the 1 and 0, both 0's, both 1's to no avail.
I've tried a few variations in .asoundrc based on the wiki example with no luck.
I'm lost, this is the first time I've had sound issues with linux and I'm really not sure if it's rooted in the hardware, my first attempt at building a pc or a simple alsa config issue.
Googling for unable to open slave in alsa seems to bring up mainly conflicting programm issues whic I don't think is my issue as I have no sound at all.
*edit*
perhaps this should be in newbie corner? my linux sound knowledge is definitely newbie status.
Last edited by Proinsias (2013-12-03 23:22:48)

Solved, not sure where I was going wrong in my initial attempts but a simple .asoundrc has my speakers singing. Could have sworn this was tried to death in the first half hour or so, oh well.
On the plus side I spent my lunch hour today getting a rough idea of sound on linux and alsa preparing for a fight with my new build, ten minutes after booting up the new machine on my return home & all is well.
pcm.!default {
type hw
card 1
ctl.!default {
type hw
card 0

[SOLVED] new install Xorg not starting

I am running a vm install of arch and I cannot get startx to work. I went through the wiki section "Xorg as a systemd user service" and tried what it suggested and still it would not work. Below is my log file. Anyone have any suggestions? Thanks!
[herminio@archlinux-vm ~]$ cat .local/share/xorg/Xorg.0.log
[ 697.138]
X.Org X Server 1.16.2
Release Date: 2014-11-10
[ 697.141] X Protocol Version 11, Revision 0
[ 697.143] Build Operating System: Linux 3.17.2-1-ARCH x86_64
[ 697.144] Current Operating System: Linux archlinux-vm 3.17.2-1-ARCH #1 SMP PREEMPT Thu Oct 30 20:49:39 CET 2014 x86_64
[ 697.144] Kernel command line: BOOT_IMAGE=../vmlinuz-linux root=/dev/sda1 rw initrd=../initramfs-linux.img
[ 697.146] Build Date: 10 November 2014 07:52:13PM
[ 697.148]
[ 697.149] Current version of pixman: 0.32.6
[ 697.152] Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
[ 697.152] Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[ 697.156] (==) Log file: "/home/herminio/.local/share/xorg/Xorg.0.log", Time: Sat Nov 15 14:29:26 2014
[ 697.158] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[ 697.158] (==) No Layout section. Using the first Screen section.
[ 697.158] (==) No screen section available. Using defaults.
[ 697.158] (**) |-->Screen "Default Screen Section" (0)
[ 697.158] (**) | |-->Monitor "<default monitor>"
[ 697.158] (==) No monitor specified for screen "Default Screen Section".
Using a default monitor configuration.
[ 697.158] (==) Automatically adding devices
[ 697.158] (==) Automatically enabling devices
[ 697.158] (==) Automatically adding GPU devices
[ 697.158] (WW) The directory "/usr/share/fonts/TTF/" does not exist.
[ 697.158] Entry deleted from font path.
[ 697.158] (WW) The directory "/usr/share/fonts/OTF/" does not exist.
[ 697.158] Entry deleted from font path.
[ 697.158] (WW) The directory "/usr/share/fonts/Type1/" does not exist.
[ 697.158] Entry deleted from font path.
[ 697.158] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/100dpi/".
[ 697.158] Entry deleted from font path.
[ 697.158] (Run 'mkfontdir' on "/usr/share/fonts/100dpi/").
[ 697.158] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/75dpi/".
[ 697.158] Entry deleted from font path.
[ 697.158] (Run 'mkfontdir' on "/usr/share/fonts/75dpi/").
[ 697.158] (==) FontPath set to:
/usr/share/fonts/misc/
[ 697.158] (==) ModulePath set to "/usr/lib/xorg/modules"
[ 697.158] (II) The server relies on udev to provide the list of input devices.
If no devices become available, reconfigure udev or disable AutoAddDevices.
[ 697.158] (II) Loader magic: 0x818d80
[ 697.158] (II) Module ABI versions:
[ 697.158] X.Org ANSI C Emulation: 0.4
[ 697.158] X.Org Video Driver: 18.0
[ 697.158] X.Org XInput driver : 21.0
[ 697.158] X.Org Server Extension : 8.0
[ 697.161] (II) systemd-logind: took control of session /org/freedesktop/login1/session/c1
[ 697.161] (II) xfree86: Adding drm device (/dev/dri/card0)
[ 697.161] (II) systemd-logind: got fd for /dev/dri/card0 226:0 fd 8 paused 0
[ 697.200] (--) PCI:*(0:0:15:0) 15ad:0405:15ad:0405 rev 0, Mem @ 0xe8000000/134217728, 0xfe000000/8388608, I/O @ 0x00001070/16, BIOS @ 0x????????/32768
[ 697.200] (WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory)
[ 697.200] (II) LoadModule: "glx"
[ 697.200] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[ 697.245] (II) Module glx: vendor="NVIDIA Corporation"
[ 697.245] compiled for 4.0.2, module version = 1.0.0
[ 697.245] Module class: X.Org Server Extension
[ 697.245] (II) NVIDIA GLX Module 343.22 Thu Sep 11 15:55:13 PDT 2014
[ 697.246] (==) Matched vmware as autoconfigured driver 0
[ 697.246] (==) Matched vmware as autoconfigured driver 1
[ 697.246] (==) Matched modesetting as autoconfigured driver 2
[ 697.246] (==) Matched fbdev as autoconfigured driver 3
[ 697.246] (==) Matched vesa as autoconfigured driver 4
[ 697.246] (==) Assigned the driver to the xf86ConfigLayout
[ 697.246] (II) LoadModule: "vmware"
[ 697.246] (II) Loading /usr/lib/xorg/modules/drivers/vmware_drv.so
[ 697.280] (II) Module vmware: vendor="X.Org Foundation"
[ 697.281] compiled for 1.16.0, module version = 13.0.2
[ 697.281] Module class: X.Org Video Driver
[ 697.281] ABI class: X.Org Video Driver, version 18.0
[ 697.281] (II) LoadModule: "modesetting"
[ 697.281] (II) Loading /usr/lib/xorg/modules/drivers/modesetting_drv.so
[ 697.281] (II) Module modesetting: vendor="X.Org Foundation"
[ 697.281] compiled for 1.16.0, module version = 0.9.0
[ 697.281] Module class: X.Org Video Driver
[ 697.281] ABI class: X.Org Video Driver, version 18.0
[ 697.281] (II) LoadModule: "fbdev"
[ 697.282] (II) Loading /usr/lib/xorg/modules/drivers/fbdev_drv.so
[ 697.282] (II) Module fbdev: vendor="X.Org Foundation"
[ 697.282] compiled for 1.16.0, module version = 0.4.4
[ 697.282] Module class: X.Org Video Driver
[ 697.282] ABI class: X.Org Video Driver, version 18.0
[ 697.282] (II) LoadModule: "vesa"
[ 697.282] (II) Loading /usr/lib/xorg/modules/drivers/vesa_drv.so
[ 697.282] (II) Module vesa: vendor="X.Org Foundation"
[ 697.282] compiled for 1.16.0, module version = 2.3.2
[ 697.282] Module class: X.Org Video Driver
[ 697.282] ABI class: X.Org Video Driver, version 18.0
[ 697.282] (II) vmware: driver for VMware SVGA: vmware0405, vmware0710
[ 697.282] (II) modesetting: Driver for Modesetting Kernel Drivers: kms
[ 697.283] (II) FBDEV: driver for framebuffer: fbdev
[ 697.283] (II) VESA: driver for VESA chipsets: vesa
[ 697.283] (++) using VT number 1
[ 697.283] (--) controlling tty is VT number 1, auto-enabling KeepTty
[ 697.283] xf86EnableIOPorts: failed to set IOPL for I/O (Operation not permitted)
[ 697.283] (WW) Falling back to old probe method for modesetting
[ 697.283] (WW) Falling back to old probe method for fbdev
[ 697.283] (II) Loading sub module "fbdevhw"
[ 697.283] (II) LoadModule: "fbdevhw"
[ 697.283] (II) Loading /usr/lib/xorg/modules/libfbdevhw.so
[ 697.283] (II) Module fbdevhw: vendor="X.Org Foundation"
[ 697.283] compiled for 1.16.2, module version = 0.0.2
[ 697.283] ABI class: X.Org Video Driver, version 18.0
[ 697.283] (EE) open /dev/fb0: Permission denied
[ 697.283] (WW) Falling back to old probe method for vesa
[ 697.283] (WW) VGA arbiter: cannot open kernel arbiter, no multi-card support
[ 697.284] (II) vmware(0): Creating default Display subsection in Screen section
"Default Screen Section" for depth/fbbpp 24/32
[ 697.284] (--) vmware(0): DRM driver version is 2.6.1
[ 697.284] (EE) vmware(0): Failed to detect device screen object capability.
[ 697.284] (WW) vmware(0): Disabling 3D support.
[ 697.284] (WW) vmware(0): Disabling Render Acceleration.
[ 697.284] (WW) vmware(0): Disabling RandR12+ support.
[ 697.284] (--) vmware(0): VMware SVGA regs at (0x1070, 0x1071)
[ 697.284] (II) Loading sub module "vgahw"
[ 697.284] (II) LoadModule: "vgahw"
[ 697.284] (II) Loading /usr/lib/xorg/modules/libvgahw.so
[ 697.284] (II) Module vgahw: vendor="X.Org Foundation"
[ 697.284] compiled for 1.16.2, module version = 0.1.0
[ 697.284] ABI class: X.Org Video Driver, version 18.0
[ 697.299] (EE)
[ 697.299] (EE) Backtrace:
[ 697.300] (EE) 0: /usr/bin/Xorg.bin (xorg_backtrace+0x56) [0x593d36]
[ 697.300] (EE) 1: /usr/bin/Xorg.bin (0x400000+0x197e89) [0x597e89]
[ 697.300] (EE) 2: /usr/lib/libc.so.6 (0x7f1fe4f6b000+0x339f0) [0x7f1fe4f9e9f0]
[ 697.300] (EE) 3: /usr/lib/libpciaccess.so.0 (pci_io_write8+0x3) [0x7f1fe631a923]
[ 697.300] (EE) 4: /usr/lib/xorg/modules/libvgahw.so (vgaHWSaveColormap+0x5b) [0x7f1fdb2adfbb]
[ 697.300] (EE) 5: /usr/lib/xorg/modules/libvgahw.so (vgaHWSave+0x55) [0x7f1fdb2afd55]
[ 697.300] (EE) 6: /usr/lib/xorg/modules/drivers/vmware_drv.so (0x7f1fdeedc000+0x7dce) [0x7f1fdeee3dce]
[ 697.300] (EE) 7: /usr/bin/Xorg.bin (InitOutput+0xa9f) [0x47a28f]
[ 697.300] (EE) 8: /usr/bin/Xorg.bin (0x400000+0x3b65a) [0x43b65a]
[ 697.300] (EE) 9: /usr/lib/libc.so.6 (__libc_start_main+0xf0) [0x7f1fe4f8b040]
[ 697.300] (EE) 10: /usr/bin/Xorg.bin (0x400000+0x25d0e) [0x425d0e]
[ 697.300] (EE)
[ 697.300] (EE) Segmentation fault at address 0x8
[ 697.300] (EE)
Fatal server error:
[ 697.300] (EE) Caught signal 11 (Segmentation fault). Server aborting
[ 697.300] (EE)
[ 697.300] (EE)
Please consult the The X.Org Foundation support
at http://wiki.x.org
for help.
[ 697.300] (EE) Please also check the log file at "/home/herminio/.local/share/xorg/Xorg.0.log" for additional information.
[ 697.300] (EE)
[ 697.308] (EE) Server terminated with error (1). Closing log file.
[herminio@archlinux-vm ~]$
Last edited by rican-linux (2014-11-17 07:45:54)

Here are the packages I installed
[herminio@archlinux-vm ~]$ sudo pacman -Q | grep xf86-video
xf86-video-ark 0.7.5-5
xf86-video-ast 0.97.0-5
xf86-video-ati 1:7.5.0-1
xf86-video-cirrus 1.5.2-4
xf86-video-dummy 0.3.7-3
xf86-video-fbdev 0.4.4-3
xf86-video-glint 1.2.8-5
xf86-video-i128 1.3.6-5
xf86-video-intel 2.99.916-3
xf86-video-mach64 6.9.4-4
xf86-video-mga 1.6.3-3
xf86-video-modesetting 0.9.0-2
xf86-video-neomagic 1.2.8-3
xf86-video-nouveau 1.0.11-2
xf86-video-nv 2.1.20-5
xf86-video-openchrome 0.3.3-4
xf86-video-r128 6.9.2-3
xf86-video-savage 2.3.7-3
xf86-video-siliconmotion 1.7.7-5
xf86-video-sis 0.10.7-6
xf86-video-tdfx 1.4.5-5
xf86-video-trident 1.3.6-6
xf86-video-v4l 0.2.0-14
xf86-video-vesa 2.3.2-5
xf86-video-vmware 13.0.2-2
xf86-video-voodoo 1.2.5-5
I made some edits to the org.conf and now I am seeing this:
[herminio@archlinux-vm ~]$ startx
X.Org X Server 1.16.2
Release Date: 2014-11-10
X Protocol Version 11, Revision 0
Build Operating System: Linux 3.17.2-1-ARCH x86_64
Current Operating System: Linux archlinux-vm 3.17.2-1-ARCH #1 SMP PREEMPT Thu Oct 30 20:49:39 CET 2014 x86_64
Kernel command line: BOOT_IMAGE=../vmlinuz-linux root=/dev/sda1 rw initrd=../initramfs-linux.img
Build Date: 10 November 2014 07:52:13PM
Current version of pixman: 0.32.6
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Sat Nov 15 16:08:43 2014
(==) Using config file: "/etc/X11/xorg.conf"
(==) Using system config directory "/usr/share/X11/xorg.conf.d"
VMware: No 3D enabled (0, Success).
^Cxinit: connection to X server lost
waiting for X server to shut down XIO: fatal IO error 0 (Success) on X server ":0"
after 896 requests (896 known processed) with 0 events remaining.
xterm: fatal IO error 11 (Resource temporarily unavailable) or KillClient on X server ":0"
xterm: fatal IO error 104 (Connection reset by peer) or KillClient on X server ":0"
xterm: fatal IO error 104 (Connection reset by peer) or KillClient on X server ":0"
(EE) Server terminated successfully (0). Closing log file.
xinit: unexpected signal 2
Couldn't get a file descriptor referring to the console
[herminio@archlinux-vm ~]$ cat /var/log/Xorg.0.log
[ 2861.854]
X.Org X Server 1.16.2
Release Date: 2014-11-10
[ 2861.854] X Protocol Version 11, Revision 0
[ 2861.854] Build Operating System: Linux 3.17.2-1-ARCH x86_64
[ 2861.855] Current Operating System: Linux archlinux-vm 3.17.2-1-ARCH #1 SMP PREEMPT Thu Oct 30 20:49:39 CET 2014 x86_64
[ 2861.855] Kernel command line: BOOT_IMAGE=../vmlinuz-linux root=/dev/sda1 rw initrd=../initramfs-linux.img
[ 2861.855] Build Date: 10 November 2014 07:52:13PM
[ 2861.856]
[ 2861.856] Current version of pixman: 0.32.6
[ 2861.856] Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
[ 2861.856] Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[ 2861.858] (==) Log file: "/var/log/Xorg.0.log", Time: Sat Nov 15 16:08:43 2014
[ 2861.859] (==) Using config file: "/etc/X11/xorg.conf"
[ 2861.860] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[ 2861.860] (==) ServerLayout "X.org Configured"
[ 2861.860] (**) |-->Screen "Screen0" (0)
[ 2861.860] (**) | |-->Monitor "Monitor0"
[ 2861.860] (**) | |-->Device "Card0"
[ 2861.860] (**) |-->Input Device "Mouse0"
[ 2861.860] (**) |-->Input Device "Keyboard0"
[ 2861.860] (==) Automatically adding devices
[ 2861.860] (==) Automatically enabling devices
[ 2861.860] (==) Automatically adding GPU devices
[ 2861.860] (WW) The directory "/usr/share/fonts/Type1/" does not exist.
[ 2861.860] Entry deleted from font path.
[ 2861.860] (WW) The directory "/usr/share/fonts/Type1/" does not exist.
[ 2861.860] Entry deleted from font path.
[ 2861.860] (**) FontPath set to:
/usr/share/fonts/misc/,
/usr/share/fonts/TTF/,
/usr/share/fonts/OTF/,
/usr/share/fonts/100dpi/,
/usr/share/fonts/75dpi/,
/usr/share/fonts/misc/,
/usr/share/fonts/TTF/,
/usr/share/fonts/OTF/,
/usr/share/fonts/100dpi/,
/usr/share/fonts/75dpi/
[ 2861.860] (**) ModulePath set to "/usr/lib/xorg/modules"
[ 2861.860] (WW) Hotplugging is on, devices using drivers 'kbd', 'mouse' or 'vmmouse' will be disabled.
[ 2861.860] (WW) Disabling Mouse0
[ 2861.860] (WW) Disabling Keyboard0
[ 2861.860] (II) Loader magic: 0x818d80
[ 2861.860] (II) Module ABI versions:
[ 2861.860] X.Org ANSI C Emulation: 0.4
[ 2861.860] X.Org Video Driver: 18.0
[ 2861.860] X.Org XInput driver : 21.0
[ 2861.860] X.Org Server Extension : 8.0
[ 2861.863] (II) systemd-logind: took control of session /org/freedesktop/login1/session/c2
[ 2861.864] (II) xfree86: Adding drm device (/dev/dri/card0)
[ 2861.865] (EE) systemd-logind: failed to take device /dev/dri/card0: Operation not permitted
[ 2861.886] (--) PCI:*(0:0:15:0) 15ad:0405:15ad:0405 rev 0, Mem @ 0xe8000000/134217728, 0xfe000000/8388608, I/O @ 0x00001070/16, BIOS @ 0x????????/32768
[ 2861.886] (WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory)
[ 2861.886] (II) "glx" will be loaded. This was enabled by default and also specified in the config file.
[ 2861.886] (II) LoadModule: "glx"
[ 2861.887] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[ 2861.931] (II) Module glx: vendor="NVIDIA Corporation"
[ 2861.931] compiled for 4.0.2, module version = 1.0.0
[ 2861.931] Module class: X.Org Server Extension
[ 2861.931] (II) NVIDIA GLX Module 343.22 Thu Sep 11 15:55:13 PDT 2014
[ 2861.931] (II) LoadModule: "vmware"
[ 2861.932] (II) Loading /usr/lib/xorg/modules/drivers/vmware_drv.so
[ 2861.959] (II) Module vmware: vendor="X.Org Foundation"
[ 2861.959] compiled for 1.16.0, module version = 13.0.2
[ 2861.959] Module class: X.Org Video Driver
[ 2861.959] ABI class: X.Org Video Driver, version 18.0
[ 2861.959] (II) LoadModule: "vmware"
[ 2861.959] (II) Loading /usr/lib/xorg/modules/drivers/vmware_drv.so
[ 2861.959] (II) Module vmware: vendor="X.Org Foundation"
[ 2861.959] compiled for 1.16.0, module version = 13.0.2
[ 2861.959] Module class: X.Org Video Driver
[ 2861.959] ABI class: X.Org Video Driver, version 18.0
[ 2861.959] (II) UnloadModule: "vmware"
[ 2861.959] (II) Unloading vmware
[ 2861.959] (II) Failed to load module "vmware" (already loaded, 0)
[ 2861.959] (II) vmware: driver for VMware SVGA: vmware0405, vmware0710
[ 2861.959] (--) using VT number 2
[ 2861.963] (--) vmware(0): DRM driver version is 2.6.1
[ 2861.963] (==) vmware(0): Depth 24, (--) framebuffer bpp 32
[ 2861.963] (==) vmware(0): RGB weight 888
[ 2861.963] (==) vmware(0): Default visual is TrueColor
[ 2861.963] (--) vmware(0): Min width 1, Max Width 8192.
[ 2861.963] (--) vmware(0): Min height 1, Max Height 8192.
[ 2861.964] (II) vmware(0): Output Virtual1 using monitor section Monitor0
[ 2861.964] (II) vmware(0): Output Virtual2 has no monitor section
[ 2861.964] (II) vmware(0): Output Virtual3 has no monitor section
[ 2861.964] (II) vmware(0): Output Virtual4 has no monitor section
[ 2861.964] (II) vmware(0): Output Virtual5 has no monitor section
[ 2861.964] (II) vmware(0): Output Virtual6 has no monitor section
[ 2861.964] (II) vmware(0): Output Virtual7 has no monitor section
[ 2861.964] (II) vmware(0): Output Virtual8 has no monitor section
[ 2861.964] (II) vmware(0): Modeline "640x480"x59.9 25.18 640 656 752 800 480 489 492 525 -hsync -vsync (31.5 kHz e)
[ 2861.964] (II) vmware(0): Modeline "800x600"x60.3 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz e)
[ 2861.964] (II) vmware(0): Modeline "1024x768"x60.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz e)
[ 2861.964] (II) vmware(0): Modeline "1152x864"x75.0 108.00 1152 1216 1344 1600 864 865 868 900 +hsync +vsync (67.5 kHz e)
[ 2861.964] (II) vmware(0): Modeline "1280x768"x59.9 79.50 1280 1344 1472 1664 768 771 778 798 -hsync +vsync (47.8 kHz e)
[ 2861.964] (II) vmware(0): Modeline "1280x800"x59.8 83.50 1280 1352 1480 1680 800 803 809 831 +hsync -vsync (49.7 kHz e)
[ 2861.964] (II) vmware(0): Modeline "1280x960"x60.0 108.00 1280 1376 1488 1800 960 961 964 1000 +hsync +vsync (60.0 kHz e)
[ 2861.964] (II) vmware(0): Modeline "1280x1024"x60.0 108.00 1280 1328 1440 1688 1024 1025 1028 1066 +hsync +vsync (64.0 kHz e)
[ 2861.964] (II) vmware(0): Modeline "1360x768"x60.0 85.50 1360 1424 1536 1792 768 771 777 795 +hsync +vsync (47.7 kHz e)
[ 2861.964] (II) vmware(0): Modeline "1400x1050"x60.0 121.75 1400 1488 1632 1864 1050 1053 1057 1089 -hsync +vsync (65.3 kHz e)
[ 2861.964] (II) vmware(0): Modeline "1440x900"x59.9 106.50 1440 1520 1672 1904 900 903 909 934 -hsync +vsync (55.9 kHz e)
[ 2861.964] (II) vmware(0): Modeline "1600x1200"x60.0 162.00 1600 1664 1856 2160 1200 1201 1204 1250 +hsync +vsync (75.0 kHz e)
[ 2861.964] (II) vmware(0): Modeline "1680x1050"x60.0 146.25 1680 1784 1960 2240 1050 1053 1059 1089 -hsync +vsync (65.3 kHz e)
[ 2861.964] (II) vmware(0): Modeline "1792x1344"x60.0 204.75 1792 1920 2120 2448 1344 1345 1348 1394 -hsync +vsync (83.6 kHz e)
[ 2861.964] (II) vmware(0): Modeline "1856x1392"x60.0 218.25 1856 1952 2176 2528 1392 1393 1396 1439 -hsync +vsync (86.3 kHz e)
[ 2861.964] (II) vmware(0): Modeline "1920x1200"x59.9 193.25 1920 2056 2256 2592 1200 1203 1209 1245 -hsync +vsync (74.6 kHz e)
[ 2861.964] (II) vmware(0): Modeline "1920x1440"x60.0 234.00 1920 2048 2256 2600 1440 1441 1444 1500 -hsync +vsync (90.0 kHz e)
[ 2861.964] (II) vmware(0): Modeline "2560x1600"x60.0 348.50 2560 2752 3032 3504 1600 1603 1609 1658 -hsync +vsync (99.5 kHz e)
[ 2861.964] (II) vmware(0): Modeline "1280x768"x60.0 78.76 1280 1330 1380 1430 768 818 868 918 -hsync +vsync (55.1 kHz eP)
[ 2861.964] (II) vmware(0): Printing probed modes for output Virtual1
[ 2861.964] (II) vmware(0): Modeline "1280x768"x60.0 78.76 1280 1330 1380 1430 768 818 868 918 -hsync +vsync (55.1 kHz eP)
[ 2861.964] (II) vmware(0): Modeline "2560x1600"x60.0 348.50 2560 2752 3032 3504 1600 1603 1609 1658 -hsync +vsync (99.5 kHz e)
[ 2861.964] (II) vmware(0): Modeline "1920x1440"x60.0 234.00 1920 2048 2256 2600 1440 1441 1444 1500 -hsync +vsync (90.0 kHz e)
[ 2861.964] (II) vmware(0): Modeline "1856x1392"x60.0 218.25 1856 1952 2176 2528 1392 1393 1396 1439 -hsync +vsync (86.3 kHz e)
[ 2861.964] (II) vmware(0): Modeline "1792x1344"x60.0 204.75 1792 1920 2120 2448 1344 1345 1348 1394 -hsync +vsync (83.6 kHz e)
[ 2861.964] (II) vmware(0): Modeline "1920x1200"x59.9 193.25 1920 2056 2256 2592 1200 1203 1209 1245 -hsync +vsync (74.6 kHz e)
[ 2861.964] (II) vmware(0): Modeline "1600x1200"x60.0 162.00 1600 1664 1856 2160 1200 1201 1204 1250 +hsync +vsync (75.0 kHz e)
[ 2861.964] (II) vmware(0): Modeline "1680x1050"x60.0 146.25 1680 1784 1960 2240 1050 1053 1059 1089 -hsync +vsync (65.3 kHz e)
[ 2861.964] (II) vmware(0): Modeline "1400x1050"x60.0 121.75 1400 1488 1632 1864 1050 1053 1057 1089 -hsync +vsync (65.3 kHz e)
[ 2861.964] (II) vmware(0): Modeline "1280x1024"x60.0 108.00 1280 1328 1440 1688 1024 1025 1028 1066 +hsync +vsync (64.0 kHz e)
[ 2861.964] (II) vmware(0): Modeline "1440x900"x59.9 106.50 1440 1520 1672 1904 900 903 909 934 -hsync +vsync (55.9 kHz e)
[ 2861.964] (II) vmware(0): Modeline "1280x960"x60.0 108.00 1280 1376 1488 1800 960 961 964 1000 +hsync +vsync (60.0 kHz e)
[ 2861.964] (II) vmware(0): Modeline "1360x768"x60.0 85.50 1360 1424 1536 1792 768 771 777 795 +hsync +vsync (47.7 kHz e)
[ 2861.964] (II) vmware(0): Modeline "1280x800"x59.8 83.50 1280 1352 1480 1680 800 803 809 831 +hsync -vsync (49.7 kHz e)
[ 2861.964] (II) vmware(0): Modeline "1152x864"x75.0 108.00 1152 1216 1344 1600 864 865 868 900 +hsync +vsync (67.5 kHz e)
[ 2861.964] (II) vmware(0): Modeline "1280x768"x59.9 79.50 1280 1344 1472 1664 768 771 778 798 -hsync +vsync (47.8 kHz e)
[ 2861.964] (II) vmware(0): Modeline "1024x768"x60.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz e)
[ 2861.964] (II) vmware(0): Modeline "800x600"x60.3 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz e)
[ 2861.964] (II) vmware(0): Modeline "640x480"x59.9 25.18 640 656 752 800 480 489 492 525 -hsync -vsync (31.5 kHz e)
[ 2861.964] (II) vmware(0): EDID for output Virtual2
[ 2861.965] (II) vmware(0): EDID for output Virtual3
[ 2861.965] (II) vmware(0): EDID for output Virtual4
[ 2861.965] (II) vmware(0): EDID for output Virtual5
[ 2861.965] (II) vmware(0): EDID for output Virtual6
[ 2861.965] (II) vmware(0): EDID for output Virtual7
[ 2861.965] (II) vmware(0): EDID for output Virtual8
[ 2861.965] (II) vmware(0): Output Virtual1 connected
[ 2861.965] (II) vmware(0): Output Virtual2 disconnected
[ 2861.965] (II) vmware(0): Output Virtual3 disconnected
[ 2861.965] (II) vmware(0): Output Virtual4 disconnected
[ 2861.965] (II) vmware(0): Output Virtual5 disconnected
[ 2861.965] (II) vmware(0): Output Virtual6 disconnected
[ 2861.965] (II) vmware(0): Output Virtual7 disconnected
[ 2861.965] (II) vmware(0): Output Virtual8 disconnected
[ 2861.965] (II) vmware(0): Using exact sizes for initial modes
[ 2861.965] (II) vmware(0): Output Virtual1 using initial mode 1280x768
[ 2861.965] (II) vmware(0): Using default gamma of (1.0, 1.0, 1.0) unless otherwise stated.
[ 2861.965] (==) vmware(0): DPI set to (96, 96)
[ 2861.965] (II) Loading sub module "fb"
[ 2861.965] (II) LoadModule: "fb"
[ 2861.965] (II) Loading /usr/lib/xorg/modules/libfb.so
[ 2861.965] (II) Module fb: vendor="X.Org Foundation"
[ 2861.965] compiled for 1.16.2, module version = 1.0.0
[ 2861.965] ABI class: X.Org ANSI C Emulation, version 0.4
[ 2861.965] (II) Loading sub module "dri2"
[ 2861.965] (II) LoadModule: "dri2"
[ 2861.965] (II) Module "dri2" already built-in
[ 2861.965] (==) Depth 24 pixmap format is 32 bpp
[ 2861.966] (II) vmware(0): Initialized VMWARE_CTRL extension version 0.2
[ 2861.967] (WW) vmware(0): Failed to initialize Gallium3D Xa. No render acceleration available.
[ 2861.967] (WW) vmware(0): Skipped initialization of direct rendering due to lack of render acceleration.
[ 2861.967] (--) vmware(0): Render acceleration is disabled.
[ 2861.967] (==) vmware(0): Rendercheck mode is disabled.
[ 2861.967] (--) vmware(0): Direct rendering (3D) is disabled.
[ 2861.967] (==) vmware(0): Backing store enabled
[ 2861.967] (==) vmware(0): Silken mouse enabled
[ 2861.967] (II) vmware(0): RandR 1.2 enabled, ignore the following RandR disabled message.
[ 2861.967] (==) vmware(0): DPMS enabled
[ 2861.967] (II) vmware(0): No 3D acceleration. Not setting up textured video.
[ 2861.967] (--) RandR disabled
[ 2861.981] (EE) Failed to initialize GLX extension (Compatible NVIDIA X driver not found)
[ 2862.011] (II) vmware(0): Setting screen physical size to 338 x 203
[ 2862.235] (II) config/udev: Adding input device Power Button (/dev/input/event1)
[ 2862.235] (**) Power Button: Applying InputClass "evdev keyboard catchall"
[ 2862.235] (II) LoadModule: "evdev"
[ 2862.235] (II) Loading /usr/lib/xorg/modules/input/evdev_drv.so
[ 2862.236] (II) Module evdev: vendor="X.Org Foundation"
[ 2862.236] compiled for 1.16.0, module version = 2.9.0
[ 2862.236] Module class: X.Org XInput Driver
[ 2862.236] ABI class: X.Org XInput driver, version 21.0
[ 2862.237] (EE) systemd-logind: failed to take device /dev/input/event1: Operation not permitted
[ 2862.237] (II) Using input driver 'evdev' for 'Power Button'
[ 2862.237] (**) Power Button: always reports core events
[ 2862.237] (**) evdev: Power Button: Device: "/dev/input/event1"
[ 2862.237] (--) evdev: Power Button: Vendor 0 Product 0x1
[ 2862.237] (--) evdev: Power Button: Found keys
[ 2862.237] (II) evdev: Power Button: Configuring as keyboard
[ 2862.237] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXPWRBN:00/input/input2/event1"
[ 2862.237] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 6)
[ 2862.237] (**) Option "xkb_rules" "evdev"
[ 2862.237] (**) Option "xkb_model" "pc104"
[ 2862.237] (**) Option "xkb_layout" "us"
[ 2862.284] (II) config/udev: Adding input device VMware VMware Virtual USB Mouse (/dev/input/event3)
[ 2862.284] (**) VMware VMware Virtual USB Mouse: Applying InputClass "evdev pointer catchall"
[ 2862.285] (EE) systemd-logind: failed to take device /dev/input/event3: Operation not permitted
[ 2862.285] (II) Using input driver 'evdev' for 'VMware VMware Virtual USB Mouse'
[ 2862.285] (**) VMware VMware Virtual USB Mouse: always reports core events
[ 2862.285] (**) evdev: VMware VMware Virtual USB Mouse: Device: "/dev/input/event3"
[ 2862.285] (--) evdev: VMware VMware Virtual USB Mouse: Vendor 0xe0f Product 0x3
[ 2862.285] (--) evdev: VMware VMware Virtual USB Mouse: Found 12 mouse buttons
[ 2862.285] (--) evdev: VMware VMware Virtual USB Mouse: Found scroll wheel(s)
[ 2862.285] (--) evdev: VMware VMware Virtual USB Mouse: Found relative axes
[ 2862.285] (--) evdev: VMware VMware Virtual USB Mouse: Found x and y relative axes
[ 2862.285] (II) evdev: VMware VMware Virtual USB Mouse: Configuring as mouse
[ 2862.285] (II) evdev: VMware VMware Virtual USB Mouse: Adding scrollwheel support
[ 2862.285] (**) evdev: VMware VMware Virtual USB Mouse: YAxisMapping: buttons 4 and 5
[ 2862.285] (**) evdev: VMware VMware Virtual USB Mouse: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
[ 2862.285] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:11.0/0000:02:00.0/usb2/2-1/2-1:1.0/0003:0E0F:0003.0001/input/input5/event3"
[ 2862.285] (II) XINPUT: Adding extended input device "VMware VMware Virtual USB Mouse" (type: MOUSE, id 7)
[ 2862.285] (II) evdev: VMware VMware Virtual USB Mouse: initialized for relative axes.
[ 2862.285] (**) VMware VMware Virtual USB Mouse: (accel) keeping acceleration scheme 1
[ 2862.285] (**) VMware VMware Virtual USB Mouse: (accel) acceleration profile 0
[ 2862.285] (**) VMware VMware Virtual USB Mouse: (accel) acceleration factor: 2.000
[ 2862.285] (**) VMware VMware Virtual USB Mouse: (accel) acceleration threshold: 4
[ 2862.286] (II) config/udev: Adding input device VMware VMware Virtual USB Mouse (/dev/input/mouse0)
[ 2862.286] (II) No input driver specified, ignoring this device.
[ 2862.286] (II) This device may have been added with another device file.
[ 2862.286] (II) config/udev: Adding input device AT Translated Set 2 keyboard (/dev/input/event0)
[ 2862.286] (**) AT Translated Set 2 keyboard: Applying InputClass "evdev keyboard catchall"
[ 2862.286] (EE) systemd-logind: failed to take device /dev/input/event0: Operation not permitted
[ 2862.286] (II) Using input driver 'evdev' for 'AT Translated Set 2 keyboard'
[ 2862.286] (**) AT Translated Set 2 keyboard: always reports core events
[ 2862.286] (**) evdev: AT Translated Set 2 keyboard: Device: "/dev/input/event0"
[ 2862.286] (--) evdev: AT Translated Set 2 keyboard: Vendor 0x1 Product 0x1
[ 2862.286] (--) evdev: AT Translated Set 2 keyboard: Found keys
[ 2862.286] (II) evdev: AT Translated Set 2 keyboard: Configuring as keyboard
[ 2862.286] (**) Option "config_info" "udev:/sys/devices/platform/i8042/serio0/input/input0/event0"
[ 2862.286] (II) XINPUT: Adding extended input device "AT Translated Set 2 keyboard" (type: KEYBOARD, id 8)
[ 2862.286] (**) Option "xkb_rules" "evdev"
[ 2862.286] (**) Option "xkb_model" "pc104"
[ 2862.286] (**) Option "xkb_layout" "us"
[ 2862.287] (II) config/udev: Adding input device ImPS/2 Generic Wheel Mouse (/dev/input/event4)
[ 2862.287] (**) ImPS/2 Generic Wheel Mouse: Applying InputClass "evdev pointer catchall"
[ 2862.287] (**) ImPS/2 Generic Wheel Mouse: Applying InputClass "vmmouse"
[ 2862.287] (II) LoadModule: "vmmouse"
[ 2862.287] (II) Loading /usr/lib/xorg/modules/input/vmmouse_drv.so
[ 2862.287] (II) Module vmmouse: vendor="X.Org Foundation"
[ 2862.287] compiled for 1.16.0, module version = 13.0.0
[ 2862.287] Module class: X.Org XInput Driver
[ 2862.287] ABI class: X.Org XInput driver, version 21.0
[ 2862.287] (II) VMWARE(0): VMMOUSE module was loaded
[ 2862.287] (II) Using input driver 'vmmouse' for 'ImPS/2 Generic Wheel Mouse'
[ 2862.287] (**) ImPS/2 Generic Wheel Mouse: always reports core events
[ 2862.288] (II) VMWARE(0): vmmouse is available
[ 2862.288] (**) Option "Device" "/dev/input/event4"
[ 2862.334] (**) ImPS/2 Generic Wheel Mouse: ZAxisMapping: buttons 4 and 5
[ 2862.334] (**) Option "config_info" "udev:/sys/devices/platform/i8042/serio1/input/input4/event4"
[ 2862.334] (II) XINPUT: Adding extended input device "ImPS/2 Generic Wheel Mouse" (type: MOUSE, id 9)
[ 2862.334] (II) VMWARE(0): VMMOUSE DEVICE_INIT
[ 2862.334] (**) ImPS/2 Generic Wheel Mouse: (accel) keeping acceleration scheme 1
[ 2862.334] (**) ImPS/2 Generic Wheel Mouse: (accel) acceleration profile 0
[ 2862.334] (**) ImPS/2 Generic Wheel Mouse: (accel) acceleration factor: 2.000
[ 2862.334] (**) ImPS/2 Generic Wheel Mouse: (accel) acceleration threshold: 4
[ 2862.334] (II) VMWARE(0): VMMOUSE DEVICE_ON
[ 2862.334] (II) VMWARE(0): vmmouse enabled
[ 2862.335] (II) config/udev: Adding input device ImPS/2 Generic Wheel Mouse (/dev/input/mouse1)
[ 2862.335] (II) No input driver specified, ignoring this device.
[ 2862.335] (II) This device may have been added with another device file.
[ 2862.336] (II) config/udev: Adding input device PC Speaker (/dev/input/event2)
[ 2862.336] (II) No input driver specified, ignoring this device.
[ 2862.336] (II) This device may have been added with another device file.
[ 2865.760] (II) VMWARE(0): VMMOUSE DEVICE_OFF/CLOSE
[ 2865.883] (II) VMWARE(0): VMMOUSE DEVICE_OFF/CLOSE
[ 2866.184] (II) VMWARE(0): VMMouseUnInit
[ 2866.184] (II) evdev: AT Translated Set 2 keyboard: Close
[ 2866.184] (II) UnloadModule: "evdev"
[ 2866.184] (II) evdev: VMware VMware Virtual USB Mouse: Close
[ 2866.184] (II) UnloadModule: "evdev"
[ 2866.184] (II) evdev: Power Button: Close
[ 2866.184] (II) UnloadModule: "evdev"
[ 2866.219] (EE) Server terminated successfully (0). Closing log file.
[herminio@archlinux-vm ~]$

[SOLVED] New arch install from Virtualbox cannot boot on real hardware

Hi,
I'm trying my luck with installing Arch on physical disk through Virtualbox. I followed Wiki and managed to install system on the disk. However, I am unable to boot it outside VM.
I have two physical disks - /dev/sda and /dev/sdb. I have installed Arch on /dev/sda1. It is there, I can see the files from my current OS and it does work in VM. /dev/sda1 is bootable.
However, when I boot my PC from /dev/sda rootfs fails to load kernel image - it says it can't be found. I tried specifing init path in Syslinux.cfg using /dev/sdxX and UUID and even PARTUUID but none worked. When in rootfs, I lsed /dev/disk/by-uuid and found that rootfs sees only one of my two disks, /dev/sdb. I find it really strange.
I followed below advise found on forums:
- Verify that mkinitcpio.conf lists "block" hook
- Create a new kernel image with mkinitcpio -p linux
- Refer to your partition by UUID
- If above doesn't work, try PARTUUID
None of these worked. I believe the reason for this is that the issue is not with how I reference the disk nor how the mkinitcpio works but with the disk not being available for rootfs at all. Alas, I have no experience with disks other than simple partitioning, so I'm not sure where to start.
Fdisk output:
Disk /dev/sda: 931,5 GiB, 1000204886016 bytes, 1953525168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x99ea4d63
Device Boot Start End Sectors Size Id Type
/dev/sda1 * 2048 314779647 314777600 150,1G 83 Linux
/dev/sda2 314779648 1153640447 838860800 400G 83 Linux
/dev/sda3 1153640448 1157834751 4194304 2G 82 Linux swap / Solaris
Disk /dev/sdb: 465,8 GiB, 500107862016 bytes, 976773168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: dos
Disk identifier: 0x75a6998e
Device Boot Start End Sectors Size Id Type
/dev/sdb1 * 2048 616447 614400 300M 83 Linux
/dev/sdb2 616448 210331647 209715200 100G 83 Linux
/dev/sdb3 210331648 241788927 31457280 15G 83 Linux
Any ideas? Suggestions and help will be appreciated!
Last edited by karm (2014-12-08 03:56:35)

Sleep is for the weak.
So I've read that article and found what the issue was.
Turns out I automatically followed previous advise without giving it some thought and run mkinitcpio from Virtualbox. Which does not make sense because the whole point of this is to prepare kernel image to run on other hardware than provided by VM. So what I did to fix this:
1. Installed arch-chroot on VM
2. Mounted /dev/sda1 on my host machine and chrooted into it using arch-chroot
3. Run mkinitpcio -p linux
4. Reinstalled boot loader just in case with syslinux-install_update -iam /dev/sda1
5. Adjusted /boot/syslinux/syslinux.cfg to work with new configuration:
5.1 set root=UUID=..... to be certain it picks the right partition
5.2 add proper systemd init path APPEND=/usr/lib/systemd/systemd
And it does work - I'm posting from my new shiny system. Thanks a lot ackt1c!

[SOLVED] Changed an option in /etc/updatedb.conf

Hello all,
I started using locate to search my files. However, it never showed files in my /home directory which is, obviously, the directory I search most. Running updatedb --debug-pruning I found out that it didn't add /home to the database because it's an "autofs" filetype:
┌─[jente @ lappy ~] 23:54:27
└─■ sudo updatedb --debug-pruning
`/home' (32 on 18) is `/' of `systemd-1' (0:27), type `autofs'
Skipping `/home': in prunefs
So, I edited /etc/updatedb.conf and removed autofs from the PRUNEFS line. I never found any documentation on this and thus, I don't know if this is the correct way of solving this. Hence this post; I would just like to get some feedback on whether or not I fixed this the right way.
Thanks in advance, guys!
Last edited by Unia (2012-12-15 13:45:36)

Unia wrote:
Mr.Elendig wrote:Another way would be to add your /home to fstab instead.
Hey! Thanks for your input. My /home is actually already there:
# /etc/fstab: static file system information
# <file system> <dir> <type> <options> <dump> <pass>
tmpfs /tmp tmpfs nodev,nosuid 0 0
# /dev/sda1
UUID=60eb73f7-635c-4b3e-9d6a-8bb49aee739a / ext4 rw,relatime 0 1
# /dev/sda2 LABEL=home
UUID=4470b151-db99-4586-a652-398e0e8995cb /home ext4 rw,relatime,noauto,x-systemd.automount 0 2
If your /home is on an internal disk, why use automount?

[SOLVED] Borked systemd setup -- dbus errors during boot; can't login

I have error messages very similar to this post. Unfortunately, as the author states, he never persisted in solving it but instead re-installed from scratch. I'd rather not do that.
For reference, I have a pure systemd setup -- no rc.conf file, no initscripts package, etc.
At boot I get the "Welcome to Arch!" messages followed by the various [OK] lines and then I get blindingly fast repeating lines about dbus not starting and attempting to restart it too quickly. If I walk away for about 1-2min, I finally see a login screen, but after entering my username/password, it just sits there and does nothing.
As for suspects... I had systemd working fine.
-- I updated some packages (not more than a few days worth and I'd have to check the list)
-- I also took care of manual updates to some .pacnew files I periodically check for. In this group were some biggies: group, shadow, and passwd. I did recall the odd bit about uuidd changing from uid 995 to 68, but in reading about that since then, it doesn't seem to be a big deal.
I've been booting in by appending
systemd.unit=emergency.target
to the kernel line, but my exploration hasn't been all that helpful. `journalctl since=date` reveals the errors, but I don't get much information about why dbus is having issues starting.
emergency.target also doesn't seem to be that helpful since I can't do anything with a read-only system. I'd love some suggestions about what, specifically, to check for before I reboot from Windows back into Arch and record more careful notes, probably by jotting notes onto a flash drive. Any places to start? For reference, I've done:
-- systemctl status dbus: lists as inactive (dead) and simply shows the errors I see at boot (failed to start)
-- systemctl list-units
-- systemctl list-unit-files
-- journalctl and looking around for instances of fail or failed or dbus
If I start systemd-logind.service or dbus.service, it displays a status message about running fsck and then takes me to a login prompt automatically. Then I can type in my username and password and then there's nothing after that. No prompt, just an apparent hang.
Thanks for any suggestions -- I'll take them and then collect more detailed results and report back.
Thanks!
Last edited by jwhendy (2012-11-08 16:07:33)

As I wondered, I think it's a problem with passwd. I don't have a dbus entry and must have missed it when I was copying things around between my version and the .pacnew. Downloading an install disc now since I can't seem to change it from the recovery console due to mounting root read-only.
I'd love to know of a way to boot that avoids starting dbus and other things that might break while still having read/write access to root. Will mark solved once I update /etc/passwd and reboot.

[solved] new systemd-sysctl applies 99-sysctl.conf before networkd?

Similar Messages

Maybe you are looking for