OpenWrt Forum Archive

Topic: AR430W Atheros AR2318 / AR2317 chipset support

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

hi
  I have never used redboot.  but won't mind reading up a bit...
on the reference you posted, you said bdrestore erase fis info, and
you need lots of fis command to restore a working fis directory
do you mind tell me where to find reference for the fis directory.

Is this all I need
-----------------
bdrestore
load -r -b %{FREEMEMLO} openwrt-atheros-2.6-vmlinux.lzma
fis create -e 0x80041000 -r 0x80041000 vmlinux.bin.l7
load -r -b %{FREEMEMLO} openwrt-atheros-2.6-root.squashfs
fis create -l 0xLENGTH rootfs
--------------------

I don't have a serial interface to this board...

(Last edited by cycrap on 21 Jul 2008, 02:49)

cycrap wrote:

hi
Is this all I need
-----------------
bdrestore
load -r -b %{FREEMEMLO} openwrt-atheros-2.6-vmlinux.lzma
fis create -e 0x80041000 -r 0x80041000 vmlinux.bin.l7
load -r -b %{FREEMEMLO} openwrt-atheros-2.6-root.squashfs
fis create -l 0xLENGTH rootfs
--------------------

I don't have a serial interface to this board...

how do you plan to do the above then?

here is what I did, and now opwnwrt is not booting (but dd-wrt redboot is okey)

-----------------------------
== Executing boot script in 3.780 seconds - enter ^C to abort
^C
DD-WRT> fis list
Name              FLASH addr  Mem addr    Length      Entry point
RedBoot           0xBFC00000  0xBFC00000  0x00030000  0x00000000
vmlinux.bin.l7    0xBFC30000  0x80041000  0x000B0000  0x80041000
rootfs            0xBFCE0000  0x80040800  0x00300000  0x80040800
FIS directory     0xBFFE0000  0xBFFE0000  0x0000F000  0x00000000
RedBoot config    0xBFFEF000  0xBFFEF000  0x00001000  0x00000000
DD-WRT> bdrestore
Board config  found at 0xbfff0000
Radio config  found at 0xbfff00f8
Starting sector program for 0xbffe0000! Please wait!
Starting sector program for 0xbfff0000! Please wait!
Restore completed successfully!!
DD-WRT> fis list
Name              FLASH addr  Mem addr    Length      Entry point
<Not a string: 0x80FF0000>                 0x41523533  0x31352064  0x65666175
0x6C740000
---------------------------------------------------------

so I restored the config file, and both redboot and openwrt is gone

---------------------------------------------
DD-WRT> load /tftproot/ap61.ram
Using default protocol (TFTP)
Entry point: 0x800410bc, address range: 0x80041000-0x800680d8
DD-WRT> go
---------------------------------------------

then I reconnect to the router at 192.168.1.1

---------------------------------------------
DD-WRT> fconfig -i
Initialize non-volatile configuration - continue (y/n)? y
Run script at boot: false
Use BOOTP for network configuration: true
Default server IP address: 192.168.1.254
Console baud rate: 9600
GDB connection port: 9000
Force console for special debug messages: false
Network debug at boot time: false
Update RedBoot non-volatile configuration - continue (y/n)? y
... Erase from 0xbffe0000-0xbfff0000: .
... Program from 0x80ff0000-0x81000000 at 0xbffe0000: .
DD-WRT> fis init
About to initialize [format] FLASH image system - continue (y/n)? y
*** Initialize FLASH Image System
Relocating Board Data to new location.
Found board data at 0xbffe0000.
Found eeprom data at 0xbffef000.
Failed to cache eeprom
... Erase from 0xbffe0000-0xbfff0000: .
... Program from 0x80ff0000-0x81000000 at 0xbffe0000: .
DD-WRT> ip_address -h 192.168.1.23
IP: 192.168.1.1/255.255.255.0, Gateway: 0.0.0.0
Default server: 192.168.1.23
DD-WRT> load -r -b %{FREEMEMLO} /tftproot/ap61.rom
Using default protocol (TFTP)
Raw file loaded 0x80080000-0x800a8717, assumed entry at 0x80080000
DD-WRT> fis create -l 0x30000 -e 0xbfc00000 RedBoot
An image named 'RedBoot' exists - continue (y/n)? y
... Erase from 0xbfc00000-0xbfc30000: ...
... Program from 0x80080000-0x800a8718 at 0xbfc00000: ...
... Erase from 0xbffe0000-0xbfff0000: .
... Program from 0x80ff0000-0x81000000 at 0xbffe0000: .
DD-WRT> reset
--------------------------------------

only thing I saw is the "Failed to cache eeprom
now loading the openWrt part

--------------------------------------------------
DD-WRT> ip_address -h 192.168.1.23
IP: 192.168.1.1/255.255.255.0, Gateway: 0.0.0.0
Default server: 192.168.1.23
DD-WRT> load -r -b %{FREEMEMLO} /tftproot/test/openwrt-atheros-vmlinux.lzma
Using default protocol (TFTP)
Raw file loaded 0x80040800-0x800f07ff, assumed entry at 0x80040800
DD-WRT> fis init
About to initialize [format] FLASH image system - continue (y/n)? y
*** Initialize FLASH Image System
... Erase from 0xbffe0000-0xbfff0000: .
... Program from 0x80ff0000-0x81000000 at 0xbffe0000: .
DD-WRT> fis create -e 0x80041000 -r 0x80041000 vmlinux.bin.l7
... Erase from 0xbfc30000-0xbfce0000: ...........
... Program from 0x80040800-0x800f0800 at 0xbfc30000: ...........
... Erase from 0xbffe0000-0xbfff0000: .
... Program from 0x80ff0000-0x81000000 at 0xbffe0000: .
DD-WRT> fis free
  0xBFCE0000 .. 0xBFFE0000
  DD-WRT> load -r -b %{FREEMEMLO} /tftproot/test/openwrt-atheros-root.squashfs
  Using default protocol (TFTP)
  Raw file loaded 0x80040800-0x801807ff, assumed entry at 0x80040800
  DD-WRT> fis create -l 0x00300000 rootfs
  ... Erase from 0xbfce0000-0xbffe0000:
  ................................................
  ... Program from 0x80040800-0x80180800 at 0xbfce0000: ....................
  ... Erase from 0xbffe0000-0xbfff0000: .
  ... Program from 0x80ff0000-0x81000000 at 0xbffe0000: .
-------------------------------------------------------------

so openwrt is loaded and need to config now

----------------------------------------------------
  DD-WRT> fconfig boot_script true
  boot_script: Setting to true
  Update RedBoot non-volatile configuration - continue (y/n)? n
  DD-WRT> fconfig bootp false
  bootp: Setting to false
  Update RedBoot non-volatile configuration - continue (y/n)? n
  DD-WRT> fconfig boot_script_timeout 5
  boot_script_timeout: Setting to 5
  Update RedBoot non-volatile configuration - continue (y/n)? n
  DD-WRT> fconfig -l -n
  boot_script: true
  boot_script_data:
  boot_script_timeout: 5
  bootp: false
  bootp_my_gateway_ip: 0.0.0.0
  bootp_my_ip: 0.0.0.0
  bootp_my_ip_mask: 0.0.0.0
  bootp_server_ip: 192.168.1.254
  console_baud_rate: 9600
  gdb_port: 9000
  info_console_force: false
  net_debug: false
  DD-WRT> fconfig
  Run script at boot: true
  Boot script:
  .. fis load -l vmlinux.bin.l7
  .. exec
  Enter script, terminate with empty line
  >> fis load -l vmlinux.bin.l7
  >> exec
  >>
  Boot script timeout (1000ms resolution): 5
  Use BOOTP for network configuration: false
  Gateway IP address:
  Local IP address: 192.168.1.1
  Local IP address mask: 255.255.255.0
  Default server IP address: 192.168.1.254
  Console baud rate: 9600
  GDB connection port: 9000
  Force console for special debug messages: false
  Network debug at boot time: false
  Update RedBoot non-volatile configuration - continue (y/n)? y
  ... Erase from 0xbffe0000-0xbfff0000: .
  ... Program from 0x80ff0000-0x81000000 at 0xbffe0000: .
  DD-WRT> reset

---------------------------------

now the router is hanging after I boot up..
I can still get into the DD-Wrt redboot. but if I wait and let the linux kernel boot, then I am getting 192.168.1.1 not reachable.  the kernel image I am using is the same as the one I compiled that boots, but no wireless support...

please let me know if I am doing something wrong..

I have a couple question about the procedure I performed

when I loaded the
openwrt-atheros-vmlinux.lzma
from the network, it says

----------------------------
Using default protocol (TFTP)
Raw file loaded 0x80040800-0x800f07ff, assumed entry at 0x80040800
----------------------------

then in the instruction, it says after "fis init", to do a "fis create" at

-------------------------------
DD-WRT> fis create -e 0x80041000 -r 0x80041000 vmlinux.bin.l7
-------------------------------

should I make the -e and -r at 0x80040800?

OK i don't want to wipe out my board so I can't really execute commands.
But I think this is what I did.

# bdrestore
# fis init
# fis create -b 0x80041000 -l 0xc0000 -f 0xbfc30000 -e 0x80274000 -n linux
# fis create -b 0 -l 0x2f0000 -n rootfs 
# load -r -b 0x80050000 /tftp/openwrt-atheros-2.6-vmlinux.lzma
# fis write -b 0x80050000 -f 0xbfc30000 -l 0xc0000
# load -r -b 0x80050000 /tftp/openwrt-atheros-2.6-root.jffs2-64k
# fis write -b 0x80050000 -f 0xbfce0000 -l 0x1a0000
# fconfig 
>> fis load -l linux
>> go 0x80274000
>>

I haven't really read the redboot help page to know what length and free_mem does. I can guess but I am not really interested in finding out. I guess I am becoming too old and tend to stick to the way I know.

I do manually calculate everything. In my shell I use ls -l --block-size=65536 to find out what are each block size.

I guess having the kernel space before the rootfs is not really standard but that's what I've been doing.

My fis list output is

DD-WRT> fis list                                                                
Name              FLASH addr  Mem addr    Length      Entry point               
RedBoot           0xBFC00000  0xBFC00000  0x00030000  0x00000000                
linux             0xBFC30000  0x80041000  0x000C0000  0x80050000                
rootfs            0xBFCF0000  0xBFCF0000  0x002F0000  0x80050000                
FIS directory     0xBFFE0000  0xBFFE0000  0x0000F000  0x00000000                
RedBoot config    0xBFFEF000  0xBFFEF000  0x00001000  0x00000000     

DD-WRT> fconfig                                                                 
Run script at boot: true                                                        
Boot script:                                                                    
.. fis load -l -c linux                                                         
.. go 0x80274000                                                                
Enter script, terminate with empty line                                         
>> ^C                                                                           
DD-WRT>

Things to note.

Mem address should be 0x80041000 for the kernel unless you actually compile your linux with a different offset.
On your System.map file you will see that the first symbol is defined at 0x80041000.

I also have "entry" alias to find out what the go address should be.

alias entry='cat  build_*/linux-*/linux-*/System.map |grep "kernel_entry"'

I use that on either 7.09 or the latest trunk of the root kamikaze directory to find out what the kernel_entry address is.  The kernel entry will move around if you reconfigure your kernel and add and remove features.

(Last edited by yoonix on 21 Jul 2008, 19:58)

yoonix wrote:
# bdrestore
# fis init
# fis create -b 0x80041000 -l 0xc0000 -f 0xbfc30000 -e 0x80274000 -n linux
# fis create -b 0 -l 0x2f0000 -n rootfs 
# load -r -b 0x80050000 /tftp/openwrt-atheros-2.6-vmlinux.lzma
# fis write -b 0x80050000 -f 0xbfc30000 -l 0xc0000
# load -r -b 0x80050000 /tftp/openwrt-atheros-2.6-root.jffs2-64k
# fis write -b 0x80050000 -f 0xbfce0000 -l 0x1a0000
# fconfig 
>> fis load -l linux
>> go 0x80274000
>>

I do manually calculate everything. In my shell I use ls -l --block-size=65536 to find out what are each block size.

My fis list output is

DD-WRT> fis list                                                                
Name              FLASH addr  Mem addr    Length      Entry point               
RedBoot           0xBFC00000  0xBFC00000  0x00030000  0x00000000                
linux             0xBFC30000  0x80041000  0x000C0000  0x80050000                
rootfs            0xBFCF0000  0xBFCF0000  0x002F0000  0x80050000                
FIS directory     0xBFFE0000  0xBFFE0000  0x0000F000  0x00000000                
RedBoot config    0xBFFEF000  0xBFFEF000  0x00001000  0x00000000     

DD-WRT> fconfig                                                                 
Run script at boot: true                                                        
Boot script:                                                                    
.. fis load -l -c linux                                                         
.. go 0x80274000                                                                
Enter script, terminate with empty line                                         
>> ^C                                                                           
DD-WRT>

Things to note.

Hi!
  thanks a lot for this detailed instruction.  I have a couple questions about this procedure and regarding how the address are calculated.

1. bdrestore, will that wipe out everything, ie, will I need to load redboot?  I did bdrestore, then loaded the redboot. but from your description, I did not see this being done.  should I start over from bdrestore, or just from "fis create" and reload the kernel?

2.
fis create -b 0x80041000 -l 0xc0000 -f 0xbfc30000 -e 0x80274000 -n linux

the 0x80041000 comes from the first symbol of the image.
how about 0xc0000? I am not getting how you get this
if I did

ls -l --block-size=65536 openwrt-atheros-vmlinux.lzma

and get 11 blocks

-rw-r--r-- 1 torus torus 11 Jul 18 11:48 openwrt-atheros-vmlinux.lzma

would I use 11*65536 = 6BA896? this seems way off from what you have

3.
fis write -b 0x80050000 -f 0xbfce0000 -l 0x1a0000
how did you get 0x1a0000? did you get the number after "load" is complete, and took the 2 numbers and subtract?

4.
how about -n? from the manual, it says

When set, no image data will be written to the flash. Only the FIS directory will be updated.

so should I take it out?

(Last edited by cycrap on 22 Jul 2008, 03:14)

ok, I think I mess the router up a little bit more.

when I did "bdrestore", instead of getting

Board config  found at 0xbfff0000
Radio config  found at 0xbfff00f8
Starting sector program for 0xbffe0000! Please wait!
Starting sector program for 0xbfff0000! Please wait!
Restore completed successfully!!

like before, I get

Board config  found at 0xbff90000
no board config data found!

so does that mean the wireless config. is gone?  I do have another same router. is there a way I can retrieve the info. and somehow loaded into this one.

now when I do the

fis create -b 0x80041000 -l 0xc0000 -f 0xbfc30000 -e 0x8024f000 -n linux
fis create -b 0 -l 0x300000 -f 0xbfce0000 -n rootfs 
load -r -b 0x80050000 /tftproot/openwrt-atheros-vmlinux.lzma
fis write -b 0x80050000 -f 0xbfc30000 -l 0xc0000
load -r -b 0x80050000 /tftproot/openwrt-atheros-root.squashfs
fis write -b 0x80050000 -f 0xbfce0000 -l 0x13ffff

the last "fis write", I get an error

Can't program at region 0xbfe00000: unknown error

could this be the problem of my bdrestore not restoring correctly?

also, I thought "fis create -b 0x80041000 -l 0xc0000 -f 0xbfc30000 -e 0x8024f000 -n linux" would make the linux at memory address 0x80041000.  but when I did "fis list" after the above step is done, under memory address, I am getting 0xbfc30000 instead.

thanks

(Last edited by cycrap on 22 Jul 2008, 03:48)

Ah so many questions.

First of all your board configuration is unique for each board, you maybe be able to use the other board configuration at least it will have a valid configuration may not maximize your radio. If you have JTAG you can get your configuration. If you actually did whole compact flash back up you might have the board configuration.

You have to use something like jtagspi or other jtag tools.

Now the size question 11 block is 65536 * 11. Mine was with some additional options it was 12 blocks which is 0xC0000.

11* 65536 should be 11 * 0x10000.

The file system for JFF format is 26 blocks which is 0x1a0000 in size

Remember all 0xbfxx0000 are your flash address. Your kernel will be loaded by the init script to 0x800410000 and execution will start from your entry. You store your compreesed image at 0xbf address.

Good luck

PS. I never used squash file format. Squash is read only file format and I don't use it.

(Last edited by yoonix on 22 Jul 2008, 06:40)

okey, I think I found out what's going on with this thing
my board info. got wipe out somehow...
on the working router

dump -b 0xbfff0000 -l 0x7f

I get some info about the board, ie,

5311.}..Atheros Ar5315 default.........

and

dump -b 0xbfff00f8 -l 0x100

has some weird text.  and I am assuming this is the radio config. since originally radio_config was found here...

on the bad router, the same content is moved up to 0xbfff0000, which means the board config is gone...

Is there any way I can write back to this section of memory without JTAG?

i don't think red boot allow you to edit the nvram area other than through bdrestore stuff.

you can try to copy the memory image to flash.. but i dont think that works well. redboot pretty much prevent you from overwriting the configuraiton.

redboot won't let me write to nvram area...so any other suggestion? but if redboot won't let me write to that area, how did this happen in the first place?
also, looking at the dmesg from the working one. 
radio_config was found actually on boot up...but madwifi still can't find the hardware. do you know a little bit about this hal stuff?  thanks

Do I know about the HAL stuff? Yes and No.

I know HAL used to fail on mine multiple times in different places until I programmed the last sector with this ROM from somewhere. And it magically fixed my problems.

If you look at my wiki remarks it does fail at the end of the boot. HAL STATUS 5.

I do not know any other way but to using JTAG. You maybe able to change the REDBOOT code to flash the last sector. I think Redboot deleted your Radio Config because somehow it knows how to reset but you may to change the source code to rewrite the configuration area if you don't want to use the JTAG.

Let me know how the progress is going.

yoonix wrote:

I know HAL used to fail on mine multiple times in different places until I programmed the last sector with this ROM from somewhere. And it magically fixed my problems.

If you look at my wiki remarks it does fail at the end of the boot. HAL STATUS 5.

I do not know any other way but to using JTAG. You maybe able to change the REDBOOT code to flash the last sector. I think Redboot deleted your Radio Config because somehow it knows how to reset but you may to change the source code to rewrite the configuration area if you don't want to use the JTAG.

Let me know how the progress is going.

thanks for all the help again.
this ROM, I assume you are talking about  ar2317-nvram.bin from your jtagspi package, right?
I went back to read the discuss you had with zinbatsu, somewhere in there, I read someone says that the redboot from dd-wrt does not support ar2318, maybe that's how my board info got wiped.  now the same post direct me to get a redboot_cobra, is that the one you used?

I can certainly modify redboot to write to the last section (seems to be an easy if check). but which, and where, should I get a reasonable easy to compile and recent redboot?  thanks

if you want to go down the path of modifying redboot, i have no clue how to do it. Ah i think i know where main is on redboot HAHAHAHA.
does your kernel boot up at least with some file structure maybe informing that the hal is not found at the end?

you may look through redboot helps or someone here knows where to modify. i looked at a bit of redboot but it's just horrifying cause redboot is written on top of ecos.

blah.. i rather modify linux kernel than redboot after looking at the code.. linux kernel or madwifi patches are a lot cleaner than redboot source code imho.

good luck!

argh i eat my own word.

i just searched for redboot

http://wiki.openwrt.org/OpenWrtDocs/Har … d9e21847a9

try that link. there are couple of articles you might get about how to mod redboot source code.

(Last edited by yoonix on 23 Jul 2008, 23:39)

I have several of this unit as I wanted to do WDS.

all 3 of them, after I installed redboot and openwrt, was working WITHOUT wireless.  some where in the dmesg output, it says radio config. found, but HAL has a status 1, which is no hardware found.

so on one of these units, I did a bdrestore, and I think that's when the board_config is no longer there. thus, I can't even boot openwrt on this one, only redboot.  that's why I am thinking about modifying redboot to let me write to the nvram area in redboot to just restore the board_config.

one quick question.  On those unit with openwrt running, but no wireless, is there a way for me to write to the nvram? so I can just take the last sector of your board config. and write it to my machine.  thanks

a couple quick question
1. how does the redboot knows the mac address of the board?
I know if the board_config is not wiped, it's at offset 0x60 starting at 0xbfff000
but on the one I had that has the board_config wiped, since I can get into redboot, redboot must contain the MAC address for the board...how did redboot find this?

thanks

(Last edited by cycrap on 24 Jul 2008, 23:38)

if you look at the source code the way kernel detects the board configuration is by looking at 5133 or something like that ascii character at the beginning of the block.

if the kernel doesn't find that key it assumes there isn't any board configuration but redboot might detect it differently.

i don't have a really good environment for the redboot either. that's why i wouldn't go into developing the redboot. i will just build the jtag.. the whole environment and developing on redboot was a mess.

you might be able to ask more info on separate topic on the forum..

http://forum.openwrt.org/viewtopic.php?id=16403

flip through this one maybe? (ah i am asking you to cross post but well.)

good luck.

Yoonix:

yeah, kernel is looking for 5311 {hex code 35 33 31 31}, which is at the beginning of 0xbfff0000, but my broken one has this over written by radio_config, which is usually found at 0xbfff00f8, that's why openwrt is not booting...but redboot can still boot, with ethernet support. what's what makes me wonder where it gets the MAC info, when 0xbfff0060 is already wiped...

Hur:

  I am using the later release than 3314, mainly, madwifi-trunk-3776.  I am not sure the difference between downloading madwifi directly and have openwrt download madwifi.  is it possible for you do do a dump of the last sector of your flash.
ie. if you are in redboot, do

dump -b 0xbfff0000 -l 0xf8 {this should be the board info}
dump -b 0xbfff00f8 -l 0x200 {should be long enough to cover all the radio config}

thanks

This is as far as I can tell looking at the code. I am sure someone can explain it better. I am not a developer merely a user.
The original madwifi was written for the client side of wifi connection. Typically it will have a single connection and connected to main cpu by PCI.
The openwrt one uses ABS (atheros bus system) and it has support for multiple connections and has the functionality of managing multiple connections.

That's what I've learned while trying to apply patches to the later version of madwifi which I gave up cause some parts just didn't make sense.

cycrep, if your redboot still boots maybe the mac address is in redboot config as well instead of nvram only. i haven't looked at it but it's a possibility.

(Last edited by yoonix on 25 Jul 2008, 17:48)

Hi
  Did some of the reply got deleted?
Hur posted his nvram data here last week...was busy and did not copy it down...now I can't find it.
or was I dreaming?

ok, partial success and failure...

I revert back to the older redboot, using dir300redboot.rom, floating somewhere on dd-wrt for people to revert back to original redboot...

using that redboot, there is a fwrite command.  not knowing what it does, I used it to write ar2317-nvram.bin to 0xbfff0000, with entry address set to 0x0

this went okey, except I think some of the fis structure is demaged....
so I downloaded the official firmware from airlink, using the emergency http server from the original redboot, to load this firmware.  and magically, I was able to go back to the airlink's firmware.

now I am back to square one...able to install dd-wrt redboot, and open-wrt... but still no wireless...

but I am finding something that I am not too sure...
I put a printk to print out some info in the source file in linux kernel

linux-atheros/linux-2.6.23.17/arch/mips/atheros/board.c

somehow, in the section that says

ifdef CONFIG_ATHEROS_AR5315

I am getting Atheros AR2315, instead of AR2317 or AR2318

could this be any problem?

(Last edited by cycrap on 1 Aug 2008, 21:45)

nearly a month after I recover the board information somehow...

After I recovered the board information, I just put on dd-wrt, and it worked fine..
Yesterday, I decided to give open-wrt another shot, for some reason, the 7.09 installed, and I got my wireless...

then I turn off the router, turn it back on, and it won't boot into open-wrt. I can see that the router is trying to boot, (the light first come on, that's the redboot, then sits for 5 seconds, then all the lights comes on again, that's when linux is trying to boot)...then it just hung.

when trying to ping the router, I got

------------------------------------------------------------------------
From 192.168.1.2 icmp_seq=1 Destination Host Unreachable
------------------------------------------------------------------------

which I think, just indicates that the machine is not up since my routing take are okey, and I can telnet into the router at redboot fine..

I tried to install open-wrt again, and same error happens again...

so I change back to dd-wrt, which went fine
once I boot into dd-wrt, I saw this in dmesg

---------------------------------------------------------
<5>Creating 8 MTD partitions on "spiflash":
<5>0x00000000-0x00030000 : "RedBoot"
<5>0x00030000-0x003d0000 : "linux"
<5>0x00100000-0x003b0000 : "rootfs"
<5>0x003b0000-0x003d0000 : "ddwrt"
<5>0x003d0000-0x003e0000 : "nvram"
<5>0x003e0000-0x003f0000 : "FIS Directory"
<5>0x003f0000-0x00400000 : "board_config"
<5>0x00030000-0x003e0000 : "fullflash"
---------------------------------------------------------

seems like some of those are left over from openwrt, like the rootfs...

is the nvram part messed up again? how can that happen as I only boot into openwrt once without doing anything....

oh...and I saw this

----------------------------------------------------
<0>scanning for root partition
<0>[0x00000000]
<0>[0x00010000]
<0>[0x00020000]
<0>[0x00030000]
<0>[0x00040000]
<0>[0x00050000]
<0>[0x00060000]
<0>[0x00070000]
<0>[0x00080000]
<0>[0x00090000]
<0>[0x000A0000]
<0>[0x000B0000]
<0>[0x000C0000]
<0>[0x000D0000]
<0>[0x000E0000]
<0>[0x000F0000]
<0>[0x00100000]
<0>
<4>found squashfs at 100000
<0>found RedBoot partition at [0xBFC00000]
<0>found linux partition at [0xBFC30000]
---------------------------------------------------------
The squashfs rootfs was when I created and installed the rootfs in redboot...
where does OpenWRT search for rootfs anyway?

(Last edited by cycrap on 28 Aug 2008, 17:25)

hmm..... sorry you should email me i don't check forums as often as i used to anymore...
is it possible your ip address is configured to openwrt default?