Bug 188041 - Riva128 no longer can be configured
Summary: Riva128 no longer can be configured
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: Fedora
Classification: Fedora
Component: xorg-x11-drv-nv
Version: rawhide
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Adam Jackson
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2006-04-05 15:45 UTC by David A. De Graaf
Modified: 2018-04-11 18:59 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2007-10-30 01:07:20 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description David A. De Graaf 2006-04-05 15:45:18 UTC
Description of problem:
system-config-display can no longer configure my video card or start X


Version-Release number of selected component (if applicable):
system-config-display-1.0.37-2

How reproducible:
Failed during FC5 new installation and twice more afterward.


Steps to Reproduce:
1. Run it from console to try to configure X for first time - with no xorg.conf
2.
3.
  
Actual results:
# system-config-display
xconf.py: Fatal IO error 104 (Connection reset by peer) on X server :17.0.
[root@datant ~]
# Window manager error: Unable to open X display :17.0



Expected results:
A working xorg.conf and working X.


Additional info:
1)  It used to work.
2)  If I retrieve xorg.conf from FC4 backup, X starts perfectly.
3)  The video card is reported by lspci thusly:
  00:11.0 VGA compatible controller: NVidia / SGS Thomson (Joint Venture)
Riva128 (rev 10)
4)  The old, working xorg.conf file contains:
Section "Device"
        Identifier  "Videocard0"
        Driver      "nv"
        VendorName  "Videocard vendor"
        BoardName   "RIVA128"
EndSection

Comment 1 Adam Jackson 2007-03-26 21:46:17 UTC
Actually an nv driver bug, in that it can't do 16bpp, but only 15 or 24.

Comment 2 Matěj Cepl 2007-08-17 14:58:54 UTC
Reporter, I am sorry, that we have left this bug unnoticed for so long, but
could you confirm please, that this bug still could be reproduced with the
latest updates?


Comment 3 David A. De Graaf 2007-08-23 19:06:42 UTC
I am happy to report that the bug is dead with F7 and kernel 2.6.21-1.3228.fc7.
I set aside the working /etc/X11/xorg.conf file and then, as root, ran
system-config-display.  It worked perfectly and created a new xorg.conf file.

This is on a very old, very slow 200 MHz Pentium that I rarely use for anything.

Now, if you could only speed up the machine...     :-)

Thanks for the fix.

Comment 4 Adam Jackson 2007-10-30 01:07:20 UTC
Cool!  Marking WORKSFORME.


Note You need to log in before you can comment on or make changes to this bug.