Re: installing debian-armeb on a new device / where to get the base filesystem?

[Tomasz Chmielewski <mangoo@wpkg.org>]

Lennart Sorensen wrote:

(...)

> > I tried different versions of dpkg available for armeb, but they all 
> > fail in the same manner.
> > strace gives no clues either, dpkg just segfaults at the same point:
> >
> > (...)
> >
> > open("/etc/dpkg/dpkg.cfg", O_RDONLY|O_LARGEFILE) = 3
> > fstat64(3, {st_mode=S_IFREG|0666, st_size=294, ...}) = 0
> > old_mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, 
> > -1, 0) = 0x40015000
> > read(3, "# dpkg configuration file\n#\n# Th"..., 4096) = 294
> > read(3, "", 4096)                       = 0
> > close(3)                                = 0
> > munmap(0x40015000, 4096)                = 0
> > brk(0)                                  = 0xe2000
> > brk(0)                                  = 0xe2000
> > brk(0xe1000)                            = 0xe1000
> > brk(0)                                  = 0xe1000
> > open("/home/toor/.dpkg.cfg", O_RDONLY|O_LARGEFILE) = -1 ENOENT (No such 
> > file or directory)
> > --- SIGSEGV (Segmentation fault) @ 0 (0) ---
> > +++ killed by SIGSEGV +++
> >
> >
> > Any clues?
>
> I wonder if your existing kernel can't run the binaries for some reason
> (too old, missing feature, etc)?

Hard to tell.
It's 2.4.27 kernel, and dpkg is the only binary I found that segfaults.

Perhaps if I work out how to change the kernel there, I'd be able to 
tell some more.

--
Tomasz Chmielewski
http://wpkg.org