On Wed, May 1, 2013 at 12:52 AM, [email protected]
<[email protected]> wrote:
> On Tue, Apr 30, 2013 at 10:46 PM, Jiri Slachta <[email protected]> wrote:
>> Dne 30.4.2013 22:08, [email protected] napsal(a):
>>> On Tue, Apr 30, 2013 at 9:36 PM, [email protected]
>>> <[email protected]> wrote:
>>>> I had missed package with engines ;)
>>>> Now I got images built correctly and installed on CF card.
>>>>
>>>> Can you or somebody else check out what is the issue?
>>>>
>>>> Please connect to:
>>>> ssh [email protected] -p 22001 password is "openwrt"
>>>
>>> I see few connections, did anybody get debug logs?
>>> _______________________________________________
>>> openwrt-devel mailing list
>>> [email protected]
>>> https://lists.openwrt.org/mailman/listinfo/openwrt-devel
>>>
>>
>> Hey,
>>
>> the first thing I see is:
>>
>> [    8.341688] padlock_aes: Unknown symbol blkcipher_walk_done (err 0)
>> [    8.360643] padlock_aes: Unknown symbol blkcipher_walk_virt (err 0)
>> [    8.379562] padlock_aes: Unknown symbol crypto_blkcipher_type (err 0)
>>
>> Could you try to enable package kmod-crypto-manager that enables 
>> CONFIG_CRYPTO_BLKCIPHER in kernel config and loads specific kernel modules? 
>> I actually do not know, where the problem is, but the "uknown symbol" error 
>> messages should disappear.
>>
>> Jiri
>
> New fimware is now on CF card with kmod-crypto-manager, I still see
> same issue, but please check it yourself.

What do strace logs show? How long ago were engines removed from
openssl? Did upstream change some things that introduces bugs in
openwrt?
_______________________________________________
openwrt-devel mailing list
[email protected]
https://lists.openwrt.org/mailman/listinfo/openwrt-devel

Reply via email to