OpenWrt Forum Archive

Topic: Install Kamikaze 7.09 on FON 2201 - Help!!!

The content of this topic has been archived on 23 Apr 2018. There are no obvious gaps in this topic, but there may still be some posts missing at the end.

Hi,
I have unsuccessfully tried to install Kamikaze 7.09 on the Fonera+ (FON2201).
Does someone know what's wrong in this procedure?
I have tried also the procedure described in http://wiki.openwrt.org/OpenWrtDocs/Hardware/Fon/Fonera with the
very same result.
I am instead able to recover the Fonera+ firmware following the procedure described here http://www.moliets-bastide.info/post/Ho … Foneraplus

Help!!!!!!! I don't like the Fonera+ firmware!!!!!!!!!

Thanks

Davide

RedBoot> version

RedBoot(tm) bootstrap and debug environment [ROMRAM]
OpenWrt certified release, version 1.1 - built 22:32:28, May  7 2007

Copyright (C) 2000, 2001, 2002, 2003, 2004 Red Hat, Inc.

Board: FON 2201
RAM: 0x80000000-0x81000000, [0x80040290-0x80fe1000] available
FLASH: 0xa8000000 - 0xa87f0000, 128 blocks of 0x00010000 bytes each.
RedBoot> fconfig -l -n
boot_script: true
boot_script_data:
.. fis load -l vmlinux.bin.l7
.. exec

boot_script_timeout: 2
bootp: false
bootp_my_gateway_ip: 0.0.0.0
bootp_my_ip: 192.168.1.1
bootp_my_ip_mask: 255.255.255.0
bootp_server_ip: 192.168.1.254
console_baud_rate: 9600
gdb_port: 9000
info_console_force: false
net_debug: false
RedBoot> load -r -b 0x80041000 openwrt-atheros-2.6-root.jffs2-64k
Using default protocol (TFTP)
Raw file loaded 0x80041000-0x801e0fff, assumed entry at 0x80041000
RedBoot> fis create -b 0x80041000 -f 0xA8030000 -l 0x006F0000 -e 0x00000000 rootfs
... Erase from 0xa8030000-0xa8720000: ...............................................................................................................
... Program from 0x80041000-0x80731000 at 0xa8030000: ...............................................................................................................
... Erase from 0xa87e0000-0xa87f0000: .
... Program from 0x80ff0000-0x81000000 at 0xa87e0000: .
RedBoot> load -r -b 0x80041000 openwrt-atheros-2.6-vmlinux.lzma
Using default protocol (TFTP)
Raw file loaded 0x80041000-0x80100fff, assumed entry at 0x80041000
RedBoot> fis create -r 0x80041000 -e 0x80041000 vmlinux.bin.l7
... Erase from 0xa8720000-0xa87e0000: ............
... Program from 0x80041000-0x80101000 at 0xa8720000: ............
... Erase from 0xa87e0000-0xa87f0000: .
... Program from 0x80ff0000-0x81000000 at 0xa87e0000: .
RedBoot> ip_address
IP: 192.168.1.1/255.255.255.0, Gateway: 0.0.0.0
Default server: 192.168.1.254
RedBoot> reset

... nothing happen and no reply from ping on 192.168.1.1  ...

... power off/on and redboot access...

RedBoot> fis list
Name              FLASH addr  Mem addr    Length      Entry point
RedBoot           0xA8000000  0xA8000000  0x00030000  0x00000000
rootfs            0xA8030000  0xA8030000  0x006F0000  0x00000000
vmlinux.bin.l7    0xA8720000  0x80041000  0x000C0000  0x80041000
FIS directory     0xA87E0000  0xA87E0000  0x0000F000  0x00000000
RedBoot config    0xA87EF000  0xA87EF000  0x00001000  0x00000000

RedBoot> fis load -l vmlinux.bin.l7
Image loaded from 0x80041000-0x80290085
RedBoot> exec

... nothing happen and no reply from ping on 192.168.1.1  ...

... power off/on and redboot access ...

RedBoot> fis load -c -l vmlinux.bin.l7
Image loaded from 0x80041000-0x80290085
Checksum: 0x929aeb35
RedBoot> exec

... nothing happen and no reply from ping on 192.168.1.1  ...

ONLY REDBOOT AVAILABLE NO WAY TO BOOT THE LINUX KERNEL!!!!!!

(Last edited by davide_lenza on 17 Apr 2008, 12:46)

Hi gpp81,
Thanks for your help.
I have followed your freifunk link but in the readme.txt it is written:

"This package installs Freifunk meshing software on top of the original FON software
delivered with the FON router named "Fonera". While the FON function continues, an
additional virtual Wifi card in AdHoc mode is created to realize parallel Freifunk
meshing."

The problem is that I don't want the FON functionality at all. It is totally unsecure. Someone can simply steal my IP and my Mac and can surf the Internet without any control (I have tried it with a second PC and it is really easy to do).

Davide

davide_lenza wrote:

Hi,
I have unsuccessfully tried to install Kamikaze 7.09 on the Fonera+ (FON2201).
Does someone know what's wrong in this procedure?
I have tried also the procedure described in http://wiki.openwrt.org/OpenWrtDocs/Hardware/Fon/Fonera with the
very same result.
I am instead able to recover the Fonera+ firmware following the procedure described here http://www.moliets-bastide.info/post/Ho … Foneraplus.

Help!!!!!!! I don't like the Fonera+ firmware!!!!!!!!!

Hi Davide,

Happy to see my little procedure helped you to recover your Fonera+  ;-)

If you visit my website.. As you know I use OpenWRT on RAM-boot only.
I am the way to release in few days a new RAM-boot for Fonera+ fully fonctional (including ethernet).
Based on k7.06 to stay closer of original firmware. sad
But if you want to try, I can search in my backups RAM-boot version for kamikze 7.09.

I don't plan for the moment to compile a OpnWRT firmware to be flashed on FON2201/2202, others are doing the job at this moment...
I'll post here a link if I have more infos in a next future.
Keep in mind AR2313 drivers are not really compatible "as is" for fonera+ with Marwell switch. I think this is your problem now.

Contact me via PM if you need more infos.

Regards,
LamaBleu

Hi ggp81,
Again, Thanks for youe help!!!
I will try also the freifunk AP51 software.
I succeeded in installing OpenWRT on Fonera but not on Fonera+ with direct access to Redboot. Maybe the problem is really in the ethernet switch driver available in Kamikaze 7.09 and not compatible with Fon2201.
Bohhh!!!

Davide

Hi Lama Bleu,
Your procedure to recover the Fonera+ is working great and I have used it a lot of times ;-) You are great!!!!! Thanks!!!!

"But if you want to try, I can search in my backups RAM-boot version for kamikze 7.09."
Yes I will thanks you for that! I would like to stay on Kamikaze 7.09.

"I don't plan for the moment to compile a OpnWRT firmware to be flashed on FON2201/2202, others are doing the job at this moment...
I'll post here a link if I have more infos in a next future."
Again... THANKS!!!! I am becoming a Kamikaze fun and I would like to stay with the latest version.

"Keep in mind AR2313 drivers are not really compatible "as is" for fonera+ with Marwell switch. I think this is your problem now."
This is an interesting point and maybe the reason of my problem. I always succeed in reflashing Fonera+ with Kamikaze 7.09 but then the command "exec" after "fis load -l vmlinux.bin.l7" simply does not reply!

Why with the redboot I am always able to see the ethernet connection and with the Kamikaze 7.09 no? Which kind of driver the Redboot is using? In which way we can use the same driver for Kamikaze 7.09?

Next steps for me will be:
1) try your Ramdisk solution
2) recompile the trunk of Kamikaze 7.09 and try to reflash the fonera+ with it
3) try the freifunk ap51 software

I have really appreciated your help.

Davide

I'm trying to install OpenWrt on Fonera (2100, so I'm off topic). I'm now running Fon firmware 0.7.2 r3.
I saw Redboot to be disabled on port 9000, so I tried to use some hacks to open SSH port, but without success. Maybe I used too old exploits.
So I tried to use the serial port to gain Redboot access. I plugged my serial port as described on the wiki, and I also followed other tutorials. Unable to communicate with the Fonera, although Fonera booted successfully.
I am going to make other retries. Anyway your help is appreciated smile
Thanks

Hi

davide_lenza wrote:

"But if you want to try, I can search in my backups RAM-boot version for kamikze 7.09."
Yes I will thanks you for that! I would like to stay on Kamikaze 7.09.

Ok Davide, will search on my backups tomorrow. But only RAM-boot OK ? Don't hope (intent)  to flash the file, this is not the purpose of this little dev.


davide_lenza wrote:

"Keep in mind AR2313 drivers are not really compatible "as is" for fonera+ with Marwell switch. I think this is your problem now."
This is an interesting point and maybe the reason of my problem. I always succeed in reflashing Fonera+ with Kamikaze 7.09 but then the command "exec" after "fis load -l vmlinux.bin.l7" simply does not reply!

Yes your default compiled kernel is not compatible for ethernet with fonera2201. And Wifi is disabled by default on kamikaze.
I'm sure your fonera+ is listening for a call coming from you .. on serial port for example.. smile
If you can enter serial port, you can enable wifi...
But no more for the moment (ethernet not working in your situation).
Replacing the vmlinux.bin.l7 by a good one may help. what is the actual partition size for the  kernel ?

davide_lenza wrote:

Why with the redboot I am always able to see the ethernet connection and with the Kamikaze 7.09 no?
Which kind of driver the Redboot is using? In which way we can use the same driver for Kamikaze 7.09?

Standard ar2313 driver does'nt support marvell switch.
Here is a post in french from "Le Finnois" : http://www.lefinnois.net/wp/index.php/2 … mware-fon/ explaining how to run
ethernet for fonera+ with kamikaze 7.07 (use file from FON sources for foneraplus)

Redboot is compiled from Ecos, it is not a kamikaze-part. I have no knowledge about this. Seems  to be very interesting.
Perhaps check this post about forking RedBoot : http://forum.openwrt.org/viewtopic.php?id=6357 ( no relation with fonera).

Regards,

Lama Bleu

Hi!

Could you help me? I installed Kamikaze 7.09 on TP-LINK WR542G but I can't change nothing, because if I reboot the router the settings changes to the default values. I tried to recover the original firmware, but it said "Could not open mtd device: vmlinux.bin.i7 Can't open device for writing!"
root@OpenWrt:/# cat /proc/mtd
dev:    size   erasesize  name
mtd0: 00010000 00010000 "RedBoot"
mtd1: 000a0000 00010000 "vmlinux.bin.i7"
mtd2: 00130000 00010000 "rootfs"
mtd3: 00030000 00010000 "rootfs_data"
mtd4: 0000f000 0000f000 "FIS directory"
mtd5: 00001000 00001000 "RedBoot config"
mtd6: 00010000 00010000 "boardconfig"

I tried to unlock but

Unlocking vmlinux.bin.i7 ...
Could not open mtd device: vmlinux.bin.i7

What can I do with the router, it's dead or not yet?

(Last edited by Shapy21 on 22 Jun 2012, 12:09)

The discussion might have continued from here.