xorg-server 1:1.0.2-0ubuntu10.3 breaks X: "no screens found"

[Ville Lindfors]

xorg-server-core 1:1.0.2-0ubuntu10.3 included a fix for a PCI support bug which inadvertently caused the X server to fail to start for some users. If you have been affected by this problem, please read the following page:

http://www.ubuntu.com/FixForUpgradeIssue

[Ville Lindfors (villi)]

Xorg log attached

[Jonathon Sim (sim)]

This also affects my Dell Inspiron 6400, also with an ATI chipset - after installing the update X doesn't start with either fglrx or vesa as the driver, giving a "No devices detected" error as in the log above.

You can get X running again by downgrading:
sudo apt-get install xserver-xorg-core=1:1.0.2-0ubuntu10
sudo /etc/init.d/gdm restart

FYI this is with the 2.6.15-26-686
and a dump of lspci is attached

[Mike Vincent (mike-vincent)]

Affects me too..
Dell Inspiron 8600 with an nvidia 5200

attached my Xorg log. Installing xserver-xorg-core_1.0.2-0ubuntu10.1_i386.deb fixed the issue for me.

[Mike Vincent (mike-vincent)]

Also attached my generic xorg.conf, created a clean one just to be sure it wasn't anything in my Xgl'd setup. Switching between the nv and nvidia drivers also yeilded no improvement.

[John Dong (jdong)]

Confirmed here, too, on nvidia hardware.

[John Dong (jdong)]

http://ubuntuforums.org/showthread.php?t=240957&highlight=xserver-xorg-core
http://ubuntuforums.org/showthread.php?t=240965&highlight=xserver-xorg-core

Two threads on the forum with users reporting the same issue.

[Gabriel Bauman (gabrielbauman)]

Same issue here, Dell Latitude D620 with an Nvidia Quadro NVS 110M video card and using the 'nvidia' driver. Downgrading the package to the previous version allowed GDM to start up, but now the screen goes blank after the gnome splash screen, after which X crashes to GDM after about 15 seconds. Even the 'safe'gnome session crashes. The only usable session is the 'terminal' one.

I was running compiz at the time that things broke, but reverting to a vanilla config is not fixing anything.

[AJ Slater (aj-slater)]

fglrx on MacBookPro also fails to detect device.

Reverting to -0ubuntu10.1 makes things work.

[Eduardo Cereto (dudus)]

same here. Both for ati radeon open driver and fglrx

[Guy Van Sanden (gvs)]

Is it possible to pull the update for the time being?

I had to make an emergency call to a friend for whom I installed Ubuntu (she's not technical) and I caught her minutes away from installing this update.

Since this seems a very severe problem, it seems prudent to pull the update until this issue is resolved.

[Rodrigo Novo (rodarvus)]

I'm working on an update to xorg-server as we speak.

Should be uploaded to the mirrors in one or two hours.

[Guy Van Sanden (gvs)]

> I'm working on an update to xorg-server as we speak.
> Should be uploaded to the mirrors in one or two hours.

Thanks Rodrigo, but still, wouldn't it we wise to pull the current update in the meantime?

The problem is that users that have breakag due to this are no longer able to login afterwards, so non-experienced users will not be able to recover with your update.

[skwirl (ubuntu-sciuridae)]

Add me to the list. Dell Insprion 600m toasted by the update.

I suggest posting detailed recovery instructions for those who can no longer launch an X session to download a fix, e.g. exact `sudo apt-get install' command. I can probably figure it out once the fix is seeded, but less experienced users won't know what to do.

It's the simplicity of Ubuntu that many of us like, vs. other distros. Please consider that as part of this request. :) Thanks.

[gist (gist)]

Recovery Instruction (with working internet connexion)
------------------------------------------------------

Run your great GNU/Linux Ubuntu Dapper Box, wait ....
Get a terminal ! try Ctrl-Alt-F2, Ctrl-Alt-F3, etc ..

login !

type now :
sudo apt-get install wget

Type this on ONE line :
sudo wget -c
http://archive.ubuntu.com/ubuntu/pool/main/x/xorg-server/xserver-xorg-core_1.0.2-0ubuntu10_i386.deb

Now the recovery fix itself ( reinstall the previous package )
dpkg -i xserver-xorg-core_1.0.2-0ubuntu10_i386.deb

Then :
/etc/init.d/gdm start

The End
Have Fun
http://gistlabs.homelinux.net/

PS: You can download the file on another computer : go there :
http://packages.ubuntulinux.org/cgi-bin/download.pl?arch=i386&file=pool%2Fmain%2Fx%2Fxorg-server%2Fxserver-xorg-core_1.0.2-0ubuntu10_i386.deb&md5sum=d359edda430ad9ac6d119e5a3bb213ad&arch=i386&type=main

[Rodrigo Novo (rodarvus)]

Thanks for the bug report, guys.

Unfortunately I am not able to reproduce this locally, on any of my machines. The latest package upload of xorg-server has two patches that might be the responsible for this issue. I have packaged two different experimental versions of xorg-server, each one removing one of the mentioned patches.

It would be muchly appreciated if you could test both versions, and report here, as soon as possible, which one fixes the problem for you.

http://people.ubuntu.com/~rodarvus/packages/dapper/xorg-server/patch_005/

and

http://people.ubuntu.com/~rodarvus/packages/dapper/xorg-server/patch_992/

Thank you in advance.

[Luinux (publicclassluis)]

Hello everybody, fist sorry if my English is poor but I'm Spanish, well I'm affected with this bug too when I do apt-get dist-upgrade, my hardware is an ATI Radeon Mobile 9700 so I've been using xorg-driver-fglrx with Kubuntu Dapper 6.06.1 I386 and official "dapper" repositories, the bug ocurrs when package "xorg-server (1:1.0.2-0ubuntu9)" is replaced with the new "xorg-server (1:1.0.2-0ubuntu10)", when machine restarts kdm isn't able to fire up any screen/device, I post the error log for people can see I say:
 ----------------------------------------------------------------------------------------
 Kdm Error:(Seen in /var/syslog)
 IO Error in XOpenDisplay
 Display :0 cannot be opened
 Unable to fire up local display :0; disabling
 -----------------------------------------------------------------------------------------
 Xserver Error:(With ati (radeon X.Org) driver)
 .........(End of log)
 (EE) No devices detected
Fatal server error:
 no screens found
 ------------------------------------------------------------------------------------------
 Xserver Error:With propietarie fglrx driver (7.0.0-8.25.18+2.6.15.11-3)
 .........(End of log)
 (EE) No devices detected
Fatal server error:
 no screens found
 ------------------------------------------------------------------------------------------
Conclusion:
 This revision of the package breaks the system, so I raise a question;
 Would be possible to downgrade the package version to the prior wich is in /var/cache/apt/archives in a clean way until the Ubuntu team fix the problem?
Thank's for any answers.

[Xargos (xargos1)]

I have the same problems as these described above - dead xserver after restarting it after the upgrade. The difference is I have a Matrox G450 graphic card.

[João Pinto (joaopinto)]

Hello,
I have tested both patches.
992 - NOT OK - Same problem
005 - OK

[Guy Van Sanden (gvs)]

Again, I want to plea to you to remove the patch until this is resolved.

Reports are still coming in on the forums from people with broken machines that installed the patch in the last hours.

[Rodrigo Novo (rodarvus)]

Just for reference: xorg-server 1:1.0.2-0ubuntu10.4 was uploaded to the archives a few moments ago. It will take a one to two hours before the packages are published and mirrored, but if you are in great hurry, you are also welcome to use the fixed packages available at:

http://people.ubuntu.com/~rodarvus/packages/dapper/xorg-server/

Please do not post any other comments to this bug, unless the fixed package doesn't works for you - so people with the old package are able to upgrade their systems too.

[Rodrigo Novo (rodarvus)]

Closing bug, package uploaded to the archives:

 xorg-server (1:1.0.2-0ubuntu10.4) dapper-updates; urgency=low
 .
   * Reverted patch 005_pci_domain.dpatch -> breaks PCI setup for many users.
     This patch will need further work before it is reintegrated into
     xorg-server again.

[Afief Halumi (afief-h)]

this one also broke(just so we can keep a list of broken hardware)

[bapoumba (bapoumba)]

Should not this appear in some way in apt-listbugs ? (tested the upgrade, no warning at all...)
Please disregard my comment if not applicable :)

[Scott Beamer (angrykeyboarder)]

I'll chime in as well. I had the same problem.

And I had to downgrade to fix it.

As far as I'm concerned, this should be "critical". It renders X useless.

See
https://lists.ubuntu.com/archives/ubuntu-users/2006-August/091420.html

----------------------------------------------------------
My Specs:

Ubuntu 6.06.1
Kernel 2.6.15-26-686
linux-restricted-modules-2.6.15-26-686
nvidia-glx
--
NVIDIA 6800 GT - 256 MB RAM
AMD 64 3500+ CPU
2.GB RAM
----------------------------------------------------------

Xorg.0.log & Xorg.0.log.old attached

[Scott Beamer (angrykeyboarder)]

oops..

I should have read further. Sorry about my previous submission ( https://launchpad.net/distros/ubuntu/+source/xorg-server/+bug/57153/comments/24 ) on this bug.

[Gergely Szirmai (gergely-szirmai)]

Hi!

I have an amd64 and if i am not mistaken the fix is for i386 only. What can I do? If there is also a fix for amd64 then sorry for the lameness.

Gergely

[Florent Mertens (givre)]

I thiink the best fix is simply to wait that the update version hit the mirror you use.

[Charl Fourie (charlfo)]

I have got the same problem (Dell Inspiron 9100; ATI Radeon 9700). I would also like to urge you to do the following:
1) Pull this update from the update server until fixed.
2) Upgrade the status ty critical.

This is very bad publicity for Ubuntu. Just imagine a corporate company having rolled out Ubuntu on their workstations in stead of Windows and suddenly Ubuntu's own upgrades break the clients!!

Attached please find my XOrg log file.

[AlejandroRiveira (ariveira)]

I can confirm the breakage i open a second bug report before noticing this one

https://launchpad.net/distros/ubuntu/+source/xorg-server/+bug/57236

[AlejandroRiveira (ariveira)]

Log in a terminal ( Crtl + Alt + F1)

Run:

sudo apt-get install xserver-xorg-core=1:1.0.2-0ubuntu10

That fixes the problem for me

[Ishaan Gulrajani (tfbfqf4x6t)]

i can confirm this (although it has already been confirmed several times). i had to reinstall ubuntu, and now im waiting for a fix to be released...

[Florent Mertens (givre)]

Fix release (please read the coment).

"Closing bug, package uploaded to the archives:

 xorg-server (1:1.0.2-0ubuntu10.4) dapper-updates; urgency=low
 .
   * Reverted patch 005_pci_domain.dpatch -> breaks PCI setup for many users.
     This patch will need further work before it is reintegrated into
     xorg-server again."

It's just a matter of time now.

[Rafael Gattringer (rafael.gattringer)]

Broken also for ATI Radeon 320M (RS200 IGP) but ok with downgrade.

[Raúl Soriano (gatoloko)]

I't seems that de "BusID" in xorg.conf is ignored and always use the same "00.0e.0" ID. Maybe the patch hardcode de BusID?

[Vincenzo Ampolo (vincenzo-ampolo)]

Confirmet in ubuntu dapper amd64 with nvidia go card:

The error is that the screen is not found.

Downgrade the package to fix everything...

[Louai Al-Khanji (slougi)]

This is a really high profile bug. Describing urgency as "low" is pretty unbelievable.

[Florent Mertens (givre)]

Urgency has nothing to do with the rapidity it will hit the repo man.

[Erik Meitner (e.meitner)]

I can also confirm this. My Xorg.log is similar to others:

...
        ATI Radeon X850 PRO (R480) (AGP), ATI Radeon X850 SE (R480) (AGP),
        ATI Radeon X850 XT (R480) (AGP), ATI Radeon X850 XT PE (R480) (AGP)
(II) ATI: Candidate "Device" section "ATI Technologies, Inc. RV350 NP [Mobility Radeon 9600/9700 M10/M11]".
(EE) No devices detected.

Fatal server error:
no screens found

Laptop is a Thinkpad t42.

0000:01:00.0 VGA compatible controller: ATI Technologies Inc RV350 [Mobility Radeon 9600 M10]

I downgraded from -0ubuntu10.3 to -0ubuntu10 and it worked again.

[Scott Beamer (angrykeyboarder)]

"Urgency has nothing to do with the rapidity it will hit the repo man."

Then what does it have to do with? I was amazed by the "low" as well. What makes it "low"?

[Walter Tautz (wtautz)]

Downgrading via dpkg and wget of previous deb worked for me also

[Colin Watson (cjwatson)]

"low" is the default you get if you just run dch to create a new changelog entry. I imagine it simply didn't occur to Rodrigo to change that, since it's never needed in the Ubuntu context anyway.

[Daniel Holbach (dholbach)]

Launchpad (which does our builds as well) does not care about the urgency=<something> setting, it's inherited from Debian, but not used.

[Rodrigo Novo (rodarvus)]

(thanks Colin and Daniel for answering this before me :) )

I was asked this same question in a private email, a few hours ago, here goes the answer I gave:

On Tue, 2006-08-22 at 03:49 -0700, Someone wrote:
> I'd like some clarification. Considering that bug 57153 was "high"
> (I'd have considered it "critical" myself. It broke ex which renders
> Ubuntu useless for the vast majority of users), why would your patch
> be "urgency=low".
>
> I'd love to know what would warrant "medium" or "high".

   urgency=high has no influence on the speed a package is
built/published on Ubuntu (meaning this field is not used by Ubuntu's build
system). Ubuntu uses different algorithms to calculate the priority of a
build: -security & -updates get higher priority, packages on main get
higher priority than packages on universe, packages with many
dependencies (such as xorg-server) get *very* high priority.

   In other words: this xorg-server update for Dapper was built
*immediately*, after it was uploaded to the archives.

   Finally, I can assure you this bug was taken care of with extreme
care, and in a rather urgent manner. (I started dealing with it as soon
as I woke up in the morning)

   Rodrigo

[Walter Tautz (wtautz)]

Just want to compliment Rodrigo for the quick fix! I'm sure all
Ubuntu users appreciate it.

On another tangent. We users should perhaps do a better job of
not creating duplicate bugs :-)

[istoyanov (istoyanov)]

I was also affected by the problem, and since I noticed that the "Monitor" section in /etc/X11/xorg.conf contained just two lines[1] (as it is the case in the xorg.conf file posted above by Sergio Oliveira), I have performed dpkg-reconfigure xserver-xorg several times to no avail. Thanks to the solution posted at ubuntuforums.org I installed manually the corrected package and everything was happily fixed.

Credits go also to Rodrigo for the quick fix!

[1] these:

Section "Monitor"
        Identifier "Generic Monitor"
        Option "DPMS"
EndSection

instead of (currently working):

Section "Monitor"
        Identifier "Generic Monitor"
        Option "DPMS"
        HorizSync 30-86
        VertRefresh 50-160
EndSection

[SonicChao (sonicchao05)]

On an HP dv1411se, after installing this update (for me) X still starts fine.

I've attached my xorg.conf though.

[Leonard Chatagnier (lenc5570)]

Me too. but I fixed mine after the update this morning by unholding
xserver-xorg-core which immediately upgraded it and X then worked on rebooting. I don't know why it was on hold as it appears as a dependency and should have been installed with xorg-server upgrade. I left Debian to get away from this stuff but Ubuntu seems to have reverted to Debian ways since the Dapper release; too bad. My issue seem to be a dependecy failure rather thain a xorg-server bug; but I no geek. Perhaps this is a different issue in my case?

[Walter Tautz (wtautz)]

the 10.4 release works for me...just did an upgrade.

[glog (glog)]

how can things like this happen?

[Walter Tautz (wtautz)]

In answer to the questionof how this happens I would surmise that
not enough testing was done on enough variable hardware. For some people
there wasn't a problem while others obviously had one. I'm not
one of the developers but a user that was effected by this.

[Mark Shuttleworth (sabdfl)]

Thanks everyone for reporting and participating in the development of a fix for this very serious issue. We have a proposed fix document, but are unable to reproduce the error on a broad enough set of test machines, so need feedback from those of you who are affected to confirm that this set of instructions is complete and appropriate:

  https://wiki.ubuntu.com/ResolutionForBug57153

Please let us know as soon as possible if these address the issue for you. In this case, please DO report if it works, as well as if it does not work, by commenting on this bug.

Note, they assume you are connected to the internet, and if you usually do that by dialup then you will need to set that up from the console. We'll post updated instructions that address that specific case soon.

Thank you!

[Fernando (fernando-medina)]

I got the same problem on an IBM THinkPad X32 with ATI Technologies Inc Radeon Mobility M6 LY card. Had to downgrade yesterday. I upgraded to new version today and no problem. Scary moment, was fiddling with dpkg-reconfigure stuff for a while, before deciding to downgrade...

[Mark Shuttleworth (sabdfl)]

Critical severity, many reports of failures in stable release. Fix is released but work continues to provide corrective instructions for affected users.

[Walter Tautz (wtautz)]

Thanks Mark, However the solution above works only once the
mirrors were synced up with the new package. Only an experienced
user would have know how to retrieve the older version and run
dpkg -i by hand to downgrade (I happen to be one of them).
 I find it a little hard to believe that
you folks couldn't have caught this prior to releasing. That being said my
card was an ATI PowerColour 9250. Note however that the
problem also occurred for a generic internal intel agp card that's
part of the motherboard.

walter, a mostly very pleased Ubuntu user.

[Fernando (fernando-medina)]

I can confirm 1.0.2-0ubuntu10.4 worked perfectly on my ThinkPad X32 with ATI Technologies Inc Radeon Mobility M6 LY. Only one suggestion for instruction page, show how to download file manually and then what to do. After my upgrade to 10.3 I shutdown and came to work, where I do not have the ability to apt-get, so I needed to download upgrade manually from a mirror and do a dpkg install... in any case, should be kept in mind that apt-get access is sometimes restricted behind corporate firewalls. thanks for fix...

[John Dong (jdong)]

Well, the xorg-server package is fixed, but that's not really the end to the problem at hand. What's being done / what can be done to prevent another mistake like this in the future?

[Matt Zimmerman (mdz)]

On Wed, Aug 23, 2006 at 07:48:01PM -0000, Walter Tautz wrote:
> Thanks Mark, However the solution above works only once the
> mirrors were synced up with the new package.

All mirrors are currently redirected to the master archive mirror, which
has the fix.

--
 - mdz

[Walter Tautz (wtautz)]

Matt Zimmerman wrote:
> On Wed, Aug 23, 2006 at 07:48:01PM -0000, Walter Tautz wrote:
>
>> Thanks Mark, However the solution above works only once the
>> mirrors were synced up with the new package.
>>
>
> All mirrors are currently redirected to the master archive mirror, which
> has the fix.
>
>
Ok. Nice trick with DNS presumably? Unfortunately we have
our own mirror....so I guess I should make a point of listing our
mirror first and then an official offsite mirror.

walter

[Jochen Becher (jochen-becher)]

Hi,

I am an experienced computer user / developer but never used atp-get,
dpkp or whatever before. Only update-manager and Synaptic. When I got
that problem (Dell Inspiron 8600 with ATI Mobility 9600 M10) I
downgraded X server manually using the console program "adaptive". It is
not as simple as Synaptic but at least it is menu driven and has online
help. That made things easier. The most serious problem was to find out
which package was "the bad one". I remembered it by heart because it was
the only package that was updated that day. Things might be much more
difficult if you can't remember updated packages.

Why not writing a program that "undo"s all package updates from a
history? That should be easily runnable (in worst case from an extra
entry in grub that boots into an minimal Ubuntu that just undo the
latest package update and reboots).

Regards, Jochen

[TuxFan (make)]

First of all, sorry for making one of the duplicate bug reports (bug 57227), I guess I didn't search with the correct keywords before posting it. See that bug report for more information about my GPU which was affected by this problem.

I didn't get the first warning message shown in the fix document about the X problem, but maybe that's because I'm actually using Kubuntu? In stead I got an empty Kubuntu boot/shutdown screen. (Empty meaning there was just the picture, no texts under it.)

But like I said in bug 57227, the version 10.4 fixed the problem for me.

[0mg (lsy123)]

I can confirm 1.0.2-0ubuntu10.4 worked perfectly on my PC - ATI RADEON 9550

[Gerard (gbendotti)]

It affected both of my machines here, one an intel 32bit with nvidia 64mb card, the other AMD64 with 256mb card GeForce 6200 TurboCache(TM). Both use the nvidia drivers, this one is NVIDIA Linux x86_64 Kernel Module 1.0-8762 Mon May 15 13:58:14.

I got things running again using the downgrade instructions. I have since updated to the 10.4 without problems.

[Sylvain Cherrier (sylvain-cherrier)]

Mark Shuttleworth a écrit :
> Thanks everyone for reporting and participating in the development of a
> fix for this very serious issue.
Well, at the beginning, when X crash at reboot, i have searched in
/var/cache/apt/archive to find what was new..

It was xserver-xorg-core, so i have downgrade to the old package version
(that was also in /apt/cache/archives/

As X was working now, i have report (bug 57207)...
And worked on my computer...

Then, i update with the latest version, and it worked...

Computer :
Kubuntu Dapper
AMD 64 2,2Ghz
MotherBoard Asus A8N-E
GPU : Nvidia GeForce 6200

[Peter Magnusson (kmpm)]

Just for reference.
This bug also affects
Compaq Evo N800c
It has ATI graphics.
ATI Technologies Inc Radeon Mobility M7 LW [Radeon Mobility 7500]

[Kim (kim-hawtin)]

I followed the steps from; https://wiki.ubuntu.com/ResolutionForBug57153

but as the machine was running in 32 bit colour mode there is the no screens foudn thing...
edit xorg.conf and set to 24bit and it works fine.

we are running again, but we have apps that only run in 32bit colour mode.

card is ATI9600

[Robert Penz (robert-penz-name)]

Dell inspiron 8600 with an nvidia card - 10.4 is working again.

ps: its not the first time a bugfix or upgrade breaks something major - same happend with the dapper kernel on one of my systems.

[sidney (sidneybrooks)]

The update procedure worked for me, but here are a couple of notes that may help others.
1. After starting the sudo apt-get update process, some things that I typed appeared on the screen, others did not. Even if nothing happened appeared when I typed, I found that it worked as long as I made no typing errors, the command was executed.

2. During the update process, the system seemed to freeze, e.g. it read 11% 1m53sec for a while with no advance. Hitting "enter" several times caused it to advance and complete.

[Gerhard Schneider (gs-ilsb)]

sidney wrote:
> The update procedure worked for me, but here are a couple of notes that may help others.
> 1. After starting the sudo apt-get update process, some things that I typed appeared on the screen, others did not. Even if nothing happened appeared when I typed, I found that it worked as long as I made no typing errors, the command was executed.
>

usplash is mangling your display.
Try removing the option splash from /boot/grub/menu.lst

                                               GS
--
Gerhard Schneider
Institute of Lightweight Design and e-Mail:<email address hidden>
Structural Biomechanics (E317) Tel.: [phone]
Vienna University of Technology / Austria Fax: [phone]
A-1040 Wien, Gusshausstrasse 27-29 http://www.ilsb.tuwien.ac.at/~gs/

[Tom Simonsen (toms-pinglebo)]

From Mark Shuttleworth:

"Please let us know as soon as possible if these address the issue for you. In this case, please DO report if it works, as well as if it does not work, by commenting on this bug."

This procedure works for me too on the hp nc8000 laptop.
Tom.

PS.I originally reported this bug as a duplicate (#57313).

[sidney (sidneybrooks)]

There is a Catch 22 quality to this suggestion. If you
get gnome working as I did, the presence of "splash"
seems to make no difference when booting (I have taken
splash out of menu.lst). If you want to make the
change before you get gnome back, you need a text
editor that works in the text environment. First, you
must know which one Ubuntu provides and then you must
know how to use it. I have always find things like vi,
vim, and emacs difficult.

--- Gerhard Schneider <email address hidden> wrote:

> sidney wrote:
> > The update procedure worked for me, but here are a
> couple of notes that may help others.
> > 1. After starting the sudo apt-get update process,
> some things that I typed appeared on the screen,
> others did not. Even if nothing happened appeared
> when I typed, I found that it worked as long as I
> made no typing errors, the command was executed.
> >
>
> usplash is mangling your display.
> Try removing the option splash from
> /boot/grub/menu.lst
>
> GS
> --
> Gerhard Schneider
> Institute of Lightweight Design and
> e-Mail:<email address hidden>
> Structural Biomechanics (E317) Tel.:
> [phone]
> Vienna University of Technology / Austria Fax:
> [phone]
> A-1040 Wien, Gusshausstrasse 27-29
> http://www.ilsb.tuwien.ac.at/~gs/
>
> --
> xorg-server 1:1.0.2-0ubuntu10.3 breaks X: "no
> screens found"
> https://launchpad.net/bugs/57153
>

__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com

[ppietryga (ppietryga)]

I'd like to confirm, that upgrade to version 1:1.0.2-0ubuntu10.4 fixed the problem.

[sidney (sidneybrooks)]

I followed the procedure at:
http://www.ubuntu.com/FixForUpgradeIssue.

Except for the two indicated problems which I got
around as described, it fixed the problem. You do not
actually specify Oubuntu10.4 in this procedure. Good
luck.

--- ppietryga <email address hidden> wrote:

> I'd like to confirm, that upgrade to version
> 1:1.0.2-0ubuntu10.4 fixed
> the problem.
>
> --
> xorg-server 1:1.0.2-0ubuntu10.3 breaks X: "no
> screens found"
> https://launchpad.net/bugs/57153
>

__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com

[Jan Stedehouder (j-stedehouder)]

Well, I suffered from the same problem earlier this week ( I run an AMD XP 2400+ box with 512 Mb RAM and an Asus n6200 256 Mb RAM card). Unfortunately I did not have the time to search for a solution. This is my production box and I needed it up and running that same moment. For me this called for a backup of the /home folder and reinstalling Ubuntu from scratch (which was simple and fast).

Anyway, for me it proves that Linux has improved greatly as far as ease of installation and ease of use are concerned, but when something goes wrong there is a serious lack of easy and accessible diagnostic and repair tools that don't require you to go over esoteric error logs with tons of information that are useless for the non-geek user. And we have to be honest, something always can and will go wrong.

http://opensourcelearning.info/blog/?p=46
http://opensourcelearning.info/blog/?p=49

[Nicola Larosa (teknico)]

Confirmed: 10.4 works on a HP DV5008EA laptop. Here's the ouput of lspci.

0000:00:00.0 Host bridge: ATI Technologies Inc RS480 Host Bridge (rev 01)
0000:00:01.0 PCI bridge: ATI Technologies Inc: Unknown device 5a3f
0000:00:05.0 PCI bridge: ATI Technologies Inc: Unknown device 5a37
0000:00:13.0 USB Controller: ATI Technologies Inc IXP SB400 USB Host Controller
0000:00:13.1 USB Controller: ATI Technologies Inc IXP SB400 USB Host Controller
0000:00:13.2 USB Controller: ATI Technologies Inc IXP SB400 USB2 Host Controller
0000:00:14.0 SMBus: ATI Technologies Inc IXP SB400 SMBus Controller (rev 11)
0000:00:14.1 IDE interface: ATI Technologies Inc Standard Dual Channel PCI IDE Controller ATI
0000:00:14.3 ISA bridge: ATI Technologies Inc IXP SB400 PCI-ISA Bridge
0000:00:14.4 PCI bridge: ATI Technologies Inc IXP SB400 PCI-PCI Bridge
0000:00:14.5 Multimedia audio controller: ATI Technologies Inc IXP SB400 AC'97 Audio Controller (rev 02)
0000:00:14.6 Modem: ATI Technologies Inc ATI SB400 - AC'97 Modem Controller (rev 02)
0000:00:18.0 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] HyperTransport Technology Configuration
0000:00:18.1 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Address Map
0000:00:18.2 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] DRAM Controller
0000:00:18.3 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Miscellaneous Control
0000:01:05.0 VGA compatible controller: ATI Technologies Inc ATI Radeon XPRESS 200M 5955 (PCIE)
0000:06:02.0 Network controller: Broadcom Corporation BCM4318 [AirForce One 54g] 802.11g Wireless LAN Controller (rev 02)
0000:06:04.0 CardBus bridge: Texas Instruments PCIxx21/x515 Cardbus Controller
0000:06:04.2 FireWire (IEEE 1394): Texas Instruments OHCI Compliant IEEE 1394 Host Controller
0000:06:04.3 Mass storage controller: Texas Instruments PCIxx21 Integrated FlashMedia Controller
0000:06:04.4 0805: Texas Instruments PCI6411, PCI6421, PCI6611, PCI6621, PCI7411, PCI7421, PCI7611, PCI7621 Secure Digital (SD) Controller
0000:06:06.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ (rev 10)

[sidney (sidneybrooks)]

This event probably has done very serious harm to the migration to linux from Windows. All of us using this forum are using another operating system as well as Ubuntu or are knowledgeable enough about linux to operate in the text mode. My guess is that most people who choose Ubuntu have no idea of how to use linux in the text mode. Ubuntu's simple graphical installation is why people pick it over Debian; you get Debian quality with ease of installation. Therefore, it is my further guess that many people who made Ubuntu their only operating system had no access to information on how to fix the bug, leaving them to reinstall while losing all files and bookmarks. Since Ubuntu is the number one system in Distro Watch, this failure discourages the use of linux. If ever there was a critical bug, it was this one.

[Sylvain Cherrier (sylvain-cherrier)]

sidney a écrit :
> This event probably has done very serious harm to the migration to linux
> from Windows.
[...]
Well, a Windows user often reinstall his OS... :-(
because of virus, malware, etc.. etc.. Even with good protections...

So, one day broken in Dapper's life is really small in front of what
happen in Windows's life !!

But, maybe it could be a good idea to think about a way of restarting
from a previous configuration...
Maybe booting from Installation CD, and downgrading ? Or something like
that ?

[Jan Stedehouder (j-stedehouder)]

Sylvain Cherrier schreef:
> sidney a écrit :
>
>> This event probably has done very serious harm to the migration to linux
>> from Windows.
>>
> [...]
> Well, a Windows user often reinstall his OS... :-(
> because of virus, malware, etc.. etc.. Even with good protections...
>
I agree. I had to do that once every 6 to 9 months. Reinstalling Ubuntu
with all the applications took only a fraction of the time that I had to
spend on getting a fully functional Windows desktop again.

> So, one day broken in Dapper's life is really small in front of what
> happen in Windows's life !!
>
> But, maybe it could be a good idea to think about a way of restarting
> from a previous configuration...
> Maybe booting from Installation CD, and downgrading ? Or something like
> that ?
>
>
That would definitely be an asset. I tried to use the Ubuntu DVD to
backup my /home folder, but I couldn't access it that way. Okay, I did
not really look into it, but the fact is that Knoppix recognized and
mounted all my partitions (ext3, NTFS and FAT32) making it easy to use
it in salvage.

Better and easier problem solving tools that won't require extensive CLI
knowledge would be an improvement.

[Robert Penz (robert-penz-name)]

I propose following solution:

1. add a menu point to grub name "Rescue Mode"
2. boot into an low Runlevel
3. start a dialog-based console program which has following features

- look for and install updates
- look at the installation history and remove possible updates (sorted by install time)
- show last boot log (parses the syslog for the new syslog start and shows the last lines before it.)
- start networking
  + Show Emergency Information from Ubuntu (lynx without navigation or something like this)
  + Rescue Support Channel (Text based minimal IRC which just joins just the #ubuntu-rescue channel on freenode)

With this even a user which doesn't know anything about the user can get help/information.

ps: you can also start that menu if the xserver start fails during booting

[Jan Stedehouder (j-stedehouder)]

Robert Penz schreef:
> I propose following solution:
>
> 1. add a menu point to grub name "Rescue Mode"
> 2. boot into an low Runlevel
> 3. start a dialog-based console program which has following features
>
> - look for and install updates
> - look at the installation history and remove possible updates (sorted by install time)
> - show last boot log (parses the syslog for the new syslog start and shows the last lines before it.)
> - start networking
> + Show Emergency Information from Ubuntu (lynx without navigation or something like this)
> + Rescue Support Channel (Text based minimal IRC which just joins just the #ubuntu-rescue channel on freenode)
>
> With this even a user which doesn't know anything about the user can get
> help/information.
>
> ps: you can also start that menu if the xserver start fails during
> booting
>
>
This suggestion has some valid points, but I wouldn't mind taking this a
bit further. Why not integrate system restore into Linux and into the
menu? I mean, that is one of the things that I have found very useful in
Windows XP and I know that many XP users have used that feature on more
than one occasion. Mind you, I don't know enough of what this will take,
or if there are any security issues associated with it.

The networking feature looks okay, but might be a bit daunting for
people with only GUI experience. Joining IRC seems nice, but who is
going to answer the repetitive questions from the users that experience
problems. One of the big problems I have noticed over the years is how
difficult it is for end-users to describe and define the problem.
Without that it is difficult to solve it. For the newbie user having an
option to restore everything back to a previous restore point is simple
and straight forward. Beyond that restore point there should be a fast
and easy access to what caused the problem in the first place, otherwise
the end-user will just stop updating his sytem in order to prevent a
similar thing from happening. This requires a set of analyses tools that
could take the information in the various logs, compare it to the same
logs at a previous restore point (the one that was reverted to) and
present a list of things that could be wrong with links to a website for
common and specific solutions. That's the kind of process I can
visualize, but whether it can be implemented.... I don't know.

[najvecamoc (najvecamoc)]

Hi
It seems that the solution that I read here doesnt work for me, I down graded the xorg version to the version that is supposed to work, now gdm wont start, and I am completely lost as what am I suposed to do from here.
here is a part of the log file that is outputed after the x restart:

        ATI Radeon X850 XT PE (R480) (PCIE),
        ATI Radeon X850 PRO (R480) (AGP), ATI Radeon X850 SE (R480) (AGP),
        ATI Radeon X850 XT (R480) (AGP), ATI Radeon X850 XT PE (R480) (AGP)
(II) Primary Device is: PCI 00:02:0
(II) ATI: Candidate "Device" section "ATI Technologies, Inc. Radeon RV100 QY [Radeon 7000/VE]".
(II) ATI: Shared non-ATI VGA in PCI/AGP slot 0:2:0 detected.
(EE) No devices detected.

Fatal server error:
no screens found

The machine is a new Toshiba Tecra A8, which was running ubuntu for a couple of days without any problems, till i did the upgrade and no more GUI
Anything else any one can tell me, or should I re-install the whole thing, or maybe move to another distro?

[flexy (gwrauh1)]

Public bug reported:

Binary package hint: ubuntu-desktop

[A64 3500+, 1gb Ram, X850XT pci-e, Audigy2]

excuse my limited unix knowledge.

I got me the ubuntu 6.06.1 64bit and burnt it on CD.

Upon booting off CD it aborts because it fails to start the X server.
I get thrown right into a shell, no login.

I was looking thru the xorg0.log

I see my radeon x850xt listed with the right busID as primary device.

But at the end of the logfile it says

"PCI Radeon Mach64 on bus 5.0.0 not found !"
"PCI Radeon Mach64 on bus 5.0.1 not found !"

(EE) no device found !!

Needless to say i dont own (never had) a Radeon Mach64.

This is trying to boot off the live-CD "as burnt" from the *.iso

** Affects: ubuntu-meta (Ubuntu)
     Importance: Undecided
         Status: Unconfirmed

** Bug 64462 has been marked a duplicate of this bug

--
does NOT start X with pci-e Radeon X850XT

https://launchpad.net/bugs/64463

this happened to me with the latest 6.06.1 64bit

- and BTW

the hints for fixes/updates are all nice and good - too bad the system is not even installed yet, it's running off the CD. So...how can i update something and replace files when it didnt even get that far off the CD to give me the option to install the distribution on an HD ?

This is some SERIOUS bug.

[Lirelent (smarts40)]

I followed
https://help.ubuntu.com/community/BinaryDriverHowto/Nvidia

I just installed edgy on my new D620 with the quadro nvs 110m video card and I'm seeing this exact behavior and obviously edgy ships with a much newer version of xorg so this solution won't work. lspci says the video card is

01:00.0 VGA compatible controller: nVidia Corporation Unknown device 01d7 (rev a1)

PLEASE HELP

[mommedia.com (dcodex2013-deactivatedaccount)]

I do not think it's the video card as stipulated, I have strong feeling that there bugs in the system and that some on line site write malicious codes. Many times the system is constantly freezing up during the process of using some on line platforms. Question; when that happens, how I do i regain control of the system without improperly shutting it down?

:-(
MoMmedia

=====================================================================================

mommI followed
mommhttps://help.ubuntu.com/community/BinaryDriverHowto/Nvidia
momm
mommI just installed edgy on my new D620 with the quadro nvs 110m video card
mommand I'm seeing this exact behavior and obviously edgy ships with a much
mommnewer version of xorg so this solution won't work. lspci says the video
mommcard is
momm
momm01:00.0 VGA compatible controller: nVidia Corporation Unknown device
momm01d7 (rev a1)
momm
mommPLEASE HELP
momm
momm--
mommxorg-server 1:1.0.2-0ubuntu10.3 breaks X: "no screens found"
mommhttps://launchpad.net/bugs/57153

[der74hva3 (der74hva3)]

wou

[Martina Neumayer (martina.neumayer)]

Confirmed
Bug "10.3" affect my system too.
After downgrade is ok, however..

This fixed xorg-server 1:1.0.2-0ubuntu10.4 can slow down system installed on VMware.
Someone has this issue too, or just I?

[Martina Neumayer (martina.neumayer)]

Update:
After system update to RC release Im again affected by this issue.
Ignoring "ABI incompatibilities" in xorg.conf - as described here:
http://azitech.wordpress.com/2010/08/23/maverick-nvidia-compiz/
don't work for me.

My system:
Ubuntu 10.10 RC
Gfx card: Nvidia GF 5200
Driver: 173 series.

[Martina Neumayer (martina.neumayer)]

Ps. After a clean install of Ubu 10.10 RC, this error also occurs.