Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#1437 - Xorg 6.8 Crash on return from VT

Attached to Project: Arch Linux
Opened by Simo Leone (neotuli) - Tuesday, 14 September 2004, 00:27 GMT
Task Type Bug Report
Category Packages: Current
Status Closed
Assigned To No-one
Architecture not specified
Severity High
Priority Normal
Reported Version 0.7 Wombat
Due in Version Undecided
Due Date Undecided
Percent Complete 0%
Votes 0
Private No

Details

When I ctrl+alt+F# out of X, the VT's all work fine, but when I attempt to return to the VT that X is running on (ctrl+alt+F7), the server crashes, and an image of the mouse freezes on the screen, including in the VT's. Both the message displayed on the VT that X was running on and in /var/log/Xorg.0.log are the same, and are as follow:

"Fatal server error:
EnterVT failed for screen 0


Please consult the The X.Org Foundation support
at http://wiki.X.Org
for help.
Please also check the log file at "/var/log/Xorg.0.log" for additional information.


*** If unresolved symbols were reported above, they might not
*** be the reason for the server aborting.

FatalError re-entered, aborting
Caught signal 11. Server aborting"

This is a major problem, as I cannot switch back to X from my VT's, and everything running in X goes down right with it, thus I hope that this problem is resolved very quickly.
This task depends upon

Closed by  Damir Perisa (damir.perisa)
Sunday, 06 March 2005, 16:42 GMT
Reason for closing:  Not a bug
Comment by Dale Blount (dale) - Tuesday, 14 September 2004, 15:25 GMT
this doesn't happen for me, I can switch to a VT then back to X just fine... Are you using a frame buffer module of some sorts?
Comment by Simo Leone (neotuli) - Tuesday, 14 September 2004, 23:03 GMT
Yes, I am running a the i810 frambuffer module in the kernel.
Comment by Steven J. Slizewski (slyski) - Wednesday, 15 September 2004, 01:29 GMT
I can't even get into x with xorg 6.8
My error messages are the same as Simo's and I'm using an ATI Radeon
card and using the radeon module.

Went back to using 6.7 with no problems
Comment by Lukas Sabota (punkrockguy318) - Saturday, 06 November 2004, 20:13 GMT
What DM are you using? GDM?
Comment by Simo Leone (neotuli) - Sunday, 07 November 2004, 01:50 GMT
I don't use GDM, or any others, I initially boot into a console and startx from there. It looks as though the same problem has been reported to xorg by people using i810's (https://freedesktop.org/bugzilla/show_bug.cgi?id=1467). This is a really annoying problem, I like being able to go back to my VT's and have lived without them for like 2 months now.
Comment by Lukas Sabota (punkrockguy318) - Thursday, 25 November 2004, 16:56 GMT
This same problem is happening to my buddy's machine. It's a very serious problem.
Comment by Kevin Piche (kpiche) - Thursday, 10 February 2005, 02:43 GMT
From a recent comment on this  bug 1567  https://bugs.freedesktop.org/show_bug.cgi?id=1467#c4 :

"Further investigations revealed that adding Option "NoAccel" "true" to xorg.conf resolves the problem which means it's a dri problem."
Comment by Kevin Piche (kpiche) - Thursday, 10 February 2005, 02:44 GMT
Umm, s/1567/1467/
Comment by Simo Leone (neotuli) - Thursday, 10 February 2005, 03:11 GMT
yea noaccel is a generally bad idea on this chip (not that there is much in the first place..but it does help). I would expect that adding the noaccel option (which makes the processor do everything) will bring graphics to a crawl at best.

I no longer use this chip, so I can no longer provide confirmation on whether or not it has been fixed in any future releases.
Comment by Simo Leone (neotuli) - Saturday, 12 February 2005, 22:17 GMT
Can someone try this out with the newly released Xorg and see if it's been fixed, so we might have a chance at closing out this bug?
Comment by Raven Morris (Samus_Aran) - Wednesday, 16 February 2005, 05:25 GMT
Simo Leone:
A simple solution is to switch to the VESA-FrameBuffer kernel module. While it is unaccellerated, and therefore much slower at rendering text and graphics to the TTY, it is extremely stable and almost never has any issues with switching back and forth from X11.
Comment by Damir Perisa (damir.perisa) - Sunday, 06 March 2005, 16:40 GMT
nvidia has very similar trouble:

http://icculus.org/lgfaq/#nvidiaframebuffer
Comment by Damir Perisa (damir.perisa) - Sunday, 06 March 2005, 16:42 GMT
this is either a kernel-fb bug or a x-driver bug but not an arch-bug

closing: not a bug

==> use vesa-fb

Loading...