public inbox for gentoo-amd64@lists.gentoo.org
 help / color / mirror / Atom feed
From: Dieter Ries <clip2@gmx.de>
To: gentoo-amd64@lists.gentoo.org
Subject: Re: [gentoo-amd64]  Re: URGENT: No more fonts after xorg changes
Date: Sat, 2 Dec 2006 20:22:07 +0100	[thread overview]
Message-ID: <200612022022.10099.clip2@gmx.de> (raw)
In-Reply-To: <eksj33$r1e$1@sea.gmane.org>

[-- Attachment #1: Type: text/plain, Size: 3755 bytes --]

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


Am Samstag 02 Dezember 2006 20:10 schrieb Duncan:
> "Dieter Ries" <Clip2@gmx.de> posted 20061202162650.218370@gmx.net,
>
> excerpted below, on  Sat, 02 Dec 2006 17:26:50 +0100:
> > When I try to start X, there is a message, that the module i use is
> > designed for ABI <1, and the XServer is running ABI 1, it says the server
> > will run, but there may be funny behaviours. Indeed there are.
>
> Either as you start or in the xorg log (/var/log/Xorg.0.log, normally),
> there should be some indication of what module it is talking about.
> See if equery belongs <module> turns up anything.  That's going to be the
> package you need to remerge.  If nothing is listed, it may be a stale
> version of a file or the slaveryware nvidia drivers you installed manually
> (which I take to mean outside of portage).  Note that installing them
> using the Gentoo package takes care of some stuff that installing them
> manually doesn't, as the manual install isn't setup for Gentoo
> specifically and uses different default paths and the like.  In
> particular, mixing the two, switching between emerged via portage, and
> manually installing the package as you did, is known to cause weird issues,
> as you'll be left with a strange and not very workable missmash of stuff.
> It's certainly  possible to do the same additional things the Gentoo
> ebuild does manually too, but it's the sort of thing that if you are
> asking about it, you are best off just sticking to the Gentoo solution and
> not trying to figure out how to manage it manually.  FWIW, the biggest
> problem has to do with Gentoo's eselect opengl management, which is
> something the nvidia package itself has no way of knowing about and
> therefore fixing, since it's not Gentoo specific as the eselect solution
> is.
>
> Of course, here, I purposefully bought an ATI Radeon 9200 series graphics
> card since it has free drivers.  I couldn't legally run slaveryware even if
> I wanted to, at least where EULAs are or could be considered legal, as I
> simply don't sign over the rights nearly all EULAs demand I sign over,
> viewing it much the same way I'd view an attempt to restrict my other
> basic rights, such as freedom of religion or freedom of expression.  Until
> Nvidia has decent free drivers, they don't get my money, just as current
> ATI doesn't get my money as they no longer provide drivers or specs for
> the community to code its own.  If I were upgrading now, it'd likely be to
> Intel, even tho I've been an AMD user for over a decade now, because
> Intel's integrated chipset video is the best choice for free drivers there
> is right now.  Fortunately, I'll be upgrading my existing dual Opteron to
> dual-cores soon, and won't be upgrading the system for at least two years
> after that.  By the time I /do/ upgrade, the currently beginning trend
> toward standardizing the graphics instruction set to the point it's
> basically an extension of the CPU instruction set should be well under
> way, with comparable openness as well, so freedomware graphics drivers
> making use of it should be getting rather more common.
>
> --
> Duncan - List replies preferred.   No HTML msgs.
> "Every nonfree program has a lord, a master --
> and if you use the program, he is your master."  Richard Stallman

-- 
Frank Castle is dead!
Call me 'The PUNISHER'!

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2006-12-02 19:25 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-02 16:10 [gentoo-amd64] URGENT: No more fonts after xorg changes Clip2
2006-12-02 16:26 ` Dieter Ries
2006-12-02 19:10   ` [gentoo-amd64] " Duncan
2006-12-02 19:22     ` Dieter Ries [this message]
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
  -- strict thread matches above, loose matches on Subject: below --
2006-12-02 23:23 Dmitri Pogosyan
2006-12-03 21:18 Dmitri Pogosyan

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=200612022022.10099.clip2@gmx.de \
    --to=clip2@gmx.de \
    --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