| 2008-10-16 13:35:05 |
Pat Double |
bug |
|
|
added bug |
| 2008-10-16 13:35:05 |
Pat Double |
bug |
|
|
added attachment 'jockey-hardware-ids.txt' (jockey-gtk --hardware-ids) |
| 2008-10-16 19:41:10 |
Martin Pitt |
jockey: status |
New |
Triaged |
|
| 2008-10-16 19:41:10 |
Martin Pitt |
jockey: bugtargetdisplayname |
jockey (Ubuntu) |
fglrx-installer (Ubuntu) |
|
| 2008-10-16 19:41:10 |
Martin Pitt |
jockey: bugtargetname |
jockey (Ubuntu) |
fglrx-installer (Ubuntu) |
|
| 2008-10-16 19:41:10 |
Martin Pitt |
jockey: statusexplanation |
|
modalias:pci:v00001002d00004E50sv00001028sd0000017Cbc03sc00i00
modalias
Indeed the current /usr/share/jockey/modaliases/fglrx-modules.alias.override does not contain this model. If you confirm that your card works with fglrx, then the list shuold be updated to include this. Thanks! |
|
| 2008-10-16 19:41:10 |
Martin Pitt |
jockey: title |
Bug #284408 in jockey (Ubuntu): "jockey does not offer fglrx for ATI Radeon Mobility 9700" |
Bug #284408 in fglrx-installer (Ubuntu): "jockey does not offer fglrx for ATI Radeon Mobility 9700" |
|
| 2008-10-16 20:53:26 |
Pat Double |
bug |
|
|
added attachment 'Xorg.0.log.baseconf-with-fglrx' (/var/log/Xorg.0.log) |
| 2008-10-17 05:43:40 |
Bryce Harrington |
bug |
|
|
added attachment 'index.html' (user manual) |
| 2008-10-17 05:44:20 |
Bryce Harrington |
fglrx-installer: importance |
Undecided |
Medium |
|
| 2008-10-17 05:44:20 |
Bryce Harrington |
fglrx-installer: statusexplanation |
modalias:pci:v00001002d00004E50sv00001028sd0000017Cbc03sc00i00
modalias
Indeed the current /usr/share/jockey/modaliases/fglrx-modules.alias.override does not contain this model. If you confirm that your card works with fglrx, then the list shuold be updated to include this. Thanks! |
|
|
| 2008-10-28 19:21:08 |
Axel Kellermann |
bug |
|
|
added attachment 'dmesg.txt' (dmesg.txt) |
| 2008-10-29 18:13:07 |
Mario Limonciello |
title |
jockey does not offer fglrx for ATI Radeon Mobility 9700 |
r3xx Hardware does not work with fglrx |
|
| 2008-10-29 18:15:40 |
Mario Limonciello |
description |
I am using 8.10 beta updated only a few minutes before this filing report. I was expecting jockey to offer fglrx for my Radeon Mobility 9700 but it does not. I know that the fglrx driver does support this card. I have the following packages installed:
jockey-gtk 0.5~beta2-0ubuntu3
fglrx-modaliases 2:8.543-0ubuntu1 |
Using fglrx-installer 2:8.543-0ubuntu4, r3xx hardware such as Radeon 9500, Mobility Radeon 9700 and similar don't work.
They are not explicitly listed in the modaliases, so they will not be offered by Jockey. In the past, this hardware did work with the fglrx driver. Now the fglrx driver indicates memory errors when trying to load. |
|
| 2008-10-29 18:16:36 |
Mario Limonciello |
description |
Using fglrx-installer 2:8.543-0ubuntu4, r3xx hardware such as Radeon 9500, Mobility Radeon 9700 and similar don't work.
They are not explicitly listed in the modaliases, so they will not be offered by Jockey. In the past, this hardware did work with the fglrx driver. Now the fglrx driver indicates memory errors when trying to load. |
Using fglrx-installer 2:8.543-0ubuntu4, r3xx hardware such as Radeon 9500, Mobility Radeon 9700 and similar don't work.
They are not explicitly listed in the modaliases, so they will not be offered by Jockey. In the past, this hardware did work with the fglrx driver. Now the fglrx driver indicates memory errors when trying to load.
Here is a snippet of what the memory error will look like:
[ 1024.699204] [fglrx] Maximum main memory to use for locked dma buffers: 1169 MBytes.
[ 1024.700616] [fglrx:drm_alloc] *ERROR* [driver] Allocating 0 bytes
[ 1024.700683] [fglrx:firegl_init_device_list] *ERROR* Out of memory when allocating device heads
[ 1024.700757] [fglrx:firegl_init_module] *ERROR* firegl_init_devices failed |
|
| 2008-10-29 18:17:51 |
Mario Limonciello |
bug |
|
|
assigned to ubuntu-release-notes |
| 2008-10-29 18:18:10 |
Mario Limonciello |
bug |
|
|
assigned to update-manager |
| 2008-10-29 18:22:10 |
Mario Limonciello |
ubuntu-release-notes: status |
New |
Fix Released |
|
| 2008-10-29 18:22:10 |
Mario Limonciello |
ubuntu-release-notes: assignee |
|
superm1 |
|
| 2008-10-29 18:22:10 |
Mario Limonciello |
ubuntu-release-notes: statusexplanation |
|
|
|
| 2008-10-29 18:40:13 |
Mario Limonciello |
fglrx-installer: importance |
Medium |
High |
|
| 2008-10-30 19:59:06 |
Bryce Harrington |
bug |
|
|
assigned to fglrx |
| 2008-10-30 20:01:02 |
Bryce Harrington |
fglrx: status |
New |
Triaged |
|
| 2008-10-30 20:01:02 |
Bryce Harrington |
fglrx: importance |
Undecided |
High |
|
| 2008-10-30 20:01:02 |
Bryce Harrington |
fglrx: statusexplanation |
|
|
|
| 2008-11-04 10:12:34 |
Michael Vogt |
update-manager: status |
New |
In Progress |
|
| 2008-11-04 10:12:34 |
Michael Vogt |
update-manager: assignee |
|
mvo |
|
| 2008-11-04 10:12:34 |
Michael Vogt |
update-manager: importance |
Undecided |
Medium |
|
| 2008-11-04 10:12:34 |
Michael Vogt |
update-manager: statusexplanation |
|
|
|
| 2008-11-04 10:12:34 |
Michael Vogt |
update-manager: milestone |
|
intrepid-updates |
|
| 2008-11-04 10:13:18 |
Michael Vogt |
update-manager: status |
New |
Invalid |
|
| 2008-11-04 10:13:18 |
Michael Vogt |
update-manager: statusexplanation |
|
|
|
| 2008-11-04 10:18:16 |
Michael Vogt |
description |
Using fglrx-installer 2:8.543-0ubuntu4, r3xx hardware such as Radeon 9500, Mobility Radeon 9700 and similar don't work.
They are not explicitly listed in the modaliases, so they will not be offered by Jockey. In the past, this hardware did work with the fglrx driver. Now the fglrx driver indicates memory errors when trying to load.
Here is a snippet of what the memory error will look like:
[ 1024.699204] [fglrx] Maximum main memory to use for locked dma buffers: 1169 MBytes.
[ 1024.700616] [fglrx:drm_alloc] *ERROR* [driver] Allocating 0 bytes
[ 1024.700683] [fglrx:firegl_init_device_list] *ERROR* Out of memory when allocating device heads
[ 1024.700757] [fglrx:firegl_init_module] *ERROR* firegl_init_devices failed |
Using fglrx-installer 2:8.543-0ubuntu4, r3xx hardware such as Radeon 9500, Mobility Radeon 9700 and similar don't work.
TEST CASE:
1. install hardy on a system with a r3xx hardware and fglrx installed and in use
2. run a release-upgrade (e.g. via update-manager - ensure that normal upgrades are enabled via the "software sources" application)
3. verify that the upgrade summary dialog (the final confirmation) does not list fglrx for removal
4. (optional) run the upgrade and verify that X comes up in failsafe mode
5. run the release upgrade via "update-manager --proposed"
6. verify that a dialog comes up that asks you to remove fglrx
7. verify in the final confirmation screen that fglrx is marked for removal
8. perform the upgrade and verify that X comes up normally and that the driver is "ati" now (in /etc/X11/xorg.conf)
They are not explicitly listed in the modaliases, so they will not be offered by Jockey. In the past, this hardware did work with the fglrx driver. Now the fglrx driver indicates memory errors when trying to load.
Here is a snippet of what the memory error will look like:
[ 1024.699204] [fglrx] Maximum main memory to use for locked dma buffers: 1169 MBytes.
[ 1024.700616] [fglrx:drm_alloc] *ERROR* [driver] Allocating 0 bytes
[ 1024.700683] [fglrx:firegl_init_device_list] *ERROR* Out of memory when allocating device heads
[ 1024.700757] [fglrx:firegl_init_module] *ERROR* firegl_init_devices failed |
|
| 2008-11-04 19:04:20 |
Martin Pitt |
fglrx-installer: status |
New |
Fix Committed |
|
| 2008-11-04 19:04:20 |
Martin Pitt |
fglrx-installer: statusexplanation |
|
|
|
| 2008-11-04 19:04:54 |
Martin Pitt |
update-manager: status |
New |
Fix Committed |
|
| 2008-11-04 19:04:54 |
Martin Pitt |
update-manager: statusexplanation |
|
|
|
| 2008-11-04 19:05:59 |
Martin Pitt |
bug |
|
|
added subscriber SRU Verification |
| 2008-11-04 19:14:30 |
Martin Pitt |
fglrx-installer: status |
Fix Committed |
Triaged |
|
| 2008-11-06 01:50:22 |
Bryce Harrington |
title |
r3xx Hardware does not work with fglrx |
r3xx Hardware does not work with fglrx [EPR#257839] |
|
| 2008-11-06 03:03:36 |
Bryce Harrington |
fglrx: importance |
High |
Medium |
|
| 2008-11-10 07:52:56 |
Martin Pitt |
update-manager: status |
Fix Committed |
Fix Released |
|
| 2008-11-10 07:52:56 |
Martin Pitt |
update-manager: statusexplanation |
|
update-manager copied to intrepid-updates. Michael, please upload the fix to jaunty, too. |
|
| 2008-11-10 07:53:13 |
Martin Pitt |
update-manager: statusexplanation |
update-manager copied to intrepid-updates. Michael, please upload the fix to jaunty, too. |
|
|
| 2008-11-10 07:53:13 |
Martin Pitt |
update-manager: milestone |
|
intrepid-updates |
|
| 2008-11-10 07:54:33 |
Martin Pitt |
update-manager: statusexplanation |
|
|
|
| 2008-11-10 07:54:33 |
Martin Pitt |
update-manager: milestone |
intrepid-updates |
jaunty-alpha-1 |
|
| 2008-11-14 04:40:32 |
Mario Limonciello |
fglrx-installer: status |
Triaged |
Fix Released |
|
| 2008-11-14 04:40:32 |
Mario Limonciello |
fglrx-installer: statusexplanation |
|
Closing the jaunty task since 8-11 is in Jaunty now. |
|
| 2008-11-14 04:43:30 |
Mario Limonciello |
description |
Using fglrx-installer 2:8.543-0ubuntu4, r3xx hardware such as Radeon 9500, Mobility Radeon 9700 and similar don't work.
TEST CASE:
1. install hardy on a system with a r3xx hardware and fglrx installed and in use
2. run a release-upgrade (e.g. via update-manager - ensure that normal upgrades are enabled via the "software sources" application)
3. verify that the upgrade summary dialog (the final confirmation) does not list fglrx for removal
4. (optional) run the upgrade and verify that X comes up in failsafe mode
5. run the release upgrade via "update-manager --proposed"
6. verify that a dialog comes up that asks you to remove fglrx
7. verify in the final confirmation screen that fglrx is marked for removal
8. perform the upgrade and verify that X comes up normally and that the driver is "ati" now (in /etc/X11/xorg.conf)
They are not explicitly listed in the modaliases, so they will not be offered by Jockey. In the past, this hardware did work with the fglrx driver. Now the fglrx driver indicates memory errors when trying to load.
Here is a snippet of what the memory error will look like:
[ 1024.699204] [fglrx] Maximum main memory to use for locked dma buffers: 1169 MBytes.
[ 1024.700616] [fglrx:drm_alloc] *ERROR* [driver] Allocating 0 bytes
[ 1024.700683] [fglrx:firegl_init_device_list] *ERROR* Out of memory when allocating device heads
[ 1024.700757] [fglrx:firegl_init_module] *ERROR* firegl_init_devices failed |
Using fglrx-installer 2:8.543-0ubuntu4, r3xx hardware such as Radeon 9500, Mobility Radeon 9700 and similar don't work
They are not explicitly listed in the modaliases, so they will not be offered by Jockey. In the past, this hardware did work with the fglrx driver. Now the fglrx driver indicates memory errors when trying to load.
Here is a snippet of what the memory error will look like:
[ 1024.699204] [fglrx] Maximum main memory to use for locked dma buffers: 1169 MBytes.
[ 1024.700616] [fglrx:drm_alloc] *ERROR* [driver] Allocating 0 bytes
[ 1024.700683] [fglrx:firegl_init_device_list] *ERROR* Out of memory when allocating device heads
[ 1024.700757] [fglrx:firegl_init_module] *ERROR* firegl_init_devices failed
TEST CASE:
1. Install intrepid w/ r3xx hardware.
2. attempt to activate fglrx and reboot verifying unable to start X
3. Activate intrepid-proposed
4. update to new fglrx version, verify that X starts up properly |
|
| 2008-11-14 04:44:03 |
Mario Limonciello |
fglrx-installer: milestone |
|
intrepid-updates |
|
| 2008-11-14 10:13:30 |
Martin Pitt |
fglrx-installer: status |
Triaged |
Fix Committed |
|
| 2008-11-14 10:13:30 |
Martin Pitt |
fglrx-installer: milestone |
intrepid-updates |
|
|
| 2008-11-14 17:02:14 |
Matthew Helmke |
bug |
|
|
added attachment 'xorglog' (as requested) |
| 2008-11-16 20:57:34 |
W. Prins |
bug |
|
|
added attachment 'Xorg.0.log.811_8552_fromati.failed' (X log of current crashing behaviour with the 8.11 Catalyst driver from ATI's website.) |
| 2008-11-20 15:54:58 |
Michael Vogt |
update-manager: status |
In Progress |
Fix Committed |
|
| 2008-11-20 15:54:58 |
Michael Vogt |
update-manager: statusexplanation |
|
update-manager in jaunty will check for r300 modaliases too. Its not very urgend as I don't excpet that the fglrx in intrepid and jaunty are actually that different, but I added it for good measure. |
|
| 2008-11-25 23:08:55 |
Steve Langasek |
update-manager: statusexplanation |
update-manager in jaunty will check for r300 modaliases too. Its not very urgend as I don't excpet that the fglrx in intrepid and jaunty are actually that different, but I added it for good measure. |
|
|
| 2008-11-25 23:08:55 |
Steve Langasek |
update-manager: milestone |
jaunty-alpha-1 |
jaunty-alpha-2 |
|
| 2008-11-26 19:31:16 |
smirk |
bug |
|
|
added subscriber Smirkware |
| 2008-12-03 14:42:19 |
Mario Limonciello |
fglrx-installer: status |
Fix Released |
Triaged |
|
| 2008-12-03 14:42:19 |
Mario Limonciello |
fglrx-installer: statusexplanation |
Closing the jaunty task since 8-11 is in Jaunty now. |
|
|
| 2008-12-07 22:04:32 |
Axel Kellermann |
bug |
|
|
added attachment 'dmesg.txt' (dmesg.txt) |
| 2008-12-15 09:45:06 |
Launchpad Janitor |
update-manager: status |
Fix Committed |
Fix Released |
|
| 2008-12-23 03:49:29 |
Michael Rooney |
description |
Using fglrx-installer 2:8.543-0ubuntu4, r3xx hardware such as Radeon 9500, Mobility Radeon 9700 and similar don't work
They are not explicitly listed in the modaliases, so they will not be offered by Jockey. In the past, this hardware did work with the fglrx driver. Now the fglrx driver indicates memory errors when trying to load.
Here is a snippet of what the memory error will look like:
[ 1024.699204] [fglrx] Maximum main memory to use for locked dma buffers: 1169 MBytes.
[ 1024.700616] [fglrx:drm_alloc] *ERROR* [driver] Allocating 0 bytes
[ 1024.700683] [fglrx:firegl_init_device_list] *ERROR* Out of memory when allocating device heads
[ 1024.700757] [fglrx:firegl_init_module] *ERROR* firegl_init_devices failed
TEST CASE:
1. Install intrepid w/ r3xx hardware.
2. attempt to activate fglrx and reboot verifying unable to start X
3. Activate intrepid-proposed
4. update to new fglrx version, verify that X starts up properly |
Using fglrx-installer 2:8.543-0ubuntu4, r3xx hardware such as Radeon 9500, Mobility Radeon 9700 and similar don't work
They are not explicitly listed in the modaliases, so they will not be offered by Jockey. In the past, this hardware did work with the fglrx driver. Now the fglrx driver indicates memory errors when trying to load.
Here is a snippet of what the memory error will look like:
[ 1024.699204] [fglrx] Maximum main memory to use for locked dma buffers: 1169 MBytes.
[ 1024.700616] [fglrx:drm_alloc] *ERROR* [driver] Allocating 0 bytes
[ 1024.700683] [fglrx:firegl_init_device_list] *ERROR* Out of memory when allocating device heads
[ 1024.700757] [fglrx:firegl_init_module] *ERROR* firegl_init_devices failed
WORKAROUND:
1. sudo apt-get remove --purge fglrx*
2. sudo apt-get remove --purge xserver-xorg-video-ati xserver-xorg-video-radeon
3. sudo apt-get install xserver-xorg-video-ati
4. Restart.
TEST CASE:
1. Install intrepid w/ r3xx hardware.
2. attempt to activate fglrx and reboot verifying unable to start X
3. Activate intrepid-proposed
4. update to new fglrx version, verify that X starts up properly |
|
| 2008-12-23 04:12:12 |
Michael Rooney |
description |
Using fglrx-installer 2:8.543-0ubuntu4, r3xx hardware such as Radeon 9500, Mobility Radeon 9700 and similar don't work
They are not explicitly listed in the modaliases, so they will not be offered by Jockey. In the past, this hardware did work with the fglrx driver. Now the fglrx driver indicates memory errors when trying to load.
Here is a snippet of what the memory error will look like:
[ 1024.699204] [fglrx] Maximum main memory to use for locked dma buffers: 1169 MBytes.
[ 1024.700616] [fglrx:drm_alloc] *ERROR* [driver] Allocating 0 bytes
[ 1024.700683] [fglrx:firegl_init_device_list] *ERROR* Out of memory when allocating device heads
[ 1024.700757] [fglrx:firegl_init_module] *ERROR* firegl_init_devices failed
WORKAROUND:
1. sudo apt-get remove --purge fglrx*
2. sudo apt-get remove --purge xserver-xorg-video-ati xserver-xorg-video-radeon
3. sudo apt-get install xserver-xorg-video-ati
4. Restart.
TEST CASE:
1. Install intrepid w/ r3xx hardware.
2. attempt to activate fglrx and reboot verifying unable to start X
3. Activate intrepid-proposed
4. update to new fglrx version, verify that X starts up properly |
Using fglrx-installer 2:8.543-0ubuntu4, r3xx hardware such as Radeon 9500, Mobility Radeon 9700 and similar don't work
They are not explicitly listed in the modaliases, so they will not be offered by Jockey. In the past, this hardware did work with the fglrx driver. Now the fglrx driver indicates memory errors when trying to load.
Here is a snippet of what the memory error will look like:
[ 1024.699204] [fglrx] Maximum main memory to use for locked dma buffers: 1169 MBytes.
[ 1024.700616] [fglrx:drm_alloc] *ERROR* [driver] Allocating 0 bytes
[ 1024.700683] [fglrx:firegl_init_device_list] *ERROR* Out of memory when allocating device heads
[ 1024.700757] [fglrx:firegl_init_module] *ERROR* firegl_init_devices failed
WORKAROUND:
You'll need to completely remove the proprietary driver and [re]install the open-source driver. As a plus, many users report improved performance with the open-source drivers in Intrepid versus ATI's fglrx in Hardy for 2D purposes such as normal desktop use and video playback.
1. sudo apt-get remove --purge fglrx*
2. sudo apt-get remove --purge xserver-xorg-video-ati xserver-xorg-video-radeon
3. sudo apt-get install xserver-xorg-video-ati
4. Restart.
TEST CASE:
1. Install intrepid w/ r3xx hardware.
2. attempt to activate fglrx and reboot verifying unable to start X
3. Activate intrepid-proposed
4. update to new fglrx version, verify that X starts up properly |
|
| 2009-01-30 09:54:16 |
Noiano |
bug |
|
|
added attachment 'Xorg.0.log' (Xorg.0.log) |
| 2009-01-30 18:28:07 |
Andrew |
bug |
|
|
added attachment 'xorg.0.log-aticonfig-dualhead' (xorg.0.log-aticonfig-dualhead) |
| 2009-02-03 07:54:53 |
Martin Pitt |
fglrx-installer: status |
Fix Committed |
Triaged |
|
| 2009-02-03 07:54:53 |
Martin Pitt |
fglrx-installer: statusexplanation |
|
Removed from intrepid-proposed as per Mario's request. |
|
| 2009-02-04 09:19:09 |
Bryce Harrington |
fglrx-installer: status |
Triaged |
Won't Fix |
|
| 2009-02-04 09:19:09 |
Bryce Harrington |
fglrx-installer: statusexplanation |
Removed from intrepid-proposed as per Mario's request. |
|
|
| 2009-02-13 09:59:52 |
Martin Pitt |
fglrx-installer: status |
Triaged |
Won't Fix |
|
| 2009-02-13 09:59:52 |
Martin Pitt |
fglrx-installer: importance |
High |
Medium |
|
| 2009-02-13 09:59:52 |
Martin Pitt |
fglrx-installer: statusexplanation |
|
This isn't really a release blocker for Jaunty. update-manager transitions r3xx users to -ati, which works well enough. This is a target of opportunity at most. |
|
| 2009-03-18 00:00:07 |
Launchpad Janitor |
fglrx-installer: status |
Won't Fix |
Fix Released |
|
| 2009-03-18 00:27:44 |
Bryce Harrington |
fglrx-installer (Ubuntu Jaunty): status |
Fix Released |
Triaged |
|
| 2009-03-18 00:27:44 |
Bryce Harrington |
fglrx-installer (Ubuntu Jaunty): statusexplanation |
This isn't really a release blocker for Jaunty. update-manager transitions r3xx users to -ati, which works well enough. This is a target of opportunity at most. |
Actually this one is not closed quite yet. |
|
| 2009-04-03 09:21:18 |
johny |
removed subscriber johny |
|
|
|
| 2009-04-08 16:48:51 |
Bryce Harrington |
fglrx-installer (Ubuntu Jaunty): status |
Triaged |
Won't Fix |
|
| 2009-04-08 16:54:51 |
Bryce Harrington |
fglrx-installer (Ubuntu): status |
Triaged |
Won't Fix |
|
| 2009-04-08 16:55:16 |
Bryce Harrington |
fglrx: status |
Triaged |
Won't Fix |
|
| 2009-04-14 06:59:10 |
WillScarlett |
removed subscriber WillScarlett |
|
|
|
| 2009-04-21 20:19:25 |
Carey Underwood |
ubuntu-release-notes: status |
Fix Released |
Confirmed |
|
| 2009-04-26 08:08:05 |
David Taylor |
removed subscriber David Taylor |
|
|
|
| 2009-05-17 14:04:26 |
philipp beitz |
removed subscriber philipp beitz |
|
|
|
| 2009-06-02 16:10:14 |
Daniel Swarbrick |
removed subscriber Daniel Swarbrick |
|
|
|
| 2009-06-02 16:12:12 |
Daniel Swarbrick |
removed subscriber Daniel Swarbrick |
|
|
|
| 2009-08-05 14:54:16 |
Launchpad Janitor |
branch linked |
|
lp:ubuntu/karmic/fglrx-installer |
|
| 2009-08-05 15:00:49 |
Launchpad Janitor |
branch linked |
|
lp:ubuntu/intrepid-proposed/fglrx-installer |
|
| 2009-08-21 20:55:35 |
Stefano Maioli |
removed subscriber Stefano Maioli |
|
|
|
| 2009-11-08 21:06:08 |
vyncere |
nominated for series |
|
Ubuntu Karmic |
|
| 2010-02-22 00:31:39 |
Launchpad Janitor |
branch linked |
|
lp:ubuntu/update-manager |
|
| 2010-03-08 00:12:46 |
mattrenfer |
description |
Using fglrx-installer 2:8.543-0ubuntu4, r3xx hardware such as Radeon 9500, Mobility Radeon 9700 and similar don't work
They are not explicitly listed in the modaliases, so they will not be offered by Jockey. In the past, this hardware did work with the fglrx driver. Now the fglrx driver indicates memory errors when trying to load.
Here is a snippet of what the memory error will look like:
[ 1024.699204] [fglrx] Maximum main memory to use for locked dma buffers: 1169 MBytes.
[ 1024.700616] [fglrx:drm_alloc] *ERROR* [driver] Allocating 0 bytes
[ 1024.700683] [fglrx:firegl_init_device_list] *ERROR* Out of memory when allocating device heads
[ 1024.700757] [fglrx:firegl_init_module] *ERROR* firegl_init_devices failed
WORKAROUND:
You'll need to completely remove the proprietary driver and [re]install the open-source driver. As a plus, many users report improved performance with the open-source drivers in Intrepid versus ATI's fglrx in Hardy for 2D purposes such as normal desktop use and video playback.
1. sudo apt-get remove --purge fglrx*
2. sudo apt-get remove --purge xserver-xorg-video-ati xserver-xorg-video-radeon
3. sudo apt-get install xserver-xorg-video-ati
4. Restart.
TEST CASE:
1. Install intrepid w/ r3xx hardware.
2. attempt to activate fglrx and reboot verifying unable to start X
3. Activate intrepid-proposed
4. update to new fglrx version, verify that X starts up properly |
Using fglrx-installer 2:8.543-0ubuntu4, r3xx hardware such as Radeon 9500, Mobility Radeon 9700 and similar don't work
They are not explicitly listed in the modaliases, so they will not be offered by Jockey. In the past, this hardware did work with the fglrx driver. Now the fglrx driver indicates memory errors when trying to load.
Here is a snippet of what the memory error will look like:
[ 1024.699204] [fglrx] Maximum main memory to use for locked dma buffers: 1169 MBytes.
[ 1024.700616] [fglrx:drm_alloc] *ERROR* [driver] Allocating 0 bytes
[ 1024.700683] [fglrx:firegl_init_device_list] *ERROR* Out of memory when allocating device heads
[ 1024.700757] [fglrx:firegl_init_module] *ERROR* firegl_init_devices failed
WORKAROUND:
You'll need to completely remove the proprietary driver and [re]install the open-source driver. As a plus, many users report improved performance with the open-source drivers in Intrepid versus ATI's fglrx in Hardy for 2D purposes such as normal desktop use and video playback.
1. sudo apt-get remove --purge fglrx*
2. sudo apt-get remove --purge xserver-xorg-video-ati xserver-xorg-video-radeon
3. sudo apt-get install xserver-xorg-video-ati
4. Restart.
TEST CASE:
1. Install intrepid w/ r3xx hardware.
2. attempt to activate fglrx and reboot verifying unable to start X
3. Activate intrepid-proposed
4. update to new fglrx version, verify that X starts up properly
|
|
| 2010-09-29 21:24:17 |
Mario Limonciello |
ubuntu-release-notes: status |
Confirmed |
Invalid |
|
| 2010-09-29 21:24:23 |
Mario Limonciello |
ubuntu-release-notes: assignee |
Mario Limonciello (superm1) |
|
|
| 2010-09-29 21:42:01 |
Filipe Sousa |
removed subscriber Filipe Sousa |
|
|
|
| 2010-09-30 07:33:53 |
smirk |
removed subscriber smirk |
|
|
|
| 2010-09-30 16:08:55 |
jonte_jo |
removed subscriber jonte_jo |
|
|
|
