1 |
2006/1/4, Daniel Gryniewicz <dang@g.o>: |
2 |
> |
3 |
> On Wed, 2006-01-04 at 19:17 +0000, Miguel Filipe wrote: |
4 |
> > Hi ppl, |
5 |
> > |
6 |
> > I cannot emerge nvidia-kernel because it thinks: |
7 |
> > "Your kernel was configured to include rivafb support!" |
8 |
> > this is what emerge complains about: |
9 |
> > ------------ |
10 |
> > Your kernel was configured to include rivafb support! |
11 |
> > |
12 |
> > The rivafb driver conflicts with the NVIDIA driver, please |
13 |
> > reconfigure your kernel and *disable* rivafb support, then |
14 |
> > try installing the NVIDIA kernel module again. |
15 |
> > |
16 |
> > *** Failed rivafb sanity check. Bailing out! *** |
17 |
> > |
18 |
> > make[1]: *** [rivafb-sanity-check] Error 1 |
19 |
> > make[1]: *** Waiting for unfinished jobs.... |
20 |
> > Your kernel was configured to include rivafb support as |
21 |
> > a loadable kernel module. |
22 |
> > |
23 |
> > The rivafb driver conflicts with the NVIDIA driver; the |
24 |
> > NVIDIA kernel module will still be built and installed, |
25 |
> > but be aware that the NVIDIA driver will not be able to |
26 |
> > function properly if the rivafb module is loaded! |
27 |
> > |
28 |
> > *** Failed rivafb module sanity check, but continuing! *** |
29 |
> > |
30 |
> > make: *** [module] Error 2 |
31 |
> > ------------- |
32 |
> > |
33 |
> > but it is not. |
34 |
> > |
35 |
> > feynman ~ # uname -r |
36 |
> > 2.6.14-gentoo-r5 |
37 |
> > feynman ~ # zgrep -i riva /proc/config.gz |
38 |
> > CONFIG_IPV6_PRIVACY=y |
39 |
> > # CONFIG_FB_RIVA is not set |
40 |
> > feynman ~ # zgrep -i riva /usr/src/linux/.config |
41 |
> > CONFIG_IPV6_PRIVACY=y |
42 |
> > # CONFIG_FB_RIVA is not set |
43 |
> > feynman ~ # zgrep -i riva /usr/src/linux-2.6.14-gentoo-r5/.config |
44 |
> > CONFIG_IPV6_PRIVACY=y |
45 |
> > # CONFIG_FB_RIVA is not set |
46 |
> > |
47 |
> > I think its thinking IPV6_PRIVACY which contains the string RIVA, is |
48 |
> FB_RIVA. |
49 |
> > |
50 |
> > best regards, |
51 |
> > |
52 |
> > btw, this happens with the stable and the unstable nvidia-kernel |
53 |
> ebuilds. |
54 |
> > anyone knows how I can "modify" its checks? I cannot find anything |
55 |
> > related to riva checks on the ebuild itself. |
56 |
> > |
57 |
> |
58 |
> You need to check the kernel linked by /usr/src/linux, not the running |
59 |
> kernel. That's where ebuilds that install kernel modules look. |
60 |
> |
61 |
> -- |
62 |
> Daniel Gryniewicz |
63 |
> Gentoo AMD64 Team / Gentoo Gnome Herd / AMD64 Operational AT Lead |
64 |
> |
65 |
> |
66 |
> -----BEGIN PGP SIGNATURE----- |
67 |
> Version: GnuPG v1.4.2-ecc0.1.6 (GNU/Linux) |
68 |
> |
69 |
> iD8DBQBDvDPPomPajV0RnrERAqX1AJ4iTwAGVv1CM8b0oD6DW8WahIAclACfc0HT |
70 |
> ahQ3OTvsd3c8OWxGseh3ZOU= |
71 |
> =BGaE |
72 |
> -----END PGP SIGNATURE----- |
73 |
> |
74 |
> |
75 |
> Yes. That's probably the reason. Nvidia-kernel looks to where |
76 |
/usr/src/linux is linked, may be your current kernel or not. You should |
77 |
install nvidia-kernel for every different kernel you want to use. |