You are not logged in.

#1 2012-08-18 12:22:49

Jindur
Member
Registered: 2011-09-29
Posts: 184

[SOLVED] X hangs for 20-30s on login / blank screen in console on boot

This is a new thing and didn't happen before, but I don't know after which "pacman -Syu" this started to happen exactly:
After I enter my crecedentials in Slim and X starts up it will hang at the "grey" blank screen for like 20-30s until the desktop finally appears and the apps are loaded etc.

Last edited by Jindur (2012-08-21 20:51:05)

Offline

#2 2012-08-18 12:40:36

bernarcher
Forum Fellow
From: Germany
Registered: 2009-02-17
Posts: 2,281

Re: [SOLVED] X hangs for 20-30s on login / blank screen in console on boot

Anything in the logs?


To know or not to know ...
... the questions remain forever.

Offline

#3 2012-08-18 16:43:11

Jindur
Member
Registered: 2011-09-29
Posts: 184

Re: [SOLVED] X hangs for 20-30s on login / blank screen in console on boot

Hm what logs would I be looking into for that? And what would I actually be looking for?

Offline

#4 2012-08-18 22:37:26

ConnorBehan
Package Maintainer (PM)
From: Long Island NY
Registered: 2007-07-05
Posts: 1,359
Website

Re: [SOLVED] X hangs for 20-30s on login / blank screen in console on boot

.xsession-errors and /var/log/Xorg.0.log for starters. If too many strange processes start, this could also slow things down. Look at the "ps -e" output to search for these.


6EA3 F3F3 B908 2632 A9CB E931 D53A 0445 B47A 0DAB
Great things come in tar.xz packages.

Offline

#5 2012-08-19 08:39:43

Jindur
Member
Registered: 2011-09-29
Posts: 184

Re: [SOLVED] X hangs for 20-30s on login / blank screen in console on boot

Thanks, here are the results:
No file '.xsession-errors' in my home folder, only '.xsession', so I take it that means there were no errors?
I copied all WW, EE, NI and ?? entries from Xorg.0.log:

[    26.108] (WW) The directory "/usr/share/fonts/OTF/" does not exist.
[    26.108]    Entry deleted from font path.
[    26.188] (WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory)
[    26.672] (WW) Falling back to old probe method for vesa
[    26.672] (WW) Falling back to old probe method for fbdev

(So there were no EE,NI,?? entries.)
ps doesn't show any odd processes except the normal ones that have always been there.

  PID TTY          TIME CMD
    1 ?        00:00:17 init
    2 ?        00:00:00 kthreadd
    3 ?        00:00:37 ksoftirqd/0
    5 ?        00:00:01 kworker/u:0
    6 ?        00:00:00 migration/0
    7 ?        00:00:00 watchdog/0
    8 ?        00:00:00 migration/1
   10 ?        00:00:35 ksoftirqd/1
   12 ?        00:00:00 watchdog/1
   13 ?        00:00:00 cpuset
   14 ?        00:00:00 khelper
   15 ?        00:00:00 kdevtmpfs
   16 ?        00:00:00 netns
   17 ?        00:00:00 sync_supers
   18 ?        00:00:00 bdi-default
   19 ?        00:00:00 kblockd
   21 ?        00:00:00 khungtaskd
   22 ?        00:00:02 kswapd0
   23 ?        00:00:00 ksmd
   24 ?        00:00:16 khugepaged
   25 ?        00:00:00 fsnotify_mark
   26 ?        00:00:00 crypto
   29 ?        00:00:00 kthrotld
   31 ?        00:00:00 deferwq
   32 ?        00:00:03 kworker/u:1
   65 ?        00:00:00 khubd
   66 ?        00:00:00 ata_sff
   67 ?        00:00:00 scsi_eh_0
   68 ?        00:00:00 scsi_eh_1
   81 ?        00:00:00 jbd2/sda1-8
   82 ?        00:00:00 ext4-dio-unwrit
   90 ?        00:00:05 flush-8:0
  125 ?        00:00:00 systemd-udevd
  184 ?        00:00:00 tifm
  185 ?        00:00:00 kpsmoused
  187 ?        00:00:00 hd-audio0
  194 ?        00:00:00 firewire
  199 ?        00:00:00 pccardd
  296 ?        00:00:05 jbd2/sda2-8
  297 ?        00:00:00 ext4-dio-unwrit
  380 ?        00:00:00 syslog-ng
  381 ?        00:00:00 syslog-ng
  406 ?        00:00:04 dbus-daemon
  433 ?        00:00:00 osspd
  518 ?        00:00:00 crond
  524 tty1     00:00:00 agetty
  525 tty2     00:00:00 agetty
  526 tty3     00:00:00 agetty
  527 tty4     00:00:00 agetty
  528 tty5     00:00:00 agetty
  529 tty6     00:00:00 agetty
  530 ?        00:00:01 slim
  535 tty7     03:53:11 X
  542 ?        00:00:00 console-kit-dae
  609 ?        00:00:00 polkitd
  619 ?        00:00:00 sh
  630 ?        00:00:00 dbus-launch
  631 ?        00:00:19 dbus-daemon
  637 ?        00:00:16 xfce4-session
  639 ?        00:00:00 xfconfd
  642 ?        00:00:06 gpg-agent
  643 ?        00:25:49 xfwm4
  645 ?        00:01:27 Thunar
  647 ?        00:00:00 gvfsd
  649 ?        00:00:00 gvfs-fuse-daemo
  656 ?        00:01:57 xfce4-panel
  658 ?        00:00:01 gvfs-udisks2-vo
  661 ?        00:00:52 udisksd
  662 ?        00:00:12 xfdesktop
  663 ?        00:00:14 xfsettingsd
  668 ?        00:01:14 pidgin
  669 ?        02:57:35 firefox
  673 ?        00:00:16 xfce4-power-man
  680 ?        00:00:00 gvfsd-trash
  684 ?        00:00:14 upowerd
  686 ?        00:00:00 gvfsd-network
  694 ?        00:00:01 xfce4-mixer-plu
  702 ?        00:00:01 xfce4-brightnes
  725 ?        00:07:24 panel-16-weathe
  729 ?        00:00:00 gvfsd-dnssd
  734 ?        00:00:03 panel-6-systray
  735 ?        00:00:02 panel-2-actions
  740 ?        00:00:03 panel-18-thunar
  747 ?        00:01:08 dropbox
  750 ?        00:01:17 guake
  754 ?        00:00:11 devilspie
  759 ?        00:00:00 Thunar
  764 ?        00:00:01 polkit-gnome-au
  804 ?        00:00:29 xfce4-mixer
  806 ?        00:00:03 xfce4-mixer
  808 ?        00:16:18 terminal
  820 ?        00:00:00 gconfd-2
  844 ?        00:08:18 conky
  857 ?        00:00:00 gnome-pty-helpe
  858 pts/0    00:00:00 bash
  863 ?        00:00:00 gnome-pty-helpe
  864 pts/1    00:00:00 bash
  872 pts/2    00:00:00 bash
  878 pts/3    00:00:00 bash
  897 pts/4    00:00:00 bash
  902 pts/5    00:00:00 bash
 1056 pts/5    00:00:02 mc
 1058 pts/8    00:00:00 bash
 1159 pts/2    00:00:39 irssi
 2323 pts/3    00:00:03 ssh
 2328 pts/1    00:00:00 bash
 2329 pts/1    00:00:00 mc
 2331 pts/6    00:00:00 bash
 4033 ?        00:09:34 scdaemon
17770 ?        00:00:15 kworker/1:1
22899 pts/0    00:01:54 mc
22901 pts/11   00:00:03 bash
24059 ?        00:00:02 kworker/0:1
24254 ?        00:00:00 kworker/1:0
24882 ?        00:00:02 kworker/0:2
25693 ?        00:00:00 kworker/0:0
25901 ?        00:00:00 kworker/1:2
25977 ?        00:00:00 scdaemon <defunct>
25979 pts/11   00:00:00 ps
26240 ?        00:00:00 gvfsd-metadata
27875 ?        00:00:00 gvfsd-http
30563 ?        00:00:00 dconf-service

..where I'm not sure why there's "scdaemon <defunct>" in there actually. It seems ok that there's an 'scdaemon' process I think though? But why is it <defunct> I wonder.

Last edited by Jindur (2012-08-19 08:40:07)

Offline

#6 2012-08-19 10:57:48

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

Re: [SOLVED] X hangs for 20-30s on login / blank screen in console on boot

Does the same thing happen if you don't use SLiM?

Comment it out from /etc/inittab, use "id:3:initdefault:" for booting into runlevel 3, and use "startx" after logging in from the console.

(you should probably have a LiveCD near you before trying this, just in case)


"How to Succeed with Linux"

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

Offline

#7 2012-08-20 20:22:30

Jindur
Member
Registered: 2011-09-29
Posts: 184

Re: [SOLVED] X hangs for 20-30s on login / blank screen in console on boot

Oh I really needed a livecd.. because after the 5 text lines were done (last one being "processing udev events") and Slim would usually start (if not in init 3), the screen turned blank and the whole thing just hung. Waited 2 minutes, then reset it.

Here is my inittab at that moment:

#
# /etc/inittab
#

#  Runlevels:
#    0    Halt
#    1(S)	Single-user
#    2    Not used
#    3    Multi-user
#    4    Not used
#    5    X11
#    6    Reboot

## Only one of the following two lines can be uncommented!
# Boot to console
id:3:initdefault:
# Boot to X11
#id:5:initdefault:

rc::sysinit:/etc/rc.sysinit
rs:S1:wait:/etc/rc.single
rm:2345:wait:/etc/rc.multi
rh:06:wait:/etc/rc.shutdown
su:S:wait:/sbin/sulogin -p

# -8 options fixes umlauts problem on login
c1:2345:respawn:/sbin/agetty -8 -s 38400 tty1 linux
c2:2345:respawn:/sbin/agetty -8 -s 38400 tty2 linux
c3:2345:respawn:/sbin/agetty -8 -s 38400 tty3 linux
c4:2345:respawn:/sbin/agetty -8 -s 38400 tty4 linux
c5:2345:respawn:/sbin/agetty -8 -s 38400 tty5 linux
c6:2345:respawn:/sbin/agetty -8 -s 38400 tty6 linux

# Serial Virtual Console for KVM and others VMs
#s0:2345:respawn:/sbin/agetty -8 -s 9600 ttyS0 linux

# Hypervisor Virtual Console for Xen and KVM
#h0:2345:respawn:/sbin/agetty -8 -s 38400 hvc0 linux

ca::ctrlaltdel:/sbin/shutdown -t3 -r now

# Example lines for starting a login manager
#x:5:respawn:/usr/bin/xdm -nodaemon
#x:5:respawn:/usr/bin/kdm -nodaemon
#x:5:respawn:/usr/sbin/lightdm >& /dev/null
#x:5:respawn:/usr/sbin/gdm -nodaemon
x:5:respawn:/usr/bin/slim >/dev/null 2>&1
#x:5:respawn:/usr/sbin/lxdm >& /dev/null

# End of file

Last edited by Jindur (2012-08-20 20:22:49)

Offline

#8 2012-08-20 20:58:45

ConnorBehan
Package Maintainer (PM)
From: Long Island NY
Registered: 2007-07-05
Posts: 1,359
Website

Re: [SOLVED] X hangs for 20-30s on login / blank screen in console on boot

Ok, .xsession-errors is a file created by some login managers but not slim. It is equivalent to the manual command

startx > .xsession-errors

. Also defunct processes or zombie processes should be safe to kill.

I see messages about vesa and fbdev. Those aren't the drivers you're using, are they?


6EA3 F3F3 B908 2632 A9CB E931 D53A 0445 B47A 0DAB
Great things come in tar.xz packages.

Offline

#9 2012-08-20 22:41:10

Jindur
Member
Registered: 2011-09-29
Posts: 184

Re: [SOLVED] X hangs for 20-30s on login / blank screen in console on boot

I've got an Intel GMA950, I didn't really configure/add/remove specific drivers, it was working automatically right from when I installed Archlinux, so I don't know if the system loads Vesa/fbdev "just for fun" or not.

Offline

#10 2012-08-21 07:03:38

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

Re: [SOLVED] X hangs for 20-30s on login / blank screen in console on boot


"How to Succeed with Linux"

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

Offline

#11 2012-08-21 08:39:35

Jindur
Member
Registered: 2011-09-29
Posts: 184

Re: [SOLVED] X hangs for 20-30s on login / blank screen in console on boot

I skipped the parts of the page (https://wiki.archlinux.org/index.php/Intel) that are only for X, since as I described in previous posting, my system now freezes at boot apparently even if I boot into console (init 3).
So here's what I did:
-verified that boot config doesn't contain 'vga' or 'nomodeset'
-added 'i915' and (just to be on the safe side) 'intel_agp' to mkinitcpio.conf modules
-did 'sudo mkinitcpio -p linux'

<rebooted>
well, I didn't notice any delay (without HDD activity) when starting X this time. However, I noticed this: Right after I picked "Arch" normal boot from GRUB menu, the screen apparently switched to the "high resolution" allowed by KMS thanks to the i915 driver, if I understood that right? However, now from this point until X started (with the exception of Slim popping up in between) the screen stayed all the time blank and didn't show any of the usual linux startup messages a la "processing udev events... [DONE]" etc. So I assume something is still wrong..

-added "video=SVIDEO-1:d" to kernel
<rebooted>
Now both works: 1) init 3 gives me console and 2) the boot process is completely visible.
Thanks, I wouldn't have guessed that it was a graphics driver issue, seemed too basic ^^

However, still I get these in Xorg.0.log:

[    25.166] (WW) The directory "/usr/share/fonts/OTF/" does not exist.
[    25.166]    Entry deleted from font path.
[    25.207] (WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory)
[    25.579] (WW) Falling back to old probe method for vesa
[    25.580] (WW) Falling back to old probe method for fbdev

Same warnings as in the beginning, so those weren't really the cause of anything I guess? (They aren't mentioned in the Wiki's intel driver page either.)

I just rebooted with Slim into init 5 -> X, and it took 70 seconds, which is pretty long. I believe that it's the longest time I waited for X to start up ever, but since the HDD was working nearly all the time I guess it's not a "delay" but ok. Maybe I'm just remembering it differently, but I kno when I just started X from console boot manually it only took like 40s.

Last edited by Jindur (2012-08-21 09:13:25)

Offline

Board footer

Powered by FluxBB