Bug 24205 - XFree86 4.0.2 hangs after power-on on neomagic
Summary: XFree86 4.0.2 hangs after power-on on neomagic
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: XFree86 (Show other bugs)
(Show other bugs)
Version: 7.1
Hardware: i386 Linux
Target Milestone: ---
Assignee: Bill Nottingham
QA Contact: David Lawrence
Whiteboard: Florence Gold
Depends On:
TreeView+ depends on / blocked
Reported: 2001-01-17 10:10 UTC by Pekka Pietikäinen
Modified: 2014-03-17 02:18 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2001-03-14 23:57:40 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

Description Pekka Pietikäinen 2001-01-17 10:10:41 UTC
On my HP 4100 with "Neomagic Corporation NM2160 [MagicGraph 128XD] (rev
after starting up directly after power-on XFree86 4.0.2 crashes after a
very short while.
(e.g. in the installer the gets up to language selection)

Two work-arounds are either Option "noaccel" or starting XF86_SVGA
first, then shutting it down and after that everything is fine with XF4, 
even after a reboot (but not a power-off)

Here's a diff of XFree86.0.log before and after starting up XF86_SVGA

--- doesntwork	Tue Jan 16 21:27:09 2001
+++ works	Tue Jan 16 21:18:32 2001
@@ -7,7 +7,7 @@
 	reporting problems.  (See http://www.XFree86.Org/FAQ)
 Operating System: Linux 2.2.17-8smp i686 [ELF] 
 Module Loader present
-(==) Log file: "/var/log/XFree86.0.log", Time: Tue Jan 16 21:22:20 2001
+(==) Log file: "/var/log/XFree86.0.log", Time: Tue Jan 16 21:15:18 2001
 (==) Using config file: "/etc/X11/XF86Config-4"
 Markers: (--) probed, (**) from config file, (==) default setting,
          (++) from command line, (!!) notice, (II) informational,
@@ -47,7 +47,7 @@
 	ABI class: XFree86 Video Driver, version 0.3
 (II) PCI: Probing config type using method 1
 (II) PCI: Config type is 1
-(II) PCI: stages = 0x03, oldVal1 = 0x00000000, mode1Res1 = 0x80000000
+(II) PCI: stages = 0x03, oldVal1 = 0x80002090, mode1Res1 = 0x80000000
 (II) PCI: PCI scan (all values are in hex)
 (II) PCI: 00:00:0: chip 8086,7192 card 0000,0000 rev 02 class 06,00,00 hdr
 (II) PCI: 00:02:0: chip 10c8,0004 card 103c,0002 rev 01 class 03,00,00 hdr
@@ -428,3 +428,4 @@
 (**) Mouse0: ZAxisMapping: buttons 4 and 5
 (II) Keyboard "Keyboard0" handled by legacy driver
 (II) XINPUT: Adding extended input device "Mouse0" (type: MOUSE)
+(II) NEOMAGIC(0): Not programming shadow registers

Comment 1 Glen Foster 2001-01-17 18:23:08 UTC
This defect is considered MUST-FIX for Florence Gold release

Comment 2 Mike A. Harris 2001-01-28 08:59:13 UTC
I'm awaiting patches for neomagic from XFree86 folk.  I do not have
a card to test with however.

Comment 3 Bill Nottingham 2001-02-14 05:44:05 UTC
Does this continue with beta3?

I can't reproduce this on my Neomagic here, but it's a different

Comment 4 Pekka Pietikäinen 2001-02-15 10:36:06 UTC
Yep, the same bug is in beta3.

Comment 5 Pekka Pietikäinen 2001-02-19 15:51:06 UTC
And RC1 (although it seemed to run for a bit longer before hanging, could be
changes in my gnome setup or something)

Comment 6 Mike A. Harris 2001-03-03 03:18:04 UTC
Try checking out the latest Rawhide packages, or the ones on my ftp


Comment 7 Pekka Pietikäinen 2001-03-05 10:12:48 UTC
Nope :(

Looking at XFree86 Changelogs at http://www.xfree86.org/cvs/changes.html,
there seems to be this in

157. Added a delay to prevent rare cases of lockups when starting 
      X on NeoMagic 2160 (Miles Lane).
And maybe related (this for 4.0.2a), although it's a different chip

1215. Fix Neomagic 2200 screen corruption (Egbert Eich).

The problem does appear as screen corruption, e.g. in gnome-terminal
the char that should be on the left edge appears in the right.
If you continue using the system for a while, _then_ it hangs. 
(I did remove mc from my gnome startup, which made it hang immediately)

Comment 8 Pekka Pietikäinen 2001-03-08 09:37:53 UTC

From the fine manual (man neomagic)

       On  some laptops using the 2160 chipset (MagicGraph 128XD)
       the following options are needed to avoid a lock-up of the
       graphic engine:
           Option "XaaNoScanlineImageWriteRect"
           Option "XaaNoScanlineCPUToScreenColorExpandFill"

And those seemed to have fixed the problem (4.0.2-11.4.0). I'm 99% sure I tested
with the original X server I was having problems in b1/b2 with without success,
Now, why starting XFree86 3.3.6 first removes the problem is complely beyond me 
(maybe it sets some magic bit in the chip, who knows)

So, I think the only thing that needs to be done is something like this in
(optionally keeping those commented out).

--- Cards.orig	Thu Mar  8 10:31:02 2001
+++ Cards	Thu Mar  8 10:34:05 2001
@@ -3013,6 +3013,10 @@
 LINE #    Option     "no_mmio"
 LINE #    Option     "lcd_center"
 LINE #    Option     "no_stretch"
+LINE #    The following options are needed to prevent a lock-up 
+LINE #	  of the graphics engine on some laptops
+LINE 	  Option "XaaNoScanlineImageWriteRect"
+LINE      Option "XaaNoScanlineCPUToScreenColorExpandFill"
 # NeoMagic

Comment 9 Bill Nottingham 2001-03-08 22:39:35 UTC
Will be fixed in Xconfigurator-4.9.19-1/kudzu-0.97.6-1.

Comment 10 Pekka Pietikäinen 2001-03-13 17:06:20 UTC
Argh! Those LINE entries were for XFree86 3.3.x, not 4.x (in fact, 3.3.x doesn't
like those lines at all and refuses to start, even)

Alas it looks like there's no way of Xconfigurator adding anything extra to the
device section
for XFree86 4.x.

Comment 11 Mike A. Harris 2001-03-14 10:16:48 UTC
Ok, I can't make heads or tails on this one.  Is this an issue with
XFree86 4.0.x or 3.3.6, or both.  The bug is currently filed against
3.3.6, and the discussion seems about 75% about 4.0.x.

If this is a bug against 4.0.x, please change the component to XFree86
as XFree86-servers is NOT 4.x, but is 3.3.6.  If bugs exist in both,
make two separate bug reports please.  I can't look into the issue unless
it is totally clear to me what version we are talking about here, and
misfiling against a wrong package doesn't help much.

Comment 12 Pekka Pietikäinen 2001-03-14 10:36:58 UTC
Yes, it's a 4.0.2 bug (and 3.3.6 is fine, in fact like I mentioned
in the first mail, starting XF86_SVGA/3.3.6 _first_,
then XFree86 4.0.2 makes the problem go away. So does using the Xaa options
with 4.0.2).

I changed the package to the correct one.

Comment 13 Bill Nottingham 2001-03-14 23:59:14 UTC
OK, Xconfigurator will be fixed to write Option lines for XFree4 as well
as of 4.9.22-1. That should fix this.

Comment 14 Pekka Pietikäinen 2001-03-15 11:31:02 UTC
Close but no cookie.

It now generates a perfectly working XFree86 4.0.2 configuration, but not a
working XFree86 3.3.6 one (not that I need one, but someone else might). The
problem is that options valid for 4.0.2 are 
not necessarily valid for 3.3.6 (and probably the other way around).  Thus there
needs to be a separate LINE4 or similar to get the right things in the right

Comment 15 Pekka Pietikäinen 2001-03-20 17:52:25 UTC
Just tried qa0319. 

Everything seems to be ok now as far as Xconfigurator is concerned.
Maybe having externDisp and internDisp enabled for XFree86 3.3.6 would be
but that would probably end up being a non-trivial change, and the way things
are now,
3.3.6 works but doesn't enable the external display by default, and 4.0.3 works
just the way you would expect it to.

Which leaves anaconda, which seems to not be using XF86_FBdev for whatever
in this release (sure it's ugly on neomagic, but it does work).

I'd say just tell users to use text mode if they have problems (or Option
"noaccel" for everyone?)

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