From: Sven Eckelmann <sven.eckelmann@gmx.de>
To: b.a.t.m.a.n@lists.open-mesh.org
Cc: Tim <Timbo2001@web.de>
Subject: Re: [B.A.T.M.A.N.] Problem openWRT "backfire" and "kmod-batman-adv"
Date: Wed, 11 Aug 2010 13:20:04 +0200 [thread overview]
Message-ID: <201008111320.14389.sven.eckelmann@gmx.de> (raw)
In-Reply-To: <4C627FCF.4090303@web.de>
[-- Attachment #1: Type: Text/Plain, Size: 1553 bytes --]
On Wednesday 11 August 2010 12:47:43 Tim wrote:
[...]
> After restarting the network the console says: "segmentation fault" and
> freezes. When doing "reboot" instead the device also freezes and the
> power-led keeps flashing.
> I also tried only changing the config in /etc/config/wireless and
> restarted the device, with the same effect.
>
> In order to make sure the error isn't related to any errors while
> compiling the image, I compiled an Image without the batman-adv package.
> After that I was able to configure the router as usual without any freezes.
Thanks for the steps to reproduce. That should help a little bit.
I don't have hardware here at the moment to test it. So cannot tell what the
problem may be. Maybe another person has some free time to test it and check
for a possible problem (but I don't think that anyone active has a WRT54GL).
what you could try is to setup the stuff by yourself using
http://open-mesh.net/wiki/batman-adv-quick-start-guide and test which command
may cause the problem (when it is batman-adv related).
> As I already mentioned I'm not very used to Linux, so I have not yet
> found a way to connect to the router with serial console without
> building an JTAG-Cable. Is that right?
No, JTAG and serial port are completely unrelated:
http://nuwiki.openwrt.org/oldwiki/OpenWrtDocs/Hardware/Linksys/WRT54GL#serial.port
But yes, you must build something. But it is highly recommended to have some
serial console on embedded devices anyway.
Best regards,
Sven
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2010-08-11 11:20 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.1.1281002401.15834.b.a.t.m.a.n@lists.open-mesh.org>
2010-08-11 10:47 ` [B.A.T.M.A.N.] Problem openWRT "backfire" and "kmod-batman-adv" Tim
2010-08-11 11:14 ` Marek Lindner
2010-08-11 11:20 ` Sven Eckelmann [this message]
2010-08-11 14:23 ` Tim
2010-08-11 14:52 ` Sven Eckelmann
[not found] <mailman.33.1282337388.934.b.a.t.m.a.n@lists.open-mesh.org>
2010-08-21 8:09 ` Tim
2010-08-21 8:15 ` Sven Eckelmann
2010-08-18 6:42 Tim
[not found] ` <201008201211.51847.sven.eckelmann@gmx.de>
[not found] ` <4C6E8B79.7040801@web.de>
2010-08-20 14:44 ` Sven Eckelmann
2010-08-20 15:38 ` Sven Eckelmann
[not found] ` <4C6F5950.8070204@bb.banban.jp>
2010-08-21 6:19 ` Sven Eckelmann
-- strict thread matches above, loose matches on Subject: below --
2010-08-17 9:20 Tim
2010-08-17 9:27 ` Sven Eckelmann
2010-08-17 9:45 ` Tim
2010-08-17 9:51 ` Sven Eckelmann
2010-08-12 18:04 Tim Glaremin
2010-08-13 3:24 ` Sven Eckelmann
2010-08-14 17:26 ` Marek Lindner
2010-08-16 16:51 ` Marek Lindner
2010-08-12 10:14 Tim Glaremin
2010-08-12 10:30 ` Marek Lindner
2010-08-12 10:32 ` Sven Eckelmann
2010-08-04 9:21 Tim
2010-08-04 9:34 ` Sven Eckelmann
2010-08-04 22:03 ` Marek Lindner
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=201008111320.14389.sven.eckelmann@gmx.de \
--to=sven.eckelmann@gmx.de \
--cc=Timbo2001@web.de \
--cc=b.a.t.m.a.n@lists.open-mesh.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox