| 1 |
On 07/19 07:51, Jorge Almeida wrote: |
| 2 |
> On Wed, Jul 19, 2017 at 7:25 PM, <tuxic@××××××.de> wrote: |
| 3 |
> > On 07/19 06:57, Jorge Almeida wrote: |
| 4 |
> >> On Wed, Jul 19, 2017 at 6:40 PM, <tuxic@××××××.de> wrote: |
| 5 |
> >> |
| 6 |
> >> > |
| 7 |
> >> > the tool is statically linked and only the command "file" |
| 8 |
> >> > reveals its 32bit nature. |
| 9 |
> >> > |
| 10 |
> >> If the tool is a static binary, you shouldn't need anything besides a |
| 11 |
> >> kernel with support for 32 bit executables (Executable file formats / |
| 12 |
> >> Emulations ---> x32 ABI for 64-bit mode) |
| 13 |
> >> |
| 14 |
> |
| 15 |
> > |
| 16 |
> > Hi, |
| 17 |
> > |
| 18 |
> > the linux32-trick is neat...but it seems a little more to be done |
| 19 |
> > here. |
| 20 |
> > |
| 21 |
> > I straced the whole thing: |
| 22 |
> > sudo strace linux32 ./pirate-loader_lnx |
| 23 |
> |
| 24 |
> Did you check that your kernel supports 32 bit executables? If so, |
| 25 |
> what happens when you run "./pirate-loader_lnx"? And what about |
| 26 |
> "strace ./pirate-loader_lnx"? The output of strace you listed shows |
| 27 |
> that something is missing, but is it required by ./pirate-loader_lnx |
| 28 |
> or just by linux32 itself? |
| 29 |
|
| 30 |
The kernel config says: |
| 31 |
|
| 32 |
# |
| 33 |
# Executable file formats / Emulations |
| 34 |
# |
| 35 |
CONFIG_BINFMT_ELF=y |
| 36 |
CONFIG_COMPAT_BINFMT_ELF=y |
| 37 |
CONFIG_ELFCORE=y |
| 38 |
CONFIG_CORE_DUMP_DEFAULT_ELF_HEADERS=y |
| 39 |
CONFIG_BINFMT_SCRIPT=y |
| 40 |
# CONFIG_HAVE_AOUT is not set |
| 41 |
CONFIG_BINFMT_MISC=y |
| 42 |
CONFIG_COREDUMP=y |
| 43 |
CONFIG_IA32_EMULATION=y |
| 44 |
CONFIG_IA32_AOUT=y |
| 45 |
CONFIG_X86_X32=y |
| 46 |
CONFIG_COMPAT_32=y |
| 47 |
CONFIG_COMPAT=y |
| 48 |
CONFIG_COMPAT_FOR_U64_ALIGNMENT=y |
| 49 |
CONFIG_SYSVIPC_COMPAT=y |
| 50 |
CONFIG_KEYS_COMPAT=y |
| 51 |
CONFIG_X86_DEV_DMA_OPS=y |
| 52 |
CONFIG_NET=y |
| 53 |
CONFIG_COMPAT_NETLINK_MESSAGES=y |
| 54 |
CONFIG_NET_INGRESS=y |
| 55 |
|
| 56 |
All combinations of sudo / strace in conjunction with |
| 57 |
pirate_loader_lnx and the lack the one or the other |
| 58 |
state the same: |
| 59 |
#>./pirate-loader_lnx |
| 60 |
zsh: no such file or directory: ./pirate-loader_lnx |
| 61 |
[1] 4125 exit 127 ./pirate-loader_lnx |
| 62 |
|
| 63 |
Since pirate_loader_lnx alone also gives the same error |
| 64 |
message, it is pirate_loader_lnx which misses someting. |
| 65 |
|
| 66 |
> |
| 67 |
> > |
| 68 |
> > Why does the task of flashing firmware walk hand in hand with mental illness so |
| 69 |
> > near at the abyss of bricked hardware that often ? |
| 70 |
> Crappy software made by professionals (alt.: smart-assed sw made by |
| 71 |
> the vendor's underpaid, or overpaid, hirelings) |
| 72 |
|
| 73 |
Sorry to say, but the Bus pirate, its software and its firmware are |
| 74 |
open source/open hardware. |
| 75 |
I dare to rebuild the flasher...I dont know what will happen, if |
| 76 |
a 32 bit could, which acts on such a low level gets compiled on 64 |
| 77 |
instead of 32 bit. I dont want to risk my swiss army kni....sorry... |
| 78 |
want to say: ...to risk my Bus Pirate... |
| 79 |
Cheers |
| 80 |
Meino |
| 81 |
|
| 82 |
|
| 83 |
|
| 84 |
|
| 85 |
> J.A. |
| 86 |
> |
Archives