1 |
Dale wrote: |
2 |
> forgottenwizard wrote: |
3 |
>> I'm having a problem getting X to work. It is seg faulting on me, and |
4 |
>> despite countless revdep-rebuilds and emerge -e world, it still doesn't |
5 |
>> work. |
6 |
>> |
7 |
>> It dies after the cursor shows up, spitting this backtrace and output. |
8 |
>> Sorry if the formatting sucks. The last line is probably refering to the |
9 |
>> fact I tried to run it from within screen, so if that could cause a |
10 |
>> problem say so, and tell me how the heck to get a log of this output |
11 |
>> (since startx > log.txt doesn't work) |
12 |
>> |
13 |
>> #--- startx output ---# |
14 |
>> |
15 |
>> X Window System Version 1.3.0 |
16 |
>> Release Date: 19 April 2007 |
17 |
>> X Protocol Version 11, Revision 0, Release 1.3 |
18 |
>> Build Operating System: UNKNOWN |
19 |
>> Current Operating System: Linux localhost 2.6.25-gentoo-r7 #1 SMP |
20 |
>> PREEMPT Fri Aug 1 21:56:38 CDT 2008 x86_64 |
21 |
>> Build Date: 22 July 2008 |
22 |
>> Before reporting problems, check http://wiki.x.org |
23 |
>> to make sure that you have the latest version. |
24 |
>> Module Loader present |
25 |
>> Markers: (--) probed, (**) from config file, (==) |
26 |
>> default setting, |
27 |
>> (++) from command line, (!!) notice, (II) |
28 |
>> informational, |
29 |
>> (WW) warning, (EE) error, (NI) not |
30 |
>> implemented, (??) unknown. |
31 |
>> (==) Log file: "/var/log/Xorg.0.log", |
32 |
>> Time: Wed Aug 20 00:11:37 2008 |
33 |
>> (==) Using config file: |
34 |
>> "/etc/X11/xorg.conf" |
35 |
>> (WW) NVIDIA: No matching Device section |
36 |
>> for instance (BusID PCI:0:1:3) found |
37 |
>> (II) Module already built-in |
38 |
>> The XKEYBOARD keymap compiler (xkbcomp) |
39 |
>> reports: |
40 |
>> > Warning: Multiple names for |
41 |
>> > keycode 211 |
42 |
>> > Using <I211>, |
43 |
>> > ignoring <AB11> |
44 |
>> Errors from xkbcomp are not fatal to the |
45 |
>> X server |
46 |
>> Backtrace: |
47 |
>> 0: X(xf86SigHandler+0x6d) [0x49690d] |
48 |
>> 1: /lib/libc.so.6 [0x7fae2c0a4430] |
49 |
>> 2: X(NumMotionEvents+0x12) [0x447822] |
50 |
>> 3: X(CreateConnectionBlock+0x53) [0x439623] |
51 |
>> 4: X(main+0x658) [0x43a168] |
52 |
>> 5: /lib/libc.so.6(__libc_start_main+0xf4) [0x7fae2c091b74] |
53 |
>> 6: X(FontFileCompleteXLFD+0x229) [0x439259] |
54 |
>> |
55 |
>> Fatal server error: |
56 |
>> Caught signal 11. Server aborting |
57 |
>> |
58 |
>> waiting for X server to begin accepting connections |
59 |
>> giving up. |
60 |
>> xinit: Connection reset by peer (errno 104): unable to connect to X |
61 |
>> server |
62 |
>> xinit: No such process (errno 3): Server error. |
63 |
>> Couldnt get a file descriptor referring to the console |
64 |
>> |
65 |
>> #--- end ---# |
66 |
>> |
67 |
>> I've brought this to #x (or xorg, whichever the X support channel in |
68 |
>> freenode is), #linux, #gentoo, and the forums. I'm at a bit of a loss as |
69 |
>> to what the problem is, or how to go about trying to find out what is |
70 |
>> the problem. |
71 |
>> |
72 |
>> |
73 |
> |
74 |
> If I read this correctly, it appears that it can not find the keyboard |
75 |
> or something. This is what makes me think that: "The XKEYBOARD |
76 |
> keymap compiler (xkbcomp) reports: > Warning: Multiple names for > |
77 |
> keycode 211". |
78 |
> |
79 |
> In your make.conf, do you have a line that is something like this: |
80 |
> |
81 |
> INPUT_DEVICES="keyboard mouse" |
82 |
> |
83 |
> Also make sure you have something like the following in your xorg.conf |
84 |
> file: |
85 |
> |
86 |
> Section "InputDevice" |
87 |
> Identifier "Keyboard0" |
88 |
> Driver "kbd" |
89 |
> EndSection |
90 |
> |
91 |
> Section "InputDevice" |
92 |
> Identifier "Mouse0" |
93 |
> Driver "mouse" |
94 |
> Option "Protocol" "auto" |
95 |
> Option "Device" "/dev/input/mouse0" |
96 |
> Option "ZAxisMapping" "4 5 6 7" |
97 |
> EndSection |
98 |
> |
99 |
> This may not have anything to do with the problem but it is something |
100 |
> that didn't look right to me. |
101 |
> |
102 |
> Dale |
103 |
> |
104 |
> :-) :-) |
105 |
|
106 |
Nah, that's not the problem, aas you can see here; "Errors from xkbcomp |
107 |
are not fatal to the X server" |
108 |
|
109 |
/ Daniel. |