On Mon, Sep 30, 2002 at 02:58:02PM -0700, Michael Michael wrote:
>Like i said its usefulness is proven in many areas.
>I see no reason not to use it. It could be introduced
>without effecting the current parser.
Current parser aside, how do you deal with the people who want to:
root# vi /etc/X11/X
On Mon, Sep 30, 2002 at 12:00:22PM -0700, Andrew P. Lentvorski wrote:
>On Mon, 30 Sep 2002, Michael Michael wrote:
>> after 1990... Note these arguments are the standard
>> anti-xml arguments given by most idots..
(Sorry but this is a reply moreso to the original that I deleted without
thinking...
On Fri, Jul 26, 2002 at 11:18:13AM -0700, Mark Vojkovich wrote:
>On Fri, 26 Jul 2002, Luca Olivetti wrote:
>
>> Mike Stilson wrote:
>>
>> | BTW: Since I stepped back to 2314 it's been nice and stable (Only 3 days
>> | so far but better than the 10 hours I could
On Wed, Jul 24, 2002 at 01:43:54AM -0400, Mike A. Harris wrote:
>The Nvidia kernel module very much does and should taint the
>kernel.
Yes, I see that now.
The problem I've got right now is... why ISN'T it?
-me
___
Xpert mailing list
[EMAIL PROTECTED]
On Tue, Jul 23, 2002 at 01:36:39PM +0200, Charl P. Botha wrote:
>On Tue, Jul 23, 2002 at 07:16:50AM -0400, Mike Stilson wrote:
>> Just to follow up after giving a little more thought...
>> The kernel module doesn't taint it since I'm recompiling it from source.
>>
On Mon, Jul 22, 2002 at 11:25:35PM +0200, Luca Olivetti wrote:
>-BEGIN PGP SIGNED MESSAGE-
>Hash: SHA1
>
>Mike Stilson wrote:
>Are you sure the nvidia module was loaded at the time of this crash?
>It would taint the kernel if loaded:
>
>Jul 7 20:20:54 pip
On Mon, Jul 22, 2002 at 11:25:35PM +0200, Luca Olivetti wrote:
>Mike Stilson wrote:
>
>| FWIW I had the same issues.
>| The problem I had was that it would crash kswapd with the following
>
>In my case it was either kdeinit, xmessage, kswapd, startkde,...
99% of the time it
On Mon, Jul 22, 2002 at 03:16:40PM +0200, Luca Olivetti wrote:
>Anyway, I was having a lot of these messages (kernel BUG at
>page_alloc.c) with the current version of nvidia driver (1.0-2960) and
>afterwards the system is unpredictable (possible hard locks, file system
>corruption, anything).
>At
>When I startup the X-server on a motherboard with the I815 chipset I get
>a warning
>"xf86AllocateGARTMemory: allocation of 1024 pages failed(Cannot allocate
>memory)".
I'm having the same problem as this guy, the thing is, it worked with
4.1 (I just upgraded yesterday.)
At first I got the mo
