| 1 |
Joseph Jezak a écrit : |
| 2 |
> |
| 3 |
> If Mackael's suggestion doesn't help, let's try with nvidiafb and a |
| 4 |
> newer kernel: |
| 5 |
|
| 6 |
It did not help, causing a kernel panic that I couldn't resolve. |
| 7 |
> |
| 8 |
> Give 2.6.14 a try (there are some release canidates for vanilla |
| 9 |
> sources), apply this patch: |
| 10 |
> |
| 11 |
> http://ozlabs.org/pipermail/linuxppc-dev/2005-October/019957.html |
| 12 |
> |
| 13 |
> and then try nvidiafb. |
| 14 |
> |
| 15 |
I have downloaded linux-2.6.14-rc3, but was unable to apply the patch: I |
| 16 |
put it within /linux and wrote |
| 17 |
patch --verbose -p1 < Patch_nvidiafb |
| 18 |
Is that not correct? It failed on 5 hunks out of 5. |
| 19 |
|
| 20 |
Nevertheless, I tried to compile the kernel using rivafb, but I got this |
| 21 |
error: |
| 22 |
|
| 23 |
init/built-in.c |
| 24 |
.tmp_vmlinux1 |
| 25 |
localsymbol 0 (or 1 or 2 or 3):discarded in section |
| 26 |
`.exit.data`from\ drivers/built-in.c |
| 27 |
[.tmp_vmlinux1] Error 1 |
| 28 |
|
| 29 |
I don't see to what item in menuconfig this could be related. There are |
| 30 |
no such files as init/built-in or drivers/built-in. |
| 31 |
|
| 32 |
Could you please enlighten me? |
| 33 |
|
| 34 |
Charles |
| 35 |
|
| 36 |
|
| 37 |
|
| 38 |
|
| 39 |
-- |
| 40 |
gentoo-ppc-user@g.o mailing list |
Archives