here a hope for me to use XGL in future???
My Mobility X700 works quite well with opensource drivers included with xorg
and AIGLX (never tried XGL, AIGLX is too simple to set up ;) ). Specifically,
I tried it with x11-base/xorg-server-1.1.99.903-r1, media-libs/mesa-6.5.2,
x11-libs/libdrm-2.3.0 an
empt to emerge.
>
> Why are you setting LD_LIBRARY_PATH system-wide to begin with? Don't
> do that.
>
>
Unfortunately, I had to ( and didn't realize the implications. )
In .bashrc :
> export LD_LIBRARY_PATH=$VULKAN_SDK/lib:$LD_LIBRARY_PATH
Required by the Vulkan Loader ( Mesa && Chromium ).
Corbin
On Thursday, August 27, 2015 07:13:58 PM Marc Joliet wrote:
> Am Thu, 27 Aug 2015 17:42:07 +0200
>
> schrieb "J. Roeleveld" :
> > I only had 1 required by set.
> > Which basically got me to remove the llvm use-flag from mesa.
> >
> > That solved the
On 03/04/2017 09:37 AM, Dutch Ingraham wrote:
>
> Michael, thanks for your response. No, I did not do a one-shot; llvm
> was brought in by way of mesa -> gallium; this is llvm's only use on
> this system as far as I know.
>
> Also, 'emerge -ac' shows no pack
lamor]
> # required by @selected
> # required by @world (argument)
> =media-libs/mesa-10.0.4 gbm
>
> So now xf86-video-intel needs glamor. What changed?
> This is a server so it did an rsync during the night, but the ebuild is
> old.
xorg-server gained a glamor USE flag, w
Heiko Baums wrote:
> Am 17.01.2015 um 10:00 schrieb cov...@ccs.covici.com:
> >
> > Thanks -- you just saved me a bunch of time -- I just masked off the
> > eselect-opengl version and hopefully this will not happen to me.
>
> Not really possible since this eselect-opengl version is a dependency
eselect-opengl back to 1.27, mesa and glproto (may
have slightly wrong name), things are back to normal, but what the heck
is happening? I saw nothing in bgo, but we had a thread on here a while
ago, but even that thread didn't say the the server would be
uninstalled.
Any ideas? Are they goi
t, or will it still
> require a complete reinstall?
>
> --
> Regards,
> Mick
On my workstation the day this option came out, "*/* abi_x86_32" in
package.use went reasonably well. x11-libs/cairo-1.12.18-r1 failed, but maybe
that problem is the 32-bit mesa. Going to rebuild i
Before this gets out of hand..
On Fri, 24 Jan 2014 19:44:38 +0100, Silvio Siefke wrote:
>> llvm-3.4 is not hardmasked. It is marked ~x86 which is something very
>> different.
>
> Correct, i mean Clang in version 3.4 is hardmasked. I want install clang
> alone llvm i not n
0(-)]
>>
>>
> dev-python/reportlab-2.6 requires
> dev-python/python-exec:0/0=[python_targets_python2_7(-),-python_single_target_python2_6(-),-python_single_target_python2_7(-)]
>> media-libs/mesa-9.1.6 requires
>> dev-python/python-exec:0/0=[python_targets_python2_7(
s
> classic mode works well.
> By the way, I think i965 is just for HD3000, why does i915 be suggested
> ?
Oh! I suggested i915 thinking that this is the chipset of your Intel video
card - apologies if I got it wrong.
A couple of years ago the gallium driver of mesa was sti
for Qt6:
kde-plasma/kwin lock
dev-qt/*wayland
kde-frameworks/*wayland
kde-plasma/libplasma wayland
media-libs/mesa wayland
x11-base/xwayland libei
There are other problems with multitasking, but I'll report those separately.
--
Regards,
Peter.
On Thursday 5 September 2024 22:29:14 BST Michael wrote:
> At a simple level you can check this file for any obvious problem:
>
> ~/.local/share/sddm/wayland-session.log
>
> Your symptom could be related to software rendering used by the kwin
> compositor, as opposed to
x27;ve switched to the open source AMDGPU drivers + proprietary opencl[0]
driver from the above version for my R9 390x. WIth this setup I can
play most of my games at 2160p and still run BOINC for opencl.
I also have Vulkan (RADV) in mesa- from the FireBurn overlay.
[0] http://www.gearsongallium.com/?p=2960
Alecks
means
> > anything. I've tried the usual trick of unmerging eselect-opengl but
> > that didn't help. A similar update went OK on my main machine.
>
> The mesa ebuild blocks eselect-opengl if the libglvnd USE-flag is set.
> If you want eselect-opengl, remove the li
On 10/22/20 11:17 AM, Ashley Dixon wrote:
On Thu, Oct 22, 2020 at 11:10:41AM +0200, n952162 wrote:
I just found this in Xorg.0.log:
/[ 37.362] (II) vboxvideo: kernel driver found, not loading./
This has been discussed before on this list in 2017. Have you tried the
(admittedly coun
off of a networkless install, so that doesn't really count). However,
when I installed it on an LFS build, on the same machine, I followed
their walkthrough, and it installed fine. Mesa would not install
without
installing Xorg first, and Xorg would not install without knowing where
the
forum pages
I just spent two hours reading were stale and of little help. Anyone
see anything stupid herein:
-- make.conf --
VIDEO_CARDS="nouveau"
-- eselect --
# for i in mesa opengl qtgraphicssystem
> do
> eselect $i list
> done
i915 (Intel 915, 945)
i965 (Intel 965, G/Q3x,
rces on supporting Composite until it's done, so I can't imagine
> that the Open Source project is going to focus on it yet either (having
> less resources and information than ATI themselves).
>
> >
> > And when is X.org going to be able on portage ?
>
> As noted on the
rge -C xorg-server
>
> x11-base/xorg-server
> selected: 1.5.3-r6
> protected: none
> omitted: none
>
>>>> 'Selected' packages are slated for removal.
>>>> 'Protected' and 'omitted' packages will not be removed.
>
>
24 root root 4096 Jun 21 13:07 linux-3.3.8-gentoo
> c2stable ~ #
I have set symlink use flag on gentoo-sources to get symlink
automatically updated (and link is OK).
> 2) Here are make.conf and portage.X package data. Maybe they will
> help. I'm updated to xorg-1.12 & mesa-8 as
Hello!
I installed a new Gentoo system, but I find big problems with ati drivers and
3D acceleration. I have followed the wiki howto but now I receive this error
message
#fglrxinfo
Xlib: extension "XFree86-DRI" missing on display ":0.0".
display: :0.0 screen: 0
OpenGL
merge)
sys-apps/systemd:0= required by (sys-apps/dbus-1.10.12:0/0::gentoo, ebuild
scheduled for merge)
For more information about Blocked Packages, please refer to the following
section of the Gentoo Linux x86 Handbook (architecture is irrelevant):
https://wiki.gentoo.org/wiki/Handbook:X86/W
vdev-2.3.2
=x11-drivers/xf86-video-ati-6.13.0
=x11-drivers/xf86-video-fbdev-0.4.2
=x11-drivers/xf86-input-keyboard-1.4.0
=x11-drivers/xf86-input-mouse-1.5.0
=x11-drivers/xf86-video-vmware-11.0.1
=media-libs/mesa-7.8.1
All of the above are not kernel modul
Hi!
I have compiz-fusion on my Intel X3100 - it run smoothly and very fast.
This is not compiz problem, try to re-emerge mesa and install oryginal
drivers from www.nvidia.com. I have using some time ago compiz-fusion on
nVidia 5500FX and this works normal only on drivers from nvidia webpage
gs->nsid)->r_state ==
> RT_CONSISTENT' failed!
>
> So many packages were upgraded along with xorg-server that I'm not
> sure what to downgrade. Here are the packages that were upgraded at
> the same time. Can anyone suggest any to downgrade? I've already
> downgraded
_initialize (0, args->nsid)->r_state ==
>> RT_CONSISTENT' failed!
>>
>> So many packages were upgraded along with xorg-server that I'm not
>> sure what to downgrade. Here are the packages that were upgraded at
>> the same time. Can anyone suggest any to downgrade? I&#x
.)?
> >
> > In my previous mail I sent the xorg.conf file. Do I have to change
> > something?
>
> Your xorg.conf is fine. Take a look at make.conf. Somewhere you should
> define a variable VIDEO_CARDS than contains the string "intel". If
> not, add it and
On Sat, Jun 27, 2009 at 3:17 PM, Nikos Chantziaras wrote:
> On 06/28/2009 12:20 AM, Mark Knecht wrote:
>>
>> As far as the bug report went it just didn't click for me.
>> Disappointing that after something like 10 months no one has fixed the
>> ebuild.
>
> The latter ebuilds are fixed. They're sti
what should I do in this situation.
>>>>
>>> For a start, I attach my Xorg.conf which works with the same chip.
>>>
>> Thank you very much Philipp, I tried your xorg.conf and modified mine,
>> however,
>> it still does not work, the log is as before...
On Wednesday 14 Dec 2011 17:55:14 pk wrote:
> On 2011-12-14 07:32, Walter Dnes wrote:
> > On Wed, Dec 14, 2011 at 01:12:10AM -0500, Walter Dnes wrote
> >
> >Please ignore the above email. I hit send by mistake. Long story
> >
> > short... the R200 is not su
ays fixes it. Including
> >> drivers and mesa.
> >>
> >> In the old days when xorg was monolithic this never happened, as all the
> >> drivers always got rebuilt anyway. Nowadays with xorg sources being
> >> modular, we have to be a little more aler
up ;) ).
Specifically,
I tried it with x11-base/xorg-server-1.1.99.903-r1, media-libs/mesa-6.5.2,
x11-libs/libdrm-2.3.0 and x11-drivers/xf86-video-ati-6.6.3.
But I still prefer using my i915, even though it's slower and uses shared
memory, since x700 tends to have hiccups on heavy disk IO and uses m
try that)
you may use a different set of drivers of course. See google on these
for more info :)
i tried google. it confused me even more. what is DRI & OpenGL
replacing X window system? what does "mesa" has to do with "DRI" & why
ATI RADEON search opens the l
:
export LD_LIBRARY_PATH=$VULKAN_SDK/lib:$LD_LIBRARY_PATH
Required by the Vulkan Loader ( Mesa && Chromium ).
I think this is what the /etc/ld.so.conf.d/ directory is there for.
Have you tried something like this instead:
echo "$VULKAN_SDK/lib" > /etc/ld.so.conf.d/v
I have been having several issues with libraries on my system and have been
attempting to use revdep-rebuild to resolve them but have been having some
issues.
I have been able to resolve many issues by re-emerging mesa and manualy
listing the packages RR wants to emerge but i have now just Folks
On Thu, 23 Jul 2015, walt wrote:
> Interesting. Maybe you could add some helpful ideas to this existing
> bug report: https://bugs.gentoo.org/show_bug.cgi?id=555186
>
Added what I found upstream, should be enough to get it to work.
> Alpine? I used Alpine a few years ago, but I thought UW had
software is trying to load the swrast GL
driver which is not there.
It would be helpful to see the output of
# eselect opengl list
and
# eselect mesa list
> On 05/05/2017 03:17 PM, Kai Krakow wrote:
> > Am Fri, 5 May 2017 21:12:53 +0200
> > schrieb tu...@posteo.de:
> &g
land since
> some upgrade. XWayland works pretty seamlessly as well, so I'll just stay
> with Wayland for now, but it might be more annoying to use it with other
> DEs/WMs.
> However, I have less screen tearing with fullscreen applications with
> Wayland than I had with X ( with radeon
gt;
>>>
>>> When i have X problems i can resolve i run emerge -av @x11-module-rebuild
>>> xorg-server mesa but its generally an act of desperation after running out
>>> of intelligent options.
>>
>>
>
> Your xorg-server was built for kernel 4.9.3
nly the minutest clue) is broken for you.
Do install the mesa-progs package that Dale found and run glxgears. It
should have almost no effect on CPU use if things are working right.
What does "eselect opengl list" show?
uired for a useful desktop machine
because important packages like Mesa probably depend on something
that in turn uses Python 2.7. For a minimal system without X11 though
you can probably do it.
Even on headless systems it's not completely possible at the moment.
At least spidermonkey ak
t; lspci | grep -i VGA
> 09:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI]
> Picasso (rev c8)
>
> In order to make it work, setting in kernel (under Graphics)
> < > ATI Radeon"
> < M > AMD GPU"
>
> In make.confg:
> VIDE
your message when I replied.
However your solution works for me. I figured that getting wayland
support would have required a lot more rebuilding, or I would have tried
it days ago. I switched on the wayland flag for gtk+ (portage required
it for mesa as well) and I was good to go.
Thanks
n it would be easy to
look into it and tell you that media-libs/mesa is only supported up to
3.11 (in the ebuild anyway). You can try adding 3.12 to the ebuild
yourself, as it seems to be working fine according to
https://bugs.gentoo.org/919912
Regards,
Arve
On Fri, Dec 18, 2015 at 11:07 PM, Tsukasa Mcp_Reznor wrote:
> I have a Bonaire gpu, which has legacy support using the amdgpu kernel
> module. I currently use the Radeon dri module with radeonsi mesa drivers
> and am quite happy. But gentoo being gentoo I thought I'd give the amd
card and I do suffer the slow compositing. I solved
> >>>> it by switching back to the classic Mesa (instead of Gallium).
> >>>
> >>> Thanks Jorge,
> >>>
> >>> I switched to classic too and now it does not crash - however:
> >
oogledrive pdfimport
dev-libs/xmlsec nss
www-client/links -X -jpeg -png -tiff -directfb -fbcon -sdl
media-libs/mesa opencl
dev-qt/qtwebengine -system-icu
net-misc/tigervnc server
media-libs/mesa -vaapi
sys-d
GLX_SGIX_fbconfig
client glx vendor string: ATI
client glx version string: 1.3
client glx extensions:
GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_EXT_import_context,
GLX_ARB_get_proc_address, GLX_ARB_multisample, GLX_ATI_pixel_format_float,
GLX_ATI_render_texture
GLX extensi
t-evdev-2.3.2
=x11-drivers/xf86-video-ati-6.13.0
=x11-drivers/xf86-video-fbdev-0.4.2
=x11-drivers/xf86-input-keyboard-1.4.0
=x11-drivers/xf86-input-mouse-1.5.0
=x11-drivers/xf86-video-vmware-11.0.1
=media-libs/mesa-7.8.1
=app-emulation/vmware-modu
2008/1/30, Mateusz Mierzwinski <[EMAIL PROTECTED]>:
>
> Hi!
>
> I have compiz-fusion on my Intel X3100 - it run smoothly and very fast.
> This is not compiz problem, try to re-emerge mesa and install oryginal
> drivers from www.nvidia.com. I have using some time ago c
Thank you all. I think I'll wait, however, do you think that that is the
problem that cause
glxinfo | grep renderer
direct rendering: Yes
OpenGL renderer string: Software Rasterizer
On my ubuntu machine, I get :
direct rendering: Yes
OpenGL renderer string: Mesa DRI Intel(R) 965Q GEM 200
lts. It really is
in /usr/include/GL/glext.h.
And that file should be symlink created by "eselect opengl" with
source belonging either to media-libs/mesa or nvidia drivers.
If source file include lines are correct, you might want to try
re-emerging nvidia drivers and eselect'ing
se it with GEM in .28/.29 kernels?
I believe GEM technology of the latest kernels should be the focus of
latest releases.
Works pretty good (for IGP) here on both:
r...@coercion:~# glxinfo | g renderer
OpenGL renderer string: Mesa DRI Intel(R) 965GM GEM 20090114 x86/MMX/SSE2
r...@coercion:~#
Hi.
Does anybody know that how to get compiz works fast on this laptop with
xf86-video-intel-2.6.3-r1? So mesa-7.3-r1 xorg-server-1.5.3-r5 and other
have latest stable versions. Kernel 2.6.29-gentoo. Here part of my
xorg.conf:
Section "Device"
Identifi
Another day of probing finally got DRI working on my new machine:
the basic problem was that Mesa needed recompiling with 'i810' enabled.
Naturally (wry smile), this led to another show-stopper:
X starts with no errors in the log, but 'glxgears' & 'glxinfo' cra
27;wobbly windows' and 'Desktop Cube Animation' are disabled.
In E17 which I use daily the compositing works fine, until I select OpenGL as
the rendering engine and then it crashes horribly (won't even boot).
I have set up mesa to use gallium (if that makes any odds). Is the
ng works fine, until I select OpenGL as
the rendering engine and then it crashes horribly (won't even boot).
I have set up mesa to use gallium (if that makes any odds). Is there anything
else I need to configure to improve OpenGL performance (at least to stop it
crashing)?
I have a Nvid
On 06/10/2011 10:08 PM, Dale wrote:
Paul Hartman wrote:
See Pandu's latest message in this thread. Once you enable it like he
showed, it'll work like this:
# eselect
bashcomp boost ctags fontconfig java-vm
locale news pager python usage
visual
binutils --brief editor help kernel
>>> For example
>>>
>>> ajglap lib64 # /bin/pwd
>>> /usr/lib64/debug/usr/lib64
>>> ajglap lib64 # du -s * | sort -n | tail -10
>>> 34020 mesa
>>> 53148 gstreamer-0.10
>>> 155992 icedtea6
>>
On Friday 21 Oct 2011 02:42:48 Vishnupradeep wrote:
> On Thu, Oct 20, 2011 at 7:33 PM, Mick wrote:
> > On Thursday 20 Oct 2011 17:40:13 Vishnupradeep wrote:
> > > Calculating dependencies... done!
> > > [ebuild R] media-libs/mesa-7.11 USE="classic egl gall
mentation section and
> simply re-emerge xorg.
>
> Hope that works ;)
> Robert
So, I found an error in my make.conf and I emerged some xorg program
(mesa for example) again.
With nvidia flag I emerged only mplayer again.
But the problem is yet here. I want to try to update xorg to 7.1 and
Yeah I would say that you're probably out of luck for right now. You might want to try the proprietary drivers with XGL, since the seperate XGL server along with the new mesa provides much of the stuff that's missing in current driver implementations. If that doesn't work, I
direct rendering, and what is most
suspicious, it uses Mesa drivers, which cause Beryl to run at an
absolutely unacceptable performance. Why both servers are not rendered
using fglrx? Have you got any ideas how to do it?
Have you checked your /var/log/Xorg.*.log files? They should reflect
why t
On 11/10/05, James <[EMAIL PROTECTED]> wrote:
> :01:00.0 VGA compatible controller: ATI Technologies Inc Radeon R250 Lf
> [Radeon Mobility 9000 M9] (rev 01)
>
>
> So I need to add MESA to get OpenGL fixed?
No. Why do you think this? You only need xorg (merged with
EPEND="kernel_linux? ( virtual/modutils |
| || ( x11-base/xorg-server virtual/x11 |
| !>=x11-base/xorg-server-1.0.99
| || ( media-libs/mesa virtual/x11 )
| app-admin/eselect-opengl
| kernel_linux? ( !media-video/nvidia-kernel )
| kernel_Free
l be my mother's when I'm done with it)
> is a simple 2D display with 16bit color because she, most likely,
> will not be using anything accellerated
Then simply use the vesa driver. At depth 16 it should work
perfectly. 3D acceleration will not really work on the 800 chip
131005 x11-apps/xvinfo-1.1.1 [for xorg-x11 : otiose]
131005 x11-libs/libXp-1.0.1 [for xorg-x11 : otiose]
131005 x11-libs/libXvMC-1.0.7 [for nvidia-drivers]
131005 x11-misc/makedepend-1.0.4 [for mesa : otiose]
131005 x11-proto/printproto-1.0.5 [for xorg-x11 LO : otiose]
(from my home-ma
r an
> agetty issue?
>
What video hardware are you using, and what driver?
I've had similar issues in the past myself with a variety of causes:
- dodgy versions of mesa
- dodgy versions of video drivers (both nouveau and radeon)
- incorrect kernel settings, usually getting KMS w
stuff (of which I have
only the minutest clue) is broken for you.
Do install the mesa-progs package that Dale found and run glxgears. It
should have almost no effect on CPU use if things are working right.
--
Please don't Cc: me privately on mailing lists and Usenet,
if you also post the follo
you could try:
>
> #eselect opengl list
> Available OpenGL implementations:
> [1] ati *
> [2] xorg-x11
>
> My ati-drivers need the proprietary version of opengl and sometimes this
> setting is wrong after updating the opensource mesa package.
>
> Otherwis
not rendering correctly so
decided not a gtk problem but strange that qt apps where hardly
affected.
Updated mesa to latest version (currently masked) and issue
has gone away.
John
I see, with uname -r, however, that this is the first gentoo system I
have that's a version 5 kernel:
5.4.66-gentoo-x86_64
On 10/22/20 11:33 AM, n952162 wrote:
On 10/22/20 11:17 AM, Ashley Dixon wrote:
On Thu, Oct 22, 2020 at 11:10:41AM +0200, n952162 wrote:
I just found this in Xorg.0.log:
res a higher version of ati-drivers. Unfortunately I
don't have a complete list of ebuilds that belong to X 7.1 but I believe at
least the following do.. You'll have to add them
to /etc/portage/package.mask. Alternatively you might of course consider
trying a higher version of ati-dr
done, so I can't imagine
> > that the Open Source project is going to focus on it yet either (having
> > less resources and information than ATI themselves).
> >
> > >
> > > And when is X.org going to be able on portage ?
> >
> > As noted on t
On 27/05/2014 15:23, Time Lucky wrote:
> My USE in make.conf is
> SE="bindist mmx mmx2 sse sse2 gnome gtk dbus systemd -consolekit -kde
> -qt4 X acpi bash-completion bluetooth cjk unicode ipv6"
At a hunch, I would say your USE for mesa is incorrect, possibly you
have classic
you already have keeps pixbuf
happy
Blockers in that output usually have "!!" annotations at the beginning.
OK, no big deal, except I next ran::
'emerge -uDtv @world'
BANG, it just started compiling as if no blokers?
Calculating dependencies... done!
[ebuild rR
ed
libGL error: reverting to (slow) indirect rendering
display: :0.0 screen: 0
OpenGL vendor string: Mesa project: www.mesa3d.org
OpenGL renderer string: Mesa GLX Indirect
OpenGL version string: 1.4 (1.5 Mesa 6.5.2)
Any ideas on that? We do not want the radeon driver because things like
urce of evil.
Sad but true: there is *NO* reliable 3D driver for recent NVidia
cards. NV's proprietary driver is crap, and they're totally unwilling
to support OSS community in any way. So if you really want GL,
either try software rendering (via mesa) or get a supported card.
(I've g
On 06/28/2009 01:30 AM, Mark Knecht wrote:
On Sat, Jun 27, 2009 at 3:17 PM, Nikos Chantziaras wrote:
On 06/28/2009 12:20 AM, Mark Knecht wrote:
As far as the bug report went it just didn't click for me.
Disappointing that after something like 10 months no one has fixed the
ebuild.
The latter
ut no screen updates. Then if I kill the X server
the entire box locks up (ssh and all) and I have to hard reboot.
I've tried re-merging all my x11-drivers/ and also mesa and xorg-server,
but nothing seems to help. I've tried this on kernel 2.6.30 as well as
2.6.31-rc4. I haven't no
SOLE=m
Also emerge the latest mesa, latest xorg-server, and latest intel
driver.
Also remove all driver options in the xorg.conf file.
If that works for you you might then also enabled XvMC:
Option
Volker Armin Hemmann tu-clausthal.de> writes:
> x11-base/xorg-server
> Installed versions: 1.5.2
> media-libs/mesa
Installed versions: 7.2
>
> x11-base/xorg-x11
> Installed versions: 7.4
> x11-drivers/ati-drivers
> Installed versions: 8.552-r2
Got the
Am 2012-06-10 19:49, schrieb Stefan G. Weichinger:
> I still don't have an idea what I did wrong ...
Solved so far.
Had to add some lines to my package.env as I run the LTO-enabled
gcc-setup suggested by Nikos lately (had to disable lto for the drivers
and mesa).
Re-compiled the
On Sunday 20 March 2011 18:38:00 Mick wrote:
> On Saturday 19 March 2011 23:02:11 Jorge Martínez López wrote:
> > I also have an ATI card and I do suffer the slow compositing. I solved
> > it by switching back to the classic Mesa (instead of Gallium).
>
> Thanks Jorge,
>
Robin Atwood wrote:
AFAIK, all "eselect opengl" does is set up some symlinks so you use NVidia
libraries and not Mesa ones. You might want to poke around and check last
access dates.
HTH
-Robin
I was thinking the same thing. I figure something worked for a while
and then had
(and standard Radeon DRI kernel model) and have
> had no problems whatsoever. It could be a different story for the card
> in your machine (a Rage II by the looks of it).
$ glxinfo | grep render
direct rendering: Yes
OpenGL renderer string: Mesa DRI R200 20040929 AGP 4x x86/MMX/SSE2 TCL
$ u
ll that explains that.
> http://wiki.openchrome.org/tikiwiki/tiki-index.php?page=Compiling+the+source+code
[snip]
> Then simply use the vesa driver. At depth 16 it should work
> perfectly. 3D acceleration will not really work on the 800 chips
> anyway: the Mesa stuff for the unichrom
lve it was by adding
>> Option "DRI" "false"
>> to Xorg.conf. The GPU is i810 here.
>>
>> My understanding is that since i810_dri was removed from mesa a lot of
>> versions ago you need to disable DRI in xorg-server, otherwise the
>>
to move from a no-multilib to a multilib environment, or will it
>> still
>> require a complete reinstall?
>>
>> --
>> Regards,
>> Mick
>
> On my workstation the day this option came out, "*/* abi_x86_32" in
> package.use went reasonab
me important packages probably depend on LLVM? Not sure.
Right now, Python 2.7 is required for a useful desktop machine because
important packages like Mesa probably depend on something that in turn
uses Python 2.7. For a minimal system without X11 though you can
probably do it.
rfaces
(openssl or gnutls, neon or other, sqlite or mysql, openvpn[lzo],
qtgui[exceptions], mesa, freetype, wine), the installation of tools
(utils, examples, tk, perl, python) or extensions (tls-heartbeat,
introspection, X, readline) the defaults usually follow the
upstream default or recommendation
version installed: 340.32
Size of files: 37.696 KiB
Homepage: https://nouveau.freedesktop.org/wiki/VideoAcceleration/
Description: Kernel and mesa firmware for nouveau (video accel and
pgraph)
License: MIT NVIDIA-r2
* x11-drivers/nvidia-drivers
Latest
resence... no
> checking for GL/glx.h... no
> configure: error: Please install GL development package. Alternatively
> you can also configure with --disable-glx.
>
> I simply do not know which package I must install! I would prefer not
> to disable gl support. To which package is this messag
system time to time.
Yesterday I was thinking about AC'97 audio problems because of freezing
when amarok 2 plays audio, but without amarok things are also bad!
What to do? Kernel from intellinuxgraphics page also don't work. I have
Mesa 7.2 downloaded from intellinuxgraphics because of fact
Mar 24 2010 .keep
lrwxrwxrwx 1 root root 18 Jun 21 12:57 linux -> linux-3.3.8-gentoo
drwxr-xr-x 24 root root 4096 Jun 15 09:01 linux-3.2.12-gentoo
drwxr-xr-x 24 root root 4096 Jun 21 13:07 linux-3.3.8-gentoo
c2stable ~ #
2) Here are make.conf and portage.X package data. Maybe they will
he
d, it is just diff of the
> configs,
> > and
> > maybe, some of them could be enabled without causing problems).
> >
> > Now, there are much more 'drm'-related messages in 'dmesg', and also
> X.org
> > uses the drm correctly. The 'glxinfo&#x
macher-misc
media-fonts/freefont-ttf
media-fonts/freefonts
media-fonts/ipamonafont
media-fonts/ja-ipafonts
media-fonts/liberation-fonts
media-fonts/libertine-ttf
media-fonts/ttf-bitstream-vera
media-fonts/wqy-microhei
media-fonts/wqy-zenhei
media-gfx/imagemagick
media-libs/exiftool
media-libs/me
-unicode-release-2.8 -I/usr/include/wx-2.8
-D_FILE_OFFSET_BITS=64 -D_LARGE_FILES -D__WXGTK__ -pthread
-I/home/siefke/Downloads/Amaya11.4.4/Amaya/obj/Mesa/include
-I/usr/include/freetype2 -c ../../thotlib/image/picture.c -o
image/picture.o
../../thotlib/image/picture.c: In Funktion »ThotBool
radeonhd) or their status as gentoo packages but you need proper
kernel support for them to work (drm-module) and matching support in
libdrm, mesa and the X server for 3D to work (DRI). How to setup is
explained here (disclaimer: I don't know how up-to-date this is):
http://www.x.org/wiki/ra
601 - 700 of 1100 matches
Mail list logo
