Re: Help!
Rebekah (luvdee@freedomnet.com)
Tue, 12 May 1998 20:20:37 -0400
Yes I got the patch and it worked fine for the afterstep problem I was having
..I havent done anything else to say if it will work for good but I cant see why
it wouldn't ...
I guess my e-mail hasn't made it to the list yet ..I sent one out earlier today
about getting afterstep going ...I am happy now .....
Rebekah
David A. Walker wrote:
> Hi y'all.
>
> I sent Rebekah email about this problem, but don't know if she's had time to
> receive it yet.
> This particular bug is listed on RedHat's 5.0 Errata page, along with the
> fix. (I had the exact URL when I mailed her, but don't have it right now.)
> It's a quick fix; I've had NO sig 11's since I installed it.
>
> -----Original Message-----
> From: Tomas Duewiger <td@music-satellite.de>
> To: Rebekah <luvdee@freedomnet.com>
> Cc: AfterStep@eosys.com <AfterStep@eosys.com>
> Date: Tuesday, May 12, 1998 11:25 AM
> Subject: Re: Help!
>
> >Rebekah <luvdee@freedomnet.com> writes:
> >
> >> from what I read on the age you sent me I would guess it is my
> >> processor ..Which I should have figured out sooner .
> >
> >Most time itīs the memory when gcc aborts with a signal 11. Iīm using
> >some very old Cyrix CPUs (the real bad ones ;-) ) and there it was
> >always the memory. If you got the chance try to change some of the
> >modules and then compile again. Another way to go around a signal 11
> >sometimes is to disable the 2nd level cache, compile a kernel (or
> >AfterStep) and enable the 2nd level cache again. You should try that
> >before changing the CPU.
> >
> >> I had a lot of
> >> trouble with Windows and blamed them on the crap O/S ,...oops maybe it
> >> was hardware all along
> >
> >I donīt think so ;-)
> >
> >> ..Anyway I have a cyrix processor and that has
> >> had some known issues exactly like mine with Red Hat 5.0 and thats
> >> what I am using ..So i am going to try to sleep now ..Totally
> >> aggrivated what a way to go o bed.. anyway if anyone knows of a patch
> >> or anything that may work out the CPU issue it would be great ..There
> >> was not one on the page .....
> >
> >Again sometimes it help playing around with the cache (write back,
> >write through, disable, ...)
> >
> >Tomas
> >
> >--
> >Tomas Duewiger
> >td@music-satellite.de
> >http://pages.vossnet.de/tomasd/
> >
> >--
> > WWW: http://www.afterstep.org/
> > FTP: ftp://ftp.afterstep.org/
> > MAIL: http://wormhole.eosys.com/mailing-lists/AfterStep-Info.html
> > FAQ: http://www.cs.purdue.edu/homes/zamboni/afterstep/FAQ.html
> >
> > To unsubscribe: echo unsubscribe | mail afterstep-request@eosys.com
> >
> Dave Walker
> davewalker@zebra.net
>
> --
> WWW: http://www.afterstep.org/
> FTP: ftp://ftp.afterstep.org/
> MAIL: http://wormhole.eosys.com/mailing-lists/AfterStep-Info.html
> FAQ: http://www.cs.purdue.edu/homes/zamboni/afterstep/FAQ.html
>
> To unsubscribe: echo unsubscribe | mail afterstep-request@eosys.com
--
WWW: http://www.afterstep.org/
FTP: ftp://ftp.afterstep.org/
MAIL: http://wormhole.eosys.com/mailing-lists/AfterStep-Info.html
FAQ: http://www.cs.purdue.edu/homes/zamboni/afterstep/FAQ.html
To unsubscribe: echo unsubscribe | mail afterstep-request@eosys.com