Re: fedora: where are the client's logs kept?

John Ellson <[email protected]>
Newsgroups gmane.linux.terminal-server.devel
Message-ID <[email protected]>
Warren Togami wrote:
> John Ellson wrote:
>   
>> I populated it with fc9 rpms, except for: xorg*, linuxwacom*, mesa*, 
>> rhpxl*,  which I grabbed from fc8.    Then I replaced the fc8 
>> xorg-x11-drv-ati
>> with xorg-x11-drv-ati-6.7.195-3.fc8.x86_64.rpm, which is the last one 
>> that works for me.  Did a "createrepo ." on the directory with my rpm 
>> collection.
>>
>> Did a:  linux-build client --arch=x86_64  using my repo and Warren's 
>> add-ons, and ... magic, VT switching now works! :-)
>>
>>     
>
> It is a complete accident that this is working for you now.
Not really.  I've been limping along with the same xorg-xll rpms on my 
x86_64 at work for the last six months.  So I  had some expectation that 
it would work for me.  I'm not proposing it for anyone else.
> Normally 
> mixing repositories is a great way to screw up your system.
I know, but ltsp client systems are cheap :)   I was just trying to get 
something working so that I could get back to the first problem.
>   Please be 
> sure that there are bugs filed for that X driver problem.
>   
There are 177 open bugs against xorg-x11-drv-ati.    I'm adding another 
one,  but perhaps you could put a plug around the office for some work 
reprioritization to get them fixed?
>   
>> Now back to the original problem:
>>
>> Trying to login at the LTSP screen fails on x86_64 fc9 clients.   On the 
>> client, /var/log/messages contains:
>>
>>     Aug 17 02:54:50 client-172 kernel: cdpinger[1649] general protection 
>> ip:637c70 sp:7fff8fac73b0 error:0 in libglib-2.0.so.0.1600.5[602000+df000]
>>     Aug 17 02:55:30 client-172 kernel: ldm[1790]: segfault at 0 ip 0 sp 
>> 7fffc2021f80 error 14 in ld-2.8.so[110000+1d000]
>>
>> Let me guess?  Its because my clients have no CD/DVD drive??
>>     
>
> No, the cdpinger thing is a known and unrelated problem.
>   
Good, OK, I'll watch for an update.
> Segfault in ldm is new.  It is possible that ldm just was never used on 
> x86-64 before and bug fixes to work on 64bit.  We could use gdb 
> tracebacks with full debuginfo, but that is a bit complicated because 
> you probably need to do it with core dumps.  It is also less feasible in 
> your case because of the screwed up mixed F8/F9 chroot.
>   
Understood. 

-- 
John Ellson

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_____________________________________________________________________
Ltsp-developer mailing list.   To un-subscribe, or change prefs, goto:
      https://lists.sourceforge.net/lists/listinfo/ltsp-developer
For additional LTSP help,   try #ltsp channel on irc.freenode.net
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.