From: maxim wexler <blissfix@yahoo.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] ati -- dreaded "xf86-ENOMEM" error
Date: Fri, 26 Aug 2005 10:34:41 -0700 (PDT) [thread overview]
Message-ID: <20050826173441.55412.qmail@web31707.mail.mud.yahoo.com> (raw)
In-Reply-To: <5bdc1c8b05082521596ce8dd7@mail.gmail.com>
--- Mark Knecht <markknecht@gmail.com> wrote:
> On 8/25/05, maxim wexler <blissfix@yahoo.com> wrote:
> >
> >
> > --- Holly Bostick <motub@planet.nl> wrote:
> > >
> > > What motherboard do you have?
> >
> > Asus K8N-E Deluxe skt 754 w/nVidia chipset
> >
>
> <hehe!!> We're in this one together buddy! I managed
> to buy one of
> those motherboards today from NewEgg. I'll be
> building the machine
> next week.
Well, at least X works. What video card will you be
using?
>
> Here's my guess. If you look at 2.6.12-gentoo-r9 the
> NVidia AGP
> support clearly says Nforce/Nforce2. My suspicion is
> that the AGP
> chipset support for this chipset (NForce4) isn't in
Whoa! NForce4?! What about 2, 3? I'm looking at the
Asus User Guide, p xi, in the box, Chipset: NVIDIA
nForce3 250Gb
> the kernel yet and
> that we need to find a patch, or possibly look at a
> kernel.org kernel
> for like 2.6.13/14/15, etc. and find one that does.
>
> Assuming that there isn't a patch then we get in
> line with the kernel
> developers and work to get one done. I had this
> problem with my laptop
> when I first got it and couldn't get DMA for the ATI
> cipset. It took
> between 30 and 60 days as I remember.
This is all new territory for me.
>
> Anyway, I bought one today so I'm in the life raft
> with ya!
>
> Cheers,
> Mark
>
> --
> gentoo-user@gentoo.org mailing list
>
UPDATE: did a sync and was able to emerge the new
ati-drivers. This time fglrx.ko *was* generated and is
loaded at boot. But now I get
$startx
(WW) fglrx: No matching Device section for instance
(BusID PCI:1:0:1) found # faq says ignore
(EE) fglrx(0): [agp] unable to acquire AGP, error
"xf86_ENODEV"
(EE) fglrx(0): cannot init AGP
Could not init font path element
/usr/share/fonts/local/, removing from list!
The fix according to the faq: I need to clean up the
sources make oldconfig etc, re-emerge the drivers.
WRONG :(
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
--
gentoo-user@gentoo.org mailing list
next prev parent reply other threads:[~2005-08-26 17:48 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-23 20:00 [gentoo-user] ati -- dreaded "xf86-ENOMEM" error maxim wexler
2005-08-23 20:24 ` Mark Knecht
2005-08-25 3:48 ` Ryan Sims
2005-08-25 21:53 ` maxim wexler
2005-08-26 0:47 ` Holly Bostick
2005-08-26 3:41 ` maxim wexler
2005-08-26 4:59 ` Mark Knecht
2005-08-26 5:11 ` [gentoo-user] Portage Won't Start now after update - help Paul Hoy
2005-08-26 10:05 ` [gentoo-user] ati -- dreaded "xf86-ENOMEM" error Holly Bostick
2005-08-26 15:22 ` Mark Knecht
2005-08-26 18:30 ` maxim wexler
2005-08-26 15:09 ` Mark Knecht
2005-08-26 18:38 ` maxim wexler
2005-08-26 19:12 ` Mark Knecht
2005-08-26 17:34 ` maxim wexler [this message]
2005-08-26 19:11 ` Mark Knecht
2005-08-27 4:28 ` maxim wexler
2005-08-26 4:13 ` maxim wexler
2005-08-25 22:23 ` maxim wexler
2005-08-25 23:15 ` Holly Bostick
2005-08-26 0:29 ` Mark Knecht
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=20050826173441.55412.qmail@web31707.mail.mud.yahoo.com \
--to=blissfix@yahoo.com \
--cc=gentoo-user@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