On Tuesday 06 April 2010 17:42:12 Florian Fainelli wrote:
> Hi Bruno,
>
> On Monday 05 April 2010 03:23:49 Bruno Randolf wrote:
> > hi!
> >
> > currently PCI is broken on the au1000 platforms.
> >
> > this is also the reason for:
> > https://dev.openwrt.org/ticket/6851
> >
> > in order to debug
Hi,
On 04/06/2010 04:30 PM, Gabor Juhos wrote:
> Nah, it was not "broken". The AR8216 driver was disabled by default because it
> is not usable on the AR913x based boards. The reason behind this is that you
> can't communicate with the switch via the MDIO bus, because its speed is too
> fast for
On Wednesday 07 April 2010 00:48:55 Jo-Philipp Wich wrote:
> Should be fixed by https://dev.openwrt.org/changeset/20733
I saw it just the same time you checked this in.
I´ll build a new Image now and report to you if it works *happy*
Bye
Clemens
signature.asc
Description: This is a digitally si
I have about 2000 of them, I can send you one for a few dollars if you want.
I am also building a few ar2317 based router solutions. I also have an
original dir-300 and a clone dir-300. It turns out that the only way you can
use the ar2317 with linux is by using the tools built for the dir-300. Giv
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Should be fixed by https://dev.openwrt.org/changeset/20733
~ J.
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEUEARECAAYFAku7ulcACgkQdputYINPTPOQlgCXQ2w/oV8mzYs5XLK9v3
On Wednesday 07 April 2010 00:41:52 jason duhamell wrote:
> Do you have a ttl to serial adapter to record the start up log on putty so
> I can see where it chokes at?
No I´m sorry I don´t have one.
Bye
Clemens
signature.asc
Description: This is a digitally signed message part.
_
If you hold reset while booting for about 10 seconds, it should stop it from
booting and go directly to redboot.
On Wed, Apr 7, 2010 at 6:20 AM, Clemens John wrote:
> On Tuesday 06 April 2010 23:31:17 jason duhamell wrote:
> > Can you access Redboot?
>
> Yes I think I can but I´m not getting beh
Do you have a ttl to serial adapter to record the start up log on putty so I
can see where it chokes at?
On Wed, Apr 7, 2010 at 6:37 AM, Clemens John wrote:
> On Wednesday 07 April 2010 00:25:50 jason duhamell wrote:
> > Can you tell me which redboot version you are using?
>
> DD-WRT> version
>
On Wednesday 07 April 2010 00:25:50 jason duhamell wrote:
> Can you tell me which redboot version you are using?
DD-WRT> version
RedBoot(tm) bootstrap and debug environment [ROMRAM]
production release, version "2.1.3" - built 18:43:19, Sep 20 2007
Platform: ap61 (Atheros WiSOC)
Copyright (C) 200
I just have experience with redboot. I havent had a chance to use the new
backfire one yet as I only use gargoyle. I just wanted to help you get to a
redboot prompt so you can recover it.
On Wed, Apr 7, 2010 at 6:26 AM, elektra wrote:
> Hi Clemens,
>
> the problem seems to be related to the Linu
Hi Clemens,
the problem seems to be related to the Linux telnet client. The problem
doesn't occur with putty.
> == Executing boot script in 4.060 seconds - enter ^C to abort
> ^C
> ^C
> ^C
> ^C
> ^C
Cheers,
Elektra
___
openwrt-devel mailing list
openw
Can you tell me which redboot version you are using?
On Wed, Apr 7, 2010 at 6:24 AM, Clemens John wrote:
> On Tuesday 06 April 2010 23:31:17 jason duhamell wrote:
> > Can you access Redboot?
>
> I managed to enter Redboot now.
> I put this in my .telnetrc:
> "192.168.20.81 mode line"
>
> [r...@m
On Tuesday 06 April 2010 23:31:17 jason duhamell wrote:
> Can you access Redboot?
I managed to enter Redboot now.
I put this in my .telnetrc:
"192.168.20.81 mode line"
[r...@myhost ~]# ./redboot.sh
Setting up network
Network setup
Waiting for Redboot to boot. Press CTRL + C to quit
Router Awake
On Tuesday 06 April 2010 23:31:17 jason duhamell wrote:
> Can you access Redboot?
Yes I think I can but I´m not getting behind this:
[r...@myhost floh]# ./redboot.sh
Setting up network
Network setup
Waiting for Redboot to boot. Press CTRL + C to quit
Router Awake
Trying 192.168.20.81...
Conn
Can you access Redboot?
On Wed, Apr 7, 2010 at 5:29 AM, Clemens John wrote:
> Hi,
>
> I´m having massive problems accessing my DLINK DIR-300 after flashing with
> the
> new OpenWrt Backfire 10.03 RC3.
>
> If I use my normal tool to flash the device, I can´t ping the device and
> can´t
> access i
Hi,
I´m having massive problems accessing my DLINK DIR-300 after flashing with the
new OpenWrt Backfire 10.03 RC3.
If I use my normal tool to flash the device, I can´t ping the device and can´t
access it over telnet/ssh/webinterface.
I tried accessing on wan and lan ports on the IP 192.168.1.1
On Tue, 2010-04-06 at 01:49 +, OpenWrt wrote:
> #6852: PPTP wrong gateway detection
> --+-
> Reporter: abr...@… | Owner: cshore
> Type: defect| Status: accepted
> Priority: norm
Jonas Gorski írta:
> Hi,
>
> *sigh* shortly after it got committed to trunk, I think I see how I
> broke ar8216 on ar71xx (actually it was already "broken" before):
Nah, it was not "broken". The AR8216 driver was disabled by default because it
is not usable on the AR913x based boards. The reason
The inclusion of the ar8216 driver in ar71xx most probably broke
networking for those devices.
The ag71xx driver currently unconditionally adds/removes the header
on ar8216 devices independent whether the header is enabled or not.
The ar8216 driver can handle that itself, but needs support by the
Hi,
*sigh* shortly after it got committed to trunk, I think I see how I
broke ar8216 on ar71xx (actually it was already "broken" before):
The header mode gets handled by the ar8216 driver itself, in theory,
but the ar8216_netif_rx never gets called by the ag71xx driver. This
leads to following si
Hi Bruno,
On Monday 05 April 2010 03:23:49 Bruno Randolf wrote:
> hi!
>
> currently PCI is broken on the au1000 platforms.
>
> this is also the reason for:
> https://dev.openwrt.org/ticket/6851
>
> in order to debug this further, does anyone know when the au1000 was
> working last? which kerne
21 matches
Mail list logo
