Used EnvyNG from Hardy-Proposed to install 173.14.09 for a nVidia 8800
GTX based card.
Using a 2.6.24-19 real-time kernel, I have experienced no issues over
several days of general use, including use of the advanced visual
effects. Similarly, suspend and resume work as they did before (that is,
wo
** Attachment added: "BootDmesg.txt"
http://launchpadlibrarian.net/46537682/BootDmesg.txt
** Attachment added: "CurrentDmesg.txt"
http://launchpadlibrarian.net/46537684/CurrentDmesg.txt
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/46537686/Dependencies.txt
** A
are or not supporting it.
If there are any suggestion that I could try to resolve this, or
anything I can do to provide further information, not already provided
by ubuntu-bug, please let me know.
Roger Barrett
ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: xorg 1:7.5+5ubuntu1
ProcVersionSignatu
75.0 60.0
1152x864 75.0 60.0
1280x768 59.9
1280x720 60.0
1024x768 75.0 60.0
1024x600 60.0
800x60075.0 60.3
800x48060.0
720x48060.0
640x48075.0 60.0
Roger Barrett
Hello Hameed,
Your problem may be similar, but is not the same, I think. This issue
has been present in the last 3 releases of Ubuntu on my laptop, so
reverting to Karmic would be of no use. Also, as metioned in my original
post, I have NO virtual terminals when using fglrx.
By the way, in the la
Public bug reported:
Release 15.10 Wily Beta 2.
GPU R9 290. Hawaii Core.
When switching to fglrx from radeon, I get no graphics.
Scenario 1: Use the "Additional Drivers" push-button to change to fglrx
; do not create xorg.conf.
Result: On reboot, both the Displayport and DVI screens turn off (
@Duncan
I think it's still being tested, so its probably only in Wily-proposed
at the moment.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1493888
Title:
FGLRX incompatible with gcc 5
To manage n
Do you remember to reverse the whole process when going from fglrx ->
open source ?
I can now switch from radeon to fglrx, but then it seems to prevent the
open source radeon driver from loading when I switch back.
See bug 1493888 Post #203 for details.
--
You received this bug notification bec
@Duncan
I don't have odd artifacts; I meant that there is just a desktop
background, no other screen items visible at all. But that is when I try
to use the driver selection utility to revert to the Open Source driver,
not when I'm trying to use the AMD binary driver, which works fine.
I think th
@northar: The general view seems to be that open source drivers must
work, but not necessarily the closed source, except for LTS releases.
Personally I think the closed-source graphics card drivers are important
enough that they should be fixed before release; it seems that every
second release ha
@Philip Gemmell
Not sure if the open source driver blacklist has made it into the fix
yet - this caused my screen to be blank after updating.
See previous comments #114 #119 and #120.
I didn't need to change nomodeset, but I did need to add "blacklist
amdgpu" to the end of /etc/modprobe.d/blackl
@Mathew Hodson.
I removed the amdgpu blacklist entry I had manually added and used the
"Additional Drivers" tab of Software and Updates to switch to the Open
Source drivers.
This resulted in a fallback Unity desktop without GPU acceleration (
glxinfo reported gallium using llvmpipe, which is mesa
@Mathew Hodson.
OK, so when switching from AMD to Open Source drivers in the additional
drivers tab, the fglrx-updates-core and fglrx-updates-dev are left
installed. This means that on reboot, dmesg contains the following
[2.470360] fglrx: module license 'Proprietary. (C) 2002 - ATI Technolog
It both works and doesn't work for me.
The kernel module is fine, the X Server loads and seems to open the device
correctly, but the screens stay blank, then turn off.
The attached tar file has dmesg output and the Xorg and gpu-manager log files.
The only thing I can see is the gpu-manager log c
>>On 27-10-15 17:47:55, Roger Barrett wrote:
>> It both works and doesn't work for me.
>>
>> The kernel module is fine, the X Server loads and seems to open the device
>> correctly, but the screens stay blank, then turn off.
>> The attached tar file has
This issue appears to have been fixed in Ubuntu 10.10. The FGLRX driver
now correctly displays on the internal LVDS connected panel.
I assume that this is from a corrected/updated version of the FGLRX
driver rather than any other reason, since xrandr ( an extension
implemented by the driver ) now
16 matches
Mail list logo
