When using the graphical installer for Fedora Core 3, the xserver crashed and displayed multicolored snow. I proceeded with the text install. After configuring X with the system config tool, the default gnome behavior was erratic, windows were not displayed fully. The xserver used to work properly with RH9 and Xfree86 4.3. I proceeded to use X -configure and setup xorg.conf by hand. X -config xorg.conf.new will produce a screen with the same multicolored static. Hardware: Compaq 3200 =============================== lspci output: =============================== 00:00.0 Host bridge: Intel Corp. 82810E DC-133 GMCH [Graphics Memory Controller Hub] (rev 03) 00:01.0 VGA compatible controller: Intel Corp. 82810E DC-133 CGC [Chipset Graphi cs Controller] (rev 03) 00:1e.0 PCI bridge: Intel Corp. 82801AA PCI Bridge (rev 02) 00:1f.0 ISA bridge: Intel Corp. 82801AA ISA Bridge (LPC) (rev 02) 00:1f.1 IDE interface: Intel Corp. 82801AA IDE (rev 02) 00:1f.2 USB Controller: Intel Corp. 82801AA USB (rev 02) 00:1f.3 SMBus: Intel Corp. 82801AA SMBus (rev 02) 01:05.0 Multimedia audio controller: ESS Technology ES1988 Allegro-1 (rev 12) 01:0a.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139 C+ (rev 10) 01:0b.0 FireWire (IEEE 1394): Texas Instruments TSB12LV26 IEEE-1394 Controller ( Link) ================================ xorg.conf ================================ Section "ServerLayout" Identifier "X.org Configured" Screen 0 "Screen0" 0 0 InputDevice "Mouse0" "CorePointer" InputDevice "Keyboard0" "CoreKeyboard" EndSection Section "Files" RgbPath "/usr/X11R6/lib/X11/rgb" ModulePath "/usr/X11R6/lib/modules" FontPath "/usr/X11R6/lib/X11/fonts/misc/" FontPath "/usr/X11R6/lib/X11/fonts/TTF/" FontPath "/usr/X11R6/lib/X11/fonts/Type1/" FontPath "/usr/X11R6/lib/X11/fonts/CID/" FontPath "/usr/X11R6/lib/X11/fonts/75dpi/" FontPath "/usr/X11R6/lib/X11/fonts/100dpi/" EndSection Section "Module" Load "record" Load "dbe" Load "xtrap" Load "extmod" Load "glx" Load "dri" Load "vnc" Load "freetype" Load "type1" Load "fbdevhw" EndSection Section "InputDevice" Identifier "Mouse0" Driver "mouse" Option "Protocol" "auto" Option "Device" "/dev/input/mice" Option "ZAxisMapping" "4 5" Option "Emulate3Buttons" "no" EndSection Section "Monitor" Identifier "Monitor0" VendorName "Monitor Vendor" ModelName "Monitor Model" HorizSync 31.5 - 48.5 VertRefresh 40.0 - 70.0 EndSection Section "Device" ### Available Driver options are:- ### Values: <i>: integer, <f>: float, <bool>: "True"/"False", ### <string>: "String", <freq>: "<f> Hz/kHz/MHz" ### [arg]: arg optional #Option "NoAccel" # [<bool>] #Option "SWcursor" # [<bool>] #Option "ColorKey" # <i> #Option "CacheLines" # <i> #Option "Dac6Bit" # [<bool>] #Option "DRI" # [<bool>] #Option "NoDDC" # [<bool>] #Option "ShowCache" # [<bool>] #Option "XvMCSurfaces" # <i> #Option "PageFlip" # [<bool>] Identifier "Card0" Driver "i810" VendorName "Intel Corp." BoardName "82810E DC-133 CGC [Chipset Graphics Controller]" BusID "PCI:0:1:0" #VideoRam 16384 #VideoRam 8000 EndSection Section "Screen" Identifier "Screen0" Device "Card0" Monitor "Monitor0" DefaultDepth 16 SubSection "Display" Viewport 0 0 Depth 16 Modes "1024x768" EndSubSection SubSection "Display" Viewport 0 0 Depth 24 Modes "1024x768" EndSubSection EndSection
I had Mandrake 10.0 on my Dell Inspiron 2500 under X working without problem, but somehow I disliked look of fonts, so I installed Fedora Core 3. First install (graphical) went OK, but on first restart I saw garbage. Second install was text, but as default initlevel is 5, on first restart -> garbage. I somehow managed to boot it, changed initlevel to 3, and now procedure is following: Boot to text mode (initlevel 3), log in to text mode, type startx and then everything works OK. Something is evidently broken in boot initialization/agpgart memory allocation.
If you upgrade to the later versions of X from the repositories, X does not exhibit the refresh problem. (The garbage that you see). I boot runlevel 3 mostly but have booted runlevel 5 before with the below in the driver section of the xorg.conf file. Option "NoAccel" There are some different aproaches to resolving or lessening the effects caused by the refresh problem. The current concept allows DRI to work at higher resolutions. The latest development fix lowers the maximum resolution where DRI is active. It does not exhibit the refresh problem on my tests. I'll try booting runlevel 5 to ensure that the refresh is not related to the order of initialization between startx and runlevel 5 later.
There have been improvements with the 810/815 card performance using the latest version of X from Fedora. The bug number is below for reference. You do not need to mask the problem with adding the option "NoAccel" to the driver section of xorg.conf any more. You can select regular resolutions that are in-line with how the driver worked before the problem. link to redhat bug report below: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=132267 Jim
Have you guys tried Fedora Core 4 test 2 to see if it solves your problems ?
To the reporter, and others who experienced this issue before: Fedora Core 3 current xorg-x11 is 6.8.2 - please upgrade to that as a minimum, and let us know if the problem is resolved, as I believe it is. If the problem still exists in that release, update to FC4test2 as Alan suggested above, which is a slightly newer build, which will also be released for FC3 in the next few months, so it will be good to know if the problem is present still or not. TIA Alan: The problem reported here sounds very very suspiciously like the issue that has been fixed for some time now, and I'm fairly certain it is resolved now. If you don't hear feedback one way or another in a week or two from anyone, I think it's likely safe to close this one as "FIXED" in XORG-6_8-branch TTYL
The problem with the driver refresh is gone now. I am running xorg-x11-6.8.2-26. There is now a problem with a border around the virtual terminal after X was launched. Also the text will start on the farmost left edge for about a tenth of a character. The remaining 90 percent of the character will start on the next line followed by the other information that is set to the display. This problem only happens after X was started. For users of the Intel 865, no text is seen in any virtual terminal. My blue border, shifted text is with an Intel 815 card.
Regarding comment #6 (by Jim), about corrupted textmode display (colors, border, wraparound) after leaving X, check out bug 2991 which was opened specifically about that problem.
Thanks! There is another bug that is similar, but is only for tracking the i810 driver. The problem seems to get worse when in DRI mode. My problem is when not using DRI. (MGA driver) There is another bug 3094 that is specifically for tracking the i810 bug. The bugs are very similar.
Closing. Believed to be fixed in X.Org 6.8.2. Re-open if the problem persists.
hi i have loaded fedora core 3 on my 810 chipset PC and also edited /xorg.conf with command line ootion "noaccel" linux working better but i am not able to increase the resolution and the color depth please help me regarding this problem
As you will discover, there are many different cards that use the i810 driver. There are also a host of causes for low resolution which are not due to the driver but are either BIOS settings that effect your memory allowed to be used by the video chip. There is a legacy video setting on Dell computers that is set as default to use only 1 MB. Change this setting to 8 MB. There is also another setting which can be set to 64 MB, 128 MB, 256 MB. I set my setting to 128 MB. You can choose whatever setting you choose. You should be able to get fairly high resolution modes even at 64 MB. My guess is you are running a Dell with an 865G with BIOS version A03. If this wild guess (based on my problem with the above mentioned). Upgrading your BIOS to version A04 and adjusting your settings in BIOS should clear up your problem. You should not have to add Option "NoAccel" to your xorg.conf either with the above mentioned settings and Upgrades to BIOS applied.
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.