1 |
On 01/03/2011 02:11 AM, Peter Humphrey wrote: |
2 |
> On Sunday 02 January 2011 15:51:24 walt wrote: |
3 |
>> On 01/02/2011 03:51 AM, Peter Humphrey wrote: |
4 |
>>> It looks as though the boot sequence is going wrong somehow, |
5 |
>>> because when I get my initial blank screen, if I then switch to a |
6 |
>>> VT and restart xdm, everything works as expected. |
7 |
>> |
8 |
>> Just for clarification, are you saying that you can do that even |
9 |
>> without re-emerging nvidia-drivers? |
10 |
> |
11 |
> Exactly so - without doing anything other than restarting KDM. This is |
12 |
> an ~amd64 box, by the way. |
13 |
|
14 |
So nvidia.ko is not the problem then.(Unless it's being loaded too late |
15 |
in the boot sequence.) |
16 |
|
17 |
>> Is there an X session already running before you restart |
18 |
>> kdm? (I don't use any of *dm, so I don't know if they are X apps |
19 |
>> that require X to be running before they can write to the screen.) |
20 |
> |
21 |
> As far as I know, KDM starts X itself. At VT4 (which I use habitually |
22 |
> for root logins) I issue the command: |
23 |
> |
24 |
> $ /etc/init.d/xdm restart&& logout |
25 |
> |
26 |
> which starts the KDM session as normal. |
27 |
|
28 |
I'm wondering if you have some mixture of baselayout versions on that |
29 |
machine from previous updates. A glance through the many relevant |
30 |
files in /etc/env.d/, /etc/conf.d/, /etc/X11*, /etc/rc.conf, /etc/init.d |
31 |
leaves me confused about what happens during xdm startup. |
32 |
|
33 |
Could your machine be trying to start something other than kdm by mistake? |
34 |
I.e., maybe you are starting kdm for the first time from the VT instead of |
35 |
re-starting it? |
36 |
|
37 |
I'd try "touch /etc/.noxdm" and reboot, then log in and do "/etc/init.d/xdm |
38 |
start" again. If that also works perfectly then I'd guess there is something |
39 |
in the list of directories above that is mis-configured -- my guess would |
40 |
be that the bootscripts are trying to start the wrong xdm -- just a SWAG :) |