Joined: 06 Jun 2006 Posts: 7492 Location: Dresden, Germany
Posted: Mon May 26, 2008 23:41 Post subject:
maybe you're not fast enough. disabling the boot script will just fall back to a default bootscript, but nothing else _________________ "So you tried to use the computer and it started smoking? Sounds like a Mac to me.." - Louis Rossmann https://www.youtube.com/watch?v=eL_5YDRWqGE&t=60s
its not 30$ never include the german vat in your math. its around 24$
consider too that i removed the activation from this build just 6 hours ago. i will provide a activation free version tomorrow, so you can reflash it using the new binaries
I'll wait for tomorrow's version and reflash. I'm confused why I got the activation screen once and now the GUI won't show at all. I guess tomorrow's version will tell me more.
Thanks BrainSlayer and Sash for all your help so far.
It looks like you set your boot script timeout to 300 from one of your post. I think that might cause a bit of a delay loading the script. It's better to set it to 5 or 6.
I'm looking forward to the new binaries myself. I'd love to see the results of all our hard work to get it successfully loaded.
I really appreciate the efforts of everyone on this forum and our site admins. Thank you all.
bbmak wrote:
I think i just brick mine b/c i disable boot up script, and now i cannot access to redboot anymore
Joined: 06 Jun 2006 Posts: 7492 Location: Dresden, Germany
Posted: Tue May 27, 2008 8:23 Post subject:
i just uploaded now the free version _________________ "So you tried to use the computer and it started smoking? Sounds like a Mac to me.." - Louis Rossmann https://www.youtube.com/watch?v=eL_5YDRWqGE&t=60s
I only have telnet access to port 9000 if I hit it early in the power on sequence and ctrl-C within a few seconds of connecting. I have nothing to the default telnet or ssh ports. Nmap shows the host down also.
Something I just noticed. The MAC address on the bottom of the unit doesn't match the one I get when I scan my network. I'm getting a MAC address of 00037ffe0003. That's an Atheros MAC but this is on my LAN and the unit says it should be 00c049xxxxxx. I'm wondering if it was hosed somehow and that's part of the problem.
I think something is wrong with the way DD-WRT writes to flash on this unit. I spent at least 6 hours from 8pm to 2am last night trying to get this working. I must have flashed this thing more than 40 times.
Even if the webgui comes up and you make changes to the system, when you save the changes or write back to the access point, the webgui dies and you have to reflash it to the starting point after the reboot.
I tried flashing the usr bin from inside DD-WRT webgui and it says successful but killed the flash again and it doesn't boot the webgui again.
I'm wondering if DD-WRT is overwriting some memory address or flash area while saving changes and kiling the webgui after reboot.
Anyone else have luck here? Thanks again.
jowski wrote:
Something I just noticed. The MAC address on the bottom of the unit doesn't match the one I get when I scan my network. I'm getting a MAC address of 00037ffe0003. That's an Atheros MAC but this is on my LAN and the unit says it should be 00c049xxxxxx. I'm wondering if it was hosed somehow and that's part of the problem.
When you do a 'fis list' do you have something different from this when the GUI is working? I can't get the GUI at all since the one time a few days back and I'm thinking that there might be an address that the usr5453 bin resides that I don't have.
Quote:
RedBoot> fis list
Name FLASH addr Mem addr Length Entry point
RedBoot 0xBE000000 0xBE000000 0x00050000 0x00000000
RedBoot config 0xBE7C0000 0xBE7C0000 0x00001000 0x00000000
FIS directory 0xBE7D0000 0xBE7D0000 0x00010000 0x00000000
rootfs 0xBE050000 0xBE050000 0x00680000 0x00000000
linux 0xBE6D0000 0x80100000 0x000E0000 0x80100000
nvram 0xBE7B0000 0xBE7B0000 0x00010000 0x00000000
After more countless hours of testing different loading addresses, this works best since the current loading instructions doesn't work for me at all. My head hurts from lack of sleep and I'm pretty tired. This current flash method doesn't corrupt anymore with any setting updates or bin uploads from webgui and the loading works fine using this method. BUT, overall I'm getting lots of WLAN disconnects. I've only been testing WPA2 + AES (PSK with 18 characters) and it doesn't hold a stable connection. I'm not sure if it is with the flashing or memory addresses or a problem in the program.
Anyway... here is it.
ip_address -h xx.xx.xx.xx (where xx.xx.xx.xx is your tftp server)
fis init -f (formatting works best... tried fis delete and erase)
load -r -v -b 0x80100000 root.fs (0x80100000 address works best for loading)
boot script timeout:
5 (if your timing is bad) or 1 (if you want access point to start up quicker)
update: y
reset
Let me know if anyone else has frequent disconnects with WPA2 + AES... almost unusable for me. I can't guarantee that this is the correct way to load the binaries but it's the only way that is working for me. If this is not the correct loading method or addresses, let me know what you find out.
I have to sleep early tonight. Thanks.
jowski wrote:
When you do a 'fis list' do you have something different from this when the GUI is working? I can't get the GUI at all since the one time a few days back and I'm thinking that there might be an address that the usr5453 bin resides that I don't have.
Quote:
RedBoot> fis list
Name FLASH addr Mem addr Length Entry point
RedBoot 0xBE000000 0xBE000000 0x00050000 0x00000000
RedBoot config 0xBE7C0000 0xBE7C0000 0x00001000 0x00000000
FIS directory 0xBE7D0000 0xBE7D0000 0x00010000 0x00000000
rootfs 0xBE050000 0xBE050000 0x00680000 0x00000000
linux 0xBE6D0000 0x80100000 0x000E0000 0x80100000
nvram 0xBE7B0000 0xBE7B0000 0x00010000 0x00000000
After more countless hours of testing different loading addresses, this works best since the current loading instructions doesn't work for me at all. My head hurts from lack of sleep and I'm pretty tired. This current flash method doesn't corrupt anymore with any setting updates or bin uploads from webgui and the loading works fine using this method. BUT, overall I'm getting lots of WLAN disconnects. I've only been testing WPA2 + AES (PSK with 18 characters) and it doesn't hold a stable connection. I'm not sure if it is with the flashing or memory addresses or a problem in the program.
Anyway... here is it.
ip_address -h xx.xx.xx.xx (where xx.xx.xx.xx is your tftp server)
fis init -f (formatting works best... tried fis delete and erase)
load -r -v -b 0x80100000 root.fs (0x80100000 address works best for loading)
boot script timeout:
5 (if your timing is bad) or 1 (if you want access point to start up quicker)
update: y
reset
Let me know if anyone else has frequent disconnects with WPA2 + AES... almost unusable for me. I can't guarantee that this is the correct way to load the binaries but it's the only way that is working for me. If this is not the correct loading method or addresses, let me know what you find out.
I have to sleep early tonight. Thanks.
maybe the are some different hw rev out there...sebatian broaght me to this point
