| 1 |
walt wrote: |
| 2 |
> Affirmative, and thereby hangs yet another woeful tale. I've been |
| 3 |
> running the gentoo-sources-3.14.xx series forever because I wearied of |
| 4 |
> spending so many hours debugging unstable kernels. This morning I |
| 5 |
> decided to take a giant leap forward all the way to 3.18.19 (BTW |
| 6 |
> 3.18.20 is already on kernel.org) because, surely, I wouldn't need to |
| 7 |
> debug a kernel as old as that, right? Wrong. Linus and friends have |
| 8 |
> been marking lots of existing kernel symbols with the |
| 9 |
> SYMBOL_EXPORT_GNU macro, which was designed to block the loading of |
| 10 |
> any kernel module not explicitly licensed as GNU software. (see output |
| 11 |
> of modinfo) x11-drivers/ati-drivers installs a proprietary binary blob |
| 12 |
> (as does nvidia-drivers) so the linker refused even to link the kernel |
| 13 |
> module into a .ko file, nevermind the kernel actually loading the |
| 14 |
> module at runtime. The remedy for ati-drivers is well-hidden in a |
| 15 |
> comment in a gentoo bug report that I found at oh-dark-hundred hours |
| 16 |
> this morning. Only two hours later I got the module installed and |
| 17 |
> loaded :) But yes, kernel 3.18.19 still has my same keyboard halting |
| 18 |
> problem, so I'm back to 3.14.50 until the ati-drivers package is |
| 19 |
> patched. I'm sure gentoo-sources-3.18.20 will be available almost |
| 20 |
> immediately and I'm not going through that hell again. |
| 21 |
|
| 22 |
|
| 23 |
Interesting info. I haven't been able to get new kernels to work |
| 24 |
either. I wonder if this is why. o_O |
| 25 |
|
| 26 |
Dale |
| 27 |
|
| 28 |
:-) :-) |
Archives