Re: ATI Rage 128 and XFree 4.1
Quoting Michael Jinks [EMAIL PROTECTED] on Wed, Jun 26 10:42: 2. Download the binary distribution of XFree86 4.2 and install this over your Debian install. I'm jumping in a little late in this discussion, but I just solved this problem on the Dell Optiplex GX240 with a ATI Technologies Inc Rage 128 Pro Ultra TF. What finally ended up working for me was to download Xmod.tgz and Xxserv.tgz from ftp://ftp.xfree86.org/pub/XFree86/4.2.0/binaries/Linux-ix86-glibc22/ . I uncompressed them in a tmp directory, then moved bin/XFree86 to /usr/X11R6/bin/ and lib/modules/ to /usr/X11R6/lib/, backing up what was previously there. After I did that, everything started working beautifully, I just cannot use the DRM 4.1 kernel driver for the Rage 128 or X locks up. Now that I think about it, using the kernel 4.1 driver with X 4.2 seems like it could be a bad idea... There are also beta X 4.2 Debian packages available. There is a list of mirrors at http://raw.no/x4.2/ . I have not tried these yet. If you use them it would be great to hear how the work out for you. I have a Dell OptiPlex GX400 on my own desk, and I've toyed with a few of these new 240's just in the process of setting them up, and yeah, from a strictly subjective feel perspective, they don't feel any faster than my home-rolled dual P-III/500 at home. In particular, when load is high, they get really stuttery. I just wanted to second this. I figure part of this is that I came from a SCSI system. When I try to really drive the GX240 it is not pretty. Hope this helps, Omen -- They told me I was gullible ... and I believed them! -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: ATI Rage 128 and XFree 4.1
Quoting Omen Wild [EMAIL PROTECTED] on Wed, Jun 26 12:13: [ snip ] I just cannot use the DRM 4.1 kernel driver for the Rage 128 or X locks up. Now that I think about it, using the kernel 4.1 driver with X 4.2 seems like it could be a bad idea... [ snip ] Hmmm, talking to myself again. ;-) I figured this one out. It was not the version of the DRM drivers, but rather I did not have the right agpgart driver. The GX240 seems to require CONFIG_AGP_I810 rather than just CONFIG_AGP_INTEL. I have both marked yes and now lsmod shows: Module Size Used byNot tainted r128 84032 1 agpgart20224 3 So they are actually getting used and X works fine. I also have: Option UseFBDev true in my XF86Config-4 Device section. Omen -- Antonym, n.: The opposite of the word you're trying to think of. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: exim error: What does it mean?
If there are any mailing list and exim experts out there I would appreciate a second set of eyeballs on what I've done. Quoting Paul Johnson [EMAIL PROTECTED] on Mon, Jun 24 07:55: What does this mean? # /usr/sbin/exim -v -M 17MVAm-0002nz-00 delivering message 17MVAm-0002nz-00 LOG: 0 MAIN PANIC DIE Neither the system_aliases director nor the address_pipe transport set a uid for local delivery of | /usr/lib/sympa/bin/queue [EMAIL PROTECTED] From a google search I managed to piece together something that worked. First, I moved all of the sympa specific aliases into a separate aliases file (/etc/aliases.sympa). Then I added the following to exim's 'TRANSPORTS CONFIGURATION' section: - Begin TRANSPORTS CONFIGURATION - sympa_list_pipe: driver = pipe user = sympa group = sympa return_fail_output - End TRANSPORTS CONFIGURATION - And this to exim's 'DIRECTORS CONFIGURATION' section: - Begin DIRECTORS CONFIGURATION - sympa_lists: driver = aliasfile search_type = lsearch file = /etc/aliases.sympa pipe_transport = sympa_list_pipe - End DIRECTORS CONFIGURATION - I put the above after the system_aliases: and before the userforward: sections. I had to take the domain part out of the aliases (that is, the part to the left of the colon) in /etc/aliases.sympa in order to get it to work. I believe there is an option in the exim config that will allow domains in the alias file but I don't know what it is. My /etc/aliases.sympa looks like this: - Begin aliases.sympa - #-- SYMPA begin ## Aliases used for the sympa mailing-list manager sympa: | /usr/lib/sympa/bin/queue sympa sympa-request: postmaster sympa-owner: postmaster listmaster: postmaster #-- SYMPA end #- [EMAIL PROTECTED] sympa-test: | /usr/lib/sympa/bin/queue [EMAIL PROTECTED] sympa-test-request: | /usr/lib/sympa/bin/queue [EMAIL PROTECTED] sympa-test-owner: | /usr/lib/sympa/bin/bouncequeue sympa-test sympa-test-unsubscribe: | /usr/lib/sympa/bin/queue [EMAIL PROTECTED] sympa-test-subscribe: | /usr/lib/sympa/bin/queue [EMAIL PROTECTED] # - End aliases.sympa - Hope this helps, Omen -- The first myth of management is that it exists. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
XEmacs 21 and updating packages question
Something that has been bothering me for quite a while: someone went through the trouble of making a /usr/local/lib/xemacs/xemacs-packages/ directory, but then when I use XEmacs' built in package updating I overwrite the packages that Debian installs. This just doesn't seem right. I have found the pui-package-install-dest-dir variable and set it to /usr/local/lib/xemacs/xemacs-packages/ and XEmacs happily installs packages into that directory. But, and here is the question, how do I get XEmacs to read the installed packages from that directory? When I load XEmacs it does not see any of the packages installed in /usr/local/lib/xemacs/xemacs-packages/ . Even adding /usr/local/lib/xemacs/xemacs-packages/lisp/speedbar (to pick one, there are around 25 installed packages) to my load-path does not make a difference. I have the same problem if I set pui-package-install-dest-dir to /usr/share/xemacs21/site-packages, which is another Debian supplied directory. Does anyone know how to get XEmacs to read packages from either or both of these directories? Many thanks, Omen pgpwWw7Kxpe0J.pgp Description: PGP signature
