Also I have problems with microsd card installed into embedded socket on main board...
Quote:
Dec 17 16:27:45 DD-WRT kern.err kernel: ehci_hcd 0000:00:04.1: fatal error
Dec 17 16:27:45 DD-WRT kern.err kernel: ehci_hcd 0000:00:04.1: force halt; handshake b8004014 00004000 00004000 -> -145
Dec 17 16:27:45 DD-WRT kern.err kernel: ehci_hcd 0000:00:04.1: HC died; cleaning up
Dec 17 16:27:45 DD-WRT kern.info kernel: sd 0:0:0:0: [sda] Result: hostbyte=0x07 driverbyte=0x00
Dec 17 16:27:45 DD-WRT kern.warn kernel: end_request: I/O error, dev sda, sector 198656
Dec 17 16:27:45 DD-WRT kern.err kernel: Buffer I/O error on device sda1, logical block 24576
Dec 17 16:27:45 DD-WRT kern.warn kernel: lost page write due to I/O error on sda1
Dec 17 16:27:45 DD-WRT kern.err kernel: Buffer I/O error on device sda1, logical block 24577
Dec 17 16:27:45 DD-WRT kern.warn kernel: lost page write due to I/O error on sda1
Dec 17 16:27:45 DD-WRT kern.err kernel: Buffer I/O error on device sda1, logical block 24578
Dec 17 16:27:45 DD-WRT kern.warn kernel: lost page write due to I/O error on sda1
Dec 17 16:27:45 DD-WRT kern.err kernel: Buffer I/O error on device sda1, logical block 24579
Dec 17 16:27:45 DD-WRT kern.warn kernel: lost page write due to I/O error on sda1
Dec 17 16:27:45 DD-WRT kern.err kernel: Buffer I/O error on device sda1, logical block 24580
Dec 17 16:27:45 DD-WRT kern.info kernel: usb 1-1: USB disconnect, address 2
Dec 17 16:27:45 DD-WRT kern.info kernel: usb 1-1.4: USB disconnect, address 3
Dec 17 16:27:45 DD-WRT kern.err kernel: Aborting journal on device sda1.
Dec 17 16:27:45 DD-WRT kern.warn kernel: __journal_remove_journal_head: freeing b_committed_data
Dec 17 16:27:45 DD-WRT kern.crit kernel: ext3_abort called.
Dec 17 16:27:45 DD-WRT kern.crit kernel: EXT3-fs error (device sda1): ext3_journal_start_sb: Detected aborted journal
Dec 17 16:27:45 DD-WRT kern.crit kernel: Remounting filesystem read-only
Dec 17 16:27:45 DD-WRT kern.err kernel: Buffer I/O error on device sda1, logical block 1
Dec 17 16:27:45 DD-WRT kern.warn kernel: lost page write due to I/O error on sda1
Dec 17 16:27:45 DD-WRT kern.err kernel: Buffer I/O error on device sda1, logical block 942
Dec 17 16:27:45 DD-WRT kern.warn kernel: lost page write due to I/O error on sda1
Dec 17 16:27:45 DD-WRT kern.err kernel: Buffer I/O error on device sda1, logical block 943
Dec 17 16:27:45 DD-WRT kern.warn kernel: lost page write due to I/O error on sda1
Dec 17 16:27:45 DD-WRT kern.info kernel: usb 2-1: new full speed USB device using ohci_hcd and address 2
Dec 17 16:27:46 DD-WRT kern.info kernel: usb 2-1: not running at top speed; connect to a high speed hub
Dec 17 16:27:45 DD-WRT kern.err kernel: ehci_hcd 0000:00:04.1: fatal error
Dec 17 16:27:46 DD-WRT kern.info kernel: hub 2-1:1.0: USB hub found
Dec 17 16:27:46 DD-WRT kern.info kernel: hub 2-1:1.0: 4 ports detected
Dec 17 16:27:46 DD-WRT kern.info kernel: usb 2-1.4: new full speed USB device using ohci_hcd and address 3
Dec 17 16:27:46 DD-WRT kern.info kernel: usb 2-1.4: not running at top speed; connect to a high speed hub
Dec 17 16:27:46 DD-WRT kern.info kernel: usb 2-1.4: configuration #1 chosen from 1 choice
Dec 17 16:27:46 DD-WRT kern.info kernel: scsi1 : SCSI emulation for USB Mass Storage devices
Dec 17 16:27:46 DD-WRT kern.err kernel: scsi 0:0:0:0: rejecting I/O to dead device
Dec 17 16:27:46 DD-WRT kern.crit kernel: EXT3-fs error (device sda1): ext3_find_entry: reading directory #2 offset 0
Dec 17 16:27:46 DD-WRT kern.err kernel: scsi 0:0:0:0: rejecting I/O to dead device
Dec 17 16:27:46 DD-WRT kern.crit kernel: EXT3-fs error (device sda1): ext3_find_entry: reading directory #2 offset 0
Dec 17 16:27:46 DD-WRT kern.err kernel: scsi 0:0:0:0: rejecting I/O to dead device
Dec 17 16:27:46 DD-WRT kern.crit kernel: EXT3-fs error (device sda1): ext3_find_entry: reading directory #2 offset 0
Dec 17 16:27:48 DD-WRT kern.notice kernel: scsi 1:0:0:0: Direct-Access Multi Flash Reader 1.00 PQ: 0 ANSI: 0
Dec 17 16:27:48 DD-WRT kern.err kernel: scsi 0:0:0:0: rejecting I/O to dead device
Dec 17 16:27:49 DD-WRT kern.notice kernel: sd 1:0:0:0: [sdb] 31340544 512-byte hardware sectors (16046 MB)
Dec 17 16:27:49 DD-WRT kern.notice kernel: sd 1:0:0:0: [sdb] Write Protect is off
Dec 17 16:27:49 DD-WRT kern.debug kernel: sd 1:0:0:0: [sdb] Mode Sense: 03 00 00 00
Dec 17 16:27:49 DD-WRT kern.err kernel: sd 1:0:0:0: [sdb] Assuming drive cache: write through
Dec 17 16:27:49 DD-WRT kern.err kernel: sd 1:0:0:0: [sdb] Assuming drive cache: write through
Dec 17 16:27:49 DD-WRT kern.info kernel: /dev/scsi/host1/bus0/target0/lun0: p1 p2
Dec 17 16:27:49 DD-WRT kern.notice kernel: sd 1:0:0:0: [sdb] Attached SCSI removable disk
Dec 17 16:27:50 DD-WRT kern.info kernel: kjournald starting. Commit interval 5 seconds
Dec 17 16:27:50 DD-WRT kern.info kernel: EXT3 FS on sdb1, internal journal
Dec 17 16:27:50 DD-WRT kern.info kernel: EXT3-fs: recovery complete.
Dec 17 16:27:50 DD-WRT kern.info kernel: EXT3-fs: mounted filesystem with ordered data mode.
Dec 17 16:27:53 DD-WRT kern.err kernel: scsi 0:0:0:0: rejecting I/O to dead device
Dec 17 16:28:06 DD-WRT kern.err kernel: scsi 0:0:0:0: rejecting I/O to dead device
Dec 17 16:28:47 DD-WRT kern.err kernel: scsi 0:0:0:0: rejecting I/O to dead device
this card at the same place with asus stock fw worked fine, I used it to backup cfe... _________________ TP-Link TL-WR1043ND: DD-WRT v24-sp2 (08/07/10) std - build 14896
Asus RT-N16: DD-WRT build 19545 (kingmod)
EDIT : If you don't need the 64K NVRAM and are ok with having only 32K NVRAM, then you can simply go here and install the "normal/Official" version of DD-WRT. Be sure however to download the one for your router (RT-N66)
Posted: Wed Dec 19, 2012 22:18 Post subject: Re: Issue
Thank you Crypticone for your report. I think it is the same issue, only MacOS and probably some specific devices can scan and discover a 00:00:00 access point mac address :/. Have you fixed the issue?
Crypticone wrote:
I have an issue that might be the same as yours. Same build and configured as repeater mode. Primary wlan link stays connected and still routes correctly to Ethernet ports. Typically while streaming Netflix to a WD TV live box, the entire virtual network disappears. No SSID showing up, all connected devices dropped. I have not checked the Mac address while this issue is happening. Rebooting does not seem to fix the issue but powering down and back up seems to correct it. I don't stream too often but it seems to happen most while trying to.
Using Fractal 20202 mega with CFE 64k, the middle one (12-2) not the newest one (12-4).
Crypticone
Thireus wrote:
Hi everyone,
I have a big issue to report:
I'm using Fractal 64k build on my Asus RT-N66U B1 router with repeater mode enabled for the 2.4GHz Antenna. I also have created a virtual Access Point on the 2.4GHz antenna and after a random period of time the MAC address of this virtual AP changes definitely to 00:00:00:00:00:00 (this issue is only for the Virtual Mac AP, not the Physical Mac AP).
DD-WRT v24-sp2 (10/31/12) mega - build 20202
Anyone has the same issue? How can I fix this? Any ways to fix the mac adress?
Joined: 14 Dec 2012 Posts: 15 Location: Québec, Canada
Posted: Thu Dec 20, 2012 0:57 Post subject:
damaster wrote:
If I have a brand new router and update to the latest Asus firmware, and then run the cfe_update script, will that take care of backing up my old CFE?
Yes if you read carefully the 3rd point on SmallNetBuilder :
ryzhov_al wrote:
3. Saving old CFE image
Please consider saving your old CFE. A ./cfe.old file will be placed in the same dir with update script, save it to some safe place.
_________________ Passion rules reason, for better or for worse...
So stop tearing your hair out, take a deep breath and find the solution to your problem
and how to make 5GHz wifi network to work on build 20363?
on stock fw it works... may be some additional configuration needed or region specific channel selection or whatever? _________________ TP-Link TL-WR1043ND: DD-WRT v24-sp2 (08/07/10) std - build 14896
Asus RT-N16: DD-WRT build 19545 (kingmod)
If I have a brand new router and update to the latest Asus firmware, and then run the cfe_update script, will that take care of backing up my old CFE?
Yes if you read carefully the 3rd point on SmallNetBuilder :
ryzhov_al wrote:
3. Saving old CFE image
Please consider saving your old CFE. A ./cfe.old file will be placed in the same dir with update script, save it to some safe place.
Dumb question probably: but how do I get the backed up cfe.old from the router to my computer? I ran the script, and the CFE update was successful. I just now want to make sure I back up that file before proceeding with DD-WRT.
If I have a brand new router and update to the latest Asus firmware, and then run the cfe_update script, will that take care of backing up my old CFE?
Yes if you read carefully the 3rd point on SmallNetBuilder :
ryzhov_al wrote:
3. Saving old CFE image
Please consider saving your old CFE. A ./cfe.old file will be placed in the same dir with update script, save it to some safe place.
Dumb question probably: but how do I get the backed up cfe.old from the router to my computer? I ran the script, and the CFE update was successful. I just now want to make sure I back up that file before proceeding with DD-WRT.
Never mind: I ran tftpd on Windows and did a tftp transfer of cfe.old and cfe.new from the router to my computer.
If I have a brand new router and update to the latest Asus firmware, and then run the cfe_update script, will that take care of backing up my old CFE?
Yes if you read carefully the 3rd point on SmallNetBuilder :
ryzhov_al wrote:
3. Saving old CFE image
Please consider saving your old CFE. A ./cfe.old file will be placed in the same dir with update script, save it to some safe place.
Dumb question probably: but how do I get the backed up cfe.old from the router to my computer? I ran the script, and the CFE update was successful. I just now want to make sure I back up that file before proceeding with DD-WRT.
Never mind: I ran tftpd on Windows and did a tftp transfer of cfe.old and cfe.new from the router to my computer.
Managed to flash fractal's build 20363 after doing the CFE update. All was working well, but the range on the 5 GHz radio wasn't as good as I had hoped it would be. Honestly though, I never tried the stock firmware so can't say if it's a DD-WRT issue.
I then tried Shibby's Tomato build 1.28 for 64k CFE and as it was my first foray with Tomato, I actually preferred the UI over DD-WRT. Sadly, there was no improvement on the 5 GHz range and the QoS settings are horribly complicated in Tomato as compared to DD-WRT.
I'm going to try going back to stock to test the 5 GHz range and then will most likely eventually switch back to DD-WRT since I need the bandwidth monitoring, QoS, static DNS, DDNS, etc.
dont expect high range on 5ghz. ist has less than 2,4 ghz _________________ RT-N66U @ Build 25697M K3.10.63
TL-WR842ND v1 @ BS-build 23919 WDS AP
TL-WR841ND @ BS-build 23919 WDS Client
TL-WR841ND @ BS-build 23919 Client Bridge ( Routed )