CFE bootloader update

[lfbb]

I've just reupdated my two units without problems but haven't done a nvram wipe, just a reboot after the cfe flash.

The 'odmpid=ASUS' does not appear in your output, meaning what, it is not necessary?

- lfbb

 

[lfbb]

Note that the odmpid var was only added a few releases ago (build 220 if I remember correctly).

That means odmpid is not important and we can even not have it on the CFE?

- lfbb

 

[Pierino]

To Gingernut, so even though I already upgraded the cfe weeks ago and have had no problems, I should do it again?
What changes between the result I got then to the result I would have now?
Is my updated cfe somehow incomplete as it is?
I beg for patience, even though I did it the first time, with help, I don't really understand this process. This tech talk is above my head.

 

[lfbb]

http://forums.smallnetbuilder.com/showpost.php?p=53500&postcount=167

- lfbb

 

[Pierino]

I've done an nvram erase more than once since updating my cfe.

 

[lfbb]

1.0.1.3 CFE fails to init nvram variable "vlan1ports" which is needed by recovery mode.

hookup serial console
CFE >

nvram set vlan1ports="1 2 3 4 8*"
nvram commit

reboot and hold reset button to enter recovery
(192.168.1.1 is up and running again)

http://www.dd-wrt.com/phpBB2/viewtopic.php?p=726576#726576

 

[Pierino]

I'm sorry ifbb, I can't really tell if your responses are to me. Like I said I don't get this technical jargon, I don't understand what "nvram set vlan1ports="1 2 3 4 8*" means.

Bottom line, since my router is already upgraded to the 1.0.1.3 cfe and is functioning, how am I in risk of bricking it if I don't do it again?

 

[RMerlin]

Merlin, did you manage to get this new code to work as expected?

- lfbb

I don't play with the CFE. I have no reason to.

 

[RMerlin]

CFE update script will take all variables from old CFE to new one, no matter US or EU specific.

He wanted to use someone else's CFE to update his router, which would have been a bad idea if both routers weren't from the same region.

 

[jbombs16]

I am currently running merlin latest. I upgraded cfe and my router can boot fine back into merlin.

How do I verify that cfe was upgraded?

If i want to flash the special 64k ddwrt, do I flash from recovery (hold reset while booting up) or can I flash from within merlin?

 

[RMerlin]

I am currently running merlin latest. I upgraded cfe and my router can boot fine back into merlin.

How do I verify that cfe was upgraded?

Run the following through telnet/SSH:

cat /dev/mtd0ro | grep bl_version

If i want to flash the special 64k ddwrt, do I flash from recovery (hold reset while booting up) or can I flash from within merlin?

From recovery.

 

[ryzhov_al]

How do I verify that cfe was upgraded?

You may check CFE version this way:

$ strings /dev/mtd0ro | grep bl_version
bl_version=1.0.1.3

Also, you may check is it updated right by:

$ strings /dev/mtd0ro | grep vlan1ports
vlan1ports=1 2 3 4 8*

If you see only vlan1ports=1 then repeat update with previously saved CFE v.1.0.1.2.

 

[jbombs16]

Thanks for the replies.

I checked the version and it returned:

bl_version = 1.0.1.2

So it did not upgrade.

How and where do I move the upgraded cfe.new to my router so I can perform step 3?

THanks

 

[RogerSC]

I am getting confused by this thread. It seems that people that have already converted their cfe to the new one are wanting an original to convert it again.
Is there a reason for this?
I converted mine and it went well, is there a reason to do it again?
Btw if it is needed I kept my original cfe if anyone needs it.

Pierino, just to let you know, I've sent you a couple of private messages, please look in your PM inbox *smile*.

Thanks.

 

[jakey]

The 'odmpid=ASUS' does not appear in your output, meaning what, it is not necessary?

- lfbb

That means odmpid is not important and we can even not have it on the CFE?

- lfbb

Can someone in the know answer this question please.

because I don't see the 'odmpid=ASUS' either.

[4/4] Checking differences between NVRAM from old and new CFE's
4c4
< bl_version=1.0.1.2
---
> bl_version=1.0.1.3
64d63
< pci/1/1/regrev=3
176d174
< wait_time=3
If you see only two differences: one is for 'bl_version' and second is a new 'odmpid=ASUS' variable then all step are done! New CFE image 'cfe.new' is prepared for flash.

 

[Pierino]

Roger, I have replied to your pm, sorry I didnt see it before. Ifbb, i read yours also and responded.

Thanks to both of you, I am now rolling up my sleeves. I performed the check that ryzhov_al suggested and i get a "vlan1ports=1" returned.

 

[jbombs16]

So i upgraded and checked that it all went well.

I want to flash the special 64k ddwrt but I cannot connect to the router in recovery mode to flash it . I can connect if it boot up normally.

Is there something I need to do after the upgrade besides a reboot?

 

[Pierino]

Here we go again. Lol.
When I run ./cfe_update.sh cfe.original cfe.new in the terminal box I get a
bash: ./cfe_update.sh: no such file directory.

This was hard enough the first time.

Never mind, I hadn't extracted the tgz file to the right directory.
I have the cfe.new again. Hopefully this is the last time.

 

[RogerSC]

Here we go again. Lol.
When I run ./cfe_update.sh cfe.original cfe.new in the terminal box I get a
bash: ./cfe_update.sh: no such file directory.

This was hard enough the first time.

Did you make cfe_update.sh executable:

chmod a+x cfe_update.sh

 

[RogerSC]

Did you make cfe_update.sh executable:

chmod a+x cfe_update.sh

On the other hand, I looked back at previous messages in this thread, make sure that you're in the directory where you put the cfe_update.sh file, as well as making sure that it's executable *smile*.