now that i've got the kernel installed and working, i need to get some
modules installed.
I'm making the kernel with make-kpkg and want to do a make-kpkg
modules_install but am getting this error:
-----------------------------------------------------
root@bssapp1:~/linux-2.6.dev.31.y# time make-kpkg modules_image
exec debian/rules DEBIAN_REVISION=2.6.31.12-10.00.Custom modules_image
for module in ; do \
if test -d $module; then \
(cd $module; \
if ./debian/rules KVERS="2.6.31.12"
KSRC="/home/jwilliams/linux-2.6.dev.31.y" \
KMAINT="Unknown Kernel Package
Maintainer" KEMAIL="unknown@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx"
\
KPKG_DEST_DIR="/home/jwilliams/linux-2.6.dev.31.y/.." \
KPKG_MAINTAINER="Unknown Kernel Package
Maintainer" \
KPKG_EXTRAV_ARG="" \
ARCH="i386" \
KDREV="2.6.31.12-10.00.Custom"
kdist_image; then \
echo "Module $module processed fine"; \
else \
echo "Module $module failed."; \
if [ "X" != "X" ]; then \
echo "Perhaps $module does not understand --rootcmd?"; \
echo "If you see messages that indicate that it is not"; \
echo "in fact being built as root, please file a bug "; \
echo "against $module."; \
fi; \
echo "Hit return to Continue"; \
read ans; \
fi; \
); \
else \
echo "Module $module does not exist"; \
echo "Hit return to Continue?"; \
fi; \
done
real 0m6.557s
user 0m4.050s
sys 0m2.810s
root@bssapp1:~/linux-2.6.dev.31.y#
-----------------------------------------------------
does anyone have a hint or tip for me?!
regs
Jason
On 21 August 2010 13:07, Ryszard <ryszard99@xxxxxxxxx> wrote:
> I've managed to compile and get bens kernel installed. the problem i
> had (for future reference) was the physical media not being
> recognised. adding rootdelay=130 to the kernel options seemed to have
> fixed that.
>
> On 11 August 2010 03:06, Ben Greear <greearb@xxxxxxxxxxxxxxx> wrote:
>> On 08/10/2010 09:54 AM, Luis R. Rodriguez wrote:
>>>
>>> On Sun, Aug 1, 2010 at 3:21 PM, Ben Greear<greearb@xxxxxxxxxxxxxxx>
>>> wrote:
>>
>>>> You would not believe how hard it is to keep up with the wireless tree.
>>>> Last time,
>>>> by the time we had something stable, upstream had changed too much to
>>>> merge.
>>>
>>> This is why you should not do your development outside of
>>> wireless-testing. If you are doing development on a stable kernel tree
>>> then you will likely run into huge issues. You should do development
>>> on wireless-testing.git, always rebase when John has a new update, and
>>> break your changes out into a small changes as possible. If you follow
>>> these basic rules I believe you will likely have better luck with
>>> keeping your code up to date.
>>
>> That sounds nice, but at that time I was carrying a lot of other patches
>> needed to make my test environment work. Fortunately, .35 pretty much
>> works out of the box, so I can develop on pristine upstream kernels now.
>>
>> Thanks,
>> Ben
>>
>> --
>> Ben Greear <greearb@xxxxxxxxxxxxxxx>
>> Candela Technologies Inc http://www.candelatech.com
>>
>>
>
--
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
