HD3850, ATI drivers and Hardy

[k33l0r]

Hi,


I'm trying to get the ATI drivers to work in my fresh install of Hardy.


I've tried just enabling the restricted drivers in Ubuntu - results in a black screen on reboot.

I've tried installing the drivers using Envy NG - results in a black screen on reboot.

And I've tried installing the drivers using ATI's own installer, with the same result as before.


Has somebody solved this problem themselves? Indeed, any help will be welcome.

If you need more information on my system, please ask.

Basics:

Intel Core 2 Duo E6750
4GB DDR2 800MHz
ATI HD3850 256MB

[John.Michael.Kane]

Hi,


I'm trying to get the ATI drivers to work in my fresh install of Hardy.


I've tried just enabling the restricted drivers in Ubuntu - results in a black screen on reboot.

I've tried installing the drivers using Envy NG - results in a black screen on reboot.

And I've tried installing the drivers using ATI's own installer, with the same result as before.


Has somebody solved this problem themselves? Indeed, any help will be welcome.

If you need more information on my system, please ask.

Basics:

Intel Core 2 Duo E6750
4GB DDR2 800MHz
ATI HD3850 256MB


Can you post your xorg.conf?

sudo gedit /etc/X11/xorg.conf

[k33l0r]

Can you post your xorg.conf?

Sure here it is.

# 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" "pc105"
Option "XkbLayout" "us"
EndSection

Section "InputDevice"
Identifier "Configured Mouse"
Driver "mouse"
Option "CorePointer"
EndSection

Section "Device"
Identifier "Configured Video Device"
EndSection

Section "Monitor"
Identifier "Configured Monitor"
EndSection

Section "Screen"
Identifier "Default Screen"
Monitor "Configured Monitor"
Device "Configured Video Device"
EndSection

Section "ServerLayout"
Identifier "Default Layout"
Screen "Default Screen"
EndSection

[John.Michael.Kane]

Sure here it is.

# 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" "pc105"
Option "XkbLayout" "us"
EndSection

Section "InputDevice"
Identifier "Configured Mouse"
Driver "mouse"
Option "CorePointer"
EndSection

Section "Device"
Identifier "Configured Video Device"
Driver "fglrx"
EndSection

Section "Monitor"
Identifier "Configured Monitor"
EndSection

Section "Screen"
Identifier "Default Screen"
Monitor "Configured Monitor"
Device "Configured Video Device"
EndSection

Section "ServerLayout"
Identifier "Default Layout"
Screen "Default Screen"
EndSection

You can try adding the line listed below to Section "Device" in your xorg. So that it looks like the above.

Driver "fglrx"

Then you can try running
sudo aticonfig --initial -f

From there you should be able to restart your machine.

Then run fglrxinfo from the terminal.

Edit: The post below may also be of some help to you.
http://ubuntuforums.org/showpost.php?p=4800609&postcount=3

[k33l0r]

I tried your instructions. Unfortunately the result is the same: a blank black screen on reboot. I have to use the "recovery mode" to reconfigure X.

But here is the xorg.conf written by aticonfig.

# 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 "ServerLayout"
Identifier "Default Layout"
Screen 0 "aticonfig-Screen[0]" 0 0
EndSection

Section "Files"
EndSection

Section "Module"
EndSection

Section "InputDevice"
Identifier "Generic Keyboard"
Driver "kbd"
Option "XkbRules" "xorg"
Option "XkbModel" "pc105"
Option "XkbLayout" "us"
EndSection

Section "InputDevice"
Identifier "Configured Mouse"
Driver "mouse"
Option "CorePointer"
EndSection

Section "Monitor"
Identifier "aticonfig-Monitor[0]"
Option "VendorName" "ATI Proprietary Driver"
Option "ModelName" "Generic Autodetecting Monitor"
Option "DPMS" "true"
EndSection

Section "Device"
Identifier "aticonfig-Device[0]"
Driver "fglrx"
EndSection

Section "Screen"
Identifier "aticonfig-Screen[0]"
Device "aticonfig-Device[0]"
Monitor "aticonfig-Monitor[0]"
DefaultDepth 24
SubSection "Display"
Viewport 0 0
Depth 24
EndSubSection
EndSection

[soxs]

Have a look at mine, I own a radeon 3870HD factory OC and it works pretty fine. Attached my xorg.conf
i installed the drivers via envyng's gtk interface (first removed all the old garbage with envyng)

[ziggyw00t]

I had this same problem with a 3850 and 3870. Do you have a "memory hole" enabled in the bios? If so, disable it and that should fix the problem. Of course, then you'll be limited to about 3.2 GB RAM max.

[soxs]

Thats a unecessary step, at least for me. I have 3.9 out of 4 GiB RAM availiable/accesssable and 3870 still works fine.

[k33l0r]

I had this same problem with a 3850 and 3870. Do you have a "memory hole" enabled in the bios? If so, disable it and that should fix the problem. Of course, then you'll be limited to about 3.2 GB RAM max.

I shouldn't think so, I've had this card working in 7.10 earlier. Back then Envy got it to work.

[k33l0r]

Here is the xorg.conf generated by aticonfig --initial -f
In other words, the xorg.conf with which x refuses to work.

xorg.conf:

# 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 "ServerLayout"
Identifier "Default Layout"
Screen 0 "aticonfig-Screen[0]" 0 0
EndSection

Section "Files"
EndSection

Section "Module"
EndSection

Section "InputDevice"
Identifier "Generic Keyboard"
Driver "kbd"
Option "XkbRules" "xorg"
Option "XkbModel" "pc105"
Option "XkbLayout" "us"
EndSection

Section "InputDevice"
Identifier "Configured Mouse"
Driver "mouse"
Option "CorePointer"
EndSection

Section "Monitor"
Identifier "aticonfig-Monitor[0]"
Option "VendorName" "ATI Proprietary Driver"
Option "ModelName" "Generic Autodetecting Monitor"
Option "DPMS" "true"
EndSection

Section "Device"
Identifier "aticonfig-Device[0]"
Driver "fglrx"
EndSection

Section "Screen"
Identifier "aticonfig-Screen[0]"
Device "aticonfig-Device[0]"
Monitor "aticonfig-Monitor[0]"
DefaultDepth 24
SubSection "Display"
Viewport 0 0
Depth 24
EndSubSection
EndSection

[soxs]

have a look at this thread: http://ubuntuforums.org/showthread.php?t=767934

[ASULutzy]

I had to edit my mtrr tables to get my ati card to work with fglrx drivers and more than 3.2 GB of memory.

Paste the output of cat /proc/mtrr

[k33l0r]

I removed the ATI drivers using EnvyNG, rebooted and then installed them again using the "Ubuntu method". I then rebooted with this xorg.conf:

# 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 "Module"
Load "bitmap"
Load "vbe"
Load "ddc"
Load "freetype"
Load "int10"
# strangely this will not be used/loaded at all
# Load "type1"
Load "glx"
Load "dri"
Load "extmod"
EndSection


Section "InputDevice"
Identifier "Generic Keyboard"
Driver "kbd"
Option "XkbRules" "xorg"
Option "XkbModel" "pc105"
Option "XkbLayout" "us"
EndSection

Section "InputDevice"
Identifier "Configured Mouse"
Driver "mouse"
Option "CorePointer"
EndSection

Section "Device"
Identifier "Configured Video Device"
Driver "fglrx"
Option "XAANoOffscreenPixmaps" "1"
Option "TexturedVideo" "1"
Option "TexturedVideoSync" "1"
Option "BackingStore" "1"
Option "Textured2D" "1"
Option "TexturedXRender" "1"
Option "BackingStore" "1"
Option "AccelMethod" "EXA"
Option "DRI" "1"
Option "DynamicClocks" "1"
Option "ForceGenericGPU" "0"
Option "VideoOverlay" "0"
Option "OpenGLOverlay" "0"
EndSection


Section "Monitor"
Identifier "Configured Monitor"
EndSection

Section "Screen"
Identifier "Default Screen"
Monitor "Configured Monitor"
Device "Configured Video Device"
Defaultdepth 24
SubSection "Display"
Modes "1680x1050" "1280x1024" "1024x768" "800x600" "640x480"
EndSubSection
EndSection

Section "ServerLayout"
Identifier "Default Layout"
screen "Default Screen"
EndSection

Section "DRI"
Mode 0666
EndSection

Section "ServerFlags"
Option "AIGLX" "1"
EndSection

Section "Extensions"
Option "RENDER" "1"
Option "XVideo" "1"
Option "Composite" "1"
Option "Damage" "1"
EndSection

Alas, to no avail. On reboot I was met with the (by now) familiar blank screen.

I tried to look in my BIOS for any mention of a "memory hole", or anything remotely like it, but I found nothing. I have a Asus P5K motherboard.

Perhaps the cause of this trouble is that I'm using the 64-bit Ubuntu. Since I've had the drivers working in a 32-bit 7.10 maybe I should reinstall a 32-bit version?

[k33l0r]

I had to edit my mtrr tables to get my ati card to work with fglrx drivers and more than 3.2 GB of memory.

Paste the output of cat /proc/mtrr

Sure, here it is:
matt@ubuntu-pc:~$ cat /proc/mtrr
reg00: base=0xd0000000 (3328MB), size= 256MB: uncachable, count=1
reg01: base=0xe0000000 (3584MB), size= 512MB: uncachable, count=1
reg02: base=0x00000000 ( 0MB), size=4096MB: write-back, count=1
reg03: base=0x100000000 (4096MB), size= 512MB: write-back, count=1
reg04: base=0x120000000 (4608MB), size= 256MB: write-back, count=1

[soxs]

I removed the ATI drivers using EnvyNG, rebooted and then installed them again using the "Ubuntu method". I then rebooted with this xorg.conf:

# 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 "Module"
Load "bitmap"
Load "vbe"
Load "ddc"
Load "freetype"
Load "int10"
# strangely this will not be used/loaded at all
# Load "type1"
Load "glx"
Load "dri"
Load "extmod"
EndSection


Section "InputDevice"
Identifier "Generic Keyboard"
Driver "kbd"
Option "XkbRules" "xorg"
Option "XkbModel" "pc105"
Option "XkbLayout" "us"
EndSection

Section "InputDevice"
Identifier "Configured Mouse"
Driver "mouse"
Option "CorePointer"
EndSection

Section "Device"
Identifier "Configured Video Device"
Driver "fglrx"
Option "XAANoOffscreenPixmaps" "1"
Option "TexturedVideo" "1"
Option "TexturedVideoSync" "1"
Option "BackingStore" "1"
Option "Textured2D" "1"
Option "TexturedXRender" "1"
Option "BackingStore" "1"
Option "AccelMethod" "EXA"
Option "DRI" "1"
Option "DynamicClocks" "1"
Option "ForceGenericGPU" "0"
Option "VideoOverlay" "0"
Option "OpenGLOverlay" "0"
EndSection


Section "Monitor"
Identifier "Configured Monitor"
EndSection

Section "Screen"
Identifier "Default Screen"
Monitor "Configured Monitor"
Device "Configured Video Device"
Defaultdepth 24
SubSection "Display"
Modes "1680x1050" "1280x1024" "1024x768" "800x600" "640x480"
EndSubSection
EndSection

Section "ServerLayout"
Identifier "Default Layout"
screen "Default Screen"
EndSection

Section "DRI"
Mode 0666
EndSection

Section "ServerFlags"
Option "AIGLX" "1"
EndSection

Section "Extensions"
Option "RENDER" "1"
Option "XVideo" "1"
Option "Composite" "1"
Option "Damage" "1"
EndSection

Alas, to no avail. On reboot I was met with the (by now) familiar blank screen.

Did you copy the xorg.conf from the thread or did you adjust your xorg.conf so it has fglrx and some of the performence options? If you used copy/paste it was damned to fail.



Perhaps the cause of this trouble is that I'm using the 64-bit Ubuntu. Since I've had the drivers working in a 32-bit 7.10 maybe I should reinstall a 32-bit version?
Definitely not. I am running 64 bit ubuntu 8.04 and it works pretty fine.
Note: with 32bit ubuntu You won't be able to use 4GB of RAM.

Edit: In case you can swith via CONTROL-ALT-F1 to terminal, plx post the autput of fglrxinfo and glxinfo |grep render.And cbackup the file
/var/log/Xorg.0.log via sudo cp -vf /var/log/Xorg.0.log /home/USERNAME/Xorg.0.log.txt && sudo chmod -vf 0755 /home/USERNAME/Xorg.0.log (this copies the log file to your desktop and gives you permissions to access it)
Afterward make your PC boot without the fglrxdriver. Attach the Xorg.0.log here (there should be some necessary info within).

[ASULutzy]

Sure, here it is:
matt@ubuntu-pc:~$ cat /proc/mtrr
reg00: base=0xd0000000 (3328MB), size= 256MB: uncachable, count=1
reg01: base=0xe0000000 (3584MB), size= 512MB: uncachable, count=1
reg02: base=0x00000000 ( 0MB), size=4096MB: write-back, count=1
reg03: base=0x100000000 (4096MB), size= 512MB: write-back, count=1
reg04: base=0x120000000 (4608MB), size= 256MB: write-back, count=1


I believe you are having the same problem that I was...

Two quick questions, can you boot into Ubuntu with 4GB of ram using vesa as your driver instead of fglrx (edit where it says fglrx in your xorg.conf to say vesa)

And second, can you boot into Ubuntu with 3 GB of ram using fglrx.

If the answer is yes to both of those questions, you're probably going to need to edit your mtrr tables. I've got similar hardware to you, Asus P5k motherboard, Radeon 2900XT card, 4 GB of ram, and a a Q6600...

Anyway, if the answer to both those questions is yes, have a look at mtrr table editing, I made a pretty hacked together guide on it, there's probably better ones available, but you can find mine at http://ubuntuforums.org/showthread.php?p=4766662

Good luck!

edit: if you find my guide sucks, just google cat /proc/mtrr

There are lots of other people who've had to do this to fix it, I'm surprised it's not more widespread an issue

[k33l0r]

I think I'll switch to the 32-bit version anyway as I also can't get my Canon multifunctional to work either (well, printing is fine but the scanner doesn't work) as Canon only supply 32-bit drivers.

I know that I'll only have 3.x GB of RAM available, but then again I haven't managed to fill that up before either...

Thanks for all the help anyway. If these problems continue with the 32-bit version, then I'll be back on the forums begging for more help...

[k33l0r]

Hey,


Just a quick follow-up...


I reinstalled using the 32-bit edition and everything is working beautifully.

The ATI drivers (Catalyst 8.4) installed just fine using the ATI installer
My Canon multifunctional works
Everything else seems to work


Thanks again for all the help.

[inphektion]

I have a Radeon HD card, forget which one exactly and use the driver from here: http://www.phoronix.com/scan.php?page=article&item=radeonhd_12&num=1
Works perfectly except 3D stuff right now.

[kingtaurus]

I think I'm experiencing the same issue with an ASUS P5K-E/Wifi, Intel Q9450, 4GB of memory and an ATi 3870. I think if you look at an /var/log/Xorg.0.log (or /var/log/Xorg.0.log.old), you should see the following warning:
(WW) RADEON(0): Failed to set up write-combining range (0xd0000000,0x10000000)
where the register numbers are machine and setup dependent. Later in the log you may see:
(EE) RADEON(0): Acceleration initialization failed

I'm wondering if this is only ASUS motherboards with this problem (or is it an Intel Chipset issue)? I'll try the mtrr fix later today (and see if this fixes the problem).

Other questions:
Will I have to redo this fix when I upgrade my kernel?
Has this issue been submitted to launchpad?

Thanks

[k33l0r]

Has this issue been submitted to launchpad

At least I have not.

[mlewis-everley]

I am not sure if it will help, But I have had a similar problem a few times with my Nvidia card.

I am not sure what monitor you are using, but does it happen to say "Out of range" on the screen before it goes black?

Mine was going to a black screen and then saying out of range, it seemed to be because the drivers were installed, but no specific resolution was added to the xorg file. As a result I think Ubuntu was trying to load at a higher resolution than my monitor could handle.

Like I said, I am not sure if that is the issue or not, but I thought I would throw the idea into the pot :).

Mo

[kingtaurus]

Can anyone else check that they have the same entry in the Xorg.0.log or Xorg.0.log prior to them using the mtrr fix (a confirmation of this would be nice).

$ grep "^(WW)" /var/log/Xorg.*
$ grep "^(EE)" /var/log/Xorg.*


Cheers,

[kingtaurus]

If you think you are having this issue, I would recommend using the mem kernel parameter (for example: mem=2048M) and trying to load the fglrx driver. Further, attach copy of /proc/mtrr before and after the kernel parameter and if possible the most recent Xorg logs (or at least the warnings and errors).


How to begin the enter parameters mode?

You need to enter all this parameter at Grub or Lilo boot prompt. For example if you are using Grub as a boot loader, at Grub prompt press 'e' to edit command before booting.

1) Select second line
2) Again, press 'e' to edit selected command
3) Type any of above parameters.
(from: http://www.cyberciti.biz/tips/10-boot-time-parameters-you-should-know-about-the-linux-kernel.html)

[kingtaurus]

I just tried disabling memory remapping in the BIOS (of my ASUS P5K-E/WIFI motherboard) and then enabling fglrx 8.3 drivers. The drivers now work without issue. So something strange is going on between the BIOS and kernel.

[Páraquedas_cascais]

Thats a unecessary step, at least for me. I have 3.9 out of 4 GiB RAM availiable/accesssable and 3870 still works fine.

Can you tell me step by step, i tried in 7.10 and now in 8.04 64bit, and even the install package gives me an error...

I will make a new full install, and than make your steps! If you please post them ... thanks!

[kurtpete]

I'm having this same issue with a Dell Optiplex 755 (with an ATI 2400xt 256mb card). I have the newest fglrx driver installed (8.4), but had the same problem with 8.3 via the repos and envyNG.

It is most certainly an issue with the way the mtrr table is being setup/recognized, but I have not been able to fix it yet. With it being from Dell, the bios is pretty restricted, and there is no memory remapping enable/disable option. The only way I can boot and not have a crash at the start of X is to remove a stick of RAM, (thereby running on 3GB instead of 4GB). Well, not entirely true, I can use the vesa driver, but that's no fun... :)

With all 4GB in, a cat /proc/mtrr gives me:
reg00: base=0x00000000 ( 0MB), size=65536MB: write-back, count=1
reg01: base=0xcff00000 (3327MB), size= 1MB: uncachable, count=1
reg02: base=0xd0000000 (3328MB), size= 256MB: uncachable, count=1
reg03: base=0xe0000000 (3584MB), size= 512MB: uncachable, count=1

Take a stick out, and I get:
reg00: base=0x00000000 ( 0MB), size=65536MB: write-back, count=1
reg01: base=0xbef00000 (3055MB), size= 1MB: uncachable, count=1
reg02: base=0xc0000000 (3072MB), size=1024MB: uncachable, count=1

an lspci -v gives me:
01:00.0 VGA compatible controller: ATI Technologies Inc Radeon HD 2400 XT (prog-if 00 [VGA controller])
Subsystem: Dell Unknown device 0d02
Flags: bus master, fast devsel, latency 0, IRQ 16
Memory at d0000000 (64-bit, prefetchable) [size=256M]
Memory at fe9f0000 (64-bit, non-prefetchable) [size=64K]
I/O ports at dc00 [size=256]
Expansion ROM at fea00000 [disabled] [size=128K]
Capabilities: [50] Power Management version 3
Capabilities: [58] Express Legacy Endpoint IRQ 0
Capabilities: [a0] Message Signalled Interrupts: Mask- 64bit+ Queue=0/0

So I know entry 2 being uncachable is giving me the problem with all 4GB in. I have tried many combinations of manually setting up my mtrr, but so far to no avail. The best I've been able to do is not crash, but slow my machine to an absolute crawl.

The script that seems at least doesn't crash is:
#!/bin/sh
# Disable (order is important!)
echo "disable=2" >| /proc/mtrr
echo "disable=1" >| /proc/mtrr
echo "disable=3" >| /proc/mtrr
echo "disable=0" >| /proc/mtrr
echo "base=0x00000000 size=0x80000000 type=write-back" >| /proc/mtrr
echo "base=0x80000000 size=0x40000000 type=write-back" >| /proc/mtrr
echo "base=0xC0000000 size=0x10000000 type=write-back" >| /proc/mtrr
echo "base=0xCFF00000 size=0x00100000 type=uncachable" >| /proc/mtrr
echo "base=0xD0000000 size=0x10000000 type=write-combining" >| /proc/mtrr
echo "base=0xE0000000 size=0x20000000 type=uncachable" >| /proc/mtrr
...but I know probably isn't correct due to the overlap. I have tried many other combinations of things based on other forum posts (and from other sites), but I can't seem to get it. It's somewhat like playing golf blindfolded for me, and I can't seem to get the ball in the hole. :)

I appreciate the work everyone has put into posting their information (and for the guide ASULutzy put together). I would appreciate any suggestions anyone has...

[inphektion]

kurtpete, I have this same optiplex, 4GB ram but with the radeon hd 2400 pro card. I have it working fine with the latest "radeonhd" driver installed following directions on phoronix. whats the benefit of using the fglrx driver? do you get compiz working with that?

[soxs]

You get AIGLX and Composite, and I think thats enough. Radeonhd lacks this atm and has only very limited/none 3d acceleration. It will take some more months till it gets usable/stable.

[kurtpete]

kurtpete, I have this same optiplex, 4GB ram but with the radeon hd 2400 pro card. I have it working fine with the latest "radeonhd" driver installed following directions on phoronix. whats the benefit of using the fglrx driver? do you get compiz working with that?

inphektion, guess I could have mentioned that... :) Yes, I'm running compiz, and I also need dual monitor support. It all works perfectly when I drop down to 3GB. I had contemplated turning compiz off, but I make pretty extensive use of it, so I don't really want to lose the productivity benefits I get from it...

As a side note, I have a friend at work who installed 8.04 32-bit on a same spec'd machine as me, and he's able to run the fglrx driver no problems. He can't see all 4GB though, of course.

[kurtpete]

I updated to the kernel in hardy-proposed (2.6.24-17-generic) just to see if there may be a difference. Alas, made no difference as far as this issue was concerned... :(

[kingtaurus]

Hmmm... I'm starting to think there is something wrong with the information the BIOS passes to the linux kernel on boot. If I remember correctly, the ATi driver is just a simple port of the Windows driver (although I could be mistaken).

It looks like the mtrr table entries (I think this is correct description) for the PCIe or AGP aperture and graphics memory are wrongly categorized (and thus when the driver attempts to use them it fails and X server hangs) . I've filled a bug report here about this problem:
https://bugs.launchpad.net/bugs/224404

If you are experiencing this problem or something similar, I would recommend you add to this. Please include the appropriate log files as well as hardware information.

[kurtpete]

As another update to this... I got my boss to spring for a nVidia card (8600 gt). While I still tend to think the real issue is somewhere between the bios and the kernel, the nVidia driver (latest installed through envy 169.12) handles the situation. I have all 4GB in and full compiz glory now...

[kingtaurus]

Would you mind posting a copy of /proc/mtrr kurtpete?

[kurtpete]

Would you mind posting a copy of /proc/mtrr kurtpete?

Sure, it's still the same as before (post #27), so it's:

reg00: base=0x00000000 ( 0MB), size=65536MB: write-back, count=1
reg01: base=0xcff00000 (3327MB), size= 1MB: uncachable, count=1
reg02: base=0xd0000000 (3328MB), size= 256MB: uncachable, count=1
reg03: base=0xe0000000 (3584MB), size= 512MB: uncachable, count=1

[kingtaurus]

Okay, this is just bizarre. This is why I hate having binary blobs in the kernel. Eventually once the radeonhd drivers are more mature ... I'll be switching to them. I'm just putting kurtpete info in the same post. This must be at least an AMD/ATI driver problem.

ATI (mtrr):

With all 4GB in, a cat /proc/mtrr gives me:
reg00: base=0x00000000 ( 0MB), size=65536MB: write-back, count=1
reg01: base=0xcff00000 (3327MB), size= 1MB: uncachable, count=1
reg02: base=0xd0000000 (3328MB), size= 256MB: uncachable, count=1
reg03: base=0xe0000000 (3584MB), size= 512MB: uncachable, count=1


NVidia (mtrr):
Sure, it's still the same as before (post #27), so it's:

reg00: base=0x00000000 ( 0MB), size=65536MB: write-back, count=1
reg01: base=0xcff00000 (3327MB), size= 1MB: uncachable, count=1
reg02: base=0xd0000000 (3328MB), size= 256MB: uncachable, count=1
reg03: base=0xe0000000 (3584MB), size= 512MB: uncachable, count=1

[kurtpete]

I did notice that ATI just released a new driver (version 8.5). I did not try this driver (and will be sticking with the nVidia card now and in fact no longer have the ATI card in my possession), but there is always hope for someone else affected by this issue:

http://ati.amd.com/support/drivers/linux64/linux64-radeon.html

[stomic]

Hi,


I'm trying to get the ATI drivers to work in my fresh install of Hardy.


I've tried just enabling the restricted drivers in Ubuntu - results in a black screen on reboot.

I've tried installing the drivers using Envy NG - results in a black screen on reboot.

And I've tried installing the drivers using ATI's own installer, with the same result as before.




This solved the problem of logging-out and/or rebooting with ATI drivers and KDM for me:

http://www.kalaj.org/blog/2008/05/23/solved-blank-screen-on-logoutreboot-with-ubuntukubuntu-hardy-heron-804-on-t60-with-ati-card/

good luck!

[soxs]

did you try the latest, just rleased yesterdy? (8.5)

[Computer Guru]

Hi Guys,

I'm having the same problem; and, no, the 8.5 drivers do not solve the issue.

E6750 on ASUS Maximus Formula
4GB DDR2 1066MHz
ATi HD 3870

By the way, here's the launchpad bug: https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules-2.6.24/+bug/224404

[kingtaurus]

Yeah ... thats the bug report that I submitted. My guess is that this due to the BIOS (ASUS use an AMI BIOS for P5K-E wifi - and this might be the common thing between). I would be interested to see if this crops up when on a motherboard with an AWARD BIOS.

Because the ASUS Maximus Formula uses an Intel X38 northbridge chipset.

Could this be due to an intel chipset issue?

Hi Guys,

I'm having the same problem; and, no, the 8.5 drivers do not solve the issue.

E6750 on ASUS Maximus Formula
4GB DDR2 1066MHz
ATi HD 3870

By the way, here's the launchpad bug: https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules-2.6.24/+bug/224404

[Bal_Zac]

I have a 3850, and am not experiencing any of the problems described in the thread. I have 2gb of ddr2, an AMD Athlon X2 Dual Core Processor BE-2300, (runs at 2 degrees north of room temperature :) ), and a GeForce 6100SM-M motherboard. From the ecs website the bios is Award BIOS with 4Mb Flash ROM Maybe it is an issue with the bios?

[kingtaurus]

I have a 3850, and am not experiencing any of the problems described in the thread. I have 2gb of ddr2, an AMD Athlon X2 Dual Core Processor BE-2300, (runs at 2 degrees north of room temperature ), and a GeForce 6100SM-M motherboard. From the ecs website the bios is

Have you tried disabling memory remapping in the BIOS (because, when you have less than 3 GB you should be fine to run with it disabled ... I don't know if there are any other performance changes with disabling memory mapping). If this fixes the problem, then it seems that the BIOS type (whether its AMI or AWARD) doesn't play a role.

[kingtaurus]

Hmmmm ... it looks like this bug hasn't gotten traction on launchpad.

[eamo]

did you have any luck getting your ati graphics card to work?

[cobolt01]

Install and Run Alberto Malone's Envy. It should automatically detect your card and then download and install the driver you need. It will alos configure xorg.conf. It seems very up to date. I've had it work with a GF6600GT and a Radeon 9550.
Instruction's from Alberto Malone's site.:

A) How do I Install EnvyNG?

1) If you installed Envy or EnvyNG 1.1.0 (or lower), make sure you remove them by typing:
sudo apt-get remove envy
sudo apt-get remove envyng
sudo rm -R /usr/share/envy

2) EnvyNG is available in Ubuntu's "universe" repository, therefore all you have to do is enable this repository. If you don't know how to do it, see Point E.

3) Install EnvyNG: if you use Ubuntu or Xubuntu (i.e. GNOME or XFCE) download and install EnvyNG-GTK. Open Terminal or Konsole and type:
sudo apt-get install envyng-gtk

OR if you use Kubuntu, install EnvyNG-QT (which contains the QT4 interface). Open Konsole and type: package:
sudo apt-get install envyng-qt

OR if you want to install only the textual interface just type:
sudo apt-get install envyng-core

4) Launch EnvyNG's GUI (inside a Desktop Environment such as GNOME,KDE, etc.) by selecting it in the "Applications/System Tools" menu OR if you need to use EnvyNG's textual interface you will have to type:
sudo envyng -t

If you have doubts you can read EnvyNG's man page:
man envyng


Here is more information http://www.albertomilone.com/envyngfaq.html
and if your configuration doesn't work:


C) What happens if you are no longer able to access your Desktop Environment (because of a blank screen at boot)?

Boot in RECOVERY MODE from the GRUB Menu (select it using your keyboard) almost as soon as you turn on your computer (it will take you to the command line). Then you will need to type:
envyng --uninstall-all

then simply type:
reboot

[kingtaurus]

Thanks for the post ... but this actually looks like a misconfiguration by the kernel is causing the drivers to crash (even the most recent drivers by ATi).

[basil54]

Try to edit file /boot/grub/menu.lst. Find and delete words "quiet splash" in the line "kernel /boot/vmlinuz-2.6.24-17-generic root=..... ro quiet splash".
Its help me. Good luck!

[alecmg]

Are you saying that all this mtrr mumbo jumbo gets fixed by disabling bootsplash?
I serioulsy doubt it

[kingtaurus]

I doubt it too. But, I'll give this a try later today (and report back on whether it fails or succeeds).

[kingtaurus]

It didn't help disabling quiet and splash.

[divisivemind]

One suggestion I received was to disable ip6tables. Booting to run level 2, disabling ip6tables and running startx works. Subsequently rebooting in RL5 crashes again, even though ip6tables doesn't start. I'm at a loss...

Just for info, I'm having this issue on Fedora 9 on OptiPlex 755, 4GB RAM (2x2GB), and ATI 2400 XT. It crashes AFAIK in an identical way as described in this thread.

[kingtaurus]

Okay. Now that is seriously messed up. I'll give this a try when I get a chance.

How do I disable ip6tables? (since ipv6 tables are compiled as a module, it will only be inserted into the kernel if requested lsmod | grep tables returns only the ipv4 tables module. Thus, I think I'll need clarification of what you meant by 'disable').

[Shinger]

Did somebody find a solution to this problem because i have exactly the same problem. Using envyng (getting black screen) and the normal way activating fglrx getting also a black screen..

[soxs]

If you have >=4GiB of RAM: http://ubuntuforums.org/showthread.php?p=4766662
otherwise I have no clue, though mine (RadeonHD3870 factory OC) is running like a charm

[zaleksf]

I also have a Dell Optiplex 755, Intel core 2 Quadcore, ATI HD2400 Pro, running Ubuntu 8.04 x86 64-bit, with all the updates, etc, etc. It is a dual boot machine running WinXP_Pro 32-bit, and the ATI drivers seem to work perfectly in WinXP.

My issues and mtrr file are identical to Kurpete's. Based upon what I've read, I'm not to keen on mucking around with the memory mapping - the results seem mixed, at best.

My question is: what defines the memory mapping that is the problem for these various ATI cards? Is it the ATI card itself, the ATI card BIOS, the motherboard BIOS, or the Linux kernel? Please pardon my ignorance, I am somewhat of a newbie to Ubuntu. Fundamentally, where should the long-term solution be resolved? I'm willing to wait a little longer for a software solution if it's possible...but if there isn't going to be a software solution, then I'll have to switch to another graphics card.

[soxs]

I also have a Dell Optiplex 755, Intel core 2 Quadcore, ATI HD2400 Pro, running Ubuntu 8.04 x86 64-bit, with all the updates, etc, etc. It is a dual boot machine running WinXP_Pro 32-bit, and the ATI drivers seem to work perfectly in WinXP.

My issues and mtrr file are identical to Kurpete's. Based upon what I've read, I'm not to keen on mucking around with the memory mapping - the results seem mixed, at best.

My question is: what defines the memory mapping that is the problem for these various ATI cards? Is it the ATI card itself, the ATI card BIOS, the motherboard BIOS, or the Linux kernel? Please pardon my ignorance, I am somewhat of a newbie to Ubuntu. Fundamentally, where should the long-term solution be resolved? I'm willing to wait a little longer for a software solution if it's possible...but if there isn't going to be a software solution, then I'll have to switch to another graphics card.
I would exclude a kernel issue, as it's cause by closed source driver aka fglrx. So either card/mainboard bios or the driveritself.
You may try yesterday released 8.7 fglrx driver which may brak even more or fix oyur problems

[kingtaurus]

I would exclude a kernel issue, as it's cause by closed source driver aka fglrx. So either card/mainboard bios or the driveritself.
You may try yesterday released 8.7 fglrx driver which may brak even more or fix oyur problems

Actually, according to another bug report:
https://bugs.launchpad.net/linux/+bug/210780

It looks like this also affects intel cards. The issue looks to be due the BIOS configure the MTRR to contain overlapping regions as well as regions without the appropriate state.

[kurtpete]

Actually, according to another bug report:
https://bugs.launchpad.net/linux/+bug/210780

It looks like this also affects intel cards. The issue looks to be due the BIOS configure the MTRR to contain overlapping regions as well as regions without the appropriate state.

I would agree this issue really exists between the BIOS and the kernel (in setting up the MTRR). That being said, I believe it's possible for the video driver to work around the issue (whether ATI will or not is another matter). I say this as what resolved (in a fashion) my problem was to switch to an nVidia card and appropriate driver. My MTRR with 4 GB RAM is still setup as what was problematic for the ATI driver, but I am able to run as such without issue. Yes, I took the cop-out route... :)

[Euphorion]

Hallo

I also have an ATI Graphics Card installed in my Laptop (HD2700 in a Fujitsu XI-2550 with 4GB RAM).

I was just about to install 64 Bit Hardy in replacement of my 32 Bit Hardy. Fortunately I stumbled on these Posts before so doing. Unfortunately I cannot change my Graphics Card in order to avoid the problems. So I have decided to keep the 32 Bit Hardy installation as is.

I have read several discussions with regard to the wisdom of installing a 64Bit Ubuntu, and have come to following conclusions especially bearing in mind that I am not that well versed in Linux.

1. I expect from a modern Operating System like Ubuntu that video drivers with full support are available for the major graphics cards. It is a great pity that we are somewhat dependent upon a half hearted ATI driver, that is not open source.

2. In many threads the max memory was given with 4GB (like myself) but bearing in mind that the memory pointers in a 64Bit System are larger than in a 32 Bit system, does the extra 1GB realy bring the big advantage and gain in speed?

3. I wanted to install a 64Bit system because I have read that it will bring up 50% improvement when rendering Video, which I do (Cinerella, AVIDemux), and wanted to test this, but have my doubts when the memory is not extended to over 4GB.

4. For all other normal applications like Open Office, FireFox, Thunderbird, 32 Bit is more than sufficient.

My course of action is to wait and review the situation when the successor to Hardy is released.

The other big wish that I have, is following: my 32 Bit Hardy including Applications (OpenOffice etc) are beautifully setup and personalized (dictioniaries, Menus, Icon Bars, Templates etc). I would like to be able to install Ubuntu 64 Bit "over the top" of my 32 Bit System and retain all my personal settings within the applications. The applications should then in the course of normal updating be replaced by 64Bit versions should they exist.

The reason for my request is that, for several applications I have had to employ "tricks, work arounds" offered in forums and naturally have not documented them all and have forgotten many. I would not like face the daunting task of setting up all applications from scratch.

[zaleksf]

Kurtpete, I concur with you that the issue must primarily revolve around the OS kernel and the BIOS. For a hypothetical situation with a dual boot machine (Win-64 and Ubuntu-64) using 4+GB ram and an ATI graphics card, all of the hardware and BIOS are the same (I am assuming that Win-64 users are currently not expected to investigate and rewrite the 4+GB memory structure of their machine in order to get their video cards to work). Only the memory handling structures are different. I'm assuming that ATI would use many of the same numerical graphics algorithms for Win and X video display for the drivers, and the graphic card on-board memory handling would be similar as well.

So it comes down to the OS kernel. Can Ubuntu/Xorg investigate the methods required to ensure that memory is mapped in a standard, rigorous way such that Linux video drivers have a high probability of working the first time they are implemented?

[kingtaurus]

I think if the issue is fixed for Intel cards ... it should be fixed for ATi cards as well. I'm also guessing that this issue will crop up when using the radeonhd drivers (perhaps, the issue will be slow rendering like the Intel cards).

If I get some time in the near future, I might try and make some kernel modification and try to fix this issue.

[Skraut]

Has there been any update to this? I'm also fighting the same ATI / 4GB memory issues on an Optiplex 755

[kingtaurus]

It is still not working. Even with the latest drivers in the repository. I've got a sneaking suspicion that the BIOS is giving the Linux an invalid memory table.

My guess is that this is due to the fact that Linux currently reports itself as Windows NT (I think ... not sure though). Does anyone know how to change which OS gets reported to the BIOS at boot? I would like to change it to report WindowsXP/Vista and see what tables the BIOS passes to kernel (even if this causes a kernel panic it would be interesting to know the differences between the various options).