http://193.7.178.18/ ixs' Vodkamelone - rants and raves... de Serendipity 1.3-beta1 - http://www.s9y.org/ http://193.7.178.18/templates/default/img/s9y_banner_small.png http://193.7.178.18/ 100 21 http://193.7.178.18/archives/80-Siemens-S65-Telefoncode-zuruecksetzen.html#c1243 http://193.7.178.18/archives/80-Siemens-S65-Telefoncode-zuruecksetzen.html#comments http://193.7.178.18/wfwcomment.php?cid=80 nospam@example.com (Thank You) Selten so eine perfekte Erklärung für so ein etwas komplizierter Vorgang gefunden. Wenn man es zuerst 3 mal ließt denkt man 3 mal :-| :-( dass klappt ja nie! ABER nach dem download und start von "PauaUtils" gings dann flott wie am Schnürchen. :-) :-) :-) :-) :-) :-) :-) :-) :-) :-) Nach versehentlichen sperren wieder ein telefoncode-freies-Ersatzhandy im Hause +++++ SUPER ANLEITUNG +++++ +++ Vielen Dank +++ :-) :-) :-) :-) :-) :-) :-) :-) :-) :-) Tue, 17 Jul 2012 14:12:45 +0200 http://193.7.178.18/archives/80-guid.html#c1243 http://193.7.178.18/archives/68-Strato-als-Serverhoster-Ganz-ganz-schlechte-Idee..html#c1167 http://193.7.178.18/archives/68-Strato-als-Serverhoster-Ganz-ganz-schlechte-Idee..html#comments http://193.7.178.18/wfwcomment.php?cid=68 nospam@example.com (wolfgang) strato hat das vor tagen auch mit meinem server gemacht, bis heute aber nicht wieder aufgeschaltet. ich geh da, das ist nicht vertretbar Tue, 6 Mar 2012 22:42:12 +0100 http://193.7.178.18/archives/68-guid.html#c1167 http://193.7.178.18/archives/80-Siemens-S65-Telefoncode-zuruecksetzen.html#c1082 http://193.7.178.18/archives/80-Siemens-S65-Telefoncode-zuruecksetzen.html#comments http://193.7.178.18/wfwcomment.php?cid=80 nospam@example.com (Mörtel) Danke für die Anleitung.Hat prima funktioniert. Ist aber etwas umständlich mit den mehreren Programmen... Das Ganze funktioniert auch lediglich mit papuaUtils bzw. wer möchte, papuaUtils + px65v4 Wed, 1 Feb 2012 11:34:43 +0100 http://193.7.178.18/archives/80-guid.html#c1082 http://193.7.178.18/archives/80-Siemens-S65-Telefoncode-zuruecksetzen.html#c1005 http://193.7.178.18/archives/80-Siemens-S65-Telefoncode-zuruecksetzen.html#comments http://193.7.178.18/wfwcomment.php?cid=80 nospam@example.com (newuser) Hallo! falls es noch jemanden interessiert: mittlerweile gibt es die Version x65PapuaSoft_v081a.rar. Da braucht man nur noch im Karteireiter Keys die codes auslesen und unter Diverse 5008 Unlock ausführen und mit OK bestätigen. Danke für die Tipps hier - hätte mein S65 sonst weggeschmissen "schluchts". so wird es mir hoffentlich noch lange treu seinen Dienst tun. Tue, 25 Oct 2011 22:37:58 +0200 http://193.7.178.18/archives/80-guid.html#c1005 http://193.7.178.18/archives/96-Spass-mit-der-Rittal-CMC-TC-PUII.html#c995 http://193.7.178.18/archives/96-Spass-mit-der-Rittal-CMC-TC-PUII.html#comments http://193.7.178.18/wfwcomment.php?cid=96 nospam@example.com (Scott) The PU is now working as normal, but mtdblock4 refuses to mount with any parameter. I assume you mean /jffs/etc/passwd is located on the mtdblock4. It just refuses to mount, and i'm getting error message "/proc/filesystems: No such file or directory". Even this command you used for mounting, did give the same error: "mount /dev/mtdblock4 /jffs2/" Anyhow, playing around with the thing really helps me to learn new stuff :-D two weeks ago i hadn't even tried unix/linux-based shells. Fri, 21 Oct 2011 17:19:36 +0200 http://193.7.178.18/archives/96-guid.html#c995 http://193.7.178.18/archives/96-Spass-mit-der-Rittal-CMC-TC-PUII.html#c994 http://193.7.178.18/archives/96-Spass-mit-der-Rittal-CMC-TC-PUII.html#comments http://193.7.178.18/wfwcomment.php?cid=96 nospam@example.com (ixs) Edit /jffs/etc/passwd, remove the cryptstring in the line starting with the right username. Password should be gone. Fri, 21 Oct 2011 16:21:04 +0200 http://193.7.178.18/archives/96-guid.html#c994 http://193.7.178.18/archives/96-Spass-mit-der-Rittal-CMC-TC-PUII.html#c993 http://193.7.178.18/archives/96-Spass-mit-der-Rittal-CMC-TC-PUII.html#comments http://193.7.178.18/wfwcomment.php?cid=96 nospam@example.com (Scott) Already tried uploading to tmp & tmpfs and to new folder. But now i found the solution! i had forgotten to upload it with the same parameter "rz -b", so that's why it didn't accept it. Uploading right now, 45min left. Hopefully it gets the PU back alive so i can concentrate on the lost password reset, btw. do you have any hints on that one? Thanks a lot for a great page and much info of the CMC, there isn't too much info on it anywhere! :-) Fri, 21 Oct 2011 15:36:20 +0200 http://193.7.178.18/archives/96-guid.html#c993 http://193.7.178.18/archives/96-Spass-mit-der-Rittal-CMC-TC-PUII.html#c992 http://193.7.178.18/archives/96-Spass-mit-der-Rittal-CMC-TC-PUII.html#comments http://193.7.178.18/wfwcomment.php?cid=96 nospam@example.com (ixs) I see. You cannot directly write via zmodem to the /dev/mtdblock4 file. You have to upload it to /tmp or so first. And then you can "cat /tmp/mtdblock4 > /dev/mtdblock4". Fri, 21 Oct 2011 15:18:57 +0200 http://193.7.178.18/archives/96-guid.html#c992 http://193.7.178.18/archives/96-Spass-mit-der-Rittal-CMC-TC-PUII.html#c991 http://193.7.178.18/archives/96-Spass-mit-der-Rittal-CMC-TC-PUII.html#comments http://193.7.178.18/wfwcomment.php?cid=96 nospam@example.com (Scott) Hello again! The mtdblock4 is still there but it's erased/corrupted. I'm connected through serial, and yes, it boots up to U-Boot and BusyBox shell when i use the setenv commands. I've tried uploading a new mtdblock4 with hyperterminal, and the upload box just blinks quickly and goes away, in other words it doesn't upload anything. Now i downloaded another terminal program, and it also doesn't upload the mtdblock4. It though gives me a little bit more detailed error: "receiver wants to skip this file". Fri, 21 Oct 2011 14:50:06 +0200 http://193.7.178.18/archives/96-guid.html#c991 http://193.7.178.18/archives/96-Spass-mit-der-Rittal-CMC-TC-PUII.html#c990 http://193.7.178.18/archives/96-Spass-mit-der-Rittal-CMC-TC-PUII.html#comments http://193.7.178.18/wfwcomment.php?cid=96 nospam@example.com (ixs) Hi Scott, glad you could use the write up. I haven't played around with our CMC-TC in quite some time so please take my suggestions as purely theoretical advice. First: What do you mean with bricked? If only the mtdblock4 is gone, nothing of value was lost. This filesystem should have only configuration files on it and anything missing can be easily regenerated. Can you see the PUII actually booting and can you get a boot shell via the serial interface? If this is the case, you can use /usr/bin/rz to transfer your image to /tmp and then cat that to mtdblock4. If hyperterm can't do Z-Modem, use another terminal program. If you cannot even boot the PUII unit, you can possibly flash the mtdblock via the bootloader. I never tried that but it should be possible. Or alternatively, which is what I'd do is to grab an OpenWRT image or build one for the machine and then network boot the box. Get a decent userland on there and then do the work from a network-booted Linux system. cheers, andreas Fri, 21 Oct 2011 10:30:05 +0200 http://193.7.178.18/archives/96-guid.html#c990 http://193.7.178.18/archives/96-Spass-mit-der-Rittal-CMC-TC-PUII.html#c989 http://193.7.178.18/archives/96-Spass-mit-der-Rittal-CMC-TC-PUII.html#comments http://193.7.178.18/wfwcomment.php?cid=96 nospam@example.com (Scott) Hello! Really interesting write-up, i learned a lot! I'm working on a bricked Processing unit, the mtdblock4 is gone and i've fetched a new one from a working PU, the question is, how do i upload the new 'mtdblock4' to the device? Hyperterminal wont send anything to the device with Zmodem?! Second question is about passwords. I've forgotten my HTML login password on one of the boxes. Which file on the device keeps user information stored, and is it possible to owerwrite with another file from a working device? Fri, 21 Oct 2011 10:16:51 +0200 http://193.7.178.18/archives/96-guid.html#c989 http://193.7.178.18/archives/146-Unbricking-an-Intel-Pro1000-e1000-network-interface.html#c983 http://193.7.178.18/archives/146-Unbricking-an-Intel-Pro1000-e1000-network-interface.html#comments http://193.7.178.18/wfwcomment.php?cid=146 nospam@example.com (Valts) One more dump for search engines Intel Corporation 82557/8/9 [Ethernet Pro 100] (rev 0c): Id: 8086:1229 Offset Values ------ ------ 0x0000 00 02 b3 9f 50 53 0b 02 ff ff 01 02 01 47 ff ff 0x0010 17 75 04 67 a0 50 40 00 86 80 64 00 ff ff ff ff 0x0020 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff 0x0030 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff 0x0040 ff ff ff ff ff ff 29 12 ff ff ff ff ff ff ff ff 0x0050 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff 0x0060 2c 01 00 40 03 30 ff ff ff ff ff ff ff ff ff ff 0x0070 ff ff ff ff ff ff ff ff ff ff ff ff ff ff 9c 49 Wed, 5 Oct 2011 17:53:57 +0200 http://193.7.178.18/archives/146-guid.html#c983 http://193.7.178.18/archives/146-Unbricking-an-Intel-Pro1000-e1000-network-interface.html#c982 http://193.7.178.18/archives/146-Unbricking-an-Intel-Pro1000-e1000-network-interface.html#comments http://193.7.178.18/wfwcomment.php?cid=146 nospam@example.com () Ok here is dump file, change XX for your MAC. The chip on board is 82541PI root@skystar:~# ethtool -e wan0 Offset Values ------ ------ 0x0000 xx xx xx xx xx xx 10 02 ff ff 00 10 ff ff ff ff 0x0010 02 c8 01 35 0b 64 76 13 86 80 7c 10 86 80 84 b2 0x0020 dd 20 55 55 00 00 90 2f 00 32 12 00 20 1e 12 00 0x0030 20 1e 12 00 20 1e 12 00 20 1e 09 00 00 02 00 00 0x0040 0c 00 a6 93 0b 28 00 00 00 04 ff ff ff ff ff ff 0x0050 ff ff ff ff ff ff ff ff ff ff ff ff ff ff 02 06 0x0060 00 01 00 40 16 12 07 40 ff ff ff ff ff ff ff ff 0x0070 ff ff ff ff ff ff ff ff ff ff ff ff ff ff 45 bb Wed, 5 Oct 2011 17:33:20 +0200 http://193.7.178.18/archives/146-guid.html#c982 http://193.7.178.18/archives/146-Unbricking-an-Intel-Pro1000-e1000-network-interface.html#c981 http://193.7.178.18/archives/146-Unbricking-an-Intel-Pro1000-e1000-network-interface.html#comments http://193.7.178.18/wfwcomment.php?cid=146 nospam@example.com (Valts) Unbricked Intel 1000/GT suspect it got corrupted due to poor contact in the PCI slot. The pci id is 8086:107c which means its magic is as suggested - 0x10768086 Will post dump bit later. Wed, 5 Oct 2011 17:06:27 +0200 http://193.7.178.18/archives/146-guid.html#c981 http://193.7.178.18/archives/167-A-little-shell-spinner.html#c964 http://193.7.178.18/archives/167-A-little-shell-spinner.html#comments http://193.7.178.18/wfwcomment.php?cid=167 nospam@example.com (towo) I haven't quite found out the reason yet, but «echo "-"» and any variations don't seem to work with zsh, instead echoing a blank line. Tue, 13 Sep 2011 11:30:34 +0200 http://193.7.178.18/archives/167-guid.html#c964