Hi All, just wanted to share a few of my observations while running FC2-test2, and maybe make life a little easier for people with the same problems as me.
1) My machine is currently equiped with a ATI Radeon 9800XT card, XFree86 (scrap that, xorg nowadays) has no support for it, and your forced to run in VESA mode. While this is fine for a server machine where you only run the occasional vnc server or a system-config-... tool, for a workstation it's just to damn dog slow.. Getting the get ATI supplied driver to work with the 2.6.x kernel seemed imposible (with some source hacking it compiled, but the kernel driver still failed with some 'invalid address' option); So i ended up downgrading my FC2-test2 instalation to a 2.4 kernel.. What you do is to download the latest 2.4.x kernel rpm's from the FC1 repository, then edit your /etc/modules.conf (i had to add usb, sound and ethernet card aliases in there), re-make your initrd for this kernel (mkinitrd), and setup lilo or grub for the new kernel.. After this the ATI driver compiled and installed without any problems, and i have fully accelerated X again (and 3D support). I won't say that 2.4.x is slower or faster then 2.6.x, but the graphical lack of speed with non accelerated X drivers, makes this downgrade a huge speedup
2) I have a wireless optical mouse thingy, which only works on USB. I noticed that the default movement speed of a mouse in X is quite slow, so i went to the gnome-control-center to speed things up a bit.. To my supprise i could slide sliders to my hearts content, but with no visible changes.. It turns out the default XF86Config is configured for 2 mouse inputs (old style psaux mice, and usb mice).. And gnome-control-center's mouse applet only changed the settings for the core mouse.. Resolution was to remove the "Mouse0" device input section, rename the device id for DevInputMice to Mouse0, and remove the DevInputMice reference in the ServerLayout section... After this the mouse configuration set the mouse speed for my usb mouse nicely again
3) While trying to do a big upgrade from FC2-test1 to the recent development tree, YUM crashed out on me.. After some digging in it's python sources i found that it fails on a RPM package version compare, where one package has no 'release' tag.. While it looks like YUM should deal with the release being 'None', it didn't.. The workaround i applied to get things working again was to edit /usr/share/yum/rpmUtils.py and at line 121 add these lines: if r2 == None: r2 = '0'
4) My Audigy with only digital sound out... Sigh this has always been and always be a problem it seems. The new 2.6 and the old 2.4 drivers support the card perfectly, but have no way to configure it for using the digital sound output instead of the analog one; Or atleast as far as i know off! A work around used to be to compile the old emu10k1 tools and use it's tools to configure the card for digital out, but it seems with the new compilers, they won't compile anymore.. Haven't found a workaround for this yet, so for now my system is silent and without sound.. Anyone know a workaround/fix for this?
Well thats it for now.. All in all i love the way things are shaping up, that the above are the only complaints means the rest is working to my satisfaction
-- Chris
On Wed, 2004-03-31 at 14:53, Chris Chabot wrote:
- I have a wireless optical mouse thingy, which only works on USB. I
noticed that the default movement speed of a mouse in X is quite slow, so i went to the gnome-control-center to speed things up a bit.. To my supprise i could slide sliders to my hearts content, but with no visible changes.. It turns out the default XF86Config is configured for 2 mouse inputs (old style psaux mice, and usb mice).. And gnome-control-center's mouse applet only changed the settings for the core mouse.. Resolution was to remove the "Mouse0" device input section, rename the device id for DevInputMice to Mouse0, and remove the DevInputMice reference in the ServerLayout section... After this the mouse configuration set the mouse speed for my usb mouse nicely again
The input subsystem of 2.6 kernels is very different from 2.4. In fact, with 2.6 kernels, all mices are multiplexed into a single device called /dev/input/mice. Thus, you can define a single Mouse in XF86Config pointing to /dev/input/mice instead of having several mouse entries. This works for me and my laptop with a built-in PS/2 touchpas and a USB Wheel Mouse.
The default XFree86 config file written by the fedora installer configures it for both those input types.. And that the gnome-control-center applet configures the Mouse0 entry (CorePointer), which is the old style /dev/psaux one.. So judging by your input the config file written the actual bug is that the xfree86 default config file should not include both mouse types, but only the /dev/input/mice one.. (Which ofcource opens up a whole can of worms about ppl running an old 2.4.x kernel w/ FC2..)
Felipe Alfaro Solana wrote:
On Wed, 2004-03-31 at 14:53, Chris Chabot wrote:
- I have a wireless optical mouse thingy, which only works on USB. I
noticed that the default movement speed of a mouse in X is quite slow, so i went to the gnome-control-center to speed things up a bit.. To my supprise i could slide sliders to my hearts content, but with no visible changes.. It turns out the default XF86Config is configured for 2 mouse inputs (old style psaux mice, and usb mice).. And gnome-control-center's mouse applet only changed the settings for the core mouse.. Resolution was to remove the "Mouse0" device input section, rename the device id for DevInputMice to Mouse0, and remove the DevInputMice reference in the ServerLayout section... After this the mouse configuration set the mouse speed for my usb mouse nicely again
The input subsystem of 2.6 kernels is very different from 2.4. In fact, with 2.6 kernels, all mices are multiplexed into a single device called /dev/input/mice. Thus, you can define a single Mouse in XF86Config pointing to /dev/input/mice instead of having several mouse entries. This works for me and my laptop with a built-in PS/2 touchpas and a USB Wheel Mouse.
On Wed, 31 Mar 2004 14:53:41 +0200, Chris Chabot wrote:
- While trying to do a big upgrade from FC2-test1 to the recent
development tree, YUM crashed out on me.. After some digging in it's python sources i found that it fails on a RPM package version compare, where one package has no 'release' tag.. While it looks like YUM should deal with the release being 'None', it didn't.. The workaround i applied to get things working again was to edit /usr/share/yum/rpmUtils.py and at line 121 add these lines: if r2 == None: r2 = '0'
Huh? A package without %release?! Which one is it?
On Wed, 2004-03-31 at 16:01 +0200, Michael Schwendt wrote:
On Wed, 31 Mar 2004 14:53:41 +0200, Chris Chabot wrote:
- While trying to do a big upgrade from FC2-test1 to the recent
development tree, YUM crashed out on me.. After some digging in it's python sources i found that it fails on a RPM package version compare, where one package has no 'release' tag.. While it looks like YUM should deal with the release being 'None', it didn't.. The workaround i applied to get things working again was to edit /usr/share/yum/rpmUtils.py and at line 121 add these lines: if r2 == None: r2 = '0'
Huh? A package without %release?! Which one is it?
Curiously it isn't yum crashing out it's rpmlib. The bindings get CRANKY when you give them values they don't expect. I think I've caught this in cvs versions of yum, not positive though. If you are getting a traceback could you bugzilla it? Thanks
-sv
On Wed, 2004-03-31 at 14:53 +0200, Chris Chabot wrote:
- My machine is currently equiped with a ATI Radeon 9800XT card,
XFree86 (scrap that, xorg nowadays) has no support for it, and your forced to run in VESA mode. While this is fine for a server machine where you only run the occasional vnc server or a system-config-... tool, for a workstation it's just to damn dog slow..
Can you trying using the radeon driver with xorg-x11? Although hwdata stuff hasn't been updated yet, the radeon driver in xorg-x11 should support a lot of the newer stuff (at least for 2d).
Jeremy
I've tried xorg's generic radeon driver, and it worked fine! Gave it a good try for a day, and haven't found any glitches.. My vote would be to include the chipset id in hwdata :-)
Ps, performance is ofcource a bit slower then the ati drivers, but i think for most ppl 'just works' is preferable over 'if you perform this voodoo magic it might work, and a little faster' :-)
Thanks for the hints,
-- Chris
Jeremy Katz wrote:
On Wed, 2004-03-31 at 14:53 +0200, Chris Chabot wrote:
- My machine is currently equiped with a ATI Radeon 9800XT card,
XFree86 (scrap that, xorg nowadays) has no support for it, and your forced to run in VESA mode. While this is fine for a server machine where you only run the occasional vnc server or a system-config-... tool, for a workstation it's just to damn dog slow..
Can you trying using the radeon driver with xorg-x11? Although hwdata stuff hasn't been updated yet, the radeon driver in xorg-x11 should support a lot of the newer stuff (at least for 2d).
Jeremy
devel@lists.stg.fedoraproject.org
-
Chris Chabot -
Felipe Alfaro Solana -
Jeremy Katz -
Michael Schwendt -
seth vidal