2007-09-26 01:13:07 "ffmpeg:582: can't map '/usr/lib/libavcodec.so.51'"
Sajith T S (INDIA)
Message: 44540 Anyone seen this before?
As soon as the network interface is up (say, on running dhcpcd), I get this error when trying to run ffmpeg:
root:~> ffmpeg
ffmpeg:582: can't map '/usr/lib/libavcodec.so.51'
ffmpeg:582: can't map '/usr/lib/libavcodec.so.51'
ffmpeg: can't load library 'libavcodec.so.51'
vlc also reports the same error.
QuoteReplyEditDelete
2007-09-26 01:57:25 Re: "ffmpeg:582: can't map '/usr/lib/libavcodec.so.51'"
Mike Frysinger (UNITED STATES)
Message: 44542 it means you dont have enough free L1 to load the libraries
QuoteReplyEditDelete
2007-09-26 04:44:43 Re: "ffmpeg:582: can't map '/usr/lib/libavcodec.so.51'"
Robin Getz (UNITED STATES)
Message: 44554 If you are using a BF537, turn the ethernet packets to use L3, (not L1).
-Robin
QuoteReplyEditDelete
2007-09-26 05:16:10 Re: "ffmpeg:582: can't map '/usr/lib/libavcodec.so.51'"
Sajith T S (INDIA)
Message: 44555 Thank you. I was wondering how to get this to work...
QuoteReplyEditDelete
2007-09-26 05:22:13 Re: "ffmpeg:582: can't map '/usr/lib/libavcodec.so.51'"
Sajith T S (INDIA)
Message: 44556 Whoa, that worked. Thank you! (I hope you indeed meant unset CONFIG_BFIN_MAC_USE_L1.)
QuoteReplyEditDelete
2007-09-26 05:57:33 Re: "ffmpeg:582: can't map '/usr/lib/libavcodec.so.51'"
Robin Getz (UNITED STATES)
Message: 44562 That is the one...
-Robin
QuoteReplyEditDelete
2010-11-22 10:54:41 Re: "ffmpeg:582: can't map '/usr/lib/libavcodec.so.51'"
aditya joshi (INDIA)
Message: 96092
hey i am not able to get rid of this problem.
I am using uClinux latest distribution.
./ffserver:564: L1 allocation failed
./ffserver:582: can't map '/lib/libavcodec.so.51'
./ffserver:564: L1 allocation failed
./ffserver:582: can't map '/lib/libavcodec.so.51'
./ffserver: can't load library 'libavcodec.so.51'
can you tell in detail about solution.
Regards
QuoteReplyEditDelete
2010-11-22 13:35:17 Re: "ffmpeg:582: can't map '/usr/lib/libavcodec.so.51'"
Mike Frysinger (UNITED STATES)
Message: 96094
same answer -- free up L1 memory. read /proc/sram to see how much is allocated and look at the kernel's System.map to see what is using it.