MTD Table Mismatch

[AltarCrystal]

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 2.6.19.2, 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?

[cazze]

Can you ping to the 192.168.1.1 address?

My Fon was on 169.254.255.1 when it arrived last week.

Here is the Howto i followed to unlock my Fon (maybe not the same for a Fon+)

http://www.zoobab.com/fonera

cazze

[AltarCrystal]

Well, like I said, I did try pinging 192.168.1.1, in which I got "Destination Host Unreachable". For some reason it never occurred to me that it may flat-out be the wrong IP. I know when it's UP, I can SSH into 192.168.10.1, however I can't ping that address at all until the Fon is completely powered up.

Sadly I can't try anything right now, as I'm at work, but when I get home I'll try scanning the network while it's booting up to see if I can't find the IP it's on while booting.

[digininja]

Well, like I said, I did try pinging 192.168.1.1, in which I got "Destination Host Unreachable". For some reason it never occurred to me that it may flat-out be the wrong IP. I know when it's UP, I can SSH into 192.168.10.1, however I can't ping that address at all until the Fon is completely powered up.

Sadly I can't try anything right now, as I'm at work, but when I get home I'll try scanning the network while it's booting up to see if I can't find the IP it's on while booting.

reboot by default listens on 192.168.1.1 on the US Fon+s but on 0.0.0.0 for the UK ones and I don't know about other countries.

Quick and easy way to test the IP address is to make sure you are on the same subnet then start a ping going to the IP you suspect redboot to be on then power on the fon, if redboot is there you'll probably get about 4 replies before the boot process continues and it goes over to the OS for networking.

Try the redboot.pl script rather than the catch one, I know that works if you have the right IP address. You can get this from my site.

[AltarCrystal]

Thanks for the speedy replies guys.

Digininja, I don't know why I completely forgot about your script, but that did the trick. I was able to flash your firmware onto my fon.

However, I'm...not quite sure it went as swimmingly as it could have. I followed the guide step for step from your site, digi, and it SEEMED to work fine. However, when I try accessing the web interface (via either http://192.168.1.1, 192.168.1.1:1471, or 192.168.1.1:1471/cgi-bin/status.rb), it times out. Not a 404, just times out.

I can, however, ping the Fon and telnet into it, however the ONLY port that is open (or, atleast, is listening) is port 9000, telnet.

Bad flash? Am I missing something?

EDIT: Hm, this is interesting. I tried running the boot script manually (fis load -l vmlinux.bin.l7), and I get the error "Not a loadable image - try using -b ADDRESS option". I'd guess these are related. Sounding more and more like I should try reflashing?

EDIT 2: Ah, yup, reflashing worked. Thanks guys! :D