Various issues with 4.0.1-0phase2v8

[<scherpo@earlham.edu>]

1.) I recently upgraded to kernel 2.4.0-test9pre1, in doing so I rebuilt my
    mga.o drm module.  At this point I was using 4.0.1-0phase2v7, and X
    would refuse to start, reporting "DRM version = 2.0.0, expected 1.0.x".
    As of phase2v8, X starts fine, but I still recieve an error as follows:
  
    (EE) MGA(0): [drm] MGADRIScreenInit failed (DRM version = 2.0.0,
    expected 1.0.x).  Disabling DRI.
  
    Obviously there is some kind of mismatch between the version of drm the
    X debs are expecting and the version that comes with 2.4.0-test9pre1.
    What confused me was the fact that the changes file for 4.0.1-0phase2v8
    indicated that 4.0.1 wasn't actually being used, but that a cvs snapshot
    of X was, so I figured that it would be up to date enough to deal with
    this drm 2.0.0.

2.) Perhaps the most distressing issue is that since my upgrade from
    phase2v7 to v8 X is now once again leaking memory like a siv.  This is a
    problem that I experienced while still using the 3.3.x X debs and was   
    pleasantly surprised to see was fixed when I upgraded to 4.0.1-phase1. 
    To illustrate the problem, when I start up X, with only my window manager
    running, a few dock apps, and a single Eterm, the RSS of X starts out at 
    about 130000 (note: my machine has 256m ram and 250m swap).  As if this 
    were not bad enough, I can watch as the RSS of X grows by about 100 every
    second.  Right now, I am nothing additional open but my mail client      
    (mutt in Eterm) and another Eterm and the usage is as follows:     
                                                                  
    ??(elmoe@stronghold)?(pts)?(11:12am:09/22/00)??
    ??(~)> ps aux | grep "X :0"
    root     18302  5.1 64.3 206520 164160 ?     S    10:53   1:01 X :0
    
    The only thing I can think of is that since you are in the process of 
    forward porting patches from the 3.3.x series debs that you inadvertently
    caused this problem to arrise again?                                      

Any light that you could shed on any of these issues would be greatly
appreciated.  Please don't let me sound demanding, Branden does an awesome
job and helps to keep the rest of us operating at full lazy status.  Keep up
the good work.
    
-- Porter

p.s. Same problems with 4.0.1-0phase2v9.