| 1 |
This affects suspend2-sources users (and maybe others) who have been |
| 2 |
using the ipw2200 ebuild in portage rather than the in-kernel ipw2200 |
| 3 |
support. It confused me pretty badly yesterday, so I thought I'd post |
| 4 |
in case it can help someone. |
| 5 |
|
| 6 |
The ipw2200 ebuild is now masked, pending removal from portage (see |
| 7 |
current package.mask). So it's probably time to migrate to using the |
| 8 |
kernel's ipw2200 support. A problem arises because (AIUI) installing |
| 9 |
the ipw2200 ebuild removes what's needed in suspend2-sources |
| 10 |
to compile the kernel with its own ipw2200 support. Or maybe the |
| 11 |
removal was done manually; ISTR having to remove some files after |
| 12 |
being prompted by the ebuild. Anyway, trying to compile the kernel |
| 13 |
after configuring for ipw2200 support results in failure. |
| 14 |
|
| 15 |
The fix is to unmerge ipw2200 and ieee80211, then emerge |
| 16 |
suspend2-sources again before reconfiguring and recompiling. |
| 17 |
|
| 18 |
Thanks to Phil for filing a bug (invalid) and to Alon Bar-Lev for |
| 19 |
pointing toward the cause of the problem. |
| 20 |
<http://bugs.gentoo.org/show_bug.cgi?id=162856> |
| 21 |
|
| 22 |
-- |
| 23 |
gentoo-user@g.o mailing list |
Archives