I realize that support for AR7 is a Work in Progress, however I've got a spare unit which I thought I'd give it a go with.

I checked out Kamikaze from subversion last night and built it with appropriate options for AR7 hardware.  I went through the instructions on the wiki, patched ADAM2 to accept non-checksummed firmware, then got FTP access easily enough, set up mtd5 as per the instructions (my current set of mtd's are the same as the wiki entry on the DG834G, so I used their numbers).  Flashed the image into mtd5 and rebooted. 

Watching the LEDs on the unit, the "tick" LED will flash on boot, (which is the period when I can access ADAM2), then go solid for about 2 seconds.  Then it will flash 3 times in quick succession and then go out.  The lights on the switch are flashing, however I'm getting nothing from it.  Not a single packet.  I've tried scanning through 192.168.0.0/24, and also 10.0.0.0/24 (the subnet which it was part of before flashing, at 10.0.0.3), and I get nothing from it. 

ADAM2 is still fine, as I can FTP into it as I have done before.  Thank goodness I didn't bork the bootloader!  I've also tried removing the wireless card to no effect. 

I suppose the next step would be to hook up a serial cable to it and see what the output from the bootloader is during the boot process. 

I'm wondering if anyone has a known working kernel config for this particular device?  Also, I noticed that the official netgear linux build is a 2.4 kernel, while Kamikaze is now 2.6.  Could it be a possibility that I could try an older build which has AR7 support?

UPDATE: I've found this: http://www.earth.li/~noodles/hardware-dg834g.html It says something about splitting the squashfs.bin file up into two, and writing over mtd0 and 1?  That sounds... scary.  I think this may well be a bit out of date, as it mentions something about a 2.4 kernel...

(Last edited by naxxtor on 1 Sep 2007, 05:19)

There could be many things going wrong here; get the serial console working first. It's likely that you are probably hitting this problem https://dev.openwrt.org/ticket/1858

Seeing how you can still get into ADAM2, you don't need to worry about serial console.  Otherwise nabcore is right.  Make the mofications in that ticket and rebuild another image.  It should work.

Since you already created mtd5 (spanning mtd1 and mtd0), you don't need to worry about splitting the image.

Ah right ok.  Now compiling with the above patch applied.  Hopefully it'll boot!

Did you have any joy?