Re: [nouveau] gentoo ebuild masked by a missing keyword

2007-01-23 Thread Alexy Khrabrov
Well, after solving Gentoo-specific masking issues (thanks to folks
who replied!), libdrm pulled by nouveau fails to build due to the
build's own issues -- is that Gentoo ebuild of nouveau maintained?
The references to the ebuilds are on the wiki, hence I hope it's fair
to ask.  I pulled it with layman -a nouveau.

Cheers,
Alexy

-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT  business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV
--
___
Dri-devel mailing list
Dri-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dri-devel


[nouveau] gentoo ebuild masked by a missing keyword

2007-01-21 Thread Alexy Khrabrov
Am trying to emerge xf86-video-nouveau, emerge tells me it's masked by
a missing keyword.  Googling reports it's a dreaded message, can be
solved by adding the package to /etc/portage/package.keywords as

x11-drivers/xf86-video-nouveau *

-- here I deduce from examples, with * or ~* trailing.  Doesn't
work still.  How do I unmask it properly?

Cheers,
Alexy

-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT  business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV
--
___
Dri-devel mailing list
Dri-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dri-devel


Re: [nouveau] a million little pieces affecting nvidia drivers

2007-01-15 Thread Alexy Khrabrov
Philipp, Mark --

Thanks for the concise and extremely useful explanation!  This is
worthy of being on the front page of a wiki.

Cheers,
Alexy

On 1/15/07, Michel Dänzer [EMAIL PROTECTED] wrote:
 On Sun, 2007-01-14 at 00:22 +0100, Philipp Klaus Krause wrote:
 
  GLX canbe used over a network, but currently the free drivers don't support
  hardware-acceleration in this case.

 That's no longer true since the introduction of AIGLX in X.org 7.1.


 --
 Earthling Michel Dänzer   |  http://tungstengraphics.com
 Libre software enthusiast |  Debian, X and DRI developer



-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT  business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV
--
___
Dri-devel mailing list
Dri-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dri-devel


Re: Any developers need castoff cards?

2007-01-12 Thread Alexy Khrabrov
And I'll cover the said shipping if said, or other, developer(s)
answer(s) my general questions sent here earlier, about interaction of
various parts of video-related toolchain!  :)

Cheers,
Alexy

On 1/12/07, Alex Jackson [EMAIL PROTECTED] wrote:
 Could any DRI developers find a use for either of the following video cards?

 AGP Radeon 9200SE
 PCI GeForce MX4000

 I might have one or both of these cards to spare soon (if only one, it'll be
 the Radeon) and I can part with them for the cost of shipping if I know
 they'll go to good use.

 --AWJ--

 _
 Buy, Load, Play. The new Sympatico / MSN Music Store works seamlessly with
 Windows Media Player. Just Click PLAY.
 http://musicstore.sympatico.msn.ca/content/viewer.aspx?cid=SMS_Sept192006


 -
 Take Surveys. Earn Cash. Influence the Future of IT
 Join SourceForge.net's Techsay panel and you'll get the chance to share your
 opinions on IT  business topics through brief surveys - and earn cash
 http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV
 --
 ___
 Dri-devel mailing list
 Dri-devel@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/dri-devel


-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT  business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV
--
___
Dri-devel mailing list
Dri-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dri-devel


[nouveau] drm/nouveau locks on suse 10.2 with nvidia GeForce 2 Go

2007-01-10 Thread Alexy Khrabrov

Greetings -- compiled drm and nouveau yesterday from git and tried to
run X -- hangs at the loading stage.  Xorg.0.log attached.  I've
followed the following checks:

-- kernel compiled with DRM disabled
-- binary nvidia module not loaded

The drm installed libdrm.so in /usr/local/lib, I copied them to
/usr/lib; similarly, copied nouveau_drv.so from /usr/local/lib/xorg to
/usr/lib/xorg.  Are there other pieces I'm missing?

Cheers,
Alexy


Xorg.0.log-nouveau-2.bz2
Description: BZip2 compressed data
-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT  business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV--
___
Dri-devel mailing list
Dri-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dri-devel


[nouveau] a million little pieces affecting nvidia drivers

2007-01-10 Thread Alexy Khrabrov
When trying to make nvidia drivers sleep, and then later get nouveau
to work, I got hopelessly confused about various pieces of video
hardware/software and their mutual entanglements.  I'd much
appreciates if one of you esteemed video sages takes a few steps
towards deconfusion.

The TLAs floating in this soup are

AGP
DRI
DRM

Obviously, we need a new DRM driver for nouveau as it says to compile
it.  This installs library libdrm.so -- who uses it?  We're talking of
DRM, while X refers to DRI?

Then there's a whole framebuffer dimension.  Various reports suggest
to use vesafb-tng driver instead of the standard vesafb.  Thus, it
interacts with nvidia drivers -- how?  I see Xorg.0.log referring to
the framebuffer...  And we also have nvidiafb driver.  Can/should it
be used with the free nv/nouveau Xorg driver?

In addition, there's the vbetool utility and Option VBERestore --
how do those interact with framebuffer/nouveau?

so here's the rest of the list:

agp drivers
glx drivers/libs
libdrm.so
--
vesafb
vesafb-tng
nvidiafb
--
vbetool

Which of these work together must be taken care of for running and
accelerating nv/nouveau properly?

Cheers,
Alexy

-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT  business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV
--
___
Dri-devel mailing list
Dri-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dri-devel


Re: [nouveau] drm/nouveau locks on suse 10.2 with nvidia GeForce 2 Go

2007-01-10 Thread Alexy Khrabrov
[forwarding to the list as well]

Here it is, below.  I manually modprobe agpgart to make drm.ko happy.
Do I have to recompile something else -- it complains about drm?  The
screen goes blank and doesn't come back, but ctrl-alt-del still
reboots.

Cheers,
Alexy
...
Jan  9 22:41:18 orator kernel: Linux agpgart interface v0.101 (c) Dave Jones
Jan  9 22:41:26 orator kernel: drm: disagrees about version of symbol
struct_module
Jan  9 22:45:21 orator kernel: [drm] Initialized drm 1.1.0 20060810
Jan  9 22:45:27 orator kernel: ACPI: PCI Interrupt :00:05.0[A] -
Link [LNKB] - GSI 11 (level, low) - IR
Q 11
Jan  9 22:45:27 orator kernel: [drm] Initialized nouveau 0.0.2
20060213 on minor 0
Jan  9 22:45:42 orator kernel: [drm] regs mapped ok at 0xe900
Jan  9 22:45:42 orator kernel: [drm] 16 MB of video ram detected
Jan  9 22:45:42 orator kernel: [drm] regs mapped ok at 0xe900
Jan  9 22:45:42 orator kernel: [drm] 16 MB of video ram detected
Jan  9 22:45:48 orator kernel: [drm] regs mapped ok at 0xe900
Jan  9 22:45:48 orator kernel: [drm] 16 MB of video ram detected
Jan  9 22:45:48 orator kernel: [drm] regs mapped ok at 0xe900
Jan  9 22:45:48 orator kernel: [drm] 16 MB of video ram detected
Jan  9 22:45:49 orator kernel: [drm] regs mapped ok at 0xe900
Jan  9 22:45:49 orator kernel: [drm] 16 MB of video ram detected
Jan  9 22:46:31 orator shutdown[7699]: shutting down for system reboot


 On 1/10/07, Stephane Marchesin [EMAIL PROTECTED] wrote:
  Alexy Khrabrov wrote:
   Greetings -- compiled drm and nouveau yesterday from git and tried to
   run X -- hangs at the loading stage.  Xorg.0.log attached.  I've
   followed the following checks:
  
   -- kernel compiled with DRM disabled
   -- binary nvidia module not loaded
  
   The drm installed libdrm.so in /usr/local/lib, I copied them to
   /usr/lib; similarly, copied nouveau_drv.so from /usr/local/lib/xorg to
   /usr/lib/xorg.  Are there other pieces I'm missing?
  
  Do you have a kernel log as well ?
 
  Stephane

-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT  business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV
--
___
Dri-devel mailing list
Dri-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dri-devel


[nouveau] compilation warnings, logs

2007-01-10 Thread Alexy Khrabrov

Additional info on my non-working nouveau:

-- followed wiki howto -- pulled git repos for drm and nouveau only
-- did pull/rebuild just now, after autogen.sh also did ./configure
--prefix=/usr, so that libdrm.so and nouveau_drv.so are deposited into
the expected locations right away

However, when compiling in xf86-video-nouveau, there's a lot of
warnings (see make-nouveau output in the attached tarball).  They're
mostly about undeclared CARD32 -- perhaps that's the problem?

I also included the last complete kernel log and Xorg log in the tar.

Cheers,
Alexy


nouveau-debug-20007-01-10-1.tar.bz2
Description: BZip2 compressed data
-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT  business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV--
___
Dri-devel mailing list
Dri-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dri-devel


accelerating horizontal scroll on nvidia -- nouveau

2007-01-08 Thread Alexy Khrabrov
Greetings -- I'm trying to accelerate horizontal scroll on nvidia
GeForce 2 Go with free nv driver(s), and wonder whether nouveau is the
solution -- with its 2D acceleration.

The rationale is this: I am installing and configuring Linux on a
tablet PC, Compaq TC1000.  I've managed most everything to work.  One
of the best things you can do with a tablet is to read the web in
vertical mode.  The native nvidia drivers support randr and scroll
fast in the rotated mode.
However, binary nvidia drivers can't hibernate, which is a non-starter
for my mobile usage.

The free nv driver supports randr as well, but landscape scrolling is
slow.  While trying to make binary nvidia drivers to fall asleep, I've
disabled all AGP, and now wonder what's the right way to enable it
back for the free nv driver.  Also -- does vesafb have anything to do
with it?  I enabled vesafb-tng instead of the standard vesafb as it's
more conducive of hibernation.  There's also an nvidiafb module, and I
wonder how that interacts with X, if at all.

But since nouveau says it focuses on 2D, I tried to configure it --
getting git clone just now -- and got this:

-- first autogen.sh run -- complains about AC_DISABLE_STATIC and something else;
-- second time:

[EMAIL PROTECTED]:/s/c/git/nouveau/mesa/drm ./autogen.sh
autoreconf: Entering directory `.'
autoreconf: configure.ac: not using Gettext
autoreconf: running: aclocal
autoreconf: configure.ac: tracing
autoreconf: configure.ac: not using Libtool
autoreconf: running: /usr/bin/autoconf
autoreconf: running: /usr/bin/autoheader
autoreconf: running: automake --add-missing --copy --no-force
libdrm/Makefile.am:21: Libtool library used but `LIBTOOL' is undefined
libdrm/Makefile.am:21:
libdrm/Makefile.am:21: The usual way to define `LIBTOOL' is to add
`AC_PROG_LIBTOOL'
libdrm/Makefile.am:21: to `configure.ac' and run `aclocal' and `autoconf' again.
autoreconf: automake failed with exit status: 1

In fact I see AC_PROG_LIBTOOL is defined in configure.ac.  I have
automake 1.9.6.  Is drm version-dependent, or I need some more mesa
components or something else?

Cheers,
Alexy

-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT  business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV
--
___
Dri-devel mailing list
Dri-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dri-devel