Suchergebnisse

It's a bit overwhelming for me all the above requirements but could you please explain how can I do it? I mean set the HW revision: filesystem//etc/init.d/rc.conf | grep 206 export CONFIG_PRODUKT="Fritz_Box_HW206" Is it the above? But if the FS is not initialized yet then we don't need it?

Ok, thx for the hint. Please find the data attached.

@PeterPawn DVB-C 7.01 and 7.08 firmware doesn't have the systemd so I used a different approach https://www.ip-phone-forum.de/threads/busybox-mit-telnet-in-fritz-os-7-2x.307385/post-2378473: echo "/usr/sbin/telnetd -l /sbin/ar7login" >>./etc/init.d/S85-apps All works but I can't get the...

@PeterPawn Please find the dmesg of the 1750E original attached.

@PeterPawn Yep, just figured out this also recently. Thx. ;)

@PeterPawn And I've also just tried with the FTD from 7.01 firmware - the same issue.

@PeterPawn I couldn't connect via telnet unfortunately despite I did all steps you wrote and built the new FS image. However the support data file has the debug log since the very beginning (line 5634) and then also dmesg log inside. Please see attached. Is it enough data?

There are logs from the normal run I assume in the support data file (#73, attached file, line 7411). And there I see also: [ 0.925287] [ 0.925278] [TFFS3_Register_Panic_CB] registering panic callback for mtd ath-nor [ 0.932758] Creating 6 MTD partitions on "ath-nor": [ 0.937694]...

@PeterPawn I tried to copy: filesystem/etc/default.Fritz_Box_HW206/ to filesystem/etc/default.Fritz_Box_HW205/ Rebuilt the filesystem image with the tools/mksquashfs4-avm-be - the same kernel panic. [ 0.949416] {avmnet_cfg_netinit} [ 0.952657] [avmnet] No config found for HWRev 205...

@PeterPawn Looks like this was the log from some other kernel panic. Now I run the 7.01 recovery firmware which flashed all mtd partitions. Then I flashed the alien.image I've built using your instructions earlier. It is again spent ~8sec with the Power led lighting, then the leds switched off...

@PeterPawn Please find the support log file attached. I see kernel panic in there. BEGIN SECTION '/proc/avm/log_sd/crash' ---------- 1970-01-01 01:03:11(1) [Bus error] notifyd([590]) watchdog expired at epoll_wait+0x40 (/lib/libc.so.1 at 0000d5d0) SIGNO 10 ERRNO 62 CODE 3 Version: 07.08-65621...

@PeterPawn I tried to "tools/lzma e -lc1 -lp2 -pb2" for both kernels patched and original and both are not working atm. The only time the original repacked kernel is working is when I am using "lzma e" w/o any switches and this time the padded kernel size is equal to the original untouched...

@PeterPawn I've just did two short tests to ensure our procedure works: 1. repacked the original kernel.image from 1750E with our procedure w/o patching FDT I got the same padded kernel size as inside the original image: freetz@freetz:~/freetz-ng$ hexdump -C -n 64 kernel_original.packed.eva...

@PeterPawn Apologies, I did a mistake and attached the data from the non-padded kernel yesterday and replaced my images and hexdumps in #64 also yesterday but I guess you didn't notice it. As you see now it looks like the image you've built via your procedure looks similar to the one I've built...

Unfortunately this was the proposal from the fda77 to connect the console and I don't have it. Please find attached first and last bytes of the packed firmware. hexdump if you prefer: freetz@freetz:~/freetz-ng$ hexdump -n512 -C kernel.image 00000000 81 12 ed fe 9b e5 17 00 00 00 06 80 01...

@PeterPawn Unfortunately doesn't work: ( After flashing I see constant restarts. I packed the kernel.image as following: tools/lzma e ~/kernel.raw.unpacked.patched ~/kernel.raw.patched tools/lzma2eva 0x80060000 0x80064870 ~/kernel.raw.patched ~/kernel.raw.patched.eva cat...

@PeterPawn Many thanks. I extracted the akc from the final patched kernel. I built the tools from freetz-ng. Unpacked the kernel via unpack-kernel and get those settings: TI_AR7.LoadAddress=0x80060000 TI_AR7.EntryAddress=0x80064870 TI_AR7.RecordLength=0x0017E3FE...

@PeterPawn It looks like FTD area of the dvb-c is larger than we have inside 1750E and it overwrites some important memory blocks in the 1750E. Please see attachment (in red you see the FTD from dvb-c copied to the unpacked kernel 1750E, and the last screenshot shows there is some data in this...

@PeterPawn Please see attached.

@PeterPawn Thank you for details. I managed to patch the unpacked kernel in the hexeditor. How to pack the kernel again and create the new kernel.image? Packing the kernel is just "lzma -c"? I used fwmod tool to unpack the firmware. Shall I use it also for packing again?