ATI prop.driver on Hardy 64bit result in no screen output

Bug #195918 reported by Sander Jonkers
4
Affects Status Importance Assigned to Milestone
linux-restricted-modules-2.6.24 (Ubuntu)
New
Undecided
Unassigned

Bug Description

Hardware: Asus M2A-VM HDMI, with onboard ATI GPU: "Integrated ATI Radeon X1250-based graphics"

The installation of Ubuntu 8.04 Hardy Heron Alpha 5 64-bit goes perfect. After reboot + first login, the proprietary driver is offered. After installation of that prop.driver (15MB) and reboot, the GUI screen does not appear and my monitor turns off (no signal).

I had to reboot into recovery mode to get a safe X config.

This might me related to Bug #177658, but I have too little knowledge to tell.

Possibly relevant stuff:

sander@ubuntu-amd64:~$ xrandr -q -d :0
Screen 0: minimum 640 x 400, current 1280 x 1024, maximum 1280 x 1024
default connected 1280x1024+0+0 0mm x 0mm
   1280x1024 60.0*
   1024x768 85.0
   800x600 86.0
   640x480 86.0
   720x400 86.0
sander@ubuntu-amd64:~$

sander@ubuntu-amd64:~$ cat /etc/*rel*
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=8.04
DISTRIB_CODENAME=hardy
DISTRIB_DESCRIPTION="Ubuntu hardy (development branch)"
sander@ubuntu-amd64:~$

Revision history for this message
Sander Jonkers (jonkers) wrote :
Revision history for this message
Olexandr Zanichkovsky (ozanichkovsky) wrote :

I confirm this bug with ATI X1300.

Revision history for this message
Sander Jonkers (jonkers) wrote :

To check it's not 64-bit related, I installed 8.04 hardy alpha 5 i386, with the same results: activating the ATI prop.driver ("fglrx") followed by a reboot, results in no screen output at all; the monitor on/off light goes into orange blinking mode instead of steady green light.

So: it's not 64-bit related.

Pressing CTRL-ALT-F1 results in a blinkinh, grey screen with some lines spaced by about 1 cm.

Pressing (CTRL) ALT-F7 after that, results in a low res GUI saying "Ubuntu is running in low-graphics mode". I can then select VESA at 800x600.

While typing this, I realize I should have saved /var/log/Xorg.0.log, which I didn't. But see below.

To repair this, on reboot I selected the second boot option ("safe graphics"?) and selected 'xfix' which brought back my 1280 x 1024. In System -> Administration -> Screen and Graphics, I *can not* see which driver is now used; all parameter boxes are empty.

After this boot, /var/log showed this:

sander@ubuntu-i386:/var/log$ ls -al Xorg.0.log*
-rw-r--r-- 1 root root 75888 2008-02-27 06:54 Xorg.0.log
-rw-r--r-- 1 root root 72225 2008-02-27 06:41 Xorg.0.log.old
sander@ubuntu-i386:/var/log$

I have included Xorg.0.log.old; hopefully it contains the no-output-logging.

Revision history for this message
Sander Jonkers (jonkers) wrote :

or: fglrx-driver

Revision history for this message
Sander Jonkers (jonkers) wrote :

To get fresh and shiny log files, I installed a fresh Ubuntu 8.04 (64-bit), installed ssh-server, activated the prop.driver (fglrx), rebooted, and then remotely logged on to get dmesg, Xorg.0.log.old, Xorg.0.log and xorg.conf. I will at those files with the filenames below:

sander@ubuntu-amd64:~$ ls -al | grep -i no-screen
-rw-r--r-- 1 sander sander 29531 2008-02-27 20:01 dmesg.fglrx.no-screen
-rw-r--r-- 1 sander sander 20499 2008-02-27 20:06 Xorg.0.log.old---prop.driver-no-screen.fglrx
-rw-r--r-- 1 sander sander 71987 2008-02-27 20:06 Xorg.0.log---prop.driver-no-screen.fglrx
-rw-r--r-- 1 sander sander 1256 2008-02-27 20:06 xorg.conf---prop.driver-no-screen.fglrx
sander@ubuntu-amd64:~$

First look at Xorg.0.log.old---prop.driver-no-screen.fglrx shows this:

(EE) fglrx(0): Given depth (8) is not supported by fglrx driver

Is that the problem?

(II) Setting vga for screen 0.
(II) fglrx(0): === [atiddxPreInit] === begin
(II) Loading sub module "vgahw"
(II) LoadModule: "vgahw"
(II) Loading /usr/lib/xorg/modules//libvgahw.so
(II) Module vgahw: vendor="X.Org Foundation"
        compiled for 1.4.0.90, module version = 0.1.0
        ABI class: X.Org Video Driver, version 2.0
(II) fglrx(0): PCI bus 1 card 5 func 0
(II) fglrx(0): Creating default Display subsection in Screen section
        "Default Screen" for depth/fbbpp 8/8
(EE) fglrx(0): Given depth (8) is not supported by fglrx driver
(EE) fglrx(0): PreInitVisual failed
SetVBEMode failed
(EE) fglrx(0): PreInit failed
(II) fglrx(0): === [atiddxPreInit] === end
(II) UnloadModule: "fglrx"
(II) UnloadModule: "vgahw"
(II) Unloading /usr/lib/xorg/modules//libvgahw.so
(EE) Screen(s) found, but none have a usable configuration.

Fatal server error:
no screens found

Revision history for this message
Sander Jonkers (jonkers) wrote :

Here's Xorg.0.log---prop.driver-no-screen.fglrx / Xorg.0.log

Revision history for this message
Sander Jonkers (jonkers) wrote :

Here's dmesg / dmesg.fglrx.no-screen

sander@ubuntu-amd64:~$ cat dmesg.fglrx.no-screen | grep fg
[ 33.230601] fglrx: module license 'Proprietary. (C) 2002 - ATI Technologies, Starnberg, GERMANY' taints kernel.
[ 33.329257] [fglrx] Maximum main memory to use for locked dma buffers: 3737 MBytes.
[ 33.329289] [fglrx] ASYNCIO init succeed!
[ 33.329410] [fglrx] PAT is enabled successfully!
[ 33.330553] [fglrx] module loaded - fglrx 8.45.5 [Feb 1 2008] on minor 0
sander@ubuntu-amd64:~

Revision history for this message
Sander Jonkers (jonkers) wrote :

And here's xorg.conf---prop.driver-no-screen.fglrx / xorg.conf

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.