> No it doesn't break unrelated software :) I thought that might be a stretch. The Gimp doesn't work too well without it though.
> Did you just upgrade xserver-xorg-video-savage? or anything else? > The previous package (1:2.1.3-3) is available from It was a full 'aptitude safe-upgrade' bringing down the first pulse or two of new upgrades since ftp-master went back up so the mesa packages are also suspects. Since this driver has been flakey in the past On the other hand, I can't even get X working with vesa so it could be something else. Since this is the first time I've tried to use it I can't say that it would have worked any better a month ago. The display manager will start with X crashing after I try to log in to a session. Here's the log section with the gorey details: (II) VESA(0): VBESetVBEMode failed...Tried again without customized values. Backtrace: 0: /usr/bin/X(xf86SigHandler+0x7e) [0x80c644e] 1: [0xffffe420] 2: /usr/lib/xorg/modules//libfb.so(fbCopyNtoN+0x18f) [0xb7a2ba5f] 3: /usr/lib/xorg/modules//libfb.so(fbCopyRegion+0x8e) [0xb7a2aa3e] 4: /usr/lib/xorg/modules//libfb.so(fbDoCopy+0x44a) [0xb7a2b05a] 5: /usr/lib/xorg/modules//libfb.so(fbCopyArea+0x78) [0xb7a2b228] 6: /usr/bin/X [0x816eee6] 7: /usr/bin/X [0x811c57a] 8: /usr/bin/X [0x812cbd0] 9: /usr/bin/X [0x816cb6b] 10: /usr/bin/X [0x816cdef] 11: /usr/bin/X [0x816d2d0] 12: /usr/bin/X(compPaintWindowBackground+0x6d) [0x8102bed] 13: /usr/bin/X(miWindowExposures+0xf2) [0x811e592] 14: /usr/bin/X(miHandleValidateExposures+0x78) [0x8134398] 15: /usr/bin/X [0x80d20e6] 16: /usr/lib/xorg/modules/drivers//vesa_drv.so [0xb7bde20f] 17: /usr/bin/X [0x80cd723] 18: /usr/bin/X(xf86SwitchMode+0xd8) [0x80c3258] 19: /usr/bin/X [0x80e42a2] 20: /usr/bin/X [0x80e459a] 21: /usr/bin/X(RRCrtcSet+0x15c) [0x816466c] 22: /usr/bin/X(ProcRRSetScreenConfig+0x4ae) [0x81690ae] 23: /usr/bin/X [0x8162f45] 24: /usr/bin/X [0x814d34e] 25: /usr/bin/X(Dispatch+0x2bf) I'm able to use X with the savage driver from a grml CD so I know the hardware isn't fried. http://snapshot.debian.net/archive/2007/09/17/debian/pool/main/x/xserver-xorg-video-savage/ > > If downgrading only this one fixes the problem, then it would be good to > find out which exact commit broke things in the savage driver. Can you > do a git-bisect with the upstream git repository? That sounds like somthing it would be handy to know how to do. > If not, could you at least try building the previous 2.1.3-3 with the > following patch applied: > http://git.debian.org/?p=pkg-xorg/driver/xserver-xorg-video-savage.git;a=commitdiff_plain;h=846a69f70d189c486448df269a512b8d42fab0c2;hp=53a2088c5590bb96ce9a7ad30d908c7ea1d54027 I'm presently fighting with dpkg as attempting to downgrade the driver brings a dependency conflict with xserver-xorg-video-2. Once I get a known functional 2.1.3-3 installed I'll give it a shot with the patched one. > Do you really need useFBDev? No. I enabled it on on the off chance that it might make a differnece. It didn't.
