Hi,

Today we released a new candidate for the upcoming OpenWrt 1.0. Please test this release candidate and report any bugs you find. It is very very important, that the bug report is detailed and that you can reproduce the problem. Always backup your data (/etc/, ipkg package list) and do a clean update with mtd:
mtd -e linux -r write image.trx linux

A bug report _must_ contain the exact router model and a description how we can reproduce the problem. Please make no bug reports when you are using rc2 or older releases. Many many bugs are fixed in the new rc3 images.

If you like to install new software, which is not in white russian, you can use HEAD packages. You can find some binarys here:
http://downloads.openwrt.org/people/wbx/head/packages

Have fun!

OpenWrt Development Team <openwrt-devel@openwrt.org>

I'm having problems with White Russian -RC3 on my Linksys WRT54G V3.1 router.
After flashing openwrt-wrt54g-squashfs.bin from -RC3 to my Linksys, it reboots gracefully (too fast, I would say: the time it takes since the elapses since the DMZ led is turned on till the time it turns off seems much short than with RC2, but I don't know if this is normal or not).

However, I can't access the router through the network. The 4-port switch leds state a network link is detected, but I can't ping the router from neither the usual IP address nor the failsafe (192.168.1.1) IP address.

After crushing my head against the wall, I reflashed White Russian -RC2 and everything has started working properly again.

NOTE: I have customized my NVRAM settings somewhat, and have customized the S45firewall script. Everything else are links to ROM.

Any ideas?

Hi,

I have a Motorola WR850Gv3 which was running rc2.  I reverted to the Motorola firmware (5.13) and tried to update to openwrt-motorola-jffs2-8MB.bin and to openwrt-motorola-squashfs.bin using the web interface.  Both files were renamed to have a .trx extension.

Both rc3 updates bricked the router (no ping, no telnet).  I debricked it both times as in http://forum.openwrt.org/viewtopic.php?id=2048 message #21 to revert to the original firmware.   I also tried using tftp with the rc3 files but had similar results, although with openwrt-motorola-squashfs.bin I was able to ping but not telnet---it was stuck in tftp receive mode.

Then I gave up and successfully reinstalled the rc2 version of openwrt-motorola-squashfs.bin, as described in http://forum.openwrt.org/viewtopic.php?id=2223.  I would have stuck with rc2 originally if I had been able to get it to work in client mode (despite many tutorials, it never worked), but I suppose that's a topic for another thread.

Note also I tried rc3 files from the official site and nbd's site.  So far rc3 is a dead end for me. 

Cheers,
Glenn

Just flashed to a Linksys WRT54GS v1.0 and an Asus WL-500g Deluxe. I used mtd and tftp without any errors.

RC3 is working perfect here so far.

Keep on that good work on OpenWrt!

Btw. Could someone make this thread sticky please.

(Last edited by olli_04 on 15 Sep 2005, 10:01)

I noticed that there was a new static compiled version of mtd in the latest cvs... Are there any risk that "mtd" fails to execute and write the flash after deleting the linux-partition?  Should "mtd-static" be used instead to avoid this problem?

RC3 works perfect on my wrt54gs

thank you guys

It is for older OpenWrt releases or other firmware to update to OpenWrt.

Can you add a serial connection? I have no Motorola WR850Gv3 and can not test. I have no idea what could break this model from rc2->rc3.

How you flashed it? via tftp or mtd? Did you try to get into failsafe mode?

well,
nbd packages were working fine already some weeks

Asus WL-500gx AKA Deluxe works fine (both jffs and squash), if remember after flashing (even tftp or mtd) needs 2 times poweroff before answer ping. Tftp on gx starts listen not 192.168.1.1 but gets addr from lan_ipaddr variable.

Does the firmwares from HEAD be working? I tried, no wireless, no ping on wired ports. Same jffs or squash variants.
BTW same behavior when i make from CVS with defaults

Using tftp is simple: take power off, push and hold reset button, plug power on, wait until power led will flash, release reset button, send firmware using last lan_ipaddr.

I flashed it via TFTP. Now, I'll try to reset my NVRAM and then will try to reflash it using mtd, to see if it works.

OK. It's now working. I reset the NVRAM then reflashed -RC1 via mtd. Thanks!

Just a beginners questions. Is the backup procedure only a measure for security or do i loose my custom configuration when i install rc3. For the time being i am using rc2 with openvpn and rrdcollect, and it would be a pity if i have to install everthing anew

You should make a backup of your filesystem. You will need to reflash and rebuild your writable filesystem when upgrading to RC3, because we don't have an upgrade path with ipkg in place, yet.

Is there any documentation on using the imagebuilder SDK? I want to customize and have been using custome compiles. Unfortunately, I recently upgraded my computer to an AMD 64 running Fedora Core 4 and compiling RC3 locks the whole computer up hard requiring a power reset to recover. Not sure if the problem is with Fedora Core 4 or otherwise.

Thanks

There is documentation for the SDK in the Wiki but not yet for the Image Builder.

OpenWRT SDK Howto:
- http://wiki.openwrt.org/BuildingPackagesHowTo

(Last edited by olli_04 on 15 Sep 2005, 19:21)

It is nice to see change/bug fix log , thanks

Can you explain exactly. Do you tried rc3 and it did not work? Did you tried cvs whiterussian branch and it did not work? Did you try CVS head and it did not work?

Please publish your .config and all trx files from a non-working build. Please, we need exact information and need to reproduce it here.

(Responding to my tale of woe regarding rc3 in message #3):

Hi wbx,

Thanks for the response.  While you are probably too polite to say so, you and I likely have
the same idea of why it didn't work: I probably hosed something.  I'm a newbie to this.
Attaching a serial connection is probably beyond what I can do.  Here is some more info.

I originally bricked it a month ago using rc2 jffs, so I've never been able to get a jffs
version to work.  I expected the rc3 squashfs to work, though.  That it gave me ping
is a good sign, perhaps I didn't wait long enough to see if telnet would come up (I doubt
this since it seemed to be in tftp receive mode).

Do you have to do something special to upgrade, like erasing something first?  I went
squash-rc2 ---tftp---> Motorola 5.13 ---web---> squash-rc3.  Within the Motorola firmware
I reverted to "default settings" before using the web interface to load rc3, but perhaps
something needs to be un/set?  I changed lots of values when trying to get it into client
mode (it would scan but not connect).  When I revert to the Motorola .trx with tftp I have
to first delete the first 8 bytes with a hex editor---is this necessary for the rc3 files?

Thanks for your help!
Cheers,
Glenn

RC1??

Actually I never had a Motorola router. It would be better to switch from one OpenWrt release to another via
mtd. It is very good to delete old stuff. Maybe your TFTP install of the original firmware, does not removed the jffs2 entirely.
This means, the new image (rc3), recognise an old unusable jffs2, and pivot_root fails. The system is not accessable.
Therefore you always should use mtd -e linux to erase the old crap before writing a new image.

Have you tried failsafe mode?

Why your jffs2 images fails? What file you use?
There are Motorola models that use 8 MB flash but an erasesize (flash specific value) of 64 kb. This means that you need to use an image with name jffs2-4MB.
I think this is your problem. But still all the bug reports are very very bad. We need to know which file you have used.

I will stop my support, if you did not include every detail, we need to find a solution for your problem.

Hi!
I experienced some problems with RC3. I'm using a WRT54GSv1.1 and flashed with tftp. Worked fine.
But being in failsafe and invoking 'firstboot' the jffs-block is erased but not populated with links/directories and not mounted as new root but just mounted beneath /jffs and left empty.

The jffs-format takes some time but the link/directory creation completes way too fast (compared to former openwrt versions)

Right now, I've flashed the jffs2-version. Also works fine. But it's mounted read only and I don't know how to unlock it. mount -o remount,rw / lacks a /etc/fstab. Is this a bug, too?

Another one: The default startup script for pptpd residing in /etc/init.d is called 'pptpd' instead of 'SXXpptpd' therefore never executed.

I'm dumb... I meant RC3, of course.

hmm. What firmware you had before?

RTFM. README-00.

It's a feature. We actually did not decide how to handle init scripts. some developer like to only put a working script, but did not name it so that it will be executed on startup. others
install Sxxx startupscripts. We will decide and document a common method before 1.0.

Sry my poor english!
I wanted to say that rc3 and also ealier builds from nbd's directory are working fine! (Asus WL-500gx)

Ready firmwares from head directory I can't get working as described above.
Files compiled myself I will overlook soon, I made them some days ago.

My hope is get working bluetooth connection for palm (still terrible unstable dun and pan).

greetings