Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 26 Mar 2009 11:35:26 -0500
From:      Robert Noland <rnoland@FreeBSD.org>
To:        Andrew Bradford <andrew@bradfordtg.com>
Cc:        freebsd-x11@freebsd.org
Subject:   Re: Xorg nv 0 videoram and insufficient memory for mode
Message-ID:  <1238085326.1792.27.camel@balrog.2hip.net>
In-Reply-To: <20090326150051.GK21707@bugaboo.gv.shawcable.net>
References:  <20090326042350.GF21707@bugaboo.gv.shawcable.net> <1238049392.1828.111.camel@balrog.2hip.net> <20090326150051.GK21707@bugaboo.gv.shawcable.net>

next in thread | previous in thread | raw e-mail | index | archive | help

--=-v4AGPmxZzWCyEHjfmZVh
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable

On Thu, 2009-03-26 at 08:00 -0700, Andrew Bradford wrote:
> On Thu Mar 26 2009 01:36AM, Robert Noland wrote:
> > On Wed, 2009-03-25 at 21:23 -0700, Andrew Bradford wrote:
> > > Hi all,
> > >=20
> > > I'd like some help with an issue I'm having with Xorg on FreeBSD 7.1 =
amd64.  X seems to ignore all videoram on my secondary video card.  I have =
3G of system RAM in the machine, could it be related to memory barriers?
> > >=20
> > > The machine specs are as follows: (onboard) GeForce 6150, PCI-E GeFor=
ce 6600.  I am using the "nv" driver.
> > >=20
> > > Up until last week, the system was working happily. Both screens work=
ing great without issue.  Upon reboot the PCI-E video card does not get pro=
perly detected by X.  In the Xorg log file, is "NV(0): VideoRAM: 0 kBytes" =
(followed by "insufficient memory for mode" for all video modes).
> > >=20
> > > The sudden appearance after a reboot may have simply been a driver th=
at had been built but not yet loaded.  I had been upgrading the system the =
previous week.  I tested out the hardware with some live cds to make sure t=
he card isn't dying.
> > >=20
> > > I've looked high and low on the web, and the only posting I can see t=
hat's relevant is this one:
> > > http://archive.netbsd.se/?ml=3Dxorg&a=3D2008-02&t=3D6547682
> > > from last year.  He appears to have the same problem as I do.  The on=
ly response points to a pciaccess mail thread, indicating that HW access in=
 Xorg was being reworked.
> > >=20
> > > The thread is from last year, has the issue not been resolved yet?  A=
re there any workarounds?  The only other driver I can use would be this No=
uveau one I heard about on freebsd-x11, but that would involve another syst=
em upgrade, and it is currently marked as broken.  The Vesa driver doesn't =
work on my cards, and nvidia won't support amd64...
> > >=20
> > > I tried rebuilding the nv driver and xorg-server with various version=
s from ports, with the same issue.  I just finished rebuilding with ports f=
rom Feb 1 -- same thing.
> > >=20
> > > I've attached Xorg.0.log and xorg.conf.new.  The config file was gene=
rated using X -configure (and cleaned because nv detected all pci devices i=
n the system).
> >=20
> > The issue is in fact the switch to libpciaccess, along with a lot of
> > changes to Xserver.  The issue is due to legacy vga handling.  The issu=
e
> > is being discussed a bit more lately, but no resolution is at hand.
> > Most modern cards have a way to deal with this, but it isn't a
> > generalized solution.  So, for right now, multiple cards generally don'=
t
> > work, for linux, solaris or us...
>=20
> Oh dear, I was afraid of that.
>=20
> There's probably not enough information to pinpoint a version, but would =
downgrading to Xserver 1.4.2 (or an even older version) work?  Or, alternat=
ely, is there an ETA on the switch to libpciaccess?
>=20
> Do you know in which version the libpciaccess changes were introduced?

The switch to libpciaccess occurred with server 1.5.3.  1.4.2 still uses
the old method.  The issue is starting to bubble up, but it isn't really
on anyone's priority list right now that I am aware of.  I've given some
thought to the proper way to address it, but it hasn't gone beyond
random musings yet.

robert.

> Thanks for your help,
> Andrew
>=20
>=20
> >=20
> > robert.
> >=20
> > > Help!
> > >=20
> > > Thanks!
> > > Andrew
> > >=20
> > > _______________________________________________
> > > 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=
"
> > --=20
> > Robert Noland <rnoland@FreeBSD.org>
> > FreeBSD
>=20
>=20
--=20
Robert Noland <rnoland@FreeBSD.org>
FreeBSD

--=-v4AGPmxZzWCyEHjfmZVh
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: This is a digitally signed message part

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.11 (FreeBSD)

iEYEABECAAYFAknLrs4ACgkQM4TrQ4qfROOmNACeKgEUaQU1WufuhUMGxnL3zVXc
/vIAnRIfGYftWkNqHDAMZVrQELTmZsLn
=Rb9p
-----END PGP SIGNATURE-----

--=-v4AGPmxZzWCyEHjfmZVh--




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1238085326.1792.27.camel>