[Bug 1493888] Re: FGLRX incompatible with gcc 5
@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 the switching process is all still a little bit confused as there now seem to be several possible drivers competing for the same hardware which need blacklisting/whitelisting appropriately every time you switch. -- 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 notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/1493888/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1510573] Re: fglrx should blacklist amdgpu
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 because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1510573 Title: fglrx should blacklist amdgpu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/1510573/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1493888] Re: FGLRX incompatible with gcc 5
@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's software implementation of OpenGL as far as I know ). It was usable but slightly laggy. This process had left traces of fglrx-core and fglrx in the dpkg database. When I purged these, and rebooted, LightDM worked, but Unity hung on at ( first flickering, but eventually stable ) the desktop background, with no other screen artifacts. Manually installing the fglrx-updates set of packages from wily-proposed then gave me the full binary driver accelerated desktop correctly without the need to blacklist anything. Subsequently switching to the open source drivers still fails to give me GPU acceleration for X ( llvmpipe again ). So something does not appear to be set or removed properly in the process of going from Proprietary to Open Source drivers. I'll see if I can find out what. -- 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 notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/1493888/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1493888] Re: FGLRX incompatible with gcc 5
@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 Technologies, Starnberg, GERMANY' taints kernel. [2.470362] Disabling lock debugging due to kernel taint [2.474696] fglrx: module verification failed: signature and/or required key missing - tainting kernel [2.502797] random: nonblocking pool is initialized [2.513664] <6>[fglrx] Maximum main memory to use for locked dma buffers: 31469 MBytes. [2.514055] <6>[fglrx] vendor: 1002 device: 67b1 revision: 0 count: 1 [2.514697] <6>[fglrx] ioport: bar 4, base 0xe000, size: 0x100 [2.515002] <6>[fglrx] Kernel PAT support is enabled [2.515016] <6>[fglrx] module loaded - fglrx 15.20.3 [Sep 8 2015] with 1 minors lsmod shows fglrx, with no users, but neither amdgpu nor radeon. Trying to load those modules with modprobe gives: modprobe: ERROR: could not insert 'off': Function not implemented Running gpu-manager gives: last_boot_file: /var/lib/ubuntu-drivers-common/last_gfx_boot new_boot_file: /var/lib/ubuntu-drivers-common/last_gfx_boot grep dmesg status 256 dmesg status 256 == 0? No /etc/modprobe.d is not a file /etc/modprobe.d is not a file /etc/modprobe.d is not a file /etc/modprobe.d is not a file Is nvidia loaded? no Was nvidia unloaded? no Is nvidia blacklisted? no Is fglrx loaded? yes Was fglrx unloaded? no Is fglrx blacklisted? no Is intel loaded? no Is radeon loaded? no Is radeon blacklisted? yes Is nouveau loaded? no Is nouveau blacklisted? no Is fglrx kernel module available? yes Is nvidia kernel module available? no Vendor/Device Id: 1002:67b1 BusID "PCI:2@0:0:0" Is boot vga? yes Error : Failed to open /dev/dri Error : Failed to open /dev/dri Error : Failed to open /dev/dri Does it require offloading? no last cards number = 1 I couldn't open /var/lib/ubuntu-drivers-common/last_gfx_boot for writing. Error: can't write to /var/lib/ubuntu-drivers-common/last_gfx_boot The Xorg.0.log file ( attached ) seems to try and fail a few alternatives before settling on FBDEV as the driver, which then causes AIGLX to degrade to software rendering. To my little brain, this looks like fglrx doesn't get properly removed, and the open source modules are not removed from blacklisting. ** Attachment added: "Xorg.0.log" https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/1493888/+attachment/4517639/+files/Xorg.0.log -- 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 notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/1493888/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1493888] Re: FGLRX incompatible with gcc 5
@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 notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/1493888/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1493888] Re: FGLRX incompatible with gcc 5
@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/blacklist.conf Then it worked fine for me on an R9 290. -- 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 notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/1493888/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1493888] Re: FGLRX incompatible with gcc 5
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 complains that /dev/dri is absent. I can force the screens to stay on ( but still blank ) by running amdconfig --initilal. The main change then is that ukiOpenDevice returns 9 rather than 11 ( can't find any documentation for this function - assume it is proprietary ). To add more strangeness, if I boot into recovery mode, and run 'startx' as the root user, I get an empty X desktop on display :1 that appears to be the Unity desktop without any menus/launchers, and no window manager. But I can run an X terminal and run gedit, eclipse, and firefox, from which I am writing this comment. However, the VTs that should be provided by fglrx do not work. This is with a new 15.10 installation ( keeping personal files ), not an upgrade, using an R9 290. It clearly works as an X server, but configuration or permissions in the installation must be askew. ** Attachment added: "Partially working..." https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/1493888/+attachment/4506836/+files/fglrx-bug.tar -- 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 notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/1493888/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1493888] Re: FGLRX incompatible with gcc 5
>>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 dmesg output and the Xorg and gpu-manager log >> files. The only thing I can see is the gpu-manager log complains that >> /dev/dri is absent. >That is LP: #1510573 Yes, it is. Thanks. So, other than blacklisting amdgpu, it worked as intended from wily- proposed. -- 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 notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/1493888/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1493888] Re: FGLRX incompatible with kernel 4.2
@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 has problems for me. On the positive side, the open source graphics stacks are catching up, and both AMD/NVidia seem to be paying more attention to their drivers, so perhaps these problems will diminish over time. -- 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 kernel 4.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/1493888/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1501276] [NEW] No Screen or Blank Screen instead of Login Screen
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 ( disconnect ), and the keyboard becomes unresponsive ( caps lock and other toggles stop working ). Cannot switch to other VTs, but can use the Alt-PrtScrn(RSEINUB) safe reboot method. Scenario 2: Use the "Additional Drivers" push-button to change to fglrx ; use amdconfig --initial to create xorg.conf. Result: On reboot, both the Displayport and DVI screens remain active but blank, and the keyboard becomes unresponsive ( caps lock and other toggles stop working ). Cannot switch to other VTs, but can use the Alt- PrtScrn(RSEINUB) safe reboot method. I originally had this behaviour when I tried to build Catalyst 15.9 ( which I think you are using in wily) from the AMD website against Ubuntu 15.04. I assumed there was a problem with Kernel DRM components, so I tried it in the wily beta in case the new kernel solver the issue, but have exactly the same result. This version of Wily beta 2 is installed from the DVD ISO, not upgraded from 15.04 ( although I did use the option to retain existing personal files ). I doubt this is an Ubuntu-resolvable issue, but if it is an AMD issue you are more likely to get them to fix it than individual users. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: fglrx 2:15.201-0ubuntu1 ProcVersionSignature: Ubuntu 4.2.0-12.14-generic 4.2.1 Uname: Linux 4.2.0-12-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.19-0ubuntu1 Architecture: amd64 BootLog: CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' Date: Wed Sep 30 10:59:20 2015 DistUpgraded: Fresh install DistroCodename: wily DistroVariant: ubuntu DkmsStatus: fglrx-core, 15.201, 4.2.0-12-generic, x86_64: installed GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Hawaii PRO [Radeon R9 290] [1002:67b1] (prog-if 00 [VGA controller]) Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Device [1002:0b00] InstallationDate: Installed on 2015-09-26 (3 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150924) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcEnviron: SHELL=/bin/bash TERM=linux PATH=(custom, no user) LANG=en_GB.UTF-8 LANGUAGE=en_GB:en ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-12-generic root=UUID=56807866-06e5-4e2d-a1f2-eda9fee8bf78 ro recovery nomodeset SourcePackage: fglrx-installer UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/24/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.30 dmi.board.name: X79 Extreme6/GB dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.30:bd07/24/2013:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnX79Extreme6/GB:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. version.compiz: compiz 1:0.9.12.2+15.10.20150908-0ubuntu1 version.fglrx-installer: fglrx-installer N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.64-1 version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.0-1ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.0.0-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0+git20150819-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20150808-0ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu3 xserver.bootTime: Wed Sep 30 10:40:09 2015 xserver.configfile: default xserver.devices: xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.17.2-1ubuntu7 ** Affects: fglrx-installer (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug ubuntu wily -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1501276 Title: No Screen or Blank Screen instead of Login Screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/1501276/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 572196] Re: No display on LCD panel when the fglrx driver is installed. Display on external VGA still works.
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 correctly reports the screen capabilities. If the version of FLGRX driver used in 10.10 is provided as an update to the previous Ubuntu versions ( 9.04, 9.10, 10.04 ), I would further assume that the issue is fixed for those versions, but I have not verified that. Catalyst Control Center reports the following sofware versions 2D Driver Version 8.78.30 RandR Version 1.3 OpenGL Version 3.3.10237 -- No display on LCD panel when the fglrx driver is installed. Display on external VGA still works. https://bugs.launchpad.net/bugs/572196 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 572196] Re: No display on LCD panel when the fglrx driver is installed. Display on external VGA still works.
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 latest version of Ubuntu, the default xorg.conf is actually blank, with xorg probing for the best values for open source drivers and screen configurations, so the best work-around is to simply delete xorg.conf. Rog. -- No display on LCD panel when the fglrx driver is installed. Display on external VGA still works. https://bugs.launchpad.net/bugs/572196 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 572196] Re: No display on LCD panel when the fglrx driver is installed. Display on external VGA still works.
** 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 ** Attachment added: GdmLog.txt http://launchpadlibrarian.net/46537687/GdmLog.txt ** Attachment added: GdmLog1.txt http://launchpadlibrarian.net/46537689/GdmLog1.txt ** Attachment added: GdmLog2.txt http://launchpadlibrarian.net/46537691/GdmLog2.txt ** Attachment added: Lspci.txt http://launchpadlibrarian.net/46537693/Lspci.txt ** Attachment added: Lsusb.txt http://launchpadlibrarian.net/46537695/Lsusb.txt ** Attachment added: PciDisplay.txt http://launchpadlibrarian.net/46537696/PciDisplay.txt ** Attachment added: ProcCpuinfo.txt http://launchpadlibrarian.net/46537698/ProcCpuinfo.txt ** Attachment added: ProcInterrupts.txt http://launchpadlibrarian.net/46537700/ProcInterrupts.txt ** Attachment added: ProcModules.txt http://launchpadlibrarian.net/46537702/ProcModules.txt ** Attachment added: RelatedPackageVersions.txt http://launchpadlibrarian.net/46537704/RelatedPackageVersions.txt ** Attachment added: UdevDb.txt http://launchpadlibrarian.net/46537705/UdevDb.txt ** Attachment added: UdevLog.txt http://launchpadlibrarian.net/46537707/UdevLog.txt ** Attachment added: XorgConf.txt http://launchpadlibrarian.net/46537709/XorgConf.txt ** Attachment added: XorgLog.txt http://launchpadlibrarian.net/46537711/XorgLog.txt ** Attachment added: XorgLogOld.txt http://launchpadlibrarian.net/46537712/XorgLogOld.txt ** Attachment added: Xrandr.txt http://launchpadlibrarian.net/46537714/Xrandr.txt ** Attachment added: glxinfo.txt http://launchpadlibrarian.net/46537716/glxinfo.txt ** Attachment added: setxkbmap.txt http://launchpadlibrarian.net/46537717/setxkbmap.txt ** Attachment added: xdpyinfo.txt http://launchpadlibrarian.net/46537719/xdpyinfo.txt ** Attachment added: xkbcomp.txt http://launchpadlibrarian.net/46537721/xkbcomp.txt -- No display on LCD panel when the fglrx driver is installed. Display on external VGA still works. https://bugs.launchpad.net/bugs/572196 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 572196] [NEW] No display on LCD panel when the fglrx driver is installed. Display on external VGA still works.
Public bug reported: Binary package hint: xorg Applies to: Ubuntu 10.04 LTS xorg 1:7.5+5ubuntu1 fglrx 2:8.723.1-0ubuntu3 1. Loaded 10.04 using Wubi on an Alienware M17 laptop (also called OCZ Whitebook, based on the Arima W840D Chassis). 2. Testing showed system worked correctly out of the box with RADEON xorg driver. 3. Switched to ATI FGLRX driver using menu item System/Administration/Hardware Drivers. 4. Multiple functional errors found with FGLRX. - xorg provides no output to the Internal LCD, but external VGA and HDMI both have output. - xorg outputs to virtual terminal 8, no other virtual terminals display anything on any screen. - Catalyst control center recognizes the existence of the LCD, but thinks it is a 1400x1050 panel (It is actually 1920x1200). This is probably very specific to fglrx on the Alienware M17. The log files do not show any real errors, which makes it hard to understand the issue. Searching the Internet uncovered a small number of forum posts from lost souls with the Alienware M17 that have been having this problem for quite a while, but as there are no obvious faults, community response was close to zero. I have also verified (by doing clean Wubi installs, and updating to the latest updates) that the issue also existed in Ubuntu 9.04 and 9.10 on the same Alienware M17. I do not really understand the xorg architecture well enough to know whether this is a problem with an xorg component, or solely the ATI fglrx driver. If I understand it correctly, xrandr is supposed to probe for screens and resolutions and does so properly when using the default radeon driver. The xorg log files suggests that the fglrx driver uses its own version of xrandr, which sees the hardware, but complains a bit about not recognizing hardware 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 ProcVersionSignature: Ubuntu 2.6.32-21.32-generic 2.6.32.11+drm33.2 Uname: Linux 2.6.32-21-generic x86_64 NonfreeKernelModules: fglrx Architecture: amd64 Date: Fri Apr 30 10:08:11 2010 DkmsStatus: fglrx, 8.723.1, 2.6.32-21-generic, x86_64: installed InstallationMedia: Ubuntu 10.04 Lucid Lynx - Alpha amd64 (20100411) MachineType: alienware Alienware M17 ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-21-generic root=/dev/sda1 loop=/hostname/disks/root.disk ro quiet splash ProcEnviron: LANG=en_GB.utf8 SHELL=/bin/bash SourcePackage: xorg Symptom: display dmi.bios.date: 10/14/2008 dmi.bios.vendor: Intel dmi.bios.version: W841.B10 dmi.board.name: alienware dmi.board.vendor: alienware dmi.board.version: alienware dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: alienware dmi.chassis.version: alienware dmi.modalias: dmi:bvnIntel:bvrW841.B10:bd10/14/2008:svnalienware:pnAlienwareM17:pvrW841.B10:rvnalienware:rnalienware:rvralienware:cvnalienware:ct1:cvralienware: dmi.product.name: Alienware M17 dmi.product.version: W841.B10 dmi.sys.vendor: alienware system: distro: Ubuntu codename: lucid architecture: x86_64 kernel: 2.6.32-21-generic ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug lucid -- No display on LCD panel when the fglrx driver is installed. Display on external VGA still works. https://bugs.launchpad.net/bugs/572196 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 572196] Re: No display on LCD panel when the fglrx driver is installed. Display on external VGA still works.
Just to update the the behaviour somewhat: According to xrandr, the LVDS (LCD panel) screen is connected. I can use xrandr to tell the LVDS screen what resolution to display, and can set the display to off. When the display is set to off, the backlight goes off, suggesting that the panel is simply not being sent the signal when it is on. However, LVDS still describes the panel incorrectly - it should be 1920x 1200, but I get the following from xrandr... ro...@ubuntu:~$ xrandr --prop Screen 0: minimum 320 x 200, current 1400 x 1050, maximum 1600 x 1600 LVDS connected 1400x1050+0+0 (normal left inverted right x axis y axis) 0mm x 0mm BACKLIGHT: 7 (0x0007) range: (0,7) SignalFormat: DisplayPort ConnectorType: Panel 1400x1050 60.2*+ 1280x1024 60.2 + 1280x960 60.2 + 1280x800 60.2 + 1152x864 60.2 + 1280x768 60.2 + 1280x720 60.2 + 1024x768 60.2 + 1024x600 60.2 + 800x60060.2 + 800x48060.2 + 720x48060.2 + 640x48060.2 + DFP1 disconnected (normal left inverted right x axis y axis) SignalFormat: TMDS ConnectorType: HDMI CRT1 connected 1400x1050+0+0 (normal left inverted right x axis y axis) 0mm x 0mm SignalFormat: VGA ConnectorType: VGA 1600x1200 60.0 + 1400x1050 60.0* 1280x1024 75.0 60.0 1440x900 59.9 1280x960 60.0 1280x800 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. -- No display on LCD panel when the fglrx driver is installed. Display on external VGA still works. https://bugs.launchpad.net/bugs/572196 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 246301] Re: Update the FGLRX and NVIDIA driver to 8.6 and 173.14.09
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, works most of the time, but occasionally does not return from suspend). Removing the driver also works as expected. -- Update the FGLRX and NVIDIA driver to 8.6 and 173.14.09 https://bugs.launchpad.net/bugs/246301 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
