Install FGLRX 8.01, links howto here

[Jojo]

Install FGLRX 8.01

The release notes are here

https://www2.ati.com/drivers/linux/catalyst_81_linux.html

Click on http://groups.google.com/group/x1250/web/drivers4linux - or
copy & paste it into your browser's address bar if that doesn't work.

Please post back to this group with the experiences good/bad that you
may have.

[Jojo]

FGLRX 8.02 released on 13-Feb-2008

Click on http://groups.google.com/group/x1250/web/drivers4linux - or
copy & paste it into your browser's address bar if that doesn't work.

As always, go ahead, try this driver and let the group know it goes

-JoJo

[Néstor Amigo Cairo]

I can't use this driver. I'm using Ubuntu Gutsy 7.10 with integrated
AMD690 (x1250) card 64 bit version, no success. I only get black
screen.

2008/2/14, Jojo <onetw...@gmail.com>:

--
Néstor Amigo Cairo
+34 687 96 74 81
nest...@gmail.com

[djdoo]

There is one new thing here!!

Now with 8.2 driver Option "Textured2D" "True" is working!

GLESX module is loading succesfully for the first time, and I will
test more and report back.

BTW still no XV or Textured video for 64 bit, but GLESX usage shows
that 2D driver's features are being worked on.

[JoJo jojo]

we can help you get fglrx working,
if only you can provide us more info about the problems you are facing.
follow the instructions exactly as on
http://wiki.cchtml.com/index.php/Main_Page

and report the issues if you get stuck somewhere.

-JoJo

[JoJo jojo]

I once got corruption with fgl_glxgears, immediately reverted to last release
(x86_64)

has this been reported to ATI ?

-JoJo

[djdoo]

@JoJo:

Man the same thing happens here too!!

Whenever I tried fgl_glxgears I got screen corruption and my system
froze!!

But that happens only with fgl_glxgears, all my other 3D games and
apps are working good.

So I thing fgl_glxgears has some kind of problem... At least I hope
so ;)

[djdoo]

No OMG!

It happens with all 3D apps!! Except RACER.

The new 8.2 finally loads GLESX module for our cards but breaks down
3D!!

I tried without Textured options, glesx didn't load but corruption and
freezes persisted!

So I will downgrade to 8.1 driver unfortunately :(

[seth lytle]

i'm seeing the black screen of death with this release too.

i'm the author who wrote> workaround: black screen of death on gutsy
  which was for 8.01/gutsy on asus m2a-vm hdmi
  the workaround doesn't work with 8.02
  this workaround is the result of following the cchtml instructions, and lots of trial and error

what info do you need to help me ?

[JoJo jojo]

dude, 3D is broken on fglrx 8.02 release,
do you really want to run it ?

-JoJo

[seth lytle]

yeah - the one time i got it to run (by loading 8.01, uninstalling it, installing 8.02) it was corrupted. so you're right, i don't want 8.02. but i would like _any_ version that just worked. have you gotten  8.01 to work with my hardware ?

[JoJo jojo]

Fact: fglrx 8.01 release works reliably on RS690.
(it works, not perfect, but it works)

I can help you get it running as well. describe the problem,
which guide did you follow to install FGLRX ?
post your xorg.conf, & logs.

-JoJo

[seth lytle]

i've tried quite a few different guides. specifically, i've tried this one several times:
http://wiki.cchtml.com/index.php/Ubuntu_Gutsy_Installation_Guide

what i've come up with that works is based on a mix of the cchtml above and this one:
http://ubuntuforums.org/showpost.php?p=3768746&postcount=225

see my other post for the details of what i'm doing (basically starting x without fglrx, then reinstalling).

in every case (other than my workaround above) if i enable dri, i get a black screen. i'll attach my conf and (failed) log. as i've said, i've tried perhaps 100 different configurations. i could probably modify my workaround to use the "build package" approach, and it might work.

if you've got any ideas, i'd love to hear them, but for now i am up and running and using the machine for real work.

[JoJo jojo]

follow the cchtml guide, to the letter.
follow the manual install explained there
build gutsy packages

also start out with a plain xorg.conf (delete old xorg.conf &
dpkg-reconfigure xserver-xorg to generate a new one)

then tell us what happens if you do the above, & we'll help you with it.

-JoJo

[seth lytle]

i've done that, the result is a black screen of death and the log file i uploaded

[JoJo jojo]

Black Screen of Death ?
never heard of it

are you able to switch to a vt via ctrl+alt+fx ?
is your system hung ? is there any disk activity ?
what happens on rebooting ?

if after "Black Screen of Death " you boot in recovery commandline mode
and look at xorg.log what do you find at the end?
what are the boot parameters you are passing to kernel on a normal boot ?

-JoJo

[JoJo jojo]

dude, what are you upto ?

just looked at your confs & logs

why won't you start with a clean xorg.conf ?
(it won't have the DRI 066 section for one), I don't wanna debug these
subtle things

If you follow instructions , it will work.

remove everything, xorg.conf, all instances of fglrx (modules, packages etc)
start over. Post back when you get black screen, with the details I asked for.

-JoJo

[JoJo jojo]

also removing quiet, splash etc from boot options will help with gutsy
(known bug)
if the black screen is hapening after boot

-JoJo

[seth lytle]

i have gdm disabled (for the obvious reason)

black screen of death:

screen goes black
there is a bit of disk activity for a second, but stops after that
can't switch to a new vt
ctrl-alt-delete, crtl-alt-backspace don't do anything
machine won't respond to ssh
machine does respond to ping
caps and num lock toggle the leds most of the time (not always)
the only way out that i've found is a hard reset

i haven't seen disk corruption from this
the next boot is normal
the xorg.0.log will look like what i posted
the next line in the log should say "DRI initialization successfull"

there are atleast a handful of other posts on the web of guys with my board (m2a-vm hdmi) with the same problem. too bad google doesn't index google groups :(

boot params:

title           Ubuntu 7.10, kernel 2.6.22-14-generic
root            (hd1,0)
kernel          /boot/vmlinuz-2.6.22-14-generic root=UUID=86b83a84-8185-4372-afbf-04e9f4fe488c ro quiet splash
initrd          /boot/initrd.img-2.6.22-14-generic

[seth lytle]

cchtml now refers to 8.02, which doesn't do dri (from that same page), so there's no point.

[JoJo jojo]

Next, I want to rule out other problems, and localize this as a fglrx problem.
try the radeonHD driver from here
https://groups.google.com/group/x1250/web/drivers4linux
(ubuntu PPAs)

BTW: even though cchtml refers to 8.02, there is no reason why it
won't work on 8.01 release.
If radeonHD is working correctly, then try fglrx 8.01 release with the
cchtml guide for 8.02 release.

Boot Parameters: change "quiet splash" to "nosplash"
Is your install uptodate ? do #apt-get update && apt-get upgrade

Are you using a CRT or a LCD/TFT monitor ?

and finally gdm disabled ? why,
start X via # /etc/init.d/gdm restart i.e the normal way, lets keep
things simple ;-)

-JoJo

[seth lytle]

ok - i haven't finished your last step (ie follow cchtml) yet. not too excited about radeonhd since it doesn't use dri, but i've been wanting to try it anyway. so if this doesn't work i might try it.

followed the guide. i'm up to the "configure

[seth lytle]

didn't mean to send that :)

the only issue from the last part was:

Configuration file `/etc/xdg/compiz/compiz-manager'
 ==> Deleted (by you or by a script) since installation.
 ==> Package distributor has shipped an updated version.
[ snip ]
*** compiz-manager (Y/I/N/O/D/Z) [default=N] ? y
Installing new version of config file /etc/xdg/compiz/compiz-manager ...

which looks ok to me.

so i'm up to the "configure the driver" part. i'm not starting up with gdm since i'd get a "black screen" immediately. so i just did the build from the command line. but it sounds like for this part they're assuming that gdm is running.


so what do you want me to do ? configure xorg.conf manually, start gdm, revert back to some default version of xorg.conf, try starting gdm, add gdm to the runlevel and reboot, ... ? you've seen my xorg.conf that i'm using now.

[seth lytle]

note: i still have a previous installation in /usr/share/ati. should i uninstall that ? should i have uninstall it before installing the build-pkg debs ?

[JoJo jojo]

yes please do.
start with a fglrx free system(uninstall/delete all), then load fglrx.
you don't need to write a xorg.conf, auto generate (#dpkg-reconfigure
xserver-xorg)

-JoJo

[lytles]

ok. removed all fglrx (both my --install ones, and those from the
cchtml .debs) and reconfigured xorg.conf to get it back to a known
state. tried a number of times with 8.01, and then with radeonhd. the
good news is that i never got a black screen of death. the bad news is
that i never got 8.01 to work at all, and radeonhd wouldn't do
1600x1200.

i'm attaching lytles_jojo.tgz to the group files. it has a directory
of config and log for each attempt.

tried vesa, ie without any x1250 specifics. this works (as it did
before).

then installed 8.01 per the cchtml guide (other than substituting 8.01
for 8.02). x complains about a missing amdpcsdb.default and won't run.

worked around this by copying the amdpcsdb to amdpscdb.default (see
the cmd.txt log for details). now x complains about PreInitDal failed.
i googled for a few minutes - can't remember what i found, but wasn't
enough to know what went wrong. again, x didn't run, but didn't lock
up the machine either.

next tried radeonhd. removed the fglrx debs, added the ubuntu ppa to
sources.list and update'd and upgrade'd. tried with radeonhd. first
attempts were garbled screens. but after a reboot worked ok. but i
can't get better than 1280x1024. 1600x1200 should work (and worked
with my fglrx workaround i mentioned earlier and with vesa). and no
dri or hardware gl. i'm not sure if i'm going to stick with this for
now or switch back to my fglrx workaround (assuming that it will still
work).

there are log files and xorg.confs for each try in lytles_jojo.tgz

all in all, nothing worked. and i never even got to the point at which
it could have worked or failed, ie when trying to initialize dri.

On Feb 23, 1:55 am, "JoJo jojo" <onetwoj...@gmail.com> wrote:
> yes please do.
> start with a fglrx free system(uninstall/delete all), then load fglrx.
> you don't need to write a xorg.conf, auto generate (#dpkg-reconfigure
> xserver-xorg)
>
> -JoJo
>

> On Sat, Feb 23, 2008 at 2:28 AM, seth lytle <seth.ly...@gmail.com> wrote:
> > note: i still have a previous installation in /usr/share/ati. should i
> > uninstall that ? should i have uninstall it before installing the build-pkg
> > debs ?
>

> > On Fri, Feb 22, 2008 at 3:54 PM, seth lytle <seth.ly...@gmail.com> wrote:
>
> > > didn't mean to send that :)
>
> > > the only issue from the last part was:
>
> > > Configuration file `/etc/xdg/compiz/compiz-manager'
> > > ==> Deleted (by you or by a script) since installation.
> > > ==> Package distributor has shipped an updated version.
> > > [ snip ]
> > > *** compiz-manager (Y/I/N/O/D/Z) [default=N] ? y
> > > Installing new version of config file /etc/xdg/compiz/compiz-manager ...
>
> > > which looks ok to me.
>
> > > so i'm up to the "configure the driver" part. i'm not starting up with gdm
> > since i'd get a "black screen" immediately. so i just did the build from the
> > command line. but it sounds like for this part they're assuming that gdm is
> > running.
>
> > > so what do you want me to do ? configure xorg.conf manually, start gdm,
> > revert back to some default version of xorg.conf, try starting gdm, add gdm
> > to the runlevel and reboot, ... ? you've seen my xorg.conf that i'm using
> > now.
>

> > > On Fri, Feb 22, 2008 at 3:47 PM, seth lytle <seth.ly...@gmail.com> wrote:
>
> > > > ok - i haven't finished your last step (ie follow cchtml) yet. not too
> > excited about radeonhd since it doesn't use dri, but i've been wanting to
> > try it anyway. so if this doesn't work i might try it.
>
> > > > followed the guide. i'm up to the "configure
>

> > > > On Fri, Feb 22, 2008 at 11:42 AM, JoJo jojo <onetwoj...@gmail.com>

> > wrote:
>
> > > > > Next, I want to rule out other problems, and localize this as a fglrx
> > problem.
> > > > > try the radeonHD driver from here
> > > > >https://groups.google.com/group/x1250/web/drivers4linux
> > > > > (ubuntu PPAs)
>
> > > > > BTW: even though cchtml refers to 8.02, there is no reason why it
> > > > > won't work on 8.01 release.
> > > > > If radeonHD is working correctly, then try fglrx 8.01 release with the
> > > > > cchtml guide for 8.02 release.
>
> > > > > Boot Parameters: change "quiet splash" to "nosplash"
> > > > > Is your install uptodate ? do #apt-get update && apt-get upgrade
>
> > > > > Are you using a CRT or a LCD/TFT monitor ?
>
> > > > > and finally gdm disabled ? why,
> > > > > start X via # /etc/init.d/gdm restart i.e the normal way, lets keep
> > > > > things simple ;-)
>
> > > > > -JoJo
>

> > > > > On Fri, Feb 22, 2008 at 9:37 PM, seth lytle <seth.ly...@gmail.com>

> > > > > > On Fri, Feb 22, 2008 at 1:03 AM, JoJo jojo <onetwoj...@gmail.com>

> > <seth.ly...@gmail.com>

> > <onetwoj...@gmail.com>

> > > > > > > > wrote:
>
> > > > > > > > > > > Fact: fglrx 8.01 release works reliably on RS690.
> > > > > > > > > > > (it works, not perfect, but it works)
>
> > > > > > > > > > > I can help you get it running as well. describe the
> > problem,
> > > > > > > > > > > which guide did you follow to install FGLRX ?
> > > > > > > > > > > post your xorg.conf, & logs.
>
> > > > > > > > > > > -JoJo
>
> > > > > > > > > > > On Thu, Feb 21, 2008 at 8:19 AM, seth lytle

> > <seth.ly...@gmail.com>

> > > > > > > > wrote:
> > > > > > > > > > > > yeah - the one time i got it to run (by loading 8.01,
> > > > > > uninstalling
> > > > > > > > it,
> > > > > > > > > > > > installing 8.02) it was corrupted. so you're right, i
> > don't want
> > > > > > > > 8.02.
> > > > > > > > > > but i
> > > > > > > > > > > > would like _any_ version that just worked. have you
> > gotten 8.01
> > > > > > to
> > > > > > > > work
> > > > > > > > > > > > with my hardware ?
>
> > > > > > > > > > > > On Mon, Feb 18, 2008 at 11:13 PM, JoJo jojo

> > > > > > <onetwoj...@gmail.com>

> > > > > > > > > > wrote:
>
> > > > > > > > > > > > > dude, 3D is broken on fglrx 8.02 release,
> > > > > > > > > > > > > do you really want to run it ?
>
> > > > > > > > > > > > > -JoJo
>
> > > > > > > > > > > > > On Feb 19, 2008 8:06 AM, seth lytle

> > <seth.ly...@gmail.com>

> > > > > > wrote:
> > > > > > > > > > > > > > i'm seeing the black screen of death with this
> > release too.
>
> > > > > > > > > > > > > > i'm the author who wrote> workaround: black screen
> > of death
> > > > > > on
> > > > > > > > gutsy
> > > > > > > > > > > > > > which was for 8.01/gutsy on asus m2a-vm hdmi
> > > > > > > > > > > > > > the workaround doesn't work with 8.02
> > > > > > > > > > > > > > this workaround is the result of following the
> > cchtml
> > > > > > > > > > instructions,
> > > > > > > > > > > > and
> > > > > > > > > > > > > > lots of trial and error
>
> > > > > > > > > > > > > > what info do you need to help me ?
>
> > > > > > > > > > > > > > On Feb 15, 2008 12:12 AM, JoJo jojo

> > <onetwoj...@gmail.com>

> > > > > > > > wrote:
>
> > > > > > > > > > > > > > > we can help you get fglrx working,
> > > > > > > > > > > > > > > if only you can provide us more info
>

> ...
>
> read more »

[JoJo jojo]

Hey
I understand it must be very frustrating for you,
I was hoping you would have it running successfully last weekend.

I probably haven't faced the same problems as you have,
as I have been upgrading from one release to the next(except 8.02).
(but you've had to start from scratch)

also there was a broken restricted modules update
(but I hope that problem went away when I asked you to update the
system software)

I think your restricted modules are out of whack !
Update the dependencies for every module.
#depmod -a
#m-a update,prepare
then give fglrx another try

there's no need to remove fglrx to try radeonhd
(just change Driver "fglrx" to "radeonHD" & removing fglrx specific
options in xorg.conf)
I suggest keeping 2 separate xorg.conf s that you can easily switch
between them.

regarding radeonhd and modes
see if
#xrandr -q
lists your requested mode(1600x1200?) if not then its because its not
detected correctly
from your monitor, however there is a workaround by adding a "virtual" mode
bigger that what you may need, explanation is here
http://wiki.x.org/wiki/radeonhd
so add a virtual mode >= 1600x1200 and you'll get your fav screen resolution

hope all this finally fixes things for you.

(BTW I used to get preinitdal failed etc but it did'nt affect X)
and there's no need for vesa logs(but read them anyway)
theres no need to use vesa, use radeohd as the fallback.

when you try fglrx next, note down the outputs of various commands
fglrxinfo, glxinfo,

lets get your 3d working

-JoJo

[Oleksiy Kokachev]

> there's no need to remove fglrx to try radeonhd
> (just change Driver "fglrx" to "radeonHD" & removing fglrx specific
> options in xorg.conf)
> I suggest keeping 2 separate xorg.conf s that you can easily switch
> between them.

Hmm.. I don't think so. I got some problems, when I tried to use
ati-radeon driver with fglrx module loaded.
The problem disappeared when I blacklisted it.
So to avoid future unexpected problems with radeon/radeonhd drivers,
add fglrx module to blacklist in /etc/modprobe.d
and _reboot_ your system.
Moreover, if you just rmmod the module it does _not_ help.
fglrx module should not be loaded _at_all_ I you want to give try to
radeon/radeonhd drivers.

Best regards, Oleksiy.

[JoJo jojo]

Hi Oleksiy

I thought cchtml wiki asked to blacklist fglrx anyways,
(its always been that way with me)

I have been successfully switching between fglrx & radeonhd
probably radeon Vs. RadeonHD may require what you say,
but its not needed between fglrx & radeonhd

-JoJo

[Oleksiy Kokachev]

Hi JoJo.
You are lucky, if everything went well with fglrx loaded.
In my case I spent two days, trying to find the bug.
So It's only my recommendation to blacklist this (blackbox?) fglrx
module before using radeon/radeonhd. It's everyone's choice: to follow
it or not. :-)
Nobody can even predict possible side effects, caused by this module.
Good luck and best regards, Oleksiy.

[JoJo jojo]

its not luck,
Its a matter of following instructions
http://wiki.cchtml.com/index.php/Ubuntu_Gutsy_Installation_Guide#Method_2:_Install_the_Catalyst_8.2_Driver_Manually
clearly says, disable module & blacklist fglrx (ubuntu's restricted
module may load and conflict etc)
(and this is to MAKE fglrx work correctly !!!)

-JoJo

[Oleksiy Kokachev]

Dear JoJo.
We are talking about different cases:
1. You talking about _manual_ install of fglrx driver onto system with
restricted modules installed.
2. What I'm saying is that fglrx module DOES conflicts with radeon
driver and can conflict with radeonhd driver.
Right?
thanks.

[JoJo jojo]

The radeonhd module is for the xorg server, not the kernel so it gets
loaded automatically by X on startup, not via modprobe like a kernel
module. There is no 3D support in the radeonHD driver yet, so A)
theres not kernel modules to be loaded yet and B) as such there no
hardware driver for mesa so it falls back to software indirect
rendering.

when we do do 3D , we may need kernel voodoo ;-)

you may be right about radeon w/ fglrx conflicts, I'll have to ask
someone or try it soon.

-JoJo

[Oleksiy Kokachev]

Dear JoJo.
I know how it works and I know the difference between kernel module
and shared library, which we call "X.org module".
The main issue is not 3D. There could be problems/conflicts with
resource allocations, incorrect hardware init/close etc.
And this COULD lead to problems with radeonhd, cause It DID lead to
problems with radeon driver in my case.
So I think, that if You don't use fglrx driver in xorg.conf and want
to give a try to any open-source driver (radeon/radeonhd) it's much
more safe to blacklist fglrx module. that is my only one
recommendation.

[JoJo jojo]

sorry, I wasn't implying you didn't know the difference between ko & lib etc

To add to what you said, its not only "more safe" but recommended by
the fglrx install guide
at cchtml.

-JoJo

[Oleksiy Kokachev]

ok..
To make things more clear:
In fglrx install guide the main purpose of blacklisting is to avoid
conflicts of two _different_ fglrx module versions: freshly installed
and from restricted package, because their versions, i.e. API are
different and not compatible with over parts of driver.

I just mentioned, that it's more safe to blacklist fglrx module to
avoid conflicts with radeon/radeonhd driver. Even though
radeon/radeonhd are not kernel modules, but fglrx kernel module can
affect them.

So purposes of these blacklistings are quite different.

[JoJo jojo]

lets end this thread JoJo Vs. Oleksiy
with an obligatory XKCD
http://xkcd.com/386/

;-)

-JoJo

[Oleksiy Kokachev]

He-he..
It's not thread Oleksiy VS JoJo..
It's rather thread: Oleksiy AND JoJo VS fglrx and close source :-))
I just wanted to help people to avoid my mistakes. :-)

[Jojo]

Everyone quick ! tryout the 3rd linux driver to support our boards !!!
(even Ubuntu Packages are available)
Please help us test & report all bugs with our boards.

Click on http://groups.google.com/group/x1250/web/drivers4linux - or
copy & paste it into your browser's address bar if that doesn't work.

If we try even harder, maybe we can get xorg-driver-avivo devs to
support our boards as well ;-)

-JoJo

[macauhtpc]

JoJo,

I think you still need the latest dri and mesa in order to make the
ati driver work. PPAs doesn't provide the latest dri and mesa.

git clone git://anongit.freedesktop.org/git/mesa/drm
git clone git://anongit.freedesktop.org/git/mesa/mesa

-B

On Feb 28, 2:12 pm, Jojo <onetwoj...@gmail.com> wrote:
> Everyone quick ! tryout the 3rd linux driver to support our boards !!!
> (even Ubuntu Packages are available)
> Please help us test & report all bugs with our boards.
>

> Click onhttp://groups.google.com/group/x1250/web/drivers4linux- or

[JoJo jojo]

Hi Bruce

yeah, if you try to use 3D it will crash,
otherwise has some 2D advantage over RadeonHD ;-)
But otherwise the driver "works". the packages are usable.

so those using RadeonHD may test those packages.
fglrx users need their 3D < : -)

-JoJo

[djdoo]

Man I compiled and install latest drm, mesa but I cannot compile the
Driver!!

./configure gives me this error:

./configure: line 20249: syntax error near unexpected token
`XINERAMA,'
./configure: line 20249: `XORG_DRIVER_CHECK_EXT(XINERAMA,
xineramaproto)'

and as you can understand procedure stops there...

Any ideas?

[JoJo jojo]

Hi Jim

I am trying to locate & put up a page(HowTo-Radeon) about it as well !!

meanwhile you could try the ubuntu packages.

maybe the devs have broken the git heads, try an older version(very
difficult for us).

how about contacting them on -ati mailing list & CCing us?

-JoJo

[djdoo]

I commented out the wrong configure lines and driver installed but I
had to specify this in order not to install in /usr/lib/local!!

./configure --with-xorg-module-dir=/usr/lib64/xorg/modules

I have it running now but I don't have DRI... I must see if git DRM is
installed somewhere in /usr/lib or something and reinstall it at /
lib64

For more news I will inform you guys...

[djdoo]

Jo jo,

I reinstalled everything with correct PREFIXes and then got the very
latest driver git (a few minutes ago) which had a fixed configure
script and no more hacking things!

Then I ran ./configure like that:
./configure --prefix=/usr --exec-prefix=/usr --libdir=/usr/lib64 --
enable-FEATURE=DRI --with-xorg-module-dir=/usr/lib64/xorg/modules

Configure's output sais DRI=enabled but glxinfo sais no DRI but all
other things are correct such as MESA version 7.1.

Any Ideas??

I posted at Phoronix too and when I achive a working DRI installation
I will make a guide at Compiz-Fusion forum how to install the driver
successfully!

Also AIGLX, EXA and 3D (glxgears) are working here but as you can
understand without DRI they work slow ;)

[Temüjin]

I thought the avivo driver was dead? Didn't Jerome Glisse stop working
on it a while ago?

On Feb 28, 1:12 am, Jojo <onetwoj...@gmail.com> wrote:
> Everyone quick ! tryout the 3rd linux driver to support our boards !!!
> (even Ubuntu Packages are available)
> Please help us test & report all bugs with our boards.
>

> Click onhttp://groups.google.com/group/x1250/web/drivers4linux- or

[djdoo]

Hm...

I read David Airlie's blog and Phoronix posts and noone mentions DRI
for our cards through MESA.

3D is working but without DRI is very slow, also AIGLX needs DRI to
work.

When I try to playback a video my system hangs...

But David Airlie said this in his blog which is very promising
statement:

"the day that just keeps giving... rs690 users rejoice..

So I finally figured out the model for the vertex-processor less cards
(rs480/rs690), thanks to a line in the new docs about how the vertex
data is routed in TCL_BYPASS mode.

So after I actually worked out what the line meant, I managed to get
rs690 rotate and textured video up and running..

So I'm stopping now, I think I've an idea how to fix compiz for rs690
with this info, but that'll have to wait..."

We ll see... but for now I will return to fglrx again ;)

[JoJo jojo]

Hi Jim

I just remembered reading that DRI requires ddx to work,
(wait...which one is ddx again :-O)

will try again this weekend

-JoJo

[djdoo]

Damn!!

I got tired with this thing! I cannot get DRI no matter what I tried!

So back to fglrx until things become more mature for RS690...

[seth lytle]

thanks for trying to help jojo. i agree that it doesn't sound like you've seen the same problems that i'm seeing. my gut is that it is tied to my hardware (m2a-vm hdmi with 4g memory), but you could also be right that it's the fresh install vs the upgrades.

radeonhd didn't honor the "virtual" resolution - it's runing at 1152x864
fglrx - 3d doesn't work because dri didn't get initialized per the logs

i've more or less given up on this. you seem to mean well, but you've had me all over the map (just the radeonhd part resulted in perhaps 15 packages changing, and the fglrx stuff adds a bunch more - and no, you can't easily switch back and forth between the two - adding the rhd stuff upgraded a bunch of packages that fglrx was based on). either things work or they don't work (i've already got a work-around). in this case, they don't work. and i'm tired of tweaking stuff.

not sure if i'll go back to my work-around or stick with the half-resolution that radeonhd gives me.

i guess that i'd ask you to stop telling people that the drivers work. they don't for me (given a reasonable investment in time), and i think there are others that are seeing similar behavior. i do think that if i kept twiddling bits for another 40 hours, i might get the thing to run. but "hunt and peck, trial and error, maybe this will work" solutions aren't solutions.


seth

[JoJo jojo]

radeonHD resolution is not a problem,

You may now directly contact the devs at rade...@opensuse.org.

when you are ready to try again, let us know & we'll help you get started.

-JoJo

[Jojo]

Good News,
No more diagonal tearing with video playback !!!

Click on http://groups.google.com/group/x1250/web/drivers4linux - or

copy & paste it into your browser's address bar if that doesn't work.

PS: windows catalyst driver is still better than the linux fglrx :-(

[portalis]

Hi,

I have an ASUS M2A-VM HDMI board with monitors connected via the VGA
and HDMI. The new fglrx 8.3 driver detects both connections just fine
(as did earlier versions), and displays just fine on the VGA connected
monitor. Nothing is displayed on the HDMI-conneced HDTV. I'm relying
on my faulty short-term memory here, but I believe I used "aticonfig --
initial=dual-head --desktop-setup=clone" to set things up and the
resulting xorg.conf and Xorg.0.log look fine. This is unchanged from
what I saw with the earlier version of the proprietary driver and what
I also see with the current radeonHD driver.

On Mar 5, 11:35 pm, Jojo <onetwoj...@gmail.com> wrote:
> Good News,
> No more diagonal tearing with video playback !!!
>

> Click onhttp://groups.google.com/group/x1250/web/drivers4linux- or

[Jojo]

FGLRX v8.4 released on 16-Apr-2008, take it for a test ride !

Click on https://groups.google.com/group/x1250/web/drivers4linux - or

copy & paste it into your browser's address bar if that doesn't work.

Resolved Issues

* Selecting Wait for vertical retrace in the AMD Catalyst Control
Center - Linux Edition no longer results in the FPS of the application
not matching the display's vertical refresh rate

* A black screen is no longer observed on some hardware when
switching to the console or leaving the X window system when a Vesa
framebuffer console driver is used. Further details can be found in
topic number 737-30687

* Video Playback is no longer displays incorrect colors and
additional shadow images when cropping or expanding a video file using
a video player that utilizes the XVideo extension

New Feedback URL
http://support.ati.com/ics/support/default.asp?deptID=894

-JoJo

[djdoo]

I installed the driver but no big differences here...

Still whenever I press stop button at kaffeine with Xv video driver
the program crashes, a bit better 2D behaviour, and since now no
freezes which were a frequent issue with the previous driver.

But still no Dual Head Video, no Crossfire, no XvMC and no AIGLX
improvements.

[thejay]

Hi,

I have an ASUS M2A-VM HDMI and a SHARP LCD connected on the HDMI-
connected .
I have got a blank screen with fglrx and ubuntu :( Have you test
nosplash option for Grub ?
Have you fond a solution ?

Thejay

> > PS: windows catalyst driver is still better than the linux fglrx :-(- Masquer le texte des messages précédents -
>
> - Afficher le texte des messages précédents -

[JoJo jojo]

On Tue, Apr 22, 2008 at 5:45 PM, thejay <thej...@gmail.com> wrote:
>
> Hi,
>

> I have an ASUS M2A-VM HDMI and a SHARP LCD connected on the HDMI-
> connected .
> I have got a blank screen with fglrx and ubuntu :( Have you test
> nosplash option for Grub ?
> Have you fond a solution ?
>
> Thejay
>

Hi thejay

can you provide us with the os, Xserver etc version, log config etc details

which version of fglrx are you using, how did you install it?

-JoJo

[thejay]

I am using Ubuntu 7.10 with Xorg 7.3 and Catalyst 8.4

My xorg.conf
----------------------------------------------------------------------------------------

# xorg.conf (xorg 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"

# Uncomment if you have a wacom tablet
# InputDevice "stylus" "SendCoreEvents"
# InputDevice "cursor" "SendCoreEvents"
# InputDevice "eraser" "SendCoreEvents"
Identifier "Default Layout"
Screen "Default Screen" 0 0
InputDevice "Generic Keyboard"
InputDevice "Configured Mouse"
EndSection

Section "Files"
EndSection

Section "Module"
EndSection

Section "ServerFlags"
Option "AIGLX" "Off"
EndSection

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

Section "InputDevice"
Identifier "Configured Mouse"
Driver "mouse"
Option "CorePointer"
Option "Device" "/dev/input/mice"
Option "Protocol" "ImPS/2"
Option "ZAxisMapping" "4 5"
Option "Emulate3Buttons" "true"
EndSection

Section "InputDevice"
Identifier "stylus"
Driver "wacom"
Option "Device" "/dev/input/wacom"
Option "Type" "stylus"
Option "ForceDevice" "ISDV4" # Tablet PC ONLY
EndSection

Section "InputDevice"
Identifier "eraser"
Driver "wacom"
Option "Device" "/dev/input/wacom"
Option "Type" "eraser"
Option "ForceDevice" "ISDV4" # Tablet PC ONLY
EndSection

Section "InputDevice"
Identifier "cursor"
Driver "wacom"
Option "Device" "/dev/input/wacom"
Option "Type" "cursor"
Option "ForceDevice" "ISDV4" # Tablet PC ONLY
EndSection


# Configuration concerning MythTV on USB begins here
# The next should be your monitor (be it analog/digital, whatever)
attached to your case during testing & installing
## Section "Monitor"
## #Modeline "1024x768" 65 1024 1048 1184 1344 768 771
777 806 -hsync -vsync
## Identifier "Proview 568"
## VendorName "BMM"
## ModelName "BMM0238"
## HorizSync 35.0 - 58.0
## VertRefresh 55.0 - 65.0
## Option "dpms" "false"
##EndSection

# TV you're using, you can "grab" modelines from the /var/log/Xorg.
0.log file, it will have output such as below
# based on which you can force the device to use a specific modeline.
Section "Monitor"
Identifier "Sharp TV"
VendorName "Sharp"
#Mode "1024x768": 43.0 MHz (scaled from 0.0 MHz), 15.7 kHz, 60.0 Hz
(I)
#Modeline "1024x768" 42.95 1024 2320 2336 2730 768 483 485 525
interlace
#mode "800x600": 43.0 MHz (scaled from 0.0 MHz), 15.7 kHz, 60.0 Hz
(I)
#Modeline "800x600" 42.95 800 2320 2336 2730 600 483 485 525
interlace
#mode "720x576": 43.0 MHz (scaled from 0.0 MHz), 15.7 kHz, 50.0 Hz
(I)
#Modeline "720x576" 42.95 720 2320 2336 2730 576 483 485 525
interlace
#HorizSync 31.5 - 80.5
#VertRefresh 60 - 100
Option "DPMS"
EndSection

# The X1250 installed onboard on the motherboard.
Section "Device"
Identifier "ATI Technologies Inc Radeon X1200 Series"
Driver "fglrx"
# Enable TV
Option "NoTV" "no"
# Set the format & standard (unofficial ATI wiki & google will give
you a list of possibilities)
Option "TVFormat" "PAL-B"
#Option "TVStandard" "VIDEO"
# Preferably SVIDEO ofcourse
Option "TVOutFormat" "SVIDEO"
# Next are all adjustment parameters, en/disable and adjust at will
if needed
#Option "TVHSizeAdj" "110"
#Option "TVVSizeAdj" "+40"
#Option "TVHPosAdj" "-10"
#Option "TVVPosAdj" "-10"
#Option "TVHStartAdj" "0"
#Option "TVColorAdj" "0"
# Turn Overscan off, not needed unless you're using a really junky &
old TV (which is likely not to support SVIDEO in the first place :-)
Option "TVOverscan" "off"
# Next some specific testing parameters, ignore please
#Option "NoDDC" "yes"
#Option "IgnoreEDID" "yes"
#Option "GammaCorrectionI" "0x00000000"
#Option "GammaCorrectionII" "0x00000000"
#Option "TwinView" "true"
#Option "TwinViewOrientation" "Clone"
#Option "SecondMonitorHorizSync" "30-50"
#Option "SecondMonitorVertRefresh" "60"
#Option "ForceMonitors" "tmds1,tv"
#Option "ForceMonitors" "tv"
#Option "EnableMonitor" "crt1,tv"
# VideoOverlay wont work on the X1200-series yet, you'll see a
warning message about that in the Xorg.0.log
# ATI driver 8.42.3 should fix that, I have yet to find the time to
test it.
# Doesn't harm to turn it on, won't work anyway.
Option "VideoOverlay" "on"
BusID "PCI:1:5:0"
EndSection

Section "Screen"
Identifier "Default Screen"
Device "ATI Technologies Inc Radeon X1200 Series"
# Select your monitor/Tv if needed
## Monitor "Proview 568"
Monitor "Sharp TV"
DefaultDepth 24
SubSection "Display"
Modes "1024x768" "800x600"
#Modes "720x576"
EndSubSection
EndSection

Section "Extensions"
# ATI doesn't like this
Option "Composite" "Off"
EndSection
-------------------------------------------------------------------------------------------------------------

On 22 avr, 16:30, "JoJo jojo" <onetwoj...@gmail.com> wrote:

[JoJo jojo]

Hi thejay

I was gonna recommend the FGLRX 8.4 with the manual install on wiki.cchtml.com
but FGLRX 8.4 is of hopeless quality, it crashes, even if you play a video !!!

even though they claim to have resolved 1 of many black screen issues

"A black screen is no longer observed on some hardware when switching
to the console or leaving the X window system when a Vesa framebuffer
console driver is used. Further details can be found in topic number
737-30687"

I am not sure what to recommend,
all fglrx with XV support crash, and you are not interested in any
fglrx without XV.

XVideo is implemented on x1200 as TexuredVideo. I believe there is a
config file on this group about it.

but you haven't posted the -logverbose 10 xorg.log so we can't tell
whether its a misconfiguration or
fglrx being naughty

-JoJo

[seth lytle]

i have the same motherboard (asus ms2-vm hdmi) and i'm getting black screens (hard reset required) too, whenever i had dri enabled. i think the last version i tried was 8.2. is anyone using this motherboard successfully with dri ?

i'm using radeonhd and it's ok, but can't use the full capability of the graphics.

[thejay]

My screen don't start with fglrx module :(

Only vesa drives works in 1920x1080 .

I have no idea for resolve my problem ...

I try to post my Xorg.0.log tonight

On 23 avr, 15:55, "seth lytle" <seth.ly...@gmail.com> wrote:
> i have the same motherboard (asus ms2-vm hdmi) and i'm getting black screens
> (hard reset required) too, whenever i had dri enabled. i think the last
> version i tried was 8.2. is anyone using this motherboard successfully with
> dri ?
>
> i'm using radeonhd and it's ok, but can't use the full capability of the
> graphics.
>
>
>

> On Tue, Apr 22, 2008 at 10:30 AM, JoJo jojo <onetwoj...@gmail.com> wrote:

>
> > On Tue, Apr 22, 2008 at 5:45 PM, thejay <theja...@gmail.com> wrote:
>
> > >  Hi,
>
> > >  I have an ASUS M2A-VM HDMI and a SHARP LCD connected on the HDMI-
> > >  connected .
> > >  I have got a blank screen with fglrx and ubuntu :( Have you test
> > >  nosplash option for Grub ?
> > >  Have you fond a solution ?
>
> > >  Thejay
>
> > Hi thejay
>
> > can you provide us with the os, Xserver etc version, log config etc
> > details
>
> > which version of fglrx are you using, how did you install it?
>

> > -JoJo- Masquer le texte des messages précédents -

[thejay]

yes It's the same problème ...

Please Help ! ( Leeloo Dallas, 5th element ;) )

On 23 avr, 15:55, "seth lytle" <seth.ly...@gmail.com> wrote:

> i have the same motherboard (asus ms2-vm hdmi) and i'm getting black screens
> (hard reset required) too, whenever i had dri enabled. i think the last
> version i tried was 8.2. is anyone using this motherboard successfully with
> dri ?
>
> i'm using radeonhd and it's ok, but can't use the full capability of the
> graphics.
>
>
>

> On Tue, Apr 22, 2008 at 10:30 AM, JoJo jojo <onetwoj...@gmail.com> wrote:

>
> > On Tue, Apr 22, 2008 at 5:45 PM, thejay <theja...@gmail.com> wrote:
>
> > >  Hi,
>
> > >  I have an ASUS M2A-VM HDMI and a SHARP LCD connected on the HDMI-
> > >  connected .
> > >  I have got a blank screen with fglrx and ubuntu :( Have you test
> > >  nosplash option for Grub ?
> > >  Have you fond a solution ?
>
> > >  Thejay
>
> > Hi thejay
>
> > can you provide us with the os, Xserver etc version, log config etc
> > details
>
> > which version of fglrx are you using, how did you install it?
>

> > -JoJo- Masquer le texte des messages précédents -

[Jojo]

Click on https://groups.google.com/group/x1250/web/drivers4linux
to install it

Resolved issues

* Support for video playback on the second head in dual head mode
is now available. Further details can be found in topic number
737-26985

* Unresolved symbols in Xorg log under RHEL 4u6 32 and 64 bit no
longer occur. Further details can be found in topic number 737-34284

* The desktop background color is no longer displayed incorrectly
when using xcommgr. Further details can be found in topic number
737-34285

* Change VT no longer fails when kernel module is not loaded.
Further details can be found in topic number 737-34286

* Switching to the virtual terminal multiple times no longer
results in X displaying corruption. Further details can be found in
topic number 737-34287

* Catalyst Control Center: The Preference page is now localized
for all supported languages. Further details can be found in topic
number 737-34275

* The Linux kernel module is no longer installed to wrong location
if the Linux kernel is updated. Further details can be found in topic
number 737-34288

* Random system hangs no longer occur when calls to the ATI driver
are made from Ring3. Further details can be found in topic number
737-34289

* X window no longer fails to respond when GoogleEarth is
maximized. Further details can be found in topic number 737-34290

* A segmentation fault no longer occurs when running SPECViewperf
on systems containing an ATI FireGL V5100 series product and running
SUSE 10.3 x86. Further details can be found in topic number 737-34276

* Enabling Composite extension no longer displays 8x AA for
graphic cards that do not support 8x AA under the Ubuntu 7.10
operating system. Further details can be found in topic number
737-34291

* Display corruption is no longer noticed at logon when compiz is
enabled. Further details can be found in topic number 737-34292

* Launching the glxgears application no longer results in
segmentation faults. Further details can be found in topic number
737-34293

* GoogleEarth: Launching the application in horizontal mode on a
system running X no longer results in corruption being noticed.
Further details can be found in topic number 737-34293

* Specviewperf 8.1 64 bit version: Segmentation faults no longer
occurs on IGP systems. Further details can be found in topic number
737-34294

* Maya 2008: Moving the render window no longer results in the
operating system failing. Further details can be found in topic number
737-34295

* Glxgears corruption is no longer noticed in big desktop mode.
Further details can be found in topic number 737-34296

Try out this release and let the group know the issues

-JoJo

[Jojo]

Hi Everyone

ATI has released the new fglrx, please take it for a test ride,
and tell us all about the driver quality

get the driver from here
https://groups.google.com/group/x1250/web/drivers4linux

-JoJo