Drivers Scsi free download - CopyTrans Drivers Installer, Adaptec ASPI Drivers, Microsoft DirectX Drivers (Windows 95), and many more programs. Adaptec SCSI RAID 2200S Low-profile dual-channel Adaptec SCSI RAID 2200S is a 64-bit/66MHz Ultra320 RAID controller designed for mid-range and high-density servers. Advanced features include Adaptec's optimized disk utilization, Online Capacity Expansion, RAID Level Migration and full OS support. Part.1 Connecting iSCSI target with Windows iSCSI initiator 1. To launch the iSCSI initiator in Windows 7, please go to Control Panel Administrative Tools. On the iSCSI Initiator Properties page, click on Discovery, enter the IP address of. The video shows how to configure the Buffalo NAS 5000 and 7000 as an iSCSI Target and create multiple targets. It shows how to attach it to a Windows Server.

“We have all our data stored on a Buffalo LinkStation Duo. We had bought a second one about 18 months ago onto which we were going to install a RAID 1 configuration but before getting round to it we received a message saying

Failure – into Emergency Mode

Tried Firmware update as noted in dialogue box. Resulted in message saying:
“Linkstation has booted in Emergency Mode – Updating may have failed Reboot Linkstation”

I would like to recover our photographs and documents etc from these discs
(Raid 0) and install onto our new Linkstation duo”

So, assuming I understand this right, you have 2 Buffalo LinkStation Duo’s. The first is set up as a RAID 0 and is your original system. The second is your new system that you intend to run as a RAID 1 but before you were able to copy your data across from the old system to the new one, the old system failed and went into Emergency Mode. You then noticed that your old LinkStation reported that your firmware was out of date so you performed a firmware update. Now your old LinkStation boots into Emergency Mode and reports that the firmware update failed. You are also unable to access any of your original data?

Ok, it seems that you have two problems here. The first is the original failure that caused the RAID 0 to enter the Emergency Mode in the first place. The second is a result of the failed attempt to upgrade the firmware. Let’s take the second problem first and look at the firmware issue. Firmware is the computer program that runs your hardware, in this case, it’s the program that actually runs the LinkStation. The firmware is not stored on the LinkStation’s hard drives, instead it’s stored on the Linkstation’s motherboard and is independent of the hard drives. Therefore because it has nothing to do with the hard drives, for the sake of data recovery purposes, we can discount this problem. Yes, the failed firmware update is a problem, but is not related to recovering the data, which is the important factor here.

Now let’s concentrate on the original failure – there’s very little information to go on here. No error codes or similar information that identifies or even gives a clue as to the type of problem your LinkStation has. Therefore, we need to turn our attention to the hard drives. Your LinkStation Duo has two hard drives, and because the system is set up as a RAID 0, each file on the LinkStation is split across both drives. This means that 50% of each file resides on the first drive and the other 50% is on the second drive. Because the data is split in this way it means that a failure on either drive will result in the total loss of your data. Recovering the information from just one drive is not enough – the data from both hard drives needs to be recovered and then the files can be carefully pieced back together again.

Troubleshooting

Check the status of each hard drive in the LinkStation’s management utility. To do this, go the the Buffalo’s Web Admin Interface and navigate to System > Storage. Both drives should be visible on the menu screen. If none or only one of the drives is visible in this menu it implies that there’s a serious error on one or both drives. Switch your system off and contact us – the faulty hard drive(s) will have to come into the lab for repair and recovery.

However, if both drives are visible on the Web Admin Interface, you can run the Check Disk utility from the same menu. You’ll notice the front of the LinkStation flash whilst this operation is running and it’ll take several minutes to complete. This will check the health of your hard drives. If this test passes the health of both hard drives is fine and it’s most likely that you have some form of logical corruption on your LinkStation: this is problem with the structure of the data, not the hard drives and as far as the seriousness of problems go, this is often minor and your data should be fully recoverable.

Apple Network & Wireless Cards drivers. If the Check Disk utility does report an error, it will be an error with one or more of the hard drives. Errors like this begin as minor issues but if left untreated, this is a problem that can quickly become worse and will ultimately lead to a loss of data, so it’s best to get the data recovered before the state of the system gets any worse.

See our page on Buffalo NAS recovery here:https://www.dataclinic.co.uk/data-recovery-buffalo-nas-terastation-linkstation/

Supported Versions

Hardware Highlights

Installation

→ Install OpenWrt (generic explanation)

TFTP Recovery

Buffalo Scsi Vs

To perform a TFTP recovery on this model:

• Set a static arp entry for 192.168.11.1 to 02:aa:bb:cc:dd:23
• TFTP the image during the 4 second window and wait

Migrate from DD-WRT to OpenWrt

1. Login to the router via SSH or Telnet
2. Change directory to /tmp and download OpenWrt firmware image file:
3. Overwrite current firmware with the downloaded one:

After flashing, the router should go down for a reboot and return running OpenWrt.

How to recover from a broken firmware

1. • On Fedora, you can do it with:
2. Download the sysupgrade image
   
3. • Set serial device to /dev/ttyUSDB0
   • Save the configuration as default and exit
4. Plugin in the FTDI USB cable that's wired to the router's pins above with router being turned off, start minicom and then turn the router on.
5. Keep pressing Control + C until you see a ar7240> prompt.
6. Find out at which IP address the TFTP server should be running and set up your LAN connection accordingly. By default, your computer should have a static IP address at 192.168.11.1. (use printenv command and ipaddr and serverip properties)
7. Copy the sysupgrade image to RAM. Write down the number of transferred bytes in hex:
   
8. Erase existing firmware (or whatever was there; u-boot won't be erased with this, you're safe; it will take a while.
   
9. Copy the image you uploaded in step 6 to flash memory
   
10. Boot into your, now fully-functional, router! (first boot will take some time)
11. Now flash the same image you downloaded in step 2 but through Open-WRTs administration interface (System > Software > Flash Firmware) and reboot your router.
12. on windows you need to use Teraterm from here https://ttssh2.osdn.jp connect serial @ 115200/8/n/1 power on the router you will see

    when the LED starts blinking you can press ctrl+c to come to u-boot prompt. from here the best way is to upload the image through serial port using y-modem protocol

    after pressing enter the router will be waiting for receiving the firmware, in Teraterm go to menu>file>transfer>ymodem>send then select openwrt-ar71xx-generic-wzr-hp-g450h-jffs2-sysupgrade.bin (which you should have downloaded earlier from http://downloads.openwrt.org/attitude_adjustment/12.09-rc1/ar71xx/generic/openwrt-ar71xx-generic-wzr-hp-g450h-jffs2-sysupgrade.bin)

    it will take 5 to 6 minutes to upload then you can erase flash(ar7240> erase BF060000 BEFFFFFF) then write to flash (ar7240> cp.b 81F00000 BF060000 2D0004) then boot from flash (ar7240> bootm BF060000) you will be greeted with

    after that connect to any LAN port and goto openwrt web interface and flash the latest image.

Hardware

Info

Photos

Buffalo Scsi & Raid Devices Driver Download For Windows Xp

Serial Port and Internal Pictures

see http://www.overclock.net/t/1331611/guide-recovering-a-bricked-buffalo-airstation-n450-router-wzr-hp-g450h for pictures.

Serial Pinout:

Firmware

u-boot default environment

Bootlog

This complete boot sequence shows Buffalo's U-BOOT ver 1.00, its TftpServer timing, and factory default DD-WRT kernel messages while booting up

BUFFALO U-BOOT Ver 1.00 CPU:400MHz, DDR:400MHz, AHB:200MHz AP111 (ar7241 - Virian) U-bootDRAM: 64 MBWAN port disabling: doneTop of RAM usable for U-Boot at: 84000000Reserving 258k for U-Boot at: 83fbc000Reserving 192k for malloc() at: 83f8c000Reserving 44 Bytes for Board Info at: 83f8bfd4Reserving 36 Bytes for Global Data at: 83f8bfb0Reserving 128k for boot params() at: 83f6bfb0Stack Pointer at: 83f6bf98Now running in RAM - U-Boot at: 83fbc000flash bank #0 found 16 MB flash [W25Q128BV, blk:0x10000, sectors:256]flash bank #1 found 16 MB flash [W25Q128BV, blk:0x10000, sectors:256]Flash: 32 MBIn: serialOut: serialErr: serialMemory Test (address line)uboot use 83F6BFB0 - 84000000Memory Test start(0x80000000) end(0x83F00000) size(67108864)Data line test start:0x80000000 pattern 0x00000001 0x00000003 0x00000007 0x0000000F 0x00000005 0x00000015 0x00000055 0xAAAAAAAA Address line test start:0x80000000 len:0x3f00000 pattern 0xAAAAAAAA 0x55555555 Fill test patnum:5 fill Pattern 5555AAAA Writing.. Reading..fill Pattern AAAA5555 Writing.. Reading..fill Pattern 0000FFFF Writing.. Reading..fill Pattern FFFF0000 Writing.. Reading..fill Pattern AAAAAAAA Writing.. Reading..Memory Test OK### buf_ver=[1.00] U-Boot Ver.=[1.00]### build_date(env)=[Apr 6 2011 - 08:52:48] build_date(bin)=[Apr 6 2011 - 08:52:48]ag7240_enet_initialize..Reading MAC Address from ENV(0x83f8c322)No valid address in Flash. Using fixed addressVirian MDC CFG Value > 4: cfg1 0x7 cfg2 0x7114eth0: 02:aa:bb:cc:dd:23athrs16_reg_init: completeeth0 upVirian MDC CFG Value > 4: cfg1 0xf cfg2 0x7214eth1: 00:03:7f:09:0b:adeth1 upeth0 02:AA:BB:CC:DD:23, eth1 00:03:7F:09:0B:ADeth0 link downtftp server(receive) go, waiting:4[sec]eth0 link downLoad address: 0x81f00000TftpServer Timeout;no file was loaded.LAN port disabling: done## Checking Image at bf060000 .. Image Name: MIPS Linux Kernel Image Created: 2011-05-27 10:22:38 UTC Image Type: MIPS Linux Kernel Image (lzma compressed) Data Size: 1016696 Bytes = 992.9 kB Load Address: 80002000 Entry Point: 80006150 Verifying Checksum .. crc32_fw: bf060040 - bf1583b7 (len:000f8378) calc..crc32_fw: range1 bf060040 - bf1583b7OKchange bootargsconsole=ttyS0,115200 root=31:03 rootfstype=jffs2 init=/sbin/init mtdparts=ar7240-nor0:256k(u-boot),64k(u-boot-env),1152k@384k(uImage),6592k@1536k(rootfs),64k@320k(ART),64k@8128k(properties),8192k@8192k(flash1),16384k@16384k(flash2) mem=64M## Booting image at bf060000 .. Image Name: MIPS Linux Kernel Image Created: 2011-05-27 10:22:38 UTC Image Type: MIPS Linux Kernel Image (lzma compressed) Data Size: 1016696 Bytes = 992.9 kB Load Address: 80002000 Entry Point: 80006150 Uncompressing Kernel Image .. OKNo initrd## Transferring control to Linux (at address 80006150) ..## Giving linux memsize in bytes, 67108864Starting kernel ..[ 0.000000] Linux version 2.6.34.9-svn17089 (root@dd-wrt) (gcc version 4.5.2 (Linaro GCC 4.5-2011.02-0) ) #5719 Fri May 27 12:10:20 CEST 2011[ 0.000000] flash_size passed from bootloader = 32[ 0.000000] bootconsole [early0] enabled[ 0.000000] CPU revision is: 00019374 (MIPS 24Kc)Booting AR7240(Python)..[ 0.000000] Determined physical RAM map:[ 0.000000] memory: 04000000 @ 00000000 (usable)[ 0.000000] Zone PFN ranges:[ 0.000000] Normal 0x00000000 -> 0x00004000[ 0.000000] Movable zone start PFN for each node[ 0.000000] early_node_map[1] active PFN ranges[ 0.000000] 0: 0x00000000 -> 0x00004000[ 0.000000] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 16256[ 0.000000] Kernel command line: console=ttyS0,115200 root=1f02 rootfstype=squashfs noinitrd init=/sbin/init[ 0.000000] PID hash table entries: 256 (order: -2, 1024 bytes)[ 0.000000] Dentry cache hash table entries: 8192 (order: 3, 32768 bytes)[ 0.000000] Inode-cache hash table entries: 4096 (order: 2, 16384 bytes)[ 0.000000] Primary instruction cache 64kB, VIPT, 4-way, linesize 32 bytes.[ 0.000000] Primary data cache 32kB, 4-way, VIPT, cache aliases, linesize 32 bytes[ 0.000000] Writing ErrCtl register=00000000[ 0.000000] Readback ErrCtl register=00000000[ 0.000000] Memory: 61804k/65536k available (2171k kernel code, 3732k reserved, 541k data, 148k init, 0k highmem)[ 0.000000] NR_IRQS:128[ 0.000000] Calibrating delay loop.. 266.24 BogoMIPS (lpj=1331200)[ 0.240000] Mount-cache hash table entries: 512[ 0.240000] NET: Registered protocol family 16[ 0.250000] found calibration data for slot 0 on 0xBF050000[ 0.460000] registering PCI controller with io_map_base unset[ 0.470000] bio: create slab <bio-0> at 0[ 0.480000] usbcore: registered new interface driver usbfs[ 0.480000] usbcore: registered new interface driver hub[ 0.490000] usbcore: registered new device driver usb[ 0.490000] detected swapped eeprom data[ 0.490000] pci 0000:00:00.0: fixup device configuration[ 0.500000] bootstrap returns device 168C:30[ 0.500000] move calibration data offset 12288[ 0.510000] pci 0000:00:00.0: BAR 0: assigned [mem 0x10000000-0x1001ffff 64bit][ 0.510000] pci 0000:00:00.0: BAR 0: set to [mem 0x10000000-0x1001ffff 64bit] (PCI address [0x10000000-0x1001ffff][ 0.520000] pci 0000:00:00.0: BAR 6: assigned [mem 0x10020000-0x1002ffff pref][ 0.520000] PCI: mapping irq 48 to pin1@0000:00:00.0[ 0.530000] fixup irq: got 48[ 0.530000] Switching to clocksource MIPS[ 0.540000] NET: Registered protocol family 2[ 0.540000] IP route cache hash table entries: 1024 (order: 0, 4096 bytes)[ 0.540000] TCP established hash table entries: 2048 (order: 2, 16384 bytes)[ 0.550000] TCP bind hash table entries: 2048 (order: 1, 8192 bytes)[ 0.550000] TCP: Hash tables configured (established 2048 bind 2048)[ 0.560000] TCP reno registered[ 0.560000] UDP hash table entries: 256 (order: 0, 4096 bytes)[ 0.570000] UDP-Lite hash table entries: 256 (order: 0, 4096 bytes)[ 0.570000] NET: Registered protocol family 1[ 0.580000] gpio_proc: module loaded and /proc/gpio/ created[ 0.590000] wl0gpio_proc: module loaded and /proc/wl0gpio/ created[ 0.590000] init_vdso successfull[ 0.600000] squashfs: version 3.0 (2006/03/15) Phillip Lougher[ 0.600000] msgmni has been set to 120[ 0.610000] io scheduler noop registered[ 0.610000] io scheduler deadline registered (default)[ 0.620000] Serial: 8250/16550 driver, 1 ports, IRQ sharing disabled[ 0.630000] serial8250.0: ttyS0 at MMIO 0x18020000 (irq = 19) is a 16550A[ 0.630000] console [ttyS0] enabled, bootconsole disabled[ 0.630000] console [ttyS0] enabled, bootconsole disabled[ 0.640000] check spi banks 2[ 0.650000] 0000 : EF 40 18[ 0.650000] found W25Q128BV device on bank#0[ 0.650000] 0000 : EF 40 18[ 0.660000] found W25Q128BV device on bank#1[ 0.660000] SPI flash size total:32 Mbytes[ 0.730000] [ 0.730000] found squashfs at 159000[ 0.740000] Creating 9 MTD partitions on 'ar7240-nor0':[ 0.740000] 0x000000000000-0x000000050000 : 'RedBoot'[ 0.750000] 0x000000060000-0x000001fe0000 : 'linux'[ 0.760000] 0x000000159000-0x000000df0000 : 'rootfs'[ 0.760000] mtd: partition 'rootfs' must either start or end on erase block boundary or be smaller than an erase block -- forcing read-only[ 0.780000] mtd: partition 'rootfs' set to be root filesystem[ 0.780000] 0x000000df0000-0x000001fe0000 : 'ddwrt'[ 0.790000] 0x000001fe0000-0x000001ff0000 : 'nvram'[ 0.790000] 0x000001ff0000-0x000002000000 : 'FIS directory'[ 0.800000] 0x000001ff0000-0x000002000000 : 'board_config'[ 0.810000] 0x000000000000-0x000002000000 : 'fullflash'[ 0.810000] 0x000000040000-0x000000050000 : 'uboot-env'[ 0.820000] PPP generic driver version 2.4.2[ 0.820000] PPP Deflate Compression module registered[ 0.830000] PPP BSD Compression module registered[ 0.830000] PPP MPPE Compression module registered[ 0.840000] NET: Registered protocol family 24[ 0.840000] PPPoL2TP kernel driver, V1.0[ 0.850000] IMQ driver loaded successfully.[ 0.850000] Hooking IMQ before NAT on PREROUTING.[ 0.860000] Hooking IMQ after NAT on POSTROUTING.[ 0.860000] tun: Universal TUN/TAP device driver, 1.6[ 0.870000] tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>[ 0.870000] AG7240: Length per segment 1544[ 0.880000] AG7240: Max segments per packet 1[ 0.880000] AG7240: Max tx descriptor count 128[ 0.890000] AG7240: Max rx descriptor count 252[ 0.890000] AG7240: fifo cfg 3 01f00140[ 0.900000] AG7240CHH: Mac address for unit 0[ 0.900000] AG7240CHH: ff:ff:ff:ff:ff:ff [ 1.110000] AG7240CHH: Mac address for unit 1[ 1.110000] AG7240CHH: ff:ff:ff:ff:ff:ff [ 1.320000] Software Watchdog Timer: 0.07 initialized. soft_noboot=0 soft_margin=60 sec (nowayout= 0)[ 1.320000] u32 classifier[ 1.330000] input device check on [ 1.330000] Actions configured [ 1.330000] Netfilter messages via NETLINK v0.30.[ 1.340000] nf_conntrack version 0.5.0 (965 buckets, 3860 max)[ 1.350000] CONFIG_NF_CT_ACCT is deprecated and will be removed soon. Please use[ 1.350000] nf_conntrack.acct=1 kernel parameter, acct=1 nf_conntrack module option or[ 1.360000] sysctl net.netfilter.nf_conntrack_acct=1 to enable it.[ 1.370000] nf_conntrack_rtsp v0.6.21 loading[ 1.370000] nf_nat_rtsp v0.6.21 loading[ 1.380000] ip_tables: (C) 2000-2006 Netfilter Core Team[ 1.380000] IPP2P v0.8.2 loading[ 1.380000] TCP westwood registered[ 1.390000] TCP hybla registered[ 1.390000] TCP vegas registered[ 1.390000] NET: Registered protocol family 17[ 1.400000] 802.1Q VLAN Support v1.8 Ben Greear <greearb@candelatech.com>[ 1.410000] All bugs added by David S. Miller <davem@redhat.com>[ 1.490000] VFS: Mounted root (squashfs filesystem) readonly on device 31:2.[ 1.500000] Freeing unused kernel memory: 148k freedstart servicestarting Architecture code for wzrg450starting hotplugJan 1 00:00:03 udevtrigger[195]: parse_config_file: can't open '/etc/udev/udev.conf' as config file: No such file or directorydoneload ATH Ethernet Driverinsmod: ag7100_mod.ko: module not foundconfigure eth0 to 10:6F:3F:25:FD:8D[ 4.280000] ag7240_ring_alloc Allocated 2048 at 0x838c5800[ 4.280000] ag7240_ring_alloc Allocated 4032 at 0x83a01000[ 4.290000] Virian MDC CFG Value > 4[ 4.290000] CFG Board AP96 [ 4.300000] athrs16_reg_init complete.[ 4.300000] Setting PHY..configure vlan1 to 10:6F:3F:25:FD:8Dconfigure vlan2 to 10:6F:3F:25:FD:8Difconfig: SIOCSIFHWADDR: Device or resource busyload ATH 802.11 a/b/g Driverinsmod: ath_hal.ko: module not foundinsmod: ath_pci.ko: module not foundinsmod: ath_ahb.ko: module not foundload ATH9K 802.11n Driver[ 5.550000] Compat-wireless backport release: compat-wireless-2011-05-11-r26927[ 5.560000] Backport based on wireless-testing.git master-2011-05-13insmod: compat_firmware_class.ko: module not found[ 5.850000] cfg80211: Calling CRDA to update world regulatory domain[ 5.980000] cfg80211: World regulatory domain updated:[ 5.990000] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)[ 6.000000] cfg80211: (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)[ 6.000000] cfg80211: (2457000 KHz - 2482000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)[ 6.010000] cfg80211: (2474000 KHz - 2494000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)[ 6.020000] cfg80211: (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)[ 6.030000] cfg80211: (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)[ 6.970000] ieee80211 phy0: Atheros AR9300 Rev:3 mem=0xb0000000, irq=48[ 6.980000] cfg80211: Calling CRDA for country: US[ 7.010000] cfg80211: Regulatory domain changed to country: US[ 7.020000] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)[ 7.030000] cfg80211: (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2700 mBm)[ 7.030000] cfg80211: (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 1700 mBm)[ 7.040000] cfg80211: (5250000 KHz - 5330000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)[ 7.050000] cfg80211: (5490000 KHz - 5600000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)[ 7.060000] cfg80211: (5650000 KHz - 5710000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)[ 7.070000] cfg80211: (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 3000 mBm)/bin/sh: can't create /proc/sys/dev/wifi0/ledpin: nonexistent directory/bin/sh: can't create /proc/sys/dev/wifi0/softled: nonexistent directory/bin/sh: can't create /proc/sys/dev/wifi1/ledpin: nonexistent directory/bin/sh: can't create /proc/sys/dev/wifi1/softled: nonexistent directory[USB] checking..umount: can't umount /mnt: Invalid argumentrmmod: usblp: No such file or directoryrmmod: printer: No such file or directoryrmmod: usb-storage: No such file or directoryrmmod: sd_mod: No such file or directoryrmmod: scsi_wait_scan: No such file or directoryrmmod: scsi_mod: No such file or directoryrmmod: usb-ohci: No such file or directoryrmmod: ohci-hcd: No such file or directoryrmmod: uhci-hcd: No such file or directoryrmmod: usb-uhci: No such file or directoryrmmod: ehci-hcd: No such file or directoryrmmod: usbcore: No such file or directoryrmmod: xfs: No such file or directoryrmmod: msdos: No such file or directoryrmmod: vfat: No such file or directoryrmmod: fat: No such file or directoryrmmod: nls_utf8: No such file or directoryrmmod: nls_iso8859-2: No such file or directoryrmmod: nls_iso8859-1: No such file or directoryrmmod: nls_cp437: No such file or directoryrmmod: nls_base: No such file or directoryrmmod: ext3: No such file or directoryrmmod: jbd: No such file or directoryrmmod: ext2: No such file or directoryrmmod: mbcache: No such file or directoryrmmod: fuse: No such file or directory/bin/sh: can't create /proc/sys/net/bridge/bridge-nf-call-arptables: nonexistent directory/bin/sh: can't create /proc/sys/net/bridge/bridge-nf-call-ip6tables: nonexistent directory/bin/sh: can't create /proc/sys/net/bridge/bridge-nf-call-iptables: nonexistent directoryath9k deconfigure_single: phy0 ath0[ 9.670000] device br0 entered promiscuous modekillall: ead: no process killed[ 9.750000] device vlan1 entered promiscuous mode[ 9.760000] device eth0 entered promiscuous mode/bin/sh: ead: not found[ 9.770000] br0: port 1(vlan1) entering learning state[ 9.780000] device br0 left promiscuous mode[ 9.780000] device br0 entered promiscuous mode[ 9.790000] device br0 left promiscuous mode[ 9.800000] device br0 entered promiscuous modeifconfig: ioctl 0x8914 failed: Cannot assign requested addressath9k deconfigure_single: phy0 ath0/bin/sh: can't create /proc/sys/dev/wifi0/superchannel: nonexistent directory/bin/sh: can't create /proc/sys/dev/wifi0/regdomain: nonexistent directory/bin/sh: can't create /proc/sys/dev/wifi0/countrycode: nonexistent directory/bin/sh: can't create /proc/sys/dev/wifi0/outdoor: nonexistent directory/bin/sh: can't create /proc/sys/dev/wifi0/antennagain: nonexistent directory/bin/sh: can't create /proc/sys/dev/wifi0/antennagainsub: nonexistent directory/bin/sh: can't create /proc/sys/dev/wifi0/channelbw: nonexistent directory/bin/sh: can't create /proc/sys/dev/wifi0/channelshift: nonexistent directoryath9k configure_single: phy0 ath0/bin/sh: can't create /sys/kernel/debug/ath9k/phy0/rx_chainmask: nonexistent directory/bin/sh: can't create /sys/kernel/debug/ath9k/phy0/tx_chainmask: nonexistent directorycommand failed: Invalid argument (-22)call mac80211autochannel for interface: ath0mac80211autochannel interface: ath0 frequency: 2412setup ath0 10:6F:3F:25:FD:8DConfiguration file: /tmp/ath0_hostap.conf[ 10.590000] device ath0 entered promiscuous mode[ 10.610000] br0: port 2(ath0) entering learning stateUsing interface ath0 with hwaddr 10:6f:3f:25:fd:8d and ssid '106F3F25FD8D'[ 10.780000] br0: port 1(vlan1) entering forwarding statedevice ath0 is already a member of a bridge; can't enslave it to bridge br0.killall: roaming_daemon: no process killedrmmod: bonding: No such file or directory[ 11.160000] bonding: Ethernet Channel Bonding Driver: v3.6.0 (September 26, 2009)[ 11.170000] bonding: MII link monitoring set to 100 ms[ 11.610000] br0: port 2(ath0) entering forwarding statecp: cannot stat '/tmp/mycron.d/*': No such file or directorycp: cannot stat '/jffs/mycron.d/*': No such file or directorycp: cannot stat '/mmc/mycron.d/*': No such file or directoryrmmod: n_hdlc: No such file or directory[ 12.230000] device vlan2 entered promiscuous mode[ 12.250000] device vlan2 left promiscuous modeSIOCGIFFLAGS: No such deviceath9k radio on: phy-1 ath-1/bin/sh: can't create /proc/sys/dev/wifi0/silent: nonexistent directorySIOCGIFFLAGS: No such deviceSIOCGIFFLAGS: No such deviceSIOCGIFFLAGS: No such device[ 13.830000] etherip: Ethernet over IPv4 tunneling driverrmmod: ipt_webstr: No such file or directoryrmmod: ipt_layer7: No such file or directoryrmmod: ipt_ipp2p: No such file or directoryThe Milkfish Router ServicesERROR: Necessary service setting not found: milkfish_username - aborting.rmmod: ebt_dnat: No such file or directoryrmmod: ebt_snat: No such file or directorykillall: proxywatchdog.sh: no process killedThe Milkfish Router ServicesRestoring SIP ddsubscriber database from NVRAM..rmmod: ebt_mark_m: No such file or directoryrmmod: ebt_mark: No such file or directoryrmmod: ebtable_filter: No such file or directoryEmpty.The Milkfish Router ServicesRestoring SIP ddaliases database from NVRAM..rmmod: ebtable_nat: No such file or directoryEmpty.rmmod: ebtables: No such file or directory/bin/sh: can't create /proc/sys/net/bridge/bridge-nf-call-arptables: nonexistent directory/bin/sh: can't create /proc/sys/net/bridge/bridge-nf-call-ip6tables: nonexistent directory/bin/sh: can't create /proc/sys/net/bridge/bridge-nf-call-iptables: nonexistent directoryrmmod: imq: No such file or directoryumount: can't umount /tmp/smbshare: No such file or directoryrmmod: cifs: No such file or directorykillall: schedulerb.sh: no process killedkillall: shatd: no process killedkillall: wdswatchdog.sh: no process killedDD-WRT v24-sp2 std (c) 2011 NewMedia-NET GmbHRelease: 05/27/11 (SVN revision: 17140)DD-WRT login:

Tags