Brian Mury wrote:
On Tue, 2008-01-22 at 06:57 -0500, Jim Cornette wrote:
Brian Mury wrote:
This has been happening to me as well on F8. I just hadn't gotten around
to reporting it yet. FC1 through F7 were fine on this box, so it
definitely looks like something F8 specific.
This change to xorg.conf started at F8 if I recall. I do a lot of
running rawhide so I sometimes vaguely remember the release changes are
implemented.
I'm not sure what you mean by "this change to xorg.conf". Do you mean
xorg.conf didn't exist prior to F8? I'm 99% sure I had an xorg.conf in
F7.
Mode lines are not used as previous versions of X used in the file.
"1280x1024" "1024x768" "800x600" or other resolutions were specified in
the past. The standard now is for automatic detection in the screen section.
The xorg.conf existed ever since xorg.conf was split from the xfree86
project in the same form but with a different name for identification.
I never see the MC_FB type of information in my radeon logs for this
laptop. Also evdiv brain sounds a bit like the automated aspects for the
new server/driver information is not functioning cognitively. It sure
shows the limitations for Artificial intelligence. - :)
FWIW, I have my mouse driver set to evdev:
Section "InputDevice"
Identifier "Mouse0"
Driver "evdev"
Option "Name" "Logitech USB-PS/2 Optical Mouse"
EndSection
which allows all of my mouse buttons to be recognized. May not be
relevant, but I'm not sure so I thought I'd mention it, since you
mentioned evdev.
Thanks! That explains why I do not see the entry in my log files.
You might try to save your current xorg.conf file and regenerate a
completely new xorg.conf file to see if there is something in your
modified file that destabilizes X.
Hopefully some lister with other ideas can offer advice or you two can
figure out what might be causing these problems. Bugzila could show
clues too from others who are not part of this list.
Yeah, I think I'll file a Bugzilla bug when I have a spare moment.
It would help since their job reflects on knowing what causes problems
and can determine problems better.
Upstream might be the best choice rather than Redhat bugzilla.
Sorry I cannot figure out a good clue that would resolve the problem.
That's ok! :-)
Legitimate problems to the list are usually masked by excessive off
topic or attacking threads. I was hoping continued discussion on this
problem would attract attention from those really good at adding options
to certain config files and resolving the problems.
Good Luck! - :)
Jim
--
Windows:
It's not pretty.
It's not ugly.
But it's pretty ugly.
--
fedora-list mailing list
fedora-list@xxxxxxxxxx
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
