Gentoo Forums
Gentoo Forums
Gentoo Forums
Quick Search: in
fglrx not suported by kernel
View unanswered posts
View posts from last 24 hours

 
Reply to topic    Gentoo Forums Forum Index Gentoo on AMD64
View previous topic :: View next topic  
Author Message
hedmo
l33t
l33t


Joined: 29 Aug 2009
Posts: 839
Location: halmstad

PostPosted: Sat Dec 05, 2009 6:51 am    Post subject: fglrx not suported by kernel Reply with quote

hello again. yesterday i made a -nuda world .wen i checked the fglrx driver it gave me a error


mybox ~ # emerge ati-drivers

* IMPORTANT: 4 news items need reading for repository 'gentoo'.
* Use eselect news to read news items.

Calculating dependencies... done!

>>> Verifying ebuild manifests

>>> Emerging (1 of 1) x11-drivers/ati-drivers-9.11
* ati-driver-installer-9-11-x86.x86_64.run RMD160 SHA1 SHA256 size ;-) ... [ ok ]
* checking ebuild checksums ;-) ... [ ok ]
* checking auxfile checksums ;-) ... [ ok ]
* checking miscfile checksums ;-) ... [ ok ]
* CPV: x11-drivers/ati-drivers-9.11
* REPO: gentoo
* USE: amd64 elibc_glibc kernel_linux modules multilib userland_GNU
* Determining the location of the kernel source code
* Found kernel source directory:
* /usr/src/linux
* Could not find a Makefile in the kernel source directory.
* Please ensure that /usr/src/linux points to a complete set of Linux sources
* Unable to calculate Linux Kernel version for build, attempting to use running version
* Found kernel object directory:
* /lib/modules/2.6.32-gentoo/build
* Found sources for kernel version:
* 2.6.32-gentoo
* Kernels newer then 2.6.31 are not supported by this driver
* ERROR: x11-drivers/ati-drivers-9.11 failed:
* Downgrade your kernel
*
* Call stack:
* ebuild.sh, line 55: Called pkg_setup
* ati-drivers-9.11.ebuild, line 196: Called _check_kernel_config
* ati-drivers-9.11.ebuild, line 107: Called die
* The specific snippet of code:
* die "Downgrade your kernel"
*
* If you need support, post the output of 'emerge --info =x11-drivers/ati-drivers-9.11',
* the complete build log and the output of 'emerge -pqv =x11-drivers/ati-drivers-9.11'.
* The complete build log is located at '/var/tmp/portage/x11-drivers/ati-drivers-9.11/temp/build.log'.
* The ebuild environment file is located at '/var/tmp/portage/x11-drivers/ati-drivers-9.11/temp/die.env'.
* S: '/var/tmp/portage/x11-drivers/ati-drivers-9.11/work'

>>> Failed to emerge x11-drivers/ati-drivers-9.11, Log file:

>>> '/var/tmp/portage/x11-drivers/ati-drivers-9.11/temp/build.log'

* Messages for package x11-drivers/ati-drivers-9.11:

* Could not find a Makefile in the kernel source directory.
* Please ensure that /usr/src/linux points to a complete set of Linux sources
* Unable to calculate Linux Kernel version for build, attempting to use running version
* Kernels newer then 2.6.31 are not supported by this driver
* ERROR: x11-drivers/ati-drivers-9.11 failed:
* Downgrade your kernel
*
* Call stack:
* ebuild.sh, line 55: Called pkg_setup
* ati-drivers-9.11.ebuild, line 196: Called _check_kernel_config
* ati-drivers-9.11.ebuild, line 107: Called die
* The specific snippet of code:
* die "Downgrade your kernel"
*
* If you need support, post the output of 'emerge --info =x11-drivers/ati-drivers-9.11',
* the complete build log and the output of 'emerge -pqv =x11-drivers/ati-drivers-9.11'.
* The complete build log is located at '/var/tmp/portage/x11-drivers/ati-drivers-9.11/temp/build.log'.
* The ebuild environment file is located at '/var/tmp/portage/x11-drivers/ati-drivers-9.11/temp/die.env'.
* S: '/var/tmp/portage/x11-drivers/ati-drivers-9.11/work'

* IMPORTANT: 4 news items need reading for repository 'gentoo'.
* Use eselect news to read news items.

mybox ~ #


is there a way to continue with the updated kernel or do i realy need to downgrade?

in either way i need help with it

regards hedmo
Back to top
View user's profile Send private message
eccerr0r
Advocate
Advocate


Joined: 01 Jul 2004
Posts: 3950
Location: USA

PostPosted: Sat Dec 05, 2009 7:42 am    Post subject: Reply with quote

Yes, you have to downgrade until ATI (or some really dedicated hacker) fixes their(ATI's) binary blob. That's the biggest drawback of using fglrx or any closed source binary kernel driver. If you can, use the opensource driver which won't have this limitation.
_________________
Intel Core i7 2700K@ 4.1GHz/HD3000 graphics/8GB DDR3/180GB SSD
What am I supposed to be advocating?
Back to top
View user's profile Send private message
hedmo
l33t
l33t


Joined: 29 Aug 2009
Posts: 839
Location: halmstad

PostPosted: Sat Dec 05, 2009 8:27 am    Post subject: Reply with quote

i swiched to mm-sources because i dont know howto downgrade and got this


* ERROR: x11-drivers/ati-drivers-9.11 failed:
* Unable to emake HOSTCC=x86_64-pc-linux-gnu-gcc CROSS_COMPILE=x86_64-pc-linux-gnu- LDFLAGS= GCC_VER_MAJ=4 KVER=2.6.28-rc2-mm1 KDIR=/usr/src/linux kmod_build
*
* Call stack:
* ebuild.sh, line 55: Called src_compile
* environment, line 3700: Called linux-mod_src_compile
* environment, line 2878: Called die
* The specific snippet of code:
* eval "emake HOSTCC=\"$(tc-getBUILD_CC)\" CROSS_COMPILE=${CHOST}- LDFLAGS=\"$(get_abi_LDFLAGS)\" ${BUILD_FIXES} ${BUILD_PARAMS} ${BUILD_TARGETS} " || die "Unable to emake HOSTCC="$(tc-getBUILD_CC)" CROSS_COMPILE=${CHOST}- LDFLAGS="$(get_abi_LDFLAGS)" ${BUILD_FIXES} ${BUILD_PARAMS} ${BUILD_TARGETS}";
*
* If you need support, post the output of 'emerge --info =x11-drivers/ati-drivers-9.11',
* the complete build log and the output of 'emerge -pqv =x11-drivers/ati-drivers-9.11'.
* The complete build log is located at '/var/tmp/portage/x11-drivers/ati-drivers-9.11/temp/build.log'.
* The ebuild environment file is located at '/var/tmp/portage/x11-drivers/ati-drivers-9.11/temp/environment'.
* S: '/var/tmp/portage/x11-drivers/ati-drivers-9.11/work'

* IMPORTANT: 4 news items need reading for repository 'gentoo'.
* Use eselect news to read news items.

mybox / #
Back to top
View user's profile Send private message
hedmo
l33t
l33t


Joined: 29 Aug 2009
Posts: 839
Location: halmstad

PostPosted: Sat Dec 05, 2009 10:31 am    Post subject: Reply with quote

i have bin trying to get back to an older kernel but wont let me config


mybox linux # eselect kernel list
Available kernel symlink targets:
[1] linux-2.6.31-gentoo-r2 *
mybox linux # ls -l /usr/src/linux
lrwxrwxrwx 1 root root 22 Dec 5 10:43 /usr/src/linux -> linux-2.6.31-gentoo-r2
mybox linux # make menuconfig
make: *** No rule to make target `menuconfig'. Stop.
mybox linux #

and wy does portage tell me that i got a newer kernel then linux-2.6.31-gentoo-r2

mybox linux # emerge --newuse --update --deep --ask world

* IMPORTANT: 4 news items need reading for repository 'gentoo'.
* Use eselect news to read news items.


These are the packages that would be merged, in order:

Calculating dependencies... done!
[ebuild NS ] sys-kernel/gentoo-sources-2.6.32 [2.6.31-r3] USE="symlink -build"
[ebuild U ] sys-apps/shadow-4.1.4.2-r1 [4.1.4.2]
[ebuild UD] x11-misc/cairo-dock-1.6.3.1 [2.0.8.2] USE="-debug%"
[ebuild U ] app-portage/layman-1.2.4 [1.2.3]
[ebuild UD] x11-misc/cairo-dock-plugins-1.6.3.1 [2.0.8.2] USE="-debug%"

!!! One or more updates have been skipped due to a dependency conflict:

x11-misc/cairo-dock:0

('ebuild', '/', 'x11-misc/cairo-dock-2.0.8.2', 'merge') conflicts with
~x11-misc/cairo-dock-1.6.3.1 required by ('installed', '/', 'x11-misc/cairo-dock-themes-1.6.3.1', 'nomerge')


!!! The following update(s) have been skipped due to unsatisfied dependencies
!!! triggered by backtracking:

x11-misc/cairo-dock-plugins:0

Would you like to merge these packages? [Yes/No] n

Quitting.


* IMPORTANT: 4 news items need reading for repository 'gentoo'.
* Use eselect news to read news items.

mybox linux #
Back to top
View user's profile Send private message
kernelOfTruth
Watchman
Watchman


Joined: 20 Dec 2005
Posts: 5701
Location: Vienna, Austria; Germany; hello world :)

PostPosted: Sun Dec 06, 2009 10:48 pm    Post subject: Reply with quote

eccerr0r wrote:
Yes, you have to downgrade until ATI (or some really dedicated hacker) fixes their(ATI's) binary blob. That's the biggest drawback of using fglrx or any closed source binary kernel driver. If you can, use the opensource driver which won't have this limitation.


nope,

there's already a way to "fix" it:

Quote:
# Kernel 2.6.32 fix
grep -q signal.h common/lib/modules/fglrx/build_mod/kcl_io.c || perl -pi -e 's|(#include <linux/poll.h>\n)|\1#include <linux/signal.h>\n|' common/lib/modules/fglrx/build_mod/kcl_io.c


you can thank Kano for that fix :)
_________________
https://github.com/kernelOfTruth/ZFS-for-SystemRescueCD
2.6.37.2_plus_v1: BFS, CFS,THP,compaction, zcache or TOI
Hardcore Linux user since 2004 :D
Back to top
View user's profile Send private message
eccerr0r
Advocate
Advocate


Joined: 01 Jul 2004
Posts: 3950
Location: USA

PostPosted: Mon Dec 07, 2009 3:55 pm    Post subject: Reply with quote

kernelOfTruth wrote:
eccerr0r wrote:
Yes, you have to downgrade until ATI (or some really dedicated hacker) fixes their(ATI's) binary blob. That's the biggest drawback of using fglrx or any closed source binary kernel driver. If you can, use the opensource driver which won't have this limitation.


nope,

there's already a way to "fix" it:

Quote:
# Kernel 2.6.32 fix
grep -q signal.h common/lib/modules/fglrx/build_mod/kcl_io.c || perl -pi -e 's|(#include <linux/poll.h>\n)|\1#include <linux/signal.h>\n|' common/lib/modules/fglrx/build_mod/kcl_io.c


you can thank Kano for that fix :)


There you have it, as I said, some really dedicated hacker did his job where a Gentoo developer did not...
Gosh... Debian?
_________________
Intel Core i7 2700K@ 4.1GHz/HD3000 graphics/8GB DDR3/180GB SSD
What am I supposed to be advocating?
Back to top
View user's profile Send private message
slackline
Veteran
Veteran


Joined: 01 Apr 2005
Posts: 1324
Location: /uk/sheffield

PostPosted: Mon Dec 07, 2009 5:24 pm    Post subject: Reply with quote

eccerr0r wrote:


There you have it, as I said, some really dedicated hacker did his job where a Gentoo developer did not...
Gosh... Debian?


How facetious! If someone provided a hack it matters not what distribution they are affiliated with, after all the kernel is independent of distribution!

Perhaps the Gentoo developers who look after the kernel already have a backlog of bugs/nuances that they were working their way through, or they had a personal crisis that took priority, these things happen.

Petty digs like the above do nothing to engender support from anyone and don't belong in support forums.

Just my tuppence anyway.

Regards

slack
_________________
"Science is what we understand well enough to explain to a computer.  Art is everything else we do." - Donald Knuth
Back to top
View user's profile Send private message
eccerr0r
Advocate
Advocate


Joined: 01 Jul 2004
Posts: 3950
Location: USA

PostPosted: Mon Dec 07, 2009 5:50 pm    Post subject: Reply with quote

slack---line wrote:

How facetious! If someone provided a hack it matters not what distribution they are affiliated with, after all the kernel is independent of distribution!


No, the problem is Gentoo knew it was a problem and actually spent the effort putting a workaround "can't use 2.6.32" but someone else actually found the problem and actually *fixed* it "CAN use 2.6.32 with patch". I see it all too often: the difference between "Upstream fix" versus "user patch"... Apparently this "patch" that was presented was actually a fairly simple fix, some definition was changed. If the build errored (or at least "WARNING: 2.6.32 not supported" instead of masked by bombing ahead of time with "we're dead, there's no way to use" I'm sure a lot more people would spot the problem and a fix presented earlier. At least the triage needs to be done better -- semantic or syntax errors versus BAPI change...

But the original statement is true, regression testing happens more readily with the opensource driver and should be used wherever possible. The root of the problem is not Gentoo, it's rather ATI and it has been the biggest problem forever. Even NVidia closed source drivers don't bomb so often.
_________________
Intel Core i7 2700K@ 4.1GHz/HD3000 graphics/8GB DDR3/180GB SSD
What am I supposed to be advocating?
Back to top
View user's profile Send private message
slackline
Veteran
Veteran


Joined: 01 Apr 2005
Posts: 1324
Location: /uk/sheffield

PostPosted: Mon Dec 07, 2009 8:41 pm    Post subject: Reply with quote

eccerr0r wrote:

No, the problem is Gentoo knew it was a problem and actually spent the effort putting a workaround "can't use 2.6.32" but someone else actually found the problem and actually *fixed* it "CAN use 2.6.32 with patch". I see it all too often: the difference between "Upstream fix" versus "user patch"... Apparently this "patch" that was presented was actually a fairly simple fix, some definition was changed. If the build errored (or at least "WARNING: 2.6.32 not supported" instead of masked by bombing ahead of time with "we're dead, there's no way to use" I'm sure a lot more people would spot the problem and a fix presented earlier. At least the triage needs to be done better -- semantic or syntax errors versus BAPI change...


As I said, maybe they labelled it as "can't use 2.6.32" as they had other more important priorities, whether they were to do with other aspects of the kernel or personal. Someone else might have had more free time and therefore could devote the time required to realise that it could be patched. Devs put a lot of hard work in for essentially nothing and we out in userland only ever voice opinions when things don't work so it must be quite demoralising.


eccerr0r wrote:
But the original statement is true, regression testing happens more readily with the opensource driver and should be used wherever possible. The root of the problem is not Gentoo, it's rather ATI and it has been the biggest problem forever. Even NVidia closed source drivers don't bomb so often.


No disagreement on this front.
_________________
"Science is what we understand well enough to explain to a computer.  Art is everything else we do." - Donald Knuth
Back to top
View user's profile Send private message
kernelOfTruth
Watchman
Watchman


Joined: 20 Dec 2005
Posts: 5701
Location: Vienna, Austria; Germany; hello world :)

PostPosted: Tue Dec 08, 2009 12:46 am    Post subject: Reply with quote

slack---line wrote:


As I said, maybe they labelled it as "can't use 2.6.32" as they had other more important priorities, whether they were to do with other aspects of the kernel or personal. Someone else might have had more free time and therefore could devote the time required to realise that it could be patched. Devs put a lot of hard work in for essentially nothing and we out in userland only ever voice opinions when things don't work so it must be quite demoralising.



nope - they have been doing this since several kernel releases (2.6.29/2.6.28 ?) so no "excuse" not to take a look and come up with some experimental patch

*runs and hides* ;)

(I'm not in the position to create a fix for those drivers)
_________________
https://github.com/kernelOfTruth/ZFS-for-SystemRescueCD
2.6.37.2_plus_v1: BFS, CFS,THP,compaction, zcache or TOI
Hardcore Linux user since 2004 :D
Back to top
View user's profile Send private message
eccerr0r
Advocate
Advocate


Joined: 01 Jul 2004
Posts: 3950
Location: USA

PostPosted: Tue Dec 08, 2009 10:36 pm    Post subject: Reply with quote

Honestly I felt mislead by the error-mask and that's why I'm somewhat upset. Many of us users may not have the time or resources to be a developer, but we sure could help them when we spot certain things that may help or even fix issues. However with broad error-masks like what was used turned me off from even looking for a solution.

Gentoo and other source based distributions have the upper hand as the users are decoupled from having to deal with dependencies - thanks to the developers - but we still can watch for build errors. Simple things, even for binary driver wrappers could potentially be spotted and fixed by the community well before upstream (in this case, ATI) releases one - This would be beneficial to many more people. We're all "developers" in sense as we're at least compiling the code and seeing the errors as another distribution developer (or manual install user) would see.

Honestly the 2.6.28/2.6.29 patches were really obscure IIRC. Those kinds of errors I don't think I could come up with a solution in a reasonable amount of time... but someone did... because they tried to install it.

#@&%* ATI FGLRX!
_________________
Intel Core i7 2700K@ 4.1GHz/HD3000 graphics/8GB DDR3/180GB SSD
What am I supposed to be advocating?
Back to top
View user's profile Send private message
hedmo
l33t
l33t


Joined: 29 Aug 2009
Posts: 839
Location: halmstad

PostPosted: Tue Jan 05, 2010 9:40 am    Post subject: thanks a 1000000 Reply with quote

even if i use this (fix) i cant continuing update my system because the driver isnt fixed.the latest times i updated i have bin getting more and more
odd message and now i cant --depclean

mybox ~ # emerge --newuse --update --deep --ask world

* IMPORTANT: 4 news items need reading for repository 'gentoo'.
* Use eselect news to read news items.


These are the packages that would be merged, in order:

Calculating dependencies... done!
[ebuild U ] sys-libs/timezone-data-2009u [2009t]
[ebuild U ] dev-libs/libffi-3.0.9 [3.0.8]
[ebuild U ] sys-devel/patch-2.6.1 [2.5.9-r1] USE="-test%"
[ebuild U ] net-misc/dhcpcd-5.1.4 [5.1.3-r1]
[ebuild U ] sys-apps/net-tools-1.60_p20100101055920 [1.60_p20090728014017-r1]
[ebuild U ] app-emulation/emul-linux-x86-baselibs-20091231 [20091226]
[ebuild U ] media-gfx/sane-backends-1.0.20-r3 [1.0.20-r2]
[ebuild U ] sys-libs/readline-6.1 [6.0_p4]
[ebuild R ] dev-db/sqlite-3.6.21 USE="fts3*"
[ebuild U ] sys-devel/gettext-0.17-r1 [0.17]
[ebuild R ] sys-apps/coreutils-8.2 USE="unicode%*"
[ebuild U ] sys-process/psmisc-22.10 [22.7]
[ebuild NS ] sys-kernel/gentoo-sources-2.6.31-r9 [2.6.31-r3, 2.6.31-r6, 2.6.31-r7, 2.6.31-r8] USE="symlink -build"
[ebuild U ] app-admin/eselect-1.2.9 [1.2.8]
[ebuild U ] app-admin/eselect-python-20091230 [20090824]
[ebuild U ] dev-python/numpy-1.4.0 [1.3.0-r2]
[ebuild U ] app-emulation/emul-linux-x86-xlibs-20091231 [20091226]
[ebuild U ] app-emulation/emul-linux-x86-gtklibs-20091231 [20091226]
[ebuild U ] app-portage/layman-1.2.5 [1.2.4]
[ebuild R ] app-crypt/pinentry-0.7.6 USE="(-qt3%*)"
[ebuild N ] kde-base/akonadi-4.3.4 USE="semantic-desktop (-aqua) -debug (-kdeenablefinal) (-kdeprefix)"
[ebuild U ] app-emulation/emul-linux-x86-soundlibs-20091231 [20091226]
[ebuild U ] app-emulation/emul-linux-x86-medialibs-20091231 [20091226]
[ebuild U ] app-emulation/emul-linux-x86-sdl-20091231 [20091226]

!!! The following update has been skipped due to unsatisfied dependencies:

x11-misc/cairo-dock-themes:0

!!! All ebuilds that could satisfy "~x11-misc/cairo-dock-1.6.3.1" have been masked.
!!! One of the following masked packages is required to complete your request:
- x11-misc/cairo-dock-1.6.3.1 (masked by: package.mask)

(dependency required by "x11-misc/cairo-dock-themes-1.6.3.1" [ebuild])

For more information, see the MASKED PACKAGES section in the emerge
man page or refer to the Gentoo Handbook.



!!! The following update has been skipped due to unsatisfied dependencies:

media-libs/mesa:0

!!! All ebuilds that could satisfy ">=x11-proto/xextproto-7.0.99.1" have been masked.
!!! One of the following masked packages is required to complete your request:
- x11-proto/xextproto-7.1.1 (masked by: package.mask)

(dependency required by "media-libs/mesa-7.7-r1" [ebuild])

For more information, see the MASKED PACKAGES section in the emerge
man page or refer to the Gentoo Handbook.



!!! Problems have been detected with your world file
!!! Please run emaint --check world


!!! Ebuilds for the following packages are either all
!!! masked or don't exist:
x11-misc/cairo-dock-themes

!!! The following installed packages are masked:
- kde-base/kdelibs-3.5.10-r6 (masked by: package.mask)
/usr/portage/profiles/package.mask:
# Samuli Suominen <ssuominen@gentoo.org> (31 Dec 2009)
# Doesn't compile anymore with Autoconf >= 2.64, wv2 >= 0.4.0,
# several open security bugs, ...
#
# Replaced by app-office/koffice-meta-2.1.0
#
# See bugs 274566, 274918, 279027, 279482, 283429, 285018, 294676,
# 287276, 292791, ...
#
# kamikaze, hearts, six, slibo, kvisualboyadvance, xpertmud,
# kfreeflight and boson will be removed with kdelibs-3.
#
# Masked for removal in 30 days
#

- x11-misc/cairo-dock-plugins-2.0.8.2 (masked by: package.mask)
- x11-misc/cairo-dock-2.0.8.2 (masked by: package.mask)
For more information, see the MASKED PACKAGES section in the emerge
man page or refer to the Gentoo Handbook.


Would you like to merge these packages? [Yes/No]

mybox ~ # revdep-rebuild
* Configuring search environment for revdep-rebuild

* Checking reverse dependencies
* Packages containing binaries and libraries broken by a package update
* will be emerged.

* Collecting system binaries and libraries
* Generated new 1_files.rr
* Collecting complete LD_LIBRARY_PATH
* Generated new 2_ldpath.rr
* Checking dynamic linking consistency
[ 100% ]

* Dynamic linking on your system is consistent... All done.
mybox ~ #


mybox ~ # emerge --depclean

* Depclean may break link level dependencies. Thus, it is
* recommended to use a tool such as `revdep-rebuild` (from
* app-portage/gentoolkit) in order to detect such breakage.
*
* Always study the list of packages to be cleaned for any obvious
* mistakes. Packages that are part of the world set will always
* be kept. They can be manually added to this set with
* `emerge --noreplace <atom>`. Packages that are listed in
* package.provided (see portage(5)) will be removed by
* depclean, even if they are part of the world set.
*
* As a safety measure, depclean will not remove any packages
* unless *all* required dependencies have been resolved. As a
* consequence, it is often necessary to run `emerge --update
* --newuse --deep world` prior to depclean.

Calculating dependencies... done!
* Dependencies could not be completely resolved due to
* the following required packages not being installed:
*
* ~x11-misc/cairo-dock-1.6.3.1 pulled in by:
* x11-misc/cairo-dock-themes-1.6.3.1
*
* Have you forgotten to run `emerge --update --newuse --deep world` prior
* to depclean? It may be necessary to manually uninstall packages that no longer
* exist in the portage tree since it may not be possible to satisfy their
* dependencies. Also, be aware of the --with-bdeps option that is documented
* in `man emerge`.

* IMPORTANT: 4 news items need reading for repository 'gentoo'.
* Use eselect news to read news items.

mybox ~ #


this hapend when i fixed my xorg with help off another post
(my package.mask)

=x11-base/xorg-server-1.6.9
>=x11-libs/libX11-1.3.2
>=x11-libs/libXinerama-1.1
>=x11-proto/xextproto-7.1.1
>=x11-libs/libXext-1.1.1
>=x11-libs/libXi-1.3
>=x11-proto/xcmiscproto-1.2.0
>=x11-proto/xf86bigfontproto-1.2.0
>=x11-proto/bigreqsproto-1.1.0
>=x11-proto/xineramaproto-1.2
>=x11-proto/xextproto-7.1.1
>=x11-proto/fixesproto-4.1.1
>=x11-proto/inputproto-2.0
>=x11-libs/libXinerama-1.1
>=x11-proto/recordproto-1.14
>=x11-libs/libXtst-1.1.0
>=x11-proto/scrnsaverproto-1.2.0
>=x11-libs/libXScrnSaver-1.2.0
>=x11-proto/xf86vidmodeproto-2.3
>=x11-libs/libXxf86vm-1.1.0
>=x11-apps/xinput-1.5.0
-app-cdr/kiso
>=sys-kernel/gentoo-sources-2.6.32
>=x11-misc/cairo-dock-1.6.3.1
>=x11-misc/cairo-dock-plugins-1.6.3.1

...........

with your experience how long do i have wait till the driver is god to go?
Back to top
View user's profile Send private message
slackline
Veteran
Veteran


Joined: 01 Apr 2005
Posts: 1324
Location: /uk/sheffield

PostPosted: Tue Jan 12, 2010 11:27 am    Post subject: Reply with quote

Have you tried doing as suggested and running 'emaint --check world"?

Have you unmasked any packages in /etc/portage/package.keywords or /etc/portage/package.unmask?

slack
_________________
"Science is what we understand well enough to explain to a computer.  Art is everything else we do." - Donald Knuth
Back to top
View user's profile Send private message
Display posts from previous:   
Reply to topic    Gentoo Forums Forum Index Gentoo on AMD64 All times are GMT
Page 1 of 1

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum