From: "Dmitri Pogosyan" <pogosyan@phys.ualberta.ca>
To: gentoo-amd64@lists.gentoo.org
Subject: Re: [gentoo-amd64] Re: URGENT: No more fonts after xorg changes
Date: Sat, 2 Dec 2006 16:23:15 -0700 [thread overview]
Message-ID: <200612022323.kB2NNFj19978@webmail.phys.ualberta.ca> (raw)
What are you talking about ? 8776 is long ago stable on amd64
> > Hi,
> >
> > I got my fonts back by now, even with the beta driver from portage. There are
> > two main problems now:
> >
> > 1: i cant go back to stable nvidia-drivers, because of the font problem
> > 2: when using the beta driver, changing the resolution when running, lets say,
> > a game in fullscreen mode with another resolution than the standard crashes
> > X.
> >
> > cu
> > Dieter
>
> Using a minute to search on google can really help solve problems.
> 1. Stable nvidia is not compatible with xorg 7.1. This has been discussed
> at length both here and on nvnews.net
> 2. nvidia 9629 has a horrible _known_ bug that causes the crash.
>
> You can easily mask it using:
>
> echo =x11-drivers/nvidia-drivers-1.0.9629 >> /etc/portage/package.mask
>
> Then emerge the unstable (~amd64) driver in portage. It should be 8776,
> which works.
> --
> gentoo-amd64@gentoo.org mailing list
--
Dmitri Pogosyan Department of Physics
Associate Professor University of Alberta
tel 1-780-492-2150 11322 - 89 Avenue
fax 1-780-492-0714 Edmonton, AB, T6G 2G7, CANADA
--
gentoo-amd64@gentoo.org mailing list
next reply other threads:[~2006-12-02 23:25 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-02 23:23 Dmitri Pogosyan [this message]
2006-12-03 10:35 ` [gentoo-amd64] [SOLVED] Re: URGENT: No more fonts after xorg changes Dieter Ries
2006-12-03 15:48 ` Michael Weyershäuser
2006-12-03 17:02 ` Dieter Ries
-- strict thread matches above, loose matches on Subject: below --
2006-12-03 21:18 [gentoo-amd64] " Dmitri Pogosyan
2006-12-02 16:10 [gentoo-amd64] " Clip2
2006-12-02 16:26 ` Dieter Ries
2006-12-02 19:10 ` [gentoo-amd64] " Duncan
2006-12-02 19:22 ` Dieter Ries
2006-12-02 22:26 ` Nuitari
2006-12-03 10:53 ` Neil Bothwick
2006-12-03 13:32 ` Boyd Stephen Smith Jr.
2006-12-03 15:24 ` Neil Bothwick
2006-12-03 21:04 ` Boyd Stephen Smith Jr.
2006-12-04 1:03 ` Thomas Rösner
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200612022323.kB2NNFj19978@webmail.phys.ualberta.ca \
--to=pogosyan@phys.ualberta.ca \
--cc=gentoo-amd64@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox