AltarCrystal Posted August 6, 2009 Share Posted August 6, 2009 Alright, so sorry if this is a dumb question, however I just received my shiny new Fon+ in the mail yesterday, and right away went to work on flashing the firmware. Now, it is the Fon2201 running firmware version 1.1.0 r2. I assumed I needed to downgrade the firmware (and am still thinking I do?), however some sources I read say I don't. I was able to unlock it (in the sense I can SSH into it). However, to patch the kernel, every article and tutorial I read says to use mtd to erase and rewrite linux.bin.l7. I ran the command, and it said it could not open the device (Yes, it is a lowercase "L", not a 1). I did a bit more reading, learned about the mtd table, and see mine differes from practically everything I read. My /proc/mtd is as follows: mtd0: RedBoot mtd1: loader mtd2: image mtd3: rootfs mtd4: rootfs_data mtd5: config mtd6: image2 mtd7: FIS directory mtd8: RedBoot config mtd9: board_cofnig After a bit of reading and some process of elimination, I'm left with 3 devices which do not match what I've read: loader, image, and image2. One can assume that loader is the boot loader, and I'm assuming image and image2 is...the kernel? The system tries to boot image, and uses image2 as a fallback? (Again, just making guesses and taking from what I've read) The Fon itself is running kernel 184.108.40.206, and I, of course, havn't allowed it to connect to the internet. So, is this a matter of simply writing image as opposed to linux.bin.l7? Or do I have to downgrade the entire firmware before proceeding? I figured I'd better ask before I overwrite stuff all willy-nilly. Edit: Also a curious problem. The script I keep seeing is the "catch_fonera+" script, which would automatically telnet into the Fon, catching it in RedBoot. However, running it from either Ubuntu or Slackware would result in "telnet: Unable to connect to remove host: Network is unreachable" Oddly enough, as I type this, I tried the script again, and got: 192.168.1.1: inverse host lookup failed: Host name lookup failure (UNKNOWN) [192.168.1.1] 9000 (?) open == Executing boot script in 1.060 seconds - enter ^C to abort == Executing boot script in 1.060 seconds - enter ^C to abort And it hangs there endlessly. Opening up a separate terminal and trying to ping that same address (192.168.1.1) results in "Destination Host Unreachable". Pinging 192.168.10.1 results in "Network is unreachable" Ideas? Quote Link to comment Share on other sites More sharing options...
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.