X won't come up on C2
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 :0.0 refused by server Xlib: no protocol specified These machines have no serial number, but have a reasonable time set (June 2007). We are trying with build 617, and kernel 20071022.2 or .3. The firmware is q2d01 When we switch to init level 3, the error messages continue to spew, and ps lists X and xinit as still running. Suggestions ? wad ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: X won't come up on C2
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 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 :0.0 refused by server Xlib: no protocol specified These machines have no serial number, but have a reasonable time set (June 2007). We are trying with build 617, and kernel 20071022.2 or .3. The firmware is q2d01 When we switch to init level 3, the error messages continue to spew, and ps lists X and xinit as still running. Suggestions ? wad ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel -- Jim Gettys One Laptop Per Child ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: X won't come up on C2
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 using? Trial3 is X 1.3, joyride is X 1.4. If it's Trial3, try this: umount /home/olpc/.Xauthority Nobody I asked really understood why, but it fixes a lot of strange X not starting problems people reported to me by random people. So I made .Xauthority a plain file in joyride (I still have to move to a writable location such as /tmp). -- \___/ |___| Bernardo Innocenti - http://www.codewiz.org/ \___\ One Laptop Per Child - http://www.laptop.org/ ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: X won't come up on C2
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 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 process. That is why I'm spooked by this ! And, what build are you using? Trial3 is X 1.3, joyride is X 1.4. Trial3 (build 617, to be more exact.) If it's Trial3, try this: umount /home/olpc/.Xauthority Nobody I asked really understood why, but it fixes a lot of strange X not starting problems people reported to me by random people. So I made .Xauthority a plain file in joyride (I still have to move to a writable location such as /tmp). If this is due to new security features, I once again plead for those features to be removed from the builds... We are about to build 10K laptops that won't boot X! wad ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: X won't come up on C2
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 process. AH! That's it! Perhaps /etc/init.d/olpc-configure is screwing up /etc/X11/xorg.conf because it cannot make sense of the manufactoring data. Moreover, we made some substantial changes to the keyboard descriptions, lately and I don't think anyone updated olpc-configure. I asked cjb on IRC to read what's in /ofw/mfg-data/ and report it back, so I can hack together some quick patch for olpc-configure. It seems a fix is needed in a hurry, so I'll try to make it blindly, without an actual C2. But I could use a procedure to save your mfg-data to a file and restore it on a C1 laptop here in 1CC. I'll ask Mitch if that is possible somehow. The definitive fix for olpc-configure would be setting the X keyboard from within the xinitrc script, without editing the config files at all. But that's planned for FDS, not Trial3. If this is due to new security features, I once again plead for those features to be removed from the builds... They should be disabled by default... I asked cjb and he confirmed it. We are about to build 10K laptops that won't boot X! Heh, so why is it necessarily a bad thing? Our children will learn in first grade how to fix their X server on Linux! That's what I would call a steep learning curve :-) -- \___/ |___| Bernardo Innocenti - http://www.codewiz.org/ \___\ One Laptop Per Child - http://www.laptop.org/ ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: X won't come up on C2
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 way to save the mfg data to a file is to boot linux to a shell prompt and tar up /ofw/mfg-data There is a way to do it from OFW too, but I don't have the recipe handy and I have to get on the plane in a couple of minutes. Bernardo Innocenti wrote: 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 process. AH! That's it! Perhaps /etc/init.d/olpc-configure is screwing up /etc/X11/xorg.conf because it cannot make sense of the manufactoring data. Moreover, we made some substantial changes to the keyboard descriptions, lately and I don't think anyone updated olpc-configure. I asked cjb on IRC to read what's in /ofw/mfg-data/ and report it back, so I can hack together some quick patch for olpc-configure. It seems a fix is needed in a hurry, so I'll try to make it blindly, without an actual C2. But I could use a procedure to save your mfg-data to a file and restore it on a C1 laptop here in 1CC. I'll ask Mitch if that is possible somehow. The definitive fix for olpc-configure would be setting the X keyboard from within the xinitrc script, without editing the config files at all. But that's planned for FDS, not Trial3. If this is due to new security features, I once again plead for those features to be removed from the builds... They should be disabled by default... I asked cjb and he confirmed it. We are about to build 10K laptops that won't boot X! Heh, so why is it necessarily a bad thing? Our children will learn in first grade how to fix their X server on Linux! That's what I would call a steep learning curve :-) ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: X won't come up on C2
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 the userland. -- \___/ |___| Bernardo Innocenti - http://www.codewiz.org/ \___\ One Laptop Per Child - http://www.laptop.org/ ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: X won't come up on C2
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 Xauthority file should care, but it apparently does. It's not a security feature; it was a feature designed to minimize flash rewrites by putting .Xauthority in a tmpfs, and this particular line (in /etc/rwtab) has been in the builds for a *long* time now (since the 500 series at least; I believe it was added by J5). I'm not sure if we're seeing troubles with C2 machines because you're doing unusual network operations on them, or if the problem is actually in the xorg.conf (as Bernie suspects) or what. As Bernie said, we've got another approach the fixing the .Xauthority problem for FRS (moving .Xauthority out of /home/olpc), but I can probably remove /home/olpc/.Xauthority from /etc/rwtab for build -- er, 619 I guess -- if that helps. --scott -- ( http://cscott.net/ ) ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: X won't come up on C2
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. Everyone I asked said that there's no way that the Xauthority file should care, but it apparently does. It's not a security feature; it was a feature designed to minimize flash rewrites by putting .Xauthority in a tmpfs, and this particular line (in /etc/rwtab) has been in the builds for a *long* time now (since the 500 series at least; I believe it was added by J5). I did check that the hostname on these machines, and they looked normal (i.e. last three digits of the MAC plus some text). I was greatly amiss in not mentioning that I have seen this in 581, but only on a single machine that had crashed hard many times, and reflashing fixed the problem. On the C2 machines, reflashing didn't help. I'm not sure if we're seeing troubles with C2 machines because you're doing unusual network operations on them, or if the problem is actually in the xorg.conf (as Bernie suspects) or what. It happens on first (and subsequent) boots.We haven't touched the networking at that time.I hope it is the xorg.conf As Bernie said, we've got another approach the fixing the .Xauthority problem for FRS (moving .Xauthority out of /home/olpc), but I can probably remove /home/olpc/.Xauthority from /etc/rwtab for build -- er, 619 I guess -- if that helps. We will get you more info in a couple of hours. Go Red Sox ! wad ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
