Gentoo Archives: gentoo-amd64

From: Mark Knecht <markknecht@×××××.com>
To: gentoo-amd64@l.g.o
Subject: Re: [gentoo-amd64] Lost ability to log in graphically
Date: Tue, 09 Feb 2010 15:15:37
Message-Id: 5bdc1c8b1002090715g775e3517uc73df5df191b6e92@mail.gmail.com
In Reply to: [gentoo-amd64] Lost ability to log in graphically by Jim Seymour
1 On Tue, Feb 9, 2010 at 6:46 AM, Jim Seymour <in2birds@×××××.com> wrote:
2 > Hi,
3 >
4 > About three weeks ago my kde desktop started to get distorted and slow reacting. I decided to go ahead and reboot the computer. That was the last time I have been logged in graphically. I have since removed KDE and the nvidia-drivers and am now just trying to get it working with the nv drivers and xdm/twm. I do get a log in screen, however upon trying to log in the screen goes blank and eventually comes back to the login screen. Since I seem to be the only one having this issue, I assume I missed an important entry in the elog. I have the modeline (no X at all without a xorg.conf) set to the parameters parsed by the video driver. I am using evdev for the keyboard and mouse (they work fine). I have googled and searched the mail archives to see if anyone else has had the same issue recently and how it was resolved. For the past three weeks I have come up empty. There are no EE entries in the Xorg.0.log at this point. I am running the stable version amd64
5 >  that is completely up to date package wise. The hardware does not seem to be the issue as a gentoo live dvd works perfectly. Any ideas on how I can get this working again? The only worthwhile errors I can find is in the xdm.log are below. This is with a clean xdm.log, reboot, login attempt and then killing X with ctrl_alt_bkspc.
6 >
7 > XIO:  fatal IO error 11 (Resource temporarily unavailable) on X server ":0.0"
8 >       after 167 requests (167 known processed) with 0 events remaining.
9 > (EE) XKB: No components provided for device Virtual core keyboard
10 > xdm error (pid 5477): fatal IO error 11 (Resource temporarily unavailable)
11 > XIO:  fatal IO error 11 (Resource temporarily unavailable) on X server ":0.0"
12 >       after 167 requests (167 known processed) with 0 events remaining.
13 > error setting MTRR (base = 0xb0000000, size = 0x10000000, type = 1) Invalid argument (22)
14 > XIO:  fatal IO error 11 (Resource temporarily unavailable) on X server ":0.0"
15 >       after 167 requests (167 known processed) with 0 events remaining.
16 > xdm error (pid 5496): fatal IO error 11 (Resource temporarily unavailable)
17 > xdm error (pid 4814): Server crash rate too high: removing display :0
18 > error setting MTRR (base = 0xb0000000, size = 0x10000000, type = 1) Invalid argument (22)
19 >
20 > Thanks for any help,
21 > Jim
22
23 Weird report.
24
25 You might try booting with DRM debugging turned on and looking at
26 dmesg to see what's going on. I presume that you have a second machine
27 that you can shell in on.
28
29 To turn on debug in grub.conf do something like this, of course
30 dropping the modeset part if you don't need it:
31
32
33
34 title 2.6.32-gentoo-r2 MS=1, DRM=0x06
35 root (hd0,6)
36 kernel (hd0,6)/boot/bzImage-2.6.32-gentoo-r2 root=/dev/sda2
37 i915.modeset=1 drm.debug=0x06
38
39
40
41 This will create a lot of output in dmesg so you may not want to run
42 with it long term, but it's helped me find a few things over the last
43 couple of weeks.
44
45 Hope this helps,
46 Mark