After upgrading to F14, switching from one workspace to another is excruciatingly slow!! I am a gnome user. Can this be attributed to Gnome or to the X server or to the ATI Radeon driver?
On 03/29/2011 06:28 PM, Joe Zeff wrote:
On 03/29/2011 05:08 PM, JD wrote:
Can this be attributed to Gnome or to the X server or to the ATI Radeon driver?
I'm using F 14 and Gnome and see no problems even though my mobo's maxed out at 1G RAM. Probably the driver.
Well, it is taking up to 3.5 seconds for the windows in a workspace to get populated and fully visible when I switch to that workspace. It used to be almost instantaneous in F13. I have 2GB ram, and 12 GB swap space, but very few apps running. Most of the time I have 6 workspaces, each with a separate FireFox window, and up to 4 4 workspaces, each with a gnome terminal. and 1 workspace with Thunderbird. Hardly any space is used in swap. To wit:
# swapon -s Filename Type Size Used Priority /dev/sda3 partition 4200992 17540 -1 /dev/sdb2 partition 8385924 0 -2
On 03/29/2011 10:43 PM, JD wrote:
On 03/29/2011 06:28 PM, Joe Zeff wrote:
On 03/29/2011 05:08 PM, JD wrote:
Can this be attributed to Gnome or to the X server or to the ATI Radeon driver?
I'm using F 14 and Gnome and see no problems even though my mobo's maxed out at 1G RAM. Probably the driver.
Well, it is taking up to 3.5 seconds for the windows in a workspace to get populated and fully visible when I switch to that workspace.
What is the load avg on the system in question? I have seen similar on my system when the load avg starts to climb (anything > 5 is really bad). But, when he load avg is low, redraws should be good.
It used to be almost instantaneous in F13. I have 2GB ram, and 12 GB swap space, but very few apps running. Most of the time I have 6 workspaces, each with a separate FireFox window,
Firefox is a resource *PIG*. Since it is one application, I'd look into how much memory it is using (both in ram and in swap), and whether or not any of its windows are doing anything (like displaying FLASH or active JAVA applets).
and up to 4 4 workspaces, each with a gnome terminal. and 1 workspace with Thunderbird.
How big are your mailboxes? Thunderbird can also slow you down if you have large mailboxes.
Hardly any space is used in swap. To wit:
# swapon -s Filename Type Size Used Priority /dev/sda3 partition 4200992 17540 -1 /dev/sdb2 partition 8385924 0 -2
What does your performance look like after you close *every* firefox window and thunderbird? [make sure firefox is no longer running.]
On 03/29/2011 08:08 PM, Kevin J. Cummings wrote:
On 03/29/2011 10:43 PM, JD wrote:
On 03/29/2011 06:28 PM, Joe Zeff wrote:
On 03/29/2011 05:08 PM, JD wrote:
Can this be attributed to Gnome or to the X server or to the ATI Radeon driver?
I'm using F 14 and Gnome and see no problems even though my mobo's maxed out at 1G RAM. Probably the driver.
Well, it is taking up to 3.5 seconds for the windows in a workspace to get populated and fully visible when I switch to that workspace.
What is the load avg on the system in question? I have seen similar on my system when the load avg starts to climb (anything> 5 is really bad). But, when he load avg is low, redraws should be good.
It used to be almost instantaneous in F13. I have 2GB ram, and 12 GB swap space, but very few apps running. Most of the time I have 6 workspaces, each with a separate FireFox window,
Firefox is a resource *PIG*. Since it is one application, I'd look into how much memory it is using (both in ram and in swap), and whether or not any of its windows are doing anything (like displaying FLASH or active JAVA applets).
and up to 4 4 workspaces, each with a gnome terminal. and 1 workspace with Thunderbird.
How big are your mailboxes? Thunderbird can also slow you down if you have large mailboxes.
Hardly any space is used in swap. To wit:
# swapon -s Filename Type Size Used Priority /dev/sda3 partition 4200992 17540 -1 /dev/sdb2 partition 8385924 0 -2
What does your performance look like after you close *every* firefox window and thunderbird? [make sure firefox is no longer running.]
Here's my load average as reported by top:
top - 21:02:44 up 1 day, 6:41, 5 users, load average: 0.17, 0.30, 0.73 The 5 users are myself: the main Gnome login session, and 4 Gnome-terminal login shells (I always start the gnome terminal as a login shell (-ls) ) Guy, it is not the system load. Under fc13, even when I had multiple kernel builds going, 6 FF windows, each with 3 to 4 tabs, and Thunderbird running, switching workspaces was snappy.
Something is terribly wrong with Xserver or Gnome, or Ati Radeon Driver, or all 3. What's worse: it will be exceedingly difficult for me to roll back to fc13. Isn't progress wonderful! I hope an Xorg developer sees this!!
On 03/30/2011 12:10 AM, JD wrote:
On 03/29/2011 08:08 PM, Kevin J. Cummings wrote:
On 03/29/2011 10:43 PM, JD wrote:
On 03/29/2011 06:28 PM, Joe Zeff wrote:
On 03/29/2011 05:08 PM, JD wrote:
Can this be attributed to Gnome or to the X server or to the ATI Radeon driver?
I'm using F 14 and Gnome and see no problems even though my mobo's maxed out at 1G RAM. Probably the driver.
Well, it is taking up to 3.5 seconds for the windows in a workspace to get populated and fully visible when I switch to that workspace.
What is the load avg on the system in question? I have seen similar on my system when the load avg starts to climb (anything> 5 is really bad). But, when he load avg is low, redraws should be good.
It used to be almost instantaneous in F13. I have 2GB ram, and 12 GB swap space, but very few apps running. Most of the time I have 6 workspaces, each with a separate FireFox window,
Firefox is a resource *PIG*. Since it is one application, I'd look into how much memory it is using (both in ram and in swap), and whether or not any of its windows are doing anything (like displaying FLASH or active JAVA applets).
and up to 4 4 workspaces, each with a gnome terminal. and 1 workspace with Thunderbird.
How big are your mailboxes? Thunderbird can also slow you down if you have large mailboxes.
Hardly any space is used in swap. To wit:
# swapon -s Filename Type Size Used Priority /dev/sda3 partition 4200992 17540 -1 /dev/sdb2 partition 8385924 0 -2
What does your performance look like after you close *every* firefox window and thunderbird? [make sure firefox is no longer running.]
Here's my load average as reported by top:
top - 21:02:44 up 1 day, 6:41, 5 users, load average: 0.17, 0.30, 0.73 The 5 users are myself: the main Gnome login session, and 4 Gnome-terminal login shells (I always start the gnome terminal as a login shell (-ls) ) Guy, it is not the system load. Under fc13, even when I had multiple kernel builds going, 6 FF windows, each with 3 to 4 tabs, and Thunderbird running, switching workspaces was snappy.
Something is terribly wrong with Xserver or Gnome, or Ati Radeon Driver, or all 3.
On your hardware. I am also using F14 on my laptop (x86_64) with the ATI driver, and I only see the problems you see under high system load, which easily happens with thunderbird open (quite a few *large* mailboxes) and a *lot* of tabs in 1 firefox window. Especially when letting a FLASH window or two run for a couple of hours....
Since I closed firefox (I now use Google chrome sparingly, and close it when I'm done), I'm running *much* better. My load avg hasn't shot up yet (and it should have started doing so already based on my hightly cron jobs!). I'll know more tomorrow morning after I suspend it an restart it.
What's worse: it will be exceedingly difficult for me to roll back to fc13. Isn't progress wonderful! I hope an Xorg developer sees this!!
I don't think they'll be interested unless you can prove its your xorg driver.
Just another thought, how long since you rebooted last? Sometimes xorg updates can require a reboot to work right. When was the last xorg update you installed?
I suspect you have something mis-configured, but I have no clue as to what right now.
On 03/30/2011 02:49 AM, Kevin J. Cummings wrote:
On 03/30/2011 12:10 AM, JD wrote:
On 03/29/2011 08:08 PM, Kevin J. Cummings wrote:
On 03/29/2011 10:43 PM, JD wrote:
On 03/29/2011 06:28 PM, Joe Zeff wrote:
On 03/29/2011 05:08 PM, JD wrote:
I concur that both firefox and TB can be memory pigs. Firefox has had mem leaks forever ... I gave up a long time ago and switched to google chrome (firefox 4 has caught up speed-wise finally but I still prefer chrome)
That aside - for TB please make sure you check a couple of configs.
(1) turn of GLODA it is an IO pig with a terrible design, which can kill your machine as well.
Prefs->Advanced -> General
make sure the Enable Global Search and Destroy thing is unchecked.
(2) Also by default, TB caches local copies of everything - you may want to play with those settings (offline usage).
gene/
On 03/29/2011 11:49 PM, Kevin J. Cummings wrote:
On 03/30/2011 12:10 AM, JD wrote:
On 03/29/2011 08:08 PM, Kevin J. Cummings wrote:
On 03/29/2011 10:43 PM, JD wrote:
On 03/29/2011 06:28 PM, Joe Zeff wrote:
On 03/29/2011 05:08 PM, JD wrote:
Can this be attributed to Gnome or to the X server or to the ATI Radeon driver?
I'm using F 14 and Gnome and see no problems even though my mobo's maxed out at 1G RAM. Probably the driver.
Well, it is taking up to 3.5 seconds for the windows in a workspace to get populated and fully visible when I switch to that workspace.
What is the load avg on the system in question? I have seen similar on my system when the load avg starts to climb (anything> 5 is really bad). But, when he load avg is low, redraws should be good.
It used to be almost instantaneous in F13. I have 2GB ram, and 12 GB swap space, but very few apps running. Most of the time I have 6 workspaces, each with a separate FireFox window,
Firefox is a resource *PIG*. Since it is one application, I'd look into how much memory it is using (both in ram and in swap), and whether or not any of its windows are doing anything (like displaying FLASH or active JAVA applets).
and up to 4 4 workspaces, each with a gnome terminal. and 1 workspace with Thunderbird.
How big are your mailboxes? Thunderbird can also slow you down if you have large mailboxes.
Hardly any space is used in swap. To wit:
# swapon -s Filename Type Size Used Priority /dev/sda3 partition 4200992 17540 -1 /dev/sdb2 partition 8385924 0 -2
What does your performance look like after you close *every* firefox window and thunderbird? [make sure firefox is no longer running.]
Here's my load average as reported by top:
top - 21:02:44 up 1 day, 6:41, 5 users, load average: 0.17, 0.30, 0.73 The 5 users are myself: the main Gnome login session, and 4 Gnome-terminal login shells (I always start the gnome terminal as a login shell (-ls) ) Guy, it is not the system load. Under fc13, even when I had multiple kernel builds going, 6 FF windows, each with 3 to 4 tabs, and Thunderbird running, switching workspaces was snappy.
Something is terribly wrong with Xserver or Gnome, or Ati Radeon Driver, or all 3.
On your hardware. I am also using F14 on my laptop (x86_64) with the ATI driver, and I only see the problems you see under high system load, which easily happens with thunderbird open (quite a few *large* mailboxes) and a *lot* of tabs in 1 firefox window. Especially when letting a FLASH window or two run for a couple of hours....
It is happening right now, and here is the system load: top - 10:07:19 up 1 day, 19:46, 4 users, load average: 0.28, 0.30, 0.16
It has been like this (i.e. the delayed workspace switch) as soon as I loged in 1 day and 19 hours ago!!
Since I closed firefox (I now use Google chrome sparingly, and close it when I'm done), I'm running *much* better. My load avg hasn't shot up yet (and it should have started doing so already based on my hightly cron jobs!). I'll know more tomorrow morning after I suspend it an restart it.
Makes no difference here. Right now, I have no firefox running. And thunderbird's cpu load is too small to be shown in the terminal window in full screen mode (98x31 - I have to use large fonts).
What's worse: it will be exceedingly difficult for me to roll back to fc13. Isn't progress wonderful! I hope an Xorg developer sees this!!
I don't think they'll be interested unless you can prove its your xorg driver.
But how can I prove it? Is there a way to instrument the Xorg driver to leave a timing trail in a large circular buffer for the workspace switch events? and then dump the buffer to a file after N many events?
Just another thought, how long since you rebooted last? Sometimes xorg updates can require a reboot to work right. When was the last xorg update you installed?
See above. Xorg got upgraded to fc14 about 1 day and 22 hours ago.
I suspect you have something mis-configured, but I have no clue as to what right now.
But I did not change any configuration between fc13 and fc14.
On 03/30/2011 01:15 PM, JD wrote:
I suspect you have something mis-configured, but I have no clue as to what right now.
But I did not change any configuration between fc13 and fc14.
Nor did I, but I had *lot's* of problems initially with my working F12/F13 configuration after I switched to F14. Mostly due to changes in the ati driver.
1) I used to have to turn off KMS in order for suspend to work right.
With F14, I had to not disable it in order to prevent a whole list of video problems, including text consoles being corrupt, X hanging completely when it started using the ati driver (I had to use vesa to even boot up using UMS). I was finally convinced that by enabling KMS, things would start working again, and they did, but there was nothing in the upgrade that suggested doing so was the right thing to do.
2) I had all sorts of problems with the xorg configuration file. I had a *very* complicated one because I had changed it continually since FC6. Once I removed most of it, things vastly improved. Its probably a good idea anyways since the advent of the /etc/x11/conf.d stuff. YMMV
So, it might me a good idea to list any anomalies with your configuration, from kernel boot parameters, to xorg.conf stuff so that we can see if you are doing anything that might now be considered problematic. Also, if you could re-state what your ATI hardware is, that could be helpful as well. Is this a desktop or laptop?
On 03/30/2011 10:39 AM, Kevin J. Cummings wrote:
On 03/30/2011 01:15 PM, JD wrote:
I suspect you have something mis-configured, but I have no clue as to what right now.
But I did not change any configuration between fc13 and fc14.
Nor did I, but I had *lot's* of problems initially with my working F12/F13 configuration after I switched to F14. Mostly due to changes in the ati driver.
I used to have to turn off KMS in order for suspend to work right.
With F14, I had to not disable it in order to prevent a whole list of
video problems, including text consoles being corrupt, X hanging completely when it started using the ati driver (I had to use vesa to even boot up using UMS). I was finally convinced that by enabling KMS, things would start working again, and they did, but there was nothing in the upgrade that suggested doing so was the right thing to do.
What is KMS and how do I enable it?
- I had all sorts of problems with the xorg configuration file. I had
a *very* complicated one because I had changed it continually since FC6. Once I removed most of it, things vastly improved. Its probably a good idea anyways since the advent of the /etc/x11/conf.d stuff. YMMV
/etc/X11/xorg.conf.d only contains 00-system-setup-keyboard.conf
(/etc/X11/xorg.conf), I do not see KMS in there at all. How would I enable it?
So, it might me a good idea to list any anomalies with your configuration, from kernel boot parameters, to xorg.conf stuff so that we can see if you are doing anything that might now be considered problematic. Also, if you could re-state what your ATI hardware is, that could be helpful as well. Is this a desktop or laptop?
From lspci: 01:00.0 VGA compatible controller: ATI Technologies Inc RV350 [Mobility Radeon 9600 M10]
From /boot/grub/grub.conf:
title Fedora (2.6.35.6-45.fc14.i686) root (hd0,1) kernel /boot/vmlinuz-2.6.35.6-45.fc14.i686 ro root=UUID=99c4a1b1-99c2-40e6-8d2c-44bba67ad7df nomodeset SYSFONT=latarcyrheb-sun16 LANG=en_US.UTF-8 KEYTABLE=us initrd /boot/initramfs-2.6.35.6-45.fc14.i686.img
And finally /etc/X11/xorg.conf # ls -l /etc/X11/xorg.conf -rw-r--r--. 1 skroot root 4978 Mar 27 18:07 /etc/X11/xorg.conf
As you can see from the date, it was touched during the upgrade to fc14.
# cat /etc/X11/xorg.conf Section "ServerLayout" Identifier "X.org Configured" Screen 0 "Screen0" 0 0 InputDevice "Mouse0" "CorePointer" InputDevice "Keyboard0" "CoreKeyboard" EndSection
Section "Files" ModulePath "/usr/lib/xorg/modules" FontPath "catalogue:/etc/X11/fontpath.d" FontPath "built-ins" EndSection
Section "Module" Load "record" Load "extmod" Load "dri2" Load "dbe" Load "glx" Load "dri" EndSection
Section "InputDevice" Identifier "Keyboard0" Driver "kbd" Option "Protocol" "Standard" Option "XkbLayout" "us" Option "XkbRules" "xfree86" EndSection
Section "InputDevice" Identifier "Mouse0" Driver "mouse" Option "Protocol" "auto" Option "Device" "/dev/input/mice" Option "ZAxisMapping" "4 5 6 7" EndSection
Section "Monitor" Identifier "Monitor0" VendorName "Monitor Vendor" ModelName "Monitor Model" HorizSync 24.0 - 85.0 VertRefresh 48.0 - 76.0 EndSection
Section "Device" ### Available Driver options are:- ### Values: <i>: integer, <f>: float, <bool>: "True"/"False", ### <string>: "String", <freq>: "<f> Hz/kHz/MHz" ### [arg]: arg optional #Option "NoAccel" # [<bool>] #Option "SWcursor" # [<bool>] #Option "Dac6Bit" # [<bool>] #Option "Dac8Bit" # [<bool>] #Option "BusType" # [<str>] #Option "CPPIOMode" # [<bool>] #Option "CPusecTimeout" # <i> #Option "AGPMode" # <i> #Option "AGPFastWrite" # [<bool>] #Option "AGPSize" # <i> #Option "GARTSize" # <i> #Option "RingSize" # <i> #Option "BufferSize" # <i> #Option "EnableDepthMoves" # [<bool>] #Option "EnablePageFlip" # [<bool>] #Option "NoBackBuffer" # [<bool>] #Option "DMAForXv" # [<bool>] #Option "FBTexPercent" # <i> #Option "DepthBits" # <i> #Option "PCIAPERSize" # <i> #Option "AccelDFS" # [<bool>] #Option "IgnoreEDID" # [<bool>] #Option "CustomEDID" # [<str>] #Option "DisplayPriority" # [<str>] #Option "PanelSize" # [<str>] #Option "ForceMinDotClock" # <freq> #Option "ColorTiling" # [<bool>] #Option "VideoKey" # <i> #Option "RageTheatreCrystal" # <i> #Option "RageTheatreTunerPort" # <i> #Option "RageTheatreCompositePort" # <i> #Option "RageTheatreSVideoPort" # <i> #Option "TunerType" # <i> #Option "RageTheatreMicrocPath" # <str> #Option "RageTheatreMicrocType" # <str> #Option "ScalerWidth" # <i> #Option "RenderAccel" # [<bool>] #Option "SubPixelOrder" # [<str>] #Option "ShowCache" # [<bool>] #Option "ClockGating" # [<bool>] #Option "VGAAccess" # [<bool>] #Option "ReverseDDC" # [<bool>] #Option "LVDSProbePLL" # [<bool>] #Option "AccelMethod" # <str> #Option "DRI" # [<bool>] #Option "ConnectorTable" # <str> #Option "DefaultConnectorTable" # [<bool>] #Option "DefaultTMDSPLL" # [<bool>] #Option "TVDACLoadDetect" # [<bool>] #Option "ForceTVOut" # [<bool>] #Option "TVStandard" # <str> #Option "IgnoreLidStatus" # [<bool>] #Option "DefaultTVDACAdj" # [<bool>] #Option "Int10" # [<bool>] #Option "EXAVSync" # [<bool>] #Option "ATOMTVOut" # [<bool>] #Option "R4xxATOM" # [<bool>] #Option "ForceLowPowerMode" # [<bool>] #Option "DynamicPM" # [<bool>] #Option "NewPLL" # [<bool>] #Option "ZaphodHeads" # <str> Identifier "Card0" Driver "radeon" VendorName "ATI Technologies Inc" BoardName "RV350 [Mobility Radeon 9600 M10]" BusID "PCI:1:0:0" EndSection
Section "Screen" Identifier "Screen0" Device "Card0" Monitor "Monitor0" SubSection "Display" Viewport 0 0 Depth 1 EndSubSection SubSection "Display" Viewport 0 0 Depth 4 EndSubSection SubSection "Display" Viewport 0 0 Depth 8 EndSubSection SubSection "Display" Viewport 0 0 Depth 15 EndSubSection SubSection "Display" Viewport 0 0 Depth 16 EndSubSection SubSection "Display" Viewport 0 0 Depth 24 EndSubSection EndSection
On 03/30/2011 01:58 PM, JD wrote:
On 03/30/2011 10:39 AM, Kevin J. Cummings wrote:
On 03/30/2011 01:15 PM, JD wrote:
I suspect you have something mis-configured, but I have no clue as to what right now.
But I did not change any configuration between fc13 and fc14.
Nor did I, but I had *lot's* of problems initially with my working F12/F13 configuration after I switched to F14. Mostly due to changes in the ati driver.
I used to have to turn off KMS in order for suspend to work right.
With F14, I had to not disable it in order to prevent a whole list of
video problems, including text consoles being corrupt, X hanging completely when it started using the ati driver (I had to use vesa to even boot up using UMS). I was finally convinced that by enabling KMS, things would start working again, and they did, but there was nothing in the upgrade that suggested doing so was the right thing to do.
What is KMS and how do I enable it?
Kernel Mode Set. See your "nomodeset" option on your kernel below. Try removing it.
- I had all sorts of problems with the xorg configuration file. I had
a *very* complicated one because I had changed it continually since FC6. Once I removed most of it, things vastly improved. Its probably a good idea anyways since the advent of the /etc/x11/conf.d stuff. YMMV
/etc/X11/xorg.conf.d only contains 00-system-setup-keyboard.conf
(/etc/X11/xorg.conf), I do not see KMS in there at all. How would I enable it?
You enable it by removing the "nomodeset" option from your kernel in grub.
So, it might me a good idea to list any anomalies with your configuration, from kernel boot parameters, to xorg.conf stuff so that we can see if you are doing anything that might now be considered problematic. Also, if you could re-state what your ATI hardware is, that could be helpful as well. Is this a desktop or laptop?
From lspci: 01:00.0 VGA compatible controller: ATI Technologies Inc RV350 [Mobility Radeon 9600 M10]
Just for comparison purposes, mine is an:
01:00.0 VGA compatible controller: ATI Technologies Inc M56P [Radeon Mobility X1600]
From /boot/grub/grub.conf:
title Fedora (2.6.35.6-45.fc14.i686) root (hd0,1) kernel /boot/vmlinuz-2.6.35.6-45.fc14.i686 ro root=UUID=99c4a1b1-99c2-40e6-8d2c-44bba67ad7df nomodeset
^^^^^^^^^
That's the guy!
SYSFONT=latarcyrheb-sun16 LANG=en_US.UTF-8 KEYTABLE=us initrd /boot/initramfs-2.6.35.6-45.fc14.i686.img
And finally /etc/X11/xorg.conf # ls -l /etc/X11/xorg.conf -rw-r--r--. 1 skroot root 4978 Mar 27 18:07 /etc/X11/xorg.conf
As you can see from the date, it was touched during the upgrade to fc14.
1) rename it so X doesn't find it and see what happens upon reboot. (I suggest that you try with "nomodeset" removed from your kernels options in grub.conf) See what X11 does to configure itself. If you know you've configured something that your server needs, you can always add it back in its own file in /etx/x11/xorg.conf.d later. (to me, your xorg.conf looks fairly generic, anyways, besides specifying the obvious.)
# cat /etc/X11/xorg.conf Section "ServerLayout" Identifier "X.org Configured" Screen 0 "Screen0" 0 0 InputDevice "Mouse0" "CorePointer" InputDevice "Keyboard0" "CoreKeyboard" EndSection
Section "Files" ModulePath "/usr/lib/xorg/modules" FontPath "catalogue:/etc/X11/fontpath.d" FontPath "built-ins" EndSection
Section "Module" Load "record" Load "extmod" Load "dri2" Load "dbe" Load "glx" Load "dri" EndSection
Section "InputDevice" Identifier "Keyboard0" Driver "kbd" Option "Protocol" "Standard" Option "XkbLayout" "us" Option "XkbRules" "xfree86" EndSection
Section "InputDevice" Identifier "Mouse0" Driver "mouse" Option "Protocol" "auto" Option "Device" "/dev/input/mice" Option "ZAxisMapping" "4 5 6 7" EndSection
Section "Monitor" Identifier "Monitor0" VendorName "Monitor Vendor" ModelName "Monitor Model" HorizSync 24.0 - 85.0 VertRefresh 48.0 - 76.0 EndSection
Section "Device" ### Available Driver options are:- ### Values: <i>: integer, <f>: float, <bool>: "True"/"False", ### <string>: "String", <freq>: "<f> Hz/kHz/MHz" ### [arg]: arg optional #Option "NoAccel" # [<bool>] #Option "SWcursor" # [<bool>] #Option "Dac6Bit" # [<bool>] #Option "Dac8Bit" # [<bool>] #Option "BusType" # [<str>] #Option "CPPIOMode" # [<bool>] #Option "CPusecTimeout" # <i> #Option "AGPMode" # <i> #Option "AGPFastWrite" # [<bool>] #Option "AGPSize" # <i> #Option "GARTSize" # <i> #Option "RingSize" # <i> #Option "BufferSize" # <i> #Option "EnableDepthMoves" # [<bool>] #Option "EnablePageFlip" # [<bool>] #Option "NoBackBuffer" # [<bool>] #Option "DMAForXv" # [<bool>] #Option "FBTexPercent" # <i> #Option "DepthBits" # <i> #Option "PCIAPERSize" # <i> #Option "AccelDFS" # [<bool>] #Option "IgnoreEDID" # [<bool>] #Option "CustomEDID" # [<str>] #Option "DisplayPriority" # [<str>] #Option "PanelSize" # [<str>] #Option "ForceMinDotClock" # <freq> #Option "ColorTiling" # [<bool>] #Option "VideoKey" # <i> #Option "RageTheatreCrystal" # <i> #Option "RageTheatreTunerPort" # <i> #Option "RageTheatreCompositePort" # <i> #Option "RageTheatreSVideoPort" # <i> #Option "TunerType" # <i> #Option "RageTheatreMicrocPath" # <str> #Option "RageTheatreMicrocType" # <str> #Option "ScalerWidth" # <i> #Option "RenderAccel" # [<bool>] #Option "SubPixelOrder" # [<str>] #Option "ShowCache" # [<bool>] #Option "ClockGating" # [<bool>] #Option "VGAAccess" # [<bool>] #Option "ReverseDDC" # [<bool>] #Option "LVDSProbePLL" # [<bool>] #Option "AccelMethod" # <str> #Option "DRI" # [<bool>] #Option "ConnectorTable" # <str> #Option "DefaultConnectorTable" # [<bool>] #Option "DefaultTMDSPLL" # [<bool>] #Option "TVDACLoadDetect" # [<bool>] #Option "ForceTVOut" # [<bool>] #Option "TVStandard" # <str> #Option "IgnoreLidStatus" # [<bool>] #Option "DefaultTVDACAdj" # [<bool>] #Option "Int10" # [<bool>] #Option "EXAVSync" # [<bool>] #Option "ATOMTVOut" # [<bool>] #Option "R4xxATOM" # [<bool>] #Option "ForceLowPowerMode" # [<bool>] #Option "DynamicPM" # [<bool>] #Option "NewPLL" # [<bool>] #Option "ZaphodHeads" # <str> Identifier "Card0" Driver "radeon" VendorName "ATI Technologies Inc" BoardName "RV350 [Mobility Radeon 9600 M10]" BusID "PCI:1:0:0" EndSection
Section "Screen" Identifier "Screen0" Device "Card0" Monitor "Monitor0" SubSection "Display" Viewport 0 0 Depth 1 EndSubSection SubSection "Display" Viewport 0 0 Depth 4 EndSubSection SubSection "Display" Viewport 0 0 Depth 8 EndSubSection SubSection "Display" Viewport 0 0 Depth 15 EndSubSection SubSection "Display" Viewport 0 0 Depth 16 EndSubSection SubSection "Display" Viewport 0 0 Depth 24 EndSubSection EndSection
On 03/30/2011 02:52 PM, Joe Zeff wrote:
On 03/30/2011 11:45 AM, Kevin J. Cummings wrote:
You enable it by removing the "nomodeset" option from your kernel in grub.
Just to be safe, do this by editing the line at boot time. If it works, you can always make it permanent; if not, all you need to do is reboot normally.
I usually edit it in /etc/grub.conf, then if it doesn't work, I can choose to edit it back in at boot time. B^) 6 of 1, 1/2 dozen of the other. Then again, my grub.conf configures me enough time to decide to edit or not. YMMV.
On 03/30/2011 11:45 AM, Kevin J. Cummings wrote:
On 03/30/2011 01:58 PM, JD wrote:
On 03/30/2011 10:39 AM, Kevin J. Cummings wrote:
On 03/30/2011 01:15 PM, JD wrote:
I suspect you have something mis-configured, but I have no clue as to what right now.
But I did not change any configuration between fc13 and fc14.
Nor did I, but I had *lot's* of problems initially with my working F12/F13 configuration after I switched to F14. Mostly due to changes in the ati driver.
I used to have to turn off KMS in order for suspend to work right.
With F14, I had to not disable it in order to prevent a whole list of
video problems, including text consoles being corrupt, X hanging completely when it started using the ati driver (I had to use vesa to even boot up using UMS). I was finally convinced that by enabling KMS, things would start working again, and they did, but there was nothing in the upgrade that suggested doing so was the right thing to do.
What is KMS and how do I enable it?
Kernel Mode Set. See your "nomodeset" option on your kernel below. Try removing it.
- I had all sorts of problems with the xorg configuration file. I had
a *very* complicated one because I had changed it continually since FC6. Once I removed most of it, things vastly improved. Its probably a good idea anyways since the advent of the /etc/x11/conf.d stuff. YMMV
/etc/X11/xorg.conf.d only contains 00-system-setup-keyboard.conf
(/etc/X11/xorg.conf), I do not see KMS in there at all. How would I enable it?
You enable it by removing the "nomodeset" option from your kernel in grub.
So, it might me a good idea to list any anomalies with your configuration, from kernel boot parameters, to xorg.conf stuff so that we can see if you are doing anything that might now be considered problematic. Also, if you could re-state what your ATI hardware is, that could be helpful as well. Is this a desktop or laptop?
From lspci: 01:00.0 VGA compatible controller: ATI Technologies Inc RV350 [Mobility Radeon 9600 M10]
Just for comparison purposes, mine is an:
01:00.0 VGA compatible controller: ATI Technologies Inc M56P [Radeon Mobility X1600] From /boot/grub/grub.conf:
title Fedora (2.6.35.6-45.fc14.i686) root (hd0,1) kernel /boot/vmlinuz-2.6.35.6-45.fc14.i686 ro root=UUID=99c4a1b1-99c2-40e6-8d2c-44bba67ad7df nomodeset
^^^^^^^^^That's the guy!
SYSFONT=latarcyrheb-sun16 LANG=en_US.UTF-8 KEYTABLE=us initrd /boot/initramfs-2.6.35.6-45.fc14.i686.img
And finally /etc/X11/xorg.conf # ls -l /etc/X11/xorg.conf -rw-r--r--. 1 skroot root 4978 Mar 27 18:07 /etc/X11/xorg.conf
As you can see from the date, it was touched during the upgrade to fc14.
- rename it so X doesn't find it and see what happens upon reboot. (I suggest that you try with "nomodeset" removed from your kernels options in grub.conf) See what X11 does to configure itself. If you know you've configured something that your server needs, you can always add it back in its own file in /etx/x11/xorg.conf.d later. (to me, your xorg.conf looks fairly generic, anyways, besides specifying the obvious.)
OK, I removed nomodeset and I renamed /etc/X11/xorg.conf and the workspace switchover is now as crisp as before. With a caveat! dmesg shows:
Mar 30 14:00:08 localhost kernel: [drm:drm_mode_getfb] *ERROR* invalid framebuffer id
Not sure what that means. Does it have to do with the FB driver not being configured?
here's the rest of the drm related messages:
Mar 30 13:59:10 localhost kernel: [drm] Initialized drm 1.1.0 20060810 Mar 30 13:59:10 localhost kernel: [drm] radeon defaulting to kernel modesetting. Mar 30 13:59:10 localhost kernel: [drm] radeon kernel modesetting enabled. Mar 30 13:59:10 localhost kernel: radeon 0000:01:00.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16 Mar 30 13:59:10 localhost kernel: [drm] initializing kernel modesetting (RV350 0x1002:0x4E50). Mar 30 13:59:10 localhost kernel: [drm] register mmio base: 0xFEAF0000 Mar 30 13:59:10 localhost kernel: [drm] register mmio size: 65536 Mar 30 13:59:10 localhost kernel: [drm:radeon_agp_init] *ERROR* Unable to acquire AGP: -19 Mar 30 13:59:10 localhost kernel: [drm] Forcing AGP to PCI mode Mar 30 13:59:10 localhost kernel: [drm] Generation 2 PCI interface, using max accessible memory Mar 30 13:59:10 localhost kernel: radeon 0000:01:00.0: VRAM: 128M 0x00000000F0000000 - 0x00000000F7FFFFFF (128M used) Mar 30 13:59:10 localhost kernel: radeon 0000:01:00.0: GTT: 512M 0x00000000D0000000 - 0x00000000EFFFFFFF Mar 30 13:59:10 localhost kernel: [drm] Supports vblank timestamp caching Rev 1 (10.10.2010). Mar 30 13:59:10 localhost kernel: [drm] Driver supports precise vblank timestamp query. Mar 30 13:59:10 localhost kernel: [drm] radeon: irq initialized. Mar 30 13:59:10 localhost kernel: [drm] Detected VRAM RAM=128M, BAR=128M Mar 30 13:59:10 localhost kernel: [drm] RAM width 128bits DDR Mar 30 13:59:10 localhost kernel: [TTM] Zone kernel: Available graphics memory: 442682 kiB. Mar 30 13:59:10 localhost kernel: [TTM] Zone highmem: Available graphics memory: 1036510 kiB. Mar 30 13:59:10 localhost kernel: [TTM] Initializing pool allocator. Mar 30 13:59:10 localhost kernel: [drm] radeon: 128M of VRAM memory ready Mar 30 13:59:10 localhost kernel: [drm] radeon: 512M of GTT memory ready. Mar 30 13:59:10 localhost kernel: [drm] GART: num cpu pages 131072, num gpu pages 131072 Mar 30 13:59:10 localhost kernel: [drm] radeon: 1 quad pipes, 1 Z pipes initialized. Mar 30 13:59:10 localhost kernel: radeon 0000:01:00.0: WB enabled Mar 30 13:59:10 localhost kernel: [drm] Loading R300 Microcode Mar 30 13:59:10 localhost kernel: [drm] radeon: ring at 0x00000000D0001000 Mar 30 13:59:10 localhost kernel: [drm] ring test succeeded in 2 usecs Mar 30 13:59:10 localhost kernel: [drm] radeon: ib pool ready. Mar 30 13:59:10 localhost kernel: [drm] ib test succeeded in 0 usecs Mar 30 13:59:10 localhost kernel: [drm] Panel ID String: Samsung LTN154X1 WXGA Mar 30 13:59:10 localhost kernel: [drm] Panel Size 1280x800 Mar 30 13:59:10 localhost kernel: [drm] Radeon Display Connectors Mar 30 13:59:10 localhost kernel: [drm] Connector 0: Mar 30 13:59:10 localhost kernel: [drm] VGA Mar 30 13:59:10 localhost kernel: [drm] DDC: 0x60 0x60 0x60 0x60 0x60 0x60 0x60 0x60 Mar 30 13:59:10 localhost kernel: [drm] Encoders: Mar 30 13:59:10 localhost kernel: [drm] CRT1: INTERNAL_DAC1 Mar 30 13:59:10 localhost kernel: [drm] Connector 1: Mar 30 13:59:10 localhost kernel: [drm] LVDS Mar 30 13:59:10 localhost kernel: [drm] Encoders: Mar 30 13:59:10 localhost kernel: [drm] LCD1: INTERNAL_LVDS Mar 30 13:59:10 localhost kernel: [drm] Connector 2: Mar 30 13:59:10 localhost kernel: [drm] S-video Mar 30 13:59:10 localhost kernel: [drm] Encoders: Mar 30 13:59:10 localhost kernel: [drm] TV1: INTERNAL_DAC2 Mar 30 13:59:10 localhost kernel: [drm] radeon: power management initialized Mar 30 13:59:10 localhost kernel: [drm] fb mappable at 0xF0040000 Mar 30 13:59:10 localhost kernel: [drm] vram apper at 0xF0000000 Mar 30 13:59:10 localhost kernel: [drm] size 4096000 Mar 30 13:59:10 localhost kernel: [drm] fb depth is 24 Mar 30 13:59:10 localhost kernel: [drm] pitch is 5120 Mar 30 13:59:10 localhost kernel: fb0: radeondrmfb frame buffer device Mar 30 13:59:10 localhost kernel: drm: registered panic notifier Mar 30 13:59:10 localhost kernel: [drm] Initialized radeon 2.8.0 20080528 for 0000:01:00.0 on minor 0 Mar 30 14:00:08 localhost kernel: [drm:drm_mode_getfb] *ERROR* invalid framebuffer id
Since last night I'm having these messages too on my laptop:
kernel: [ 388.964307] [drm:drm_mode_getfb] *ERROR* invalid framebuffer id
CPU gets really loaded and top says it's Xorg who os eating the CPU.
Any ideas? Couldn't find anything on bugzilla and no updates available, not even on *testing
2011/3/30 JD jd1008@gmail.com:
On 03/30/2011 11:45 AM, Kevin J. Cummings wrote:
On 03/30/2011 01:58 PM, JD wrote:
On 03/30/2011 10:39 AM, Kevin J. Cummings wrote:
On 03/30/2011 01:15 PM, JD wrote:
I suspect you have something mis-configured, but I have no clue as to what right now.
But I did not change any configuration between fc13 and fc14.
Nor did I, but I had *lot's* of problems initially with my working F12/F13 configuration after I switched to F14. Mostly due to changes in the ati driver.
- I used to have to turn off KMS in order for suspend to work right.
With F14, I had to not disable it in order to prevent a whole list of video problems, including text consoles being corrupt, X hanging completely when it started using the ati driver (I had to use vesa to even boot up using UMS). I was finally convinced that by enabling KMS, things would start working again, and they did, but there was nothing in the upgrade that suggested doing so was the right thing to do.
What is KMS and how do I enable it?
Kernel Mode Set. See your "nomodeset" option on your kernel below. Try removing it.
- I had all sorts of problems with the xorg configuration file. I had
a *very* complicated one because I had changed it continually since FC6. Once I removed most of it, things vastly improved. Its probably a good idea anyways since the advent of the /etc/x11/conf.d stuff. YMMV
/etc/X11/xorg.conf.d only contains 00-system-setup-keyboard.conf
(/etc/X11/xorg.conf), I do not see KMS in there at all. How would I enable it?
You enable it by removing the "nomodeset" option from your kernel in grub.
So, it might me a good idea to list any anomalies with your configuration, from kernel boot parameters, to xorg.conf stuff so that we can see if you are doing anything that might now be considered problematic. Also, if you could re-state what your ATI hardware is, that could be helpful as well. Is this a desktop or laptop?
From lspci: 01:00.0 VGA compatible controller: ATI Technologies Inc RV350 [Mobility Radeon 9600 M10]
Just for comparison purposes, mine is an:
01:00.0 VGA compatible controller: ATI Technologies Inc M56P [Radeon Mobility X1600] From /boot/grub/grub.conf:
title Fedora (2.6.35.6-45.fc14.i686) root (hd0,1) kernel /boot/vmlinuz-2.6.35.6-45.fc14.i686 ro root=UUID=99c4a1b1-99c2-40e6-8d2c-44bba67ad7df nomodeset
^^^^^^^^^
That's the guy!
SYSFONT=latarcyrheb-sun16 LANG=en_US.UTF-8 KEYTABLE=us initrd /boot/initramfs-2.6.35.6-45.fc14.i686.img
And finally /etc/X11/xorg.conf # ls -l /etc/X11/xorg.conf -rw-r--r--. 1 skroot root 4978 Mar 27 18:07 /etc/X11/xorg.conf
As you can see from the date, it was touched during the upgrade to fc14.
- rename it so X doesn't find it and see what happens upon reboot.
(I suggest that you try with "nomodeset" removed from your kernels options in grub.conf) See what X11 does to configure itself. If you know you've configured something that your server needs, you can always add it back in its own file in /etx/x11/xorg.conf.d later. (to me, your xorg.conf looks fairly generic, anyways, besides specifying the obvious.)
OK, I removed nomodeset and I renamed /etc/X11/xorg.conf and the workspace switchover is now as crisp as before. With a caveat! dmesg shows:
Mar 30 14:00:08 localhost kernel: [drm:drm_mode_getfb] *ERROR* invalid framebuffer id
Not sure what that means. Does it have to do with the FB driver not being configured?
here's the rest of the drm related messages:
Mar 30 13:59:10 localhost kernel: [drm] Initialized drm 1.1.0 20060810 Mar 30 13:59:10 localhost kernel: [drm] radeon defaulting to kernel modesetting. Mar 30 13:59:10 localhost kernel: [drm] radeon kernel modesetting enabled. Mar 30 13:59:10 localhost kernel: radeon 0000:01:00.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16 Mar 30 13:59:10 localhost kernel: [drm] initializing kernel modesetting (RV350 0x1002:0x4E50). Mar 30 13:59:10 localhost kernel: [drm] register mmio base: 0xFEAF0000 Mar 30 13:59:10 localhost kernel: [drm] register mmio size: 65536 Mar 30 13:59:10 localhost kernel: [drm:radeon_agp_init] *ERROR* Unable to acquire AGP: -19 Mar 30 13:59:10 localhost kernel: [drm] Forcing AGP to PCI mode Mar 30 13:59:10 localhost kernel: [drm] Generation 2 PCI interface, using max accessible memory Mar 30 13:59:10 localhost kernel: radeon 0000:01:00.0: VRAM: 128M 0x00000000F0000000 - 0x00000000F7FFFFFF (128M used) Mar 30 13:59:10 localhost kernel: radeon 0000:01:00.0: GTT: 512M 0x00000000D0000000 - 0x00000000EFFFFFFF Mar 30 13:59:10 localhost kernel: [drm] Supports vblank timestamp caching Rev 1 (10.10.2010). Mar 30 13:59:10 localhost kernel: [drm] Driver supports precise vblank timestamp query. Mar 30 13:59:10 localhost kernel: [drm] radeon: irq initialized. Mar 30 13:59:10 localhost kernel: [drm] Detected VRAM RAM=128M, BAR=128M Mar 30 13:59:10 localhost kernel: [drm] RAM width 128bits DDR Mar 30 13:59:10 localhost kernel: [TTM] Zone kernel: Available graphics memory: 442682 kiB. Mar 30 13:59:10 localhost kernel: [TTM] Zone highmem: Available graphics memory: 1036510 kiB. Mar 30 13:59:10 localhost kernel: [TTM] Initializing pool allocator. Mar 30 13:59:10 localhost kernel: [drm] radeon: 128M of VRAM memory ready Mar 30 13:59:10 localhost kernel: [drm] radeon: 512M of GTT memory ready. Mar 30 13:59:10 localhost kernel: [drm] GART: num cpu pages 131072, num gpu pages 131072 Mar 30 13:59:10 localhost kernel: [drm] radeon: 1 quad pipes, 1 Z pipes initialized. Mar 30 13:59:10 localhost kernel: radeon 0000:01:00.0: WB enabled Mar 30 13:59:10 localhost kernel: [drm] Loading R300 Microcode Mar 30 13:59:10 localhost kernel: [drm] radeon: ring at 0x00000000D0001000 Mar 30 13:59:10 localhost kernel: [drm] ring test succeeded in 2 usecs Mar 30 13:59:10 localhost kernel: [drm] radeon: ib pool ready. Mar 30 13:59:10 localhost kernel: [drm] ib test succeeded in 0 usecs Mar 30 13:59:10 localhost kernel: [drm] Panel ID String: Samsung LTN154X1 WXGA Mar 30 13:59:10 localhost kernel: [drm] Panel Size 1280x800 Mar 30 13:59:10 localhost kernel: [drm] Radeon Display Connectors Mar 30 13:59:10 localhost kernel: [drm] Connector 0: Mar 30 13:59:10 localhost kernel: [drm] VGA Mar 30 13:59:10 localhost kernel: [drm] DDC: 0x60 0x60 0x60 0x60 0x60 0x60 0x60 0x60 Mar 30 13:59:10 localhost kernel: [drm] Encoders: Mar 30 13:59:10 localhost kernel: [drm] CRT1: INTERNAL_DAC1 Mar 30 13:59:10 localhost kernel: [drm] Connector 1: Mar 30 13:59:10 localhost kernel: [drm] LVDS Mar 30 13:59:10 localhost kernel: [drm] Encoders: Mar 30 13:59:10 localhost kernel: [drm] LCD1: INTERNAL_LVDS Mar 30 13:59:10 localhost kernel: [drm] Connector 2: Mar 30 13:59:10 localhost kernel: [drm] S-video Mar 30 13:59:10 localhost kernel: [drm] Encoders: Mar 30 13:59:10 localhost kernel: [drm] TV1: INTERNAL_DAC2 Mar 30 13:59:10 localhost kernel: [drm] radeon: power management initialized Mar 30 13:59:10 localhost kernel: [drm] fb mappable at 0xF0040000 Mar 30 13:59:10 localhost kernel: [drm] vram apper at 0xF0000000 Mar 30 13:59:10 localhost kernel: [drm] size 4096000 Mar 30 13:59:10 localhost kernel: [drm] fb depth is 24 Mar 30 13:59:10 localhost kernel: [drm] pitch is 5120 Mar 30 13:59:10 localhost kernel: fb0: radeondrmfb frame buffer device Mar 30 13:59:10 localhost kernel: drm: registered panic notifier Mar 30 13:59:10 localhost kernel: [drm] Initialized radeon 2.8.0 20080528 for 0000:01:00.0 on minor 0 Mar 30 14:00:08 localhost kernel: [drm:drm_mode_getfb] *ERROR* invalid framebuffer id
-- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
-
Genes MailLists -
JD -
Joe Zeff -
Kevin Cummings -
Martín Marqués