Gargoyle on Ebay/Vietnam/Japan WZR-HP-G300NH

[Gary.M]

I recently purchased one of these via Ebay. The company selling them have many listings, and the price is good.

It arrived with Buffalo's own firmware and in a search for the elusive "high-power" capability I decided to install Gargoyle.

I had no luck via tftp. The process worked perfectly by following instructions on this forum, with all expected messages etc (from an Ubuntu machine) but after the firmware image was uploaded the router always stayed on the Buffalo firmware.

I next moved to DD-WRT easily via the web interface upgrade using the firmware found on the DD-WRT router database for this router.

Go to http://www.dd-wrt.com/site/support/router-database and enter WZR-HP-G300NH. Select the router and download the "special file for initial flashing" That file installs via the router's web firmware upgrade screen.

From here I used other instructions from this forum...

I set the router up as a gateway and connected it to my cable broadband modem so it had internet access.

Then I telneted into the router and then used this set of commands...

> cd /tmp

> wget http://www.gargoyle-router.com/download ... pgrade.bin

> mtd -e linux -r write gargoyle_1.3.14-ar71xx-wzr-hp-g300nh-squashfs-sysupgrade.bin linux

If you follow this guide I suggest you copy and paste from the above to the terminal to ensure you get everything just right. Leave off the ">" of course.

The terminal window then showed progress... at times it looked as if nothing much was happening, the file writing is eventually indicated by an alternating "e" and "w"

After some 10 minutes or so the router restarted and was happily running Gargoyle.

[TWilliam]

Hello Gary,

Would you be willing to do me a favor? Would you please, via either telnet or ssh, run the following command on your WZR-HP-G300NH and post the output here?

Code: Select all

dmesg | grep rtl_chip

Thanks!

[Gary.M]

Hi, That returned nothing, rtl_chip is not found. So here goes the entire thing. Tell me what you find...



root@Buffalo:~# dmesg
Linux version 2.6.32.27 (eric@Osiris) (gcc version 4.3.3 (GCC) ) #3 Sat May 7 18:07:11 EDT 2011
prom: fw_arg0=00000007, fw_arg1=a3f57fb0, fw_arg2=a3f58480, fw_arg3=00000020
MyLoader: sysp=00000000, boardp=00000000, parts=00000000
bootconsole [early0] enabled
CPU revision is: 00019374 (MIPS 24Kc)
Atheros AR9132 rev 2, CPU:400.000 MHz, AHB:200.000 MHz, DDR:400.000 MHz
Determined physical RAM map:
memory: 04000000 @ 00000000 (usable)
Initrd not found or empty - disabling initrd
Zone PFN ranges:
Normal 0x00000000 -> 0x00004000
Movable zone start PFN for each node
early_node_map[1] active PFN ranges
0: 0x00000000 -> 0x00004000
On node 0 totalpages: 16384
free_area_init_node: node 0, pgdat 802ce1e0, node_mem_map 81000000
Normal zone: 128 pages used for memmap
Normal zone: 0 pages reserved
Normal zone: 16256 pages, LIFO batch:3
Built 1 zonelists in Zone order, mobility grouping on. Total pages: 16256
Kernel command line: rootfstype=squashfs,yaffs,jffs2 noinitrd console=ttyS0,115200 board=WZR-HP-G300NH
PID hash table entries: 256 (order: -2, 1024 bytes)
Dentry cache hash table entries: 8192 (order: 3, 32768 bytes)
Inode-cache hash table entries: 4096 (order: 2, 16384 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=00000000
Readback ErrCtl register=00000000
Memory: 61764k/65536k available (2075k kernel code, 3700k reserved, 416k data, 148k 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... 266.24 BogoMIPS (lpj=1331200)
Mount-cache hash table entries: 512
NET: Registered protocol family 16
MIPS: machine is Buffalo WZR-HP-G300NH
bio: create slab <bio-0> at 0
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: 2048 (order: 2, 16384 bytes)
TCP bind hash table entries: 2048 (order: 1, 8192 bytes)
TCP: Hash tables configured (established 2048 bind 2048)
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 May 7 2011 18:06:47 Installing.
msgmni has been set to 120
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 [ttyS0] enabled, bootconsole disabled
ar91xx-flash ar91xx-flash: 02000000 at 1e000000
ar91xx-flash: Found 1 x16 devices at 0x0 in 16-bit bank
CFI mfr 0x00000001
CFI id 0x00002201
Amd/Fujitsu Extended Query Table at 0x0040
Amd/Fujitsu Extended Query version 1.3.
ar91xx-flash: CFI does not contain boot bank location. Assuming top.
number of CFI chips: 1
cfi_cmdset_0002: Disabling erase-suspend-program due to code brokenness.
ar91xx-flash ar91xx-flash: using static partition mapping
Creating 7 MTD partitions on "ar91xx-flash":
0x000000000000-0x000000040000 : "u-boot"
0x000000040000-0x000000060000 : "u-boot-env"
0x000000060000-0x000000160000 : "kernel"
0x000000160000-0x000001fc0000 : "rootfs"
mtd: partition "rootfs" set to be root filesystem
mtd: partition "rootfs_data" created automatically, ofs=540000, len=1A80000
0x000000540000-0x000001fc0000 : "rootfs_data"
0x000001fc0000-0x000001fe0000 : "user_property"
0x000001fe0000-0x000002000000 : "art"
0x000000060000-0x000001fc0000 : "firmware"
Atheros AR71xx SPI Controller driver version 0.2.4
Realtek RTL8366S ethernet switch driver version 0.2.2
rtl8366s rtl8366s: using GPIO pins 19 (SDA) and 20 (SCK)
rtl8366s rtl8366s: RTL8366 ver. 1 chip found
rtl8366s: probed
eth0: Atheros AG71xx at 0xb9000000, irq 4
eth0: using fixed link parameters
eth1: Atheros AG71xx at 0xba000000, irq 5
eth1: connected to PHY at rtl8366s:04 [uid=001cc960, driver=Realtek RTL8366S]
Atheros AR71xx hardware watchdog driver version 0.1.0
ar71xx-wdt: timeout=15 secs (max=21)
TCP westwood registered
NET: Registered protocol family 17
Bridge firewalling registered
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:3.
Freeing unused kernel memory: 148k freed
Please be patient, while OpenWrt loads ...
input: gpio-buttons as /devices/platform/gpio-buttons/input/input0
Button Hotplug driver version 0.3.1
ar71xx: pll_reg 0xb8050014: 0x1e000100
eth0: link up (1000Mbps/Full duplex)
Registered led device: wzr-hp-g300nhsecurity
Registered led device: wzr-hp-g300nh:green:wireless
Registered led device: wzr-hp-g300nh:green:router
Registered led device: wzr-hp-g300nh:red:diag
Registered led device: wzr-hp-g300nh:blue:usb
mini_fo: using base directory: /
mini_fo: using storage directory: /overlay
eth0: link down
ar71xx: pll_reg 0xb8050014: 0x1e000100
eth0: link up (1000Mbps/Full duplex)
device eth0 entered promiscuous mode
br-lan: port 1(eth0) entering forwarding state
Compat-wireless backport release: compat-wireless-2011-04-14
Backport based on wireless-testing.git master-2011-04-19
cfg80211: Calling CRDA to update world regulatory domain
SCSI subsystem initialized
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
cfg80211: World regulatory domain updated:
cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
cfg80211: (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
cfg80211: (2457000 KHz - 2482000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
cfg80211: (2474000 KHz - 2494000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
cfg80211: (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
cfg80211: (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
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
ieee80211 phy0: Selected rate control algorithm 'minstrel_ht'
ieee80211 phy0: Atheros AR9100 MAC/BB Rev:7 AR2133 RF Rev:a2 mem=0xb80c0000, irq=2
cfg80211: Calling CRDA for country: US
RPC: Registered udp transport module.
RPC: Registered tcp transport module.
RPC: Registered tcp NFSv4.1 backchannel transport module.
PPP generic driver version 2.4.2
Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
ip_tables: (C) 2000-2006 Netfilter Core Team
cfg80211: Regulatory domain changed to country: US
cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
cfg80211: (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2700 mBm)
cfg80211: (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 1700 mBm)
cfg80211: (5250000 KHz - 5330000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
cfg80211: (5490000 KHz - 5600000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
cfg80211: (5650000 KHz - 5710000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
cfg80211: (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 3000 mBm)
NET: Registered protocol family 24
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 (968 buckets, 3872 max)
CONFIG_NF_CT_ACCT is deprecated and will be removed soon. Please use
nf_conntrack.acct=1 kernel parameter, acct=1 nf_conntrack module option or
sysctl net.netfilter.nf_conntrack_acct=1 to enable it.
xt_time: kernel timezone is -0000
Hooked IMQ after mangle on PREROUTING
Hooked IMQ after nat on POSTROUTING
IMQ driver loaded successfully.
Ebtables v2.0 registered
ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
Initializing USB Mass Storage driver...
usbcore: registered new interface driver usb-storage
USB Mass Storage support registered.
usbcore: registered new interface driver ums-alauda
usbcore: registered new interface driver ums-cypress
usbcore: registered new interface driver ums-datafab
usbcore: registered new interface driver ums-freecom
usbcore: registered new interface driver ums-isd200
usbcore: registered new interface driver ums-jumpshot
usbcore: registered new interface driver ums-karma
usbcore: registered new interface driver ums-sddr09
usbcore: registered new interface driver ums-sddr55
usbcore: registered new interface driver ums-usbat
fuse init (API version 7.13)
device wlan0 entered promiscuous mode
br-lan: port 2(wlan0) entering forwarding state
device wlan0 left promiscuous mode
br-lan: port 2(wlan0) entering disabled state
device wlan0 entered promiscuous mode
br-lan: port 2(wlan0) entering forwarding state
device wlan1 entered promiscuous mode
wlan1: authenticate with 00:1c:f0:bc:53:69 (try 1)
wlan1: authenticated
wlan1: associate with 00:1c:f0:bc:53:69 (try 1)
wlan1: RX AssocResp from 00:1c:f0:bc:53:69 (capab=0x421 status=0 aid=1)
wlan1: associated
br-lan: port 3(wlan1) entering forwarding state
ar71xx-wdt: enabling watchdog timer
ipt_bandwidth: timezone shift detected, adjusting
ath: Failed to stop TX DMA!
ath: Failed to stop TX DMA!
root@Buffalo:~#

[TWilliam]

Thanks Gary. I'm presently running dd-WRT on my WZR-HP-G300NH, because Gargoyle does not, and this is why ( DEVS PLEASE TAKE NOTE). This is the piece of information I was after, and what I expected to see:

Realtek RTL8366S ethernet switch driver version 0.2.2
rtl8366s rtl8366s: using GPIO pins 19 (SDA) and 20 (SCK)
rtl8366s rtl8366s: RTL8366 ver. 1 chip found

The boot messages are different due to the different firmwares, but here is the relevant piece of info from my dmesg output:

<0>[ 0.570000] rtl_chip_type_select:RTL8366RB

The RTL8366 is the router switch in these units. Note that yours is identified as a version 1 chip and that it utilizes the driver designated as RTL8366S. Earlier I was running OpenWRT on my unit(on which Gargoyle is built) and it provides a little more dmesg info than dd-WRT. It identifies the switch in my unit as a version 2, which uses the RTL8366RB driver. While a bit more cryptic, you can still see from the bit of output I posted above that this is indeed the driver being used in the dd-WRT firmware.

As far as the OpenWRT devs have been able to determine, this chip revision is the only physical difference between our two units. The OpenWRT firmware image for the WZR-HP-G300NH does not work on units with the version 2 chip (and thus neither does the Gargoyle WZR-HP-G300NH image). However, they currently have an image in trunk, designated WZR-HP-G301NH, which does.

Now to the point of all this: devs, could we PLEASE get an image built against the OpenWRT trunk source that supports this chip revision? I understand the desire to avoid placing any 'non-stable' builds in the main downloads section, but how about at least posting one in the forums with a note indicating where it's built from and why? Myself and I'm sure at least a few others would be very grateful.

Thanks so much for all the hard work!

[DoesItMatter]

What is the hardware revision on your routers?

There should be 2 sets of hex.

Either on the box or router.

For example - I have 2 WZR-HP-G300NH's (actually shipped one off)

1 was - A0 A3

the other one was B0 B0 (I think, have to verify when I get home)

These codes tell what hardware revisions the router is using.

It has been reported the newer WZR-HP-G300NH's
are using different types of chips in them.

[TWilliam]

Hi DoesItMatter, thanks for getting involved.

I believe you are referring to the short alphanumeric sequence that appears on the label on the back of the router that also lists the router's preset SSID and MAC, located to the right of the barcode that's above the SSID?

Mine lists a revision code of F2 A0B.

It has been reported the newer WZR-HP-G300NH's
are using different types of chips in them.

This does indeed appear to be the case, corroborated by the info in my previous post. I've seen indications on the various relevant forums that suggest that the chips using the RTL8366S driver were originally utilized in the U.S. versions of the router and that those needing the RTL8366RB driver were originally the Japanese models. It appears that newer U.S. versions are now using the chip requiring the RTL8366RB driver.

[Gary.M]

The hardware version of the one I have off ebay, and on which I ran the install in the first post is A0 A2.

[jul]

The RTL8366 is the router switch in these units. Note that yours is identified as a version 1 chip and that it utilizes the driver designated as RTL8366S. Earlier I was running OpenWRT on my unit(on which Gargoyle is built) and it provides a little more dmesg info than dd-WRT. It identifies the switch in my unit as a version 2, which uses the RTL8366RB driver. While a bit more cryptic, you can still see from the bit of output I posted above that this is indeed the driver being used in the dd-WRT firmware.

As far as the OpenWRT devs have been able to determine, this chip revision is the only physical difference between our two units. The OpenWRT firmware image for the WZR-HP-G300NH does not work on units with the version 2 chip (and thus neither does the Gargoyle WZR-HP-G300NH image). However, they currently have an image in trunk, designated WZR-HP-G301NH, which does.

Now to the point of all this: devs, could we PLEASE get an image built against the OpenWRT trunk source that supports this chip revision? I understand the desire to avoid placing any 'non-stable' builds in the main downloads section, but how about at least posting one in the forums with a note indicating where it's built from and why? Myself and I'm sure at least a few others would be very grateful.

Thanks so much for all the hard work!

Same issue as you, I come from VietNam.
Please help us