On Tue, Sep 25, 2001 at 14:40:33 +0200, Bas van Gils wrote:
> I have a sig-11 problem. Now, I know that this usually means: broken RAM.
That the most common cause. There are however many other potential causes;
see http://www.bitwizard.nl/sig11 for the list.
HTH,
Ray
--
Obsig: developing a new s
Quoth Damon Muller,
> Quoth Frederik Vanrenterghem,
> > This is a link to the Matrox linux users forum. In this forum, you'll find
> > many questions regarding the G450 and X4.02. Essentially, it seems to boil
> > down to this: sorry, it doesn't work very well yet, wait for a driver
> > update.
>
Quoth Frederik Vanrenterghem,
> This is a link to the Matrox linux users forum. In this forum, you'll find
> many questions regarding the G450 and X4.02. Essentially, it seems to boil
> down to this: sorry, it doesn't work very well yet, wait for a driver
> update.
>
> If you do find a way to get
Damon Muller <[EMAIL PROTECTED]> writes:
> Hi gang,
>
> After having bought a spanking-new Matrox G540 video card, I'm not able
> to get it to use drm/dri for accelerated 3d. This is mildly annoying, as
> I went and bought myself an expensive video-card so I could see the cool
> OpenGL XScreensav
On Thu, 8 Feb 2001, Damon Muller wrote:
>
> BTW, this is using the mga_drv.o module from the Matrox site (the
> standard X4 one does not work with the G450).
>
http://forum.matrox.com/cgi-bin/mgaforum/forumdisplay.cgi?
action=topics&forum=Linux&number=2&DaysPrune=30&LastLogin=
This is a link t
>> Marcus Brinkmann <[EMAIL PROTECTED]> wrote
>> (regarding hardware problems indicated by failed kernel compiles):
>>
>> > You can also change the bios setings, adding more wait states or so.
>>
>> This is a good idea. I forgot to mention that I already
>> did that.
Hi!
Also you *may*
Marcus Brinkmann <[EMAIL PROTECTED]> wrote
(regarding hardware problems indicated by failed kernel compiles):
> You can also change the bios setings, adding more wait states or so.
This is a good idea. I forgot to mention that I already
did that.
-- Frank
--
TO UNSUBSCRIBE FROM THIS M
Lawrence <[EMAIL PROTECTED]> wrote (ragarding hardware problems
indicated by failed kernel compiles):
> because you are using K6, make sure that it is made after week 30. K6
> before week 30 will trigger a bug where people cannot compile Linux
> kernel if there are more than 32MB in their comput
On Sun, Oct 26, 1997 at 02:36:12PM -0600, Frank Sergeant wrote:
> [EMAIL PROTECTED] (Thalia L. Hooker) wrote
>
> > Anyways, my next step was to 'make zImage'. I kept getting Sig 11 errors
> > though not at the same point of compilation:
> > gcc: Internal compiler error: program cc1 got fatal sign
because you are using K6, make sure that it is made after week 30. K6
before week 30 will trigger a bug where people cannot compile Linux
kernel if there are more than 32MB in their computer. It only happens
to Linux world and in fact the bug is uncovered by Linux guys.
Frank Sergeant wrote:
>
On Sun, Oct 26, 1997 at 02:36:12PM -0600, Frank Sergeant wrote:
> [EMAIL PROTECTED] (Thalia L. Hooker) wrote
>
> I seem to have (nearly) the same problem on my AMD K90 system,
> except the error I usually get is "segmentation fault". Again, it
> happens at random places during a kernel compi
[EMAIL PROTECTED] (Thalia L. Hooker) wrote
> Anyways, my next step was to 'make zImage'. I kept getting Sig 11 errors
> though not at the same point of compilation:
> gcc: Internal compiler error: program cc1 got fatal signal 11
...
> After reading the FAQ, it seemed that my problems were typical
On Fri, Oct 24, 1997 at 02:14:56PM -0500, Thalia L. Hooker wrote:
Hi!
For kernel compiling, try using the kernel-package deb file. It is a lot of
easier with it, and you avoid common mistakes.
For your seg11 problem, try pulling the RAM out and put it in again.
Follow the suggestions in the FAQ
13 matches
Mail list logo
