"ati" driver for Radeon Mobility X700 is WRONG, should be "radeon"

[shiechka]

5.10 recognized my gfx card properly during install, xorg.conf says:

Identifier "ATI Technologies, Inc. Radeon Mobility X700 (RV410)"

...and chose good resolution for my WXGA TFT:

Modeline "1280x800@60" 83.91 1280 1312 1624 1656 800 816 824 841

...but with the default "ati" driver I get a following error:

(II) Primary Device is: PCI 03:00:0
(II) ATI: Candidate "Device" section "ATI Technologies, Inc. Radeon Mobility
X700 (RV410)".
(WW) ATI: PCI Mach64 in slot 3:0:0 could not be detected!
(EE) No devices detected.

Fatal server error:
no screens found

I noticed that Xorg.conf.log says that "ati" driver is NOT FOR Radeon X700, only
the "radeon" driver is:
(II) RADEON: Driver for ATI Radeon chipsets: ATI Radeon QD (AGP),
...
ATI MOBILITY RADEON X700, ATI MOBILITY RADEON X700,
ATI RADEON X700 PRO, ATI RADEON X700 XT, ATI RADEON X700,
ATI RADEON X700 SE, ATI RADEON X700 SE,

So I substituted default driver "ati" with "radeon", and added a line for
correct handling of monitor, so that Section "Device" looks as following now:

Section "Device"
 Identifier "ATI Technologies, Inc. Radeon Mobility X700 (RV410)"
 Driver "radeon"
 BusID "PCI:3:0:0"
 Option "MonitorLayout" "LVDS"
EndSection

... and I can happily write this bug report on my laptop in X mode, at last :).
Using 1280x800!

Please make the "radeon" driver default for Radeon Mobility. Other Radeons
propably too, I guess. Note that the "LVDS" option is necessary for the screen
to display anything - without it the screen is black. However please investigate
on the "LVDS,options" correct syntax first, I found plenty of variations of this
on the net. Plain "LVDS" works for me, though not sure how for the others.

cheers
Maciek

[Daniel Stone (daniels)]

please attach a full Xorg.0.log.

[shiechka (werchowyna)]

Created an attachment (id=4405)
for default Ubuntu xorg.conf

[shiechka (werchowyna)]

Created an attachment (id=4406)
for modified xorg.conf

[Tormod Volden (tormodvolden)]

Created an attachment (id=4449)
Xorg.log on a TravelMate 8100

I have the same card (1002,5653) on a Acer Travelmate 8100. The xserver-xorg
installation (Breezy RC) picks the "ati" driver for xorg.conf and everything
works fine ! Except the missing LVDS option, and failing autodetection of
resolution, that is. From what I can see from the log, the radeon module is a
submodule of ati.

[shiechka (werchowyna)]

(In reply to comment #4)
> Created an attachment (id=4449) [edit]
> Xorg.log on a TravelMate 8100
>
> I have the same card (1002,5653) on a Acer Travelmate 8100. The xserver-xorg
> installation (Breezy RC) picks the "ati" driver for xorg.conf and everything
> works fine !

Hmm, I tried "ati" once more and stil the same errors,
https://bugzilla.ubuntu.com/attachment.cgi?id=4405. Only "raden" works. Strange?

> Except the missing LVDS option,

Does your display work without LVDS set?

[shiechka (werchowyna)]

(In reply to comment #5)
> Only "raden" works.

I meant "radeon" of course.

[Tony Austin (tony-gigaday)]

Created an attachment (id=4730)
Xorg log from HP nx8220 crash with std ati driver

[Tony Austin (tony-gigaday)]

Similar problem with Breezy on HP nx8220 (ATI Radeon X600). I installed fglrx
drivers and it works great with them. LiveCD has same problem which renders it
almost unusable - I have got around this by putting the fglrx drivers on a
memory stick and installing with a bash script.

[Henrik Nilsen Omma (henrik)]

Hello,

Have any of you had a chance to test your hardware with dapper (a live CD perhaps)? If so are you still seeing this problem? Thanks.

- Henrik

[shiechka (werchowyna)]

On Fri, 07 Apr 2006 10:11:18 -0000
Henrik Nilsen Omma <email address hidden> wrote:

> Hello,
>
> Have any of you had a chance to test your hardware with dapper

No.

> (a live CD perhaps)? If so are you still seeing this problem?

Dunno.

> Thanks.

Cheers.

BUT - this is no a method for fixing bugs:

1. Wait half a year after the bug is reported.

2. Just before the next release confirm with the user if he can check
for this bug in the incomming release.

3. The user is usually not using an experimental pre-release, so he
can't say. He is also not really eager to download a 600 MB live CD only
to make sure that "yes, this bug still bites". And to be "forced" to do
more and more testing, verifying, dowloading, reporting. C'mon, those
times are over: I, user, am not a geek/coder/developer/maniac. I am a
simple man. I want things work. I have my work.

And, moreover, I don't suffer from this bug on my Breezy knowing how to
workaround it. So please consider me not a requester for help. I don't
need this bug fixed for myself. I want it to fixed for others. You are
not doing me a favor fixing it. It is I doing you a favor reporting the
bug. And it is the case for most my bug reports.

4. If you don't understand what I mean, you are free to assume this:
"OK. Let's consider this bug fixed. Unless somebody else confirms."

C'mon.

Maciek

--------------------
W polskim Internecie s? setki milion?w stron. My przekazujemy Tobie tylko najlepsze z nich!
http://katalog.panoramainternetu.pl/

[Dennis Kaarsemaker (dennis)]

Sure we understand, but there are lots of bugs and lots of really busy
people are working on Ubuntu. They do their best to read (and solve) all
bug reports, but they can't do miracles.

 status FixReleased

[shiechka (werchowyna)]

On Sat, 08 Apr 2006 13:54:34 -0000
Dennis Kaarsemaker <email address hidden> wrote:

> Sure we understand, but there are lots of bugs and lots of really busy
> people are working on Ubuntu. They do their best to read (and solve)
> all bug reports, but they can't do miracles.

Not miracles but fixing bugs. If Ubuntu team cannot stand up to it,
what is the point of bothering people about using Ubuntu? And
developing the distro? And reporting bugs?

> status FixReleased

Nice.

--------------------
W polskim Internecie s? setki milion?w stron. My przekazujemy Tobie tylko najlepsze z nich!
http://katalog.panoramainternetu.pl/

[Dennis Kaarsemaker (dennis)]

On za, 2006-04-08 at 14:13 +0000, shiechka wrote:
> Not miracles but fixing bugs.

Which is exactly what they have been doing all the time... Your bug was
also fixed, even without seeing it on the bugtracker.
--
Dennis K.
 - Linux for human beings - http://www.ubuntu.com
 - Linux voor iedereen - http://www.ubuntu-nl.org

[Tormod Volden (tormodvolden)]

If you still experience this bug in latest Dapper, please attach Xorg.0.log for both ati and radeon again, since the old logs from Breezy are a bit outdated.

The MonitorLayout issue is our all favorite bug #22985.

[Tormod Volden (tormodvolden)]

Bug #38649 also has the wrong driver (or card detection) issue, and has some up to date X server logs.

Funny that it complains about not finding a Mach64 card, aren't the X700/X800's something completely different?