[r128] Rage 128: Unsuitable videomode autoselected

[Gerald Kolllenda]

Binary package hint: xserver-xorg-video-ati

I tested Ubunti 7.10-beta-desktop-i386 on my PCs.

At one PC the X-Server was not able to start, and i saw only the commandline.

This PC has a ATI Technologies Inc Rage 128 PF/PRO AGP 4x TMDS connected to a Belinea 108080 CRT-Display. I tried to start the X-Server at the commandline an got errormessages, the X-Server didn't start:
************************************************************************
auth: creating new authority file /home/ubuntu/.serverauth.20130
xauth: creating new authority file /home/ubuntu/.Xauthority
xauth: creating new authority file /home/ubuntu/.Xauthority

X Window System Version 1.3.0
Release Date: 19 April 2007
X Protocol Version 11, Revision 0, Release 1.3
Build Operating System: Linux Ubuntu (xorg-server 2:1.3.0.0.dfsg-12ubuntu6)
Current Operating System: Linux ubuntu 2.6.22-12-generic #1 SMP Sun Sep 23 18:11:30 GMT 2007 i686
Build Date: 21 September 2007
 Before reporting problems, check http://wiki.x.org
 to make sure that you have the latest version.
Module Loader present
Markers: (--) probed, (**) from config file, (==) default setting,
 (++) from command line, (!!) notice, (II) informational,
 (WW) warning, (EE) error, (NI) not implemented, (??) unknown.

(==) Log file: "/var/log/Xorg.0.log", Time: Mon Oct 1 21:58:06 2007
(==) Using config file: "/etc/X11/xorg.conf"
(II) Module already built-in
(II) Module already built-in
(II) Module already built-in
(EE) R128(0): No DFP detected
(II) Module already built-in
(EE) R128(0): (Ron = 12288) + (Rloop = 17) >= (Roff = 10752)

Fatal server error:
AddScreen/ScreenInit failed for driver 0

XIO: fatal IO error 104 (Connection reset by peer) on X server ":0.0"
      after 0 requests (0 known processed) with 0 events remaining.

***************************************************************************************************
The /etc/X11/xorg.conf:
***************************************************************************************************
# xorg.conf (xorg X Window System server configuration file)
#
# This file was generated by dexconf, the Debian X Configuration tool, using
# values from the debconf database.
#
# Edit this file with caution, and see the xorg.conf manual page.
# (Type "man xorg.conf" at the shell prompt.)
#
# This file is automatically updated on xserver-xorg package upgrades *only*
# if it has not been modified since the last upgrade of the xserver-xorg
# package.
#
# If you have edited this file but would like it to be automatically updated
# again, run the following command:
# sudo dpkg-reconfigure -phigh xserver-xorg

Section "Files"
EndSection

Section "InputDevice"
 Identifier "Generic Keyboard"
 Driver "kbd"
 Option "CoreKeyboard"
 Option "XkbRules" "xorg"
 Option "XkbModel" "pc105"
 Option "XkbLayout" "de"
EndSection

Section "InputDevice"
 Identifier "Configured Mouse"
 Driver "mouse"
 Option "CorePointer"
 Option "Device" "/dev/input/mice"
 Option "Protocol" "ImPS/2"
 Option "ZAxisMapping" "4 5"
 Option "Emulate3Buttons" "true"
EndSection

Section "InputDevice"
 Driver "wacom"
 Identifier "stylus"
 Option "Device" "/dev/input/wacom"
 Option "Type" "stylus"
 Option "ForceDevice" "ISDV4" # Tablet PC ONLY
EndSection

Section "InputDevice"
 Driver "wacom"
 Identifier "eraser"
 Option "Device" "/dev/input/wacom"
 Option "Type" "eraser"
 Option "ForceDevice" "ISDV4" # Tablet PC ONLY
EndSection

Section "InputDevice"
 Driver "wacom"
 Identifier "cursor"
 Option "Device" "/dev/input/wacom"
 Option "Type" "cursor"
 Option "ForceDevice" "ISDV4" # Tablet PC ONLY
EndSection

Section "Device"
 Identifier "ATI Technologies Inc Rage 128 PF/PRO AGP 4x TMDS"
 Driver "ati"
 BusID "PCI:1:0:0"
EndSection

Section "Monitor"
 Identifier "108080"
 Option "DPMS"
EndSection

Section "Screen"
 Identifier "Default Screen"
 Device "ATI Technologies Inc Rage 128 PF/PRO AGP 4x TMDS"
 Monitor "108080"
 DefaultDepth 24
 SubSection "Display"
  Modes "2048x1536" "1920x1440" "1600x1200" "1280x1024" "1152x864" "1024x768" "832x624" "800x600" "720x400" "640x480"
 EndSubSection
EndSection

Section "ServerLayout"
 Identifier "Default Layout"
 Screen "Default Screen"
 InputDevice "Generic Keyboard"
 InputDevice "Configured Mouse"

# Uncomment if you have a wacom tablet
# InputDevice "stylus" "SendCoreEvents"
# InputDevice "cursor" "SendCoreEvents"
# InputDevice "eraser" "SendCoreEvents"
EndSection
**************************************************************************

The result of lspci:
******************************************************************************
0000:00:00.0 Host bridge: VIA Technologies, Inc. VT8605 [ProSavage PM133] (rev 81)
0000:00:01.0 PCI bridge: VIA Technologies, Inc. VT8605 [PM133 AGP]
0000:00:04.0 ISA bridge: VIA Technologies, Inc. VT82C686 [Apollo Super South] (rev 22)
0000:00:04.1 IDE interface: VIA Technologies, Inc. VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE (rev 10)
0000:00:04.2 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 10)
0000:00:04.3 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 10)
0000:00:04.4 Host bridge: VIA Technologies, Inc. VT82C686 [Apollo Super ACPI] (rev 30)
0000:00:0d.0 Ethernet controller: Intel Corp. 82557/8/9 [Ethernet Pro 100] (rev 0c)
0000:00:0e.0 Ethernet controller: Accton Technology Corporation SMC2-1211TX (rev 10)
0000:00:0f.0 SCSI storage controller: LSI Logic / Symbios Logic 53c810 (rev 23)
0000:00:11.0 Multimedia audio controller: Ensoniq 5880 AudioPCI (rev 02)
0000:01:00.0 VGA compatible controller: ATI Technologies Inc Rage 128 PF/PRO AGP 4x TMDS
******************************************************************************************

Normally i run debian sarge on this PC and so i compared the Xorg.conf files.

I tried to remove the both highest resolutions "2048x1536" "1920x1440" from the Modes-Line. After that i was able to start the X-Server from the commandline.

As far as I see, the autoselected Videomodes are unsuitable for this combination of hardware.

I hope my information is helpful

Gerald

[Timo Aaltonen (tjaalton)]

Seems like xresprobe didn't quite do it's job. Could you run 'sudo xresprobe radeon' and show what it gives?

[Gerald Kolllenda (ing-g-kollenda)]

Am Dienstag, den 02.10.2007, 14:43 +0000 schrieb Timo Aaltonen:
> Seems like xresprobe didn't quite do it's job. Could you run 'sudo
> xresprobe radeon' and show what it gives?
>
> ** Changed in: xresprobe (Ubuntu)
> Sourcepackagename: xserver-xorg-video-ati => xresprobe
> Status: New => Incomplete
>

Hello Timo,
here the output of sudo xresprobe radeon:
**********************************************
id: 108080
res: 2048x1536 1920x1440 1600x1200 1280x1024 1152x864 1024x768 832x624
800x600 720x400 640x480
freq: 30-121 50-160
disptype: crt
***********************************************
 Gerald

[Tormod Volden (tormodvolden)]

I wonder if the monitor reports these modes as fine, but the card can not drive them, and bails out instead of falling back on other modes.
Can you please run:
 sudo ddcprobe > ddcprobe.txt
and attach the file ddcprobe.txt?

[Gerald Kolllenda (ing-g-kollenda)]

Am Samstag, den 06.10.2007, 14:49 +0000 schrieb Tormod Volden:
> I wonder if the monitor reports these modes as fine, but the card can not drive them, and bails out instead of falling back on other modes.
> Can you please run:
> sudo ddcprobe > ddcprobe.txt
> and attach the file ddcprobe.txt?
>
Hello Tormold,
here the output of sudo ddcprobe:
*************************************
vbe: VESA 2.0 detected.
oem: ATI RAGE128
memory: 32768kb
mode: 800x600x16
mode: 1024x768x16
mode: 320x200x32k
mode: 320x200x64k
mode: 320x200x16m
mode: 1600x1200x256
mode: 640x400x256
mode: 640x480x256
mode: 640x480x32k
mode: 640x480x64k
mode: 640x480x16m
mode: 1600x1200x32k
mode: 800x600x256
mode: 800x600x32k
mode: 800x600x64k
mode: 800x600x16m
mode: 1600x1200x64k
mode: 1024x768x256
mode: 1024x768x32k
mode: 1024x768x64k
mode: 1024x768x16m
mode: 1280x1024x256
mode: 1280x1024x32k
mode: 1280x1024x64k
mode: 1280x1024x16m
mode: 132x25 (text)
mode: 132x43 (text)
edid:
edid: 1 2
id: 1f90
eisa: MAX1f90
serial: 00000490
manufacture: 50 2000
input: composite sync, sync on green, analog signal.
screensize: 41 30
gamma: 2.720000
dpms: RGB, active off, suspend, standby
timing: 720x400@70 Hz (VGA 640x400, IBM)
timing: 640x480@60 Hz (VGA)
timing: 640x480@67 Hz (Mac II, Apple)
timing: 640x480@75 Hz (VESA)
timing: 800x600@60 Hz (VESA)
timing: 800x600@72 Hz (VESA)
timing: 800x600@75 Hz (VESA)
timing: 832x624@75 Hz (Mac II)
timing: 1024x768@87 Hz Interlaced (8514A)
timing: 1024x768@70 Hz (VESA)
timing: 1024x768@75 Hz (VESA)
timing: 1280x1024@75 (VESA)
ctiming: 640x480@85
ctiming: 800x600@85
ctiming: 1024x768@85
ctiming: 1152x864@75
ctiming: 1280x1024@85
ctiming: 1920x1440@75
ctiming: 1600x1200@85
ctiming: 2048x1536@75
dtiming: 2048x1536@92
monitorserial: 01168
monitorname: 108080
monitorrange: 30-121, 50-160
***************************

nice greetings
 Gerald

[Tormod Volden (tormodvolden)]

If I understand /var/lib/dpkg/info/xserver-xorg.postinst well (likely not) the monitor ranges should have been written to xorg.conf because you have a "Rage 128" card. Can you please post the output from:
 grep -A2 config/monitor/use_sync_ranges /var/cache/debconf/config.dat

[Gerald Kolllenda (ing-g-kollenda)]

Am Samstag, den 06.10.2007, 19:23 +0000 schrieb Tormod Volden:
> If I understand /var/lib/dpkg/info/xserver-xorg.postinst well (likely not) the monitor ranges should have been written to xorg.conf because you have a "Rage 128" card. Can you please post the output from:
> grep -A2 config/monitor/use_sync_ranges /var/cache/debconf/config.dat
>
Hello Tormod,
here the output:
************************************
Name: xserver-xorg/config/monitor/use_sync_ranges
Template: xserver-xorg/config/monitor/use_sync_ranges
Value:
Owners: xserver-xorg
**************************************
nice greetings
 Gerald

[Tormod Volden (tormodvolden)]

Thanks for the information. Can you also do this (it will overwrite xorg.conf but makes a backup of the old):
 DEBUG_XORG_DEBCONF=1 sudo dpkg-reconfigure xserver-xorg -fnoninteractive 2>/tmp/reconf.log
and attach /tmp/reconf.log as a separate file attachment please.

[Gerald Kolllenda (ing-g-kollenda)]

Am Samstag, den 06.10.2007, 23:04 +0000 schrieb Tormod Volden:
> Thanks for the information. Can you also do this (it will overwrite xorg.conf but makes a backup of the old):
> DEBUG_XORG_DEBCONF=1 sudo dpkg-reconfigure xserver-xorg -fnoninteractive 2>/tmp/reconf.log
> and attach /tmp/reconf.log as a separate file attachment please.
>
Hello Tormod,
her the wanted logfile:
*********************************************
xserver-xorg postinst note: Configuring xserver-xorg.
xserver-xorg postinst note: X server symlink exists and points to
executable
   X server; capping X server question priority at medium.
xserver-xorg postinst note: $OWNERS has only one value;
shared/default-x-server
   will not be asked
xserver-xorg postinst note: auto_answer() "db_input medium
   xserver-xorg/autodetect_video_card" with default "true"
xserver-xorg postinst note: auto_answer: auto-answering with "true"
xserver-xorg postinst note: auto_answer:
xserver-xorg/autodetect_video_card
   is not being asked
xserver-xorg postinst note: auto_answer:
xserver-xorg/autodetect_video_card is
   "true"
xserver-xorg postinst note: autodetected X server: XFree86
xserver-xorg postinst note: seen flag of shared/default-x-server is
false
xserver-xorg postinst note: db_input low shared/default-x-server
xserver-xorg postinst note: auto_answer() "db_input low
   shared/default-x-server" with default "xserver-xorg"
xserver-xorg postinst note: auto_answer: auto-answering with
"xserver-xorg"
xserver-xorg postinst note: auto_answer: shared/default-x-server is not
   being asked
xserver-xorg postinst note: auto_answer: shared/default-x-server is
   "xserver-xorg"
xserver-xorg postinst note: available video driver list set to "amd,
apm,
   ark, ati, chips, cirrus, cyrix, fbdev, glint, i128, i740, i810,
imstt,
   intel, mga, neomagic, newport, nsc, nv, psb, rendition, s3, s3virge,
   savage, siliconmotion, sis, sisusb, tdfx, tga, trident, tseng, vesa,
vga,
   via, vmware, voodoo, ztv "
xserver-xorg postinst note: autodetected X server driver: ati
xserver-xorg postinst note: auto_answer() "db_input low
   xserver-xorg/config/device/driver" with default "ati"
xserver-xorg postinst note: auto_answer: auto-answering with "ati"
xserver-xorg postinst note: auto_answer:
xserver-xorg/config/device/driver
   is not being asked
xserver-xorg postinst note: auto_answer:
xserver-xorg/config/device/driver is
   "ati"
xserver-xorg postinst note: auto_answer() "validate_string_db_input low
   xserver-xorg/config/device/identifier" with default "ATI Technologies
   Inc Rage 128 PF/PRO AGP 4x TMDS"
xserver-xorg postinst note: auto_answer: auto-answering with "ATI
Technologies
   Inc Rage 128 PF/PRO AGP 4x TMDS"
xserver-xorg postinst note: auto_answer: asking
   xserver-xorg/config/device/identifier
xserver-xorg postinst note: auto_answer:
xserver-xorg/config/device/identifier
   is "ATI Technologies Inc Rage 128 PF/PRO AGP 4x TMDS"
xserver-xorg postinst note: auto_answer() "validate_bus_id_db_input
medium
   xserver-xorg/config/device/bus_id" with default "PCI:1:0:0"
xserver-xorg postinst note: auto_answer: auto-answering with "PCI:1:0:0"
xserver-xorg postinst note: auto_answer: asking
   xserver-xorg/confi...

[Tormod Volden (tormodvolden)]

> If I understand /var/lib/dpkg/info/xserver-xorg.postinst well (likely not) the monitor ranges should have been written to xorg.conf

Looking at it again, it seems like it is not meant to do that, only for lcd screens... Can you try to manually add the sync ranges to the autogenerated xorg.conf and see if that makes any difference? Add this to the Monitor section:
        HorizSync 30-121
        VertRefresh 50-160

Anyway, I might be on the wrong track here...

[Gerald Kolllenda (ing-g-kollenda)]

Am Dienstag, den 09.10.2007, 08:22 +0000 schrieb Tormod Volden:
> > If I understand /var/lib/dpkg/info/xserver-xorg.postinst well (likely
> not) the monitor ranges should have been written to xorg.conf
>
> Looking at it again, it seems like it is not meant to do that, only for lcd screens... Can you try to manually add the sync ranges to the autogenerated xorg.conf and see if that makes any difference? Add this to the Monitor section:
> HorizSync 30-121
> VertRefresh 50-160
>
> Anyway, I might be on the wrong track here...
>
Hello Tormod,
i don't see any difference.

I add the modified xorg.conf here, so you can check, whether i made the
changes correctly:
****************************************************
# xorg.conf (xorg X Window System server configuration file)
#
# This file was generated by dexconf, the Debian X Configuration tool,
using
# values from the debconf database.
#
# Edit this file with caution, and see the xorg.conf manual page.
# (Type "man xorg.conf" at the shell prompt.)
#
# This file is automatically updated on xserver-xorg package upgrades
*only*
# if it has not been modified since the last upgrade of the xserver-xorg
# package.
#
# If you have edited this file but would like it to be automatically
updated
# again, run the following command:
# sudo dpkg-reconfigure -phigh xserver-xorg

Section "Files"
EndSection

Section "InputDevice"
 Identifier "Generic Keyboard"
 Driver "kbd"
 Option "CoreKeyboard"
 Option "XkbRules" "xorg"
 Option "XkbModel" "pc105"
 Option "XkbLayout" "de"
EndSection

Section "InputDevice"
 Identifier "Configured Mouse"
 Driver "mouse"
 Option "CorePointer"
 Option "Device" "/dev/input/mice"
 Option "Protocol" "ImPS/2"
 Option "ZAxisMapping" "4 5"
 Option "Emulate3Buttons" "true"
EndSection

Section "InputDevice"
 Driver "wacom"
 Identifier "stylus"
 Option "Device" "/dev/input/wacom"
 Option "Type" "stylus"
 Option "ForceDevice" "ISDV4" # Tablet PC ONLY
EndSection

Section "InputDevice"
 Driver "wacom"
 Identifier "eraser"
 Option "Device" "/dev/input/wacom"
 Option "Type" "eraser"
 Option "ForceDevice" "ISDV4" # Tablet PC ONLY
EndSection

Section "InputDevice"
 Driver "wacom"
 Identifier "cursor"
 Option "Device" "/dev/input/wacom"
 Option "Type" "cursor"
 Option "ForceDevice" "ISDV4" # Tablet PC ONLY
EndSection

Section "Device"
 Identifier "ATI Technologies Inc Rage 128 PF/PRO AGP 4x TMDS"
 Driver "ati"
 BusID "PCI:1:0:0"
EndSection

Section "Monitor"
 Identifier "108080"
 HorizSync 30-121
 VertRefresh 50-160
 Option "DPMS"
EndSection

Section "Screen"
 Identifier "Default Screen"
 Device "ATI Technologies Inc Rage 128 PF/PRO AGP 4x TMDS"
 Monitor "108080"
 DefaultDepth 24
 SubSection "Display"
  Modes "2048x1536" "1920x1440" "1600x1200" "1280x1024" "1152x864"
"1024x768" "832x624" "800x600" "720x400" "640x480"
 EndSubSection
EndSection

Section "ServerLayout"
 Identifier "Default Layout"
 Screen "Default Screen"
 InputDevice "Generic Keyboard"
 InputDevice "Configured Mouse"

# Uncomment if you have a wacom tablet
# InputDevice "stylus" "SendCoreEvents"
# InputDevice "cursor" "SendCoreEvents"
# InputDevice "erase...

[Tormod Volden (tormodvolden)]

Thanks for trying out. Yes, I think the monitor detection is working right, but the card driver fails to drive some modes or fails to disable modes it cannot drive.

[Brian Murray (brian-murray)]

Thanks for taking the time to report this bug and helping to make Ubuntu better. In the development cycle for Intrepid there have been some vast improvements in the open source ati video driver and we could use your help testing them. Could you please download the latest Alpha CD image of Intrepid and test this particular bug just using the Live CD? You can find the latest image at http://www.ubuntu.com/testing . Your testing can help make Ubuntu and the open source ati driver even better! Thanks in advance.

[Gerald Kolllenda (ing-g-kollenda)]

Am Donnerstag, den 14.08.2008, 23:56 +0000 schrieb Brian Murray:
> Thanks for taking the time to report this bug and helping to make Ubuntu
> better. In the development cycle for Intrepid there have been some vast
> improvements in the open source ati video driver and we could use your
> help testing them. Could you please download the latest Alpha CD image
> of Intrepid and test this particular bug just using the Live CD? You
> can find the latest image at http://www.ubuntu.com/testing . Your
> testing can help make Ubuntu and the open source ati driver even better!
> Thanks in advance.
>
> ** Changed in: xserver-xorg-video-ati (Ubuntu)
> Status: Confirmed => Incomplete
>

Hello Brian,

i was on holidays, so some time went by until my answer.

I tried the Alpha4 Kubuntu today. I started the system from CD in the
live mode. The software was not able to find a correct video mode for
the grapics card and finally showed a text console after some attempts
to initialize the graphics card.

I tried to start the xserver from the textconsole with startx and got
the following error messages:

(EE) R128(0): No DFP detected
(EE) R128(0): (Ron = 12288) + (Rloop = 17) >= (Roff = 10752)

Fatal server error:
AddScreen/ScreenInit failed for driver 0

giving up.

As a test i used the /etc/X11/xorg.conf.failsafe instead of the
xorg.conf. In this way the xserver was able to start.

(Meanwhile I installed Kubuntu 8.04 on this system. I also had to modify
the xorg.conf to specify a reasonable resolution to get the Xserver
running.)

nice greetings

 Gerald

[Bryce Harrington (bryce)]

Thanks, could you attach your /var/log/Xorg.0.log from one of these failures on Intrepid, along with the full output from startx and the /etc/X11/xorg.conf that you used?

Also, just in case, can you also see what happens if you run with no xorg.conf? (Boot the live cd, then sudo mv /etc/X11/xorg.conf /etc/X11/xorg.conf.bak, then log out and log back in). The /var/log/Xorg.0.log from this would be useful to have as well.

Thanks ahead of time.

[Gerald Kolllenda (ing-g-kollenda)]

Am Donnerstag, den 28.08.2008, 20:05 +0000 schrieb Bryce Harrington:
> Thanks, could you attach your /var/log/Xorg.0.log from one of these
> failures on Intrepid, along with the full output from startx and the
> /etc/X11/xorg.conf that you used?
>
> Also, just in case, can you also see what happens if you run with no
> xorg.conf? (Boot the live cd, then sudo mv /etc/X11/xorg.conf
> /etc/X11/xorg.conf.bak, then log out and log back in). The
> /var/log/Xorg.0.log from this would be useful to have as well.
>
> Thanks ahead of time.
>
> ** Changed in: xserver-xorg-video-ati (Ubuntu)
> Status: Incomplete => New
>
> ** Changed in: xserver-xorg-video-ati (Ubuntu)
> Status: New => Incomplete
>

Hello Bryce,

i added the wanted files as attachment.

Good luck in debugging.

nice greetings

 Gerald

[Bryce Harrington (bryce)]

Not sure why this is filed against -ati when it should be against -r128. Refiling.

[Tormod Volden (tormodvolden)]

I think we should forward this bug report upstream. For this, we would need you to test latest Jaunty (for instance running a live CD) and attach new logs. Get a PowerPC live CD here: http://cdimage.ubuntu.com/ports/daily-live/current/

At the CD boot menu, add "text" to the boot options: https://help.ubuntu.com/community/BootParameters

The CD will now boot but not start X. At the text prompt, run "startx" to start X with the default driver.

Afterwards, copy the corresponding X log to the current directory:
 cp /var/log/Xorg.0.log .

Now edit xorg.conf to make X use the "vesa" (failsafe) driver:
 nano /etc/X11/xorg.conf
and change the Device section to look like this:

Section "Device"
      Identifier "Configured Video Device"
      Driver "vesa"
EndSection

Then start X which should give you a desktop session, although with low resolution:
 startx

From here, attach the xrandr.log and Xorg.0.log (which are in the Home
Folder) to this bug report. If for some reason you can not log into
launchpad from the live CD (network problems etc), you can also copy the
files to a USB drive now and attach them from another computer or
session later.

See also https://wiki.ubuntu.com/X/Troubleshooting/BlankScreen

[Gerald Kolllenda (ing-g-kollenda)]

Am Sonntag, den 15.03.2009, 14:38 +0000 schrieb Tormod Volden:
> I think we should forward this bug report upstream. For this, we would
> need you to test latest Jaunty (for instance running a live CD) and
> attach new logs. Get a PowerPC live CD here:
> http://cdimage.ubuntu.com/ports/daily-live/current/
>
> At the CD boot menu, add "text" to the boot options:
> https://help.ubuntu.com/community/BootParameters
>
> The CD will now boot but not start X. At the text prompt, run "startx"
> to start X with the default driver.
>
> Afterwards, copy the corresponding X log to the current directory:
> cp /var/log/Xorg.0.log .
>
> Now edit xorg.conf to make X use the "vesa" (failsafe) driver:
> nano /etc/X11/xorg.conf
> and change the Device section to look like this:
>
> Section "Device"
> Identifier "Configured Video Device"
> Driver "vesa"
> EndSection
>
> Then start X which should give you a desktop session, although with low resolution:
> startx
>
> >From here, attach the xrandr.log and Xorg.0.log (which are in the Home
> Folder) to this bug report. If for some reason you can not log into
> launchpad from the live CD (network problems etc), you can also copy the
> files to a USB drive now and attach them from another computer or
> session later.
>
> See also https://wiki.ubuntu.com/X/Troubleshooting/BlankScreen
>

Hello Tormod,

it is NOT a Power PC but a quite old (about year 2000) pentium 933MHz
PC. What image should i use please?

--
mit freundlichen Grüßen

Gerald Kollenda

Ingenieurbüro Kollenda
Ortsstraße 20
91466 Gerhardshofen
Tel: [phone]
Fax: [phone]
Mobil: 0172/6958297
Mail: <email address hidden>

[Tormod Volden (tormodvolden)]

Sorry, I mixed it up with another bug report (these cards are common on old macs). You can find images here: http://cdimage.ubuntu.com/releases/jaunty/

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

Created an attachment (id=23935)
Xorg.0.log with r128 driver

Forwarded from Ubuntu https://bugs.launchpad.net/bugs/148117

"This PC has a ATI Technologies Inc Rage 128 PF/PRO AGP 4x TMDS connected to a Belinea 108080 CRT-Display. I tried to start the X-Server at the commandline an got errormessages, the X-Server didn't start:"

(EE) R128(0): (Ron = 12288) + (Rloop = 17) >= (Roff = 10752)

Fatal server error:
AddScreen/ScreenInit failed for driver 0

This is with xorg-server 2:1.6.0-0ubuntu1 and xserver-xorg-video-r128 6.8.0+git20090201.08d56c88-1

[Gerald Kolllenda (ing-g-kollenda)]

Hello,

here is the wanted feedback with the both logfiles.

Am Sonntag, den 15.03.2009, 14:38 +0000 schrieb Tormod Volden:
> I think we should forward this bug report upstream. For this, we would
> need you to test latest Jaunty (for instance running a live CD) and
> attach new logs. Get a PowerPC live CD here:
> http://cdimage.ubuntu.com/ports/daily-live/current/
>
> At the CD boot menu, add "text" to the boot options:
> https://help.ubuntu.com/community/BootParameters
>
> The CD will now boot but not start X. At the text prompt, run "startx"
> to start X with the default driver.
>
> Afterwards, copy the corresponding X log to the current directory:
> cp /var/log/Xorg.0.log .
>
> Now edit xorg.conf to make X use the "vesa" (failsafe) driver:
> nano /etc/X11/xorg.conf
> and change the Device section to look like this:
>
> Section "Device"
> Identifier "Configured Video Device"
> Driver "vesa"
> EndSection
>
> Then start X which should give you a desktop session, although with low resolution:
> startx

> >From here, attach the xrandr.log and Xorg.0.log (which are in the Home
> Folder) to this bug report. If for some reason you can not log into
> launchpad from the live CD (network problems etc), you can also copy the
> files to a USB drive now and attach them from another computer or
> session later.
>
> See also https://wiki.ubuntu.com/X/Troubleshooting/BlankScreen
>
--
mit freundlichen Grüßen

Gerald Kollenda

Ingenieurbüro Kollenda
Ortsstraße 20
91466 Gerhardshofen
Tel: [phone]
Fax: [phone]
Mobil: 0172/6958297
Mail: <email address hidden>

[Tormod Volden (tormodvolden)]

I've forwarded your bug upstream to http://bugs.freedesktop.org/show_bug.cgi?id=20700 - please subscribe to this bug in case upstream needs more information or wishes you to test something. Thanks ahead of time!

[Mattst88 (mattst88)]

Is this still a problem?

[Tormod Volden (tormodvolden)]

Is this still a problem in Ubuntu 10.10 or Natty?

[Gerald Kolllenda (ing-g-kollenda)]

Am Freitag, den 03.12.2010, 20:14 +0000 schrieb Tormod Volden:
> Is this still a problem in Ubuntu 10.10 or Natty?
>
Hello Tormod,

this is still a problem in Ubuntu 10.10 (just tested with Ubuntu User
DVD in Life-Mode).

nice greetings

--
mit freundlichen Grüßen

Gerald Kollenda

Ingenieurbüro Kollenda
Ortsstraße 20
91466 Gerhardshofen
Tel: [phone]
Fax: [phone]
Mobil: 0172/6958297
Mail: <email address hidden>

[Bugzi11-fdo-tormod (bugzi11-fdo-tormod)]

Yes, this is still the same on Ubuntu 10.10 which has xserver 1.9.0.

[Jeremy Sequoia (jeremyhu)]

This is coming from R128InitDDARegisters during init in r128_driver.c:

    Roff = XclksPerTransferPrecise * (DisplayFifoDepth - 4);

    Ron = (4 * info->ram->MB
             + 3 * MAX(info->ram->Trcd - 2, 0)
             + 2 * info->ram->Trp
             + info->ram->Twr
             + info->ram->CL
             + info->ram->Tr2w
             + XclksPerTransfer) << (11 - UseablePrecision);

Not that it helps me much, but maybe someone can work with that...

That being said, this driver isn't really maintained anymore since it's not
used my modern devices... so I'm not sure this will ever be fixed.

[penalvch (penalvch)]

Gerald Kolllenda, thank you for reporting this bug to Ubuntu. Maverick reached EOL on April 10, 2012.
See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases

Is this an issue on a supported release? If so, could you please execute the following command, as it will automatically gather debugging information, in a terminal:
apport-collect 148117

Please ensure you have xdiagnose installed, and that you click the Yes button for attaching additional debugging information.

[Ajax-a (ajax-a)]

Mass closure: This bug has been untouched for more than six years, and is not
obviously still valid. Please reopen this bug or file a new report if you continue to experience issues with current releases.