Re: [OpenWrt-Devel] [OpenWrt] #6812: kamikaze trunk can't start RB433AH
anyone could tell me how to resolve the problem, I want NOT to change my
kamikaze version.
I used the kamikaze r19358.
2010/3/10 OpenWrt openwrt-devel@lists.openwrt.org
#6812: kamikaze trunk can't start RB433AH
+---
Reporter: jete...@… | Owner: developers
Type: defect | Status: closed
Priority: high | Milestone: Kamikaze
Component: base system| Version: Kamikaze trunk
Resolution: worksforme |Keywords:
+---
Changes (by juhosg):
* status: new = closed
* resolution: = worksforme
Comment:
Booting of the intramfs kernel:
{{{
RouterBOOT booter 2.15
RouterBoard 433AH
Authorization: Passed
CPU frequency: 680 MHz
Memory size: 128 MB
Press any key within 4 seconds to enter setup.
RouterBOOT-2.15
What do you want to configure?
d - boot delay
k - boot key
s - serial console
o - boot device
u - cpu mode
f - cpu frequency
r - reset booter configuration
e - format nand
g - upgrade firmware
i - board info
p - boot protocol
x - exit setup
your choice: o - boot device
Select boot device:
* e - boot over Ethernet
n - boot from NAND, if fail then Ethernet
1 - boot Ethernet once, then NAND
o - boot from NAND only
b - boot chosen device
your choice: b - boot chosen device
trying dhcp protocol... OK
resolved mac address 00:1F:D0:3F:39:3C
transfer started .. transfer ok, time=1.51s
setting up elf image... OK
jumping to kernel code
Linux version 2.6.32.9 (juh...@idared) (gcc version 4.3.3 (GCC) ) #12 Tue
Mar 9 21:36:31 CET 2010
bootconsole [early0] enabled
CPU revision is: 00019374 (MIPS 24Kc)
Atheros AR7161 rev 2, CPU:680.000 MHz, AHB:170.000 MHz, DDR:340.000 MHz
Determined physical RAM map:
memory: 0800 @ (usable)
User-defined physical RAM map:
memory: 0800 @ (usable)
Initrd not found or empty - disabling initrd
Zone PFN ranges:
Normal 0x - 0x8000
Movable zone start PFN for each node
early_node_map[1] active PFN ranges
0: 0x - 0x8000
Built 1 zonelists in Zone order, mobility grouping on. Total pages: 32512
Kernel command line: rootfstype=squashfs,yaffs,jffs2 noinitrd
console=ttyS0,115200 console=ttyS0,115200 gpio=4031 HZ=3
4000 mem=128M kmac=00:0C:42:2D:B6:E4 board=433 boot=0
PID hash table entries: 512 (order: -1, 2048 bytes)
Dentry cache hash table entries: 16384 (order: 4, 65536 bytes)
Inode-cache hash table entries: 8192 (order: 3, 32768 bytes)
Primary instruction cache 64kB, VIPT, 4-way, linesize 32 bytes.
Primary data cache 32kB, 4-way, VIPT, cache aliases, linesize 32 bytes
Writing ErrCtl register=00012000
Readback ErrCtl register=00012000
Memory: 125396k/131072k available (2027k kernel code, 5508k reserved, 523k
data, 1336k init, 0k highmem)
SLUB: Genslabs=7, HWalign=32, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
Hierarchical RCU implementation.
NR_IRQS:56
Calibrating delay loop... 452.19 BogoMIPS (lpj=2260992)
Mount-cache hash table entries: 512
NET: Registered protocol family 16
MIPS: machine is MikroTik RouterBOARD 433/AH
registering PCI controller with io_map_base unset
bio: create slab bio-0 at 0
pci :00:00.0: PME# supported from D0 D1 D2 D3hot
pci :00:00.0: PME# disabled
Switching to clocksource MIPS
NET: Registered protocol family 2
IP route cache hash table entries: 1024 (order: 0, 4096 bytes)
TCP established hash table entries: 4096 (order: 3, 32768 bytes)
TCP bind hash table entries: 4096 (order: 2, 16384 bytes)
TCP: Hash tables configured (established 4096 bind 4096)
TCP reno registered
NET: Registered protocol family 1
squashfs: version 4.0 (2009/01/31) Phillip Lougher
Registering mini_fo version $Id$
JFFS2 version 2.2. (NAND) (SUMMARY) © 2001-2006 Red Hat, Inc.
yaffs Mar 9 2010 09:16:07 Installing.
msgmni has been set to 245
io scheduler noop registered
io scheduler deadline registered (default)
Serial: 8250/16550 driver, 1 ports, IRQ sharing disabled
serial8250.0: ttyS0 at MMIO 0x1802 (irq = 11) is a 16550A
console [ttyS0] enabled, bootconsole disabled
console [ttyS0] enabled, bootconsole disabled
NAND flash driver for RouterBoard 4xx series version 0.1.10
NAND SPI clock 28333 kHz (AHB 17 kHz / 6)
FLASH SPI clock 28333 kHz (AHB 17 kHz / 6)
NAND device: Manufacturer ID: 0xad, Chip ID: 0x76 (Hynix NAND 64MiB 3,3V
8-bit)
Scanning device for bad blocks
Creating 3 MTD partitions on NAND 64MiB 3,3V 8-bit:
0x-0x0004 : booter
0x0004-0x0040 : kernel
0x0040-0x0400 : rootfs
mtd: partition rootfs set to be root filesystem
split_squashfs: no squashfs found in
Re: [OpenWrt-Devel] [OpenWrt] #6812: kamikaze trunk can't start RB433AH
On Thu, 2010-03-18 at 16:25 +0800, Yongheng Qi wrote: anyone could tell me how to resolve the problem, I want NOT to change my kamikaze version. I used the kamikaze r19358. Then find the change that fixed the issue and patch your setup yourself. You cannot expect someone to fix your problem if you refuse to accept the logical solution of calling svn up make. Kamikaze trunk is work in progress and you should be willing to upgrade your tree to fix problems. Otherwise, you are on your own. Bas. ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] [PATCH] python: fix wrong zlib headers/libs inclusion
Hi,
Recently, zlib has been enabled for target python (I'm working on host
python zlib support so we can get setuptools working on the host and
simplifying building python packages) but the patch also includes host
headers and libs (directly from /usr/{include,lib}). That breaks
compiling python on x86-64 as it's looking for 32 bits headers/libs that
are not present. Following patch fixes it.
But it's not a perfect patch : for me, at least, zlib.so still isn't
built and is missing when copied to the package. I don't know why, and
the fact that target dynlibs don't appear in the build log (V=99) is
strange ; I see host libs being built, but not target ones. Still, every
target lib (appart from zlib) is built and copied correctly !? Has
anyone a clue on this ? Cc'ing Alexander who submitted the patch
enabling zlib to see if he better succeeds.
Thanks.
Signed-off-by: Benjamin Cama ben...@free.fr
Index: lang/python/patches/110-enable-zlib.patch
===
--- lang/python/patches/110-enable-zlib.patch (revision 20235)
+++ lang/python/patches/110-enable-zlib.patch (working copy)
@@ -5,7 +5,7 @@
# This require zlib 1.1.3 (or later).
# See http://www.gzip.org/zlib/
-#zlib zlibmodule.c -I$(prefix)/include -L$(exec_prefix)/lib -lz
-+zlib zlibmodule.c -I$(prefix)/include -L$(exec_prefix)/lib -lz
++zlib zlibmodule.c -lz
# Interface to the Expat XML parser
#
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH] update xl2tpd to 1.2.5
Committed r20276. Thanks Travis 2010/3/17 Raphaël HUCK r...@cksum.org: Hi, this patch updates xl2tpd to 1.2.5. From the changelog: * Fix initscript for https://bugzilla.redhat.com/show_bug.cgi%3Fid%3D247100 * Fix for two Windows machines behind the same NAT with the same number of l2tp connection attempts since boot [Shinichi Furuso] Changes in this patch: * use PKG_INSTALL:=1 * use standard config file names like in other major distributions * new patch to disable building pfc (which was not installed anyway), removes dependency to libpcap * include a commented sample config file * use INSTALL_CONF instead of INSTALL_DATA + chmod 0600 -Raphael ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] AR7240 switch // was: TP-Link TL-WR741ND: broadcasts on ethernet not reaching CPU
Hi Ulf, On 03/15/2010 11:31 AM, ulf kypke wrote: does this prolific has only 3 lines (rx, tx, ground) and no 3.3volt, if so, use a 1K resistor and connect the tplinks 3.3volt to rx, this might stabilize it. I tried two of the black boxes once sold at c-base (BenQ boot cable). I'd rather try to find and add the Vcc_3V3 line first before adding a pull-up on Rx. an other trick is to use a transformer 12volt power adapter not a ac/dc switching power adapter and if you do this on your laptop, unplug it from ac to run on battery power. with some devices i got better results in this way. Noise on the ground line? I tried a lab power supply instead of the 9V wallplug, no avail. i'm still looking for a very good 3.3v serial adapter, the prolific is not the best one. What about the OTI6858 used in some mobile phone data cables? Unfortunately mine broke recently. I ordered a new cable and got a PL2303 inside (but with a Vcc wire). I got a FTDI FT2232D DIP module here as well - meant to be used in a JTAG/RS232 adapter sometime. But this one still misses the adapter board. Regards, Jörg. ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH] Support for Alice Gate W2+ (aka AliceV3-S1 or Vela) bcm63xx-based routers
I admit, that's may be a pretty hard problem. I would suggest you start with exactly pinpointing the place, where it goes wrong. Enable kernel symbols and such stuff. Maybe you get lucky and it's something simple. Otherwise you would have to compare with the datasheet of the flashchip. Bernhard 2010/3/17 Gianfranco Bauco de_gianfranc...@hotmail.com: @Bernhard Loos The problem is described here https://forum.openwrt.org/viewtopic.php?id=17370p=12 on post #279 I don't know hot to fix it, but at least in this way is easy to circumvent. Ciao. Hotmail: Trusted email with Microsoft’s powerful SPAM protection. Sign up now. ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] [PATCH] mac80211: enable debug option for ath5k
From: Bruno Randolf b...@tt-desk.(none) resent and rebased against current trunk --- package/mac80211/Makefile |3 ++- 1 files changed, 2 insertions(+), 1 deletions(-) diff --git a/package/mac80211/Makefile b/package/mac80211/Makefile index b302419..64cbf28 100644 --- a/package/mac80211/Makefile +++ b/package/mac80211/Makefile @@ -597,7 +597,7 @@ BUILDFLAGS:= \ $(if $(CONFIG_LEDS_TRIGGERS), -DCONFIG_MAC80211_LEDS -DCONFIG_LEDS_TRIGGERS -DCONFIG_B43_LEDS -DCONFIG_B43LEGACY_LEDS -DCONFIG_AR9170_LEDS) \ -DCONFIG_B43_HWRNG -DCONFIG_B43LEGACY_HWRNG \ $(if $(CONFIG_PACKAGE_MAC80211_DEBUGFS),-DCONFIG_MAC80211_DEBUGFS -DCONFIG_ATH9K_DEBUGFS) \ - $(if $(CONFIG_PACKAGE_ATH_DEBUG),-DCONFIG_ATH_DEBUG) \ + $(if $(CONFIG_PACKAGE_ATH_DEBUG),-DCONFIG_ATH_DEBUG -DCONFIG_ATH5K_DEBUG) \ -D__CONFIG_MAC80211_RC_DEFAULT=minstrel \ $(if $(CONFIG_ATH_USER_REGD),-DATH_USER_REGD=1) \ $(if $(CONFIG_PACKAGE_ATH9K_USE_MINSTREL),-DATH9K_USE_MINSTREL) @@ -627,6 +627,7 @@ MAKE_OPTS:= \ CONFIG_B43LEGACY=$(if $(CONFIG_PACKAGE_kmod-b43legacy),m) \ CONFIG_ATH_COMMON=$(if $(CONFIG_PACKAGE_kmod-ath),m) \ CONFIG_ATH_DEBUG=$(if $(CONFIG_PACKAGE_ATH_DEBUG),y) \ + CONFIG_ATH5K_DEBUG=$(if $(CONFIG_PACKAGE_ATH_DEBUG),y) \ CONFIG_ATH5K=$(if $(CONFIG_PACKAGE_kmod-ath5k),m) \ CONFIG_ATH9K=$(if $(CONFIG_PACKAGE_kmod-ath9k),m) \ CONFIG_ATH9K_DEBUGFS=$(if $(CONFIG_PACKAGE_MAC80211_DEBUGFS),y) \ -- 1.6.3.3 ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [OpenWrt] #6812: kamikaze trunk can't start RB433AH
Thanks Bas , because kamikze trunk used linux kernel changed so faster. and my application depend on fixed kernel version. so I can't use svn up. only need resolve the problem. I want to know how to resolve the problem myself. should check which code. Thanks 2010/3/18 Bas Mevissen ab...@basmevissen.nl On Thu, 2010-03-18 at 16:25 +0800, Yongheng Qi wrote: anyone could tell me how to resolve the problem, I want NOT to change my kamikaze version. I used the kamikaze r19358. Then find the change that fixed the issue and patch your setup yourself. You cannot expect someone to fix your problem if you refuse to accept the logical solution of calling svn up make. Kamikaze trunk is work in progress and you should be willing to upgrade your tree to fix problems. Otherwise, you are on your own. Bas. ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel -- Yongheng Qi Mobile: +86 1390 119 7481 ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] WRT160NL new bootloader fix
The WRT160NL gets shipped with a new bootloader since some time, which actually checks the checksum in the trx image header. As the checksummed area includes the jffs2 start marker, this will blow up after first boot. This patch fixes this by adding a new funktion to mtd (fixtrx) which is called in firstboot. Nice patch. I was waiting for something like this since months. Some brcm63xx devices like Pirelli Alice Business Gate 2 Plus (1) and Alice Gate W2+ (2) has the same problem. Can this patch be extended to support this router's CFE bootloader? I'm a WRT160NL user, but I do not have this new hardware revision. However, I am working on some documentation that I hope will be applicable to the new hardware revision. Can anyone comment on when this should make it to subversion (I don't see the patch in Trac yet)? Could someone provide the symptoms of using the new hardware without this change? I understand this as the system will not boot the flash image. Is this correct? Could anyone provide any different markings that identify the new hardware revision from older revisions? Are the changes made transparent to the older hardware revision? That is, will a new build continue to work on the old hardware with no configuration change? Thanks! -- Mike :wq ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] WRT160NL new bootloader fix
On Wed, Mar 17, 2010 at 05:34:33PM +0100, Bernhard Loos wrote: Hello I forgot to svn add the firstboot script, that actually calls mtd to fix the trx, sorry about that. Here is the complete patch again. Bernhard Hello Bernhard, FYI I try your patch on my newer WRT160NL but it lost again the new firmware on boot and just sits waiting for a TFTP put from the network. - Otto ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
