OpenWrt Forum Archive

Topic: Wrt160nl?

The content of this topic has been archived between 9 Mar 2018 and 6 May 2018. Unfortunately there are posts – most likely complete pages – missing.

linuxjacques wrote:
freezer2k wrote:

Ethernet, wifi and USB are working fine!

Does this mean the switch driver issue is solved?

That's the only thing stopping me from getting one of these.

My guess would be if he said,

freezer2k wrote:

Ethernet, wifi and USB are working fine!

then the switch is was solved. Makes sense right???

(Last edited by mordak on 8 Aug 2009, 00:53)

mordak wrote:
linuxjacques wrote:
freezer2k wrote:

Ethernet, wifi and USB are working fine!

Does this mean the switch driver issue is solved?

That's the only thing stopping me from getting one of these.

My guess would be if he said,

freezer2k wrote:

Ethernet, wifi and USB are working fine!

then the switch is was solved. Makes sense right???

Not necessarily.

If freezer2k was referring to the WAN ethernet port, and it's not connected to the switch chip, your assumption would be incorrect.

IIRC back in the early WRT54G days, sometimes initially the WAN port worked but the other ports did not.

I don't know the port topology of the WRT160NL.

I would just like confirmation from someone who has tried it that the non-WAN ethernet ports work before I buy.

linuxjacques wrote:
mordak wrote:
linuxjacques wrote:

Does this mean the switch driver issue is solved?

That's the only thing stopping me from getting one of these.

My guess would be if he said,

freezer2k wrote:

Ethernet, wifi and USB are working fine!

then the switch is was solved. Makes sense right???

Not necessarily.

If freezer2k was referring to the WAN ethernet port, and it's not connected to the switch chip, your assumption would be incorrect.

IIRC back in the early WRT54G days, sometimes initially the WAN port worked but the other ports did not.

I don't know the port topology of the WRT160NL.

I would just like confirmation from someone who has tried it that the non-WAN ethernet ports work before I buy.

If he tftped, by ethernet cable, the firmware on the the unit and not via serial connection then his only way of knowing if ethernet was working is by being connected by ethernet. I'm not 100% sure but I think tftp is always done over the ethernet connection. Also, I'm new to this Atheros stuff. I've always been a broadcom user so the process is a bit different. Also I'm learning the OpenWrt stuff too I've been using DD-WRT for several years though.

Yes, switch is working now.

freezer2k wrote:

Yes, switch is working now.

I guess my assumption was correct after all.

Here's some dmesg output:  (trunk r17151)

root@OpenWrt:~# dmesg
Linux version 2.6.28.10 (freezer@pioneer) (gcc version 4.1.2) #1 Thu Aug 6 21:38:32 CEST 2009
prom: fw_arg0=00000002, fw_arg1=8006040c, fw_arg2=00000000, fw_arg3=00000000
MyLoader: sysp=aaaa5554, boardp=aaaa5554, parts=aaaa5554
console [early0] enabled
CPU revision is: 00019374 (MIPS 24Kc)
Atheros AR9130 rev 2, CPU:400.000 MHz, AHB:200.000 MHz, DDR:400.000 MHz
Determined physical RAM map:
memory: 02000000 @ 00000000 (usable)
Initrd not found or empty - disabling initrd
Zone PFN ranges:
  Normal   0x00000000 -> 0x00002000
Movable zone start PFN for each node
early_node_map[1] active PFN ranges
    0: 0x00000000 -> 0x00002000
On node 0 totalpages: 8192
free_area_init_node: node 0, pgdat 8027aec0, node_mem_map 81000000
  Normal zone: 64 pages used for memmap
  Normal zone: 0 pages reserved
  Normal zone: 8128 pages, LIFO batch:0
  Movable zone: 0 pages used for memmap
Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 8128
Kernel command line: rootfstype=squashfs,yaffs,jffs2 noinitrd console=ttyS0,115200
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=00000000
Readback ErrCtl register=00000000
PID hash table entries: 128 (order: 7, 512 bytes)
Dentry cache hash table entries: 4096 (order: 2, 16384 bytes)
Inode-cache hash table entries: 2048 (order: 1, 8192 bytes)
Memory: 29692k/32768k available (1819k kernel code, 3076k reserved, 343k data, 136k init, 0k highmem)
SLUB: Genslabs=6, HWalign=32, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
Calibrating delay loop... 266.24 BogoMIPS (lpj=1331200)
Mount-cache hash table entries: 512
net_namespace: 480 bytes
NET: Registered protocol family 16
MIPS: machine is Linksys WRT160NL
ar71xx: using random MAC address for eth0
ar71xx: using random MAC address for eth1
NET: Registered protocol family 2
Switched to high resolution mode on CPU 0
IP route cache hash table entries: 1024 (order: 0, 4096 bytes)
TCP established hash table entries: 1024 (order: 1, 8192 bytes)
TCP bind hash table entries: 1024 (order: 0, 4096 bytes)
TCP: Hash tables configured (established 1024 bind 1024)
TCP reno registered
NET: Registered protocol family 1
squashfs: version 3.0 (2006/03/15) Phillip Lougher
Registering mini_fo version $Id$
JFFS2 version 2.2. (NAND) (SUMMARY)  © 2001-2006 Red Hat, Inc.
yaffs Aug  6 2009 21:34:55 Installing.
msgmni has been set to 57
io scheduler noop registered
io scheduler deadline registered (default)
Serial: 8250/16550 driver1 ports, IRQ sharing disabled
serial8250.0: ttyS0 at MMIO 0x18020000 (irq = 11) is a 16550A
console handover: boot [early0] -> real [ttyS0]
ag71xx_mdio: probed
eth0: Atheros AG71xx at 0xb9000000, irq 4
eth0: connected to 4 PHYs
eth1: Atheros AG71xx at 0xba000000, irq 5
eth1: connected to PHY at 0:04 [uid=001cc852, driver=Generic PHY]
Atheros AR71xx SPI Controller driver version 0.2.4
m25p80 spi0.0: mx25l64 (8192 Kbytes)
spi0.0: searching for MyLoader partition table at offset 0x10000
spi0.0: searching for MyLoader partition table at offset 0x20000
spi0.0: searching for MyLoader partition table at offset 0x30000
spi0.0: searching for MyLoader partition table at offset 0x40000
spi0.0: no MyLoader partition table found
Searching for RedBoot partition table in spi0.0 at offset 0x7e0000
Searching for RedBoot partition table in spi0.0 at offset 0x7f0000
No RedBoot partition table detected in spi0.0
TRX on WRT160NL detected
6 trxpart partitions found on MTD device spi0.0
Creating 6 MTD partitions on "spi0.0":
0x00000000-0x00040000 : "u-boot"
0x00040000-0x00160000 : "kernel"
0x00160000-0x007e0000 : "rootfs"
mtd: partition "rootfs" set to be root filesystem
mtd: partition "rootfs_data" created automatically, ofs=350000, len=490000
0x00350000-0x007e0000 : "rootfs_data"
0x007e0000-0x007f0000 : "nvram"
0x007f0000-0x00800000 : "ART"
0x00040000-0x007e0000 : "firmware"
Atheros AR71xx hardware watchdog driver version 0.1.0
ar71xx-wdt: timeout=15 secs (max=21)
TCP westwood registered
NET: Registered protocol family 17
802.1Q VLAN Support v1.8 Ben Greear <greearb@candelatech.com>
All bugs added by David S. Miller <davem@redhat.com>
VFS: Mounted root (squashfs filesystem) readonly.
Freeing unused kernel memory: 136k freed
Please be patient, while OpenWrt loads ...
mini_fo: using base directory: /
mini_fo: using storage directory: /jffs
ar71xx: pll_reg 0xb8050014: 0x13000a44
eth0: link up (100Mbps/Full duplex)
device eth0 entered promiscuous mode
br-lan: topology change detected, propagating
br-lan: port 1(eth0) entering forwarding state
PPP generic driver version 2.4.2
NET: Registered protocol family 24
cfg80211: Using static regulatory domain info
cfg80211: Regulatory domain: US
    (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
    (2402000 KHz - 2472000 KHz @ 40000 KHz), (600 mBi, 2700 mBm)
    (5170000 KHz - 5190000 KHz @ 40000 KHz), (600 mBi, 2300 mBm)
    (5190000 KHz - 5210000 KHz @ 40000 KHz), (600 mBi, 2300 mBm)
    (5210000 KHz - 5230000 KHz @ 40000 KHz), (600 mBi, 2300 mBm)
    (5230000 KHz - 5330000 KHz @ 40000 KHz), (600 mBi, 2300 mBm)
    (5735000 KHz - 5835000 KHz @ 40000 KHz), (600 mBi, 3000 mBm)
cfg80211: Calling CRDA for country: US
ar71xx: pll_reg 0xb8050018: 0x13000a44
eth1: link up (100Mbps/Full duplex)
SCSI subsystem initialized
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
ath: EEPROM regdomain: 0x0
ath: EEPROM indicates default country code should be used
ath: doing EEPROM country->regdmn map search
ath: country maps to regdmn code: 0x3a
ath: Country alpha2 being used: US
ath: Regpair used: 0x3a
phy0: Selected rate control algorithm 'ath9k_rate_control'
phy0: Atheros AR9100 MAC/BB Rev:0, AR2122 RF Rev:a2, mem=0xb80c0000, irq=2
cfg80211: Calling CRDA for country: US
ip_tables: (C) 2000-2006 Netfilter Core Team
Driver 'sd' needs updating - please use bus_type methods
ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
ar71xx-ehci ar71xx-ehci: Atheros AR91xx built-in EHCI controller
ar71xx-ehci ar71xx-ehci: new USB bus registered, assigned bus number 1
ar71xx-ehci ar71xx-ehci: irq 3, io mem 0x1b000000
ar71xx-ehci ar71xx-ehci: USB 2.0 started, EHCI 1.00
usb usb1: configuration #1 chosen from 1 choice
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 1 port detected
nf_conntrack version 0.5.0 (512 buckets, 2048 max)
usb 1-1: new high speed USB device using ar71xx-ehci and address 2
usb 1-1: configuration #1 chosen from 1 choice
usblp0: USB Bidirectional printer dev 2 if 0 alt 0 proto 2 vid 0x03F0 pid 0x2B17
usbcore: registered new interface driver usblp
Initializing USB Mass Storage driver...
usbcore: registered new interface driver usb-storage
USB Mass Storage support registered.
gpio-buttons driver version 0.1.1
device wlan0 entered promiscuous mode
wlan0: deauthenticating by local choice (reason=3)
ath9k: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x40000020
br-lan: port 2(wlan0) entering disabled state
br-lan: topology change detected, propagating
br-lan: port 2(wlan0) entering forwarding state
ar71xx-wdt: enabling watchdog timer

The MACs for eth0/1 are still random, but this might be a generic ar71xx issue?!

(Last edited by freezer2k on 8 Aug 2009, 13:01)

freezer2k wrote:

Yes, switch is working now.

Great! I'm buying one this weekend.

I updated to trunk r17166 and built a ramdisk image.
Options used in menuconfig were as noted profile WRT160NL.
It tftpbooted fine, then the test:

BusyBox v1.13.4 (2009-08-07 12:27:27 PDT) built-in shell (ash)
Enter 'help' for a list of built-in commands.

  _______                     ________        __
 |       |.-----.-----.-----.|  |  |  |.----.|  |_
 |   -   ||  _  |  -__|     ||  |  |  ||   _||   _|
 |_______||   __|_____|__|__||________||__|  |____|
          |__| W I R E L E S S   F R E E D O M
 KAMIKAZE (bleeding edge, r17166) -------------------
  * 10 oz Vodka       Shake well with ice and strain
  * 10 oz Triple sec  mixture into 10 shot glasses.
  * 10 oz lime juice  Salute!
 ---------------------------------------------------
root@OpenWrt:/# ifconfig br-lan 10.70.1.20 netmask 255.255.255.0
root@OpenWrt:/# ifconfig br-lan
br-lan    Link encap:Ethernet  HWaddr 00:23:69:98:2E:DB
          inet addr:10.70.1.20  Bcast:10.70.1.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:42 errors:0 dropped:0 overruns:0 frame:0
          TX packets:6 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:9114 (8.9 KiB)  TX bytes:1094 (1.0 KiB)

root@OpenWrt:/# ping 10.70.1.1
PING 10.70.1.1 (10.70.1.1): 56 data bytes
64 bytes from 10.70.1.1: seq=0 ttl=64 time=1.162 ms
64 bytes from 10.70.1.1: seq=1 ttl=64 time=1.050 ms
64 bytes from 10.70.1.1: seq=2 ttl=64 time=1.223 ms
^C
--- 10.70.1.1 ping statistics ---
3 packets transmitted, 3 packets received, 0% packet loss
round-trip min/avg/max = 1.050/1.145/1.223 ms
root@OpenWrt:/#

I will do a full squashfs build and flash and test that a bit later
but it seems pretty safe to do so now.  Thanks to whoever did
the code modifications for the switch!

(Last edited by vincentfox on 8 Aug 2009, 19:57)

WARNING:  My attempt to upgrade via web-interface bricked it.

I updated to trunk 17182 and rebuilt for squashfs.

The flash upgrade seemed to accept the header
on the file openwrt-ar71xx-wrt160nl-squashfs.bin
and proceeded to flash it.

On reboot however I get this:

VFS: Cannot open root device "<NULL>" or unknown-block(0,0)
Please append a correct "root=" boot option; here are the available partitions:
1f00             256 mtdblock0 (driver?)
1f01             896 mtdblock1 (driver?)
1f02            6912 mtdblock2 (driver?)
1f03              64 mtdblock3 (driver?)
1f04              64 mtdblock4 (driver?)
1f05            7808 mtdblock5 (driver?)
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)

So need to spend some time tonight/tomorrow unbricking.
At least I have serial console so shouldn't be too tough.

vincentfox wrote:

WARNING:  My attempt to upgrade via web-interface bricked it.

I updated to trunk 17182 and rebuilt for squashfs.

The flash upgrade seemed to accept the header
on the file openwrt-ar71xx-wrt160nl-squashfs.bin
and proceeded to flash it.

On reboot however I get this:

VFS: Cannot open root device "<NULL>" or unknown-block(0,0)
Please append a correct "root=" boot option; here are the available partitions:
1f00             256 mtdblock0 (driver?)
1f01             896 mtdblock1 (driver?)
1f02            6912 mtdblock2 (driver?)
1f03              64 mtdblock3 (driver?)
1f04              64 mtdblock4 (driver?)
1f05            7808 mtdblock5 (driver?)
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)

So need to spend some time tonight/tomorrow unbricking.
At least I have serial console so shouldn't be too tough.

Any luck yet vincentfox?

mordak wrote:

Any luck yet vincentfox?

Houseguest & toddler interfering with my ability to spend uninterrupted time on the problem.
Maybe I'll be able to get to it this evening.  I don't think it's a showstopper issue but I wouldn't
flash the *.bin from web-interface if you don't have serial until it's sorted out.

vincentfox wrote:
mordak wrote:

Any luck yet vincentfox?

Houseguest & toddler interfering with my ability to spend uninterrupted time on the problem.
Maybe I'll be able to get to it this evening.  I don't think it's a showstopper issue but I wouldn't
flash the *.bin from web-interface if you don't have serial until it's sorted out.

Thanks for the hard work.

freezer2k wrote:

Here's some dmesg output:  (trunk r17151)

root@OpenWrt:~# dmesg
Linux version 2.6.28.10 (freezer@pioneer) (gcc version 4.1.2) #1 Thu Aug 6 21:38:32 CEST 2009
..........

Thank you very much, I'm currently hunting my postman carrying this box. I have few questions, note that I have no OpenWrt experience:
1. Tftp through ethernet is sufficient?
2. 802.11n is working?
3. Have you tried client mode? I've read there's some issues dropping bandwidth..

My purpose is to interconnect 2 routers AP <- client (WPA2-EAP). Though thanks to freezer2k I can order the second one without hesitation:)

I see there's been some updates in the trunk I was wondering if any of the above issues have been resolved?

I just ordered up my WRT160NL yesterday. Should have it in a couple days.

Hoping to get serial going so I can start playing around. Any advice on what kits to get?
Is it much the same as the wrt54g? I was looking at AD233BK from compsys1.com.
Or possibly RJ45SA.

Any info would be greatly appreciated.

I'm not sure of the progress vincentfox has made he hasn't posted in about 5 days. I'm still waiting to do an install as i don't have the setup for a serial connection. I'm sure with a bunch of wire and some soldering I could connect a standard jtag header to the micro-jtag on the pcb. It might not be pretty but it should work.

Nokia DKU-5 cable is simplest, surest, and CHEAPEST solution look back a few pages.  These cables are commonly found for $5 US and the DKU-5B version currently made is commonly called a CA-42.  I bought a CA-42 off EBay and opened it up and the board inside is labelled DKU-5B.

(Last edited by vincentfox on 16 Aug 2009, 10:23)

Ah, sorted out simplest rescue procedure back to factory.
This web page was MOST useful:
http://www.cdaniel.de/?cat=6

0) Download latest Linksys firmware store a copy as code.bin
1) Add secondary IP on my desktop so it has IP 192.168.1.10
2) From U-boot enter
upgrade code.bin
3) From PC side enter
tftp -i 192.168.1.1 put code.bin
4) From U-boot enter
go

This nicely restored to factory settings.

I am having another go with trunk 17283.  Takes a while on my old P4 after doing a make clean.

(Last edited by vincentfox on 16 Aug 2009, 10:16)

FAILURE with my own build.  Guess I need to scrutinize
all my build options.  Maybe even wipe SVN and start fresh.

Make clean, then make.  Tried both web upgrade and U-Boot flash.
File I used was openwrt-ar71xx-wrt160nl-squashfs.bin
Still ending the boot with this:

VFS: Mounted root (squashfs filesystem) readonly on device 31:2.
Freeing unused kernel memory: 136k freed
Please be patient, while OpenWrt loads ...
Kernel panic - not syncing: Attempted to kill init!

Full boot text in case someone wants to scrutinize it:

U-Boot 1.1.5 (Mar 10 2009 - 07:34:04)

AP81 (ar7100) U-boot
sri
32 MB
WRT160NL u-boot version: 1.0.0
Top of RAM usable for U-Boot at: 82000000
Reserving 277k for U-Boot at: 81fb8000
Reserving 192k for malloc() at: 81f88000
Reserving 44 Bytes for Board Info at: 81f87fd4
Reserving 36 Bytes for Global Data at: 81f87fb0
Reserving 128k for boot params() at: 81f67fb0
Stack Pointer at: 81f67f98
Now running in RAM - U-Boot at: 81fb8000
id read 0x100000ff
flash size 8MB, sector count = 128
Flash:  8 MB
*** Warning - bad CRC, using default environment

In:    serial
Out:   serial
Err:   serial
Net:   ag7100_enet_initialize...
ag7100 get ethaddr for device eth0
Fetching MAC Address from 0x81feaf20

 --------***** Get the RTL8306SD Manufactory ID=34dc *****-------
 Reg6: speed=0 nway=1 duplex=1
 Reg5: speed=0 nway=0 duplex=0
 Reg1: a1=7fd9 a2=2890 a3=115c a4=2890 a5=0
 Reg1: a1=7fd9 a2=2890 a3=115c a4=2890
 Reg1: a1=7fd9 a2=2890 a3=115c a4=2890
 Reg1: a1=7fd9 a2=2890 a3=115c a4=2890
 Reg1: a1=7fd9 a2=2890 a3=115c a4=2890
eth0: 00:23:69:98:2e:db
eth0 up
eth0
### main_loop entered: bootdelay=1

Hit any key to stop autoboot:  0
## Booting image at bf04003c ...
   Image Name:   MIPS OpenWrt Linux-2.6.30.4
   Created:      2009-08-16   8:27:28 UTC
   Image Type:   MIPS Linux Kernel Image (gzip compressed)
   Data Size:    1142047 Bytes =  1.1 MB
   Load Address: 80060000
   Entry Point:  80060000
   Verifying Checksum ... OK
   Uncompressing Kernel Image ... OK
kernel: org len = 1142047, new len = 1179648
No initrd
## Transferring control to Linux (at address 80060000) ...
## Giving linux memsize in bytes, 33554432

Starting kernel ...

Linux version 2.6.30.4 (vf5@baird) (gcc version 4.1.2) #1 Sun Aug 16 01:26:58 PD
T 2009
console [early0] enabled
CPU revision is: 00019374 (MIPS 24Kc)
Atheros AR9130 rev 2, CPU:400.000 MHz, AHB:200.000 MHz, DDR:400.000 MHz
Determined physical RAM map:
 memory: 02000000 @ 00000000 (usable)
Initrd not found or empty - disabling initrd
Zone PFN ranges:
  Normal   0x00000000 -> 0x00002000
Movable zone start PFN for each node
early_node_map[1] active PFN ranges
    0: 0x00000000 -> 0x00002000
Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 8128
Kernel command line: rootfstype=squashfs,yaffs,jffs2 noinitrd console=ttyS0,1152
00
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=00000000
Readback ErrCtl register=00000000
NR_IRQS:56
PID hash table entries: 128 (order: 7, 512 bytes)
Dentry cache hash table entries: 4096 (order: 2, 16384 bytes)
Inode-cache hash table entries: 2048 (order: 1, 8192 bytes)
Memory: 29536k/32768k available (1913k kernel code, 3232k reserved, 421k data, 1
36k init, 0k highmem)
SLUB: Genslabs=7, HWalign=32, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
Calibrating delay loop... 266.24 BogoMIPS (lpj=1331200)
Mount-cache hash table entries: 512
net_namespace: 528 bytes
NET: Registered protocol family 16
MIPS: machine is Linksys WRT160NL
bio: create slab <bio-0> at 0
NET: Registered protocol family 2
IP route cache hash table entries: 1024 (order: 0, 4096 bytes)
TCP established hash table entries: 1024 (order: 1, 8192 bytes)
TCP bind hash table entries: 1024 (order: 0, 4096 bytes)
TCP: Hash tables configured (established 1024 bind 1024)
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 Aug 16 2009 01:21:03 Installing.
msgmni has been set to 57
alg: No test for lzma (lzma-generic)
alg: No test for stdrng (krng)
io scheduler noop registered
io scheduler deadline registered (default)
Serial: 8250/16550 driver, 1 ports, IRQ sharing disabled
serial8250.0: ttyS0 at MMIO 0x18020000 (irq = 11) is a 16550A
console handover: boot [early0] -> real [ttyS0]
ag71xx_mdio: probed
eth0: Atheros AG71xx at 0xb9000000, irq 4
eth1: Atheros AG71xx at 0xba000000, irq 5
Registering RTL8306SD switch with Chip ID: 0x5988, version: 0x0000
Atheros AR71xx SPI Controller driver version 0.2.4
m25p80 spi0.0: en25p64 (8192 Kbytes)
Searching for RedBoot partition table in spi0.0 at offset 0x7e0000
Searching for RedBoot partition table in spi0.0 at offset 0x7f0000
No RedBoot partition table detected in spi0.0
6 wrt160nl partitions found on MTD device spi0.0
Creating 6 MTD partitions on "spi0.0":
0x000000000000-0x000000040000 : "u-boot"
0x000000040000-0x000000170000 : "kernel"
0x000000170000-0x0000007e0000 : "rootfs"
mtd: partition "rootfs" set to be root filesystem
mtd: partition "rootfs_data" created automatically, ofs=3E0000, len=400000
0x0000003e0000-0x0000007e0000 : "rootfs_data"
0x0000007e0000-0x0000007f0000 : "nvram"
0x0000007f0000-0x000000800000 : "art"
0x000000040000-0x0000007e0000 : "firmware"
Atheros AR71xx hardware watchdog driver version 0.1.0
TCP westwood registered
NET: Registered protocol family 17
802.1Q VLAN Support v1.8 Ben Greear <greearb@candelatech.com>
All bugs added by David S. Miller <davem@redhat.com>
VFS: Mounted root (squashfs filesystem) readonly on device 31:2.
Freeing unused kernel memory: 136k freed
Please be patient, while OpenWrt loads ...
Kernel panic - not syncing: Attempted to kill init!

(Last edited by vincentfox on 16 Aug 2009, 12:14)

SUCCESS flashing the trunk snapshot r17264 file.
Flashed fine both from web console and using the
U-Boot "upgrade code.bin" methods.

BusyBox v1.13.4 (2009-08-14 22:26:48 CDT) built-in shell (ash)
Enter 'help' for a list of built-in commands.

  _______                     ________        __
 |       |.-----.-----.-----.|  |  |  |.----.|  |_
 |   -   ||  _  |  -__|     ||  |  |  ||   _||   _|
 |_______||   __|_____|__|__||________||__|  |____|
          |__| W I R E L E S S   F R E E D O M
 KAMIKAZE (bleeding edge, r17264) -------------------
  * 10 oz Vodka       Shake well with ice and strain
  * 10 oz Triple sec  mixture into 10 shot glasses.
  * 10 oz lime juice  Salute!
 ---------------------------------------------------
root@OpenWrt:/#

Looks like network is there:

root@OpenWrt:/# ifconfig -a
br-lan    Link encap:Ethernet  HWaddr 00:23:69:98:2E:DB
          inet addr:192.168.1.1  Bcast:192.168.1.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:12 errors:0 dropped:0 overruns:0 frame:0
          TX packets:2 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:2705 (2.6 KiB)  TX bytes:814 (814.0 B)

eth0      Link encap:Ethernet  HWaddr 00:23:69:98:2E:DB
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:12 errors:0 dropped:0 overruns:0 frame:0
          TX packets:2 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:2873 (2.8 KiB)  TX bytes:814 (814.0 B)
          Interrupt:4

eth1      Link encap:Ethernet  HWaddr 00:23:69:98:2E:DC
          UP BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)
          Interrupt:5

lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

root@OpenWrt:/#

(Last edited by vincentfox on 16 Aug 2009, 12:14)

Yes that's where I grabbed my snapshot from, it was dated August 13th turned out to be r17264.

I nuked all my trunk, and checked out a fresh copy.  Built r17290 which flashed and booted fine.
Somehow my trunk was messed up leaving you all uncertain for about a week for no need.
I should have thought to try flashing an official trunk snapshot earlier.  What can I say except
I am no developer just an amateur poking around blindly.

BusyBox v1.13.4 (2009-08-16 18:47:04 PDT) built-in shell (ash)
Enter 'help' for a list of built-in commands.

  _______                     ________        __
 |       |.-----.-----.-----.|  |  |  |.----.|  |_
 |   -   ||  _  |  -__|     ||  |  |  ||   _||   _|
 |_______||   __|_____|__|__||________||__|  |____|
          |__| W I R E L E S S   F R E E D O M
 KAMIKAZE (bleeding edge, r17290) -------------------
  * 10 oz Vodka       Shake well with ice and strain
  * 10 oz Triple sec  mixture into 10 shot glasses.
  * 10 oz lime juice  Salute!
 ---------------------------------------------------
root@OpenWrt:/# ifconfig wlan0
wlan0     Link encap:Ethernet  HWaddr 00:03:7F:BE:F5:2D
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:29 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 B)  TX bytes:7743 (7.5 KiB)

Anyhow I think it's relatively "safe" to play with now.
Although IMO you SHOULD have a serial console in
case some build bricks it.  It is SO easy to unbrick it
with the little investment in a console hookup.

After testing out wireless some I will probably swap
it in as my main house router to stress-test.

Need to start a Wiki page entry for it too.

(Last edited by vincentfox on 17 Aug 2009, 06:02)

vincentfox wrote:

Yes that's where I grabbed my snapshot from, it was dated August 13th turned out to be r17264.

I nuked all my trunk, and checked out a fresh copy.  Built r17290 which flashed and booted fine.
Somehow my trunk was messed up leaving you all uncertain for about a week for no need.
I should have thought to try flashing an official trunk snapshot earlier.  What can I say except
I am no developer just an amateur poking around blindly.
Anyhow I think it's fairly "safe" to play with now.

After testing out wireless some I will probably swap
it in as my main house router to stress-test.

Thanks man someone needed to do some work on this router many thanks to you for your time and work. I'll play tomorrow hopefully. It's too late tonight for a work night.

So I sit down thinking to start a Wiki page for WRT160NL.

Find that the Wiki is in some state where it's transitioning to
the "NuWiki" and all the supported hardware pages are still part
of oldwiki and not available for edit.

*sigh*

I found and modified a line in Wikipedia about it:

http://en.wikipedia.org/wiki/Linksys_WR … s#WRT160NL

I also dropped a draft page into the NuWiki inbox:

http://wiki.openwrt.org/inbox/wrt160nl

(Last edited by vincentfox on 17 Aug 2009, 09:15)

vincentfox wrote:

So I sit down thinking to start a Wiki page for WRT160NL.

Find that the Wiki is in some state where it's transitioning to
the "NuWiki" and all the supported hardware pages are still part
of oldwiki and not available for edit.

*sigh*

I found and modified a line in Wikipedia about it:

http://en.wikipedia.org/wiki/Linksys_WR … s#WRT160NL

I also dropped a draft page into the NuWiki inbox:

http://wiki.openwrt.org/inbox/wrt160nl

I agree, that lack of documentation or obsolete howtos is alarming. I had success with this box using serial console, now running yesterdays trunk. Thinking of writing my own detailed howto because all of the documents here on openwrt.org assumes you have knowledge you can find on tens of other pages or forum threads.. awful.

vincentfox: I have a question. How much is your router 802.11n? I managed to get working "open" and "psk2" (according to some info are the only options compatible with 802.11n rate), windows Intel client is showing purple "N", but while connecting it shows 54 Mbps and in detail of connection is "Supported rates" = "1 .. omitted .. and 54 Mbps". Some threads says that ath9k does not show this supported rates properly but using "iperf" I could not rate bandwith more than a bit over 2 MB (17 Mbit). I've tried almost everything, tweaking /etc/config/wireless and different ht_capab or diversity or rxantenna/txantenna or country options but always 2 MB. I know, I should better ask ath9k devel..

(Last edited by nemozny on 17 Aug 2009, 15:26)