desktop cd fails to start gdm with hp nc6400 (widescreen, ati-based laptop)

[Michael Blakeley]

Binary package hint: xorg

The feisty beta desktop cd for amd64 boots ok on my nc6400, but gdm fails to start. The error log suggests that xorg found the ati video card, but couldn't find a valid mode. If I remove /etc/X11/xorg.conf entirely, xorg still can't find a usable mode. If I hand-edit the xorg.conf to add some modelines, I can get 1024x768 to work.

Here are some details that may help:

$ lspci | grep ATI
01:00.0 VGA compatible controller: ATI Technologies Inc M52 [ATI Mobility Radeon X1300]
$ sudo ddcprobe
vbe: VESA 3.0 detected.
oem: ATI ATOMBIOS
vendor: (C) 1988-2005, ATI Technologies Inc.
product: M52T 01.00
memory: 16384kb
mode: 640x400x256
mode: 640x480x256
mode: 800x600x256
mode: 1024x768x256
mode: 1280x1024x256
mode: 640x480x32k
mode: 640x480x64k
mode: 640x480x16m
mode: 800x600x32k
mode: 800x600x64k
mode: 800x600x16m
mode: 1024x768x32k
mode: 1024x768x64k
mode: 1024x768x16m
mode: 1280x1024x32k
mode: 1280x1024x64k
mode: 1280x1024x16m
mode: 320x200x32k
mode: 320x200x64k
mode: 320x200x16m
mode: 1600x1200x256
mode: 1600x1200x32k
mode: 1600x1200x64k
edid:
edid: 1 3
id: 8d00
eisa: LPL8d00
serial: 00000000
manufacture: 0 2005
input: analog signal.
screensize: 30 19
gamma: 2.200000
dpms: RGB, no active off, no suspend, no standby
dtiming: 1280x800@59
monitorid: LGPhilipsLCD
monitorid: LP141WX1-TLA
$ sudo /usr/share/xresprobe/ddcprobe.sh
res: 1280x800
disptype: crt
name:
freq:

The ddcinfo seems off: this is definitely an lcd, not a crt. The input is digital, I'd think, and the dpms is probably wrong too. The native lcd resolution, 1280x800, isn't listed in the modes.

If I can provide any other info, please let me know.

[S.Rey (s.rey)]

I can reproduce this bug.
My laptop is a Fujitsu Amilo Pi1536, Core Duo T2300, ATI x1400
The X server crashes on starting gdm (signal 11 error).
I have edited the xorg.conf file and the vesa driver was being used. (This should be OK, since ATI x1000 series are not supported by the open source ati driver).
I suppose this is a xorg or vesa driver related bug.
I consider that it should be classified as critical, as it blocks the average user (the target audience of the desktop install cd).

I have found the following workaround (I have been able to successfully start the livecd in 640x480, and complete the installation). See if this works for you.

$ sudo dpkg-reconfigure -phigh xserver-xorg

Choose the default options, except when you are asked for the resolutions. Then choose only 640x480. (I have found this is the only one that works).
(you can instead edit manually /etc/X11/xorg.conf with nano and delete all the other resolutions)
$ sudo killall gdm
$ sudo gdm

After the installation has finished you can install the fglrx through "Restricted Drivers Manager". (I think you need to have the internet connection active).
Then in a console
$ sudo dpkg-reconfigure xserver-xorg
Make sure you choose the 1280x800 resolution.
CTRL+ALT+BackSpace

And that's all, you should now have your ubuntu feisty working at native resolution.

[Michael Blakeley (mike+ubuntu)]

I just took a few minutes to try that workaround with the 7.04 final ubuntu amd64 desktop cd. The reconfigure seemed to work, and I disabled all resolutions except for 640x480. However, I still can't start X (no screens found). The log messages look similar to my original report.

[Michael Blakeley (mike+ubuntu)]

Per https://help.ubuntu.com/community/DebuggingXAutoconfiguration the following workaround did work for me:

$ sudo dpkg-reconfigure -phigh xserver-xorg
...choose defaults for everything

$ sudo vi /etc/X11/xorg.conf
...in the section "Monitor" (around line 100 in my file), insert these lines before EndSection
  HorizSync 36-52
  VertRefresh 36-60

$ sudo /etc/init.d/gdm restart
...may need to do that twice - the first restart failed for me, probably due to a stray pid file or something like that.

[Timo Aaltonen (tjaalton)]

Could you attach the Xorg.0.log when it fails? This seems like bug 89853 but you can work around it..

[S.Rey (s.rey)]

There seems to be 2 similar bugs here. (Not sure which one is #89853)

One of them manifest itself like this:
"Screen(s) found, but none have a usable configuration.
Fatal server error:
no screens found"

The other (mine) is this one:
"No valid modes left. Trying less strict filter...
Fatal server error:
Caught signal 11. Server aborting"

In my case I can start X by choosing only the 640x480 mode in xorg.conf

[brokencrystal.com (admin-brokencrystal)]

https://bugs.launchpad.net/ubuntu/+bug/131799

[brokencrystal.com (admin-brokencrystal)]

Will this be assigned to someone and fixed before Gutsy is released?

[Bryce Harrington (bryce)]

This bug is also reported in Ubuntu here: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/103945

On 64-bit systems with ATI cards, Xorg recognizes the ati card but fails to find a suitable mode. This occurs whether the xorg.conf is present or not. The original reporter says he got it working by hand-editing modelines into xorg.conf.

In speaking with Alex Deucher, he adds:
<agd5f> vesa fails on my radeon on 64 bit
<agd5f> don't know why. even kernel vesafb fails

Original report:

"The feisty beta desktop cd for amd64 boots ok on my nc6400, but gdm fails to start. The error log suggests that xorg found the ati video card, but couldn't find a valid mode. If I remove /etc/X11/xorg.conf entirely, xorg still can't find a usable mode. If I hand-edit the xorg.conf to add some modelines, I can get 1024x768 to work.

Here are some details that may help:

$ lspci | grep ATI
01:00.0 VGA compatible controller: ATI Technologies Inc M52 [ATI Mobility Radeon X1300]
$ sudo ddcprobe
vbe: VESA 3.0 detected.
oem: ATI ATOMBIOS
vendor: (C) 1988-2005, ATI Technologies Inc.
product: M52T 01.00
memory: 16384kb
mode: 640x400x256
mode: 640x480x256
mode: 800x600x256
mode: 1024x768x256
mode: 1280x1024x256
mode: 640x480x32k
mode: 640x480x64k
mode: 640x480x16m
mode: 800x600x32k
mode: 800x600x64k
mode: 800x600x16m
mode: 1024x768x32k
mode: 1024x768x64k
mode: 1024x768x16m
mode: 1280x1024x32k
mode: 1280x1024x64k
mode: 1280x1024x16m
mode: 320x200x32k
mode: 320x200x64k
mode: 320x200x16m
mode: 1600x1200x256
mode: 1600x1200x32k
mode: 1600x1200x64k
edid:
edid: 1 3
id: 8d00
eisa: LPL8d00
serial: 00000000
manufacture: 0 2005
input: analog signal.
screensize: 30 19
gamma: 2.200000
dpms: RGB, no active off, no suspend, no standby
dtiming: 1280x800@59
monitorid: LGPhilipsLCD
monitorid: LP141WX1-TLA
$ sudo /usr/share/xresprobe/ddcprobe.sh
res: 1280x800
disptype: crt
name:
freq:

The ddcinfo seems off: this is definitely an lcd, not a crt. The input is digital, I'd think, and the dpms is probably wrong too. The native lcd resolution, 1280x800, isn't listed in the modes.

If I can provide any other info, please let me know."

[Bryce Harrington (bryce)]

Created an attachment (id=11218)
Disables mode checking so xorg doesn't drop modes before they've had a chance to be validated

I've not tested to see if this fixes the issue, but Debian has the following patch, which I've been told addresses a "vesa-crashes on r5xx hardware" issue that might be relevant here.

[Bryce Harrington (bryce)]

In speaking with the Xorg -ati maintainer, this is a known issue that he's able to reproduce, and confirmed that it even fails for kernel vesafb. I'm forwarding it upstream.

[Bryce Harrington (bryce)]

Btw - the known issue is specific to 64-bit systems. I've marked several bugs as dupes of this one. If anyone subscribed to this bug is *not* on 64-bit, let me know - in those cases it's probably a different issue and we should de-dupe it.

[Bryce Harrington (bryce)]

There is also a vesa fix coming up in our next xorg-server upload (probably tomorrow), which includes a patch from debian, 41_vbe_filter_less.diff, which makes Xorg not drop modes too early, before they've had a chance to be validated. I'll post here when that is uploaded, so the issue can be re-tested.

[Bojan Rajkovic (bojanr)]

I'm not on 64 bit and I have the X1400 issue--I'm using a 32-bit Intel Core Duo (Yonah core). If you need more information from me, I can pass it up to you, though it should already be posted in some duplicated bug.

[Leif Walsh (leif.walsh)]

My bug (122663) was on 32-bit as well.

On 8/22/07, Bojan Rajkovic <email address hidden> wrote:
> I'm not on 64 bit and I have the X1400 issue--I'm using a 32-bit Intel
> Core Duo (Yonah core). If you need more information from me, I can pass
> it up to you, though it should already be posted in some duplicated bug.
>
> --
> desktop cd fails to start gdm with hp nc6400 (widescreen, ati-based laptop)
> https://bugs.launchpad.net/bugs/103945
> You received this bug notification because you are a direct subscriber
> of a duplicate bug.
>

[Timo Aaltonen (tjaalton)]

If anyone of you is using gutsy at the moment, please test a new xserver version available here:

http://users.tkk.fi/~tjaalton/dpkg/xserver

It has a patch which should fix this for good.

[Michael Blakeley (mike+ubuntu)]

Note that Timo's debs are i386, not amd64 (aka x86-64).

[Thomas Novin (thomasn80)]

Timo,

I've just tried with todays (070824) iso of gutsy. I got the usual error and I was told X was disabled.

I downloaded xserver-xorg-core_1.3.0.0.dfsg-12ubuntu1_i386.deb and upgraded with dpkg -Gi. Restarted gdm and waited but X didn't start this time either, same error as before.

I'm attaching my Xorg.0.log.

[Leif Walsh (leif.walsh)]

I uninstalled xorg-driver-fglrx, installed Timo's xserver-xorg-core, and modified my xorg.conf to use Driver "vesa". I restarted X and got the same problem as before. Attaching xorg.conf and Xorg.0.log from that run.

[Joe Smith (yasumoto7)]

I've got a similar issue with my Dell E1505 running an ATI x1400. I managed to get it running in a weird resolution with the vesa driver, but it still isn't operating as it should be.

[Wenzhuo Zhang (wenzhuo)]

I am experiencing a similar problem with my HP Compaq 6515b. The graphics card is an ATI x1270. I cannot get X running. Attaching Xorg.0.log...

[Wenzhuo Zhang (wenzhuo)]

using gutsy tribe-5 desktop CD.

[Bugzi09-fdo-tormod (bugzi09-fdo-tormod)]

Created an attachment (id=11339)
Xorg.0.log with vesa driver on X700

I have similar problems on i386 with a laptop with an ATI Mobility X700, when I force it to use the vesa driver. The native mode 1680x1050 is not in the list of modes returned by ddcprobe. ddcprobe.sh returns the right resolution, but "crt".
X starts up in 1280x1024. If I use an xorg.conf and specifies 1680x1050, X doesn't start at all.

I use xserver-xorg-core 1.3.0.0.dfsg-12ubuntu3feisty1 which has the above patch, and xserver-xorg-video-vesa 1.3.0-1ubuntu5feisty1. (The ati driver works perfectly.)

[Joe Smith (yasumoto7)]

I've managed to get everything working with fglrx, it's just that people shouldn't have to mess around with xorg.conf

[Leif Walsh (leif.walsh)]

On 8/31/07, Joe Smith <email address hidden> wrote:
> I've managed to get everything working with fglrx, it's just that people
> shouldn't have to mess around with xorg.conf

If I'm not mistaken, the preferred way to change xorg.conf is through
dpkg-reconfigure. Of course, this doesn't invalidate your point, that
it should Just Work, even with ATI cards.

[Timo Aaltonen (tjaalton)]

Please try with the latest gutsy daily live-cd, it has a newer package for vesa-driver, and that should fix this.

http://cdimages.ubuntu.com/daily-live/

[Thomas Novin (thomasn80)]

Timo, now it actually works! Ok, I don't get the optimal resolution but enough to do the install.

ubuntu@ubuntu:~$ xrandr
Screen 0: minimum 1400 x 1050, current 1400 x 1050, maximum 1400 x 1050
default connected 1400x1050+0+0 0mm x 0mm
   1400x1050 60.0*

Usually I have 1680x1050.

[Bugzi09-fdo-tormod (bugzi09-fdo-tormod)]

Created an attachment (id=11365)
Xorg.0.log (failing) with sync/refresh set

I tried again with the Gutsy Tribe 5 live cd, updated with xserver-xorg-video-ati 1:6.7.192-1ubuntu1 and xserver-xorg-core 2:1.3.0.0.dfsg-12ubuntu3. With
        HorizSync 30-70
        VertRefresh 50-160
in xorg.conf it fails with
 (II) VESA(0): VBESetVBEMode failed
 (EE) VESA(0): Set VBE Mode failed!

 Fatal server error:
 AddScreen/ScreenInit failed for driver 0
and if I remove these two lines it starts up in 1280x1024.

[Michael Blakeley (mike+ubuntu)]

Yes, gdm now starts up with my hp nc6400, ati graphics. The resolution is 1024x768, rather than 1280x800, but that's another issue.

[Wenzhuo Zhang (wenzhuo)]

Tried 20070831 gutsy desktop CD on my HP Compaq 6515b. X still fails to start.

[Paul Douglas (stonecarver)]

Tried 20070381 on my Acer 8204WLMi ATI x1600. Live CD loads but the resolution is 1024/768 with a refresh rate of 61! Expected resolution of 1680x1050 refresh 60, but at least it loaded.

[Leif Walsh (leif.walsh)]

Similar. Not optimal, but usable.

On 9/1/07, Paul Douglas <email address hidden> wrote:
> Tried 20070381 on my Acer 8204WLMi ATI x1600. Live CD loads but the
> resolution is 1024/768 with a refresh rate of 61! Expected resolution of
> 1680x1050 refresh 60, but at least it loaded.
>
> --
> desktop cd fails to start gdm with hp nc6400 (widescreen, ati-based laptop)
> https://bugs.launchpad.net/bugs/103945
> You received this bug notification because you are a direct subscriber
> of a duplicate bug.
>

[Bojan Rajkovic (bojanr)]

This is fixed in the latest round of updates--starting up Xorg.conf with VESA actually gets me a working X on my Mobility Radeon X1400.
(I tested it because I severely borked my fglrx setup and had to wipe the whole lot of it out)

[Emerson Ribeiro de Mello (emerson-ml)]

I'm trying with Gutsy Tribe 5 + Dell Ispiron 6400 (ATI Mobility Radeon x1300) and I got the same result, that is, X fails to start.

Well, I saw this bug in Feisty (7.04) and I had to download/install xorg-driver-fglrx (in live CD mode) to install Feisty in my Laptop.

Hey Ubuntu Team!! Please, could you return to Dapper's X conf files? In Dapper this graphic card works perfect. :-D

[Bryce Harrington (bryce)]

With the fix I did Friday to bug 27667 I believe this is fixed as well. At least, the issue of the max resolution not getting detected should be resolved. I think we got the gdm/vesa issue fixed as well, but if anyone can test today's daily ISO to check, that would help verify. If the issue still exists, please re-open.

[Michael Blakeley (mike+ubuntu)]

No change with the 10-01 nightly: the gnome session still starts in 1024x768, and the screen-resolution applet lists only 1024x768, 800x600, and 640x480 (1280x800 is missing).

$ apt-show-versions xresprobe
xresprobe/gutsy uptodate 0.4.24ubuntu5
$ sudo ddcprobe
vbe: VESA 3.0 detected.
oem: ATI ATOMBIOS
vendor: (C) 1988-2005, ATI Technologies Inc.
product: M52T 01.00
memory: 16384kb
mode: 640x400x256
mode: 640x480x256
mode: 800x600x256
mode: 1024x768x256
mode: 1280x1024x256
mode: 640x480x32k
mode: 640x480x64k
mode: 640x480x16m
mode: 800x600x32k
mode: 800x600x64k
mode: 800x600x16m
mode: 1024x768x32k
mode: 1024x768x64k
mode: 1024x768x16m
mode: 1280x1024x32k
mode: 1280x1024x64k
mode: 1280x1024x16m
mode: 320x200x32k
mode: 320x200x64k
mode: 320x200x16m
mode: 1600x1200x256
mode: 1600x1200x32k
mode: 1600x1200x64k
edid:
edid: 1 3
id: 8d00
eisa: LPL8d00
serial: 00000000
manufacture: 0 2005
input: analog signal.
screensize: 30 19
gamma: 2.200000
dpms: RGB, no active off, no suspend, no standby
dtiming: 1280x800@59
monitorid: LGPhilipsLCD
monitorid: LP141WX1-TLA
$ sudo xresprobe fglrx
id:
res:
freq:
disptype: lcd/lvds

[Nabeelfa (nabeelfa-deactivatedaccount-deactivatedaccount-deactivatedaccount)]

I'm trying with Gutsy Tribe 5 + Toshiba Satellite M100 (ATI Mobility Radeon x1400) and I got the same result, that is, X fails to start.

Well, I saw this bug in Feisty (7.04) and I had to download/install xorg-driver-fglrx (in live CD mode) to install Feisty in my Laptop.

Hey Ubuntu Team!! Please, could you return to Dapper's X conf files? In Dapper this graphic card works perfect. :-D

As mentioned in Bug #103945

[Tal Shachar (shachtal)]

hi nabeel
i know about this but

as wel as i know that it was already fixed

try downloading the beta verssion instead of the tribe 5 (it is the one that was released after tribe 5)

and enjoy

[jeff (j-perry)]

Another data point:

Vesa mode does not work on Averatec 3200 series laptop - even when booting in safe graphics mode
Gutsy 7.10 beta release live cd
This did work fine on the 7.04 livecd.

Symptoms: When booting in safe graphics mode, X seems to start fine, cursor becomes X then an arrow, background changes to blue, mouse can move arrow around but nothing else ever happens :-(

[Nabeelfa (nabeelfa-deactivatedaccount-deactivatedaccount-deactivatedaccount)]

Hi Tal Shachar,
I tried the Beta version, its showing the same issue.....

[Nabeelfa (nabeelfa-deactivatedaccount-deactivatedaccount-deactivatedaccount)]

by the way my notebook is Toshiba Satellite M100-180
ATI Mobility Radeon X1400

[Paul Douglas (stonecarver)]

Tried with the Oct 04 daily build on my Acer 8204 (x1600). Live CD loads but the
resolution is 1280x1024 with a refresh rate of 61!

Expected resolution of 1680x1050 refresh 60.
There are no 1680 or 1050 options available in the "Screen Resolution Preferences" and the only refresh rate is 61!

[jeff (j-perry)]

Just tried the latest release of Gutsy: 7.10 Release Candidate.
New behaviour, instead of the behaviour I reported earlier I'm seeing the following on my Averatec 3200

Since the safe boot option no longer is a choice, I selected Start or Install....
After booting for a bit I think X attempts to start and the screen is blank but back-lit.
I waited a bit for this and finally gave up.

I rebooted and edited the boot line to add vga=771
Eventually (after 5 or more mins) the system X started and produced a warning error box
indicating it was in low-res mode because it could not detect my hardware and asking whether I would like to configure things manually.

I tried various of the options offered (rebooting between each and painstakingly waiting to get to the warning box). None of the following attempts succeeded

1) simply press continue at the warning box
2) Configure as 800x600 generic lcd at 60hz device driver vga
3) Configure as 1024x768 generic lcd at 60hz device driver vesa

All of these result in a blank backlit screen but no X windows or cursor displayed.

[Nabeelfa (nabeelfa-deactivatedaccount-deactivatedaccount-deactivatedaccount)]

Well, I am not accepting the fact of placing all these orders specially for newbies.....
they need to install the Ubuntu Gutsy as simple as the Dapper!!!! Thats it!!

[Alex Tanner (alex-slightlyunstable)]

I think I understand what your saying. If you are saying that the
install must be simple than I agree. I am not a complete newbie but I
don't like to deal with this crap.

[Chris Rowson (christopherrowson)]

I also agree that if the new method of installing doesn't work, we
should default back to the old method.

Chris

[Alex Tanner (alex-slightlyunstable)]

Here's how I see it,

For Ubuntu to be an effective distro to convert people to linux, it has
to be very simple to install and use.

Alex

[Emerson Ribeiro de Mello (emerson-ml)]

Great news!

I'm using rigth now the new Ubuntu 7.10 (in liveCD mode).

Now, Xorg is ok in liveCD. I got a 1400x1050 resolution (my LCD default resolution is 1680x1050) that is enough for me to install Ubuntu in my HD.

Congratulations Ubuntu Team!!

My system:

Dell Inspiron 6400
LCD 1680x1050
ATI Radeon Mobility x1300

[Bojan Rajkovic (bojanr)]

Fixed! Xorg starts with 1152x864 resolution without any problems. Not my native resolution (1440x900) but good enough to run the installer (and Restricted Manager is very prompt about asking me to install the ATI driver after I log in.)

Great job!

[Orin77 (eppie)]

Ok, tried to install Gutsy from the "official" Canonical CD and it fails during install, as above. Even in safe graphics mode.

This on a Toshiba Satellite Pro 4600, with Trident Cyberblade graphics card. A card, if I may say so, that worked out-of-the-box since the 2006 LTS version.

My only hope is to upgrade from the LTS version as later versions leave me without wireless (another regression).

Great quality assurance guys! :-(

[penalvch (penalvch)]

Fix released downstream.