I installed Hardy this morning, it automatically detected and asked for me to install my GFX drivers (I presume they're the current 8.4's) however, now I don't get any display.
I'm using a 3850 AGP.
I'll reinstall the OS tonight and do it manually, just wondering if this was a Hardy bug or something to with the fact it's an AGP card.
Thanks for your time.
Announcement
Collapse
No announcement yet.
Catalyst 8-4 and Ubuntu 8.04
Collapse
X
-
DefaultDepth just forces the color depth to 24bit. Just leave it there. As for Xv, try playing some videos with that extension; if the video player crashes or complains about an invalid extension/overlay, then try setting the VideoOverlay/TexturedVideo options I mentioned.
If you do force those options, which one to use will depend on what card you have; according to Bridgman, cards older than the x1xxx series had a better overlay engine than the newer cards, which in turn had much better shader processing. TexturedVideo just forces the card to render Xv using the 3d engine (shaders), therefore it being preferred with cards that have powerfull shader capabilities. You could still use TexturedVideo on, say, a 9800PRO, but chances are that it would be slower than using regular VideoOverlay. This of course, matters little if you have a powerful card, but when using a lowly IGP, every little bit of speed gains matter.
Edit: Here is how my xorg.conf looks (I use aticonfig):
Code: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" Option "TexturedVideo" "on" EndSection Section "Screen" Identifier "aticonfig-Screen[0]" Device "aticonfig-Device[0]" Monitor "aticonfig-Monitor[0]" DefaultDepth 24 SubSection "Display" Viewport 0 0 Depth 24 Modes "1680x1050" "1600x1200" "1400x1050" "1440x900" "1280x1024" "1024x768" "800x600" EndSubSection
Last edited by Melcar; 29 April 2008, 07:42 PM.
Leave a comment:
-
Can I deleta information like?:
Code:Section "Monitor" Identifier "Configured Monitor" EndSection
Leave a comment:
-
So, my xorg.conf can be like that:
Code:# 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" "ca" 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" Defaultdepth 24 EndSection Section "ServerLayout" Identifier "Default Layout" screen "Default Screen" EndSection
Code:Defaultdepth 24
Leave a comment:
-
Under hardy, fglrx does not load Xv (in any form) unless I load it manually in xorg.conf. This behavior is not present in Gutsy. This has happened to all my ATI cards. I don't know why it happens, but it does.
The driver should automatically use either VideoOverlay or TexturedVideo depending on the card being used (according to Bridgman it's VideoOverlay for pre-AVIVO cards and TexturedVideo for newer models). I confirmed this on Gutsy; my HD2900XT would work with TexturedVideo by default, while my X200 used VideoOverlay by default (both cases without having to specify anything in xorg.conf). This is supposed to be a new functionality thought, so maybe Hardy conflicts with something.
Originally posted by damentz View Post...
Oh, and two, you guys are kind of doing the installation wrong:
First, to make this clean, put the run script in its own directory, cleaner organization
Code:chmod +x ati-script.run ./ati-script.run --buildpkg Ubuntu/hardy dpkg -i *.deb m-a a-i -f fglrx-kernel-src
Last edited by Melcar; 29 April 2008, 07:29 PM.
Leave a comment:
-
You guys are making it difficult, there is no XV bug, everything is using TexturedVideo now. There used to be an xv scaling issue, but thats fixed.
Code:Option "TexturedVideo" "on"
But really, your system should work fine without any options except Driver "fglrx" and the identifier...
Oh, and two, you guys are kind of doing the installation wrong:
First, to make this clean, put the run script in its own directory, cleaner organization
Code:chmod +x ati-script.run ./ati-script.run --buildpkg Ubuntu/hardy dpkg -i *.deb m-a a-i -f fglrx-kernel-src
Last edited by damentz; 29 April 2008, 06:48 PM.
Leave a comment:
-
The GLX extension is loaded automatically, so no need to specify it. When you perform the aticonfig --initial command, aticonfig creates entries in your xorg.conf for the driver; these new entries are duplicates of the Device, Screen, and Monitor sections, so you can safely remove the older ones. Alternatevely, you can simply change the driver paramenter under the Device section to fglrx and then add the other overlay options manually without aticonfig. Either way works. Fglrx does support xrandr as well; just type in a terminal xrandr -s [resolution you want].
Hardy seems to have problems with non-native resolutions on LCDs. Don't know why. The driver worked fine on Gutsy, even with a custom 2.6.24 kernel. Another thing is the fonts; on Gutsy fglrx would cause the fonts to appear bigger and clearer, but in Hardy for some reason they get noticeably smaller.Last edited by Melcar; 29 April 2008, 10:47 AM.
Leave a comment:
-
Question about xorg.conf:
On sectection "screen", what is the utility of "Defaultdepth 24" ?
And at the end of the file what is the utility
"Code:Module" Load "glx"
Code:In Gutsy, the Xv extension is loaded automatically (for the most part), unless you specify otherwise in xorg.conf. In Hardy it does not for some reason; you have to manually specify it in your xorg.conf, either VideoOverlay or TexturedVideo.
Code:Option "TexturedVideo" "on"
Question: Is aticonfig have his owne config file?
Is the command:
Code:sudo aticonfig --initial
Does Catalyst support RandR, does aticonfig command will set my RandR.
Sorry for my english, I'me a Canadien of the Qu?bec. (French speaker)
Leave a comment:
-
If you're going to simply run the installer you most likely just need dkms and ia32-libs (if you're running 64bit). The other dependencies are for package generation, which doesn't hurt to have on your system anyways.
fglrx hardly gets updated in the Ubuntu repositories. It will probably remain at 8.4 until the new Ubuntu comes out, unless the developers decide otherwise.
Edit: One thing I have noticed in Hardy in relation to the drivers. In Gutsy, the Xv extension is loaded automatically (for the most part), unless you specify otherwise in xorg.conf. In Hardy it does not for some reason; you have to manually specify it in your xorg.conf, either VideoOverlay or TexturedVideo. I don't think it's a kernel issue, since this behavior was not present when I was using the 2.6.24 kernel in Gutsy. So after you do the aticonfig --initial part, you have to input an additional command:
Code:sudo aticonfig overlay-type=Xv
Code:Option "TexturedVideo" "on"
Last edited by Melcar; 28 April 2008, 06:10 PM.
Leave a comment:
-
Code:sudo apt-get install build-essential fakeroot dh-make debhelper debconf libstdc++5 dkms linux-headers-$(uname -r)
Finally, I have try to install the driver with the prprietary driver toll of Ubuntu 8.04 and it work. But, I don't know if they will update the depot when ATI will give the version 8-5 of Catalyst so it's important for me to understand the install procedure.
Now, the driver number, I think it's 8-3, work and this is my xorg.conf.
Code:# 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" "ca" 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" Defaultdepth 24 EndSection Section "ServerLayout" Identifier "Default Layout" screen "Default Screen" EndSection Section "Module" Load "glx" EndSection
Leave a comment:
Leave a comment: