Linux-Misc Digest #652, Volume #25 Sun, 3 Sep 00 07:13:04 EDT
Contents:
Re: X Windows Not Display? (James Richard Tyrer)
Is linux compatible with the "Asus K7V" Motherboard? ([EMAIL PROTECTED])
Dealing with segmentation faults (Sean McAfee)
Re: xlockmore makes machine freeze (Tomalak)
Re: Shared library and PIC (Casper H.S. Dik - Network Security Engineer)
Re: Linux, XML, and assalting Windows ([EMAIL PROTECTED])
Re: X Windows Not Display? ("Peter T. Breuer")
Re: X Windows Not Display? (Anita Lewis)
Re: Dealing with segmentation faults ("Peter T. Breuer")
----------------------------------------------------------------------------
From: James Richard Tyrer <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.hardware,comp.os.linux.setup,comp.os.linux.x
Subject: Re: X Windows Not Display?
Date: Sun, 03 Sep 2000 05:20:34 GMT
This is a multi-part message in MIME format.
==============668C595864F22441697CD69C
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
"T.F.Lai" wrote:
> Hi, I'm installed RedHat 6.2 on the following hardware :
> AMD K6-400, 32MB RAM, S3 Trio3D Graphics Card, Sony CPD-15SF II.
>
> But the X Windows seem to detect the graphics card but when I type startx at
> the command prompt. The monitor doesn't display and the button become
> orange.
>
> Can anyone give me some tips or hints?
>
> I'll appreciate for your kindly help.
>
> Thanks.
A good first guess would be that the autodetection didn't work. As root, try
running "XF86Setup.
JRT
==============668C595864F22441697CD69C
Content-Type: text/x-vcard; charset=us-ascii;
name="tyrerj.vcf"
Content-Transfer-Encoding: 7bit
Content-Description: Card for James Richard Tyrer
Content-Disposition: attachment;
filename="tyrerj.vcf"
begin:vcard
n:Tyrer;James Richard
tel;fax:call first
tel;home:(520) 648-3720
x-mozilla-html:FALSE
org:JRT Engineering
adr:;;1468 North Rio Sonora;Green Valley;Arizona;85614-4007;USA
version:2.1
email;internet:[EMAIL PROTECTED]
x-mozilla-cpt:;2
fn:James Richard Tyrer
end:vcard
==============668C595864F22441697CD69C==
------------------------------
From: [EMAIL PROTECTED]
Subject: Is linux compatible with the "Asus K7V" Motherboard?
Date: Sun, 03 Sep 2000 05:40:34 GMT
The Asus K7V Motherboard uses the VIA KX133tm Chipset. Does anyone know
whether this chipset will support the installation of linux. Thanks.
Joel.
Sent via Deja.com http://www.deja.com/
Before you buy.
------------------------------
Subject: Dealing with segmentation faults
From: [EMAIL PROTECTED] (Sean McAfee)
Date: Sun, 03 Sep 2000 07:22:43 GMT
I've always preferred compiling software packages from source instead of
from binaries. I've had remarkably few library compatibility problems over
the years as a result, but occasionally I'll want to use a program that is
only available in binary form. If there are any problems running the
binary on my system, I'm rather at a loss how to proceed.
The program in this case is the freeware version of PGP 6.5.8 from pgp.com.
When I run it, it immediately segfaults. My own system is Slackware 4.0.
Thanks to my compile-everything policy I'm only dimly aware of the various
issues related to the libc5-->glibc2 transition, but I at least know that
it's one of the biggest sources of library incompatibility problems out
there. I would suspect my libc version of being out of date, but Slack 4.0
uses glibc2 as far as I know; at least, here's the relevant portion of my
/lib directory listing:
-rwxr-xr-x 1 root root 652412 Oct 25 1998 /lib/libc-2.0.7.so
lrwxrwxrwx 1 root root 13 Sep 24 1999 /lib/libc.so.4 -> libc.so.4.7.6
-rwxr-xr-x 1 root root 634880 Jun 4 1996 /lib/libc.so.4.7.6
lrwxrwxrwx 1 root root 14 Sep 24 1999 /lib/libc.so.5 -> libc.so.5.4.46
-rwxr-xr-x 1 root root 614840 Oct 5 1998 /lib/libc.so.5.4.46
lrwxrwxrwx 1 root root 13 Sep 24 1999 /lib/libc.so.6 -> libc-2.0.7.so
When programs that I write segfault, I use gdb on them; here's what gdb has
to say about pgp's crashing:
Program received signal SIGSEGV, Segmentation fault.
0x4004a8d5 in _IO_file_close_it () from /usr/lib/libstdc++.so.2.8
(gdb) back
#0 0x4004a8d5 in _IO_file_close_it () from /usr/lib/libstdc++.so.2.8
#1 0x4001916d in fclose () from /lib/libpthread.so.0
#2 0x80e853b in sExistsProc ()
#3 0x80e7b59 in PFLFileSpecExists ()
#4 0x8114331 in pgpInitMacBinaryMappings ()
#5 0x80c0e04 in PGPsdkInit ()
#6 0x804a7dc in main (argc=1, argv=0xbffff444) at main.c:187
I'm kinda stuck about where to go from here. Can anyone suggest a general
way to go about diagnosing and fixing segmentation faults generated by
not-locally-compiled binaries? If not, how about some pointers for this
specific case?
Many thanks in advance.
--
"It's a deicide. This guy Lokk arranged the murder of this guy Baldur.
Now Baldur's Dad's going postal and threatening to end the universe..."
"I've had enough of this. Listen, Pops, you end the universe and I'm
running you BOTH in!" -- from Top Ten #7 | Sean McAfee | [EMAIL PROTECTED]
------------------------------
From: [EMAIL PROTECTED] (Tomalak)
Subject: Re: xlockmore makes machine freeze
Date: Sun, 03 Sep 2000 08:26:03 GMT
I'm not using a RH distro, but I heard tell you now have to manually
install XFree86 with RH 6.1. In any event, might want to double check
that you are indeed using the proper s3 virge drivers. Not sure how
one goes about that in a RH disto without XFree86. Nevertheless,
unless there is a bug with RH's xscreensaver and xlockmore packages,
then everything you wrote here suggests to me a device driver issue.
---
On 1 Sep 2000 23:06:14 GMT, [EMAIL PROTECTED] (David Rysdam) asked:
:-----BEGIN PGP SIGNED MESSAGE-----
:Hash: SHA1
:
:(I have to avoid the word "lock" in this post so I don't confuse
:matters)
:
:A few months ago I swapped out the video card I had in my machine
:(don't remember what, but I can check if it matters) for an S3 Virge
:DX2. I immediately began having two problems.
:
:1) Random freezes--screen suddenly goes "test pattern" and machine is
: total frozen, can't alt-sysrq-anything, have to power off.
:
:2) Non-random freezes--screen freezes as is (i.e. no test patter)
: otherwise exactly like #1. I call them "non-random" because it
: happens, without fail, when I startup xlockmore (password or not).
: It generally freezes within 10 seconds of starting xlockmore. I
: just downloaded 4.16 last night and it has the same problem. When
: I first started having the problem I tried xscreensaver and had the
: same problem.
:
:I thought for a while that it was an OpenGL problem (don't ask me why
:I thought that). But for the last several nights I've been doing
:OpenGL tutorials and they work just fine. Now I don't know what to
:think. I'd replace the card but other than these freezes it works
:great.
:
:System: RH 6.1, upgraded. Kernel 2.2.16. I can supply other
:hardware/software data on demand--I just don't know what might be
:relevant.
:
:- --
:My public encryption key is available from www.keyserver.net
:-----BEGIN PGP SIGNATURE-----
:Version: GnuPG v1.0.0 (GNU/Linux)
:Comment: For info see http://www.gnupg.org
:
:iD8DBQE5sDaa8mkEvJSZJO8RAq2MAJ9b9kjzep1v+W8K3sGAIy5IXb3N3ACbB7Bc
:JkBWtNG+DiGQ/PIvmcEzeOw=
:=cWHP
:-----END PGP SIGNATURE-----
------------------------------
From: [EMAIL PROTECTED] (Casper H.S. Dik - Network Security Engineer)
Crossposted-To: comp.unix.programmer,comp.unix.solaris
Subject: Re: Shared library and PIC
Date: 3 Sep 2000 08:57:18 GMT
[[ PLEASE DON'T SEND ME EMAIL COPIES OF POSTINGS ]]
[EMAIL PROTECTED] (Kenny McCormack) writes:
>Funny you should mention that. After reading your post, I decided to go
>back and give it a try. I read the ld man page and it seemed reasonable.
>When I added "-z defs" to the Makefile and re-built it, I got a whole bunch
>of fatal errors, complaining that various symbols were implicitly defined in
>libc.so - i.e., it seemed that I was asking it to resolve these things now,
>when the original code expected them to be resolved at runtime (I.e., from
>the standard libs).
To have a proper shared object, you should have included -lc in its
dependencies.
Casper
--
Expressed in this posting are my opinions. They are in no way related
to opinions held by my employer, Sun Microsystems.
Statements on Sun products included here are not gospel and may
be fiction rather than truth.
------------------------------
From: [EMAIL PROTECTED]
Crossposted-To: alt.os.linux,comp.text.xml,comp.os.linux.development.system
Subject: Re: Linux, XML, and assalting Windows
Date: Sun, 03 Sep 2000 09:12:59 GMT
In comp.os.linux.development.system Christopher Browne <[EMAIL PROTECTED]> wrote:
| XML buys you the ability to get a "cheap parser."
"Cheap" seems to be the operative rule, at least in the C language.
--
| Phil Howard - KA9WGN | My current websites: linuxhomepage.com, ham.org
| phil (at) ipal.net +----------------------------------------------------
| Dallas - Texas - USA | [EMAIL PROTECTED]
------------------------------
From: "Peter T. Breuer" <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.hardware,comp.os.linux.setup,comp.os.linux.x
Subject: Re: X Windows Not Display?
Date: 3 Sep 2000 09:59:19 GMT
In comp.os.linux.misc T.F.Lai <[EMAIL PROTECTED]> wrote:
: Hi, I'm installed RedHat 6.2 on the following hardware :
: AMD K6-400, 32MB RAM, S3 Trio3D Graphics Card, Sony CPD-15SF II.
: But the X Windows seem to detect the graphics card but when I type startx at
: the command prompt. The monitor doesn't display and the button become
: orange.
Show us the output from "X -probeonly". And from "SuperProbe" if you have
time.
: Can anyone give me some tips or hints?
Need data. Saying "it doesn't work" isn't useful. The datapoint you
_have_ provided is the card. Thanks! Now we need to see your belief
confirmed with hard output from a program that probes the chipset.
TTThe card is supported, as far as I remember, so either you are using
the wrong driver, or you have configured the right driver wrongly.
The output from X -probeonly will tell us most of that. You might
also consider "X -showconfig" to let us see more driver-oriented info.
Check out such Xblah-HOWTOs as you can find. But this is a trivial
problem ... you can always use the VGA16 driver just to confirm taht
it's X and not your system that has the problem.
Peter
------------------------------
From: [EMAIL PROTECTED] (Anita Lewis)
Crossposted-To: comp.os.linux.hardware,comp.os.linux.setup,comp.os.linux.x
Subject: Re: X Windows Not Display?
Reply-To: [EMAIL PROTECTED]
Date: Sun, 03 Sep 2000 10:32:19 GMT
On Sun, 3 Sep 2000 12:55:09 +0800, T.F.Lai wrote:
>Hi, I'm installed RedHat 6.2 on the following hardware :
> AMD K6-400, 32MB RAM, S3 Trio3D Graphics Card, Sony CPD-15SF II.
>
>But the X Windows seem to detect the graphics card but when I type startx at
>the command prompt. The monitor doesn't display and the button become
>orange.
>
>Can anyone give me some tips or hints?
>
>I'll appreciate for your kindly help.
>
>Thanks.
Run either xf86config, XF86Setup, or Xconfigurator and put in the proper
monitor Horiz and Vert Range.
------------------------------
From: "Peter T. Breuer" <[EMAIL PROTECTED]>
Subject: Re: Dealing with segmentation faults
Date: 3 Sep 2000 10:30:55 GMT
Sean McAfee <[EMAIL PROTECTED]> wrote:
: The program in this case is the freeware version of PGP 6.5.8 from pgp.com.
Yeah, the various incompatible PGP's are pretty much hell. I've had
most success with the oldest (pgp 2?). The rest don't seem compatible
with my elm mailers idea of how they should work ...
: When I run it, it immediately segfaults. My own system is Slackware 4.0.
: Thanks to my compile-everything policy I'm only dimly aware of the various
: issues related to the libc5-->glibc2 transition, but I at least know that
: it's one of the biggest sources of library incompatibility problems out
In this case it should not be a biggie. My system should be pretty much
the same as yours, so I'll try it. Good grief .. the site is heavily
javascripted. My poor lynx is having trouble. Ahh, I see, this is a
commercial frontend hiding the MIT depository. If only MIT would
respond ... Well, I see binaries, but no source. Still, the binary they
include seems to have no problems on my system (as you can see, I
maintain libc6 libraries in a separate directory):
oboe:/usr/oboe/ptb/src/pgp-6.5.8% ldd ./pgp
libpthread.so.0 => /usr/lib6/libpthread.so.0 (0x4001c000)
libnsl.so.1 => /usr/lib6/libnsl.so.1 (0x4002d000)
libstdc++.so.2.8 => /usr/lib6/libstdc++.so.2.8 (0x40042000)
libm.so.6 => /usr/lib6/libm.so.6 (0x40088000)
libc.so.6 => /usr/lib6/libc.so.6 (0x400a4000)
/lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x40000000)
: there. I would suspect my libc version of being out of date, but Slack 4.0
: uses glibc2 as far as I know; at least, here's the relevant portion of my
No, as far as I recall, it uses glibc 2.0 (i.e. the development version).
That is not compatible with glibc 2.1 (the release version).
: /lib directory listing:
: -rwxr-xr-x 1 root root 652412 Oct 25 1998 /lib/libc-2.0.7.so
Yep. glibc 2.0. Sorry. You have to move to glibc2.1. This might
actually be harder for you on a glibc2.0 system than it is for me on a
glibc1 system (slackware 3.0).
Tell me where you got the source ... OK OK, Il go to freshmeat. Not
there. Whatever happened to archie .... Well, I find the source for
6.5.i1, but nothing else so far. Indeed, the tables I see indicate that
the latest freeware version is 6.5.1i beta2. So I don't see how you got
source for 6.5.8.
Peter
------------------------------
** FOR YOUR REFERENCE **
The service address, to which questions about the list itself and requests
to be added to or deleted from it should be directed, is:
Internet: [EMAIL PROTECTED]
You can send mail to the entire list (and comp.os.linux.misc) via:
Internet: [EMAIL PROTECTED]
Linux may be obtained via one of these FTP sites:
ftp.funet.fi pub/Linux
tsx-11.mit.edu pub/linux
sunsite.unc.edu pub/Linux
End of Linux-Misc Digest
******************************
