[gentoo-user] info for ipw2200 users
This affects suspend2-sources users (and maybe others) who have been using the ipw2200 ebuild in portage rather than the in-kernel ipw2200 support. It confused me pretty badly yesterday, so I thought I'd post in case it can help someone. The ipw2200 ebuild is now masked, pending removal from portage (see current package.mask). So it's probably time to migrate to using the kernel's ipw2200 support. A problem arises because (AIUI) installing the ipw2200 ebuild removes what's needed in suspend2-sources to compile the kernel with its own ipw2200 support. Or maybe the removal was done manually; ISTR having to remove some files after being prompted by the ebuild. Anyway, trying to compile the kernel after configuring for ipw2200 support results in failure. The fix is to unmerge ipw2200 and ieee80211, then emerge suspend2-sources again before reconfiguring and recompiling. Thanks to Phil for filing a bug (invalid) and to Alon Bar-Lev for pointing toward the cause of the problem. http://bugs.gentoo.org/show_bug.cgi?id=162856 -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] info for ipw2200 users
On Saturday 20 January 2007 19:58, »Q« wrote:
This affects suspend2-sources users (and maybe others) who have been
using the ipw2200 ebuild in portage rather than the in-kernel ipw2200
support. It confused me pretty badly yesterday, so I thought I'd post
in case it can help someone.
The ipw2200 ebuild is now masked, pending removal from portage (see
current package.mask). So it's probably time to migrate to using the
kernel's ipw2200 support. A problem arises because (AIUI) installing
the ipw2200 ebuild removes what's needed in suspend2-sources
to compile the kernel with its own ipw2200 support. Or maybe the
removal was done manually; ISTR having to remove some files after
being prompted by the ebuild. Anyway, trying to compile the kernel
after configuring for ipw2200 support results in failure.
The fix is to unmerge ipw2200 and ieee80211, then emerge
suspend2-sources again before reconfiguring and recompiling.
Thanks to Phil for filing a bug (invalid) and to Alon Bar-Lev for
pointing toward the cause of the problem.
http://bugs.gentoo.org/show_bug.cgi?id=162856
This issue is specific to neither suspend2-sources nor ipw2200. You hit the
same issue with any other kernel if you emerge ieee80211. From the ieee80211
ebuild:
eerror Your kernel source contains an incompatible version of the
eerror ieee80211 subsystem, which needs to be removed before
eerror ${P} can be installed. This can be accomplished by running:
eerror
eerror # /bin/sh ${FILESDIR}/remove-old ${KV_DIR}
if [ ${KV_DIR} != ${KV_OUT_DIR} ]; then
eerror # /bin/sh ${FILESDIR}/remove-old ${KV_OUT_DIR}
fi
eerror
eerror Please note that this will make it impossible to use some of the
eerror in-kernel IEEE 802.11 wireless LAN drivers (eg. orinoco).
You ran the script and you were warned. The ieee80211 ebuild is depended upon
by four external, wireless net drivers: ipw{2100,2200,3945} and rt2x00.
--
Bo Andresen
pgpwlgpEg5ag2.pgp
Description: PGP signature
Re: [gentoo-user] info for ipw2200 users
On Saturday 20 January 2007 15:23, Bo Ørsted Andresen wrote:
snip
This issue is specific to neither suspend2-sources nor ipw2200. You hit the
same issue with any other kernel if you emerge ieee80211. From the
ieee80211 ebuild:
eerror Your kernel source contains an incompatible version of the
eerror ieee80211 subsystem, which needs to be removed before
eerror ${P} can be installed. This can be accomplished by running:
eerror
eerror # /bin/sh ${FILESDIR}/remove-old ${KV_DIR}
if [ ${KV_DIR} != ${KV_OUT_DIR} ]; then
eerror # /bin/sh ${FILESDIR}/remove-old ${KV_OUT_DIR}
fi
eerror
eerror Please note that this will make it impossible to use some of
the eerror in-kernel IEEE 802.11 wireless LAN drivers (eg. orinoco).
You ran the script and you were warned. The ieee80211 ebuild is depended
upon by four external, wireless net drivers: ipw{2100,2200,3945} and
rt2x00.
Having just gotten my ipw2100 to be working (kind of), I want to comment on
this. This is just stupid. There's nothing wrong with having that source in
the kernel if it's not configured is there? The solution used here seems
just wrong to me.
David
--
gentoo-user@gentoo.org mailing list
Re: [gentoo-user] info for ipw2200 users
On Saturday 20 January 2007 23:06, David Corbin wrote:
You ran the script and you were warned. The ieee80211 ebuild is depended
upon by four external, wireless net drivers: ipw{2100,2200,3945} and
rt2x00.
Having just gotten my ipw2100 to be working (kind of), I want to comment on
this. This is just stupid. There's nothing wrong with having that source
in the kernel if it's not configured is there? The solution used here
seems just wrong to me.
Oh, I'm sure the devs would be interested if you have a better solution.. I
haven't bothered to even attempt to find out whether or why this is
necessary. Fortunately we as ipw2100 users don't have to care any longer
because the external ipw2x00 kernel modules are no longer required. Just use
the in-kernel modules and you won't have to deal with this ever again...
That's what this thread is all about.
Also just a side note to the OP. Just because ipw2200 has been masked doesn't
mean you have to rebuild a working kernel that allready has the external
modules working. You could just unmerge ipw2200 and ieee80211. /lib/modules
are under forced CONFIG_PROTECT so the modules won't be removed from there
during the unmerge. Next time you upgrade your kernel anyway you just have to
make sure they get enabled as modules in the kernel.
--
Bo Andresen
pgpEKbiX6GgiK.pgp
Description: PGP signature
