Mpd systemd issues
Hello all,
I'm not a guru of systemd but I try to have an idea of what's going on. I had set up systemd user session with previous versions. I think also my system is not propeprly configured as I see multiple errors in journal.
I'm attaching my logs from journal --this-log with hopes that someone will understand something more than me. As it stands I can't start mpd which I had it configured as user. Also I think I don't completely understand the systemd user session.
journal.log: http://pastebin.com/LHKqb0DN
Thanks in advance for any comments
~$ systemctl status [email protected]
[email protected]
Loaded: not-found (Reason: No such file or directory)
Active: inactive (dead)
~$ cat .config/systemd/user/mpd.service 3 ↵
[Unit]
Description=Music Player Daemon
After=network.target sound.target
[Service]
ExecStart=/usr/bin/mpd --no-daemon /home/inglor/.mpd/mpd.conf
[Install]
WantedBy=multi-user.target
Similar Messages
-
MPD Pulseaudio issues [SOLVED]
Hi,
I've just setup pulseaudio on my system as I was tired of not being able to handle simultaneous output whilst one program had control of the soundcard (using alsa).
I run MPD from startup with the user "mpd", unfortunately when it starts, it starts it's own pulseaudio session which conflicts with that when I launch into X, therefore I can either have sound from mpd (that pulseaudio session uses the soundcard) or other programs launched as me e.g. chromium, rhythmbox, mplayer etc (and my user's pulseaudio session locks the soundcard).
What's the best way to remedy this situation so that I only have one pulseaudio session running? I'm toying with the idea of launching mpd as myself using .xinitrc. Ideally I want to just run one pulseaudio session and leave my mpd configuration as is.
Any thoughts or ideas would be most appreciated.
Thanks.
Last edited by will.price94 (2012-02-14 16:51:19)OK Scott, I'll do that. Thank you for your suggestion. Hopefully it will remedy the issues I'm having.
EDIT: Worked a treat, no more issues!
Last edited by will.price94 (2012-02-14 16:51:05) -
Systemd issues. mdadm-raid and nfs with no network timeouts.
Hi,
I'm migrating my final two machines to systemd now and ran into some troubles.
Issue 1:
I've got a md-raid that systemd tries to 'start' (dev-md0p1.device).
This obviously doesn't work since there is nothing to 'start' and it just times out after 90 seconds thus entering emergency mode.
From there I can mount /dev/md0p1 just fine.
Is there any way to make systemd just mount the device and do nothing else?
Issue 2:
I'm not booting my laptop with network, but has a NFS-entry in fstab.
systemd still tries to mount it, delaying the boot with 90 seconds.
x-systemd.device-timeout doesn't make any difference at all.
Any way to fix this? They say it shouldn't try mount any network devices when no network is up...
Thank you for all help!Ok, if someone else encounters these problems:
The nfs-shares need the option "command=systemd.automount" for systemd to care about them apparently. Normal auto is not enough.
Systemd makes the md0-device busy during boot at about the same time it tries to mount md0p1 making it busy and time out.
Running systemctl --system daemon-reload makes it reload everything that hangs, 4 services/devices in my case.
Not a good solution, but I'm pretty fed up with systemd now.
Last edited by Goophy (2012-09-05 22:32:24) -
Mysterious NFS and systemd issue
I don't know what to do with this problem
I have a cluster that runs arch linux. 20 compute nodes, a fast login node, and a head node that runs scientific linux 6.2 and has two large RAID drives attached (it also provides DNS, DHCP, and torque servers). The cluster is connected by a DDR infiniband network, including a direct infiniband connection between the login node and the head node. That infiniband has IPoIB set up, and an NFSv3 filesystem running over that. For years it just worked, with read/write speeds over 600MB/s, but in the last week or two it has started having lots of trouble. It is just really slow, sometimes the whole login node is slow for no good reason, but mostly that fast network drive is crushingly slow, with no heavy traffic. The problem is the same regardless of which network device I use, ethernet or infiniband. Plus, the login node itself has frozen and crashed several times in the last week. Major stability issues are just appearing out of nowhere.
Here is the best part though: I can see *nothing* useful in journalctl, or in any old-fashioned syslogs, on any of the nodes. Nothing. The only thing I see that is out of place is the following message repeating about once every three minutes:
Nov 17 08:09:47 fraser-server systemd[6962]: Starting Exit the Session...
Nov 17 08:09:47 fraser-server systemd[6962]: Reached target Shutdown.
Nov 17 08:09:47 fraser-server systemd[6962]: Starting Shutdown.
Nov 17 08:09:47 fraser-server systemd[6962]: Stopped target Sockets.
Nov 17 08:09:47 fraser-server systemd[6962]: Stopping Sockets.
Nov 17 08:09:47 fraser-server systemd[6962]: Stopped target Timers.
Nov 17 08:09:47 fraser-server systemd[6962]: Stopping Timers.
Nov 17 08:09:47 fraser-server systemd[6962]: Stopped target Paths.
Nov 17 08:09:47 fraser-server systemd[6962]: Stopping Paths.
Nov 17 08:09:47 fraser-server systemd[6962]: Stopped target Basic System.
Nov 17 08:09:46 fraser-server systemd[6962]: Stopping Basic System.
Nov 17 08:09:46 fraser-server systemd[6962]: Stopped target Default.
I get the distinct impression that that is completely unrelated though.
The output of nfsstat -v for both servers are here:
https://gist.github.com/MikeDacre/2d1b3e9c4bd17c96c97f
I am pretty sure this isn't the right place to post this problem, probably I should be emailing an infiniband or nfs forum, but with the complete lack of log information or any sign of hardware trouble, I really don't even know where to begin.
Anyone have any idea on where else I should be looking? Any good debug options I should try?Hi,
I'm answering to myself.
Akonadi was the problem.
Even if I have disabled the search features in KDE configuration, if in console I type the following command:
akonadictl status
It shows me:
Akonadi Control: started
Akonadi Server: started
Akonadi Server Search Support: not available
I've edited .config/akonadi/akonadiserverrc file and set StartServer to false
I've also disabled the launch of Korganizer (as it uses Akonadi).
After a reboot, Akonadi is not launching anymore and I could shutdown correctly my computer.
Last edited by beber75 (2011-05-26 09:13:00) -
[SOLVED] Wifi won't auto connect on boot - systemd issue?
I'm using netcfg and have a working profile for a WPA wireless network. Connecting using netcfg from the terminal works reliably.
However, I can't get automatic wifi connection at boot to work. I've followed the wiki instructions on the netcfg page, but some thing isn't quite right.
Last in the post is the output from:
$ systemctl status net-auto-wireless.service
Could this be some kind of timing / starting order issue with systemd and the network-related services?
Any ideas anyone?
net-auto-wireless.service - Provides automatic netcfg wireless connection
Loaded: loaded (/usr/lib/systemd/system/net-auto-wireless.service; enabled)
Active: active (running) since Sat, 2013-01-12 20:32:01 CET; 1min 39s ago
Process: 1142 ExecStart=/usr/bin/netcfg-wpa_actiond $WIRELESS_INTERFACE (code=exited, status=0/SUCCESS)
CGroup: name=systemd:/system/net-auto-wireless.service
└─1323 /usr/sbin/wpa_actiond -p /run/wpa_supplicant -i wlan...
Jan 12 20:32:00 carbon systemd[1]: Starting Provides automatic netcfg wireless connection...
Jan 12 20:32:00 carbon netcfg-wpa_actiond[1142]: catland
Jan 12 20:32:01 carbon wpa_actiond[1323]: Starting wpa_actiond session for interface 'wlan0'
Jan 12 20:32:01 carbon systemd[1]: Started Provides automatic netcfg wireless connection.
Jan 12 20:32:04 carbon wpa_actiond[1323]: Interface 'wlan0' connected to network 'CATLAND'
Jan 12 20:32:04 carbon dhcpcd[1402]: version 5.6.4 starting
Jan 12 20:32:04 carbon dhcpcd[1402]: wlan0: sending IPv6 Router Solicitation
Jan 12 20:32:04 carbon dhcpcd[1402]: wlan0: sendmsg: Cannot assign requested address
Jan 12 20:32:04 carbon dhcpcd[1402]: wlan0: broadcasting for a lease
Jan 12 20:32:08 carbon dhcpcd[1402]: wlan0: send_raw_packet: Network is down
Jan 12 20:32:08 carbon dhcpcd[1402]: wlan0: sending IPv6 Router Solicitation
Jan 12 20:32:08 carbon dhcpcd[1402]: wlan0: sendmsg: Network is unreachable
Jan 12 20:32:12 carbon dhcpcd[1402]: wlan0: sending IPv6 Router Solicitation
Jan 12 20:32:12 carbon dhcpcd[1402]: wlan0: sendmsg: Network is unreachable
Last edited by 4ZM (2013-01-14 08:16:17)For posterity: the problem seems to be that I hadn't enabled netcfg@<networkprofile>.service with systemd. I had only enabled my wired profile. I.e. doing 'systemctl enable [email protected]' fixed it.
In short this was a failure to configure netcfg startup with systemd. But hey, that makes it (drum roll...) a sysytemd issue! Like most of the problems one encounters while setting up a computer; it is a configuration issue (i.e. PEBKAC). But hey, thats what the forums are for.
@Trilby, @WonderWoofy Thank you both for your insightful, constructive and, above all, helpful comments. I hope everyone else coming to this thread for information on why their wifi won't start will find them every bit as useful as I did. -
I followed the wiki but sonata does not play music at all.
Is there a hidden step or am I just a little slow?
#Edit
I think I have all the codecs installed, amarok works fine.
Last edited by dustinw (2009-03-17 01:05:35)Maybe you've forgot to configure the "device" section in mpd.conf?
You should specify something, for example like this:
############################# MIXER ############################
# MPD needs to know what mixer settings to change when you
# adjust the volume. If you don't specify one here, MPD will
# pick one based on which ones it was compiled with support for.
# An example for controlling an ALSA mixer:
mixer_type "alsa"
mixer_device "default"
mixer_control "PCM"
# An example for controlling an OSS mixer:
#mixer_type "oss"
#mixer_device "/dev/mixer"
#mixer_control "PCM"
# If you want MPD to adjust the volume of audio sent to the
# audio outputs, you can tell it to use the software mixer:
#mixer_type "software"
Or what now is applicable in your system. Looks like it plays but doesn't know what device to use. -
Hello!
I've installed Dropbox from the AUR, and am starting it for my user using sytemd (sytemctl enable [email protected]).
It works fine, but it seems that the actual dropboxd executable only executes a "local one" from my home directory (~/.dropbox-dist/dropbox).
This seems to cause systemd trying to restart it all over again, which has to fail as dropbox is already running...
In journalctl, this looks like
Apr 05 13:03:07 thorin systemd[1]: [email protected]: main process exited, code=killed, status=9/KILL
Apr 05 13:03:07 thorin systemd[1]: Unit [email protected] entered failed state
Apr 05 13:03:07 thorin systemd[1]: [email protected] holdoff time over, scheduling restart.
Apr 05 13:03:08 thorin dropboxd[682]: Another instance of Dropbox (592) is running!
Apr 05 13:03:09 thorin systemd[1]: [email protected]: main process exited, code=exited, status=255/n/a
Apr 05 13:03:09 thorin systemd[1]: Unit [email protected] entered failed state
Apr 05 13:03:09 thorin systemd[1]: [email protected] holdoff time over, scheduling restart.
Apr 05 13:03:10 thorin dropboxd[738]: Another instance of Dropbox (592) is running!
Apr 05 13:03:10 thorin systemd[1]: [email protected]: main process exited, code=exited, status=255/n/a
Apr 05 13:03:10 thorin systemd[1]: Unit [email protected] entered failed state
Apr 05 13:03:10 thorin systemd[1]: [email protected] holdoff time over, scheduling restart.
Apr 05 13:03:11 thorin dropboxd[768]: Another instance of Dropbox (592) is running!
Apr 05 13:03:11 thorin systemd[1]: [email protected]: main process exited, code=exited, status=255/n/a
Apr 05 13:03:11 thorin systemd[1]: Unit [email protected] entered failed state
Apr 05 13:03:11 thorin systemd[1]: [email protected] holdoff time over, scheduling restart.
Apr 05 13:03:11 thorin dropboxd[805]: Another instance of Dropbox (592) is running!
Apr 05 13:03:11 thorin systemd[1]: [email protected]: main process exited, code=exited, status=255/n/a
Apr 05 13:03:11 thorin systemd[1]: Unit [email protected] entered failed state
Apr 05 13:03:12 thorin systemd[1]: [email protected] holdoff time over, scheduling restart.
Apr 05 13:03:12 thorin dropboxd[836]: Another instance of Dropbox (592) is running!
Apr 05 13:03:12 thorin systemd[1]: [email protected]: main process exited, code=exited, status=255/n/a
Apr 05 13:03:12 thorin systemd[1]: Unit [email protected] entered failed state
Apr 05 13:03:13 thorin systemd[1]: [email protected] holdoff time over, scheduling restart.
Apr 05 13:03:13 thorin systemd[1]: [email protected] start request repeated too quickly, refusing to start.
Apr 05 13:03:13 thorin systemd[1]: Unit [email protected] entered failed state
Did I do wrong? If yes, could you help me out here and tell me what I shoud do instead? E.g. start dropboxd usint .xinitrc/.xsession?
Thanks in advance!I don't know why, but on my home server systemd launch ~/.dropbox-dist/dropbox too.
I just remove all (exclude ~/.dropbox and ~/Dropbox folders) off old versions files from $HOME, /opt and /usr (include /usr/lib/systemd/system/dropbox*) and reinstall dropbox with yaourt. Then `sudo systemctl start dropbox@$USER.service` work normally
Last edited by Felixoid (2013-04-05 14:45:51) -
Systemd Issues - Failed to start MyApp daemon
Hi all,
Sorry if I'm asking a stupid question, I'm new to Arch Linux, Pi, and Python. I have a Python script I'd like to start automatically after boot so I created a myapp.service file:
[Unit]
Description=MyApp daemon
Requires=network.target
[Service]
Type=forking
ExecStart=/root/bin/myapp/initmyapp.py
ExecStop=/bin/kill $MAINPID
[Install]
WantedBy=multi-user.target
After initmyapp.py runs it calls "myapp.py &" that's why I tried type=forking. I tested "systemctl start myapp" and it looks like it's working; I can see the process running. So, I did "systemctl enable myapp" which ran without errors and then I rebooted. After reboot, however, the process is not running and "systemctl status myapp" tells me this:
myapp.service - MyApp daemon
Loaded: loaded (/etc/systemd/system/myapp.service; enabled)
Active: failed (Result: exit-code) since Wed, 1969-12-31 19:00:10 EST; 43 years and 0 months ago
Process: 102 ExecStart=/root/bin/myapp/initmyapp.py (code=exited, status=1/FAILURE)
CGroup: name=systemd:/system/myapp.service
Dec 31 19:00:09 mybox initmyapp.py[102]: '_open', req)
Dec 31 19:00:09 mybox initmyapp.py[102]: File "/usr/lib/python2.7/urllib2.py", line 378, in _call_chain
Dec 31 19:00:09 mybox initmyapp.py[102]: result = func(*args)
Dec 31 19:00:09 mybox initmyapp.py[102]: File "/usr/lib/python2.7/urllib2.py", line 1207, in http_open
Dec 31 19:00:09 mybox initmyapp.py[102]: return self.do_open(httplib.HTTPConnection, req)
Dec 31 19:00:09 mybox initmyapp.py[102]: File "/usr/lib/python2.7/urllib2.py", line 1177, in do_open
Dec 31 19:00:10 mybox initmyapp.py[102]: raise URLError(err)
Dec 31 19:00:10 mybox initmyapp.py[102]: urllib2.URLError: <urlopen error [Errno -2] Name or service not known>
Dec 31 19:00:10 mybox systemd[1]: Failed to start MyApp daemon.
Dec 31 19:00:10 mybox systemd[1]: Unit myapp.service entered failed state
Does this mean that networking is not ready yet? Instead of Requires=network.target I also tried Requires=multi-user.target but didn't work. I have no idea what I'm doing so any suggestion would be appreciated.Thank you for the quick response. I removed the kill part and "stop" still works. I also removed all the network includes to test it out and the background call too and after hours of trial and error I was finally able to make it work. Now I just have to figure out how to tell when the network is up. That article covers it for C (I think) but not for Python. It also seems very technical.
Anyway, thanks again for your help. -
Systemd: Suspend and Hibernate not working
Hi,
When I try to hibernate my Notebook using systemd with 'systemctl hibernate', it sometimes (from time to time it even works) fails with the error message "a dependency job for hibernate.target failed". In the journal I see the following:
The system clock has been changed to REALTIME microseconds after January 1st, 1970.
Jun 04 23:52:57 localhost systemd[1]: systemd-hibernate.service: main process exited, code=exited, status=1/FAILURE
Jun 04 23:52:57 localhost systemd[1]: Failed to start Hibernate.
-- Subject: Unit systemd-hibernate.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/li … temd-devel
-- Unit systemd-hibernate.service has failed.
-- The result is failed.
Jun 04 23:52:57 localhost systemd[1]: Dependency failed for Hibernate.
-- Subject: Unit hibernate.target has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/li … temd-devel
-- Unit hibernate.target has failed.
-- The result is dependency.
Jun 04 23:52:57 localhost systemd[1]: Service sleep.target is not needed anymore. Stopping.
Jun 04 23:52:57 localhost systemd[1]: Unit systemd-hibernate.service entered failed state.
Jun 04 23:52:57 localhost systemd[1]: Stopping Sleep.
-- Subject: Unit sleep.target has begun shutting down
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/li … temd-devel
-- Unit sleep.target has begun shutting down.
Jun 04 23:52:57 localhost systemd[1]: Stopped target Sleep.
-- Subject: Unit sleep.target has finished shutting down
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/li … temd-devel
-- Unit sleep.target has finished shutting down.
:x
Any ideas? Furthermore, during hibernate (when it works) my screen first gets black, the system comes back and only then it really hibernates.
Others suggest switching to linux-lts. Does that really make sense? Isn't this a systemd issue?
suspend sometimes fails to work either (screen gets blank, but system weaks up after a few seconds again):
Jun 05 06:59:14 localhost systemd[1]: Stopping Sleep.
-- Subject: Unit sleep.target has begun shutting down
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/li … temd-devel
-- Unit sleep.target has begun shutting down.
Jun 05 06:59:14 localhost systemd[1]: Stopped target Sleep.
-- Subject: Unit sleep.target has finished shutting down
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/li … temd-devel
-- Unit sleep.target has finished shutting down.
Jun 05 06:59:14 localhost systemd[1]: Reached target Suspend.
-- Subject: Unit suspend.target has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/li … temd-devel
-- Unit suspend.target has finished starting up.
-- The start-up result is done.
Thanks,
MichaelThanks, but I do not call systemd-sleep manually, I just do the ordinary "systemctl hibernate".
Unfortunately, the error "A dependency job for hibernate.target failed. See 'journalctl -xn' for details" just happened again. Alas, I'm not able to debug it according to the manual (https://wiki.archlinux.org/index.php/sy … emd_errors). When I try to get the log messages for the PID that causes hibernate.service to fail, I don't see anything suspicious in the logs:
$ sudo systemctl status systemd-hibernate.service
systemd-hibernate.service - Hibernate
Loaded: loaded (/usr/lib/systemd/system/systemd-hibernate.service; static)
Active: failed (Result: exit-code) since Fri 2014-06-13 14:32:52 CEST; 12min ago
Docs: man:systemd-suspend.service(8)
Process: 26712 ExecStart=/usr/lib/systemd/systemd-sleep hibernate (code=exited, status=1/FAILURE)
Main PID: 26712 (code=exited, status=1/FAILURE)
Jun 13 14:32:37 localhost systemd[1]: Starting Hibernate...
Jun 13 14:32:37 localhost systemd-sleep[26712]: Suspending system...
Jun 13 14:32:52 localhost systemd[1]: systemd-hibernate.service: main process exited, code=exited, status=1/FAILURE
Jun 13 14:32:52 localhost systemd[1]: Failed to start Hibernate.
Jun 13 14:32:52 localhost systemd[1]: Unit systemd-hibernate.service entered failed state.
$ sudo journalctl -b _PID=XXXX
-- Logs begin at Thu 2013-09-26 16:12:25 CEST, end at Fri 2014-06-13 14:43:40 CEST. --
Jun 13 14:32:37 localhost systemd-sleep[26712]: Suspending system...
Any ideas? -
[edited for additional question clarity]
[edited again showing result of running in.tftpd manually]
I have a recently installed systemd based machine with 2 NICs. One faces the LAN and runs dhcpcd, the other faces a local isolated subnet and runs dhcpd and tftpd.
Everything was working until an update early this week (including the new 3.6.9 kernel) caused the eth0 and eth1 to swap places.
I tried a udev rule to assign the eth0 and eth1, but it didn't seem to work.
Subsequently, I just renemaed the eth0 and eth1 in the dhcpd.service file and the /etc/conf.d/network file referenced by the network.service file.
Now dhcpd4 seems to be working, but tftpd is continuing to fail to start with the error:
Dec 12 09:36:57 beezey in.tftpd[1386]: cannot bind to local IPv4 socket: Address already in use
Dec 12 09:36:57 beezey systemd[1]: tftpd.service: main process exited, code=exited, status=71/n/a
Dec 12 09:36:57 beezey systemd[1]: Unit tftpd.service entered failed state
The tftpd.service file:
[root@beezey johnea]# cat /etc/systemd/system/tftpd.service
[Unit]
Description=hpa's original TFTP daemon
[Service]
ExecStart=/usr/sbin/in.tftpd -l -4 -s /srv/tftp/
StandardInput=socket
StandardOutput=inherit
StandardError=journal
[Install]
WantedBy=multi-user.target
I've used the network.service file indicated here:
https://wiki.archlinux.org/index.php/Co … IP_address
Including this file to configure the static eth0:
[root@beezey johnea]# cat /etc/conf.d/network
interface=eth0
address=10.20.30.1
netmask=24
broadcast=10.20.30.255
And started and stopped tftpd.socket prior to .service as instructed here:
https://wiki.archlinux.org/index.php/Tf … er#Systemd
Netstat show the IPv6 port 69 for tftpd, but there is no port 69 listening on IPv4:
[root@beezey johnea]# netstat --udp --tcp -l -n
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address Foreign Address State
tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN
tcp 0 0 127.0.0.1:6010 0.0.0.0:* LISTEN
tcp 0 0 127.0.0.1:6011 0.0.0.0:* LISTEN
tcp 0 0 127.0.0.1:6012 0.0.0.0:* LISTEN
tcp 0 0 127.0.0.1:6013 0.0.0.0:* LISTEN
tcp6 0 0 :::22 :::* LISTEN
tcp6 0 0 ::1:6010 :::* LISTEN
tcp6 0 0 ::1:6011 :::* LISTEN
tcp6 0 0 ::1:6012 :::* LISTEN
tcp6 0 0 ::1:6013 :::* LISTEN
udp 0 0 0.0.0.0:58493 0.0.0.0:*
udp 0 0 0.0.0.0:67 0.0.0.0:*
udp 0 0 10.20.30.1:123 0.0.0.0:*
udp 0 0 192.168.13.73:123 0.0.0.0:*
udp 0 0 127.0.0.1:123 0.0.0.0:*
udp 0 0 0.0.0.0:123 0.0.0.0:*
udp6 0 0 :::32138 :::*
udp6 0 0 :::69 :::*
udp6 0 0 fe80::21b:21ff:fe6b:123 :::*
udp6 0 0 fe80::1a03:73ff:fe3:123 :::*
udp6 0 0 ::1:123 :::*
udp6 0 0 :::123 :::*
I'm able to start in.tftpd manually via:
[root@beezey johnea]# in.tftpd -l -s /srv/tftp/
After this command line netstat shows the active socket 69 on IPv4 and IPv6:
[root@beezey johnea]# netstat --udp -l -n
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address Foreign Address State
udp 0 0 0.0.0.0:44194 0.0.0.0:*
udp 0 0 0.0.0.0:67 0.0.0.0:*
udp 0 0 0.0.0.0:69 0.0.0.0:*
udp 0 0 192.168.13.73:123 0.0.0.0:*
udp 0 0 10.20.30.1:123 0.0.0.0:*
udp 0 0 127.0.0.1:123 0.0.0.0:*
udp 0 0 0.0.0.0:123 0.0.0.0:*
udp6 0 0 :::41398 :::*
udp6 0 0 :::69 :::*
udp6 0 0 fe80::21b:21ff:fe6b:123 :::*
udp6 0 0 fe80::1a03:73ff:fe3:123 :::*
udp6 0 0 ::1:123 :::*
udp6 0 0 :::123 :::*
I'm unclear on:
1) why tftpd thinks IPv4 0.0.0.0:69 is already in use
2) how to best configure persistent interface names under sytemd and udev
Any guidance is greatly appreciated...
johnea
Last edited by android (2012-12-14 00:20:19)OK, I have it working. There were several things wrong:
1) The modified tftpd.service file was incorrect. The introduction of the '-l' flag, to run tftpd as a standalone service, not inetd driven, was preventing the socket based unit from working. The tftpd.service file below is working correctly with the stock tftpd.socket file provided with the tftp-hpa package. This file has modifications to make tftpd run only on the statically configured interface.
[Unit]
Description=hpa's original TFTP daemon on subnet interface sub0
Requires=network.target
After=network.target
[Service]
ExecStart=/usr/sbin/in.tftpd -a 10.20.30.1 -s /srv/tftp/
StandardInput=socket
StandardOutput=inherit
StandardError=journal
[Install]
WantedBy=multi-user.target
The "Requires=network.target" and "After=network.target" were necessary additions for restricting tftpd to one interface by it's IP address.
The "-a 10.20.30.1" argument specifies the interface to monitor.
2) The /etc/conf.d/network file had typos.
The statically configured interface uses the network.service file specified here:
https://wiki.archlinux.org/index.php/Tf … er#Systemd
However my /etc/conf.d/network file somehow managed to pick up spaces at the beginning of the lines after the first line. This prevented the network.service file from extracting the parameters.
I additionally modified the network.service file by commenting out the wpa_supplicant line, and the "ip route add" line, because this is a wired interface and it is a local subnet with no outbound gateway.
The netstat output was misleading me. Since the tftpd unit is socket driven, it does not show up as a listening socket on port 69 (this also kept it out of ps listings). I believe systemd had started tftpd.socket and was monitoring UDP port 69. This is why I was experiencing the "Address already in use" error on the tftpd.service file that specified the '-l' option.
The persistent interface names where established via a Udev rule, as specified here:
https://wiki.archlinux.org/index.php/Ud … ork_device
This led to custom interface names, which required the /etc/conf.d/network file, and other network config files be updated.
These steps led to a working tftpd service on one statically configured interface only.
The only remaining systemd issue to be resolved on this host is to restrict the dhcpcd client to the other interface only, but that's another post.
johnea -
I do keep hitting these little systemd issues, but google hasn't helped.
How do i boot a recovery console using a systemd only boot? I've tried both ro single and systemd.unit=rescue.target on the kernel command line, and whilst in both cases I can see the final message long enough to know that it's recovery mode, it then goes on before I have a chance to actually do anything to (I assume) continue trying to load my DM, resulting in a blank screen with nowhere to go and no way to get there. Obviously because it's now at run level 1 there are no TTYs available to switch to.
Is there a way to get something resembling the old behaviour with systemd where it will either drop to a console, or at the very least wait for me to make a choice?Sorry it's taken me a couple of days to come back to this, but my day job and experimenting have got in the way.
I copied sulogin in to /sbin and it made no difference at all, so on to step two, using initramfs, which is getting closer, particularly using the break point.
However, nothing here yet provides a true recovery system, which is what I long for. At the moment we are restricted to either a recovery system than will allow us to change system config files, or a chroot environment from a live boot that will let us modify the system generally, but nothing compares to init for system recovery where you can get both with a recovery boot.
For now, and since I already have a clonezilla ISO conigured in grub for boot, I may make a modified Arch ISO that I can boot to with the full chroot set up at login, but it would be far better to be able to boot the existing system to a recovery tty without the extraneous stuff starting. Surely rescue.service or emergency.service should stop all other *.services running, thus giving us a true recovery option. -
[SOLVED]Serious frustrations with MPD-Pulse and ncmpcpp
There are a couple of problems I'm having. First and foremost, I can't access any sort of flash video without mpd stopping and not working until a full system reboot, I've tried "sudo mpd --kill && sudo mpd --no-create-db" as well as "sudo /etc/rc.d/mpd restart" and they don't work. I've noticed several people with this problem while using alsa, I've tried normal mpd and tried some of the suggestions that I found for mpd.conf but to no avail and got the added bonus of play on startup which annoys me (mpd-pulse for whatever reason doesn't do that) so I was wondering if there exist any sort of work around for mpd-pulse or pulse in general (I'll take whatever).
Moving onto the more minor problem with ncmpcpp, there was an update today and upon installing I've noticed a serious decrease in speed, particularly when scrolling through the library and stumbling upon a certain artist that has a lot of albums/songs, but also when first playing a song after a system boot ncmpcpp will wait ~6 seconds before playing any sound (while the progress bar for the song is moving forward). The first issue is more important as I have several discographies and going from one end of my library to another is rather difficult at present, but the latter is still really annoying.
I'm mainly trying to see if any one has a suggestion for my mpd-pulse issues with flash, and I'm curious if the ncmpcpp things are something everyone is experiencing or if it's just me.
Thank you in advance,
--Wes
Last edited by Wesman26 (2010-06-19 03:52:55)About flash:
If I'm correct in saying that all audio is out after using flash in a browser, and nothing works until the browser is closed, then the problem is indeed OSS. Here's what you do: before starting any audio applications, (as root)
# rmmod snd-pcm-oss
# rmmod snd-mixer-oss
# rmmod snd-seq-oss
Add these into your /etc/rc.conf module list, with a ! before them (this blacklists them):
MODULES=( <...other modules...> !snd_pcm_oss !snd_seq_oss)
I found this thread because of ncmpcpp is gone really slow for me too. Gonna have to try this unix socket stuff. I don't really understand it if I'm honest B-) -
Setting up a LUKS partition to use a USB key
Im playing with an old netbook I've been given, essentially practicing for when I get a new desktop. Anyway, I want to install Arch on a LUKS encrypted partition and have it unlocked at boot time using a key located on a USB key.
This is what I did first time round and whilst the root partition is indeed encrypted I'm having to type a passphrase every boot:
loadkeys uk
lsblk
gdisk /dev/sda
outout should eventually look like:
Command (? for help): p
Disk /dev/sda:
Logical sector size: 512 bytes
Disk identifier (GUID):
Partition table holds up to 128 entries
First usable sector is 34, last usable sector is
Partitions will be aligned on 2048-sector boundaries
Total free space is 2014 sectors (1007.0 KiB)
Number Start (sector) End (sector) Size Code Name
1 2048 8191 3.0 MiB EF02 BIOS boot partition
2 8192 1032191 500.0 MiB 8300 boot
3 1032192 8300 root
cryptsetup -v --cipher aes-xts-plain64 --key-size 512 --hash sha512 --iter-time 5000 --use-random luksFormat /dev/sda3
enter a passphrase twice here
cryptsetup open /dev/sda3 ARCHROOT
mkfs.ext4 /dev/sda2
mkfs.btrfs /dev/mapper/ARCHROOT
mount /dev/mapper/ARCHROOT /mnt
cd /mnt
Would I need to
cryptsetup luksAddKey /path/to/keyfile
after the first cyptsetup step? If so can the live Arch environment mount USB drives at this point in the installation process?frostschutz wrote:Do you have a backup of those headers, then? Kinda sucks to lose all your data to a faulty USB key.
hehe, yes several USB keys and other secure storage.
frostschultz wrote:Security wise it shouldn't matter, if someone can modify my Initramfs, they can also modify my Grub.
The other thing I forgot to mention is that my USB stick is also my boot device. There's no Grub or any other bootloader on the target systems to mess with. If started without the key, they just say "operating system not found". Even if someone got hold of the USB stick, as a last line of defence, all the keys and headers that Grub needs (as well as the Grub boot config) is stored on an encrypted partition on the USB stick that requires a passphrase to unlock.
frostschultz wrote:
I can pull my USB stick as soon as Grub is done loading the kernel and initramfs, i.e. the moment kernel messages start to appear. They keys and all are part of the Initramfs, so the USB stick is no longer necessary.
Basically, it's this method: https://wiki.gentoo.org/wiki/Custom_Ini … ed_Keyfile and the first example here: https://wiki.gentoo.org/wiki/Custom_Initramfs/Examples
That gentoo example doesn't use systemd. I wanted to use the native systemd functionality as much as possible. My my initramfs opens what's necessary for boot (essentially the root filesystem) and the main early-boot does everything else. I wanted to use the standard /etc/fstab and /etc/crypttab and allow systemd to sort everything out but I encountered the dependency problem. I have a very simple workaround for it, however.
I'll just add to that as well that the systemd issue is only on systems where the initramfs is insecure and, therefore, cannot contain keys. Those systems with the initramfs on an encrypted filesystem don't need the usb key to unlock the rest of the encrypted filesystems because the keys are in the encrypted initramfs. They only need the USB key to unlock the root. I cannot secure the initramfs on some systems because of the way they boot (specifically, non-x86 boxes that cannot use Grub or are unable to boot off arbitrary devices).
Last edited by starfry (2015-02-07 14:09:29) -
Journalctl with no PID message for cups and avahi contemporary failure
I have facing a persistent problem with avahi-daemon and cups as systemd services. They have been enabled but fallen in a failed state as being started. Any investigation of the failures by journalctl (using _PID=) returned no useful info (log period only). Is there another way how to find why the services failed? A dependency between cups and avahi should be IMHO optional and recommended only for those using printers connected remotedly (or managable by users in cups.conf). I cannot identify wheather the failures are caused by systemd issue, some wrong config file or missing some needed file. Any idea? Thank you all.
Had similar issue with my HP Deskjet F4500C All in one printer, here's what I did:
make sure these packages are installed or install them
pacman -S cups cups-pdf hplip pyqt3 python2-pyqt
pacman -S system-config-printer-gnome
rc.d cups start
To add device and install hp driver:
1. Run ‘hp-setup’ as root.
2. Click ‘Show Advanced Options’ button and check-enable ‘Manual Discovery’.
3. Enter IP address 192.168.59.63 in the ‘…device ID…’ entry and click ‘Next’ to install driver.
run system-config-printer as root, to add printer
# system-config-printer
click “Add”， Select Device -> Network Printer -> input the IP address of the printer such as “192.168.1.3″, click “Find” -> “Process”
you should be ok from here, if not some further steps:
If you encounter the following error:
File “/usr/share/system-config-printer/newprinter.py”, line 1531, in getNetworkPrinterMakeModel
debugprint (host + “: ” + args)
TypeError: cannot concatenate ‘str’ and ‘list’ objects
You should comment out the error line at 1531 of newprinter.py, and then continue to add the printer.
4). Finally, you can run hp-check to see what problems exists for the printer. -
Hi!
After today's update, gdm crashes on my laptop (hp probook 6510s, intel graphic chipset). I'm using systemd, booted into single mode, started x, no problem, started gnome-session, it crashed. I've seen nothing suspicious on xterm. My home desktop machine doesn't have this problem, I updated and rebooted fine. Both machine has 64 bit arch installed.
Any clue?
Edit: It seems like a systemd issue on the laptop (the desktop machine uses initscripts), reverted back to initscripts on the laptop, and gdm runs fine.
Frankieboy
Last edited by frankieboy (2012-06-06 06:19:49)I have sthe same problem.
To have gdm running open, a terminal using control + alt + f1, even if gdm is not runnig well,
Then register as root or a user in the sudoers group and read the root processes with:
#ps -x
You may obtain a list of processes like:
# ps -x
warning: bad ps syntax, perhaps a bogus '-'?
See http://gitorious.org/procps/procps/blobs/master/Documentation/FAQ
PID TTY STAT TIME COMMAND
1 ? Ss 0:00 init [3]
2 ? S 0:00 [kthreadd]
3 ? S 0:00 [ksoftirqd/0]
5 ? S 0:00 [kworker/u:0]
6 ? S 0:00 [migration/0]
7 ? S 0:00 [watchdog/0]
8 ? S 0:00 [migration/1]
10 ? S 0:00 [ksoftirqd/1]
12 ? S 0:00 [watchdog/1]
13 ? S< 0:00 [cpuset]
14 ? S< 0:00 [khelper]
15 ? S 0:00 [kdevtmpfs]
16 ? S< 0:00 [netns]
17 ? S 0:00 [sync_supers]
18 ? S 0:00 [bdi-default]
19 ? S< 0:00 [kblockd]
20 ? S 0:00 [kworker/1:1]
21 ? S 0:00 [khungtaskd]
22 ? S 0:00 [kswapd0]
23 ? SN 0:00 [ksmd]
24 ? SN 0:00 [khugepaged]
25 ? S 0:00 [fsnotify_mark]
26 ? S< 0:00 [crypto]
29 ? S< 0:00 [kthrotld]
30 ? S 0:00 [kworker/1:2]
31 ? S< 0:00 [deferwq]
32 ? S 0:00 [kworker/u:1]
43 ? S< 0:00 [rpciod]
45 ? S< 0:00 [nfsiod]
68 ? S 0:00 [khubd]
69 ? S< 0:00 [ata_sff]
70 ? S 0:00 [scsi_eh_0]
71 ? S 0:00 [scsi_eh_1]
74 ? S 0:00 [scsi_eh_2]
75 ? S 0:00 [scsi_eh_3]
82 ? S 0:00 [scsi_eh_4]
83 ? S 0:00 [usb-storage]
89 ? S 0:00 [kworker/1:3]
90 ? S 0:00 [kworker/0:3]
94 ? S 0:00 [jbd2/sda6-8]
95 ? S< 0:00 [ext4-dio-unwrit]
101 ? S 0:00 [jbd2/sda8-8]
102 ? S< 0:00 [ext4-dio-unwrit]
230 ? Ss 0:00 /usr/lib/systemd/systemd-udevd --daemon
284 ? S< 0:00 [kpsmoused]
289 ? S< 0:00 [hd-audio0]
300 ? S 0:00 [flush-8:0]
337 ? S 0:00 [jbd2/sda7-8]
338 ? S< 0:00 [ext4-dio-unwrit]
340 ? S 0:00 [jbd2/sda5-8]
341 ? S< 0:00 [ext4-dio-unwrit]
342 ? S 0:00 [jbd2/sda10-8]
343 ? S< 0:00 [ext4-dio-unwrit]
427 ? S 0:00 supervising syslog-ng
428 ? Ss 0:00 /usr/sbin/syslog-ng
453 ? Ss 0:00 /usr/sbin/crond
528 ? Ss 0:00 /usr/sbin/httpd -k start
580 ? S 0:00 /usr/sbin/avahi-dnsconfd -D
611 ? Ssl 0:00 /usr/sbin/NetworkManager
638 ? Sl 0:00 /usr/lib/polkit-1/polkitd --no-debug
662 ? S 0:00 /sbin/dhcpcd -B -K -L -G -c /usr/lib/networkmanager/n
689 ? Ss 0:00 cupsd -C /etc/cups/cupsd.conf
745 ? Ss 0:00 /usr/bin/rpcbind
816 ? Ss 0:00 /usr/sbin/rpc.statd --no-notify
837 ? Ss 0:00 /usr/sbin/rpc.idmapd
891 ? S 0:00 /bin/sh /usr/bin/mysqld_safe --user=mysql
1196 ? Sl 0:00 /usr/lib/accountsservice/accounts-daemon
1205 ? Sl 0:00 /usr/sbin/console-kit-daemon --no-daemon
1292 ? Ss 0:00 login -- root
1293 tty2 Ss+ 0:00 /sbin/agetty -8 -s 38400 tty2 linux
1294 tty3 Ss+ 0:00 /sbin/agetty -8 -s 38400 tty3 linux
1295 tty4 Ss+ 0:00 /sbin/agetty -8 -s 38400 tty4 linux
1296 tty5 Ss+ 0:00 /sbin/agetty -8 -s 38400 tty5 linux
1297 tty6 Ss+ 0:00 /sbin/agetty -8 -s 38400 tty6 linux
1314 tty1 Ss+ 0:00 -bash
1377 tty1 Sl 0:00 /usr/sbin/gdm-binary
1441 tty1 Sl 0:00 /usr/lib/gdm/gdm-simple-slave --display-id /org/gnome
1445 tty8 Ss+ 0:35 /usr/bin/Xorg :0 -br -verbose -auth /var/run/gdm/auth
1490 ? Sl 0:00 /usr/lib/upower/upowerd
1591 tty1 Sl 0:00 gdm-session-worker [pam/gdm-password]
1718 ? Sl 0:00 /usr/lib/colord/colord
1736 ? Sl 0:00 /usr/lib/colord/colord-sane
1780 ? Sl 0:00 /usr/lib/udisks2/udisksd --no-debug
2091 ? S 0:00 [kworker/0:0]
2099 ? S 0:00 [kworker/1:5]
2116 ? S 0:00 [kworker/1:4]
2132 pts/0 S 0:00 su
2133 pts/0 S 0:00 bash
2141 ? S 0:00 [kworker/0:1]
2151 pts/0 R+ 0:00 ps -x
Then remove the gdm process associated with gdm-binary:
1377 tty1 Sl 0:00 /usr/sbin/gdm-binary
Using:
kill 1377
May be a process number like 703.
Then I go back to start gdm:
Then start GDM:
#gdm&
GDM run well achieving a graphical interface and access to gdm-binary.
I reisntalled gdm and see some warnings:
# pacman -S gdm
atención: gdm-3.4.1-2 está actualizado -- re-instalando
resolviendo dependencias...
verificando conflictos...
Objetivos (1): gdm-3.4.1-2
Tamaño instalado: 6,66 MiB
Tamaño a actualizar: 0,00 MiB
¿Continuar con la instalación? [S/n] s
(1/1) verificando la integridad de los paquetes [######################] 100%
(1/1) cargando los archivos del paquete... [######################] 100%
(1/1) verificando conflictos entre archivos [######################] 100%
(1/1) verificando el espacio disponible en disco [######################] 100%
(1/1) actualizando gdm [######################] 100%
atención: los permisos de directorio difieren en var/lib/gdm/.config/
sistema de archivos: 700 paquete: 755
atención: los permisos de directorio difieren en var/lib/gdm/.config/dconf/
sistema de archivos: 755 paquete: 700
Or:
attention: directory permissions differ on /var/lib/gdm/.config/
filesystem: 700 package: 755
attention: directory permissions differ on var /lib/gdm/.config/dconf/
filesystem: 755 package: 700
The problem persist with GDM reinstalled.
I do not see problem in Xorg. My /var/log/Xorg.0.log is the following:
# cat /var/log/Xorg.0.log
[ 153.247]
X.Org X Server 1.12.2
Release Date: 2012-05-29
[ 153.247] X Protocol Version 11, Revision 0
[ 153.247] Build Operating System: Linux 3.0.32-1-lts x86_64
[ 153.247] Current Operating System: Linux eaep1 3.4.4-3-ARCH #1 SMP PREEMPT Tue Jul 3 14:36:44 UTC 2012 x86_64
[ 153.247] Kernel command line: BOOT_IMAGE=/vmlinuz-linux root=/dev/sda6 ro quiet
[ 153.247] Build Date: 30 May 2012 07:24:13PM
[ 153.247]
[ 153.247] Current version of pixman: 0.26.2
[ 153.247] Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
[ 153.247] Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[ 153.247] (==) Log file: "/var/log/Xorg.0.log", Time: Sun Jul 8 19:05:55 2012
[ 153.247] (==) Using config directory: "/etc/X11/xorg.conf.d"
[ 153.247] (==) No Layout section. Using the first Screen section.
[ 153.247] (==) No screen section available. Using defaults.
[ 153.247] (**) |-->Screen "Default Screen Section" (0)
[ 153.247] (**) | |-->Monitor "<default monitor>"
[ 153.247] (==) No monitor specified for screen "Default Screen Section".
Using a default monitor configuration.
[ 153.247] (==) Automatically adding devices
[ 153.247] (==) Automatically enabling devices
[ 153.247] (==) FontPath set to:
/usr/share/fonts/misc/,
/usr/share/fonts/TTF/,
/usr/share/fonts/OTF/,
/usr/share/fonts/Type1/,
/usr/share/fonts/100dpi/,
/usr/share/fonts/75dpi/
[ 153.247] (==) ModulePath set to "/usr/lib/xorg/modules"
[ 153.247] (II) The server relies on udev to provide the list of input devices.
If no devices become available, reconfigure udev or disable AutoAddDevices.
[ 153.247] (II) Loader magic: 0x7c58e0
[ 153.247] (II) Module ABI versions:
[ 153.247] X.Org ANSI C Emulation: 0.4
[ 153.247] X.Org Video Driver: 12.0
[ 153.247] X.Org XInput driver : 16.0
[ 153.247] X.Org Server Extension : 6.0
[ 153.248] (--) PCI:*(0:0:2:0) 8086:2e32:1565:3103 rev 3, Mem @ 0xfe400000/4194304, 0xd0000000/268435456, I/O @ 0x0000dc00/8
[ 153.248] (WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory)
[ 153.248] (II) LoadModule: "extmod"
[ 153.248] (II) Loading /usr/lib/xorg/modules/extensions/libextmod.so
[ 153.248] (II) Module extmod: vendor="X.Org Foundation"
[ 153.248] compiled for 1.12.2, module version = 1.0.0
[ 153.248] Module class: X.Org Server Extension
[ 153.248] ABI class: X.Org Server Extension, version 6.0
[ 153.248] (II) Loading extension MIT-SCREEN-SAVER
[ 153.248] (II) Loading extension XFree86-VidModeExtension
[ 153.248] (II) Loading extension XFree86-DGA
[ 153.248] (II) Loading extension DPMS
[ 153.248] (II) Loading extension XVideo
[ 153.248] (II) Loading extension XVideo-MotionCompensation
[ 153.248] (II) Loading extension X-Resource
[ 153.248] (II) LoadModule: "dbe"
[ 153.248] (II) Loading /usr/lib/xorg/modules/extensions/libdbe.so
[ 153.248] (II) Module dbe: vendor="X.Org Foundation"
[ 153.248] compiled for 1.12.2, module version = 1.0.0
[ 153.248] Module class: X.Org Server Extension
[ 153.248] ABI class: X.Org Server Extension, version 6.0
[ 153.248] (II) Loading extension DOUBLE-BUFFER
[ 153.248] (II) LoadModule: "glx"
[ 153.249] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[ 153.249] (II) Module glx: vendor="X.Org Foundation"
[ 153.249] compiled for 1.12.2, module version = 1.0.0
[ 153.249] ABI class: X.Org Server Extension, version 6.0
[ 153.249] (==) AIGLX enabled
[ 153.249] (II) Loading extension GLX
[ 153.249] (II) LoadModule: "record"
[ 153.249] (II) Loading /usr/lib/xorg/modules/extensions/librecord.so
[ 153.249] (II) Module record: vendor="X.Org Foundation"
[ 153.249] compiled for 1.12.2, module version = 1.13.0
[ 153.249] Module class: X.Org Server Extension
[ 153.249] ABI class: X.Org Server Extension, version 6.0
[ 153.249] (II) Loading extension RECORD
[ 153.249] (II) LoadModule: "dri"
[ 153.249] (II) Loading /usr/lib/xorg/modules/extensions/libdri.so
[ 153.249] (II) Module dri: vendor="X.Org Foundation"
[ 153.249] compiled for 1.12.2, module version = 1.0.0
[ 153.249] ABI class: X.Org Server Extension, version 6.0
[ 153.249] (II) Loading extension XFree86-DRI
[ 153.249] (II) LoadModule: "dri2"
[ 153.249] (II) Loading /usr/lib/xorg/modules/extensions/libdri2.so
[ 153.249] (II) Module dri2: vendor="X.Org Foundation"
[ 153.249] compiled for 1.12.2, module version = 1.2.0
[ 153.249] ABI class: X.Org Server Extension, version 6.0
[ 153.249] (II) Loading extension DRI2
[ 153.249] (==) Matched intel as autoconfigured driver 0
[ 153.249] (==) Matched vesa as autoconfigured driver 1
[ 153.249] (==) Matched fbdev as autoconfigured driver 2
[ 153.249] (==) Assigned the driver to the xf86ConfigLayout
[ 153.249] (II) LoadModule: "intel"
[ 153.249] (II) Loading /usr/lib/xorg/modules/drivers/intel_drv.so
[ 153.250] (II) Module intel: vendor="X.Org Foundation"
[ 153.250] compiled for 1.12.2, module version = 2.19.0
[ 153.250] Module class: X.Org Video Driver
[ 153.250] ABI class: X.Org Video Driver, version 12.0
[ 153.250] (II) LoadModule: "vesa"
[ 153.250] (II) Loading /usr/lib/xorg/modules/drivers/vesa_drv.so
[ 153.250] (II) Module vesa: vendor="X.Org Foundation"
[ 153.250] compiled for 1.12.0, module version = 2.3.1
[ 153.250] Module class: X.Org Video Driver
[ 153.250] ABI class: X.Org Video Driver, version 12.0
[ 153.250] (II) LoadModule: "fbdev"
[ 153.250] (II) Loading /usr/lib/xorg/modules/drivers/fbdev_drv.so
[ 153.250] (II) Module fbdev: vendor="X.Org Foundation"
[ 153.250] compiled for 1.12.2, module version = 0.4.3
[ 153.250] Module class: X.Org Video Driver
[ 153.250] ABI class: X.Org Video Driver, version 12.0
[ 153.250] (II) intel: Driver for Intel Integrated Graphics Chipsets: i810,
i810-dc100, i810e, i815, i830M, 845G, 854, 852GM/855GM, 865G, 915G,
E7221 (i915), 915GM, 945G, 945GM, 945GME, Pineview GM, Pineview G,
965G, G35, 965Q, 946GZ, 965GM, 965GME/GLE, G33, Q35, Q33, GM45,
4 Series, G45/G43, Q45/Q43, G41, B43, B43, Clarkdale, Arrandale,
Sandybridge Desktop (GT1), Sandybridge Desktop (GT2),
Sandybridge Desktop (GT2+), Sandybridge Mobile (GT1),
Sandybridge Mobile (GT2), Sandybridge Mobile (GT2+),
Sandybridge Server, Ivybridge Mobile (GT1), Ivybridge Mobile (GT2),
Ivybridge Desktop (GT1), Ivybridge Desktop (GT2), Ivybridge Server,
Ivybridge Server (GT2)
[ 153.251] (II) VESA: driver for VESA chipsets: vesa
[ 153.251] (II) FBDEV: driver for framebuffer: fbdev
[ 153.251] (++) using VT number 8
[ 153.258] (WW) Falling back to old probe method for vesa
[ 153.258] (WW) Falling back to old probe method for fbdev
[ 153.259] (II) Loading sub module "fbdevhw"
[ 153.259] (II) LoadModule: "fbdevhw"
[ 153.259] (II) Loading /usr/lib/xorg/modules/libfbdevhw.so
[ 153.259] (II) Module fbdevhw: vendor="X.Org Foundation"
[ 153.259] compiled for 1.12.2, module version = 0.0.2
[ 153.259] ABI class: X.Org Video Driver, version 12.0
[ 153.259] drmOpenDevice: node name is /dev/dri/card0
[ 153.259] drmOpenDevice: open result is 8, (OK)
[ 153.259] drmOpenByBusid: Searching for BusID pci:0000:00:02.0
[ 153.259] drmOpenDevice: node name is /dev/dri/card0
[ 153.259] drmOpenDevice: open result is 8, (OK)
[ 153.259] drmOpenByBusid: drmOpenMinor returns 8
[ 153.259] drmOpenByBusid: drmGetBusid reports pci:0000:00:02.0
[ 153.259] (II) intel(0): Creating default Display subsection in Screen section
"Default Screen Section" for depth/fbbpp 24/32
[ 153.259] (==) intel(0): Depth 24, (--) framebuffer bpp 32
[ 153.259] (==) intel(0): RGB weight 888
[ 153.259] (==) intel(0): Default visual is TrueColor
[ 153.259] (II) intel(0): Integrated Graphics Chipset: Intel(R) G41
[ 153.259] (--) intel(0): Chipset: "G41"
[ 153.259] (**) intel(0): Relaxed fencing enabled
[ 153.259] (**) intel(0): Wait on SwapBuffers? enabled
[ 153.259] (**) intel(0): Triple buffering? enabled
[ 153.259] (**) intel(0): Framebuffer tiled
[ 153.259] (**) intel(0): Pixmaps tiled
[ 153.259] (**) intel(0): 3D buffers tiled
[ 153.259] (**) intel(0): SwapBuffers wait enabled
[ 153.259] (==) intel(0): video overlay key set to 0x101fe
[ 153.324] (II) intel(0): Output VGA1 has no monitor section
[ 153.391] (II) intel(0): EDID for output VGA1
[ 153.391] (II) intel(0): Manufacturer: HWP Model: 26a4 Serial#: 2147483648
[ 153.391] (II) intel(0): Year: 2009 Week: 11
[ 153.391] (II) intel(0): EDID Version: 1.3
[ 153.391] (II) intel(0): Analog Display Input, Input Voltage Level: 0.700/0.700 V
[ 153.391] (II) intel(0): Sync: Separate
[ 153.391] (II) intel(0): Max Image Size [cm]: horiz.: 41 vert.: 26
[ 153.391] (II) intel(0): Gamma: 2.20
[ 153.391] (II) intel(0): DPMS capabilities: Off; RGB/Color Display
[ 153.391] (II) intel(0): Default color space is primary color space
[ 153.391] (II) intel(0): First detailed timing is preferred mode
[ 153.391] (II) intel(0): redX: 0.640 redY: 0.329 greenX: 0.300 greenY: 0.600
[ 153.391] (II) intel(0): blueX: 0.150 blueY: 0.060 whiteX: 0.313 whiteY: 0.329
[ 153.391] (II) intel(0): Supported established timings:
[ 153.391] (II) intel(0): 720x400@70Hz
[ 153.391] (II) intel(0): 640x480@60Hz
[ 153.391] (II) intel(0): 640x480@75Hz
[ 153.391] (II) intel(0): 800x600@60Hz
[ 153.391] (II) intel(0): 800x600@75Hz
[ 153.391] (II) intel(0): 832x624@75Hz
[ 153.391] (II) intel(0): 1024x768@60Hz
[ 153.391] (II) intel(0): 1024x768@75Hz
[ 153.391] (II) intel(0): 1280x1024@75Hz
[ 153.391] (II) intel(0): 1152x864@75Hz
[ 153.391] (II) intel(0): Manufacturer's mask: 0
[ 153.391] (II) intel(0): Supported standard timings:
[ 153.391] (II) intel(0): #0: hsize: 1280 vsize 1024 refresh: 60 vid: 32897
[ 153.391] (II) intel(0): #1: hsize: 1152 vsize 720 refresh: 60 vid: 113
[ 153.391] (II) intel(0): #2: hsize: 1280 vsize 960 refresh: 60 vid: 16513
[ 153.391] (II) intel(0): #3: hsize: 1440 vsize 900 refresh: 60 vid: 149
[ 153.391] (II) intel(0): Supported detailed timing:
[ 153.391] (II) intel(0): clock: 106.5 MHz Image Size: 408 x 255 mm
[ 153.391] (II) intel(0): h_active: 1440 h_sync: 1520 h_sync_end 1672 h_blank_end 1904 h_border: 0
[ 153.391] (II) intel(0): v_active: 900 v_sync: 903 v_sync_end 909 v_blanking: 934 v_border: 0
[ 153.391] (II) intel(0): Ranges: V min: 50 V max: 76 Hz, H min: 24 H max: 83 kHz, PixClock max 145 MHz
[ 153.391] (II) intel(0): Monitor name: Compaq WF1907
[ 153.391] (II) intel(0): Serial No: CNC911PSDV
[ 153.391] (II) intel(0): EDID (in hex):
[ 153.391] (II) intel(0): 00ffffffffffff0022f0a42600000080
[ 153.391] (II) intel(0): 0b13010368291a782ede95a3544c9926
[ 153.391] (II) intel(0): 0f5054a56b8081807100814095000101
[ 153.391] (II) intel(0): 0101010101019a29a0d0518422305098
[ 153.391] (II) intel(0): 360098ff1000001c000000fd00324c18
[ 153.391] (II) intel(0): 530e000a202020202020000000fc0043
[ 153.391] (II) intel(0): 6f6d70617120574631393037000000ff
[ 153.391] (II) intel(0): 00434e43393131505344560a202000d6
[ 153.391] (II) intel(0): EDID vendor "HWP", prod id 9892
[ 153.391] (II) intel(0): Using EDID range info for horizontal sync
[ 153.391] (II) intel(0): Using EDID range info for vertical refresh
[ 153.391] (II) intel(0): Printing DDC gathered Modelines:
[ 153.391] (II) intel(0): Modeline "1440x900"x0.0 106.50 1440 1520 1672 1904 900 903 909 934 -hsync +vsync (55.9 kHz eP)
[ 153.391] (II) intel(0): Modeline "800x600"x0.0 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz e)
[ 153.391] (II) intel(0): Modeline "640x480"x0.0 31.50 640 656 720 840 480 481 484 500 -hsync -vsync (37.5 kHz e)
[ 153.391] (II) intel(0): Modeline "640x480"x0.0 25.18 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz e)
[ 153.391] (II) intel(0): Modeline "720x400"x0.0 28.32 720 738 846 900 400 412 414 449 -hsync +vsync (31.5 kHz e)
[ 153.391] (II) intel(0): Modeline "1280x1024"x0.0 135.00 1280 1296 1440 1688 1024 1025 1028 1066 +hsync +vsync (80.0 kHz e)
[ 153.391] (II) intel(0): Modeline "1024x768"x0.0 78.75 1024 1040 1136 1312 768 769 772 800 +hsync +vsync (60.0 kHz e)
[ 153.391] (II) intel(0): Modeline "1024x768"x0.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz e)
[ 153.391] (II) intel(0): Modeline "832x624"x0.0 57.28 832 864 928 1152 624 625 628 667 -hsync -vsync (49.7 kHz e)
[ 153.391] (II) intel(0): Modeline "800x600"x0.0 49.50 800 816 896 1056 600 601 604 625 +hsync +vsync (46.9 kHz e)
[ 153.391] (II) intel(0): Modeline "1152x864"x0.0 108.00 1152 1216 1344 1600 864 865 868 900 +hsync +vsync (67.5 kHz e)
[ 153.391] (II) intel(0): Modeline "1280x1024"x0.0 108.00 1280 1328 1440 1688 1024 1025 1028 1066 +hsync +vsync (64.0 kHz e)
[ 153.391] (II) intel(0): Modeline "1152x720"x60.0 67.32 1152 1208 1328 1504 720 721 724 746 -hsync +vsync (44.8 kHz e)
[ 153.391] (II) intel(0): Modeline "1280x960"x0.0 108.00 1280 1376 1488 1800 960 961 964 1000 +hsync +vsync (60.0 kHz e)
[ 153.391] (II) intel(0): Printing probed modes for output VGA1
[ 153.391] (II) intel(0): Modeline "1440x900"x59.9 106.50 1440 1520 1672 1904 900 903 909 934 -hsync +vsync (55.9 kHz eP)
[ 153.391] (II) intel(0): Modeline "1280x1024"x75.0 135.00 1280 1296 1440 1688 1024 1025 1028 1066 +hsync +vsync (80.0 kHz e)
[ 153.391] (II) intel(0): Modeline "1280x1024"x60.0 108.00 1280 1328 1440 1688 1024 1025 1028 1066 +hsync +vsync (64.0 kHz e)
[ 153.391] (II) intel(0): Modeline "1280x960"x60.0 108.00 1280 1376 1488 1800 960 961 964 1000 +hsync +vsync (60.0 kHz e)
[ 153.392] (II) intel(0): Modeline "1152x864"x75.0 108.00 1152 1216 1344 1600 864 865 868 900 +hsync +vsync (67.5 kHz e)
[ 153.392] (II) intel(0): Modeline "1152x720"x60.0 67.28 1152 1208 1328 1504 720 721 724 746 -hsync +vsync (44.7 kHz)
[ 153.392] (II) intel(0): Modeline "1024x768"x75.1 78.80 1024 1040 1136 1312 768 769 772 800 +hsync +vsync (60.1 kHz e)
[ 153.392] (II) intel(0): Modeline "1024x768"x60.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz e)
[ 153.392] (II) intel(0): Modeline "832x624"x74.6 57.28 832 864 928 1152 624 625 628 667 -hsync -vsync (49.7 kHz e)
[ 153.392] (II) intel(0): Modeline "800x600"x75.0 49.50 800 816 896 1056 600 601 604 625 +hsync +vsync (46.9 kHz e)
[ 153.392] (II) intel(0): Modeline "800x600"x60.3 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz e)
[ 153.392] (II) intel(0): Modeline "640x480"x75.0 31.50 640 656 720 840 480 481 484 500 -hsync -vsync (37.5 kHz e)
[ 153.392] (II) intel(0): Modeline "640x480"x60.0 25.20 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz e)
[ 153.392] (II) intel(0): Modeline "720x400"x70.1 28.32 720 738 846 900 400 412 414 449 -hsync +vsync (31.5 kHz e)
[ 153.392] (II) intel(0): Output VGA1 connected
[ 153.392] (II) intel(0): Using exact sizes for initial modes
[ 153.392] (II) intel(0): Output VGA1 using initial mode 1440x900
[ 153.392] (II) intel(0): Using default gamma of (1.0, 1.0, 1.0) unless otherwise stated.
[ 153.392] (II) intel(0): Kernel page flipping support detected, enabling
[ 153.392] (**) intel(0): Display dimensions: (410, 260) mm
[ 153.392] (**) intel(0): DPI set to (89, 87)
[ 153.392] (II) Loading sub module "fb"
[ 153.392] (II) LoadModule: "fb"
[ 153.392] (II) Loading /usr/lib/xorg/modules/libfb.so
[ 153.392] (II) Module fb: vendor="X.Org Foundation"
[ 153.392] compiled for 1.12.2, module version = 1.0.0
[ 153.392] ABI class: X.Org ANSI C Emulation, version 0.4
[ 153.392] (II) Loading sub module "dri2"
[ 153.392] (II) LoadModule: "dri2"
[ 153.392] (II) Loading /usr/lib/xorg/modules/extensions/libdri2.so
[ 153.392] (II) Module dri2: vendor="X.Org Foundation"
[ 153.392] compiled for 1.12.2, module version = 1.2.0
[ 153.392] ABI class: X.Org Server Extension, version 6.0
[ 153.392] (II) UnloadModule: "vesa"
[ 153.392] (II) Unloading vesa
[ 153.392] (II) UnloadModule: "fbdev"
[ 153.392] (II) Unloading fbdev
[ 153.392] (II) UnloadSubModule: "fbdevhw"
[ 153.392] (II) Unloading fbdevhw
[ 153.392] (==) Depth 24 pixmap format is 32 bpp
[ 153.392] (II) intel(0): [DRI2] Setup complete
[ 153.392] (II) intel(0): [DRI2] DRI driver: i965
[ 153.392] (II) intel(0): Allocated new frame buffer 1472x900 stride 6144, tiled
[ 153.402] (II) UXA(0): Driver registered support for the following operations:
[ 153.402] (II) solid
[ 153.402] (II) copy
[ 153.402] (II) composite (RENDER acceleration)
[ 153.402] (II) put_image
[ 153.402] (II) get_image
[ 153.402] (==) intel(0): Backing store disabled
[ 153.402] (==) intel(0): Silken mouse enabled
[ 153.402] (II) intel(0): Initializing HW Cursor
[ 153.402] (II) intel(0): RandR 1.2 enabled, ignore the following RandR disabled message.
[ 153.402] (==) intel(0): DPMS enabled
[ 153.402] (==) intel(0): Intel XvMC decoder enabled
[ 153.402] (II) intel(0): Set up textured video
[ 153.402] (II) intel(0): [XvMC] xvmc_vld driver initialized.
[ 153.402] (II) intel(0): direct rendering: DRI2 Enabled
[ 153.402] (==) intel(0): hotplug detection: "enabled"
[ 153.426] (--) RandR disabled
[ 153.426] (II) Initializing built-in extension Generic Event Extension
[ 153.426] (II) Initializing built-in extension SHAPE
[ 153.426] (II) Initializing built-in extension MIT-SHM
[ 153.426] (II) Initializing built-in extension XInputExtension
[ 153.426] (II) Initializing built-in extension XTEST
[ 153.426] (II) Initializing built-in extension BIG-REQUESTS
[ 153.426] (II) Initializing built-in extension SYNC
[ 153.426] (II) Initializing built-in extension XKEYBOARD
[ 153.426] (II) Initializing built-in extension XC-MISC
[ 153.426] (II) Initializing built-in extension SECURITY
[ 153.426] (II) Initializing built-in extension XINERAMA
[ 153.426] (II) Initializing built-in extension XFIXES
[ 153.426] (II) Initializing built-in extension RENDER
[ 153.426] (II) Initializing built-in extension RANDR
[ 153.426] (II) Initializing built-in extension COMPOSITE
[ 153.426] (II) Initializing built-in extension DAMAGE
[ 153.439] (II) AIGLX: enabled GLX_MESA_copy_sub_buffer
[ 153.439] (II) AIGLX: enabled GLX_INTEL_swap_event
[ 153.439] (II) AIGLX: enabled GLX_SGI_swap_control and GLX_MESA_swap_control
[ 153.439] (II) AIGLX: GLX_EXT_texture_from_pixmap backed by buffer objects
[ 153.439] (II) AIGLX: Loaded and initialized i965
[ 153.439] (II) GLX: Initialized DRI2 GL provider for screen 0
[ 153.439] (II) intel(0): Setting screen physical size to 381 x 238
[ 153.531] (II) config/udev: Adding input device Power Button (/dev/input/event2)
[ 153.531] (**) Power Button: Applying InputClass "evdev keyboard catchall"
[ 153.531] (**) Power Button: Applying InputClass "Keyboard Defaults"
[ 153.531] (II) LoadModule: "evdev"
[ 153.531] (II) Loading /usr/lib/xorg/modules/input/evdev_drv.so
[ 153.531] (II) Module evdev: vendor="X.Org Foundation"
[ 153.531] compiled for 1.12.0, module version = 2.7.0
[ 153.531] Module class: X.Org XInput Driver
[ 153.531] ABI class: X.Org XInput driver, version 16.0
[ 153.531] (II) Using input driver 'evdev' for 'Power Button'
[ 153.531] (**) Power Button: always reports core events
[ 153.531] (**) evdev: Power Button: Device: "/dev/input/event2"
[ 153.531] (--) evdev: Power Button: Vendor 0 Product 0x1
[ 153.531] (--) evdev: Power Button: Found keys
[ 153.531] (II) evdev: Power Button: Configuring as keyboard
[ 153.531] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXPWRBN:00/input/input2/event2"
[ 153.531] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 6)
[ 153.531] (**) Option "xkb_rules" "evdev"
[ 153.531] (**) Option "xkb_model" "microsoftinet"
[ 153.531] (**) Option "xkb_layout" "latam"
[ 153.531] (**) Option "xkb_variant" "deadtilde"
[ 153.554] (II) config/udev: Adding input device Power Button (/dev/input/event1)
[ 153.554] (**) Power Button: Applying InputClass "evdev keyboard catchall"
[ 153.554] (**) Power Button: Applying InputClass "Keyboard Defaults"
[ 153.554] (II) Using input driver 'evdev' for 'Power Button'
[ 153.554] (**) Power Button: always reports core events
[ 153.554] (**) evdev: Power Button: Device: "/dev/input/event1"
[ 153.554] (--) evdev: Power Button: Vendor 0 Product 0x1
[ 153.554] (--) evdev: Power Button: Found keys
[ 153.554] (II) evdev: Power Button: Configuring as keyboard
[ 153.554] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/device:00/PNP0C0C:00/input/input1/event1"
[ 153.554] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 7)
[ 153.554] (**) Option "xkb_rules" "evdev"
[ 153.554] (**) Option "xkb_model" "microsoftinet"
[ 153.554] (**) Option "xkb_layout" "latam"
[ 153.554] (**) Option "xkb_variant" "deadtilde"
[ 153.554] (II) config/udev: Adding input device HDA Intel Line (/dev/input/event5)
[ 153.554] (II) No input driver specified, ignoring this device.
[ 153.554] (II) This device may have been added with another device file.
[ 153.554] (II) config/udev: Adding input device HDA Intel Front Mic (/dev/input/event6)
[ 153.554] (II) No input driver specified, ignoring this device.
[ 153.554] (II) This device may have been added with another device file.
[ 153.555] (II) config/udev: Adding input device HDA Intel Rear Mic (/dev/input/event7)
[ 153.555] (II) No input driver specified, ignoring this device.
[ 153.555] (II) This device may have been added with another device file.
[ 153.555] (II) config/udev: Adding input device HDA Intel Front Headphone (/dev/input/event8)
[ 153.555] (II) No input driver specified, ignoring this device.
[ 153.555] (II) This device may have been added with another device file.
[ 153.555] (II) config/udev: Adding input device HDA Intel Line Out (/dev/input/event9)
[ 153.555] (II) No input driver specified, ignoring this device.
[ 153.555] (II) This device may have been added with another device file.
[ 153.555] (II) config/udev: Adding input device AT Translated Set 2 keyboard (/dev/input/event0)
[ 153.555] (**) AT Translated Set 2 keyboard: Applying InputClass "evdev keyboard catchall"
[ 153.555] (**) AT Translated Set 2 keyboard: Applying InputClass "Keyboard Defaults"
[ 153.555] (II) Using input driver 'evdev' for 'AT Translated Set 2 keyboard'
[ 153.555] (**) AT Translated Set 2 keyboard: always reports core events
[ 153.555] (**) evdev: AT Translated Set 2 keyboard: Device: "/dev/input/event0"
[ 153.555] (--) evdev: AT Translated Set 2 keyboard: Vendor 0x1 Product 0x1
[ 153.555] (--) evdev: AT Translated Set 2 keyboard: Found keys
[ 153.556] (II) evdev: AT Translated Set 2 keyboard: Configuring as keyboard
[ 153.556] (**) Option "config_info" "udev:/sys/devices/platform/i8042/serio0/input/input0/event0"
[ 153.556] (II) XINPUT: Adding extended input device "AT Translated Set 2 keyboard" (type: KEYBOARD, id 8)
[ 153.556] (**) Option "xkb_rules" "evdev"
[ 153.556] (**) Option "xkb_model" "microsoftinet"
[ 153.556] (**) Option "xkb_layout" "latam"
[ 153.556] (**) Option "xkb_variant" "deadtilde"
[ 153.556] (II) config/udev: Adding input device ImPS/2 Generic Wheel Mouse (/dev/input/event4)
[ 153.556] (**) ImPS/2 Generic Wheel Mouse: Applying InputClass "evdev pointer catchall"
[ 153.556] (II) Using input driver 'evdev' for 'ImPS/2 Generic Wheel Mouse'
[ 153.556] (**) ImPS/2 Generic Wheel Mouse: always reports core events
[ 153.556] (**) evdev: ImPS/2 Generic Wheel Mouse: Device: "/dev/input/event4"
[ 153.556] (--) evdev: ImPS/2 Generic Wheel Mouse: Vendor 0x2 Product 0x5
[ 153.556] (--) evdev: ImPS/2 Generic Wheel Mouse: Found 3 mouse buttons
[ 153.556] (--) evdev: ImPS/2 Generic Wheel Mouse: Found scroll wheel(s)
[ 153.556] (--) evdev: ImPS/2 Generic Wheel Mouse: Found relative axes
[ 153.556] (--) evdev: ImPS/2 Generic Wheel Mouse: Found x and y relative axes
[ 153.556] (II) evdev: ImPS/2 Generic Wheel Mouse: Configuring as mouse
[ 153.556] (II) evdev: ImPS/2 Generic Wheel Mouse: Adding scrollwheel support
[ 153.556] (**) evdev: ImPS/2 Generic Wheel Mouse: YAxisMapping: buttons 4 and 5
[ 153.556] (**) evdev: ImPS/2 Generic Wheel Mouse: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
[ 153.556] (**) Option "config_info" "udev:/sys/devices/platform/i8042/serio1/input/input4/event4"
[ 153.556] (II) XINPUT: Adding extended input device "ImPS/2 Generic Wheel Mouse" (type: MOUSE, id 9)
[ 153.556] (II) evdev: ImPS/2 Generic Wheel Mouse: initialized for relative axes.
[ 153.557] (**) ImPS/2 Generic Wheel Mouse: (accel) keeping acceleration scheme 1
[ 153.557] (**) ImPS/2 Generic Wheel Mouse: (accel) acceleration profile 0
[ 153.557] (**) ImPS/2 Generic Wheel Mouse: (accel) acceleration factor: 2.000
[ 153.557] (**) ImPS/2 Generic Wheel Mouse: (accel) acceleration threshold: 4
[ 153.557] (II) config/udev: Adding input device ImPS/2 Generic Wheel Mouse (/dev/input/mouse0)
[ 153.557] (II) No input driver specified, ignoring this device.
[ 153.557] (II) This device may have been added with another device file.
[ 153.557] (II) config/udev: Adding input device PC Speaker (/dev/input/event3)
[ 153.557] (II) No input driver specified, ignoring this device.
[ 153.557] (II) This device may have been added with another device file.
[ 153.621] (II) intel(0): EDID vendor "HWP", prod id 9892
[ 153.621] (II) intel(0): Using hsync ranges from config file
[ 153.621] (II) intel(0): Using vrefresh ranges from config file
[ 153.621] (II) intel(0): Printing DDC gathered Modelines:
[ 153.621] (II) intel(0): Modeline "1440x900"x0.0 106.50 1440 1520 1672 1904 900 903 909 934 -hsync +vsync (55.9 kHz eP)
[ 153.621] (II) intel(0): Modeline "800x600"x0.0 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz e)
[ 153.621] (II) intel(0): Modeline "640x480"x0.0 31.50 640 656 720 840 480 481 484 500 -hsync -vsync (37.5 kHz e)
[ 153.621] (II) intel(0): Modeline "640x480"x0.0 25.18 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz e)
[ 153.621] (II) intel(0): Modeline "720x400"x0.0 28.32 720 738 846 900 400 412 414 449 -hsync +vsync (31.5 kHz e)
[ 153.621] (II) intel(0): Modeline "1280x1024"x0.0 135.00 1280 1296 1440 1688 1024 1025 1028 1066 +hsync +vsync (80.0 kHz e)
[ 153.621] (II) intel(0): Modeline "1024x768"x0.0 78.75 1024 1040 1136 1312 768 769 772 800 +hsync +vsync (60.0 kHz e)
[ 153.621] (II) intel(0): Modeline "1024x768"x0.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz e)
[ 153.621] (II) intel(0): Modeline "832x624"x0.0 57.28 832 864 928 1152 624 625 628 667 -hsync -vsync (49.7 kHz e)
[ 153.621] (II) intel(0): Modeline "800x600"x0.0 49.50 800 816 896 1056 600 601 604 625 +hsync +vsync (46.9 kHz e)
[ 153.621] (II) intel(0): Modeline "1152x864"x0.0 108.00 1152 1216 1344 1600 864 865 868 900 +hsync +vsync (67.5 kHz e)
[ 153.621] (II) intel(0): Modeline "1280x1024"x0.0 108.00 1280 1328 1440 1688 1024 1025 1028 1066 +hsync +vsync (64.0 kHz e)
[ 153.621] (II) intel(0): Modeline "1152x720"x60.0 67.32 1152 1208 1328 1504 720 721 724 746 -hsync +vsync (44.8 kHz e)
[ 153.621] (II) intel(0): Modeline "1280x960"x0.0 108.00 1280 1376 1488 1800 960 961 964 1000 +hsync +vsync (60.0 kHz e)
[ 157.318] (II) intel(0): EDID vendor "HWP", prod id 9892
[ 157.318] (II) intel(0): Using hsync ranges from config file
[ 157.318] (II) intel(0): Using vrefresh ranges from config file
[ 157.318] (II) intel(0): Printing DDC gathered Modelines:
[ 157.318] (II) intel(0): Modeline "1440x900"x0.0 106.50 1440 1520 1672 1904 900 903 909 934 -hsync +vsync (55.9 kHz eP)
[ 157.318] (II) intel(0): Modeline "800x600"x0.0 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz e)
[ 157.318] (II) intel(0): Modeline "640x480"x0.0 31.50 640 656 720 840 480 481 484 500 -hsync -vsync (37.5 kHz e)
[ 157.318] (II) intel(0): Modeline "640x480"x0.0 25.18 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz e)
[ 157.318] (II) intel(0): Modeline "720x400"x0.0 28.32 720 738 846 900 400 412 414 449 -hsync +vsync (31.5 kHz e)
[ 157.318] (II) intel(0): Modeline "1280x1024"x0.0 135.00 1280 1296 1440 1688 1024 1025 1028 1066 +hsync +vsync (80.0 kHz e)
[ 157.318] (II) intel(0): Modeline "1024x768"x0.0 78.75 1024 1040 1136 1312 768 769 772 800 +hsync +vsync (60.0 kHz e)
[ 157.318] (II) intel(0): Modeline "1024x768"x0.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz e)
[ 157.318] (II) intel(0): Modeline "832x624"x0.0 57.28 832 864 928 1152 624 625 628 667 -hsync -vsync (49.7 kHz e)
[ 157.318] (II) intel(0): Modeline "800x600"x0.0 49.50 800 816 896 1056 600 601 604 625 +hsync +vsync (46.9 kHz e)
[ 157.318] (II) intel(0): Modeline "1152x864"x0.0 108.00 1152 1216 1344 1600 864 865 868 900 +hsync +vsync (67.5 kHz e)
[ 157.318] (II) intel(0): Modeline "1280x1024"x0.0 108.00 1280 1328 1440 1688 1024 1025 1028 1066 +hsync +vsync (64.0 kHz e)
[ 157.318] (II) intel(0): Modeline "1152x720"x60.0 67.32 1152 1208 1328 1504 720 721 724 746 -hsync +vsync (44.8 kHz e)
[ 157.318] (II) intel(0): Modeline "1280x960"x0.0 108.00 1280 1376 1488 1800 960 961 964 1000 +hsync +vsync (60.0 kHz e)
[ 181.823] (II) intel(0): EDID vendor "HWP", prod id 9892
[ 181.823] (II) intel(0): Using hsync ranges from config file
[ 181.823] (II) intel(0): Using vrefresh ranges from config file
[ 181.823] (II) intel(0): Printing DDC gathered Modelines:
[ 181.823] (II) intel(0): Modeline "1440x900"x0.0 106.50 1440 1520 1672 1904 900 903 909 934 -hsync +vsync (55.9 kHz eP)
[ 181.823] (II) intel(0): Modeline "800x600"x0.0 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz e)
[ 181.823] (II) intel(0): Modeline "640x480"x0.0 31.50 640 656 720 840 480 481 484 500 -hsync -vsync (37.5 kHz e)
[ 181.823] (II) intel(0): Modeline "640x480"x0.0 25.18 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz e)
[ 181.823] (II) intel(0): Modeline "720x400"x0.0 28.32 720 738 846 900 400 412 414 449 -hsync +vsync (31.5 kHz e)
[ 181.823] (II) intel(0): Modeline "1280x1024"x0.0 135.00 1280 1296 1440 1688 1024 1025 1028 1066 +hsync +vsync (80.0 kHz e)
[ 181.823] (II) intel(0): Modeline "1024x768"x0.0 78.75 1024 1040 1136 1312 768 769 772 800 +hsync +vsync (60.0 kHz e)
[ 181.823] (II) intel(0): Modeline "1024x768"x0.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz e)
[ 181.823] (II) intel(0): Modeline "832x624"x0.0 57.28 832 864 928 1152 624 625 628 667 -hsync -vsync (49.7 kHz e)
[ 181.823] (II) intel(0): Modeline "800x600"x0.0 49.50 800 816 896 1056 600 601 604 625 +hsync +vsync (46.9 kHz e)
[ 181.823] (II) intel(0): Modeline "1152x864"x0.0 108.00 1152 1216 1344 1600 864 865 868 900 +hsync +vsync (67.5 kHz e)
[ 181.823] (II) intel(0): Modeline "1280x1024"x0.0 108.00 1280 1328 1440 1688 1024 1025 1028 1066 +hsync +vsync (64.0 kHz e)
[ 181.823] (II) intel(0): Modeline "1152x720"x60.0 67.32 1152 1208 1328 1504 720 721 724 746 -hsync +vsync (44.8 kHz e)
[ 181.823] (II) intel(0): Modeline "1280x960"x0.0 108.00 1280 1376 1488 1800 960 961 964 1000 +hsync +vsync (60.0 kHz e)
[ 183.021] (II) intel(0): EDID vendor "HWP", prod id 9892
[ 183.021] (II) intel(0): Using hsync ranges from config file
[ 183.021] (II) intel(0): Using vrefresh ranges from config file
[ 183.021] (II) intel(0): Printing DDC gathered Modelines:
[ 183.021] (II) intel(0): Modeline "1440x900"x0.0 106.50 1440 1520 1672 1904 900 903 909 934 -hsync +vsync (55.9 kHz eP)
[ 183.021] (II) intel(0): Modeline "800x600"x0.0 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz e)
[ 183.021] (II) intel(0): Modeline "640x480"x0.0 31.50 640 656 720 840 480 481 484 500 -hsync -vsync (37.5 kHz e)
[ 183.021] (II) intel(0): Modeline "640x480"x0.0 25.18 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz e)
[ 183.021] (II) intel(0): Modeline "720x400"x0.0 28.32 720 738 846 900 400 412 414 449 -hsync +vsync (31.5 kHz e)
[ 183.021] (II) intel(0): Modeline "1280x1024"x0.0 135.00 1280 1296 1440 1688 1024 1025 1028 1066 +hsync +vsync (80.0 kHz e)
[ 183.021] (II) intel(0): Modeline "1024x768"x0.0 78.75 1024 1040 1136 1312 768 769 772 800 +hsync +vsync (60.0 kHz e)
[ 183.021] (II) intel(0): Modeline "1024x768"x0.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz e)
[ 183.021] (II) intel(0): Modeline "832x624"x0.0 57.28 832 864 928 1152 624 625 628 667 -hsync -vsync (49.7 kHz e)
[ 183.021] (II) intel(0): Modeline "800x600"x0.0 49.50 800 816 896 1056 600 601 604 625 +hsync +vsync (46.9 kHz e)
[ 183.021] (II) intel(0): Modeline "1152x864"x0.0 108.00 1152 1216 1344 1600 864 865 868 900 +hsync +vsync (67.5 kHz e)
[ 183.021] (II) intel(0): Modeline "1280x1024"x0.0 108.00 1280 1328 1440 1688 1024 1025 1028 1066 +hsync +vsync (64.0 kHz e)
[ 183.021] (II) intel(0): Modeline "1152x720"x60.0 67.32 1152 1208 1328 1504 720 721 724 746 -hsync +vsync (44.8 kHz e)
[ 183.021] (II) intel(0): Modeline "1280x960"x0.0 108.00 1280 1376 1488 1800 960 961 964 1000 +hsync +vsync (60.0 kHz e)
[ 183.357] (II) intel(0): EDID vendor "HWP", prod id 9892
[ 183.357] (II) intel(0): Using hsync ranges from config file
[ 183.357] (II) intel(0): Using vrefresh ranges from config file
[ 183.357] (II) intel(0): Printing DDC gathered Modelines:
[ 183.357] (II) intel(0): Modeline "1440x900"x0.0 106.50 1440 1520 1672 1904 900 903 909 934 -hsync +vsync (55.9 kHz eP)
[ 183.357] (II) intel(0): Modeline "800x600"x0.0 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz e)
[ 183.357] (II) intel(0): Modeline "640x480"x0.0 31.50 640 656 720 840 480 481 484 500 -hsync -vsync (37.5 kHz e)
[ 183.357] (II) intel(0): Modeline "640x480"x0.0 25.18 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz e)
[ 183.357] (II) intel(0): Modeline "720x400"x0.0 28.32 720 738 846 900 400 412 414 449 -hsync +vsync (31.5 kHz e)
[ 183.357] (II) intel(0): Modeline "1280x1024"x0.0 135.00 1280 1296 1440 1688 1024 1025 1028 1066 +hsync +vsync (80.0 kHz e)
[ 183.357] (II) intel(0): Modeline "1024x768"x0.0 78.75 1024 1040 1136 1312 768 769 772 800 +hsync +vsync (60.0 kHz e)
[ 183.357] (II) intel(0): Modeline "1024x768"x0.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz e)
[ 183.357] (II) intel(0): Modeline "832x624"x0.0 57.28 832 864 928 1152 624 625 628 667 -hsync -vsync (49.7 kHz e)
[ 183.358] (II) intel(0): Modeline "800x600"x0.0 49.50 800 816 896 1056 600 601 604 625 +hsync +vsync (46.9 kHz e)
[ 183.358] (II) intel(0): Modeline "1152x864"x0.0 108.00 1152 1216 1344 1600 864 865 868 900 +hsync +vsync (67.5 kHz e)
[ 183.358] (II) intel(0): Modeline "1280x1024"x0.0 108.00 1280 1328 1440 1688 1024 1025 1028 1066 +hsync +vsync (64.0 kHz e)
[ 183.358] (II) intel(0): Modeline "1152x720"x60.0 67.32 1152 1208 1328 1504 720 721 724 746 -hsync +vsync (44.8 kHz e)
[ 183.358] (II) intel(0): Modeline "1280x960"x0.0 108.00 1280 1376 1488 1800 960 961 964 1000 +hsync +vsync (60.0 kHz e)
[ 2580.900] (II) AIGLX: Suspending AIGLX clients for VT switch
[ 2586.252] (II) AIGLX: Resuming AIGLX clients after VT switch
[ 2586.330] (II) intel(0): EDID vendor "HWP", prod id 9892
[ 2586.330] (II) intel(0): Using hsync ranges from config file
[ 2586.331] (II) intel(0): Using vrefresh ranges from config file
[ 2586.331] (II) intel(0): Printing DDC gathered Modelines:
[ 2586.331] (II) intel(0): Modeline "1440x900"x0.0 106.50 1440 1520 1672 1904 900 903 909 934 -hsync +vsync (55.9 kHz eP)
[ 2586.331] (II) intel(0): Modeline "800x600"x0.0 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz e)
[ 2586.331] (II) intel(0): Modeline "640x480"x0.0 31.50 640 656 720 840 480 481 484 500 -hsync -vsync (37.5 kHz e)
[ 2586.331] (II) intel(0): Modeline "640x480"x0.0 25.18 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz e)
[ 2586.331] (II) intel(0): Modeline "720x400"x0.0 28.32 720 738 846 900 400 412 414 449 -hsync +vsync (31.5 kHz e)
[ 2586.331] (II) intel(0): Modeline "1280x1024"x0.0 135.00 1280 1296 1440 1688 1024 1025 1028 1066 +hsync +vsync (80.0 kHz e)
[ 2586.331] (II) intel(0): Modeline "1024x768"x0.0 78.75 1024 1040 1136 1312 768 769 772 800 +hsync +vsync (60.0 kHz e)
[ 2586.331] (II) intel(0): Modeline "1024x768"x0.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz e)
[ 2586.331] (II) intel(0): Modeline "832x624"x0.0 57.28 832 864 928 1152 624 625 628 667 -hsync -vsync (49.7 kHz e)
[ 2586.331] (II) intel(0): Modeline "800x600"x0.0 49.50 800 816 896 1056 600 601 604 625 +hsync +vsync (46.9 kHz e)
[ 2586.331] (II) intel(0): Modeline "1152x864"x0.0 108.00 1152 1216 1344 1600 864 865 868 900 +hsync +vsync (67.5 kHz e)
[ 2586.331] (II) intel(0): Modeline "1280x1024"x0.0 108.00 1280 1328 1440 1688 1024 1025 1028 1066 +hsync +vsync (64.0 kHz e)
[ 2586.331] (II) intel(0): Modeline "1152x720"x60.0 67.32 1152 1208 1328 1504 720 721 724 746 -hsync +vsync (44.8 kHz e)
[ 2586.331] (II) intel(0): Modeline "1280x960"x0.0 108.00 1280 1376 1488 1800 960 961 964 1000 +hsync +vsync (60.0 kHz e)
Must be another cause of GDM do not work when turn on my computer.
Last edited by eaep (2012-07-09 01:05:51)
Maybe you are looking for
-
Invoking a WS from BPEL - WS URL is hardcoded in the WSDL
I have published a PL/SQL package as a webservice and deployed it successfully to a development instance (say DEV). I created a BPEL process and used a Partner Link to invoke the above web service. When I deploy the BPEL process to the DEV instance,
-
Need help getting rid of Safari popups on Macbook air.
Yesterday I chose to download some kind of program that was supposed to let me download content on a certain website - when I was getting ready to install the program there was a selection bubble I didn't see until the last second that said i would a
-
Creation of Repair Order (SD with reference to a Service Notification
Hi, I hv a requirment to create a Repair Order(Sales Order) with reference to a Service Notification when a Purchase Order arrives via EDI / interfaces using CIP2SAP ( EXITS OR BADI ). Pls suggest, if there are any user exit(s) to meet this requirem
-
Video output settings same as iMovie?
Hi Everyone, I've made my first real FCE movie - but when I output it using File, Export, Using Quicktime conversion, Size = PAL 720x576 16:9, I get a file size about 10 times bigger than the equivalent file I'd get from iMovie. It looks great - just
-
Does The Apple USB Modem Work With The Mac mini ??????
Just wanted to know if anyone has successfully used the new Apple USB Modem with the Mac mini, is it compatable ???? Thank you for your input on this. Mike D.