Date: Wed, 4 Feb 2009 00:36:52 +0100 From: "Paul B. Mahol" <onemda@gmail.com> To: Marcin Cieslak <saper@system.pl> Cc: freebsd-x11@freebsd.org Subject: Re: [HEADS UP/CFT] Xserver 1.6 + randr + intel Message-ID: <3a142e750902031536o617e13c4m248ed716783ff37@mail.gmail.com> In-Reply-To: <498897CB.7080505@system.pl> References: <1233456742.1534.14.camel@ferret.2hip.net> <498897CB.7080505@system.pl>
next in thread | previous in thread | raw e-mail | index | archive | help
On 2/3/09, Marcin Cieslak <saper@system.pl> wrote: > Robert Noland wrote: >> Ok, I'm expecting Xserver 1.6 final to release sometime on Monday. I'm >> planning to commit this sometime next week. This patch includes the >> following Xserver 1.6rc2, randrproto rc, libXrandr rc, xrandr rc, and >> the 2.6.1 release of the intel driver. > > > After a successful upgrade of kernel and world r187968M:two days ago and > a successful (sic!) update of X to server 1.5.3 and friends I have > decided to give 1.6 a try. > > I have tried this both with intel and nv driver (my laptop has both but > only one can be active at the time - switchable at the boot time). > > 1. First thing, I have lost access to my legacy X11 fonts. > > [dix] Could not init font path element /usr/local/lib/X11/fonts/misc/, > removing from list! > [dix] Could not init font path element /usr/local/lib/X11/fonts/TTF/, > removing from list! > [dix] Could not init font path element /usr/local/lib/X11/fonts/OTF, > removing from list! > > etc. > > I get: > > % xset fp+ /usr/local/lib/X11/fonts/100dpi > xset: bad font path element (#23), possible causes are: > Directory does not exist or has wrong permissions > Directory missing fonts.dir > Incorrect font server address or syntax > > There is no more a "freetype" and "xtrap" module, so I had to change by > config. > > Gtk applications (seamonkey) and Qt (psi) have no problems with fonts, > but xterm does. xterm is unable to locate any bitmap font (fallback to > "fixed") and when told to use Freetype fonts (-fa 'Luxi Mono-10' option) > it looks like black text on black background (my xterm has a white fb, > black bg). You can issue commands in such a window (the letter spacing > is preserved and the cursor moves), but xterm segfaults when there is > a need to scroll. > > xterm -bg white segfaults immediately, > > xterm has been recompiled after 1.6 installation. > > 2. Once (when running NVidia) the server froze, i.e. I could only move > mouse and no keys worked (including server zap, switching VTs or > Ctrl-Alt-Del). This happened when displaying a fast-scrolling > ./configure output of the libXfont in a full-screen xterm window. > > The freeze doesn't look like > a http://bugs.freedesktop.org/show_bug.cgi?id=17358 however. > > I am using dwm as the window manager. > > A bunch of config files and output from various commands is available at: > > http://akson.sgh.waw.pl/~saper/FreeBSD/ports/xorg-server/xorg-1.6/ > > --Marcin > > _______________________________________________ > freebsd-x11@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-x11 > To unsubscribe, send any mail to "freebsd-x11-unsubscribe@freebsd.org" > Missing freetype module should be fixed in xorg-server git. -- Paul
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3a142e750902031536o617e13c4m248ed716783ff37>