Created attachment 527 [details]
Description of problem:
I had 2GB of RAM (DDR2, PC6400, 800MHz), I added another 2GB so now I have 4GB (2x2GB) and I'm not able to use fglrx drivers. After system reboot and Xserver startup, screen becomes violet or black and I'm not even able to switch to other virtual console with Ctrl+Alt+F1...F6. When I remove 2GB (only 2GB left) system starts normally and everything works fine.
It's not RAM issue, because I've got Windows 7 installed as well and it works fine, 4GB of memory are visible in the system. Besides when I installed Backtrack 5 which is based on Ubuntu 10.04 LTS, catalyst drivers were working correctly with 4GB RAM inserted. I borrowed 1GB of RAM and tested configuration with 3GB and it was working fine! Problem is present only when 4GB are inserted...
Steps to reproduce:
1. Download and Install catalyst dirvers according to WIKI http://wiki.cchtml.com/index.php/Ubuntu_Precise_Installation_Guide#Installing_Catalyst_Manually_.28from_AMD.2FATI.27s_site.29
2. Reboot system
DETAILED description and discussion: http://phoronix.com/forums/showthread.php?71848-Drivers-for-AMD-(ATI)-Radeon-HD-5670-in-Ubuntu-12-04-LTS-(Precise-Pangolin)&p=271419
Violet or black screen
Can you check for a system BIOS update from your mobo vendor ? That frequently fixes 4GB problems.
unfortunatelly I have the latest version of BIOS installed...
There's not a lot that can be done... how about trying to boot after disabling the ubuntu splash screen?
also, if you can boot into the pae kernel using using the console, run the commands
dkms -m fglrx v8.980 -k 3.2.0-26-generic-pae remove
dkms -m fglrx v8.980 -k 3.2.0-26-generic-pae build
dkms -m fglrx v8.980 -k 3.2.0-26-generic-pae install
also, even though you have not ran memtest yet, please give it a try.
and as for the two sticks of ram, have you tried testing one set then the other? or vise versa? also, have you checked the memory timings and complete details between the two memory sticks. It's possible that windows works fine because it's only using one of the sticks of ram to boot.
Created attachment 529 [details]
Information displayed when splash screen is not in use.
Created attachment 530 [details]
Information displayed during installation.
when I disabled splash screen, unfortunatelly system did not boot up, there were only some displays as in attachment no_sploash_screen.JPG
Removeing, building and installing fglrx module also did not help... I had to modify a little bit provided commands to loook like this:
dkms -m fglrx/8.980 -k 3.2.0-26-generic-pae remove
Regarding the sticks, I've tested configuration when each single 2GB is insert and everything is working fine. Even when 3GB are inserted it is OK- the problem is only with 4GB of RAM. It is a new set of 2GB sticks which is working in Dual Channel- I removed old 2GB stick. In Windows 7, 4GB of RAM are visible in the system.
I made today a fresh install to capture things that were displayed when I launched Live CD with Ubuntu (they also appear during system shutdown)- please see attachment fresh_install.JPG- maybe this will help to identify the root cause.
> unfortunatelly I have the latest version of BIOS installed...
According to your atisysteminfo-report.txt, motherboard model is GA-MA69G-S3H, and BIOS version is F4a. Latest BIOS for this motherboard is F8E:
May you please try update BIOS, as John Bridgman recommends?
Problem is SOLVED!
As per your recommendation- BIOS upgrade on my motherboard (Gigabyte GA-MA69G-S3H) was the solution! I upgraded to the newest version which is F8E. I was able to install latest Catalyst 12.6 drivers succesfully.
I had problems with upgradeing BIOS from Windows XP and Windows 7, but upgrade directly from BIOS with Q FLASH worked perfectly! To do it, just download BIOS from Gigabyte site, extract the archive, copy BIOS file to USB stick, plug USB stick into computer, reboot system, hit "End" button during startup and select BIOS upgrade from HDD- you can find lots of videos on YouTube about that.
Many thanks for your help and support!
Please don't forget to change bugreport status (which probably should be INVALID in this case, as this is not fglrx bug).
status changed to CLOSED INVALID.
Glad to hear that it's working now.