Xorg does not detect Ati Radeon mobility x1300 during Ubuntu i386 7.04 install

[FRIZI]

Tryed to install fresh Ubuntu desktop i386 7.04 but at start booting from cd it dissable x window and many other stuff. Exept of that it writes many errors what it don't did with the versions before (6.10). Install it's not smooth like other time, please fix it somehow, Ubuntu it's great !

[Scott Kitterman (kitterman)]

Please give us additional detail about your computer.

What brand and model number?
What video card?
What motherboard?

From your working 6.10 install, please give us the output of sudo lspci -vv

Thanks for the report.

[FRIZI (f-leginski)]

Hy, thanks for the fast reply.

It's a NB with specifications :

Dell inspiron 1505/6400 Intel core duo 1.63 MHz
1024 Mb Ram
Ati Radeon mobility x1300

One that many peoples uses and a lot of ppl have ubuntu on.

I tryed to install with safe graphic mode to but doesen't work like it
should to.

Then I read a post that says about a problem with installation of ubuntu
becouse of the slow speed of the cd-r, so i write the ISO of another
faster cd but the problem still there.

I've copyied couple of messages that displays at install.

Most of the loading goes ok and at loading graphic mode it writes :

"
Fatal server error: no screens found
XIO : fatal IO error
EE VESA(0): No Matching modes
EE Screen(s) found : but none have usable configuration

ipw3954 : Max thermel spin reached
ipw3945: Radio frequency kill switch on
"

That's what it says when stuck at install. If the problem apears only at my
Notebook and you could help me somehow please conntact me imediatly.

Thank You In Advance.

[Scott Kitterman (kitterman)]

If you have a command line, try entering:

sudo dpkg-reconfigure xserver-xorg

This may bring you up into a series of windows that will allow you to manually configure your display. If it does, accept the defaults unless you know for certain they are wrong. Keep good notes and report back.

[FRIZI (f-leginski)]

Hi.

I tryied to config the xserver-xorg and changed the resolution + everything
I thought that would help. It wasn't efficient at all. Problem still actual.
You know what's the problem or how could I fix it ?
It's gonna be another version of the ubuntu 7.04 that work's well ?

The last error msg was :
"
Fatal server error
no screen found
XIO: fatal IO error 104(connection reset by peer) on X server ":0.0" after 0
request (0 known processed) with 0 events remaining
"
Thanks !

[Steve Dee (mrdomino)]

I'm encountering a similar bug on a Lenovo T60 laptop with a Radeon Mobility x1400. Attached is my Xorg.0.log. Similar results with the default Feisty xorg.conf--the only changes to mine are to prefix each mode line with "1680x1050", my monitor's default resolution.

[Marquitos (marcos-truchado)]

Your trick worked for me!!!
after running sudo dpkg-reconfigure xserver-xorg I selected fdeb device, and finally I put the native resolution (1280x800) and everything works.

[Benjamin Hodgetts (enverex)]

I can confirm this. When I install Feisty on my laptop with a Mobility Radeon 9000 and first boot, X fails to start and if you look at the log file it says no screens were found. If you check the /etc/X11/xorg.conf file you'll find it's completely blank (!!). Deleting this file (and letting X figure everything out itself) or using reconfigure works, but this is odd and would likely scare people away if they couldn't get a GUI after installing the OS. I've used the same CD to install to my desktop (with an nVidia card) and it was fine then and I've reinstalled on that same laptop with the same issue just to confirm it wasn't a fluke.

[Timo Aaltonen (tjaalton)]

ben: your situation is different from this one, please open a new bug.

[Benjamin Hodgetts (enverex)]

Ah sorry, I thought they looked close enough. I'll open a new one.

[Maarten Hogendoorn (mhogendoorn)]

*** Bug: ***
I have exactly the same problem with the ATI X1300:
System->Preferences->Resolution only offers 640x480 and (default) 800x600.
What I would like is to use 1280x800.

*** Situation ***
Just unpacked my brand new 13,3" notebook (from ahtec) with ATI Mobility Raedon X1300.
Threw in Ubuntu 7.04 (downloaded 29 May 2007). All fine, but resolution is too low, also after using the restricted driver option.

*** Tried ***:
I tried dpkg-reconfigure xserver-xorg,
gave in the default where possible,
and changed the resolution to 1280x800.
No success... Couldn't start X anymore:
The last error msg was :
"
Fatal server error
no screen found
XIO: fatal IO error 104(connection reset by peer) on X server ":0.0" after 0
request (0 known processed) with 0 events remaining
"

I also tried keeping the original xorg.conf, but simply changing the modes (resolutions). Doesn't have any effect at all.

In the (falsly?) mentioned duplicate bug (#89853) somebody speaks about time-issues... could that be a lead.

Can someone help me get ATI Readon Mobility X1300 to 1200x800 ?
Thanks a lot in advance!
Maarten

[William Cattey (wdc-mit)]

Maarten:

Could you attach /var/log/Xorg.0.log to this bug?

I'm curious about details of what your X server has gotten from the EDID fetch. On my Dell Optiplex 745, the EDID fetch sometimes comes back all zeros, instead of actually providing the monitor config data.

I have an xorg.conf that seems to more consistently fetch the EDID data, but I don't yet know why.
Two differences are that the line:
     Load "i2c"
is deleted and a line is added:
     Option "UseFBDev" "true"

Things started working when I added these lines. They seem to have changed the timing of the EDID fetch such that it was successful more often.

See also efforts to find the root cause of similar symptoms under Red Hat in the bug I opened there at:
http://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=236416

-wdc

[Maarten Hogendoorn (mhogendoorn)]

William,

Here it comes: my /var/log/Xorg.0.log...
Next, I'll try your hints of adding two lines to xorg.conf (and keep you posted of course)
Thanx ! - m

[Maarten Hogendoorn (mhogendoorn)]

William,

Bad news - I (tried to) follow your hints:
a) in Xorg.conf, I removed the line with: Load "i2c"
b) I added in the section "Extension" a line with: Option "UseFBDev" "true"
c) I rebooted

Still this machine doesn't offer larger resolutions...
I'll keep trying & keep you posted - M.

[William Cattey (wdc-mit)]

I find your log output most interesting.

Someone who understands the X configuration better than I should work on the question,
"Why does the EDID data CLEARLY offer details for operation at 1280x800, but the X server configure itself down to 800x600?"

The particular problem I'm working on has to do with the question, "How much of the EDID data block really SHOULD be coming up zeros?"

If you look at your log output, you see the lines beginning, "EDID (in hex):"

Those 128 bytes should ALWAYS be the same. If you're being bitten by the same bug that bites me, you will see them coming up randomly DIFFERENT with successive runs of the X server.
This has the effect of only providing a partial fill-in of the data X wants in order to successfully configure the monitor.

Something for you to try: Restart the X server several times, and watch that EDID output.
See if it changes.

Something that might get you going is to see if, in xorg.conf, you have 1280x1024 and 1024x768 in the "Modes" subsection of your "Screen" section, looking something like this:

        SubSection "Display"
                Depth 24
                Modes "1280x1024" "1152x864" "1024x768" "800x600" "640x480"
        EndSubSection

Maybe you're being bit by the bug I will get bit by in the FUTURE when the EDID transfer becomes successful, but the X server mis-applies the data.

[William Cattey (wdc-mit)]

Yes, I was playing with those lines in xorg.conf today, and they do not seem to be relevant to whether or not I get good EDID data. Sometimes my buffer is fully filled in. Sometimes it is only partiallly filled in.

[Maarten Hogendoorn (mhogendoorn)]

WIlliam,

Restarting the X server more times didn't have any effect... nothing changed.

Good news this time ! Yeah Baby... IT WORKS this time !
The trick is exactly as you wrote: extending those "modes" line with the required (and supported) resolution.
For completeness I attached my working xorg.conf. (feel free to have a look)
The only thing I did was *adding* those 1280x800 resolutions, all the rest was default after Ubuntu installed,
and I added the restricted driver of ATI.

I am very pleased... Thanks for your precise and quick help.
Kind regards, Maarten.

[tekg (oldskewlcool)]

This def. effects all inspiron 6400 with X1300 card. I get the exact same error. dpkg-reconfigure does nothing, deleting xorg.conf makes things worse. Sigh. gnome hates ati, loves nvidia. ati hates linux. Its a never ending cycle. Also shows the maturity level of ubuntu. Guess its back to kubuntu until 7.10 :(

[devil3000 (alexisright1000)]

okay just to let some people know the resolution issue has something to do with the version of ubuntu you download i have tried 3 diffrent ones , now i can change the resolution and it happens to be the amd version works that way

[William Cattey (wdc-mit)]

One root cause of inability to find a proper X resolution is a flaky EDID transfer from the BIOS. This is due to code added to vm86.c to try and resolve noisy error messages from the auditing subsystem. This is not an issue on non-x86 systems which use the x86emu code instead of vm86 to talk to the BIOS of the ATI card.

The definitive symptom here is if the EDID hex output in Xorg.0.log is missing, or mostly zeros.

The definitive work-around until the vm86.c kernel bug is fixed, or a more clever approach to getting the EDID data is added to the X server, is to add the line:

        Option "Int10Backend" "x86emu"

to the ServerLayout section of xorg.conf.