We are having an impossible time getting X to come up on C2 machines.
And X takes forever to stop trying to come up when we switch to init
level 3.
The error message spewed out on the console is:
AUDIT: date time : pid: X: client 1 rejected from local host
(uid 500)
Xlib: connection to
Please send the /var/log/Xorg.0.log file.
Thanks,
- Jim
On Wed, 2007-10-24 at 04:28 -0400, John Watlington wrote:
We are having an impossible time getting X to come up on C2 machines.
And X takes forever to stop trying to come up when we switch
On 10/24/07 04:28, John Watlington wrote:
We are having an impossible time getting X to come up on C2 machines.
And X takes forever to stop trying to come up when we switch to init
level 3.
I've never seen a C2 machine yet. What are the relevant
hardware changes?
And, what build are you
On Oct 24, 2007, at 10:14 AM, Bernardo Innocenti wrote:
On 10/24/07 04:28, John Watlington wrote:
We are having an impossible time getting X to come up on C2 machines.
And X takes forever to stop trying to come up when we switch to
init level 3.
I've never seen a C2 machine yet. What
On 10/24/07 10:56, John Watlington wrote:
I've never seen a C2 machine yet. What are the relevant
hardware changes?
None. Testers in Cambridge should be seeing the same problems!
The only difference should be that these machines didn't go through
the full write manufacturing data
So far the new keyboard descriptions in the manufacturing data are a
paper spec only.
By that I mean that, as far as I know, the new tags are not present in
the pre-build machines, and the OS doesn't look for them.
(That is not quite true for OFW; it will use the new KA tag if it exists).
One
On 10/24/07 11:35, Mitch Bradley wrote:
One way to save the mfg data to a file is to boot linux to a shell
prompt and tar up /ofw/mfg-data
And how could I restore it to another machine?
I was looking for a trick involving the rewrite of the
specific flash page, either from within OFW or from
On 10/24/07, John Watlington [EMAIL PROTECTED] wrote:
If it's Trial3, try this:
umount /home/olpc/.Xauthority
This seems to be related to machines which change their hostname or IP
address after first boot; I'm not sure exactly which. Everyone I
asked said that there's no way that the
On Oct 24, 2007, at 12:22 PM, C. Scott Ananian wrote:
On 10/24/07, John Watlington [EMAIL PROTECTED] wrote:
If it's Trial3, try this:
umount /home/olpc/.Xauthority
This seems to be related to machines which change their hostname or IP
address after first boot; I'm not sure exactly which.