1 |
On Fri, May 22, 2009 at 17:46, Mark Knecht <markknecht@×××××.com> wrote: |
2 |
> On Fri, May 22, 2009 at 12:54 PM, Alan McKinnon <alan.mckinnon@×××××.com> wrote: |
3 |
>> On Friday 22 May 2009 21:19:40 Mark Knecht wrote: |
4 |
>>> On Fri, May 22, 2009 at 12:08 PM, Matt Harrison |
5 |
>>> |
6 |
>>> <iwasinnamuknow@×××××××××.com> wrote: |
7 |
>>> > Mark Knecht wrote: |
8 |
>>> >> On Fri, May 22, 2009 at 11:49 AM, bn <brullonulla@×××××.com> wrote: |
9 |
>>> >>> Mark Knecht ha scritto: |
10 |
>>> >>>> Title sort of says it. I have an old machine that I'm setting up as a |
11 |
>>> >>>> Myth server. I didn't want X on the machine but I'm having trouble so |
12 |
>>> >>>> I emerged xdm and start it using /etc/init.d/xdm start. The drivers |
13 |
>>> >>>> get loaded but I get a black screen. No error message in the X log |
14 |
>>> >>>> file. |
15 |
>>> >>>> |
16 |
>>> >>>> I haven't messed with X at this level before. What's the minimum test |
17 |
>>> >>>> of X that would display a terminal or something very basic? |
18 |
>>> >>> |
19 |
>>> >>> Have you tried |
20 |
>>> >>> |
21 |
>>> >>> startx /usr/bin/xterm |
22 |
>>> >> |
23 |
>>> >> Yes. Same black screen. Nothing else going on. The processes show up |
24 |
>>> >> in ps aux, X as root, xterm as me. |
25 |
>>> > |
26 |
>>> > I've found before that if everything seems to be running (can list X |
27 |
>>> > processes and logs look fine) but you still don't see anything, it's |
28 |
>>> > possible it is your monitor. I used to use a really old 15" CRT for a |
29 |
>>> > server but it just wouldn't run X at anything over 640x480. Modern |
30 |
>>> > monitors will at least tell you if the resolution/refresh is out of |
31 |
>>> > limits, but older ones don't often. Try with a different monitor if that |
32 |
>>> > one is old or suspect. |
33 |
>>> > |
34 |
>>> > ~Matt |
35 |
>>> |
36 |
>>> Good point. I'll hook the machine up to a very good monitor later today. |
37 |
>>> Thanks. |
38 |
>> |
39 |
>> You need to run an X-server, not the one that is displaying xdm because that |
40 |
>> will only run xdm and once you authenticate will launch an entirely different |
41 |
>> session. Either launch the failsafe session, it gives you twm on gentoo with a |
42 |
>> single xterm, or ditch xdm and run startx. |
43 |
>> |
44 |
>> You can also run xinit (startx is a wrapper script around xinit that launches |
45 |
>> user-defined apps) and that gives you plain X without a window manager so you |
46 |
>> need to put at least xterm into .xinitrc |
47 |
>> |
48 |
>>> One question about this X stuff. Is there any difference at all at the |
49 |
>>> application level if I run an app displaying on the monitor of that |
50 |
>>> machine, or use ssh -X -Y -C and run the app displaying on a remote |
51 |
>>> machine? |
52 |
>> |
53 |
>> No difference whatsoever for basic apps. X is network transparent, meaning |
54 |
>> that the X client reads and writes a Unix socket, TCP socket, or whatever else |
55 |
>> you can dream up. However, I'm sure you will find that recent fancy stuff like |
56 |
>> compiz and OpenGL don't work as expected. |
57 |
>> |
58 |
>>> If there is absolutely no difference then I don't need to bother with |
59 |
>>> this. If there is then I do. The real issue here is that Myth doesn't |
60 |
>>> work. If I can be certain that displaying Myth apps on a remote |
61 |
>>> screen, such as mythtv-setup or mythfrontend, is really the same then |
62 |
>>> I'll just do that. However those apps are currently failing so I'm |
63 |
>>> trying to eliminate issues, and possibly creating one I don't care |
64 |
>>> about in doing that! |
65 |
>> |
66 |
>> Running X apps locally locally tests your X libs and your X server. |
67 |
>> Running X apps remotely tests the X libs |
68 |
>> |
69 |
> |
70 |
> Thanks Alan, |
71 |
> OK, I switched to a known good monitor, left xdm turned off and |
72 |
> used startx at my command line. I see all the right stuff in ps but |
73 |
> still no video, and it seems that I've lost control of my keyboard as |
74 |
> I cannot use Alt-Ctrl-F2 to get to another console. (The machine |
75 |
> currently doesn't have a mouse) |
76 |
> |
77 |
> MacMini ~ # ps aux | grep x |
78 |
> <SNIP> |
79 |
> mark 4643 0.0 0.2 3324 1348 tty1 S+ 13:24 0:00 |
80 |
> /bin/sh /usr/bin/startx |
81 |
> mark 4659 0.0 0.2 3680 1104 tty1 S+ 13:24 0:00 xinit |
82 |
> /etc/X11/xinit/xinitrc -- -nolisten tcp -br -auth |
83 |
> /home/mark/.serverauth.4643 -deferglyphs 16 |
84 |
> mark 4679 0.0 0.6 8216 3252 tty1 S 13:24 0:00 xterm |
85 |
> -geometry 80x66+0+0 -name login |
86 |
> mark 4694 0.0 0.6 8376 3488 tty1 S 13:24 0:00 |
87 |
> xclock -geometry 50x50-1+1 |
88 |
> mark 4695 0.0 0.6 8208 3252 tty1 S 13:24 0:00 xterm |
89 |
> -geometry 80x50+494+51 |
90 |
> mark 4696 0.0 0.6 8196 3236 tty1 S 13:24 0:00 xterm |
91 |
> -geometry 80x20+494-0 |
92 |
> root 4735 0.0 0.1 2840 1020 pts/3 R+ 13:26 0:00 ps aux |
93 |
> root 4736 0.0 0.1 2060 580 pts/3 R+ 13:26 0:00 grep |
94 |
> --colour=auto x |
95 |
> MacMini ~ # |
96 |
> |
97 |
> If I use top in a terminal and kill startx and xinit then I get back |
98 |
> to my login console. |
99 |
> |
100 |
> Possibly xorg-server-1.5 isn't compatible with a 2.6.24 kernel? |
101 |
> |
102 |
> Maybe I should move this to the Power PC group. Likely I'll find |
103 |
> someone there with direct experience. Still, I appreciate the wider |
104 |
> audience of gentoo-user. |
105 |
> |
106 |
|
107 |
Or you're using an intel card. |
108 |
Set your VIDEO_CARDS variable in /etc/make.conf to "vesa" and |
109 |
recompile xorg-server, then try again. |
110 |
|
111 |
-- |
112 |
Daniel da Veiga |