Hi Duncan,
I solved my problem by using Piotr's xorg.conf.
>>>>> "Duncan" == Duncan <[EMAIL PROTECTED]> writes:
> The cards aren't new, and they've had 2D support for awhile
> (AFAIK), but the 3D support is what's new and experimental...
at the moment I'm happy with 2D support. I don't have any game
installed deliberately (besides "M-x tetris" in Emacs).
>> Section "Monitor" Identifier "Monitor0" HorizSync 30.0 - 121.0 #
>> Warning: This may fry old Monitors VertRefresh 50.0 - 150.0 #
>> Very conservative. May flicker.
>>
>> DisplaySize 400 300
> Hmm... nice size monitor size! =8^) I'm running two that size, @
> 1600x1200 stacked for 1600x2400. (I used to run them at 2048x1536
> for 2048x3072, but decided that was a bit much.)
I spent a lot of money for the monitor. But I spend most of the time
with TeX and beautiful fonts. Hence I think it's worth the money,
especially because it's now 8 years old and still works properly.
And every craftsman will tell you that the most important thing is to
have good tools. That was my thought when I bought it.
> Note that the monitor section above may not be used -- here the ID
> specified has a space. Above, no space. Does xorg ignore the
> space and treat them the same?
Hmm, at least xorg-6.8 didn't complain.
>> (WW) RADEON: No matching Device section for instance (BusID
>> PCI:1:0:1) found
> This is the only indication of problems there, but as you probably
> already know, this is often normal on chips that can have two
> outputs (whether your card does or not), with the second instance
> only auxiliary and not needed/used under normal circumstances,
> even when both outputs are used.
I got this warning in the past and I assumed that it has to do with
the second channel. So I decided to ignore this message.
> I checked the strace output. I'm /not/ an expert in such things
> and don't claim to be, but the following caught my eye:
>> open("/usr/lib64/xserver/SecurityPolicy", O_RDONLY) = 6 [pid 9421]
>> open("/dev/input/mouse0", O_RDWR|O_NONBLOCK) = 6 [pid 9421] ---
>> SIGFPE (Floating point exception) @ 0 (0) ---
> The more likely issue from my viewpoint is the mouse config.
> /dev/input/mouse0 exists, right?
This worked in the past. I'm using /dev/input/mice from Piotr's
config file now. But note that I didn't update X11 only but the
whole system. Maybe something changed somewhere else.
Regards, and many thanks for your response,
Reinhard
--
----------------------------------------------------------------------------
Reinhard Kotucha Phone: +49-511-4592165
Marschnerstr. 25
D-30167 Hannover mailto:[EMAIL PROTECTED]
----------------------------------------------------------------------------
Microsoft isn't the answer. Microsoft is the question, and the answer is NO.
----------------------------------------------------------------------------
--
[email protected] mailing list
