Date: Tue, 27 Jan 2009 14:54:18 +0000 From: "O. Hartmann" <ohartman@zedat.fu-berlin.de> To: Alex Goncharov <alex-goncharov@comcast.net> Cc: freebsd-ports-bugs@FreeBSD.org, freebsd-gnats-submit@FreeBSD.org Subject: Re: ports/131016: xorg-7.4 renders system unusable! Message-ID: <497F201A.8020305@zedat.fu-berlin.de> In-Reply-To: <E1LRVQw-0005go-0P@daland.home> References: <200901261646.n0QGkDpr097208@www.freebsd.org> <E1LRVQw-0005go-0P@daland.home>
next in thread | previous in thread | raw e-mail | index | archive | help
Alex Goncharov wrote: > Ditto here. > > Last night I updated a desktop and have garbage (or call it a visual > noise if you will) in my windows all the time now. > > Nevertheless, I upgraded a laptop -- and can't use X here at all: > while the mouse pointer moves, the keyboard is "dead", until some > number of key presses leads to a loud continuous beep; I can switch to > the non-X virtual consoles but the beep continues and I have to reboot > the system to kill the sound. > > Disabling HAL doesn't make things much better, although in my current > configuration I don't have a continuous sound and can experiment. > > Putting `xev' into ~/.xsession, I observed that all (?) the keystrokes > result in "keysym 0x0". > > Bottom line: the X system is unusable after the upgrade; no diagnostic > tool that I tried provides a clue about how to make it work. After an compilation orgy and the weirdness of an obvious false xcb-XXX compilation (xcb-proto etc needs to be recompiled BEFORE the suggested UPDATING step via portupgrade -rf libxcb is performed) X is up and running - but NO(!!!!) switching to any VT. This sucks. This is with driver 'nv' as with 'radeon'. Switching obviously works - I can switch vom ttyv7 keeping the X11-display to others - but they are black and the monitor is NO SIGNAL signalling. I can switch back to the tty keeping X11 without any problem. Having no VT/console is very bad :-( I also performed the steps for avoiding this useless 'hald/dbus' combination for my keyboard and mouse and it works now for me - but with the above mentioned result of not having access to my VT.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?497F201A.8020305>