> > > On 7 Nov 2002, Eric Anholt wrote: > > > On Thu, 2002-11-07 at 16:56, Horen wrote: > > > > > > > > > > > > On 7 Nov 2002, Eric Anholt wrote: > > > > > > > On Thu, 2002-11-07 at 04:40, Horen wrote: > > > > > > > > > > > > > > > On 6 Nov 2002, Eric Anholt wrote: > > > > > > > > > > > On Wed, 2002-11-06 at 18:34, Horen wrote: > > > > > > > > > > > > > > Posted a week ago the question, didn't get any reaction. > > > > > > > > > > > > > > Everything with current from last night works fine but killing > > > > > > > X or logging out ends in a black screen. No way to activate the > > > > > > > display without reboot. Remote login is fine. Typing blind works > > > > > > > too. > > > > > > > > > > > > How long has this been going on? Did it start at any particular point > > > > > > (a specific kernel or XFree86 upgrade)? What video card do you use? > > > > > > Does starting X again not work? > > > > > > > > > > > > > > > > It started sometimes in Oct, switched back to 4.7 stable. Did yesterday > > > > > an installation from scratch and built XFree86-Server after buildworld. > > > > > > > > I was asking if X has ever exited cleanly to console for you after > > > > logging out, and if it has, what you changed (particularly in your > > > > XFree86-Server version) between when it was working and when it wasn't. > > > > This is most likely just a failure of the driver to properly reset > > > > things for your card. Does disabling DRI in XF86Config help it exit > > > > cleanly? > > > > > > > > > > X has exited cleanly only on 4.6 or 4.7 , never on 5.0 in the > > > last 4-5 weeks. Didn't change anything. I disabled DRI but, didn't > > > help. Work normally with res 1600x1200 , tried 1024x768 to 1920x1440. > > > Nothing changed. > > > > Exact same version of the X Server (pkg_info | grep XFree86-Server)? > > > > XFree86-Server-4.2.1_5 XFree86-4 X server and related programs >
Do you think, it makes sense, that I grab an other version, 4.2.0 or even 4.1.x to check ? -Horen To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
