1 |
Duncan wrote: |
2 |
> "Mark Haney" <mhaney@××××××××××××.org> posted |
3 |
> 49B20B46.4070309@××××××××××××.org, excerpted below, on Sat, 07 Mar 2009 |
4 |
> 00:51:02 -0500: |
5 |
> |
6 |
> |
7 |
>> Well I upgraded my xorg-server from 1.3.0 to 1.5.3 (masked) in order to |
8 |
>> overcome some of the KDE4.2 blocks I was encountering (for some |
9 |
>> particular kde4.2 package, which escapes me for the moment. |
10 |
>> |
11 |
>> So I ungraded, updated my ati driver (I use the radeon driver not one |
12 |
>> from ATI) and now my X server won't start. It says 'X server died on |
13 |
>> start up' and 'Can't start display on 0:0' or something similar, I'm |
14 |
>> writing this on the same box from a different OS. What next? How do I |
15 |
>> fix this? |
16 |
>> |
17 |
> |
18 |
> I don't believe 1.5.3 is masked, only ~arch. Unless that's what you |
19 |
> meant by masked... Now xorg-server-1.6.0, if it were in the tree (it's |
20 |
> in the xorg overlay not the tree at this point), would be masked, as |
21 |
> there are still some issues with it, including that some of its |
22 |
> dependencies don't have sufficient released versions yet, it requires git- |
23 |
> live builds for some of them. |
24 |
> |
25 |
> There were a LOT of changes in the way things worked between 1.3.x and |
26 |
> 1.5.x. I STRONGLY suspect that your xorg.conf file simply isn't |
27 |
> configured correctly for the newer version, thus X dies when you try to |
28 |
> start it. |
29 |
> |
30 |
> What input drivers are you using? It /may/ be as simple as adding the |
31 |
> following line to the ServerFlags section (you may use "false" or "off" |
32 |
> instead of "0" if you prefer): |
33 |
> |
34 |
> Option "AllowEmptyInput" "0" |
35 |
> |
36 |
> The reason is that xorg now ignores the xorg.conf configured input |
37 |
> drivers and tries to hotplug them (using hal) if you don't tell it not |
38 |
> to. Except, the hotplug will try to use the newer evdev driver which you |
39 |
> may not have the INPUT_DEVICES setup for, instead of the older keyboard |
40 |
> and mouse drivers which you likely have installed and configured in |
41 |
> xorg.conf, if you are updating from a suitably old xorg configuration. |
42 |
> |
43 |
> Now, if your keyboard and mouse settings are vanilla enough, you can |
44 |
> switch to the evdev driver and just let xorg-server hotplug it, no |
45 |
> problem. However, if you have something other than a generic 102-key (or |
46 |
> whatever) keyboard or a standard mouse, the evdev driver will need |
47 |
> additional configuration or you'll lose that additional functionality and |
48 |
> just have the generic functionality. The problem is that the hal |
49 |
> hotplugging configuration isn't all that clearly documented yet, |
50 |
> especially for all the permutations of hardware special features out |
51 |
> there, so it may be difficult actually finding instructions for doing |
52 |
> that configuration if you need it. |
53 |
> |
54 |
> The other option, easier if you already had a working configuration using |
55 |
> the existing keyboard and mouse (or other inputdev) drivers, and just |
56 |
> want it to work like it did before, is to put the line above in the |
57 |
> serverflags section of xorg.conf, so it actually honors the xorg.conf |
58 |
> input device configuration. |
59 |
> |
60 |
> The other thing that may have changed, depending on what version of |
61 |
> xf86-video-ati you are running, is that the newer configuration (from |
62 |
> version 6.8 at least, 6.6 was still the old way) is all RandR based. For |
63 |
> a normal single-monitor system, it should still work with little problem, |
64 |
> but for a dual-monitor or more system, again, there's configuration |
65 |
> changes you'll need to work thru. This is the part that was hardest for |
66 |
> me, since I effectively punted on figuring out the inputdev stuff by |
67 |
> simply adding the line above in the appropriate place. |
68 |
> |
69 |
> But that's rather more complex. If the above added line doesn't fix it, |
70 |
> post your Xorg.0.log, xorg.conf, and the output of an |
71 |
> emerge --pretend --verbose xorg-server xf86-video-ati xf86-input-<driver> |
72 |
> (whichever ones you use). |
73 |
> |
74 |
> Meanwhile, all these changes are to make it ideally "just work", for most |
75 |
> people. Most people will have all the various drivers already installed |
76 |
> or available, and xorg-server and hal are normally able to detect which |
77 |
> drivers are needed and configure them appropriately -- provided nothing |
78 |
> goes wrong and the hardware isn't too exotic. If you have the evdev |
79 |
> driver available already, are content with a generic keyboard and mouse |
80 |
> setup, and either don't have multiple monitors or aren't too particular |
81 |
> about what orientation and resolution they end up in, it's quite possible |
82 |
> you can run without an xorg.conf entirely, now. |
83 |
> |
84 |
> |
85 |
Well, here's an update on this problem. I didn't get a chance to work |
86 |
on it at all yesterday since I wanted to spend time with the kids. |
87 |
|
88 |
So, here's the deal. Duncan, I added that option to the 'ServerFlags' |
89 |
section and it made no difference at all. In dmesg I get ''X server |
90 |
died during startup' 'X server for display :0 cannot be started, session |
91 |
disabled' |
92 |
|
93 |
I had been running 1.3.x without an xorg.conf file for a couple months |
94 |
now without trouble. The above message happens both with and without an |
95 |
xorg.conf file. So, what I'm going todo right now is recompile all the |
96 |
X11 drivers and see if that helps. |
97 |
|
98 |
|
99 |
-- |
100 |
Mark Haney |
101 |
mhaney@××××××××××××.org |
102 |
Fedora release 9 (Sulphur) |
103 |
Kernel: 2.6.27.9-73.fc9.i686 GNU/Linux |
104 |
|
105 |
06:48:33 up 11 days, 11:54, 2 users, load average: 0.28, 0.18, 0.11 |