OpenWrt Forum Archive

Topic: Backfire 10.03 Beta

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

hutchman wrote:

Yes, please ... how do I build Backfire from SVN???  Is is just trunk?  I grabbed trunk but couldn't get it to build.

OK, I must have got a bad trunk or something as the last few checkouts have been fine.

I'm good to go now.

Hi there smile

It still don't work in my WL500GP V2

I Flashed it  (with Backfire 10.03 Beta), enabled  the wireless in the config file, reloaded the network configuration and pufff I lost connection with the router.
I also tried with the last snapshot and the result is the same sad
I reboot the router, the AIR led gets on past 2 secs gets off and I can't communicate with the router sad

(Last edited by microcris on 15 Mar 2010, 21:58)

Works great on my D-Link DIR-825. Using a 2GB usbstick as rootfs. Good work! smile

I take it that b43 does not support multiple ESSID / virtual interfaces yet?

EDIT: Boo, this beta seems to be unstable on my Buffalo WHR-G54S. It locks up and reboots itself under simple tasks such as trying to install the QoS scripts package, or attempting to use luci-flash to reflash to an older firmware while keeping the configuration. Backing down to 8.09.2 until a future date.

(Last edited by kode54 on 19 Mar 2010, 16:42)

Nope, doesn't appear to work with WRT54G v1.1. I have two of these devices and it is interesting that on one of the two it shows the wireless interface on the "iwconfig" command but the 2nd one doesn't detect any wireless at all. Weird.

I have a WRT54G v1.0 which works ok with backfire brcm47xx plus kmod-b43legacy.

sbued wrote:

Nope, doesn't appear to work with WRT54G v1.1. I have two of these devices and it is interesting that on one of the two it shows the wireless interface on the "iwconfig" command but the 2nd one doesn't detect any wireless at all. Weird.

I have a WRT54G v1.0 which works ok with backfire brcm47xx plus kmod-b43legacy.

Thanks, I'll try that!

Hi!

I was able to compile and flash the Backfire r20324 on my WRT54GL, which replaced the old Kamikaze 7.09. It basically works ok, but there's some questions I wasn't able to solve:

1. On reboot, WiFi drivers can't find firmware, the same problem as in the post #14 here: https://forum.openwrt.org/viewtopic.php … 032#p89032.

But if i run

wifi down
wifi up

the WiFi loads firmware with no problem and works okay. Is it a bug?

2. How to make WiFi NOT to turn on the SES LED? I want to use it for PPTP connection status, via the PPP up/down scripts (BTW, why there's no standard LEDs in the /sys/class/leds/ path (wlan, power, ses_orange, etc)? I want the SES to blink when the wan is up and to light steady when ppp0 is up - I did it already on DIR-300, very handy).

3. Can't change any switch settings with robocfg, e.g. any command gives same error:

[SOLVED]

P.S. If there is more appropriate topic to for such questions, please suggest.

(Last edited by smokie on 21 Mar 2010, 23:32)

I tried to install the binary version of Backfire 10.3 (I couldn't use openwrt-wrt150n-squashfs.bin 
so i used the openwrt-brcm47xx-squashfs.trx) on a linksys router (WRT150N), however the wireless device is not recognized (even iwconfig doesn't find any wireless devices.).
When I used the kamikaze i needed to install kmod-brcm-wl-mimo package to make the wireless device to be recognized.
Am I doing forgetting to do something?
Sorry for my bad english. If anyone could help me, I would be very grateful.

sbued wrote:

Nope, doesn't appear to work with WRT54G v1.1. I have two of these devices and it is interesting that on one of the two it shows the wireless interface on the "iwconfig" command but the 2nd one doesn't detect any wireless at all. Weird.

I have a WRT54G v1.0 which works ok with backfire brcm47xx plus kmod-b43legacy.

I installed the brcm47xx image from the backfire downloads site and it seems whenever I try to change the network config it reboots and does a firstboot and wipes everything back to defaults. I guess I'll download the latest trunk and see if that behaves any differently.

Void Main wrote:

I installed the brcm47xx image from the backfire downloads site and it seems whenever I try to change the network config it reboots and does a firstboot and wipes everything back to defaults.

I had the same problem, that's because the jffs partition couldn't be created (see logread). So the OpenWrt just has no space to store its settings. But it indeed reboots frequently, I think the Luci is too heavy for the device and the memory is exhausted during configuration actions (or there's too little space in /jffs, don't know). You may try to disable watchdog deamon, but it helps a little - it takes too much time for the device to come to consciousness itself, so rebooting is faster. Ah, and it boots much longer too (comparing to 7.09)...

So, anyone please point me where to look to disable the WiFi-driven SES LED in the sources, I'll do the rest myself (it's a bit annoying, wanna get back the old behavior).

And, though it's a more general question, what chains to use to add VPN pass-through rules to the firewall? I have the rules from my old config, but the firewall here is a bit different.

smokie wrote:
Void Main wrote:

I installed the brcm47xx image from the backfire downloads site and it seems whenever I try to change the network config it reboots and does a firstboot and wipes everything back to defaults.

I had the same problem, that's because the jffs partition couldn't be created (see logread). So the OpenWrt just has no space to store its settings. But it indeed reboots frequently, I think the Luci is too heavy for the device and the memory is exhausted during configuration actions (or there's too little space in /jffs, don't know). You may try to disable watchdog deamon, but it helps a little - it takes too much time for the device to come to consciousness itself, so rebooting is faster. Ah, and it boots much longer too (comparing to 7.09)...

Yeah, I just installed the latest trunk (r20348) and luci doesn't work at all on it. If I try and change something simple in the config and reboot it seems to do a firstboot again.

dmesg shows a lot of these:

Jan  1 00:01:54 OpenWrt user.notice kernel: jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x000e0000: 0x8585 instead
Jan  1 00:01:54 OpenWrt user.notice kernel: jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x000e0004: 0x0c0c instead
Jan  1 00:01:54 OpenWrt user.notice kernel: jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x000e0008: 0xb1b1 instead
Jan  1 00:01:54 OpenWrt user.notice kernel: jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x000e000c: 0x8585 instead

Looks like jffs doesn't even get mounted:

root@OpenWrt:/# df
Filesystem           1K-blocks      Used Available Use% Mounted on
/dev/root                 1920      1920         0 100% /rom
tmpfs                     6704        40      6664   1% /tmp
tmpfs                      512         0       512   0% /dev
root                      6700        64      6636   1% /tmp/root
mini_fo:/tmp/root         1920      1920         0 100% /
Void Main wrote:

Yeah, I just installed the latest trunk (r20348) and luci doesn't work at all on it. If I try and change something simple in the config and reboot it seems to do a firstboot again.

Looks like jffs doesn't even get mounted:

To solve this, I flashed the original LinkSys firmware (damn, how fast it is!), then flashed original 10.03 Beta, it worked ok. So I decided to give it another try, and checked out everything from scratch again. Then it flashed and jffs was mounted correctly. Dunno what was the reason. The mtd table looks strange even now, some regions seem overlapped, but it works. Today was the first day I left it unattended, uptime is 22hrs and counting smile I disabled the lucid though, to give it more memory.

Well, the jffs mounts with the 2.4 kernel but not with the 2.6. I have a v1.1 router too (same as in the bug report) and I think that could possibly be the difference.

I forgot to mention that before flashing Linksys firmware I erased everything except the cfe partition with mtd. And always flashed via CFE TFTP. And now I have successfully working Backfire r20324 (brcm47xx target).

(Last edited by smokie on 22 Mar 2010, 21:49)

I just tried "mtd -r erase linux" followed by a tftp upload of r20348 and I get the same thing:

jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00000000: 0xdede instead
jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00001000: 0xdede instead
jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00010000: 0xdede instead
jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00020000: 0xdede instead
Cowardly refusing to erase blocks on filesystem with no valid JFFS2 nodes
empty_blocks 14, bad_blocks 0, c->nr_blocks 17
Void Main wrote:
jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00000000: 0xdede instead

Mmm, I actually had another error, something about a boundary a partition must start at. Don't remember exactly. Maybe your firmware size is too large?

It's the firmware off the download site so I would think it shouldn't be a problem.

Don't be, RC1 did not yet exist at the time of your post smile

The discussion might have continued from here.