[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Loading emdebian file system on ARM target from USB stick



On Tue, 2009-04-28 at 09:34 -0300, Amandeep Bhullar wrote:
> Hi
> 
> > Setting up debian-archive-keyring (2009.01.31em1) ...
> > gpg: symbol lookup error: /lib/libreadline.so.5: undefined symbol:
> PC
> > gpg: symbol lookup error: /lib/libreadline.so.5: undefined symbol:
> PC
> > gpg: symbol lookup error: /lib/libreadline.so.5: undefined symbol:
> PC
> > dpkg: error processing debian-archive-keyring (--configure):
> > subprocess post-installation script returned error exit status 127
> 
> > Does libreadline exist at that path in the rootfs? What version?
> 
> Yes, libreadline.so.5 exists under /lib. Will it affect the working.
> 
> Another question, My arm board booted into emdebian filesystem,
> but /sbin appears as a file. I cant use the commands like ifconfig.
> Any suggestions?
> 
> Thanks.
> Aman.
Hmm, I haven't had this problem. Unfortunately I have no Idea what could
have caused that :-(

> 
> 
> 
> On Thu, Apr 23, 2009 at 5:12 PM, Neil Williams <codehelp@debian.org>
> wrote:
>         On Thu, 23 Apr 2009 11:13:17 -0300
>         Amandeep Bhullar <arm.debian@gmail.com> wrote:
>         
>         > My ARM board AT91SAM9263-EK is running linux that I came
>         with the
>         > board as linux demo. It is running from NAND flash and has a
>         jffs2
>         > filesystem (not NFS). It is probably running an Angstrom
>         based
>         > filesystem. You are right, the NAND flash is partitioned in
>         different
>         > partitions for kernel, rootfs etc. So what I have done is (I
>         dont
>         > know if I did the right thing), copied the emdebian-arm.tgz
>         on a USB
>         > stick, mounted it on the board running linux and gave
>         command tar
>         > -xzpf emdebian-arm.tgz and ./emsecondstage in the folder
>         Emdebian I
>         > created. Here is what happened:
>         
>         
>         That sounds OK so far.
>         
>         > Setting up libc6 (2.7-18em1) ...
>         > Alignment trap: iconvconfig (2310) PC=0x00009960
>         Instr=0xe5952000
>         > Address=0x0005
>         > 875e FSR 0x013
>         > Alignment trap: iconvconfig (2310) PC=0x00009960
>         Instr=0xe5952000
>         > Address=0x0005
>         > 876a FSR 0x013
>         > Alignment trap: iconvconfig (2310) PC=0x00009960
>         Instr=0xe5952000
>         > Address=0x0005
>         > 8786 FSR 0x001
>         
>         
>         That's a possible problem.
>         
>         > Setting up base-passwd (3.5.20em1) ...
>         >
>         > update-passwd has found some differences between your system
>         accounts
>         > and the current Debian defaults. It is advisable to allow
>         
>         
>         Hmm, thought I'd fixed that.
>         
>         > Setting up debian-archive-keyring (2009.01.31em1) ...
>         > gpg: symbol lookup error: /lib/libreadline.so.5: undefined
>         symbol: PC
>         > gpg: symbol lookup error: /lib/libreadline.so.5: undefined
>         symbol: PC
>         > gpg: symbol lookup error: /lib/libreadline.so.5: undefined
>         symbol: PC
>         > dpkg: error processing debian-archive-keyring (--configure):
>         > subprocess post-installation script returned error exit
>         status 127
>         
>         
>         Does libreadline exist at that path in the rootfs? What
>         version?
>         
>         > My question is - di dI do the right thing? What is the error
>         about
>         > debian-archive-keyring :
>         
>         
>         Not sure, not seen it before.
>         
>         > If I was not to run it from within linux, then how should I?
>         
>         
>         What do you mean?
>         
>         Does the board now boot and can gpg work after boot?
>         
>         > Please
>         > help.Thanks.
>         >
>         > Aman.
>         
>         Emdebian Crush isn't problem-free, various niggles like this
>         come and
>         go. Not all actually cause significant breakage. It depends if
>         gpg can
>         work after initial setup or whether it is a continuing error.
>         
>         --
>         
>         
>         Neil Williams
>         =============
>         http://www.data-freedom.org/
>         http://www.linux.codehelp.co.uk/
>         http://e-mail.is-not-s.ms/
>         
> 


Reply to: