Bug#524280: Same problem on Radeon HD 3200
On Wed, May 6, 2009 at 01:25:51 +0200, Astrid S. de Wijn wrote: (II) Loading sub module fglrxdrm (II) LoadModule: fglrxdrm (II) Loading /usr/lib/xorg/modules/linux//libfglrxdrm.so (II) Module fglrxdrm: vendor=FireGL - ATI Technologies Inc. compiled for 1.4.99.906, module version = 8.60.3 This might cause some issues... You probably need to remove anything fglrx-related before testing the radeon driver. Cheers, Julien -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#524280: Same problem on Radeon HD 3200
On Wed, May 06, 2009 at 09:23:02AM +0200, Julien Cristau wrote: On Wed, May 6, 2009 at 01:25:51 +0200, Astrid S. de Wijn wrote: (II) Loading sub module fglrxdrm (II) LoadModule: fglrxdrm (II) Loading /usr/lib/xorg/modules/linux//libfglrxdrm.so (II) Module fglrxdrm: vendor=FireGL - ATI Technologies Inc. compiled for 1.4.99.906, module version = 8.60.3 This might cause some issues... You probably need to remove anything fglrx-related before testing the radeon driver. Ooops. I didn't realise that was still there. Removing it fixed my problem. And I was so looking forward to helping out... Thanks for the assistance! Astrid -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#524280: Same problem on Radeon HD 3200
On Sun, Apr 26, 2009 at 11:15:46PM -0400, Alex Deucher wrote: On Thu, Apr 23, 2009 at 5:16 AM, Astrid S. de Wijn Please let me know if you need any more details on my hardware cofiguration. Unfortunately I am not in a position to reboot this computer a lot right now for testing different versions, because it is being used for long simulations. If you get a chance, can you try any versions between 6.9.0 and 6.12.x or do a git bisect between 6.9.0 and some some broken release? Also, did you do anything else like upgrade the amount of ram in the system? I'm afraid I won't be able to do any rebooting untill these simulations finish, which might be a while. The xorg upgrade did not coincide with a hardware upgrade. I did fix some hardware a few days before, and subsequently ran memtest86+, which reported no errors. The machine has 6 Gb of ram, the motherboard is only a few months old, and it has never had any problems with xorg before. Astrid -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#524280: Same problem on Radeon HD 3200
On Tue, Apr 28, 2009 at 12:17 PM, Astrid S. de Wijn astrid-spamme...@syonax.net wrote: On Sun, Apr 26, 2009 at 11:15:46PM -0400, Alex Deucher wrote: On Thu, Apr 23, 2009 at 5:16 AM, Astrid S. de Wijn Please let me know if you need any more details on my hardware cofiguration. Unfortunately I am not in a position to reboot this computer a lot right now for testing different versions, because it is being used for long simulations. If you get a chance, can you try any versions between 6.9.0 and 6.12.x or do a git bisect between 6.9.0 and some some broken release? Also, did you do anything else like upgrade the amount of ram in the system? I'm afraid I won't be able to do any rebooting untill these simulations finish, which might be a while. The xorg upgrade did not coincide with a hardware upgrade. I did fix some hardware a few days before, and subsequently ran memtest86+, which reported no errors. The machine has 6 Gb of ram, the motherboard is only a few months old, and it has never had any problems with xorg before. Some people have reported problems on systems with large amounts of ram due to bad mtrr setup by the bios. Alex -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#524280: Same problem on Radeon HD 3200
On Thu, Apr 23, 2009 at 5:16 AM, Astrid S. de Wijn astrid-spamme...@syonax.net wrote: I have the same problem with the on-board graphics card of a Gigabyte GA-MA78GPM-DS2H motherboard. Lspci output: 01:05.0 VGA compatible controller: ATI Technologies Inc Radeon HD 3200 Graphics (prog-if 00 [VGA controller]) Subsystem: Giga-byte Technology Device d000 Flags: bus master, fast devsel, latency 0, IRQ 10 Memory at d000 (32-bit, prefetchable) [size=256M] I/O ports at ee00 [size=256] Memory at fdfe (32-bit, non-prefetchable) [size=64K] Memory at fde0 (32-bit, non-prefetchable) [size=1M] Expansion ROM at unassigned [disabled] Capabilities: [50] Power Management version 3 Capabilities: [a0] MSI: Mask- 64bit+ Count=1/1 Enable- I don't have any more information to add to the extensive test results from Jacek Politowski, except perhaps for my pretty generic xorg.conf (see attachment). I am using unstable with a stock 2.6.29 kernel. Downgrading to 6.9.0 worked for me as well. I can confirm that the image on the screen with the broken driver is some sort of mixup of what the screen looked like just before things broke. At one point during my downgrade things were half fixed and I got almost the entire original image back. I could read most of the text in my terminals. This happened even after a soft reboot. Please let me know if you need any more details on my hardware cofiguration. Unfortunately I am not in a position to reboot this computer a lot right now for testing different versions, because it is being used for long simulations. If you get a chance, can you try any versions between 6.9.0 and 6.12.x or do a git bisect between 6.9.0 and some some broken release? Also, did you do anything else like upgrade the amount of ram in the system? Alex -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#524280: Same problem on Radeon HD 3200
I have the same problem with the on-board graphics card of a Gigabyte GA-MA78GPM-DS2H motherboard. Lspci output: 01:05.0 VGA compatible controller: ATI Technologies Inc Radeon HD 3200 Graphics (prog-if 00 [VGA controller]) Subsystem: Giga-byte Technology Device d000 Flags: bus master, fast devsel, latency 0, IRQ 10 Memory at d000 (32-bit, prefetchable) [size=256M] I/O ports at ee00 [size=256] Memory at fdfe (32-bit, non-prefetchable) [size=64K] Memory at fde0 (32-bit, non-prefetchable) [size=1M] Expansion ROM at unassigned [disabled] Capabilities: [50] Power Management version 3 Capabilities: [a0] MSI: Mask- 64bit+ Count=1/1 Enable- I don't have any more information to add to the extensive test results from Jacek Politowski, except perhaps for my pretty generic xorg.conf (see attachment). I am using unstable with a stock 2.6.29 kernel. Downgrading to 6.9.0 worked for me as well. I can confirm that the image on the screen with the broken driver is some sort of mixup of what the screen looked like just before things broke. At one point during my downgrade things were half fixed and I got almost the entire original image back. I could read most of the text in my terminals. This happened even after a soft reboot. Please let me know if you need any more details on my hardware cofiguration. Unfortunately I am not in a position to reboot this computer a lot right now for testing different versions, because it is being used for long simulations. Astrid # xorg.conf (X.Org X Window System server configuration file) # # This file was generated by dexconf, the Debian X Configuration tool, using # values from the debconf database. # # Edit this file with caution, and see the xorg.conf manual page. # (Type man xorg.conf at the shell prompt.) # # This file is automatically updated on xserver-xorg package upgrades *only* # if it has not been modified since the last upgrade of the xserver-xorg # package. # # If you have edited this file but would like it to be automatically updated # again, run the following command: # sudo dpkg-reconfigure -phigh xserver-xorg Section InputDevice Identifier Generic Keyboard Driver kbd Option XkbRules xorg Option XkbModel pc104 Option XkbLayout us EndSection Section InputDevice Identifier Configured Mouse Driver mouse EndSection Section InputDevice Driverwacom Identifierstylus OptionDevice/dev/input/wacom #USB ONLY OptionType stylus OptionUSB on #USB ONLY EndSection Section InputDevice Driverwacom Identifiereraser OptionDevice/dev/input/wacom #USB ONLY OptionType eraser OptionUSB on #USB ONLY EndSection Section InputDevice Driverwacom Identifiercursor OptionDevice/dev/input/wacom #USB ONLY OptionType cursor OptionMode relative OptionUSB on #USB ONLY EndSection Section Extensions OptionComposite enable EndSection Section Device Identifier Configured Video Device Driver radeon Option XAANoOffscreenPixmaps true # Option DRI off # Option NoAccel true # Option R4xxATOM true EndSection Section Monitor Identifier Configured Monitor EndSection Section Screen Identifier Default Screen Monitor Configured Monitor EndSection Section ServerLayout Identifier Default Layout Screen Default Screen InputDevice Generic Keyboard #InputDevice Configured Mouse SendCoreEvents InputDevice stylus SendCoreEvents InputDevice eraser SendCoreEvents InputDevice cursor SendCoreEvents EndSection
